Support updating Hyperdisk IOPS and throughput in Compute SDK

We want to modify the IOPS and throughput parameters of the hyperdisks using the Java Compute SDK. While we've come across documentation for achieving this via the REST API, we haven't been able to find any Java SDK documentation covering this topic. Could you let us know whether the Java SDK supports this operation? If it does, could you link us to the documentation? Otherwise, do you have an expected date for supporting this operation in the SDK?

I don't think this feature is supported in any SDKs yet and we don't have a expected date on SDK side. The Compute team would need to support it first then we can add the functionality in the SDKs. Can you please submit a feature request in the support console instead of filing on GitHub? Which should ensure a timely response from the Compute team.


Unknown  failure uploading files to threads

Jenkins and plugins versions report

Environment

Jenkins: 2.462.2
OS: Linux - 6.1.109-118.189.amzn2023.x86_64
Java: 17.0.12 - Amazon.com Inc. (OpenJDK 64-Bit Server VM)
---
analysis-model-api:12.5.0
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
apache-httpcomponents-client-5-api:5.3.1-117.v4d95117cd34f
asm-api:9.7-33.v4d23ef79fcc8
authentication-tokens:1.119.v50285141b_7e1
authorize-project:1.7.2
aws-credentials:231.v08a_59f17d742
aws-java-sdk-cloudformation:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-codebuild:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-ec2:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-ecr:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-ecs:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-efs:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-elasticbeanstalk:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-iam:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-kinesis:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-logs:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-minimal:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-secretsmanager:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-sns:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-sqs:1.12.767-467.vb_e93f0c614b_6
aws-java-sdk-ssm:1.12.767-467.vb_e93f0c614b_6
blueocean:1.27.16
blueocean-bitbucket-pipeline:1.27.16
blueocean-commons:1.27.16
blueocean-config:1.27.16
blueocean-core-js:1.27.16
blueocean-dashboard:1.27.16
blueocean-display-url:2.4.3
blueocean-events:1.27.16
blueocean-git-pipeline:1.27.16
blueocean-github-pipeline:1.27.16
blueocean-i18n:1.27.16
blueocean-jwt:1.27.16
blueocean-personalization:1.27.16
blueocean-pipeline-api-impl:1.27.16
blueocean-pipeline-editor:1.27.16
blueocean-pipeline-scm-api:1.27.16
blueocean-rest:1.27.16
blueocean-rest-impl:1.27.16
blueocean-web:1.27.16
bootstrap5-api:5.3.3-1
bouncycastle-api:<IP_ADDRESS>.1-248.ve27176eb_46cb_
branch-api:2.1178.v969d9eb_c728e
build-name-setter:2.4.3
build-timeout:1.33
build-user-vars-plugin:176.vb_9c7907fd524
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.2.1
cloudbees-bitbucket-branch-source:888.v8e6d479a_1730
cloudbees-folder:6.951.v5f91d88d76b_b_
command-launcher:115.vd8b_301cc15d0
commons-compress-api:1.26.1-2
commons-lang3-api:3.17.0-84.vb_b_938040b_078
commons-text-api:1.12.0-129.v99a_50df237f7
conditional-buildstep:1.4.3
configuration-as-code:1850.va_a_8c31d3158b_
copyartifact:749.vfb_dca_a_9b_6549
credentials:1378.v81ef4269d764
credentials-binding:681.vf91669a_32e45
dashboard-view:2.517.v776a_b_811a_b_4e
data-tables-api:2.1.6-1
display-url-api:2.204.vf6fddd8a_8b_e9
durable-task:577.v2a_8a_4b_7c0247
ec2:1688.v8c07e01d657f
echarts-api:5.5.1-1
eddsa-api:0.3.0-4.v84c6f0f4969e
embeddable-build-status:487.va_0ef04c898a_2
envinject:2.919.v009a_a_1067cd0
envinject-api:1.199.v3ce31253ed13
favorite:2.221.v19ca_666b_62f5
file-operations:266.v9d4e1eb_235b_a_
font-awesome-api:6.6.0-2
forensics-api:2.5.0
git:5.4.1
git-client:5.0.0
github:1.40.0
github-api:1.321-468.v6a_9f5f2d5a_7e
github-branch-source:1797.v86fdb_4d57d43
gson-api:2.11.0-41.v019fcf6125dc
handy-uri-templates-2-api:2.1.8-30.v7e777411b_148
htmlpublisher:1.36
instance-identity:185.v303dc7c645f9
ionicons-api:74.v93d5eb_813d5f
jackson2-api:2.17.0-379.v02de8ec9f64c
jakarta-activation-api:2.1.3-1
jakarta-mail-api:2.1.3-1
javax-activation-api:1.2.0-7
javax-mail-api:1.6.2-10
jaxb:2.3.9-1
jdk-tool:80.v8a_dee33ed6f0
jenkins-design-language:1.27.16
jjwt-api:0.11.5-112.ve82dfb_224b_a_d
job-dsl:1.89
jobConfigHistory:1264.v054b_c928547e
joda-time-api:2.13.0-85.vb_64d1c2921f1
jquery3-api:3.7.1-2
jsch:0.2.16-86.v42e010d9484b_
json-api:20240303-41.v94e11e6de726
json-path-api:2.9.0-58.v62e3e85b_a_655
junit:1300.v03d9d8a_cf1fb_
mailer:472.vf7c289a_4b_420
markdown-formatter:220.v1a_262cd9f77f
matrix-auth:3.2.2
matrix-project:832.va_66e270d2946
mina-sshd-api-common:2.13.2-125.v200281b_61d59
mina-sshd-api-core:2.13.2-125.v200281b_61d59
node-iterator-api:55.v3b_77d4032326
okhttp-api:4.11.0-172.vda_da_1feeb_c6e
p4:1.16.0
parameter-separator:166.vd0120849b_386
parameterized-scheduler:277.v61a_4b_a_49a_c5c
parameterized-trigger:806.vf6fff3e28c3e
permissive-script-security:0.7
pipeline-build-step:540.vb_e8849e1a_b_d8
pipeline-graph-analysis:216.vfd8b_ece330ca_
pipeline-groovy-lib:730.ve57b_34648c63
pipeline-input-step:495.ve9c153f6067b_
pipeline-milestone-step:119.vdfdc43fc3b_9a_
pipeline-model-api:2.2214.vb_b_34b_2ea_9b_83
pipeline-model-definition:2.2214.vb_b_34b_2ea_9b_83
pipeline-model-extensions:2.2214.vb_b_34b_2ea_9b_83
pipeline-rest-api:2.34
pipeline-stage-step:312.v8cd10304c27a_
pipeline-stage-tags-metadata:2.2214.vb_b_34b_2ea_9b_83
pipeline-stage-view:2.34
pipeline-utility-steps:2.17.0
plain-credentials:183.va_de8f1dd5a_2b_
plugin-util-api:4.1.0
prism-api:1.29.0-17
pubsub-light:1.18
rebuild:332.va_1ee476d8f6d
resource-disposer:0.23
role-strategy:743.v142ea_b_d5f1d3
run-condition:1.7
scm-api:696.v778d637b_a_762
script-security:1362.v67dc1f0e1b_b_3
slack:741.v00f9591c586d
snakeyaml-api:2.3-123.v13484c65210a_
sse-gateway:1.27
ssh-agent:376.v8933585c69d3
ssh-credentials:343.v884f71d78167
ssh-steps:2.0.68.va_d21a_12a_6476
sshd:3.330.vc866a_8389b_58
structs:338.v848422169819
throttle-concurrents:2.14
timestamper:1.27
token-macro:400.v35420b_922dcb_
trilead-api:2.147.vb_73cc728a_32e
variant:60.v7290fc0eb_b_cd
warnings-ng:11.6.0
workflow-aggregator:600.vb_57cdd26fdd7
workflow-api:1336.vee415d95c521
workflow-basic-steps:1058.vcb_fc1e3a_21a_9
workflow-cps:3964.v0767b_4b_a_0b_fa_
workflow-durable-task-step:1371.vb_7cec8f3b_95e
workflow-job:1436.vfa_244484591f
workflow-multibranch:795.ve0cb_1f45ca_9a_
workflow-scm-step:427.v4ca_6512e7df1
workflow-step-api:678.v3ee58b_469476
workflow-support:926.v9f4f9b_b_98c19

What Operating System are you using (both controller, and any agents involved in the problem)?
Windows Controller
Windows Agent
Reproduction steps
def fileName = "test.txt";
writeFile file: fileName, text: "Test File"

def channelName = 'test-builds'

// This posts a new message with the file but lacking any jenkins configured icon/username overrides
slackUploadFile(channel: channelName, filePath: fileName, initialComment: 'Original Message')

// Normal new message, respects jenkins configured icon/username overrides
def message = slackSend(channel: channelName, message: 'Test Thread')

// Fails to upload file
slackUploadFile(channel: message.threadId, filePath: fileName, initialComment: 'Using ThreadId')

// Says it may have failed to  upload file due to not finding the channel, but it does show up
slackUploadFile(channel: message.channelId, filePath: fileName, initialComment: 'Using Channel Id')

Expected Results
The above code should create a small file and upload it three different ways:

As a message in the channel 'test-builds' with the text 'Original Message'
As a reply 'Using Thread Id' to message 'Test Thread'
As a message in the channel 'test-builds' with the text 'Using Channel Id'

It is expected that there is no error output
It is expected the messages/threads should appear as described
It is expected the messages would respect the jenkins slack plugin configured user name and icon
Actual Results
Actual results are three messages as expected, but missing the threaded reply.
The two messages associated with a file upload are not respecting user icon or name.
Some logs exist for both the failed file upload, and for one that did not fail.

[Pipeline] writeFile
[Pipeline] slackUploadFile
[Pipeline] slackSend
Slack Send Pipeline step running, values are - baseUrl: <empty>, teamDomain: <redacted>, channel: test-builds, color: <empty>, botUser: true, tokenCredentialId: SlackBotToken, notifyCommitters: false, iconEmoji: :br3:, username: BRG Jenkins, timestamp: <empty>
[Pipeline] slackUploadFile
Using dirname=c:\jenkins\workspace\Shared\Test\TestCode and includeMask=test.txt
Adding file c:\jenkins\workspace\Shared\Test\TestCode\test.txt
ERROR: Failed uploading file to slack
[Pipeline] slackUploadFile
Using dirname=c:\jenkins\workspace\Shared\Test\TestCode and includeMask=test.txt
Adding file c:\jenkins\workspace\Shared\Test\TestCode\test.txt
Slack upload may have failed. Response: {"ok":false,"error":"channel_not_found"}
Failed to complete uploading file to Slack

Anything else?
This did not happen until we recently updated the Slack plugin. We update plugins about once a quarter. I believe prior to this I last updated July 18th/19th so my previous plugin version would have been from then.
Are you interested in contributing a fix?
No response

Can you check this please and see if it applies:
https://github.com/jenkinsci/slack-plugin/releases/tag/711.v41060f587001
Slack deprecated the API we were using for file upload so we had to change to one that worked a bit differently.

Oh yes, my apologies I did forget to mention as part of debugging this I did find in the Jenkins's log that additional permissions were required.
As part of debugging this I did grant those additional permissions. That shifted the behavior slightly, as two of the three cases above were failing before I fixed the permissions.
Unfortunately the one failing case still remains in this issue.

Is the bot invited into the channel?
Can you compare to this manifest?
https://github.com/jenkinsci/slack-plugin#creating-your-app

Yes, the bot is invited to the channel. As per the "Actual Results" you can see the bot (both with and without user overrides applying) posting successfully to the channel.
As for the manifest, I am not sure how to view my own in manifest form but the permissions applied are:
*chat:write
*chat:write.customize
*files:write
*reactions:write
+im:read
+mpim:read
*channels:read
*groups:read
*users:read
*users:read.email
Looks like I have them all (*) then two more (+). Those two more were listed in the jenkins log when I first started hitting this issue along with channels:read and groups:read so I added all four.

see here for viewing the manifest:
https://api.slack.com/reference/manifests#updating

{
    "display_information": {
        "name": "Jenkins",
        "description": "Jenkins Build Service",
        "background_color": "#000060"
    },
    "features": {
        "bot_user": {
            "display_name": "Jenkins",
            "always_online": true
        }
    },
    "oauth_config": {
        "scopes": {
            "bot": [
                "chat:write",
                "chat:write.customize",
                "files:write",
                "reactions:write",
                "users:read",
                "users:read.email",
                "channels:read",
                "groups:read",
                "mpim:read",
                "im:read"
            ]
        }
    },
    "settings": {
        "org_deploy_enabled": false,
        "socket_mode_enabled": false,
        "token_rotation_enabled": false
    }
}

I take this all to mean the reproduction steps I provided do not reproduce?
I got it down to a fairly short and sweet example so was hoping they would be enlightening, maybe something about my environment though is interfering?

Apologies I misunderstood, I can reproduce it and am looking into it

No worries, glad to hear and appreciate your work.


Build python 3.12 wheels

Issue
Wheels for Python 3.12 are missing.
Description of changes

Updating workflow to build wheels for Python 3.12
Removing building wheels for Python 3.7 which is already out-of-life

Includes

[ ] Code changes
[ ] Tests
[ ] Documentation

Build passes: https://dev.azure.com/pavlingp/openTSNE/_build/results?buildId=620&view=results

Thanks for the PR. Just for consistency's sake, could you please also update the following:

the CI spec for the testing jobs in azure-pipelines.yml
the reference to Python 3.7 in the readme
the install_requires field in setup.py

Done. I didn't find any other place mentioning python version

Thank you! I'll try to push out a new release by the end of the week.


test(transformer): more tests for arrow function transform

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5849  👈
#5848
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


haplotype coordinates in GRCh38

I'd like to figure out where these haplotypes came from. Unfortunately, I can't seem to find the epost utility that you used to get the coordinates. Where is this from?

Whoops, it seems GeneRefSeqCoordinates has what I want.

@ekg  I could pull the coordinates from that folder out into a spreadsheet, if you think other people would find it helpful for verifying the files.

What I just realized is that I'm after something different, which is where
the haplotypes map in the complete chromosomes in the genome.
This would greatly simplify the process of constructing a graph from them.
On Feb 24, 2015 3:45 PM, "nouyang-curoverse"<EMAIL_ADDRESS>wrote:

@ekg https://github.com/ekg I could pull the coordinates from that
folder out into a spreadsheet, if you think other people would find it
helpful for verifying the files.
—
Reply to this email directly or view it on GitHub
https://github.com/nouyang-curoverse/GA4GH_regions/issues/1#issuecomment-75780884
.

I think I've found the information I'm after. It's just a table of mappings between the alts and the primary chromosomes.

@ekg Awesome that you got an answer on twitter!


"Nagions" should be "Nagios“

“NRPE” refers to "Nagios Remote Execution Protocol"  :P

/assign

changed as prompt :p

/lgtm


Provider complaining about hot reloading store

Whenever I change store related code, I get the following message:
<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/rackt/react-redux/releases/tag/v2.0.0 for the migration instructions.

My store setup looks like this:
import reducers from './reducers/index'

const devStore = () => {
    const store = createStore(
        reducers,
        initialState,
        compose(
            middleware
        )
    )

    if (module.hot) {
        module.hot.accept('./reducers', () => {
            const nextRootReducer = require('./reducers/index')
            store.replaceReducer(nextRootReducer)
        })
    }

    return store
}

const store = env.ENVIRONMENT == 'production' ? prodStore() : devStore()

export { store as default }

My module.hot check is in place. I am not sure how to go about debugging this. Any help is appreciated.

Since you import <Provider> from react-redux, https://github.com/reactjs/react-redux would be a more appropriate place for this issue.
What do you call “store-related code”? Updates to store.js are not supposed to be handled, so the warning sounds correct to me. Updates to reducers should be handled by that module.hot code.
If you still have issues please attach a project reproducing the issue. I’m closing because this is a Webpack usage question and not the library issue, and it is not about this repository.

By store related code I mean actions or sagas. If it's expected to not hot reload actions or sagas then I will leave this as is, else I will open an issue under react-redux

Sagas don’t currently hot reload. (I’m actually not sure why; it feels like pausing existing sagas and restarting them would be a “good enough” solution for most cases. I think it would be great if there was something like sagaMiddleware.replaceSagas(...sagas) method. See also https://github.com/yelouafi/redux-saga/issues/22.)

And action creators likely don’t hot reload for you because you import them from sagas.

Ah so there lies the problem. Glancing over that issue I can see how time travel is a problem with sagas, although I don't exactly need time travel in my use case so something like replaceSaga would be very useful.
Anyway thanks for helping out, was bugging me for some time now

No problem. I think you would be welcome sending a PR to Redux Saga to implement something like replaceSaga and starting a discussion around it. cc @yelouafi

any word on sagas hot loading?

Please discuss this in Redux Saga repo. We’re not personally developing it 😉


Read file

Describe the need of your request
Hi author, is it possible to add a function that reads a file or references a file?
Optimised token formatting to recognise replicated IDEA token formats.
Proposed solution
No response
Additional context
No response

Hey, wdym by a function that reads a file or references a file?
Would this work?

Right-click on a project file/folder -> CodeGPT -> Include in Context...

Hi, what I mean is that it's possible to add a reference/context reading
feature?
Carl-Robert @.***> 于2024年3月28日周四 18:47写道：

Hey, wdym by a function that reads a file or references a file?
Would this work?
Screenshot.2024-03-28.at.12.44.13.png (view on web)
https://github.com/carlrobertoh/CodeGPT/assets/15891408/c323999a-d477-4123-b58b-f671c3c39027
Right-click on a project file/folder -> CodeGPT -> Include in Context...
—
Reply to this email directly, view it on GitHub
https://github.com/carlrobertoh/CodeGPT/issues/428#issuecomment-2024895067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5VG3TPB7SEJ6E5DYRQIIYDY2PRMDAVCNFSM6AAAAABFLD6BMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUHA4TKMBWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks @carlrobertoh! I had this exact same question and your answer provided what I needed. I was expecting this option to be in the context menu for the currently open file similar to how github copilot has it.

copilot context menu for reference

@Soufdsfe65w just to reiterate what @carlrobertoh had said, right click on the left side in the project view for this option.

Thanks, I saw it. Special thanks.

@WilliamEddy Nice, I didn't think of that. I'll add it to the editor's context menu as well. 👍


Links nao encontrados

Nao consigo abrir nenhum Filme para visualizar. A resposta e sempre a mesma: Nao se encontram Links

@antonsoroko burst Does it only recognize magnet link? https://paste.kodi.tv/quseceqemu I'm having a problem with a provider the link is to download the .torrent file

@icarok99 please do not hijack other persons issues :-) create new issue. i do not want to mix different things.


New feature

New features ability to dump / load some feeds at some date in a new arangoDB database

Close by commit d6275efd6c134ccae7d3e11067572cd7b12da338.


Staff role authorisation

Context
CBL has a support interface where we manage application config and upload additions to the data. This section of the service should only be available to users with the internal user role from DSI internal organisation.
Changes proposed in this pull request

switch to DB sessions. We're overflowing the cookie by putting the ID token in it from DSI. Doing it this way rather than storing the token on the dsi_user_session model means we can prune the old ones easily out of the database.
Add an extra env var for internal user and add DsiUser#internal? to allow us to identify internal users throughout the service. We already store the role on the DsiUserSession model so I've just exposed the current one through the user
Scope features and the upload stuff under SupportInterface::SupportInterfaceController and enforce the authorisation in there.
Remove a bit of unused code
Fix the path helper scoping in the support interface. This is currently causing errors in main.

Guidance to review
Probably needs a bit of finessing of local env to move the role that DSI returns between the standard and internal env vars. The internal role should be able to access everything, a standard role only things outside of the SupportInterface scope and a role not in either shouldn't have any access.
Checklist

[x] Attach to Trello card
[x] Rebased main
[x] Cleaned commit history
[x] Tested by running locally

 Check for staff role


Caching + Changing the Api Key

Hello, that's more of a question than a problem.
If i'm using caching and change the api key, as far as i understand, the claude backend thinks that it's a different chat(i might be wrong, sorry if i am).
Hence the caching system breaks once i change the api key, since it "stays" with previous chat and api key in the backend of claude ai?
Let's say i work with API1, give the code to cache and everything.
Then i change to API2(since i've used more than 1mil tokens)
All the previous caching is still intact and system uses its correctly, or there's some reason to not do that?
==End of the main question==
Also, a real newbie question, would be great if somebody would answer this aswell - i've seen some good changes in pull requests, is it hard to use them in my version of claude-dev so i might do some testing for those pulls? Cause there're some features which i've really wanted.

Hello! You're right about caching being tied to the account/api key, so in your case it will not be able to reuse caches.
As for the PRs, you just need to git clone them, follow the instructions in the readme (under Contribution) and you can run it in a debugger or use vsce package to create a vsix that you can download (similar to an update).


Define vim color scheme related to the windows terminal theme

Hello,
I'd like to be able to apply the good vim's color scheme in accordance with the windows terminal theme defined.
In putty or Iterm, I use a variable defined when loading the profile whether it is a dark or bright theme that  I can reuse later according to what I wanna do.
So, Is there an already integrated solution or has anyone ever tried to do that ?
Thanks in advance.

What variable is that? If there is prior art for exposing the terminal's color scheme to connected applications, we could consider following it.

I don't understand.
I just wanna apply the correct color scheme in my vim editor related to my terminal color scheme.
For example, If I launch my terminal in a bright mode, i wanna get my vim editor in a bright mode too, so how can i get the terminal color scheme information in order to be able to detect it in my vimrc file and apply it when it's needed, and the same in reverse for a dark display ?

#3718  could be a solution. Unfortunately WT has not yet support it.

Sorry, I had forgotten this issue.
I've found the solution in the meantime, you juste have to get WT_PROFILE_ID variable's content which corresponds to your loaded profile's id with colorization etc ...
Then from there, if your .bashrc configuration is well designed, you can autodetect all other colorization's parameters like in vim for example.
I'm gonna close the issue.


Update Klarna payment provider to v3 API

Current Klarna payment provider is using the v2 API but the current Klarna API is v3. We need to create a v3 version of the payment provider to allow people to upgrade.

Will be solved by PR #26
Closing issue, can continue convo on the PR


[spaceship] add update method to ConnectAPI::User

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
We want to have the ability to change user roles and app access. And for that, we need Modify a User Account
API implemented.
Description

Add a new request to update user. We can modify the User instance and just execute update or describe changes using parameters.
Fix UserInvitation.create docs.
Remove relationships for User.update & UserInvitation.requests if all apps are allowed to reduce the number of API errors.

Testing Steps
users = Spaceship::ConnectAPI::User.all
users.first.update(provisioning_allowed: false, roles: ['SALES'])

last_user = users.last
last_user.provisioning_allowed = false
last_user.roles = ['SALES', 'DEVELOPER']
last_user.update

@revolter , sorry for the ping, but if there is something I can improve?

@joshdholtz , do I have any chances you review this PR🙏 ?

@ainame , @rogerluan , any kind of feedback is appreciated 🙏 .

Any chances of merging this?

I took another look, and, again, it doesn't look like it could break existing logic, it rather adds new logic, so I will merge this.


[FEATURE REQUEST] Add a standard default window layout.

Description
We should use LayoutRoot to implement a standard window layout for new users instead of relying on a pre-saved layout configuration.
The Why
This will ensure the application will look the same across different monitors and we won't have to worry about shipping a layout configuration for each release.
The How
We should look at the current layout configuration and determine how we can adjust DockView to create a standard layout - or alternatively, we can create a default_layout.config file that is shipped with each release.
Requirements
🚧🚧🚧
Possible Issues
Please list any possible issues that may arise when attempting to implement this feature.

Fixed #227


Add technical committee members

List of accounts taken from here: https://github.com/OpenRailAssociation/technical-committee/pull/115
This should enable us to assign TC members to issues.

I would suggest to mark the people we have listed as maintainers at https://github.com/OpenRailAssociation/technical-committee/blob/main/MAINTAINERS.md as maintainers here as well, not only the chair of the TC. This gives us a bit more redundancy.
Adding the other members looks good.

Thanks for the feedback. I took this a bit further and create a separate group for the maintainers. This allows them to make changes in this repo.
The way I designed it, we'd only have to add people once in technical-committee.yaml. The maintainers are allowed to create PRs here and approve them for the two TC teams.


getProducts works, but requestPurchase fails

Version of react-native-iap
^3.0.0-rc.2
Version of react-native
0.59.5
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
const products = await RNIap.getProducts(preorders);
Result: Products: Two products with productIds 'xyz1', 'xyz2'
const purchase = await RNIap.requestPurchase('xyz1');
Expected: Purchase successful.
Actual behavior
const products = await RNIap.getProducts(preorders);
Result: Products: Two products with productIds 'xyz1', 'xyz2'
const purchase = await RNIap.requestPurchase('xyz1');
Actually: 'PROMISE_BUY_ITEM', 'The sku was not found. Please fetch products first by calling getItems'
Tested environment (Emulator? Real Device?)
Real Device Samsung S8
Steps to reproduce the behavior
As described above.
This even happens when directly before the purchase, I fetch the products again via RNIap.getProducts('skus').
PlayStore since more than 24h:
Beta Release: 0.3.0
Full rollout.
1 app bundle, version code: 1

@joeroos Could you tell what you're receivin in purchaseUpdatedListener?
purchaseUpdateSubscription = purchaseUpdatedListener((purchase: ProductPurchase) => {
      console.log('purchaseUpdatedListener', purchase);
      this.setState({ receipt: purchase.transactionReceipt }, () => this.goNext());
    });
    purchaseErrorSubscription = purchaseErrorListener((error: PurchaseError) => {
      console.log('purchaseErrorListener', error);
      Alert.alert('purchase error', JSON.stringify(error));
    });

Also please try 3.0.0-rc.7 if not working as expected. Feel free to reopen when you still face the problem.

Hi @hyochan I upgraded to 3.0.0-rc.7. Still the same mistake.
Additionally, I found that in the index.d.ts, purchaseUpdateListener is exported twice, but purchaseErrorListener never. I assume this is a bug.
purchaseUpdateListener does not give any output! purchaseErrorListener I cannot say as it fails upon initiation (probably due to the bug I mentioned above).

So I removed purchaseErrorListener and changed the functions to not await the purchase, but just call RNIap.requestPurchase(sku);
Now function looks like this:
buyProduct = async (sku) => {     console.info(buy: ${sku});     try {       console.log('Trying to requestPurchase with ID', sku);       RNIap.requestPurchase(sku);     } catch (err) {       console.warn(err.code, err.message);       Alert.alert('Error while buying', err.message);     }     console.log('finished buyProduct');   };
Console output:
'Trying to requestPurchase with ID ', 'xyz1'
finished BuyProduct
Around 2s later:
Possible Unhandled Promise Rejection (id: 1):
Error: The sku was not found. Please fetch products first by calling getItems

Typo is fixed in 3.0.0-rc.8. Could you provide a full code of yours? I don't understand your symptoms. Also, could you try the example project first?

i have same issue
i have used listener and i got this
purchaseErrorListener {debugMessage: "The sku was not found. Please fetch products first by calling getItems"}

@yogeshmoradiya121 Which version are you using? Please try the recent one.

"react-native-iap": "^3.3.2",
"react-native": "0.60.3",

Could you provide any message I can look up?

Same here. I get an error message: This item is unavailable.
"react-native-iap": "^3.3.5",
"react-native": "0.60.0",

Same here. I get an error message: This item is unavailable.
purchaseErrorListener:{"responseCode":4}
"react-native-iap": "^3.3.5",
"react-native": "0.60.0",
same problem
but it is not observed on all devices.
on some devices a can bay subscriptions

I'm experiencing the same problem with a more recent version of RN and RN IAP.
"react-native-iap": "^4.2.2",
"react-native": "0.61.5",

Experiencing the same problem
"react-native": "0.59.8",
"react-native-iap": "^4.3.0"

Same to me. It only happens on Android devices (not all, some of them)
"react-native-iap": "^4.3.2"
"react-native": "0.61.4"

Could you share some useful information other than the versions? Something like code snippets or minimal reproduction so I can move this forward.
Also please try out the latest version which currently is 4.4.4.
Thanks.

It is working for me now, sadly I've lost context.
But remember the Issue being in project code.
Will update when I remember.

same issue facing on iap : 4.5.0

Same issue  on iap 4.5.4


Fix templates and ISOs listing pagination

Description
After the changes in #4774, when an account other than the root admin lists templates/ISOs with pagination, count gets set to the number of items returned in that page. For example, when the user lists 10 templates/ISOs and 15 entries are found, in the first page, count is set to 10 (the number of items being returned), as opposed to 15 (the total number of items). As a result, the deploy VM wizard only shows the first page of templates/ISOs.
This PR fixes this behavior and makes count return the correct number of found entries.
Types of changes

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

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Everything has been tested in a local lab.
In the tested scenario, the following domains have templates:

ROOT: 13 public and featured templates;
ROOT/test: 4 public and featured templates.

CloudMonkey command used to list templates.

list templates templatefilter=featured page=1 pageSize=5

In every test, the expected number of templates/ISOs was returned.
With share.public.templates.with.other.domains set to true in both domains:

In the root admin account, I listed the templates. I verified that the expected value of 17 was returned;
In a user account belonging to ROOT, I listed the templates. I verified that the expected value of 17 was returned;
In a user account belonging to ROOT/test, I listed the templates. I verified that the expected value of 17 was returned;
I marked a template belonging to ROOT as not public. Then, in a user account belonging to ROOT, I listed the templates. I verified that the expected value of 16 was returned;
I marked a template belonging to ROOT as not public. Then, in a user account belonging to ROOT/test, I listed the templates. I verified that the expected value of 16 was returned;
I marked a template belonging to ROOT/test as not public. Then, in a user account belonging to ROOT, I listed the templates. I verified that the expected value of 16 was returned;
I marked a template belonging to ROOT/test as not public. Then, in a user account belonging to ROOT/test, I listed the template. I verified that the expected value of 16 was returned.

With share.public.templates.with.other.domains set to false in both domains:

In the root admin account, I listed the templates. I verified that the expected value of 17 was returned;
In a user account belonging to ROOT, I listed the templates. I verified that the expected value of 13 was returned;
In a user account belonging to ROOT/test, I listed the templates. I verified that the expected value of 4 was returned;
I marked a template belonging to ROOT as not public. Then, in a user account belonging to ROOT, I listed the templates. I verified that the expected value of 12 was returned;
I marked a template belonging to ROOT as not public. Then, in a user account belonging to ROOT/test, I listed the templates. I verified that the expected value of 4 was returned;
I marked a template belonging to ROOT/test as not public. Then, in a user account belonging to ROOT, I listed the templates. I verified that the expected value of 13 was returned;
I marked a template belonging to ROOT/test as not public. Then, in a user account belonging to ROOT/test, I listed the template. I verified that the expected value of 3 was returned.

I also verified the behavior of the listIsos API. In the tested scenario, the following domains have ISOs:

ROOT: 11 public and featured ISOs;
ROOT/test: 2 public and featured ISOs.

CloudMonkey command used to list ISOs.

list isos page=1 pageSize=5 isoFilter=featured bootable=true

With share.public.templates.with.other.domains set to true in both domains:

In the root admin account, I listed the ISOs. I verified that the expected value of 13 was returned;
In a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 13 was returned;
In a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 13 was returned;
I marked an ISO belonging to ROOT as not public. Then, in a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 12 was returned;
I marked an ISO belonging to ROOT as not public. Then, in a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 12 was returned;
I marked an ISO belonging to ROOT/test as not public. Then, in a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 12 was returned;
I marked an ISO belonging to ROOT/test as not public. Then, in a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 12 was returned.

With share.public.templates.with.other.domains set to false in both domains:

In the root admin account, I listed the ISOs. I verified that the expected value of 13 was returned;
In a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 11 was returned;
In a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 2 was returned;
I marked an ISO belonging to ROOT as not public. Then, in a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 10 was returned;
I marked an ISO belonging to ROOT as not public. Then, in a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 2 was returned;
I marked an ISO belonging to ROOT/test as not public. Then, in a user account belonging to ROOT, I listed the ISOs. I verified that the expected value of 11 was returned;
I marked an ISO belonging to ROOT/test as not public. Then, in a user account belonging to ROOT/test, I listed the ISOs. I verified that the expected value of 1 was returned.

I also verified the changes in the UI. Before, the deploy VM wizard showed only one page of templates/ISOs. After the changes, all pages are shown as expected.

@blueorangutan package

@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 7057

@blueorangutan test

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

[SF] Trillian test result (tid-7688)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43052 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7974-t7688-kvm-centos7.zip
Smoke tests completed. 107 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_upgrade_kubernetes_cluster
Failure
575.22
test_kubernetes_clusters.py

@blueorangutan package

@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 7149

@blueorangutan test

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

[SF] Trillian test result (tid-7756)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 52974 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7974-t7756-kvm-centos7.zip
Smoke tests completed. 107 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_invalid_upgrade_kubernetes_cluster
Failure
3623.09
test_kubernetes_clusters.py

test_02_upgrade_kubernetes_cluster
Failure
3615.24
test_kubernetes_clusters.py

test_03_deploy_and_scale_kubernetes_cluster
Failure
0.06
test_kubernetes_clusters.py

test_04_autoscale_kubernetes_cluster
Failure
0.03
test_kubernetes_clusters.py

test_05_basic_lifecycle_kubernetes_cluster
Failure
0.03
test_kubernetes_clusters.py

test_06_delete_kubernetes_cluster
Failure
0.03
test_kubernetes_clusters.py

test_07_deploy_kubernetes_ha_cluster
Failure
0.04
test_kubernetes_clusters.py

test_08_upgrade_kubernetes_ha_cluster
Failure
0.04
test_kubernetes_clusters.py

test_09_delete_kubernetes_ha_cluster
Failure
0.03
test_kubernetes_clusters.py

test_10_vpc_tier_kubernetes_cluster
Failure
50.90
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
126.40
test_kubernetes_clusters.py

@shwstppr @DaanHoogland it would be interesting to have this fix on 4.19

@hsato03 are you allright with this PR like this?
@winterhazel , did you get some 3rd party testing?

Code LGTM

@winterhazel , did you get some 3rd party testing?

@DaanHoogland yes, some users have tested these changes; I will ask them to report the results here.

@blueorangutan package

@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 7285

@blueorangutan test

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

[SF] Trillian test result (tid-7896)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41089 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7974-t7896-kvm-centos7.zip
Smoke tests completed. 113 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@winterhazel , did you get some 3rd party testing?

@DaanHoogland yes, some users have tested these changes; I will ask them to report the results here.

It would be nice to see those, thanks.

I have tested this PR by replicating the tests on my local lab. First, I tested on the current main and verified the problem was present. Then, I applied the changes and verified it had been fixed.
My scenario had the same amount of domains, templates and ISOs (ROOT with 13 and 11 and ROOT/test with 4 and 2), and I used the same commands to list templates and ISOs.

Templates:

Without the changes
With share.public.templates.with.other.domains set to true in both domains:

Domain
Account
count

ROOT
Admin
17

ROOT
User
5

ROOT/test
TestAdmin
5

ROOT/test
TestUser
5

I marked one of the ROOT templates as non-public. It stopped showing in templatefilter=featured for all accounts:

Domain
Account
count

ROOT
Admin
16

ROOT
User
5

ROOT/test
TestAdmin
5

ROOT/test
TestUser
5

With share.public.templates.with.other.domains set to false in both domains:

Domain
Account
count

ROOT
Admin
17

ROOT
User
5

ROOT/test
TestAdmin
Empty

ROOT/test
TestUser
Empty

With the changes
With share.public.templates.with.other.domains set to true in both domains:

Domain
Account
count

ROOT
Admin
17

ROOT
User
17

ROOT/test
TestAdmin
17

ROOT/test
TestUser
17

I marked one of the templates as non-public. It stopped showing in templatefilter=featured for all accounts. The first column indicates the domain of the non-public template:

Template Domain
Domain
Account
count

ROOT
ROOT
Admin
16

ROOT
ROOT
User
16

ROOT
ROOT/test
TestAdmin
16

ROOT
ROOT/test
TestUser
16

ROOT/test
ROOT
Admin
16

ROOT/test
ROOT
User
16

ROOT/test
ROOT/test
TestAdmin
16

ROOT/test
ROOT/test
TestUser
16

With share.public.templates.with.other.domains set to false in both domains:

Domain
Account
count

ROOT
Admin
17

ROOT
User
13

ROOT/test
TestAdmin
4

ROOT/test
TestUser
4

With share.public.templates.with.other.domains set to false in both domains. The first column indicates the domain of the non-public template:

Template Domain
Domain
Account
count

ROOT
ROOT
Admin
16

ROOT
ROOT
User
12

ROOT
ROOT/test
TestAdmin
4

ROOT
ROOT/test
TestUser
4

ROOT/test
ROOT
Admin
16

ROOT/test
ROOT
User
13

ROOT/test
ROOT/test
TestAdmin
3

ROOT/test
ROOT/test
TestUser
3

ISOs:

Without the changes
With share.public.templates.with.other.domains set to true in both domains:

Domain
Account
Count

ROOT
Admin
13

ROOT
User
5

ROOT/test
TestAdmin
5

ROOT/test
TestUser
5

I marked one of the ROOT ISOs as non-public. It stopped showing in isofilter=featured for all accounts:

Domain
Account
count

ROOT
Admin
12

ROOT
User
5

ROOT/test
TestAdmin
5

ROOT/test
TestUser
5

With share.public.templates.with.other.domains set to false in both domains:

Domain
Account
count

ROOT
Admin
13

ROOT
User
5

ROOT/test
TestAdmin
Empty

ROOT/test
TestUser
Empty

With the changes
With share.public.templates.with.other.domains set to true in both domains:

Domain
Account
count

ROOT
Admin
13

ROOT
User
13

ROOT/test
TestAdmin
13

ROOT/test
TestUser
13

I marked one of the ISOs as non-public. It stopped showing in isofilter=featured, for all accounts. The first column indicates the domain of the non-public ISO:

ISO Domain
Domain
Account
Count

ROOT
ROOT
Admin
12

ROOT
ROOT
User
12

ROOT
ROOT/test
TestAdmin
12

ROOT
ROOT/test
TestUser
12

ROOT/test
ROOT
Admin
12

ROOT/test
ROOT
User
12

ROOT/test
ROOT/test
TestAdmin
12

ROOT/test
ROOT/test
TestUser
12

With share.public.templates.with.other.domains set to false in both domains:

Domain
Account
Count

ROOT
Admin
13

ROOT
User
11

ROOT/test
TestAdmin
2

ROOT/test
TestUser
2

I marked one of the ISOs as non-public. It stopped showing with isofilter=featured for all accounts. The first column indicates the domain of the non-public ISO:

ISO Domain
Domain
Account
Count

ROOT
ROOT
Admin
12

ROOT
ROOT
User
10

ROOT
ROOT/test
TestAdmin
2

ROOT
ROOT/test
TestUser
2

ROOT/test
ROOT
Admin
12

ROOT/test
ROOT
User
11

ROOT/test
ROOT/test
TestAdmin
1

ROOT/test
ROOT/test
TestUser
1

My testing yielded the same results. The only caveat is that the featured not-public templates do not show under the featured filter to anyone. However, this situation was observed even without the patch; therefore, it is outside the scope of this PR,

@hsato03 Do you think this is ready for merge, now?

@DaanHoogland Yes, CLGTM.


Strings don't appear inline when switching to Low Level IL on ARM

Looking at an assembly graph, strings appear inline for both x86 and arm, but if I switch to the LLIL graph, the strings are only there for x86. In this case, the instruction at 0x10448 is loading from a non-writeable section.
hello.zip

This has been resolved since some time before the latest stable. Sorry we missed closing it.


Got error while running 248-stable-diffusion-xl

I am running on Serpent Canyon which has arc 770 GPU. I got this error:-
Compiling the vae_decoder...
RuntimeError                              Traceback (most recent call last)
Cell In[3], line 5
3     text2image_pipe.half()
4     text2image_pipe.save_pretrained(model_dir)
----> 5     text2image_pipe.compile()
6 else:
7     text2image_pipe = OVStableDiffusionXLPipeline.from_pretrained(model_dir, device=device.value)
File ~\anaconda3\envs\sdxl\lib\site-packages\optimum\intel\openvino\modeling_diffusion.py:487, in OVStableDiffusionPipelineBase.compile(self)
486 def compile(self):
--> 487     self.vae_decoder._compile()
488     self.unet._compile()
489     for component in {self.text_encoder, self.text_encoder_2, self.vae_encoder}:
File ~\anaconda3\envs\sdxl\lib\site-packages\optimum\intel\openvino\modeling_diffusion.py:533, in OVModelPart._compile(self)
531 if self.request is None:
532     logger.info(f"Compiling the {self._model_name}...")
--> 533     self.request = core.compile_model(self.model, self.device, self.ov_config)
File ~\anaconda3\envs\sdxl\lib\site-packages\openvino\runtime\ie_api.py:543, in Core.compile_model(self, model, device_name, config)
537 if device_name is None:
538     return CompiledModel(
539         super().compile_model(model, {} if config is None else config),
540     )
542 return CompiledModel(
--> 543     super().compile_model(model, device_name, {} if config is None else config),
544 )
RuntimeError: Exception from src\inference\src\core.cpp:118:
[ GENERAL_ERROR ] Check 'false' failed at src\plugins\intel_gpu\src\plugin\program.cpp:401:
GPU program build failed!
Exception from src\plugins\intel_gpu\src\graph\include\primitive_type_base.h:58:
[GPU] Can't choose implementation for constant:Reshape_261408_reorder_convolution:/decoder/up_blocks.0/resnets.2/conv2/Conv/WithoutBiases node (type=reorder)
[GPU] Original name:
[GPU] Original type:
[GPU] Reason: vector too long

Hi @tarunmcom, I also observed a similar issue when running the notebook.

I will highlight the issues with the relevant team and update here soon.

@tarunmcom I see different errors when executing on iGPU vs dGPU (Arc A770 16GB), sometimes the kernel gets shutdown due to system being out of Memory (my system only has 16GB of RAM), and I also observed a [ GENERAL_ERROR ] get_shape was called on a descriptor::Tensor with dynamic shape error when compiling the vae_encoder. FYI we've shared this with the development team, as soon as we have any updates to share we will let you know.
Ref. 118872

@tarunmcom there are two issues that needed to be addressed, the first one is that some of the demonstrated models in this notebook can require at least 64GB RAM for conversion and running. Please ensure your system has enough memory, otherwise the Linux kernel may kill the notebook as it consumes large amounts of memory.
For the second issue faced, openvino==2023.1.0.dev20230811 has a fix for get_shape() dynamic shape runtime error.
Please try the latest notebook (commit e31ac564d64c25094601c5b5297d1434d2c59942) with clean python environment. The clean python environment can get the latest optimum version. Then all the outputs with GPU.1 (Arc A770) are good and functional. Let us know if you have any additional questions or if the issue persists, hope this helps.

Closing this as issue has been addressed. Feel free to reopen if you have any additional questions or if the issue persists.


XBee: Use dict for response event data

Since https://github.com/home-assistant/core/pull/69631 ZHA now requires the event data to be dict and does not accepts plain strings (see https://github.com/home-assistant/core/blob/dev/homeassistant/components/zha/core/channels/base.py#L405).
This PR fixes XBee quirk to provide that. The data for Serial data event is sent as {"data": ...} and the AT command responses are sent as {"response": ...}.
Also updating some outdated info in readme for PWM.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.556%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6061

Relevant Lines:
7524

💛  - Coveralls

Codecov Report
Base: 80.55% // Head: 80.55% // No change to project coverage :thumbsup:

Coverage data is based on head (968635f) compared to base (f282203).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #1857   +/-   ##
=======================================
  Coverage   80.55%   80.55%
=======================================
  Files         242      242
  Lines        7524     7524
=======================================
  Hits         6061     6061
  Misses       1463     1463

Impacted Files
Coverage Δ

zhaquirks/xbee/__init__.py
42.85% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

the referenced PR restored list functionality. This should not be necessary. What is the issue you are trying to fix. Please include debug logs from your automation that isn't working.

We are trying to send a plain number or a string, not list.
Here is an example log, I think it can explain better than me:
DEBUG [zigpy_xbee.uart] Frame received: b'\x97\xe4\x00\x13\xa2\x00A\xa0~\x1aH\x7fTP\x00\x005'
DEBUG [zigpy_xbee.api] Frame received: remote_at_response
DEBUG [zigpy_xbee.api] Remote AT command response from: (228, 00:13:a2:00:41:a0:7e:1a, 0x487f, b'TP', 0, b'\x005')
WARNING [zigpy.util] Error calling listener <bound method ZigbeeChannel.zha_send_event of <homeassistant.components.zha.core.channels.general.LevelControlClientChannel object at 0xacf25e68>> with args ('tp_command_response', 53): TypeError("Unexpected zha_send_event 'tp_command_response' argument: 53")
DEBUG [zigpy.util] Error calling listener <bound method ZigbeeChannel.zha_send_event of <homeassistant.components.zha.core.channels.general.LevelControlClientChannel object at 0xacf25e68>> with args ('tp_command_response', 53)
Traceback (most recent call last):
  File "/srv/homeassistant/deps/lib/python3.10/site-packages/zigpy/util.py", line 55, in listener_event
    result.append(method(*args))
  File "/usr/lib/python3.10/site-packages/homeassistant/components/zha/core/channels/base.py", line 405, in zha_send_event
    raise TypeError(f"Unexpected zha_send_event {command!r} argument: {arg!r}")
TypeError: Unexpected zha_send_event 'tp_command_response' argument: 53

can you add some tests for this? We are trying to get the test coverage up for all custom logic like this.

Will try

Done, added some tests (and done some other small fixes along the way)

Done, added some tests (and done some other small fixes along the way)

Thanks!


enable es6 class inheritance

resolves #23
It seems that the tests are broken even without my change. This should
be fixed before merging to ensure the compatibility to older versions.

It doesn't work without a BLE device. Make sense. Maybe we should mock noble in the future.
The test are now passing, but are a bit unstable (sometimes, some tests are failing). I think it depends on the bluetooth device, to which noble is connecting to.

It doesn't work without a BLE device. Make sense. Maybe we should mock noble in the future.

Yes, this is discussed in https://github.com/sandeepmistry/noble-device/pull/22#issuecomment-244797368
What versions of Node.js have you tested this with? I'd like to ideally support v0.10.x or v0.12.x for now ...

Anyone working on this ? Any ideas when this might bet implemented ?


Support ~/.aws/config with instance profile

Fix https://github.com/sonots/ec2-host/pull/15#issuecomment-460504160

1.0.2 is released.

@toyama0919 can you check assume role is working well?

not works assume role..
bug fix PR is there.
https://github.com/sonots/ec2-host/pull/18


Add the package version to README without pypi.

Can someone help with this? Thank you devs.

I don't understand the question. If there's still confusion, could you clarify?


SCB-678 Optimize govern api

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run go build go test go fmt go vet to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #375 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #375   +/-   ##
=======================================
  Coverage   69.94%   69.94%
=======================================
  Files          25       25
  Lines        3746     3746
=======================================
  Hits         2620     2620
  Misses        938      938
  Partials      188      188

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e614a9...a865255. Read the comment docs.

Coverage increased (+0.06%) to 73.347% when pulling a86525516ecf59af954d207a7ea727a2e9232265 on little-cui:master into 8e614a9f11c98383e44fdd0c72c629b182f50f2f on apache:master.


Color contrast test not working?

Sample of my test:
import React from 'react';
import { render, cleanup } from '@testing-library/react';
import { axe, toHaveNoViolations } from 'jest-axe';

expect.extend(toHaveNoViolations);
afterEach(cleanup);

test('button(button) should pass accessiblity test', async () => {
    const { container } = render(
<button style={{backgroundColor: '#fff', color: '#fff'}}>test</button>
);
    expect(await axe(container)).toHaveNoViolations();
});

I get a pass with above code and am not getting violation for color contrast. Does jest-axe not have color contrast test?

Axe does not support colour contrast tests in. Node.js environment (jsdom)


Install Not Workign

https://i.gyazo.com/fe9848ef361db1d173d8486cdba4b620.png
On the latest version of flarum. This happens with many extensions and I have to put flarum into debug mode to find out it has to do with this..

Hehe that worked. Good ol' purge and Ctrl+F5


Disable CSRF policy

Hi.
I need to disable CSRF policy in /alfresco/tomcat/shared/classes/alfresco/web-extension/share-config-custom.xml file.
It is not possible to do that with your current container.
If you don't mind, I plane to fork your project, make some change and perform a nice pull request...
(https://github.com/ATIH/docker-alfresco)
Regards.

Merged.  Thanks for the changes.

After merging, I realized that my SHARE_PORT and ALFRESCO_PORT were being set to null, so I had to revert this portion of the merge.  Perhaps this worked for you if you had these values set with an environment variable, but were not working if these values were not set.

Sorry for this mistake. I thought I checked that.
I'll correct this ASAP.


[speexdsp] Improve SIMD extension support

Sadly, vcpkg's use of CMAKE_SYSTEM_PROCESSOR doesn't look like it is correct, as ARM builds somehow enable SSE.
This moves target arch detection to vcpkg part.

Thanks!


Provide utilities to auto implement opEquals, opCmp and toHash

This still needs a changelog entry and ddoc'ed style unittests.

Out of curiosity, what is the vision for how this will relate to DMD clone.d's buildXopEquals/buildXopCmp/buildXtoHash?

Out of curiosity, what is the vision for how this will relate to DMD clone.d's buildXopEquals/buildXopCmp/buildXtoHash?

I might be wrong, but this will not cause trouble for buildXopEquals/buildXopCmp/buildXtoHash.
The mixins in this PR provide the user with greater flexibility, so he can pick and choose what are his significant (to be taken into account) member fields.
The user can even provide the name of a method/property to be used inside the operators. The reason for this is: the user used to have a field X that he now changed to a @property -> his code will continue to work.
Another benefit, imho, is that the implementation is in the library and it's easier for a contributor to understand.
What do you think?

What do you think?

I think it could be convenient. Syntax-wise it might be worth considering an approach based around annotating specific fields (either whitelist or blacklist) like in Java's Project Lombok:
import lombok.EqualsAndHashCode;

@EqualsAndHashCode
public class EqualsAndHashCodeExample {
  private transient int transientVar = 10;
  private String name;
  private double score;
  @EqualsAndHashCode.Exclude private Shape shape = new Square(5, 10);
  private String[] tags;
  @EqualsAndHashCode.Exclude private int id;

  public String getName() {
    return this.name;
  }

  @EqualsAndHashCode(callSuper=true)
  public static class Square extends Shape {
    private final int width, height;

    public Square(int width, int height) {
      this.width = width;
      this.height = height;
    }
  }
}

What do you think?

I think it could be convenient. Syntax-wise it might be worth considering an approach based around annotating specific fields (either whitelist or blacklist) like in Java's Project Lombok:
import lombok.EqualsAndHashCode;

@EqualsAndHashCode
public class EqualsAndHashCodeExample {
  private transient int transientVar = 10;
  private String name;
  private double score;
  @EqualsAndHashCode.Exclude private Shape shape = new Square(5, 10);
  private String[] tags;
  @EqualsAndHashCode.Exclude private int id;

  public String getName() {
    return this.name;
  }

  @EqualsAndHashCode(callSuper=true)
  public static class Square extends Shape {
    private final int width, height;

    public Square(int width, int height) {
      this.width = width;
      this.height = height;
    }
  }
}

At DConf, @atilaneves also asked me if I have thought about using UDAs to exclude fields.
At the time, I had not. I've given it some thought since and I think we could have UDAs as an enhancement to the current implementation. I'm afraid we could "clash" with some existing UDAs that users have in their codebases.
The reason I'm saying we can have it as an enhancement is because I think we could see how the users use the current implementation and if they feel that UDAs would increase their productivity / make the code nicer.
As a final note, I'm not opposing to using UDAs those are just my thoughts.

@edi33416:

I'm afraid we could "clash" with some existing UDAs that users have in their codebases.

This is easily disambiguated by using the fully qualified name when/if necessary.

@atilaneves is UDAs support required as part of this PR or can it come as a future PR?

@edi33416 I wouldn't say UDA support is required, no.

@edi33416 What are your plans with this PR?

@edi33416 Is there anything blocking this PR?

@RazvanN7 I don't think there are any blockers for this PR. I've just rebased with master and pushed the updated branch.
Let's see if the checks pass

Since this PR is adding so many public symbols, it requires a changelog entry.

This assert seems to be tripping:
core.exception.AssertError@std/typecons.d(5802): unittest failure

@edi33416 please address @atilaneves 's comments. Also, can you split this up into 3 PRs?

PR closed as stalled. If you wish to resurrect it you are welcome to do so, however it is recommend to split this up in to multiple PR's.


Cannot allocate memory after a few tests are successful

Hi,
after a few tests in sirix-core are successful without any failures any subsequent test fails, because it can't allocate enough memory somehow.
failed to allocate memory for io_uring ring; Cannot allocate memory
java.lang.RuntimeException: failed to allocate memory for io_uring ring; Cannot allocate memory
	at one.jasyncfio.Native.setupIoUring0(Native Method)
	at one.jasyncfio.Native.setupIoUring(Native.java:32)
	at one.jasyncfio.Ring.<init>(Ring.java:43)
	at one.jasyncfio.PollRing.<init>(PollRing.java:23)
	at one.jasyncfio.EventExecutorImpl.<init>(EventExecutorImpl.java:125)
	at one.jasyncfio.EventExecutor$Builder.build(EventExecutor.java:183)
	at one.jasyncfio.EventExecutor.initDefault(EventExecutor.java:205)
	at org.sirix.io.iouring.IOUringStorage.<init>(IOUringStorage.java:62)
	at org.sirix.io.StorageType$5.getInstance(StorageType.java:87)
	at org.sirix.io.StorageType.getStorage(StorageType.java:112)

However, via debugger I can see that the storage.close() method is executed:
  @Override
  public void close() {
    try {
      if (revisionsOffsetFile != null) {
        revisionsOffsetFile.close().join();
        revisionsOffsetFileEventExecutor.close();
      }
      dataFile.close().join();
      dataFileEventExecutor.close();
    } catch (Exception e) {
      throw new RuntimeException(e);
    }
  }

The executors are initialized with the default factory method.

Hi!
I think I've encountered a similar problem too, but it seems to have been resolved when I made sure I called the close method for the EventExecutor everywhere.
The thing is that the queue allocation for io_uring happens under the rlimit memlocked parameter, which
can be quite low on some setups (64K). So I recommend increasing its value.
Also, I looked at your implementation of io_uring based storage. There is definitely no point in creating two EventExecutor, I recommend keeping one.
And to reduce memory consumption, I recommend creating EventExecutor not with default parameters, but with parameter, entries equal to 1024, if not enough and strange errors or hangs appear, then up to 2048, which I think should be enough (default 4096).
And most importantly, make sure the close method of EventExecutor is invoked everywhere when SirixDB stops.
If the problem won't go away, please let me know.

Hmm, it should definitely be closed, but maybe keeping it alive for the whole session is too long (sharing for a couple of transactions for instance). Maybe it should be created per Reader/Writer And already closed once they are closed instead of once the session and the underlying storage is closed?

I'll make the changes based on your suggestions, too :)

So, I'm not getting the error anymore. However I've "fixed" a few issues, such that reading and writing are always done in a virtual thread:
  @NotNull
  private IOUringWriter writePageReference(final PageReadOnlyTrx pageReadOnlyTrx, final PageReference pageReference,
      Bytes<ByteBuffer> bufferedBytes, long offset) {
    try {
      POOL.submit(() -> writePage(pageReadOnlyTrx, pageReference, bufferedBytes, offset)).get();
      return this;
    } catch (InterruptedException | ExecutionException e) {
      throw new SirixIOException(e);
    }
  }

and ExecutorService POOL = Executors.newVirtualThreadPerTaskExecutor();
however, performance is somewhat worse, and CPUs are now at 100%:

Maybe it should be created per Reader/Writer And already closed once they are closed instead of once the session and the underlying storage is closed?

No, the EventExecutor must be created once and live for the entire lifetime of the DB instance.

however, performance is considerably worse, and CPUs are now at 100%

I've run unit tests using io_uring, there is indeed a significant drop in performance.
This may be because when using io_uring there is an overhead to create the io_uring queue, which becomes significant due to constant re-creation of the context in the unit tests, but I'm not sure.
If you could provide an example of using SirixDB that does a significant amount of I/O work, I'd be happy to try and work out what's wrong. I've seen in benchmarks that a 10 mb file is used, it would be nice to have a similar example that is easy to run with a several gigabyte file.

I know. There's also the revisions cache which should be a cache per resource and initialized statically once for the lifetime of the JVM instance (should hopefully be relatively easy to change -- maybe a concurrent map, which maps the resource path to the caffeine caches).
I'm unsure where to put the EventExecutor as it should be closed at some point.
Also, look at my current configuration of the EventExecutor in the IOUringStorage class.
I'll try to upload the 3,8 Gb cityofchicago.json file somewhere. Then you can enable the Test in JsonShredderTest::testChicago. You should probably also use the Shenandoah GC (but one param I mentioned in the comment is not working anymore in Java 19).
I guess the virtual thread stuff is not working correctly with the io_uring library. If you, for instance, comment the lines with POOL::submit in both the reader and writer implementation, it might be much faster (but still, I think slightly worse than the FileChannel or memory-mapped I/O layers).
https://www.file-upload.net/download-15038251/cityofchicago.zip.html
Thanks a lot for all your effort. I appreciate your knowledge and help :+1:

Let me know if you can download the file. It seems to be a bit weird... Maybe I have to find another file upload service. Also, I wonder how we can automatically run these tests in another test-project. I think even Git LFS doesn't support these very large files or you have to pay a lot.

I've made the EventExecutor static... one problem might be that it's now never closed, however. Despite the 100% CPU usage being gone, I think latency is still a bit worse than the other backends.

It seems to help a bit to dramatically reduce the time to sleep interval for the event loop. The read-write trx in the test during an import commits itself periodically, that is it flushes the in-memory trx intent log to disk everytime during a commit in a postorder traversal of the changed page fragments. I'll have to check the performance of the read-only trx again. Nontheless, I'll have to read the Systems Performance book by Brandon Gregg, to figure out what really goes on in such situations.
Apparently the event loop occupies too much CPU time, but the only thing which is done in parallel is reading page fragments if a page has been changed in more than one revision (for instance due to hash updates for the ancestors of inserted nodes) and serialization of the UnorderedKeyValuePage and one of 8 cores doesn't sound that much.
Maybe it would be great to have an initial time to sleep value which is very low for the rrvent loop, but during a commit/sync to disk set a much higher value?
But even after setting the time to sleep to a very low value (1-10ms) it's about 25sec slower than the file channel based implementation (around 3:50m vs 4:15m).
So maybe that's only part of the story. In general I also want to switch to an off-heap map as Chronicle Map for the trx intent log, which should have an impact of several seconds in this test, hopefully (due to much lower garbage).

Also, I wanted to add that during the test I observed that the write speed to the disk was around 10-12MB/sec. This is quite a small value for an average SSD disk. Therefore, as a benchmark for further optimizations of the I/O layer, I suggest to use and increase this characteristic.

Disk I/O usage indeed is terrible:
Device             tps    kB_read/s    kB_wrtn/s    kB_dscd/s    kB_read    kB_wrtn    kB_dscd
nvme0n1         309,50         0,00     10452,00         0,00          0      20904          0
nvme0n1p1         0,00         0,00         0,00         0,00          0          0          0
nvme0n1p2         0,00         0,00         0,00         0,00          0          0          0
nvme0n1p3       309,50         0,00     10452,00         0,00          0      20904          0

It's, on average, maybe about  1.75 x better if you disable all options (storing no hashes, no path summary...), but it's still way too low, I guess.
(but this is not about your io_uring lib -- though I couldn't measure the 20sec faster than the other backends, too, that you mentioned somehow; in my test when switching from a file channel based backend to the io_uring based approach, it's 20sec slower on my machine (constantly)). That said, the main issue and insight for me currently is the horrible disk I/O usage :-/

output from vmstat -1
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
 2  0  14592 7167968 1042708 10715320    0    0     0     0 12989 59878 53  4 43  0  0
 1  0  14592 6860564 1042728 10717444    0    0     8 33008 2955 7607 20  3 77  1  0
 1  0  14592 6656196 1042736 10717436    0    0     0    52 1951 2653 14  2 84  0  0
 2  0  14592 6608824 1042736 10737152    0    0     0     0 11316 45129 49  3 48  0  0
 1  0  14592 6624540 1042752 10750372    0    0     0 33456 3326 19335 21  2 76  1  0
 1  0  14592 6650496 1042752 10750308    0    0     0    80 2329 4072 24  1 76  0  0
 4  0  14592 6613548 1042752 10761696    0    0     0   196 9845 32601 62  2 36  0  0
 1  0  14592 6669560 1042768 10783128    0    0     0 33044 4930 29539 38  3 58  0  0
 1  0  14592 6675864 1042768 10783128    0    0     0     0 3311 6018 29  1 70  0  0
 9  0  14592 6215208 1042768 10783128    0    0     0    12 4164 6709 19  2 79  0  0
 2  0  14592 6142636 1042788 10816328    0    0     0 33072 11459 60453 36  3 60  1  0
 1  0  14592 6185552 1042788 10816328    0    0     0    12 2854 4942 18  1 80  0  0
11  0  14592 6183788 1042796 10816328    0    0     0   220 4007 6843 33  1 66  0  0
 2  0  14592 6092816 1042812 10849172    0    0     0 32968 11970 60387 40  3 56  1  0

And a flame graph will wall clock time

I close this task as the discussion is no longer relevant to jasyncfio. I suggest creating a similar task to investigate in the SirixDB repository. Once created, please add me as a participant, in case I can help in any way, I will write :)


Migrating to sdk .net core 2.0 + VisualStudio 2017

Seems like build script is failed due to lack of project.json in VS2017 project structure

Can you check the travis config? This seems fishy to me as you probably want to use dotnetcore 2.0 here?
https://github.com/vladimir-kucher/AspNetCore.Identity.MongoDB/blob/Core2Migration/.travis.yml#L21

This is amazing @vladimir-kucher and @Razzeee! Thanks for doing this, will have a look now and try to get the build passing!

This is mostly positive and lots of good things under this! A few things that worth noting:

Do you know whether ASP.NET Identity 1.1.2 store interface is compatible with 2.0.0? If that's the case, targeting that would be more beneficial. In any case, let's keep this PR focused to SDK move which is an amazing step on its own.

I assume that targeting Identity 2.0.0 package was not your main intention with this PR. Am I correct to assume that?

Build script needed a change the way it builds and created packages. I created https://github.com/tugberkugurlu/AspNetCore.Identity.MongoDB/tree/dotnetcore2-sdk branch on top of this. Let's observe the build of that and if it passed, I pushed my changes to your branch and merge that in! Keep in mind that this will not erase your commits and you will be seen as a contributor 🎉

There are a few other things I have change under dotnetcore2-sdk branch. I will point some of the important ones out as code comments.

Had a few issues with running the tests under Travis CI but it all seems to be working now 🎉 once this is green, we can get this in!

It turned out that you cannot target 1.1.2 and work for 2.0.0 of identity. I made the move on https://github.com/tugberkugurlu/AspNetCore.Identity.MongoDB/pull/50


Strip out commas in distribution limit to avoid crashing big number up stack

What does this PR do and why?
Strip out commas in distribu tion limit to avoid crashing big number up stack.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #1804   👈

This comment was auto-generated by Graphite.


Update gradle to 8.10.2 and specify hash

Ran ./gradlew wrapper --gradle-version=8.10.2 and specified hash from https://gradle.org/release-checksums/

This would require us to manually update the hash every time gradle is updated right? In that case I am inclined not to include this just to not add additional unneeded complexity to managing the app.

This is necessary for F-Droid inclusion. Gradle doesn't have to be updated often (just for new AS/AGP versions). As it's just changing a version number & copy pasting the checksum, imo this should be integrated.
Gradle checksum page: https://gradle.org/release-checksums/
Gradle issue for automatic inclusion of the hash: https://github.com/gradle/gradle/issues/12412


Update periodic jobs to point to release-0.20

Description of changes:
Update periodic jobs to point to release-0.20
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


Default subscription not being saved / respected

This is autogenerated. Please review and update as needed.
Describe the bug
When I log in to my tenant using az cli, the default subscription is always the "wrong" subscription (not the one that I want).  I will change the subsciption, but that will not be respected when I log out and log in again.
Command Name
az account set --subscription

Errors:
It is not an error, just that the subscription is not remembered.  See below.
To Reproduce:
❯ az logout
~
❯ az login --tenant <removed for privacy> -o table
The default web browser has been opened at https://login.microsoftonline.com/<removed for privacy>/oauth2/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.
You have logged in. Now let us find all the subscriptions to which you have access...
CloudName    HomeTenantId                          IsDefault    Name                     State    TenantId
-----------  ------------------------------------  -----------  -----------------------  -------  ------------------------------------
AzureCloud   <removed for privacy>                 True         SubscriptionA            Enabled  <removed for privacy>
AzureCloud   <removed for privacy>                 False        SubscriptionB            Enabled  <removed for privacy>
AzureCloud   <removed for privacy>                 False        SubscriptionC            Enabled  <removed for privacy>
~
❯ az account set --subscription "SubscriptionB"
~
❯ az account show -o table
EnvironmentName    HomeTenantId                          IsDefault    Name                     State    TenantId
-----------------  ------------------------------------  -----------  -----------------------  -------  ------------------------------------
AzureCloud         <removed for privacy>                 True         SubscriptionB            Enabled  <removed for privacy>
~
❯ az logout
~
❯ az login --tenant <removed for privacy> -o table
The default web browser has been opened at https://login.microsoftonline.com/<removed for privacy>/oauth2/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.
You have logged in. Now let us find all the subscriptions to which you have access...
CloudName    HomeTenantId                          IsDefault    Name                     State    TenantId
-----------  ------------------------------------  -----------  -----------------------  -------  ------------------------------------
AzureCloud   <removed for privacy>                 True         SubscriptionA            Enabled  <removed for privacy>
AzureCloud   <removed for privacy>                 False        SubscriptionB            Enabled  <removed for privacy>
AzureCloud   <removed for privacy>                 False        SubscriptionC            Enabled  <removed for privacy>
~

Expected Behavior
az account set --subscription is supposed to change my default subscription.  In the case above, once I set it to "SubscriptionB", it should stay at that subscription even when I log out and log in again.
Environment Summary
macOS-11.3.1-x86_64-i386-64bit
Python 3.8.10
Installer: HOMEBREW

azure-cli 2.23.0

Extensions:
azure-devops 0.16.0
storage-preview 0.2.12
account 0.2.1

Additional Context

This is the designed behavior because az logout removes both

token cache file ~/.azure/accessTokens.json
profile file ~/.azure/azureProfile.json

az login simply selects the first enabled subscription returned by Subscriptions - List REST API.
Also, there is no Azure REST API to save and retrieve the selected subscription for a user.
Let me mark this issue as a feature request and see if other people want this behavior too.

So, @jiasli , are you saying that the following are true:

There is no way to specify a default subscription that persists as I would wish (beyond az logout).
There is no interest or effort within the MS / Azure team to address this so that the default subscription can persist.

It is not the biggest issue I have, needing to set this every time I work with az, but I would say that defaulting just to "the first subscription found" is not very user-friendly.
Could a config file be made that lives in ~/.azure?  Maybe something like userConfig.json where a user can set all these things on a more permanent basis?
Also, as an aside, I therefore do not understand exactly what az account set --subscription is doing or what its purpose is.  Is it merely so that I do not have to pass --subscription with every az command I use?  I guess that is helpful, but then the command name is confusing.

There is no way to specify a default subscription that persists as I would wish (beyond az logout).

I therefore do not understand exactly what az account set --subscription is doing or what its purpose is.  Is it merely so that I do not have to pass --subscription with every az command I use?

Exactly, az account set --subscription persists the subscription in ~/.azure/azureProfile.json by setting "isDefault": true so that you don't need to specify --subscription for every az command. The default subscription is also persisted when you close and reopen the terminal.

There is no interest or effort within the MS / Azure team to address this so that the default subscription can persist.

If I understand correct, what you want is to persist the subscription even after az logout and az login. This is not the designed behavior, as az logout is designed to be "forget everything about me". If we still persist the subscription after az logout, we will definitely need another file to save this info and another command or parameter to clear that info. This makes az overly complex (2 levels of subscription persistence) and more difficult to understand.
The same behavior also applies to Azure PowerShell Connect-AzAccount and Disconnect-AzAccount.

Hi @jiasli , yes, you understood me correctly:  I would like for metadata to persist - at least locally on my machine - beyond az logout.  Current behavior is in fact persisting information right now:  it persists the "decision" to choose the first subscription listed in my account alphabetically.
Regardless, I understand your point that it makes az overly complex; I will create an az alias on my machine to simplify this process.
Thanks for your patience and understanding in working with me!  😄

Oops, I forgot to close the issue with my last comment.  😉

I would say that defaulting just to "the first subscription found" is not very user-friendly.

We are considering not to select the default subscription in the future: https://github.com/Azure/azure-cli/issues/27915. Any idea or feedback is welcome!


IOBJ fix - issue 3105

Fix for IOBJ issue #3105

I'm not exactly sure if cx_sy_dyn_call_illegal_func is thrown, but any how 👍


Separate html and script from template

Hi,
It might be useful to have {{ chart.as_html }} and {{ chart.as_script }} or something similar in order to collect all scripts at the end of the page.  The first method would make the divs will be rendered and the second will show the script.
When we load jquery at botton of the page, we got ReferenceError for $ function, because the script function appears before than the chart js library was loaded.
Thanks for consider this option!

This PR is ready, just not merged. I hope someone can merge it because I'm eager to use this feature.

@8ksoft @tkwon The PR for this is merged into master. Can you check if this is what you wanted. Please feel free to reopen this issue if you think it's not fixed.

@8ksoft @tkwon After merging PR for suggested changes, now the following can be done in the template:
<script type="text/javascript" src="https://www.google.com/jsapi"></script>
<script type="text/javascript">
      google.load("visualization", "1", {packages:["corechart"]});
</script>
{{chart.render_js}}
{{chart.render_html}}

This assumes that view has following code:
sd = SimpleDataSource(data)
chart = gchart.LineChart(sd)
context = {'chart': chart}
return render(request, 'some_template.html', context)

Great!


Fixed the createTestStateWithDelegatedPolicies

Fixed the createTestStateWithDelegatedPolicies, so that when it is used in conjunction with createTestRepository, and when the state is commited, it can pass the verification check.
Currently the test will not pass, but when PR 219 is merged, it should work

Note that tests pass because this isn't used for a verification test yet.


chromium: 101.0.4951.54 -> 101.0.4951.64

https://chromereleases.googleblog.com/2022/05/stable-channel-update-for-desktop_10.html
This update includes 13 security fixes.
CVEs:
CVE-2022-1633 CVE-2022-1634 CVE-2022-1635 CVE-2022-1636 CVE-2022-1637
CVE-2022-1638 CVE-2022-1639 CVE-2022-1640 CVE-2022-1641
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Oops, https://github.com/NixOS/nixpkgs/pull/171849 wasn't merged yet...
I just opened https://github.com/NixOS/nixpkgs/pull/172600 for the backport.


-TimeoutSeconds of Test-Connection not work when value gt 4,no err

https://docs.microsoft.com/zh-cn/powershell/module/Microsoft.PowerShell.Management/Test-Connection?view=powershell-6
input 1----4  to TimeoutSeconds Parameter,then  work.
input 5----more  to TimeoutSeconds Parameter,does not work.（use 4，No error）
Steps to reproduce
Test-Connection -TargetName $ip -TCPPort 22 -TimeoutSeconds 20
Expected behavior
Until 20 seconds
Actual behavior
4---5 seconds ,and return false.
Environment data
centos76 + ps v6.1.5 + console #has this bug
centos76 + ps v6.2.2 + console #has this bug
centos76 + ps v7.0 preview2 + console #has this bug
reporter
By the chinese powershell study & research group. QQ group No. is 183173532

I do not understand what the problem is. If the cmdlet sleeps for more than 20 seconds, it will be a problem.

the point is:
input 1----4  to TimeoutSeconds Parameter,then  work.
input 5----more  to TimeoutSeconds Parameter,does not work.
The current practice is very unprofessional
If this is a by design, the parameter values should be limited in a friendly way.
eg：
ValidateRange

@iSazonov  remove Resolution-Answered  label.
put the label,and let bot close this issue is Is not responsible for the practice.

I re-check that the parameter works as expected on Windows and on WSL.
If there is an issue on centos76 it is not PowerShell Core issue, maybe it is .Net Core issue.

1 I re-check that the parameter works as expected on Windows,by version 6.2.2. it can wait Until 20 seconds.
2 I re-check that the parameter works  4 seconds on linux + docker ,by version 6.2.2.it can not wait Until 20 seconds.
docker run -it   mcr.microsoft.com/powershell:6.2.2-alpine-3.8 pwsh -c 'Test-Connection -TargetName <IP_ADDRESS> -TCPPort 22 -TimeoutSeconds 20'

@chuanjiao10 can you do a simple test to see if the issue is with the type that is used in .NET Core?
using namespace System.Net.NetworkInformation

$Destination = 'https://github.com'
[byte[]]$Buffer = 1..32
$Options = [PingOptions]::new()

foreach ($timeout in 1..20) {
    $ping = [Ping]::new()
    $ping.Send($Destination, $timeout, $Buffer, $Options)
}

I'm curious as to what the errors would be... and why it's having this issue. If it is a .NET Core issue, we should be able to get them to check it out before .NET Core 3 GA release. 🙂

@vexx32  Is your discussion related to the topic?
[root@centos76 ~]# pwsh-preview
PowerShell 7.0.0-preview.2
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/powershell
Type 'help' to get help.

PS /root> /powershell/20190725.ps1
Testing ping to 'https://github.com' with timeout value of 1...
Exception calling "Send" with "4" argument(s): "An exception occurred during a Ping request."
At /powershell/20190725.ps1:11 char:2
+     $ping.Send($Destination, $timeout, $Buffer, $Options)
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : PingException

Testing ping to 'https://github.com' with timeout value of 2...
Exception calling "Send" with "4" argument(s): "An exception occurred during a Ping request."
At /powershell/20190725.ps1:11 char:2
+     $ping.Send($Destination, $timeout, $Buffer, $Options)
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : PingException

open this issue @msftbot

There already is a tracking issue https://github.com/dotnet/corefx/issues/28934. Please discuss there.

@iSazonov
1In https://github.com/dotnet/corefx/issues/28934 Below short list:，
Which item is related to    “-TimeoutSeconds gt 4 not work”  ?
2 the “related”， Is this your guess, or has it been investigated?
Anyone willing to help review the Test-Connection code first?
2 If it is related,this issue marked "wait for .net core" as well.
The bug is still, willing to be unidentified, reopen this issue!

@chuanjiao10 Underlying .Net  Core code is broken for Unix-s. We can not fix this in PowerShell Core repo. Please report such bugs to CoreClr/CoreFX repos and ask them to fix.

This is a deliberate ignorance and closure of the problem.

The issue is not in the scope of our code. We can only do so much with hiding problems exposed by .net Core. In this case, the only way we could bypass the problem would be to implement our own version of the Ping APIs from the native P/invoke calls.
The PowerShell team likely do not have the manpower to build nor maintain such a complex solution, when the bug is being tracked in the provider's repo and will be fixed eventually.

This is a deliberate ignorance,The problem is still, Although the problem is relatively small.
Suggested "wait for .net core" lable.


It works with Docker swarm ?

Do this works with docker swarm ?
I have a
level=WARN msg="blocked request" reason="forbidden IP" method=GET URL=/v1.24/version client=<IP_ADDRESS>:60802 response=403

When I try to use it with Traefik v3. I guess this is supposed to be allowed with the option -allowfrom=reverse-proxy in the command but with swarm is that works ?
(reverse-proxy in the name of my traefik service in the stack)
Thanks

It works if I set ip (but I would like it dynamic) and if I allow all GET
services:
  dockerproxy:
    image: wollomatic/socket-proxy:1 # see https://github.com/wollomatic/socket-proxy for reference
    command:
      - '-loglevel=info' # set to debug for far more logging
      - '-allowfrom=<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>'
      - '-listenip=<IP_ADDRESS>'
      - '-allowGET=.*' # this regexp allows readonly access only for requests that traefik needs
      - '-shutdowngracetime=5'
      - '-watchdoginterval=600'
      - '-stoponwatchdog'

The above error message is caused by the -allowfrom configuration.
If the hostnames in Swarm are dynamically generated, it is difficult to set an allowlist for them. A possibility would be to allow a local network range, e.g., -allowfrom=<IP_ADDRESS>/24. Please keep in mind that this can easily result in insecure configurations (on the other hand, most of the other Socket-Proxy-Software allows access from any IP).

The -allowGET option depends on how you use Traefik:
If you use the docker provider (https://doc.traefik.io/traefik/providers/docker/), the '-allowGET=/v1\..{1,2}/(version|containers/.*|events.*)' is fine for socket-proxy.
You probably need another configuration for the allowlist if you use the swarm provider (https://doc.traefik.io/traefik/providers/swarm/): Maybe -allowGET=.* is fine in that case. You can enable the debug logging and see how the requests look. After that, you can create a more specific working regexp.
Also, see https://github.com/wollomatic/socket-proxy/discussions/30
(I'll convert this issue to a discussion)


Disable incorrect pushdown in Mongo connector

Fixes #1781

Could you confirm the following CI failure?
[ERROR] Failures:
[ERROR]   TestMongoSession.testBuildQuery:52 Maps do not have the same size:1 != 2
[ERROR]   TestMongoSession.testBuildQueryNull:103 Maps do not have the same size:0 != 1
[ERROR]   TestMongoSession.testBuildQueryOr:90 Maps do not have the same size:0 != 1
[ERROR]   TestMongoSession.testBuildQueryStringType:66 Maps do not have the same size:1 != 2

@ebyhr thanks, updated

CI failed -- https://github.com/prestosql/presto/issues/3049

CI failed -- checkout failed. This PR is cursed.

Finally green. Please review.

improve commit message to mention that pushdown is disabled only for not supported types

it says "disable incorrect pushdown", not "disable pushdown"

added test

AC

@kokosing  ready for re-review


Display image dimensions and size for RG cover art

https://community.metabrainz.org/t/ropdebees-userscripts-support-thread/551947/57

I don’t remember if it ever worked in either case but on “set cover art” pages neither dimension nor size are displayed and on release group pages size is always “??? KB”:

https://musicbrainz.org/release-group/e722cfc7-0975-4a33-82dd-bf37cc714321
https://musicbrainz.org/release-group/ab26a2e1-76bf-4007-ac86-8f064d456a8a/set-cover-art

The RG size issue has been around forever, it's because the size is loaded from the IA metadata, which is release-specific. To fix it, we'd need to extract which release the RG image belongs to (which is probably possible somehow). Not sure about the "set cover art" page issue.
Probably needs a TS rewrite first though 🙂


menu not showing on persian local on shop front

i am making categories but the name of categories are not showing up in category menu and when i want to make the product , my guess is that its because of adding locals ,  see the image below :

so now even when i chose the option to show this category on shop front nothing shows up there . thanks

i figured that the problem was saving the categories on default and you have to change it manually so please review this if possible


[language] migrate IR test suite

This PR migrates our old functional-test-based IR testsuite to the new transactional tests. More specifically, it contains 3 stacked commits:

A small but representative sample of the tests being migrated. Hope this makes the PR easier to review.
Bulk migration of tests.
Deletion of the ir-testuite crate.

Note: this also deletes a few tests that are redundant or no longer make sense.

 I feel pretty aggressive about removing them and I didn't see anything I would miss being removed, but I think he might have a different temperature reading.

Yeah, didn't realize you were also planning to do this until Todd mentioned it to me yesterday. ;) Anyway, thank you for reviewing!

and in my head I thought it would be best to implement script disassembling #9941 before migrating.
And anyway, I still have the move-ir-compiler unit_tests to migrate, so, I guess I still have plenty of my own work to do
Sounds like a great plan to me. I guess you can get some coverage for the script disassembler by using on some the unit_tests you'll migrate.

@tnowacki Looks like I went through the tests a bit too fast and misclassified a few of them. Some of them probably got broken long time ago, with the functional test directives checking for syntax errors instead of what they really intend to test. Will get them restored/rewritten. Thank you so much for catching this!!!

transactions/tx_assoc.mvir
mutation/mint_money.mvir
modules/publish_resource_internal.mvir, modules/has_resource_internal.mvir, modules/get_resource_internal_bypass.mvir
cant_borrow_field_of_resource.mvir

I still think these should be deleted:

publish/publish_two_modules.mvir,

Already ported to move-vm/transactional-tests/tests/module_publishing/publish_two_modules.mvir

publish_module_and_use.mvir

Already ported to move-vm/transactional-tests/tests/module_publishing/publish_module_and_use.mvir

natives/vector/vector_module.mvir

Already ported to move-vm/transactional-tests/tests/native_functions/vector_module.mvir

@tnowacki I've changed the address from 0x0 to 0x1, so to be consistent with other tests, and reimplemented the missing tests. (See the two new commits for details.)

/land


Fix leaking file descriptors

@marpaia would be great if we can get this in, as this caused us quite some grief... Thx!

Thanks @svanharmelen! Use this library at your own risk, as I don't actively maintain it anymore :)

@marpaia I know, no problem :wink:


app is STARTING on device, but not in cloud

Cloud

Agent

I am restarting the agent to try to fix this. Then I got

Another thing here:
After clicking update. The update FAILED. Then I tried to remove the app and get:

The reason for this seems to be that the image name lacks the container suffix number.
I changed from a former dockerfile to a docker-compose setup. The proper image name is probably:
Image is up to date for registry.reswarm.io/apps/prod_arm64_1240_traffic_2:2.0.1

Also A_Park1 device, but this time in dev environment. Few days ago I did docker system prune-a on the device.


add google analytics

What kind of change does this PR introduce?
Add google analytics through Gatsby official plugin

Does this PR introduce a breaking change?
Nope

What needs to be documented once your changes are merged?
Nope

Thanks @wenqili! @joeyklee let me know when this is deployed and I'll check and make sure the data is coming in?


P2SH address support

def SegWitP2SHAddress(self):
    addressversion = b'\x05' if not self.testnet else b'\xc4'
    scripthash = hashlib.new('ripemd160', hashlib.sha256(b'\x00\x14' + self.Identifier()).digest()).digest()
    return Base58.check_encode(addressversion + scripthash)

Taken from Reddit
I guess Bech32 support should also be added eventually.

Please send a pull request and close this issue. Thanks!