Unable to connect to client object.

I am beginner to linux.
https: "Connect and get the world" command described in //carla.readthedocs.io/en/latest/python_api_tutorial/ does not work.
client = carla.Client('localhost', 2000)
In the localhost part
ip a
Substitute <IP_ADDRESS> from the above command.
In the 2000 part,
lsof -i
Substitute the number from the above command (eg 43334).
Execution result,
syntax error near unexpected token (' (Because we are Japanese environment　予期しないトークン (' 周辺に構文エラーがあります　It shows)
Is it a hierarchy problem that causes the command to be executed?
/carla
/carla/PythonAPI/axamples
Both had the same result.
please tell me solution.
environment
Ubuntu18.04
UnrealEngine4.22
CARLA0.9.7
shishau

If the error you are getting is syntax error near unexpected token, then it's not a CARLA issue but probably just your Python syntax. What is the exact code you are running?

Thank you for your reply!
client = carla.Client（ '<IP_ADDRESS>'、2000)
A syntax error is returned as a result of putting the above in the CUI.
What is the code in this case?
Sorry for not knowing much.
shishau

You're almost there! The problem is the character after '<IP_ADDRESS>', which Python is expecting to be a comma but looks more like a Japanese comma in your code? Anyways, the line should be:
client = carla.Client('<IP_ADDRESS>', 2000)


Fix voters scoreboard

I was wondering if that change was intentional in the other PR...

Also fix top voters please.

https://github.com/chaosbot/Chaos/blob/master/server/static/js/chaos.js#L146

@andrewda Does the script you linked also need to be updated?

Yes. However, all of these should be working when with the new webserver.py – not sure why it isn't working.

@Swizz I am withholding my vote until the thing @andrewda pointed out gets sorted

Odd. /voters and /voters.json both work fine locally in docker. However, at chaosthebot.com  only /voters.json works.

@PlasmaPower Yea it's working in Docker for me, too. Not sure what's up with the production site...

@andrewda Did you link/copy the new nginx config chaos_uwsgi?


Arks don't resolve

https://yamz.net/term=h6295

Suggested (untested) routes that should work:
@term.route("/term=<concept_id>")
@term.route("/ark:99152/<concept_id>")
@term.route("/ark:/99152/<concept_id>")
@term.route("/ark/<concept_id>")

@term.route("/ark:/99152/<concept_id>")
@term.route("/ark:99152/<concept_id>")
@term.route("/ark/<concept_id>")
We now have these 3 in dev.
The "/term=" route might deserve additional consideration. Blueprints in Flask came after og yamz. They let url routing enforce separation of concerns (so that there doesn't have to be one monolithic views module) for the application. For this syntax, it has the side effect that /term= is a different route than /term. We would have to add a new blueprint "term=" unless someone knows a better way. If we can change the rewrite rule on n2t, it would be great. If not we'll have to do the hack. We could also conditionally apply the blueprint after parsing the URL of the main route, but that is likewise a hack.
the /ark redirect is another blueprint I will add.

That's probably fine. It may be cleaner just to forget about the old /term= route altogether. I put in the changes so that the N2T resolver should get updated by the end of Monday to select ARKs matching regex ark:/?99152/h.* and redirect them to yamz.net/<matching_string>.
I didn't know how to test it locally. For example, https://yamz-dev.yamz.link/ark:/99152/h6295 didn't work.
I couldn't get anything from yamz-dev.yamz.net. Does someone need to ask John McNamara to register it?

the route is always /term/* for the term model
so  https://yamz-dev.yamz.link/ark:/99152/h6295 won't work yet (https://yamz-dev.yamz.link/term/ark:/99152/h6295 will)
/ark is a different route that I still have to make a blueprint for.
/ark: is also a separate route but there it doesn't matter so much if we have both since nothing's hanging off of /ark yet (unlike) /term
I can point the dev server to yamz-dev.yamz.net. I only hesitate because I always manage to screw up the nginx config. I will get it done though.

Could https://yamz-dev.yamz.link/ark:/99152/h6295 be made to work (for whatever yamz instance/hostname)? That would be ideal.
If there's another URL path needed, let me know and I can have the yamz rule at N2T adjusted.

ok

Ok, https://yamz-dev.yamz.link/ark:/99152/h6295 should work.
You can add routes derived from ark (eg. /ark/something) https://github.com/metadata-research/yamz/blob/development/app/ark/views.py or let me know what they should be.

Awesome! Thank you!
Could you also make that work with no slash after the colon? That is, "/ark:/foo" should work the same as "/ark:foo". This will future-proof Yamz for the newer form ARKs.

FMI
https://werkzeug.palletsprojects.com/en/2.2.x/routing/
https://flask.palletsprojects.com/en/2.2.x/api/#flask.request

Closing this and opening a separate one for no slash after the colon  ("/ark:/foo" should work the same as "/ark:foo") because this is outside of normal url routing and has to be handled as a special case.


Prevent test folder deletion on running flutter create --empty on an existing app project

This PR modifies the flutter create --empty command to not delete the test/ folder when run on an existing app project.
Before:
flutter create my_app --empty
mkdir my_app/test
if test -d my_app/test; then echo "test exists"; else echo "test does not exist"; fi # test exists
flutter create my_app --empty
if test -d my_app/test; then echo "test exists"; else echo "test does not exist"; fi # test does not exist

After:
flutter create my_app --empty
mkdir my_app/test
if test -d my_app/test; then echo "test exists"; else echo "test does not exist"; fi # test exists
flutter create my_app --empty
if test -d my_app/test; then echo "test exists"; else echo "test does not exist"; fi # test exists

Fixes https://github.com/flutter/flutter/issues/134928
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

When not creating a new project, won't this recreate test/widget_test.dart if it doesn't exist?
Ideally, this should probably just never write a file to test at all, and skip the delete step.

When not creating a new project, won't this recreate test/widget_test.dart if it doesn't exist?

Indeed, this seems to be the case.

Ideally, this should probably just never write a file to test at all, and skip the delete step.

Agreed.

When not creating a new project, won't this recreate test/widget_test.dart if it doesn't exist?
Ideally, this should probably just never write a file to test at all, and skip the delete step.

Agreed. Will make this change.

I've modified the 'create' command so that when run with '--empty', it doesn't write to the test/ directory, for either new or existing projects.

@andrewkolos Can you re-review this now that it's been updated?


add Bloqade & its components

coming from slack would be nice if this could get merged since I already had BloqadeExpr waited 3 days...

thanks for helping with the registration! and thanks for reminding me of the Aqua tests, they are quite helpful! Indeed, I'm thinking to add Aqua afterward, despite some of our dependencies having quite serious ambiguities to be fixed, lol

Personally I often just use ambiguities=false, although maybe that's not the best...


Any plan to update to python3?

It is 2019 now, and python2 will not be maintained after 2020.
I wish we could have a code with python3
Best wishes!!

Hi, feel free to make a python3 version, which is not difficult I believe.


make generated *.c file into pyx build dir

Describe your issue
*.c is an generated intermediate file for Cython toolchain. I don't think it is good practice for user to modify it.
In my repos involved Cython source code, generated *.c is supposed to be ignored. However, there is also some user-written *.c code in the project, As a result, it make source code management difficult, I have to add the line of code to explicitly delete them after pyximport.
Moving them to pyx_build_dir would make situation a lot easier.

@scoder , is it possible?


Rahul reduce heading size

Before:

After:

Coverage remained the same at 94.466% when pulling d9acf3c312e3bbb8c501b36afb1e87776ce2a454 on rahul-reduce-heading-size into 9f8112f43bf0524bd946ed14b984e07a4554f102 on main.


Mock NTP on testground

Description
Currently tests are failing because the node is trying to reach NTP on the external internet. testground is a closed network within a docker/k8s cluster.
we need to be able to mock them to control the time the node knows. but most importantly right now testground doesn't allow external communication and it blocks us from running.

Maybe we can just disable ntp check on testground for now? I think the plan was to eventually turn it off anyway. We already have a process that will report if time is not in sync with peers.

Well, I opened the test to outgoing networking now so it'll just work with NTP. we could probably reverse this when we drop the NTP dependency. easiest solution for now..


Inability to post via webhooks

Posting messages via incoming webhooks allows for attachment only posts that are easier to format.
PR Coming to allow posting to a known URL.

Thanks.


Add FIL_ADDRESS support

As described in https://github.com/filecoin-project/saturn-l2/issues/14.
Let me know if you had another approach in mind :)

@joaosa sorry for blasting away your work, I didn't realize you were a contributor. I'll keep you in the loop next time.

@joaosa sorry for blasting away your work, I didn't realize you were a contributor. I'll keep you in the loop next time.

@guanzo no worries and thank you :)


DCOS-7859 Bug - Task Detail view errors

Fixed some javascript errors. Also the error screen wasn't being rendered, oops

Reviewer: @Poltergeist


Update README

Added link to GitHub Project on root ReadMe page
Also, this PR correctly tests the integration of Pull Panda + Pull Assigner GitHub apps integration on ChatKit project

Closing PR now will reopen with CodeBeat app Integration in sometime


pre-commit: PR111233

Link: https://github.com/llvm/llvm-project/pull/111233
Requested by: @dtcxzyw

/add-label regression,reviewed


Add --verbose or --log-level options

Probably self-explanatory:) Or if it is there, help does not mention it

Yeah we need this... Or "--debug" or whatever

@ericcurtin Is this fixed ? Can we have option to set the log level on the tool level (can be configured as a part of config) . For eg- if we configure ramalama --debug DEBUG, all the debug logs can be seen for all commands of ramalama

This is half-done, we have --debug . But we don't have log-level , but when we do implement log-level I would recommend we copy llama.cpp log levels.


Add command to upload metadata to Movey

Motivation
Add move package upload command to upload move package to Movey, modify move package build command to call Movey API to increase download count.
How to use it
Before you use the new command to upload metadata to Movey, please make sure:

your package must be on Github
the remote must be named “origin”
file $HOME/.move/credential.toml must exist, and the content should be like:

[registry]
token = "cwagbNajttYGWjKymJdn9n2nq4yOYIpT"

Note: you could use the move login command from this PR to save your Movey's api token using the CLI.
Step 1: Navigate to the folder containing your package.
Step 2: Run the following command:
move package upload
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cargo test --package move-cli --test cli_tests upload_package
cargo test --package move-cli --lib get_api_token

wrwg, awelc, damirka
Would you guys help us with rerunning Actions and review? We have already contacted Sam and Todd.

@sblackshear All issues were resolved, please check again.

Hi Sam, we have updated all 3 of our PRs(https://github.com/move-language/move/pull/226, https://github.com/move-language/move/pull/227, https://github.com/move-language/move/pull/318). Please give them another round of review.

Hi Sam, we have updated all 3 of our PRs(#226, #227, #318). Please give them another round of review.

I reassigned these to myself and will re-review shortly.

Thanks awelc, we will work on these and have them ready within today. It's Friday for us so we won't be able to response to you tomorrow.
About your uploaded package we believed you uploaded to staging instead of production.
It's here https://movey-app-staging.herokuapp.com/packages/MyFirstPackage
since we read from the move.toml file the package name won't be the same as your folder name.

I have merged #226 and, as a result, this PR now has conflicts. While resolving these, please refactor Movey configuration file access routines so that the functionality to create/read the file (for both the login command and for the upload command are in the same place).


slice

https://lodash.com/docs/4.17.15#slice

implemented by https://github.com/shogo82148/hi/pull/183


Add more development applications to Dev Home

Suggested new feature or improvement
I was setting up my new laptop for development and Dev Home is a very good application.
Please add the following applications to the list.

Postman
VS Code
Azure Data Studio
Visual Studio 2022 Community
Enable WSL and install Ubuntu distribution
Docker
Android Studio

Scenario
n/a
Additional details
Please add the following applications to the DevHome application list.

Postman
VS Code
Azure Data Studio
Visual Studio 2022 Community
Enable WSL and install Ubuntu distribution
Docker
Android Studio

Related to:

#375

Most of the packages are available in the WinGet Community source and are available via search.
We're doing work on the WinGet side to enable support for WSL in our next release targeted for the end of February. It might take a few weeks for the new version to roll out to most devices before we add WSL.


[ebpfless] Add 5 second expiry to pending connections

What does this PR do?
This PR adds a 5 second expiry to pending connections that didn't complete the handshake in time.
Motivation
Pending connections don't have a ConnectionStats object yet so the existing tracer logic won't expire them. Plus it's probably better to have a shorter timeout for pending connections (although the exact number we can decide, it will be a config later)
Describe how you validated your changes

Run the TCP processor test suite:
go test -tags=linux,linux_bpf,npm,process,test ./pkg/network/tracer/connection/ebpfless

In particular, the new test TestPendingConnExpiry should pass.
Possible Drawbacks / Trade-offs
This adds a timestamp into the connectionState structure which is effectively redundant with ConnectionStats. The reason to have it is, the ConnectionStats won't exist yet until the connection moves out of pending, so it has to be stored somewhere. But I think it would be good to refactor this in the future, will have to think about how to combine these responsibilities.
Additional Notes

/merge


shield-label-position-tolerance (post-Mapnik 2.3)

Added support for label-position-tolerance on ShieldSymbolizers per mapnik/mapnik#2087. Depends on mapnik/mapnik-reference#63.

Merged, but I think this is outdated again.


Library is not working in ios device safari browser, after authentication, broadcast service is not triggering login success

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>Framework
Description
Error Message
Security

[ ] Is this issue security related?

Regression

[ ] Did this behavior work before?
Version:

MSAL Configuration
// Provide configuration values here.
// For Azure B2C issues, please include your policies.

Reproduction steps
// Provide relevant code snippets here.
// For Azure B2C issues, please include your policies.

Expected behavior
Browsers/Environment

[ ] Chrome
[ ] Firefox
[ ] Edge
[x] Safari
[ ] IE
[ ] Other (Please add browser name here)

It is a known issue that MSAL Angular v1 will not work when third-party cookies are disabled, such as in Safari with ITP enabled. We are working on MSAL Angular v2, which will address problems caused by third-party cookie blocking in most scenarios.
Closing as duplicate of #2042

Hi ,
I am using angular 9, how & from where to get MSAL.Js 2.0 ?
can you pls guide me?
Thanks!
Babloo Kumar
On Mon, Oct 19, 2020 at 10:11 PM Jason Nutter<EMAIL_ADDRESS>wrote:

Closed #2449
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/2449
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/2449#event-3894460276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIOAAVPX3PDJOJ2WO5ZD3LSLRT5HANCNFSM4SVW3EAQ
.


Playwright executor - Screenshots are not being generated using toHaveScreenshot or toMatchSnapshot

Describe the bug
Hello!, I have been using the playwright executor and I noticed that the screenshots are not being generated using toHaveScreenshot or toMatchSnapshot. According to playwright docs (https://playwright.dev/docs/test-snapshots) "On first execution, Playwright test will generate reference screenshots". I tested it in a repo using only playwright and it worked so I'm thinking that the issue is with the nx executor.
To reproduce
Steps to reproduce the behavior:
I have this repo and screenshots are being generated on first execution

Clone this repo https://github.com/ealejandrootalvaro/playwright-repo
Follow README.md instructions

but in this other repo (using the nx executor) it doesn't work

Clone this repo https://github.com/ealejandrootalvaro/nx-repo
Follow README.md instructions

Expected behaviour
On first execution, Playwright test will generate reference screenshots
Additional context
I am willing to help in the implementation of the PR if we find that the problem is the executor, but I would need help understanding what is going on.
Thanks!

Thanks for reporting this @ealejandrootalvaro, I'll have a look and work on a fix

@ealejandrootalvaro did https://github.com/marksandspencer/nx-plugins/pull/84 help with this issue?
If not are you still keen on working on a PR?

Closing as stale Issue


Add CycleGAN

🚀 Feature
CycleGAN in PyTorch Lightning
Motivation
The authors of this paper proposed an unpaired image to image translation algorithm using the well-known GAN framework. Obtaining input-output pairs for graphics tasks like artistic stylization can be difficult since the desired output is highly complex, and typically requires artistic authoring. For many tasks, like object transfiguration (e.g., zebra <-> horse), the desired output is not even well-defined. So, this algorithm comes in very handy in such situations. Nowadays, researchers use CycleGAN even in the Compressive Sensing and BioMedical domain.
Pitch
I already ported my code of CycleGAN from PyTorch to PyTorch Lightning. I want to add this in the PyTorch Lightning Bolts repo, but I still need help from your side to check the robustness of my code. You can find the code on my repo.
Alternatives
I couldn't find CycleGAN implementation in PyTorch Lightning. So, adding it would be of great help who are just starting in GAN research or want to use PyTorch Lightning to do advanced research in the GAN domain.
Additional context
I am attaching a few results that I obtained to build some credibilty.

@Adi-iitd this seems like a good addition to the library. Feel free to create a PR for this.
I think the code needs some minor changes but overall looks good. Do you have saved weights for the model? Or loss plots? We are encouraging saved checkpoints and loss plots (and images like you posted) to be added to alongside implementations to build credibility for the correctness of code.

@ananyahjha93 Yes, I do have the loss plots as well as the pre-trained weights. Attaching the TensorBorad loss logs here, kindly let me know how to share the saved checkpoints. I will open a PR for the same.

@Adi-iitd Sorry for the delay.

Do you have saved weights for the model? Or loss plots? We are encouraging saved checkpoints and loss plots (and images like you posted) to be added to alongside implementations to build credibility for the correctness of code.

@ananyahjha93 @Borda I'd love to have this in Bolts, but I'm not aware of how to store pretrained weights in Bolts. Do we currently have guidance on this for contributors? Is it something like this?:
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/99232c32602165410779c494b6bf492c2d291a71/pl_bolts/utils/pretrained_weights.py#L5-L6

@Adi-iitd Sorry for the delay.

Do you have saved weights for the model? Or loss plots? We are encouraging saved checkpoints and loss plots (and images like you posted) to be added to alongside implementations to build credibility for the correctness of code.

@ananyahjha93 @Borda I'd love to have this in Bolts, but I'm not aware of how to store pretrained weights in Bolts. Do we currently have guidance on this for contributors? Is it something like this?:
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/99232c32602165410779c494b6bf492c2d291a71/pl_bolts/utils/pretrained_weights.py#L5-L6

yep would be nice to have, atm we have custom/manual model uploading... :rabbit:


We should have default strategies for caching

As pointed out by @MattIPv4 (https://openjs-foundation.slack.com/archives/C05TRU8PZL6/p1699990976027789) we should be explicit about caching strategies.
And we should also:

Only cache 2XX responses, and if they're get Requests (explicit cache)
Our default responses (on the constants) should have explicit headers for no-cache/no-store
5XX responses also should not have cache
We should extract many other implicit constants as mentioned https://github.com/nodejs/release-cloudflare-worker/pull/64#issuecomment-1808057972 to proper constant files

We should extract many other implicit constants ... to proper constant files

Do we want to just move the object to a constants file like this
// src/constants/r2Prefixes.ts
export function getUrlToBucketPathMap(url) {
  return {
    dist: DIST_PATH_PREFIX + (url.pathname.substring('/dist'.length) || '/'),
    download:
      DOWNLOAD_PATH_PREFIX +
      (url.pathname.substring('/download'.length) || '/'),
    docs: DOCS_PATH_PREFIX + (url.pathname.substring('/docs'.length) || '/'),
    api: API_PATH_PREFIX + (url.pathname.substring('/api'.length) || '/'),
    metrics: url.pathname.substring(1), // substring to cut off the /
  }
}

// src/util.ts
const urlToBucketPathMap = getUrlToBucketPathMap(url);
// ...
} else if (basePath in urlToBucketPathMap) {
  bucketPath = urlToBucketPathMap[basePath];
}

or can we do something like this, where we only construct the url we need rather than all of them
// src/constants/r2Prefixes.ts
export function constructDistPath(url) {
  return DIST_PATH_PREFIX + (url.pathname.substring('/dist'.length) || '/');
}
// constructDownloadPath, constructDocsPath, ...

// src/util.ts
} else {
  switch (basePath) {
    case 'dist': {
      bucketPath = constructDistPath(url)
      break;
    }
    // download, docs, ...
    default: {
      if (env.DIRECTORY_LISTING === 'restricted') {
        return undefined;
      }
      bucketPath = url.pathname.substring(1);
    }
  }
}
...

or was there something else you were thinking about?

// src/constants/r2Prefixes.ts
export function getUrlToBucketPathMap(url) {
  return {
    dist: () => `${DIST_PATH_PREFIX}{$url.pathname.substring('/dist'.length) || '/'}`,
    download: () => `${DOWNLOAD_PATH_PREFIX}${url.pathname.substring('/download'.length) || '/'}`,
    ...
  }
}

// src/util.ts
const urlToBucketPathMap = getUrlToBucketPathMap(url);
// ...
} else if (basePath in urlToBucketPathMap) {
  bucketPath = urlToBucketPathMap[basePath];
}

I think it's important to mention that we have numerous constant files and it would make sense to have similar constants grouped together (ie. assume we have multiple constants for dist related things or download/ related things, it makes sense to have all these paths and logic to be close together

Is there a reason behind why dist: () => `${DIST_PATH_PREFIX}${url.pathname.substring('/dist'.length) || '/'}`, instead of dist: DIST_PATH_PREFIX + (url.pathname.substring('/dist'.length) || '/'),?

// src/constants/r2Prefixes.ts
const BUCKET_TO_PATHNAME_MAP = {
  return {
    dist: url => `${DIST_PATH_PREFIX}${url.pathname.substring('/dist'.length) || '/'}`,
    download: url => `${DOWNLOAD_PATH_PREFIX}${url.pathname.substring('/download'.length) || '/'}`,
    ...
  }
}

// src/util.ts
const urlToBucketPathMap = getUrlToBucketPathMap(url);
// ...
} else if (basePath in urlToBucketPathMap) {
  bucketPath = BUCKET_TO_PATHNAME_MAP[basePath](url);
}

The main reasoning behind is: You don't calculate and do all these string interpolation at once...

Do we want to tell clients to locally cache HEAD requests? It's what we're doing now, but given we don't cache them on the worker's end I wanted to double check https://github.com/nodejs/release-cloudflare-worker/blob/830d72a0c9096da3fb46280fbaa7a493d5d65db4/src/handlers/strategies/serveFile.ts#L159


Split vfx image group to avoid space issues

Jobs were failing on master because they were running out of space, so I split the vfx image group into vfx1 and vfx2. I also cleaned up some azure yaml config to have less duplication and the build-images and build-packages config look a lot more similar now.
I also updated the code coverage badge urls to point to the main repo on master.
And finally I fixed a mistake when detecting the current branch in utils.py.

Thanks JF! These image builds actually only download pre-built ci package Docker images... But these actually are quite big, such as https://hub.docker.com/r/aswf/ci-package-qt/tags which is 1.3Gb !


Clarification on scope of licencing explanation

Once you assign an approval request to a user, they can respond directly from an Outlook email, a Teams adaptive card, or the Power Automate action center, if they have a Power Automate, an Office 365, or a Dynamics 365 license with built-in Power Automate capabilities. You can find a list of these Office 365 and Dynamics 365 licenses in the Microsoft Power Apps and Power Automate licensing guide.
1/ Wording is confusing: does "*with built-in Power Automate capabilities" apply to just Dynamics 365, or all the listed items (incld Office 365 AND Dynamics 365)
2/Microsoft Power Apps and Power Automate licensing guide. Suggestion to add link to :https://github.com/MicrosoftDocs/power-platform/blob/main/power-platform/admin/powerapps-flow-licensing-faq.md

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

ID: 013c76ec-927e-4fff-77f3-aed163b9ccf1
Version Independent ID: b463656a-9ea6-1cc8-8efa-fdd6d83f51bc
Content: Get started with Power Automate approvals. - Power Automate
Content Source: articles/get-started-approvals.md
Service: power-automate
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@PriyaKodukula Can you help clarify this issue?

@Fandengbo Thanks for your feedback. We've updated the document to clarify the licensing requirements. We've also added the link to the liceing FAQs. You'll see these updates publicly within the next 12 hours.


How can I push a previous location onto the history stack?

I'm trying to call history.push() to push my user back to the previous page. Of course there's history.goBack() which would take them there, but that puts them at an earlier place in their browser history, which I don't want. I want to push that previous location onto the end of the history stack, just like any other history.push(). Is there a simple way to do this?

That's not generally possible. Consider using location.state to track the previous location explicitly. You can check the React Router auth-flow example for a related implementation.

Just push them to that location. history.push(previousLocation)

Ok. Thanks for the advice. I was hoping there was something like a history.get(-1) function that could retrieve a previous location. I'm pretty inexperienced when it comes to browser history, so I assumed there would be a way to retrieve the location information on any arbitrary history item. I'll just track the previous location explicitly. Thanks for the clarification.


let filter selectors with static_options be auto-widthed

related to https://github.com/merico-dev/table/issues/412

it's more difficult than i expected


Error when using current scipy version (1.8.1)

Hello authors,
I encountered an error when growing with gradmax and using scipy version 1.8.1.
I'm pretty sure that just some function got moved.
With scipy 1.6.3 and 1.7.3 the error didn't occur, so I would recommend specifying sciypy version 1.7.3 in setupy.py.
The configuration and error are below, for reproduction.
Kind regards.
configuration:
python growneuron/cifar/main.py --output_dir=/tmp/cifar
--config=growneuron/cifar/configs/grow_round_robin.py
--config.grow_type=add_gradmax
--config.updater.start_iteration=1000
error:
File "growneuron\growneuron\growers.py", line 405, in get_growth_directions
AttributeError: module 'scipy.sparse.linalg._eigen.arpack.arpack' has no attribute 'svds'

Thanks! Updated the requirenments.
7401194


Bootstrap label view helper

Add initial version of bootstrap label view helper.

Initial version of view helper imported into sample site.

Updated to allow glyphicon before or after label text.


Add Call action

Call Action
High Level Description
Add call action and parser function.
Code

[x] Unit test 100% coverage
[x] Does your code follow the naming and code documentation guidelines?

Documentation

[x] Is your code up to date with the spec?
[x] Have you added your tests to the testing doc?

LGTM
Did we want to have the whitelist here or in controller?

In the controller. The library shouldn't do external calls


BUG: Clipper downloads cookie/data security information instead of the page.

Hi,
thank you for the clipper, works great in most cases.
However, in some instances, the clipper doesnt't download the page, but data security / cookie information text (probably a popup)..
Example
Regards

This seems to be a Readability issue. Please review troubleshooting instructions
https://help.obsidian.md/web-clipper/troubleshoot


Resolve unstructured code warnings

This PR resolves (all) warnings in the unstructured code. Most of them are -Woverloaded-virtual warnings inside the unstructured grids. This PR also passes a few buffers by reference (instead of copying) where it fits.
For details (e.g. warnings messages) see individual commits. Tested with clang-3.8.

cool beans! thanks

BTW: you're now #2 contributor on this repo. grats!

Uh, nice :-)

Uh, nice :-)


Allow scrolling by placing the cursor on status bar and scrolling without clicking

Currently we can scroll through the TouchBar by clicking and dragging along, but could it be possible to do it by placing the mouse cursor on top of it and just dragging along without having to click. I'm using an apple magic Mouse and since it can detect gestures it'll be kind of cool to be able to do it. It'll give it an actual feeling as if we were really dragging it along with out fingers in a way.

Duplicate of #31


DEI SIG Participant Recruiting

How can we encourage new people to join the SIG?
Badge?
Tools for people to distribute?

I think the answer might be micro messaging. Different message based on whom we talk to - a person who is an ally for some cause might need a different message than a person themselves affected.

Hi Team - I think we should look toward baseline engagement from member firms and get their perspective on how to best engage their communities.
I also think working on articulation of value proposition against each of our activities in very simple terms(what is in it for me as a volunteer, what is in it for the broader community) would be helpful in drumming up excitement around the opportunities we're organizing.

Totally agree @sergiobettencourt.
Does anyone know how we get hold of the details of who has signed up to the DEI SIG from our members?

Can we leverage the FINOS distribution lists and put out CTAs for this?

Hi Kaajal - I can provide the details.
We can discuss in our sync later today.
Thank you.
On Tue, Jun 4, 2024 at 06:54 KaajalAminSharma @.***>
wrote:

Where can we find the details for the distribution lists? IF anyone can
point me in the right direction I'm happy to look in to this
—
Reply to this email directly, view it on GitHub
https://github.com/finos/DEI-SIG/issues/49#issuecomment-2147233551, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BHRIF2U6AHX5Z7XQZMN66ETZFWMHLAVCNFSM6AAAAABGCEXXKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXGIZTGNJVGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Added Pocketsync, a script used for syncing the schemas of different pocketbase instances.

I added the script I said I was going to build
Here:
https://github.com/benallfree/pockethost/discussions/189#discussioncomment-5072473

Hey, thanks for the contribution!
This project appears to be a single snippet of code exporting a schema from one instance and importing it to another.
If that's all it is, I think this would be better as a gist or code sample in a readme rather than a whole project. Also, it seems there are node_modules and other unnecessary files included in the repo.
Closing this PR for now.

Hey, thanks for the tip about the node modules and other files, I'm new to contributing and didn't realise i don't need those.
Also, the project isn't complete. I am thinking about making a CLI and allowing for syncs of other entities, such as data and settings. But for now it's just the schema. I guess i'll make another pr when more of those features are done.

Hey, thanks for the tip about the node modules and other files, I'm new to contributing and didn't realise i don't need those.
Also, the project isn't complete. I am thinking about making a CLI and allowing for syncs of other entities, such as data and settings. But for now it's just the schema. I guess i'll make another pr when more of those features are done.


Emissions import error from historical

Found during regression testing in ecmps-tst.app.cloud.gov v2.0.90.
Logged in as saber_ds (Submitter) and attempted to import 2023 Q3 emissions data from historical for ORIS 6071, MS-2A, MS-2B, 2, but encountered an unspecified error.
Same issue for ORIS 6288, 2 and 2023 Q3 emissions data.
Error message does not specify the issue.

Additional error information should be in the logs.

This issues fixed in DEV environment. and also this being inadvertently handled in #5793

Blocked by #5793

Verified in dev environment. Was able to import and view 2023 Q3 emissions data for ORIS 6071, MS-2A, MS-2B, 2 and ORIS 6288, 2

Verified in the test environment. I was able to import from historical 2023 Q3 data for the following two facilities and configuration combos:

ORIS 6288, 2
ORIS 6071, MS-2A, MS-2B, 2


Add markdown support for render authors in publications

Feature Request
Is your feature request related to a problem? Please describe.
As an author, he/she may want to highlight her own name in the author list.
For example, a researcher Lily published an article with others. She want to list her publications as follows.
[1] Alice, Bob, Lily, Jack. "Sample title". sample organization. 2020.
Describe the solution you'd like
Add markdown support for the rendering of authors in publications.
Describe alternatives you've considered
I think the markdown support is enough.
Additional context
Thanks for your reading. I would be very honored if the proposal were adopted。

Now, there is only organization can be render by markdown format.

Just a note here as I was also searching for this problem
According to this forum
You can configure highlight super user to true and just use admin as the author


Send Instance health changed event when the overall status changed

Before this fix, during a deployment triggered by a restart, the old
instances of an app were killed before the new ones were healthy. This
was due to the "instance_health_changed_event" event sent too early to
the ReadinessBehavior instance (when the first health check reported to be
healthy instead of ALL health checks).
The aim of this fix is to aggregate the results of health checks and
maintain a global instance health state which is Some(true) if all health
checks of a given instances report healthy, Some(false) if all health checks
report unhealthy and Option.empty if there is at least one unreported result.
The "instance_health_changed_event" event is now sent only when there is a
transition between those 3 states.
This commit relates to those tickets: MARATHON-7609, MARATHON-2683.
Backport in branch v1.5: https://github.com/mesosphere/marathon/pull/6045

This is a really important change for us as we have apps that have several healthchecks and some of them take time to be up, especially for applications with a warming up phase.
It really cause us some troubles on some of our apps, and it would benefits to many to have this kind of sane behaviour, especially when restarting applications or upgrading applications with new versions.

Hello @alenkacz, no problem. It has been a pain in our company for the restart of apps, thus we decided to tackle it.
Regarding this PR, I simplified a bit the code on our end. I'm rebasing right now.

The rebase is done.

Do you know why it takes forever to build the new change?

@clems4ever apologies... we have it setup so that PRs require a committer to bump the build.   this prevents malicious executions... if everyone is paying attention... let me help with that

hit "proceed" button!   unicorns and gerbils released!

thank you @kensipe!

Thank you very much for the review @kensipe! This one was really critical for us since we have more and more apps deployed in our platform. I guess a lot of users will be happy to have it in the next release :).

@kensipe , I added some documentation and updated the logs.

@timcharper , nice catch! Thank you for the review.
@kensipe , I think there's an easy way to avoid the leak, I will implement it.
Regarding the benchmark, do you have a some sort of test suite you'd like me to use or should I build one from scratch?

@clems4ever see this part of the repo https://github.com/mesosphere/marathon/tree/master/benchmark if you need any help with that, ping me on slack :-)

Thank you @alenkacz , I'll have a look.

I've generated the benchmarks but not have the time to analyze yet.

Hey, I've removed the graphs since they are not really useful here. I've done some optimizations and benchmarked them. Here are the the two tests:
1/ 1000 apps having 3 versions and 3 health checks. (addHealthCheck)
2/ 10000 randomly selected updates of health check statuses in bulk (updateHealthCheckStatus)
And the results
*Without optim*

[info] # Run complete. Total time: 00:02:42
[info] Benchmark                                           Mode  Cnt  Score   Error   Units
[info] AppHealthCheckBenchmark.addHealthChecks            thrpt   20  0.606 ± 0.005  ops/ms
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses  thrpt   20  0.118 ± 0.004  ops/ms
[info] AppHealthCheckBenchmark.addHealthChecks             avgt   20  1.680 ± 0.017   ms/op
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses   avgt   20  9.708 ± 0.594   ms/op

*With optim and immutable map*

[info] # Run complete. Total time: 00:02:42
[info] Benchmark                                           Mode  Cnt  Score   Error   Units
[info] AppHealthCheckBenchmark.addHealthChecks            thrpt   20  0.590 ± 0.017  ops/ms
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses  thrpt   20  0.118 ± 0.003  ops/ms
[info] AppHealthCheckBenchmark.addHealthChecks             avgt   20  1.727 ± 0.032   ms/op
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses   avgt   20  8.528 ± 0.214   ms/op

*With optim and mutable map*

[info] # Run complete. Total time: 00:02:42
[info] Benchmark                                           Mode  Cnt  Score   Error   Units
[info] AppHealthCheckBenchmark.addHealthChecks            thrpt   20  0.738 ± 0.019  ops/ms
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses  thrpt   20  0.143 ± 0.027  ops/ms
[info] AppHealthCheckBenchmark.addHealthChecks             avgt   20  1.285 ± 0.009   ms/op
[info] AppHealthCheckBenchmark.updateHealthCheckStatuses   avgt   20  4.985 ± 0.118   ms/op

Here is my configuration:  8 core CPU and 32GB of RAM
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 94
Model name:            Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz
Stepping:              3
CPU MHz:               3600.000
CPU max MHz:           4000,0000
CPU min MHz:           800,0000
BogoMIPS:              7200.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              8192K
NUMA node0 CPU(s):     0-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
And 2 slots of RAM with the following specs:
Handle 0x000A, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0009
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 16384 MB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: Not Specified
Type: DDR4
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2400 MHz
Manufacturer:<PHONE_NUMBER>2C
Serial Number: E8391463
Asset Tag: 04171700
Part Number: KYXC0V-MIB
Rank: 2
Configured Clock Speed: 2133 MHz
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.2 V

Can someone tell me why the tests end red at head since I cannot check the logs?

Hey @clems4ever , I'll get the tests running today and will investigate this, sorry for the delay! It has taken me a while to go through all of my notifications.

We are still getting used to the new pull request authorization system, we missed the error message. I have kicked off the build again.

Jenkins cannot run the tests because the following file conflicts:

src/main/scala/mesosphere/marathon/core/health/impl/MarathonHealthCheckManager.scala

I will try and watch more carefully. Feel free to flag us in the Marathon community slack channel if we miss the build approval notification.

I rebased the PR after the last commit.

I've added more documentation as suggested.

Awesome! Thank you very much @alenkacz , @timcharper and @kensipe .

Just waiting for a second reviewer to approve, then we can merge.

back from vacation... quick scan of changes looks great!   I will make time to review today.


 Seriously. I've created another Apple ID to see if this solves the error 65 I was having and yes it did, but I'm facing ANOTHER error.
Exit code: 1
"Attempting to write a readonly database".
I have my iPad connected to the Mac, I have updated Xcode, I've changed the Bundle Identifier, I've changed the developer account, I installed brew and all the dependencies Fugu14 needs, I gave Xcode all privileges to compile it using Python, I installed latest version of Python.
Everything you can imagine I've could done, I did.

Apple revoked 2 of my main Apple IDs for 7 days and I can't create more App IDs, so you can imagine the level of madness I'm right now.
Any help is appreciated.

what's your issue? and why are you compiling fugu14 through Xcode? that's the old way of doing it now.

No issue now. Jailbreaking with Altstore is broken in some devices as stated by Linus. Already jailbroke with source code Fugu14 and flawlessly good.  Prove it: launch Fruit Ninja 2. It will panic before you can even reach the first level of the gameplay. We are tracking this issue on the pwn2ownd Undecimus GitHub.


Relayer should query the ethereum contract for the latest processed Substrate block

in a future PR the relayer should query the eth contract for the latest parachain block that has been processed and then resume the substrate listener from that block so that it can catch up even if it crashes and falls behind.

Obsolete


SVG with embeded jpg/png not rendered in png export

Description
Inspired by  https://github.com/typst/typst/pull/1729#issuecomment-1647935742, I notice that typst disble default features for resvg. Therefore SVG with embeded jpg/png will not get rendered in png export. Note that the pdf export works fine.
Desired behavior:

PNG export behavior:

Reproduction URL
https://typst.app/project/r7PeXxeBvdW4JfhPt2HVrd
Operating system
Web app, Windows, Linux, macOS
Typst version

[X] I am using the latest version of Typst

I don't the exact reason why default features are disabled. However if we want to fix this we can simply enable these features.

@LaurenzV that's sounds like something for the SVG guru 🙏

I don't know the exact reason why default features are disabled. I just find this behavior interesting but i don't know if whether the current behavior is intended or not. However if we want to fix this we can simply enable these features.

Not sure why either, it did work before, my guess is that it was accidentally changed while refactoring the crate structure. I created a PR.


Specify external jar file as a dependency for fuzzer

Hi, instead of importing a library from maven for fuzzing, I wanted to import a locally-downloaded jar file containing the library to be fuzzed on the classpath. Is that possible to do so by tweaking the rules in jazzer/examples/BUILD.bazel?
As an example, let's say I had this as the original build rule for the fuzz target.
java_fuzz_target_test(
    name = "GifImageParserFuzzer",
    srcs = [
        "src/main/java/com/example/GifImageParserFuzzer.java",
    ],
    target_class = "com.example.GifImageParserFuzzer",
    deps = [
        "@maven//:org_apache_commons_commons_imaging",
    ],
)

How can I update the deps to not retrieve the imaging library from maven but instead use my own local copy of the library as a jar file instead?
Alternatively is there someway for me to alter the below command to include my custom library on the classpath? I tried adding -- --cp=/path/to/custom/jar/file --target_class=com.example.GifImageParserFuzzer at the end of the below command but it did not work as expected.
./bazelisk-linux-amd64 run //examples:GifImageParserFuzzer -- --cp=/path/to/custom/jar/file --target_class=com.example.GifImageParserFuzzer

[UPDATE] I was able to finally fuzz my own custom library by using the jazzer binary and including the custom library on the classpath like so (as referred to here ) .
./jazzer --cp=fuzz_target.jar:custom_library.jar --target_class=com.example.MyFuzzTarget

@prashast What you mention in your update is exactly how you should use Jazzer (although there is also a Docker image in case that is more convenient). The java_fuzz_target_test Bazel macro is something we use to verify examples don't break in Jazzer's CI - it is not meant to be used for more than toy examples. If you want to use Jazzer in Bazel, proper integration is available over at rules_fuzzing.

Thanks for clarifying the intended usage. :)


Only allocate one Slot per Entrypoint

Generated VTables already do this, this was an oversight in the "normal" generation

Closing, as not using VTables isn't generally supported right now anyways.


Home, Exhibitions, Events - Research & Audit

Conduct a review of "best in class" competitor websites within the museum/attraction/events landscape.
Review experiences through a set of user goals:

I am a new visitor, I want to understand what they do
I am near venue and planning a visit in near future
I live far away and planning a visit one day
I am familiar with x and want to see what is new

Other considerations:

Mobile and responsive experience
Editorial content
Past event content
Any on-site content/features

Prepare a series of recommendations based on findings that will be used to kick off collaborative creative work with core team and key stakeholders.

Some helpful articles around visitors of museum websites:
http://www.intk.com/en/ideas/visitor-motivation-in-online-museum-audiences
http://marty.cci.fsu.edu/preprints/marty_mmc_2008.pdf
http://mw2015.museumsandtheweb.com/paper/assessing-the-user-experience-ux-of-online-museum-collections-perspectives-from-design-and-museum-professionals/
https://blog.optimalworkshop.com/understanding-museums-digital-audience

@tomi quite a nice load of stuff from the Guggenheim.
http://exhibitions.guggenheim.org/burri/home

@Norvard Is this still a WIP or is it OK to close?

@jennpb close away :)


Real mode and ImageBatch node

Hi,
I'm getting error running ImageBatch in real mode. It's fine in the virtual mode.
from comfy_script.runtime.real import *
load()
from comfy_script.runtime.real.nodes import *

im, mask = LoadImage('test.png')

with Workflow():
    ImageBatch(im, im)

Traceback (most recent call last):
  File "/home/ro/test.py", line 9, in <module>
    ImageBatch(im, im)
  File "/home/ro/ComfyUI/custom_nodes/ComfyScript/src/comfy_script/runtime/real/nodes.py", line 132, in new
    outputs = getattr(obj, obj.FUNCTION)(*args, **kwds)
  File "/home/ro/ComfyUI/nodes.py", line 1658, in batch
    s = torch.cat((image1, image2), dim=0)
TypeError: Multiple dispatch failed for 'torch.cat'; all __torch_function__ handlers returned NotImplemented:

  - tensor subclass <class 'comfy_script.runtime.real.nodes.RealNodeOutputWrapper'>

For more information, try re-running with TORCH_LOGS=not_implemented

Fixed. Please run git pull to update.

Great, thanks!


fixing handles to work

Coverage decreased (-0.24%) to 62.34% when pulling 8d453708708cac1e064f7cfb2694229e5a1b5928 on lukasoppermann:fix-handles into 55a9261b1faf96fb186fbbc93f1f62cd08ece770 on voidberg:master.

Coverage decreased (-0.24%) to 62.34% when pulling cfa26d2a6deeda1e6d0a0bd118956f11933c1b3d on lukasoppermann:fix-handles into 55a9261b1faf96fb186fbbc93f1f62cd08ece770 on voidberg:master.


feat: update redirect to feed page for unauthenticated users

Description
This PR updates the redirect from homepage to /feed when a user is not authenticated

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Closes #1461

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@OgDev-01 the e2e tests may need updating also


After panel update (.84?), themes no longer applied to hassio panel pages

Themes are working everywhere except for the hassio menu.

Same here.
I got this in logs when accessing Hassio panel
2018-02-01 11:45:06 INFO (MainThread) [homeassistant.components.http] Serving /api/hassio/app-es5/hassio-app.html to <IP_ADDRESS> (auth: False)
2018-02-01 11:45:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=system_log, service=write, service_data=logger=frontend.js.latest.201801300, message=https://<IP_ADDRESS>:8123/frontend_latest/panels/ha-panel-hassio-ad7aa9a6055f74475fd3ba2c00bfe512.html:1:829 Uncaught TypeError: Cannot read property ‘setProperties’ of null, service_call_id=1964707344-56>
2018-02-01 11:45:14 ERROR (MainThread) [frontend.js.latest.201801300] https://<IP_ADDRESS>:8123/frontend_latest/panels/ha-panel-hassio-ad7aa9a6055f74475fd3ba2c00bfe512.html:1:829 Uncaught TypeError: Cannot read property ‘setProperties’ of null
2018-02-01 11:45:14 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1964707344-56>

@ekt- that's different problem and might be already fixed in 0.62.1...
both issues should be reported to the polymer repo btw

i'm on 0.62.1
is the PR #860 included or after the 0.62.1 release?

I'm missing something.  I don't understand how I can fix it.


bug(feature?): should allow same target.Target for different upstreams

Currently, GetStateFromContent returns a duplicate target definitions found for: ... error when different upstreams have same target.
It's not rare that different services sharing the same group of pods in Kubernetes. Such restrictions causes the kubernetes-ingress-controller stop working. Maybe we can use ${upstream.id}/${target.Target} here as the id in TargetsCollection?

Fixed in https://github.com/hbagdi/deck/commit/b6265c3a6207ead319d94cfdceba9760ffe4adaf


OpenYurt Knative Setup Issue

Describe the bug
Failed to setup Knative for OpenYurt, the cluster-local-gateway and istio-ingressgateway pod are not in READY status
- Processing resources for Istio core.
✔ Istio core installed
- Processing resources for Istiod.
- Processing resources for Istiod. Waiting for Deployment/istio-system/istiod
✔ Istiod installed
- Processing resources for Ingress gateways.
- Processing resources for Ingress gateways. Waiting for Deployment/istio-system/cluster-local-ga...
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
  Deployment/istio-system/cluster-local-gateway (containers with unready status: [istio-proxy])
  Deployment/istio-system/istio-ingressgateway (containers with unready status: [istio-proxy])
- Pruning removed resourcesError: failed to install manifests: errors occurred during operation

To Reproduce
After setting up Kubernetes cluster include cloud and edge nodes, run ./openyurt_deployer knative, following the OpenYurt setup manual.
Expected behavior
Knative should be successfully setup for OpenYurt.
Logs
kubectl get pods -n istio-system
NAME                                     READY   STATUS    RESTARTS   AGE
cluster-local-gateway-76bbc4bf78-lnjm2   0/1     Running   0          15m
istio-ingressgateway-dbcbdd6d5-lvw2q     0/1     Running   0          15m
istiod-657b54846b-5sxrq                  1/1     Running   0          15m

kubectl get svc -n istio-system
NAME                    TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                                      AGE
cluster-local-gateway   ClusterIP      <IP_ADDRESS>   <none>        15020/TCP,80/TCP,443/TCP                     20m
istio-ingressgateway    LoadBalancer   <IP_ADDRESS>      <pending>     15021:31926/TCP,80:30778/TCP,443:31594/TCP   20m
istiod                  ClusterIP      <IP_ADDRESS>    <none>        15010/TCP,15012/TCP,443/TCP,15014/TCP        20m
knative-local-gateway   ClusterIP      <IP_ADDRESS>   <none>        80/TCP                                       14m

kubectl logs cluster-local-gateway-76bbc4bf78-lnjm2 -n istio-system --tail=20
2024-03-05T08:39:30.972101Z	warn	ca	ca request failed, starting attempt 4 in 797.764779ms
2024-03-05T08:39:31.770157Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"
2024-03-05T08:39:31.912041Z	warn	ca	ca request failed, starting attempt 1 in 102.654655ms
2024-03-05T08:39:32.015484Z	warn	ca	ca request failed, starting attempt 2 in 203.884035ms
2024-03-05T08:39:32.220005Z	warn	ca	ca request failed, starting attempt 3 in 367.516646ms
2024-03-05T08:39:32.588638Z	warn	ca	ca request failed, starting attempt 4 in 846.114595ms
2024-03-05T08:39:33.434912Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"
2024-03-05T08:39:33.642198Z	warn	ca	ca request failed, starting attempt 1 in 93.76391ms
2024-03-05T08:39:33.736643Z	warn	ca	ca request failed, starting attempt 2 in 188.254413ms
2024-03-05T08:39:33.925052Z	warn	ca	ca request failed, starting attempt 3 in 430.149563ms
2024-03-05T08:39:34.355720Z	warn	ca	ca request failed, starting attempt 4 in 852.894099ms
2024-03-05T08:39:35.209024Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"
2024-03-05T08:39:35.608001Z	warn	ca	ca request failed, starting attempt 1 in 94.065982ms
2024-03-05T08:39:35.702460Z	warn	ca	ca request failed, starting attempt 2 in 193.463351ms
2024-03-05T08:39:35.896931Z	warn	ca	ca request failed, starting attempt 3 in 392.137813ms
2024-03-05T08:39:36.289533Z	warn	ca	ca request failed, starting attempt 4 in 871.494812ms
2024-03-05T08:39:37.161684Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"
2024-03-05T08:39:37.563544Z	warn	ca	ca request failed, starting attempt 1 in 91.317602ms
2024-03-05T08:39:45.811213Z	warning	envoy config	StreamAggregatedResources gRPC config stream to xds-grpc closed since 3220s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"
2024-03-05T08:40:14.606232Z	warning	envoy config	StreamAggregatedResources gRPC config stream to xds-grpc closed since 3249s ago: 14, connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:15012: i/o timeout"

kubectl logs istio-ingressgateway-dbcbdd6d5-lvw2q -n istio-system --tail=20
2024-03-05T08:39:18.676212Z	warn	ca	ca request failed, starting attempt 1 in 109.786691ms
2024-03-05T08:39:18.786619Z	warn	ca	ca request failed, starting attempt 2 in 215.392111ms
2024-03-05T08:39:19.003146Z	warn	ca	ca request failed, starting attempt 3 in 399.242009ms
2024-03-05T08:39:19.267186Z	warning	envoy config	StreamAggregatedResources gRPC config stream to xds-grpc closed since 3194s ago: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc: i/o timeout"
2024-03-05T08:39:19.402866Z	warn	ca	ca request failed, starting attempt 4 in 799.453932ms
2024-03-05T08:39:20.203095Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:34056-><IP_ADDRESS>:53: i/o timeout"
2024-03-05T08:39:20.340578Z	warn	ca	ca request failed, starting attempt 1 in 94.646846ms
2024-03-05T08:39:20.436013Z	warn	ca	ca request failed, starting attempt 2 in 219.345007ms
2024-03-05T08:39:20.656524Z	warn	ca	ca request failed, starting attempt 3 in 399.759668ms
2024-03-05T08:39:21.057245Z	warn	ca	ca request failed, starting attempt 4 in 863.372867ms
2024-03-05T08:39:21.921368Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:34056-><IP_ADDRESS>:53: i/o timeout"
2024-03-05T08:39:22.142503Z	warn	ca	ca request failed, starting attempt 1 in 94.927632ms
2024-03-05T08:39:22.237921Z	warn	ca	ca request failed, starting attempt 2 in 206.659364ms
2024-03-05T08:39:22.445396Z	warn	ca	ca request failed, starting attempt 3 in 381.600133ms
2024-03-05T08:39:22.828096Z	warn	ca	ca request failed, starting attempt 4 in 830.636367ms
2024-03-05T08:39:23.659210Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:34056-><IP_ADDRESS>:53: i/o timeout"
2024-03-05T08:39:23.966994Z	warn	ca	ca request failed, starting attempt 1 in 101.581298ms
2024-03-05T08:39:24.069457Z	warn	ca	ca request failed, starting attempt 2 in 189.259981ms
2024-03-05T08:39:24.258852Z	warn	ca	ca request failed, starting attempt 3 in 362.50633ms
2024-03-05T08:39:24.622570Z	warn	ca	ca request failed, starting attempt 4 in 873.762276ms

Notes
The configuration of nodes is as following, two nodes on cloud site, two nodes on edge sides, using image emulab-ops/UBUNTU20-64-STD
{
    "master"<EMAIL_ADDRESS>    "workers": {
        "cloud": [
<EMAIL_ADDRESS>        ],
        "edge": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>        ]
    }
}

kubectl describe pod istio-ingressgateway-dbcbdd6d5-gd9jf -n istio-system
Name:             istio-ingressgateway-dbcbdd6d5-gd9jf
Namespace:        istio-system
Priority:         0
Service Account:  istio-ingressgateway-service-account
Node:             edge-0.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us/<IP_ADDRESS>
Start Time:       Tue, 05 Mar 2024 02:16:53 -0700
Labels:           app=istio-ingressgateway
                  chart=gateways
                  heritage=Tiller
                  install.operator.istio.io/owning-resource=unknown
                  istio=ingressgateway
                  istio.io/rev=default
                  operator.istio.io/component=IngressGateways
                  pod-template-hash=dbcbdd6d5
                  release=istio
                  service.istio.io/canonical-name=istio-ingressgateway
                  service.istio.io/canonical-revision=latest
                  sidecar.istio.io/inject=false
Annotations:      cni.projectcalico.org/containerID: ad4a6fe1c266d4264a17c4c037581461abceec9904bc5253f6cbd562400aac79
                  cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                  cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                  prometheus.io/path: /stats/prometheus
                  prometheus.io/port: 15020
                  prometheus.io/scrape: true
                  sidecar.istio.io/inject: false
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/istio-ingressgateway-dbcbdd6d5
Containers:
  istio-proxy:
    Container ID:  containerd://694a4a8c920e222c07990a2762cb14669a7c05ae1507f02e108e56e8f59c456e
    Image:         docker.io/istio/proxyv2:1.16.3
    Image ID:      docker.io/istio/proxyv2@sha256:35ecc61d241242e8d68746fcccb253c4abc7d3b7671702ddb9e20b532cc514f2
    Ports:         15021/TCP, 8080/TCP, 8443/TCP, 15090/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP
    Args:
      proxy
      router
      --domain
      $(POD_NAMESPACE).svc.cluster.local
      --proxyLogLevel=warning
      --proxyComponentLogLevel=misc:error
      --log_output_level=default:info
    State:          Running
      Started:      Tue, 05 Mar 2024 02:17:00 -0700
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  1Gi
    Requests:
      cpu:      100m
      memory:   128Mi
    Readiness:  http-get http://:15021/healthz/ready delay=1s timeout=1s period=2s #success=1 #failure=30
    Environment:
      JWT_POLICY:                   first-party-jwt
      PILOT_CERT_PROVIDER:          istiod
      CA_ADDR:                      istiod.istio-system.svc:15012
      NODE_NAME:                     (v1:spec.nodeName)
      POD_NAME:                     istio-ingressgateway-dbcbdd6d5-gd9jf (v1:metadata.name)
      POD_NAMESPACE:                istio-system (v1:metadata.namespace)
      INSTANCE_IP:                   (v1:status.podIP)
      HOST_IP:                       (v1:status.hostIP)
      SERVICE_ACCOUNT:               (v1:spec.serviceAccountName)
      ISTIO_META_WORKLOAD_NAME:     istio-ingressgateway
      ISTIO_META_OWNER:             kubernetes://apis/apps/v1/namespaces/istio-system/deployments/istio-ingressgateway
      ISTIO_META_MESH_ID:           cluster.local
      TRUST_DOMAIN:                 cluster.local
      ISTIO_META_UNPRIVILEGED_POD:  true
      ISTIO_META_CLUSTER_ID:        Kubernetes
    Mounts:
      /etc/istio/config from config-volume (rw)
      /etc/istio/ingressgateway-ca-certs from ingressgateway-ca-certs (ro)
      /etc/istio/ingressgateway-certs from ingressgateway-certs (ro)
      /etc/istio/pod from podinfo (rw)
      /etc/istio/proxy from istio-envoy (rw)
      /var/lib/istio/data from istio-data (rw)
      /var/run/secrets/credential-uds from credential-socket (rw)
      /var/run/secrets/istio from istiod-ca-cert (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sggs (ro)
      /var/run/secrets/workload-spiffe-credentials from workload-certs (rw)
      /var/run/secrets/workload-spiffe-uds from workload-socket (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  workload-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  credential-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  workload-certs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istiod-ca-cert:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio-ca-root-cert
    Optional:  false
  podinfo:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.labels -> labels
      metadata.annotations -> annotations
  istio-envoy:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio
    Optional:  true
  ingressgateway-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-certs
    Optional:    true
  ingressgateway-ca-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-ca-certs
    Optional:    true
  kube-api-access-9sggs:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  9m2s                  default-scheduler  Successfully assigned istio-system/istio-ingressgateway-dbcbdd6d5-gd9jf to edge-0.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us
  Normal   Pulling    9m2s                  kubelet            Pulling image "docker.io/istio/proxyv2:1.16.3"
  Normal   Pulled     8m55s                 kubelet            Successfully pulled image "docker.io/istio/proxyv2:1.16.3" in 443.023989ms (6.245443949s including waiting)
  Normal   Created    8m55s                 kubelet            Created container istio-proxy
  Normal   Started    8m55s                 kubelet            Started container istio-proxy
  Warning  Unhealthy  4m (x152 over 8m54s)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:15021/healthz/ready": dial tcp <IP_ADDRESS>:15021: connect: connection refused

kubectl describe pod cluster-local-gateway-76bbc4bf78-xmjpv -n istio-system
Name:             cluster-local-gateway-76bbc4bf78-xmjpv
Namespace:        istio-system
Priority:         0
Service Account:  cluster-local-gateway-service-account
Node:             edge-0.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us/<IP_ADDRESS>
Start Time:       Tue, 05 Mar 2024 02:16:53 -0700
Labels:           app=cluster-local-gateway
                  chart=gateways
                  heritage=Tiller
                  install.operator.istio.io/owning-resource=unknown
                  istio=cluster-local-gateway
                  istio.io/rev=default
                  operator.istio.io/component=IngressGateways
                  pod-template-hash=76bbc4bf78
                  release=istio
                  service.istio.io/canonical-name=cluster-local-gateway
                  service.istio.io/canonical-revision=latest
                  sidecar.istio.io/inject=false
Annotations:      cni.projectcalico.org/containerID: 1b4b8a4991baa26046ca537fb6a765198453cb4e7848cc35cbec4d3a28044394
                  cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                  cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                  prometheus.io/path: /stats/prometheus
                  prometheus.io/port: 15020
                  prometheus.io/scrape: true
                  sidecar.istio.io/inject: false
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/cluster-local-gateway-76bbc4bf78
Containers:
  istio-proxy:
    Container ID:  containerd://343cad521d50edf23bfa3d741a08034082ab1962663f354f1fdd7da84b2633a7
    Image:         docker.io/istio/proxyv2:1.16.3
    Image ID:      docker.io/istio/proxyv2@sha256:35ecc61d241242e8d68746fcccb253c4abc7d3b7671702ddb9e20b532cc514f2
    Ports:         15020/TCP, 8080/TCP, 8443/TCP, 15090/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP
    Args:
      proxy
      router
      --domain
      $(POD_NAMESPACE).svc.cluster.local
      --proxyLogLevel=warning
      --proxyComponentLogLevel=misc:error
      --log_output_level=default:info
    State:          Running
      Started:      Tue, 05 Mar 2024 02:16:59 -0700
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  1Gi
    Requests:
      cpu:      100m
      memory:   128Mi
    Readiness:  http-get http://:15021/healthz/ready delay=1s timeout=1s period=2s #success=1 #failure=30
    Environment:
      JWT_POLICY:                   first-party-jwt
      PILOT_CERT_PROVIDER:          istiod
      CA_ADDR:                      istiod.istio-system.svc:15012
      NODE_NAME:                     (v1:spec.nodeName)
      POD_NAME:                     cluster-local-gateway-76bbc4bf78-xmjpv (v1:metadata.name)
      POD_NAMESPACE:                istio-system (v1:metadata.namespace)
      INSTANCE_IP:                   (v1:status.podIP)
      HOST_IP:                       (v1:status.hostIP)
      SERVICE_ACCOUNT:               (v1:spec.serviceAccountName)
      ISTIO_META_WORKLOAD_NAME:     cluster-local-gateway
      ISTIO_META_OWNER:             kubernetes://apis/apps/v1/namespaces/istio-system/deployments/cluster-local-gateway
      ISTIO_META_MESH_ID:           cluster.local
      TRUST_DOMAIN:                 cluster.local
      ISTIO_META_UNPRIVILEGED_POD:  true
      ISTIO_META_CLUSTER_ID:        Kubernetes
    Mounts:
      /etc/istio/config from config-volume (rw)
      /etc/istio/ingressgateway-ca-certs from ingressgateway-ca-certs (ro)
      /etc/istio/ingressgateway-certs from ingressgateway-certs (ro)
      /etc/istio/pod from podinfo (rw)
      /etc/istio/proxy from istio-envoy (rw)
      /var/lib/istio/data from istio-data (rw)
      /var/run/secrets/credential-uds from credential-socket (rw)
      /var/run/secrets/istio from istiod-ca-cert (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dzjnl (ro)
      /var/run/secrets/workload-spiffe-credentials from workload-certs (rw)
      /var/run/secrets/workload-spiffe-uds from workload-socket (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  workload-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  credential-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  workload-certs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istiod-ca-cert:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio-ca-root-cert
    Optional:  false
  podinfo:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.labels -> labels
      metadata.annotations -> annotations
  istio-envoy:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio
    Optional:  true
  ingressgateway-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-certs
    Optional:    true
  ingressgateway-ca-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-ingressgateway-ca-certs
    Optional:    true
  kube-api-access-dzjnl:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                      From               Message
  ----     ------     ----                     ----               -------
  Normal   Scheduled  9m21s                    default-scheduler  Successfully assigned istio-system/cluster-local-gateway-76bbc4bf78-xmjpv to edge-0.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us
  Normal   Pulling    9m21s                    kubelet            Pulling image "docker.io/istio/proxyv2:1.16.3"
  Normal   Pulled     9m15s                    kubelet            Successfully pulled image "docker.io/istio/proxyv2:1.16.3" in 5.809399086s (5.809488756s including waiting)
  Normal   Created    9m15s                    kubelet            Created container istio-proxy
  Normal   Started    9m15s                    kubelet            Started container istio-proxy
  Warning  Unhealthy  4m19s (x154 over 9m14s)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:15021/healthz/ready": dial tcp <IP_ADDRESS>:15021: connect: connection refused

kubectl describe pod istiod-657b54846b-2ncl8 -n istio-system
Name:             istiod-657b54846b-2ncl8
Namespace:        istio-system
Priority:         0
Service Account:  istiod
Node:             edge-1.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us/<IP_ADDRESS>
Start Time:       Tue, 05 Mar 2024 02:16:43 -0700
Labels:           app=istiod
                  install.operator.istio.io/owning-resource=unknown
                  istio=pilot
                  istio.io/rev=default
                  operator.istio.io/component=Pilot
                  pod-template-hash=657b54846b
                  sidecar.istio.io/inject=false
Annotations:      cni.projectcalico.org/containerID: 5cdc8c69e6be7075b384931191d7f08a742cc61928743a598e886165e56d6642
                  cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                  cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
                  prometheus.io/port: 15014
                  prometheus.io/scrape: true
                  sidecar.istio.io/inject: false
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/istiod-657b54846b
Containers:
  discovery:
    Container ID:  containerd://f1789e0fd9199390262c119cfca3a118ab2c7bb127298e07b9860a87fd958174
    Image:         docker.io/istio/pilot:1.16.3
    Image ID:      docker.io/istio/pilot@sha256:91a8907fee81051fe22d767cbca2584d1b07b475c686403395a7207d82e8f36e
    Ports:         8080/TCP, 15010/TCP, 15017/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Args:
      discovery
      --monitoringAddr=:15014
      --log_output_level=default:info
      --domain
      cluster.local
      --keepaliveMaxServerConnectionAge
      30m
    State:          Running
      Started:      Tue, 05 Mar 2024 02:16:48 -0700
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:      500m
      memory:   2Gi
    Readiness:  http-get http://:8080/ready delay=1s timeout=5s period=3s #success=1 #failure=3
    Environment:
      REVISION:                                     default
      JWT_POLICY:                                   first-party-jwt
      PILOT_CERT_PROVIDER:                          istiod
      POD_NAME:                                     istiod-657b54846b-2ncl8 (v1:metadata.name)
      POD_NAMESPACE:                                istio-system (v1:metadata.namespace)
      SERVICE_ACCOUNT:                               (v1:spec.serviceAccountName)
      KUBECONFIG:                                   /var/run/secrets/remote/config
      PILOT_TRACE_SAMPLING:                         1
      PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_OUTBOUND:  true
      PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_INBOUND:   true
      ISTIOD_ADDR:                                  istiod.istio-system.svc:15012
      PILOT_ENABLE_ANALYSIS:                        false
      CLUSTER_ID:                                   Kubernetes
    Mounts:
      /etc/cacerts from cacerts (ro)
      /var/run/secrets/istio-dns from local-certs (rw)
      /var/run/secrets/istiod/ca from istio-csr-ca-configmap (ro)
      /var/run/secrets/istiod/tls from istio-csr-dns-cert (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rvxxs (ro)
      /var/run/secrets/remote from istio-kubeconfig (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  local-certs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  <unset>
  cacerts:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cacerts
    Optional:    true
  istio-kubeconfig:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istio-kubeconfig
    Optional:    true
  istio-csr-dns-cert:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  istiod-tls
    Optional:    true
  istio-csr-ca-configmap:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio-ca-root-cert
    Optional:  true
  kube-api-access-rvxxs:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  34m                default-scheduler  Successfully assigned istio-system/istiod-657b54846b-2ncl8 to edge-1.yulin001-194981.ntu-cloud-pg0.utah.cloudlab.us
  Normal   Pulling    34m                kubelet            Pulling image "docker.io/istio/pilot:1.16.3"
  Normal   Pulled     34m                kubelet            Successfully pulled image "docker.io/istio/pilot:1.16.3" in 4.771692006s (4.771701671s including waiting)
  Normal   Created    34m                kubelet            Created container discovery
  Normal   Started    34m                kubelet            Started container discovery
  Warning  Unhealthy  34m (x2 over 34m)  kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503


run erb2haml in lib/

Hi, is there a way to get the rake tasks to lookup the erb templates in Rails.root/lib/engine-name/app/views as well?
cheers, christian

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @ReactARDev, @enobt, @jydxkj, @james600gsxr, @theebuddylee, @flamuri-dev, @Sagor2214, @alexchuvand, @pocketwalker, @Ververtom, @desfero, @Ptranscend, @theophoric, @elizachen, @yar0myr93, @ar6104ra, @haskel, @darwindu, @stefannebesnak, @vinhphuctadang, @v36u, @lsb108, @JohannesGitHub, @tejastn10, @ShaneLi, @ap501boii, @hurtadodayna, @nickmccurdy, @ravjotsandhu, @yywolf1983, @noumanmhd, @payomdraftparty, @nactran, @workwithhim, @AyushyaChitransh, @K1-R1, @DoCmAL1, @CagatayKolus, @JourneyToSilius, @NadhirBenLazhar, @Ravenclaw696, @RGHuang, @salvortore, @saranp, @tony204601, @babayevanurana, @Technoprenerd, @amirkhan7javi, @tjvsx, @WilfredTA

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @RusseII, @Nuer365, @Ifechukwudaniel, @ontofractal, @InSpirit12, @prowebdever, @fatmatto


添加文章《三步教你用Node做一个微信脱单神器，小白可上手》

Fixes # .
Make sure these boxes are checked before creating your pull request -- thank you!

[ ] Add Blog Header, including title, author, date.
e.g.

---
 layout: post
 title: "'Score Your Face Photo' a ML&Wechaty practice"
 date: 2017-09-18 09:00 +0800
 author: huyingxi
 ---

 > Author: [@huyingxi](https://github.com/huyingxi/wechaty_selfie) enjoying ML&Wechaty at BUPT

[ ] Keep all filenames & url as lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor instead of 2017-10-06-WeChat PC Impactor,
[ ] Embed the photo & video before publishing, save all external file to the blog /download/2018 directory.
[ ] Add <!--more--> section to just show the abstract in blog homepage.

See more

Thanks！


IGNITE-21032 Ensured all entries in AttributeList are Attributes

This pull request resolves issue: https://github.com/apache/ignite/issues/11045
This change ensures that all elements in a created AttributeList are Attribute instances.
https://issues.apache.org/jira/browse/IGNITE-21032

I created the following ticket https://issues.apache.org/jira/browse/IGNITE-21032 and moved it to the In Progress state. Please assign it to yourself.

@NSAmelchev @sk0x50 - Unfortunately I cannot get access to the Ignite Jira ticket in order to progress it, due to my Apache account being broken. The "password reset" link on the ASF website does not result in me being sent an e-mail, and I can't create an account with that e-mail as it is already in us. I've e-mailed the relevant addresses at ASF but I have not had any response. Until I can progress the Jira, I can't do much.

LGTM. I have run CI.
@sk0x50  Will you take a look too?

Hello @simon-greatrix @NSAmelchev ,
I merged this patch into the master branch. Thank you for your efforts!
@NSAmelchev could you please cherry-pick the patch into Ignite 2.16?


Mod Manager Change Log History not updated with latest changes

In the Mod Manager, the Change Log History doesn't show anything past <IP_ADDRESS>.  I like to read the change history and I sometimes skip updates.

Use https://github.com/SolastaMods/SolastaUnfinishedBusiness/blob/dev/SolastaUnfinishedBusiness/ChangelogHistory.txt


Use OwnerReference

https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/
ownerReference.blockOwnerDeletion=true

https://groups.google.com/forum/#!msg/kubernetes-dev/juMOsdaCml0/FwVNJA9uBAAJ

CRDs are GC-ed from 1.8. https://github.com/coreos/prometheus-operator/issues/12 . We need to see if we can remove our own GC code.
I don't think we can fully remove it since we manage Firewall rules ourselves.


Bliss os android x86_64 crash

Hello! The module installs as usual with kernelsu. But it crashes always, even after having root access. I have checked with matlog and found out that it crashes because of the exception caused by unknown source. Is it be possible to be fixed?

probably the library doesn't support x86


I2C Transfer Limit of 16384 Bytes = MSFT Limit or Bug?

Discovered during implementation of FRAM chip support and worked around with chunking read/write code. Full details in issue opened on official Microsoft IoT forum.
As there is a workaround and this chip is rarely used it just remains as a low priority item.

We got a response from MS as follows:
"There is in fact a limit of 16384 bytes. The I2C controller hardware has a theoretical limit of 64k. The reason it's limited to 16384 is because that's the largest transfer validated by the I2C controller test suite. We'll look into enabling transfers up to 64k."
Okay so the chunking design we have already is correct and the constant for 16K will move to I2cExtensions as it's a global limit. This bug will close then that change is made...

Done in commit c264287b41b0523ff350c43b5e44f1d8ed0defa4


'Active' setting not working as expected

Thanks for a superb carousel. I revisited the docs and determined that to re-set the default active slide I have to add "start: '2', ( or whatever the slide number is, counting from 0). This is not working as expected- dunno if I did something wrong. The advantage of being able to set an altered view is that the visitor likely will end up swiping in both directions and hopefully, linger longer. Thanks for any pointers about how this can be done. My settings:

Hi,
Here is a working example: http://jsbin.com/mesivoleya/edit?html,css,js,output
didn't work because you need to give the parameter start the number 2 and not the string '2'.

Thanks!


fix: added script to fetch subscriptions in graphql schema

:tada: This PR is included in version 1.30.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


KW Get Attribute Names dose not always return a list

Describe the bug
If the element just has one attribute('class' for example) , the KW Get Attribute Names does not returns a list but a string ('class').
The CODE
@{续期attr}=    Get Attribute Names    ${buttons}[0]
@{退回attr}=    Get Attribute Names    ${buttons}[1]
@{降级attr}=    Get Attribute Names    ${buttons}[2]

IF    "${权限input}" == "只读"
    List Should Not Contain Value    ${续期attr}    disabled
    List Should Not Contain Value    ${退回attr}    disabled
    List Should Contain Value    ${降级attr}    disabled
END

The LOG
${续期attr} = class
${退回attr} = class
${降级attr} = ['class', 'disabled', 'style']

Good catch, it would be bets to always return a list.
@allcontributors please add @mawentao119 for bugs

I can not reproduce the issue, Get Attribute Names returns always a list. I have vague recollection that this was not always a case and it was fixed in some release. Are you perhaps using an older versions of Browser library.
This was not actually tested and I did enhance our acceptance tests https://github.com/MarketSquare/robotframework-browser/pull/2892

Because keyword returns a list, I am going to close the issue. But if you would have an example where this is not true by using the latest version of the library, please provide more details and we can reconsider opening the issue.

I will check the library version. And then test again.
Tatu Aalto @.***> 于2023年6月25日周日 23:43写道：

Because keyword returns a list, I am going to close the issue. But if you
would have an example where this is not true by using the latest version of
the library, please provide more details and we can reconsider opening the
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/MarketSquare/robotframework-browser/issues/2890#issuecomment-1606138605,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGLCKYUHSY2VNQZVTNYEO23XNBMCFANCNFSM6AAAAAAZS5MJHU
.
You are receiving this because you were mentioned.Message ID:
@.***>

If you can reproduce the problem, can we see the html element which returns the names and how you are calling the keyword?


Refactor the building of toFontChar for non-embedded fonts

Currently there's a lot of duplicate code for non-embedded toFontChar, which this patch simplifies by extracting the code into a helper function instead.

/botio test

/botio-linux test

/botio-linux test

/botio-linux test

/botio test

r+ pending passing tests

And nice code removal!


⚠ Avatar API Endpoint has degraded performance

In b2c1859, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 4231 ms

Resolved: Avatar API Endpoint performance has improved in 823b1c2 after 22 minutes.


[Doc] Add Documentation for Extra-Requirements and Features

The deephyper installation is not clear. It must be clarified to detail the purpose of extra-requirements.

@iamyixuan started working on this in https://github.com/deephyper/deephyper/pull/171


Text fields loses state when scrolling in Flutter Gallery

Steps to Reproduce
Go to the Flutter Gallery Text Fields demo. Enter a text string on the top line. Scroll down to the bottom. Scroll up and the text is gone.
Flutter Doctor
[✓] Flutter (Channel dev, v0.2.0, on Mac OS X 10.13.2 17C88, locale en-US)
    • Flutter version 0.2.0 at /Users/vik/Projects/flutter
    • Framework revision f8ac23cd86 (10 days ago), 2018-03-05 23:27:57 +0100
    • Engine revision a00f8e8bc0
    • Dart version 2.0.0-dev.32.0.flutter-ee15c8eb68

[!] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/vik/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
    ✗ Android license status unknown.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.2, Build version 9C40b
    • ios-deploy 1.9.2
    • CocoaPods version 1.2.0

[✓] Android Studio (version 3.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio - old.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2.5)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 20.0.2
    • Dart plugin version 172.4343.25

[✓] Connected devices (1 available)
    • Viktor’s iPhone • 0f78a8bf61e64931b13636987dc7597b86ba55a7 • ios • iOS 11.2.6

! Doctor found issues in 1 category.

dup of #14104 ?