Fix goenv plugin

The original version suffers from a few bugs:

If the user defined $GOENV_ROOT, but defined it outside of $HOME/.goenv, then the script would exit without finding it.
For path-munging, the script checked for the tool in $HOME/.goenv instead of $GOENV_ROOT - This would cause the tool to not end up on the path if the $GOENV_ROOT was defined outside of $HOME
The script would path-munge $GOENV_ROOT/bin even if the binary was already on the path (say by using homebrew), causing it now to appear on the path twice, with the $GOENV_ROOT version overriding the homebrew version.

Hey. I owe you an apology. I could have used a custom plugin entry and kept up my progress locally while we discussed everything. I'm sorry.
Would you be willing to expand this to all the env plugins? Each one has minor differences, so you'll want to do some reading on each one, but they're similar enough. I think the consistency will really help. Thanks.

Before I get started, I hope I can clear the air and say I'm sorry our last exchange got so heated.
Would you please expand this to all the env plugins? As we discussed in the other PRs, the existing state is a pattern that other env plugins are using. I think you've made some great points and catches, but I'd rather not pick arbitrary places to enforce this level of scrutiny and think the consistency will really help everyone, which is the point of this project.
Each *env tool has minor differences, so you'll want to do some reading on each one, but they're similar enough.
Thanks!

Hello @cornfeedhobo ,

I hope I can clear the air and say I'm sorry our last exchange got so heated.

Thank you very much for taking the time and effort to apologize - I also hope we can clear the air.  I suspect we're going to have a lot of conversations over time as we're both active contributors who care a lot about the BASH-IT project.  But I'm also aware that we have very different view points of how to do things, and that's going to be a challenge.  I hope we can both avoid letting discussions get too heated and instead focus on keeping BASH-IT moving forward.

Would you please expand this to all the env plugins?

Two of the mantras I use as part of working to enable my teams to move fast while keeping code quality high are:

"Keep changes tight and focused"
"Minimize the size of the diff"

These mantras focus on minimizing risk and keeping change-sets singularly-focused and easy to reason about.
Trying to modify core logic of multiple plugins in one PR adds too much complexity and risk.
So, while I believe there is plenty of room for improvement across the existing *env plugins, I would not be interested in expanding this PR to encompass multiple plugins.
What I would be very interested in doing, however, is having a discussion on formalizing the expected behavior of these types of plugins (and maybe all plugins in general).
If you wanted to open an issue to discuss formalizing + back-fixing *env plugin behavior, I would absolutely participate in the discussion.
Once we reached consensus (me, you, @nwinkler, etc), we could update the documentation (ie. maybe CONTRIBUTING.md etc), identify each plugin that should be subject to the new requirements, and then open issues to discuss/address each plugin individually.
Once we get to that point, I'll be happy to pick up some of the *env plugins and open PRs to fix them.

As we discussed in the other PRs, the existing state is a pattern that other env plugins are using.

I put extra effort in this PR to ensure that it matches the spirit and patterns you established in your original PR.  I hope that comes through as you review the changes.
This PR is not focused on trying to change any patterns, but is instead focused on fixing actual bugs, the most significant being better support for users who have configured $GOENV_ROOT to point outside of $HOME/.goenv
Much of the crux of the bug stems from this line:
export GOENV_ROOT="${GOENV_ROOT:-$HOME/.goenv}"

This line's conditional-assign logic signifies that we care about the user's ability to specify the location of the root folder.
In order to fully honor the user's ability to control this value, we need to also check there for the binary before deciding to bail.
And although neither the pyenv, rbenv, or jenv plugins follow this behavior, I'm very much in support of the user's ability to control this value, so I would not advocate for removing this logic, even though it goes against the "existing pattern".
I hope this clarifies the intention of the PR, and also hope that we can get these bug-fixes merged quickly.
Thank you for your time, and please feel free to @mention me if you open an issue to discuss formalizing the *env plugin behavior.
-DF

Thanks for the good discussion on this topic. I'm with @davidpfarrell on this, let's keep the changes localized as much as possible.
Enforcing the same conventions across the whole codebase is a nice goal, but is going to be rather difficult. I'm much more in favor of fixing a current issue now than waiting for a much bigger PR (which will be more work to review)...
I'm in favor of merging this PR - how do you feel about that, @cornfeedhobo?

Unfortunately I've been peeling away too much time to respond in as much detail as I would like, so please excuse my terse reply. I've watched a few companies fall apart because of these maxims. I'm actually at a large enterprise trying to undo these habits and align development teams. It's funny that we are discussing this around the goenv plugin because Rob Pike has been a huge figure in pushing away from these maxims.
By not updating all conventions at once, you leave a path for future contributors that is confusing and more difficult to navigate. They may look at rbenv, make a new plugin, only to get a wall of text and stop there. The real cost of programming is human hours and stress, and this maxim makes that cost even higher.
I know you are senior engineers. I'm more than confident that a PR encompassing all the env plugins would be trivial to review.
P.S. personally, I kinda still want GOENV_ROOT blindly exported without checking for the tool, but I don't care enough to make a thing of it.

@nwinkler  Unfortunately I've been peeling away too much time to respond in as much detail as I would like, so please excuse my terse reply.
I've watched a few companies fall apart because of these maxims. I'm now at a large enterprise, where my position is specifically to undo these habits and align development teams. It's funny that we are discussing this around the goenv plugin because Rob Pike has been a huge figure in pushing away from these maxims. I encourage every senior engineer to watch his talks on efficiency and collaboration.
By not updating all conventions at once, you leave a path for future contributors that is confusing and more difficult to navigate. They may look at rbenv, make a new plugin, only to get a review that is a wall of text and stop there. The real cost of programming is human hours and stress, and this maxim makes that cost even higher. Look at the backlog of PRs and open Issues; the easier we can make things for the average contributor, all the better.
I know you are both senior engineers. I'm more than confident that a PR encompassing all the env plugins would be trivial to review, or you can break them up as a suite of PRs if you want clean reverts, but I still think they should be done in batch.
Personally, I still like *_ROOT blindly exported without checking for the tool, but I don't care enough to make a thing of it.
P.S. On a personal note, having my work taken and a new branch started was like a punch to the stomach. I'm trying to press forward, but it still really bugs me. I've been contributing to codebases since I was around 12. I had never had anyone take my code like that. I feel robbed and belittled. Frankly I'm not sure I want to continue if it's going to be like this going forward.

@nwinkler  Unfortunately I've been peeling away too much time to respond in as much detail as I would like, so please excuse my terse reply.
TL;DR: yeah it's fine, merge it
My real opinion: I've watched a few companies fall apart because of these maxims. I'm now at a large enterprise, where my position is specifically to undo these habits and align development teams. It's funny that we are discussing this around the goenv plugin because Rob Pike has been a huge figure in pushing away from these maxims. I encourage every senior engineer to watch his talks on efficiency and collaboration.
By not updating all conventions at once, you leave a path for future contributors that is confusing and more difficult to navigate. They may look at rbenv, make a new plugin, only to get a review that is a wall of text and stop there. The real cost of programming is human hours and stress, and this maxim makes that cost even higher. Look at the backlog of PRs and open Issues; the easier we can make things for the average contributor, all the better.
I know you are both senior engineers. I'm more than confident that a PR encompassing all the env plugins would be trivial to review, or you can break them up as a suite of PRs if you want clean reverts, but I still think they should be done in batch.

@cornfeedhobo Thanks for explanation - good thoughts.
I fully agree with you (and I think that @davidpfarrell would also agree), I'm fully in line with cleaning things up when the opportunity is there. There are a couple of things that are different here, though:
Bash-it is an open source project, it's not a company. At work, I push my teams to complete refactorings and clean-up work as part of the regular work - don't delay these things. With open source work, it's slightly different. We rely on voluntary contributions, which people mostly do in their free time. I can ask contributors to include other works in their Pull Requests, but if I push too hard, people will shy away.
Some other examples were people were asking for bigger changes are putting an open source license on Bash-it, or providing error feedback to the user in case of a missing dependency. These are all good things to have, but the fact is that these are going to be a lot of work - and the reality is that the majority of contributors don't have the time to implement a big change like that.
Both you and @davidpfarrell are some of the more active (probably the most active at the moment) contributors - I really appreciate this. This might give us an opportunity to do some bigger work if we plan carefully. I'd love to get some of this stuff done, but not sure how we want to go about it.
One option might be to create a new project here in Bash-it (https://github.com/Bash-it/bash-it/projects) for these kind of refactorings, and start listing items there (like the Pyenv plugin that you mentioned). With this, we would at least have a backlog of items to work on.
Again, I'm fully supportive of your view (and it's what I'm doing at work as well), but with an open source project, we have to take what we can get in some cases.
Please keep pushing for these things - this is great stuff, please keep it coming!

@nwinkler I'd like to return to this with a longer reply later, but I do think it's worth pointing out that this PR was created by someone that doesn't even use the tool in question. That took extra time to do. This gives me the sense that either the work is motivated out of spite, or that there is plenty of extra capacity to do things right where possible, it just needs the proper motivation.
I completely understand your point about opensource vs a company. I can't stress enough, this only came up because of the context I've laid out. I mean, A few years ago I submitted a pretty bad GOPATH parser. Took like a year to fix. No one put up any fight. Yet today we have enough capacity to have these drawn out conversations about a plugin that is doing far less. You have reached critical mass. It's time to add some rigidity for the core contributors. It's either that, or I'm left to assume that the culture is left to devolve into exactly where I see these type of "small code" mantras go: pedantic yak shaving by non-invested parties.

Thanks - that's a good summary. I'm open for suggestions on how we could make this happen. Would love to hear from both you (@cornfeedhobo) and @davidpfarrell on how could structure Bash-it work in more efficient ways.
A couple of ideas - let me know what you think:

Moving bigger undertakings (more/better documentation, cleaning up copy/paste work, refactorings) to GitHub Projects instead of handling via individual issues/PRs.
Setting up a team in GitHub with a separate discussion channel to discuss these things there instead of going through issues/comments.
We will need a better understanding about people's capacity to work on things. Not sure how we want to track that.

@nwinkler I'd like to give this some time to chew on. I'm a little stretched thin, but think you're 100% right that this project sits in a vague place where it only needs a light hand. I'd like to get this right because I am passionate about contributing to shared projects like this over maintaining my own one-off solutions. Everyone benefits, plus I can make it an easy standard to push on my teams(!!!). Although MacOS just made that a harder conversation now that they are switching to zsh as the default shell. Now I'll have devs writing non-portable scripts more and more, but I digress.
I love these ideas!

Moving bigger undertakings (more/better documentation, cleaning up copy/paste work, refactorings) to GitHub Projects instead of handling via individual issues/PRs.

Yes we should definitely do this. Everyone benefits.

Setting up a team in GitHub with a separate discussion channel to discuss these things there instead of going through issues/comments.

My initial thought is to treat it like a small startup; core contributors use email/chat to discuss. I prefer Freenode IRC because I detest email (too easy to come off mean) and it's a common standard for opensource projects. The technical barrier to entry just high enough to discourage the most time-consuming support questions.

We will need a better understanding about people's capacity to work on things. Not sure how we want to track that.

I think we could use a system of ownership and delegation. E.g. set out projects and tasks. if an issue comes up or someone volunteers, give it an owner. If they fall off the wagon and someone else takes it on, we can ping them for sign-off and review, or re-assign if it they stop replying. That might fit the project for the current state it's in? I've yet to use github projects in a serious capacity and am relating it to pivotal/jira/gus/etc. I'll try to make time to play with it more on a test repo.
I'm definitely going to keep thinking about this when I can. It feels like it's the right time.
Thanks again for starting the project and the relentless positivity!
@davidpfarrell thanks for your passion and support!

@cornfeedhobo Thanks for the kind words! One (major) clarification: I did not start Bash-it, that was @revans. I started contributing at one point and was then added to the list of owners.
I'll look into setting up some of the mentioned things - if only I had more time...


grpc-copytrade

Is it impossible to replicate and trade tokens for pumps that have not yet entered Raydium?

end


fix: Fix race condition when creating lock directory

Description
This PR makes two changes:

when --nolock is set, it will avoid creating a lock directory
when multiple instances of snakemake are running there is a race condition on the os.mkdir call. Switching to os.makedirs and setting exist_ok=True will simply avoid raising an exception in this case.

QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Removing the conditions and using os.makedirs(path, exist_ok=True) which is perfectly able to deal with concurrency is probably best.


Upgrade broccoli-string-replace dependency

to v0.1.0

Related to https://github.com/softlayer/sl-ember-components/issues/919

@notmessenger please assign to me.

It is already assigned to me

Ah OK, nvm then.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_b2b65b09-fed4-4fe6-adb2-8b0d3359a202/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_b2b65b09-fed4-4fe6-adb2-8b0d3359a202.git

Docs Build status updates of commit 5fc6202:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-05-17-44 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-05-17-44

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


style: colums and column classes to tailwind

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

Context

[ ] Closes #9191
[ ] Requires deployment <snek/rubick/worker>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[ ] I've tested it at </ksm/collection>
[x] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[ ] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Ecosystem Telegram?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

hey @iMac7 I'm going to to throw here what i've found halfway trough:
make sure to compare to canary and check mobile when replacing styles with tailwind, ty
mobile:
image
mobile:
image
mobile:
image
too close:
image
desktop:
https://github.com/kodadot/nft-gallery/assets/36627808/9157548e-b43e-4b78-9dac-7dd42d88cbff
desktop:
https://github.com/kodadot/nft-gallery/assets/36627808/1fecf527-b25a-47b9-84b3-835584ed3730
desktop:
https://github.com/kodadot/nft-gallery/assets/36627808/b23049c9-bbfe-4af4-9f54-91ad86e778ef
desktop:
https://github.com/kodadot/nft-gallery/assets/36627808/fac9c3db-b3e1-4029-af12-26f4edbe8375
desktop:
image
desktop:
image

hey @iMac7 I'm going to to throw here what i've found halfway trough: make sure to compare to canary and check mobile when replacing styles with tailwind, ty
mobile: image
mobile: image
mobile: image
too close: image
desktop: https://github.com/kodadot/nft-gallery/assets/36627808/9157548e-b43e-4b78-9dac-7dd42d88cbff
desktop: https://github.com/kodadot/nft-gallery/assets/36627808/1fecf527-b25a-47b9-84b3-835584ed3730
desktop: https://github.com/kodadot/nft-gallery/assets/36627808/b23049c9-bbfe-4af4-9f54-91ad86e778ef
desktop: https://github.com/kodadot/nft-gallery/assets/36627808/fac9c3db-b3e1-4029-af12-26f4edbe8375
desktop: image
desktop: image

wow quickly switching tabs is a great way to test especially for me working with just my laptop XD thanks for the tip

That last one (OverviewTable) requires that I have at least one row of data in the table to work with. I've not figured out how to buy or mint an nft or anything that requires money on localhost (If you know how to get test dot or ksm please share, the docs left me hanging at that point, no response on telegram yet).
Tiny differences in the Responsivetable on desktop (apparently each cell had its own padding before?). Workable but lmk if changes are needed there.
Sorry if many errors from me this needs time, coffee and the eye of a designer to get right :grinning:

That last one (OverviewTable) requires that I have at least one row of data in the table to work with. I've not figured out how to buy or mint an nft or anything that requires money on localhost (If you know how to get test dot or ksm please share, the docs left me hanging at that point, no response on telegram yet).

we lack a testnet at the moment sir, i'll test it

Sorry if many errors from me this needs time, coffee and the eye of a designer to get right 😀

haha, thank you for your work, and yup, we know, lots of small details to check

made some comments but we are almost there!

@prury for the tiny changes left that can't be easily mocked on the dev environment, maybe to be fixed later? how does this look like to merge so far?

@prury for the tiny changes left that can't be easily mocked on the dev environment, maybe to be fixed later? how does this look like to merge so far?

I think the best path is to undo tailwind modifications on the places you could not access and leave them for a follow up issue

I think the best path is to undo tailwind modifications on the places you could not access and leave them for a follow up issue

done

@iMac7 please resolve conflicts

pay 50 usd
Hopefully won't break things


Fix search by issue type

Fixes #1886.
Other fixes/changes:

Only display the "Type" menu when the user is logged-in (otherwise a search for "Assigned to you" doesn't make much sense)
Fix ambiguous column references in GetIssueStats(..)
Proper error handling for GetIssueStats(..)

Maybe some integration tests.

@lunny Added an integration test

It fails on postgresql with error pq: operator does not exist: boolean = integer

@lafriks Fixed

LGTM

LGTM

ffs LG-TM...


feat: format files and add format action

fixes #690

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

What about branches on the main repo?
${{ github.repository_owner != 'EddieHubCommunity' }}

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

What about branches on the main repo?
${{ github.repository_owner != 'EddieHubCommunity' }}

it won't format 🤔 but why do we need this?

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

What about branches on the main repo?
${{ github.repository_owner != 'EddieHubCommunity' }}

it won't format 🤔 but why do we need this?

Me as maintainer often dont create a fork rather than making a new branch in the base repo on eddiehub. But I think we can ignore this usecase

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

What about branches on the main repo?
${{ github.repository_owner != 'EddieHubCommunity' }}

it won't format 🤔 but why do we need this?

Me as maintainer often dont create a fork rather than making a new branch in the base repo on eddiehub. But I think we can ignore this usecase

A maintainer adding their own profile after becoming a maintainer? It would just format profiles btw

Note to reviewers: This is rather a smart approach to prevent permission issues, the action will only run on forks, that is where the PRs come from, do you get the point now? 😉

What about branches on the main repo?
${{ github.repository_owner != 'EddieHubCommunity' }}

it won't format 🤔 but why do we need this?

Me as maintainer often dont create a fork rather than making a new branch in the base repo on eddiehub. But I think we can ignore this usecase

A maintainer adding their own profile after becoming a maintainer? It would just format profiles btw

Oh just saw that one looking good for me


features: timer is not in the package

when running the following command for profiling
cargo build --features timer

The error appears:
Package `marlin v0.1.0 (/home/zy/Desktop/github/marlin)` does not have these features: `timer`

How to add this feature in the package? It seems that only modifying Cargo.toml is enough, but I am not familiar with rust.....

Oops, sorry! The README is outdated; the timer feature was renamed to print-trace, so the command is actually cargo build --features print-trace. However, the repo currently doesn't contain an example end-to-end binary that would print out the trace. I'll add one soon, so that you can get a sense of the heavy components.

Ok, thanks for your reply. Hope to see the end-to-end example very much !

I've fixed the README, and will soon add a small example to the repo.

Hi Pratyush, I want to double check one thing:
The test.rs in the library now is just testing a size 1 circuit for 100 times (just a*b=c each time, so matrix should be "1"). Is my understanding right?
(Also I have sent email to you about some other questions, just a short follow up to avoid being classified as spam email)

Any updates for the example?


fix .com and .org domain in  documentation

What does this PR do?
fix documentation error
Motivation
Based on https://github.com/traefik/traefik/blob/v2.11/docs/content/https/acme.md, which says
* A certificate for the domains `example.com` (main) and `*.example.org` (SAN)
  is requested:

It looks like the main domain should be example.com and the SAN should be example.org, but the included YAML files did not show that.
More

[ ] Added/updated tests
[ ] Added/updated documentation

Additional Notes
Please check if this is correct.

This fix looks correct to me.

FYI I closed/re-opened the PR to launch the CI.


Select by color

Allow selecting or expanding a selection based on colors:

foreground/text color
background/fill
border/stroke

would be super cool, could follow the node/class/id link style in place now

https://youtu.be/Q2jzq_2Spds?t=194


[FEAT] :  Design Eye-Catching Progress Bar and a Back to top button for UI Aesthetics

:red_circle: Add a progress bar and a back to top button in all the pages
:red_circle: Enhancement Aim :
:red_circle: Changes :

Enhanced Usability: A visually appealing progress bar helps users understand their progress within a task or process, and a back to top button helps users to go back to the top-part improving usability and navigation.

Improved Aesthetics: Customizing the  progress bar and the back to top button to match the UI enhances the overall look and feel of the application, making it more attractive to users.

Increased User Engagement: An engaging and cohesive interface can lead to higher user satisfaction, encouraging them to interact more with the application.

@Yash-Ainapure   Please assign this issue to me under gssoc-ext, hacktoberfest-accepted and a relevant level labels

🔴 Add a progress bar and a back to top button in all the pages 🔴 Enhancement Aim : 🔴 Changes :

Enhanced Usability: A visually appealing progress bar helps users understand their progress within a task or process, and a back to top button helps users to go back to the top-part improving usability and navigation.
Improved Aesthetics: Customizing the  progress bar and the back to top button to match the UI enhances the overall look and feel of the application, making it more attractive to users.
Increased User Engagement: An engaging and cohesive interface can lead to higher user satisfaction, encouraging them to interact more with the application.

@Yash-Ainapure Please assign this issue to me under gssoc-ext, hacktoberfest-accepted and a relevant level labels

1.Where you will add the progress bar?
2.and we don't require the back to top button.

🔴 Add a progress bar and a back to top button in all the pages 🔴 Enhancement Aim : 🔴 Changes :

Enhanced Usability: A visually appealing progress bar helps users understand their progress within a task or process, and a back to top button helps users to go back to the top-part improving usability and navigation.
Improved Aesthetics: Customizing the  progress bar and the back to top button to match the UI enhances the overall look and feel of the application, making it more attractive to users.
Increased User Engagement: An engaging and cohesive interface can lead to higher user satisfaction, encouraging them to interact more with the application.

@Yash-Ainapure Please assign this issue to me under gssoc-ext, hacktoberfest-accepted and a relevant level labels

1.Where you will add the progress bar? 2.and we don't require the back to top button.

On scroll progress bar.
Like this:

I think it won't look good as we want the website to be minimilistic .
you could contribute to other issues,thanks


Add validate append method

This PR adds the validate append method as described in #43.

Thanks for adding this @robertkossendey


feat: add basic table state behavior

Closes #485
Closes #486
Closes #487
Closes #503
Closes #562
Moves some of the existing pieces around, plus some general clean-up. Also adds in the following behaviors to DataTable:

Sorting
Expansion
Filtering

Changelog
New

src/components/DataTable
src/components/DataTable/tools
src/components/DataTable/state
src/tools/wrapComponent

Changed

Moved around components from existing DataTable

Removed

@asudoh for comments on propTypes, are these not sufficient: https://github.com/carbon-design-system/carbon-components-react/pull/562/files#diff-16b180768413647ce20626ec847d891aR25 ?

@joshblack Great that you added the propTypes comments to several components - Great if you can add ones to e.g. https://github.com/joshblack/carbon-components-react/blob/08f3e7faa63e61353543df7b363c77732c8dda1f/src/components/DataTable/TableBatchAction.js#L11, too. Thanks!

TODO:

[ ] Update example content to provide more realistic data


Gov cloud article - Change bare absolute links to use display title

Please use this template to ensure easier processing of your pull request
Category

[x] Content fix
[ ] New article

Related issues

mentioned in #752

Contents of the Pull Request
Thank you @sympmarc!  This PR has the links updated to use display title, rather than the bare ones.

Learn Build status updates of commit fa0a0af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/government-cloud.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


How to use d435i with Khadas VIM3?

How to find the device(realsense d435i) with khadas VIM3? I have found that libreasense doesn't support the ubuntu 4.9 kernel. Which version of librealsense needs to be installed？

Hi.
In the official page's supported platform list, there is no 4.9 kernel on the list.
However, I am pretty sure that 4.9 kernel is naturally supported with any librealsense version, since I also just installed normal librealsense on Khadas VIM3 and NVIDIA Jetson boards which are using 4.9 kernels.
To clarify, I installed 2.45 version when I tested with the boards.


Evaluate posibilities for Mongo Query injection

We are good with knex as we do not use any raw statements, but I would like to check how our mapper prevents this from happening.
Info:
https://nullsweep.com/a-nosql-injection-primer-with-mongo/
https://stackoverflow.com/questions/49665023/does-knex-js-prevent-sql-injection/49665379

All good in this space.
CC @ssd71


NOJIRA-0: update .gitignore for IntelliJ and Makefile for downloading go.mod dependencies

Proposed changes

Jira ticket: CLOUDP-#

Closes #[issue number]
Checklist

[ ] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation (if appropriate)
[ ] I have run make fmt and formatted my code

Further comments

Given all the time that has passed I'll close this PR, feel free to reopen it if the latests changes we did to the Makefile don't cover your use case


Update utils.js

I simply changed the way the curriculumLangs constant is extracted from availableLangs. The functionality remains unchanged, and the output will be the same as before.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


iOS build failed, cannot find IAPPromotionObserver.m

Version of react-native-iap
4.5.2, manual installation
Version of react-native
0.59.9
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
build success
Actual behavior
Build failed due to unable to find IAPPromotionObserver.m
This is because IAPPromotionObserver.m is removed in https://github.com/dooboolab/react-native-iap/pull/1039
but it is still referenced in ios/RNIap.xcodeproj/project.pbxproj
Remove that reference will fix the issue.
Tested environment (Emulator? Real Device?)
Steps to reproduce the behavior
Manually install RNIap by adding RNIap.xcodeproj to xcode and build

@howg0924 exactly so. no issue using pods

IAPPromotionObserver is removed now in iOS. Feel free to reopen if you still find the issue with the recent version which is 4.6.3.

Believe there's still an issue with 4.6.3 while adding as a Library
clang: error: no such file or directory: '/Users/mac/Sites/eventlivernnew/node_modules/react-native-iap/ios/IAPPromotionObserver.m'
clang: error: no input files

Adding as pod didn't work due to this error:
[!] Unable to find a specification for `React-Core` depended upon by `RNIap`

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

react-native is 0.59.9

Believe there's still an issue with 4.6.3 while adding as a Library
clang: error: no such file or directory: '/Users/mac/Sites/eventlivernnew/node_modules/react-native-iap/ios/IAPPromotionObserver.m'
clang: error: no input files
Adding as pod didn't work due to this error:
[!] Unable to find a specification for React-Core depended upon by RNIap
You have either:

mistyped the name or version.
not added the source repo that hosts the Podspec to your Podfile.

react-native is 0.59.9

Same issue here on react-native 0.59.10. Does it not support this version of react-native with pod install? working fine for andorid as i upgraded due to the new google billing library v3?

Same issue.
clang: error: no such file or directory: '/Users/project-name/node_modules/react-native-iap/ios/IAPPromotionObserver.m'
clang: error: no input files
react-native is 0.59.9
react-native-iap:5.2.7


Check with JSDT

JSDT has a feature request on the topic of supporting .editorconfig: https://bugs.eclipse.org/bugs/show_bug.cgi?id=463071 . You should add some comments there explaining how your plugin currently work with JSDT, and what could halp to have both projects interacting well.

I think the better mean to support any editor is to provide an extension point to apply format instead of hard coding preferences to update for each editors

I agree with the extension point approach.

As mentioned in #9, not all editorconfig settings have been implemented yet and I don't know what an editorconfig extensionpoint should look like. I think it is acceptible to add support for Javascript editors as a short-term solution. For the indentation support we just need to know the names of the settings that JSDT uses for indendation style and size.

I've looked at several projects using .editorconfig, and it really seems like the goal and common usage of of editorconfig is to attach the setting to the project.I do not think that we need to have a registry and an extension point to share those editor configs as Eclipse plugin.

common usage of of editorconfig is to attach the setting to the project.

@mickaelistria if you read section "Where are these files stored?" from http://editorconfig.org/, teh preferences is not linked to a project but to a file. I'm afraid that it's not possible today with Eclipse, since preferences belongs to a Workspace or Project.
In case of .editorconfig, the preferences of the editor, belongs to the location of the IFile and not from the IProject preferences.

Indeed, the editorconfig rules can apply to a single file, and this is not really Eclipse can support currently. Let's just be clear about that: the Eclipse IDE cannot in short-term support fully editorconfig. But let's focus on what's possible right now.
Each project has one or multiple editorconfig files. In most cases, those rules are defined by extension, and many times, it's always the same indent, the same tab/space setting for all rules in the file. So those can be used for project-wide or workspace-wide settings without too much risk. See also my suggestion on comment #23 for ideas of usage.

@angelozerr I've commented on your Eclipse JSDT issue report.
I don't see anything happening anytime soon with Eclipse to support genuine editorconfig support so I think we should add JS support directly into this plugin. I will close this and open a separate issue for adding JS support if you don't mind.

@ncjones Have you considered contributing your plugin to Eclipse?

This plugin is a hack that attempts to work around the fact that Eclipse's editor plugin architecture is fundamentally incompatible with editorconfig so I don't expect this to ever be contributed to Eclipse as it currently stands. If I, or someone else (hint), implement #7 then we will have a better idea about what it might take to get this done properly.

Contributing to Eclipse doesn't imply have it shipped and enabled by default in the IDE. But it means that other Eclipse projects can safely rely on it, and then be able to provide specific extensions.

Ok, then yes. I think that should be a goal.


Openshift is stuck with KEDA v2.7.1

This isn't a feature request but neither is an actual bug report, at least not with the operator itself.
Currently observing that Openshift instances on IBM Cloud and on AWS are pretty much stuck with KEDA v2.7.1, if operator is installed from the Hub.
On a different cluster (on-prem) we deployed KEDA using helm, it's running KEDA 2.12.1 as expected.
Perhaps some note is needed in the readme to raise awareness that Hub installation can be problematic. Message on Hub does say (Depricated) but it was working just fine until the semi-recent kubernetes upgrade on the openshift.
With a manual install one needs to be aware that KEDA version have to be matched with a proper kubernetes versions, to avoid this:
xxxxx INFO setup Running on Kubernetes 1.25 {"version": "v1.25.16+a4e782e"}
xxxxx INFO setup WARNING: KEDA 2.12.1 hasn't been tested on Kubernetes v1.25.16+a4e782e

Found the link to the mapping:
https://keda.sh/docs/2.13/operate/cluster/
edit: we used helm for the on-prem deployment, not the operator

Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift and deploy via the OLM operator, you should add the Kubernetes Community Operators repo as a catalog source, which will allow you to install the KEDA OLM operator.

fyi
Viktor Kuropiatnyk
Software Engineer ? AI4K
IBM Research GmbH
S?umerstrasse 4
8803 R?schlikon
Switzerland
From: Joel Smith @.>
Date: Tuesday, 18 June 2024 at 21:31
To: kedacore/keda-olm-operator @.>
Cc: Viktor Kuropiatnyk @.>, Author @.>
Subject: [EXTERNAL] Re: [kedacore/keda-olm-operator] Openshift is stuck with KEDA v2.7.1 (Issue #222)
Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift
Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift and deploy via the OLM operator, you should add the Kubernetes Community Operators repohttps://olm.operatorframework.io/docs/concepts/crds/catalogsource/#example---operatorhubio as a catalog source, which will allow you to install the KEDA OLM operator.
?
Reply to this email directly, view it on GitHubhttps://github.com/kedacore/keda-olm-operator/issues/222#issuecomment-2176814624, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYWG2B6LDIRTKHKWFFHJTWLZICDJHAVCNFSM6AAAAABF4U3NNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWHAYTINRSGQ.
You are receiving this because you authored the thread.Message ID: @.***>


[Idea] KubeCon NA 2024 Round Table

An idea came up on our call today about Hill Air Force Base being within driving distance to SLC KubeCon.
It might be cool to see who we can invite down to the conference and potentially have a round table discussion.
Possible topics:

Cloud Native tooling usage
Unique challenges folks face for different security environments
We have empty seats at the table, how do we fill them with folks from the public sector?

How and who do we reach out to to extend an invitation? Is this something we could potentially get some tickets issued for?
cc @idunbarh @onlydole

Howdy, @eddiezane! This is a great idea and I know we'd all enjoy seeing more engagement/interaction from folks in the public sector space 😄 I'm going to connect you both via email with the CNCF Events team so we can kickstart this conversation and figure out a plan.

Great initiative, will keep this in mind for KubeCon EU 2025 as well since I will not be attending NA this year.

Great Idea.... Count me in!!!
On Thu, Jul 11, 2024 at 5:24 PM Eddie Zaneski @.***>
wrote:

An idea came up on our call today about Hill Air Force Base being within
driving distance to SLC KubeCon.
It might be cool to see who we can invite down and potentially have a
round table discussion.
Possible topics:

Cloud Native tooling usage
Unique challenges folks face for different security environments
We have empty seats at the table, how do we fill them with folks
from the public sector?

How and who do we reach out to to exteend an invitation? Is this something
we could potentially get some tickets issued for?
cc @idunbarh https://github.com/idunbarh @onlydole
https://github.com/onlydole
—
Reply to this email directly, view it on GitHub
https://github.com/cncf/public-sector-user-group/issues/14, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMT4H3Y35QRHD3LNCHYGAITZL3ZZ7AVCNFSM6AAAAABKXYGTMSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDIMJVGI2DSMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Thanks,
Damani Corbin
917-575-8294

Have some folks from a few different groups of the 309th coming so far.

@eddiezane - this has been requested and is in the queue for KubeCon + CloudNativeCon NA in SLC 🎉 I've set you as the main point of contact and can help with anything else in the interim.

@eddiezane Is it fair to say we can close this in light of http://sched.co/1nBx4?


EXC_BAD_ACCESS on try! Realm().objects(MyModel)

When creating a Realm object and fetching within one line using try! Realm().objects(MyModel) I get an EXC_BAD_ACCESS (code=2, address=0x100...) error.
Here's the top of the output from lldb:
(lldb) bt all
Realm was compiled with optimization - stepping may behave oddly; variables may not be available.
* thread #1: tid = 0x14a0d7, 0x000000018016c8e4 libobjc.A.dylib`realizeClass(objc_class*) + 988, queue = 'com.apple.main-thread', activity = 'send control actions', stop reason = EXC_BAD_ACCESS (code=2, address=0x100132948)
    frame #0: 0x000000018016c8e4 libobjc.A.dylib`realizeClass(objc_class*) + 988
    frame #1: 0x000000018016ce90 libobjc.A.dylib`realizeAllClasses() + 88
    frame #2: 0x000000018016ed24 libobjc.A.dylib`objc_copyClassList + 40
  * frame #3: 0x0000000101511600 Realm`+[RLMSchema sharedSchema](self=RLMSchema, _cmd=<unavailable>) + 92 at RLMSchema.mm:228 [opt]
    frame #4: 0x0000000101509660 Realm`+[RLMRealm realmWithConfiguration:error:](self=RLMRealm, _cmd=<unavailable>, configuration=0x000000015d8229a0, error=domain: class name = _TtC11ProjectName18SomeViewController - code:<PHONE_NUMBER>) + 1388 at RLMRealm.mm:367 [opt]
    frame #5: 0x000000010128b910 RealmSwift`RealmSwift.Realm.__allocating_init () throws -> RealmSwift.Realm + 120 at Realm.swift:0

I also checked for the Realm Swift property cheat sheet, everything seems to be fine, I follow all requirements as far as I can see. Any ideas on how to get this fixed? This started to appear after updating to Realm 1.0.0 -- I'll try going back to an older version and report.

Which version of Xcode are you using?

I’m using Xcode 7.3 on a OS X 10.11.5 and integrated Realm-Swift via Carthage (v0.16.2).
Am 5. Juni 2016 um 19:42:20, Mark Rowe<EMAIL_ADDRESS>schrieb:
Which version of Xcode are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you please try updating to Xcode 7.3.1 when you have a chance and see if that changes anything?

@bdash I just updated to Xcode 7.3.1 (Apple didn't show any update since I "only" had 12 GB of free space which seems not to be enough for Xcode O.o) and in my first test within the simulator it worked! Thanks for the suggestion, I'll report if this happens again but for now it seems to be solved. 👍

I know this issue is closed and a solution to it was found, but I'll add my experience here just for new people who might stumble upon this.
My app was working fine, no changes made and out of nowhere it started crashing with this error. Deleting and reinstalling the app didn't fix it, but running a super clean did the trick. Be sure to try this if you have this issue or a similar one!


gotoAndPlay from javascript

Hi.
I can create calls from javascript?
for example. I have a animation with 4 keyframes. And i wanna stop animation from javascript in keyframe number two.
it is possible?

I have the latest Javascript file (1.2.3), and apparently gotoAndStop and gotoAndPlay functions are not working...

Some changes have been made in the dev branch that hasn't been merged to master, could you follow the instructions on this issue: https://github.com/cjgammon/SnapSVG-Animator/issues/86 and see if this then works.


OTLP Output Operator

Is your feature request related to a problem? Please describe.
The standalone stanza agent does not have a way to emit logs over network to an OpenTelemetry collector.
Describe the solution you'd like
Stanza should implement an OTLP output operator, which sends to an OpenTelemetry OTLP receiver.
Additional context
This will be useful in some kubernetes deployments.

Marking this done -- merged in #173


Bundles

JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing - will reopen when looking at Bundles


Warning when using dotnet restore use .shproj ?

Hello,
When using this I got a warning at build
.... warning NU1503: Skipping restore for project .... . The project file may be invalid or missing targets required for restore. [C:\dev\git\mediaclip-hub\Mediaclip.Hub.sln]

After some search I found that instead of using a .csproj, we can use .shproj and then this warning disable since the project will not be in the list of project to restore: https://github.com/NuGet/NuGet.Client/blob/b0fef98e6328948e7669297d6869fa792b39e805/src/NuGet.Core/NuGet.Build.Tasks/NuGet.targets#L269
I don't know if this change imply any unexpected change but maybe the documentation could mention it in the README  ?

Feel free to propose a documentation update, though, I don't think shproj is a very commonly used feature.


Welcome page opens in Codespaces even when workbench.startupEditor is set to "readme" in Remote settings

Does this issue occur when all extensions are disabled?: Yes

The same issue as this issue occurs in the current version of codespaces.
#134073

VS Code Version:1.69.0
x64
OS Version: OSX 10.14.6

Steps to Reproduce:

Create a Codespace from a repo containing a .devcontainer.json with "workbench.startupEditor": "readme".
Welcome page still opens within a tab, per screenshot below.

This is as-designed, unfortunately.
As we state here: https://code.visualstudio.com/docs/getstarted/settings, the readme setting value only applies to the Global Configuration. The goal is to not allow tracking via images/etc requested from the readme. Hence, this setting value cannot be set at a resource level (devcontainer settings, workspace settings, folder settings).

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!

Just realized  that this was set via remote settings. Re opening to fix an issue where we open the Get Started when we fail to find a readme.

This is fixed with https://github.com/microsoft/vscode/pull/169674


Add filtering to EMQ-Dashboard

Definition of done

Filtering by

[ ] Date range
[ ] Message type
[ ] QoS
[ ] Topic

Reference

Available analytics data

I'd like to take this one.

Updated def. of done


MapController::getPosition return LngLat with negative Longitude

Tangram-ES Version 0.4.5
MapController::getPosition and MapController::screenPositionToLngLat may return a LngLat in which (at least) the longitude is negative.
I got this above Hamburg, when having the map centered at lat=53,58220643220753, lon=9,939129168887803. Lon was -350.0608708311122 instead.
I know this is still mathematically correct, but having a coordinate whose longitude is not within the -180°..+180° bounds is certainly unexpected. If you intend to not fix this by normalizing the angle, it would be good if this were documented.

Oh, haha that's fair. It's probably more convenient for everyone if we return longitudes within (-180, 180] and say that in the documentation for the getter.

Fun fact:
My app made lon=-350.0608708311122 into lon=79,939129168887803 until I fixed this bug right now https://github.com/westnordost/osmapi/commit/16691490a7be8a187fde052d6db0b3e1f1ff316f

I should point actually not wrapping allowed had a side effect of allowing lines to be drawn across the international dateline. Since I raised a duplicate bug on the exact issue addressed here perhaps I should have added this before
See this freehand drawing example (just me drawing a random wave):
Before fix

After fix

I know this fix is better for most scenarios, but maybe some applications will want to work as before. At this point I'm still just playing with Tangram-es to see what can be done. Freehand drawing works pretty well with markers.

@ac87 thats a valid argument, maybe we can expose the API such that the user has the flexibility of getting a wrapped longitude or an unwrapped longitude (controlled by a boolean)? And by default we always return wrapped longitude.

I don't think it will be helpful to add an option for getting an explicitly "unwrapped" longitude, as this concept isn't guaranteed to be preserved if we change the implementation of world-wrapping. Lines with segments that cross 180 degrees longitude will be correctly displayed using a MapData instance, so I'd recommend using that for cases like this.

I'm not sure a drawing use case works with MapData or at least I haven't seen something dynamic enough to allow variable thickness and any color. I do appreciate the world-wrapping situation though, its currently not ideal with markers, without a jump to my location button taking you to the 'primary' world you can get lost.


HTTPD build is failed due to rsync is not install in the s2i base image

[kind/bug]

What versions of software are you using?

Operating System:

jingfus-mbp:~ jingfuwang$ uname -a
Darwin jingfus-mbp.war.can.ibm.com 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64

Output of odo version:

jingfus-mbp:~ jingfuwang$ odo version
odo v1.0.0-beta7 (785a922d)

Server: https://jing-okd-master.rtp.raleigh.ibm.com:8443
OpenShift: v3.11.0+3a34b96-217
Kubernetes: v1.11.0+d4cacc0

How did you run odo exactly?

git clone https://github.com/OpenShiftDemos/http-base
odo create httpd httpdodo
odo push

Actual behavior
Build is failed with error /opt/odo/bin/assemble-and-restart: line 24: rsync: command not found, logs with details are below
Expected behavior
Build should be successfully then deploy application to cluster
Any logs, error output, etc?
jingfus-mbp:http-base jingfuwang$ odo create httpd httpdodo
Warning: httpd is not fully supported by odo, and it is not guaranteed to work.
 ✓  Validating component [80ms]
Please use `odo push` command to create the component with source deployed
jingfus-mbp:http-base jingfuwang$ odo push
Validation
 ✓  Checking component [126ms]

Configuration changes
 ✓  Initializing component
 ✓  Creating component [395ms]

Pushing to component httpdodo of type local
 ✓  Checking files for pushing [1ms]
 ✓  Waiting for component to start [13s]
 ✓  Syncing files to the component [1s]
 ◓  Building component ✗  Unable to build files
+ set -eo pipefail
+ export ODO_UTILS_DIR=/opt/odo
+ ODO_UTILS_DIR=/opt/odo
+ export ODO_IMAGE_MAPPINGS_FILE=/opt/odo/language-scripts/image-mappings.json
+ ODO_IMAGE_MAPPINGS_FILE=/opt/odo/language-scripts/image-mappings.json
++ /opt/odo/bin/getlanguage
+ IMAGE_LANG=
+ '[' '!' -z /opt/app-root/src ']'
+ '[' /tmp '!=' /opt/app-root/src ']'
+ '[' -n /opt/app-root/src-backup ']'
+ '[' '!' -d /opt/app-root/src-backup ']'
+ mkdir -p /opt/app-root/src-backup/src
+ rsync -rlO /tmp/src/. /opt/app-root/src-backup/src/
/opt/odo/bin/assemble-and-restart: line 24: rsync: command not found

 ✗  Building component [495ms]
 ✗  command terminated with exit code 127

Hey @GeekArthur
I actually created an issue here: https://github.com/sclorg/httpd-container/issues/78 with regards to rsync not being added with httpd.
A PR was merged, which fixed base container httpd was using: https://github.com/sclorg/s2i-base-container/pull/169
Is there any way you may be using an older version of the httpd container from the service catalog? If so, could you update it and try again?

@cdrage I am not sure how to update the version of httpd container. Given we already cloned the component locally and run odo create <component type> <component name> to create the .odo, my understanding is that once we run the odo push, odo will pull the latest s2i base image then trigger the build? If that's the design I should already used the latest s2i base image but that one doesn't have rsync installed.

odo will pull the latest s2i base image then trigger the build?

odo is not pulling any s2i builder images, it uses the ImageStreams definitions that are in your OpenShift cluster in the openshift project.
To update the s2i builder image you will have to update the httpd ImageStream inside the openshfit  project.
Sadly we can't currently guaranteed that odo will work with any s2i builder image. This is why we recently started grouping images into supported, and unsupported. Supported are those that we test and we make sure that it works (currently nodejs, and java (openjdk based)), the unsupported might work, or might break, it depends how image was built.
We are currently looking for a better solution for this.
Supported images are listed at https://github.com/openshift/odo/blob/425d77670264efc502e02aed28a5665546bfefd8/pkg/catalog/catalog.go#L282-L290

@kadel Thanks for your clarification! I am new to ImageStream but I make it work. I find when I update the ImageStream I can use oc tag to let the the ImageStream points to specific builder image and I need to specify the registry.
Also another question is for official odo supported templates, the templates from here: https://docs.openshift.com/container-platform/4.2/cli_reference/openshift_developer_cli/creating-a-single-component-application-with-odo.html#examples-from-git-repositories are the templates that odo recommend to use or have better support of odo?

Seams PHP images have the same bug since rhel8/ubi8.

Also another question is for official odo supported templates, the templates from here: https://docs.openshift.com/container-platform/4.2/cli_reference/openshift_developer_cli/creating-a-single-component-application-with-odo.html#examples-from-git-repositories are the templates that odo recommend to use or have better support of odo?

Not really :-( Documentation is a little bit misleading there :-(
The templates (component types) that odo recommended to use are just nodejs and java that are based on the images listed at https://docs.openshift.com/container-platform/4.2/cli_reference/openshift_developer_cli/understanding-odo.html#odo-supported-languages-and-images
You can verify that on your cluster using odo catalog list components. You will get a list of all available images that odo see. The first group is supported images, those are supported, and we guarantee that it will work wit odo. The second group is unsupported images, those are images that should work, but we can't guarantee that as s2i builder image interface is too loose, and there might be images that are not compatible with odo.

I'm closing this issue, as currently there is not anything that we can do on odo side.
/close
@GeekArthur , if you have any additional questions we can continue the discussion here


Adding dotnet/core 🧚

Reasons for making this change:
I always need it and it is not there, that's why my contribution.
Links to documentation supporting these rule changes:
Dotnet/core
If this is a new template:
gitignore of dotnet/core

Thanks for the contribution, however per the contribution guidelines this file should be placed in the community folder. Please edit the location of the file.
https://github.com/github/gitignore#specialized-templates

Perfect, I'm going to do another pull request with the changes. 😃 🤝


Validate c context upon scratch creation

At scratch creation time, we should compile the context in isolation and ensure we get no errors. If any errors come up, tell the user and don't create the scratch.

I disagree with this now, actually. They should be able to submit bogus context, and now that we show errors nicely, they can just fix the errors once they're looking at the scratch.


Python: GetAutomaticFirstSolutionStrategy() unusable

When wrapping:
https://github.com/google/or-tools/blob/4681581b02b0a5350e0aec8beec37a0eb62e4e84/ortools/constraint_solver/routing.h#L1531-L1535
the output is unusable:
e.g.
solstrat = routing.GetAutomaticFirstSolutionStrategy()
print(solstrat)

observed:
Swig Object of type 'operations_research::FirstSolutionStrategy::Value *' at 0x7fba34f470f0

note: Spotted by Margaux Borgmann on or-tools-discuss https://groups.google.com/g/or-tools-discuss/c/Hz708HslJhA

FirstSolutionStrategy::Value is a proto enum...
https://github.com/google/or-tools/blob/dd29e9c0ae254fb2f79383c2a89ccca26f3dc856/ortools/constraint_solver/routing_enums.proto#L24-L26

https://github.com/google/or-tools/blob/9270aa0d59910175be8df9d7247e10b7233b4686/ortools/constraint_solver/python/pywraprouting_test.py#L734-L736
https://github.com/google/or-tools/blob/9270aa0d59910175be8df9d7247e10b7233b4686/ortools/constraint_solver/python/pywraprouting_test.py#L765-L767


Calculated field Error "hydra:description": "Notice: Undefined index: request_uri",

I have a custom operation with a custom controller action
  resource.ecopoint.item_operation.custom_get:
    class:   "Dunglas\ApiBundle\Api\Operation\Operation"
    public:  false
    factory: [<EMAIL_ADDRESS>"createItemOperation" ]
    arguments:
        -<EMAIL_ADDRESS>             # Resource
        -    [ "GET", "HEAD" ]                 # Methods
        -    "/eco_points/{id}/distance/{distance}"           # Path
        -    "MapBundle:Api:findByDistance"         # Controller
        -    "api_find_by_distance"                 # Route name
        -    # Context (will be present in Hydra documentation)
             "@type":       "hydra:Operation"
             "hydra:title": "A custom operation"
             "returns":     "xmls:string"

  resource.ecopoint:
    parent:    "api.resource"
    arguments: [ %map.ecopoint.entity.class% ]
    tags:      [ { name: "api.resource" } ]
    calls:
        -      method:    "initNormalizationContext"
               arguments: [ { groups: [ "expose_to_api"] } ]
        -      method:    "initFilters"
               arguments: [ [<EMAIL_ADDRESS>],[<EMAIL_ADDRESS>] ]
        -      method:    "initItemOperations"
               arguments: [ [<EMAIL_ADDRESS>]]

In this controller action I call a repository action that returns an array of entity Ecopoint and a calculated field with a distance field, when i try to return the response with getSuccessResponse bundle returns  "Notice: Undefined index: request_uri". I dont' know how can I return serialized object without a resource for this data ( My data is an array with Ecopoint and Distance). I only want to return an array that containt on each position a ecopoint object and a calculated field distance.
class ApiController extends ResourceController
{

    public function findByDistanceAction(Request $request, $id, $distance)
    {
        $resource = $this->getResource($request);
        $object = $this->findOrThrowNotFound($resource, $id);

        //$this->get('event_dispatcher')->dispatch(Events::RETRIEVE, new DataEvent($resource, $object));

        $ecopoints = $this->getEcoPointManager()->getByDistance($object->getPoint(), $distance);
        return $this->getSuccessResponse($resource, $ecopoints);

    }

I solved, creating a Data Provider that catch the distance parameter and return filtered response

Thanks for your feedback @rbaraut. Your problem was probably related to a missing key in the serializer context. Take a look at https://github.com/dunglas/DunglasApiBundle/blob/1.x/Controller/ResourceController.php#L161


Create rawsonshomeshool.txt

@WORawSon Please provide us with:

the university official website URL, if different from the domain you are submitting
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students.

@WORawSon You might miss my previous comment. Please reply.

@WORawSon I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


feat: publish message to appropriate quueue based on the language

support for java to publish in MQ is added

now message published either in java or cpp queue based on the lang

Message is published to respected queue
now code manager publishes messages to cpp or java queue depending on the language.
cb672ea

As per job requirement of Java RCE Engine, make the lang 'java' as uppercase 'JAVA'
2ec9020


portal example does not work

[Enter feedback here]
probably from the time it was written till now, something changed a lot, but this no longer works as described.

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

ID: 939101cd-9c92-ed8f-b241-664794db8a0d
Version Independent ID: 21392fd3-c4e7-f785-a660-ebbbf88646e4
Content: Store unstructured data using Azure Cosmos DB and Functions
Content Source: articles/azure-functions/functions-integrate-store-unstructured-data-cosmosdb.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@nagendramishr
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.


Pinia store values in layout is not server side rendered

Environment

Operating System: Darwin
Node Version:     v16.17.1
Nuxt Version:     3.0.0-rc.12
Nitro Version:    0.6.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, meta, modules, image, components, build, css, postcss, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Source code
https://github.com/novicell/nuxt3-boilerplate/tree/repro/ssr-layout-hydration
Deployed version
https://repro-ssr-layout-hydration--novicell-nuxt3-boilerplate.netlify.app/
Describe the bug
Hi!
We have a general Nuxt 3 boilerplate at Novicell that we use to build various client websites.
We've encountered a problem with server side rendering things that is loaded in the layout such as navigation, footer etc.
We use useAsyncData inside our [...slug].vue for rendering CMS pages. To save requests we usually include the navigation in the response on the first page load and set it in our Pinia store which is then loaded inside the layout.
It looks like the layout is rendered before the [...slug].vue and is not hydrated during SSR until the page is loaded.
I've made a small example where I have an initial value in the store that is then updated upon fetch of the page.
SSR value

Hydrated value

I'm not sure if this is a bug or a matter of configuration, but please let us know how to solve it 😄
Additional context
No response
Logs
No response

Can you explain your solution a little bit more?
I don't call any backend for fetching data, my situation is much simpler than that...
I have an store
// part of store.ts
state: () => ({ h1Title: 'initialValue' })

and used it inside layout

{{ h1Title }}

    <nuxt-child />

Now if I change the state inside a page, the Node mismatch happens.
I tried doing it in the script setup, in and outside asyncData, both has the same result.
What can I do? (except changing the whole layout and move h1 inside pages itself)
I don't understand your solution about populating store inside middleware or something. Can you explain it a little clearer?

I would also appreciate an illustrative example of the middleware solution.

Related https://github.com/vuejs/pinia/discussions/2441

I had the same issue and adding a hydrate function in my store solved this for me: https://pinia.vuejs.org/cookbook/composables.html#SSR


efficientdet-d7 weight file

Hi,
Where I can find your trained model weight file for efficientdet-d7?
Thanks,
Ajmal

@ma-siddiqui have you found relative weights?

Sorry I can not find. Please share the link here.

https://www.kaggle.com/kerneler/starter-efficientdet-model-d8ba73bf-a/data
#159


ng-repeat not functioning if ng-init contains repeated values

Below code is not working

Looping with objects:

      {{ x }}

This works as expected. It throws an error, because ngRepeat can't handle duplicate objects, unless you exlicitly tell it how to distinguish between them (read more about it in the docs).
E.g. you could change it to ng-repeat="x in names track by $index" and it will work as expected.
--
That said, this is a general support question. In the future, please direct such question to the appropriate channels. GitHub is reserved for bug reports and feature requests.

Thanks.


Add ExcludeFromJacocoGeneratedReport annotation

Codecov Report

Merging #441 (ec64e19) into master (33f46a5) will increase coverage by 0.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #441      +/-   ##
============================================
+ Coverage     35.07%   35.24%   +0.16%
  Complexity      663      663
============================================
  Files           219      219
  Lines         11466    11413      -53
  Branches        279      279
============================================
  Hits           4022     4022
+ Misses         7182     7129      -53
  Partials        262      262

Flag
Coverage Δ

java
63.00% <ø> (+0.87%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...org/apache/rocketmq/client/java/impl/Settings.java
100.00% <ø> (+41.17%)
:arrow_up:

...mq/client/java/impl/consumer/ProcessQueueImpl.java
66.37% <ø> (+1.15%)
:arrow_up:

...mq/client/java/impl/consumer/PushConsumerImpl.java
34.48% <ø> (+1.28%)
:arrow_up:

...t/java/impl/consumer/PushSubscriptionSettings.java
76.08% <ø> (+15.74%)
:arrow_up:

...java/impl/consumer/SimpleSubscriptionSettings.java
81.25% <ø> (+19.34%)
:arrow_up:

.../client/java/impl/producer/PublishingSettings.java
57.69% <ø> (+14.83%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


all modes failed on certain bitstream

Attached test2.264 (640x480) failed on all the 3 modes. But I'm able to do muxing with this bitstream using ffmpeg:
$ ffmpeg -framerate 30 -i test2.264 -c copy test2.mp4
test2.264.zip

This stream is progressive high profile, needs to be supported in mp4_h26x_write_nal helper. Will do this at some point. Fragmentation mode + slices also currently not supported.
minimp4 still can be used in such cases, just other demuxer should be used instead of mp4_h26x_write_nal which correctly aggregates one h264 frame into sample and pass it directly to MP4E_put_sample.

Turns out it's trivial to fix. Problem was not in progressive encoding as I think at first, but access unit delimiter NALu`s which was not handled. This fixes default and sequential modes, for fragmentation there same issue as https://github.com/lieff/minimp4/issues/15 .


Add ticking, metronome, or custom sound when the timer is running

This would be nice.  In addition, a wind-up noise when start is pressed the first time.
I didn't think sounds were important, but I read those sounds serve as audio cues to boost habit creation and focus:

Winding noise -> Commit to stop procrastinating and begin work
Ticking -> Continue to work and focus, resisting distraction
Ding -> A positive feeling for a job well done, signals reward of break.

Does anyone know where to source high quality versions of these sorts of sounds that could be distributed under this apps license?

Not sure for special sounds.
But you could leave an option for each person can choose his MP3 file.
Then no license problem.
Thanks


[UPDATE] QR Pairing screen

After feedback from JP we updated all pairing screen to be cleaner and less packed.
Please verify that pairing screens match on all flows:

[ ] Onboarding
[ ] Reshare
[ ] Send
[ ] Swap

QA done.


Fix bug with ConfigDocument.setValue

Fix a bug in the setValue method in SimpleConfigDocument wherein
a rendered ConfigValue could have leading or trailing whitespace,
leading to an issue with setting a value on a ConfigDocument.

thanks!


DBeaver is unable to 'close connection' when the connection is not possible

Description
Working on different places with my laptop, connecting to all kind of db's in different environments.
Moving around with my laptop, I get a lot of popups about 'The connection attempt failed', to connections I cannot connect to (anymore), just because I'm at another client of office.
The issue is about: IF I cannot connect to the db anymore, the interface shows the 'red cross', and apparently after a restart keeps trying to connect again, failing again, with popup again.
It would be handy if I can just tell DBeaver: "disconnect" even if there is no possibility to connect (because on different network).
Note that I don't even had any editors open.
Note2: in this case it was a connection to a localhost db running in a removed container....
DBeaver Version
CE <IP_ADDRESS>405051837
Operating System
Debian Trixie
Database and driver
Mostly postgres drivers
Steps to reproduce
Create postgres db in docker container.
Create a connection to it, do some queries, close editor, close dbeaver (make sure you were connected)
Stop the container
Start dbeaver again.
I'm aware of the checkbox about 'try to reconnect', somewhere in the settings, but cannot find it anymore. 100% sure that I did tell dbeaver NOT to try to reconnect anymore...
Additional context
No response

Thank you for the ideas.

We want to add a setting that prevents DBeaver from reconnecting to a datasource after restart of DBeaver.
We want to improve the indication of different statuses, like never connected / connected / disconnected because of error.

We need to conduct a UX investigation of both of these.


Prefix not showing

Im not sure what im doing incorrectly. here is my config.yml: https://pastebin.com/RGQe6rCu
[22:45:37 INFO]: [LP] > User Info: stealth62
[22:45:37 INFO]: [LP] - UUID: 8b90ffb0-d119-4a84-884a-965e68b8d172
[22:45:37 INFO]: [LP] - Status: Offline
[22:45:37 INFO]: [LP] - Primary Group: administrator
[22:45:37 INFO]: [LP] - Counts:
[22:45:37 INFO]: [LP] -    Permissions: 9
[22:45:37 INFO]: [LP] -    Temporary Permissions: 0
[22:45:37 INFO]: [LP] -    Prefixes: 1
[22:45:37 INFO]: [LP] -    Suffixes: 0
[22:45:37 INFO]: [LP] -    Meta: 0
[22:45:37 INFO]: [LP] - Parent Groups:
[22:45:37 INFO]: [LP] -    > default
[22:45:37 INFO]: [LP] -    > administrator
[22:45:37 INFO]: [LP] -    > appeals
[22:45:37 INFO]: [LP] - Cached Data:
[22:45:37 INFO]: [LP] -    Has contextual data: false
[22:45:37 INFO]: [LP] -    Current Contexts: None
[22:45:37 INFO]: [LP] -    Current Prefix: None
[22:45:37 INFO]: [LP] -    Current Suffix: None
[22:46:02 INFO]: [LP] administrator's Prefixes
[22:46:02 INFO]: [LP] -> 1 - "[A]" (inherited from self)
[22:46:02 INFO]: [LP] -> 1 - "[O]" (inherited from fullop)
[22:46:02 INFO]: [LP] -> 0 - "[A]" (inherited from self)
[22:46:02 INFO]: [LP] -> 0 - "[O]" (inherited from fullop)
[22:46:02 INFO]: [LP] administrator has no suffixes.
[22:46:02 INFO]: [LP] administrator has no meta.
My chat plugin is EssentialsChat and i use Vault, any idea why my prefixes are not showing?http://imgur.com/SioyoqB
Using zpermissions and permissionsex i can get the prefixes to show fine

You need to update to EssentialsX.


Do not CaptureStartupErrors when running in IIS

We currently capture startup errors in Hosting when running in IIS- https://github.com/aspnet/AspNetCore/blob/3477daf3c4f530dff80f197e0642cb39a26fb07b/src/Servers/IIS/IIS/src/WebHostBuilderIISExtensions.cs#L33
We initially did this to prevent triggering rapid failure protection in IIS by crashing the worker process too often.
However, given that we now have https://github.com/aspnet/AspNetCore/pull/8518, we should stop capturing the exception in Hosting and let ANCM capture it instead. This ensures that the .NET Runtime will still log the exception message and stack trace to the event log. By capturing the exception in hosting, we prevent the runtime from logging this exception

When using the WebHost and CaptureStartupErrors(false), the process exits, we should see why that is.

@anurse or @shirhatti - i don't see any milestones on this. is it slotted for a specific preview release?

We'll cover it in triage. I don't have any specific preview planned.

Acceptance checklist (check one item)

[ ] We decided not to take this fix.
[ ] The fix is tests-only.
[x] The fix contains product changes (check all items below).

[ ] Relevant XML documentation comments for new public APIs are present.
[ ] Narrative docs (docs.microsoft.com) are updated. (check one item below)

[ ] The change requires a new article. An issue with an outline has been filed here: [ISSUE LINK]
[ ] The change requires a change to an existing article. A closed docs PR with these changes is linked here: [PR LINK]
[ ] The change requires no docs changes.

[x] Verification has been completed. (check one item below)

[x] The change is in the shared framework and was verified against the following versions

SDK installer: 3.0.100-preview6-012113
ASP.NET Core Runtime: 3.0.0-preview6-19279-01
.NET Core Runtime: 3.0.0-preview6-27728-04

[ ] The change is in an OOB NuGet/NPM/JAR package and was verified against the following version of that package: [PACKAGE ID] [VERSION]

Actually, I think we didn't do this for Out of Process: https://github.com/aspnet/AspNetCore/blob/3477daf3c4f530dff80f197e0642cb39a26fb07b/src/Servers/IIS/IISIntegration/src/WebHostBuilderIISExtensions.cs#L81. It should be a small change. @anurse cool if I squeeze this into preview6?

Yep, no prob.


Loggable Boxes: Add BoxLogging helpers.

Direct lift from the commit message:
BoxLogging provides helpers for logging boxes and then continuing to operate on
the box, alloing logging to become a fluent part of the box interaction. It
provides methods that can allow for logging empties and failures, or just
failures. It also allows logging these to different log levels, and allows for
different adapters to be applied.
For example, one could write a snippet:
  class MySnippet(id: String) extends LoggableBoxLogging {
    def render = {
      "#content" #> {
        Content.getById(id).flatMap { content =>
          content.text.asHtml // assume this returns Box[NodeSeq]
        }.infoLogEmptyBox(s"Failed to retrieve content HTML for $id")
    }
  }

When this snippet gets rendered, if the provided content lookup fails, or if
the conversion to NodeSeq fails, there will be an INFO level log that will
capture this failure with the provided message prefix.
BoxLogging provides handling for arbitrary-depth failure chains, as well as
providing logging for failure params, thus ensuring all of the information in a
failure will be logged. It also correctly passes any captured Throwable to the
logger methods, provided that the adapter handles them correctly.
Two adapters are provided out of the box: LoggableBoxLogging, which can be
mixed in as above and is based on Lift's Loggable, and SLF4JBoxLogging,
which is based on the raw SLF4J interface, and requires a protected logger
var with an SLF4J logger to be available.
Lastly, for simplicity, you can import net.liftweb.common.BoxLogging._ to have
the logging helpers available without mixing anything else into your classes.
We've been using this at @elemica with great success for a while now, so it's time
to contribute it on back to Lift. This version even grew some extra capabilities, with
the possibility of doing this logging at various log levels.
See #1856 .

This looks familiar. =)


accelerator refactor - DDP, DDPSpawn, DDP2 plugins

What does this PR do?
Part of #5616, copy ddp plugins
There are some TODO comments, these will be addressed when we integrate and write additional tests
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[ ] Check that target branch and milestone match!

Did you have fun?
Make sure you had fun coding 🙃

Hello @awaelchli! Thanks for updating this PR.

In the file pytorch_lightning/accelerators/accelerator.py:

Line 365:26: W292 no newline at end of file

In the file pytorch_lightning/plugins/base_plugin.py:

Line 44:14: W292 no newline at end of file

Hello @awaelchli! Thanks for updating this PR.

In the file pytorch_lightning/accelerators/accelerator.py:

Line 365:26: W292 no newline at end of file

In the file pytorch_lightning/plugins/base_plugin.py:

Line 44:14: W292 no newline at end of file


[ERROR]

(No Cloudflare challenge detected.) hello Xewdy444, any method to resolve?

Can you provide some more information about this issue.

Can you provide some more information about this issue.

[21:13:54] [INFO] Launching headless browser...
[21:14:08] [INFO] Going to https://-----.com...
[21:14:14] [ERROR] No Cloudflare challenge detected.
it's showing it to me now, before it just couldn't solve it... and it gave timeout

Try using a different user agent.

Try using a different user agent.

I tested several, none worked, the same message appears
could it be the website?

If the website issued a challenge before the latest update to the scraper, then the website was most likely issuing the challenge due to certain HTTP headers that the Webkit browser was using (or lack of). It may also have been due to the user agent used, which by default was Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/605.1.15 (KHTML, like Gecko). I changed the scraper to use Firefox because Cloudflare has a hard time verifying newer versions of Webkit for some reason, and I wanted users to be able to use the scraper with the latest version of Playwright. You can try changing the scraper to use Webkit again by simply editing a single line:
Line 70:
browser = self._playwright.webkit.launch(headless=headless, proxy=proxy)

Then, just make sure you are using a Playwright version greater than or equal to 1.27.0 and less than or equal to 1.28.0.

I'm going to test it soon, I need to sleep... I'll come back to let you know if it worked, thanks for the support

From my experience cloudflare the version of HTTP meters as well. While most probably your HTTP client it's using 1.1 the chrrome/ff browser it's using HTTP 2.
To disable http2 in chrome use '--disable-http2' option

From my experience cloudflare the version of HTTP meters as well. While most probably your HTTP client it's using 1.1 the chrrome/ff browser it's using HTTP 2.
To disable http2 in chrome use '--disable-http2' option

This is also true. I have pushed an update that added the --disable-http2 and --disable-http3 options, which allow users to disable support for HTTP/2 and HTTP/3 for the Playwright browser.

From my experience cloudflare the version of HTTP meters as well. While most probably your HTTP client it's using 1.1 the chrrome/ff browser it's using HTTP 2.
To disable http2 in chrome use '--disable-http2' option

This is also true. I have pushed an update that added the --disable-http2 and --disable-http3 options, which allow users to disable support for HTTP/2 and HTTP/3 for the Playwright browser.

unfortunately the problem persists, but congratulations on the update.
I don't know if it's allowed, but this is the website I'm trying to access
http://stake.best
check if the problem occurs for you

I was able to get this website to issue a managed challenge using this user agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html). However, it had a difficult time verifying the browser, and I was only able to scrape a Cloudflare clearance cookie one time.

python main.py -v -u https://stake.best/ -ua "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

If the website issued a challenge before the latest update to the scraper, then the website was most likely issuing the challenge due to certain HTTP headers that the Webkit browser was using (or lack of). It may also have been due to the user agent used, which by default was Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/605.1.15 (KHTML, like Gecko). I changed the scraper to use Firefox because Cloudflare has a hard time verifying newer versions of Webkit for some reason, and I wanted users to be able to use the scraper with the latest version of Playwright. You can try changing the scraper to use Webkit again by simply editing a single line:
Line 70:
browser = self._playwright.webkit.launch(headless=headless, proxy=proxy)

Then, just make sure you are using a Playwright version greater than or equal to 1.27.0 and less than or equal to 1.28.0.

I didn't find out the real reason, but using "browser = self._playwright.webkit.launch(headless=headless, proxy=proxy)" with Firefox's UserAgent worked
thanks for the help guys


Minor Changes

@atjonathan there are a lot of changes here, many of which I've made independently. Could you take a look at the current state of master and make the fixes that are still needed off of that?

@QuincyLarson, at the time of making this PR, I'm pretty sure none of these changes were fixed.


Fonts activated by FontBase are not found by FontCollector

(Windows 11)
The current font enumeration method does not find fonts activated by FontBase; even though they should be detected as system fonts considering every app with a font picker can find them.
Potentially could also be causing issues with other apps that utilize the same method as FontBase to activate their fonts.
I've confirmed with other users that they also experience the same issue. One user have testified that FontCollector successfully finds their FontBase fonts though but we couldn't identify the cause—so there might be a configuration change necessary for it to work.

This is a issue for: https://github.com/moi15moi/FindSystemFontsFilename

Could you tell me if this print Found... ?
from find_system_fonts_filename import get_system_fonts_filename

fonts = get_system_fonts_filename()
font_name = "Comixo" # Replace this by the family name you activated

for font in fonts:
    if font_name.lower() in font.lower():
        print(f"Found at {font}")

Thanks for replying.
It doesn't reach the print statement. Works if I replace it with a different font that was manually installed however; not ones from FontBase.

Ok, then, this is a issue for https://github.com/moi15moi/FindSystemFontsFilename
Please, reopen the issue on the right repo.


Fix Makefile incorrect shared lib major version for install

Trivial change to parameterize the soname used when installing libraries.
Fixes #10299 #10942 #11868 #12764

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

One or more commits was unable to be associated with a GitHub user. The email used in the Git commit must match a verified email address in a GitHub profile. For more information, please see https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

Regards,
The Linux Foundation CLA GitHub bot

Email issue should be fixed

Email/CLA issue should be fixed

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

I see there are two CI checks failing, but I cannot access the report.
Let me know if there's something to fix.

Any progress on this? We have this issue when packaging grpc for Linux in the Linuxbrew package manager: https://github.com/Linuxbrew/homebrew-core/pull/8136
I could hack around the issue but I would prefer a proper solution is found upstream first.

@sgleizes It seems the Makefile is automatically generated, so you need to patch the build source.
See the header:

# GRPC global makefile
# This currently builds C and C++ code.
# This file has been automatically generated from a template file.
# Please look at the templates directory instead.
# This file can be regenerated from the template by running
# tools/buildgen/generate_projects.sh

Superseded by https://github.com/grpc/grpc/pull/16832


Removed git remnants. #24310

Sorry @raymond91125 I didn't see you had already done this. I merged #24312, so i think you can close this one.


New release of crossbeam-epoch

The current unreleased version of crossbeam-epoch bumps its scopeguard dependency for 1.0. This will be a big help in reducing duplicate scopeguard dependencies - since it's now at 1.0, Cargo will apply the normal Semver rules when picking dependencies (i.e. treating minor versions as compatible).
It would be very useful to get a new point release of crossbeam-epoch to make this transitive dependency change available.

Hi! This is also necessary to get a new version of memoffset, which was upgraded in https://github.com/crossbeam-rs/crossbeam/pull/402 but did not have a corresponding hotfix change to the parent project.  My local version of crossbeam  0.7.1 , for example, doesn't update the dependency, which the cargo audit tool flags as a having security vulnerability.
error: Vulnerable crates found!

ID:      RUSTSEC-2019-0011
Crate:   memoffset
Version: 0.2.1
Date:    2019-07-16
URL:     https://github.com/Gilnaa/memoffset/issues/9#issuecomment-505461490
Title:   Flaw in offset_of and span_of causes SIGILL, potential memory unsafety
Solution: upgrade to: >= 0.5.0

error: 1 vulnerability found!

Oh whoops, I see this is already happening in the linked discussion. Sorry to be repetitive -- thanks!

Hey just to follow up in both threads I wrote up what I see here: https://github.com/RustSec/advisory-db/pull/124#issuecomment-512870145

Version 0.2.1 is unsound but not known to cause any concrete problems.

Just an FYI for anyone who comes across this issue, the advisory has since been updated to include all versions prior to 0.5, so 0.2.1 is indeed affected and will be reported y cargo audit.  Ref https://github.com/RustSec/advisory-db/pull/129

Right, it was found out that the lack of protection against deref coercions could (if the deref coercion panics) lead to drop on uninitialized memory.
However, if crossbeam does not actually call offset_of on a field involving a deref coercion, there is no issue in crossbeam.

Any updates on a new release to crates.io? The memoffset issue is causing any project that runs cargo-audit during CI to fail builds.

Will the next release be a PATCH-compatible, crossbeam-epoch-0.7.2? That would be nice because the security fix for memoffset 0.5, per 7169d4f, would most likely get applied downstream via cargo update? (Reading this I see that that security issue might be overstated, but still nice to move forward with memoffset 0.5)
Or does it require new MINOR releases, e.g: (crossbeam-epoch-0.8.0 crosbeam-0.8.0 crossbeam-deque-0.8.0 …)?  Below are the changes since the crossbeam-epoch-0.7.1 release. The MSRV bump was reverted.  Looks like scopeguard (upgraded in b465caa0, #370) is a purely private dependency? At first glance, 088012e appears to change pub interface, but IsElement<T> isn't actually exported?
If this does need a MINOR release, would it be worth considering backporting only the security fix(s) or other PATCH-safe changes to a crossbeam-epoch-0.7.2?  I'm happy to try and help, if I can.
% git log crossbeam-epoch-0.7.1.. -- crossbeam-epoch

7169d4f update memoffset to 0.5, which contains plenty of soundness fixes
088012e Fix list's finalize API
32ef2fd Small fixes and renames
9d5346c Remove unnecessary mention of Box
dd6212a Update readmes
96ddd4d Support non-atomic targets
cafe143 Add the alloc feature
7b6cca7 Fix no_std build
0e266b0 Revert "Bump the minimum Rust version"
aa1b263 epoch: Add Atomic::into_owned
b4651ca chore: Update scopeguard to 1
b5f287d Bump the minimum Rust version
a1e480c Merge #357
72fbfbe Update README.md
de696d5 Add copyright notice
c92c4f5 Merge #355
28da96f Fix broken build on latest nightly
e62a39f long-form superscript notation in readmes
8c20ae9 Add minimal versions check to travis
2076c5a Rustfmt everything

I have just published a new version of crossbeam-epoch. Sorry for the delay!

Thanks a lot @stjepang !


Azure Service Operator support for ASO-created Managed Identities

Describe the solution you'd like
If you create a Managed Identity using Azure Service Operator, the operator exposes values through a Kubernetes ConfigMap (Principal ID, Client ID, Tenant ID). However, when creating a SecretProviderClass, you need to provide the ClientID value. There's no easy way to transpose the values from one to the other without a manual solution involving scraping the value and passing it over.
If there were an interoperable way for the SecretProviderClass to get the client ID of the ManagedIdentity for the purposes of Workload Identity, that would remove a manual step and make setting up an environment much simpler. Off the top of my head, if there were a way for the SecretProviderClass to support getting the ClientID value from a ConfigMap, that could alleviate the issue.
Anything else you would like to add:
The ASO team tapped me to create this as an issue, as I mentioned there was no easy solution for this.

I am not sure what the right solution to this issue is, but interested in folks thoughts. I do think that the ability to use ASO to provision a Managed Identity + Role Assignment for your app as part of your Helm chart or YAML, and then feeding that directly to CSI Driver would be an interesting scenario to enable. Curious what @aramase thinks.

It would be great to get this solved. Would it be possible to get the Client ID of the ManagedIdentity from the workload requesting the volume mount? The workload would have it as an environment variable.
Currently, the CSI driver is getting the service account token associated with the workload requesting the volume mount, and I'm curious if the same can be done with the Client ID. Suppose there's a way to get that value through Pod Info on Mount [https://kubernetes-csi.github.io/docs/pod-info.html].

@tyler-gs were you able to find some work around for this other than using a different helm chart and install it as a prerequisite ?  please let me know if there is a better way to handle this .

@tyler-gs were you able to find some work around for this other than using a different helm chart and install it as a prerequisite ? please let me know if there is a better way to handle this .

I'll be honest, I ended up swapping from this CSI driver provider to the External Secrets operator, since that does what I want it to do, which is setup the secrets automatically without having to launch a pod first.

I've asked the same thing for the App Configuration Kubernetes Provider and the feature was developed. I really need this too. For this moment, I see two workarounds:

Using the App Configuration Kubernetes Provider to access a Key Vault secret via the App Configuration Store.
Using the External Secrets Operator which can read the clientID from a configmap.

Seeing the same issue as well. Supporting something like this would be great:
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
spec:
  provider: azure
  parameters:
    clientID: # string | configMapKeyRef | secretKeyRef
      configMapKeyRef:
        name: some-name
        key: some-key


significant stuttering when time tracking plugin is displayed

Describe the bug
Runelite hitches for about a quarter to a half second at regular intervals when the timer plugin is displayed. This happens every 10 or so seconds passively. If you are harvesting a patch then the stuttering occurs very frequently if any panel except the overview is selected. The more frequent stutter might be happening whenever a patch's 'life' is consumed, so harvesting things like herbs better reproduces the issue.
To Reproduce

Log into the game with the time tracker plugin displayed
keep rotating the camera with the arrow keys, to make the stutter more noticeable, observe the intermittent stuttering
harvest a patch with the appropriate category panel open and rotate the camera, observe the frequent stuttering

Expected behavior
Displaying the timer plugin UI should not result in stuttering
Screenshots
N/A
Environment (please complete the following information):

OS: Windows 10
RuneLite version: <IP_ADDRESS> (I believe this issue is recent, but I'm not sure how recent)
Launcher version: 2.0.2

Additional context
Issue was present with GPU mode enabled or disabled, and with the client fullscreened or with it in a small window.
If there is any issue reproducing this then I'll happily share my config or client logs.

Given that nothing has happened on this issue for months, and no one has reported anything similar, closing as stale


Make all PyEnsembl objects hashable

Implementation of hash needed for memoization (maybe only in Python 3?)

LGTM


PHP 8.0 compatibility change, braces to brackets

This appears to be an exact match of @Shadowritter commit #39.