HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

did it bud. noice


Missing space after "Authorization: Bearer" in curl command

Using devportal then trying to execute a curl request, the curl generated statment shows that the token value is merged with the string bearer in the header.
Example of generated curl command:
curl -X GET "http://localhost:8280/hello/v1" -H "accept: /" -H "Authorization: BearereyJ0eXAiOiJKV1QiLCJhb.............;"

Hi @BeParis
Could you please let us know the API version you are using?

There was a similar issue reported with M4 and we have fixed it in M5 release.
Please refer [1].
[1] https://github.com/wso2/product-apim/issues/7098


Link to matched text in Markdown Page

Context
We want to be able to link people to specific parts of the Terms page.
The current MarkDownPage is great for maintaining documentation from legal to serve on the site. One limitation we currently have is that if we change the Markdown, there is no way to keep that consistent with the original docx file.
Problem or idea
We should add logic to the MarkdownPage that allows us to navigate to any page that uses that component and read a query parameter called match. The value of this query parameter should be a string that should match the inner text of an element on the page.
Ex: /terms-of-use?match=Access to and Use of Content should load the page and then scroll down until that section is at the top of the screen.
These markdown docs change infrequently but do change. In order to prevent this from breaking in the future we should collect the strings that we want to match in a config file that we can write tests for in a future issue. For now, lets just have Access to and Use of Content in there as we will be using that soon.
A suggestion for solving this would be using XPath.
Solution or next step

add new config for matchable sections of the about page
add mentioned logic to MarkdownPage

@davidsmejia Instead of using a query parameter match, do you want to generate a navigation (a kind of table of contents) and display it at the top of a page, making it easier for users to navigate through each section (or both)?

Hey I think I understand what you mean, could you just give me an initial approach to how we would have the auto-inserted ids?
I think the TOC/menu features are outside of the scope of what we are trying to accomplish at this moment. Could you create a new issue for that and then ping me and Deepa for that. I don't have any reason to say we shouldn't do it at this time just that there would be some design to it and we don't explicitly need it at this time.

an initial approach to how we would have the auto-inserted ids?

My approach is to first get all the necessary DOM elements of the sections that need be linkable in a markdown page (e.g., Eligibility, Account Registration , Access to and Use of Content), and then assign an id to each section so that it can be linked from anywhere in the application.

I think the TOC/menu features are outside of the scope of what we are trying to accomplish at this moment. Could you create a new issue for that and then ping me and Deepa for that.

Sure, will do 👍 I was going to ask Deepa's feedback if one of my suggestions above would be a good candidate for a new feature to be added to markdown pages (and if so, yes, that would be handled in a separate issue!).

My approach is to first get all the necessary DOM elements of the sections that need be linkable in a markdown page (e.g., Eligibility, Account Registration , Access to and Use of Content), and then assign an id to each section so that it can be linked from anywhere in the application.

What I like about your suggestion is that it looks and feels like how you would normally link to a div or element on a page. Ideally we would be able to implement this outside of editing the markdown which is what I think you mean when you say auto inserted id's.
One thing that I think might be useful with using something like XPath or more generally searching innertext is that it would allow us to navigate nested subsections without assigning id's on the server by default since it doesn't care about the page structure only the contents and would work on any MarkdownPage component.
So in the future if we need to add new predefined sections that we want to link to, we would just add them to the config and use them and the matcher would already be able to find the element that contains the text.
Additionally, we would be able to write tests since the .md file would have to be checked on update we could automate a test to ensure that anything we explicitly want to match can be found in the markdown file as a check via github actions.
So I think the inner text solution would be a quick implementation that would be more flexible for the future usage since we are dealing with a document that we really don't want to make modifications whenever we want to update it. I think either solution would be testable.
If you want to implement the assigning id's for now that seems ok to me since we don't really have any actual use cases for this at the moment other than linking to Access to and Use of Content in an upcoming issue.

Yes, let's use the id for page linking on FE.

Ideally we would be able to implement this outside of editing the markdown which is what I think you mean when you say auto inserted id's.

As chatted on 1:1, inserting an id to each section won’t edit the original markdown, since that manipulation will be performed on html elements that we generate using that markdown file and those id attributes will be only present during runtime (when component mounts and renders the page in a browser).
Here is the approach using the `id. Please let me know if any suggestions/ideas:
On FE, at runtime, we'll use the most recent markdown file to populate a list of linkable sections, and it will be re-populated when changes are made to the markdown file and is committed to CVS.
Breakdown:
Step 1: After the MarkdownPage component is mounted (when the markdown HTML is ready),  we get all the sections that needs to be linked. HTML for Terms of Use and Privacy Policy currently share the same page structure, so those sections can be easy to be obtained.
Step 2: Once you have a list of all the sections that can be linked, insert IDs into them using text contents (e.g., Eligibility, Account Registration, Access to and Use of Content).

...we need to add new predefined sections that we want to link to, we would just add them to the config  and use them and the matcher would already be able to find the element that contains the text.

Step 3: For the config, we can create it using that text contents (in Step 2)
Step 4: We'll create a macther helper (e.g., getMarkdownLink(route, section)) which composes a URL for each section based on the given page route and section name (defined in the config), so that it can be used anywhere in the application.
 I was able to link each section, however when scrolled (to that section on page load), the site header and the content of the selected section's content overlap.
I am trying to hack it but the site structure might need to be adjusted. Let me know your thought on this (any alternative solution)!
e.g. ) the terms of use page
The linked sections:

The selected section's content overlaps with the site header (*disregard the border, it's for testing):

But it should be:

Merged #555


[GURPS] 2.11.0

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

NEW: GCS Export/Import, see the instructions on the import tab. Gear Icon > Import tab.
ENHANCEMENTS: Some changes for the importer to work with files generated by the GCS Roll20 exporter.

Character Sheet Info Roll20 Internal Use only.


Remove duplicate child/calls edge; Function CUs now know their children and vice versa, refactorings

[x]  consistently use NodeID or LineID instead of str as a type to make them easy to differentiate
[x]  remove child edges when there is a calls edge
[ ]  improve performance by looking at the graph from a function point-of-view

sorry for all the notifications, i only just noticed you are already involved in this PR 😅
This is now in a state that can be merged. I can put further improvements based on these changes in another merge request.
@lukasrothenberger


Put all the extension in a tabular format

@sivolko Can we put all the extensions in a tabular format?

Yes I can,  I m confused with duplicate one. In last PR  a few were duplicated ?

@sivolko Great work. I see a few of them not in a tabular format. Most of them are single ones.
Let's get them too.

Sure, Tonight will Raise PR

All done !


MySQL gone during install

Hi,
While battleing with my non dockerized install, I decided to go the docker way to test anyway.
Installed clean VM (Ubuntu 20.04 server), docker and all dependendies (for you rinfo a lot of your support documentation is in German which makes it a bit complicated for non german speaker, but thanks to google), It all went well till the last part of the process where username and password are created, the app:first-run process were I got this:
 ! [NOTE] Accommodation prepared.

 ! [NOTE] Customers prepared.

08:48:06 CRITICAL  [console] Error thrown while running command "app:first-run". Message: "SQLSTATE[HY000]: General error: 2006 MySQL server has gone away" ["exception" => PDOException { …},"command" => "app:first-run","message" => "SQLSTATE[HY000]: General error: 2006 MySQL server has gone away"]

In Connection.php line 113:

  SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

app:first-run

   > loading App\DataFixtures\TemplatesFixtures
Do you want to load some initial test data into the application? (yes/no) [no]:yes

   > loading App\DataFixtures\SettingsFixtures
08:48:18 CRITICAL  [console] Error thrown while running command "doctrine:fixtures:load --append --group settings --group customer --group reservation --group invoices". Message: "App\DataFixtures\SettingsFixtures::createRooms(): Argument #3 ($subsidiary) must be of type App\Entity\Subsidiary, null given, called in /var/www/html/fewohbee/src/DataFixtures/SettingsFixtures.php on line 49" ["exception" => TypeError { …},"command" => "doctrine:fixtures:load --append --group settings --group customer --group reservation --group invoices","message" => "App\DataFixtures\SettingsFixtures::createRooms(): Argument #3 ($subsidiary) must be of type App\Entity\Subsidiary, null given, called in /var/www/html/fewohbee/src/DataFixtures/SettingsFixtures.php on line 49"]

In SettingsFixtures.php line 86:

  App\DataFixtures\SettingsFixtures::createRooms(): Argument #3 ($subsidiary)
   must be of type App\Entity\Subsidiary, null given, called in /var/www/html
  /fewohbee/src/DataFixtures/SettingsFixtures.php on line 49

doctrine:fixtures:load [--append] [--group GROUP] [--em EM] [--purger PURGER] [--purge-exclusions PURGE-EXCLUSIONS] [--shard SHARD] [--purge-with-truncate]

done

Looks like the SQL install went wrong somewhere. But since it is within docker, I have no idea how to access it (docker not being my thing... that's why I am still trying the normal install way).
I tried to rerun the install process, but I was told setup was completed...
But although the SQL part is not there, the install finished and you can actually call the application through the browser. Can't connect -> user and password unknown (due to the previous error I guess). So almost there.
Can you direct me through the correcting steps ? And maybe fix what's wrong in the install process (if it was not my fault).
Thanks

hi @dom-madrid,
I'm sorry that you are facing some issues in order to use the tool.
And you are right documentation needs to be improved somehow.
Since I've never encountered this issue before we need to make sure that every prerequisite is met.
Have you installed docker for the correct architecture? (arm64, x86, ...)
My documentation here https://github.com/developeregrem/fewohbee/wiki/Docker-Setup is for debian and arm64. According to my documentation please make sure to choose the guide for your architecture and OS. For ubuntu it will be this one here: https://docs.docker.com/engine/install/ubuntu/
If this is correct go to the folder where you cloned the fewohbee files into it and run (reset fewohbee installation):
  ./cleanup.sh
  rm .env

(maybe with sudo)
and execute the install script again
sudo ./install.sh
Afterwards make sure that all containers are running by executing
docker ps
... and take a look at the "status" column. Everything needs to be "up".
You can also take a look at the log of a container by executing (e.g. for the db container)
docker-compose logs db
If you want to go inside the container you can run
docker-compose exec db /bin/sh
BTW: Have you tried my short Howto for non-dockerized installations here: https://github.com/developeregrem/fewohbee/wiki/LAMP-Stack:-Apache,-MySQL,-PHP-(Ubuntu-22) ?

I assume your problem is solved. Therefore the issue will be closed.


Formalize how trees are parsed with respect of their children

This is my reply to the comment about exhaustivity of parenthesis parsing: https://github.com/scalameta/scalameta/pull/1489#issuecomment-380499309.

@densh any clues what is wrong here: https://travis-ci.org/scalameta/scalameta/jobs/367107521#L2544 ?

@olafurpg CI is green, comments addressed.


SPP-10158-add-guidance-on-gpg-keys

Description
When we set up GPG Keys/ Signed commits for the sml-catalogue repo, we encountered some recurring issues that needed some troubleshooting. This PR is meant to document the issues and how to troubleshoot them by adding a confluence page and updating the readme accordingly.
Code has not been commented because it is not necessary for this PR.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Technical Enhancements

Checklist:
If any of these are not completed, please explain why in the notes.
Definition of Done
Code and merges

[ ] Code to be commented on where applicable
[x] Documentation updated where required
[x] Have considered non-functional requirements such as Security, Performance, Scalability, and Fault Tolerance
[x] I have linted the code

Testing

[x] All levels of acceptance test are passing (automated, integration, manual, accessibility, etc.)
[x] I have run the behave command to check the selenium behaviour tests pass locally
[x] Acceptance criteria met

Other Checks

[x] I have performed a self-review of my own code
[x] I have checked for spelling errors
[ ] I have commented on my code, particularly in hard-to-understand areas
[x] My changes don't break anything unexpected
[x] I have checked and updated the security.txt file where required
[x] Up to date with the main branch

DEPLOY_URL=https://d14d91vv2l3snb.cloudfront.net/
cloudfront_id=E1HPNT9B0UF383


Add ISO8601 tests, initialize and formatter for InternetDateTimeExtended.

In TestDateInRegion+Formatter.swift
I added formatter test for ISO8601 InternetDateTimeExtended.

In TestDateInRegion+Formatter.swift
I added initializing test for ISO8601 InternetDateTimeExtended with Z and Timezone.

Thank you very much, tests are always welcomed!


db_owner role must use the database diagramming functionality

How can I enable this role to see my DB diagrams?

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

ID: 3ead09d9-3e51-04ce-dc6e-ac9bb59816ec
Version Independent ID: 94d19f8d-3c5e-8ed9-53ee-4b6173f49144
Content: Use SQL to query data (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/dataverse-sql-query.md
Service: powerapps
GitHub Login: @mayadumesh
Microsoft Alias: pehecke

@ugreg
Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Create a canonical technical tutorial

The Zero-to-DApp tutorial introduces users to our App Mining program. We have several individual tutorials that illustrate our features in isolation in simple apps.
We wanted an application that illustrates and explains our technical features. The sample should have a compelling story the makes it memorable. It should include a viral / social component.
cc: @jeffdomke @diwakergupta

@shreyasthiagaraj I've added you here. I think in all likelihood, I'm going to ask you to review the written tutorial. But, if you see something else you want to jump on, let me know.  For example, it would be super cool to have whatever our final code is in React also be implemented in an iOS application --- here is it on mobile vs web --- that is the idea.


doppler: 3.52.1 -> 3.53.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dopplerhq/cli/releases.
meta.description for doppler is: The official CLI for interacting with your Doppler Enclave secrets and configuration
meta.homepage for doppler is: https://doppler.com
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.53.0 with grep in /nix/store/lknxr2lpi6xzq9zf7j0q9jmqc4bdf50j-doppler-3.53.0
found 3.53.0 in filename of file in /nix/store/lknxr2lpi6xzq9zf7j0q9jmqc4bdf50j-doppler-3.53.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
doppler

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lknxr2lpi6xzq9zf7j0q9jmqc4bdf50j-doppler-3.53.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A doppler https://github.com/r-ryantm/nixpkgs/archive/dc784f5c93b7206bfdde0dc938c37e3a84dbd62e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lknxr2lpi6xzq9zf7j0q9jmqc4bdf50j-doppler-3.53.0
ls -la /nix/store/lknxr2lpi6xzq9zf7j0q9jmqc4bdf50j-doppler-3.53.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

doppler

Maintainer pings
cc @lucperkins for testing.

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

1 package built:

doppler


Only methods returning a Task<Operation<T>> are being instrumented automatically

The InstrumentResultInterceptor is only automatically intercepting and proxying methods that return a Task<Operation<T>>. This was discovered when async tests were completing in tends of milliseconds, while sync tests were taking seconds. For the Conversations SDK, that triggered the 5s local playback error.
To work around this we can manually instrument, but it'd be nice if this was automatic so we didn't have to condition code to instrument.

This is specific to SyncOnly tests. Most tests are written as async and will have their operations instrumented here. The UseSyncMethodsInterceptor runs after this to handle running the sync variant of tests. The operation instrumentation doesn't work for SyncOnly tests because the operation method doesn't return a Task.

IIRC, you had a reason why this wouldn't work but I wanted to ask it again here for posterity, but would it not be as easy as switching the order of the interceptors for instrumenting async operations (to bifurcate sync and async) and the one to instrument operations based on method signature?

I tried it, and it's not quite so simple as reversing the order. Some changes to the flow and method name calculation in the UseSyncMethodIntercepter got me further, but it's clear this is going to require more thought and careful evaluation. I have a scenario where this would be handy, but will just work around this for now by using WaitUntil.Started in non-SNIPPET code and disable recordings while I wait - perhaps something akin to what @m-nash suggested in Azure/azure-sdk-tools#2703.

@heaths do you think there is value in exploring a solution here?

Yes. For sync-only tests that use LROs, we need a way to make sure they are runnable.


CloudFront Spec bug(s)

While working on the Allowed Values for CloudFront I'm hitting some doc/spec issues:

LambdaFunctionAssociation's LambdaFunctionARN not required.

  CloudFrontDistribution:
    Type: AWS::CloudFront::Distribution
    Properties:
      DistributionConfig:
        CustomErrorResponses:
          - ErrorCode: 504 # Valid AllowedValue
            ResponseCode: 414 # Valid AllowedValue
            ResponsePagePath: "/404-errors/403-forbidden.html"
        CacheBehaviors:
          - ForwardedValues:
              QueryString: False
            LambdaFunctionAssociations:
              - EventType: "viewer-request" # Valid AllowedValue
            PathPattern: "images/*.jpg"

Results in:
1 validation error detected: Value null at
'distributionConfigWithTags.distributionConfig.cacheBehaviors.items.1.member.lambdaFunctionAssociations.items.1.member.lambdaFunctionARN'
failed to satisfy constraint: Member must not be null
 (Service: AmazonCloudFront; Status Code: 400; Error Code: MalformedXML; Request ID)

API doumentation: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_LambdaFunctionAssociation.html
Cfn documentation: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-lambdafunctionassociation.html#cfn-cloudfront-distribution-lambdafunctionassociation-lambdafunctionarn

Looks like one for me to take internally and look into.

@rjlohan We can patch this for now if needed/wanted BTW... What do you say?

What's the solution for me here? There's no way to provide lambda_function_arn via cdk.

@Arvanaghi what issue are you running into? If you don't specify any LambdaFunctionAssociations, you don't have to specify a lambda arn, and both cfn-lint and CloudFormation should behave correctly


az repos list hangs

This is autogenerated. Please review and update as needed.
Describe the bug
hangs, doesn't work
cyl@diamat:~/LSG-linux-yocto$ az repos list --verbose
^Ccommand ran in 3802.346 seconds.
Command Name
az repos list Extension Name: azure-devops. Version: 0.17.0.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az repos list --verbose

Expected Behavior
Environment Summary
Linux-5.0.0-37-generic-x86_64-with-debian-buster-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.80

Extensions:
azure-devops 0.17.0

Additional Context

@ironyman
The command works for me so the issue is definitely limited to the environment/organization. Please help me with the answers below to troubleshoot -

Is this consistently reproducible behavior or it happened one time?
Is the command hang issue limited to az repos list command or is it across other az repos/az devops/az commands?

Can you run the command with the issue in debug mode and share the output (run with --debug flag)?
This will help in figuring out where the command was stuck.

It did happen everytime I ran it. But az repos list is working now. I signed out and signed in and deleted some stuff. Can't quite remember everything I did.
But this is hanging
echo $USERPAT | az devops login --organization https://msazure.visualstudio.com --verbose --debug

This happens everytime.
azext_devops.devops_sdk.client : Api version '5.0-preview.1'
azext_devops.devops_sdk.client : GET https://msazure.visualstudio.com/_apis/ConnectionData
azext_devops.devops_sdk.client : Request content: None
msrest.universal_http : Configuring redirects: allow=True, max=30
msrest.universal_http : Configuring request: timeout=100, verify=True, cert=None
msrest.universal_http : Configuring proxies: ''
msrest.universal_http : Evaluate proxies against ENV settings: True
urllib3.connectionpool : Starting new HTTPS connection (1): msazure.visualstudio.com:443
urllib3.connectionpool : https://msazure.visualstudio.com:443 "GET /_apis/ConnectionData HTTP/1.1" 200 694
azext_devops.devops_sdk.client : Response content: b'{"authenticatedUser": censored
keyring.backend : Loading KWallet
keyring.backend : Loading SecretService
keyring.backend : Loading Windows
keyring.backend : Loading chainer
keyring.backend : Loading macOS
Keyring backend : keyring.backends.SecretService.Keyring (priority: 5)

hangs there
I have a stack trace at that point
File "/opt/az/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/az/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/__main__.py", line 49, in <module>
    exit_code = cli_main(az_cli, sys.argv[1:])
  File "/opt/az/lib/python3.6/site-packages/azure/cli/__main__.py", line 38, in cli_main
    return cli.invoke(args)
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 601, in execute
    results, exceptions = self._run_jobs_serially(jobs, ids)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 666, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 636, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 306, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 493, in default_command_handler
    return op(**command_args)
  File "/home/cyl/.azure/cliextensions/azure-devops/azext_devops/dev/team/credentials.py", line 31, in credential_set
    set_credential(organization=organization, token=token)
  File "/home/cyl/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 33, in set_credential
    cred_store.set_password(key, token)
  File "/home/cyl/.azure/cliextensions/azure-devops/azext_devops/dev/common/credential_store.py", line 31, in set_password
    old_token = keyring.get_password(key, self._USERNAME)
  File "/home/cyl/.azure/cliextensions/azure-devops/keyring/core.py", line 57, in get_password
    return _keyring_backend.get_password(service_name, username)
  File "/home/cyl/.azure/cliextensions/azure-devops/keyring/backends/SecretService.py", line 64, in get_password
    collection = self.get_preferred_collection()
  File "/home/cyl/.azure/cliextensions/azure-devops/keyring/backends/SecretService.py", line 56, in get_preferred_collection
    collection.unlock()
  File "/home/cyl/.azure/cliextensions/azure-devops/secretstorage/collection.py", line 67, in unlock
    return unlock_objects(self.connection, [self.collection_path])
  File "/home/cyl/.azure/cliextensions/azure-devops/secretstorage/util.py", line 154, in unlock_objects
    dismissed, (signature, unlocked) = exec_prompt(connection, prompt)
  File "/home/cyl/.azure/cliextensions/azure-devops/secretstorage/util.py", line 140, in exec_prompt
    connection.recv_messages()
  File "/home/cyl/.azure/cliextensions/azure-devops/jeepney/integrate/blocking.py", line 62, in recv_messages
    b = self.sock.recv(4096)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/__main__.py", line 21, in quit_handler
    traceback.print_stack()

I reported a similar issue:
https://github.com/Azure/azure-devops-cli-extension/issues/948
I worked around it by installing version 0.12.0 of the extension. Does that work for you?

Hi @ironyman ,
Are you running this command interactively or within a script?

echo $USERPAT | az devops login --organization https://msazure.visualstudio.com --verbose --debug

If not, can you try running the command interactively?
Also, is there a prompt to enter password for SecureStorage?
Or any other warning or error?

It was failing in a script and I ran it interactively when I tried to debug it. There as no prompt. I was running it in an ssh session. That's the full output no other error.
I tried running it again and it logged in successfully with this error message
keyring.backend : Loading KWallet
keyring.backend : Loading SecretService
keyring.backend : Loading Windows
keyring.backend : Loading chainer
keyring.backend : Loading macOS
Keyring backend : keyring.backends.SecretService.Keyring (priority: 5)
Failed to store PAT using keyring; falling back to file storage.
You can clear the stored credential by running az devops logout.
Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
Keyring failed. ERROR :Failed to unlock the collection!
Storing credentials in the file: /home/cyl/.azure/azuredevops/personalAccessTokens
Another organization is already set as default.
Event: CommandInvoker.OnTransformResult [<function _resource_group_transform at 0x7fbed61ff8c8>, <function _x509_from_base64_to_hex_transform at 0x7fbed61ff950>]
Event: CommandInvoker.OnFilterResult []
Event: Cli.PostExecute []
az_command_data_logger : exit code: 0
telemetry.save : Save telemetry record of length 2564 in cache
telemetry.check : Negative: The /home/cyl/.azure/telemetry.txt was modified at 2020-03-18 16:50:51.857824, which in less than 600.000000 s
command ran in 0.636 seconds.

but it logged in and other commands work. Not sure what happened but it works now. I did do apt update recently so maybe one of those keyring libs were borked and they fixed it.

@ironyman ,
As you can see from the when logs and the warning, when keyring fails we fallback to filestorage for linux.

Keyring backend : keyring.backends.SecretService.Keyring (priority: 5)
Failed to store PAT using keyring; falling back to file storage.
You can clear the stored credential by running az devops logout.
Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
Keyring failed. ERROR :Failed to unlock the collection!

If you can fix the Secret storage on your system, do az devops logout and then login again, you will be able to store the credentials in your secure storage now. Check this issue.
Otherwise it will just continue using filestorage.
Another option is to create environment variable named AZURE_DEVOPS_EXT_PAT and store your PAT in environment variable.

@ironyman
You are still facing this?
or shall we close this bug?

It is not happening anymore and we are closing this
If you are facing this issue feel free to re-open it


Filter messages by their origin instead of using a list of filtered ID's

This should prevent the message filter slice slowly growing for every message that is sent on the bus.
Resolves #86

@jpcoenen Thank you for filing this! I will take a look.

I can't replicate the failing test locally. @cohix Any chance we can run it again?

Hey Connor 👋 I see this repo has been deprecated. Can you tell me what that means for this MR?

@jpcoenen I just wanted to check in here to see if I can help with anything.


Add BaseProfile class to store profile information and fits

To be subclassed for surface brightness, density, stacked profile etc.

This has been added with basic functionality.


Translation inside feature modules

So I'm trying to make the translation to work globally, but I don't seem to get how it works. It might be my lack of understanding of how modules/services in Angular 2 work. Following the guide here I have the following setup right now:
  bootstrap: [AppComponent],
  declarations: [
    AppComponent,
    HomeComponent
  ],
  imports: [
    LocaleModule.forRoot(), // New instance of LocaleService.
    LocalizationModule.forRoot(), // New instance of LocalizationService.
    CoreModule,
    CoursesModule
    ....
  ],
})
export class AppModule {}

And my AppComponent:
@Component({
  selector: 'app',
  encapsulation: ViewEncapsulation.None,
  styleUrls: ['./app.component.scss'],
  templateUrl: './app.component.html'
})
export class AppComponent extends Locale implements OnInit {

  constructor(
    public appState: AppState,
    public locale: LocaleService,
    public localization: LocalizationService
  ) {
    super(locale, localization);

    this.locale.addLanguages(['en', 'es']);
    this.locale.definePreferredLocale('en', 'US', 30);
    this.locale.definePreferredCurrency('USD');
    this.localization.translationProvider('/locale/locale-');
    this.localization.updateTranslation();
  }
}

And then in my CoursesComponent, I have set it as the guide for Lazy routing:
@NgModule({
    imports: [
        ...
        LocaleModule, // LocaleService is singleton.
        LocalizationModule.forChild() // New instance of LocalizationService.
    ],
    declarations: [CoursesComponent]
})

The translation works in my HomeComponent, but not in my CoursesComponent. What's weird is that if I import LocalizationModule only and not LocalizationModule.forChild(), translation works. Does that mean that it is creating an instance for the first time and the instance created from AppModule is not injected inside CoursesModule? Do I need to export the service through the CoreModule? I'm confused, any help is appreciated!

If you are using lazy loaded modules with the router, there are two scenarios:

You want to use the same translation files for the whole application.

You must not call the forChild method, because it creates a new instance of the service. So you have to use:
    imports: [
        ...
        LocaleModule, // LocaleService is singleton.
        LocalizationModule // LocalizationService is singleton.
    ]

You want to use different translation files for each module.

You must call the forChild method:
    imports: [
        ...
        LocaleModule, // LocaleService is singleton.
        LocalizationModule.forChild() // New instance of LocalizationService.
    ]

But you have to reinitialize LocalizationService with new providers, as explained here: https://github.com/robisim74/angular2localization/blob/master/doc/spec.md#5
Also the List module/component of the sample app is built in this way: https://github.com/robisim74/angular2localization/tree/gh-pages

Thanks for the quick response. I have been trying to do the first option you mentionted and I don't seem to get it to work. I have moved the modules to my CoreModule and have created a HomeModule for my HomeComponent. This should allow it to use any services from the CoreModule, right? This is my CoreModule:
imports...

@NgModule({
  imports: [
    SharedModule,
    RouterModule,
    LocaleModule, //  LocaleService is singleton.
    LocalizationModule, // LocalizationService is singleton.
  ],
  declarations: [],
  exports: [],
  providers: [
    UserService,
    LocaleService,
    LocalizationService
  ]
})

export class CoreModule {}

My AppComponent is the same. So, shouldn't LocalService and LocalizationService be available everywhere? Right now, my Home page is not getting translated, unless I import  the LocaleModule and LocalizationModule. Is this how it works and must I import these modules in every feature module or am I doing something wrong elsewhere?

Sorry, but I don't understand what you are trying to do. However: for the first option, in the AppModule you have to use:
  imports: [
    LocaleModule.forRoot(), // New instance of LocaleService.
    LocalizationModule.forRoot(), // New instance of LocalizationService.
    ....
  ],

so you create the new instances of the services.
In all the other sub-modules, you have to use:
    imports: [
        ...
        LocaleModule, // LocaleService is singleton.
        LocalizationModule // LocalizationService is singleton.
    ]

and remove from the providers:
    LocaleService,
    LocalizationService

otherwise you create other instances.

Sorry, but I don't understand what you are trying to do.
Neither do I, lol! Anyway, I've been doing it wrong, thanks for your help, everything is clear to me now and it works. I just couldn't comprehend how it all works I guess. Thanks a lot for the help!

You'll never know until you try... :)

@Shiroh1ge  I'm closing this issue. If you need, open a new issue. Greetings


but my connection string comes from api in multi tenant app and multiple database

Type of issue
Typo
Description
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
var tenant = _tenantService.Tenant;
var connectionStr = _configuration.GetConnectionString(tenant);
optionsBuilder.UseSqlite(connectionStr);
}
this is microsoft documentation
but my connection string comes from api
Page URL
https://learn.microsoft.com/en-us/ef/core/miscellaneous/multitenancy
Content source URL
https://github.com/dotnet/EntityFramework.Docs/blob/main/entity-framework/core/miscellaneous/multitenancy.md
Document Version Independent Id
bb29a2b6-c401-287f-2da9-1aeb3c633b41
Article author
@JeremyLikness

@NarenderDhamarlapally this is just a code sample showing one scenario; it's up to you to adjust the code to get the connection string for your tenant in whatever way is needed in your own application.


Refactor dispatcher's getting next consumer with consumer priority

Motivation
Refactoring #364 to have simplicity in finding next-available consumer at dispatcher by considering consumer-priority level.
Result
No functional change.

@merlimat can you review it when you get a chance as thinking to pick this one over #364


Notifications and other popups are treated like "normal" windows on Plasma Wayland

Describe the bug
When running Plasma Wayland,  notifications and krunner pop-downs are treated like first-class windows and therefore take focus and appear in the task manager.
This used to be an issue back in the day (https://bugs.kde.org/show_bug.cgi?id=365107) so this is in all likelyhood something we do (wrong) on our side.
To Reproduce
Steps to reproduce the behavior:

follow the steps in https://github.com/NixOS/nixpkgs/pull/117102 to get wayland running
log in to the plasma wayland session
wait for a notification or trigger krunner
observe the focus steal (for notifications) and appearance in the task manager

Expected behavior
Notifications and similar should not be treated as a regular window and therefore not show in task manager or receive focus (krunner should still have focus of course).
Notify maintainers
Cc: @NixOS/qt-kde
Metadata

system: "x86_64-linux"
host os: Linux 5.11.11, NixOS, 21.05.git.d3ff65233f9M (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre20210326_dd77f71
channels(root): ""
channels(peter): ""
nixpkgs: /nix/store/w9zhp284bnx3f1ma6mdbsw008jpnq15v-nixpkgs_unstable

References:

https://github.com/NixOS/nixpkgs/pull/117102

https://bugs.kde.org/show_bug.cgi?id=435415

Oh, my intuition tells me this could be the root cause of the totally-wonky Plasma Mobile notifications.

@samueldr - I found this: https://community.kde.org/Plasma/Notifications#DesktopEntry_in_notifyrc
I haven't looked through the code yet (I'm not at all familiar with the plasma code) but it sure sounds like there is a disconnect between kwin, application and desktop file.

However, KNotifications uses the application name for identification rather than the desktop entry, so a DesktopEntry hint must be placed in the respective notifyrc file, so they can be filed under "applications".

I don't think this is relevant to the "rendering" bits of the notifications. I'm not an expert either, but to me this sounds like it is concerned with the communication between apps and the daemon.
BUT, "However, KNotifications uses the application name for identification rather than the desktop entry" is possibly a similar issue to the one we're having. But it's likely to be something concerning the kwin/KNotifications relationship, rather than KNotifications/app relationship.

The bug @peterhoeg links says that the bug was fixed by these git commit back in the day:
https://invent.kde.org/plasma/kwin/-/commit/c81d8204f9a3a9fc806fedf7a8bb915dc19a7892
https://invent.kde.org/guokaka/kwayland/-/commit/2f4cb0613b1c31ef3a32d6a7d47dbf484e2b85ef
https://invent.kde.org/plasma/kwayland-integration/-/commit/fdb09dc29a3d628a0c64db1ec5eba613d8728b52

So I've followed the instructions given to @peterhoeg in the 2nd bug report
Here are the properties of a notification window on Wayland:

And here the same on X:

Of note:Entire window class is plasmashell-wrapped.org.kde.plasmashell on Wayland, plasmashell.plasmashell on X
SImilarly windows type is Normal window on Wayland, and apparently empty on X

plasmashell-wrapped

I would bet this is the issue.

@samueldr where do you think we shpuld look specifically?

My hunch is some special casing in kwin. I still haven't taken the time to look into that. That should be the first thing I do when I resume work on the PR monday, since that's a good clue.

@samueldr any news?

(All looked at under Plasma Mobile...)
My current line of thoughts is that the window role is lost for some reason. This is supported by your previous screenshots, and my testing under Plasma Mobile shows me the same issue where window type is Normal.
AFAICT this condition is never true:

https://invent.kde.org/plasma/kwin/-/blob/98424da878e69048eaf1ca8a097fdc44d8090392/xdgshellclient.cpp#L927-930

But if I force any m_plasmaShellSurface clients to not accept focus, while it breaks some things, the notification does stop taking over the focus.
--- a/xdgshellclient.cpp
+++ b/xdgshellclient.cpp
@@ -926,6 +926,7 @@ bool XdgToplevelClient::acceptsFocus() const
         }
         if (m_plasmaShellSurface->role() == PlasmaShellSurfaceInterface::Role::Notification ||
             m_plasmaShellSurface->role() == PlasmaShellSurfaceInterface::Role::CriticalNotification) {
+       return false;
             return m_plasmaShellSurface->panelTakesFocus();
         }
     }

This is not a solution, far from it. I simply don't know how to debug this kind of issues, and am learning along the way how all of this is setup within kwin, plasma, and friends.
This also does not affect the window sizing in Plasma Mobile, but it changes something for sure since it won't put the notification halfway off-screen.
I would assume if the window never lost it

Can I trouble you to report your findings on the KDE bug tracker? I'm sure the guys over there are able to help.

I suspect https://github.com/NixOS/nixpkgs/issues/107595 is connected

@peterhoeg I don't have much confidence in my findings.
Reading through kwin's and plasma-* and kwayland* projects a bit hapazardly I found out that maybe it's totally expected that window roles are normal under wayland. Though I'm not confident either in those findings.

@pasqui23 AFAIK this patch solved that.

Looks like I'm stabbing in the dark, at random, and only hitting irrelevant bits. I'd need a KDE/Plasma person to take a better look at that. It is exhausting to look into, since I'm mostly learning everything from scratch on the spot.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/plasma-wayland-session-not-available-from-sddm/13447/3

Not yet fixed in 5.22

However I have also installed Grid WM and I found that the spectacle window got managed by Grid when on X11 it was not, and the window for unlocking kwallet does not get positioned in the center as it does in X11.
Those put thogether suggest that somehow KWin thinks every window is a normal window.
Also the properties of a notification window on wayland

Also the Plasma entry in the tasks list shows up also on openin plasmoid menus like kickoff or the notification menu.
Also the sound menu is put in the top left instead of bottom center

Also also no clock widget

Ok how do we contact the KDE devs for guidance?

So here are the 3 commits that fixed this problem back in the day
https://invent.kde.org/frameworks/kwayland/-/commit/2f4cb0613b1c31ef3a32d6a7d47dbf484e2b85ef
https://invent.kde.org/plasma/kwin/-/commit/c81d8204f9a3a9fc806fedf7a8bb915dc19a7892
https://invent.kde.org/plasma/kwayland-integration/-/commit/fdb09dc29a3d628a0c64db1ec5eba613d8728b52
@samueldr This suggest that window roles are not expected to be "Normal" for notification,
especially since PlasmaShellSurfaceInterface::Private::setRole remain unchanged in master
https://invent.kde.org/frameworks/kwayland/-/blob/master/src/server/plasmashell_interface.cpp#L218

So controlling the window type on a notification turn out that on X11 is revealed as empty.
Follows wold,possibly incorrect speculation: this suggest that the Notification role somehow is broken and on X11 the broken role behaves like a notification but on Wayland it behaves like a normal window.

Devs, how can we, community, help to give some traction to this issue.
Judging by the complexity of the issue, will setting up a bounty through https://issuehunt.io/ help?

Most likely, it's not an issue about "traction" internal to Nixpkgs, but about talent knowledgeable in the intersection of [Kwin, Wayland, Nixpkgs packaging]. Most devs involved in this current discussion would be, I assume, knowledgeable with Nixpkgs packaging only.

Most likely, it's not an issue about "traction" internal to Nixpkgs, but about talent knowledgeable in the intersection of [Kwin, Wayland, Nixpkgs packaging]. Most devs involved in this current discussion would be, I assume, knowledgeable with Nixpkgs packaging only.

That's my understanding too hence I'm trying to be creative here. Can someone with the write access try connecting issuehunt.io to this repo and we'll give it a shot?

That's my understanding too hence I'm trying to be creative here. Can someone with the write access try connecting issuehunt.io to this repo and we'll give it a shot?

fyi there are bounty sites that dont need to be connected such as gitpay and bountysource
i have received a bounty via gitpay in https://github.com/NixOS/nixpkgs/issues/130590
and if needed the maintainer can help if there are issues @alexanmtz

@Artturin what sites you suggest?

I've edited bountrysource out of my comment because it appears that they've been acquired by a "by a blockchain company"
https://github.com/bountysource/core/issues/1539
So I suggest gitpay since it's dev is active

Ok I've put $50 on it on gitpay https://gitpay.me/#/task/535

Donate to help make it happen: https://gitpay.me/#/task/535

(trying to make it to sticking out)

Thanks, @Artturin for recommending Gitpay
And let me know if any of you have any issues, and all feedback will be appreciated 🙏

i have seen this issue app_id issue on other wayland programs where the app_id is binname-wrapped
im also experimenting with changing the wrapper to move the wrapped binaries to $out/.bin/binname instead of $out/bin/.binname-wrapped

added instructions to test to the pr

@Artturin It seems your fix is enough for plasmashell (notifications, this issue), but this mismatch between appIds caused by the wrappers seems likely to cause issues with any other wrapped GUI app on plasma wayland. Would there be a generic fix to ensure any wrapped app keeps its correct app_id?

im looking in to it

im also experimenting with changing the wrapper to move the wrapped binaries to $out/.bin/binname instead of $out/bin/.binname-wrapped. however that will require larger changes

Seems like setting orgDomain/desktopFileName explicitly via QApplication.{setOrganizationDomain/setDesktopFileName} for plasmashell fixes this issue too, but i will try to implement this fix via patching unwrapping file name in qt itself, to make it work for every qtwayland app

This issue is not caused by app_id, but something else
PR #139459 fixes app_id, but this issue is still present

Seems like this issue is in plasmashell itself, i can see this via WAYLAND_DEBUG=1
[1470662.098]  -> org_kde_plasma_surface@28.set_role(1)
[1470662.128]  -> org_kde_plasma_surface@28.set_role(1)
[1470884.175]  -> org_kde_plasma_surface@28.set_role(1) -- panels
[1500945.930]  -> org_kde_plasma_surface@39.set_role(2)
[1501766.760]  -> org_kde_plasma_surface@39.set_role(2) -- desktop

But no other surface created by plasmashell receives role

kwayland-integration kwindowsystem plugin is responsible for this (It provides plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so), but just adding it to systemPackages doesn't help, because kwindowsystem is patched to be pure, and only load plugins from itself: https://github.com/NixOS/nixpkgs/blob/nixos-21.05/pkgs/development/libraries/kde-frameworks/kwindowsystem/0001-platform-plugins-path.patch#L32 (QT_PLUGIN_PATH is defined at build time)
We also can't just add kwayland-integration to its path, as this package itself depends on kwindowsystem
The only way i see here - make kwindowsystem plugin loading impure (by removing this patch), and rely on existing QT_PLUGIN_PATH being set here: https://github.com/NixOS/nixpkgs/blob/nixos-21.05/nixos/modules/services/x11/display-managers/sddm.nix#L209

Starting session via startplasma-wayland with #139459 and #139537 applied on top of 39b5332bd1065fc5bc4446b2a7062ebea9e0a4e5 fixes this issue

(Tangentially related, I'll be trying with the plasma-mobile PR tomorrow. Hopefully this is what fixes the issues there too.)

@CertainLach do you have a good enough mental model of what is happening to know if, instead of (ab)using the environment through tons of wrappers, we'd instead allow loading Qt plugins for all dependencies intrinsically regardless of the environment?
Note that I'm not talking about "unwrapping" the name of /proc/self/exe. I'm talking about the general idea of making Qt aware of library paths through a declarative and pure (enough?) method that does not rely on an unreliable method like the environment and wrappers.
I still think that using wrappers and the environment is the worst misfeature in NixOS integration we're still doing.

If the wrapper magic is the problem, I wonder if the "proper" solution would also make screensharing/recording via pipewire, ssh-agent and fcitx (and presumably other IMEs) finally work on wayland as well.

@jansol unlikely that it alone would be the fix, but it might be part of making things easier.
It seems that their design for Wayland application "authentication" relies, among other things, on looking at the application names (from /proc/self/exe), finding either the desktop file or dbus description for said app. This is where "unwrapping" is currently needed. Without unwrapping, either directly the application name is wrong, or the desktop file / dbus files for .$app-wrapped don't exist.
Then there's the possibility that ".so" Qt plugins aren't found if a wrapper is missing or misconfigured. Though that one is less likely to be an issue, assuming the wrappers are configured.
It's possible every service needs to be tracked down to their hardcoded special casing in the different Wayland components to know for sure how they work.

@CertainLach's fixes works for Plasma Mobile!
 :computer::camera: Screenshot

@samueldr

we'd instead allow loading Qt plugins for all dependencies intrinsically regardless of the environment?

I agree with that qt wrapping is a mess, but i see the better story with qt plugins much as something like:

Patch qt to load plugins from something like /run/current-system/<current derivation hash>/ (I.e /nix/store/aabbcc-kwindowsystem would load plugins from /run/current-system/aabbcc-kwindowsystem)
Add nixos module to define plugin directories:

enviroment.qtPlugins = {
  "${pkgs.kwindowsystem}" = [
    pkgs.kwayland-integration
  ];
};

This way it would be explicit, and pure enough to not break things with errorously loaded plugins

I agree with that qt wrapping is a mess, but i see the better story with qt plugins much as something like:
* Patch qt to load plugins from something like `/run/current-system/<current derivation hash>/` (I.e `/nix/store/aabbcc-kwindowsystem` would load plugins from `/run/current-system/aabbcc-kwindowsystem`)

* Add nixos module to define plugin directories:

Breaks on non-NixOS systems, user profiles or nix-shell.

This way it would be explicit, and pure enough to not break things with errorously loaded plugins

The way I implemented in that old PR was pure from the inputs of a given derivation, while still staying compatible with the less pure automatic loading of plugins from profile directories that is already in use.

Reopening; I think it also requires #139459, though I never tested for myself.

#139459 doesn't required for this fix, but it fixes other possible problems, i.e kwin has some plugins with hardcoded app_ids, i.e glide uses this to blacklist animation on shell surfaces

Huge thanks for fixing this!
Can someone else confirm it solves the problem for them? (we need to release the bounty :)

With #139537 applied running sleep 10; notify-send "foo" in a terminal does indeed no longer steals focus from typing this comment in my browser. The notification also doesn't show up in the task manager.

I can also confirm several other plasma wayland issues I was experiencing got fixed by #139537 :

blur on plasmoids, panel, yakuake/konsole are working again; before, I was only getting normal transparency and no blur
some other plasmoids popups besides notifications were also stealing focus and having an entry on taskbar, including launcher
volume/brightness HUD were also stealing focus, and were always localized on the top-left corner of the screen; they now appear in the center, as on X11

@CertainLach can you please submit your PR that fixed this at the bounty page as a solution (to claim the bounty)?

I tried to do that before, but "The issue is closed on GitHub" check is missing, i though there is some confirmation required from issue creator


Test publish

Sadly I think there's a much less complicated way to get publishable data into the API:
      - run:
          name: Create dev dandiset
          command: python manage.py migrate && python manage.py createsuperuser ... && python manage.py create_dev_dandiset --owner<EMAIL_ADDRESS>          working_directory: dandi-api
          environment:
            DJANGO_DATABASE_URL: postgres://postgres:postgres@localhost:5432/django

Then the test can just log in with the new super user credentials and they should be able to click publish on dandiset 000001 immediately.

I thought about doing this but ran into some issues:

How would we run this locally? (maybe the answer is we don't run these types of tests locally? or we could make the user run that management command before running the tests I suppose)
We can't guarentee that the test dandiset has an id of 000001 because the other tests also create dandisets, and there's no way to control the order that tests are executed in Jest

We could do some tricks with environment variables to tell the tests which dandiset is the test dandiset, but this limits us to just this one set of assets (see next bullet point)

I think it'd be nice to have a test_data directory where we can have different types of assets (invalid assets, assets with large directory depths as mentioned in https://github.com/dandi/dandiarchive/issues/728, etc.) that can be used in testing.

Maybe the answer to this is that it's not worth pursuing these kind of tests

Good point. We could perhaps augment the script to specify a dandiset ID to replace if it already exists, but the test user is a slightly trickier proposition. Perhaps a new command setup_test_data that destructively builds a test environment would be better?
I think in this case it would be guaranteed to be 000001, because that step is run before the tests begin executing. This would also be solved by a destructive setup_test_data script.
Agreed, we need some kind of facility for providing data of various flavors. Right now the create_dev_dandiset script uses gibberish as the asset contents, but I think some kind of test_data could be used instead.

I think I'm talking myself into a setup_test_data command that destroys any existing conflicting data and ensures that some body of test data is always present. It would be run before the integration test in CI and devs would have to run it before running integration tests to ensure the environment is ripe for testing.
It would mean that we can't run the test suite in prod/staging, although I think it's better to be able to run it on demand against an arbitrary branch.

Having a setup_test_data function would also work, but then we would need to designate certain dandisets as certain flavors. Like we would need to hardcode (or use env var) somewhere that dandiset 000001 is guaranteed to be a certain flavor, 00002 is another, etc. And this would have to be synchronized across two different repos, since the tests are in the dandiarchive repo and the setup_test_data command would be in the dandi-api repo.
The way I'm doing it in this PR introduces some complexity, but all of that complexity is wrapped in the uploadAssets() function. Thinking ahead, all the user has to do to add new assets is drop them in test_data (with some slight modifications to dandiset.yaml) and call uploadAssets() on it during the test. On the other hand if we used the setup_test_data function, adding new test data would require making an additional PR to dandi-api to modify the setup_test_data command. I'm seeing it as a tradeoff between

having a simpler way to add assets in testing that makes it more of a burden to add future tests
vs
having a more complex way to add assets in testing that makes it easier to add future tests

What do you think?

That is an excellent summation of the tradeoffs.
In general, I think that maintenance burden is the biggest obstacle to browser testing, since it's sort of like the cherry balanced on top of a house of cards. Anything that can reduce that burden is good.
I agree that the upload.sh method you have here makes it much easier to just drop a new asset in and add it as needed to only the tests that need it. It's nice that the test starts from a blank slate and explicitly sets up everything it needs right there. However, it involves a long pipeline of things that might break: fetching API key -> installing dandi-cli -> invoking a shell script -> invoking dandi-cli to upload the asset. There's also the bit about remembering to update dandiset.yml whenever a new asset is added, which is kinda hard to document and remember to do.
Additionally, this only solves uploading assets; as the app grows, we will need to provision more things and invent similar pipelines (admin users, zarr files, embargo'd dandisets, for example). The maintenance burden will only grow.
On the other hand, we have the setup_test_data solution. Basically, we would define "blank slate" to include some baseline of existing data. It has drawbacks, mostly that we have to separate the tests from the test data. It does suck to work with two repositories to set up test data. Maintaining the script itself will also be burdensome, as it will have to do some weird DB stuff, and it will presumably get bigger and more complicated as we add more tests and need more data. And resetting the DB prior to every run would involve an extra command before every yarn run test.
However, we would have the freedom to put the DB into any state that we wanted prior to the test running. Any simple test data (dandisets, new users, maybe metadata?) could be added through the UI, and we could save the script for the really gross, difficult data.
My value judgement leans toward setup_test_data as more maintainable long term.

incidentally setup_test_data would also resolve https://github.com/dandi/dandi-api/issues/495 by simply provisioning users with predefined names.

In general, I think that maintenance burden is the biggest obstacle to browser testing, since it's sort of like the cherry balanced on top of a house of cards. Anything that can reduce that burden is good.

Good analogy, can confirm after working on these tests the last few weeks :smile:

Additionally, this only solves uploading assets; as the app grows, we will need to provision more things and invent similar pipelines (admin users, zarr files, embargo'd dandisets, for example). The maintenance burden will only grow.
On the other hand, we have the setup_test_data solution. Basically, we would define "blank slate" to include some baseline of existing data. It has drawbacks, mostly that we have to separate the tests from the test data. It does suck to work with two repositories to set up test data. Maintaining the script itself will also be burdensome, as it will have to do some weird DB stuff, and it will presumably get bigger and more complicated as we add more tests and need more data. And resetting the DB prior to every run would involve an extra command before every yarn run test.

I spent some time thinking about this, and I agree with your setup_test_data solution.
I agree with your point about maintainability - the setup_test_data solution is guaranteed to continue working for any future features (embargo + others) since it's executing within Django, while the node execSync/dandi-cli method will probably have to be expanded or rewritten to accommodate changes to the upload process. We would also have to start worrying about changes to dandi-cli, especially since we're using dev-only options which I assume are subject to change.

However, we would have the freedom to put the DB into any state that we wanted prior to the test running.

Yeah I agree that this is huge, and would allow us to write more focused tests.
re: having to work across both repos, the E2E tests have access to the contents of the dandi-api repo prior to running, so we could maybe do some environment variable trickery to keep test data in the dandi-api repo and avoid having to keep it "synced" across both repos. Or maybe not, either way I'm okay with the setup_test_data solution.

@mvandenburgh are you planning on a new PR with the alternative test data scheme? If so there were some frontend fixes that could be cherrypicked out of this PR.

@mvandenburgh are you planning on a new PR with the alternative test data scheme? If so there were some frontend fixes that could be cherrypicked out of this PR.

Yes, I was planning on a new PR in dand-api for this. All of the frontend fixes here should also be present in the landing-page-redesign branch so I don't think we need to do anything here.


Add the ability to use out on Crystal methods and procs

Feature Request
Is your feature request related to a problem? Please describe clearly and concisely what is it.
Like Lib funs it would be great if we could use out keyword in parameters to methods and procs outside of Libs. Interfacing with COM classes in Windows requires that the VTable struct to contain fields that are Proc type and many of the methods have out direction on the params, the returned value being sucess or error code.
https://learn.microsoft.com/en-us/windows/win32/api/rometadataapi/nf-rometadataapi-imetadatatables-getcodedtokeninfo
Describe the feature you would like, optionally illustrated by examples, and how it will solve the above problem.
The feature would allow for methods and procs to be able to accept out for params.
Describe considered alternative solutions, and the reasons why you have not proposed them as a solution here.
Right now the only solution is to initialize pointers ahead of time and pass them as parameters.
Does it break backward compatibility, if yes then what's the migration path?
This feature should not affect backward compatibility.

Right now the only solution is to initialize pointers ahead of time and pass them as parameters.

No? You just return multiple values in a tuple or another structure and that's it

many of the methods have out direction on the params, the returned value being sucess or error code.

If you're making convenient wrappers for Crystal users, then dealing with separate numeric codes doesn't count as "convenient", you should change them into expressions or at least as a union type Result | ErrorCode.
If you're not making convenient wrappers, then just leave the fun as is and it can be used directly.
This will not be done, it greatly reduces obviousness of the language because you can't be sure anymore how a parameter will behave when you see one being passed.

Oh sorry, the last part that I wrote is wrong - there wouldn't be a surprise for the caller side if the out keyword is present there of course

Right now the only solution is to initialize pointers ahead of time and pass them as parameters.

No? You just return multiple values in a tuple or another structure and that's it

I would but the function pointer is created by the C/C++ library and it is not returning a tuple.

If you're not making convenient wrappers, then just leave the fun as is and it can be used directly.

It's not a fun being called but function pointers.

I see that you're dealing with function pointers and not necessarily even funs. In that case indeed you have to create the variable in advance and can't use out

it is not returning a tuple.

Yes but in your wrapper you can receive data this way, transform it and return a tuple

it is not returning a tuple.

Yes but in your wrapper you can receive data this way, transform it and return a tuple

Right, but creating those wrappers can be very time consuming to create with large libraries like Win32 API.

That should be automated then :/


Fix file name typos

Fixing typos in file names - nothing major, I believe...

@ldanielw1 Thanks. There are a couple more, but most of those files will be deleted by #57


Refactor Form component to accept nested functional components as its child component

Problems:

Form component can not process functional components when they're supplied as descendent components.
Form component traversing down the component tree from the child component passed to it and cloning each component in that tree. This approach is against the declarative nature of React, makes the code hard to read, and causes bugs like the one above.

Problem 1
When you pass nested functional components to Form as a child component, the Form component throws an error.
Example code:
<Form>
 <View>
  {() => <Text>Hello</Text>
 <View>
</Form>

tl;dr Reactc.cloneElement cannot accept a function {() => <Text>Hello</Text>} as its argument
Form recursively traverses its child component. During the recursive traversal, it clones each component it encounters and passes additional props related to Form state and Form state management. However, when an inline component (i.e. () => <>{() => <Text>Hello</Text>}</>) exists, cloning fails.
Problem 2
The component should not examine or modify other components directly. Doing so is against React's core concept of declarative programming. It also makes the user of Form more complicated and unexpected, causing an issue like the above.
What we need to do
We should refactor the Form component to use the Context API and custom hooks.

I'll check back on this. Maybe the issue has been already fixed as the component migration is going and at some point, some PR is going to encounter this issue


Allow observable.subscribe(var) when Owner available

I'd like to sync Observable into RxWriter/Observers:
// with implicit Owner in scope:
val number = Var(0)
Observable.intervalMillis(1000).subscribe(number)

Just to understand better: You mean, that subscribe on observables should take an implicit owner? I would not like to do that, I think the owner concept is good for the hot variables use-case, but not generally for observables.
You can easily just convert the observable to an Rx and work from there:
Rx.observableSync(Observable.intervalMillis(1000)).subscribe(number)

closed via https://github.com/cornerman/colibri/pull/271


npm package untar to not use remote-cache

It's pretty meaningless to use remote-cache for npm untar action. All npm packages are small in size I think?

If there's a few files in the tarball, untar would be instant anyway
If there's a lot of files in the barball, untar would be instant, but it takes long time to upload to remote cache

And even if there's a big tarball, it probably take similar time to extract the tarball vs downloading these files from remote-cache? Even if the remote-cache is a local implemented one.

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


Remove hard dependency on Cats

I've tested on 2.81, 2.93 and 3.4, so the minimum required Blender version should still be 2.81.
I've tried a bunch of different avatar setups and fixed any bugs I've found with them, so hopefully there's nothing big that's slipped through the cracks.

The apply_pose_to_rest function is modified from what I wrote in Cats development to fix the bug causing mesh vertices and reference shape key desync and adds support for multi-user data
Implementation changes:
Only count vertices as weighted to feet if their weight is not zero
Add base class with poll method for armature operators
After trying to find the armature specified by Cats, if no such armature exists or Cats isn't loaded, attempt to get the armature from the context, otherwise fall back to trying to get an armature object with the name "Armature" (original behaviour) and if that fails, if there's only one armature object in the scene, use that
Optimisation
Speed up get_highest_point and get_lowest_point

Use numpy where possible to avoid iteration
Check object bounding boxes to skip checking some meshes
Order meshes by bounding box max/min z
Turn lists that are checked if elements are in them into sets
Replace hide/unhide and editmode swap to fix desync with direct copy of basis shape key 'co' into vertices 'co' (this could be removed entirely or moved elsewhere, such as running once at the start of the operator, but I didn't want to mess with the structure of the addon too much)
Use built-in property for getting bone children recursively
Find minimums after iterating vertices to reduce calls within the loops

Fixes
Fix use of undeclared result_final_points variable
Fix get_lowest_point not taking into account the mesh's worldspace matrix
Fix bone override enum function not keeping python references to strings
Fix head_to_hand calculation when arm and elbow bones are not connected
Fix error raising in get_eye_height when eye bones are not found
Fix asymmetrical bones with symmetrical names becoming symmetric when armature has symmetry enabled
Raise error in get_lowest_point if there are no vertices
Refactoring/documentation
Small readme update now that Cats isn't required
Remove legacy scaling option and info since the initial changes to scaling in IK 2.0 were reverted
Re-use the same items function for each bone override EnumProperty
Correct head_to_hand comment that says the arm length is from the shoulder, when it is actually calculated starting from the upper arm
Remove unused argument in get_body_meshes and get_armature
Remove make_annotations functions
Remove unused functions

I've realised there is an additional area that needs to see some fixes. The get_highest_point() and get_lowest_point() functions return world-space coordinate values (before this pr, get_lowest_point() erroneously returns per-mesh local-space coordinate values), but wherever bone positions are being used, their positions are in local-space of the armature object.
In some places, e.g. get_leg_length(...), world-space and local-space coordinates are being used together, which can result in incorrect values if the armature object's matrix_world isn't the identity matrix.
get_leg_length(...) in particular can easily be seen to change if the armature object (with meshes parented to it) is moved up/down.
I'm thinking the most simple solution is going to be to convert all the bone positions to world-space.

Updated the PR with the following:
Add button to set Upper Leg Percent from current avatar
Fix some calculations mixing world-space and local-space values
Fix different arm length calculation in head_to_hand and calculate_arm_rescaling (they both use a new get_arm_length function)
Fix recursive_scale when Objects have multi-user data (would error because the operator can't be applied to multi-user data, the data is now replaced by a copy if it has multiple users)
Fix current height and eye height not taking into account the lowest point of the avatar
Fix operations not working when armature/meshes are disabled (when hide_viewport == True or is True because it is inherited from the parent Object or all collections that it's in)
Fix typo in left_wrist and left_leg bone_names (there was one name in each that was named as if it was a right-side bone)
Replace individual object hide/unhide with context_manager used by operators that ensures the armature and body meshes are enabled (it does this by temporarily adding them to the scene's collection, since that always exists and can never have hide_viewport == True and temporarily setting each Object's hide_viewport to False)
Move pose mode and reset before get_view_y in scale_to_floor
Replace O(len(bpy.data.objects)**2) Object children recursion with O(len(bpy.data.objects))


docs: updating documentation for NIMf connection example in Metal Connection Resource

-Updated template, doc and schema files for NIMF connection Documentation change:

resources/fabric-conenction
respurces/metal-connection
data-sources/metal-connection
Update example file names for metal and fabric connection resource

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 51.88%. Comparing base (f8c2ab9) to head (1fd29eb).
Report is 11 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #734       +/-   ##
===========================================
+ Coverage   34.44%   51.88%   +17.43%
===========================================
  Files         151      153        +2
  Lines       20710    20994      +284
===========================================
+ Hits         7133    10892     +3759
+ Misses      13415     9672     -3743
- Partials      162      430      +268

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Composable THOR memo processing

Overview
Follows-up on https://github.com/shapeshift/web/issues/6683 / https://github.com/shapeshift/web/issues/6679
See e.g https://github.com/shapeshift/web/pull/6700#discussion_r1582421070,
https://github.com/shapeshift/web/blob/5a7fc2e28761a823e0c2a6e6a126d21ddf822628/src/lib/swapper/swappers/ThorchainSwapper/utils/addAggregatorAndDestinationToMemo.ts#L89-L114, or
https://github.com/shapeshift/web/blob/6566b6525d060e4db72370c695e8b7992046224e/src/lib/swapper/swappers/ThorchainSwapper/utils/addSlippageToMemo.ts#L39-L44
For places that do memo mutation. #6755 brought an assertAndProcessMemo util.
At the moment, it's very dumb and takes whichever memo is passed in, splits it into parts, and adds the affiliate name if needed.
We want to improve our current memo-building (addSlippageToMemo, addAggregatorAndDestinationToMemo.ts and THORChain LP's memo expression) to be composable and pass parts to assertAndProcessMemo (or a new building-focused util instead), to benefit from its validation feature.
References and additional details
See overview
Acceptance Criteria

assertAndProcessMemo is able to do validation on parts to ensure that the memo is correct
Nice-to-have: either:

some building-specific util is added to consolidate the memo-building logic (i.e build a memo from parts) across addSlippageToMemo, addAggregatorAndDestinationToMemo.ts and THORChain LP's memo expression`
assertAndProcessMemo knows how to build a memo from parts

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

We will need to do some stuff following https://github.com/shapeshift/web/pull/7351
Making LP deposit/withdraw composable and validated the same way we do for swaps


Keep volumes alive if they have the jhub.SwarmSpawner.keep label attached

useful when you're restarting jupyter frequently, but want to keep your workspace

Yes that is good option to have.
Ty for pull.


🐛  Biome simply doesn't work on vscodium

VS Code version
v1.93.1
Extension version
v2.3.0
Biome version
v1.9.1
Operating system

[ ] Windows
[ ] macOS
[X] Linux

Description
When I open the linked repo, the  biome extension gives two notifications to report errors and then shuts down.
Steps to reproduce

Install the biome extension and donwload the binary when prompted.
Open the repo in vscode/vscodium, observe the errors being thrown in the notifications.
a. Sending document notification textDocument/didOpen failed
b. Client Biome: connection to server is erroring. Shutting down server.

Expected behavior
The extension simply works.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
https://github.com/shellheim/biome-minimal
Logs
Couldn't find any trace logs in the biome trace category, but here's the biome category logs that I think are relevant.

Could not resolve Biome in the dependencies of workspace folder: /home/shell/Code/projects/react/repo
Searching for Biome in PATH
Biome binary found at /home/shell/.config/VSCodium/User/globalStorage/biomejs.biome/server/biome
Executing Biome from: /home/shell/.config/VSCodium/User/globalStorage/biomejs.biome/server/biome
[cli-stdout] data 44
[cli] exit 0
Connecting to "/home/shell/.cache/biome/biome-socket-1.9.1" ...
[cli-stderr] data 393
[Error - 15:41:25] Sending document notification textDocument/didOpen failed
Error: This socket has been ended by the other party
	at genericNodeError (node:internal/errors:984:15)
	at wrappedFn (node:internal/errors:538:14)
	at Socket.writeAfterFIN [as write] (node:net:561:14)
	at /home/shell/.vscode-oss/extensions/biomejs.biome-2.3.0-universal/out/main.js:3008:25
	at new Promise (<anonymous>)
	at WritableStreamWrapper.write (/home/shell/.vscode-oss/extensions/biomejs.biome-2.3.0-universal/out/main.js:2999:16)
	at StreamMessageWriter.doWrite (/home/shell/.vscode-oss/extensions/biomejs.biome-2.3.0-universal/out/main.js:1429:31)
	at /home/shell/.vscode-oss/extensions/biomejs.biome-2.3.0-universal/out/main.js:1420:25
[Info  - 15:41:25] Connection to server got closed. Server will restart.
true
[cli-stderr] end
[cli-stderr] finish
[cli-stdout] end
[cli-stdout] finish
[cli-stdout] close
[cli] close 0
[cli-stderr] close
[cli-stdout] data 44
[cli] exit 0
Connecting to "/home/shell/.cache/biome/biome-socket-1.9.1" ...
[cli-stderr] data 393
[Error - 15:41:26] Client Biome: connection to server is erroring. Shutting down server.
[Error - 15:41:26] Client Biome: connection to server is erroring. Shutting down server.
[Error - 15:41:26] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 15:41:26] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 15:41:26] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[cli-stderr] end
[cli-stderr] finish
[cli-stdout] end
[cli-stdout] finish
[cli-stdout] close
[cli] close 0
[cli-stderr] close

Hey, any chance you could try with the prerelease of the extension. We've addressed a lot of issues since.

Tried with the nightly, getting the same errors.

Looks like you've installed the deprecated nightly distribution. I'm talking about the pre-release channel on the extension. You can switch the channel on the extensions page within VS code

Oh sorry, I fixed that. While the extension doesn't error out, it only works when I add @biomejs/biome as a dependency in my project. Is the sole binary option being phased out?

Okay, so I just discovered this, formatting seems to be broken too. Though it lints fine.

We're encouraging the use of the binayry through your dependencies, but if you install Biome globally on your system (in your PATH), we'll pick it up there if it cannot be found in your deps.
Alternatively, you can force the extension to use the binary of your choice by setting its path in biome.lsp.bin

Ahh, thanks for the reply. Everything works as expected after adding the dep and tweaking some settings. Closing this now.


Replace recursive-copy with own implementation

Replace recursive-copy npm package by a simpler implementation with less options.
It's currently only used in next export. The new implementation will always follow symlinks and expand it (meaning a symlink in the source tree pointing to a regular file will become a regular file in the destination tree). It will also always fail if a file in the destination folder already exists.
Todo :

[x] update yarn.lock
[x] do not fail if destination folder already exists

Fix https://github.com/zeit/next.js/issues/6941

I'm not sure why some tests are not passing 🤔
I managed to successfully run the tests locally with Node 8.16.

Could you do a benchmark similar to the bench directory

@timneutkens
I added a benchmark in bench/recursive-copy.
~ cd bench
~ yarn run bench:recursive-copy
test recursive-copy npm module
{ sum: 1067.209105, nb: 10, avg:<PHONE_NUMBER>9999999 }
test recursive-copy custom implementation
{ sum: 582.435537, nb: 10, avg: 58.24355369999999 }

I'd be super happy to take in these changes once the merge conflicts are solved 💯

Thanks!


Add per shard and per Instance drop-down to all IO dashboards

@glommer can you please review?

@tzach tested and it works well
Thanks!


Swapped Current State

Hi MnrGreg. Now that Homekit is working I've tested it a bit and noticed that when I manually Stay-Arm at the panel it returns a CurrentState of 1 (i.e. Away_Arm state) on both the Pi terminal and on Homekit. Whereas, when I set the alarm on Homekit it is correct (i.e. the TargetState is a 0). IIf I close Homekit and start it again with the alarm in any state the alarm icon will always shows an "Away" state. Is this normal? I'm not much past the 'nooby' stage so unfortunately I'm can't make too much sense of the code. Thanks.

Hi Minimiller,
What does it mean "'initialising' the Homebridge by Stay-Arming the MG5050"?
I think I have the same problems as you were when Homekit not working. Can You Help Me?
The problem is inside the file Config.json?

Thanks a lot.


[FEATURE] Improvement in Footer

Description
There is much room for improvement in Footer but I found some of the following:

Improve the Report button CSS
Need to increase the size of social link icons for better visibility

Screenshots

Additional information
It would be great if there is an improvement in the color scheme of the Footer.
Thank you!

It's great having you contribute to Milan ! This is an auto-generated textThe maintainers/owner will look into the issue soon, add relevant tags and proceed further, please have paitence. Meanwhile feel free to support star the repo and share it with your friends. :nerd_face: :rocket:

A great spot, however we already have a new Report button looks.
Social link size will be increased in another issue where we are adding contact link !
Thanks for raising the issue, but closing it since someone else is already working on it !


Update dependencies

This PR

Adds compat bounds to environments
Updates the ClimaComms compat bounds
Updates the manifest files
Applies fixes for ClimaComms updates.

bors r+


Enable flake checking on code and notebooks

Not necessary at this point, we can reopen later if the need arises.


Show correct authentication header

The variable APP_ID_SHORT is not set, so the header was shown incorrectly.

Thanks for the PR!


Webexception was unhandled

after i login and the program logs me in successfully after i give the two factors code , and starts pulling offers every 10 seconds , i have pending offers already , but the program crashed giving me , webexception was unhandled , i've tried to debug it ... ive tried to see the error and it appears that the server is responding with 500 error ...
so if you can help :)

Does this happen the minute it attempts to receive an offer or after a few times?

Does this happen the minute it attempts to receive an offer or after a few times?

no the minute it starts to pull the offer

no the minute it starts to pull the offer

but it doesn't happen when there's no pending offers the last time i checked

but it doesn't happen when there's no pending offers the last time i checked

The fact that it has the 2FA code makes me think that you have mobile confirmations enabled, is this correct?

yup its enabled

Unfortunately, I have not done much testing in that area. Because of this, I have not finished adding support for mobile confirmations. Sorry!

its okai , no problem , but can we talk in private  i need your help in some stuff cuz im creating my own bot right now , so i might use some of your experience


Fix Fix data loss when node channel been cancelled before close wait

Proposed changes
Fix data loss when node channel been cancelled before close wait

run buildall


Improve import declaration recovery

Purpose
$subject.
Fixes #27026
Approach
N/A
Samples
N/A
Remarks
N/A
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[x] Added necessary documentation

[x] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@lochana-chathura Shall we resolve the conflicts and handle the review comments, please?

@lochana-chathura Can you please respond to the review comments and handle the conflicts.

@lochana-chathura Can you please respond to the review comments and handle the conflicts.

On it.

@rdulmina Shall we merge this PR if everything's ok?


employment situation - add more than one

Do we want this here?  Why not get this information when getting/by employment information?  It seems weird to add the ability to choose multiple employment statuses when we are already collecting multiple jobs.

https://github.com/LemmaLegalConsulting/docassemble-Covid19debt/issues/55

If we remove this question the only opportunity someone has to share a potential lack of income is in the income section which they will skip if they are unemployed. We miss information like being a student or unemployed vs retired
It doesn't have a impact on the calculus, but might be important to a debt advisor.
The question could be moved to seem less redundant.


Season and episode

Hi sir I would like to thank you first for your hardworking and amazing app second it will be nice if you will be able to add dimming the season or the episode which have been watched  thanks again

Hey @Baker0o7, as of version 1.1.1, there is a small progress bar that appears below each episode indicating how much of the episode you have watched.


Dropdown Component

Implement Dropdown component, similar to Dropdowns - Bootstrap, or Reach UI - Menu Button (Dropdown).

Related #131

Need to connect to pick up workstream btw @jxnblk & self to figure out the next step for this issue.

CC @jxnblk & other WG members,
Going to pick back up this issue, any objection if the proposal for this issue uses Dropdown instead of ~PopoverContainer~ & ~Popover~? Feel that since the Select component now is pretty clear to <select> to wrap <option>, the original purpose of choosing Popover name to distinguish is not needed.
I'd go with Dropdown for the upcoming PR, if no objection. But ping me here to let me know if any thoughts.

Yeah, I think we should call this thing a Dropdown unless anyone has a really good reason not to

Cross-posting this comment from #434 to denote why this issue could be closed. Issue could be re-opened if needed, and further question could be discussed in this thread:

Unfortunately, after WG session, the feeling is that Select is serving most of what a Dropdown would offer. There was doubt that if reach-ui or other lib like downshift would be used. Also the underlying native  on mobile would opt in the mobile browser's UI & benefits for .

On that note, this undesired Dropdown PR would be closed, as well as its related issue. Further questions could be discussed in the closed issue though ...


chore(nodejs): update client ref docs link in metadata

@fhinkel The docs test is unhappy because https://cloud.google.com/nodejs/docs/reference/common/latest is 404.
Do we have a plan to create that page?

I've spoken to @fhinkel, she will take a look!

Opened by mistake.


[microNPU] Add support for TFLite FULLY_CONNECTED

This is primarily a legalization to an NPU Conv2d operator. The
legalization target is Conv2d with 1 1 I O (HWIO)

cc @ekalda @manupa-arm @lhutton1 @NicolaLancellotti

Looks like CI only failed because of a flaky GPU test :)


SCRIPT1002: Syntax error on IE11 in ver ^6.0

I am using webpack and upgrading this library to latest version (as of now ver 6.8.1) is giving me Syntax Error in IE11 (other browsers are fine)

And this is the exact error location:

Downgrading to version 5 does not trigger this error.
Any help or fix is very much appreciated on this.

From the top of the readme:

This module targets Node.js 6 or later and the latest version of Chrome, Firefox, and Safari. If you want support for older browsers, or, if your project is using create-react-app v1, use version 5: npm install query-string@5.

This one bit us in prod, ty @iainheng for opening issue it made finding the resolution quick enough.
I wonder if theres a reason for not transpiling down to support older browsers? I don't think IE11 is EOL yet 🤔 anyway thanks for the package.

Same thing... This has tripped me up on two separate occasions now (shame on me).  Given the simplicity of this library, seems like no reason not to target something lower.

So what is the "real" solution to fix this?

I guess it is possible to just parse it on build using babel-loader
        test: /\.js$/,
        exclude: /node_modules[\\,/](?!(query-string)[\\,/]).*/,
        use: {
          loader: 'babel-loader',
        }

or im I wrong?

From the top of the readme:

This module targets Node.js 6 or later and the latest version of Chrome, Firefox, and Safari. If you want support for older browsers, or, if your project is using create-react-app v1, use version 5: npm install query-string@5.

v5 does not support custom decode options. With v6, we can just use
querystring.parse(data, {decode: false})


fix: specify type variable of GUID

Description

Specifying type variable would help static analyzers do their jobs.

Closes

Thanks for this.  I think the failure here is a result of the move into the Litestar org.  We'll get this merged soon.


Better error handling for field deserialization

I believe the deserialization logic here should be improved: https://github.com/scipr-lab/zexe/blob/e1db7c5fede8ba5a0f5b3958692de44da65c1cb6/algebra-core/src/fields/macros.rs#L175
When Zexe tries to read a byte stream and it gets a value that isn’t in the field it returns 0. This is both confusing for users to check for errors and prevents from getting a valid 0 value.
A current approach to mitigate it is https://github.com/scipr-lab/zexe/pull/181/files#diff-0d3539aa74111fa4e3ea4d5b08b7278cR289, but should be improved.

I believe this is fixed now? from_repr returns an Option<Self>.


How to decrease the block sway speed

I just want to decrease sway speed of the block or wanna slow down the block sway to the left and right that the user can play more

You could try hookSpeed and hookAngle


Simplify the package installation and ship with model configuration files

Regarding issue #51, I suggest simplifying the install process by shipping the model configuration files with the python package.
Install with pip install git+https://github.com/facebookresearch/segment-anything-2.git@main

Thanks for the PR! We recently resolved it in #176. Now when running
python3 -m pip install git+https://github.com/facebookresearch/segment-anything-2.git

the SAM 2 config files would be copied over in the sam2_configs package added to user's site-packages


Do I need an Auth0 account to use this module?

Hi, I am planning to implement tokens in my swift mobile application. I am not able to figure out if i need Auth0 account to use this module.. What is another alternative if I don't want to use Auth0 and implement the authentication myself?

I use socketio-jwt without Auth0 account :)


[firebase-admob][android] App crashing on startup when using build command

when I use tns run android to test the application locally, the app works fine. But when I build the application tns build android the application is crashing with the following exception on startup.

As we are using angular in our app we added Admob.init() in APP_INITIALIZER.
import { Admob } from "@nativescript/firebase-admob";
export function initializeAdmob() {
return (): Promise => {
return Admob.init();
};
}
node version: 18.4.0
npm version: 8.1.4
ns version: 8.2.3
ns firebase version: 2.1.0

Can you try adding this to your webpack config
  webpack.chainWebpack((config) => {

    config.optimization.usedExports(false);

this seems to have fix the issue. The app is building successfully now. But could you please explain why this was happening and if this is a permanent solution can this be added to the documentation.


How to set timeout for client?

I do not see any option to feed options while creating client. How to set timeouts to ensure that if there is a connection problem or, another failure request terminates with error?

@amitmahbubani idiomatic way that this is managed across go is context. I was developing a AWS lambda where I receive a context with deadline. It would far more easier for me to pass the context rather than compute timeout.


misc/cgo/test: make sure we run TestCrossPackageTests with appropriate options

In https://golang.org/cl/163418 we started running several of the tests in misc/cgo/test via a separate invocation of go test.  In cmd/dist we run the tests in misc/cgo/test with several different -linkmode options; see (*tester).cgoTest in cmd/dist/test.go.  But as far as I can see those different options are not being carried through the separate invocation of go test in TestCrossPackageTests, so we are no longer testing all the cases we did before.
This issue is to make sure that we run those tests with the appropriate options.
CC @bcmills

TestCrossPackageTests explicitly propagates os.Environ(), so it would probably suffice to set whatever options are needed in the GOFLAGS variable before running the test.


Why shared memory used when worker dealing with alien packets?

Dear sir,
I wander why litespeed use shared memory to deal with alien packets but not unix domain socket ? What's the main concern?
For us, the memory used can't be avoided.
Best regards！

This is for historic reason, when SO_REUSEPORT has not been implemented in our products.
When multiple processes read packets from the same UDP socket, packets belong to one QUIC connection received by different worker processes.
It is still useful during graceful restart, which need to pass packets from one process to another.
For simple single worker process implementation that do not need graceful restart, it is not required.

This is for historic reason, when SO_REUSEPORT has not been implemented in our products. When multiple processes read packets from the same UDP socket, packets belong to one QUIC connection received by different worker processes. It is still useful during graceful restart, which need to pass packets from one process to another. For simple single worker process implementation that do not need graceful restart, it is not required.

Thanks for your reply.
I have already known the problem as you described. However, my question is why Share Memory Used but not UDS, as packets stored in SHM will cost the memory and  scalability is not so good.

SHM is zero-copy, UDS is slower.

Ok, thx, I  got that, but UDS is more flexible.
I will do some performance test.
Close at this time.


Use rocm 6.1.0 in CI on Tioga

We update RADIUSS Spack configs and the Tioga CI jobs to test with<EMAIL_ADDRESS>Once this branch is merged, we should work on https://github.com/LLNL/Umpire/pull/795

Closed in favor of #885


feat(eosio.token): add inline_transfer static method

Add inline_transfer static method to eosio.token.
This method is needed for other contracts to call tranfer action.
It is similar to what old currency::inline_transfer did.

@zorba80 transfer_args  doesn't need a EOSLIB_SERIALIZE macro?
In my tests, structs in action params should have a EOSLIB_SERIALIZE macro.