Animate Text Layer

Is it possible to change the text of a Text Layer?
Example:
text = new ios.Text
	text: 'Initiating...'
	font: 'Vaud'
	fontSize: 20
	textAlign: 'center'
	color: '#fff'
	fontWeight: 400
	constraints:
		leading: 16
		top: 350
		width: 320
	opacity: 0

text.states.add
	one:
		text: "Communicating with server..."

	two:
		text: "Completing upload..."

Yeah, you change the layer's html. In the last update, I pushed a change that when you modify the html by default, it'll resize the layer to the new string.
I'm not sure it'll work with states. I may because it's just working with the HTML property.


Array or List in query string does not get parsed #7712

After resolving conflicts.
35955df

Hi @dougbu
I think now you can see my changes.

Hi @dougbu ,
I added a test case.

welcome @dougbu, i did 50% work. remaining with your help. thank you very much @dougbu.

I think that this broke my code when I updated to SDK 2.1.403 and I have been pulling my hair out trying to determine why.
Here is my controller:
[ApiController]
public class ProductsController : ControllerBase
{
    public async Task<List<ProductViewModel>> PutMany([FromBody]List<ProductUpdateViewModel> products)
    => await _genericCRUDService.UpdateRangeAsync(products);
}

I think when you guys did this: https://github.com/aspnet/Mvc/commit/5e20c31#diff-c693720b853e696ccec4442fb4f072a3R259
All my controllers that accept a List<ComplexType> now get treated as if they are NOT complex types.
I found that applying [FromBody] fixes my code. I thought that using [ApiController] attribute was supposed to prevent me from needing to do that kind of think everywhere.

@VictorioBerra we're tracking the regression via https://github.com/aspnet/Mvc/issues/8536


Provide example for windows servers

It would be good to provide an example for windows servers here too.
For instance the script generator in azure for this actually does not create the first task to validate the azure agent is downloaded so i had to refer to this page but than needed to refactor into the windows equivalent.

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

ID: a88d4cbe-fe02-3ec4-d952-e2288e68658d
Version Independent ID: c2a1531e-24ad-b7f5-6dea-58c26959cda0
Content: Connect machines at scale using Ansible Playbooks - Azure Arc
Content Source: articles/azure-arc/servers/onboard-ansible-playbooks.md
Service: azure-arc
Sub-service: azure-arc-servers
GitHub Login: @johnmarco
Microsoft Alias: johnmarc

Oh just realized the windows tasks are in there just further down, my bad.
Just odd that the onboarding script generator is missing the first task for windows.

Closed


Line numbers completely wrong in UI test report

Describe the bug

I'm using the 0.15.1 release of both vitest and @vitest/ui and for several releases now I've noticed that the console output reports the correct line number but surprisingly the web UI is completely wrong. No idea what could cause this but the enclosed image is the same error.
Reproduction
clone @antfu/vite-plugin-md and then cause a break in any of the tests to see this behavior. I suspect you could get the same results with any TS/VueJS project but that's speculation.
System Info
System:
    OS: macOS 12.4
    CPU: (28) x64 Intel(R) Xeon(R) W-2170B CPU @ 2.50GHz
    Memory: 7.84 GB / 128.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.15.0 - /usr/local/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 102.0.5005.115
    Firefox: 101.0
    Safari: 15.5
  npmPackages:
    @vitejs/plugin-vue: ^2.3.3 => 2.3.3
    @vitejs/plugin-vue-jsx: ^1.3.10 => 1.3.10
    vite: ^2.9.12 => 2.9.12
    vitest: ^0.15.1 => 0.15.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It's working in Node, because we are processing it:
https://github.com/vitest-dev/vitest/blob/b8590f159d42d7a2ac8d66b01efcb9d9fcc8d0b4/packages/vitest/src/utils/source-map.ts#L24
Maybe we need to do it before sending the error to UI.


test_functions.R

Two notes on the API function tests (code in the /tests folder):

These function checks are based around the expected outputs of given calls, but those outputs will change depending on the Symbiota2 database the user is calling. I'm using the outputs from the development database as the comparison to check against (which seems reasonable), but I'm wondering if this is something to worry about? Or at least, if there's a way we can make users more aware of this requirement.

The tests as they stand now are a little sparse/repetitive--mostly, I'm just checking the length() of what's being outputted, and making sure that it's a list. These can become more detailed if needed, but for now I feel they're distinctive enough.

When it comes to tests, honestly you're above 98% of the population simply by having them. I think these are good, though.
We will fix the database problem when we write the code to allow users to connect to other databases; these ones will only run against the development server and so all will be well.
Good job, Austin!!!


updating typos for security/lab01/index.rst file

update typos:
-at the beginning under Lab 1 first paragraph second sentence you need "is" after "This"
-Task 7 Under Step 2 "Browse" is spelled wrong

I'm closing this out since this currently has a merge conflict. if there's still an issue please submit a new PR.


I couldn't receive Network Inspection on my app

Hi
I am completely newbie in this section . I wanted to get network inspection on my android app , nut I couldn't . How I can do it properly ?
This is my activity code:
`public class MainActivity extends AppCompatActivity {
OkHttpClient client;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    client = new OkHttpClient.Builder()
            .addNetworkInterceptor(new StethoInterceptor())
            .build();

    AsyncTask.execute(new Runnable() {
        @Override
        public void run() {
            try {
                String ali = runLoad("https://www.telewebion.com/live/tv3");
                Log.i("taggg",ali);
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
    });

}

public String runLoad(String url) throws IOException {
    Request request = new Request.Builder()
            .url(url)
            .build();

    try (Response response = client.newCall(request).execute()) {
        return response.body().string();
    }
}

}`
I would appreciate it if someone could help me on this case . I just got normal data (webpage source) and nothing more .

same here

same,  maybe It happed i upgrade oktthp->4.xx  ,i guess stetho is not compact with okhttp 4， #671

pls fix this bug @longinoa

pls fix this bug @longinoa
okhttp          : "4.5.0",


icewm: 3.4.7 -> 3.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ice-wm/icewm/releases.
meta.description for icewm is: A simple, lightweight X window manager
meta.homepage for icewm is: https://ice-wm.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.5.0 with grep in /nix/store/x5wabxmj027ki585nadqgh342j5ak8zi-icewm-3.5.0
found 3.5.0 in filename of file in /nix/store/x5wabxmj027ki585nadqgh342j5ak8zi-icewm-3.5.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

icewm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x5wabxmj027ki585nadqgh342j5ak8zi-icewm-3.5.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 icewm https://github.com/r-ryantm/nixpkgs/archive/846c76d05c47da7ac69d90af8ca065fe83cc454a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/846c76d05c47da7ac69d90af8ca065fe83cc454a#icewm

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x5wabxmj027ki585nadqgh342j5ak8zi-icewm-3.5.0
ls -la /nix/store/x5wabxmj027ki585nadqgh342j5ak8zi-icewm-3.5.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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

icewm

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge

@NixOS/nixpkgs-merge-bot merge


Replace media_url with url in provider scripts

Fixes

Fixes #1409 by @stacimc
Description

This PR renames audio_url and image_url in the provider API scripts and ImageStore/AudioStore classes to url, which simplifies the code significantly.
Testing Instructions

The CI should pass. The tests have been updated to use url instead of image_url/audio_url
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@obulat Is this PR ready for review or it is a work in progress?

I've rebased it onto the license_info PR, and am going to draft it until that PR is merge. I will run the ingestion for all providers locally after that to check that everything works as expected.

@AetherUnbound, I ran data ingestion locally, and did not get any url-related errors. All but two providers correctly load data. I do get errors in rawpixel (403 response in Airflow, although if I open the link in the browser - it shows results) and iNaturalist (something with local setup in the preingestion tasks).


Mention doesn’t invite the user to a group

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

Version Number: 9.0.49-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @danielrvidal
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1728943849987709
Action Performed:

Create a group
Try to invite a user by mentioning @

Expected Result:
Should have invite them Do nothing options appear.
Actual Result:
No option to invite them
Workaround:
unknown
Platforms:

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

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

Screenshots/Videos
https://github.com/user-attachments/assets/d0b34fd7-fdef-4af2-97df-e995a6c52054
https://github.com/user-attachments/assets/da7815c2-9cfd-4167-99dc-b1895f9af570

Add any screenshot/video evidence

View all open jobs on GitHub

Adding to MEDIUM priority in the Quality project

Reproduced

Edited by proposal-police: This proposal was edited at 2024-09-28 10:38:21 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
When mentioning a user who is not part of a group, the action buttons (Invite/Do Nothing) do not appear.
What is the root cause of that problem?
The expected action buttons should display when a user is mentioned outside of a group.
https://github.com/Expensify/App/blob/652d2ffa1b099f9c5a1f0cdce780792097f736ad/src/pages/home/report/ReportActionItem.tsx#L764-L769
However, the actionableItemButtons array remains empty due to the following condition:
https://github.com/Expensify/App/blob/652d2ffa1b099f9c5a1f0cdce780792097f736ad/src/pages/home/report/ReportActionItem.tsx#L417-L419
This happens because the isActionableWhisper variable is set to false, as indicated here:
https://github.com/Expensify/App/blob/652d2ffa1b099f9c5a1f0cdce780792097f736ad/src/pages/home/report/ReportActionItem.tsx#L207-L208
The root of the issue lies in the backend, where the report action name is not designated as ACTIONABLEMENTIONWHISPER, as required by:
https://github.com/Expensify/App/blob/652d2ffa1b099f9c5a1f0cdce780792097f736ad/src/libs/ReportActionsUtils.ts#L1409-L1415
What changes do you think we should make in order to solve the problem?
We need to investigate the backend logic to identify which validators control the assignment of ACTIONABLEMENTIONWHISPER when a user is mentioned in group.
https://github.com/user-attachments/assets/d734d46a-f3eb-43b0-bcfb-8e6fb6783f52
What alternative solutions did you explore? (Optional)
None at this time.

Hi, Will check this today.

Checking now

I don't think @ugogiordano 's root cause https://github.com/Expensify/App/issues/50798#issuecomment-2439758662 here is correct. When we add a comment, report action is expected to be ADDCOMMENT.
And @muttmuure I haven't seen this feature, does the suggestion come kind of a new conceirge suggestion similar to the below one?

So it sounds like this would be a new feature for groups. I actually think that it's expected for now.
I note that Slack does not add people to your group DM if you @ them. I think most people would prefer it that way, so you can mention someone without notifying them (which is useful in some contexts).
Rooms are different, because they are open collaborative chats, whereas groups are deliberately smaller and invite only. You can still add people to the group via the RHP.
I've responded in Daniel's thread

Not overdue

We're not prioritizing this right now


feat(COMMON,LLD,LLM): Add support for Tron Stake 2.0

📝 Description
Adds the following operation modes to enable Tron Stake 2.0 in Ledger Live (Primarily to use with the Ledger Wallet API).

freeze -> FreezeBalanceV2Contract - To freeze/stake TRX and obtain voting rights (Tron Power) + Bandwidth or Energy
unfreeze -> UnfreezeBalanceV2Contract - To unfreeze/unstake TRX and release the corresponding amount of bandwidth or energy, and voting rights (Tron Power)
unDelegateResource - For cases when a user has delegated resources and wants to unstake an amount larger than what's just "Frozen".
withdrawExpireUnfreeze - To withdraw unFrozenV2 balances and get back the funds after the 14-day unfreezing period has passed.
legacyUnfreeze- To unfreeze legacy (Tron Stake 1.0) TRX, in case a user still has balance frozen with 1.0.

...The above operations and associated balances (frozen, delegatedFrozen, unfrozen, legacyFrozen) are now part of the account balance. Meaning, that they will be part of the historical operations and asset balance on the accounts page. The PR includes minor adjustments to LLD and LLM to be able to display the operations and balance.
❓ Context
We're from StakeKit and we've just released a Ledger Live app that offers users a unified non-custodial staking experience across a wide range of networks and protocols. We're opening this PR because we would like to offer users the possibility to participate in Tron 2.0 staking via our Ledger Live app. We will also open up another PR in the wallet-api repository that enables the new modes. FYI, the DelegateResource operation is out of scope as per our requirements. unDelegateResource has been added in case a user would like to fully unstake their funds through our UI and needs to undelegate the resources before unfreezing them.
✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[x] npx changeset was attached.
[x] Covered by automatic tests.
[x] Impact of the changes:

This PR impacts the portfolio balance and historical transactions of Tron accounts for both LLD and LLM.

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Thanks a lot for your contribution.
A general question: since Tron staking v1 isn't active anymore, wouldn't it make sense to just replace v1 fields and functions with v2 equivalents?

"un/freeze" could just be updated/replaced, no need for additional "un/freezev2"
Not sure about legacy "vote" and "claimRewards", but if unused they should either be removed or updated with v2 equivalents

WDYT?

You're welcome.
Since users can technically still have frozen funds tied to Tron Stake 1.0 we'd like to keep support for unfreeze. We can for sure remove the freeze v1 operation as it's deprecated.
The "vote" and "claimRewards" operation modes are the same for Tron Stake 2.0, so no changes are required.

@haammar-ledger After some thought, I realized it could be beneficial (For UX, translations, etc) to just replace the v1 with the v2 methods and add another operation for "LegacyUnfreeze". Pushing some changes...

@Philippoes I can see you're still working on this PR, just let me know when this is ready and you want us to review again :+1:
You can also set the PR to "draft" then set it as "ready to review" again later if you want.
Thanks!

@haammar-ledger It is ready for review now. I just rebased the PR yesterday to resolve a conflict. 👍
Thank you!

@haammar-ledger Just rebased the branch and fixed a small issue in the transaction status logic, and also updated the phrases in the mobile translations as suggested. Feel free to take a look!

@haammar-ledger Thanks! I've pushed a fix, and the CI should pass now. 👍

@Philippoes One very last test failing :slightly_smiling_face: if you want to have a look
https://github.com/LedgerHQ/ledger-live/actions/runs/7277060700/job/19828256925#step:8:3665
Almost there!

@haammar-ledger Thanks for pointing this out. The failing test is resolved, also added some integration tests for more coverage. Let's give the CI another go! 👍

@Philippoes Congrats on passing the review and the CI tests!
We'll just do a last step of manual QA before merging, please bear with us, this should be done shortly.
Thanks again.


Move core logic out of UTF into its own package

Signed-off-by: Tanner Lewis<EMAIL_ADDRESS>Description
This change splits the core functionality of the UTF package (clients, step-wise framework runner, cluster manipulation logic) into its own package. This will give us greater flexibility in the future with allowing other packages to have this common functionality they will likely need, as well as eliminate a lot of code duplication that could arise such as common rest clients needed by both the UTF and robot tests.
Also included were some minor changes such as Lint fixes, adjusting github action unit tests, etc.
As a side note, the way the UTF had been structured and segregated made it very easy to pull this logic out
Issues Resolved

https://github.com/opensearch-project/opensearch-migrations/issues/61

Testing
Cluster migration core unit tests
(.venv) (10:48:37) local [/Volumes/workplace/opensearch/lewijacn-migrations/opensearch-migrations/cluster_migration_core] -> python -m pytest unit_tests/
================================================================================================================================================= test session starts ==================================================================================================================================================
platform darwin -- Python 3.10.7, pytest-7.2.0, pluggy-1.0.0
rootdir: /Volumes/workplace/opensearch/lewijacn-migrations/opensearch-migrations/cluster_migration_core
collected 104 items

unit_tests/clients/test_rest_client_default.py .........                                                                                [  8%]
unit_tests/clients/test_rest_ops.py ....                                                                                [ 12%]
unit_tests/cluster_management/test_cluster.py ............                                                                                [ 24%]
unit_tests/cluster_management/test_container_configuration.py .                                                                                [ 25%]
unit_tests/cluster_management/test_docker_framework_client.py ...............                                                                                [ 39%]
unit_tests/cluster_management/test_node.py ...........                                                                                [ 50%]
unit_tests/cluster_management/test_node_configuration.py ..                                                                                [ 51%]
unit_tests/core/test_exception_base.py ...                                                                                [ 54%]
unit_tests/core/test_expectation.py .........                                                                                [ 63%]
unit_tests/core/test_framework_runner.py ......                                                                                [ 69%]
unit_tests/core/test_framework_state.py ...                                                                                [ 72%]
unit_tests/core/test_framework_step.py ....                                                                                [ 75%]
unit_tests/core/test_logging_wrangler.py .                                                                                [ 76%]
unit_tests/core/test_shell_interactions.py .......                                                                                [ 83%]
unit_tests/core/test_test_config_wrangling.py .........                                                                                [ 92%]
unit_tests/core/test_versions_engine.py .......                                                                                [ 99%]
unit_tests/core/test_workspace_wrangler.py .                                                                                [100%]

================================================================================================================================================= 104 passed in 0.79s ==================================================================================================================================================

UTF snapshot restore test run
(.venv) (10:49:13) local [~/workplace/opensearch/lewijacn-migrations/opensearch-migrations/upgrades] -> ./run_utf.py --test_config test_config.json
[FrameworkRunner] ============ Running Step: LoadTestConfig ============
[LoadTestConfig] Loading test config file...
[LoadTestConfig] Loaded test config file successfully
[FrameworkRunner] Step Succeeded: LoadTestConfig
[FrameworkRunner] ============ Running Step: BootstrapDocker ============
[BootstrapDocker] Checking if Docker is installed and available...
[BootstrapDocker] Docker appears to be installed and available
[BootstrapDocker] Ensuring the Docker image docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 is available either locally or remotely...
[BootstrapDocker] Docker image docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 is available
[BootstrapDocker] Ensuring the Docker image opensearchproject/opensearch:1.3.6 is available either locally or remotely...
[BootstrapDocker] Docker image opensearchproject/opensearch:1.3.6 is available
[FrameworkRunner] Step Succeeded: BootstrapDocker
[FrameworkRunner] ============ Running Step: SnapshotRestoreSetup ============
[SnapshotRestoreSetup] Creating shared Docker volume to share snapshots...
[SnapshotRestoreSetup] Created shared Docker volume cluster-snapshots-volume
[FrameworkRunner] Step Succeeded: SnapshotRestoreSetup
[FrameworkRunner] ============ Running Step: SelectExpectations ============
[SelectExpectations] Loading Knowledge Base and filtering for relevant expectations
[SelectExpectations] Found 2 relevant expectations.
[FrameworkRunner] Step Succeeded: SelectExpectations
[FrameworkRunner] ============ Running Step: StartSourceCluster ============
[StartSourceCluster] Creating source cluster...
[StartSourceCluster] Waiting up to 30 sec for cluster to be active...
Node source-cluster-node-1 is now active
Node source-cluster-node-2 is now active
[StartSourceCluster] Cluster source-cluster is active
[FrameworkRunner] Step Succeeded: StartSourceCluster
[FrameworkRunner] ============ Running Step: PerformPreUpgradeTest ============
==============================================================================
Tests
==============================================================================
Tests.Common Upgrade Test
==============================================================================
Perform pre-upgrade setup of "consistent-document-count" expectation  PUT http://localhost:9200/sample-index [status:200 request:0.462s]
.POST http://localhost:9200/sample-index/_doc [status:201 request:0.173s]
.POST http://localhost:9200/sample-index/_doc [status:201 request:0.009s]
.POST http://localhost:9200/sample-index/_refresh [status:200 request:0.038s]
.POST http://localhost:9200/sample-index/_count [status:200 request:0.049s]
Perform pre-upgrade setup of "consistent-document-count" expectation  | PASS |
------------------------------------------------------------------------------
Tests.Common Upgrade Test                                             | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Tests                                                                 | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Output:  /tmp/utf/test-results/pre_upgrade/output.xml
Log:     /tmp/utf/test-results/pre_upgrade/log.html
Report:  /tmp/utf/test-results/pre_upgrade/report.html
[FrameworkRunner] Step Succeeded: PerformPreUpgradeTest
[FrameworkRunner] ============ Running Step: CreateSourceSnapshot ============
[CreateSourceSnapshot] Creating snapshot of source cluster...
[CreateSourceSnapshot] Confirming snapshot of source cluster exists...
[CreateSourceSnapshot] Source snapshot created successfully
[FrameworkRunner] Step Succeeded: CreateSourceSnapshot
[FrameworkRunner] ============ Running Step: StartTargetCluster ============
[StartTargetCluster] Creating target cluster...
[StartTargetCluster] Waiting up to 30 sec for cluster to be active...
Node target-cluster-node-1 is now active
Node target-cluster-node-2 is now active
[StartTargetCluster] Cluster target-cluster is active
[FrameworkRunner] Step Succeeded: StartTargetCluster
[FrameworkRunner] ============ Running Step: RestoreSourceSnapshot ============
[RestoreSourceSnapshot] Checking if source snapshots are visible on target...
[RestoreSourceSnapshot] Source snapshot visible to target cluster
[RestoreSourceSnapshot] Restoring source snapshot onto target...
[RestoreSourceSnapshot] Snapshot restored successfully
[FrameworkRunner] Step Succeeded: RestoreSourceSnapshot
[FrameworkRunner] ============ Running Step: PerformPostUpgradeTest ============
==============================================================================
Tests
==============================================================================
Tests.Common Upgrade Test
==============================================================================
Perform post-upgrade assertion of "consistent-document-count" expe... .POST http://localhost:9202/sample-index/_count [status:200 request:0.101s]
Perform post-upgrade assertion of "consistent-document-count" expe... | PASS |
------------------------------------------------------------------------------
Tests.Common Upgrade Test                                             | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Tests                                                                 | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Output:  /tmp/utf/test-results/post_upgrade/output.xml
Log:     /tmp/utf/test-results/post_upgrade/log.html
Report:  /tmp/utf/test-results/post_upgrade/report.html
[FrameworkRunner] Step Succeeded: PerformPostUpgradeTest
[FrameworkRunner] ============ Running Step: StopSourceCluster ============
[StopSourceCluster] Stopping cluster source-cluster...
[StopSourceCluster] Cleaning up underlying resources for cluster source-cluster...
[FrameworkRunner] Step Succeeded: StopSourceCluster
[FrameworkRunner] ============ Running Step: StopTargetCluster ============
[StopTargetCluster] Stopping cluster target-cluster...
[StopTargetCluster] Cleaning up underlying resources for cluster target-cluster...
[FrameworkRunner] Step Succeeded: StopTargetCluster
[FrameworkRunner] ============ Running Step: SnapshotRestoreTeardown ============
[SnapshotRestoreTeardown] Removing shared Docker volume cluster-snapshots-volume...
[SnapshotRestoreTeardown] Removed shared Docker volume cluster-snapshots-volume
[FrameworkRunner] Step Succeeded: SnapshotRestoreTeardown
[FrameworkRunner] ============ Running Step: ReportResults ============
[ReportResults] ======================== SKIPPED EXPECTATIONS =======================
[ReportResults] doy-format-date-range-query-bug
[ReportResults] 	Description: Given 1/ an index created in ES 7.x; 2/ documents with dates uploaded in a yyyy-DDD (day of year) format,
[ReportResults] 	and a query that uses an inclusive date range, the results of the query will fail to include documents where the date
[ReportResults] 	of the document is the same day as the inclusive endpoint of the range. See https://github.com/opensearch-
[ReportResults] 	project/OpenSearch/issues/4285
[ReportResults]

[ReportResults] ======================== PASSED EXPECTATIONS ========================
[ReportResults] consistent-document-count
[ReportResults] 	Phases: pre_upgrade, post_upgrade
[ReportResults]

[ReportResults] For additional details on test results, see the test result directory: /tmp/utf/test-results
[FrameworkRunner] Step Succeeded: ReportResults
[FrameworkRunner] Ran through all 14 steps successfully
[FrameworkRunner] Saving application state to file...
[FrameworkRunner] Application state saved
[FrameworkRunner] Application state saved to: /tmp/utf/state-file
[FrameworkRunner] Full run details logged to: /tmp/utf/logs/run.log.2023-01-04_10_49_18

Check List

[ ] New functionality includes testing

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #66 (77558d3) into main (9b2001e) will increase coverage by 15.24%.
The diff coverage is 97.29%.

@@             Coverage Diff             @@
##             main      #66       +/-   ##
===========================================
+ Coverage   78.50%   93.75%   +15.24%
===========================================
  Files          37       21       -16
  Lines        1233      944      -289
  Branches      130       94       -36
===========================================
- Hits          968      885       -83
+ Misses        255       49      -206
  Partials       10       10

Impacted Files
Coverage Δ

...on_core/cluster_migration_core/clients/rest_ops.py
90.56% <ø> (ø)

...gration_core/cluster_management/cluster_objects.py
85.71% <ø> (ø)

...tion_core/cluster_migration_core/core/constants.py
100.00% <ø> (ø)

...core/cluster_migration_core/core/exception_base.py
100.00% <ø> (ø)

.../cluster_migration_core/core/shell_interactions.py
97.36% <ø> (ø)

...uster_migration_core/core/test_config_wrangling.py
93.97% <ø> (ø)

...ore/cluster_migration_core/core/versions_engine.py
100.00% <ø> (ø)

.../cluster_migration_core/core/workspace_wrangler.py
96.00% <ø> (ø)

...on_core/cluster_migration_core/clients/__init__.py
80.00% <80.00%> (ø)

...cluster_migration_core/clients/rest_client_base.py
72.72% <100.00%> (ø)

... and 27 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I see a "cluster_migration_core" folder within a "cluster_migration_core" folder, do you think we need to rename one maybe?


MasterDetailPage not implemented

I've been resisting writing a hamburger menu, but lots of people want MasterDetail.

I have a web implementation of MasterDetail I could share, do you still feel this would fit in version 0.11 ?

Hi Stephen
Would you be so kind to share your implementation of the master detail page


Print issue in embedded PDF viewer Cordova / Phonegap

Hi all!
I'm using the viewer embedded in a Cordova app. I've embeded it like that:
var htmlContent = '<object type="text/html" width="100%" height="100%" data="pdfjs/web/viewer.html?' + paramFile + paramSearch + '"></object>';

	if(DEVICE_WINDOWS) {
		MSApp.execUnsafeLocalFunction(function() {
			document.getElementById("rightSection").innerHTML = htmlContent;
		});

When printing, the preview (and the printed document) are like a screen capture instead of the whole pdf document. See it here:

I think is something related with the rendering using window since window corresponds to innerHTML instead of to the whole page. I've tried to change somewhere window by window.parent but still doesn't works. Any idea ?
Thank you in advance !

You might need to select the canvas elements manually then, but since nobody here is a Cordova developer it might be better to ask the question on a website or IRC channel for Cordova developers.


How to generate Solana Public and Private Keys from 12 words Mnemonic

Generated mnemonic using Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);
Generated seed using final seed = Bip39SeedGenerator(mnemonic).generate();

Solana Address generated correctly using solana package
Ed25519HDKeyPair.fromSeedWithHdPath(seed: seed, hdPath: "m/44'/501'/0'/0'").then((value) {       print(' correct address: ${value.address}');     });
How can we get public and private key using this package?

Generated mnemonic using Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);
Generated seed using final seed = Bip39SeedGenerator(mnemonic).generate();

Solana Address generated correctly using solana package Ed25519HDKeyPair.fromSeedWithHdPath(seed: seed, hdPath: "m/44'/501'/0'/0'").then((value) { print(' correct address: ${value.address}'); });
How can we get public and private key using this package?

Hi
// Generate a mnemonic phrase using BIP39 standard with 12 words
final mnemonic = Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);

// Generate a seed from the mnemonic
final seed = Bip39SeedGenerator(mnemonic).generate();

// Create a Solana wallet using BIP44 standard from the generated seed
final solanaWallet = Bip44.fromSeed(seed, Bip44Coins.solana);

// Derive the default HD wallet path for Solana
final solanaDefaultHdWallet = solanaWallet.deriveDefaultPath;

// Extract the private key from the derived wallet
final privateKey = solanaDefaultHdWallet.privateKey;

// Extract the public key from the derived wallet
final publicKey = solanaDefaultHdWallet.publicKey;

// Convert the public key to a Solana address
final address = publicKey.toAddress;

The default path in SLIP-0010 Ed25519 key derivation is m/44'/501'/0'. If you want to derive a custom path, you should use the following method:
  final customDeriavtion =
      Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");

@mrtnetwork can we do all kind of functionality e.g send/receive solana, send/receive USDC/USDT in solana, listen to transaction upon solana address similar to solana package?

Generated mnemonic using Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);
Generated seed using final seed = Bip39SeedGenerator(mnemonic).generate();

Solana Address generated correctly using solana package Ed25519HDKeyPair.fromSeedWithHdPath(seed: seed, hdPath: "m/44'/501'/0'/0'").then((value) { print(' correct address: ${value.address}'); });
How can we get public and private key using this package?

Hi
// Generate a mnemonic phrase using BIP39 standard with 12 words
final mnemonic = Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);

// Generate a seed from the mnemonic
final seed = Bip39SeedGenerator(mnemonic).generate();

// Create a Solana wallet using BIP44 standard from the generated seed
final solanaWallet = Bip44.fromSeed(seed, Bip44Coins.solana);

// Derive the default HD wallet path for Solana
final solanaDefaultHdWallet = solanaWallet.deriveDefaultPath;

// Extract the private key from the derived wallet
final privateKey = solanaDefaultHdWallet.privateKey;

// Extract the public key from the derived wallet
final publicKey = solanaDefaultHdWallet.publicKey;

// Convert the public key to a Solana address
final address = publicKey.toAddress;

The default path in SLIP-0010 Ed25519 key derivation is m/44'/501'/0'. If you want to derive a custom path, you should use the following method:
  final customDeriavtion =
      Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");

@mrtnetwork
Public address not matching generated with 12 phrase words with Solflare and Phantom

``> > > 1. Generated mnemonic using Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);

Generated seed using final seed = Bip39SeedGenerator(mnemonic).generate();

Solana Address generated correctly using solana package Ed25519HDKeyPair.fromSeedWithHdPath(seed: seed, hdPath: "m/44'/501'/0'/0'").then((value) { print(' correct address: ${value.address}'); });
How can we get public and private key using this package?

Hi
// Generate a mnemonic phrase using BIP39 standard with 12 words
final mnemonic = Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);

// Generate a seed from the mnemonic
final seed = Bip39SeedGenerator(mnemonic).generate();

// Create a Solana wallet using BIP44 standard from the generated seed
final solanaWallet = Bip44.fromSeed(seed, Bip44Coins.solana);

// Derive the default HD wallet path for Solana
final solanaDefaultHdWallet = solanaWallet.deriveDefaultPath;

// Extract the private key from the derived wallet
final privateKey = solanaDefaultHdWallet.privateKey;

// Extract the public key from the derived wallet
final publicKey = solanaDefaultHdWallet.publicKey;

// Convert the public key to a Solana address
final address = publicKey.toAddress;

The default path in SLIP-0010 Ed25519 key derivation is m/44'/501'/0'. If you want to derive a custom path, you should use the following method:
  final customDeriavtion =
      Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");

@mrtnetwork Public address not matching generated with 12 phrase words with Solflare and Phantom

we checked with phantom chrome extension and its ok.
  final seed = Bip39SeedGenerator(Mnemonic.fromString(
          "release grab ice belt crack year kiss trash girl work state brisk"))
      .generate();
  final slp = Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");
  final addr = SolAddrEncoder().encodeKey(slp.publicKey.compressed);
  String phantomAddr = "48xZJSzRFnmkmo8MU5CtS36QuVjc2MFiF2MujTiQ1Atv";
  assert(addr == phantomAddr);

@mrtnetwork can we do all kind of functionality e.g send/receive solana, send/receive USDC/USDT in solana, listen to transaction upon solana address similar to solana package?

with this package, u can generate an address and sign Solana transaction but for API and create and serialization transactions you should take a look at some packages in pub.dev (Solana, Solana web3, on_chain, etc)

final addr = SolAddrEncoder().encodeKey(slp.publicKey.compressed);

I was checking with code but using Slip it's correct
But how to generate private same like phantom?
`// Generate a mnemonic phrase using BIP39 standard with 12 words
final mnemonic = Bip39MnemonicGenerator().fromWordsNumber(Bip39WordsNum.wordsNum12);
// Generate a seed from the mnemonic
final seed = Bip39SeedGenerator(mnemonic).generate();
// Create a Solana wallet using BIP44 standard from the generated seed
final solanaWallet = Bip44.fromSeed(seed, Bip44Coins.solana);
// Derive the default HD wallet path for Solana
final solanaDefaultHdWallet = solanaWallet.deriveDefaultPath;
// Extract the private key from the derived wallet
final privateKey = solanaDefaultHdWallet.privateKey;
// Extract the public key from the derived wallet
final publicKey = solanaDefaultHdWallet.publicKey;
// Convert the public key to a Solana address
final address = publicKey.toAddress;
`

@mrtnetwork can you please help with some of basic functionality using this package

Import wallet from private key for solana i.e public address and 12 words mnemonic
Generate private key from 12 words mnemonic

final seed = Bip39SeedGenerator(Mnemonic.fromString(
"release grab ice belt crack year kiss trash girl work state brisk"))
.generate();
final slp = Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");
final addr = SolAddrEncoder().encodeKey(slp.publicKey.compressed);
String phantomAddr = "48xZJSzRFnmkmo8MU5CtS36QuVjc2MFiF2MujTiQ1Atv";
assert(addr == phantomAddr);

Encode, Decode Phantom private key
  final seed = Bip39SeedGenerator(Mnemonic.fromString(
          "release grab ice belt crack year kiss trash girl work state brisk"))
      .generate();
  final slp = Bip32Slip10Ed25519.fromSeed(seed).derivePath("m/44'/501'/0'/0'");
  final addr = SolAddrEncoder().encodeKey(slp.publicKey.compressed);
  String phantomAddr = "48xZJSzRFnmkmo8MU5CtS36QuVjc2MFiF2MujTiQ1Atv";
  assert(addr == phantomAddr);
  const phantomPrivateKey =
      "52qt3JzK54cmRupKqdTtc3ECFwbuJgqgXJS7pMhbajBfJ8ZCnXzjpQ8FueJoApgoDTZGLy4nbWg3vksYQH2jfgZk";
  final inBytes = Base58Decoder.decode(phantomPrivateKey);
  assert(
      BytesUtils.bytesEqual(inBytes.sublist(0, Ed25519KeysConst.privKeyByteLen),
          slp.privateKey.raw),
      true);
  assert(
      BytesUtils.bytesEqual(
          inBytes.sublist(Ed25519KeysConst.privKeyByteLen),

          /// remove ed25519 public key prefix
          slp.publicKey.compressed.sublist(1)),
      true);

  final convertToPhantomPrivateKey = Base58Encoder.encode(
      <int>[...slp.privateKey.raw, ...slp.publicKey.compressed.sublist(1)]);
  assert(convertToPhantomPrivateKey == phantomPrivateKey);

@mrtnetwork can you please help with some of basic functionality using this package

Import wallet from private key for solana i.e public address and 12 words mnemonic
Generate private key from 12 words mnemonic

this package contains many tools for interacting with blockchain cryptography and related tools.
you can read the readme page and check test files.
I have many plugins and each one only uses this package you should take a look at them
on_chain: interacting with Solana, Ethereum, Tron, and Cardano
bitcoin_base: interacting with bitcoin and forked networks like bitcoin, dogecoin, bitcoin cash, dash, litecoin, and ...,
xrpl_dart: interacting with ripple network
cosmos_sdk: interacting with networks based on cosmos_sdk
polkadot_dart: interacting with substrate networks
ton_dart: interacting with Ton network

Ok will explore on_chain package more
Thanks for help!


Using it responsive with two video files

Hey Stefan,
I have a problem as I would like to use a Video as Background for our page: www.ruff-cycles.com/xpro2/video.html
But I would like to also use one video for the desktop version and one for the mobile version. So the video does still make sense.
Once I switch to the mobile version it seems the Covervid is not loading the video correct. I guess it cannot handle two videos for this purpose and uses the wrong size for full screen background.
Any idea how I can get this done? Thanks
Stefan

This project is no longer maintained now that their is widespread support for the object-fit and object-position CSS properties in modern browsers


Fix mistyped method name in purpose-strings.rst

@halter73 @muratg @Tratcher

Hi @cesarbs, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@danroth27

:shipit:

:+1:


Feedback for: swarm/scheduler/strategy.md

File: swarm/scheduler/strategy.md
This page refers to swarm manage and there is no docker swarm manage commands in Engine 1.12.  docker swarm update also does not have any scheduling strategy configuration listed in the help commands.

This topic is about legacy standalone swarm, not swarm mode.


Don't return nil for delegated NetworkManager associations

If a NetworkManager doesn't have a parent_manager (e.g. Nuage) don't
return nil for delegated associations.
This is an issue where we are assuming that associations will at least return an empty assoc not nil e.g.: (hosts + ems_clusters).inject(0) { |v, obj| v + (obj.send(field) || 0) }
Before:
>> ManageIQ::Providers::Nuage::NetworkManager.first.hosts
=> nil

After:
>> ManageIQ::Providers::Nuage::NetworkManager.first.hosts
=> []

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1767747

Closing in favor of https://github.com/ManageIQ/manageiq/pull/19473


Quality of Life improvements

First pass at QoL improvements reported in #56
Currently implemented:

[x] Observer or greater can distribute currency
[x] Observer or greater can loot currency (with settings toggle)
[x] Bulk permissions update from sheet
[x] Loot All button (with settings toggle)
[x] Quick looting of stacks using shift-modifier (and bypass quantity dialog for single-quantity stacks)

Fixes #56

I believe this is ready for review. Commits are broken down by feature, if there's a particular feature you'd prefer not to take or modify, I'm happy omit or modify it, but these all seem quite useful to me.

Thanks, I'll review these next week. Appreciate it!


[Bug] Bat AI confused.

The Bat keeps flying in the same spot.

Are you sure the server isn't frozen? It seemed to work for me even at extreme depths.

I found the code responsible for this:
            if (this.spawnPosition != null && (!this.world.isAirBlock(this.spawnPosition) || this.spawnPosition.getY() < 1))
            {
                this.spawnPosition = null;
            }

It's not literally stopped in one place, it just doesn't fly very far.


Fabric LanguageAdapter port + (Actions)

This PR contains changes from my fork, mainly the config is now loaded by a language Adapter and configured using Configurator#initialize as the previous solution was overridden by Minecraft's default config.

This PR is targeting the fabric branch, but quilt is the main development branch. The fabric branch is maintained by rebasing it ontop of the quilt branch after changes are pushed. Also, the CI stuff should be in its own PR. Could you open two new PRs targeting the quilt branch, one implementing the language adapter port for Quilt, and one with the CI additions? After those are merged, I'll update the fabric branch accordingly and release the new versions.

Strangely enough, the quilt version doesn't reconfugre everything this early(?) Some messages don't have the (Minecraft) prefix, but the same setup works on Fabric. I feel that this has something to do with classloaders, but not really sure.


Openrpc Firebolt definition references to schema in Private Comcast repository

Lot of places inside Firebolt openrpc API definition points to schemas on private Comcast repository
https://github.com/rdkcentral/firebolt-apis/blob/d4f5ad8ae302df89fc6969bbb8abbdcd45753573/src/openrpc/accessibility.json#L30
https://github.com/rdkcentral/firebolt-apis/blob/d4f5ad8ae302df89fc6969bbb8abbdcd45753573/src/openrpc/second_screen.json#L25
etc...
Could you please move this schemas to public repository (or even better to https://github.com/rdkcentral/firebolt-apis itself?)
Without this cleanup, there is no possibility to use open-rpc tooling like https://playground.open-rpc.org/

We've been moving these schemas over one at a time, as they get edited, but if it's blocking you, we can move them all over.


Encode query parameters in an array before joining them

Related to Issue: 4244 && PR: 8377
@ramya-rao-a Please review and approve

PR https://github.com/Azure/ms-rest-js/pull/384 should fix your final CI error, you'll need to rebase your PR on master after I get it merged.


RL and DP refactor

This pull request addresses #13

These commits look fine to me!
@fabiorobayo you can add yourself as the author in setup.py file!

@hbk-ronak initially it was a relative path but the automated build wouldn't find the file, I tried to use pathlib to fix it but it still didn't work, the setup of the environment used to do the automated build is not visible to me so I can't really make sure it will find the file. We added a try/except to handle absolute and relative cases.

@fabiorobayo you can use ./tests/filename as the path it should work

@hbk-ronak didn't work locally for me. Can we merge this pull request and create an issue for the filepath?

@fabiorobayo I've already approved. We are waiting for a review from professor. @PawPol can you review the code?


Upgrading the app leads to loss of all information.

Add local storage / caching?

This is the first time I get this report, so far people has been upgrading it without losing the data. The app has a local DB plus a SecureStorage instance to store keys. Can you provide more info?

That was an issue on my end. Sorry.
One instance of the app was running in the business profile of the phone.


Page refers to AzureRM PS module

PowerShell example in Cause 1: Port 445 is blocked
Azure PowerShell example states:
“ This command requires you to be logged into your Azure account, run Login-AzAccount if you haven't already logged in.”
PowerShell 7.2.1 shows that Login-AzAccount is aliased to Connect-AzureRMAccount.
This article, Migrate Azure PowerShell scripts from AzureRM to Az | Microsoft Docs, states:
“All versions of the AzureRM PowerShell module are outdated.”
Recommend the example be updated to:
“This command requires you to be logged into your Azure account and set the subscription your storage account is under, run:
Connect-AzAccount -SubscriptionId ‘xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’
if you haven't already logged in.”

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

ID: dfcc20de-f394-74bf-155f-639cfe00aba4
Version Independent ID: 76ccfc8f-6190-0618-f668-91c9bab532c0
Content: Troubleshoot Azure Files problems in Windows
Content Source: articles/storage/files/storage-troubleshoot-windows-file-connection-problems.md
Service: storage
Sub-service: files
GitHub Login: @jeffpatt24
Microsoft Alias: jeffpatt

Thanks for the feedback! We are currently investigating and will update you shortly.

@David-W-Williams Thanks for letting us know. I have created a PR to address this and the changes should go live soon.


Generate user identifiers from Persistent Name IDs

I'm having trouble getting started with the SAML backend. Whenever I try to login an exception gets thrown:
[2016-10-18 15:00:37] [DEBUG]: [urn:uuid:e9b38285-e2a5-43e5-b11a-8aee973a597c] received attributes:
{
    "displayName": [
        "John Doe"
    ],
    "eduPersonScopedAffiliation": [
        "member"
    ],
    "eduPersonTargetedID": [
        {
            "NameID": {
                "name_qualifier": "https://idp.local/idp/sso",
                "format": "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent",
                "sp_name_qualifier": "https://satosa.local/example/proxy_saml2_backend.xml",
                "value": "KHj2iBGk+sAhaQw+lIVaxCdfJFw="
            }
        }
    ],
    "mail": [
<EMAIL_ADDRESS>    ]
}
[2016-10-18 15:00:37] [ERROR]: [urn:uuid:e9b38285-e2a5-43e5-b11a-8aee973a597c] Uncaught exception
Traceback (most recent call last):
  File "/opt/satosa/src/satosa/base.py", line 256, in run
    resp = self._run_bound_endpoint(context, spec)
  File "/opt/satosa/src/satosa/base.py", line 204, in _run_bound_endpoint
    return spec(context)
  File "/opt/satosa/src/satosa/backends/saml2.py", line 162, in authn_response
    return self.auth_callback_func(context, self._translate_response(authn_response, context.state))
  File "/opt/satosa/src/satosa/base.py", line 165, in _auth_resp_callback_func
    self.config["INTERNAL_ATTRIBUTES"]["user_id_from_attrs"]]
  File "/opt/satosa/src/satosa/base.py", line 164, in <listcomp>
    user_id = ["".join(internal_response.attributes[attr]) for attr in
TypeError: sequence item 0: expected str instance, dict found
[2016-10-18 15:00:37] [ERROR]: Unknown error
Traceback (most recent call last):
  File "/opt/satosa/src/satosa/base.py", line 256, in run
    resp = self._run_bound_endpoint(context, spec)
  File "/opt/satosa/src/satosa/base.py", line 204, in _run_bound_endpoint
    return spec(context)
  File "/opt/satosa/src/satosa/backends/saml2.py", line 162, in authn_response
    return self.auth_callback_func(context, self._translate_response(authn_response, context.state))
  File "/opt/satosa/src/satosa/base.py", line 165, in _auth_resp_callback_func
    self.config["INTERNAL_ATTRIBUTES"]["user_id_from_attrs"]]
  File "/opt/satosa/src/satosa/base.py", line 164, in <listcomp>
    user_id = ["".join(internal_response.attributes[attr]) for attr in
TypeError: sequence item 0: expected str instance, dict found

internal_attributes.yml
attributes:
  displayname:
    openid: [nickname]
    saml: [displayName]
  edupersontargetedid:
    facebook: [id]
    openid: [sub]
    saml: [eduPersonTargetedID]
  mail:
    facebook: [email]
    openid: [email]
    saml: [email, emailAdress, mail]
hash: [edupersontargetedid]
user_id_from_attrs: [edupersontargetedid]
user_id_to_attr: edupersontargetedid

Is there a way I can still use eduPersonTargetedID?

This should be fixed as of v3.3.0 which includes an updated pysaml2 dependency.
Is this still present in version later than that?

You're right, thank you! I'm sorry for not updating all dependencies.
Now eduPersonTargetedID is flattened and an access token is issued. However, the UserInfo endpoint throws an exception:
[2016-10-19 10:56:35] [DEBUG]: [urn:uuid:f4f30b77-68f2-40bc-9788-4d4cba272563] Found registered endpoint: module name:'OIDC', endpoint: OIDC/userinfo
[2016-10-19 10:56:35] [ERROR]: [urn:uuid:f4f30b77-68f2-40bc-9788-4d4cba272563] Uncaught exception
Traceback (most recent call last):
  File "/opt/satosa/src/satosa/base.py", line 255, in run
    resp = self._run_bound_endpoint(context, spec)
  File "/opt/satosa/src/satosa/base.py", line 203, in _run_bound_endpoint
    return spec(context)
  File "/opt/satosa/src/satosa/frontends/openid_connect.py", line 337, in userinfo_endpoint
    response = self.provider.handle_userinfo_request(urlencode(context.request), headers)
  File "/opt/satosa/venv/lib/python3.4/site-packages/pyop/provider.py", line 428, in handle_userinfo_request
    response = OpenIDSchema(sub=introspection['sub'], **user_claims)
TypeError: type object got multiple values for keyword argument 'sub'
[2016-10-19 10:56:36] [ERROR]: Unknown error
Traceback (most recent call last):
  File "/opt/satosa/src/satosa/base.py", line 255, in run
    resp = self._run_bound_endpoint(context, spec)
  File "/opt/satosa/src/satosa/base.py", line 203, in _run_bound_endpoint
    return spec(context)
  File "/opt/satosa/src/satosa/frontends/openid_connect.py", line 337, in userinfo_endpoint
    response = self.provider.handle_userinfo_request(urlencode(context.request), headers)
  File "/opt/satosa/venv/lib/python3.4/site-packages/pyop/provider.py", line 428, in handle_userinfo_request
    response = OpenIDSchema(sub=introspection['sub'], **user_claims)
TypeError: type object got multiple values for keyword argument 'sub'

I already reported the issue to pyop#6 when we didn't use eduPersonTargetedID. However, it seems to be related to SATOSA.

Yes, I recognize this issue as the same you reported earlier.
I still need more info (all configuration for SATOSA), since I haven't been able to reproduce it locally yet.

proxy_conf.yml
BASE: https://satosa.local
INTERNAL_ATTRIBUTES: "internal_attributes.yaml"
COOKIE_STATE_NAME: "SATOSA_STATE"
STATE_ENCRYPTION_KEY: "123123"
CUSTOM_PLUGIN_MODULE_PATHS:
  - "plugins/backends"
  - "plugins/frontends"
  - "plugins/micro_services"
BACKEND_MODULES:
  - "plugins/saml2_backend.yaml"
FRONTEND_MODULES:
  - "plugins/openid_connect_frontend.yaml"
MICRO_SERVICES: []
USER_ID_HASH_SALT: "123123"
LOGGING:
  version: 1
  formatters:
    simple:
      format: "[%(asctime)-19.19s] [%(levelname)-5.5s]: %(message)s"
  handlers:
    console:
      class: logging.StreamHandler
      level: DEBUG
      formatter: simple
      stream: ext://sys.stdout
    info_file_handler:
      class: logging.handlers.RotatingFileHandler
      level: INFO
      formatter: simple
      filename: info.log
      maxBytes: 10485760 # 10MB
      backupCount: 20
      encoding: utf8
  loggers:
    satosa:
      level: DEBUG
      handlers: [console]
      propagate: no
  root:
    level: INFO
    handlers: [info_file_handler]

internal_attributes.yaml
see above
plugins/saml2_backend.yaml
identical to examples/plugins/backend/saml2_backend.yaml.example
plugins/openid_connect_frontend.yaml
module: satosa.frontends.openid_connect.OpenIDConnectFrontend
name: oidc
config:
  signing_key_path: oidcsign.pem
  db_uri: mongodb://localhost/satosa
  provider:
    client_registration_supported: No
    response_types_supported: ["code"]
    subject_types_supported: ["pairwise"]
    scopes_supported: ["openid", "email", "profile"]

Please let me know in case you need more information to reproduce the issue.

v3.3.2 contains an updated pyop dependency which fixes the issue with the 'sub' claim.
Let me know if you still have issues after that upgrade.

Thank you for the fast fix! Now the sub claim gets properly propagated to the clients.

Sure thing, thanks for reporting and testing it out! :)


Fix scanOp lowering by adding support for shfl_up

The implementation of shuffle up is copied from hcc function _shfl_up().
This PR also copied test_scan2d and test_scan_layouts from test_core.py into test_core_amd.py.

P.S. sorry, for some reason I can not login into @alefimov-amd, so can not add proper accept :(


feat(storage): move nlohmann/json.hpp includes to cc file

Fixes: #2772
This completes the work of removing the nlohmann/json.hpp include from public
headers. storage_include_test.cc has been amended to test this.
PatchBuilder has been changed to follow the Pimpl idiom and some unused
functions were removed. SetArrayField no longer takes a vector but now a
std::string which represents a stringified array.

This change is

Maybe file a separate issue for this, but GOOGLE_CLOUD_CPP_STORAGE_ENABLE_GRPC is disabled by default (but enabled by default in the CI). It wasn't building locally, hence why I wasn't seeing the compiler errors.

Argh, I bet that is annoying.  The GCS+gRPC plugin is not ready for prime time yet, that is why it is disabled by default.

I just merged https://github.com/googleapis/google-cloud-cpp/pull/5313, which may conflict slightly with this. Sorry, but FYI.

I just merged #5313, which may conflict slightly with this. Sorry, but FYI.

No conflicts as far as I can tell, however the macos builds have flaked.


Sounds do not play in iOS

Apple says:

In Safari on iOS (for all devices, including iPad), where the user may be on a cellular network and be charged per data unit, preload and autoplay are disabled. No data is loaded until the user initiates it. This means the JavaScript play() and load() methods are also inactive until the user initiates playback, unless the play() or load() method is triggered by user action. In other words, a user-initiated Play button works, but an onLoad="play()" event does not.

What would be the workaround? Shotgun sounds and footsteps could potentially be initiated from touch events, but the rest... no idea so far.

Okay, these guys do this:

The default behavior of howler.js is to attempt to silently unlock audio playback by playing an empty buffer on the first touchstart event.


fix DateTime SQL

 In der Pro-Version gibt die Session-API falsche Datumswerte aus

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.0007%) to 84.107%

Files with Coverage Reduction
New Missed Lines
%

services/src/server.rs
1
66.47%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0007%

Covered Lines:
35096

Relevant Lines:
41728

💛  - Coveralls

Can you add a test that verifies this fix? It is always concerning if we change behavior and no tests need to be adjusted :smile:.

Can you add a test that verifies this fix? It is always concerning if we change behavior and no tests need to be adjusted 😄.

I just delegate the method and the actual implementation is tested in the postgres_types crate. Doesn't this suffice?

Can you add a test that verifies this fix? It is always concerning if we change behavior and no tests need to be adjusted 😄.

unfortunately, I can't. The config for the postgres isn't accessible in the datatypes crate. I guess it's ok though because I only delegate the method to the implementation in postgres_types.

From Slack: Test the functionality in the services crate.

I indirectly test it now as part of the method where we first noticed the error: 773c15bffb399b731d74d5dff5eea73e6c5d3f2b

bors merge


Revisit AWS documental changes for PCI DSS controls

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@rajlearner17 Can you please include more details on what changes we need?


Dynamic tabs support ?

Tab Navigation bar is static. when I add more tabs its not scrolling horizontally

Hi! We merged to master this new feature. We'll deliver a new version soon.


Fixed broken 4c logo URL

Description
I have fixed broken URL of 4c Logo which is now visible under Discord and Twitter icons in Readme.md
Issue No : 618
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Hey @SamarthSaxena10, the image on the Readme isn't broken. It looks fine from my end. Thanks for your awesome contribution.


_tanh(x) returns different values for the same x

Why is the last one (0.99505478) different from the first four?
>>> import tensorflow as tf
>>> from tensorflow.python.ops.gen_math_ops import _tanh
>>> a = tf.ones([1, 3], tf.float32)
>>> b = tf.ones([3, 5], tf.float32)
>>> c = tf.matmul(a, b)
>>> sess = tf.Session()
>>> print(sess.run(_tanh(c)))
[[ 0.99505472  0.99505472  0.99505472  0.99505472  0.99505478]]

With tf.float64, the values are all 0.99505475.

Can't reproduce, tried on Z420 and Z840 machines and TF at head.
Are you using GPU?
import tensorflow as tf
with tf.device("/cpu:0"):
  a = tf.ones([1, 3], tf.float32)
  b = tf.ones([3, 5], tf.float32)
sess = tf.Session()
print(sess.run(tf.tanh(tf.matmul(a, b))))

[[ 0.99505478  0.99505478  0.99505478  0.99505478  0.99505478]]

I get the same result even with your code specifying tf.device("/cpu:0").
I am using 0.8.0 in the VirtualBox image of Ubuntu (vagrant-ubuntu-vivid-64 3.19.0-10-generic #10-Ubuntu SMP).

Can you try and see if it's still non-deterministic when using with less threads
import tensorflow as tf
with tf.device("/cpu:0"):
  a = tf.ones([1, 3], tf.float32)
  b = tf.ones([3, 5], tf.float32)
  c = tf.tanh(tf.matmul(a, b))
config = tf.ConfigProto(inter_op_parallelism_threads=1, intra_op_parallelism_threads=1)
sess = tf.Session(config=config)
print(sess.run(c))

I can reproduce it (in python 3.5.1):

It's getting interesting when I change the input size 10:

with 100, the problem is gone:

Hm, could it be numpy display issue? What if you do
import tensorflow as tf
with tf.device("/cpu:0"):
a = tf.ones([1, 3], tf.float32)
b = tf.ones([3, 5], tf.float32)
c = tf.log(tf.tanh(tf.matmul(a, b))-0.99505478)/tf.log(2.)
config = tf.ConfigProto(inter_op_parallelism_threads=1, intra_op_parallelism_threads=1)
sess = tf.Session(config=config)
print(sess.run(c))

I suspect eigen packet/vector vs non vector difference. Inputs mod 4 will
be the same, the remainder will be different because it uses a different
code path?
On Thu, May 5, 2016, 3:37 PM Yaroslav Bulatov<EMAIL_ADDRESS>wrote:

Hm, could it be numpy display issue? What if you do
import tensorflow as tf
with tf.device("/cpu:0"):
a = tf.ones([1, 3], tf.float32)
b = tf.ones([3, 5], tf.float32)
c = tf.log(tf.tanh(tf.matmul(a, b))-0.99505478)/tf.log(2.)
config = tf.ConfigProto(inter_op_parallelism_threads=1,
intra_op_parallelism_threads=1)
sess = tf.Session(config=config)
print(sess.run(c))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/2234#issuecomment-217287498

@benoitsteiner @rmlarsen for comment?
On Thu, May 5, 2016, 3:40 PM Vijay Vasudevan<EMAIL_ADDRESS>wrote:

I suspect eigen packet/vector vs non vector difference. Inputs mod 4 will
be the same, the remainder will be different because it uses a different
code path?
On Thu, May 5, 2016, 3:37 PM Yaroslav Bulatov<EMAIL_ADDRESS>wrote:

Hm, could it be numpy display issue? What if you do
import tensorflow as tf
with tf.device("/cpu:0"):
a = tf.ones([1, 3], tf.float32)
b = tf.ones([3, 5], tf.float32)
c = tf.log(tf.tanh(tf.matmul(a, b))-0.99505478)/tf.log(2.)
config = tf.ConfigProto(inter_op_parallelism_threads=1,
intra_op_parallelism_threads=1)
sess = tf.Session(config=config)
print(sess.run(c))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/2234#issuecomment-217287498

We have an optimized version of the tanh function that processes coefficients 4 by 4. In a tensor of 10 elements we call that function twice to process the 8 first element, and we process the last 2 elements one by one by calling std::tanh. std::tanh and our optimized versions don't fully agree on the final result, which is why the last 2 coefficients are slightly different from the rest.
When the input contains 100 elements, we simply call the optimized version of tanh 25 times, so all the results match.

Contributions welcome to fix this to be consistent!

I'll work on this

I find that SSE2 vectorization is a feature of eigen, so adding addtional code to tensorflow may be a good choice.

one eigen's core dev pushed some update to tanh.

I've confirmed that this is now fixed.


WIP New Conversation

Description

Bringing "Conversation" UI to Sparkle
Creating a "Compact" style for conversatons

@flvndvd leaving this one to you.


Updating Formatting According to WILDS Guidelines

Description
Just performing a slight structural revamp of this repository in preparation for the WILDS WDL go-live. Nothing in terms of the WDL script's actual logic, just adjusting the formatting to align with WILDS guidelines. The major updates are as follows:

Adding governance and template files according to Scott's templates
Updating WDL script formatting according to WILDS guidelines
Adding WOMtool validate GitHub Action to execute as a check during every pull request

All comments have been addressed and variable names have been updated to meet WILDS stylistic guidelines. Submitted a test run with real data via PROOF and run completed successfully. Going to merge this pull request unless @laderast or @sitapriyamoorthi have any other feedback. Thank you guys so much for taking a look at this! :)


Missing 'logging.py' file in pip installation

Hi there!
Tried to run your code from "Transformers\examples\pytorch\run_image_classification_no_trainer.py.
I installed the required accelerate package via pip, seems to be the right version (0.7.1),
but the code crashes on the line "from accelerate.logging import get_logger" line with the error that there's no such module.
I even tried to edit the init file, but I can access all other modules - Accelerator, checkpointing, tracking etc...
It's as if I downloaded an older version without '.logging', but the version number seems correct.
Any idea why this might happen, and how could I fix it without manually cloning your repository from github?
Thanks

The directions state that you need to install from source, as we're rapidly working on Accelerate and bringing in new features.
https://github.com/huggingface/transformers/tree/main/examples/pytorch#using-accelerate

Thank you!
This is from the 'transformers' directions, while I was looking in the directions in the 'accelerate' repository itself where there's a regular installation command.

Anyway, installed from source as you suggested, works well now, thanks again!

@sptom thanks, all the directions in transformers now state this 🤗


Opening channel with Eclair: -22: TX rejected: insufficient priority

@mably Reports that opening channels with Eclair sometimes fails with error
2017-12-04 09:12:53.926 [ERR] FNDG: Unable to complete reservation sign complete: -22: TX rejected: transaction 0f87c6a036365a340616e1a9efc264eb29150ec7bdb2c72af2f12a7fa3cb1f07 has insufficient priority (2.7887592694300517e+07 <= 5.76e+07)
2017-12-04 09:12:53.927 [ERR] FNDG: Failing funding flow: (*lnwire.Error)(0xc421367e00)({

(logs NdHU5paC.txt)

This error comes from the funding transaction having an insufficient fee. We should figure out why this fee is being set too low, and
handle the returned error by cancelling the funding flow and clearing out leftover state. Currently the channels looks like they stay 'pending', as per the screenshot: https://i.imgur.com/E5gXQzu.png

Don't know if it has any kind of importance but I was trying to open a channel with the Acinq endurance Eclair node.

Fixed due to https://github.com/lightningnetwork/lnd/commit/1121b0c48b8eb0c4d7a2cdbca1aaa6cdb5a46153.
Closing.


has('previous_release') doesn't return true when multiple releases are present

Deployer version: 6
Deployment OS: CentOS

My project keeps two releases (I'll attach my deploy.php file), I've got a custom task which checks using the has method provided by Deployer whether the previous_release is present, and I can indeed see two release folders on my production server in my releases directory.
When I add the previous_release check into an if statement it appears to always go into the else implying that it can't find a previous release?
I beleive this to be a bug with Deployer as I have followed what the example contains and it does not return true.
My deploy.php file
<?php
namespace Deployer;

require 'vendor/autoload.php';
require 'recipe/common.php';
require 'deploy/recipe/fudge-npm.php';
require 'deploy/recipe/fudge-server.php';
require 'deploy/recipe/fudge-composer.php';
require 'deploy/recipe/fudge-nuxt.php';
require 'deploy/recipe/fudge-duration.php';
require 'deploy/recipe/fudge-github.php';

// Project repository
set('repository', 'git@github.com:company/repo.git');

// [Optional] Allocate tty for git clone. Default value is false.
set('git_tty', true);

// [Optional] Timeout in seconds, set to 14,400 (4 hours) for max compatibility.
set('default_timeout', 14400);

// Shared files/dirs between deploys
add('shared_files', ['.env', 'brand-theme.scss']);

// Set number of releases to keep
set('keep_releases', 2);

// Writable dirs by web server
set('allow_anonymous_stats', false);

// All brands
// See the README.md for list of friendly brand names for these hosts.
host('MYIP')
    ->set('branch', 'main')
    ->stage('all')
    ->set('repository', 'git@fudge:company/repo')
    ->user('root')
    ->set('deploy_path', '/var/www/include-forms/fudge');

// deploy
task('deploy', [
  'deploy:duration:datetime:start',
  'deploy:github:validate',
  'server:health:check',
  'server:health:validate',
  'deploy:prepare',
  'deploy:lock',
  'deploy:release',
  'deploy:update_code',
  'npm:install',
  'composer:install',
  'deploy:shared',
  'deploy:writable',
  'nuxt:generate',
  'deploy:clear_paths',
  'deploy:symlink',
  'deploy:unlock',
  'cleanup',
  'success',
  'deploy:duration:datetime:finish'
]);

// [Optional] if deploy fails automatically unlock.
after('deploy:failed', 'deploy:unlock');

The custom recipe in question is deploy/recipe/fudge-server.php which does the following (I've removed all code that isn't needed for the context of this bug):
<?php
/*
 * Custom server health recipe for us.
 */

namespace Deployer;

use Symfony\Component\Console\Input\InputOption;

option('disable-health-checks', false, InputOption::VALUE_OPTIONAL, 'disable disk health checks');

/*
** Disk health validation, will exit on insufficient amount.
*/
desc('Validate server health and exit if appropriate');
task('server:health:validate', function () {
    $hostname = get('hostname');

    // disable health checks
    $disableHealthChecks = false;
    if (input()->hasOption('disable-health-checks')) {
        $disableHealthChecks = input()->getOption('disable-health-checks');
    }

    // check if we should disable checks
    if ($disableHealthChecks) {
        writeln("<comment>[ ".$hostname." ][ health_validate: Disk health checks are disabled, this is highly discouraged. ]</comment>");
    } else {

        // execute on server
        on(host($hostname), function ($host) use ($hostname) {

            // if we have a previous release, we should check this first
            // for our file as we want our script to execute as early on
            // in the process as possible.
            if (has('previous_release')) {

                // make sure that we have the correct files for executing health
                // check otherwise we can't run it.
                if (
                    test('[ -f {{previous_release}}/deploy/scripts/server_disk_free.php ]') &&
                    test('[ -f {{previous_release}}/deploy/scripts/server_disk_total.php ]')
                ) {

                    // ... stuff here

                } else {
                    writeln("<comment>[ ".$hostname." ][ health_validate: Unable to check disk health, scripts can't be found. ]</comment>");
                }

            } else {
                writeln("<comment>[ ".$hostname." ][ health_validate: Unable to check disk health, no previous release found. ]</comment>");
            }
        });
    }
});

/*
** General disk info.
** 5% or less = CRITIAL, take action, deployer will exit before deploy.
** 15% or less = ALERT, action is advised now.
** more than 15% = normal
*/
desc('Output server health');
task('server:health:check', function () {
    $hostname = get('hostname');

    // disable health checks
    $disableHealthChecks = false;
    if (input()->hasOption('disable-health-checks')) {
        $disableHealthChecks = input()->getOption('disable-health-checks');
    }

    // check if we should disable checks
    if ($disableHealthChecks) {
        writeln("<comment>[ ".$hostname." ][ health_check: Disk health checks are disabled, this is highly discouraged. ]</comment>");
    } else {

        // execute on server
        on(host($hostname), function ($host) use ($hostname) {

            // if we have a previous release, we should check this first
            // for our file as we want our script to execute as early on
            // in the process as possible.
            if (has('previous_release')) {

                // make sure that we have the correct files for executing health
                // check otherwise we can't run it.
                if (
                    test('[ -f {{previous_release}}/deploy/scripts/server_disk_free.php ]') &&
                    test('[ -f {{previous_release}}/deploy/scripts/server_disk_total.php ]')
                ) {

                    // ... stuff here

                } else {
                    writeln("<comment>[ ".$hostname." ][ health_check: Unable to check disk health, scripts can't be found. ]</comment>");
                }

            } else {
                writeln("<comment>[ ".$hostname." ][ health_check: Unable to check disk health, no previous release found. ]</comment>");
            }
        });

    }
});

See screenshot of multiple releases:

I got why it is. Not in the "release" state.
task('server:health:check', function
        on(host($hostname), function ($host) use ($hostname) {
            if (has('previous_release')) {

If deploy:release not called, previous_release is not updated.

Fixed: added exception with explanation.

@antonmedv Adding the exception is a breaking change in the following case:
We can't run some build commands on the remote server so we rely on "localhost" to locally pull and build the project and then we send all the files to the remote via rsync.
Since 7.0.2, we can't deploy anymore because the task yarn:install which use previous_release is now throwing an exception.
The thing is, we call deploy:release before using previous_release so the config should exists !
Here is an excerpt of our deploy.php file:
// Set the source for rsync
set('rsync_src', '/home/www-data/deploy_local/current');

// Create a localhost host which will be used to build the project locally
$localhost = localhost()
    ->set('deploy_path', '/home/www-data/deploy_local');

// Declare the target host for production
host('production')
    ->set('hostname', 'xxx.xxx.xxx.xxx')
    ->set('deploy_path', '/var/www/test');

// This is the main task which is call to deploy the projet
task('custom:deploy-ci', function () use ($localhost) {
    // We start by building the project on the localhost host
    on($localhost, function () {
        invoke('local:build');
    });

    // Then we prepare and push the code to the remote server
    invoke('remote:release');
})->desc("Project deployment");

// This task should only be used on the "localhost" host
task('local:build', [
    'deploy:setup',
    // We call deploy:release so "previous_release" should be set
    'deploy:release',
    'deploy:update_code',
    'deploy:vendors',
    // Yarn recipe start with "if (has('previous_release'))..."
    // which throw an exception and I cant' understand why
    'yarn:install',
    'deploy:symlink',
])->hidden()
  ->desc("Local build of the assets");

task('remote:release', [
    'deploy:setup',
    'deploy:lock',
    'deploy:release',
    'rsync:warmup',
    'rsync',
    ... // some other irrelevant command
    'deploy:unlock',
    'deploy:cleanup',
])->hidden()
  ->desc("Remote deployment");

fail('custom:deploy-ci', 'deploy:failed');
after('deploy:failed', 'deploy:unlock');
after('custom:deploy-ci', 'deploy:success');

Do you need me to create a dedicated issue or should this one be opened again ?
Thx for your time !
Tristan

Question: why do you do local build with all those steps?
task('local:build', [
'deploy:setup',
// We call deploy:release so "previous_release" should be set
'deploy:release',
'deploy:update_code',
'deploy:vendors',
// Yarn recipe start with "if (has('previous_release'))..."
// which throw an exception and I cant' understand why
'yarn:install',
'deploy:symlink',
])->hidden()

Because we are limited to file transfer only to the remote server. No git, no composer, no nodejs... Only good old ssh access and file transfer.
So the pipeline is:

On CI trigger

Pull and build dependencies (composer, yarn) locally (local:build)
Then push the generated code via rsync to the remote (remote:release)

But no matter why I do that, there is clearly a bug in the deploy:release or in something else because this code:
    on($localhost, function () {
        invoke('local:build');
    });

invoke the local:build task on the localhost host. So if the local:build task run the deploy:release task, the config previous_release should have been defined right ?


Some unit tests have flipped the order of parameters for Assert.Equal

The method is defined as: public static void Equal<T>(T expected, T actual),
but some of the tests have flipped expected and actual, resulting in misleading error messages when the tests fail.
It seems to be only in the the tests for Parse but in that class nearly all the calls to Assert.Equal uses the wrong order.
It's easy to mess up and it makes me miss the Assert.That-syntax from nUnit, or the .Should()-syntax from FluentAssertions where you rarely make these mistakes.

I can make a pull-request for this if you like, of course.

Great finding! A PR would be very welcome.

20 okt. 2018 kl. 17:41 skrev Viktor Andersson<EMAIL_ADDRESS>I can make a pull-request for this if you like, of course.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Color Code Subscription and Accounts (Tab Color)

Storage Explorer Version: 0.9.6
OS Version: Windows 10 (All)
Expected Experience:
Ability to specify a tab color for subscription or account
Actual Experience:
Hard to tell which account/subscription the opened Tab is from.

Similar to #4

We need color code + some other visual cues/text.  Color code itself is not going to meet accessibility requirements.

Similar to being able to color a connection in SSMS, it would be useful to be able to color-code individual blob/cosmos/data lake accounts or even whole subscriptions, so that you can easily filter visually between different environments (set the tab color to RED for production, for example)

For anyone who works on multiple environments this is an important feature, especially since the only place the storage account is shown for a tab is in the URL section of the properties tab, written in small font.
(even the info icon notifying you that you are using a preview feature is more significant than the storage account you are currently about to interact with).
Although interaction metrics would rate knowing this as low because nobody would "click" on this info, not having it visible can cause significant issues.
I've opened the "uploads" blob store, and i want to click across to the message queue that is supposed to hold a specific message. Which "raw-data" should i click? -- current UX is click one, read the url properties and check if that is correct, if not, click the other one.

@craxal please get the accessibility team to comment on if lettings users pick arbitrary colors for the something that serves as the background color for text is ok.

Accessibility team recommends giving users the tools to make colors work the way they want. If we provide or select any colors be default in some way, those colors, of course, should be accessible.

I'd like to add to this - last week one of my teammates accidentally made a change to a production table, rather than a test version because they had a table open and they thought it was from the test environment. It would be much safer if Storage Explorer provided a visual clue as to which tab is from which storage connection (similar to SSMS allowing the same per connection). Where I work there are several deployment environments so it's very common to have the same table name in a bunch of storage accounts.
If readability of the tab text is an issue, I'd suggest adding a colored bar under the tab name - the color would come from the connection properties, so all tabs from the same connection would share the same color and tabs from different connections could have different colors. For example:

The two tables come from different storage accounts (used in different environments). In this example I picked green as the "safe" color and red as the "warning" color but I'd expect this feature to allow me to pick any color that I wanted.


How to set non-expired token in OAuth2?

How to set non-expired token in OAuth2?

The following example OAuthV2 policy shows a long expiration time of 200 days for refresh tokens:

GenerateAccessToken
1800000
17280000000

password

The following example OAuthV2 policy shows a long expiration time of 200 days for refresh tokens:
<OAuthV2 name="GenerateAccessToken">     <Operation>GenerateAccessToken</Operation>     <ExpiresIn>1800000</ExpiresIn> <!-- 30 minutes -->     <RefreshTokenExpiresIn>17280000000</RefreshTokenExpiresIn> <!-- 200 days -->     <SupportedGrantTypes>       <GrantType>password</GrantType>     </SupportedGrantTypes>     <GenerateResponse enabled="true"/> </OAuthV2>

Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add more detail if you feel this is a genuine bug.


Publish single-arch images alongside nightly multi-arch images

_publish_container.yaml will now by default add single-arch images using the older docker manifest v2 schema 2 format.
This is controlled by the EXPOSE_SINGLE_ARCH_IMAGES input, which defaults to true. This will create single-arch images that looks like:
ghcr.io/nvidia/jax:nightly-YYYY-MM-DD-linux-amd64
ghcr.io/nvidia/jax:nightly-YYYY-MM-DD-linux-arm64

Note:

Multi-arch images will remain in OCI format.
This currently only applies to the nightly container tags. If needed, we can also apply it to containers created in ci.yaml.

Additional workflow: https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6571445794. Note that the created manifest type is application/vnd.docker.distribution.manifest.v2+json (Docker V2.2) instead of application/vnd.oci.image.index.v1+json (OCI).
$ docker manifest inspect ghcr.io/nvidia/jax-toolbox-internal:6571445794-linux-amd64
{
        "schemaVersion": 2,
        "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
        ...
}
$ docker manifest inspect ghcr.io/nvidia/jax-toolbox-internal:6571445794-linux-arm64
{
        "schemaVersion": 2,
        "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
        ...
}

p.s. docker has mostly abandoned the v2s2 schema in favor of OCI, as it almost cannot be found anywhere in the latest official documentation.

We also need that for the CI container for manuel build. That can be a follow up pr.

Also, we should document those container and ideally also document the error that is triggered when docker is too old for the multi arch container.

Also, we should document those container

Once this PR is merged and we have the first batch of single-arch nightlies created, we will add the corresponding badges to the README.

document the error that is triggered when docker is too old for the multi arch container.

This is already documented on our landing page: https://github.com/NVIDIA/JAX-Toolbox#faq-frequently-asked-questions

We also need that for the CI container for manuel build. That can be a follow up pr.

CI already creates single-arch images, e.g. ghcr.io/nvidia/jax-toolbox-internal:6578372511-pax-amd64, but they are still encoded as a multi-arch manifest list that contains a single platform. This is just a natural consequence of using builtkit>0.10.6. If we downgrade buildkit, we will break how we current combine single-arch images (1, 2, and 3, etc.)
What do you suggest?

@terrykong @ashors1 @maanug-nv Could you please investigate if these errors should block the merge?

https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6571572593/job/17851934588?pr=321#step:9:470
https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6571572593/job/17857688031?pr=321
https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6571572593/job/17858432019?pr=321

Also, we should document those container

Once this PR is merged and we have the first batch of single-arch nightlies created, we will add the corresponding badges to the README.

Why not add the README update in this PR?

document the error that is triggered when docker is too old for the multi arch container.

This is already documented on our landing page: https://github.com/NVIDIA/JAX-Toolbox#faq-frequently-asked-questions

It doesn't document the error with docker. The current docker error is related to the shared memory usage.

We also need that for the CI container for manuel build. That can be a follow up pr.

CI already creates single-arch images, e.g. ghcr.io/nvidia/jax-toolbox-internal:6578372511-pax-amd64, but they are still encoded as a multi-arch manifest list that contains a single platform. This is just a natural consequence of using builtkit>0.10.6. If we downgrade buildkit, we will break how we current combine single-arch images (1, 2, and 3, etc.)
What do you suggest? @nouiz

Could we change the format when we make them public?
One way I changed the format is by making a new simple container. Maybe there is a simpler way?

https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6571572593/job/17858432019?pr=321
This failure is expected. The pax DP+TP+PP test failed, so we would expect the workflow status to reflect this.

Why not add the README update in this PR?

We'll be unable to verify if the links work without producing the first batch of images. That said, I'm fine either way.

document the error that is triggered when docker is too old for the multi arch container.

This is already documented on our landing page: https://github.com/NVIDIA/JAX-Toolbox#faq-frequently-asked-questions

It doesn't document the error with docker. The current docker error is related to the shared memory usage.

There is a second bullet point that refers to exactly the enroot vs. OCI issue:

We also need that for the CI container for manuel build. That can be a follow up pr.

CI already creates single-arch images, e.g. ghcr.io/nvidia/jax-toolbox-internal:6578372511-pax-amd64, but they are still encoded as a multi-arch manifest list that contains a single platform. This is just a natural consequence of using builtkit>0.10.6. If we downgrade buildkit, we will break how we current combine single-arch images (1, 2, and 3, etc.)
What do you suggest? @nouiz

Could we change the format when we make them public? One way I changed the format is by making a new simple container. Maybe there is a simpler way?

The old manifest format does not inherently store the OS/arch the image is associated with. If we convert it back to the old format, we have to infer the OS/arch by either:

pull the image and inspect the config (slow)
use tag to encode this information

The bottom line is that it isn't a good idea to walk backward towards an older technology, as we will have to upgrade to the new OCI format again in the future and then repeat the work to adapt to the new format.
How about we create another repo in addition to jax-toolbox-internal, say, naming it jax-toolbox-legacy, and put all old-format manifests there?

Merging as time is of essence here for this PR to help with 23.10 testing.
The failed tests also fail on the main branch: https://github.com/NVIDIA/JAX-Toolbox/actions/runs/6578998485. In addition, given that this PR only manipulates docker manifests, it is very unlikely that it causes the failure.

It doesn't document the error with docker. The current docker error is related to the shared memory usage.

There is a second bullet point that refers to exactly the enroot vs. OCI issue:

Yes, but the error aren't exacty the same. And people using docker won't look at the hidden error for a tool that they don't know. This is why we need both.

It doesn't document the error with docker. The current docker error is related to the shared memory usage.

There is a second bullet point that refers to exactly the enroot vs. OCI issue:

Yes, but the error aren't exacty the same. And people using docker won't look at the hidden error for a tool that they don't know. This is why we need both.

Wait, are you saying that even people using docker (not pyxis/enroot) are also having difficulties with the OCI manifest? Could you please provide an example of that error with docker?

Wait, are you saying that even people using docker (not pyxis/enroot) are also having difficulties with the OCI manifest? Could you please provide an example of that error with docker?

With old docker version. But yes, maybe we can wait for it to happen again before adding it to the faq.


Liver fluke images are cropped

Hi!
First of all MANY thanks for developing such an amazing toolbox for research illustration. I am really excited about bioicons, the icons are just beautiful and I'm glad that a free icon library is finally accessible to researchers.
I am opening this issue just to report that some of the liver fluke icons (e.g. sporocysts, rediae) are cropped. Some of borders of the images are missing.
Is there a way to access to the full images that I'm missing?
Many thanks in advance and sorry to bother with this
Cheers from South America!
Mauricio

I've just realized that when downloading the full svg-images the issue is resolved. I guess there is some issue when copying images online.
Closing the issue,
Cheers!


Upgrading from springboot 1.2.3 to Springboot 1.5.4

Hi, I would like to upgrade your excellent sample code to springboot v 1.5.4 that I am using myself.
Cheers
/Carl

Thanks! I made a couple small changes on top and merged it into master afterward.


vimPlugins.sniprun: 1.3.1 -> 1.3.3

Description of changes
Update the sniprun vim plugin to its latest version.
It was needed to manually add the Cargo.lock file as it was removed since the last release.
It was added back on the dev branch, so we might be able to get rid of this patch at the next release.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

vimPlugins.sniprun

@figsoda do you prefer to wait for the next release or adding (temporarily) this patch works fine for you ?

this patch works for me, mostly just waiting for ofborg so nixpkgs-review doesn't eat my laptop