🐛 Bug Report: npm dependencies resolution issue

📜 Description
I don't know much about publishing package to npm, but yarn can't link correct version of the plugin.
Our Renovate bot that updates our dependencies tried to upgrade @procore-oss/backstage-plugin-... but cannot link dependency with the correct latest version but uses @workspace:^ local version.
👍 Expected behavior
For example, yarn add --cwd packages/backend @procore-oss/backstage-plugin-search-backend-module-announcements should automatically resolve current version  0.1.1
👎 Actual Behavior with Screenshots
It actually lead to this error and can found local workspace plugin:
YN0001: │ Error: @procore-oss/backstage-plugin-announcements-common@workspace:^: Workspace not found (@procore-oss/backstage-plugin-announcements-common@workspace:^)

It should npm version:
"@procore-oss/backstage-plugin-announcements-common": "npm:^0.1.4"

👟 Reproduction steps

I did a fresh install of Backstage:  npx @backstage/create-app@latest
Then install backend plugin:

$ yarn add --cwd packages/backend @procore-oss/backstage-plugin-announcements-backend
yarn add v1.22.19
[1/4] Resolving packages...
warning Lockfile has incorrect entry for "<EMAIL_ADDRESS>|| ^17.0.0". Ignoring it.
Couldn't find any versions for "@procore-oss/backstage-plugin-announcements-common" that matches "workspace:^"
? Please choose a version of "@procore-oss/backstage-plugin-announcements-common" from this list: (Use arrow keys)
❯ 0.1.4
  0.1.3
  0.1.2
  0.1.1
Couldn't find any versions for "@procore-oss/backstage-plugin-search-backend-module-announcements" that matches "workspace:^"
? Please choose a version of "@procore-oss/backstage-plugin-search-backend-module-announcements" from this list: (Use ar
row keys)
❯ 0.1.1
  0.1.0

Then yarn prompts that it can't find "workspace:^" version.

📃 Provide the context for the Bug.
Our main instance use yarn v4 and I reproduced it with yarn v1.22, got similar results on both version
🖥 Your Environment
yarn run v1.22.19
$ /home/ggt/gaelgoth-github/tests/debug-package-resolution/node_modules/.bin/backstage-cli info
OS:   Linux <IP_ADDRESS>-microsoft-standard-WSL2 - linux/x64
node: v18.16.0
yarn: 1.22.19
cli:  0.25.1 (installed)
backstage:  1.22.1

Dependencies:
  @backstage/app-defaults                                          1.4.7
  @backstage/backend-app-api                                       0.5.10
  @backstage/backend-common                                        0.20.1
  @backstage/backend-dev-utils                                     0.1.3
  @backstage/backend-openapi-utils                                 0.1.2
  @backstage/backend-plugin-api                                    0.6.9
  @backstage/backend-tasks                                         0.5.14
  @backstage/catalog-client                                        1.5.2
  @backstage/catalog-model                                         1.4.3
  @backstage/cli-common                                            0.1.13
  @backstage/cli-node                                              0.2.2
  @backstage/cli                                                   0.25.1
  @backstage/config-loader                                         1.6.1
  @backstage/config                                                1.1.1
  @backstage/core-app-api                                          1.11.3
  @backstage/core-compat-api                                       0.1.1
  @backstage/core-components                                       0.13.10
  @backstage/core-plugin-api                                       1.8.2
  @backstage/e2e-test-utils                                        0.1.0
  @backstage/errors                                                1.2.3
  @backstage/eslint-plugin                                         0.1.4
  @backstage/frontend-plugin-api                                   0.5.0
  @backstage/integration-aws-node                                  0.1.8
  @backstage/integration-react                                     1.1.23
  @backstage/integration                                           1.8.0
  @backstage/plugin-api-docs                                       0.10.3
  @backstage/plugin-app-backend                                    0.3.57
  @backstage/plugin-app-node                                       0.1.9
  @backstage/plugin-auth-backend-module-atlassian-provider         0.1.1
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.3
  @backstage/plugin-auth-backend-module-github-provider            0.1.6
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.6
  @backstage/plugin-auth-backend-module-google-provider            0.1.6
  @backstage/plugin-auth-backend-module-oauth2-provider            0.1.6
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.1
  @backstage/plugin-auth-backend-module-okta-provider              0.0.2
  @backstage/plugin-auth-backend                                   0.20.3
  @backstage/plugin-auth-node                                      0.4.3
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.6
  @backstage/plugin-catalog-backend                                1.16.2
  @backstage/plugin-catalog-common                                 1.0.20
  @backstage/plugin-catalog-graph                                  0.3.3
  @backstage/plugin-catalog-import                                 0.10.5
  @backstage/plugin-catalog-node                                   1.6.1
  @backstage/plugin-catalog-react                                  1.9.3
  @backstage/plugin-catalog                                        1.16.1
  @backstage/plugin-events-node                                    0.2.18
  @backstage/plugin-github-actions                                 0.6.10
  @backstage/plugin-org                                            0.6.19
  @backstage/plugin-permission-common                              0.7.12
  @backstage/plugin-permission-node                                0.7.20
  @backstage/plugin-permission-react                               0.4.19
  @backstage/plugin-proxy-backend                                  0.4.7
  @backstage/plugin-scaffolder-backend-module-azure                0.1.1
  @backstage/plugin-scaffolder-backend-module-bitbucket            0.1.1
  @backstage/plugin-scaffolder-backend-module-gerrit               0.1.1
  @backstage/plugin-scaffolder-backend-module-github               0.1.1
  @backstage/plugin-scaffolder-backend-module-gitlab               0.2.12
  @backstage/plugin-scaffolder-backend                             1.20.0
  @backstage/plugin-scaffolder-common                              1.4.5
  @backstage/plugin-scaffolder-node                                0.2.10
  @backstage/plugin-scaffolder-react                               1.7.1
  @backstage/plugin-scaffolder                                     1.17.1
  @backstage/plugin-search-backend-module-catalog                  0.1.13
  @backstage/plugin-search-backend-module-pg                       0.5.18
  @backstage/plugin-search-backend-module-techdocs                 0.1.13
  @backstage/plugin-search-backend-node                            1.2.13
  @backstage/plugin-search-backend                                 1.4.9
  @backstage/plugin-search-common                                  1.2.10
  @backstage/plugin-search-react                                   1.7.5
  @backstage/plugin-search                                         1.4.5
  @backstage/plugin-tech-radar                                     0.6.12
  @backstage/plugin-techdocs-backend                               1.9.2
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.4
  @backstage/plugin-techdocs-node                                  1.11.1
  @backstage/plugin-techdocs-react                                 1.1.15
  @backstage/plugin-techdocs                                       1.9.3
  @backstage/plugin-user-settings                                  0.8.0
  @backstage/release-manifests                                     0.0.11
  @backstage/test-utils                                            1.4.7
  @backstage/theme                                                 0.5.0
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.7

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

Try these steps:

yarn cache clean
rm yarn.lock
yarn install - you may be asked to choose a version on several packages, just pick latest.

This resolved the issue for me and now I'm able to update to latest.

@gaelgoth, let me know if @wss-alubic instructions work, and we will go from there.

@kurtaking I'm running into this same issue. I tried the above steps and that didn't work. I'm running node version v20.22.0 and yarn version 4.0.2.

@codingdiaz thanks for sharing. Tuesdays are my busiest nights of the week.
I won't have time to look at this until tomorrow.

I confirm that running yarn add<EMAIL_ADDRESS>works as expected. But it doesn't work with latest version (0.5.4):
➤ YN0001: │ Error: @procore-oss/backstage-plugin-announcements-common@workspace:^: Workspace not found (@procore-oss/backstage-plugin-announcements-common@workspace:^)
    at Pt.getWorkspaceByDescriptor (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:210:3520)
    at l1.getCandidates (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:140:115276)
    at Dd.getCandidates (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:141:1311)
    at Dd.getCandidates (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:141:1311)
    at /home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:210:8409
    at Ky (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:140:53916)
    at Fe (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:210:8389)
    at async Promise.allSettled (index 10)
    at async Uc (/home/user/workspace/backstage/.yarn/releases/yarn-4.1.0.cjs:140:53244)
➤ YN0000: └ Completed in 0s 812ms
➤ YN0000: · Failed with errors in 0s 821ms

I think it is related on these changes on package. Maybe some adaptations need to be done to tell changeset to set version for published release ?:
https://github.com/procore-oss/backstage-plugin-announcements/commit/f7b3b0b92bc3b5356f50fb0111f482526c716ce7#diff-12939dbee1121abad884fb2d88194561bda99b5d2ad39b5756d2fb7379bfdee5

Hmm, yeah, I don't understand things well enough. I plan to look at how backstage is doing this later today.

Still here, still stumped 😞

I think the issue is related to the script you are running for releasing the plugins.
Your release script is changeset publish https://github.com/procore-oss/backstage-plugin-announcements/blob/main/package.json#L23
which under the hood it invokes npm publish (which might have troubles resolving the linked packages) instead of yarn npm publish.

I think the issue is related to the script you are running for releasing the plugins. Your release script is changeset publish https://github.com/procore-oss/backstage-plugin-announcements/blob/main/package.json#L23 which under the hood it invokes npm publish (which might have troubles resolving the linked packages) instead of yarn npm publish.

Hey @vinzscam, thanks for taking a look! This gives me some direction to explore.

I published new patch versions of all packages using different commands based on @vinzscam recommendation and this issue.
@gaelgoth, @codingdiaz - can either of you report back on updating to the latest patch versions?

Well done, I was able to update the plugin to the latest version:
 "@procore-oss/backstage-plugin-announcements-backend": "^0.5.5",
 "@procore-oss/backstage-plugin-announcements-common": "^0.1.5",

Thank your for the fix

@kurtaking, thanks a ton! I'm able to update to the latest versions.


Introduce before_request configuration

Discussed in #137
Add a before_request: -> (env) { ... } configuration option. This option can be useful for users to authenticate their calls, add metrics, etc.

👋
I've been able to test it in my repository, and it worked: passed when authenticated, rejected with expected status when unauthenticated.
I'm not sure whether to add tests to specs_e2e, could you point me to the right direction @grantspeelman  🙏 ?

Thanks @RomainEndelin! Looks solid. Check this out @grantspeelman.


LDAP modifications should be able to adjust string case

Since LDAP strings are, by default, case-insensitive, the current modify operations do not perform a modification if only the case of a string changes. Update the plugin to allow for case-based string modifications.

This was implemented. See commit 36991c13be7ffb8ae98ceee1674aebea059716b6.


{CI} Add auto reply for pull request

Add permission pull-requests: write to avoid error:
Error: Parameter token or opts.auth is required
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

CI


Updated vault info

The doc was not fully uptodate, relative to the last changes.
Amend that, add a command to show the full json for the vault keys
and surround the storing of the unseal keys sentence in a Note.
Also make sure we use the wrapper when invoking make commands in all
examples
Closes #344

This is an automated message:
You can preview this docs PR at http://358.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.


ImportError: lxml not found, please install it

@dennolouis I pushed an updated, follow the update instructions in the readme.  If it doesn't work, re-open this issue.


Editor override: opening same input does not pass options in

Steps to Reproduce:

uncomment https://github.com/microsoft/vscode/blob/be2ddfaad6db9a87de5ddc40f838b3456cf2f267/src/vs/workbench/contrib/search/browser/anythingQuickAccess.ts#L977-L977
run smoke tests
they fail

Another way to reproduce:

open an editor
focus terminal
bring up quick open and select the top editor in the list

=> focus remains in terminal
I think the reason for this is that somewhere in the code when override is defined, we no longer call setOptions on a pane.

Actually it is different, I am not even seeing openEditor being called in that case.

@lramos15 please have a look at the change, it seems to work nicely and does what we had previously: if the editors match, just pass them into the group.

Well now that we use untyped inputs it would create a typed input and pass it in. Although I'm not sure how this flow would work in the untyped case since we wouldn't be passing typed editor inputs forward into the override service.

I am not sure I understand your last comment, is there an issue with that?


fixed some refs and links

This is an automated message:
You can preview this docs PR at http://372.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.


[STARKs] Better code organization

Description
The lib.rs file under proving_system/stark was cleaned up. Tests were moved to their own integration tests directory and a few structs to their own separate modules. The only thing left to move are the functions related to Fiat-Shamir, which have their own issue for it.
This PR branches off of #206, I will update after it's merged.

Codecov Report

Merging #229 (5033711) into main (9a524e5) will increase coverage by 0.48%.
The diff coverage is 95.98%.

@@            Coverage Diff             @@
##             main     #229      +/-   ##
==========================================
+ Coverage   93.51%   94.00%   +0.48%
==========================================
  Files          77       78       +1
  Lines        8989     8988       -1
==========================================
+ Hits         8406     8449      +43
+ Misses        583      539      -44

Impacted Files
Coverage Δ

proving_system/stark/src/lib.rs
95.83% <ø> (+27.97%)
:arrow_up:

proving_system/stark/src/proof.rs
0.00% <0.00%> (ø)

proving_system/stark/src/air/trace.rs
83.92% <83.63%> (+8.92%)
:arrow_up:

...oving_system/stark/src/air/constraints/boundary.rs
92.70% <93.75%> (+4.10%)
:arrow_up:

...ving_system/stark/src/air/constraints/evaluator.rs
100.00% <100.00%> (ø)

proving_system/stark/src/air/context.rs
100.00% <100.00%> (ø)

proving_system/stark/src/air/frame.rs
80.00% <100.00%> (-2.82%)
:arrow_down:

proving_system/stark/src/air/mod.rs
91.89% <100.00%> (+0.22%)
:arrow_up:

proving_system/stark/src/prover.rs
100.00% <100.00%> (ø)

proving_system/stark/src/verifier.rs
98.25% <100.00%> (+0.27%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Sort rows in EDA tool

Is your feature request related to a problem?
The buttons to sort rows in the EDA tool don't work.
Desired solution
They should sort the rows.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
Just adding this issue explicitly, since it came up during the evalutation.

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

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.17.0
GitHub release

Your semantic-release bot :package::rocket:


Notification > Charge Finished: Do not use the inactivity to trigger the Charge Finished notification

Dups of #1314


Added resources to css-grid-layout

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@meowwwls, everything LGTM! Thank you for helping us improve this section of the guide. Looking forward to your next contribution! :+1: :+1:


[DO NOT MERGE] Perf indexing no atomics

Describe your changes
Perf testing indexes and removing the atomic updates to see how they affect throughput
How best to test these changes
Issue ticket number and link

Codecov Report
Base: 57.68% // Head: 29.91% // Decreases project coverage by -27.77% :warning:

Coverage data is based on head (a3671ed) compared to base (bff06c2).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #862       +/-   ##
===========================================
- Coverage   57.68%   29.91%   -27.77%
===========================================
  Files         175      175
  Lines       19464    19450       -14
===========================================
- Hits        11227     5818     -5409
- Misses       7278    12949     +5671
+ Partials      959      683      -276

Impacted Files
Coverage Δ

server/config/options.go
0.00% <ø> (-10.53%)
:arrow_down:

server/services/v1/database/secondary_indexer.go
51.88% <ø> (-18.44%)
:arrow_down:

server/search/factory.go
0.00% <0.00%> (-100.00%)
:arrow_down:

lib/container/priority_queue.go
0.00% <0.00%> (-100.00%)
:arrow_down:

server/quota/namespace.go
0.00% <0.00%> (-98.37%)
:arrow_down:

server/search/sorted_hits.go
0.00% <0.00%> (-95.84%)
:arrow_down:

schema/lang/go.go
0.00% <0.00%> (-90.63%)
:arrow_down:

schema/lang/java.go
0.00% <0.00%> (-90.63%)
:arrow_down:

schema/lang/typescript.go
0.00% <0.00%> (-90.63%)
:arrow_down:

server/search/facets.go
0.00% <0.00%> (-88.60%)
:arrow_down:

... and 114 more

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.


Nirranjan Akilan's Personal Website changes

I added my social media links, a current project I am working on, and a picture of myself

Added changes


feat: check for shared key created by us

What I did

The code below fixes the case of where sharedWith and the authenticated atSign are the same atSign. In that case, we wouldn't want to be looking up a key like shared_key.alice@alice so we get the sharedBy instead.

String toLookup = "shared_key." + key.sharedWith.withoutPrefix() + atSign;
if(key.sharedWith.withoutPrefix().equals(atSign.withoutPrefix())) {
    toLookup = "shared_key." + key.sharedBy.withoutPrefix() + atSign;
}

For getting data from another atSign (shared with me), we have to find the shared aes key. First we check if it's shared by them with us and if that does not exist, we will try finding the shared key created by us shared with them.

private String _getSharedByOtherWithMe(SharedKey sharedKey) throws AtException {
    String shareEncryptionKey = null;
    try{
        shareEncryptionKey = getEncryptionKeySharedByOther(sharedKey);
    } catch (AtException e) {
        shareEncryptionKey = getEncryptionKeySharedByMe(sharedKey);
    }

It appears this was not actually required. I had been testing something on my ESP32 and it turned out to be an ESP32 problem. All is well now.


Fix UI unit tests

Description
This PR fixes unit tests for the UI
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
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Run npm run test:unit and verified all tests are passing:

=============================== Coverage summary ===============================
Statements   : 5.26% ( 1369/26007 )
Branches     : 4.64% ( 667/14381 )
Functions    : 2.39% ( 192/8021 )
Lines        : 5.35% ( 1351/25250 )
================================================================================

Test Suites: 4 passed, 4 total
Tests:       175 passed, 175 total
Snapshots:   0 total
Time:        18.776s
Ran all test suites.

Thanks @nvazquez I just got free from my household work, but saw you've already fixed it. I might ask for assistance on another PR where unit tests are failing.


quartz cli Please

Have you considered making Quartz simpler and less invasive in its usage?
Thank you for developing Quartz, both the previous Quartz-Hugo and the current Quartz v4. But I have a question, why not use a command-line tool to accomplish these tasks? My ideal process would be:

In my Obsidian directory, npm install @jackyzha0/quartz.
Run quartz init in the Obsidian directory to initialize a configuration file, which I can modify as needed.
Then, I can use quartz to build and publish my own website.
Of course, there can be some conventions, and if you want to use Quartz, certain conditions must be met, or changes must be made.

I found an issue on https://github.com/jackyzha0/quartz/issues/502, but I still don't understand why.
I have been using an Obsidian directory for a while, and in this directory, I have my own package.json and some of my own content. I don't want to fully integrate the Quartz repository into my directory,so the comparison is confusing to me. Is there any difficulty in providing a command-line tool?
I believe providing a CLI is a better approach. If you already have a package.json, you can simply add quartz as a dependency, and if you don't, you can use npm install @jackyzha0/quartz -g to use Quartz as a tool.

Hi, I have used quartz for some days, and here is my thought:
I make quartz and my obsidian vault independently, when I want to build my blog, I will do
npx quartz build -d <path to obsidian vault>

and upload pulic as my website.
Now quartz can't let config in one file, so it's unrealistic to have a quartz cli (especially when you want to customize quartz).

Closing as duplicate of #502

@qrzbing  Thank u, That's a  good idea.


Updated proposal with our motivation and purpose.

I edited the m1_proposal.md file to include:

Motivation
Purposes

of our project. Please review them and let me know what you think!

Looks good! I think this will form the foundation of our argument for our dashboard presentation in 542.
Good work


Providing alt attribute updates email

By defining alt as alt: Ember.computed.alias('email') the alt property can not be set without also updating the email field. I noticed this issue when suddenly the email and name properties of my models appeared to be bound to eachother...

Ah, yeah. I've been meaning to change this. I'll be removing the alias shortly and pushing a new version.

Published to npm<EMAIL_ADDRESS>


Talview changes

What talview changes? Everything is talview change

@harishnv Resolve the comments and clarify if required


Implement About Section

References #13

[ ] Add an about section to GoVizzy
[ ] List author names and SDP info
[ ] Manually test for functionality and correctness
[ ] Add UT to the extent possible

Got this done. Spent a real long time researching possibilities and trying things out, only to end up doing markdown.
[t:90]


Add QR code generation and verifying functions

Not sure if this should live in this repo or in jubmoji.quest, but we should have some code that generates a QR code for proofs (using various encoding tricks to lower size) and also a demo website that can verify such proofs.

Actually I think this should just be in jubmoji.quest repo for tracking purposes but the code might end up better being a part of this NPM package instead.


Incorrect argument label in call (have 'itemsCount:', expected 'coder:')

From the example code I try running, and it get error at this line of code:
let onboarding = PaperOnboarding(itemsCount: 3)
Saying: Incorrect argument label in call (have 'itemsCount:', expected 'coder:'). but when I change from itemsCount to coder it yell another error. I'm not sure that should I change or I am missing something?
I looked further inside the framework and appear to be in this area
init(itemsCount _: Int, delegate: OnboardingContentViewDelegate) {
        self.delegate = delegate
        super.init(frame: CGRect.zero)

        commonInit()
    }

    required init?(coder _: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }
}

PaperOnboarding does not have init(itemsCount,...) method
look to the code https://github.com/Ramotion/paper-onboarding/blob/master/Source/PaperOnboarding.swift#L67-L82
To set pages, you must use delegate and datasource methods

@0ber In the README on https://github.com/Ramotion/paper-onboarding you guys have let onboarding = PaperOnboarding(itemsCount: 3) tho?


BUG: Hotkeys not work

If you run the application in a language other than English, the hotkeys do not work.

https://www.autoitscript.com/forum/topic/209697-how-to-use-guisetaccelerators-for-multiply-language-layouts-moved


Enable LTO for Clang

In the same vein as #1, we get test failures with LTO enabled under clang in CPython under MacOS. My guess is that combining all the profile data from different extensions messes with LTO, so fixing #1 should fix this issue.
See https://github.com/esoma/pgo/actions/runs/681436849

Closed by a9fc37fa929b95414e1092421c4c4f0ad26416fc.


specify additional filter which would return only running instances

Thanks so much for your contribution. We just merged a pull request for the same issue so I'll be closing this one. Again, thanks very much for your contribution.


Update repo folder structure

We might want to consider updating the folders. For instance, there are 3 image files for the sketch which should probably be in a folder. Just not sure what to name it :P
If we change the location of the image files we need to remember to update the references in the README and any other document that links to them.

Certainly data should be moved to its own folder. And maybe the proposal as well? Open to suggestions on this one.

Certainly data should be moved to its own folder. And maybe the proposal as well? Open to suggestions on this one.

I think the pdf and png files should also be in a folder, maybe "images".

I think the pdf and png files should also be in a folder, maybe "images".


Add AWS Serverless example

See README.md for details. Source (and some others) are in Kotlin.
Programs.java and SourceModule.java are derived from the weather example, so I've left the Yahoo copyrights in.
There's not much actual code here (see Source classes), it's mostly glue!

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

Just a note that I have signed the CLA

Thank you.


[6.x] Add tests for preg_replace_array

This PR adds tests for the currently untested preg_replace_array helper.

For reference: https://github.com/laravel/framework/pull/31504


Update README.rst

Fixed typo.

Coverage remained the same at 89.888% when pulling 20b25c61866128d415a55e8d9ca1aab397e14960 on jox:patch-1 into bc495201374529613a475e83899785d6658f8ce3 on omji:master.

Thanks for the fix :)


Add nvramio

Implemented
nvram_read_ekcert()
nvram_read_key()
nvram_write_key()
These functions are used for read/write the U key from nvram in TPM.
Test passed. Ready for a reveiw.
Thanks!

Now there is only one commit for this PR. Removed all the unwraps.
Test passed. Read for a review.
Thanks!


[SPARK-46422][PS][TESTS] Move test_window to pyspark.pandas.tests.window.*

What changes were proposed in this pull request?
1, Move test_window to pyspark.pandas.tests.window.*
2, rename to test_missing
Why are the changes needed?
we use pyspark.pandas.tests.window.* to place all window-related tests;
test_window is confusing, it just test the missing stuffs
Does this PR introduce any user-facing change?
no, test-only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

cc @HyukjinKwon

merged to master


Missing biospecimens variables in dev [10/19/2022] - Jing

Compared with the Connect biospecimens data (original one), the flat version are missing these variables shown attached (especially those with compound field path in the sheet). Please help me double check if possible.
https://nih-my.sharepoint.com/:x:/g/personal/wuj12_nih_gov/ERt22Nj0IUZGvHsfHpeGCCABX3-5lUYTgSfo4Aba1stT0g

Yes. Just these variables need to help us carry to the flat version from dev.Connect.Biospecimens table. Thanks, Jake.

I added all variables from the excel sheet with type INT64 or STRING to the flatBiospecimen_JP table in dev.
I did not think that it is appropriate to add those variables with type STRUCT.
The query that generates this table can be found under Saved Queries --> Project Queries --> flatBiospecimen_JP in dev.
There is currently no scheduled query for this table in any of the environments. @FrogGirl1123 @jeannewu please let me know if you would like me to add one.

Hi, Jake, thank you very much for letting me know. Yes, no need to ferry those struct variables to the flat table. Thanks for letting me know.


Faulty connection between Teensy and LORA-E5

Teensy UART1 is connected to LORA-E5 UART, but incorrectly.
Current
Teensy TX1 -> E5 TX
Teensy RX1 -> E5 RX
Correct
Teensy TX1 -> E5 RX
Teensy RX1 -> E5 TX

Schematic fixed in e292b60af7054abfad739ed28330af7e54759051


Regression: textureSize() of screen/depth texture causes internal errors and editor hang

Godot version
v4.0.rc.custom_build [b12bf7ff0]
System information
Ubuntu 23.04 (Lunar Lobster)
Issue description
In a spatial shader: calling textureSize with a texture with hint_screen_texture or hint_depth_texture causes a long list of errors in the terminal, hangs the editor for a minute and fails to run the shader. Shaders using textureSize built fine two weeks ago.
Steps to reproduce
Open sample project. Errors should be printed to console right away.
terminal_output.txt
Minimal reproduction project
textureSize.zip
Shader for MeshInstance3D with a plane mesh:
shader_type spatial;

uniform sampler2D SCREEN_TEXTURE : hint_screen_texture, filter_linear_mipmap;

void fragment() {
    textureSize(SCREEN_TEXTURE, 0);  // <- culprit
    ALBEDO = vec3(1, 0, 0);
}

Looks like our multiview handling code is a little over-eager and is producing this:
textureSize(multiviewSampler(color_buffer, material_samplers[9]), multiview_uv(0.xy)

CC @BastiaanOlij


Treat wreal like any other primitive data type.

Simplify the grammar without making a special case for wreal.
Fixes #1017

If this fixes #1017, then you can also remove https://github.com/chipsalliance/verible/blob/master/.github/bin/smoke-test.sh#L113

done.


setTimeout 10000 ?

Hi @liuwenchao and thanks for your nice job,
I feel curious about the setTimeout 10000.
page.onInitialized = function() {
       page.evaluate(function() {
            setTimeout(function() {
                window.callPhantom();
            }, 10000);
        });
    };

is-it for testing purpose ?
Thanks

I answer myself : It's to be sure the page is fully rendered.
As @liuwenchao mention in the source code, please check : https://github.com/ariya/phantomjs/blob/master/examples/waitfor.js


3908: Media objects in response view

Adds thumbnails for audio/video
Updates download filenames for media files
Adds media_object association to Answer
Delegates mission to response through answer
Adds interpolations for mission and locale
Updates media object show route
Unhides multimedia questions for response view
Updates initializer with new paperclip URL specification

These look amazing:

One small note: please add a 5px bottom margin to each thumbnail so the spacing is more even.

Note: I changed disposition to inline so that the browser will display what it can. Fewer steps to view something that way. If the browser doesn't know what to do with it it will download it anyway.

Fantastic work overall. Really pleased!

Hmm, my browser was still displaying the images in the image tags with disposition: 'attachment' but wasn't downloading audio/video (instead, it was trying to play it in a new tab), are you saying the browser opening the content in a tab is more desirable?


Minor discussion edits

@ethanwhite I think all the discussion edits you did look good. I'd like to look at all the statements one more time when we have figures to look at. This is just fixing a few typos and adding in some more citation info.

Looks good to me. Thanks for the tip about rich diffs. I'd tried it on multi-commit diffs and assumed it wasn't relevant.


Fix typo in rule docs

Description
Small typo
What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.
[x] Read contribution guidelines.

Thank you!

This seems to be a problem on every page of the rule documentation. I have corrected everywhere. Thank you very much!


Always use https:// protocol for bower dependencies

git:// is unauthenticated (and we don't pin with commit SHA) so https:// should be preferred.
Since we're downloading from GitHub we need to add .git to access the Git endpoint over HTTPS.
This is a duplicate of the following pull requests:

#367 on the buyer app
#199 on the admin app

:+1:


Errors and deprecations

Getting this error:
~ npm run build
... <all tests are ok> ...
...
Loading "Gruntfile.js" tasks...ERROR
>> invalid snippets detected
Warning: Task "default" not found. Use --force to continue.

Aborted due to warnings.
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR<EMAIL_ADDRESS>build: `grunt`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/dmitrizaitsev/.npm/_logs/2019-07-26T03_49_11_024Z-debug.log

Might be due to some outdated deps, e.g. this one had been deprecated:
https://www.npmjs.com/package/grunt-contrib-uglify-es

'However, they do some steps in the false direction, like making a difference between verbs and functions.'
https://vector.org.uk/a-modern-apl-system/
View in Slack

I'm not sure it's the same issue, but I'm getting this today on osX 12.0.1 (Monterey)
82 verbose stack Error<EMAIL_ADDRESS>preinstall: `npm run build --silent`
82 verbose stack Exit status 1
82 verbose stack     at EventEmitter.<anonymous> (/opt/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
82 verbose stack     at EventEmitter.emit (node:events:390:28)
82 verbose stack     at ChildProcess.<anonymous> (/opt/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
82 verbose stack     at ChildProcess.emit (node:events:390:28)
82 verbose stack     at maybeClose (node:internal/child_process:1064:16)
82 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
83 verbose pkgid<EMAIL_ADDRESS>84 verbose cwd /Users/douglasmennella/bin
85 verbose Darwin 21.1.0
86 verbose argv "/opt/local/bin/node" "/opt/local/bin/npm" "i" "@kparc/k"
87 verbose node v16.13.1
88 verbose npm  v6.14.15
89 error code ELIFECYCLE
90 error errno 1
91 error<EMAIL_ADDRESS>preinstall: `npm run build --silent`
91 error Exit status 1
92 error Failed at the<EMAIL_ADDRESS>preinstall script.
92 error This is probably not a problem with npm. There is likely additional logging output above.
93 verbose exit [ 1, true ]

There's not a lot more useful that I can spot in the log.  This probably:
74 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
75 info lifecycle<EMAIL_ADDRESS>Failed to exec preinstall script


Check archive prior to every download

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Using --download-archive options saves info about the already downloaded video. If the archive.txt file was changed manually, for example manually added "site video_id" for not available videos, yt-dlp ignores it until next start and is trying to downloadt it again. Often the same video is available miltiple times in the playlist. Could you please let yt-dlp to check this file not only at start but also for every not downloaded video.
Many thanks in advance
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

The file is not intended to be edited manually. This would significantly slow down archive speed (like in youtube-dl). This won't be properly supported, but perhaps a compat option can be added.


The option 'family' for tex2svg / tex2chtml has no default value

I use MathJax.getMetricsFor to get an options object for tex2chtml or tex2svg, as described in the typesetting page in the docs.
It includes an attribute family whose value is the empty string. When I pass the object to tex2chtml, I get an error "Invalid option "family" (no default exists)". So it looks easy to fix, but I don't know where to look for the default values.
Here's a node script which produces the error:
const MathJax = require('mathjax');

MathJax.init({
    loader: {load: ['input/tex', 'output/svg']}
}).then(MathJax => {
    const svg = MathJax.tex2svg('2x',{family:''});
}).catch(err => {
    console.error(err);
});

(I'd love to fix this myself, but I can't remember how to run unminified MathJax v3)

Ok, this is caused by the addition of the family property to the extended metric data used by the HTML MathDocument class, which was not taken into account by the convert() macro that underlies tex2svg() and the other similar conversion functions.  Unfortunately, the default list is not in a place that is easily adjusted on the fly.  Here is a configuration that can be used to replace the convert() function with a fixed one.  This not only allows the family property, but actually handles it to provide support for mtextInheritFont and the other similar output options.
<script>
MathJax = {
  startup: {
    ready() {
      const {HTMLDocument} = MathJax._.handlers.html.HTMLDocument;
      const {userOptions} = MathJax._.util.Options;
      const {STATE} = MathJax._.core.MathItem;
      HTMLDocument.prototype.convert = function (math, options = {}) {
        let {family, format, display, end, ex, em, containerWidth, lineWidth, scale} = userOptions({
          family: '', format: this.inputJax[0].name, display: true, end: STATE.LAST,
          em: 16, ex: 8, containerWidth: null, lineWidth: 1000000, scale: 1
        }, options);
        if (containerWidth === null) {
          containerWidth = 80 * ex;
        }
        const jax = this.inputJax.reduce((jax, ijax) => (ijax.name === format ? ijax : jax), null);
        const mitem = new this.options.MathItem(math, jax, display);
        if (this.outputJax.options.mtextInheritFont) {
          mitem.outputData.mtextFamily = family;
        }
        if (this.outputJax.options.merrorInheritFont) {
          mitem.outputData.merrorFamily = family;
        }
        mitem.start.node = this.adaptor.body(this.document);
        mitem.setMetrics(em, ex, containerWidth, lineWidth, scale);
        mitem.convert(this, end);
        return (mitem.typesetRoot || mitem.root);
      };
      MathJax.startup.defaultReady();
    }
  }
};
</script>

It is longer than I would like, but you have to replace the entire convert() function in order to make the needed changes.  I will make a PR that fixes the function for the next release.  We'll probably have to make a point release to fix this.  Sigh.

When will this fix be released?

We are hoping to get a release out later this week.


Integration / link with youtube help videos

It would be great to further integrate with the youtube support videos that @izzirbucknall has created:
https://www.youtube.com/channel/UCAVH1gcgJXElsj8ENC-bDQQ/videos
We can discuss on this thread, perhaps

Yes would be good to point users to these espeically as we have had good feedback about them and they are definitely being used. Could something be added to the main home page at www.aidstream.org?

@anjhero need to put the video somewhere in the homepage - thoughts please?

We will put the following text in besides the video link or button.
"Watch videos on how to use Aidstream [button to youtube channel]"
@iatisupport does that sound ok to you?

Included the line on youtuve under "How to use" block.


Karpenter can't add new nodes after a Windows workload

Description
Observed Behavior:
On a cluster with both Windows and Linux support, no Linux nodes can be created after windows nodes have been created.
Expected Behavior:
Windows and Linux workloads can run at any time and at the same time.
Reproduction Steps (Please include YAML):
With a new EKS 1.28 cluster, perform the following steps:

Enable windows support by applying the following yaml (see https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html):

apiVersion: v1
kind: ConfigMap
metadata:
  name: amazon-vpc-cni
  namespace: kube-system
data:
  enable-windows-ipam: "true"

Install karpenter
Add a NodeClass for Linux

apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: linux-default
spec:
  amiFamily: AL2
  role: XXX
  securityGroupSelectorTerms:
  - id: XXX
  - id: XXX
  subnetSelectorTerms:
  - id: XXX
  - id: XXX

Add a NodePool for Linux

apiVersion: karpenter.sh/v1beta1
kind: NodePool
metadata:
  name: default
spec:
  template:
    spec:
      nodeClassRef:
        name: linux-default
      requirements:
      - key: kubernetes.io/arch
        operator: In
        values:
        - amd64
  weight: 20

Add a NodeClass for Windows

apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: windows-default
spec:
  amiFamily: Windows2022
  role: XXX
  securityGroupSelectorTerms:
  - id: XXX
  - id: XXX
  subnetSelectorTerms:
  - id: XXX
  - id: XXX

Add a NodePool for Windows

apiVersion: karpenter.sh/v1beta1
kind: NodePool
metadata:
  name: windows-default
spec:
  template:
    spec:
      nodeClassRef:
        name: windows-default
      requirements:
      - key: kubernetes.io/arch
        operator: In
        values:
        - amd64
      - key: kubernetes.io/os
        operator: In
        values:
        - windows
  weight: 10

Add a Windows workload.  Wait until the Node is ready and the workload is running before proceeding to the next step.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: eks-sample-windows-deployment
  labels:
    app: eks-sample-windows-app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: eks-sample-windows-app
  template:
    metadata:
      labels:
        app: eks-sample-windows-app
    spec:
      containers:
      - name: windows-server-iis
        image: mcr.microsoft.com/windows/servercore:ltsc2022
        imagePullPolicy: IfNotPresent
        command:
        - powershell.exe
        - -command
        - "Add-WindowsFeature Web-Server; Invoke-WebRequest -UseBasicParsing -Uri 'https://dotnetbinaries.blob.core.windows.net/servicemonitor/<IP_ADDRESS>/ServiceMonitor.exe' -OutFile 'C:\\ServiceMonitor.exe'; echo '

<marquee>
Hello EKS!!!
<marquee>' > C:\\inetpub\\wwwroot\\default.html; C:\\ServiceMonitor.exe 'w3svc'; "
      nodeSelector:
        kubernetes.io/os: windows

Add a Linux workload (I add resources to make sure karpenter adds a node to my cluster)

apiVersion: apps/v1
kind: Deployment
metadata:
  name: eks-sample-linux-deployment
  labels:
    app: eks-sample-linux-app
spec:
  replicas: 6
  selector:
    matchLabels:
      app: eks-sample-linux-app
  template:
    metadata:
      labels:
        app: eks-sample-linux-app
    spec:
      containers:
      - name: nginx
        image: public.ecr.aws/nginx/nginx:latest
        imagePullPolicy: IfNotPresent
        resources:
          requests:
            memory: "8Gi"
            cpu: "2000m"
          limits:
            memory: "8Gi"
            cpu: "2000m"
      nodeSelector:
        kubernetes.io/os: linux

The expected result is that karpenter will add a new Linux node for the additional pods requested in step 8.  Instead Karpenter shows the following message:
{
  "level": "ERROR",
  "time": "2024-02-15T01:06:29.649Z",
  "logger": "controller.provisioner",
  "message": "Could not schedule pod, incompatible with nodepool \"default\", daemonset overhead={\"cpu\":\"660m\",\"memory\":\"1424Mi\",\"pods\":\"8\",\"vpc.amazonaws.com/PrivateIPv4Address\":\"1\"}, no instance type satisfied resources {\"cpu\":\"2660m\",\"memory\":\"9616Mi\",\"pods\":\"9\",\"vpc.amazonaws.com/PrivateIPv4Address\":\"1\"} and requirements karpenter.sh/nodepool In [default], kubernetes.io/arch In [amd64], kubernetes.io/os In [linux] (no instance type has enough resources); incompatible with nodepool \"windows-default\", daemonset overhead={\"cpu\":\"30m\",\"memory\":\"120Mi\",\"pods\":\"1\",\"vpc.amazonaws.com/PrivateIPv4Address\":\"1\"}, incompatible requirements, key kubernetes.io/os, kubernetes.io/os In [linux] not in kubernetes.io/os In [windows]",
  "commit": "1072d3b",
  "pod": "default/eks-sample-linux-deployment-7bcbb64cc8-skgrc"

Versions:

Chart Version: v0.32.1
Kubernetes Version (kubectl version): 1.28

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What's the status output from getting both of the EC2NodeClasses that you have on the cluster?

Ok, after looking into it a little deeper, I think I know what's going on here. Karpenter currently calculates DaemonSet overhead based off of the NodePool requirements. It isn't currently aware of the instance type requirements or the EC2NodeClass requirements, so the scheduler is unaware of the fact that that NodePool that you are using for Linux is only targeted for Linux nodes solely based off of the NodePool (even though you are referencing AL2 in the EC2NodeClass).
I'm assuming that you have some DaemonSet on your cluster (maybe the Windows EBS CSI driver) that is targeted at Windows nodes and gets the vpc.amazonaws.com/PrivateIPv4Address resource. Karpenter thinks that this DaemonSet will schedule against your default NodePool targeted at Linux nodes. When it sees that none of the instance types for your AL2 EC2NodeClass can support this resource, it says it can't schedule. Likewise, it can't target your Windows NodePool due to the OS requirement.

There's some ideas around how to solve this problem that are detailed in #715. For now, the suggested workaround would be to add the kubernetes.io/os label to the default NodePool so that you can continue to schedule both OSes on your cluster.

/remove-kind bug
/kind support

Thanks @jonathan-innis.  I was just working on reproducing the issue since I was testing with a transient cluster.
You are correct that my cluster has the EBS CSI driver Daemonset for windows nodes.  And it does seem that adding a linux nodeSelector solves the issue.
Thanks again.

/reopen


Travis builds are taking too long

We've been noticing that Travis builds are taking up a lot of time: well over 40 minutes in most cases, sometimes even timing out. In contrast, zipline's tests seem to take somewhere around 20 minutes apiece. This is affecting our ability to develop pyfolio.
@yankees714 @richafrank I think we'll need an engineer to weigh in on this: Gus, Thomas and I didn't really know what to do about this.

Seems like we've seen large variations in travis job times on zipline too. For example, python 3.5 took double that of python 3.4 on this build. Not sure - maybe we just have to live with that on shared infrastructure?
Since some pyfolio tests in the "fast" cases still take 10 minutes (pyfolio.tests.test_tears.PositionsTestCase.test_create_bayesian_tear_sheet_breakdown_1), is there any way to make them faster? Smaller time frames?


Add WhateverItWorks Instances

https://whateveritworks.org

There are already 8 instances in services-full.json
Some of them scraped automatically from official lists

There are already 8 instances in services-full.json
Some of them scraped automatically from official lists

one of them is cringe.whateveritworks.social which is wrong, should be cringe.whateveritworks.org

one of them is cringe.whateveritworks.social

No, it's not. It's just cringe.whatever.social, and cringe.whateveritworks.org have been added on #110


"Pițiga" is listed in the drop-down menu

Description:
"Pițiga" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Pițiga" in the search bar.

Expected results
The location is listed in the drop-down menu as "Pițiga, Alba (Lupșa)".


The server part of the library sends open and change event on open

The library should only send a open even on open notification. The current code does:
this._onDidOpen.fire({ document });
this._onDidChangeContent.fire(Object.freeze({ document }));

@aeschli any objection that I change this. It is IMO bogus and I have no idea why I did it this way.

You talk about the events on TextDocuments, right?
My servers only listen to TextDocuments.onDidChangeContent to trigger a validation (they don't listen to onDidOpen).
documents.onDidChangeContent(change => {
	triggerValidation(change.document);
});

Would your change break me, or is there a onDidChangeContent guaranteed to follow after a document has opened?
It's also what the sample does.
So I'd say it's a risky change.

Yes, you would be affected. Good point with the sample. Then we leave it as is.


Warning messages

Hey guys,
I'm getting the following warning messages:
Warning: output "user_name": must use splat syntax to access aws_iam_user.default attribute "name", because it has "count" set; use aws_iam_user.default.*.name to obtain a list of the attributes across all instances

Warning: output "user_arn": must use splat syntax to access aws_iam_user.default attribute "arn", because it has "count" set; use aws_iam_user.default.*.arn to obtain a list of the attributes across all instances

Warning: output "user_unique_id": must use splat syntax to access aws_iam_user.default attribute "unique_id", because it has "count" set; use aws_iam_user.default.*.unique_id to obtain a list of the attributes across all instances

Warning: output "access_key_id": must use splat syntax to access aws_iam_access_key.default attribute "id", because it has "count" set; use aws_iam_access_key.default.*.id to obtain a list of the attributes across all instances

Warning: output "secret_access_key": must use splat syntax to access aws_iam_access_key.default attribute "secret", because it has "count" set; use aws_iam_access_key.default.*.secret to obtain a list of the attributes across all instances

I'm using the following version of Terraform:
andres ~ $ terraform version
Terraform v0.11.2

Thank you!

@amontalban
This was addressed in https://github.com/cloudposse/terraform-aws-iam-system-user/releases/tag/0.2.2
Merged to master.
Thank you for testing.
We'll close the issue for now.

w00t! Thank you so much for fixing this @aknysh!

Hi @aknysh,
I have tested this change but for some reason I'm not getting output (Besides the users are created properly). This is the text I get when running terraform apply:
Apply complete! Resources: 11 added, 0 changed, 0 destroyed.

And when trying to do terraform output I get this:
The state file either has no outputs defined, or all the defined
outputs are empty. Please define an output in your configuration
with the `output` keyword and run `terraform refresh` for it to
become available. If you are using interpolation, please verify
the interpolated value is not empty. You can use the
`terraform console` command to assist.

This is my configuration:
module "gitlabci-user" {
  source = "cloudposse/iam-system-user/aws"
  version = "0.2.2"

  namespace = "${var.domain}"
  stage = "production"
  name = "gitlabci"
  policy  = "${data.aws_iam_policy_document.gitlabci_user_policy.json}"
}

Am I doing something wrong?
Thanks!

@amontalban
thank you again for testing.
 Resources: 3 added, 0 changed, 0 destroyed.

Outputs:

access_key_id = AKIAIV4CHHX7R5J43CMQ
secret_access_key = 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
user_arn = arn:aws:iam::423790052478:user/app
user_name = app
user_unique_id = AIDAJBDM7QVKSM5A7HCFY

Do you use other resources? I see 11 resources added in your example
 Apply complete! Resources: 11 added
Can you share the full setup that you are using?

@amontalban based on your example, you do not provide any outputs. That's why terraform output is empty. Unfortunately module outputs are not automatically output. You need to redefine the in the root scope.
E.g.
This is my configuration:

module "gitlabci-user" {
  source = "cloudposse/iam-system-user/aws"
  version = "0.2.2"

  namespace = "${var.domain}"
  stage = "production"
  name = "gitlabci"
  policy  = "${data.aws_iam_policy_document.gitlabci_user_policy.json}"
}
output "user_name" {
  value = "${module.gitlabci-user.user_name}"
}

output "user_arn" {
  value = "${module.gitlabci-user.user_arn}"
}

output "user_unique_id" {
  value = "${module.gitlabci-user.user_unique_id}"
}

output "access_key_id" {
  value = "${module.gitlabci-user.access_key_id}"
}

output "secret_access_key" {
  value = "${module.gitlabci-user.secret_access_key}"
}


prevents posting with backward or existing k

sometimes clients are lazy to update lasthave values or users can't be patient, especially on retwisting k and lastk values can be equal, so that pieces can't be added to swarm but it is put on dht, like...

and it prevents also posting with backward k...

that approach was completely wrong :(

I didn't thought of the patch yet, but it sounds like a valid concern (preventing such case).

sorry for not reviewing in time... was your second approach wrong? it looks like a good check.

after using it awhile, i couldn't be sure.. especially with newpostraw, postponed insertion can be required. it would be better to check only in newrtmsg and newpostmsg.

Ehm, maybe I am interpreting this wrong, but preventing "decrementing" k from being posted should be somewhat equivalent to the problem that distributed consensus algorithms typically solve, and why they were researched in the first place, no?
If you take the original Paxos paper for example, they story is literally about a parliament trying to pass decrees in a certain order, making sure that no decree can be passed out of order. Skipping k's is okay, but filling up gaps left before is not.
Iff that is indeed an analogy to our "problem" here then for me that would suggest that a quick fix won't do it since the problem is pretty darn complicated, pretty much on the same level as the identity management (bitcoin) actually.


View not refreshing

I've deployed kubedash to my Google Cloud Compute cluster, and originally it was working great: the information showed matched the information I had gotten from the GCP dashboard. However, the information shown is stuck at around the time I first created the service. I've tried deleting the service and ReplicationController and re-creating them; no luck. Any advice on troubleshooting?

Kubedash does not understand services. It can only understand pods, nodes,
containers and namespaces as of now. Can you elaborate a bit more? Any
chance you are confusing kube terminology?
On Tue, Feb 2, 2016 at 5:14 PM Adrian Wan<EMAIL_ADDRESS>wrote:

I've deployed kubedash to my Google Cloud Compute cluster, and originally
it was working great: the information showed matched the information I had
gotten from the GCP dashboard. However, the information shown is stuck at
around the time I first created the service. I've tried deleting the
service and ReplicationController and re-creating them; no luck. Any advice
on troubleshooting?
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/kubedash/issues/51.

I think @awan1 is referring to the kubedash service itself.
Kubedash should be periodically polling the Heapster Model REST API. If you are not receiving new data in real-time or after refreshing your browser, I would recommend the following troubleshooting steps and listing your results here:

Open your browser's javascript console and check for recurring errors (F12 for chrome/firefox).
Manually access the Heapster API through /api/v1/model/metrics and check the timestamps of the resulting timeseries. Check again after a couple of minutes to see if new data has been added.
Access the heapster and kubedash logs with kubectl get pods and then kubectl logs <pod_id> and search for errors.

@afein thanks for clarifying - I was indeed referring to the kubedash service.
Javascript console:
Mixed Content: The page at 'https://<k8s_master_ip>/api/v1/proxy/namespaces/kube-system/services/kubedash/#!/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Muli:400,300italic'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://<k8s_master_ip>/api/v1/proxy/namespaces/kube-system/services/kubedash/#!/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Montserrat:400,700'. This request has been blocked; the content must be served over HTTPS.
(index):34 Mixed Content: The page at 'https://<k8s_master_ip>/api/v1/proxy/namespaces/kube-system/services/kubedash/#!/' was loaded over HTTPS, but requested an insecure image 'http://kubernetes.io/img/desktop/nav_logo.svg'. This content should also be served over HTTPS.
<IP_ADDRESS>/:1 GET https://<k8s_master_ip>/img/mobile/nav_logo.svg 404 (Not Found)

Heapster API:
In https://<k8s_master_ip>/api/v1/model/metrics (K8s master IP obtained from kubernetes cluster-info), I get a 404:
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "the server could not find the requested resource",
  "reason": "NotFound",
  "details": {},
  "code": 404
}

That seems like a good indication of something going wrong. And the cluster-info command also gives
Heapster is running at https://<k8s_master_ip>/api/v1/proxy/namespaces/kube-system/services/heapster
instead of at the URL /api/v1/model/metrics as above. Any suggestions?
Logs:

Kubedash logs look good, code-200 GETs to /api/v1/model/...
No logs from the heapster pod, the logs command returns nothing. The pod is running, though.

I set up this cluster via gcloud container clusters create, in case that's important.

Possibly related: following this page, which seemed to apply because I did set up my cluster with GKE, I checked the stackdriver link and found that I hadn't enabled Google Cloud Monitoring on my project yet.

FYI: @allannaim

Update: after enabling Google Cloud Monitoring and using the stackdriver dashboard, I can see all my live information in awesome detail. So my data is being served somewhere that GCM can access; I guess it might be in a different place than Kubedash is expecting.
I'll leave this issue open in case someone else experiences this, but, as I have access to the data I need, this shouldn't be considered urgent.


Prepare for renaming default branch to main

Summary
With the pending support being added to qiskit-bot in
Qiskit/qiskit-bot#9 we're able to rename the default branch for the
repository to 'main'. However, when we do that several things will need
to be updated, most importantly the CI trigger was hardcoded to the
previous default branch 'master. This commit fixes these references and
should be merged after we rename the branch to re-enable CI.
Details and comments

Labeling this as on hold because it can't merge until we actually rename the branch (which is still blocked on https://github.com/Qiskit/qiskit-bot/pull/9 ). This should probably wait until after the 0.17.1 release later this week and we can schedule a time to do this so we can plan ahead of time.

ok, the default branch is now named main so this is unblocked


Introduce Module Named "Overlay" and Merge "NoChatRect" Into It

Describe the solution you'd like
The NoChatRect module is a very nice addition to the HUD, and it would be nice if options for disabling the scoreboard and tab background could also be implemented. Instead of creating two separate modules for this functionality, it would make sense to include them as toggles inside a single module named "Overlay" (or perhaps a different name.)
Additional context
Replaces some of the functionality of the better tab mod.

planned for 1.13


TOSCA Mini-IDE git Verison not found

➜  puccini git:(main) ✗ git show 1c0eb8a7858a6a8442f68b9a7f0c22dea34b84c7
fatal: bad object 1c0eb8a7858a6a8442f68b9a7f0c22dea34b84c7

Click show puccini Version of TOSCA Mini-IDE, and then see the result:
version=v0.20.1-31-g1c0eb8a
revision=1c0eb8a7858a6a8442f68b9a7f0c22dea34b84c7
timestamp=2022-12-28 14:19:30 CST
arch=wasm
os=js
compiler=gc
compiler-version=go1.19.4

This is due to us sometimes doing a git push --force and hashes disappearing. :) We try not to do this often. This will be fixed in the next Mini-IDE release.

Thanks


No longer working out of nowhere

I use it almost every day without messing on anything i don't know, so i only go between the separated and tracks folders, but suddenly it stopped working with any model i used, and it's giving the message:
loading model... done
stft of wave source... Traceback (most recent call last):
File "/content/drive/MyDrive/VocalRemover5-COLAB_arch/main.py", line 307, in
main()
File "/content/drive/MyDrive/VocalRemover5-COLAB_arch/main.py", line 293, in main
multi_file(useModel, args.input)
File "/content/drive/MyDrive/VocalRemover5-COLAB_arch/main.py", line 244, in multi_file
process.inference()
File "/content/drive/MyDrive/VocalRemover5-COLAB_arch/main.py", line 94, in inference
X_spec_m, input_high_end_h, input_high_end = spec_utils.loadWave(self.input, mp, hep=self.hep)
File "/content/drive/MyDrive/VocalRemover5-COLAB_arch/lib/spec_utils.py", line 14, in loadWave
X_wave[bands_n+1], _ = librosa.load(
TypeError: load() takes 1 positional argument but 3 positional arguments (and 2 keyword-only arguments) were given
How do I fix it?

I do not provide support for the Colab version since I did not write it.

There is a problem with the librosa library version, just reinstall the old one, and run the following two lines to test it out
!pip uninstall librosa -y
!pip install librosa==0.8.1


Strange URL (http://) on public endpoints

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Set up Rancher HA as described in https://rancher.com/docs/rancher/v2.x/en/installation/ha/
Deploy a Catalog App which creates a public endpoint

Result:
The public endpoints have strange URLs, for example:

http://<nil>:32285
http://<nil>:31871

Other details that may be helpful:
The issue does not occur when using single-node Installation of Rancher.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): Rancher v2.1.5, but even tried with v2.1.6
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Imported

Machine type (cloud/VM/metal) and specifications (CPU/memory): 4 VMs, each with 2 vCPUs and 16 GB RAM. Two hold the etcd and Control Plane roles, the other two are workers.

cluster.yml (used for creation):

# If you intened to deploy Kubernetes in an air-gapped environment,
# please consult the documentation on how to configure custom RKE images.
nodes:
- address: dkr9000.blab.ch
  port: "22"
  internal_address: ""
  role:
  - controlplane
  - etcd
  hostname_override: ""
  user: user
  docker_socket: /var/run/docker.sock
  ssh_key: ""
  ssh_key_path: /home/user/.ssh/id_rsa
  labels: {}
- address: dkr9001.blab.ch
  port: "22"
  internal_address: ""
  role:
  - controlplane
  - etcd
  hostname_override: ""
  user: user
  docker_socket: /var/run/docker.sock
  ssh_key: ""
  ssh_key_path: /home/user/.ssh/id_rsa
  labels: {}
- address: dkr9002.blab.ch
  port: "22"
  internal_address: ""
  role:
  - worker
  hostname_override: ""
  user: user
  docker_socket: /var/run/docker.sock
  ssh_key: ""
  ssh_key_path: /home/user/.ssh/id_rsa
  labels: {}
- address: dkr9003.blab.ch
  port: "22"
  internal_address: ""
  role:
  - worker
  hostname_override: ""
  user: user
  docker_socket: /var/run/docker.sock
  ssh_key: ""
  ssh_key_path: /home/user/.ssh/id_rsa
  labels: {}
services:
  etcd:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    external_urls: []
    ca_cert: ""
    cert: ""
    key: ""
    path: ""
    snapshot: null
    retention: ""
    creation: ""
  kube-api:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    service_cluster_ip_range: <IP_ADDRESS>/16
    service_node_port_range: ""
    pod_security_policy: false
  kube-controller:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    cluster_cidr: <IP_ADDRESS>/16
    service_cluster_ip_range: <IP_ADDRESS>/16
  scheduler:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
  kubelet:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    cluster_domain: cluster.local
    infra_container_image: ""
    cluster_dns_server: <IP_ADDRESS>
    fail_swap_on: false
  kubeproxy:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
network:
  plugin: canal
  options: {}
authentication:
  strategy: x509
  options: {}
  sans: []
addons: ""
addons_include: []
system_images:
  etcd: rancher/coreos-etcd:v3.2.18
  alpine: rancher/rke-tools:v0.1.15
  nginx_proxy: rancher/rke-tools:v0.1.15
  cert_downloader: rancher/rke-tools:v0.1.15
  kubernetes_services_sidecar: rancher/rke-tools:v0.1.15
  kubedns: rancher/k8s-dns-kube-dns-amd64:1.14.10
  dnsmasq: rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10
  kubedns_sidecar: rancher/k8s-dns-sidecar-amd64:1.14.10
  kubedns_autoscaler: rancher/cluster-proportional-autoscaler-amd64:1.0.0
  kubernetes: rancher/hyperkube:v1.11.6-rancher1
  flannel: rancher/coreos-flannel:v0.10.0
  flannel_cni: rancher/coreos-flannel-cni:v0.3.0
  calico_node: rancher/calico-node:v3.1.3
  calico_cni: rancher/calico-cni:v3.1.3
  calico_controllers: ""
  calico_ctl: rancher/calico-ctl:v2.0.0
  canal_node: rancher/calico-node:v3.1.3
  canal_cni: rancher/calico-cni:v3.1.3
  canal_flannel: rancher/coreos-flannel:v0.10.0
  wave_node: weaveworks/weave-kube:2.1.2
  weave_cni: weaveworks/weave-npc:2.1.2
  pod_infra_container: rancher/pause-amd64:3.1
  ingress: rancher/nginx-ingress-controller:0.16.2-rancher1
  ingress_backend: rancher/nginx-ingress-controller-defaultbackend:1.4
  metrics_server: rancher/metrics-server-amd64:v0.2.1
ssh_key_path: /home/user/.ssh/id_rsa
ssh_agent_auth: true
authorization:
  mode: rbac
  options: {}
ignore_docker_version: false
kubernetes_version: ""
private_registries: []
ingress:
  provider: ""
  options: {}
  node_selector: {}
  extra_args: {}
cluster_name: "test"
cloud_provider:
  name: ""
prefix_path: ""
addon_job_timeout: 0
bastion_host:
  address: ""
  port: ""
  user: ""
  ssh_key: ""
  ssh_key_path: ""
monitoring:
  provider: ""
  options: {}

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:35:51Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.6", GitCommit:"b1d75deca493a24a2f87eb1efde1a569e52fc8d9", GitTreeState:"clean", BuildDate:"2018-12-16T04:30:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:      17.03.2-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:21:36 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.2-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:21:36 2017
 OS/Arch:      linux/amd64
 Experimental: false

Operating System is CentOS 7:
Output of cat /etc/os-release:

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Output of uname -r:
3.10.0-957.1.3.el7.x86_64

Upgrade to Rancher v2.1.6 and Kubernetes v1.12.5 did not resolve the issue.

Example of what I exactly mean:
Software:

OS: CentOS 7
Rancher version: v2.1.6
Kubernetes version: v1.12.4
Docker version: 17.3.2
RKE version: v0.1.15

HA-Setup:

VM 1 is loadbalancer
VM 2 and 3 are etcd/Control Plane hosts
VM 4 and 5 are workers

Connection can be established, it is all working correctly (no errors).
To reproduce the problem, I use "efk" from the "Library"-Catalog. I go to Cluster --> test --> Namespace Default. Then I go to Catalog Apps, select EFK and change the setting "Expose Kibana using Layer 7 Load Balancer" to "False". After that, I launch the application. The following occurs:

The Pods, Services, Secrets and Config Maps are created
The Endpoints are created

Now, let's have a look at the Endpoints:

The URL is http://<nil>:Port
Here the output of kubectl get service -n efk-test:
NAME                     TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
efk-test-elasticsearch   NodePort   <IP_ADDRESS>   <none>        9200:31237/TCP,9300:31986/TCP   5m37s
efk-test-kibana          NodePort   <IP_ADDRESS>    <none>        443:31290/TCP                   5m37s

Output of kubectl describe service -n efk-test efk-test-elasticsearch:
Name:                     efk-test-elasticsearch
Namespace:                efk-test
Labels:                   app=elasticsearch
                          chart=elasticsearch-0.1.0
                          heritage=Tiller
                          io.cattle.field/appId=efk-test
                          release=efk-test
Annotations:              field.cattle.io/publicEndpoints:
                            [{"addresses":["\u003cnil\u003e"],"port":31237,"protocol":"TCP","serviceName":"efk-test:efk-test-elasticsearch","allNodes":true},{"address...
Selector:                 app=elasticsearch,component=master,release=efk-test
Type:                     NodePort
IP:                       <IP_ADDRESS>
Port:                     http  9200/TCP
TargetPort:               http/TCP
NodePort:                 http  31237/TCP
Endpoints:                <IP_ADDRESS>:9200,<IP_ADDRESS>:9200,<IP_ADDRESS>:9200 + 3 more...
Port:                     transport  9300/TCP
TargetPort:               transport/TCP
NodePort:                 transport  31986/TCP
Endpoints:                <IP_ADDRESS>:9300,<IP_ADDRESS>:9300,<IP_ADDRESS>:9300 + 3 more...
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

Output of kubectl describe service -n efk-test efk-test-elasticsearch:
Name:                     efk-test-kibana
Namespace:                efk-test
Labels:                   app=kibana
                          chart=kibana-0.5.0
                          heritage=Tiller
                          io.cattle.field/appId=efk-test
                          release=efk-test
Annotations:              field.cattle.io/publicEndpoints:
                            [{"addresses":["\u003cnil\u003e"],"port":31290,"protocol":"TCP","serviceName":"efk-test:efk-test-kibana","allNodes":true}]
Selector:                 app=kibana,release=efk-test
Type:                     NodePort
IP:                       <IP_ADDRESS>
Port:                     <unset>  443/TCP
TargetPort:               5601/TCP
NodePort:                 <unset>  31290/TCP
Endpoints:                <IP_ADDRESS>:5601
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

As you can see in the Annotations, the adress does not look healthy 😄

FYI your "HA" is not HA at all... 2 nodes with etcd is worse than one, it survives a maximum of 0 nodes failing and you now have twice as many available to fail.  You want an odd number.

I admit this is my fault, I will change that soon. But unfortunately this does not solve my problem.
If you need more information, configurations or logs, please tell me.

Yes I know it's not related, just saying.

Hello everyone
I have now tried it again with two HP ProLiant BL490c G7 and three HP ProLiant BL620c G7. The problem is still the same when deploying workloads with endpoints:
http://:32285
http://:31871 or other URLs like this.
This time I have used Rancher version v2.2.3 and RKE version v0.2.2.
Other details that may be helpful:
The issue does not occur when using single-node Installation of Rancher.

I am experiencing this too. What's strange is that the first cluster I brought up doesn't have this problem. The next two, however, do. It would be helpful to know, where rancher gets the info to populate the annotations field
field.cattle.io/publicEndpoints:
                            [{"addresses":["\u003cnil\u003e"]...

From my testing it appears that this behaviour occurs when provisioning clusters with nodes where the 'address' defined for cluster nodes in the RKE cluster configuration yaml is a FQDN, rather than an IP, I reproduced with the cluster configuration yaml below, using RKE v0.2.7 and Rancher v2.2.7:
nodes:
- address: node00.alexseymour.com
  user: root
  role: [controlplane,worker,etcd]
- address: node01.alexseymour.com
  user: root
  role: [controlplane,worker,etcd]
- address: node02.alexseymour.com
  user: root
  role: [controlplane,worker,etcd]

ssh_agent_auth: true

services:
  etcd:
    snapshot: true
    creation: 6h
    retention: 24h

@axeal can you share the following output for one of the nodes having fqdn as the name:
kubectl get node <nodename> -o json

@axeal I can confirm your observation. I was getting this quite consistently when using the fqdn of our servers with rke0.2.4 and rancher 2.2.4.

@alena1108
$ kubectl get node node00.alexseymour.com -o json
{
    "apiVersion": "v1",
    "kind": "Node",
    "metadata": {
        "annotations": {
            "flannel.alpha.coreos.com/backend-data": "{\"VtepMAC\":\"e6:d2:2c:12:0e:5a\"}",
            "flannel.alpha.coreos.com/backend-type": "vxlan",
            "flannel.alpha.coreos.com/kube-subnet-manager": "true",
            "flannel.alpha.coreos.com/public-ip": "<IP_ADDRESS>",
            "node.alpha.kubernetes.io/ttl": "0",
            "rke.cattle.io/external-ip": "node00.alexseymour.com",
            "rke.cattle.io/internal-ip": "node00.alexseymour.com",
            "volumes.kubernetes.io/controller-managed-attach-detach": "true"
        },
        "creationTimestamp": "2019-09-23T07:47:19Z",
        "labels": {
            "beta.kubernetes.io/arch": "amd64",
            "beta.kubernetes.io/os": "linux",
            "kubernetes.io/arch": "amd64",
            "kubernetes.io/hostname": "node00.alexseymour.com",
            "kubernetes.io/os": "linux",
            "node-role.kubernetes.io/controlplane": "true",
            "node-role.kubernetes.io/etcd": "true",
            "node-role.kubernetes.io/worker": "true"
        },
        "name": "node00.alexseymour.com",
        "resourceVersion": "2711",
        "selfLink": "/api/v1/nodes/node00.alexseymour.com",
        "uid": "5ef04b4a-ddd6-11e9-8634-bede9c943c2a"
    },
    "spec": {
        "podCIDR": "<IP_ADDRESS>/24"
    },
    "status": {
        "addresses": [
            {
                "address": "<IP_ADDRESS>",
                "type": "InternalIP"
            },
            {
                "address": "node00.alexseymour.com",
                "type": "Hostname"
            }
        ],
        "allocatable": {
            "cpu": "2",
            "ephemeral-storage": "74761043435",
            "hugepages-1Gi": "0",
            "hugepages-2Mi": "0",
            "memory": "3943916Ki",
            "pods": "110"
        },
        "capacity": {
            "cpu": "2",
            "ephemeral-storage": "81120924Ki",
            "hugepages-1Gi": "0",
            "hugepages-2Mi": "0",
            "memory": "4046316Ki",
            "pods": "110"
        },
        "conditions": [
            {
                "lastHeartbeatTime": "2019-09-23T07:50:19Z",
                "lastTransitionTime": "2019-09-23T07:47:19Z",
                "message": "kubelet has sufficient memory available",
                "reason": "KubeletHasSufficientMemory",
                "status": "False",
                "type": "MemoryPressure"
            },
            {
                "lastHeartbeatTime": "2019-09-23T07:50:19Z",
                "lastTransitionTime": "2019-09-23T07:47:19Z",
                "message": "kubelet has no disk pressure",
                "reason": "KubeletHasNoDiskPressure",
                "status": "False",
                "type": "DiskPressure"
            },
            {
                "lastHeartbeatTime": "2019-09-23T07:50:19Z",
                "lastTransitionTime": "2019-09-23T07:47:19Z",
                "message": "kubelet has sufficient PID available",
                "reason": "KubeletHasSufficientPID",
                "status": "False",
                "type": "PIDPressure"
            },
            {
                "lastHeartbeatTime": "2019-09-23T07:50:19Z",
                "lastTransitionTime": "2019-09-23T07:47:49Z",
                "message": "kubelet is posting ready status",
                "reason": "KubeletReady",
                "status": "True",
                "type": "Ready"
            }
        ],
        "daemonEndpoints": {
            "kubeletEndpoint": {
                "Port": 10250
            }
        },
        "images": [
            {
                "names": [
                    "rancher/hyperkube@sha256:0fc3e30f679ed144cb99262fea0357334844e4eb14f673a4257026115eba81a2",
                    "rancher/hyperkube:v1.14.5-rancher1"
                ],
                "sizeBytes":<PHONE_NUMBER>
            },
            {
                "names": [
                    "rancher/nginx-ingress-controller@sha256:5a60a68777ed1aa5472b987d1f085a653ada50056b7e6a43d22361973a24f2c0",
                    "rancher/nginx-ingress-controller:0.21.0-rancher3"
                ],
                "sizeBytes": 568544147
            },
            {
                "names": [
                    "rancher/rancher@sha256:2351fcc560585f5d236ef5f758a2ad6dafa95279381dcac01b91455ee6a6ea8b",
                    "rancher/rancher:v2.2.7"
                ],
                "sizeBytes": 473735479
            },
            {
                "names": [
                    "rancher/rancher-agent@sha256:fe9f7981b7ef1f585ec1ad7cb0dcc90da0f8c81d098f15abfca2bbfcda492213",
                    "rancher/rancher-agent:v2.2.7"
                ],
                "sizeBytes": 280450684
            },
            {
                "names": [
                    "rancher/rke-tools@sha256:d48bf7d13461694a5d2a8aefea48b9276368e67431e935420d1565844d495077",
                    "rancher/rke-tools:v0.1.40"
                ],
                "sizeBytes": 130122333
            },
            {
                "names": [
                    "rancher/calico-node@sha256:2f46157483904649f334da83e6b5e522bf20cbd3ea6ec9f43456673933021d5a",
                    "rancher/calico-node:v3.4.0"
                ],
                "sizeBytes": 75919845
            },
            {
                "names": [
                    "rancher/calico-cni@sha256:b3f4045680586133039f1e77f3ebb4bb5e6c60fa85f184f395eee32303462715",
                    "rancher/calico-cni:v3.4.0"
                ],
                "sizeBytes": 75434816
            },
            {
                "names": [
                    "quay.io/jetstack/cert-manager-controller@sha256:958074178ed595cd6733ecf07b746e520bddae10c6264c70cb8b07ecb0083311",
                    "quay.io/jetstack/cert-manager-controller:v0.5.2"
                ],
                "sizeBytes": 47280337
            },
            {
                "names": [
                    "rancher/coreos-flannel@sha256:57f85f0bb7360f2dd378d74ffc01ac99a4c152ad463455ff429867c6879f4386",
                    "rancher/coreos-flannel:v0.10.0"
                ],
                "sizeBytes": 44598861
            },
            {
                "names": [
                    "rancher/coredns-coredns@sha256:638adb0319813f2479ba3642bbe37136db8cf363b48fb3eb7dc8db634d8d5a5b",
                    "rancher/coredns-coredns:1.3.1"
                ],
                "sizeBytes": 40303560
            },
            {
                "names": [
                    "rancher/coreos-etcd@sha256:b2100f7b0dbd592e6e81689ac607055ed80f0bdbde7e29d24b4decf4cca63ea9",
                    "rancher/coreos-etcd:v3.3.10-rancher1"
                ],
                "sizeBytes": 39468433
            },
            {
                "names": [
                    "rancher/pause@sha256:d22591b61e9c2b52aecbf07106d5db313c4f178e404d660b32517b18fcbf0144",
                    "rancher/pause:3.1"
                ],
                "sizeBytes": 742472
            }
        ],
        "nodeInfo": {
            "architecture": "amd64",
            "bootID": "85f123c6-707d-4474-99b5-c3ab7b00fe45",
            "containerRuntimeVersion": "docker://18.9.9",
            "kernelVersion": "4.4.0-164-generic",
            "kubeProxyVersion": "v1.14.5",
            "kubeletVersion": "v1.14.5",
            "machineID": "311936e2303b034fe7ef70182235b8cb",
            "operatingSystem": "linux",
            "osImage": "Ubuntu 16.04.6 LTS",
            "systemUUID": "62368578-A16B-4AE0-BE9E-5952516FAB2D"
        }
    }
}

This issue has been fixed in v2.3.0 with https://github.com/rancher/rancher/pull/22287; corresponding issue https://github.com/rancher/rancher/issues/19208.
Closing as a duplicate.


Next week?

Hey! I can see that the sensor attribute have both this week's menu and next week.
But the card only show me this week. Is it possible to make it show next week as well?

Hi, yes sure, it could be added as a config setting for the card. I'll consider it when I get into the code next time

Thank you! But thanks for the work you do!


appmanager refactoring and test

adding changes
adding grpc-promise depencendy to the storage module
JDOC reviewing
Adding some changes in ctl
appmanager refactoring and test

This PR was closed because it got refactored in the PR #77


ui: azd should handle terminal resize

On a laptop screen + VSCode, the terminal resizes often. This can lead to bad spinner rendering where each render is now printed as a line output:

We should handle terminal resize in azd. This is as simple as listening for SIGWINCH on linux and polling on windows. Other CLIs already handle this so there's prior art if needed.

Remember @vhvb1989 did fix the re-sizing?

#2017 did start handling terminal width with truncation, but we didn't make it responsive yet.
The next set of changes (I'm currently experimenting with) is to react to terminal width changes (polling on windows, syscall signal on unix). It won't catch all spinner renders (may be multiple lines printed before the size response kicks in), but this aligns with other popular clis like docker is doing.

Some suggestions for this:

Make the polling-for-ux-changes an azd-config setting
Make the polling interval configurable.

This would allow folks to opt-in to this and adjust the speed based on their needs.

For unix, SIGWINCH already exists. No polling needed.
For windows, polling is the only option. We should only expose if users ask. This is largely an implementation detail that users care about. The idea is to make the terminal usable.
I have a non-thread-safe PoC working with these changes.


Support Examples Menu

fixes https://github.com/lfortran/lcompilers_frontend/issues/59

Beautiful, that's exactly what what I was imagining. Thanks!


Add vimagit extension to display current mode

What do you use to make screencast? I can't find a good asciinema converter...

Upload image

I am not entirely satisfied by the screenshot as it is not the same width as the other ones.

thanks


Bump framework version

$Subject
Related PR

https://github.com/wso2/carbon-identity-framework/pull/6210

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12371371281


UndefVarError: head not defined in the documentation

While following the example of the reduction of β Pictoris in the documentation, in the section about the contrast curve I ran into the error
julia> head(filter(row -> isfinite(row.contrast_corr), cc))
ERROR: UndefVarError: head not defined
Stacktrace:
 [1] top-level scope
   @ REPL[41]:1

This is my environment:
(tmp) pkg> status
Status `/tmp/Project.toml`
  [904a6c7d] ADI v0.5.2
  [3b1b4be9] CFITSIO v1.0.0
  [a93c6f00] DataFrames v0.22.0
  [1893dc6a] HCIDatasets v0.2.0
  [b6cd55e5] HCIToolbox v0.4.2
  [91a5bcdd] Plots v1.9.1

Seems like a compat issue with DataFrames. Thanks for pointing it out.

Probably related to change of API of DataFrames:
julia> plot(
           cc_empty[:distance],
           [cc_empty[:contrast_corr] cc_empty[:contrast]],
           yscale=:log10,
           xlim=(0, NaN),
           label=["Student-t" "Gaussian"],
           ylabel="5-sigma contrast",
           xlabel="radius [px]"
       )
ERROR: MethodError: no method matching getindex(::DataFrame, ::Symbol)
Closest candidates are:
  getindex(::AbstractDataFrame, ::CartesianIndex{2}) at /home/mose/.julia/packages/DataFrames/X0xNW/src/other/broadcasting.jl:3
  getindex(::AbstractDataFrame, ::Integer, ::Colon) at /home/mose/.julia/packages/DataFrames/X0xNW/src/dataframerow/dataframerow.jl:210
  getindex(::AbstractDataFrame, ::Integer, ::Union{Colon, Regex, AbstractVector{T} where T, All, Between, Cols, InvertedIndex}) at /home/mose/.julia/packages/DataFrames/X0xNW/src/dataframerow/dataframerow.jl:208
  ...
Stacktrace:
 [1] top-level scope
   @ REPL[55]:1

I think you need
cc_empty[:, :distance],
[cc_empty[:, :contrast_corr] cc_empty[:, :contrast]],

Should be fixed on master, now. Docs updates will propagate to https://juliahci.github.io/ADI.jl/dev/ as soon as actions catches up.

I can confirm the new version of the documentation fixed the issue, thanks!


Composer fails on dependency

composer fails with below message

ceejayoz/laravel-phumbor dev-master requires 99designs/phumbor ^1.2 -> no matching package found.

Installation request for ceejayoz/laravel-phumbor dev-master -> satisfiable by ceejayoz/laravel-phumbor[dev-master].

+1

+1

@frozonfreak @skhro87 @chongeu At this point this package isn't maintained - I no longer use the older Laravel 4 nor Phumbor. If someone wants to take it over, let me know. I'm using https://www.imgix.com/ these days.

Here is an updated version https://github.com/beeyev/thumbor-php


KAFKA-16027: MINOR Refactor MetadataTest#testUpdatePartitionLeadership

Split MetadataTest#testUpdateParitionLeadership into two tests:
MetadataTest#testIgnoreUpdatePartitionLeadership
MetadataTest#testApplyAndIgnoreUpdatesPartitionLeadership
Each test < 100 lines, helper functions combined to about 50 lines.
Not sure if this is sufficient or if more refactoring is necessary.
Additional complications for putting this into ConsumerMetadataTest so if that is preferred some issues have to be overcome.

Hi @philipnee, thank you for the feedback! I am a newbie so the guidance is appreciated. I used a lot of the concepts from your refactor but edited some components to make it more readable. However, I have a problem with the testApplyPartialMetadataLeaderUpdate test. For some reason, the behavior is not as expected and I'm not exactly sure why. To be specific, the test fails with the following error:
org.opentest4j.AssertionFailedError: expected: <LeaderAndEpoch{leader=Optional[localhost:1971 (id: 2 rack: null)], epoch=200}> but was: <LeaderAndEpoch{leader=Optional.empty, epoch=200}>
on the assertion:
assertEquals(expectedLeaderInfo, updatedMetadata.currentLeader(tp));
It seems that partition 2 (of 2) in topic 1 is updating the metadata information when it shouldn't. Everything else seems to work fine.
I have narrowed the undesired change down to this line:
Set<TopicPartition> updatedTps = metadata.updatePartitionLeadership(updates, nodes);
which is not entirely surprising because it is the function that enacts the partition leadership update within the metadata. It is strange to me though because the intended effect is "update to partition1's leadership are to be applied, and no update to partition2(so remains at it is)." but the outcome seems to be partition 2 is affected.
I'm not sure whether I'm configuring something incorrectly, making an incorrect assumption in the setup, or if there is some other error.
Thanks for all the help!

Oh I just noticed https://github.com/apache/kafka/pull/15023
Could this be the source of the issue?
After making the change from the PR, the tests passed as expected.
Would you still want to utilize this refactor as I saw you also made some edits to MetadataTest.
If so, how would you recommend merging the code since there are conflicts?

Hey @Alexander-Aghili - Thanks making the changes. Seems like you've made some changes to the PR but the branch is a bit behind.  Would you have time to rebase the branch to trunk?

Ya sure, Ill do it at some point today.

any update here?

Okay I messed up the git a little here (still have much to learn), the current trunk does exist on my Kafka-16027 branch but I had to redo it force push which led to auto-closing this branch. Any recommendation on what do to next?

Okay I messed up the git a little here (still have much to learn), the current trunk does exist on my Kafka-16027 branch but I had to redo it force push which led to auto-closing this branch. Any recommendation on what do to next?

that is totally a bad news. Maybe you can take a look at this post (https://stackoverflow.com/questions/3973994/how-can-i-recover-from-an-erronous-git-push-f-origin-master) ?

I have the correct file still saved on my new forced update but I can't link it to this issue. I don't want to revert because I accidently pushed all the commits from the past few months as part of this one.

I have the correct file still saved on my new forced update but I can't link it to this issue. I don't want to revert because I accidently pushed all the commits from the past few months as part of this one.

maybe you can file a new PR ?

Ok will do. Ill link it here when done

I have the correct file still saved on my new forced update but I can't link it to this issue. I don't want to revert because I accidently pushed all the commits from the past few months as part of this one.

maybe you can file a new PR ?

https://github.com/apache/kafka/pull/15857
Updated PR


Pypercard behaves weirdly in the PyScript.com preview when it's included as a package dependency

Pypercard behaves weirdly in the PyScript.com preview when it's included as a package dependency
I tried to follow this documentation example: https://pypercard.readthedocs.io/en/latest/tutorial3.html#interactive-hello
However, the project fails to start running (see traceback below) in the PyScript.com preview (see screenshot below). I haven't found the exact problem, but the code crashes immediately after the App.start() method is called, regardless if I include any transitions. Also, if instead of including pypercard as a package dependency, I explicitly add a [[fetch]]-block and link the modules hosted on GitHub pages, it works.
Here is a PyScript (URL: https://9a88206f-0390-4f47-ba0f-1901ee181974.pyscriptapps.com/e983a9dc-50cc-4593-848c-25996024ba08/latest/) that shows it not working (press the view code button to see the error).
Here is the exception traceback:
Traceback (most recent call last):
  File "/home/pyodide/pyscript/_internal.py", line 104, in run_pyscript
    result = eval_code(code, globals=__main__.__dict__)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/_pyodide/_base.py", line 468, in eval_code
    .run(globals, locals)
     ^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/_pyodide/_base.py", line 310, in run
    coroutine = eval(self.code, globals, locals)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<exec>", line 36, in <module>
  File "/lib/python3.11/site-packages/pypercard/core.py", line 761, in start
    self.machine.start(card_name)
  File "/lib/python3.11/site-packages/pypercard/state_machine.py", line 181, in start
    self._enter_state(self.current_state)
  File "/lib/python3.11/site-packages/pypercard/state_machine.py", line 233, in _enter_state
    state.call_on_enter_hooks(self)
  File "/lib/python3.11/site-packages/pypercard/state_machine.py", line 265, in call_on_enter_hooks
    hook(machine)
  File "/lib/python3.11/site-packages/pypercard/core.py", line 871, in <lambda>
    on_enter=[lambda machine: self.show_card(card)],
                              ^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.11/site-packages/pypercard/core.py", line 515, in show_card
    card.show()
  File "/lib/python3.11/site-packages/pypercard/core.py", line 215, in show
    html = self.template.format(**self.app.datastore)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python3.11/site-packages/pypercard/datastore.py", line 147, in __getitem__
    return json.loads(self.store.getItem(key))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lib/python311.zip/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

And here is a screenshot:

Tested browsers (Windows):

Firefox 114.0.2 (64-bit)
Vivaldi 6.1.3035.84 (Stable channel) (64-bit)

I wondered if the iframe in the PyScript editor somehow confused Pypercard, but that didn't seem to be the case when I tried locally.
After investigating it further, I found some even weirder behaviour. I checked the URL of the iframe embedded in the PyScript.com editor and that code failed whenever I opened that URL in a browser where I was signed into PyScript.com (I tested with both my and my partner's user), and succeeded whenever I used a private window or a browser where I was not signed in.
So it's beginning to look more and more like it might be a PyScript.com problem.

We fixed a very very similar issue (if not this one). I'll try to check out, might be that we just didn't release after fixing the issue

@ntoll .. I think this has been fixed and it's only missing a new release. Can you confirm?