pwndbg: add glibc debug symbols to debug dirs

Description of changes
Currently, pwndbg doesn't have any sensible debug info paths set up:
pwndbg> show debug-file-directory
The directory where separate debug symbols are searched for is "/nix/store/5xm7rggy43c6gm7rj6nara2l6lbkyc5j-gdb-11.2/lib/debug:/usr/lib/debug".

In fact, both of those paths don't exist.
If a program is built on NixOS and someone wants to debug it with pwndbg, the heap commands like heap or vis_heap_chunks won't work:
pwndbg> heap
/home/git/.cache/pwndbg/typeinfo/x86-64_struct-malloc_state.cc:3:21: error: aggregate ‘malloc_state foo’ has incomplete type and cannot be defined
    3 | struct malloc_state foo;
      |                     ^~~
Exception occurred: heap: No struct type named malloc_state. (<class 'gdb.error'>)
For more info invoke `set exception-verbose on` and rerun the command
or debug it by yourself with `set exception-debugger on`

This PR fixes this by prepending the current glibc debug symbols to the NIX_DEBUG_INFO_DIRS. This doesn't work if the binary uses a different glibc buid (this has to be still configured manually) but at least the basic functionality is fixed.
Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 171856 run on x86_64-linux 1

1 package built:

pwndbg

Ah, it's not evaled properly because debug do not seem to exist.


Fix "Cannot read property 'startContainer' of undefined" caused by code assuming that saveSelection always returns a range or null and never undefined. Update saveSelection to never return undefined.

@mervick thanks for your work on this project -- any plans on a release that includes this fix?

Sorry, I have no time for review all of latest commits and test it. If you need this fix you always can use master branch by npm, composer or bower


Add ID search capability to sshkeypairs

Description
This PR adds the search by ID capability to SSH Key pairs to bring it at par with accounts
Also needed as a UI fix
In a 4.16 env, try to view the second / third sshkey. It tries to fetch it by id which does not work and leads to the first keypair always displayed
Types of changes

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

Feature/Enhancement Scale

[ ] Major
[x] Minor

Screenshots (if appropriate):
(localhost) 🐱 > list sshkeypairs id=5210f701-b13e-4ff7-8aab-eb24ee81526a filter=id,name
{
  "count": 1,
  "sshkeypair": [
    {
      "id": "5210f701-b13e-4ff7-8aab-eb24ee81526a",
      "name": "b"
    }
  ]
}
(localhost) 🐱 > list sshkeypairs filter=id,name
{
  "count": 3,
  "sshkeypair": [
    {
      "id": "d1348275-e203-46bf-a985-45dc2a1b331f",
      "name": "c"
    },
    {
      "id": "5210f701-b13e-4ff7-8aab-eb24ee81526a",
      "name": "b"
    },
    {
      "id": "b4430a09-5b9d-49e4-be55-156e1b7ebd72",
      "name": "a"
    }
  ]
}

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

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

@weizhouapache a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_multiplication_x: el7 :heavy_multiplication_x: el8 :heavy_multiplication_x: debian :heavy_multiplication_x: suse15. SL-JID 2523

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

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

@blueorangutan test

@davidjumani a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3234)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 32976 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5963-t3234-kvm-centos7.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File


Token Limits

First, thanks for your efforts on this. CodeGPT is a useful tool for my workflow in CLion.
I realize the current limitation of the GPT-3 model is currently 4097 tokens. However, the current implementation is a  hard stop once the current conversation reaches this limit, which IMO leads to poor user experience. From some quick reading it appears in many instances, as opposed to a hard stop, a strategy of incorporating (n) number of prior conversation elements into subsequent calls is a better approach. This would allow the conversation to continue seamlessly, without the hard stop. Certainly historical conversation elements would naturally age out and not become part of the current model(prompt) context, but it would allow for a reasonable volume of recency without forcing a hard stop for the user. I believe you could also calculate the proximity to the token limitation to determine how many historical conversation elements to discard from subsequent calls.
E.G.
Human: Optimize this code: {code}
AI: Output
Human: Ok, refactor code to do XyZ and please explain QrT
AI: Output
As prompt accumulates, removing historical elements from the prompt array in whole is advisable. You can calculate the number of tokens the entire prompt will use relative to the total limit and the determine how many prompt elements are required to be removed from the array in order to comply with the model token limit.
Incorporating this feature would improve the usability considerably of CodeGPT. Additionally, this is already effectively the result, as conversations are useless once they accumulate, and the user is required to manually create a new conversation. The conversation itself from an offline perspective can continue in perpetuity for the historical benefit of the user, but the interaction with ChatGPT will only include the allowable history.
Thanks again for your time, in review.

Hi @chriskyndrid
I like the idea of having seamless conversation despite the token limitation. If I understood you correctly, you're suggesting discarding the earliest historical conversations (or truncating the previous messages) based on the new prompt token count?
If that's the case, then I see two issues:

Technical difficulties - since the response is being streamed, we're unable to retrieve the usage info from the response. Another option would be to calculate the total ourselves by using an existing library, but unfortunately, I couldn't find any written in Java. A workaround would be to use the tiktoken library, but that requires mixing Java with python...
High quota - every request we make will cost you around 4k tokens. For example, even a simple "Hi" prompt will cost 0.008 USD (gpt-3.5). However, I guess we can reduce the token limit to e.g. 1k and work around that.

Thank you for the feature request!

@carlrobertoh thanks for getting back to me. Here are my thoughts:

Would jtokkit work?  I belive GPT 3.5 uses cl100k_base. Otherwise approximation could be a strategy, though that would get complicated based on language.

From a cost perspective, I'm personally not very concerned about that. A compromise would be create a check box in the setup that allows for perpetual conversations with a caveat on token utilization. You could default it to off(same functionality as today) and allow the user to decide. Generally speak, for simple tasks like optimizations, etc, the impact will likely be minimal if non existent with this change. If the user decides to continue an ongoing conversation, you could argue even in the current situation(how you have it currently), they are accepting the costs as the historical prompt elements are already stacking and then hard terminate, often in the middle of a dialog. Going a step further, you could, although I don't think it is particularly necessary, allow the user to specify the maximum number of tokens they're willing to afford. I would not however, arbitrarily reduce the number of tokens allowed to save cost(like your suggestion to limit at 1k), as you loose the benefit of context. If it's a concern, a combination of allowing the user to toggle the feature and specify maximum token limits would be adequate.

As far as strategy for removing historical conversation elements. I haven't reviewed your code....but assuming the prior conversation elements are stored in an array(or could be), I would calculate the number of tokens that need to be removed given the new incoming prompt and then determine the number of prompt elements to remove starting with the oldest prompt. This could require more thought, but I think truncated elements from the oldest prompt to fit the incoming prompt could cause contextual issues...but maybe not.

jtokkit is a great find, I believe that could do the trick. Approximation can't be used since most of the people are Chinese.

I think adding a check box to a settings panel is bit hard to find(or not), I would rather trigger a warning alert once the token limit exceeds and let the users decide whether they want to continue the ongoing conversation or not. I agree with your suggestion as to custom limits. This could be part of a generic request params overriding logic and I would leave that out for now.

Truncating the messages is probably a bad idea yes, most likely we need to discard the entire message/messages to fit the prompt. The logic probably needs to be built inside the CompletionRequestProvider that is responsible of creating the API request payload or maybe even in the client library itself...

FYI: The jtokkit seems to be working really good and I'm thinking of adding the token counter to the toolbar:

Not yet sure if I'm going to include it in the next release or not.

@carlrobertoh,
That looks good. You might consider doing something different than raising an alert when the user hits the token limit and begins the perpetual "high" token transmission(maximal cost), something like changing the Tokens: XX/XXX to red or something.
That's a bit shameless on my part, but it would be a PITA to have a popup raised whenever I hit the point where each transmission represents close to token limit, as for me, it will regularly occur.
Otherwise, thanks for your efforts on this.

@chriskyndrid
Having a colorful indicator sounds like a really good idea!
Regarding to the popup, I think this can be easily solved by adding the "Don't ask me again" option inside the dialog or smth.
Also, I'm not sure when I am going to start with the implementation since there are few other requested features in my current bucketlist.

@chriskyndrid Support for seamless conversations has been added in version 1.10.2. However, it is currently only available for the main models gpt-3.5 and gpt-4. I will add the support for other models in the near future.

FYI: The jtokkit seems to be working really good and I'm thinking of adding the token counter to the toolbar:

Not yet sure if I'm going to include it in the next release or not.

Please include it. It looks super useful.


comparison of different types with ==, compiler says it will always evaluate to false

TypeScript Version:  3.8.3
Search Terms:

comparison
comparisons
==

Code
let a = "1";
let b = 1;

console.log(a == b);

Expected behavior:
Should complain about incompatible types, maybe with a warning that the == operator will lead to an implicit type conversion.
Actual behavior:
It does complain, but the error message is wrong.
error TS2367: This condition will always return 'false' since the types 'string' and 'number' have no overlap.
This is wrong. If the code is executed, the comparison will evaluate to true.
Related Issues:
#30655. In that issue the expected behaviour was that loose comparisons of strings and numbers are considered valid.  The issue was closed with a comment that an error message is intended here. I do agree with an error being the intended output. It's simply that the error message is wrong.
#29155 has exactly this problem as title but seems unrelated.
Playground Link: Provided

This should be correct. If you do not use any compiled code will behave right, if it compiles :-). You should not be able to compare different types. So, implicit conversions should not be valid typescript.

Yes, implicit conversions should not be valid typescript. I do agree.
But the error message is wrong. The condition will not always return false, just look at the playground example (where it returns true).

Closely related to https://github.com/microsoft/TypeScript/issues/37251

Exact duplicate of #26592


feature/global options

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Comment Tag'd Styles Fail

Sorry, I didn't know a better title.
I using tiny_mce for a project which automatically puts the html comment tags around any inline styles found in the body area.
This then causes emogrify to give an error :" Uncaught exception 'InvalidArgumentException' with message 'DOMXPath::query(): Invalid expression in selector >>"
Working HTML:
`

	Forward Unsubscribe

`
After TinyMCE Failing HTML:
`

	Forward Unsubscribe

`
For now, I'm just kludging the tiny_mce output, but it would be nice if I didn't have to :)
EDIT: I think the code is getting hidden because of the tags, sample file uploaded.
demo.txt

Inside CSS, you need to use /* */ as comment marks. HTML comment marks will make the CSS invalid, causing parsing errors.
Did you comment out the code, or did TinyMCE do that?

Oh, I missed the part where you mentioned that it's TinyMCE that did that. Could you please report there that it needs to use CSS comment markers instead of HTML comment markers? Thanks!

Unfortunately the project is using an old version of tiny_mce, so it may be fixed in the latest version, just I can't switch to it :(
Ok - so I guess I'll leave my kludging in then! Thanks!


Filter import

It would be nice to have a hook in point to filter which users should be imported. This would be especially useful for the rake import task. In our case, we have a deleted column on our user table. The way it works now, deleted users get imported to Intercom, and from there might get emails they should not get.

Found this in the config. Should be documented in readme, but it is a solution.
config.user.exclude_if = Proc.new { |user| user.deleted? }


azure.mgmt.containerregistry create Token with no Passwords Generated

Package Name:  azure.mgmt.containerregistry
Package Version: 2020-11-01-preview
Operating System: MacOs
Python Version: 3.6

Describe the bug
I followed Code Samples in here
To create Token assigned to specific ScopeMap in Azure Container Registry. Using begin_create method, a token was created successfully and assigned to the correct scopemap, however, password1 and password2 do not get generated and output as expected. Unlike, when running az cli command to create token, "az acr token create --name tokenName --registry registryName --scope-map scopemapName" 2 passwords get generated and output.
To Reproduce
Steps to reproduce the behavior:
Behavior can be reproduced in any of the following 3 scenarios:
1.

from azure.identity import DefaultAzureCredential
from azure.mgmt.containerregistry import ContainerRegistryManagementClient
from azure.mgmt.resource import ResourceManagementClient

SUBSCRIPTION_ID = os.environ.get("SUBSCRIPTION_ID", None)
GROUP_NAME = "testgroupx"
TOKEN = "tokenxxyyzz"
REGISTRIES = "registriesxxyyzz"
SCOPE_MAP = "scopemapxxyyzz"

resource_client = ResourceManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID
)
containerregistry_client = ContainerRegistryManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID,
        api_version="2020-11-01-preview"
)
scope_map = containerregistry_client.scope_maps.get(
        GROUP_NAME,
        REGISTRIES,
        SCOPE_MAP
)

# Get already existing registry and already existing scopemap and use them to create token
token = containerregistry_client.tokens.begin_create(
        GROUP_NAME,
        REGISTRIES,
        TOKEN,
        {
          "scope_map_id": scope_map.id,
          "status": "enabled",
        }
).result()
print("Create token:\n{}".format(token))

2-

from azure.identity import DefaultAzureCredential
from azure.mgmt.containerregistry import ContainerRegistryManagementClient
from azure.mgmt.resource import ResourceManagementClient
from azure.mgmt.containerregistry.v2020_11_01_preview.models import TokenCredentialsProperties
from azure.mgmt.containerregistry.v2020_11_01_preview.models import TokenPassword

SUBSCRIPTION_ID = os.environ.get("SUBSCRIPTION_ID", None)
GROUP_NAME = "testgroupx"
TOKEN = "tokenxxyyzz"
REGISTRIES = "registriesxxyyzz"
SCOPE_MAP = "scopemapxxyyzz"

resource_client = ResourceManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID
)
containerregistry_client = ContainerRegistryManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID,
        api_version="2020-11-01-preview"
)
scope_map = containerregistry_client.scope_maps.get(
        GROUP_NAME,
        REGISTRIES,
        SCOPE_MAP
)

pass1= TokenPassword(
name=”password1”
)
pass2= TokenPassword(
name=”password2”
)
passes = TokenCredentialsProperties(
passwords= [pass1, pass2]
)

# Get already existing registry and already existing scopemap and use them to create token
token = containerregistry_client.tokens.begin_create(
        GROUP_NAME,
        REGISTRIES,
        TOKEN,
        {
          "scope_map_id": scope_map.id,
          "status": "enabled",
          "credentials":passes
        }
).result()
print("Create token:\n{}".format(token))

3-

from azure.identity import DefaultAzureCredential
from azure.mgmt.containerregistry import ContainerRegistryManagementClient
from azure.mgmt.resource import ResourceManagementClient
from azure.mgmt.containerregistry.v2020_11_01_preview.models import GenerateCredentialsParameters

SUBSCRIPTION_ID = os.environ.get("SUBSCRIPTION_ID", None)
GROUP_NAME = "testgroupx"
TOKEN = "tokenxxyyzz"
REGISTRIES = "registriesxxyyzz"
SCOPE_MAP = "scopemapxxyyzz"

resource_client = ResourceManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID
)
containerregistry_client = ContainerRegistryManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID,
        api_version="2020-11-01-preview"
)
scope_map = containerregistry_client.scope_maps.get(
        GROUP_NAME,
        REGISTRIES,
        SCOPE_MAP
)

# Get already existing registry and already existing scopemap and use them to create token
token = containerregistry_client.tokens.begin_create(
        GROUP_NAME,
        REGISTRIES,
        TOKEN,
        {
          "scope_map_id": scope_map.id,
          "status": "enabled",
        }
).result()
print("Create token:\n{}".format(token))

passgn = GenerateCredentialsParameters()
passgn.name='password1'
passgn.token_id=token.id
passgn2 = GenerateCredentialsParameters()
passgn2.name='password2'
passgn2.token_id=token.id
gen_pass = registry_client.registries.begin_generate_credentials(
                     GROUP_NAME,
                     REGISTRIES,
                     passgn
)
gen_pass2 = registry_client.registries.begin_generate_credentials(
                     GROUP_NAME,
                     REGISTRIES,
                     passgn2
)

Expected behavior
1- In scenario 1, I expected the token to be created with proper name given and assigned to the proper scopemap given with 2 passwords password1 and password2 generated and output to me
2- In scenario 2, I expected the token to be created with proper name given and assigned to the proper scopemap given with 2 passwords password1 and password2 generated and output to me
3- In scenario 3, I expected the token to be created with proper name given and assigned to the proper scopemap given with 2 passwords password1 and password2 generated and output to me
Screenshots
1- In scenario 1, token created successfully and assigned to the correct scopemap but none of the passwords were generated
2- In scenario 2, exception below arose

3- In scenario 3, I tried to use generateCredentials as the exception above instructed, I found it in begin_generate_credentials methods here but the exception below arose

Additional context
I need to be able to create Token for Specific ScopeMap in ACR with its passwords automatically generated, as same as, the result of this az cli command "az acr token create --name tokenName --registry registryName --scope-map scopemapName"

@Ayatallah Thanks for the issue, we’ll investigate asap

Hi @Ayatallah Thanks for the feedback.
In Azure-cli, run the az acr token create --name tokenName --registry registryName --scope-map scopemapName command to automatically generate a password because it has a built-in method to generate a key. The direct use of SDK will not automatically generate passwords.
If you need a password, you need to execute begin_generate_credentials method in azure.mgmt.containerregistry.RegistriesOperations.
Here is the document : https://docs.microsoft.com/en-us/python/api/azure-mgmt-containerregistry/azure.mgmt.containerregistry.v2021_06_01_preview.operations.registriesoperations?view=azure-python#begin-generate-credentials-resource-group-name--registry-name--generate-credentials-parameters----kwargs-
Hope this unblocks you.
BTW, If necessary, I can provide a detailed example later.

Hi @Ayatallah Thanks for the feedback.

RE: scenario 1 & 2

In Azure-cli, run the az acr token create --name tokenName --registry registryName --scope-map scopemapName command to automatically generate a password because it has a built-in method to generate a key. The direct use of SDK will not automatically generate passwords.
If you need a password, you need to execute begin_generate_credentials method in azure.mgmt.containerregistry.RegistriesOperations.
Here is the document : https://docs.microsoft.com/en-us/python/api/azure-mgmt-containerregistry/azure.mgmt.containerregistry.v2021_06_01_preview.operations.registriesoperations?view=azure-python#begin-generate-credentials-resource-group-name--registry-name--generate-credentials-parameters----kwargs-

RE: scenario 3

The python SDK has a password protection mechanism and will not directly display the password.
A compromised solution is to directly access the password value, such as you can use print(gen_pass.passwords[0].value)
Hope this unblocks you.
BTW, If you want more detailed examples, I can provide them later.

Hi @Ayatallah Thanks for the feedback.

RE: scenario 1 & 2

In Azure-cli, run the az acr token create --name tokenName --registry registryName --scope-map scopemapName command to automatically generate a password because it has a built-in method to generate a key. The direct use of SDK will not automatically generate passwords.
If you need a password, you need to execute begin_generate_credentials method in azure.mgmt.containerregistry.RegistriesOperations.
Here is the document : https://docs.microsoft.com/en-us/python/api/azure-mgmt-containerregistry/azure.mgmt.containerregistry.v2021_06_01_preview.operations.registriesoperations?view=azure-python#begin-generate-credentials-resource-group-name--registry-name--generate-credentials-parameters----kwargs-

RE: scenario 3

The python SDK has a password protection mechanism and will not directly display the password.
A compromised solution is to directly access the password value, such as you can use print(gen_pass.passwords[0].value)
Hope this unblocks you.
BTW, If you want more detailed examples, I can provide them later.

@BigCat20196 Thanks for your reply! Actually, I have tried begin_generate_credentials method but It was not recognized as callable method in azure.mgmt.containerregistry.RegistriesOperations please find below the exception and the code and let me know if there's anything needs to be fixed
Exception:

Code:

from azure.identity import DefaultAzureCredential
from azure.mgmt.containerregistry import ContainerRegistryManagementClient
from azure.mgmt.resource import ResourceManagementClient
from azure.mgmt.containerregistry.v2020_11_01_preview.models import GenerateCredentialsParameters

SUBSCRIPTION_ID = os.environ.get("SUBSCRIPTION_ID", None)
GROUP_NAME = "testgroupx"
TOKEN = "tokenxxyyzz"
REGISTRIES = "registriesxxyyzz"
SCOPE_MAP = "scopemapxxyyzz"

resource_client = ResourceManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID
)
containerregistry_client = ContainerRegistryManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID,
        api_version="2020-11-01-preview"
)
scope_map = containerregistry_client.scope_maps.get(
        GROUP_NAME,
        REGISTRIES,
        SCOPE_MAP
)

# Get already existing registry and already existing scopemap and use them to create token
token = containerregistry_client.tokens.begin_create(
        GROUP_NAME,
        REGISTRIES,
        TOKEN,
        {
          "scope_map_id": scope_map.id,
          "status": "enabled",
        }
).result()
print("Create token:\n{}".format(token))

passgn = GenerateCredentialsParameters()
passgn.name='password1'
passgn.token_id=token.id
passgn2 = GenerateCredentialsParameters()
passgn2.name='password2'
passgn2.token_id=token.id
gen_pass = registry_client.registries.begin_generate_credentials(
                     GROUP_NAME,
                     REGISTRIES,
                     passgn
)
gen_pass2 = registry_client.registries.begin_generate_credentials(
                     GROUP_NAME,
                     REGISTRIES,
                     passgn2
)

@Ayatallah
What is client registry_client in the last two lines of your code?
You can try changing them to containerregistry_client And run it again.

@Ayatallah
What is client registry_client in the last two lines of your code?
You can try changing them to containerregistry_client And run it again.

@BigCat20196 they're the same thing, excuse the confusion in the variable names, still the same exception arise!

Okay, I changed the version below :
containerregistry_client = ContainerRegistryManagementClient(
        credential=DefaultAzureCredential(),
        subscription_id=SUBSCRIPTION_ID,
        api_version="2020-11-01-preview"
)

from 2020-11-01-preview to 2021-06-01-preview and it works fine now!


Disable TensorFlow test

This test seems to fail more often than it succeeds in CI. I propose we disable it until we can diagnose and fix the flakiness.

I'm fine with this as a temporary measure. My understanding right now is that this test was fairly reliable for a while and started failing recently for legitimate reasons. @sjezewski is working on getting it passing again and making it more resilient to future failures. The issue seemed to be the tensorflow image changing underneath us, I believe the plan is to use a static image reference so that won't happen again. @sjezewski is that all accurate?

Yup that all sounds right.
Matt asked me if he could disable it temporarily. Since I didn't have a working fix yet, that's ok with me.
I was getting blocked by dockerhub DDoS DNS issues today ... all I needed was that silly version number ... but I had to wait/hit DH a bunch to get it. I have a build pending on CI now w the fix. (Works locally). So if its not urgent, its probably easier to wait for that to land. Sorry for the racy-development @msteffen

No worries. I have other code I can work on. I'll submit this when your (@sjezewski) PR is in


"az eventgrid event-subscription create" does not support Service Bus Topic endpoint type but Azure Portal does

Describe the bug
In the azure portal, you can create an Azure Event Grid Subscription with a Service Bus Topic endpoint. However, the "az eventgrid event-subscription create" command does not support Service Bus Topic for the "--endpoint-type" argument.
To Reproduce
Run "az eventgrid event-subscription create --help" and see that the options listed for "--endpoint-type" do not include Service Bus Topic.
Expected behavior
That the options available in Azure portal are implemented in the Azure CLI.
Environment summary
Azure CLI version 2.6.0 on Linux

routing to appropriate team

@jfggdl do we have any update on this?

Hello @nwohlgemuth nwohlgemuth. Thanks for reporting this issue. You are using quite old az cli version. Support service bus topic was already added to CLI long time ago. Please move to latest version (2.12 currently). The following is part of the create cmd help for event subscription
--endpoint-type                                : The type of the destination endpoint.  Allowed
values: azurefunction, eventhub,
hybridconnection, servicebusqueue,
### servicebustopic, storagequeue, webhook.
Default: webhook.
$ az version
{
"azure-cli": "2.12.0",
"azure-cli-core": "2.12.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {
"ai-examples": "0.2.3"
}
}
Thanks

@ahamad-MS I opened this issue on May 19th. Azure CLI version 2.6.0 was released on May 19th. At that time, that was the newest version I could have possibly been using (same day as it was released!) but it did not support the requested feature. Since then, the feature was added. To workaround it in the meantime, I wrote code that directly made an HTTP request to the Azure API. Now that Azure CLI supports it, I will remove that code I wrote and use the Azure CLI.


JSON files 'subdeaddits_base.json' and 'users.json' not found

(venv) jcromero@missandei:~/src/deaddit$ python deaddit/data/load_seed_data.py
Starting subdeaddit ingestion...
Error: JSON file 'subdeaddits_base.json' not found.

Starting user ingestion...
Error: JSON file 'users.json' not found.

You must add the deaddit/data to the path or change the instructions in the README for executing the script.

Good catch - sorry about that. This is now fixed


NameHelper

Features

Added AbstractEntity support for class[]
Added NameHelper
Improved trigger_error and EntityPropertyTrait

Please improve doc if you can

Can see that @wonowicki changes are working, added small amount of docs to my understanding.


Modal: Modal Overlay colour is incorrect

Current Modal Overlay

Correct Modal Overlay

Acceptance Criteria:

Modal overlay background colour should be #333 --> --goa-color-greyscale-black
Modal overlay background colour should have an opacity of 50%

:tada: This issue has been resolved in version 1.17.0-alpha.57 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.17.0-alpha.29 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use index(s, t) instead of regular expression

for checking the common root. It is a simpler implementation.
I see a similar logic, still using ~! comparison exists since initial commit (9b240f3):
    } else for( i in a ) if( shortest !~ a[i] ) x = 1

Rename parameters in output function to avoid using multiple names for the same domains. Use the same names as in other functions.

This also fixes #203.


Method to 'autoCrop' right after loading source

We disabled 'autoCrop' because when there is no image, we put a placeholder on the canvas. When we load an image onto the canvas, we want to call a method to get the same effect as the autoCrop setting does.
Tried to find it around this line in the README but couldn't make a conclusion out of it:

As there is a asynchronous process when load the iamge, you should call most of the methods after built, except "setAspectRatio", "replace" and "destroy".

So, is there a method to automatically make a centered optimal crop after loading an image asynchronously?

Try the crop method:
$().cropper({
  autoCrop: false,
  built: function () {
    // Do something here
    // ...
    // And then:
    $(this).cropper('crop');
  }
});

This does work for the image that is initially loaded, but in not in the script I've found somewhere to load a local image into the canvas:
var $inputImage = $('#form_file'),
$inputImage.change(function () {
    var files = this.files,
    file;

    if (files && files.length) {
        file = files[0];

        if (/^image\/\w+$/.test(file.type)) {
            blobURL = URL.createObjectURL(file);
            $image.one('built.cropper', function () {
                URL.revokeObjectURL(blobURL); // Revoke when load complete
             }).cropper('reset').cropper('clear').cropper('replace', blobURL).cropper('crop');

         } else {
            sweetAlert('Please choose an image file.');
         }
     }
});

Also tried:
// ..
}).cropper('reset').cropper('clear').cropper('crop').cropper('replace', blobURL);
// ..

Cropping does work for the first image, but does not seem to work for the image that was loaded via this script.


[BUG]: AzureRmWebAppDeployment@4 missing localization resource for key BasicAuthNotSupported

New issue checklist

[X] I searched for existing GitHub issues
[X] I read pipeline troubleshooting guide
[X] I checked how to collect logs

Task name
AzureRmWebAppDeployment
Task version
4
Issue Description
I am trying to track a AzureRmWebAppDeployment which fail when using WebDeploy.
Anyway, during development, I received a warning in the logs which seems to be caused by a missing ressource in the task loc files:
##[debug]Site Publishing Policy check: {"id":"/subscriptions/xxx/basicPublishingCredentialsPolicies/scm","name":"scm","type":"Microsoft.Web/sites/basicPublishingCredentialsPolicies","location":"xxx","tags":{},"properties":{"allow":false}}
##[debug]Function App does not allow SCM Access
##[debug]USE_MSDEPLOY_TOKEN_AUTH=undefined
##[warning]Can't find loc string for key: BasicAuthNotSupported
##[debug]Processed: ##vso[task.issue type=warning;]Can't find loc string for key: BasicAuthNotSupported
##[debug]Deployment Failed with Error: Error: BasicAuthNotSupported
##[debug]task result: Failed
##[error]Error: BasicAuthNotSupported
##[debug]Processed: ##vso[task.issue type=error;]Error: BasicAuthNotSupported
##[debug]Processed: ##vso[task.complete result=Failed;]Error: BasicAuthNotSupported

Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2022.2 (AzureDevopsServer_20240702.1)
Operation system
Windows Server 2022 Datacenter 21H2
Relevant log output
##[debug]Site Publishing Policy check: {"id":"/subscriptions/xxx/basicPublishingCredentialsPolicies/scm","name":"scm","type":"Microsoft.Web/sites/basicPublishingCredentialsPolicies","location":"xxx","tags":{},"properties":{"allow":false}}
##[debug]Function App does not allow SCM Access
##[debug]USE_MSDEPLOY_TOKEN_AUTH=undefined
##[warning]Can't find loc string for key: BasicAuthNotSupported
##[debug]Processed: ##vso[task.issue type=warning;]Can't find loc string for key: BasicAuthNotSupported
##[debug]Deployment Failed with Error: Error: BasicAuthNotSupported
##[debug]task result: Failed
##[error]Error: BasicAuthNotSupported
##[debug]Processed: ##vso[task.issue type=error;]Error: BasicAuthNotSupported
##[debug]Processed: ##vso[task.complete result=Failed;]Error: BasicAuthNotSupported

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps
- task: AzureRmWebAppDeployment@4
  displayName: 'deploy azure webapp'
  inputs:
    ConnectionType: 'AzureRM'
    azureSubscription: 'Azure Subscription'
    appType: 'webApp'
    WebAppName: 'xxx'
    packageForLinux: '$(Build.ArtifactStagingDirectory)/website.zip'
    enableCustomDeployment: true
    DeploymentType: 'webDeploy'

It seems the incorrect ressource name usage is here: https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureRmWebAppDeploymentV4/operations/WebDeployUtility.ts#L65


feat(artifacts): always loglevel=trace for log artifacts

[x] This is a small change

Description:
When something wrong happens, we usually go to the logs.
When things mostly go alright, we don't turn on verbose logging mode.
At the moment, verbosity in log artifacts is tightly coupled to the verbosity of CLI output.
This PR suggests using always loglevel=trace for log artifacts, presuming that a user will stick to --record-logs failing in the majority of cases. If it is --record-logs all — better to take care of CI storage. ;)

Great!

LGTM 2 😄


Add information to unimplemented! messages

The first time I ran trustfall_stubgen this is what I saw:
thread 'main' panicked at~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/trustfall_core-0.7.1/src/schema/mod.rs:163:46:
not implemented
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This should alleviate that a bit. At some point, we should also have a reference detailing the difference between Trustfall and GraphQl schemas.

Pushed a format, should pass now


feat(order/basic) more max lemmas

Some lemmas about max that I use in my normed stuff

Are there already theorems saying that a \leq max b c iff a \leq b or a \leq c
and max b c \leq a iff b \leq a and c \leq a?
They would be good simprules, and I think many max proofs would then be automatically closed by simp or finish.

Thanks for this suggestions, I added those simp lemmas, and played some more Lean golf. However in three uses of these simp lemmas, I was forced to use simp only once.

The properties about max are already available but in a hidden form: discrete_linear_order forms a lattice and in this lattice max = sup. (lattice_of_decidable_linear_order) So you might want to move them to the end of lattice.lean and just prove them using the lattice instances.
Also the multiplication theorems should go into a theory were we officially talk about rings and orders: algebra/ordered_ring.lean

Hopefully I got files right this time. I was originally misled by your comments about algebra/ordered_ring.lean. After creating lots of sections about max and abs in files about ordered algebraic structures, I discovered the file algebra/functions.lean which actually contains all lemmas about max/min and abs with different sections for different algebraic structures. I had no idea this file existed (the file name was completely opaque to me).

Commited in 140c6728d6474eb259e7ddbd5c2d440426ff0f9a
I cleaned up the proofs:

many things are now derived from the lattice structures on linear orders
if you use have please also state the concrete statement you proof. Especially in term style.
put a space between simp and the list [...]
line length should be below 100 characters
in theorem names, the assumptions are separated using _of_


Travis CI

Release Playbook

[ ] Rebase against master

[ ] Code review

[ ] Merge into master

[ ] Verify changes at http://site-staging.convox.com

[ ] Promote release on site-production in the convox/production Rack

Remove JEKYLL_ENV from docker-compose.yml, as it gets set in _bin/web

Exclude vendor in _config.yml as per https://github.com/jekyll/jekyll/issues/2938

Check for broken links using Travis CI

 Add link checker to site CI


[system] TypeScript compose error

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Types of parameters 'props' and 'props' are incompatible.
Type '{ theme: DefaultTheme; }' …

Expected Behavior 🤔
No errors
Steps to Reproduce 🕹
https://codesandbox.io/s/create-react-app-with-typescript-02vx8
Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.7.1

React
16.12.0

Browser

TypeScript
3.7.2

etc.

@sunshixiong789  Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

https://codesandbox.io/embed/create-react-app-with-typescript-i5sp7
I used the demo, can't find error.    but use IDE, throw the typescript error

I can reproduce it in the codesandbox (you have to force it to evaluate the expression).
Can't confirm if it's an actual bug though.

I use the typescript3.5.2, it's a right,but I use the typescript3.6.3. throw the
Error:(24, 3) TS2345: Argument of type 'StyleFunction<Partial<Record<"border" | "borderBottom" | "borderColor" | "borderLeft" | "borderRadius" | "borderRight" | "borderTop", any>> & Partial<Record<"display" | "overflow" | "textOverflow" | "visibility" | "whiteSpace" | "displayPrint", any>> & ... 6 more ... & Partial<...>>' is not assignable to parameter of type 'CreateCSSProperties | ((props: { theme: DefaultTheme; }) => CreateCSSProperties)'.
Type 'StyleFunction<Partial<Record<"border" | "borderBottom" | "borderColor" | "borderLeft" | "borderRadius" | "borderRight" | "borderTop", any>> & Partial<Record<"display" | "overflow" | "textOverflow" | "visibility" | "whiteSpace" | "displayPrint", any>> & ... 6 more ... & Partial<...>>' is not assignable to type '(props: { theme: DefaultTheme; }) => CreateCSSProperties'.
Types of parameters 'props' and 'props' are incompatible.
Type '{ theme: DefaultTheme; }' has no properties in common with type 'Partial<Record<"border" | "borderBottom" | "borderColor" | "borderLeft" | "borderRadius" | "borderRight" | "borderTop", any>> & Partial<Record<"display" | "overflow" | "textOverflow" | "visibility" | "whiteSpace" | "displayPrint", any>> & ... 6 more ... & Partial<...>'.

It's not the same problem,you shoud use createStyles
https://codesandbox.io/embed/k10p4yj8zr

I find the error

https://codesandbox.io/embed/create-react-app-with-typescript-i5sp7

I have updated the issue description. The problem seems reproducible with the latest version.

I can't reproduce with the latest version (v5.0.0-alpha.13): https://codesandbox.io/s/create-react-app-with-typescript-forked-h8z1s?file=/src/Box.tsx.


enc, change salt handling, way 2

This is an attempt to workaround the 'curse' of the salt handling using the enc command :
The salt is not always stored with the encrypting data.
As could be expected, it is stored when it was generated on the fly (not supplied with args), but not only.
It is stored when no key is given.
And when stored, even good IV and key fails to decrypt.
You must enter the password (but are NOT prompted for).
This second PR act as folows :
When decrypting, first try to extract or skip any heading salt.
see also : #4486, #2083

This is not strictly a 1.1.1 bug/misfeature or feature-add, so I am removing the 1.1.1 milestone.

I think #4486 is preferable.


Enable the scroll wheel for zooming

Feels weird that it isn't allowed

@jasonlally @jeanwalshie is there a reason that we shouldn't allow the scroll wheel for zooming?

@jasonlally @jszwedko i just had to google "scroll wheel" haha. i have no thoughts on this and don't see why not! :)


Improve visibility of startup problems

Fixes #1873
Also improves behaviour in the case that the user has set a restart policy on weaver or weaveproxy, and then encountered a problem.
Replacement for #1879, now on master branch

Fixed cutpasta

This surprised me...
$ weave launch-router
dc4d47c5899bb063a771415f8290f83c87bfb19de6f82326370cae5e5c141c69
$ weave launch-plugin --foo
The weaveplugin container has died. Consult the container logs for further details.
$ weave launch-plugin
weaveplugin is restarting; you can stop it with 'weave stop-plugin'.

Perhaps we should do a docker kill in wait_for_status?

Perhaps we should do a docker kill in wait_for_status?

Done.

This works well. Not just for the plugin, but e.g.
WEAVE_DOCKER_ARGS="--restart=always" weave launch --foo

will now error and stop the container instead of hanging.


Remove Display for TextSize

We removed the Display impl for TextRange, we should at least consider removing it for TextSize as well.

Excellent observation! utf8 index does not make any sense for the user. Ie, using it as a "column", for example, would be wrong!

Excellent observation! utf8 index does not make any sense for the user. Ie, using it as a "column", for example, would be wrong!


Support for driver version 4.X

There are situations with Quarkus where the driver version 4.X is absolutely necessary and this seems to be the most usable solution for handling unit testing with database connection beans.

Hi,
I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast.
In the same time, testcontainers is an awesome project and can handle all mongodb version.
see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example

Hi,
I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast.
In the same time, testcontainers is an awesome project and can handle all mongodb version.
see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example

Hi,
I'm sorry but it's too hard to maintain fongo alone, and drivers are moving too fast.
In the same time, testcontainers is an awesome project and can handle all mongodb version.
see https://phauer.com/2019/modern-best-practices-testing-java/#dont-use-in-memory-databases-for-tests for example

hi @twillouer , I am working on upgrade of Fongo to support driver version 4.X. I will be a very big PR and I wanted to ask if you will be willing to review and merge such PR?

hi, thanks, yes, it will be possible :)

@vladimirmyp are u working on the PR. We were also upgrading our mongo client version to 4.x and faced the same issue with fmongo. Seeing your comment I refrained to start working on it.


Highlight exact fuzzy matches with different color

It would be great to have color highlighting for the matched characters.

Agreed, this will be tackled at some point

There is a working implementation, but I'm not happy with the performance


0.7.1

Coverage remained the same at 91.285% when pulling e1094aa026d78e0759e83cd1e37bf74ff7e6e81d on boguslavsky:fix-release into b632ad514089afcae685a49e4aa6e848c8b8c116 on exonum:master.

Coverage remained the same at 91.285% when pulling e1094aa026d78e0759e83cd1e37bf74ff7e6e81d on boguslavsky:fix-release into b632ad514089afcae685a49e4aa6e848c8b8c116 on exonum:master.


Error sending API - connection reset by peer

$ ./infracost configure set api_key $INFRACOST_API_KEY
$ ./infracost configure set tls_insecure_skip_verify true
$ ./infracost breakdown --path plan.json
i try to run this on k8s with gitlab runner
time="2022-06-06T02:02:48Z" level=error msg="Error reporting event: Error sending API request: Post "https://pricing.api.infracost.io/event\": read tcp 10.xx.x.xx:50120->3.xx.xxx.xx:443: read: connection reset by peer"

@mansan1230 what infracost --version are you using?
Please note that configure set tls_insecure_skip_verify true was only created for users who self-host the Cloud Pricing API who need to use a self-signed cert, is that what you're doing? if so, did you also set the endpoint to be your endpoint (shown below)? The logs above show pricing.api.infracost.io, which is our managed service:
export INFRACOST_PRICING_API_ENDPOINT=http://my-non-TLS-endpoint-here
export INFRACOST_TLS_INSECURE_SKIP_VERIFY=true

@mansan1230 what infracost --version are you using?
Please note that configure set tls_insecure_skip_verify true was only created for users who self-host the Cloud Pricing API who need to use a self-signed cert, is that what you're doing? if so, did you also set the endpoint to be your endpoint (shown below)? The logs above show pricing.api.infracost.io, which is our managed service.
export INFRACOST_PRICING_API_ENDPOINT=http://my-non-TLS-endpoint-here
export INFRACOST_TLS_INSECURE_SKIP_VERIFY=true

i am using  Infracost v0.10.1
even i commont "configure set tls_insecure_skip_verify true"
it still the same

Are you self-hosting the Cloud Pricing API?

no i did not

Then are you following this GitLab CI guide? Notice how that guide only asks you to set the INFRACOST_API_KEY: $INFRACOST_API_KEY env var, no need to run infracost configure commands.

@mansan1230 I'm going to close this but feel free to comment if you're still having issues


Wifi not supported

Hello,
I have installed ubuntu 20.04 today and thought that adding your packages would help to get the wifi to work.
I followed your instructions for pre-compiled mods (bios and packages) but ubuntu can't find a "supported wifi adapter" (it worked on windows). I have tried different solutions found on the internet :

Adding the code for the 3165 from intel to /lib/firmware https://www.intel.com/content/www/us/en/support/articles/000005511/network-and-io/wireless.html
and tried to rename them like they do here : https://itectec.com/ubuntu/ubuntu-how-to-install-intel-dual-band-wireless-ac-3165-drivers/
also tried this one (in french) : https://www.debian-fr.org/t/tuto-carte-wifi-intel-dual-band-wireless-ac-3165-sur-jessie-debian-8/71424
Tried "dmesg | grep iwl" but it returns nothing and "rfkill list all" only returns the Bluetooth hci0 :
0: hci0: Bluetooth
Soft blocked : no
Hard blocked : no
(found these commands here : https://ubuntuforums.org/showthread.php?t=2382682 )

I am able to connect to the internet through the Bluetooth connection but it's only a few kB/s.
Have you been through a similar problem? Do you have an idea to solve it?
Thank you for your great work :)
EDIT: I have version 3.05 of the BIOS, I think I will try to update to 3.06 as recommended here: https://techtablets.com/forum/topic/teclast-f5-bios-update/

I'm sorry for creating an issue for something that had nothing to do with your work, I reinstalled Windows to update the BIOS to 2.06 and the wifi now works.
Have a nice day.

@101Robotics Glad to be of some use.


[Event Request] Codeunit 1381 "Customer Templ. Mgt." - OnBeforeApplyTemplate

Hello Team,
in addition to #9881  i would like to have the following event.
local procedure ApplyTemplate(var Customer: Record Customer; CustomerTempl: Record "Customer Templ.")
//----------NewEvents---------------
var
    IsHandeld: Boolean;
//----------NewEvents---------------
begin
    //----------NewEvents---------------
    OnBeforeApplyTemplate(Customer, CustomerTempl, IsHandeld);
    if IsHandeld then
        exit;
    //----------NewEvents---------------
    Customer.City := CustomerTempl.City;
    Customer."Customer Posting Group" := CustomerTempl."Customer Posting Group";
    Customer."Currency Code" := CustomerTempl."Currency Code";
    Customer."Language Code" := CustomerTempl."Language Code";
    Customer."Payment Terms Code" := CustomerTempl."Payment Terms Code";
    Customer."Fin. Charge Terms Code" := CustomerTempl."Fin. Charge Terms Code";
    Customer."Invoice Disc. Code" := CustomerTempl."Invoice Disc. Code";
    Customer."Country/Region Code" := CustomerTempl."Country/Region Code";
    Customer."Bill-to Customer No." := CustomerTempl."Bill-to Customer No.";
    Customer."Payment Method Code" := CustomerTempl."Payment Method Code";
    Customer."Application Method" := CustomerTempl."Application Method".AsInteger();
    Customer."Prices Including VAT" := CustomerTempl."Prices Including VAT";
    Customer."Gen. Bus. Posting Group" := CustomerTempl."Gen. Bus. Posting Group";
    Customer."Post Code" := CustomerTempl."Post Code";
    Customer.County := CustomerTempl.County;
    Customer."VAT Bus. Posting Group" := CustomerTempl."VAT Bus. Posting Group";
    Customer."Block Payment Tolerance" := CustomerTempl."Block Payment Tolerance";
    Customer."Validate EU Vat Reg. No." := CustomerTempl."Validate EU Vat Reg. No.";
    Customer.Blocked := CustomerTempl.Blocked;
    Customer.Modify(true);
end;

//----------NewEvents---------------
[BusinessEvent(false)]
local procedure OnBeforeApplyTemplate(var Customer: Record Customer; CustomerTempl: Record "Customer Templ."; var IsHandeld: Boolean;)
begin
end;
//----------NewEvents---------------

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


MSID: 87935 Version: 1 DOI: 2<IP_ADDRESS>4894

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[ ] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87935)

or (only one should be ticked. remove other from description.)

[ ] Confirmed with Ted at bioRxiv that MECA archive is available

Send the following email to Ted and wait for his reply.
Hi Ted,

Please can you prepare the preprint MECA for 10.1101/2<IP_ADDRESS>4894

Thanks

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87935/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4894)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87935)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87935

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87935

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87935/v1/87935-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87935)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Response from datahub is:
{"detail":"No Docmaps available for requested manuscript from the publisher eLife"}

@HazalCiplak is this something you can investigate/help with?

Nice one thank you @HazalCiplak 🙌
@QueenKraken, It looks like the meca package isn't available going from bioRxiv's API:
$ curl "https://api.biorxiv.org/meca_index/elife/all/2<IP_ADDRESS>4894" | jq
{
  "status": [
    {
      "count": 0,
      "messages": "none found"
    }
  ]
}

This one was posted back at the start of April so I would expect it to be available.
Are you OK to reach out to Ted please? Thanks.


sim-se: gpu-tests are failing

Describe the bug
The daily tests, specifically the gpu-tests, are failing. This commit https://github.com/gem5/gem5/commit/00d4b6825c697a7c2b56d86ee54dc033c3c87794 appears to be causing the test failures. It is suspected that the older version of Ubuntu is incompatible with the changes introduced in this commit.
Affects version
current develop branch
To Reproduce
Build gem5 scons build/VEGA_X86/gem5.opt -j $(nproc) using this docker image ghcr.io/gem5/gcn-gpu:latest.
Terminal Output
This is the error message displayed in the terminal output during the build process.
src/sim/syscall_emul.hh:744:29: error: ‘struct statx’ has no member named ‘stx_mnt_id’; did you mean ‘stx_uid’?
  744 |     tgt->stx_mnt_id = host->stx_mnt_id;
      |                       ~~~~~~^~~~~~~~~~
      |                       stx_uid

@nmosier, could you please take a look at this issue? The commit that was merged yesterday is causing tests to fail. We tried to fix it but didn't find the appropriate solution. Thank you.

Oh no! I think the problem is because the statx struct is only defined on Linux hosts since v4.11. Are the GPU tests running on older Linux hosts (pre 4.11) or a different os (e.g., macOS)?

Oh no! I think the problem is because the statx struct is only defined on Linux hosts since v4.11. Are the GPU tests running on older Linux hosts (pre 4.11) or a different os (e.g., macOS)?
It could also be the members in struct statx has changed over time, and stx_mnt_id was added in a more recent version of the kernel than the one the GPU tests are running on.

I believe these tests are running on 5.14. They are running in the they are running on Ubuntu 20.04. According to this: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle, should be running with Linux 5.14.
However, I think this solution/patch would be worth checking. We have a way to reproduce this error so should be able to quickly verify if this fix works.

I submitted a patch. Let me know if that fixes the issue!

I've verified that this patch appears to fix this issue. I use docker run -u ${UID}:${GID} -v $(pwd):/gem5 -w /gem5 -it --rm ghcr.io/gem5/gcn-gpu:latest scons build/VEGA_X86/gem5.opt -j8 : on the develop branch it fails with the error outlined, but completes fine with #989.

Thanks for the quick fix!!


Fix segfault in iox_cheeky_app.cpp in ice_access_control example

Required information
When a subscriber is created without any readable shared memory segment it segfaults. This should not segfault in the example since this could be a valid use case. We have to provide a sensible error code instead.

@elfenpiff Isn't that a duplicate of #722?

Yes it seems so


Add functional test for dataplane extraMounts

This change adds a functional test for the dataplane extraMounts, this ensures we're able to validate our abstraction of the corev1.VolumeSource struct during functional tests.

@bshephar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 	450c6a4 link 	true 	/test openstack-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

Removing debug pod ...
error: unable to upgrade connection: container container-00 not found in pod oko-14-t6vvn-master-1-debug-m7lls_openstack-kuttl-tests

/test openstack-operator-build-deploy-kuttl


Not able to load multiple images for annotation

Hi,
I tried creating a task for testing with three images.

Task created successfully..Able to load the task..

But in all the three frames i am able to see only the first image.

Please suggest..

@vamsykothuru , please check files which you are loading. Probably they are all the same.

@vamsykothuru , need more information from you to advise something. I will close the issue for now. Don't hesitate to reopen it if you can reproduce the problem on your side and check that loaded images are different.

@nmanovic, I have checked the images. filenames deceived me. Filenames are different but seems like all are same.
Thanks for your time.
Thanks,
Ravi


Added support for arm64e (Mac M1 and new iPhones) architecture on LLDB

M1 Macs, newer iPhones and any device running on A12 Apple chipset run on a specific arm64e architecture that introduces some new features like PAC or nested virtualizations.
Registers, instructions and basic core ARM components are mostly the same as for arm64, but Voltron does not support arm64e architecture as shown in my issue : https://github.com/snare/voltron/issues/297.
Support for this arm64e architecture is not hard to implement thanks to the similarity of these two architecture versions, so here is my pull request to add this support on LLDB.
It may work with other debuggers but I have only tested it with LLDB.

Nice one @AdamTaguirov Looking that almost a year passed, I could move to your fork. @snare did you plan to merge this?


Consolidate auto-release workflow

what

Use cloudposse/github-action-auto-release in auto-release.yaml workflow

why

Solve old nodejs warning
Reduce duplication of code

/test

/test all

@goruha can you recheck this one ?

/test all

/terratest

/test all


Add styling for non-panel parts of sphinx-panels

Describe the bug
sphinx-panels dropdown directive does not respect dark mode if it is not within a panels directive
To Reproduce
sorry I don't have a full repro, but here's the page I used to test this
Bug
===

.. panels::

    Content of the top-left panel

    ---

    Content of the top-right panel

    :badge:`example,badge-primary`

    ---

    .. dropdown:: :fa:`eye,mr-1` Bottom-left panel

        Hidden content

    ---

    .. link-button:: https://example.com
        :text: Clickable Panel
        :classes: stretched-link

.. dropdown:: Click on me to see my content!

    I'm the content which can be anything:

    .. link-button:: https://example.com
        :text: Like a Button
        :classes: btn-primary

Expected behaviour
The dropdown at the bottom of the page should also have a dark background
Screenshots
https://gyazo.com/b53f60444de0427d08b270a280f9784e
https://gyazo.com/2ed3766faa9d43325e8b020311ad78a6
Desktop (please complete the following information):

OS: macOS Big Sur 11.2.1
Browser: safari
Version: 14.0.3

Additional context
Using the latest PyPi version for both Furo and sphinx-panels

GAH. Bootstrap colors. >.<
What's happening here is that custom colors are being set for sphinx-panel's panels, but not for the dropdowns (which are inheriting them from sphinx-panels) -- see https://github.com/pradyunsg/furo/blob/main/src/furo/assets/styles/extensions/_sphinx-panels.sass.
I guess the fix would be to add styling more for sphinx-panels things... Oh boy. That's gonna be a fun one.

Note sphinx-panels will eventually be deprecated for the new shiny https://sphinx-design.readthedocs.io/en/furo-theme 😄

So there this is basically the minimal css I've happened to work with dark mode: https://github.com/executablebooks/sphinx-design/blob/6b5982110bd4fb8a6d7ff6ec3ba16bb819ec39b6/docs/_static/sd-furo.css#L1

Note sphinx-panels will eventually be deprecated for the new shiny https://sphinx-design.readthedocs.io/en/furo-theme smile
the colors here are all css variables, so hopefully should be easier to override: https://sphinx-design.readthedocs.io/en/furo-theme/css_variables.html

@chrisjsewell Awesome! Just wanted to say thanks for pointing this out, because that's exactly the kind of stuff I've been looking for to resolve some of our docs layouts in my projects.

Added direct support for sphinx-design in db4dd7395d7f962a1fd02e90eb3e182ca316d518.
I'm gonna say that is enough, and we can close this now.

Oh, and once released, this is how sphinx-design stuff will look in Furo: https://pradyunsg.me/furo/kitchen-sink/sphinx-design/

I note the commit doesn’t seem to change the colours when in dark mode, like the current furo css does in sphinx-design?

It does. All the variables used there are modified when the page is in dark mode.

Further, what's there in the sample doc for sphinx-design right now won't work with Furo versions that have the dark mode toggle.

Maybe I'm missing something in the implementation, but what if you used e.g. :color: dark? In https://github.com/executablebooks/sphinx-design/blob/68b75e8cda9b3760555e6aaca3739ca3266fd8e9/docs/_static/sd-furo.css#L1 it changes --sd-color-light and --sd-color-dark when in dark mode, but I don't see that here?

:color: dark for a button?

It'll be dark, regardless of dark mode vs light mode? I don't think "dark" should look light on dark mode or vice-versa. 🤷🏽

I don't think "dark" should look light on dark mode or vice-versa. 🤷🏽

yeh hmm, maybe the naming of light and dark should be changed to something like high-contrast and low-contrast, since this is how I envisage them being used semantically. What do you think?

I can't imagine any good reason to have low-contrast content. 🤷🏽
Let's move the discussion to https://github.com/executablebooks/sphinx-design/pull/22?

Released in beta43.


Log capture for Kubernetes tests in Travis

We currently have no way to capture and dump the output from Kubernetes pods running in our Travis test jobs. I found an example of a pretty simple setup (using fluentd) that would let us grab stdout/stderr on all running pods and cat them all into a single long-running system pod:
https://github.com/joatmon08/kubernetes-reference/tree/master/logging
We could then use kubectl logs to dump all the output to a file for debugging failures.
We should also ensure that Kitchen defaults to use stream=sys.stderr for logging when it's running in our test container on Kubernetes.

Fixed in #359.


Check task logs in tests

Refers to #127
The flaky issue that was happening was:
TaskRun gets marked as 'done' before we can collect any logs. Ideally, we want to mark the task as 'done' only after the container logs had been captured.

Superseded by #267.


Set custom selected options after loading the tree

Hello,
How i can set my custom selected options after loading the tree?
Thanks

Do you mean checking specific options after loading, or adding options?

I only need to set value for every checkbox control inside the tree
Thanks

You have to render the HTML with the option value. See the demo. You're not supposed to modify anything inside the tree-multiselect manually.


Creating a schematic for the bot

A major problem we had last year was only a handful of people knowing where a wire went if it fell out. We are working hard to mitigate that risk this year through a combination of new wire management techniques and the Dark Power project.  However it is still helpful to have a document to reference the wireing layout including pins on the beagle bone to the various modules.
This needs to be done fore the Line Following dev-bot and the same thing needs to be created for the new bot as it is built.
This issues specifically pertains to creating the documents and beginning to layout the schematic

The wiki has been a great help.


modify canary to use shallow from env

Issue #, if available: n/a
Description of changes:

Modifying the run_test script to add the shallow marker based off an environment variable rather than having it in the script

Testing

Tested inside one of the canaries

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/retest


Fix dex for Kubernetes 1.21

Which issue is resolved by this Pull Request:
Pulling fix from https://github.com/kubeflow/manifests/pull/1883 regarding an issue where dex pods were not getting creating the kubeflow namespace for EKS cluster running version 1.21.
Description of your changes:
Update dex deployment.yaml
Checklist:
CLI verifcation:
❮ kbl get pods -n auth
NAME                   READY   STATUS    RESTARTS   AGE
dex-5ddf47d88d-fh29t   1/1     Running   1          6m21s

[x] Manual testing EKS v1.21 (verify fix)

[x] Verify pod in CLI
[x] Connect to central dashboard and run an experiment

[x] Manual testing EKS v1.19 (verify fix doesn't break previous versions)

[x] Verify pod in CLI
[x] Connect to central dashboard and run an experiment

We should also test on 1.20 since this is a last minute fix, ok to merge if all 3 versions are tested.


Question about relay and SSL/TLS

We are interested in using relay mode for docker-mailserver. A question though which is not documented in the relay wiki page.
Our external SMTP requires the use to SSL or TLS. How to setup the relay for these modes to be used?  Will docker-mailserver guess and auto apply either mode depending on RELAY_PORT value?
Then do we have to send mail to docker-mailserver on the same as RELAY_PORT or on 25?

The wiki https://github.com/tomav/docker-mailserver/wiki/Configure-Relay-Hosts uses TLS

Yes but what is the port I need to send my mail against in order for the email to be relayed to my server using TLS?
I saw on your wiki we can have @domain1.com        [relay1.org]:587  but it does not stats what is the port we have to use to send the email to docker-mailserver.
Do we have to do:
backend --> docker-mailserver:25 --> relay:587
Or:
backend --> docker-mailserver:587 --> relay:587

TLDR: the second one, assuming "backend" is a mail client, not another mailserver.
docker-mailserver should use TLS if it's offered by your relay, see http://www.postfix.org/postconf.5.html#smtp_use_tls which is set to yes when you add a relay host.
docker-mailserver will only accept connections from mail clients on 465 and 587 as per the README.

Our backend is indeed a java application acting as mail client to send email through SMTP. So we were looking for proper settings to put on our code to send emails through docker-mailserver (which will act as relay to the real SMTP given by our customer).
Your explanation makes things clearer for us. Another question comes in mind though: our java backend (client) will send the email on 587. But I am right saying my backend doesn't have to know the relay user and password?
We basically just have to send email to docker-mailserver on port 587, then, docker-mailserver will relay the email with proper user and password? So our code doesn't have to know about these credentials.

Right - your backend doesn't know anything about the relay. The relay info lives in the configuration of docker-mailserver.

@blackholegalaxy is this all good now? can it be closed?

Yes of course thanks for explanations.


Bump some versions

Hi again,
I just have been looking at the dependency versions here, nailed within [1] and [2]. I would suggest that we might want to upgrade some of the main artefacts.

Sphinx is available in version 3.3.1.
Vale is available in version 2.6.5.
Also: docutils==0.16.

With kind regards,
Andreas.
[1] https://github.com/crate/crate-docs/blob/master/src/requirements.txt
[2] https://github.com/crate/crate-docs/blob/master/src/rules.mk
P.S.: General compatibility of the crate-docs-theme with Sphinx 3.x should be given. See also https://github.com/crate/crate-docs-theme/issues/232, https://github.com/crate/crate-docs-theme/pull/233 and https://github.com/crate/crate/pull/10836 where we have been working on bringing this to the crate/crate repository.

This has been improved through #40 and #43.


Add a sub-command generator and auto loader for user infrastructure code

Codecov Report

Merging #50 into master will increase coverage by 0.02%.
The diff coverage is 31.42%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
+ Coverage   25.54%   25.57%   +0.02%
==========================================
  Files          14       16       +2
  Lines         274      305      +31
==========================================
+ Hits           70       78       +8
- Misses        204      227      +23

Impacted Files
Coverage Δ

tpl/tasks/command.rb.erb
0% <0%> (ø)

lib/kite.rb
100% <100%> (ø)
:arrow_up:

lib/kite/core.rb
80% <100%> (+1.42%)
:arrow_up:

lib/kite/generate.rb
25% <18.75%> (-12.5%)
:arrow_down:

lib/kite/user_tasks_autoload.rb
50% <50%> (ø)

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 fcff8bf...596c9ae. Read the comment docs.


Upgrades tedious version

Upgrades node-mssql to use version 1.13.x of tedious . There don't seem to be any breaking changes but a major improvement in performance.
Signed-off-by: Luca Moser

Thanks.


Option for async chunk loading with network error

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
For code splitting with async chunk loading,
when the chunk fail to load, it will call the error callback.
There are no option to have a fallback url for the chunk
What is the expected behavior?
By default is load the chunk base on public path, etc http://cdn.example.com/chunk-1.js
if http://cdn.example.com/chunk-1.js fail to load (404 or timeout),
I can config and fallback path, like http://another-cdn.example.com
so that it will try to load http://another-cdn.example.com/chunk-1.js
If this is a feature request, what is motivation or use case for changing the behavior?
The use case is if the CDN network fail in some region, it can automatically fallback to another CDN or the web server to get the chunk.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
I am using webpack 2, node v6.9.4, macOS Sierra

Try this:
const cdns = [
	"https://cdn1.example.com/",
	"https://cdn2.example.com/",
	"https://cdn3.example.com/",
];

let currentCdn = 0;

const original = __webpack_chunk_load__;
__webpack_chunk_load__ = (id) => {
	let n = cdns.length;
	return (function tryCdn() {
		if(--n === 0)
			return original(id);
		return original(id).catch(e => {
			currentCdn = (currentCdn + 1) % cdns.length;
			__webpack_public_path__ = cdns[currentCdn];
			return tryCdn();
		})
	}());
}

@sokra
Thanks for your quick reply!
But I don't where should i put these code
Do you mean I have to create a plugin?

I understand what to do after reading this
I have to put the code in my application code and webpack_chunk_load is accessable from the compiled code

@sokra How to provide fallback if you load only some files from CDN? E.g. angular and jquery which are set external: in webpack config (implemented as in the docs), but not the chunks of your own code?
Right now adding require(file-loader!pathToLibOnOurServer) throws error __webpack_public_path__ is not defined
Or should it be done with the script which is outside of webpack?

Is it somehow possible to get chunk information from the chunk id, which is passed to the __webpack_chunk_load__ function?

one thing that confused me at first, which it might help to mention in the docs, is that __webpack_chunk_load__ gets compiled to __webpack_require__.e.
At first I thought it was a local variable and assigning to it would only take effect locally.  It was only when I saw that assigning to it changes the value of __webpack_require__.e shared by all modules that I understood why this recommendation works.

If one uses MiniCssExtractPlugin and both chunk.css and chunk.js fail for certain chunkId then there'll be an uncaught exception. It's because they both put a promise on the same installedChunks[chunkId] and the first one that get rejected - free the Promise.all defined in the end of webpack_require.e.

To solve this I extended MiniCssExtractPlugin with a custom plugin and in the hookmainTemplate.hooks.requireEnsure.tap I replaced rejecet(err) with resolve(). This way only the chunk.js will fire a fallback to the next cdn.

I think we should add this line below, otherwise the first chunk that's failing will force all later loaded chunks to fallback also.
Like this:

const original = __webpack_chunk_load__;
__webpack_chunk_load__ = (id) => {
	 __webpack_public_path__ = cdns[0]     <---------
	let n = cdns.length;
	return (function tryCdn() {
		if(--n === 0)
			return original(id);
		return original(id).catch(e => {
			currentCdn = (currentCdn + 1) % cdns.length;
			__webpack_public_path__ = cdns[currentCdn];
			return tryCdn();
		})
	}());
}


Data Validation at the backend

Problem description
Currently when a schema has been created outside the UI, or for some types even tif they have been validated by the UI, the backend fails to validate it, or recognise as valid in the latter case.
Requirements
Need to add Data Validation at the backend, compatible with the validation rules in the front-end.
Definition of done
Validation are added and tested
Acceptance criteria
Full compatibility with UI validation and backend.

Related to #43

Please add your planning poker estimate with ZenHub @anvabr

This issue was closed on March 14th.


Default parameters in MaltExtract leading missing output

Hi,
When comparing my previous mapping results -which seem to be authentic- with the aMETA output, I noticed that there were significantly fewer reads in each case. Upon further investigation into the aMETA outputs, I observed that the default parameters in MaltExtract may lead to missing data in the final output. The default settings and their functions are as follows:
--destackingOff: This option removes reads in situations where there is an overlapping sequence between them. Essentially, using this option significantly decreases the total number of assigned reads on the specified node. It results in a lower number of reads but achieves high genome coverage.
--downSampOff: I think this option was added to speed up the process. Essentially, it restricts the maximum number of assigned reads for a specified node to 10,000.
--dupRemOff: It removes PCR duplicates. While it is a good option, sometimes obtaining raw, unfiltered data can be preferable. I use my in-house script to remove PCR duplicates.
From my understanding, in the aMETA pipeline, MaltExtract is only running with the parameters below:
-i -f -o --reads --threads --matches --minPI 85.0 --maxReadLength 0 --minComp 0.0 --meganSummary -t

It appears that the three parameters I mentioned above are missing. It seems like there may need to be some modifications in the aMETA pipeline to include those parameters accordingly. Detailed information for MaltExtract parameters can be found in the HOPS Github page.

Arda is right, I have been avoiding to use the fasta files generated by MaltExtract because they always seemed to have too few reads and these default parameters are the reason.
I have now investigated it for one taxid in two samples.
Sample 1:

Pipeline MaltExtract rule: 2521 defaults reads for the species
MaltExtract command suggested by Arda: 3557
Megan extract reads from species and lower nodes manually: 3557

Sample 2:

Pipeline MaltExtract rule: 2521 defaults reads for the species: 6219
MaltExtract command suggested by Arda: 81171
Megan extract reads from species and lower nodes manually: 81171

In the second case, a tremendous amount of reads is lost and this reflects in the authentication plots that don't appear to have a similar amount of reads depending on the input file they use.
So I suggest we include:
--destackingOff
--downSampOff
--dupRemOff
In the Maltextract command to allow the user to obtain all the reads for a species and do downstream analyses involving those reads.

Agreed, will be fixed in the next PR

Thank you @ardasevkar for your valuable input! We have added
--destackingOff
--downSampOff
--dupRemOff
to the MaltExtract command line in the latest PR.


IndexError: list index out of range

Your project is very interesting and has indeed simplified my development process.
I have tested the library and it throws an exception when receiving data that is too long.
Also, this could potentially risk out of memory as well.
Here is my code
# netcore  ==  0.0.1
# python   ==  3.10.11
# platform ==  windows10

length = 1024 * 1024 * 1024
sk = socket.socket()
sk.connect(('localhost', 5555))
head = pt.Protocol.make_head('.test', length, 'utf-8')
sk.send(head)
pt.Protocol.stream_until(bytes, length, writefunc=sk.send)
sk.close()

And the Error
protocol, line 368, in __recver safe = info[1] IndexError: list index out of range

Your project is very interesting and has indeed simplified my development process.
I have tested the library and it throws an exception when receiving data that is too long. Also, this could potentially risk out of memory as well.
Here is my code
# netcore  ==  0.0.1
# python   ==  3.10.11
# platform ==  windows10

length = 1024 * 1024 * 1024
sk = socket.socket()
sk.connect(('localhost', 5555))
head = pt.Protocol.make_head('.test', length, 'utf-8')
sk.send(head)
pt.Protocol.stream_until(bytes, length, writefunc=sk.send)
sk.close()

And the Error
protocol, line 368, in __recver safe = info[1] IndexError: list index out of range

For the error caused by your test, it may be that you are not using safecode()
head = pt.Protocol.make_head('.test'+pt.safecode(), length, 'utf-8')

In addition, Package receives data roughly in two steps, the first step is to receive the HEAD information, and the second step is to receive the META.

I suggest that both parties to the communication use one class consistently
Endpoint ( Package ) OR Protocol


Update tooltips.md

Typo

Howdy—thanks for the pull request, @kennethlove!
Before we can merge your changes, we need you to review our Contributor License Agreement (CLA). We think of CLAs as an open source software license between you and the project, letting us and other users know that we have permission to use the code you contribute.
At the bottom of the pull request, you'll see the note about a failed test. Just click the Details link, review the CLA, and sign off at the bottom.
Questions? Just holler—I'm here to help :).
<3

Done!

Thanks!


Add simple performance test

Coverage decreased (-1.0%) to 44.198% when pulling 95e8e07385aeecc5aab0a3c07cb819c12e15d6b7 on performance-test into 0e90ae7a00efda5077b9888a53fc67f74fa61566 on master.

Coverage decreased (-1.1%) to 44.055% when pulling 1320cfa964d7c49c925228c7708b5808ced3f1b1 on performance-test into 0e90ae7a00efda5077b9888a53fc67f74fa61566 on master.

Coverage decreased (-1.1%) to 44.021% when pulling 1320cfa964d7c49c925228c7708b5808ced3f1b1 on performance-test into 0e90ae7a00efda5077b9888a53fc67f74fa61566 on master.


✨ Add work hours to profile card

Cc: @jimmidier @BrookJeynes @william-liebenberg @adamcogan

To myself
Pain

Hi Luke
I always forget which days Kiki is working… it is Tue, Thu and Fri.
If it is not normal it would be good to see in SophieBot.

Under “Last Seen” could you add the field in CRM that has his working days (but only if it is not null)

Tasks

[x] Investigate
[x] Add workHours field to employees endpoint
[x] Display Work Hours on profile card

Screenshots

Figure: Current profile
Definition of Done

[x] All tasks are updated and closed
[x] No high priority defects/bugs are on that user story
[x] Code reviewed by one other team member (e.g. Checked by Bill)
[x] All acceptance criteria have been met
[x] Deployed to Dev
[ ] (If implemented) Pass automated UI testing
[x] (If not implemented above) Do a manual test on all supported commands (at least one for each LUIS intent) against Dev
[x] Complex code is documented (removing technical debt)
[x] Deployed to Production
[x] Add description about the changes for the PBI
[x] Tick off the definition of done tasks in the PBI
[ ] (Optional) A Done Video, particularly for PBI with multiple stages

Thanks!

Done

Figure: Work Hours added

Hi @jimmidier
This is inconsistent with CRM.

Vs

Please investigate and fix

-a

In code, how did the line breaks get lost?

The Adaptive Cards doesn't interpret the line breaks correctly
I used | to replace the line breaks to make the content more compact.

Please investigate and fix

Done

Figure: Work Hours now is consistent with CRM

Hi @adamcogan

This is inconsistent with CRM. Did you check the UI?

I was not aware of the requirement that the text format should be consistent with the one in CRM, so I approved the PR after checking the code change and attached screenshot.

If not, what process in your PR approval should change?

As per above, it's an issue of misunderstanding of the acceptance criteria so I think it's the issue description that need be improved rather than the PR approval process.

In code, how did the line breaks get lost?

The Adaptive Cards doesn't interpret the line breaks correctly
I used | to replace the line breaks to make the content more compact.

Please investigate and fix

Done

Figure: Work Hours now is consistent with CRM


[Only-Test] Some pull requests cause memory errors when pipeline is not enabled.

Proposed changes

Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run p0

run buildall


Use file.readAsBytes() on Flutter web

Hello
I used file_selector on flutter web to get an image file, after that I tried to get Uint8List of this file by using readAsBytesSync method but it's throw a bug, I tried to use readAsBytes and don't work too.
So how can I get Uint8List in flutter web?

Hi @MuhmdHsn313, please provide a complete minimal reproducible code sample as well as the output of flutter doctor -v and flutter run -v that shows the error that you're experiencing.
Thank you

Flutter doctor -v
[√] Flutter (Channel stable, 2.10.3, on Microsoft Windows [Version 10.0.22000.556], locale en-US)
    • Flutter version 2.10.3 at C:\Program Files\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (4 weeks ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at C:\Users\muham\AppData\Local\Android\sdk
    • Platform android-32, build-tools 32.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.7)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.31911.196
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code (version 1.66.0)
    • VS Code at C:\Users\muham\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.36.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22000.556]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 99.0.4844.84
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 99.0.1150.55

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

the line of code that make the bug
final rawPath = file1.readAsBytesSync();

the error showing when I run flutter web app
Error: Unsupported operation: _Namespace
    at Object.throw_ [as throw] (http://localhost:53611/dart_sdk.js:5067:11)
    at Function.get _namespace [as _namespace] (http://localhost:53611/dart_sdk.js:56704:17)
    at io._File.new.openSync (http://localhost:53611/dart_sdk.js:54742:45)
    at io._File.new.readAsBytesSync (http://localhost:53611/dart_sdk.js:54795:25)
at printed_kyc.KycStepperPdf.new.generatePDF (http://localhost:53611/packages/merchant_portal/features/home/presentation/widgets/printed_kyc.dart.lib.js:310:29)
    at generatePDF.next (<anonymous>)
    at http://localhost:53611/dart_sdk.js:40571:33
    at _RootZone.runUnary (http://localhost:53611/dart_sdk.js:40441:59)
    at _FutureListener.thenAwait.handleValue (http://localhost:53611/dart_sdk.js:35363:29)
    at handleValueCallback (http://localhost:53611/dart_sdk.js:35931:49)
    at Function._propagateToListeners (http://localhost:53611/dart_sdk.js:35969:17)
    at _Future.new.[_completeWithValue] (http://localhost:53611/dart_sdk.js:35817:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:53611/dart_sdk.js:35838:35)
    at Object._microtaskLoop (http://localhost:53611/dart_sdk.js:40708:13)
    at _startMicrotaskLoop (http://localhost:53611/dart_sdk.js:40714:13)
    at http://localhost:53611/dart_sdk.js:36191:9

Hi @MuhmdHsn313, the error is due to the fact that reasAsBytesSync is from dart:io which is not available on web. Can you check this SO comment to see if the solution used works for you?

Unfortunately, It's don't work!
I need to export a PDF file using pdf package, so I need to get it as Uint8List from flutter web, after that I can use Uint8List to print image in PDF.

Thanks @danagbemava-nc
I solve this bug using networkImage, this is be more easy when I understand this idea, we have to replace io with network in flutter web.
final netImage = await networkImage('https://www.nfet.net/nfet.jpg');

now it's work correctly!


OOM error caused by AzureMonitorLogRecordExporter

Below line cause OOM error. When DEBUG level is on, there will be some kind of recursive invocation.
LogRecords logging causes more log entries which causes sending more and more LogRecords.
https://github.com/Azure/azure-sdk-for-java/blob/174041384dd09ac1bb23a07655f4a966af7c777a/sdk/monitor/azure-monitor-opentelemetry-exporter/src/main/java/com/azure/monitor/opentelemetry/exporter/AzureMonitorLogRecordExporter.java#L57

@rafalp88
Thank you for reporting this!
As a mitigation step,  could you please disable verbose logs from com.azure.monitor.opentelemetry.exporter? If you haven't done it already ?
@heyams @trask could you please take a look?
it seems exporter logs with ClientLogger from core which, when such debug logs are enabled, produces enormous amount of logs.
We might need to figure out how to disable all logs from the exporter http pipeline completely or prevent the exporter from consuming its own logs in some other way. LMK if you need any help with ClientLogger.


WIP: Enable last will

Enable the library to use last will during connection
https://www.eclipse.org/paho/files/mqttdoc/MQTTClient/html/struct_m_q_t_t_client__will_options.html
To test:
$ mosquitto_sub -v -t "test"

\l mqtt.q
opts:`lastWillTopic`lastWillQos`lastWillMessage`lastWillRetain!(`test;2i;"disconnect";0i)
.mqtt.conn[`localhost:1883;`src;opts]
\\

mosquitto_sub will print:
test disconnect

One problem - the mac build is failing on Travis.
The problem is the use of strndup which I believe is a GNU extension that isn't support on earlier OS X builds.
We could bump the travis OS X image (as is done by arrowkdb) but it's probably easier to change the strndup to a malloc + memcpy  (or just use plain strdup if the strings don't contain \0 chars)


[bug] Task resolution cannot merge and extends correctly

Describe the bug

✅ When a task B extends another task A, it inherits all its field
✅ When a task A is override by a workspace, it inherits all its field
❌  When a task B extends a taks A and this task A is override in a workspace, the override inheritance doesn't work (the extends works)
Steps to reproduce

Clone 'https://github.com/maastrich/repro/tree/moonrepo/moon-1146' (go to branch moonrepo/moon-1146)
pnpm i --frozen-lockfile
moon run app:child

You will see that the child task run as noop (no command is defined in apps/app/moon.yml in the parent task)
Expected behavior
I would expect the command to be defined and inherited from the original parent task
expected output of moon run app:child -> VAR1: parent-overridden, VAR2: child
Screenshots

Environment
  System:
    OS: macOS 13.6
    CPU: (10) arm64 Apple M1 Max
    Memory: 86.95 MB / 32.00 GB
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.6.0 - ~/.proto/bin/node
    Yarn: 3.6.4 - ~/.proto/bin/yarn
    npm: 10.2.0 - ~/.proto/bin/npm
    pnpm: 8.7.3 - ~/.proto/bin/pnpm
  Managers:
    Homebrew: 4.1.17 - /opt/homebrew/bin/brew
    pip3: 21.3.1 - /opt/homebrew/bin/pip3
    RubyGems: <IP_ADDRESS> - /usr/bin/gem
  Utilities:
    CMake: 3.27.5 - /opt/homebrew/bin/cmake
    Make: 3.81 - /usr/bin/make
    GCC: 15.0.0 - /usr/bin/gcc
    Git: 2.42.0 - /opt/homebrew/bin/git
    Clang: 15.0.0 - /usr/bin/clang
    FFmpeg: 6.0 - /opt/homebrew/bin/ffmpeg
    Curl: 8.1.2 - /usr/bin/curl
  Servers:
    Apache: 2.4.56 - /usr/sbin/apachectl
  Virtualization:
    Docker: 20.10.23 - /usr/local/bin/docker
  IDEs:
    Emacs: 29.1 - /opt/homebrew/bin/emacs
    VSCode: 1.83.1 - /usr/local/bin/code
    Vim: 9.0 - /usr/bin/vim
    Xcode: /undefined - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Go: 1.21.1 - /opt/homebrew/bin/go
    Perl: 5.36.1 - /opt/homebrew/bin/perl
    PHP: 8.2.10 - /opt/homebrew/bin/php
    Protoc: 24.3 - /opt/homebrew/bin/protoc
    Python: 3.11.6 - /Users/maastrich/.proto/bin/python
    Python3: 3.11.5 - /opt/homebrew/bin/python3
    Ruby: 2.6.10 - /usr/bin/ruby
  Databases:
    SQLite: 3.39.5 - /usr/bin/sqlite3
  Browsers:
    Chrome: 118.0.5993.88
    Safari: 16.6

Thanks for your reply @milesj ,
build global B
build local A
build local B

This seems good to me as a process
I'm wondering if, when you build local B,  local A has already been built and is passed as an already merged task 🤔
Isn't it possible that the  build of both local tasks is run concurrently ? causing a not merged local A, being extended by local B ?

I think I figured this out in 1.16 if you want to try it.

@milesj It seems to be working fine again 💪
Thanks for your time, I'll leave you the liberty of closing the issue