Longest option argument not used as internal/variable name

It seems that with 7.0 the longest option argument isn't being used as the internal and variable name.
https://github.com/pallets/click/blob/2c622eed402c64e1645db3904c2410f6c05fbf19/docs/parameters.rst#L93-L95

the internal name is generated automatically by taking the longest argument

import click
import click.testing

print(click.__version__)

@click.command()
@click.option(
    '--temp',
    '--temporary',
    'temporary',
)
def good(temporary):
    pass

@click.command()
@click.option(
    '--temp',
    '--temporary',
)
def bad(temporary):
    pass

def click_runner(command):
    print(command.name)
    runner = click.testing.CliRunner()
    result = runner.invoke(
        command,
        [],
        catch_exceptions=False,
    )
    print(result.output)

click_runner(command=good)
click_runner(command=bad)

https://repl.it/@altendky/click-67-unexpected-keyword-argument-1
6.7
good

bad

https://repl.it/@altendky/click-70-unexpected-keyword-argument-1
7.0
good

bad
Traceback (most recent call last):
  File "python", line 37, in <module>
  File "python", line 32, in click_runner
TypeError: bad() got an unexpected keyword argument 'temp'

https://repl.it/@altendky/click-2e856a5-unexpected-keyword-argument
7.0
good

bad
Traceback (most recent call last):
  File "python", line 37, in <module>
  File "python", line 32, in click_runner
TypeError: bad() got an unexpected keyword argument 'temp'

Seems to relate to #793/#794 where a different part of the docs were referenced.  So I guess the question is which one do we want?
options:
https://github.com/pallets/click/blob/b1b8c48345d8accc4dea262b8a41ac5ac1de3af2/docs/options.rst#L41-L43
vs parameters:
https://github.com/pallets/click/blob/2c622eed402c64e1645db3904c2410f6c05fbf19/docs/parameters.rst#L93-L95

@altendky I would suggest to revert to the old (pre #794) behaviour to fix the regression, and align the documentation with actual implementation instead.

Thansk! Seems better to revert to the old behavior and update the docs.

@davidism should the PR be against 7.x or master?  Am I supposed to modify CHANGES.rst?

It should be against 7.x. You can add a change entry that points to the pr now that it's submitted.

This brokes backward cvompatibility. Click used to use the last --arg (as I thought but holds in my case) - now it uses the first (or maybe it's the first longest).

@kiwi0fruit are you referring to #1149 not properly reverting functionality?

I'm presently setting up the tests against 6.7 as the reference since the point is to revert to that functionality, but with consistent docs.

It's kind of tempting to deprecate this 'feature' and just say 'if you have multiple of the longest type of parameter, specify the name'.  Or maybe provide a marker so you don't have to repeat.  Maybe '+--the-default' or somesuch?  I dunno, explicit over implicit and all.  This just seems like a bit of a fiddly mess with little benefit.

Why not have it backward compatible?

I thought that he picked the last in order given. What makes you think that it's related to argument length? (if we speak about 6.7)

Why deprecate order based selection when it works?

@kiwi0fruit please stop having this discussion. 6 -> 7 was a major version, it's not required to maintain compatibility. That said, we've already acknowledged that we want to adjust the behavior. If you want to provide constructive feedback, look into comparing the code and behaviors of the two versions with actual examples.

The docs.  Though admittedly above I believe I linked latest docs, not 6.7 docs.  But, even 6.7 docs were inconsistent.
options:
https://github.com/pallets/click/blob/df0e37dd890d36fc997986ae6d2b6c255f3ed1dc/docs/options.rst#L19-L20
parameters:
https://github.com/pallets/click/blob/df0e37dd890d36fc997986ae6d2b6c255f3ed1dc/docs/parameters.rst#L83-L88
I also checked out 6.7 and pulled a branch to validate tests against.  The tests in #1149 did not pass so I adjusted them as follows so we could have an actual 6.7 reference.  I am happy to add more cases to that branch so as to keep them all together.
https://github.com/altendky/click/commit/bcd70a3702dffdca92bd1433b69de87a25998bbb
@pytest.mark.parametrize('option_args,expected', [
    (['--aggressive', '--all', '-a'], 'all'),
    (['--first', '--second', '--third', '-a', '-b', '-c'], 'third'),
    (['--apple', '--banana', '--cantaloupe', '-a', '-b', '-c'], 'cantaloupe'),
    (['--cantaloupe', '--banana', '--apple', '-c', '-b', '-a'], 'apple'),
    (['-a', '-b', '-c'], 'c'),
    (['-c', '-b', '-a'], 'a'),
    (['-a', '--apple', '-b', '--banana', '-c', '--cantaloupe'], 'cantaloupe'),
    (['-c', '-a', '--cantaloupe', '-b', '--banana', '--apple'], 'apple'),
    (['--from', '-f', '_from'], '_from'),
    (['--return', '-r', '_ret'], '_ret'),
    (['-f', '-r', '--from', '--read'], 'read'),
    (['-w', '-t', '--write', '--to'], 'to'),
])

Sure, 6->7 is a major version but I wouldn't want to change just because.  But, I think that the interface is bad if nothing else because we seem to have three definitions that all conflict (options: "first long option", parameters: "longest argument", code: picks last long).  How about we make the rule super simple and just require people to be explicit in the face of ambiguity.  shrug  I would think the + prefix or similar wouldn't be particularly onerous.
Anyways, I'll hold off on making any changes to the PR until we decide what behavior we really want.  At this point we may have to consider that 6->7 breaking may not be preferred but was 'technically acceptable' while reverting the functionality in 7->7.1 (or whatever this might end up in) would be a regression of sorts.  I dunno.  I just put an explicit name in our code so we could stop caring what happens here (as far as our code working).

Oh, I see. So this mistake was intentional. OK. There is nothing I can add
on this.

@kiwi0fruit, I never meant to advocate changing the interface from 6.7.  I just made the mistake of looking at the docs rather than the code.  At which point we could even argue that 6.7 actual behavior was a bug since it didn't match either piece of documentation.  But still, when you are stuck with 3 inconsistent 'policies' and now have new functionality in a new major version...  Let's at least consider where we should end up.  Then how to get there with the least surprise and frustration.
Side note, this made me start looking into actual CI.  Not just build on each commit, but integrating latest on each build.  Not that this change was that horrible, it just triggered me to actually act and try to setup CI with Tox, which was reasonably painful.  I added a few extra jobs to do latest deps, latest --pre deps, and vcs deps.  Hopefully this will help us catch these things prior to release.  Though having a prerelease on PyPI could also help encourage people to use things before a full release.

If you need to unify and break backward compatibility it obviously
better unify to most common use-case (what interface users of click library
use most often?). I'm not sure what it is so it needs investigation.

@kiwi0fruit, you dislike requiring an explicit decision of the developer?

@altendky I don't really care. I don't have a packege that would break. I am a passer by that saw people breaking backward compatibility and warned them about it as it almost always a mistake.

@kiwi0fruit, consider that this ticket exists exactly because we observed the change...

I haven't thought it through a lot but just so we have something (more) concrete to consider...

Immediately

Indicate old interface as deprecated and raise a warning for any use of it
Implement a new explicit interface

+ prefix to specify the parameter which should be processed to create the variable name
If no argument starts with a +, retain 6.7 functionality
Update docs to reflect new explicit rules

This includes removing reference to old rules that didn't even match the code

If any argument starts with + use the new strict and explicit rules
New strict and explicit rules

If other than a single argument starts with + raises an exception
Old-style explicit name specification (thename without any leading -'s) must be adjusted to start with a +.  Without is an error.

Later (I dunno, two years?  Click 8.0?)

Strictly require new explicit rules

By the way. If the question is only in mappings of options to arguments
(and there are three different ways of such mappings unfortunately) then
they all can be unified by intelligent guesser that returns solution when
there is only one solution and returns error when there are more than one
solution.

Or may be it returns error also when any one of python function arguments is present in more than one list of CLI options.

I considered there being possible improvements to automatic selection.  It didn't seem like they would provide much value over just checking for an explicit choice by the developer.  Explicit has the upsides of simple everything for everyone. Nobody has to remember anything beyond the explicit indicator.

And a single extra character seems like a minimal burden.

So we have two things to address.  How do we handle the documentation/code disagreement right now and where do we want to go in the future.
Right now we should do one of...

[ ] Correct docs to match 7.0 code behavior
[ ] Change code and docs to match 6.7 code behavior

Later, none or more of...

[ ] Require explicit variable name specification
[ ] Provide a less repetitive way to specify the name explicitly

And maybe also consider doing prereleases in hopes to catch stuff like this before release next time.  Maybe, I dunno.
(@sirosen)

Well, totally forgot this discussion happened, then did some digging here https://github.com/pallets/click/issues/1420#issuecomment-595903444 when it was brought up again. Based on that, my decision is that the change to use the first argument, preferring double dash over single dash, was intentional, and the docs should be updated to be clear about the rules as they currently work.


No results for Windows 11 and Windows 10 22H2 for Microsoft

When searching for Windows 11 and Windows 10 22H2 for Microsoft as a Manufacturer, DAT says that there are "No matches found. Please try another OS/Build." Selecting any other Windows version works correctly.
Choosing HP or Lenovo will producer models.
Is this an issue with Microsoft?
I am using version DAT 7.2.0 and using the latest Configuration Manager 2207 with Hotfix Rollup (KB15152495).

It seems that the filtering is wrong, according to the DriverAutomationtool.log it filter - Filtering models based on Windows 11 build 21621 but it should be build 22621


process.env.npm_package_description is no more available with npm v7

https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate/blob/d764ce1405b5ce3af84a362947bd1f56c117cbdc/webpack.config.js#L64
according to https://github.com/npm/rfcs/blob/latest/implemented/0021-reduce-lifecycle-script-environment.md

Remove npm_package* values from the script lifecycle environment.

Wrong place. I think no one is maintaining the project anymore.


table problems

With a bleeding edge branches of mathjax and sre, tables appear broken. Let's collect examples and investigate.

This looks like a downstream issue. Closing for now.


When dismissing a search result, the total result count should decrement by 1, or indicate dismissed results count

I do not see a duplicate of my issue:

So I'm in the clear.

VSCode Version: 1.32.0
OS Version: Windows 10 1809 Stable

Steps to Reproduce:

In Visual Studio Code, click on the "Search" sidebar menu item to bring up the huge Search menu.

Search for a common word used quite a lot. Like "a", "let", "var", "i", and so forth.
When the Search displays the total results count, dismiss a few of them.
The total results count should decrement by 1 per dismissal, or indicate both the original total results count and the remaining non-dismissed total results count side by side when dismissing the search results. For example:

Does this issue occur when all extensions are disabled?: Yes

For me, it does decrement. You don't see that? You are clicking the 'x' icon on a result row, right?

@roblourens It doesn't.

Ok, so I was about to get it to decrement, but that's not done in real-time.

That's right, I thought you were talking about the total shown at the top ("x results in y files") in your original post.

This also happens when a new match is added or deleted in an existing file match.


poor performance on sherlock holmes devil's daugther

Software information
Sherlock Holmes Devil's daughter
System information

GPU: amd gigabyte rx460 4gb
Driver: mesa 19.0.1
Wine version: Proton 4.2
DXVK version: 1.0.1
CPU: Ryzen 1600
Ram: 12gb ddr4 2400mhz

Apitrace file(s)
https://drive.google.com/file/d/1LjQPajXke2s8_GT5Nf92RQWwY0xajyje/view?usp=sharing
Log files

d3d11.log: https://drive.google.com/file/d/1-1VGGWcT_1_5Mcx7cwY0YT7aifkAZljz/view?usp=sharing
dxgi.log: https://drive.google.com/file/d/1kKwWEi5HGEbE7EyqUsyi8VzN6NmYRETJ/view?usp=sharing

And what exactly is "poor performance"?

steam version doesn't work cause of denuvo you need gog version.

And what exactly is "poor performance"?

freezes, lags

This is completely normal as long as new shaders are being compiled, and not a bug.

*up

This is completely normal as long as new shaders are being compiled, and not a bug.

too bad is barely playable but to be fair it happens with other games like shadow of the tomb raider with my system, maybe I need a more powerful gpu. closing.

Some games are worse than others, Shadow of the Tomb Raider is also known for being problematic due to the sheer number of different shaders it has. There's no reasonable way to fix this unfortunately.

Some games are worse than others, Shadow of the Tomb Raider is also known for being problematic due to the sheer number of different shaders it has. There's no reasonable way to fix this unfortunately.

I could try using AMDVLK driver instead, would that help?

Not really. The proprietary driver is a bit faster, but also has issues with a lot of games (including SotTR).


Fix legacy client feature config

Legacy Client's feature config seems not correct, and example has compile error.

Thank you! Looks like rustfmt is grumpy.


onboarding key generator package rename as it does not implies what it does

renaming the package for the onboarding job as it does not imply what it does. Renamed to onboarding-validation-keys-generator

@leelavg @nb-ohad please review.

/lgtm

@rchikatw pls make sure that you inform build team about Dockerfile changes.

Hah, I had an earlier review comment that didn't get sent... might as well at least actually publish it.
I don't see why there needs to be a change to the directory name at all, it just looks like introducing needless build changes for the sake of being more verbose. And, as it was, it seemed fine that the directory name itself was kinda vague since the artifacts produced from it are an implementation detail.

pls make sure that you inform build team about Dockerfile changes.

Sure...Thanks for pointing that out


Backup not compatible

When i try to create a backup i see the following message. Both apple devices. JW Library version on both iOS is: 14.0.2(316115)

If you're interested, I made a quick and dirty Python script to merge my backups while this app gets updated.
Here it is:
https://github.com/sircharlo/jwl-backup-merger

Thank you for opening this issue!
Unfortunately, since the playlist update of JW Library the version of backups have been inconsistent, sometimes even switching to a newer (v14) one and back (v13) without an apparent update of the app. As I don't want to risk losing data, I'm currently trying to play safe and only support one backup version at a time (I fear that there might be inconsistencies that could lead to issues after the merge).
I heared from other users that after some time the backup version was updated for them, so they could merge again. This might be the case for you as well (this years convention theme was quite fitting in this case 😅😄). I hope that the inconsistency won't last forever. At the same I will continue to find out if it's safe to support both versions. I will keep you updated.
Sorry for the trouble. I hope that the issue will not last for too long and you can merge again soon 😊

Hi @AndreasSko, I have the same issue. What is odd is that the issue happens when trying to merge a backup from iPhone but it doesn’t happen with a backup from iPad. Both are in the same version of JW Library 🧐

If you're interested, I made a quick and dirty Python script to merge my backups while this app gets updated.
Here it is:
https://github.com/sircharlo/jwl-backup-merger

Does this need to be installed and ran on Windows?

If you're interested, I made a quick and dirty Python script to merge my backups while this app gets updated.

Here it is:

https://github.com/sircharlo/jwl-backup-merger

Does this need to be installed and ran on Windows?

It's a Python script, so it could run on any system that runs Python.

Update to this issue: today JW Library was updated to version 14.1. I ran a backup from the iPad and another from the iPhone. They both worked in the Merger. I then imported the backup created by the Merger in JW Library on iPad and ran another backup from it. When I tried to import this last created backup from iPad, the Merger wouldn't work it anymore. So I'm guessing that something inside the code is making this happen. Not sure if I could make myself clear enough with the explanations.

Confirmed. The two backups to be merged are 3.8MB each, but the resulting file is just 2 MB. Trying to use the new 2MB file as input fails.


[Bug] Similarity match threshold is not updated in title

In Similarity match evaluation the title contains a constant threshold and is not updated when we adjust the slider.
Fix suggestions:

Make it dynamic with the the default value similar to the one in the slider
Consider deleting it as we already have the information in the slider itself?

https://github.com/Agenta-AI/agenta/assets/6608260/6c29c5d7-ebb9-42bb-8450-6367c6ca3b42

Hey, I would like to work on this issue.

Hi @mrkirthi-24, thanks for taking this on. Assigned!


[5.2] Add Arr::unDot() method

Expand a dotted-key array. It acts the opposite way of Arr::dot().
Note: I am not sure about the method name itself (is it good or not). If acceptable for merge, then we can change the method name.

Interesting idea. :)

Past attempt #5663

Already rejected in #4292

@lucasmichot even if empty, is it a problem to go on? cause it will not enter loops and empty $results will be returned, right? Thoughts?

Let's see what happens after two years ;)

@lucasmichot even if empty, is it a problem to go on? cause it will not enter loops and empty $results will be returned, right? Thoughts?

No need to go through a loop for an empty array either ;-)

@JosephSilber Done. Thank you!

Holding off on this. Useful as a package if you need it.


spring-cloud-gateway can not start with cloud-nacos-discovery version 0.2.2.BUILD-SNAPSHOT

Which Component
Nacos Discovery 0.2.2.BUILD-SNAPSHOT
Describe the bug
spring-cloud-gateway can not startup with cloud-nacos-discovery in version 0.2.2.BUILD-SNAPSHOT
Error logs
No qualifying bean of type 'org.springframework.cloud.alibaba.nacos.NacosDiscoveryProperties' available: expected at least 1 bean which qualifies as autowire candidate
Additional context
MacOS  、Java8 、 0.2.2.BUILD-SNAPSHOT

There is the example on git .
branch:master
path: spring-cloud-alibaba/spring-cloud-alibaba/spring-cloud-alibaba-examples/nacos-example/nacos-gateway-example/nacos-gateway-discovery-example
try it.

NacosDiscoveryProperties bean  from NacosDiscoveryClientAutoConfiguration move  NacosDiscoveryAutoConfiguration

@SmileTower  good suggestion, thank you.
@leiruiqi fixed now.

Yes , spring-cloud-gateway can startup with newest Nacos Discovery 0.2.2.BUILD-SNAPSHOT.
But, it not works right，the spring gateway can not discovery any client with nacos.

@flystar32 I saw you last commit for spring cloud discovery，it works good with spring-cloud-gateway now . thank you.


Tracking: 1 to 1 DMs MLS (Mobile)

MVP

[ ] Permissions - Ability to create a group chat that only has two members and cannot have additional members added (Medium)

[ ] New permission type to identify a 1to1 conversations
[ ] Way to handle adding just one person to the group after create (possibly and immutable list called allowed_members)
[ ] Validation

[ ] 1to1 Group should not be able to be named
[ ] You cannot leave a 1to1 Group
[ ] Should not see a group membership change codec on first send

[ ] Duel Sending - Can still receive messages from non V3 clients (Medium)

[ ] Welcome messages for 1to1 should be hidden in libxmtp for clients that don't support 1to1 yet
[ ] Resolver logic for sending messages

[ ] Resolve the wallet_address to an inbox_id

[ ] If it can’t be resolved, abort the process. Dual-send isn’t possible here.

[ ] Check if there is an existing 1:1 convo with that inbox_id

[ ] If not, create one and invite the other member

[ ] Send the message

[ ] Validation

[ ] A client that supports V3 can still recieve a V2 only message
[ ] A client that supports only V2 can still get messages sent from a V3 client
[ ] A client that supports V3 can send a V2 and V3 message
[ ] A client that supports V3 does not show double messages

[ ] Conversation History - New installations only see one 1to1 conversation (NEEDS SCOPING - Large)

Follow ups

[ ] V2/V1 Removal

[ ] Period of read only
[ ] Clear datadog metric tracking
[ ]	Import of all V2 messages into V3 database

[ ] Dedupe on message unique identifier

Note to self: hold off on converting any of these into GH issues/importing into ZH.

I think we also need a replacement for personal preferences, otherwise there's no point in starting the 1:1 migration earlier than that? And I think that's a fairly substantial work item. What do you think @neekolas?


Threading issues

As the number of tests grows, thread unsafe behavior creeps out of the woodwork. I have no idea what is causing it but something is breaking parallel running of tests. I have to babysit Travis to restart it if it fails randomly, and locally I usually have to run sbt test followed by sbt test-quick to re-run anything that fails to make sure it isn't actually failing.

Would it possibly be the case that any of these failing tests are verilator runs? There's a path collision problem in chisel3 verilator invokation that I can PR my fix.

The fails that I'm seeing are actually errors during FIRRTL execution.
Is the problem you're referring to the one where if you have a verilog file in the chisel3 (or firrtl) directory with the same name as one in a /tmp/ directory that you're trying to build, Verilator will grab the wrong one?

It seem like firrtl is thread unsafe again.

@jackkoenig "Random invalid strings should fail" in StringSpec keeps failing on travis. It may also affect threading tests?

I have PRed a fix to StringSpec. That shouldn't have anything to do with threading though. If the Threading tests are failing, something is most likely not threadsafe.

I believe the issue is in 94b28438d1658d0835122b8c27bbbf3753892475
I haven't figured out what exactly in the code is doing it, but it seems the previous commit does not fail the MultiThreading test.

I'm pretty sure the issue is that the instance loop checking uses mname which is a global variable

Running CI tests under Jenkins has revealed another concurrency issue. We find cases where tests are caught in a tight loop in:
/* inlined HashTable.findEntry0 to preserve its visibility */
private[this] def findEntry(key: A, h: Int): Entry = {
  var e = table(h).asInstanceOf[Entry]
  while (notFound(key, e))
    e = e.next
  e
}

due to the fact that e.next point to e.
This has been traced to the following code in src/main/scala/firrtl/passes/RemoveAccesses.scala:
// This improves the performance of this pass
private val createExpsCache = mutable.HashMap[Expression, Seq[Expression]]()
private def create_exps(e: Expression) =
  createExpsCache getOrElseUpdate (e, firrtl.Utils.create_exps(e))

This cache needs to be protected against simultaneous access from multiple threads and the problem can be remedied by:

using a per-circuit cache,
converting RemoveAccess from an object to a class and making it scoped per transform instance.

I'll close this and open a new issue - we should have new issues for each threading issue we find and correct.


WhisperX integration

In this PR I want to add the full functionality of the whisperX project with the ability to get advanced subtitles and split any audio into parts.
WhisperX Project : https://github.com/m-bain/whisperX
Separate Speakers into Parts Project: https://github.com/daswer123/split_audio_speakers
UI

Integration completed but not within the scope of this PR


Add support for CMSIS-NN int8 transpose and padding operators

BUG=New operator support

CMSIS-NN SHA is already up to date so cmsis_nn_download.sh script should not be updated. Also AddTranspose in micro_mutable_op_resolver.h should be updated to support quant specific registration.

Thanks for the review, should be all good now


Fix some Swift 5.6 compatibility issues

We've had some regressions under Swift 5.6 in the latest changes, particularly around using implicitly opened existentials, which is a 5.7 feature. I've tested these changes using Swift 5.6 on Linux and macOS 12.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

@swift-ci Please test


github .gitingore bug

github .gitingore bug
bug

create 000-xyz folder, add files

ignore 000-xyz/  folder in .gitingore file, push to github

000-xyz/  folder, still in github ❌

solution

move 000-xyz/ to other place

commit and push to github

recover 000-xyz/ to repo ✅

.gitattributes


#6343: QA demo using Functional Bloom CausalLM model

This PR contains end to end demo of ttnn_functional_bloom, ttnn_optimized_functional_bloom for Question Answering.

CI passed. Link here


Is X448 planned to be supported as an alternative alogrithm to X25519

As the title mentions, just wondering if there is a plan to introduce X448.

Already answered in a previous issue:


Support for projects with "Multiple prompt styles"

Hi, I spent today messing with Promptfoo, it's a cool project.
I see that the design is essentially meant to do "horizontal" comparisons of prompts intended for the same use case for comparative performance evaluation. Are there plans to support multiple of these sorts of prompts in one config?
For example, in a single project, I might have a bunch of prompts that are used for different things. It'd be nice to be able to get everything working in the same config. It doesn't seem to work well currently as prompts for different use cases would have different variables entirely.

Thanks for comment.  This is similar in spirit to #57, where the solution is to make additional prompt configs but that is tedious (and does not lend itself well to reusability).
One option would be to let developers set up multiple test suites in a file.  Another option would be to let you pass multiple test suite configs to the promptfoo eval runner..

Thanks for the quick reply. It is pretty similar, but I think 1 difference would be that in the use case I'm considering, each prompt could have very different variables. I actually don't hate multiple prompt configs, since they really are different, but it's a bit clunky, you're right.
I think allowing multiple test suites in a file makes sense to me, everything would work the same as now, except there could be multiple test blocks pointing to a prompt file and a bunch of tests?

We also have a slightly different use case, where we have more complicated chains of prompts on service side. We don't really want to test the individual prompts, but instead the final output of these chains (basically simulate what a user would see at the end -> have promptfoo call our API with certain options).
For this we implemented a custom provider and apply a patch (via patch-package) on promptfoo which simply passes down the vars object to the providers, in addition to the prompt string.
For us, the prompt string given to promptfoo is just Run #1 etc and instead of the prompt, we use the vars which are set on the individual tests and send them to our API. The result string is then returned to promptfoo as usual.
We trigger promptfoo.evaluate inside of a custom script and we can specify a suite of individual tests to run (ie yarn test:ai foo or yarn test:ai bar will each only pass their respecitve test cases to evaluate).
The TestCase object in our case gets extended with specific additional (typed) keys in the vars object, where we can use our existing types for this API request (so it's all nicely typed across the board) - it would be nice if TestCase would accept generics for its vars 🤔
We might create some PRs with suggestions / additions here for promptfoo, but since I'm going to be on vacation the next 2 weeks it could take some time 😅

I'm having similar cases. I need to run multiple totally different prompts against the same set of LLMs. Each prompt has different variables and assertions. The only way I can see now is to write different config for each prompt which is ok as I can manually combine the results. But it would be great to be able to see the results in the same report.

Hi @zhlmmc,
I think Scenarios solve your problem.  It's a way to include multiple sets of vars and tests on the same set of LLMs.
@flipace I'm late to your feedback, but https://github.com/promptfoo/promptfoo/commit/d9623cbd2814919a9046b97f59673bb8f31d7804 makes TestCase generic and also passes context: {vars} as a second argument to callApi.  It will be in the next release :)

Hi @zhlmmc,
I think Scenarios solve your problem. It's a way to include multiple sets of vars and tests on the same set of LLMs.
@flipace I'm late to your feedback, but d9623cb makes TestCase generic and also passes context: {vars} as a second argument to callApi. It will be in the next release :)

Hi,
I have tried to play with the Scenarios, but it seems not working in my case. What I need is actually "prompt-test" combination not "data-test" combination. In my case, all prompts are fixed prompts that do not need variables to input at runtime. The ideal output looks like this:

Prompt
GPT-3.5
GPT-4
Llama2
ChatGLM
PaLM

1
score
score
score
score
score

2

3

4

5

Not sure if there is a way to achieve this, thanks!

To get this sort of layout, I would suggest the following:
prompt.txt simply outputs the prompt var:
{{ prompt }}

promptfooconfig.yaml sets multiple providers, with each unique prompt as a var:
prompts: [prompt.txt]
providers: [openai:gpt-3.5-turbo, openai:gpt-4, llama2, chatglm, palm]
tests:
  - vars:
      prompt: <insert prompt 1 here>
  - vars:
      prompt: <insert prompt 2 here>
  - vars:
      prompt: <insert prompt 3 here>
  # ...

This will produce a table similar to what you have outlined above.


Correct publicPath in webpack config

Hot reloading was not working due to a config error as described here:
https://github.com/gaearon/react-hot-loader/blob/master/docs/Troubleshooting.md#syntax-error-unexpected-token-

Ah, thanks for that!


Plugins are not handled by Sbtix yet

Currently, plugins are still downloaded by SBT from the internet as usual. Ideally Sbtix should download these as well, and add them to the repo.

Do you have an ideas on how to go about fixing this? My research on sbt seems to indicate that the implementers have given very little thought to non connected development of any strip. My approach in supporting Erlang's build system rebar (which has a similar problem) was to actually patch the build system. The down side of that is that rebar in nix is different then rebar everywhere else. The upside is it is impossible for it to hit the network.

@ericbmerritt
Sort of. SBT allows you to apply plugins to the "plugins project" (and so on, going on forever). So in the worst case it should be doable, with the caveats that the plugin has to be applied "one level higher" than your highest other plugin, and that it would slow down genNix significantly. It would probably also make it a bit more annoying to invoke...
A better solution would be if we could dynamically run the task in the context of those projects as well, but I'm not sure what to do about that...
Making SBT load it from our repo afterwards should be a much easier affair: AFAIK, SBT loads the repos to use from the launcher config file, which we can replace with our own that only contains the Sbtix repo.

Using SBT's global plugins feature might be useful in solving this problem.

Pull request https://github.com/teozkr/Sbtix/pull/8 provides a method to easily load the sbtix plugin as a global plugin.  It is then possible to run the genNix command against the plugins project with the command: sbtix "reload plugins" genNix

This coursier issue might become a problem: https://github.com/alexarchambault/coursier/issues/292

adding resolvers to simple example's plugins.sbt seems to almost solve this problem:
resolvers += Resolver.typesafeIvyRepo("releases")
resolvers += Resolver.sbtPluginRepo("releases")

With those resolvers in place I get:
[info] Fetching file:/home/haste-chris/.coursier/cache/v1/https/repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/classpath/0.13.12/jars/classpath.jar
path is ‘/nix/store/byqri0fzcsphlcn54wi3vkh42llsjgv9-classpath.jar’
[info] Fetching https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/classpath/0.13.12/jars/classpath.pom
error: unable to download ‘https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/classpath/0.13.12/jars/classpath.pom’: HTTP response code said error (22)
java.lang.RuntimeException: Nonzero exit value: 1
        at scala.sys.package$.error(package.scala:27)
        at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.slurp(ProcessBuilderImpl.scala:131)
        at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.$bang$bang(ProcessBuilderImpl.scala:101)
        at se.nullable.sbtix.CoursierArtifactFetcher.fetchChecksum(CoursierArtifactFetcher.scala:59)
        at se.nullable.sbtix.CoursierArtifactFetcher.buildArtifact(CoursierArtifactFetcher.scala:54)
        at se.nullable.sbtix.CoursierArtifactFetcher$$anonfun$buildNixRepo$2.apply(CoursierArtifactFetcher.scala:40)
        at se.nullable.sbtix.CoursierArtifactFetcher$$anonfun$buildNixRepo$2.apply(CoursierArtifactFetcher.scala:27)
        at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
        at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)

and I wonder if it could be because of how sbtix is resolving pom files.  Or because it is looking at pom files at all.  I think most plugins are stored in ivy repositories and not maven ones because plugins need ivy's extra attributes feature.

Fixed issue #1 and am now able to generate a repo.nix for the plugin project, it finds the ivy.xml, pom and jar artifacts. Am probably going to have a problem when I try to use it though, since I need to build Ivy formatted repos.


Add AWS cloud guide

Describe changes
This PR adds a step by step guide to run a ZenML pipeline on AWS.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Other (add details above)

You mean aws cli commands for each step?


[WANT HELP] How the Deployment ID is generated?

Subgraph manifest is fully resolved, this means finding each and every local file and uploading them to IPFS. For each of the uploaded file extracted from your original manifest, the original link in the document is replaced by something like /ipfs:<hash> (I don't recall the exact format) where <hash> is the hash of the files uploaded and computed by IPFS client.
Then, once you have this final resolved file where are local files link have been replaced by resolved IPFS hashes, you upload again this final file to IPFS and the hash of this resolved file is the deployment ID Qm....


fix: add project validation

:tada: This PR is included in version 0.105.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


WIP: Add hooks variant of createAnimatedComponent

Summary
This is a continuation of https://github.com/facebook/react-native/pull/24218
As mentioned in that PR by maintainers, hooks based variant is preferred to make animated components strict-mode compatible. This PR adds that.
Note: The old variant still exists in the code and can be used by providing false as the second argument to createAnimatedComponent.
related to https://github.com/facebook/react-native/issues/22186
Note: Will squash/cleanup history at the end
Changelog
[General] [Fixed] - Converted createAnimatedComponent to be compatible with StrictMode. Old behaviour can be retained by providing false as the second argument.
Test Plan
Tested all animation examples in RNTester to make sure they still work. Created a component that used refs to access getNode and it worked the same for both the old and new implementation. Finally I also ran some real-world apps that I have built at work with the code and did not notice any regressions.

Going to be fixing the tests tomorrow.

Hey @Jyrno42, what's the status of this PR?

It seems like this PR got stale so I'm going to close it. I'm really curious to see whether we can build a better API for Animated though, or whether we should start recommending reanimated to people.

OK. Will look around for that before I start working on this again (once I have more time available).


Implement and test transport::UTransport

This is the full implementation, and all the testing. Anything that wasn't done in #113.

Recommend Uzi for this

This test has been written as part of recent bug fixes


Replace Node Exporter with Alloy?

Part suggestion and part note in case anyone else runs into it -- I was working to deploy this on a cluster which included several nodes that were running CEPH - one of the options with current versions of CEPH is to have nodes run Node Exporter. This caused my attempt to deploy the helmchart for grafana-k8s-monitoring to fail as it couldn't start node exporter due to a conflict on the port. My immediate solution was to disable the CEPH associated node-exporter.
Better though, I think, might be to consider using Alloy rather than node-exporter here, unless there's some specific reason not to. Alloy includes node-exporter capabilities under the covers, if I'm not mistaken?

Thanks for posting this!
There are a few reasons why this chart prefers to deploy its own copy of Node Exporter and not use Alloy's built-in version of prometheus.exporter.unix (essentially Node Exporter itself).
First is separation of concerns. Node Exporter can do it's thing: building node metrics, Alloy does its thing: being a telemetry data collector.
Second is deployment pattern. If we use Alloy as Node Exporter, we need to deploy Alloy as a daemonset with elevated permissions to get access to the node. So, like point 1, we leave that to Node Exporter, which has a smaller footprint than Alloy.
Third, and actually the biggest reason is that sometimes Node Exporter already exists in the cluster, so let's make it simple to use what's already there and not duplicate work. You can configure this chart to still gather Node Exporter metrics, but not deploy Node Exporter itself.
If you set this:
metrics:
  node-exporter:
    labelMatchers: ...    # Set so that it matches the Node Exporter pod instances in your cluster
prometheus-node-exporter:
  enabled: false.  # Disables the deployment of Node Exporter

It'll skip deploying NE, but tell Alloy how to find the one that already exists in the system.

Quick question, because I'm not as familiar with CEPH. Does Node Exporter show up as a pod in the cluster, or is it installed on the node, outside of Kubernetes? If the former, the above config snippet should work. If the latter, we might need to do a different path (basically, find all nodes and manually set the Node Exporter port number), but I can help with that, too.
Finally, if all else fails, we can configure the Helm chart to deploy Node exporter again, but use an alternate port number.

Re: CEPH — like many things “it depends” — Ceph has several ways it can be installed. What seems to be the current generally recommended method is to use “cephadm” which is (basically) a python script which will setup a set of docker containers (so, outside of Kubernetes) for each of the ceph “services” - one of which is Node Exporter. It also has (optional) Prometheus and Grafana services.--Dan BrownOn Jul 28, 2024, at 10:58, Pete Wall @.***> wrote:
Quick question, because I'm not as familiar with CEPH. Does Node Exporter show up as a pod in the cluster, or is it installed on the node, outside of Kubernetes? If the former, the above config snippet should work. If the latter, we might need to do a different path (basically, find all nodes and manually set the Node Exporter port number), but I can help with that, too.
Finally, if all else fails, we can configure the Helm chart to deploy Node exporter again, but use an alternate port number.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I’d probably ask whether the Node Exporter thats getting installed with the k8s-monitoring-helm needs to have port 9100 exposed externally? --Dan BrownOn Jul 29, 2024, at 05:40, Daniel H Brown @.> wrote:
Re: CEPH — like many things “it depends” — Ceph has several ways it can be installed. What seems to be the current generally recommended method is to use “cephadm” which is (basically) a python script which will setup a set of docker containers (so, outside of Kubernetes) for each of the ceph “services” - one of which is Node Exporter. It also has (optional) Prometheus and Grafana services.--Dan BrownOn Jul 28, 2024, at 10:58, Pete Wall @.> wrote:
Quick question, because I'm not as familiar with CEPH. Does Node Exporter show up as a pod in the cluster, or is it installed on the node, outside of Kubernetes? If the former, the above config snippet should work. If the latter, we might need to do a different path (basically, find all nodes and manually set the Node Exporter port number), but I can help with that, too.
Finally, if all else fails, we can configure the Helm chart to deploy Node exporter again, but use an alternate port number.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Node Exporter needs hostNetwork in order to gather network metrics on that node, but there's no reason why we cannot have it use an alternate port number.
I think if you set:
prometheus-node-exporter:
  service:
    port: 9101
    targetPort: 9101

Thanks - will give that a go. Though - is there any reason that Alloy (which I’m assuming is in use to scrape NE and forward to Grafana Cloud) couldn’t talk to NE inside of Kubernetes?
As a non-kubernetes example, I’m doing something similar with docker compose - I’ve setup a private “monitoring” network so that various containers talk to each other across that, rather than needing to expose ports externally on the host itself.

On Jul 30, 2024, at 1:12 PM, Pete Wall @.***> wrote:
Node Exporter needs hostNetwork in order to gather network metrics on that node, but there's no reason why we cannot have it use an alternate port number.
I think if you set:
prometheus-node-exporter:
service:
port: 9101
targetPort: 9101
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

If you can access the NE metrics endpoint from within a pod, then you should totally be able to have Alloy use that instead.
We currently discover NE by finding all pods, then filtering down to Node Exporter pods, then scraping them for metrics.
An alternative we could look at is discover all Nodes, then append the Node Exporter port onto the Node IP.
Can you check to see if that's a usable solution?
From within a pod, see if you can curl <nodeIP:9100>/metrics


how can i install jobe in Nginx?

how can i install jobe in Nginx?
Nginx is insalled as my httpserver, how can i install jobe in a Nginx server instead of apacher?

Jobe was intended to be a completely self-contained stand alone sandbox server. It is a complete package, with Apache as the web server. It wasn't intended to be installed on some existing server, so there really isn't a good answer to this question, which is why I never addressed it properly (sorry). However, if you really do wish to run Jobe on an existing server you could install Docker and run the Docker image JobeInABox. This uses Apache within the container but you could map the container port (80) to any external port not being used by nginx. Or you could configure nginx as a reverse proxy to redirect requests for selected URIs to the selected port.


PLANNER-530 : Workbench: Solver Editor: spent limit checkbox states are not saved

+1

master: 9deb6b7275cfd1d0b97053dc96b9a947f7277805


After stopEnvelopeTime is set on AKPlayer, a play() followed by stop() will play at faded volume instead of regular volume.

There seems to be no way to reset a FaderNode once it's been started on an AKPlayer node.
let player = AKPlayer()
player.stopEnvelopeTime = 0.1
player.load(audioFile: file)
player.play()  // plays at regular volume

player.stop()

player.load(audioFile: anotherFile)
player.play()   // plays at diminished volume.
I tried the following:

setting faderNode.gain to 1.0 ==> still same behavior as above.
player.gain to 1.0 ==> same behavior as above.
detach faderNode and set it to nil (so that when stopEnvelopeTime is set again, it'll get created once again) ... this works but causes audio latency due to allocation/deallocation in the audio path.

Is there a recommend way to reuse a player node once a fade has been triggered?
it seems loading of an audioFile or a stop() should invalidate the fade but that doesn't seem to be happening.
What am I missing? or is there a bug here?

seems like a small bug - will take a look.

can you post the rest of your test code? I don't see how your code would ever work in a loop. what am i missing?

Try what I'm using to test this -- which is the macOSDevelopment project: AudioKit-develop/AudioKit/Developer/macOS/macOSDevelopment/macOSDevelopment.xcodeproj

Loading new files into the same player is fine and the stop envelope is correct.

I'm trying this on iOS.
I just created a fresh project with a start and stop button.
pressing start button just loads a file and calls player.play(), pressing stop button calls player.stop().
I've set stopEnvelopeTime to 0.5
This setup works with latest audiokit with the fader being reset correctly.
Thanks!
g


The process '/opt/hostedtoolcache/node/16.17.1/x64/bin/npm' failed with exit code 127

Bug Report
Current behavior
Whenever I am running the CI/CD, getting the following error:
Run mansagroup/nrwl-nx-action@v2
🏃 Working in custom directory: ./
🔍 Ensuring Nx is available
/opt/hostedtoolcache/node/16.17.1/x64/bin/npm run nx -- run-many --target=lint --all
<EMAIL_ADDRESS>nx
 nx
/tmp/nx-d1766103.sh: 1: nx: not found
Error: Error: The process '/opt/hostedtoolcache/node/16.17.1/x64/bin/npm' failed with exit code 127

Code:
name: Nx CI

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v1
      with:
        node-version: 16
    - uses: mansagroup/nrwl-nx-action@v2
      with:
        targets: lint,build
        all: 'true'
        workingDirectory: ./

This error is occurring every time.

Hi @mrcreatist. This action was expecting a nx script in your package.json. I've removed this check as npx nx just work now. It is fixed and released under v3.
Thanks!


chore: ship API documentation

Relates to #3058

Summary
Ships an independent version of our API documentation and exposes more packages in typedoc. In a follow-up PR, we will remove the existing API docs and move the doc links (otherwise CI fails until we've successfully shipped the API docs).
Preview

Checklist

[x] All changes are covered by tests (or not applicable)
[x] All changes are documented (or not applicable)
[x] I reviewed the entire PR myself (preferably, on GH UI)
[x] I described all Breaking Changes (or there's none)

Had some issues with the secondary entry points that @petertonysmith94 suggested enabling. It is only a problem in the integrated API docs due to the postbuild script. I will leave them disabled for now, and will reintroduce them once we delete the postbuild script and commit to the isolated API docs.


test: stabilized tests

Added missing await-statement in test for asset.delete: Jira
Moved 3D viewer tests under revision-tests: Jira
Fixed tests for assets.retrieve when comparing lastUpdatedTime failed: Jira

:tada: This PR is included in version 2.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Expecting robust processing of irregular headdings

This input fails on my computer:
## Heading 2
#### Heading 4

After studying the question, it seems that the idea to use a markdown representation for these kind of broken unordered lists was a bad idea after all.
Conflicts with fenced code blocks among other things arise when having empty list levels between entries.
I'll switch back to a tree to html representation in the next version, removing the markdown callback option.
This will be a breaking change anyway, although not sure if anyone uses this feature.

Thank you very much for your effort!
The problem I met is that, I need real time rendering for changing texts. When user alter the content, the middle state could be unpredictable, which includes the problem described here.


AWS example data "aws_eks_cluster"

I am sorry but I am having trouble understanding what am I supposed to do on the AWS example providers file
data "aws_eks_cluster" "cluster" {
  name = ""
}

data "aws_eks_cluster_auth" "cluster" {
  name = ""
}

Why can't the provisioning of this cluster be part of the example?
What is the expected configuration of this cluster?
How does the code change if I provision the cluster in the same script instead of it already existing?
Furthermore, the example page states "Requirements No requirements."

data "aws_eks_cluster" "cluster" {
  name = "cluster-name"
}

data "aws_eks_cluster_auth" "cluster" {
  name = "cluster-name"
}

Hi @OscarGarciaF , You need to provide the name of your kubernetes cluster in the providers file which will enable the terraform provider to authenticate with Kubernetes cluster.
Why can't the provisioning of this cluster be part of the example?

You can provision cluster in the same terraform code of the example directory. This module is specific to provisioning mongodb in kubernetes. For cluster provisioning we have different modules like: https://github.com/squareops/terraform-aws-eks.
Refer to examples for more detailed configuration.
Check more such modules at https://github.com/squareops
Furthermore, the example page states "Requirements No requirements."

This is related to terraform requirements.


AIRFLOW-15: Remove gcloud

https://issues.apache.org/jira/browse/AIRFLOW-15

Test failure is due to deletion of some files, which reduces license header count.

I added some license headers to make the tests pass.

Changes Unknown when pulling c2dc2665a2fa56b5d4c5d276794aa59dbe2110f4 on criccomini:remove-gcloud into ** on airbnb:master**.

Please see my one comment about the error always printing. Also, I tried running this in my local env with no key in the Airflow connection and got the following message:
INFO:root:Getting connection using `gcloud auth` user, since no service_account/key_path are defined for hook.
WARNING:oauth2client.util:__init__() takes at most 2 positional arguments (3 given)

But I'm not sure if this matters (or even if it's on the Airflow side), since it appears to read/write the logs to GCS just fine.
One last thought -- would be great to bump this up to oauth2client 2.0 compatibility at some point. Maybe not this PR but at some point. This is the offending line: from oauth2client.client import SignedJwtAssertionCredentials, GoogleCredentials. I think the signed credentials just need to be pulled from a different module but I don't know the library well so I'm not sure.

I just saw your message on the Apache issue that you're already looking at compatibility issues :) Sorry for being repetitive. Need to get used to the split infrastructure...

Changes Unknown when pulling 844eb2c8d0806d7420e948e73c93e0fc932234e6 on criccomini:remove-gcloud into ** on airbnb:master**.

@jlowin updated based on your feedback.
Could I get a +1?
Re: oauth compatibility, I'll bump to latest as part of https://issues.apache.org/jira/browse/AIRFLOW-16

Looking good to me @criccomini. Merge away.


Better bash workaround

The bash workaround documented in the README talks about reading in the file and (re)-exporting the variables (lines in the file) 1-by-1.  There is an easier/cleaner/more-correct solution that still allows comments in the .env file (i.e., treats it like bash script still).  Basically you use set -a which will treat all variables that are set as exports.  The second set +a disables this behavior for the rest of the script (back to default behavior)
.env:
# this comment is fine
FOO=bar
VERSION=1.2

set-env.sh
set -a
. .env
set +a

See SF post on similar topic: https://unix.stackexchange.com/a/79084
Just thought I'd pass this along for other users that think the solution in the README is just a little bit too hacky 😄

This solution above is nice!  Here is what I came up with.  Might be helpful to somebody, so I'll leave it here.  I also ran into some slight issues with the bash example.
Issue 1:  the env file can't have double quotes on the value.
In the example:
SECRET_KEY="hip-hip-env-files"

This resulted in an env var of:
declare -x SECRET_KEY="\"hip-hip-env-files\""

So I stripped out all the double quotes.
SECRET_KEY=hip-hip-env-files

which resulted in
declare -x SECRET_KEY="hip-hip-env-files"

Issue 2: Blank and Commented out (#) lines cause issues
If any of the lines are commented out, or just blank newlines, it ran export which dumped all my env vars to my screen.  I fixed that with:
while read -r line; do
  [[ $line =~ ^#.* ]] && continue
  [ -z $line ] && continue
  export $line;
done < .env

Thanks for tips! Would welcome a PR to docs!

Another option, which I'm using because my .env has if[]s and other structures that don't parse nicely.

Add a "Shell script" run configuration, with "script text" = source .env; env > temp_captured_env_vars
Add a "before launch task" to my actual run configuration that executes the above shell script
Use this plugin to load temp_captured_env_vars

Instead of attempting to parse the bash file, just execute it to export whatever variables it likes and load all environment variables to a temporary file, which the plugin can handle as a .env file. This works fairly seamlessly - it will pick up changes to the bash file when you run your application, and the bash file doesn't need any particular structure or care.
WARNINGS/notes:

this loads all env vars to a temporary file. You should probably be careful not to commit this file (make sure it's gitignored or similar, or in a different directory)
the first time you run, the plugin complains that it can't find your temporary file. Just run again, and it will work.

the first time you run, the plugin complains that it can't find your temporary file. Just run again, and it will work.
There is an option for tell to ignore files it cannot find.

More importantly, the latest version includes an option to execute any file, and interpret stdout as .env or JSON/YAML with env vars. So you could add an extra script like:
. my-env.sh
env

which should output all the env vars including those that are set in the script.
Will need to update the readme.


Portainer 1.23.2 "Unable to initiate communications with endpoint"

I am facing an issue where portainer works for a few days then suddenly shows the following error:
http error: Unable to initiate communications with endpoint (err=Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?) (code=500)
When I restart the container it works for some days and then again shows the same error.
Someone told it may be an issue with docker but I checked that my docker is fine and all the other containers are working fine.
I deployed portainer using docker-compose
version: '3.5'
services:
  portainer:
    image: "portainer/portainer:1.23.2"
    container_name: portainer
    ports:
      - '8000:8000'
      - '9000:9000'
    command: --admin-password-file /tmp/portainer_password
    restart: 'no'
    volumes:
      - '/var/run/docker.sock:/var/run/docker.sock'
      - '/data/portainer_password:/tmp/portainer_password'
    networks:
      - docker_net
networks:
  docker_net:
       external: true

My Docker Version is: 18.09.7
Portainer Version: 1.23.2
OS: Ubuntu 18.04

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
As discussed on slack, requesting to upgrade docker and portainer to latest
and try

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
As discussed on slack, requesting to upgrade docker and portainer to latest
and try

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
please let us if rther assistance required on this ticket.

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
please let us if rther assistance required on this ticket.

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
abhishekjayaram wasn't found at github.com.
hello   Office 365      abhishekjayaram
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:13:53 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: Portainer 1.23.2 "Unable to initiate communications with endpoint" #QUE00000230
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser d17si14019339wrv.308 - gsmtp
DSN generated by:       ME2PR01MB2852.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:13:53 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:14:00 AM      v2app8.mail.happyfox.com MW4PR03CA0373.namprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    7 sec
3       1/18/2021
4:14:00 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    *
4       1/18/2021
4:14:00 AM      MEAPR01MB2631.ausprd01.prod.outlook.com ME2PR01MB2852.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=EbR7ndti7F+kJTTHknwUoThdOQ3KZaaCMWV3sBFiU1/yourBlJQS/qlXbmfDkmWREJ9nIDeY07QttLPyh5FgBudfSIN7HpPTCc6twLOJcVLTmvUSAfRVBG0tDnyX40dL4O9MdLe+NajtRl0r10AGVvTgA6qdJNbGsjQfciIOITI0QIhi+HNAUGZ/nHchjwqF4ZyDsNAdaZy68cpYKdJvzkva5BdggjAJuZz3PukjKM2h1NmMqHDYMdIF+NtaN3jwHhTXdIXTb1KamgH/USUBcs4IGQOQP47+WGmNrO5aJPPEZGRMymrF81fbe2ho1p2mVutzaqNQb621tV/78ZTC1A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=XSXaAohNmOGOa/ZfnTmjID3kAyzGLKuAA8asVGPT4F0=;
b=J/6hX/Ird5vbzrmqjMJmtdRBC9q8AD2WuSnK8RE4bpTyz4LGR/P5CKjWjK9osBTIxNUuBIid/A9QydXxXb0Teuvk9cnljhbw4U5oZTCl5UkfHCfszSeeRXz22oIDhx3lh8NAb2iN14UIpjWl1Vg1OKJBCcCOljDPBeYer6Qok4PEEOdiQ706Agi1WHfNwNGH/QDgyTJIweafbCChg7Kgnm9SFYZu2KtqJ5Ksw3d9f9kIoY2/eK9b+iE/skQGNPRBCOydJA1Bz4heKykLJiUU+/zr4Oo1Dr2NCGWbUU1csWwSpCN+olgd/OUmT/0TMvAQ1Wwa3BTtnLyrreOq3FckaA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=XSXaAohNmOGOa/ZfnTmjID3kAyzGLKuAA8asVGPT4F0=;
b=DPG0I0C/EpWSixu+jrFDuPyN2WPQE6VMvjEACkbU601KzfLV9DO1zQSxdYjmsxKriH+YYNvg1tuFLMhS7pWUMxZ9Ce7ngj5S+Km1uGOmijCTUwSP0vtkA9hWaZJz4zL91Wk1CtI0GCwO6HGgjHdvrXP2LPD1lHHxCJ5N+uh/PYo=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by ME2PR01MB2852.ausprd01.prod.outlook.com (2603:10c6:201:1a::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.11; Mon, 18 Jan
2021 04:14:00 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:14:00 +0000
Content-Type: multipart/alternative;
boundary="===============2598558810652011693=="
Subject: Re: Portainer 1.23.2 "Unable to initiate communications with
endpoint"
#QUE00000230
From: "Bala Natarajan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:13:53 -0000
Reply-To: "Bala Natarajan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW4PR03CA0373.namprd03.prod.outlook.com
(2603:10b6:303:114::18) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW4PR03CA0373.namprd03.prod.outlook.com (2603:10b6:303:114::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9 via Frontend Transport; Mon, 18 Jan 2021 04:14:00 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id ADD461E0318        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:13:53 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 11563e28-81c9-479e-0efb-08d8bb677bb5
X-MS-TrafficTypeDiagnostic: ME2PR01MB2852:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6790;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
FcqCmFwqdirz2P9cKsl9dfWNJg3bTukf00PTISwWzDYe+gssidyP0Eq47VGPXHGPWbWfHcEabtyncxzUbHl3ksLcHasozcIsjdebSjoYjgAKPJz9FWiTMNsatUUfsCa1x8Rstt3MJploDd8rvxnJddvuTfyHGlH4vTErl9is8zFEiQH2PkE+/DEpIZOVwtbQuXvKxg4IVANWvap9MD6v5D6mlCko+F72V3mCBzSqcb3SeWImrhM9nmcw25mMlBF04RNoWQ2Awc5i8QRt+pU5kMfSfeZT0Mtdv/3OWef7sKc8i9cQDToXXNaTQuYLjMopwvbqCzHpNz1UQum22LRy08AGpiyx3xrgH8JH3c9XR+Z/XXH5AxDsu8t0bcAnirEMp8JhjZEfqJzyoVduP+3Cpxkcjy0l2pj25YV0cIUoHq9AlIlbUXEKDx6bh8OYTnClHDrnTZt1TEN23yZD9KBtw8efegQnCeZ8FNE3grfSixNdGsNAGYbTJOCVhpzRA6YYbtOY9XA0W8j9g7a/EiRt9g==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(346002)(366004)(376002)(136003)(396003)(39830400003)(186003)(5660300002)(66556008)(26005)(103116003)(8936002)(9686003)(478600001)(66946007)(55236004)(66476007)(6916009)(86362001)(6266002)(2906002)(8676002)(3450700001)(83380400001)(36756003)(7126003)(316002)(33964004)(52116002);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?Gr+rf6kMOQKPxl2Y47YVTs6McCIEMrmEkpOtW4YSx2XYAK+pOZZnc9JApJCZ?=
=?us-ascii?Q?OtVSomJDk/sRcrGwZGrEGCTJa5N5LlBKgtb4QmcDWYe+5e/GgDqdULh8KUNY?=
=?us-ascii?Q?ffUhg6ZgRshU6ZBysScXS/znrjgoGEo/sDMtkPvh9iuc9mlTGjCo1+eURXTh?=
=?us-ascii?Q?jZidYgNxBEy2qw/KmuieC8fw3cHf6AV5S2b+c+WBeGrE1yvhN/fefBqsf5BL?=
=?us-ascii?Q?7fTSDWX5POenDjYSAlNfW1zpDDziN1yMXMHhtCN2aam5lS+gktxT2GOhyQYC?=
=?us-ascii?Q?GyXVnuX69vRKL59CpZ9nLXEekFbvk2q7KUzYjSakHmfDAj9nUhU8g+t8fIyd?=
=?us-ascii?Q?oDk+jiYfZ17GVjW1bdwKE/0XvS5cfWuR5DxLE33XgH6d+yPxj83Swz4tPjMI?=
=?us-ascii?Q?X5oNVNzPx8fJ0MdZ20OKF8FjTgbO0prPQt8y6mV2ZTHXrepMlIxYuOAFBO2u?=
=?us-ascii?Q?vYRwFYfBPV9DCET7kxxGX+ELTSH8veVkUapV4bRhtXB3MCOA8rl5GbTsjsy+?=
=?us-ascii?Q?KUlErSkCBa2B9BRTc03/utRZSGP0nkxcz3QGSbv+y+Cv/E4c/vtrXWU5TJnA?=
=?us-ascii?Q?40CBVEHl4wwzbSIXcOfoitS9nS4LZDCZnsQV5yIuXAJ1LFAw+yIdCOp+61cZ?=
=?us-ascii?Q?zlc4kaiXYd4oV9pHhM2w7ZNEiYp9Bm1pdTpR1YyoswX1EKxvm0yP3wnZ8a3x?=
=?us-ascii?Q?jCiIkGRScCdBiGmQ7WWL6iJjQg+F/efpPvvYNcBCNB2jrQ1Saj465PS4DOsX?=
=?us-ascii?Q?z4x5/mH9SMzptvsHIN92NYT2DzMy56pRJ8u3KED4FZONRuHxWFFxoCqjp4bh?=
=?us-ascii?Q?UcMDmDG2ACgoq2J7tvzhdiGn8Y2ZUwqTmNGlEqQEaAPhwSHkQvKOvjfzdUSl?=
=?us-ascii?Q?jmqy97gF0Ik3N3PAiiy3SplgD5CADLIVk/MCwR3jnDgLlvfUcanOWrZU0Lvt?=
=?us-ascii?Q?b/OcTUGPHD6/9pMd+61QIMQy1q2WcFkwGBIkXUn2DFMa1oZ4Cjg6EA8C1JV/?=
=?us-ascii?Q?RbZY?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: 11563e28-81c9-479e-0efb-08d8bb677bb5
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:14:00.5313
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: fKbemGROeViPnwPWCRldQe+urdHBBHe3+vmiBDIjwfVPV3PhBx1hjQc9/6HI/5bfesDz2OSPTQ82Xz2s0vYkbA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ME2PR01MB2852
New reply for the ticket #QUE00000230
Hi
please let us if rther assistance required on this ticket.
Bala Natarajan
Reply to this email to submit an update.

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
abhishekjayaram wasn't found at github.com.
hello   Office 365      abhishekjayaram
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:13:53 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: Portainer 1.23.2 "Unable to initiate communications with endpoint" #QUE00000230
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser d17si14019339wrv.308 - gsmtp
DSN generated by:       ME2PR01MB2852.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:13:53 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:14:00 AM      v2app8.mail.happyfox.com MW4PR03CA0373.namprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    7 sec
3       1/18/2021
4:14:00 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    *
4       1/18/2021
4:14:00 AM      MEAPR01MB2631.ausprd01.prod.outlook.com ME2PR01MB2852.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=EbR7ndti7F+kJTTHknwUoThdOQ3KZaaCMWV3sBFiU1/yourBlJQS/qlXbmfDkmWREJ9nIDeY07QttLPyh5FgBudfSIN7HpPTCc6twLOJcVLTmvUSAfRVBG0tDnyX40dL4O9MdLe+NajtRl0r10AGVvTgA6qdJNbGsjQfciIOITI0QIhi+HNAUGZ/nHchjwqF4ZyDsNAdaZy68cpYKdJvzkva5BdggjAJuZz3PukjKM2h1NmMqHDYMdIF+NtaN3jwHhTXdIXTb1KamgH/USUBcs4IGQOQP47+WGmNrO5aJPPEZGRMymrF81fbe2ho1p2mVutzaqNQb621tV/78ZTC1A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=XSXaAohNmOGOa/ZfnTmjID3kAyzGLKuAA8asVGPT4F0=;
b=J/6hX/Ird5vbzrmqjMJmtdRBC9q8AD2WuSnK8RE4bpTyz4LGR/P5CKjWjK9osBTIxNUuBIid/A9QydXxXb0Teuvk9cnljhbw4U5oZTCl5UkfHCfszSeeRXz22oIDhx3lh8NAb2iN14UIpjWl1Vg1OKJBCcCOljDPBeYer6Qok4PEEOdiQ706Agi1WHfNwNGH/QDgyTJIweafbCChg7Kgnm9SFYZu2KtqJ5Ksw3d9f9kIoY2/eK9b+iE/skQGNPRBCOydJA1Bz4heKykLJiUU+/zr4Oo1Dr2NCGWbUU1csWwSpCN+olgd/OUmT/0TMvAQ1Wwa3BTtnLyrreOq3FckaA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=XSXaAohNmOGOa/ZfnTmjID3kAyzGLKuAA8asVGPT4F0=;
b=DPG0I0C/EpWSixu+jrFDuPyN2WPQE6VMvjEACkbU601KzfLV9DO1zQSxdYjmsxKriH+YYNvg1tuFLMhS7pWUMxZ9Ce7ngj5S+Km1uGOmijCTUwSP0vtkA9hWaZJz4zL91Wk1CtI0GCwO6HGgjHdvrXP2LPD1lHHxCJ5N+uh/PYo=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by ME2PR01MB2852.ausprd01.prod.outlook.com (2603:10c6:201:1a::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.11; Mon, 18 Jan
2021 04:14:00 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:14:00 +0000
Content-Type: multipart/alternative;
boundary="===============2598558810652011693=="
Subject: Re: Portainer 1.23.2 "Unable to initiate communications with
endpoint"
#QUE00000230
From: "Bala Natarajan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:13:53 -0000
Reply-To: "Bala Natarajan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW4PR03CA0373.namprd03.prod.outlook.com
(2603:10b6:303:114::18) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW4PR03CA0373.namprd03.prod.outlook.com (2603:10b6:303:114::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9 via Frontend Transport; Mon, 18 Jan 2021 04:14:00 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id ADD461E0318        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:13:53 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 11563e28-81c9-479e-0efb-08d8bb677bb5
X-MS-TrafficTypeDiagnostic: ME2PR01MB2852:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6790;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
FcqCmFwqdirz2P9cKsl9dfWNJg3bTukf00PTISwWzDYe+gssidyP0Eq47VGPXHGPWbWfHcEabtyncxzUbHl3ksLcHasozcIsjdebSjoYjgAKPJz9FWiTMNsatUUfsCa1x8Rstt3MJploDd8rvxnJddvuTfyHGlH4vTErl9is8zFEiQH2PkE+/DEpIZOVwtbQuXvKxg4IVANWvap9MD6v5D6mlCko+F72V3mCBzSqcb3SeWImrhM9nmcw25mMlBF04RNoWQ2Awc5i8QRt+pU5kMfSfeZT0Mtdv/3OWef7sKc8i9cQDToXXNaTQuYLjMopwvbqCzHpNz1UQum22LRy08AGpiyx3xrgH8JH3c9XR+Z/XXH5AxDsu8t0bcAnirEMp8JhjZEfqJzyoVduP+3Cpxkcjy0l2pj25YV0cIUoHq9AlIlbUXEKDx6bh8OYTnClHDrnTZt1TEN23yZD9KBtw8efegQnCeZ8FNE3grfSixNdGsNAGYbTJOCVhpzRA6YYbtOY9XA0W8j9g7a/EiRt9g==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(346002)(366004)(376002)(136003)(396003)(39830400003)(186003)(5660300002)(66556008)(26005)(103116003)(8936002)(9686003)(478600001)(66946007)(55236004)(66476007)(6916009)(86362001)(6266002)(2906002)(8676002)(3450700001)(83380400001)(36756003)(7126003)(316002)(33964004)(52116002);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?Gr+rf6kMOQKPxl2Y47YVTs6McCIEMrmEkpOtW4YSx2XYAK+pOZZnc9JApJCZ?=
=?us-ascii?Q?OtVSomJDk/sRcrGwZGrEGCTJa5N5LlBKgtb4QmcDWYe+5e/GgDqdULh8KUNY?=
=?us-ascii?Q?ffUhg6ZgRshU6ZBysScXS/znrjgoGEo/sDMtkPvh9iuc9mlTGjCo1+eURXTh?=
=?us-ascii?Q?jZidYgNxBEy2qw/KmuieC8fw3cHf6AV5S2b+c+WBeGrE1yvhN/fefBqsf5BL?=
=?us-ascii?Q?7fTSDWX5POenDjYSAlNfW1zpDDziN1yMXMHhtCN2aam5lS+gktxT2GOhyQYC?=
=?us-ascii?Q?GyXVnuX69vRKL59CpZ9nLXEekFbvk2q7KUzYjSakHmfDAj9nUhU8g+t8fIyd?=
=?us-ascii?Q?oDk+jiYfZ17GVjW1bdwKE/0XvS5cfWuR5DxLE33XgH6d+yPxj83Swz4tPjMI?=
=?us-ascii?Q?X5oNVNzPx8fJ0MdZ20OKF8FjTgbO0prPQt8y6mV2ZTHXrepMlIxYuOAFBO2u?=
=?us-ascii?Q?vYRwFYfBPV9DCET7kxxGX+ELTSH8veVkUapV4bRhtXB3MCOA8rl5GbTsjsy+?=
=?us-ascii?Q?KUlErSkCBa2B9BRTc03/utRZSGP0nkxcz3QGSbv+y+Cv/E4c/vtrXWU5TJnA?=
=?us-ascii?Q?40CBVEHl4wwzbSIXcOfoitS9nS4LZDCZnsQV5yIuXAJ1LFAw+yIdCOp+61cZ?=
=?us-ascii?Q?zlc4kaiXYd4oV9pHhM2w7ZNEiYp9Bm1pdTpR1YyoswX1EKxvm0yP3wnZ8a3x?=
=?us-ascii?Q?jCiIkGRScCdBiGmQ7WWL6iJjQg+F/efpPvvYNcBCNB2jrQ1Saj465PS4DOsX?=
=?us-ascii?Q?z4x5/mH9SMzptvsHIN92NYT2DzMy56pRJ8u3KED4FZONRuHxWFFxoCqjp4bh?=
=?us-ascii?Q?UcMDmDG2ACgoq2J7tvzhdiGn8Y2ZUwqTmNGlEqQEaAPhwSHkQvKOvjfzdUSl?=
=?us-ascii?Q?jmqy97gF0Ik3N3PAiiy3SplgD5CADLIVk/MCwR3jnDgLlvfUcanOWrZU0Lvt?=
=?us-ascii?Q?b/OcTUGPHD6/9pMd+61QIMQy1q2WcFkwGBIkXUn2DFMa1oZ4Cjg6EA8C1JV/?=
=?us-ascii?Q?RbZY?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: 11563e28-81c9-479e-0efb-08d8bb677bb5
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:14:00.5313
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: fKbemGROeViPnwPWCRldQe+urdHBBHe3+vmiBDIjwfVPV3PhBx1hjQc9/6HI/5bfesDz2OSPTQ82Xz2s0vYkbA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ME2PR01MB2852
New reply for the ticket #QUE00000230
Hi
please let us if rther assistance required on this ticket.
Bala Natarajan
Reply to this email to submit an update.

This is being Closed because of inactivity.

Closed due to inactivity


Implement logout functionality

Would it be worth adding logout functionality ala https://github.com/aysiu/offset ?

Seams reasonable.
Detecting the state is...something

There has to be a more macOS native way to do this. Hrmmm.

Looking at Munki, it uses:
	<key>LimitLoadToSessionType</key>
	<array>
		<string>LoginWindow</string>
	</array>

Which is the obvious way to do it at the login window. I'd argue a reboot is also a logout, so we don't need to care about that (bur document it clearly)
System startup on the other hand is not a logout, so we'd need some method to figure that out.
This lead me to finding this:
https://stackoverflow.com/a/63372640
So perhaps you could have a LaunchD that does nothing but run code to detect these events, then touch a file on disk that the LoginWindow LaunchAgent looks for (also similar to munki: https://github.com/munki/munki/blob/main/launchd/LaunchAgents/com.googlecode.munki.managedsoftwareupdate-loginwindow.plist#L9)
This of course circles right back around to what is the use case for this? Is it worth the time and effort? (I could see computer labs perhaps wanting something like this).

it was worth it enough for someone to write offset. The computer lab scenario of "run scripts that perform cleanup tasks" is one I can see people using. For that I don't think it's required to detect a logout event per-se, you just have a launchd that loads in the login window context.
Properly documented the workflow would be left to the admin, e,g,
loginwindow tasks always run at the login window. if you want an even to take place after a logout then use something like this:

create your login window script to require presence of a trigger file
create a login-every script to create the trigger file
when the user logs out and you are back at the login window, your task should trigger, and then clean up after itself
optionally add a boot script that performs initial cleanup before the loginwindow is presented (e.g. your script trigger is still present)

I don't think it needs to be complicated. At a reboot event, the login window isn't displayed so these events won't trigger in that scenario.
In short I think we don't implement "logout" functionality. We implement "login-window" and the logic for a "logout" scenario can be an exercise for the admin - maybe document some basic scenario as an example but not build that into outset.
WDYT?

this is also a core justification for Ouset IMO - creation of launchd logic for admin tasks that can be managed under a single banner and save admins from creating their own seperate ones and individually managing the login items settings.

I like this method better. Less complicated and allows for as much flexibility as the admin might desire.

it was worth it enough for someone to write offset. The computer lab scenario of "run scripts that perform cleanup tasks" is one I can see people using. For that I don't think it's required to detect a logout event per-se, you just have a launchd that loads in the login window context.
Properly documented the workflow would be left to the admin, e,g,
loginwindow tasks always run at the login window. if you want an even to take place after a logout then use something like this:

create your login window script to require presence of a trigger file
create a login-every script to create the trigger file
when the user logs out and you are back at the login window, your task should trigger, and then clean up after itself
optionally add a boot script that performs initial cleanup before the loginwindow is presented (e.g. your script trigger is still present)

I don't think it needs to be complicated. At a reboot event, the login window isn't displayed so these events won't trigger in that scenario.
In short I think we don't implement "logout" functionality. We implement "login-window" and the logic for a "logout" scenario can be an exercise for the admin - maybe document some basic scenario as an example but not build that into outset.
WDYT?

Closing this one - while there's no direct "logout" function as such, this can be achieved with a login-window script and some flags set on user login to trigger the login window script to run at user logout (either as a logout, or reboot event)


Explain why certain image features are missing

Describe what this PR does
I spent a good long while tracking down the reason for some image features being unsupported, so I have added the relevant link to the documentation.

I think that's it.

I think that's it.


doc: spiderfoot and domain scan pictures

Checks

[ ] Your YAML file has required fields as listed in Specs
[ ] All checks have passed yaml-lint passed
[ ] You agree to contribute your work under MIT license

We work together. Arthur Heriard Dubreuil E11215007


[Improvement-#9680][task-plugin] add hive sql log listener

[Improvement-#9680][task-plugin]  add hive sql log listener, print MapReduce progress log and obtain application_id allows developers to better track tasks

Codecov Report

Merging #9701 (a4a306d) into dev (29a0ea3) will decrease coverage by 0.01%.
The diff coverage is 17.64%.

:exclamation: Current head a4a306d differs from pull request most recent head 8875740. Consider uploading reports for the commit 8875740 to get more accurate results

@@             Coverage Diff              @@
##                dev    #9701      +/-   ##
============================================
- Coverage     40.02%   40.00%   -0.02%
+ Complexity     4475     4471       -4
============================================
  Files           835      835
  Lines         33550    33550
  Branches       3710     3710
============================================
- Hits          13427    13421       -6
- Misses        18875    18881       +6
  Partials       1248     1248

Impacted Files
Coverage Δ

...cheduler/api/service/impl/ExecutorServiceImpl.java
40.62% <0.00%> (ø)

...i/service/impl/ProcessTaskRelationServiceImpl.java
21.03% <0.00%> (ø)

...er/api/service/impl/TaskDefinitionServiceImpl.java
24.01% <0.00%> (ø)

...heduler/api/service/impl/SchedulerServiceImpl.java
8.36% <20.00%> (ø)

...api/service/impl/ProcessDefinitionServiceImpl.java
31.07% <50.00%> (ø)

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
37.77% <0.00%> (-2.23%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.11% <0.00%> (-1.41%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:

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 29a0ea3...8875740. Read the comment docs.


Hello, sure https://cmu-perceptual-computing-lab.github.io/foot_keypoint_dataset/

tysm, your work really helps me ~~


fix: use strict typing for sqlite in payment request example app

sqlite will store floating point numbers sent as string as actual real numbers with exponential notation.
Using strict should explicitely store them as string.
See also: https://www.sqlite.org/stricttables.html
sqlitebrowser currently errors when trying to view STRICT tables, see https://github.com/sqlitebrowser/sqlitebrowser/issues/3259#issuecomment-1485322524.

Still errors with

[SQLITE_CONSTRAINT_DATATYPE] An insert or update attempted to store a value inconsistent with the column's declared type in a table defined as STRICT (cannot store BLOB value in TEXT column customer_order_line_item.id)

sqlitebrowser currently errors when trying to view STRICT tables, see https://github.com/sqlitebrowser/sqlitebrowser/issues/3259#issuecomment-1485322524.

Try our continuous "AppImage" build instead:
    https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/continuous

sqlitebrowser currently errors when trying to view STRICT tables, see sqlitebrowser/sqlitebrowser#3259 (comment).

Try our continuous "AppImage" build instead, as that automatically uses the newest version of SQLite each time it's built:
https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/continuous

Awesome. Works great. Thank you :pray:


Run

How do I run this? I get no output from ember build or ember test.. I have a .stylelintrc and added postcss-less to processors:
{
  "processors": ["postcss-less"],
  "rules": {
    "color-no-invalid-hex": true,
    "declaration-colon-space-after": "always",
    "indentation": [2, {
      "except": ["value"]
    }],
    "max-empty-lines": 2,
    "rule-nested-empty-line-before": [ "always", {
      "except": ["first-nested"],
      "ignore": ["after-comment"]
    }]
  }
}

hey sorry there was a bug, it wasn't printing to console. i added a test so that this doesn't happen again. grab the latest release 0.2.2

Will give it a go again, thanks :)

@knownasilya is it working ?

No, it has the same result, no output. I'll try to create a fresh project and test on that.

Hi @knownasilya  sorry for late reply i have been offline on holiday. have you had any success. it might be because of postcss-less processor will test it.

Hi @knownasilya please upgrade to 0.6.0 and change your ember-cli-build.js file to reflect the syntax of your choosing
here is a sample
var EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    stylelint: {
      linterConfig:{
        syntax: 'less'
      }
    }
  });

Works 👍


Read default config file from ~/.holmes/config.yaml not current directory

This makes holmes behave like other command line tools (e.g. kubectl) and more like users expect. This came up in a recent user feedback call.

@pavangudiwada FYI


support english anime sites

Would be great if youtube-dl can support some english sub anime. Some examples:
http://cc-anime.com/
http://www.animeram.eu/
etc. Thanks!

They probably don't have the right for distributing that content, therefore we can't add support for the site. If you think they can, please comment here and we will reopen the issue.


TemplateMatcher relies on PathString type as input which limits its functionality to url paths

I'm using the TemplateMatcher to build tenant/subdomain functionality in my 1.1 core project. Due to the TemplateMatcher function TryMatch relying on a PathString instead of a regular String as input, I can only use relative paths beginning with a "/". My actual input is "test.example.com". Because it does not begin with a slash, I get an exception when TemplateMatcher tries to instantiate the input as a PathString.
Example:
ParsedTemplate = TemplateParser.Parse("{tenant}.example.com");
_matcher = new TemplateMatcher(ParsedTemplate, Defaults);
_matcher.TryMatch("test.example.com", values);
previous line throws an exception because the first parameter needs to start with a slash.
I feel that requiring a PathString here is an oversight that artificially limits what can be done with Template Routes. There should be support for doing non-url templates.

I believe that TemplateMatcher (and, in fact, all of Routing's built-in parsing stuff) is specifically about working with the "path" portion of the URL. It is not designed to work with any other part of the URL (scheme, port, host, query string, etc.). For this reason it needs to use many URL-path-specific APIs, because rules for various parts of the URL are quite different with regard to what is valid, how to encode/decode, etc.


HTML escaping non-alphanumerical characters is unnecessary

Currently all non-alphanumerical characters are escaped to HTML entities when exporting HTML, which makes the result unreadable for languages that rely on characters with diacritics, for example, and it doesn't make sense for a general use case. There can be special use cases where the HTML needs to be ASCII, but that escaping can be done afterwards, while reversing it is more difficult.

Workaround: .replace(/&#(\d+);/g, (_, code) => String.fromCharCode(+code)).
I'd use patch-package to just remove the escaping, but unfortunately it's not possible when using stackedit.js.


[FEATURE] README to be created for the website project

⭐ Suggestion
We need to create a proper README.md file to explain all the necessary steps and descriptions of this project.
Such as About project, Tech Stack section, How to set up the local-dev environment, and other helpful links/resources.
💻 Use Cases
This will help the contributors to get started with ease and understand the project workflow in a better way.
❌ Related Problems
Nothing as such, It's a completely new feature

Can I work on this?

Yes @danger-ahead You can get started with this issue. Make sure you're creating a new unique branch from the development branch and raise a PR to development only. Go ahead with this issue and feel free to ask for queries. 🚀

okay. please consider assigning me.
also please provide me with the necessary details to be added


Add nologo support to NUnit3

Can commandLineBuilder.AppendSwitch("/nologo"); be added to MSBuild.ExtensionPack.CodeQuality.NUnit3, it appears in MSBuild.ExtensionPack.CodeQuality.NUnit

thats should do it...


Bump Dependencies #11523798444

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/11523798444

 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.


Updated debian, UI can be started again

@inspectit-docker/owners I updated the debian version and now the ui starts. It does not look too good, I am not sure if some extra packages must be downloaded, but at least it works.. I was not able to completely remove the welcome screen showing, I will investigate more to see how to make this work later.
I also removed xulrunner-1.9.1 lib as it was not available anymore.

Try to click on the Welcome in the middle of the screen. Does it crash?
I would prefer to skip the welcome screen completely.

When I click in the middle I get the error window only and you can close it. I would also like to skip the welcome screen I just need to figure out how. But at least for now let's have this working version.

@andreasreinhardt Updated with fix not to show welcome screen at all.


elixir_1_15: 1.15.6 -> 1.15.7

Description of changes
https://github.com/elixir-lang/elixir/releases/tag/v1.15.7

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Thank you !


New version: JetBrains.IntelliJIDEA.Ultimate.EAP version 223.7401.7

Result: Installation Failed

Manifest
Add/Remove Programs

Name
IntelliJ IDEA Ultimate Edition (EAP)
IntelliJ IDEA Community Edition 223.7401.7

Version
223.7401.7
223.7401.7

Publisher
JetBrains s.r.o.
JetBrains s.r.o.

ProductCode

IntelliJ IDEA Community Edition 223.7401.7

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 3637
Microsoft Reviewers: Open in CodeFlow

@Trenly @vedantmgoyal2009 - Shouldn't the PackageName be IntelliJ IDEA instead of IntelliJ IDEA Ultimate Edition (EAP)? I have seen such naming in other JetBrains manifests where the PackageName doesn't quite match the Control Panel so wanted to learn if this is intentional.

@Trenly @vedantmgoyal2009 - Shouldn't the PackageName be IntelliJ IDEA instead of IntelliJ IDEA Ultimate Edition (EAP)? I have seen such naming in other JetBrains manifests as well where the PackageName doesn't quite match the Control Panel so wanted to learn if this is intentional.

PackageName should keep the edition and EAP, IMO. We can use the AppsAndFeaturesEntries if we need to ensure a match, but when you're searching through our catalog there wouldn't be a way to tell community from ultimate or EAP from stable otherwise.


"Raised by Belief" background provides only 1 Ability boost instead of 2

The Raised by Belief background is supposed to provide a total of two Ability boosts. One boost must be to an ability specified in the Divine Ability entry for your deity, and one is a free ability boost. However, after creating a new character, selecting my deity and selecting the "Raised by Belief" background, I am only provided with a total of 1 (free) Ability boost for my background choice. I do not have any way to select my second boost according to my deity's Divine Ability.
Expected behavior: At the very least I would expect to be provided two free boosts, one to assign manually in accordance with the Divine Ability entry for my deity, and one for a free ability boost. Ideally of course, the Divine Ability boost would be assigned and locked like other keyed boosts, and the remaining Ability boost would be left for free assignment.

"Harrow-Led" is also missing a boost.