can we share file or document via udp?

I want to send and receive files,documents like pdf or images with server client connection. can we achieve this with UDP?
Currently I have tried this with file convert in to base64 string and pass as message and another side can receive it too.but its not proper way when document size is large. can you please help?

My opinion UDP is only for light weight sending of data. You may have to use TCP.
Sent from Yahoo Mail for iPhone
On Wednesday, September 6, 2023, 3:31 AM, Shivani12345 @.***> wrote:
I want to send and receive files,documents like pdf or images with server client connection. can we achieve this with UDP?
Currently I have tried this with file convert in to base64 string and pass as message and another side can receive it too.but its not proper way when document size is large. can you please help?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Fix typo in migration document

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Typo in migration document (gard -> grad)
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:

[ ] Pre-commit or other linting tools are used to fix the potential lint issues.
[ ] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[ ] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[ ] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects, like MMDet or MMSeg.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

 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.


fixed monk's unarmored defense

Fixed the minor detail of how the monk's unarmored defense works

Fixed in V4.0.3


refactor(connector): [Coinbase] Use connector_request_reference_id as reference to the connector

Type of Change
[FEATURE]: [Coinbase] Use connector_request_reference_id as reference to the connector
#2295

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[ X] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Make any Payment for connector Coinbase and see that you are getting "reference_id" field in the logs of payment request.
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Hey @sccalabr,
I have reviewed the latest changes in the main branch, and unfortunately, I did not find the necessary updates. As a result, I will be closing this pull request


install gulp#v4.0.0-alpha.2 git damaged

npm install gulpjs/gulp#6d71a65
npm ERR! code 1
npm ERR! Command failed: C:\Program Files\Git\cmd\git.EXE checkout 6d71a65
npm ERR! error: Your local changes to the following files would be overwritten by checkout:
npm ERR!        docs/why-use-pump/pipe-error.png
npm ERR!        docs/why-use-pump/pump-error.png
npm ERR! Please commit your changes or stash them before you switch branches.
npm ERR! Aborting
npm ERR!

npm install gulpjs/gulp#430df36
npm ERR! code 1
npm ERR! Command failed: C:\Program Files\Git\cmd\git.EXE checkout 4.0
npm ERR! error: pathspec '4.0' did not match any file(s) known to git.
npm ERR!

I want to install v4.0.0-alpha.2, what should I do

Same on my end. Can confirm this isn't an NPM issue either, as other repos work fine.
I don't have a solution, but in the meantime I have an alternative. As of around 5 hours ago v4 was released on NPM with the next tag, so you could simple pull direct from NPM with npm install gulp@next. (ref https://twitter.com/gulpjs/status/947642181631721472)

I had to delete package-lock.json on my repo to solve the problem. For me the lockfile did not matter since I wanted the latest of all packages anyways.

@ParaBolt Really? I replicated this immediately after npm init, so there was no lock file. I've eliminated the existance of node_modules as a factor too, it makes no difference.
Huh. Heres a thought. 4.0 is now on master, and no doubt there were merge conflicts given how long it was in development. Could it be possible that this has been caused by caching? (something untouched by npm cache clean --force?)

@Silic0nS0ldier : Reverting to the old package-lock.json and reinstalling brings back the issue for me. I had tried cleaning the cache and even using an older version of node but the problem still persisted.

Removing '4.0' broke a lot of stuff 😞
And using glup@next with the current version of npm fails due the the @:
$ npm --version
6.4.1
$ npm install gulp@next
Unhandled rejection Error: Invalid tag name "gulp@next": Tags may not have any characters that encodeURIComponent encodes.

Is gulpjs/gulp#v4.0.0 equivalent for now?

@whereisaaron we've left that stale branch around for 10 months - it's time to upgrade, we've even updated our API docs and getting started guide to help with your migration.  I'm not sure what's messed up with your npm install but everyone uses tags like that.  You'll have to look somewhere else for the solution to that issue.

Thanks @phated, I was not thinking to keep the branch, just to dual tag that release with the old and the new scheme, ie. '4.0' and 'v4.0.0'. Once you've had a stable version number in use for more than a year, I think it should stay around. The same way you have 'v3.8.1' etc. but still kept the old '3.8'.
I fixed the weird npm invalid tag error by deleting the packages-lock.json.

When it stopped working for me, I had gulp installed like
"gulp": "git://github.com/gulpjs/gulp.git#6d71a658c61edb3090221579d8f97dbe086ba2ed"
I try to use "gulp": "git://github.com/gulpjs/gulp.git#6d71a658c61edb3090221579d8f97dbe086ba2ed" but fail. I try to use gulpjs/gulp#v4.0.0-alpha.3  is ok.


Desktop application fails showing alpha video transparency

What happened?
We put a plane on our land and set texture as transparent video.
webgl version works good but desktop application  doesn't show transparenct but black color.
Steps to reproduce
Go in to decentraland using desktop application and try to show a transparent video.
Operating System
Windows 10  (10.0.19042) 64bit
Wallet
Metamask
CPU
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
GPU
NVIDIA GeForce RTX 2070 8031MB
RAM
16225MB
Kernel Version
1.0.0-2141827118.commit-450c363
Unity Version
desktop-main.commit-64822b7
Realm
dg
NameTag
sd#1452

The solution for this would be to change the RGB24 format, to RGBA32 format. The current VideoPlayer implementation is ignoring the alpha channel.

We believe this is fixed


SEO update advanced-hunting-overview

replaces PR#2249
reverted to original metadata title
added high value search keyword to description
added "cyber threat" keyword to body
@DaniHalfin

@lomayor - ok to merge?

@DaniHalfin reverted edits


[Feature]  Serve online document on git pages

Component
Other (please provide more details)
Describe the feature you would like
Since the crates are not fully published yet, developers hardly can get an overview of this toolset by now which is also blocking issuing bugs, contribution, etc.
Additional context
No response

All crates are published on crates.io, and as such are also available on docs.rs. Example: alloy-primitives (docs.rs)


pythonPackages.dash: 1.17.0 -> 1.19.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112080 run on x86_64-linux 1

15 packages built:

python37Packages.dash
python37Packages.dash-core-components
python37Packages.dash-html-components
python37Packages.dash-renderer
python37Packages.dash-table
python38Packages.dash
python38Packages.dash-core-components
python38Packages.dash-html-components
python38Packages.dash-renderer
python38Packages.dash-table
python39Packages.dash
python39Packages.dash-core-components
python39Packages.dash-html-components
python39Packages.dash-renderer
python39Packages.dash-table

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112080 run on x86_64-darwin 1

15 packages built:

python37Packages.dash
python37Packages.dash-core-components
python37Packages.dash-html-components
python37Packages.dash-renderer
python37Packages.dash-table
python38Packages.dash
python38Packages.dash-core-components
python38Packages.dash-html-components
python38Packages.dash-renderer
python38Packages.dash-table
python39Packages.dash
python39Packages.dash-core-components
python39Packages.dash-html-components
python39Packages.dash-renderer
python39Packages.dash-table


[ServiceBus] update error raised when completing lock expired messages

addressing: #29667

/azp run python - servicebus - tests

API change check
API changes are not detected in this pull request.


⚠ Bofrost.de has degraded performance

In c118509, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1325 ms

Resolved: Bofrost.de performance has improved in 77583cd after 6 minutes.


Hackathon Jira 1

Test integration 1

Looks like Github -> Jira worked

Testing Jira comment 1

Testing Jira comment 2

Testing Jira comment 3

mParticle ticket status has been changed to In Review

mParticle ticket status has been changed to Wont Do


⚠ ClamAV has degraded performance

In 074f9cd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: ClamAV performance has improved in cc41c01.


Added json.toggle

Added support and tests for JSON.TOGGLE command

Hi @JyotinderSingh, @lucifercr07
Can you have a look at this PR

thanks for your contribution. this pr linked  #503. In case of other person is doing the same work,  should notice issue with the assigned.
because json.toggle change the original json, should add integration test in tests/json_test.go
a few other comments added, please take a look thanks.

Made all the changes that you requested and committed.

fixed the issue
newobj:=store.NewObj(jsonData,-1,object.ObjTypeJSON,object.ObjEncodingJSON) store.Put(key, newobj)

Hi @TheRanomial , @srivastava-yash, I have found a solution for our problem with expr.Set(). Please refer to PR #585 for your reference and please let me know if you find any issues in the code as well.

Hi @TheRanomial , @srivastava-yash, I have found a solution for our problem with expr.Set(). Please refer to PR #585 for your reference and please let me know if you find any issues in the code as well.

@TheRanomial please go through the linked PR and also the comments I've left. You can modify this implementation accordingly. Please add additional test cases too (to verify behavior where multiple keys are being toggled as being discussed in other comments)

Hii @JyotinderSingh Implemented all the changes that you requested and tests are working fine.


The MMU still seem to have timings issues when used with a RAMWorks III card

With this setup:

Rockwell R6502
Unenhanced ROMs
ASIC IOU
RAMWorks III

The games "The Black Cauldron" fail to load and the game "ALIENS" have visual glitches.

This is an interesting issue, it seems that the CPLD itself is the issue.
The RA bus on the Apple IIe is shared between the MMU and the IOU; the MMU drives the bus when PHI_0 is HIGH, and the IOU drives it when PHI_0 is LOW. When the MMU or IOU is not driving the RA bus, it 'disables' it's output to the bus. If we consider the MMU, it drives the bus from the rising edge of /RAS in the previous cycle (i.e. /RAS is HIGH, but PHI_0 and Q3 are LOW) to the falling edge of Q3 of the current cycle (i.e. while both PHI_0 and Q3 are HIGH). A requirement of the RAM used in the Apple II serie is that the RA bus must hold it's value for some short delay past the falling edge of Q3. One way to do this, when using an Altera device, is to use the LCELL primitive; it adds ~5 ns per LCELL and is useful when precise timing is not required.
The LCELL primitive is a buffer and should not modify the signal. So, with this VHDL code:
    TEST_SIGNAL <= Q3 nand PHI_0;
    INITIAL_DELAY : LCELL port map(
        A_IN => TEST_SIGNAL,
        A_OUT => TEST_DELAYED(0)
    );

    g_GENERATE_DELAY: for i in 0 to 8 generate
        DELAY : LCELL port map(
            A_IN => TEST_DELAYED(i),
            A_OUT => TEST_DELAYED(i+1)
	    );
    end generate g_GENERATE_DELAY;

    LCELL_DELAYED <= TEST_DELAYED(9);

This just connect TEST_SIGNAL through a serie of 10 LCELLs. We would expect LCELL_DELAYED to be the same as TEST_SIGNAL, delayed by ~50ns. But that's not what we have:

Yellow is TEST_SIGNAL,
Cyan is LCELL_DELAYED,
Magenta is PHI_0,
Blue is Q3
The above image is a bit crowded, so this is just TEST_SIGNAL and LCELL_DELAYED:

You can see LCELL_DELAYED dropping but TEST_SIGNAL is not! It's the LCELLs that are causing this drop; this is what a 2-LCELLs looks like:

Normally, LCELLs behave as expected, but in the above case, I think it's due to the fact that TEST_SIGNAL is computed from two slow-changing signals:

As you can see the drop is ~50ns after the PHI_0 / Q3 change.
Should be fixed soon.


can't start service [pylon]

2020-08-05 05:49:07,806 [INFO] - deployment.paiLibrary.paiService.service_management_start : -----------------------------------------------------------
2020-08-05 05:49:07,806 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to generate service cluster-configuration's template file
2020-08-05 05:49:07,806 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Begin to generate the template file in service cluster-configuration's configuration.
2020-08-05 05:49:07,807 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Create template mapper for service cluster-configuration.
2020-08-05 05:49:07,807 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Done. Template mapper for service cluster-configuration is created.
2020-08-05 05:49:07,807 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/secret.yaml.template.
2020-08-05 05:49:07,807 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/secret.yaml.
2020-08-05 05:49:07,809 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/host-configuration/host-configuration.yaml.template.
2020-08-05 05:49:07,810 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/host-configuration/host-configuration.yaml.
2020-08-05 05:49:07,813 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/gpu-configuration/gpu-configuration.yml.template.
2020-08-05 05:49:07,813 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/gpu-configuration/gpu-configuration.yml.
2020-08-05 05:49:07,816 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/gpu-configuration/gpu-configuration.json.template.
2020-08-05 05:49:07,816 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/gpu-configuration/gpu-configuration.json.
2020-08-05 05:49:07,821 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/docker-credentials/config.json.template.
2020-08-05 05:49:07,821 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/docker-credentials/config.json.
2020-08-05 05:49:07,821 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/stop.sh.template.
2020-08-05 05:49:07,822 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/stop.sh.
2020-08-05 05:49:07,823 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/start.sh.template.
2020-08-05 05:49:07,823 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/cluster-configuration/deploy/start.sh.
2020-08-05 05:49:07,830 [INFO] - deployment.paiLibrary.paiService.service_template_generate : The template file of service cluster-configuration is generated.
2020-08-05 05:49:07,830 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to start service: [ cluster-configuration ]
2020-08-05 05:49:07,830 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to execute service cluster-configuration's start script.
W0805 05:49:07.869872   29691 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/host-configuration configured
W0805 05:49:08.024375   29716 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/docker-credentials configured
W0805 05:49:08.153906   29740 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/gpu-configuration configured
W0805 05:49:08.328847   29763 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/pai-version configured
W0805 05:49:08.466242   29784 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/k8s-version configured
yes: standard output: Broken pipe
W0805 05:49:08.684822   29811 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
secret/job-ssh-secret configured
secret/pai-secret unchanged
secret/pai-secret unchanged
src/cluster-configuration/deploy/start.sh: line 65: parallel: command not found
2020-08-05 05:49:09,122 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to clean all service's generated template file
2020-08-05 05:49:09,123 [INFO] - deployment.paiLibrary.paiService.service_template_clean : Begin to delete the generated template of cluster-configuration's service.
2020-08-05 05:49:09,123 [INFO] - deployment.paiLibrary.paiService.service_template_clean : The generated template files of cluster-configuration's  service have been cleaned up.
2020-08-05 05:49:09,123 [INFO] - deployment.paiLibrary.paiService.service_management_start : Successfully start cluster-configuration
2020-08-05 05:49:09,123 [INFO] - deployment.paiLibrary.paiService.service_management_start : -----------------------------------------------------------
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_management_start : -----------------------------------------------------------
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to generate service pylon's template file
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Begin to generate the template file in service pylon's configuration.
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Create template mapper for service pylon.
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Done. Template mapper for service pylon is created.
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/pylon.yaml.template.
2020-08-05 05:49:09,124 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/pylon.yaml.
2020-08-05 05:49:09,152 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/start.sh.template.
2020-08-05 05:49:09,153 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/start.sh.
2020-08-05 05:49:09,155 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Generate the template file /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/pylon-config/run.sh.template.
2020-08-05 05:49:09,155 [INFO] - deployment.paiLibrary.paiService.service_template_generate : Save the generated file to /quick-start-config/pai/deployment/paiLibrary/paiService/../../../src/pylon/deploy/pylon-config/run.sh.
2020-08-05 05:49:09,158 [INFO] - deployment.paiLibrary.paiService.service_template_generate : The template file of service pylon is generated.
2020-08-05 05:49:09,158 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to start service: [ pylon ]
2020-08-05 05:49:09,158 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to execute service pylon's start script.
W0805 05:49:09.195002   29872 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
configmap/pylon-config configured
daemonset.apps/pylon-ds configured
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
pylon is not ready yet. Please wait for a moment!
...

The information above was met when I deployed openPAI. How can I fix this problem?

Could you paste the pod output?
kubectl get pods --no-headers -o custom-columns=":metadata.name" \
  | grep pylon | xargs kubectl logs

And pls make sure 80 port is available on the host.

@yingunjun - Could you please follow the issue template to share more information to us as context? thanks.
Organization Name:
Short summary about the issue/question:
Brief what process you are following:
How to reproduce it:
OpenPAI Environment:
OpenPAI version:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Hardware (e.g. core number, memory size, storage size, GPU type etc.):
Others:
Anything else we need to know:

Thanks for your reply, I already fixed it. Thank you very much.

Thanks for your reply, I already fixed it. Thank you very much.

@yingunjun hello, can you please share with me your solution? Thanks～

resolved, caused by crt file lost after upgrade


file mode displayed

Add a row for file permission display (Unix style).

I made some significant changes, see commit messages for details.
Please let me know if that works for you.

Wow very happy thank you very much! excellent , works perfectly! I hope all others will be happy too


Address Issue #71 - Make Unit test and Integration test templates available

This change/addition addresses Issue #71 Add Unit and Integration Test Templates. These templates were originally created in the xNetworking DSC resource by @tysonjhayes. They have been converted over into two general purpose templates (and a support file for integration tests) so that they could be added to any DSC module.
Added files are:

Tests.Template/integration_template.ps1 - Integration test template.
Tests.Template/integration_config_template.ps1 - DSC config file used by the Integration test template.
Tests.Template/unit_template.ps1 - Unit test template.
DscResource.Template/.gitignore - this file is added to ensure that any new DSC repositories based on this resource template do not accidentally commit DSCResource.Tests into a repo by default. The new test templates will automatically download DSCResource.Tests repo to the module folder to perform tests, so ensuring it doesn't get commited back by accident should be a default behavior.
TestsGuidelines.md - guidelines and instructions for using the unit/integration test templates.

Updated files:

CONTRIBUTING.md - added/updated info on creating tests.

All feedback is much appreciated here, but there is no rush on this one - just thought I'd get it in there before the end of the year :+1:
Thankyou!

Hi @PlagueHO, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thanks @PlagueHO , looks good!


Astro Package?

Warning: this has become a dumping ground for some very disjointed thoughts :-)
But the big idea is that it would be nice to offer a subset package of AgnosticUI designed to work for SSR without the need for client partial hydration…

Astro based playgrounds have led me to believe it would be nice to have a component set that's available as Astro components. Perhaps an agnostic-astro package.
Astro components appear to use a sort of combination of SFC (e.g. <style> tags) and frontmatter and markup/template. So, the copystyles.js nodejs approach where we copy over the CSS from agnostic-css into the Astro package seems like it would work just fine.
For a first MVP, we could curate out some of the more dynamic JavaScript if it seems too difficult to support in a first iteration.
I'm marking this as v2 but if someone else wanted to help with this I'd definitely be up for having it sooner then that!

Longer-term Ideas
If we had truly platform-based JavaScripts for components available, we could certainly support that too as Astro has the notion of <script> tags. Today, I  suspect something like a11y-dialog could be leveraged to make Dialog / Drawer components work for example.
Cons

One con is the notion of building an Astro specific component set. This begs questions like "Well, what about Remix or other SSR methods?".
Another con is my own limitation in how many frameworks I can manage on my own.

My initial thought is—at some point I really need to have a community to do what I'd like to do. TodoMVC which is the big inspiration in terms of it having an amazing number of framework implementations was not literally all coded by Addy. He cultivated a community and they contributed as excitement grew.
As such, I do have to be careful where I put my early efforts. Can someone jump in and own this?
I also need to consider how to best show recognition to core contributors and maintainers so folks feel incentive and benefit corresponding to the amount of effort they'd put forth to make it all worthwhile for them 💯

I'm starting to feel like I should do a spike on using customElements and maybe Astro.resolve will result in preserving SSR?
https://navillus.dev/blog/web-components-in-astro
https://github.com/RocketCommunicationsInc/astro-components
https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements
https://m-docs.org/
I also read that you can use :host to define global styles then import into shadow https://www.colorglare.com/css-resets-and-global-styles-in-web-components-c71fcea86dbd but it seems wasteful to import it into each component
Another idea is to rely on css custom properties and maybe make a very minimal reset for WCs for things like box-sizing and what not.

Some Astro specific research
https://github.com/aFuzzyBear/xelement
astro hackathon: https://discord.com/channels/830184174198718474/961848242281259078/965615969026314321

@Croug re the priority list which was a great point I'm just jotting this down here (don't bother trying to read this mess notes I've left here otherwise lol)

So here are the biggest challenges for the ones that aren't dumb:

Keyboard navigation

I've been in contact with Peter @aFuzzyBear in the -XElement Discord channel (and creator of XElement.
I think I have a way forward on this just need to make some time.

a11y-dialog

Also worked w/Peter and have a way forward. This will require a CDN which is fine for the hackathon but there's a way to do this later ourselves. Gets us:
Dialog, Toasts, and Drawers

Probably the table/pagination is also going to need to be client hydrated

@Croug is on this one
I will easily have all the "dumb components" like tags, avatars, etc., done 💯 so I'd like to consider that a given.
So I think we may end up with full coverage but if there's a couple/few we can't get to I think it's still a big win.

This is done less Table / Pagination and this issue getting resolved in terms of being able to build the custom astro integration:
https://github.com/withastro/astro/issues/3246


[SBOM] Add information about the build that generated the attested artifacts

The sbom should contain also a reference to the build that produces the artifact and provenance, e.g. the jenkins build url.
This information could be captured as property, e.g.

name: "Build URL"
value: "https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk21u/job/jdk21u-aix-ppc64-temurin_SmokeTests/2/"

Furthermore, the sbom should capture information how the pipeline script was generated, i.e. include the following:

reference the ci-jenkins-pipelines repo with digest
reference the script that was used to generate the pipeline file

To give a reference how this is currently handled by SLSA. Here is an excerpt of the attestation produced for the slsa builder docker image as published here:
https://github.com/slsa-framework/slsa-github-generator/releases/download/v1.9.0/slsa-builder-docker-linux-amd64.intoto.jsonl
The reference to the actual build job is captured in metadata -> buildInvationId

to access the run you have to use figure out the url yourself:
https://github.com/slsa-framework/slsa-github-generator/actions/runs/5945355419-1

The BUILD_URL environment variable that gets passed from jenkins should be adequate for this.
There's also RUN_DISPLAY_URL but that redirects to a BlueOcean view.
We should also look at making sure that the release pipelines don't get deleted where possible, other than the attached artefacts (which will be stored in GitHub as well as on the parent pipeline)


x86: Add support for 'rdrand'

This should address #1 and #15 I am writting the rest of the patches to send to gentoo-dev as of now.

Thanks!


Internal use of axios causes error inside Cloudflare Workers

Describe the bug
I am trying to use the client inside a Cloudflare Worker and I get an error as follows:
TypeError: adapter is not a function
    at dispatchRequest (index.js:35781:14)
    at Axios.request (index.js:36049:19)
    at Function.wrap [as request] (index.js:34878:20)

Seems to be a common problem as the way Axios checks for XHR breaks in CF workers which is a reduced node environment:
https://community.cloudflare.com/t/typeerror-e-adapter-s-adapter-is-not-a-function/166469/2
Recommendation is to use fetch instead.
To Reproduce
Try to use API in a cloudflare worker
Code snippets
No response
OS
Windows 10
Node version
Node v16
Library version
openai v3.1.0

I got the same error, because of axios adapters used XMLHttpRequest and node http, but workers used fetch to send request, so we should specify a fetch adapter, I found a package @vespaiach/axios-fetch-adapter, you can refer to the following code
const { Configuration, OpenAIApi } = require("openai");
+ const fetchAdapter = require("@vespaiach/axios-fetch-adapter")

const configuration = new Configuration({
  apiKey: process.env.OPENAI_API_KEY,
});
const openai = new OpenAIApi(configuration);

const response = await openai.createCompletion({
  model: "text-davinci-003",
  prompt: "Say this is a test",
  temperature: 0.9,
  max_tokens: 150,
  top_p: 1,
  frequency_penalty: 0.0,
  presence_penalty: 0.6,
  stop: [" Human:", " AI:"],
}, {
+  adapter: fetchAdapter
});

Import
import { Configuration, OpenAIApi }  from 'openai'
+ import fetchAdapter from '@vespaiach/axios-fetch-adapter'

const configuration = new Configuration({
  apiKey: process.env.OPENAI_API_KEY,
});
const openai = new OpenAIApi(configuration);
const response = await openai.createCompletion({
  model: "text-davinci-003",
  prompt: "Say this is a test",
}, {
+   adapter: fetchAdapter
})

Think you should ditch axios in favour of using fetch directly instead.
Either use node-fetch, undici or global fetch (NodeJS v18 provides fetch built in)
using fetch instead means it would be more functional inside of service worker, deno, bun.js and any other env. it would be more cross compatible.
also form-data is now a piece of legacy and more proper, spec'ed FormData is available to use.
When logging anything from response.data then it dumps way too much unnecessary information that cluters the hole terminal

Looks like this was resurfaced in #47 and I am guessing it will be fixed if / when #45 is merged.

would love to see this fixed — it's a blocker for using this library in Cloudflare, and as other comments have pointed out, there is no reason to use axios when fetch is widely supported

This is fixed in our upcoming v4! Please give it a try on Cloudflare Workers and let us know if you run into any issues.


Convert Amigaguide docs to Markdown for online use

Depends on github.com/EEC-Developers/EEC/issues/36

The AG2TXT utility that came with AmigaE v3 demo version can be converted to an AmigaGuide to MarkDown converter. I don't expect monospace layouts to work correctly but titles, headings and subheading styles should work for E documentation. GitHub MarkDown supports tables if possible to make columns work.
The main thing is translating links. Any page that links from the main menu will become a separate MarkDown file. The link format becomes [text title](targetfile.md) where targetfile.md is an external, single-page MarkDown file.


Add support for the hipFuncGetAttributes interface.

This adds support for hipFuncGetAttributes but, more profoundly, percolates the whole amd_kernel_code_t header structure and makes it accessible from a Kernel_descriptor. This should help with a number of other APIs. Note that this is not fully symmetric with NVIDIA - theirs works on the device side, whereas ours does not yet do so. One of the HIP experts should actually carefully review the mapping from CUDA attribute to HIP attribute, the currently proposed one is minimalistic.

@bensander could you please provide details about what you mean by "output from a few systems" for review? Is there a particular test setup that you have in mind? Note that as things are today for some function foo() the attributes would essentially be the same on gfx8 or gfx9, modulo register allocation differences between the two, since the limits are roughly the same.


Fix typo in docstring for make_csv_dataset_v2

replace the proper variable name in given example code

Hi @gadagashwini , please don't use a "Update " commit message. Instead, please try to follow proper commit etiquette


Analytics with Push Notifications - Missing Address exception

Describe the bug
Analytics Plugin uses Pinpoint SDK under the covers. Pinpoint SDK has a requirement for the developer to register the device token with pinpoint when enabling push notifications.
To Reproduce (To be tested)
Steps to reproduce the behavior:

Use Analytics Plugin
Enable push notifications
enable debugging logs
see that there is the Missing Address issue

Expected behavior
One option is to use the escape hatch to get the underlying pinpoint client, and use it to call interceptDidRegisterForRemoteNotifications(withDeviceToken) to fix the issue.

this will be fixed with https://github.com/aws-amplify/aws-sdk-ios/pull/2455 and then need to ensure Analytics plugin takes on the dependency of the pinpoint SDK with released fix


is javatuples compatible with java 11?

Hi folks,
I tried to find this in documentation in this repo as well in your website, but I wasn't able to do it. I would like to know if this project could be used with java 11.
Thank you

I don't see any reasons why it should NOT work with Java 11

Thank you. I have been using for a while, no issues detected
José Luis Larroque
BCS - UNLP
El mar, 24 ago 2021 a las 9:59, mfnalex @.***>)
escribió:

I don't see any reasons why it should NOT work with Java 11
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/javatuples/javatuples/issues/15#issuecomment-904618648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHG742GSQG3MGJMLPWI5DT6OJULANCNFSM46J4DDQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Any plan to add explicit Java modules? CONTRIBUTING.markdown claims you're aiming for Java 5.0 compatibility but that seems excessive.


Revisit FileProviders

Chatted with @lodejard and he had some thoughts about how we can improve these.

Support IFileProvider abstraction directly
Revisit how we expose BaseFilePath

Make sure to Address https://github.com/aspnet/Configuration/issues/323 as part of this issue

Related existing issue: https://github.com/aspnet/Configuration/issues/183.

30e59f1190e01a9ae0c2fae4022af5ba3ca2eafd


Missing 'pytest' dependency

I tried the following sequence:

Build the polytracker image:

$ docker build -t trailofbits/polytracker .
...
[+] Building 42.0s (20/20) FINISHED

Ceated a new virtual env:

$ python -m venv poly_venv
$ source poly_venv/bin/activate

Install developer version of polytracker

$ python -m pip install -e .

Tried to run the polytracker image:

$ polytracker docker run
Traceback (most recent call last):
  File "/Users/.../poly_venv/bin/polytracker", line 33, in <module>
    sys.exit(load_entry_point('polytracker', 'console_scripts', 'polytracker')())
  File "/Users/.../poly_venv/bin/polytracker", line 25, in importlib_load_entry_point
    return next(matches).load()
  File<EMAIL_ADDRESS>line 86, in load
    module = import_module(match.group('module'))
  File<EMAIL_ADDRESS>line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/Users/.../polytracker/__main__.py", line 16, in <module>
    import pytest
ModuleNotFoundError: No module named 'pytest'

Are we missing an explicit dependency on 'pytest'?

This is already solved by 782ca52d1cec252a1ae6858a671e00730feac072.


Proposal: preImport loader hook

A preImport hook can take the place of the async use cases for having an async resolver hook by allowing any async work to be done upfront before triggering the further pipeline steps. For example, loading an import map could be an async operation prior to synchronously using that import map in resolution (which is exactly what the browser does).
Ultimately, the goal would be that by covering these needs, this should allow for a synchronous core resolver which would enable unification with browser resolution.
The initial hook PR would not deprecate the resolver yet, and could be released to get feedback on this first, before following up with a subsequent async resolver deprecation.
There is a basic draft API in https://github.com/nodejs/node/pull/43245, with the following documentation:
preImport(specifier, context)
* `specifier` {string}
* `context` {Object}
  * `conditions` {string\[]} Resolution conditions of the current environment,
    as defined for the `package.json` imports and exports fields
  * `dynamic` {boolean} Whether this import is a dynamic `import()`
  * `importAssertions` {Object}
  * `parentURL` {string|undefined} The module importing this one, or undefined
    if this is the Node.js entry point

The preImport hook allows for tracking and asynchronous setup work for every
top-level import operation.
The preImport hook is called for each top-level import operation by the
module loader, both for the host-called imports (ie for the main entry) and for
dynamic import() imports. These are distinguished by the dynamic context.
All preImport hooks for all loaders are run asynchronously in parallel,
and block any further load operations (ie resolve and load) for the module graph
being imported until they all complete successfully.
Multiple import calls to the same import specifier will re-call the hook
multiple times. The first error thrown by the preImport hooks will be directly
returned to the specific import operation as the load failure.

export async function preImport (specifier, context) {
  if (context.topLevel)
    console.log(`Top-level load of ${specifier}`);
  else
    console.log(`Dynamic import of ${specifier} in ${context.parentURL}`);
}

This is an interesting idea! I have a couple questions:

All preImport hooks for all loaders are run asynchronously in parallel,
and block any further load operations (ie resolve and load) for the module graph
being imported until they all complete successfully.

Is this effectively a Promise.all() or Promise.race()? Also, why? I'm a little confused by why they should run in parallel.

In your example, you have if (context.topLevel), but topLevel is not in context currently or in your proposed additions. What does it mean? I presume top-level await, but that's what dynamic intends to identify, no?

I'm a little concerned by the pre prefixes: I already find globalPreload confusing (it's effectively a “setup” step). I think if we introduce this new hook, we should re-visit the globalPreload name (especially because it does not behave like the other hooks).

Is this effectively a Promise.all() or Promise.race()? Also, why? I'm a little confused by why they should run in parallel.

It's a Promise.all, the reason being that is the most performant design when we don't want to unnecessarily serialize to slow down imports. If two loaders both want to do fs / network / other async operations when a new import is initiated, there's no reason they need to block eachother.

In your example, you have if (context.topLevel), but topLevel is not in context currently or in your proposed additions. What does it mean? I presume top-level await, but that's what dynamic intends to identify, no?

Ahh thanks for spotting the issue in the example, that should be context.dynamic yes. I've gone back and fourth on the wording to get something clear. A top-level import is basically an import which will run the ECMA-262 top-level Evaluation function - https://tc39.es/ecma262/#sec-moduleevaluation. Not all modules go through a whole graph execution operation (eg most dependencies). topLevel is perhaps more descriptive than dynamic, but both likely need clarification. I have a better definition in the current readme update I'll add to the PR now.

I'm a little concerned by the pre prefixes: I already find globalPreload confusing (it's effectively a “setup” step). I think if we introduce this new hook, we should re-visit the globalPreload name (especially because it does not behave like the other hooks).

My preference would have been to just call it the import hook, but export function import() isn't supported in ECMA-262 unfortunately. I'm open to alternative names, eg beforeImport or importHook or prepareImport etc.
Yes, both globalPreload and preImport are effectively non-chainable hooks which can run without blocking other hooks. They fall under a different parallel hook model. In the loader documentation it could be worth eg explicitly documenting the "hook type" of each hook something like Hook Type: Sync Chained or Hook Type: Async Parallel, and there may also be other variants in future.

Closing in favor of https://github.com/nodejs/loaders/pull/89


Error: Cannot prepare tests due to an error.

I am getting the following error while doing mostly the same as in the tutorial/example.
Am I still doing something wrong?

Starting http-server
Running tests (see command in output (3.):

import { Selector } from "testcafe";
import { Config } from "./testcafe.config";
import percySnapshot from "@percy/testcafe";

fixture(`Intro screens test`).page`${Config.baseUrl}`; // base Url is http://localhost:8080

test("Finish intro screens", async (t) => {
  const nextButton = Selector("a").withAttribute("role", "button").child().withText("Weiter");
  const websiteText = Selector("html").textContent;

  const titleForIntro1 = "Willkommen bei der CovMap";

  await t.expect(websiteText).contains(titleForIntro1);
  await percySnapshot(t, "Final Site");
});

Percy Fails

PS C:\Develop\GitHub\CovOpen\CovMapper> npm run percy

><EMAIL_ADDRESS>percy C:\Develop\GitHub\CovOpen\CovMapper
> percy exec -- testcafe chrome testcafe/*.spec.js

[percy] Percy has started!
[percy] Created build #18: <redacted>/7450300
[percy] Running "testcafe chrome testcafe/*.spec.js"
 Running tests in:
 - Chrome 86.0.4240.75 / Windows 10

 Intro screens test
[percy] Could not take DOM snapshot "[object Object]"
[percy] Error: Cannot prepare tests due to an error.

Cannot implicitly resolve the test run in the context of which the test controller action should be executed. Use test function's 't' argument instead.
 √ Finish intro screens

 1 passed (4s)
[percy] Stopping percy...
[percy] Finalized build #18: <redacted>/7450300
[percy] Done!

If you more context is needed, this is the branch I am working on: https://github.com/CovOpen/CovMapper/tree/chore/percy-integration/testcafe

Hey @DanielHabenicht! Thanks for the issue -- it looks like you're using the latest beta version of this SDK. The docs for how to use the latest (beta) version can be found here: https://github.com/percy/percy-testcafe#usage There are a lot of big changes made to the SDK. One being the first argument to percySnapshot is now the name (and no longer the test instance).
You'll want to update your test to remove that first arg:
test("Finish intro screens", async (t) => {
  const nextButton = Selector("a").withAttribute("role", "button").child().withText("Weiter");
  const websiteText = Selector("html").textContent;

  const titleForIntro1 = "Willkommen bei der CovMap";

  await t.expect(websiteText).contains(titleForIntro1);
  await percySnapshot("Final Site");
});

The docs on docs.percy.io haven't been updated yet, you'll want to refer to the README for setup & config.

Thanks for the lighting fast feedback.
Unfortunately your solution is bringing me back to #4 but this time if changed to import * as percySnapshot from ... Typescript errors:
This expression is not callable.
  Type 'typeof import("c:/Develop/GitHub/CovOpen/CovMapper/node_modules/@percy/testcafe/types/index")' has no call signatures.

So it looks like we inadvertently released the beta on the latest channel which is why you accidentally found yourself on the beta following the docs. I've sense deprecated the first beta, released a new "previous" version to be tagged as latest, and now the new beta.2 lives on the @next channel.
Feel free to continue using the beta to help us vet out any bugs, but now you are able to install 0.2.1 and follow the guides on the site along with not having to install the new @percy/cli.
Back to the beta discussion, those types are found here and look to be valid as well as the type tests are passing without issue. Curious what might be going on to cause those type issues? 🤔

I have looked into it a bit but I don't get it.

@percy/testcafe is imported fine, but Typescript transpiles it with a default function.
This has something to do with https://www.typescriptlang.org/tsconfig#esModuleInterop and that my project is using     "module": "esnext", and yours is using the default tsconfig, thus     "module": "commonjs",. I have already sunken to much time into it and will try the 0.2.1

Baaam, made it. So it seems that testcafe has its own tsconfig.json which leads to ignoring my tsconfig.json.
Specifying my tsconfig.json in the testcaferc.json solved the problem:
{
  "tsConfigPath": "./tsconfig.e2e.json"
}

The key is to include esModuleInterop like so:
{
  "compilerOptions": {
    "esModuleInterop": true
  }
}

As this is an extension solely for testcafe specifying a tsconfig.json for this project which is compatible with the tsconfig.json of testcafe might also solve this problem.

Back to the error from the beginning :(

I think I answered the map question via support -- is that right? :D I want to double check. If not send over a build link and we can take a closer look

yep, you did :) Thx again.
Any idea how to investigate the error?

Hello. I am getting the same error as in title, from a very plain setup with the latest downloads.
I am really hoping to use your implicit test controller, because our large project has a lot of Testcafe scripting with an implicit controller. We can't rewrite it all in PercyScript.
Anyway: to spell it out:  in a completely new folder, I did npm install of testcafe, then percy then
npm install --save-dev @percy/cli @percy/testcafe@next      as in your instructions.
My test script is exactly yours, except I changed the URL and one selector:
import percySnapshot from '@percy/testcafe';

fixture('MyFixture')
    .page('https://my url here/');

test('Test1', async t => {
    await t.typeText('#my selector', 'XYZ');
    await percySnapshot('TestCafe Example');
});

I run it with    npx percy exec -- testcafe chrome test-vr-2.js
and I see
[percy] Could not take DOM snapshot "TestCafe Example"
[percy] Error: Cannot prepare tests due to an error.

Cannot implicitly resolve the test run in the context of which the test controller action should be executed. Use test function's 't' argument instead.

Thanks. Dave

Hello. I am getting the same error as in title, from a very plain setup with the latest downloads.
I am really hoping to use your implicit test controller, because our large project has a lot of Testcafe scripting with an implicit controller. We can't rewrite it all in PercyScript.
Anyway: to spell it out:  in a completely new folder, I did npm install of testcafe, then percy then
npm install --save-dev @percy/cli @percy/testcafe@next      as in your instructions.
My test script is exactly yours, except I changed the URL and one selector:
import percySnapshot from '@percy/testcafe';

fixture('MyFixture')
    .page('https://my url here/');

test('Test1', async t => {
    await t.typeText('#my selector', 'XYZ');
    await percySnapshot('TestCafe Example');
});

I run it with    npx percy exec -- testcafe chrome test-vr-2.js
and I see
[percy] Could not take DOM snapshot "TestCafe Example"
[percy] Error: Cannot prepare tests due to an error.

Cannot implicitly resolve the test run in the context of which the test controller action should be executed. Use test function's 't' argument instead.

Thanks. Dave


remove unused sweep hash function

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@73e7396). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #111   +/-   ##
=======================================
  Coverage        ?   86.83%
=======================================
  Files           ?       43
  Lines           ?     2310
  Branches        ?        0
=======================================
  Hits            ?     2006
  Misses          ?      304
  Partials        ?        0

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


Models will not update

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
16.7.0
Amplify CLI Version
10.6.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
If i update my models, it does not update for some reason. I changed some fields in my model and pulled it, but whenever i saved an instance of it it would ONLY create the fields that were there before.
My code:

The result:

(the problem isn't with the variables, even if i replaced all the variables with just a hello string, it wouldnt save it).
I tried making a new model altogether, but even after pulling multiple times it did not recognize it.
(Post2 is the old model)

If i look at my schema it shows all the update models. Please help i dont know what to do.
Expected behavior
I expected the models to be updated.
Reproduction steps
I don't know if this problem is only for me or not, only way to reproduce i know is to create new models and pull.
Project Identifier
8741d2665676fac5a5554da0cf079d3b
Log output

# Put your logs below this line

zsh: no such file or directory: issue-date

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

yeah, I tried that, it didn't do anything. My local files will not update

it says this:

and the model is updated if i check it there. But my local files wont update, so i cant use any of them

basically, my graphql schema has changes, but if i run amplify push, it says no changes. That's the heart of the problem

any suggestions?

Hi @Arnav7501, Can you please re-try after adding a blank space in the schema file?

Hi @Arnav7501 were you making changes and then running amplify pull? If so, that would overwrite your local files with the schema that was most recently pushed. If you ran amplify push after pulling, there wouldn't be any changes to push because the local files are all now up to date and any changes have been lost. Try making your changes to your schema again, then run amplify status to see if the changes are detected. If they were, run amplify push. Let us know if that helps.

Nevermind, i just cloned a environment and pulled that one, and my models updated, so no large harm done i guess. I appreciate the quick responses

I am also having this issue currently, All the changes i made were from the amplify studio and pulling it did not update the local schema.js. what could be wrong?


How to resolve Package X is referenced though multiple groups

Hi,
I am looking into groups in order to speed up new package installations/updates. According to docs I can update only one group. Trying to migrate my huge dependencies file I spitted dependecies per source. However when paket install i get

Package System.Runtime.CompilerServices.Unsafe is referenced through multiple groups in SomeProject  (inspect lockfile for details). To resolve this warning use a single group for this project to get a unified dependency resolution or use conditions on the groups.

I fail to see how to efficient resolve such warnings? Should I create a new group containing only the packages for this project and assign them from there? Wouldn't that be a nightmare support?  my strategy up to now is to share the same dependecies for all projects and would like to keep it like this. Also I fail to see how a group condition may applied at nothing is on the docs.
Any pointers much appreciated

@apobekiaris Did you come up with a solution for this?
Ran into it trying to figure out how should deal with projects that need different versions of certain specific things and reference a common class library in the solution, and as you say seems a maintenance nightmare to explicitly list all the common stuff in every group.

unfortunately no shame to the power will lose at some point my current setup would be impossible to scale and was hopping to treat that with groups, but no idea how

I have the problem that i have a group with some packages which are used by analyzers.
They need to use different versions of some packages because visual studio uses old collections apis internally.
This gives me a about 100 warnings and i don't really know how to get away from this.
Obviously i don't want analyzers to influence what versions of packages i can use in my project,, which is why i have these in a separate group with copy_local: true. That seems to work fine, but yeah, anoying warnings.
I wish you could disable these warnings.


Xcode 7 build warnings

Getting the following build warning with Xcode 7 -
/MMWormhole/Source/MMWormholeFileTransiting.m:36:17: Method override for the designated initializer of the superclass '-init' not found

I have a fix for this on my fork at https://github.com/HiddenJester/MMWormhole. It's nothing fancy, you just need to provide some sort of implementation of init in MMWormholeFileTransiting.m. My just prints a message saying to not call it and then returns a wormhole that isn't really going to work (because it lacks a valid App Group Identifier).
I could submit a pull request if desired, but I've already got an open PR (see https://github.com/mutualmobile/MMWormhole/pull/53 ) so I wasn't in a hurry to submit this one.

Thanks, Jester for the prompt reply - It would be great if this fix made it's way into the pod.

Hey guys, sorry for the delayed response. I'm putting the finishing touches on an Xcode 7 update that will address this. Hoping to have that wrapped up in the next few days.
Thanks,

Conrad

Hey guys. This will also go in as part of 1.3.0. Thanks very much for the issue/PR!

Awesome! Thanks, Conrad.


Add an option to avoid lazy loading

Hello, and thanks for your amazing work.
I tried graphql-jpa on very simple projects and it worked simply, out-of-the-box, which is really neat !

GraphQL is very good for the client to tell "I want that piece of information, and only that", which, translated into the ORM-world could mean : "I want that entity, this relation to that other entity, but not this other one".
What would be awesome, would be to add an ability, when creating the GraphQLQuery, to generate an "adaptative" query, using FETCH JOIN to fetch all the entities needed at once, avoiding lazy loading when sending the response to the client.
Not sure how to implement it, but by parsing the client's query (and the field he is asking for), and analyzing the annotations on the fields of the entity returned, I guess it should be possible.
What do you think ? Is this something you're thinking about ? Working on ? Is it too difficult ? Out of scope ?
Thanks a lot !

Currently it seems all the to-one relationships are eagerly fetch joined. This could be a point to implement to-many fetching as well. Keep in mind that fetch joining multiple to-many relationships can cause all sorts of funky behaviour, see also: http://blog.eyallupu.com/2010/06/hibernate-exception-simultaneously.html .  It just won't work with unindexed lists. Also, the cross product may become quite large and sometimes its just more efficient to run a couple of queries instead. Another idea could be to provide an EntityGraph to the query run by graphql-jpa or to use any of the fetch strategies that your JPA provider provides.


Strange MiscellaneousScoreResultEventDictionary data.

I parsed a replay file to extract the map objectives data, and I know it will be stored in the player's ScoreResult -> MiscellaneousScoreResultEventDictionary.
But I found there are some strange data:
The map  is Volskaya Foundry, and the replay parsed with no error.
But the MiscellaneousScoreResultEventDictionary data are:
		"MiscellaneousScoreResultEventDictionary": {
			"TeamTakedowns": 4,
			"Tier1Talent": 1,
			"Tier2Talent": 1,
			"Tier3Talent": 2,
                        ...
			"DragonNumberOfDragonCaptures": 0,
			"DragonShrinesCaptured": 0

They are  the map objectives data of the Dragon Shire??
The same thing happed again when I parsed a Hanamura replay, this time the MinesSkullsCollected from Haunted Mines showed up.

Can you upload/attach a replay file(s)?

replays.zip
Replays uploaded.
The replays are from chinese region, I don't think this will cause the issue.

That is a bit odd but I wouldn't think anything of it.  It's probably something the developers forgot or didn't care to remove.  The values for these are '0' as they should be.  It's just odd that they are included on a map they don't exist on.


Cleanup of vkcubepp

Fixes #421 Fixes #422 Fixes #409 Fixes #452

CI Vulkan-Tools build queued with queue ID 6287.

CI Vulkan-Tools build # 631 running.

CI Vulkan-Tools build # 631 failed.

CI Vulkan-Tools build queued with queue ID 6339.

CI Vulkan-Tools build # 632 running.

CI Vulkan-Tools build # 632 passed.

Should malloc and free be replace with new and delete?

CI Vulkan-Tools build queued with queue ID 7896.

CI Vulkan-Tools build # 633 running.

CI Vulkan-Tools build # 633 passed.

CI Vulkan-Tools build queued with queue ID 7908.

CI Vulkan-Tools build # 634 running.

@ziga-lunarg @lunarpapillo Thank you both for reviewing, found probably a dozen real mistakes and inconsistencies.

Should malloc and free be replace with new and delete?

Turns out I missed a spot! I didn't realize this code was there, I moved it over to using the vulkan.hpp functions that return vectors in a single call instead of the 2-call pattern.

CI Vulkan-Tools build # 634 failed.

CI Vulkan-Tools build queued with queue ID 7920.

CI Vulkan-Tools build # 635 running.

CI Vulkan-Tools build # 635 passed.

CI Vulkan-Tools build queued with queue ID 17167.

CI Vulkan-Tools build # 658 running.

CI Vulkan-Tools build # 658 passed.


Updated Variant Projection Schema, changed Field classes to objects

This allows Projections to be used for Variant and VariantCallingAnnotations

@erictu can you run ./scripts/format-source? That's why the build is failing. I will merge when fixed.

@AmplabJenkins is down, so I verified this manually (I've dropped @shaneknapp an email) and merged as https://github.com/bigdatagenomics/adam/commit/5c82d9476450264dfda5cbd2c2cfe0bcaba591df.

jenkins is back up...  looks like there was a power event in the colo and
all of the workers (which aren't on UPS) went down.
On Sat, Jun 27, 2015 at 10:09 AM, Frank Austin Nothaft <
<EMAIL_ADDRESS>wrote:

Closed #720 https://github.com/bigdatagenomics/adam/pull/720.
—
Reply to this email directly or view it on GitHub
https://github.com/bigdatagenomics/adam/pull/720#event-342020661.


[Feature][config-ui] blueprints service pack 2.0

Description
Apply post-development tasks, bugfixes and outstanding features to the Blueprints V.0.12.0 Release.

Feature #2578
Bug #2549
Feature Setup & Enable All Connections Section (ON-HOLD Stage III ?)
Add/Update Blueprint Workflow Validation Rules
Update Data Entity Type Associations
CSS & Styling Updates
Code Cleanups & Linting

Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

hi @e2corporation , can we close this issue now ?

Closing already resolved @klesh


Adding coveralls

Just did this to another repo, thought it would be nice to include here.
@oconnor663

Changes Unknown when pulling 0d572a321c49c38110de4714eaa2853bd08ca5bb on coveralls into ** on master**.

👍 👍


SHARD-990: verifyGlobalTxReceipt unit tests

Linear: https://linear.app/shm/issue/SHARD-990
Summary: unit tests for verifyGlobalTxReceipt method

And not just that we've to change command in package.json as npm run start command expects server.js to be inside build directory

Please keep the old flow and inside the same directory where it used to put the build before. Thanks.


Files hangs

Description
Files becomes totally unresponsive.
Need to close with Task Manager.
Steps To Reproduce
Sorry, unable to determine when or why this happens.
Simply in the middle of working with Files (no specific actions that I am aware of)  it stops responding - no selection, no resize, no close, no ....
This has happened a few times over the past few days.
Steps to fix
Fix Files hanging
Files Version
<IP_ADDRESS>
Windows Version
10.0.22623.1325
Log file
debug.log

Were you right clicking a file when it happened?

On some (most?) occasions - yes.
I think that there were others where I wasn't.
Sorry for the lack of detail.
Thanks for the app & support.
On Wed, Feb 22, 2023 at 4:48 PM Yair @.***> wrote:

Were you right clicking a file when it happened?
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/11408#issuecomment-1440170866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6BXXEQWF3DBBRWSES6VKALWYYRLPANCNFSM6AAAAAAVD7RRLQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It could be multiple things, but I think it's most likely the context menu, we're currently testing some changes in the preview build, so this is to be expected. If you notice it happens when doing something else, please open an issue or add a comment here and I'll reopen the issue.

Hung again
Version <IP_ADDRESS>  !!!!
Definitely NOT on right click

Was it when extracting a zipped archive?

No.
I just clicked (left) on a file.
Sorry, don't remember what type.
On Thu, Feb 23, 2023 at 6:27 PM Yair @.***> wrote:

Was it when extracting a zipped archive?
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/11408#issuecomment-1442071957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6BXXETHEWSLPSJOL626PR3WY6FWTANCNFSM6AAAAAAVD7RRLQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Background Image in Hero Doesn't Display in Outlook 365

Describe the bug
The background image in mj-hero doesn't display in Outlook 365,the fallback color does not display, and padding is ignored.
To Reproduce
Steps to reproduce the behavior:

Create fluid-height hero in MJML
Test by sending through Putsmail
Open in Outlook 365

Here is the MJML used:
 <mj-hero mode="fluid-height"       background-width="650px"       background-height="700px"       background-url="https://s3.amazonaws.com/production.campaign.talemetry/uploads/emails/images/15632/content_73069_Email_Update_4.jpg"       background-color="#771b61"       padding="460px 20px 0px 20px"       >     <mj-text>
UPMC Careers News

Your monthly update on featured jobs, events, and other happenings in home health at UPMC.
</mj-text>     </mj-hero>
Expected behavior
Render like this:

MJML environment (please complete the following information):

OS: [e.g. MacOS]
MJML Version [e.g. 4.2.0]
MJML tool used [e.g MJML App]

Email sending environment(for rendering issues):

Putsmail]

Affected email clients (for rendering issues):

Outlook 365
Windows

Screenshots

Can you try with a png background image to see if it does anything ?

Hi iRyusa, thanks! I tried it with the new version and the image displayed, but the padding was still ignored.

I haven't tried the PNG yet but I'll give it a go.

PNG was the same result

Padding left & right are applied twice to the right: it's a bug within outlook render engine. There's no real fix for that sadly. I'm closing this then

Actually I've got a work-around. Take the right and left padding off mj-hero and add it to the text instead. But I would still consider that an issue with MJML that needs to be addressed, right?

That something we cannot fix with vml & nested table inside it. We did tried everything, even mso-alt-padding does behave the same.


Adding Climb-Up on staircases

Swapped climb and climb-up so you do not have to right click on staircase to go up.

Hey, you'll have to reposition your { } braces in the style that the file started with, since not putting them on their own line is a Checkstyle failure. Nice feature though.

Now just un-double the doubled indents in MenuEntrySwapperPlugin.java and it's ready. The green markers show where you've added an extra tab.

Might be neat to swap climb up/down conditionally based on the last plane change. If last change was down, swap climb down. If last change was up, climb up.

The conditional would break whenever you are go down or up twice however, such as in Lumbridge bank or warrior's guild.