Atom tabs switch-list does not appear

Using Atom's tab package for tab-switching, had the tab switch disabled.
The class on that element is select-list tabs-mru-switcher
Reproduction Steps:
Settings for atom-material-ui:

[x] Generate complementary accent
[ ] Paint text editor's cursor
[ ] Use animations
[x] Contrasting panels
[ ] Panels cast shadows
[x] Compact tab bar
[x] No minimum width for tabs
[ ] Tinted tab bar
[ ] Blend tree view with tab bar
[x] Compact tree view

Settings for tabs:

[ ] Add New Tabs At End
[x] Always Show Tab Bar
[x] Enable MRU Tab Switching
[x] Enable VSC Coloring
[x] Show Icons
Tab Scrolling - platform
[x] Use Preview Tabs

Using ctrl-tab to switch tabs
keybindings
'body':
  'ctrl-tab': 'pane:show-next-recently-used-item'

'body':
  'ctrl-tab ^ctrl': 'pane:move-active-item-to-top-of-stack'

Expected behavior:

Observed behavior:

Atom version: v1.14.3
OS and version: Windows 10
Installed packages:
https://atom.io/packages/tabs

Let's wait what @silvestreh will show us when the sneaky 2.0 branch is merged and released. ;) I was wondering, when I was reading the 1.14 Atom release notes, why this list is not showing up for me, so I found your ticket and investigated the issue. This is a workaround, I've been able to come up with:

Open the lib/tabs-settings.js file (located in this package sources in .atom/packages/atom-material-ui/ folder)
Remove lines 41 to 47 containing:

atom.workspace.onDidChangeActivePaneItem(() => {
    var activeTab = document.querySelector('.tab-bar .tab.active');

    if (activeTab && activeTab.click) {
        activeTab.click();
    }
});

Reload your Atom window via window:reload (or restart Atom)

The issue is, the code mentioned above is clicking on the newly selected tab (see activeTab.click();). That effectively hides the tabs list, because before it can be rendered, a new tab is "fully activated" and the list is not necessary anymore.
I've tried to figure out if removing the code has any impact on the package, but it behaves just fine for me and no other problems are introduced.
In addition, I would like to say that this should not be used as a fix as is. I pretty much enjoy the behavior when tab list is not shown. It feels a bit quicker to me. So I would be glad, if this can be introduced just as an option, via some toggle in settings. I actually like this bug, lol.

It's on the 2.0 branch, but requires Atom 1.17 (unfortunately, not even in the Beta channel)

I'll leave this issue open!

This is fixed in 2.0 which is available for Atom 1.17-beta users.


Use once instead of chan on service init and optimize

1.Use sync.Once instead of chan for service init once, just better.
2.I don't understand why create a temp options to keep cmd instance, it still will be override in the loop

"Just better" is not a valid reason for this change. It's just style preference.

First commit is ok. but second. Could you explain for me?

Options contain a lot of nested interfaces. Init provides a way to set some of those Options but in certain cases it cannot be done cleanly due to the nature of how the entire library is built. Starting with a new set of options then cleanly applying changes to that works better. There's also the ability to additionally add flags and arguments related to command line parsing at this stage so again best way to handle this is preserving the existing cmd and making it part of the new options.

I got it, here only to set the cmd interface, regardless of other parameters.


fix: Purge orphaned paths from dynamicTriggerPathList

Description
On certain occasions, we find that paths which are defined in a widget's dynamicTriggerPathList and dynamicBindingPathList don't really exist in the widget. This has been observed in the MenuButton widget
This results in issues in subsequent evaluations. The details with respect to the exact issue in the evaluations are unclear -- nevertheless, having orphaned paths is akin to having a bad DSL. This fix purges then during property update.
Fixes #10791
Fixes #10768
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Jest test added for the purging function.
Tested manually using the steps shown in #10768
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/purge-orphaned-triggerpaths

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.05 (0)
36.62 (0.01)
34.79 (0.02)
55.45 (0)

:red_circle:
app/client/src/sagas/WidgetOperationSagas.tsx
51.54 (0)
38.73 (-0.29)
52.08 (0)
52.79 (0)

:green_circle:
app/client/src/sagas/WidgetOperationUtils.ts
61.86 (1.08)
44 (2.06)
59.62 (2.48)
61.26 (1.26)

:red_circle:
app/client/src/selectors/commentsSelectors.ts
83.61 (-1.64)
61.76 (-2.95)
73.33 (0)
88.24 (-2.35)

/ok-to-test sha=d307df2


use Bootstrap as default CSS framework

when twitter's bootstrap 2 comes out on january 31st we should make it the default CSS framework
http://www.markdotto.com/2012/01/24/bootstrap-2-ready-for-testing-and-feedback/

Yes please!

This would be awesome. I'm about to start a new project and I was wondering, if 2.0 is released on Tuesday, how do you think it would take before this Roots repository includes it?

likely by the end of the week, but probably not with bootstrap-specific markup (ie. for the top navbar) at that point

With BS markup inclusive, Roots will be insane. I've looked long and hard for the ultimate WordPress Framework, and Roots could be it.

been discussing this with @swalkinshaw and we're considering dropping all CSS frameworks besides bootstrap and just focusing on that.

H5BP people are on the same page: https://github.com/h5bp/html5-boilerplate/issues/936

+1 on this! Twitter Bootstrap 2.0 integration would be fantastic, with responsive design Foundation's one competitive advantage disappeared.

Wow, this project is awesome!
The bootstrap framework seems like the way to go for layout and it looks like 2.0 just hit. I'm about to start a new site project and am wondering if I should hold off until bootstrap 2.0 is incorporated? Does the end of week estimate still seem realistic? Is it just a matter of replacing the css and js files in the template to get things working temporarily?
Thanks guys!

end of the week is still realistic (sunday) - was in business meetings all day yesterday and doing the same again today, but will start working on this tomorrow.
you could replace the css/js files for now if you'd like, you'll need to make sure you update the calls in roots-scripts.php for the new scripts. the default grid classes need to be updated as well since the total number of columns is different

I added Bootstrap v2.0.0 this morning with the commit 7266dae71b68139e5ac2508302374da746cca993 pulled in my @retlehs

Does this mean BS2 is fully integrated and this issue is pending closure? Or is there more work to be done to update script calls, grid classes, etc.?

It is not yet the default framework and I will be removing all the
other frameworks as part of this ticket.
Sent from my iPhone
On Feb 1, 2012, at 6:01 PM, m1chael
<EMAIL_ADDRESS>wrote:

Does this mean BS2 is fully integrated and this issue is pending closure? Or is there more work to be done to update script calls, grid classes, etc.?

Reply to this email directly or view it on GitHub:
https://github.com/retlehs/roots/issues/251#issuecomment-3769911

All of the bootstrap v2.0 CSS and JavaScript files are included in
bootstrap from the commit I made earlier today. But as Ben said soon
Roots will only use Bootstrap.
Sent from my iPhone
On Feb 1, 2012, at 6:01 PM, m1chael
<EMAIL_ADDRESS>wrote:

Does this mean BS2 is fully integrated and this issue is pending closure? Or is there more work to be done to update script calls, grid classes, etc.?

Reply to this email directly or view it on GitHub:
https://github.com/retlehs/roots/issues/251#issuecomment-3769911

Hi, thanks for all the great work. I had some layout issues with Bootstrap v2.0 from your latest commit, as it appears the bootstrap.css file is still at v1.4.0. Solved it by replacing it with the 2.0 version.
Also, it looks like some frameworks are missing the image files. For example, Bootstrap is missing the "img" dir which contains the glyphicons.png and Foundation is missing its "images" directory, which contains some button backgrounds, loading.gif for Orbit and so on. These files are often referenced in the css as ../img, so i guess the corresponding "img" directory should either be placed at the root of the /css directory or the links from these framework's css should be edited to point to the correct location. Just a suggestion.

keeping this open until i tag a new release and update the changelog but it should be all done

right arm!

For those of you still wanting to use Grid 960 and Foundation I plan on maintaining forks for each framework.  I should hopefully have the basics setup for each running by the end of the weekend

This is pretty cool, thanks a lot. Just curious, what's the reason for not including and linking to the minified version of the .css & .js instead?

thx @elfo, minifed the css with 320a1d32c087efd55402a45d485f180aab7f671a and minified the js with d97ae91d240e1d156952783bc02c959f0e522331

Wow, very timely - just starting a new WordPress project and wanted to use bootstrap 2.0 and H5BP. \o/
Are we all good to go with the latest commit, and just waiting for tags/changelog? Or is there more to do before it's fully incorporated?
Thx!

Should probably be renamed "RootStraps" then now :)

@josscrowcroft should be good to go. let me know if you run into anything

Yep, all works great! I have a bunch of little suggestions and tweaks (based on my past life as a WP developer) which I'll try to do some pull requests for. On the whole this is a fantastic project, massively impressed.

oh my.

5.0.0 tagged, http://www.rootstheme.com/ updated
will update changelog shortly

I heard about Twitter Bootstrap some months back, but am yet to look at it in full. I'm sure it's absolutely fantastic, but I am not sure what the logic in removing all the other frameworks from Roots is. Isn't it good to give us the option to choose? I've got a good way of working on a 960 grid, and moving to a 940 grid is going to be a bit of a culture shift for the way I work at the moment. Sure, in the future I'll see the light and use Bootstrap, but I'd like the choice. Is Bootstrap now hardwired throughout Roots, or is there a way for me to still use other frameworks? Thanks.

@baritoneuk I am going to maintain a grid 960 version of Roots for those that are not ready to move over to bootstrap.  I also have a foundation version of roots as well if you prefer foundation.
I have been a bit busy but I may be able to have the grid960 fork ready sometime on tuesday.  You can check for it on my fork http://github.com/coreywagehoft/roots-grid960/ in a few days

@baritoneuk I highly suggest giving Bootstrap a try. It's quickly become the de facto "framework" because it's so good.
In terms of the choice to remove all other frameworks, it was ridiculous to think we could support all of them. Somehow it actually worked out decently, but there was always bugs and it made the theme much more complicated that it should be. Framework support just spiralled out of control since there's so many these days.
The options for selecting and setting up the framework also didn't make much sense. I highly doubt many Roots users would change frameworks once it was installed and they customized the theme.

@swalkinshaw you are right of course. It's just having to learn to work with yet another Framework. Normally i'd love the chance at playing with something new, but with time constraints it's not always easy.
I take your point regarding the option to change the framework once loaded being a little silly. However, it would be good if it were still possible to work with other Frameworks other than Bootstrap. I am sure this is still possible within Roots as longs as bootstrap is not going to be completely hardwired.
I've looked at Bootstrap and it looks comprehensive. I hadn't realised there were other options other than the 940 grid (i.e. fluid etc). I'll have more of a play when I get the chance. I've got an issue with the dropdown menu not working, but I've mentioned that in another issue.

Does Roots compile bootstrap via php or is it done client-side via javascript?

client side minified js
-moimikey
On Thursday, March 8, 2012 at 10:16 AM, hannesjohansson wrote:

Does Roots compile bootstrap via php or is it done client-side via javascript?

Reply to this email directly or view it on GitHub:
https://github.com/retlehs/roots/issues/251#issuecomment-4392975

I've never used bootstrap so this could be dumb question, but is there any reason for not doing in server-side with php? After googling it seems like there are alternatives like phpless, could they be used to compile the css serverside (and thus be embedded natively in Roots)? Or are there benefits with doing it client-side that I'm not realizing?


4-bit quantization meta device bias loading bug: fixes #2742

What does this PR do?

Fixes #2742
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

I'm finishing this PR since no changes were made from the past 3 weeks. @MuhammedHasan, you will be included as a co-author of the PR since I used the commit here.


Select all

add a Select all to make linking documents faster

Please clarify your use case.

I create a new page, write a document, press to create links, and it finds some 200 links to create. having a select all, would speed up my process many minutes per document.

Thank you for explaining. However, the process you've described is unclear. Perhaps an example would help.

I write technical documentation, lots of jargon, so here is an example
Yosys is an open-source framework for Verilog RTL synthesis.
It is widely used in the field of digital design automation (EDA) for transforming high-level Hardware description Language (HDL) into gate-level representations. Here are some key aspects of Yosys:

1. **Open-Source Nature**: Yosys is freely available under the ISC license, which allows User to modify, distribute, and use the Software without significant restrictions.

2. **Verilog Support**: Yosys primarily supports the Verilog Hardware description language, which is commonly used in designing digital circuits. It can parse, analyze, and optimize Verilog code.

press to create links, gives a selection of some 200 possible links to create to existing pages, a select all would be really helpful here
the document becomes
[[Yosys]] is an open-source framework for [[Verilog]] [[RTL]] synthesis.
It is widely used in the field of digital design automation ([[EDA]]) for transforming high-level Hardware description Language ([[HDL]]) into gate-level representations. Here are some key aspects of Yosys:

1. **[[Open-Source Nature]]**: Yosys is freely available under the [[ISC license]], which allows User to modify, distribute, and use the Software without significant restrictions.

2. **[[Verilog Support]]**: Yosys primarily supports the Verilog Hardware description language, which is commonly used in designing [[digital circuits]]. It can parse, analyze, and optimize Verilog code.

Thank you for the example. I will review it and see what I can do.


Hangs when attempting to execute any command that brings up a modal dialog

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.22.0
Regression From
Only started happening a couple of weeks - May be related to recent Windows 11 updates
Architecture
x64
Storage Explorer Build Number
20211211.10
Platform
Windows
OS Version
Windows 11
Bug Description
When attempting an operation that brings up a modal dialog, for example deleting a blob, the dialog never appears and the entire app becomes inoperable. In other words clicking anywher on the app just produces a beep from the system
The issue has become more severe with recent Windows 11 updates - Is there an incompatbility?
Steps to Reproduce

Launch Storage explorer
Navigate to a blob container
Continue to navigate to a single file (blob) under the container
Select the file
Click Delete

Actual Experience
After step (5) in repro steps:

The expected dialog never appears and the whole storage explorer app  becomes unresponsive. Clicking anywhere results in a beep indicative of when clicking on a windows app when a modal dialog is visible
The only course of action is to kill storage explorere from task manager

Expected Experience
Expected:  When clicking on delete the confirmation dialog should appear enabling completion of the delete ction
Additional Context
This only started happening in past few weeks - perhaps related to recent Windows 11 updates.  I tried upgrading from a previous version V1.21.xx to the latest version V1.22.0  but that made no difference to the behaviour

@mrevow
We think what may be happening is that that dialog is opened but just off screen such that you cannot see it/move it/interact with it using your mouse. However, you should be able to use the Windows key + either the left or right arrow key to move it back to being visible. So can you:

Open task manager
Sort by name and look for a group of StorageExplorer.exe processes
Count how many there are
Do something that should open a dialog
Go back to task manager and count how many StorageExplorer.exe processes there are, specifically we want to know if any additional processes appeared
Press Windows Key + arrow Key left/right and see if you can make the dialog appear

Let us know if any additional processes appeared, and if using the arrow keys made the dialog visible again.

Closing as a duplicate of #5262


Systemd nolimit

Systemd does not respect the nofiles limits set outside the service script. This PR implements setting the nofiles accordingly. Had to move the system service script into the provider so that the proper descriptor values are used. This results in the need to create a separate service scrpt for each server instanes as maxclients could be different for each server instance.

Dupe of https://github.com/brianbianco/redisio/pull/228

I commented on #228 in that it uses the default value of max-clients and does not take into account the server hash overrides. So the value set ignores what is set for each server instance.

Closing this pull request as #228 was merged in.  Please feel free to make further changes to master now if you spot something you feel needs improvement regarding nolimit and systemd.


Nested event structure definitions cause downstream code generation problems

Is your feature request related to a problem? Please describe.
Rust event types for AWS Lambda are generated from this project's event definitions and the recent introduction of nested Go structure definitions in APIGatewayV2HTTPRequestContext via https://github.com/aws/aws-lambda-go/pull/274 has caused Rust code generation to fail (Rust has no nested structure definitions).
Describe the solution you'd like
Would it be possible to declare all event types as top-level structures?
Describe alternatives you've considered
In the short term a blacklist for structures that can't be handled could be introduced but the long term alternative would be significant work to rejig the Rust code generator.

Would it be possible to declare all event types as top-level structures?

Seems fine to me


[Unity][WebGPU] Get params from cache by name

This PR is essentially https://github.com/apache/tvm/pull/16078 but for web runtime.
Add function getParamsFromCacheByName() for web runtime, hence creating CreateByName() in ndarray cache. Create() to GetParams() is analogous to CreateByName() to GetParamsByName().

cc @tqchen


pydantic schema validator for vp token

pyeudiw.opeid4vp

Closed by https://github.com/italia/eudi-wallet-it-python/pull/71


fix(scripts): Dockerfile is outdated

Fix issue #190
Hi, there is indeed a minor issue. Now the script file should be ./scripts/download_driver_for_all_platforms.sh.

This doesn't work anymore. At least it seems like that.
When executing the Dockerfile I get the following error:
> [7/8] RUN cd /tmp/pw-java &&     ./scripts/download_driver_for_all_platforms.sh &&     mvn install -D skipTests --no-transfer-progress &&     DEBIAN_FRONTEND=noninteractive mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI                      -D exec.args="install-deps" -f playwright/pom.xml --no-transfer-progress &&     mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI                      -D exec.args="install" -f playwright/pom.xml --no-transfer-progress &&     rm -rf /tmp/pw-java:
#12 0.658 /bin/sh: 1: ./scripts/download_driver_for_all_platforms.sh: not found

@aslushnikov is that a side effect of https://github.com/microsoft/playwright-java/pull/709 ?

@FloHiwg can you please open an issue and describe what is not working? Docker build works fine with that file on our bots, see e.g. this run


Teach Hubot to say good night

After a long night of coding sometimes only Hubot is awake to send you off to bed properly.

A lot of overlapping functionality with https://github.com/github/hubot-scripts/blob/master/src/scripts/polite.coffee


[FEATURE] Add events validation in playground

Description
Add another option in the playground for events just like profile:

validates json
formats json
shows event card

Screenshots
No response
Additional information
No response

We would like to be assigned this task!

We would like to be assigned this task!

All yours!

hello. could i please be assigned this issue

@vibronst and @KaveriRai great to see you are working together on this issue, I have assigned it to you both

I am going to close this issue, as the pull request has been closed and in the near future forms will be available


Update GC_MS_pipeline_xcms.ga

updated descriptions
added creator
added license
made interesting outputs visible and added labels
added annotations for inputs

@xtrojak I guess it can.


Anonymous types equality and order of properties

two anonymous objects with the same Properties in different order should be equal ?

The Equals and GetHashcode methods on anonymous types override the methods inherited from object, and are defined in terms of the Equals and GetHashcode of the properties, so that two instances of the same anonymous type are equal if and only if all their properties are equal.

var p1 = new { Name = "Lawnmower", Price = 495.00 };
var p2 = new { Name = "Lawnmower", Price = 495.00 };
var p3 = new { Price = 495.00, Name = "Lawnmower" };

Console.WriteLine($"are equal {p1.Equals(p2)}");// true
Console.WriteLine($"are equal {p1.Equals(p3)}"); //false

Within the same program, two anonymous object initializers that specify a sequence of properties of the same names and compile-time types in the same order will produce instances of the same anonymous type.

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

ID: e783650c-e063-e268-316e-564362cb1e37
Version Independent ID: aa9f4996-cab4-0bed-6452-213342453785
Content: Expressions - C# language specification
Content Source: spec/expressions.md
Product: dotnet-csharp
Technology: csharp-spec
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

@jskeet
This may be below the bar. The "in the same order" is already in informative text for assignment, but not for equality.

I think we probably do want to improve this, but I'm happy to close it as a duplicate of #114.
Labeling as "meeting:discuss" and "meeting:proposal" to ratify that decision.

Closing as a duplicate.


Python 2 support

Should Python 2 be supported by pylance?
I ask this question because I get an "xrange" is not defined message but xrange is Python 2 only.
Thanks.

Pylance supports only Python 3 and newer. It doesn't support Python 2.
If you still have Python 2.x code, the Jedi language server is available.


Build Failed

And here is the message:
Build FAILED.
"C:\Users\Daniel\Documents\GitHub\td\build\ALL_BUILD.vcxproj" (default target) (1) ->
"C:\Users\Daniel\Documents\GitHub\td\build\test\all_tests.vcxproj" (default target) (3) ->
"C:\Users\Daniel\Documents\GitHub\td\build\tdactor\tdactor.vcxproj" (default target) (4) ->
"C:\Users\Daniel\Documents\GitHub\td\build\tdutils\tdutils.vcxproj" (default target) (5) ->
"C:\Users\Daniel\Documents\GitHub\td\build\tdutils\generate\tdmime_auto.vcxproj" (default target) (6) ->
(CustomBuild target) ->
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(1
71,5): error MSB6006: "cmd.exe" exited with code 1. [C:\Users\Daniel\Documents\GitHub\td\build\tdutils\generate\tdmime_
auto.vcxproj]
0 Warning(s)
1 Error(s)

This error supposed to happen when gperf isn't found.
Could you try to manually run from the /tdutils/generate/ directory command
powershell -ExecutionPolicy ByPass " & gperf -m100 --output-file=auto/mime_type_to_extension.cpp auto/mime_type_to_extension.gperf"?

I have the same problem, after downloading gperf (not sed) and adding its install path to environment variables, it was fixed.

Error message, shown when gperf is not found, was improved in 1.2.0.


Leave Wells Out

Hi again,
I´m not expecting wonders here but trying to be systematic to learn during this competition.
Still investigating the bafflestone overfitting. Here are three submissions with different data and cross validation stratergies. The parameters are different and have been calibrated for each. Same feature engineering for all 3.
_5 - OneVsOne - Macro score. Similar to previous entires.
_6 - Leave Wells Out CV. Not including Facies F9, or well Recruity F9 or Cross H Cattle. Cross H Cattle seen as a distraction with more facies 1. OneVsONe Boosted Trees. + F1 Micro score calibration.
Dataset = Dataset[Dataset["Well Name"] != "Recruit F9"]
Dataset = Dataset[Dataset["Well Name"] != "Cross H Cattle"]
Dataset = Dataset[Dataset["Facies"] != 9]
_7 Leave Wells Out CV all wells all facies. OneVsONe Boosted Trees. + F1 Micro score calibration  (Higher proportion of F9 still present).
If you interested the solution to being able to use these in GridSearchCV are:
"Scoping" to be able to pass parameter grid into GridSearchCV while using Xgb boost and OneVsOne:
parameters = [{'estimator__subsample': [0.7],...
How to pass LeavePGroupsOut into
cv=list(LeavePGroupsOut(n_groups=n).split(X,y,groups))

Hello again, and thank you for these. Some good news...
_5  0.561
_6  0.549
_7  0.441

The _5 score bumps you up a bit. Something to build on there. Cheers!

Oh sorry, I just noticed that I don't think you checked in the notebooks to go with these results... Maybe you can do that next time — just add them in. I only really need the one for _5, since it's your high score. No hurry.


Hot exit: automatically restored window has lowercase workspace path

MacOS

Dirty a file
Quit vscode
Open some other folder with vscode so that the orginal workspace is opened
The original workspace will have a lowercase workspace path - if you hover a file to see its full path, it will be all lowercase.

This causes problems with debugging - https://github.com/Microsoft/vscode/issues/16570

This also causes issues that file events will not work under Mac, so we must ensure to not open a workspace path with the wrong casing. Marking as important because this will cause lots of issues.

Can reproduce, the second launch has both the mixed case and lowercase path in the workspaces.json.


Cannot Find hiyaCFW/ No Such File or Directory: hiyaCFW.7z - WINDOWS 10

When I try to start to install the latest twilight menu i get an error message saying it can't find the 7 zip file "hiyaCFW.7z" and that there basically isn't a such thing.

Is HiyaCFW.7z in the directory, where the Helper is?

All I see in the dire tory is the helper and a folder entitled windows and inside that folder is a tool exe file. But no hiyacfw.7z I have searched for it with the start menu and everything, thinking maybe it's in the wrong place. But it's just flat out not there. What am I missing. I've got all the steps in place and when I run the loader, it says it can't find the file. That's the only place it stops me. Once I get that hiyacfw.7z I can go through with this the rest of the way.

Try not to put the NAND file in a route with special characters or too long. Put it in C:\NAND\ or something like that

In the status window for the helper it says Downloading latest Hiyacfw release...
ERROR: Could not get HiyaCFW
And in the console:
[Errno 2] Nosuch file or directory: 'HiyaCFW.7z'
Not sure what I did wrong here. Went step by step and didn't use any crazy folder names with any odd characters.

Is HiyaCFW.7z in the directory, where the Helper is?
No, I don't believe so. I feel like if it was, my pc would find it instead of telling me there's no such file or directory.

By any chances do you have any antivirus software? If you do, can you check its logs to see if it's deleting the downloaded HiyaCFW.7z?

I turned off my antivirus software just in case that's what the issue was and it wasn't that, either. I am not sure where to look for logs to see if its been deleting it or not. Is there somewhere where i can just redownload the file and start over or is there some way to fix this?

Put it in the same folder as the helper
https://github.com/RocketRobz/hiyaCFW/releases/download/v1.3.2/HiyaCFW.7z

now, it is saying extractor failed. ugh.

Opening HiyaCFW Helper...
Initializing GUI...
Searching for 7-Zip in the Windows registry...
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\banner.bin
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\bootloader arm7 patch.ips
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\bootloader arm9 append to start.bin
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\bootloader arm9 patch.ips
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\header.bin
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\make bootloader nds.bat
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader update.ips
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\v1.4 Launcher (00000002.app) (JAP-KOR) patch.ips
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\v1.4 Launcher (00000002.app) patch.ips
ERROR: Can not open output file : The system cannot find the path specified. : .\for SDNAND SD card\title\00030017\484e4145\content\title.tmd
ERROR: Can not open output file : The system cannot find the path specified. : .\for SDNAND SD card\title\00030017\484e414a\content\title.tmd
ERROR: Can not open output file : The system cannot find the path specified. : .\for SDNAND SD card\title\00030017\484e4150\content\title.tmd
ERROR: Can not open output file : The system cannot find the path specified. : .\for SDNAND SD card\title\00030017\484e4155\content\title.tmd
ERROR: Can not open output file : The system cannot find the path specified. : .\for SDNAND SD card\hiya.dsi
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\bootloader files\ndstool.exe
ERROR: Can not open output file : The system cannot find the path specified. : .\for PC\twltool.exe
this is what i get.
i even ran as admin

did i say/do something wrong? lol

It seems you are using the helper inside a read-only folder

No follow up from reporter, closing ticket


lili

i respond to that  comment

i respond to that  comment

Good pull requests have a body description that tells other contributors about the change you're suggesting, so they understand the context.
Let's edit this pull request to add a body description.
Activity: Fixing your pull request

The first comment on your pull request will have the default text of No description provided. Click on the ... icon located at the top right corner of the comment box, then click on Edit to make an edit
Add a description of the changes you've made in the comment box. Feel free to add a description of what you’ve accomplished so far. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request
Click the green Update comment button at the bottom right of the comment box when done

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.
I'll respond when I detect this pull request's body has been edited.

nice help thank you

Good pull requests have a body description that tells other contributors about the change you're suggesting, so they understand the context.
Let's edit this pull request to add a body description.
Activity: Fixing your pull request

The first comment on your pull request will have the default text of No description provided. Click on the ... icon located at the top right corner of the comment box, then click on Edit to make an edit
Add a description of the changes you've made in the comment box. Feel free to add a description of what you’ve accomplished so far. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request
Click the green Update comment button at the bottom right of the comment box when done

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.
I'll respond when I detect this pull request's body has been edited.

nice help thank you


[Segment Replication] Update peer recovery logic for segment replication

Signed-off-by: Suraj Singh<EMAIL_ADDRESS>Description
Update the peer recovery logic to work with segment replication. The existing primary relocation is broken because of segment files conflicts. This happens because of target (new primary) is started with InternalEngine writes its own version of segment files which later on conflicts with file copies on replicas (copied from older primary); when this target is promoted as primary.
This change patches the recovery flow by first recovering the primary target with NRTReplicationEngine engine (to prevent target from generating segment files). Post phase 1 file copy operation, the older primary is blocked from performing segment file copy events to replicas (prevent segment file copy to replicas from auto refreshes). Post phase 2 before finalizeRecovery and handoff, the target (new primary) is forced to refresh segment files from older primary (to catch up with other replicas) followed by switching engine to InternalEngine.
Issues Resolved
#5242
Check List

[x] New functionality includes testing.

[ ] All tests pass

[x] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/7257/
CommitID: 1414c09
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

Looks like a legit test failure. Looking into it.
  2> REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.index.shard.IndexShardTests.testPrimaryHandOffUpdatesLocalCheckpoint" -Dtests.seed=EF62886CB90D105 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=lv-LV -Dtests.timezone=Atlantic/St_Helena -Druntime.java=19
  2> java.lang.AssertionError: RecoveryFailedException[[index][0]: Recovery failed from {dsEyIzXaub}{dsEyIzXaub}{Lyp3hhGUQ6KLW2cur9rZLQ}{<IP_ADDRESS>}{<IP_ADDRESS>:72}{dimrs} into {VrZdpzmpJk}{VrZdpzmpJk}{yNPgntL_ROidrq8BPYEYrw}{<IP_ADDRESS>}{<IP_ADDRESS>:71}{dimrs} ([index][0]: Recovery failed from {VrZdpzmpJk}{VrZdpzmpJk}{yNPgntL_ROidrq8BPYEYrw}{<IP_ADDRESS>}{<IP_ADDRESS>:71}{dimrs} into {dsEyIzXaub}{dsEyIzXaub}{Lyp3hhGUQ6KLW2cur9rZLQ}{<IP_ADDRESS>}{<IP_ADDRESS>:72}{dimrs})]; nested: RecoveryFailedException[[index][0]: Recovery failed from {VrZdpzmpJk}{VrZdpzmpJk}{yNPgntL_ROidrq8BPYEYrw}{<IP_ADDRESS>}{<IP_ADDRESS>:71}{dimrs} into {dsEyIzXaub}{dsEyIzXaub}{Lyp3hhGUQ6KLW2cur9rZLQ}{<IP_ADDRESS>}{<IP_ADDRESS>:72}{dimrs}]; nested: RecoveryEngineException[Phase[1] prepare target for translog failed]; nested: IllegalArgumentException[Shard can only be wired as a read only replica with Segment Replication enabled];
        at __randomizedtesting.SeedInfo.seed([EF62886CB90D105:92C2488BA82DB989]:0)
        at org.opensearch.index.shard.IndexShardTestCase$2.onFailure(IndexShardTestCase.java:187)
        at org.opensearch.indices.recovery.RecoveryTarget.notifyListener(RecoveryTarget.java:141)
        at org.opensearch.indices.replication.common.ReplicationTarget.fail(ReplicationTarget.java:175)
        at org.opensearch.index.shard.IndexShardTestCase.recoverUnstartedReplica(IndexShardTestCase.java:899)
        at org.opensearch.index.shard.IndexShardTestCase.recoverReplica(IndexShardTestCase.java:824)
        at org.opensearch.index.shard.IndexShardTestCase.recoverReplica(IndexShardTestCase.java:806)
        at org.opensearch.index.shard.IndexShardTests.testPrimaryHandOffUpdatesLocalCheckpoint(IndexShardTests.java:2431)

Codecov Report

Merging #5344 (4d1644c) into main (9c03010) will increase coverage by 0.02%.
The diff coverage is 56.42%.

@@             Coverage Diff              @@
##               main    #5344      +/-   ##
============================================
+ Coverage     70.84%   70.86%   +0.02%
+ Complexity    58306    58290      -16
============================================
  Files          4741     4742       +1
  Lines        278541   278661     +120
  Branches      40268    40281      +13
============================================
+ Hits         197339   197485     +146
+ Misses        65045    64948      -97
- Partials      16157    16228      +71

Impacted Files
Coverage Δ

.../opensearch/indices/recovery/ForceSyncRequest.java
0.00% <0.00%> (ø)

...search/indices/recovery/RecoveryTargetHandler.java
100.00% <ø> (ø)

.../indices/recovery/RemoteRecoveryTargetHandler.java
89.55% <0.00%> (-10.45%)
:arrow_down:

...ch/indices/recovery/PeerRecoveryTargetService.java
52.56% <27.27%> (-0.93%)
:arrow_down:

...nsearch/index/shard/CheckpointRefreshListener.java
83.33% <50.00%> (-5.56%)
:arrow_down:

...rg/opensearch/indices/recovery/RecoveryTarget.java
72.48% <54.54%> (-1.40%)
:arrow_down:

...org/opensearch/index/shard/IndexShardTestCase.java
93.17% <55.55%> (-0.63%)
:arrow_down:

...search/indices/recovery/RecoverySourceHandler.java
76.96% <56.25%> (+0.41%)
:arrow_up:

...ation/OpenSearchIndexLevelReplicationTestCase.java
89.69% <77.77%> (-0.13%)
:arrow_down:

...in/java/org/opensearch/index/shard/IndexShard.java
70.21% <100.00%> (-0.06%)
:arrow_down:

... and 504 more

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

Windows precommit failure to memorry error. Refiring!
> Task :modules:lang-painless:forbiddenApisTest
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000795600000, 716177408, 0) failed; error='The paging file is too small for this operation to complete' (DOS error/errno=1455)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 716177408 bytes for Failed to commit area from 0x0000000795600000 to 0x00000007c0100000 of length 716177408.

@Bukhtawar @ashking94 : Please have a look in latest changes.

@Bukhtawar : Please feel free to leave any comment in case you have any concerns.

@dreamer-89  are you planning to backport this PR to 2.x?

@dreamer-89 are you planning to backport this PR to 2.x?

Yes @ashking94. I am planning to backport this along with the fix. Right now, I am testing the fix on actual cluster with setup you mentioned in #5848

@dreamer-89 are you planning to backport this PR to 2.x?

I am planning to backport this along with the fix. Right now, I am testing the fix on actual cluster with setup you mentioned in #5848

It is probably best to stay on top of the backports (even if for this case it means backporting a muted integration test). When you don't backport a change that touches the same files as a subsequent change that is to be backported, then the cherry-pick will fail and it will be harder for everyone. #5944 is a backport of a change that touched the new integration test introduced in this PR. I had to resolve a conflict on the cherry-pick to exclude the new file, but it also means when you do backport you'll need to manually apply the subsequent changes to that integration test that happened on main.

git fetch

Thank you @andrross for the comment and apologies for inconvenience. Backport was initially delayed to avoid the change in 2.5.0. I am backporting this change now.

Thank you @andrross for the comment and apologies for inconvenience. Backport was initially delayed to avoid the change in 2.5.0. I am backporting this change now.

@dreamer-89 are you planning to backport this PR to 2.x?

I am planning to backport this along with the fix. Right now, I am testing the fix on actual cluster with setup you mentioned in #5848

It is probably best to stay on top of the backports (even if for this case it means backporting a muted integration test). When you don't backport a change that touches the same files as a subsequent change that is to be backported, then the cherry-pick will fail and it will be harder for everyone. #5944 is a backport of a change that touched the new integration test introduced in this PR. I had to resolve a conflict on the cherry-pick to exclude the new file, but it also means when you do backport you'll need to manually apply the subsequent changes to that integration test that happened on main.

Thank you @andrross for the comment and apologies for inconvenience. Backport was initially delayed to avoid the change in 2.5.0. I am backporting this change now.


Fix scrum icons

Change icons of work item types and side panel entries according to these designs: https://redhat.invisionapp.com/share/WJGSJ17SMHN#/screens/290540724.
NOTE: Most of the changed files are new golden files. We didn't have golden files for listing work item types of the pre-known space templates before and that is what bloats this PR. The important change is this: https://github.com/fabric8-services/fabric8-wit/pull/2067/files#diff-f71e2910b3317a6a57a3a93edc987a7b.
Impediment (WIT):
Changed from fa fa-question to fa fa-stumbleupon
Product Backlog Item (WIT) / Backlog Items (Sidepanel entry):
Change from fa fa-question to pficon pficon-image
Epic (WIT) / Epics (Sidepanel entry):
Change from fa fa-bolt to fa fa-bullseye

[test]

@DhritiShikhar @baijum thank you for approving this PR. I just found out that I've overwritten the WIT IDs which I shouldn't have done. I will create a followup PR to not touch the WIT IDs...

@DhritiShikhar @baijum here it is: #2068


Failed to detect a master: Failed to parse data of unknown label 'json.info'

I have a problem
please tell me how to solve the problem.
Thank you very much!

hey @zhanghangchina : sorry for the delay in response.  I'm actually on vacation right now.  But that issue you are seeing is an error from mesos itself, and thus is not related to this project:
Trying to get '/mesos/json.info_0000000152' in ZooKeeper
Failed to detect a master: Failed to parse data of unknown label 'json.info'

I would ensure your Mesos setup is correct.  e.g., with my setup I have 3 masters here and here's what my /mesos dir has in ZooKeeper:
[json.info_0000000229, log_replicas, json.info_0000000231, json.info_0000000225]

You may need to clean up the ZK nodes in /mesos and try again.

Feel free to comment again, but I'm closing this issue as it's not a problem in this project.


Sub-Umbrella Issue: List of Glossary files to Localize in Bangla

 What is this issue for?
Hello Bengali localizers, we have a total of 146 glossary terms to localize into Bangla. I will separate some files for you, which are prioritized. Please make sure to localize them first.
How can I contribute?
All the information you need is covered  in this video. [ Remember our latest working branch is dev-1.31-bn.1 ]
For more information join us on slack
 Checklist to translate a term

Check that no one else has claimed the page in the comments below.

Comment below the page that you would like to localize, focus on one page per PR, at a time.
Example: I  am working on content/bn/<xyz.md>

Maintainers will add your username next to your selected page in the below checklist.

Fork this repo, make your localizations, and submit a pull request following the name convention [bn]  Localization of <file_name.md>.
Example: [bn] Localization of cloud_native_apps.md

While creating a new branch on your forked repo, make sure your
source repo : kubernetes/website
source branch: dev-1.31-bn.1

Maintain line break and line number as EN

Target branch dev-1.31-bn.1 when creating the PR

tag/ping a maintainer to make it easier to track progress

Also, when you create a PR, please make sure to add these line in the description.
Related issue : #45729

### First priority
- [ ] `content/en/docs/reference/glossary/controller.md` @aytullahdev
- [ ] `content/en/docs/reference/glossary/kube-scheduler.md` @aytullahdev

### Glossary file list
- [x] `content/en/docs/reference/glossary/addons.md` @sajjadrahman56
- [x] `content/en/docs/reference/glossary/admission-controller.md` @sajjadrahman56
- [x] `content/en/docs/reference/glossary/affinity.md` @sajjadrahman56
- [ ] `content/en/docs/reference/glossary/aggregation-layer.md` @Ashfinn
- [x] `content/en/docs/reference/glossary/annotation.md` @Ashfinn
- [ ] `content/en/docs/reference/glossary/api-eviction.md`
- [ ] `content/en/docs/reference/glossary/api-group.md` @MRH-Romit
- [x] `content/en/docs/reference/glossary/app-container.md` @MRH-Romit
- [ ] `content/en/docs/reference/glossary/application-architect.md` @MRH-Romit
- [ ] `content/en/docs/reference/glossary/application-developer.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/applications.md` @Ashfinn
- [ ] `content/en/docs/reference/glossary/approver.md` @Ashfinn
- [ ] `content/en/docs/reference/glossary/cadvisor.md`
- [ ] `content/en/docs/reference/glossary/certificate.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/cgroup.md`
- [ ] `content/en/docs/reference/glossary/cidr.md`
- [ ] `content/en/docs/reference/glossary/cla.md` @Ashfinn
- [ ] `content/en/docs/reference/glossary/cloud-controller-manager.md`
- [ ] `content/en/docs/reference/glossary/cloud-provider.md`
- [ ] `content/en/docs/reference/glossary/cluster-architect.md`
- [ ] `content/en/docs/reference/glossary/cluster-infrastructure.md`
- [ ] `content/en/docs/reference/glossary/cluster-operations.md`
- [ ] `content/en/docs/reference/glossary/cluster-operator.md`
- [x] `content/en/docs/reference/glossary/cluster.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/cncf.md`
- [ ] `content/en/docs/reference/glossary/cni.md`
- [ ] `content/en/docs/reference/glossary/code-contributor.md`
- [x] `content/en/docs/reference/glossary/configmap.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/container-env-variables.md`
- [ ] `content/en/docs/reference/glossary/container-lifecycle-hooks.md`
- [ ] `content/en/docs/reference/glossary/container-runtime-interface.md`
- [x] `content/en/docs/reference/glossary/container-runtime.md` @sajibAdhi
- [x] `content/en/docs/reference/glossary/container.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/containerd.md`
- [ ] `content/en/docs/reference/glossary/contributor.md`
- [x] `content/en/docs/reference/glossary/control-plane.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/controller.md` @aytullahdev
- [ ] `content/en/docs/reference/glossary/cri-o.md`
- [ ] `content/en/docs/reference/glossary/cri.md` @sadique21hs
- [ ] `content/en/docs/reference/glossary/cronjob.md`
- [ ] `content/en/docs/reference/glossary/csi.md`
- [ ] `content/en/docs/reference/glossary/customresourcedefinition.md`
- [x] `content/en/docs/reference/glossary/daemonset.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/data-plane.md` @SAShameem
- [x] `content/en/docs/reference/glossary/deployment.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/developer.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/device-plugin.md`
- [ ] `content/en/docs/reference/glossary/disruption.md`
- [ ] `content/en/docs/reference/glossary/docker.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/dockershim.md`
- [ ] `content/en/docs/reference/glossary/downstream.md`
- [ ] `content/en/docs/reference/glossary/downward-api.md`
- [ ] `content/en/docs/reference/glossary/dynamic-volume-provisioning.md`
- [ ] `content/en/docs/reference/glossary/endpoint-slice.md`
- [ ] `content/en/docs/reference/glossary/endpoint.md`
- [x] `content/en/docs/reference/glossary/ephemeral-container.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/etcd.md`
- [ ] `content/en/docs/reference/glossary/event.md`
- [ ] `content/en/docs/reference/glossary/eviction.md`
- [ ] `content/en/docs/reference/glossary/extensions.md`
- [ ] `content/en/docs/reference/glossary/feature-gates.md`
- [ ] `content/en/docs/reference/glossary/finalizer.md`
- [ ] `content/en/docs/reference/glossary/flexvolume.md`
- [ ] `content/en/docs/reference/glossary/garbage-collection.md` @sadique21hs
- [ ] `content/en/docs/reference/glossary/gateway.md` @sadique21hs
- [ ] `content/en/docs/reference/glossary/group-version-resource.md`
- [ ] `content/en/docs/reference/glossary/helm-chart.md`
- [ ] `content/en/docs/reference/glossary/horizontal-pod-autoscaler.md`
- [ ] `content/en/docs/reference/glossary/host-aliases.md`
- [ ] `content/en/docs/reference/glossary/image.md`
- [ ] `content/en/docs/reference/glossary/immutable-infrastructure.md`
- [x] `content/en/docs/reference/glossary/index.md` @sajibAdhi
- [ ] `content/en/docs/reference/glossary/ingress.md`
- [x] `content/en/docs/reference/glossary/init-container.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/istio.md`
- [x] `content/en/docs/reference/glossary/job.md` @AdiyanAbdurRahman
- [ ] `content/en/docs/reference/glossary/jwt.md`
- [ ] `content/en/docs/reference/glossary/kops.md`
- [x] `content/en/docs/reference/glossary/kube-apiserver.md` @MRH-Romit
- [ ] `content/en/docs/reference/glossary/kube-controller-manager.md`
- [ ] `content/en/docs/reference/glossary/kube-proxy.md`
- [ ] `content/en/docs/reference/glossary/kube-scheduler.md` @aytullahdev
- [ ] `content/en/docs/reference/glossary/kubeadm.md`
- [ ] `content/en/docs/reference/glossary/kubectl.md`
- [ ] `content/en/docs/reference/glossary/kubelet.md`
- [ ] `content/en/docs/reference/glossary/kubernetes-api.md` @sadique21hs
- [ ] `content/en/docs/reference/glossary/label.md`
- [ ] `content/en/docs/reference/glossary/limitrange.md`
- [ ] `content/en/docs/reference/glossary/logging.md`
- [ ] `content/en/docs/reference/glossary/managed-service.md`
- [ ] `content/en/docs/reference/glossary/manifest.md`
- [ ] `content/en/docs/reference/glossary/master.md`
- [ ] `content/en/docs/reference/glossary/member.md`
- [ ] `content/en/docs/reference/glossary/minikube.md`
- [x] `content/en/docs/reference/glossary/mirror-pod.md` @MRH-Romit
- [ ] `content/en/docs/reference/glossary/mixed-version-proxy.md`
- [ ] `content/en/docs/reference/glossary/name.md`
- [x] `content/en/docs/reference/glossary/namespace.md` @radiumSodium
- [ ] `content/en/docs/reference/glossary/network-policy.md`
- [ ] `content/en/docs/reference/glossary/node-pressure-eviction.md`
- [x] `content/en/docs/reference/glossary/node.md` @Ashfinn
- [x] `content/en/docs/reference/glossary/object.md` @asem-hamid
- [ ] `content/en/docs/reference/glossary/operator-pattern.md`
- [ ] `content/en/docs/reference/glossary/persistent-volume-claim.md`
- [ ] `content/en/docs/reference/glossary/persistent-volume.md`
- [ ] `content/en/docs/reference/glossary/platform-developer.md`
- [ ] `content/en/docs/reference/glossary/pod-disruption-budget.md`
- [x] `content/en/docs/reference/glossary/pod-disruption.md` @asem-hamid
- [ ] `content/en/docs/reference/glossary/pod-lifecycle.md`
- [ ] `content/en/docs/reference/glossary/pod-priority.md`
- [ ] `content/en/docs/reference/glossary/pod-security-policy.md`
- [x] `content/en/docs/reference/glossary/pod.md` @asem-hamid
- [ ] `content/en/docs/reference/glossary/preemption.md`
- [ ] `content/en/docs/reference/glossary/probe.md` @sadique21hs
- [ ] `content/en/docs/reference/glossary/proxy.md` @awwroni
- [ ] `content/en/docs/reference/glossary/qos-class.md`
- [ ] `content/en/docs/reference/glossary/quantity.md`
- [ ] `content/en/docs/reference/glossary/rbac.md`
- [ ] `content/en/docs/reference/glossary/replica-set.md`
- [ ] `content/en/docs/reference/glossary/replica.md`
- [x] `content/en/docs/reference/glossary/replication-controller.md` @asem-hamid
- [ ] `content/en/docs/reference/glossary/resource-quota.md`
- [ ] `content/en/docs/reference/glossary/reviewer.md`
- [x] `content/en/docs/reference/glossary/secret.md` @SAShameem
- [ ] `content/en/docs/reference/glossary/security-context.md`
- [ ] `content/en/docs/reference/glossary/selector.md`
- [x] `content/en/docs/reference/glossary/service-account.md` @Ashfinn
- [ ] `content/en/docs/reference/glossary/service-catalog.md`
- [ ] `content/en/docs/reference/glossary/service.md`
- [ ] `content/en/docs/reference/glossary/shuffle-sharding.md`
- [x] `content/en/docs/reference/glossary/sidecar-container.md` @sajibAdhi
- [ ] `content/en/docs/reference/glossary/sig.md`
- [ ] `content/en/docs/reference/glossary/spec.md`
- [x] `content/en/docs/reference/glossary/statefulset.md` @sajjadrahman56
- [ ] `content/en/docs/reference/glossary/static-pod.md`
- [ ] `content/en/docs/reference/glossary/storage-class.md`
- [ ] `content/en/docs/reference/glossary/sysctl.md`
- [ ] `content/en/docs/reference/glossary/taint.md`
- [ ] `content/en/docs/reference/glossary/toleration.md`
- [ ] `content/en/docs/reference/glossary/uid.md`
- [ ] `content/en/docs/reference/glossary/upstream.md`
- [ ] `content/en/docs/reference/glossary/userns.md`
- [ ] `content/en/docs/reference/glossary/volume-plugin.md`
- [x] `content/en/docs/reference/glossary/volume.md` @asem-hamid
- [ ] `content/en/docs/reference/glossary/wg.md`
- [x] `content/en/docs/reference/glossary/workload.md` @Ashfinn

/language bn

/sig docs
/area localization

I am working on content/en/docs/reference/glossary/addons.md

content/en/docs/reference/glossary/namespace.md

I am working on
content/en/docs/reference/glossary/namespace.md

I am working on content/en/docs/reference/glossary/job.md

i am working on content/en/docs/reference/glossary/admission-controller.md

I am working on content/en/docs/reference/glossary/cluster.md

I am working on
content/en/docs/reference/glossary/deployment.md

I am working on :
content/en/docs/reference/glossary/container.md

I am working on
content/en/docs/reference/glossary/init-container.md

i am working on en/docs/reference/glossary/affinity.md

I am working on
content/en/docs/reference/glossary/ephemeral-container.md

i am working on
content/en/docs/reference/glossary/statefulset.md

working on content/en/docs/reference/glossary/controller.md

@aytullahdev  Join our Slack channel to connect with us .

I am working on content/en/docs/reference/glossary/workload.md

working on content/en/docs/reference/glossary/kube-scheduler.md

working on content/en/docs/reference/glossary/kube-scheduler.md

@aytullahdev
try this link

I am working on content/en/docs/reference/glossary/node.md

I am working on
content/en/docs/reference/glossary/secret.md

I am working on content/en/docs/reference/glossary/annotation.md

@SAShameem  Join our Slack channel to connect with us .

I'm working on,
content/en/docs/reference/glossary/configmap.md

I am working on, content/en/docs/reference/glossary/gateway.md

@sadique21hs  check out this comment .
also Join our Slack channel to connect with us .

I'm working on,
content/en/docs/reference/glossary/garbage-collection.md

i am working on content/en/docs/reference/glossary/mirror-pod.md

I am working on content/en/docs/reference/glossary/control-plane.md

I'm working on content/en/docs/reference/glossary/daemonset.md

@SAShameem Please fix your old PRs first

i'm working on content/en/docs/reference/glossary/app-container.md

I am working on content/en/docs/reference/glossary/service-account.md

@SAShameem Please fix your old PRs first

@asem-hamid vaiya, ki fix kora lagbe ektu jodi bolten. Thik vabe bujhte parinai bisoyta. ektu jodi guide korten.  first e branch e ektu vul koresilam segula delete kore new branch e sob abar koresi. thanks in advance.

I am working on content/en/docs/reference/glossary/aggregation-layer.md

You need to submit the pull request

I have submitted the pull request, please check

I am working on content/en/docs/reference/glossary/cla.md

I'm Working on  content/en/docs/reference/glossary/api-group.md

I'm Working on content/en/docs/reference/glossary/application-architect.md

I  am working on content/en/docs/reference/glossary/applications.md

I am working on content/en/docs/reference/glossary/application-developer.md

I am working on,
content/en/docs/reference/glossary/kubernetes-api.md

I am working on content/en/docs/reference/glossary/approver.md

i am working on content/en/docs/reference/glossary/probe.md

@sadique21hs  did you submit PR for glossary/garbage-collection.md ?

@sadique21hs  did you submit PR for glossary/garbage-collection.md ?

Yes

@sadique21hs  please share the PR link .

@sadique21hs please share the PR link .

https://github.com/kubernetes/website/pull/46165

I'm working on content/en/docs/reference/glossary/certificate.md

I am working on content/en/docs/reference/glossary/proxy.md

@awwroni  Join our Slack channel to connect with us .

I am working on content/en/docs/reference/glossary/data-plane.md

I am working on content/en/docs/reference/glossary/developer.md

I am working on content/en/docs/reference/glossary/docker.md

@SAShameem Hi , let me know (here) if you are available . After finishing glossary/docker.md

i am working on content/en/docs/reference/glossary/cri.md

i am working on content/en/docs/reference/glossary/application-architect.md

/hold
Hello contributors,
As you may know, the first version of Kubernetes in Bangla is now live!
For this reason, the dev-1.24-bn.1 branch is being deprecated. Until we get a new branch, we can hold off on localizing glossary terms.
There is still plenty of scope to update in our first version. Feel free to check out our website and create an issue if you find any small typos or big mistakes.
Kubernetes in Bangla : https://kubernetes.io/bn/

/hold

/remove-lifecycle stale

Hello Contributors,
As you may know, the first version of Kubernetes in Bangla has been live since May 2024!
We are now ready to start our work on the second version of the Kubernetes Bangla documentation.
Our latest working branch is dev-1.31-bn.1.
New Tracking Issue:
Our new tracking issue is #47747. Please refer to this issue for updates and progress.
PR Guidelines:
When you create a new branch on your forked repo, make sure it’s based on the latest dev-1.31-bn.1 branch.
Source Repository: kubernetes/website
Source Branch: dev-1.31-bn.1
Target Branch: dev-1.31-bn.1 (when creating the PR)
Also, when submitting a PR, please include the following line in the description:
Related issue: #45729 (for glossary files)
Kubernetes in Bangla: https://kubernetes.io/bn/
Happy contributing!

i am working on content/en/docs/reference/glossary/cloud-provider.md

I  am working on content/en/docs/reference/glossary/api-eviction.md

i want to work on
content/en/docs/reference/glossary/cgroup.md

i want to work on
content/en/docs/reference/glossary/cluster-architect.md

@Noblesse013
Please checkout this comment first  .

I am working on content/en/docs/reference/glossary/cla.md

I am working on content/en/docs/reference/glossary/approver.md

i am working on content/en/docs/reference/glossary/contributor.md

@Noblesse013 and others
Please take one task at a time. After submitting a PR for the current task, you can proceed with the next one.

i am working on content/en/docs/reference/glossary/uid.md

I am working on content/en/docs/reference/glossary/api-group.md

i am working on content/en/docs/reference/glossary/cluster-infrastructure.md

I am working on content/en/docs/reference/glossary/application-architect.md

I am working on content/en/docs/reference/glossary/cadvisor.md

I am working on content/en/docs/reference/glossary/cidr.md

I am working on content/en/docs/reference/glossary/code-contributor.md

I am working on content/en/docs/reference/glossary/eviction.md

I am working on content/en/docs/reference/glossary/managed-service.md

I am working on content/en/docs/reference/glossary/reviewer.md

@Noblesse013 Please take one task at a time. After submitting a PR for the current task, you can proceed with the next one.

I am working on content/en/docs/reference/glossary/application-developer.md

I am working on content/en/docs/reference/glossary/certificate.md

I am working on content/en/docs/reference/glossary/data-plane.md

I am working on content/en/docs/reference/glossary/developer.md

I am working on content/en/docs/reference/glossary/docker.md

I am working on content/en/docs/reference/glossary/cluster-operator.md

I am working on content/en/docs/reference/glossary/cni.md

Thanks for contributing, @AdiyanAbdurRahman! You have been contributing for a while now, so I recommend you check out some bigger content from here . The glossary is  for absolute beginners.

Hi @Ashfinn  and @Noblesse013  .  Thanks for contributing! You have been contributing for a while now, so I recommend you check out some bigger content from https://github.com/kubernetes/website/issues/47747 (after finishing taken task) . The glossary is for absolute beginners.


Build failure: rPackages.terra likely due to pkg-config on Darwin

Steps To Reproduce
Try to build rPackages.terra on Darwin (also affects other packages, such as rPackages.sf.
Build log
building '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/bl6pnawvyhfd7yv45s2vlchsj556n58h-terra_1.7-78.tar.gz
source root is terra
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file terra/MD5
Running phase: patchPhase
Running phase: configurePhase
Running phase: buildPhase
Running phase: checkPhase
Running phase: installPhase
During startup - Warning messages:
1: Setting LC_CTYPE failed, using "C"
2: Setting LC_TIME failed, using "C"
3: Setting LC_MESSAGES failed, using "C"
4: Setting LC_MONETARY failed, using "C"
* installing *source* package 'terra' ...
** package 'terra' successfully unpacked and MD5 sums checked
** using staged installation
configure: CC: clang
configure: CXX: /nix/store/bkhpl7q6fzghx08zzrmcckh12rrnnl29-clang-wrapper-16.0.6/bin/c++ -std=gnu++17
checking for gdal-config... /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/bin/gdal-config
checking gdal-config usability... yes
configure: GDAL: 3.9.2
checking GDAL version >= 2.0.1... yes
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether clang accepts -g... yes
checking for clang option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for gdal.h... yes
checking GDAL: linking with --libs only... yes
checking GDAL: /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/share/gdal/pcs.csv readable... no
checking GDAL: checking whether PROJ is available for linking:... yes
checking GDAL: checking whether PROJ is available for running:... yes
configure: GDAL: 3.9.2
configure: pkg-config proj exists, will use it
configure: using proj.h.
Package libtiff-4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libtiff-4.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libtiff-4', required by 'proj', not found
configure: PROJ: 9.4.1
checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
configure: error: libproj or sqlite3 not found in standard or given locations.
ERROR: configuration failed for package 'terra'
* removing '/nix/store/nbwfdhv18l9c3k2zby6ni880x51py2gl-r-terra-1.7-78/library/terra'
error: builder for '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv' failed with exit code 1;
       last 25 log lines:
       > checking for stdlib.h... yes
       > checking for string.h... yes
       > checking for inttypes.h... yes
       > checking for stdint.h... yes
       > checking for strings.h... yes
       > checking for sys/stat.h... yes
       > checking for sys/types.h... yes
       > checking for unistd.h... yes
       > checking for gdal.h... yes
       > checking GDAL: linking with --libs only... yes
       > checking GDAL: /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/share/gdal/pcs.csv readable... no
       > checking GDAL: checking whether PROJ is available for linking:... yes
       > checking GDAL: checking whether PROJ is available for running:... yes
       > configure: GDAL: 3.9.2
       > configure: pkg-config proj exists, will use it
       > configure: using proj.h.
       > Package libtiff-4 was not found in the pkg-config search path.
       > Perhaps you should add the directory containing `libtiff-4.pc'
       > to the PKG_CONFIG_PATH environment variable
       > Package 'libtiff-4', required by 'proj', not found
       > configure: PROJ: 9.4.1
       > checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
       > configure: error: libproj or sqlite3 not found in standard or given locations.
       > ERROR: configuration failed for package 'terra'
       > * removing '/nix/store/nbwfdhv18l9c3k2zby6ni880x51py2gl-r-terra-1.7-78/library/terra'
       For full logs, run 'nix-store -l /nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv'.
error: build of '/nix/store/72afakncr7isb6c0s9n3fmq0976jvr4n-r-languageserver-0.3.16.drv', '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv' failed

Additional context
Build succeeds on Linux, and also succeeds on Darwin with following fix:
 terra = old.terra.overrideAttrs (attrs: {
                configureFlags = [
                    "--with-proj-lib=${pkgs.lib.getLib pkgs.proj}/lib"
                ];
            });

I PR'ed the fix, but it turns out that the issue is likely related to pkg-config, see, for context: https://github.com/NixOS/nixpkgs/pull/344498#pullrequestreview-2334701617
I don't have Apple hardware, so it's difficult for me to work on this.
Notify maintainers
pkg-config has no maintainers, so I'm pinging the last person to touch it @sevanspowell
Metadata
I can't run the below, because as explained above, I don't have the hardware.
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Add a :+1: reaction to issues you find important.

--- a/pkgs/development/libraries/proj/default.nix
+++ b/pkgs/development/libraries/proj/default.nix
@@ -49,6 +49,12 @@ stdenv.mkDerivation (finalAttrs: {
     "-include cstdint"
   ];

+  postPatch = ''
+    # These should be proper Requires, using the header needs their headers
+    substituteInPlace proj.pc.in \
+      --replace 'Requires.private' 'Requires'
+  '';
+

Might help.

Steps To Reproduce
Try to build rPackages.terra on Darwin (also affects other packages, such as rPackages.sf.
Build log
building '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/bl6pnawvyhfd7yv45s2vlchsj556n58h-terra_1.7-78.tar.gz
source root is terra
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file terra/MD5
Running phase: patchPhase
Running phase: configurePhase
Running phase: buildPhase
Running phase: checkPhase
Running phase: installPhase
During startup - Warning messages:
1: Setting LC_CTYPE failed, using "C"
2: Setting LC_TIME failed, using "C"
3: Setting LC_MESSAGES failed, using "C"
4: Setting LC_MONETARY failed, using "C"
* installing *source* package 'terra' ...
** package 'terra' successfully unpacked and MD5 sums checked
** using staged installation
configure: CC: clang
configure: CXX: /nix/store/bkhpl7q6fzghx08zzrmcckh12rrnnl29-clang-wrapper-16.0.6/bin/c++ -std=gnu++17
checking for gdal-config... /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/bin/gdal-config
checking gdal-config usability... yes
configure: GDAL: 3.9.2
checking GDAL version >= 2.0.1... yes
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether clang accepts -g... yes
checking for clang option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for gdal.h... yes
checking GDAL: linking with --libs only... yes
checking GDAL: /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/share/gdal/pcs.csv readable... no
checking GDAL: checking whether PROJ is available for linking:... yes
checking GDAL: checking whether PROJ is available for running:... yes
configure: GDAL: 3.9.2
configure: pkg-config proj exists, will use it
configure: using proj.h.
Package libtiff-4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libtiff-4.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libtiff-4', required by 'proj', not found
configure: PROJ: 9.4.1
checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
configure: error: libproj or sqlite3 not found in standard or given locations.
ERROR: configuration failed for package 'terra'
* removing '/nix/store/nbwfdhv18l9c3k2zby6ni880x51py2gl-r-terra-1.7-78/library/terra'
error: builder for '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv' failed with exit code 1;
       last 25 log lines:
       > checking for stdlib.h... yes
       > checking for string.h... yes
       > checking for inttypes.h... yes
       > checking for stdint.h... yes
       > checking for strings.h... yes
       > checking for sys/stat.h... yes
       > checking for sys/types.h... yes
       > checking for unistd.h... yes
       > checking for gdal.h... yes
       > checking GDAL: linking with --libs only... yes
       > checking GDAL: /nix/store/zj7j809wk0c5iv5s7fsd32fnhh6185vr-gdal-3.9.2/share/gdal/pcs.csv readable... no
       > checking GDAL: checking whether PROJ is available for linking:... yes
       > checking GDAL: checking whether PROJ is available for running:... yes
       > configure: GDAL: 3.9.2
       > configure: pkg-config proj exists, will use it
       > configure: using proj.h.
       > Package libtiff-4 was not found in the pkg-config search path.
       > Perhaps you should add the directory containing `libtiff-4.pc'
       > to the PKG_CONFIG_PATH environment variable
       > Package 'libtiff-4', required by 'proj', not found
       > configure: PROJ: 9.4.1
       > checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
       > configure: error: libproj or sqlite3 not found in standard or given locations.
       > ERROR: configuration failed for package 'terra'
       > * removing '/nix/store/nbwfdhv18l9c3k2zby6ni880x51py2gl-r-terra-1.7-78/library/terra'
       For full logs, run 'nix-store -l /nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv'.
error: build of '/nix/store/72afakncr7isb6c0s9n3fmq0976jvr4n-r-languageserver-0.3.16.drv', '/nix/store/dza9i9zwxmnzzbwb0xchdksa9ari8dkw-r-terra-1.7-78.drv' failed

Additional context
Build succeeds on Linux, and also succeeds on Darwin with following fix:
 terra = old.terra.overrideAttrs (attrs: {
                configureFlags = [
                    "--with-proj-lib=${pkgs.lib.getLib pkgs.proj}/lib"
                ];
            });

I PR'ed the fix, but it turns out that the issue is likely related to pkg-config, see, for context: #344498 (review)
I don't have Apple hardware, so it's difficult for me to work on this.
Notify maintainers
pkg-config has no maintainers, so I'm pinging the last person to touch it @sevanspowell
Metadata
I can't run the below, because as explained above, I don't have the hardware.
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Add a 👍 reaction to issues you find important.

% nix-shell -p nix-info --run "nix-info -m"
these 2 paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
  /nix/store/i17n43d9h64nzp5mjwd8zlj00i1zpab0-DarwinTools-1
  /nix/store/g16nnzwy639cmbhcggrwniba70fympah-nix-info
copying path '/nix/store/i17n43d9h64nzp5mjwd8zlj00i1zpab0-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/g16nnzwy639cmbhcggrwniba70fympah-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-darwin"`
 - host os: `Darwin 21.6.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.24.8`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

+  postPatch = ''
+    # These should be proper Requires, using the header needs their headers
+    substituteInPlace proj.pc.in \
+      --replace 'Requires.private' 'Requires'
+  '';

Thanks for the pointer! Unfortunately that doesn’t seem to cut it. I’ve add the lines here: https://github.com/b-rodrigues/nixpkgs/blob/812fef336e2c1eacccba4e893e0338e65adb3e21/pkgs/development/libraries/proj/default.nix#L52
and tried to build the package from this branch, but still get the same error.

No sorry, that actually did the trick for rPackages.terra! It now builds successfully on linux and macOS with this patch. I thought it didn’t work because I didn’t read the error message carefully enough: what fails now is another package: rPackages.sf which is closely related to rPackages.terra (I was trying to build them all instead of individually, my bad). I thought that sf and terra might need the same fix as they seemed to have the same issue related to proj, but sf seems to require another fix to build successfully on darwin on top of the patch for proj:
checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
configure: error: libproj or sqlite3 not found in standard or given locations.
ERROR: configuration failed for package ‘sf’
* removing ‘/nix/store/090rqzxk9dlm3001ksvsnsrp6mh6nsvq-r-sf-1.0-16/library/sf’
error: builder for '/nix/store/80gp841mb76m9rx208l4nxcmppkqpknc-r-sf-1.0-16.drv' failed with exit code 1;
       last 25 log lines:
       > checking whether the compiler supports GNU C... yes
       > checking whether clang accepts -g... yes
       > checking for clang option to enable C11 features... none needed
       > checking for stdio.h... yes
       > checking for stdlib.h... yes
       > checking for string.h... yes
       > checking for inttypes.h... yes
       > checking for stdint.h... yes
       > checking for strings.h... yes
       > checking for sys/stat.h... yes
       > checking for sys/types.h... yes
       > checking for unistd.h... yes
       > checking for gdal.h... yes
       > checking GDAL: linking with --libs only... yes
       > checking GDAL: /nix/store/vdl5cxnbm7n02kf9mn3417glarvik1r6-gdal-3.8.5/share/gdal/pcs.csv readable... no
       > checking GDAL: checking whether PROJ is available for linking:... yes
       > checking GDAL: checking whether PROJ is available for running:... yes
       > configure: GDAL: 3.8.5
       > configure: pkg-config proj exists, will use it
       > configure: using proj.h.
       > configure: PROJ: 9.4.1
       > checking PROJ: checking whether PROJ and sqlite3 are available for linking:... no
       > configure: error: libproj or sqlite3 not found in standard or given locations.
       > ERROR: configuration failed for package ‘sf’
       > * removing ‘/nix/store/090rqzxk9dlm3001ksvsnsrp6mh6nsvq-r-sf-1.0-16/library/sf’
       For full logs, run 'nix log /nix/store/80gp841mb76m9rx208l4nxcmppkqpknc-r-sf-1.0-16.drv'.
error: 1 dependencies of derivation '/nix/store/fnd6sjisbfzambjmnpwd3pc602b68cnz-nix-shell.drv' failed to build

could it be something with sqlite3?

Nope that wasn't it... so to summarize, for now the fix suggested by @tomberek works for rPackages.terra but rPackages.sf fails. Trying the same fix on libgeotiff, a dependency of rpackages.sf doesn't help

So it turns out the issue was in the configure script of rPackages.terra  see https://github.com/NixOS/nixpkgs/pull/344498#issuecomment-2407292524
the original fix I PR'd turned out to be the good one after all, thanks for the help!


Rewording and Reworking 8Values From The Ground Up

So I have been thinking of some ways to help improve the quality of the test and solve some commonly seen complains about it.
Firstly is the perceived bias many say they see in the test. Most individuals I've heard criticism from complain of a left-leaning bias in the test. I struggled to find a way to easily quantify this supposed bias, until I found a rather simple, yet elegant solution. Clicking the same answer on each question, for example "Strongly Agree", the final results should roughly even out to be 50/50 in each category, or lose to it. This is because in a properly balanced test, a survey topic should be approached by asking two questions. Each question is the opposite of the other, meaning that if answered the same way, the results would cancel out to a net-zero change in the final results for the survey. This is an easy way to tell what bias a survey might have, and how badly it is skewed in one direction or another. As an example, I used this method on the Political Compass test and you can see the results below:

As you can see, the economic axis of the graph came out to be exactly 0, but the authoritarian/libertarian axis has an obvious, and rather large, skew towards the libertarian end of the compass.
Following this procedure, I used this method on the 8Values test, selecting "Strongly agree" too all questions, and you can see the results below:

You can see that the diplomatic axis is decently balanced, at only a little over 1 percentage point difference. The societal axis, though a few percentage points, is within what I would consider to be an acceptable margin or error. The Economic and Civil axises though are far beyond what a margin of error should cause. It's obvious that there is an imbalance of questions for those two parts that leads to a very large, 20 point gap total between the two sides of each axis. (Please note that selecting all "Strong Disagree" to the questions will result in a mirror opposite of the results shown above, with the same numbers being reversed on the axis scales.)
So firstly, we need to go back and we work the questions to include two for each basic idea being asked, each having an opposite view from the other. For example, one question could be, "I support single-payer, universal healthcare" while the second one could be "I do not support government welfare for medical needs". This suits the opposing view for the same topic, and also insure that people who fall below the "Universal healthcare", but above "No Welfare" have an option to click. This also means that there will always need to be an even number of questions in the test, though I don't see why that should be an issue.
Secondly, we need to get rid of questions that contain double negatives. Double negatives might be ok in grammar, but in a survey they will lead to confusion about what option to pick. For example, instead of saying, "No authority should be left unquestioned", say, "All authority should be questioned", as was mentioned in another issue thread #64
Finally, I think one other thing that would go a long way towards helping to ease fears of bias is to have the questions be randomized each time a user takes the test. This shouldn't be too terribly hard to achieve with just some JavaScript, an Array, and a random number generator. This would help make the test less predictable and more unique each time someone takes it.
These are just a few of my suggestions to help make the 8Values test truly great! Let me know what y'all think of these suggestions, or if you have any additions to add to them! :smiley:

Definitely look for some input from the other Contributors on this topic! @TristanBomb, @elifoster, @gervasiocaj, and any others wanna jump in and offer some input on this idea? :slightly_smiling_face:

I definitely agree with most of the changes you suggest, but I also dispute that "what happens when you agree to everything" is a sure-fire way to test the bias of a test. A more insidious issue is questions might very well be worded in a way that lends users to respond in a certain way; I think one way to resolve this is to just have multiple users writing the questions. As the only one to write questions (so far), I've tried to avoid letting this bias the test as much as I can, but I can't guarantee that I was successful. Randomizing the order of questions probably won't affect the bias of the test, but it might still be a good idea.
I'd also like to comment on the ways I think the test might be biased. This isn't based on hard data or anything, but just what I've observed. I think the economic axis definitely reports values left of the "true value," but I actually think the authority axis is fine. Yes, clicking agree to everything resorts in a more authoritarian result, but most people are usually inclined to click the more liberty-oriented responses, so I reckon it balances out. The diplomatic axis, as you state, is fine; I'm not really sure about the society axis.
Finally, while we're discussing complete reworks, I/we/someone really needs to draft a better ideology matching system, because frankly, the current one just doesn't work very well.

I will admit, that isn't an aspect I thought about. However, you are entirely correct that even though the individual axis's are evened out, they could still be skewed one way or another. However, this might be hard to fully find as it may not be immediately obvious from the outside.  Even still, just doing what I did can show more obvious preexisting bias that is in the test.
With the randomization, this would help cut any preexisting bias an individual might have coming into the test if they found the test through someone else, like Sargon or Esoteric Entity. This will help people to read the questions and answer for themselves, instead of falling back on what someone else might have done.
I do agree as well that the ideology matching system does need some help. For one, it's far to exact! For example, my results show Libertarian Capitalist, but I can say honestly that the Civil Axis is exactly one number away from making me an Ultra-Capitalist. If I answered one question even just slightly different, I would get an entirely different result. What might be an optimal substitute to this exact system would be maybe a list or graph showing what the top three most related ideologies are that someone matches. So for me It'd probably Libertarian Capitalist, Ultra Capitalist, and maybe something like Anarcho-Capitalist, or whatever the next best alternative is for my axis matches.
Another issue is presented though, I'm actually not a Libertarian, but instead I'm an Objectivist. While technically Libertarian Capitalist is decently close to Objectivism, they are not the same. For me, the most important graphs would be the Market and Civil axis. The Societal axis is less important, but I'd imagine it'd trend towards being progressive, as you can see in the image above. The Diplomatic axis could prove troublesome though. Many Objectivists might place themselves in the "peaceful" category. However, when that's on a scale that includes Internationalism at the far end, that idea sorta falls apart. So I don't honestly know how to handle the Diplomatic axis when trying to determine something like Objectivist, or even Libertarian Capitalism for that matter.
These are things that need to be sorted out in due time. How to sort out some of these issues is beyond my scope of reasoning at this point. However, I think some things can be fixed decently easy! Making the test less biased, or at least seem less biased, would go a long ways towards fixing some of the major griefs with it I heard! As for the ideology matching, is there any kind of list containing all of the major political ideologies you could use as a blueprint to make the list/graph style of ideology matching for people? That might save you a lot of work when remaking that!

Any update on that?
If help is needed, I wouldn't mind.

I created a pull request to fix it slightly ages ago.

It's not referenced it seems.

https://github.com/8values/8values.github.io/pull/70

It's still open tho :/.

I know because nobody has bothered to look into it in-depth/give a full opinion.


Contrary to documentation, loading a file from JSON performs validation

I noticed this when trying to load an ACH file from JSON using file.UnmarshalJSON.
The documentation states that the resulting file should be validated, as it may be invalid.
https://github.com/moov-io/ach/blob/85a464f43f8b32f8e19cbe8767f764e3ba431959/file.go#L98-L103
However, before returning a successful file, validation is called resulting in an error:
https://github.com/moov-io/ach/blob/85a464f43f8b32f8e19cbe8767f764e3ba431959/file.go#L166-L168
I'd like to be able to validate my parsed file on my own after unmarshalling from JSON, and preferably without duplicating the behavior already present. My recommendation is to remove the validation, or at a minimum, update the documentation to more specifically address the behavior of the function.

I can see where removing this check helps to keep errors from unmarshaling and validation isolated. It'd need to be in a new minor release.
return file, err was meant to return the entire file even if Validation errors occurred, but it's non-trivial to detect which type of error was returned.

I can see where removing this check helps to keep errors from unmarshaling and validation isolated. It'd need to be in a new minor release.
return file, err was meant to return the entire file even if Validation errors occurred, but it's non-trivial to detect which type of error was returned.


Bug 2047779: Never degrade cluster on storage policy syncResult

Only degrade if storage class creation fails because of API error
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2047779

/lgtm

/retest

/override ci/prow/e2e-vsphere
I can see the job succeeded, only etcd alerted on slow disk. This PR does not affect it.


[SUGGESTION] More uses for creosote oil

Vanilla furnace fuel
Immersive Technology liquid boiler fuel
Making torches efficiently (maybe 16 or 32 per craft using a bucket)
IE lantern crafting recipe instead of the default glowstone, to basically simulate oil lamps

Nah


recieving item in child Dialog from context.Forward(T item)

var dialog = new EchoDialog();
await context.Forward(dialog, DialogDone, item, CancellationToken.None);

the forward method uses the IPostToBot.PostAsync(T item) method to post an item to the child dialog.
But i'm not able to find the item in my new dialog:
async Task IDialog<object>.StartAsync(IDialogContext context)
        {
            context.Wait(next);
        }

You can Wait() to get the message.
Forward() puts the message on the BotContext and eventually calls StartAsync on the dialog you passed, so technically you could read the message directly off of the IDialogContext, but I recommend doing context.Wait() and then reading the message from the method you pass into the Wait().

public async Task StartAsync(IDialogContext context)
{
    //Since a message is passed along when using IDialogContext.Forward(), read it first
    context.Wait(MessageReceivedAsync);
}

async Task MessageReceivedAsync(IDialogContext context, IAwaitable<IMessageActivity> message)
{
    var msg = await message;
    //Do stuff with msg here
}

that sounds logic, and i also get into MessageReceivedAsync.
But when I try to await the message, i get a
Exception: Stack is empty
[File of type 'text/plain']
I tried to access my Dialog with different types of Dialogs and i also changed the generic Type of IAwaitable, but it is always the same, i cannot acces the message.

The primary purpose of Forward is to reuse a child dialog that is "reactive", where the child dialog (in StartAsync) waits for a T with some ResumeAfter handler.  In particular, if you have a child dialog that waits for a message (e.g. the LuisDialog), you can decide to forward the incoming message already received by some parent dialog by calling LuisDialog.
So it's much more common that T is an IMessageActivity, because almost nobody writes dialogs that wait for other types.
So @fingejo you would "find the item" in the first ResumeAfter handler (e.g. MessageReceived) that is scheduled by the StartAsync.
(most people just use Call directly)

@willportnoy thankyou for your detailed explanation. I was able to figure out my problem with your explanation
That is my solution now:
public async Task Bildersuche(IDialogContext context, IAwaitable<IMessageActivity> argument, LuisResult result)
        {
            //BilderDialog.lresult = result;
            var a = await argument;
            a.Text = result.Entities[0].Entity;
            var dialog = new BilderDialog();
            await context.Forward(dialog, DialogDone, a, CancellationToken.None);

        }

public async Task bilder(IDialogContext context, IAwaitable<IMessageActivity> argument)
        {
            string b = "";
            var c = await argument;

I am now able to recieve my item. It had to be an IMessageActivity. So i just cloned the information from LuisDialog i needed into it.

I would like to receive a custom type T. The root dialogue calls dialog 1 and then calls dialogue 2 passing in the value returned by dialog 1. I  called
context.Wait(MessageReceivedAsync);
but I get an unexpected type exception when await'ing for that "ReturnedValue".
What am I missing?


Out of memory in subviews

Hello,
I'm using subviews and I get an out of memory when I have big view data objects.
The problem is that even I dont need objects in the subview, the object get loaded into memory a second time at the subview call.
In the view:
$data = array();
$data["categoriesAndFields"] = $categoriesAndFields;
$data["properties"] = $properties;
get_instance()->load->view($view, $data);

The in the Loader.php class, there is the following:
if (is_array($_ci_vars))
{
	$this->_ci_cached_vars = array_merge($this->_ci_cached_vars, $_ci_vars);
}
extract($this->_ci_cached_vars);

The problem is my $this->_ci_cached_vars contains a big array with 55000 values. This was loaded a first time through  $_ci_vars var and this extract function, it passed.
But for the subview, it is now in $this->_ci_cached_vars and extracts throws outofmemory.
Do I miss something or there is here a way to improve memory management ?
PS : Do I need to call get_instance()->load->clear_vars(); before each subview call if I donc need parent variables ?

Please raise support questions on forum.codeigniter.com
We use github issues for bug tracking.

I was seeing this as a memory management bug or evolution...


Add support for disabling routes

I used this to turn down a hostname in my dev environment just now, which uncovered at least one issue (in my first draft, it's covered here), so pretty confident this works!


not working on ios 8.3

token seems not getting on ios 8.3

+1

+1
Facing same issue

was facing same issue, but it worked for me. make the json which you pass as payload is not a nested json object

Same problem here.below is the code I am using in mobile app. there is no error message but the the call back function never trigger, I didn't get the device token.
pushNotification.register(
APNsuccessHandler,
APNerrorHandler,
{
"badge": "true",
"sound": "true",
"alert": "true",
"ecb": "onNotificationAPN"
});

+1
have the same problem
the application not show in the notifications list

I experiment a successful registration (enabling notifications) but the first time the token isn't retrieved...
Anyone experienced something like this ?

+1

+1

i solved it by deleting the platform and create it again
ionic platform rm ios
ionic platform add ios

I wrote a post here: http://stackoverflow.com/questions/30648351/ngcordova-pushplugin-does-not-work-well-with-ios-8-3

+1


Allow parsing of fenced code blocks inside lists

While working with the Mudblazor.Markdown package, I discovered that, if a block of Markdown text being parsed included a fenced code block within a list, the code block would not be rendered in the output.  This pull request is designed to correct this issue.
The following Markdown can be used as an example:

To prevent the warning message regarding the deprecation of the mysql_native_password plugin from being logged, you have a couple of options:
Option 1: Update User Authentication Method:

Connect to your MySQL server using a MySQL client, such as the mysql command-line tool:
mysql -u username -p

Once connected, run the following command to alter the user's authentication method:
ALTER USER 'username'@'hostname' IDENTIFIED WITH caching_sha2_password;

Replace 'username' with the actual username and 'hostname' with the appropriate hostname or IP address. If you want to update for all users, replace 'username'@'hostname' with '*'@'%'.

Repeat this process for each user on your MySQL server.

Will be fixed in https://github.com/MyNihongo/MudBlazor.Markdown/pull/236


Reduce file size: cadmium-playercore-6.0033.414.911 from 7MB to 2MB…

Reduce file size: cadmium-playercore-6.0033.414.911 from 7MB to 2MB
Using https://jscompress.com
Highly recommend feature updates to do so as well

why do it?
can you tell me why it needs to be reduced?

I think there are 3 reasons:
1: Smaller size runs fast
2: People tend to use smaller size packages.
4: The code seems to be compressed before, it's not readable, so recompressing it should be reasonable