unexpected colour overlay when revealing active file in explorer

VSCode Version: 1.51.1
OS Version: Darwin x64 19.6.0

Steps to Reproduce:

I have these colour codings.

"workbench.colorCustomizations": {
    ...
    "list.activeSelectionBackground": "#1a1a1a",
    "list.activeSelectionForeground": "#848484",
    "list.focusBackground": "#1a1a1a",
    "list.focusForeground": "#848484",
    "list.highlightForeground": "#2979FF",
    "list.hoverBackground": "#1a1a1a",
    "list.hoverForeground": "#848484",
    "list.inactiveFocusBackground": "#1a1a1a",
    "list.inactiveSelectionBackground": "#1a1a1a",
    "list.inactiveSelectionForeground": "#848484",
    ...
}

I have this keyboard shortcut.

With ctrl+e I am switching focus between explorer and editor. Here you see that the background and foreground colours change in ways the theme is not configured. My expectation would be that the foreground colour of the untracked file stays greenish. My expectation would be that the background of the focussed explorer column remains to be #1a1a1a. Though what happens is that foreground changes and background gets overlaid with some magic layer that I cannot identify. I cannot find any configuration to fix this. I could not identify anything obvious to me in the DOM and CSS when inspecting with the developer tools. Any help with this is appreciated.

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

When you do the SHow Explorer command we focus and select a file.
Please remove all your setting and do the following:
"workbench.colorCustomizations": {
		"list.activeSelectionForeground": "#ff0000"
	}

Press Ctrl + E -> file in the Explorer shoud be red. It is for me.

Hi there. Cool to see you getting back to my issue this quickly. Appreciate it a lot. I did as suggested above. I am unclear how this helps or what the intention with the exercise was. There is still the problem of the background overlay overriding any configuration available. There is always some overlay that I do not understand. And then I would just like to keep the state of the git decoration based on the file change status. I only want to have control over the background, which is not fully possible right now.

The intention of the exercie is to show that it everything works as expected. I believe you are surpsied by the list background focus color.
I think this is all as designed and should be asked in our ext development community. However forwarding this to @aeschli and @joaomoreno so they can decide if this should be closed

https://github.com/microsoft/vscode/issues/95768

I am not sure how you guys think how you should treat human beings. Though I think this issue should not get closed, without any comment towards the problem I reported. I made an effort to help improve the product you maintain and thus far we do not seem to be on the same page. The linked issue is about completely different concerns and feature requests. Also there is no mention about how this issue here is now being addressed. I just want control over the background and want that my settings are respected. If this is not desired just tell me.

@xh3b4sd You are right, this is not a duplicate of that.
So, the discussion seems strange to me. @xh3b4sd, you seem to talk about foreground and background. @isidorn has only addressed foreground, which can be explained like this:

list.activeSelectionForeground sets the foreground color when the list is focused only
list.inactiveSelectionForeground does the same but when the list is not focus
this is all true, unless there is a resource decoration which overwrites this, which is what's happening in your first gif. You can disable that with explorer.decorations.colors.

❓ @jrieken or @isidorn can clarify whether there is a way to set the list foreground theme color to have higher priority than the decoration foreground color, or whether that's not supported.
As for background: Since decorations have no control over background color, this works as expected for me using both list.activeSelectionBackground and list.inactiveSelectionBackground. No matter what, VS Code respects the background colors I set on those theme colors.
@xh3b4sd If this still doesn't clarify/help, please provide better steps with higher saturation background colors, since everything looks dark gray in the GIFs above.

this is all true, unless there is a resource decoration which overwrites this, which is what's happening in your first gif

As per my understanding this means that the foreground colour for added files should be always green, which is not what happens. I like to have that, but this is in parts what this issue is about. Regardless is the list item is active or focussed, I would like to let the git decoration take precedence. This is not the case right now.

please provide better steps with higher saturation background colors, since everything looks dark gray in the GIFs above

I can imagine that the problem is not easily visible if one does not pay close attention to the shading. It is that "magically" there is some 5% overlay shading going on and nobody can explain where this is coming from. All my settings are consistent and I verified there is magical shading going on without any settings nor extensions enabled. When you are on Mac you can try to zoom into the gif.

focus

no focus

Got it. Thanks for the persistence @xh3b4sd. The problem started in https://github.com/microsoft/vscode/commit/37e74c3135364bcbb8e5769aa1d9bef8c4179fd4 with: https://github.com/microsoft/vscode/blob/master/src/vs/platform/theme/common/styler.ts#L241
There is an implicit darkening of the list row selection background color, when the list doesn't have DOM focus. @misolori Should we instead keep the row selection background color stable, regardless of DOM focus, and just have a default lighter color for listFocusAndSelectionBackground, and expose that as a customizable theme color?

yea I think we added this because we didn't want to add another color token, since the list already has so many tokens. I think it makes sense to keep the row selection stable regardless of focus and adding a new color token, but would have to try this out first. I just attempted to do this to play with it but got lost multiple times with the selection/focus logic 🤷♂

I think this got fixed with one of the recent releases. Can anyone confirm work happened so that it wasn't an accident? On my end I see a more consistent shading. The experience is now solid. Though I noticed the command palette colours changed, which I had to fix like this to accommodate my custom colour scheme.
    "quickInput.list.focusBackground": "#1a1a1a",

Though I see the git colours are still not respected on active items in the explorer.

Yeah, the latest release changes the focus decoration to be an outline rather than a background color! That's great news that it has been fixed for you.

Though I see the git colours are still not respected on active items in the explorer.

Can you show me a screenshot?

I have a dark low contrast theme. Hope you can recognize the active element, it is darkish on darkish. Below I modified venture_test.go and now there is a compiler error, which marks the file yellowish. All while the item timeline_test.go is active.

Now if I click on venture_test.go to make it active it loses the git colour. My desired behaviour would be to keep the foreground git colour and only change the background to indicate the active element.

@jrieken Where in the code do we inject label decoration foreground color?

For my understanding, how do you (unit) test this behaviour?

@joaomoreno There is code that creates (and removes) dynamic CSS for different combinations of decorations: asDecoration is a good start for reading into this

For my understanding, how do you (unit) test this behaviour?

We currently don't.

Won't fix the "when the list is focused and the element is selected, the git decoration color doesn't apply" because that will have broader reprecursions, as per screenshot:

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


[CAPI] Expose layer enums

[CAPI] Expose layer enums

This patch contains layer enums to be exposed

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1444. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1444-202107271147170.71713209152222-90dfe801df26b63c8a5aa948f1f70c6e71acf818/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1444-202107271441010.61838293075562-e8df6841c884b918453a1028204e7675641a2ce2/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1444-202107281136030.7945990562439-aaef69e40632fdbca4deab3d4d392a65d96b7961/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1444-202107281143280.018263101577759-dcd724ca1708ce016dda3a674de2f5c64b71004e/.


fix protocols transformation of function Class parameters

Harmonize Engine compilation with Pure for f: ::new(..). Included test for roundtrip from Pure Code->PMCD->Pure Code, using Pure transformation.

depends on: https://github.com/finos/legend-pure/pull/560


part_of implies located_in

I think I forgot that - need to fix it in the specification.

@alanruttenberg
I would like to confirm that you mean to remove following sentences from the specification:
"For all independent continuants a and b, parthood implies location.
AXIOM: if b continuant_part_of c at t and b is an independent continuant, then b is located_in c at t. [047-002]"
If so, I will do it.


NDRS-971: Restrict cleanup to unclean shutdowns

Adds a Pidfile that gets created when using the cli. The pidfile will be removed only if Pidfile is dropped safely, thus indicating that any previous reactor has also been cleanly dropped.
If we drop it in using logic of always continuing to operate, only omitting integrity checks on a PidfileOutcome::Clean we should have strictly better behavior than before, without risking to exit due to bugs in Pidfile, provided we do not give false positives on PidfileOutcome::Clean
Not as clear cut as I'd like, due to the awkward placement of the integrity check, but otherwise very reasonable. It also makes it so that we can actually cleanly unwind, from what I understand we also crashed previously due to process::exit. E.g. when exiting due to SIGTERM, process::exit is called from within the scope where the validator lives, preventing its destructors to run.

Typos have been fixed.
bors r+

bors r+

bors r+


error when using "make -f makefile.unix"

Could you pls help me?
I do step by step the document (https://github.com/starcoinproject/starcoin/blob/master/doc/build-unix.txt), but I don't know when I used "make -f makefile.unix", I had an issue.
I use linux 2017.3.

Could I miss some libraries or miss any step?

Hi. Can you post there screenshot whrer you get first "error:" not "warning:"?

Tks, I resolved it


[Release] sdk/resourcemanager/saas/armsaas/0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armsaas - ci

/check-enforcer override


Adding Environment variable for determining of Dark Mode is enabled

I think plugins should be able to easily tell if Dark Mode is enabled to adjust text color and other factors. I added an environment variable for this that is sent to plugins (Similar to the "BitBar" environment variable) and also made a pull request for a tutorial on how to use it.

I like this, thanks very much.


fix: ease off the details loading to avoid stalling out

This builds off of the work from #26

I tried this out with a couple very large node operators and it seems to solve the issue.
e.g. https://rocketsweep-prod--pr27-daniel-gentler-loadi-873hdn43.web.app/node/whatwall.eth

Cool, and it's interesting this fixes it!
I'm shocked that we were hitting rate limits on my 66 nodes, but now with whatwall a longer window is enough to stop it.
Though I see it's no longer doing Promise.all on a few sequential calls in there, which has got to help too.
It seems like it'd be more robust to chunk it into 50's and do those chunks serially, or something like this. But if it works it works!


python311Packages.teslajsonpy: 3.9.3 -> 3.9.4

Diff: https://github.com/zabuldon/teslajsonpy/compare/refs/tags/v3.9.3...v3.9.4
Changelog: https://github.com/zabuldon/teslajsonpy/releases/tag/v3.9.4
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 258603 run on x86_64-linux 1

4 packages built:

python310Packages.teslajsonpy
python310Packages.teslajsonpy.dist
python311Packages.teslajsonpy
python311Packages.teslajsonpy.dist


Can only console log supported languages, undefined when returned

Attempting to map over supported languages:
const languageList = googleTranslate.getSupportedLanguages((err, languageCodes) => {
       return languageCodes
      })

console.log(languageList) // undefined

Console.log will return an array, but trying to return the array value (to use with a map for instance) produces an undefined value. Is it something fundamental I'm misunderstanding? Is this the intended use? I'm trying to map over the codes to produce a selection box.

Nevermind, this was a non-issue. I just had to put the codes into state first.


Can I replace print ticket in xps driver with other printer print ticket?

I am developing printer redirection on wfreerdp-server.
The protocol part([MS-RDPEPC] [MS-RDPEXPS]) I have coded, and Now I complete the printing function between mstsc and wfreerdp-server, but preferences configuration is not effective.
So  I try to replace print ticket in xps driver with client printer print ticket. Now preferences of some printer is effection, but some printer is not.
Could some one give some tips about that?
Is it good choice about replacing print ticket?

You should replace the print ticket of one printer with another printer, unless both printers are the same model. If you really want to replace it, you need to merge and validate the print ticket with the target printer and get the resulting print ticket, now you can use the print ticket for the target printer.


Implement new designs for deployment tool & inline connection errors

This PR implements new designs for deployment tool. It also inlines connection errors as we do not have a global connection feedback anymore.
Closes #186

@nazlikaya Can you have a look at this?

Let's call it a WIP now. I just discovered one issue:

OK fixed. A bunch of screenshots

I did some manual tests and looking good 👍The fix works too!
I'm not approving the PR as we're waiting to here from Nazli. If she gives ok I think we can merge this.

I also briefly tested it and it worked as expected 👍

Does this also include an improved input validation logic? I remember we had to separate PRs for design and logic in the Camunda Modeler. Or do we simply don't need any extra improvements here?

Does this also include an improved input validation logic? I remember we had to separate PRs for design and logic in the Camunda Modeler. Or do we simply don't need any extra improvements here?

It's just the designs, the validation logic will come next, in a separate PR.

@andreasgeier mentioned me to find that in my list. Take on the design review task from Nazli.

Design Review
Please fix style and alignment of the triangle of the tooltip (see Zeplin):

shape and its border needs correction
alignment has to be centered to warning icon, consider spacing between them

I realized we have the same issue in Camunda Modeler as well, so we'll have to apply the fix there too.

I realized we have the same issue in Camunda Modeler as well, so we'll have to apply the fix there too.

Can you maybe open an issue there as well?

Design Review
Please fix style and alignment of the triangle of the tooltip (see Zeplin):

shape and its border needs correction
alignment has to be centered to warning icon, consider spacing between them

This will be fixed via https://github.com/camunda/camunda-modeler/pull/1765

I pulled here the tooltip arrow fix as well as fixed the labels pointed out today. @andreasgeier please feel free to have a look again.
Regarding the mixing auth method & deployment target thing, I created a separate issue as it is outside of scope of this issue: https://github.com/zeebe-io/zeebe-modeler/issues/203

✅  Design Review: Passed. Tooltip arrow looks fine.


Fixes issue 6054: incorrect system table query on DB2 AS/400 platform

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Fixes #6054 incorrect system table queries being executed when running on the DB2i AS/400 platform by re-introducing two return statements.

Hello @MalloD12,
the changes look fine to me, but unfortunately I can't test them because we don't have DB2i either, only DB2z and DB2luw. Too sorry I can't help.
Michael


Getting opacity value change event

Hi Team,
I have one requirement to show some behaviour when opacity value is zero. Do we achieve this?

@narsireddypanta
Tell me more about the question.


Operation error

I try Run the trump case.
But it occur OSError: [Errno 95] Operation not supported.
Google colab connected.
And I confirmed file path.
But , it can't solve.
May I help you?

Maybe, it occur error by input file .
Process PreprocessConsumer_0:
Traceback (most recent call last):
File "/content/drive/MyDrive/Colab Notebooks/iPERCore/iPERCore/services/preprocess.py", line 80, in run
visual=True,
File "/content/drive/MyDrive/Colab Notebooks/iPERCore/iPERCore/tools/processors/base_preprocessor.py", line 74, in execute
src_img_dir = process_utils.format_imgs_dir(input_path, processed_info["src_img_dir"])
File "/content/drive/MyDrive/Colab Notebooks/iPERCore/iPERCore/tools/processors/process_utils.py", line 32, in format_imgs_dir
os.symlink(osp.abspath(src_path), osp.abspath(dst_path))
OSError: [Errno 95] Operation not supported: '/content/drive/MyDrive/Colab Notebooks/iPERCore/assets/samples/sources/wangyibo_2.jpg' -> '/content/drive/MyDrive/Colab Notebooks/iPERCore/results/primitives/processed/orig_images/wangyibo_2.jpg'

Sorry, It solved


Use ReactNative to the ios native project，and the compilation was several times slower

[√] Review the documentation: https://facebook.github.io/react-native
[√] Search for existing issues: https://github.com/facebook/react-native/issues
[√] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.4
CPU: x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 240.03 MB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.8.0 - /usr/local/bin/node
Yarn: 1.9.4 - /usr/local/bin/yarn
npm: 6.2.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
IDEs:
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.3.1 => 16.3.1
react-native: ^0.56.0 => 0.56.0
Description
Hi，why did I add ReactNative to the native ios project? Every time when I first compiled the project, it was very slow. It was much slower than the native project.How should this problem be solved?
I tried using the latest version ReactNative v0.56.0 just now, but it still took me a long time to build the project for the first time, so the latest version doesn't solve that problem.
I find that comment out RCTWebSocket and RCTAnimation , and then pod install will not have that particularly slow compilation problem.
pod 'React', :path => '../node_modules/react-native', :subspecs => [
    'Core',
    'CxxBridge', # Include this for RN >= 0.47
    'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
    'RCTText',
    'RCTLinkingIOS',
    'RCTPushNotification',
    'RCTImage',
    'RCTNetwork',
    #'RCTWebSocket', # Needed for debugging
    #'RCTAnimation', # Needed for FlatList and animations running on native UI thread
  ]

#21004

In short, you cannot solve it. What it does is compiling a bunch of extra objective-c, swift code from react native components into native code, so it is expected to be longer than native code.
However, once it is compiled and run, you can always use the "reload" feature which allows you to apply changes much faster.
To do that, press cmd + R in simulator, or shake the real device and select "reload" from the menu

@matthewkwong2 Thank you. But I'm talking about the long build time after the clean project. Or I want to archive, which is very long...


subnet can have an associated tunnel interface for evpn

@glimchb @venkatmahalingam - pls review one field change in subnet.proto file

Vipin, I thought you adding subnet reference to the tunnel object. Not the other way around… if tunnel is vxlan, and subnet is bridge we may have one to many…

@glimchb @sanders-mark  - should we merge this? this way cloud APIs can be a bit more flexible. Having said that we are addressing evpn use case as a first class APIs and so the use case for this enhancement becomes somewhat unclear.


llama-index-vector-stores-weaviate pypi version

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Is there a reason that version 1.0.1 of llama-index-vector-stores-weaviate is not available in pypi?

Weird. Just published it.


Konami Krazy Racers (USA) missing tracks during the intro

using official bios

I have a fix I am pushing to https://github.com/skylersaleh/SkyEmu/pull/40 for this.


Find a better way to accommodate "exactOptionalPropertyTypes" setting in React components

See @re-do/utils/src/text/ErrorText.tsx:
<Tooltip
            ...
            // TODO: Figure out a better way to accomodate TS's "exactOptionalPropertyTypes" in React components
            // https://github.com/re-do/redo/issues/277
            {...{
                ...(tooltipPlacement
                    ? { placement: tooltipPlacement }
                    : undefined),
                ...tooltipProps
            }}
        >

🤢


Improve jira and artifactory login note

According to infra.ci, both jobs run every other hour. I've improved the Jira login notice too.

bihourly is not a common word (chrome spellcheck doesn't know about it even) best to simplify I think

rip, let's use something simpler then


table column search should be case-insensitive

if i search for lowercase, then it should match any case.
if there is any uppercase letter in the search string, then case of every letter must match.
(this is like how emacs works)

@scottdraves shouldn't this one be closed already?


Inconsistent behavior between arm-gnueabi and arm-gnueabihf

I have a Rust program which depends on some C libs that I have downloaded the source for and compiled with arm-linux-gnueabi-gcc and arm-linux-gnueabihf-gcc into two separate directories.
When I run cargo build --target=arm-unknown-linux-gnueabi --verbose everything compiles and works correctly and I can run the binary on my Raspberry Pi. However when I run cargo build --target=arm-unknown-linux-gnueabihf --verbose it throws an error
note: /usr/lib/x86_64-linux-gnu/libgphoto2.so: file not recognized: File format not recognized

And I notice that the arguments cargo is passing to rustc differ by the compiler toolchain arm-linux-gnueabihf- vs arm-linux-gnueabihf (which is expected) but also by the last pair of flags. With the the hard-float version I get
rustc ... -L native=/usr/local/lib -L native=/usr/lib/x86_64-linux-gnu

Instead of the correct path to the compiled libs for that architecture.
-L /home/erik/Code/build/arm/lib

I change this last flag manually and run rustc manually I don't get an error. In my .cargo/config file I have rustc-link-search configured appropriately for each target.

Thanks for the report! I think arm-linux-gnueabihf-gcc isn't a valid target (as opposed to arm-unknown-linux-gnueabihf, so maybe that's what's going on?

Hey, thanks for the quick reply. Sorry that was a typo. I corrected my post with the actual commands I was running. Also this is my .cargo/config file contents for clarity:
[target.arm-unknown-linux-gnueabi]
linker = "arm-linux-gnueabi-gcc"
[target.arm-unknown-linux-gnueabi.gphoto2]
rustc-link-lib = ["gphoto2", "gphoto2_port"]
rustc-link-search = ["/home/erik/Code/build/arm/lib"]

[target.arm-unknown-linux-gnueabihf]
ar = "arm-linux-gnueabihf-ar"
linker = "arm-linux-gnueabihf-gcc"
[target.arm-unknown-linux-gnueabihf.gphoto]
rustc-link-lib = ["gphoto2", "gphoto2_port"]
rustc-link-search = ["/home/erik/Code/build/armhf/lib"]

[target.armv7-unknown-linux-gnueabihf]
ar = "arm-linux-gnueabihf-ar"
linker = "arm-linux-gnueabihf-gcc"
[target.armv7-unknown-linux-gnueabihf.gphoto]
rustc-link-lib = ["gphoto2", "gphoto2_port"]
rustc-link-search = ["/home/erik/Code/build/armhf/lib"]

Ah ok, can you also gist a log of cargo build -vv I could poke around as well?

Sure
https://gist.github.com/eberkund/389c6d4ed833d00ce6df89fb5d1f2a5b

Oh sorry forgot to mention, but can you run cargo clean ahead of that as well?

@eberkund hm it looks like that gist doesn't have the same error message as before? For example the current gist doesn't mention /usr/lib/x86_64-linux-gnu at all

There is two files in the gist, the first one labelled "arm" is the working one. The second one labelled "armhf" is the one that is not working, it has /usr/lib/x86_64-linux-gnu a few times throughout.

Ah sorry I missed that! So the output contains:
     Running `/home/erik/Code/rust-camera-client/target/debug/build/gphoto2-sys-f69e79f789fee58d/build-script-build`
cargo:rustc-link-search=native=/usr/local/lib
cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu

Are you sure the gphoto2-sys crate is doing the right thing? It looks like that's finding the wrong linker path

That's possible, but it works with arm-unknown-linux-gnueabi just not arm-unknown-linux-gnueabihf and the build.rs file in gphoto2-sys is very simple:
extern crate pkg_config;

fn main() {
    pkg_config::find_library("libgphoto2").unwrap();
}

Do you have any environment variables perchance that'd control the pkg_config crate?

I don't think so, other than PKG_CONFIG_ALLOW_CROSS=1 which I need otherwise I get an error telling me to use it

I think that may be the bug? It seems like pkg-config isn't configured to correctly cross compile?

Sorry, what do you mean? A bug where?
Isn't it normal to need that variable set to cross compile?

The pkg-config utility is rarely "out of the box" ready for cross compilation, so setting the env var to cross compile typically involves first configuring pkg-config (the CLI) itself first. I haven't personally dont that much, though, I've mostly only heard of others doing it.

So are you suggesting that I play around with those environment variables to get it to work?

Yes there's presumably some pkg-config env vars that need to be configured to get it to work correctly in cross-compiled situations (although I don't know which ones)

You'd typically set PKG_CONFIG_PATH to point to a copy of the library built for your target.

I tried setting PKG_CONFIG_PATH to a bunch of different things but it didn't seem to make any difference. I was using rustc-link-search in .cargo/config to compile arm-unknown-linux-gnueabi successfully. But the approach doesn't work for arm-unknown-linux-gnueabihf.

IMO this is an issue with Cargo because:

The behavior is not consistent between arm-unknown-linux-gnueabi and arm-unknown-linux-gnueabihf.
If I modify the resulting rustc command produced by cargo I don't get errors.

cargo build --target=arm-unknown-linux-gnueabihf

results in this. (It seems to completely ignore what I have in .cargo/config)
rustc ... -L native=/usr/local/lib -L native=/usr/lib/x86_64-linux-gnu

compared to,
cargo build --target=arm-unknown-linux-gnueabi

results in
rustc ... -L /home/erik/Code/build/arm/lib

where /home/erik/Code/build/arm/lib is defined in my project .cargo/config file with rustc-link-search. This is the expected behavior

@eberkund the /usr/lib/x86_64-linux-gnu argument isn't injected by Cargo, it's sort of equivalent to shooting the messenger. Cargo's transporting that argument from a build script to the linker, but Cargo's not why it's there.

Ah okay, yeah I just made a fresh hello world project to check and it works as expected. So I referred to these docs and searched my target/arm-unknown-linux-gnueabihf/debug/build directory and found:
➤ rg '/usr/lib/x86_64-linux-gnu' .
gphoto2-sys-8a360ca8035e79e2/output
2:cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu

Then I referred to the build script from the package that is producing that, gphoto2-sys
extern crate pkg_config;

fn main() {
  pkg_config::find_library("libgphoto2").unwrap();
}

I followed that to the here and I am still not sure what is happening, maybe the environment variables are not getting picked up and it's printing out /usr/lib/x86_64-linux-gnu as a default or something?

Sorry I'm not entirely sure, I haven't done much cross-compiling with pkg-config :(. @sfackler indicates that PKG_CONFIG_PATH may help.
FWIW in the meantime I'm going to close this as I don't think there's a bug in Cargo, here, but you can of course continue to post questions!

Okay well thank you for all of the help so far.
I will keep trying.

I think I figured out what was going wrong.
Putting this in .cargo/config doesn't work
[target.arm-unknown-linux-gnueabihf]
ar = "arm-linux-gnueabihf-ar"
linker = "arm-linux-gnueabihf-gcc"
[target.arm-unknown-linux-gnueabihf.gphoto]
rustc-link-lib = ["gphoto2", "gphoto2_port"]
rustc-link-search = ["/home/erik/Code/build/armhf/lib"]

But putting this in my build.rs does work
println!("cargo:rustc-link-search=/home/erik/Code/build/armhf/lib");

I think the problem is that the later is "project level" while the former only applies to "gphoto" so the couple of other dependencies I had were not found.
Is there away to write the equivalent in my .cargo/config?

The .cargo/config configuration will only be read if the crate says links = "gphoto", so to confirm, the crate says that right?


Poppies are detected as poodles

I am using a private dataset. However, I discover that all the poppies images are detected as poodles. I used the given checkpoint to test. I wonder if there is any mistake in labeling during training.
Details:
Model used: "https://openaipublic.azureedge.net/clip/models/40d365715913c9da98579312b702a82c18be219cc2a73407c4526f58eba950af/ViT-B-32.pt"
Text used for poppies: 'an image of poppies, a type of flower'
Text used for poodles: 'an image of poodles, a type of dogs'

What about "puppies"?

That's very strange -- I'm hosting the same model here, but it can differentiate between poppies/poodles no problem, so I don't think it's inherent to the CLIP checkpoint.

Thanks to all who checked for me, @LaCavao @gwern. With a cleaned-up model, this issue is now solved.

 If a girl dont is a slut shes no use


Create react form validation lib

Creates the initial version of the lib.
Still need to write some tests and documentation, but it should be already usable.
To run the demo application, install dependencies with yarn and then run yarn start to start the development server on port 3000.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1d47d01). Click here to learn what that means.
The diff coverage is 51.51%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   51.51%
=========================================
  Files             ?       10
  Lines             ?      132
  Branches          ?        0
=========================================
  Hits              ?       68
  Misses            ?       64
  Partials          ?        0

Impacted Files
Coverage Δ

src/Validate.js
0% <0%> (ø)

src/Validator.js
0% <0%> (ø)

src/validate-fns.js
100% <100%> (ø)

src/validations/match-validation.js
100% <100%> (ø)

src/validations/length-validation.js
100% <100%> (ø)

src/validations/required-validation.js
100% <100%> (ø)

src/validations/validation.js
100% <100%> (ø)

src/validations/equals-validation.js
100% <100%> (ø)

src/validations/email-validation.js
100% <100%> (ø)

src/field.js
4.34% <4.34%> (ø)

Continue to review full report at Codecov.

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


Potentially using in a wasm target?

I'm hoping to allow a library to compile to a wasm target. We're using pest-derive at the moment, which I think doesn't support a wasm target
Would Chumsky? I see there's a std feature that can be turned off — would you have any thoughts on how much of Chumsky's features we can use without that feature?
(for transparency, I'm a big fan of Chumsky, but was really hoping to not rewrite the parser quite yet, so I'll probably push it off for a while iff we can. Forgive the noise if so.)
ref https://github.com/max-sixty/prql/issues/175 & https://github.com/max-sixty/prql/issues/131

Chumsky should definitely work without std! I think there are only a few minor features that don't work without the feature, and none of those should change the way you work with the crate. If you run into any issues, feel free to mention them and I'll be sure to fix them!

Great, thanks @zesterer!


egui_plot: Force use of min_auto_bounds if auto_bounds is disabled by default.  Fixes  #3893.

The logic for determining bounds was not using the values supplied by include_x()/include_y() after the initial plot call when auto_bounds() was false. This change forces the use of the manual limits when default_auto_bounds is false.

Closes https://github.com/emilk/egui/issues/3893

Looks like this just needs a label applied.

Perhaps it would be better to factor this out into two methods, expand_{x,y} to expand the bounds to always show the specified value, and limit_{x,y} to limit the axis range, both applying regardless of whether auto bounds is active or not.
Of course if the user moves the plot, this should not apply. You could always disallow moving the plot if you don't want that.

egui_plot has recently been moved to its own repository, at https://github.com/emilk/egui_plot
This will hopefully speed up its development by having more reviewers and maintainers.
Please re-open this PR at https://github.com/emilk/egui_plot/pulls


Update api_callable

Fixes #10, and related to googleapis/gax-python#104. This respect
the basic redesign of gax-python.

[Current coverage][cc-pull] is 92.53%

Merging [#17][cc-pull] into [master][cc-base-branch] will increase coverage by 0.21%

@@             master        #17   diff @@
==========================================
  Files             6          6
  Lines           651        670    +19
  Methods          80         82     +2
  Messages          0          0
  Branches        142        147     +5
==========================================
+ Hits            601        620    +19
  Misses           50         50
  Partials          0          0

Powered by Codecov. Last updated by [545319b...6b4434b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/googleapis/gax-nodejs/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/googleapis/gax-nodejs/compare/545319b3528c98bbe812a7d43a70fba7bfa1c53d...6b4434b6ca2b30c158386a7a8d320aa21db8e7b2
[cc-pull]: https://codecov.io/gh/googleapis/gax-nodejs/pull/17?src=pr

Just one small suggestion for a comment.
LGTM


GitHub Signup

Describe the bug
The access to the platform through GitHub is not working.
When accessing the signup page and selecting the GitHub option, an error is alerted: User (role: guests) missing scope (account).
To Reproduce
Steps to reproduce the behavior:

Go to landing page.
Click on Sign up button
Click on Continue with GitHub button
Autorize OAuth  for Code Snippet Builder
See the error on the top left section of screen: User (role: guests) missing scope (account).

Expected behavior
Be able to sign up through GitHub OAuth.
Desktop (please complete the following information):

OS: Linux - Manjaro
Browser: Firefox
Version: 119.0

Hello @FelipePardim , thanks for reporting this, we will take a look and fix it soon, thanks, and have a good day.

After initial investigation found this https://github.com/appwrite/appwrite/issues/1203#issuecomment-850787160, will investigate it further.
Quick Hack : @FelipePardim you can try signing up in chrome.

Thanks @Sachin-chaurasiya for the advice, I will switch to Chrome

yup got the same issue. gonna sign in on chrome. thx


[Bug]: Not possible to upgrade k8s.io/api and k8s.io/apimachinery from 0.24.4 to 0.25.0

What happened?
The automatic upgrade of k8s.io/api and k8s.io/apimachinery failed when upgrading to 0.25.0. #2048 and #2049

I'll work on this

Closing because it was fixed as part of #2053


New version: Axure.AxureRP.11 version <IP_ADDRESS>22

Created by 🥟 Dumplings in workflow run #9527.

Log
Updated: <IP_ADDRESS>21 → <IP_ADDRESS>22
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

This package installs and launches normally in a Windows 10 VM.


[BUG] vscode-icons needs re-activation after new version installation and editor restart

[x] I'm sure this issue is not a duplicate.

It came to my attention that vscode-icons requires re-activation when a new version is released and after closing and re-opening vscode (not after reload).
This is caused because vscode, on the restart, executes the uninstall script to remove the previous version and in that script, we do a clean-up that includes the removal of the workbench.iconTheme setting.

Please consider fixing this.


Programs Missing/Duplicate (Resident view)

Describe the bug
If a resident logs in to CiviForm with an existing account, the programs displayed are incorrect. For example, it lists the ORCA Middle School program twice and the Parks Childcare program is left off. If a resident logs in as a guest though, the correct programs display.
To Reproduce
Steps to reproduce the behavior:

Log in to an existing account (or create a new one!)
View the programs listed
See "ORCA Opportunity" listed twice. And "Park Child Care Scholarship" missing
See attachments
Error_Programs missing when logged in.pdf

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I tried logging in as a guest and with an IDCS account and was unable to reproduce this behavior.
There's some logic on that page regarding programs that are in an active/draft state. Have there been changes published since this was reported?

Hi @bion, thanks for taking a look. I re-published all programs about an hour ago. But I'm still able to replicate the issue now.

I am also unable to reproduce this behavior - I logged in as a guest and with an IDCS account. @elisekalstad can you check one more time and see if this is still happening?
Looking into the logic that Bion mentioned above.

Hi @ettengererin - Yeah, I'm still getting the error when I login with an IDCS account.

Hi @ettengererin - Yeah, I'm still getting the error when I login with an IDCS account.

...but I'm now noticing that if I scroll down a bit, the Parks and Rec program is listed under "new programs".

That's helpful to know re the "new programs" section. Thanks Elise!

The Parks and Rec program is listed under "New programs" because you haven't started that application yet. All the other apps you've started are in the "Continue" section. This behavior is expected.
The unexpected behavior is the duplicate ORCA opportunity programs. @elisekalstad does clicking "Continue" on both of those versions work? I.e. click continue on both the first and last ORCA programs, and see if it goes to the application where you left off. Please let me know what the result is here!

Hi @ettengererin -- I clicked continue on both ORCA programs and it was pre-filled with my "test" data on both. They looked just the same, attached.


Add Configuration to FBProcessTerminationStrategy

FBProcessTerminationStrategy has a bunch of behaviours on top of kill making these explicit with an option set means that behaviour is more understandable. FBSimulatorManagementOptionsUseProcessKilling no longer makes sense as it is always the fallback.
Additionally, the relaunch interaction could result in strange behaviour when the failure to kill an existing application was suppressed. As a result, the app wouldn't be re-launched at all.

@facebook-github-bot shipit


How to get the bounding box of the subtitle?

Hello, I would like to extract the dimensions of the rendered subtitle to create an interactive UI. Is this possible? Thanks.

mark

I'm wondering if it's possible to use OpenCV to recognize, extract, and calculate the position of subtitles. However, considering that there may be karaoke-style subtitles, this method seems to be more complicated.


use fixed ssh.net

Fixes #537
@darkoperator  SSH.NET v2023.0.0 has the fix, updating the reference I see the PoshSSH.Core compiles fine and works as expected in my tests against 8.8 SSHD with sha-rsa disabled. I can add the dlls to the PR, but thought you may want to do that yourself.

@MVKozlov maybe you could release the fix?

I need to compile from develop and change the name, then compile against it because MS ships a binary with the same name as the nugget. Im the only owner of the project with permission to push changes. Will see if I have time this weekend to do it and push a mew version


beaconblockproposer: "error": "transactions root mismatch", "message":"Failed to obtain blinded proposal"

Hi 👋   Any ideas what might be causing this error?  It happens with Teku.
Unabridged version:
{"level":"error","service":"beaconblockproposer","impl":"standard","slot":9574572,"error":"transactions root mismatch","time":"2024-07-23T07:14:49Z","message":"Failed to obtain blinded proposal"}
This is causing VanillaBlocks production and rewards loss.
Logs around when it happens for slot 9574572: https://gist.github.com/adaszko/d8e709c45d40c1ae1cae74352039b719
Teku produces Slot Block Production/Publishing warnings for such slots:
Jul 23 07:14:48 teku-beacon-node-1 teku-beacon-node[5466]: 07:14:48.230 WARN  - Slow Block Production *** Slot: 9574572 start 935ms, preparation_on_tick +0ms, preparation_apply_deferred_attestations +0ms, preparation_process_head +60ms, retrieve_state +0ms, beacon_block_prepared +89ms, builder_get_header +1ms, local_get_payload +8ms, beacon_block_created +1ms, state_transition +126ms, state_hashing +10ms, complete +0ms total: 295ms
Jul 23 07:14:48 teku-beacon-node-1 sh[5375]: 07:14:48.230 WARN  - Slow Block Production *** Slot: 9574572 start 935ms, preparation_on_tick +0ms, preparation_apply_deferred_attestations +0ms, preparation_process_head +60ms, retrieve_state +0ms, beacon_block_prepared +89ms, builder_get_header +1ms, local_get_payload +8ms, beacon_block_created +1ms, state_transition +126ms, state_hashing +10ms, complete +0ms total: 295ms
Jul 23 07:14:49 teku-beacon-node-1 teku-beacon-node[5466]: 07:14:49.443 WARN  - Slow Block Publishing *** Slot: 9574572 start 2181ms, blob_sidecars_prepared +16ms, block_import_completed +205ms, block_and_blob_sidecars_publishing_initiated +0ms, complete +41ms total: 262ms
Jul 23 07:14:49 teku-beacon-node-1 sh[5375]: 07:14:49.443 WARN  - Slow Block Publishing *** Slot: 9574572 start 2181ms, blob_sidecars_prepared +16ms, block_import_completed +205ms, block_and_blob_sidecars_publishing_initiated +0ms, complete +41ms total: 262ms
Jul 23 07:14:51 teku-beacon-node-1 teku-beacon-node[5466]: 07:14:51.000 INFO  - Slot Event  *** Slot: 9574572, Block: 61a70d5079a1309c05b53119738cd59a40fc3b541a1e34eafc6e2cd81f265353, Justified: 299204, Finalized: 299203, Peers: 128
Jul 23 07:14:51 teku-beacon-node-1 sh[5375]: 07:14:51.000 INFO  - Slot Event  *** Slot: 9574572, Block: 61a70d5079a1309c05b53119738cd59a40fc3b541a1e34eafc6e2cd81f265353, Justified: 299204, Finalized: 299203, Peers: 128

I have a strong suspicion this is caused by
         beaconblockproposal:
            style: best
         blindedbeaconblockproposal:
            style: best

since that's one of very few changes that were made.  There's 4 nodes configured in the beacon-node-addresses: section.

Are your beacon node(s) configured to use the vouch instance as the builder?

Yes, Ligthouse is started with the --builder <VOUCH URL> option and Teku with --builder-endpoint=<VOUCH URL>

I have a strong suspicion this is caused by
         beaconblockproposal:
            style: best
         blindedbeaconblockproposal:
            style: best

since that's one of very few changes that were made. There's 4 nodes configured in the beacon-node-addresses: section.

This has been reverted and the problem is still there.

The root cause was one of the MEV relays producing wrong payloads.


chore(deps): loopback version update

Description

Loopback version update

Fixes # (GH-60)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

This one thing needed to be addressed


Update check.py

I think the check script isn't defining the colnames for the report correctly, so i added a fix that I think addresses that.

Is this modification ok @xrotwang ?


Doesn't work outside github pages

Description
This project doesn't work on anything that is not github pages. Even trying it out with python -m http.server doesn't work.
What I Did
I forked the project because it's perfect for my use case, other than the GH pages thing.
Here is the commit that makes it work anywhere: https://github.com/awoimbee/docs_versions_menu/commit/b9f221d9ab10367fb5a6b8964ddf8a3650afe060
Are you interested in bringing some of this into this repo ?
My modifications aren't clean at all (not meant for a PR) (Also I don't like jquery nor var 😄 ) but I can clean them up for you if you want.

You are correct that out of the box, the plugin only works on Github pages. Anything else requires modifying the JS-template at the moment.
I absolutely have plans to rewrite the template so that it works under a much wider range of hosts, in a future version. This includes both the situation where the project isn't hosted on Github and where the documentation isn't hosted on Github pages (although that will remain the primary use case). I'll probably want to move more information into the docs_versions_menu_conf settings in conf.py so that there will be little if any need for people to touch the JS-template
How exactly the template can be made more robust will require some planning on my end. I might accept pull requests to improve the template in this respect, although I can't make any promises I'll have time to review or merge it in the next couple of weeks. I'll want to think a little about where I want the design of the template to go.
If you do make a pull request, please keep it minimal: don't mix in unrelated changes such as getting rid of jquery/var, renaming variables, or reformatting code, in the same PR. That being said, I would definitely be open to merge in PR's for such changes separately. I barely know Javascript, so I'd welcome improvements, provided they're reasonably atomic and come with a little bit of explanation: why is let better than var? Are there expected compatibility/performance improvements with getting rid of jQuery?

Ok, thanks for the quick response. I'll clean up and use my fork while you figure out where you want this project to go. I think we don't have the same use-case and I want/need fast updates.
Don't worry I will never open a PR where I half-assed re-wrote most of a file like in the cited commit 😄.
Regarding the explanations:

let is better than var because it's much stricter so less bug inducing and acts more like in other languages. Check out https://stackoverflow.com/questions/762011/whats-the-difference-between-using-let-and-var
jquery is bad in this day and age because it's a fat useless lib, native ES6 has way better APIs.


es6-promise is not a safe polyfill to recommend in your readme

es6-promise's strict spec handling of uncaught exceptions (by not doing so at all) is a footgun. I don't feel like it should be the default recommendation of polyfill, and personally is the reason I've kept my team away from fetch() for months. Here are examples why:

http://requirebin.com/?gist=8f13d5147c1c252ab1691115bfa8b7c5
http://requirebin.com/?gist=06e8c85fcaca56c9651c6aabd0d91476

Bluebird, however does the right thing:

http://requirebin.com/?gist=43a3858fa57d9b94c00b2b454722c15d

I'm not saying Bluebird should be what you suggest instead, as I haven't dug into relative sizes/support/practicalities of that. I just feel that recommending people use es6-promise is going to cause a lot of people pain.

Maybe you could give yaku a try.
Features

The minified file is only 4.1KB (1.8KB gzipped)
Supports "uncaught rejection" and "long stack trace", [Comparison][docs/debugHelperComparison.md]
Designed to work on IE5+ and other major browsers
100% statement and branch test coverage
Much better performance than the native Promise
Well commented source code with every Promises/A+ spec

Yaku looks excellent, and ticks all my personal boxes, thank you!
I've been trying to pin this down even more, because when I actually hit it I felt it was way worse than I've actually demonstrated. And I remembered that even when you .catch() and re-raise, es6-promise does NOT surface the error/exception.
To me this is the most concrete example that the developer is absolutely doing all the right things, and the error is STILL swallowed:
http://requirebin.com/?gist=9c59be0170fa7691a534705daf6b765d
And (now using Yaku as alternative), here's how you do it right:
http://requirebin.com/?gist=8e1d11f8754e58afd271a994760bb0c4

If you have any problem with Yaku, please feel free to issue me. The project is quite active to user feedbacks now.

To make matters even worse the author has now closed that issue thread, so it's not even visible to people now that it's an issue: https://github.com/stefanpenner/es6-promise/issues/70

Sad story.
On Sat, 22 Oct 2016 at 4:15 AM Nick Williams<EMAIL_ADDRESS>wrote:

To make matters even worse the author has now closed that issue thread, so
it's not even visible to people now that it's an issue:
stefanpenner/es6-promise#70
https://github.com/stefanpenner/es6-promise/issues/70
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/matthew-andrews/isomorphic-fetch/issues/111#issuecomment-255454823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWZQLp0R61aNwevzCqx_ZT5o5rHv0ACks5q2R1wgaJpZM4Kbj6l
.

I would recommend looking at promise-polyfill. I tested a bunch of polyfills and it's the smallest and I don't think it has that footgun.

This repo no longer recommends any polyfill.


Apply upstream aarch64 consecutive register fix (11.x)

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

xref: https://github.com/conda-forge/numba-feedstock/pull/94#issuecomment-1218068344

xref: https://reviews.llvm.org/D104123
cc @gmarkall

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/llvmdev, this is ready for review

There are some failed tests on osx, is that expected...?

Should add we could also just ignore that job. There are already macOS packages for LLVM. The fix here is focused on ARM, which seems to build ok.

I'm trying to downgrade the compiler in https://github.com/conda-forge/llvmdev-feedstock/pull/167

See https://github.com/conda-forge/llvmdev-feedstock/pull/167#pullrequestreview-1079581882

Reverting to the old macOS version fixes CI
However @isuruf noted in this comment ( https://github.com/conda-forge/llvmdev-feedstock/pull/165#pullrequestreview-1079581576 ) and following discussion that there is an ABI breakage caused by the patch that would need to be fixed

@jakirkham In my branch https://github.com/gmarkall/llvmdev-feedstock/tree/fix_llvm_11_aarch I have the consecutive registers patch and the ABI fix applying successfully when I run build-locally.py - would you like to take a look at this branch / try it out?

Thanks! I just started the bots and made them work in: https://github.com/conda-forge/llvmdev-feedstock/pull/170

Looks like it appeared to be successful in #170? @jakirkham Is there anything else you need from me to help move forward right now?

Resolved by PR ( https://github.com/conda-forge/llvmdev-feedstock/pull/171 ). Closing...


Clarify naming in resolution tests

Changes

Prior to this commit, ResolvedPipelineRunTask was sometimes referred to as Task and PipelineRun referred to as Run in the resolution tests. This was confusing when adding more tests to the resolution.
In this change, we clarify the naming to be clear and consistent with the rest of the codebase.
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Docs included if any changes are user facing
[n/a] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in
(if there are no user facing changes, use release note "NONE")

Release Notes

NONE

cc @pritidesai @abayer more yak shaving, ptal

/lgtm

/approve

/retest


docs: Assorted docco updates to make them betterer.

Make some links actual links
Note that we do support Oracle 🥳
Update config values to match new order in executable
Various minor spelling, grammar and syntactic issues

Thanks a lot, @wokket !


EndpointSuffix for azure

I' m azure user from china. my azure storage account is different from global azure.
so there is a property EndpointSuffix can identity it.
We will add it in next version?
    return new CloudStorageAccount(
                    new StorageCredentials(
                        options.AccountName,
                        options.AccessKey),
                    useHttps: true,
                    endpointSuffix:options.EndpointSuffix);

Thanks in advance.

Ah interesting, I've never used that before. I'll add support for using a full connection string. Thanks for the suggestion!

Just out of curiosity, how do you plan to use BaGet on Azure China?

@loic-sharma  I develop BaGet in a docker with my virtual machine.
The machine os is debian 10.

So glad for supporting full connection string. Thanks .

Hello, this will be addressed by: https://github.com/loic-sharma/BaGet/pull/411/files

Hi, could you update to the latest version of BaGet and try out the connection string? Please let me know what you think!
For more information, check out the docs: https://loic-sharma.github.io/BaGet/quickstart/azure/#azure-blob-storage

@loic-sharma  I test, it works. thanks.


allow users to specify a local/bind address

would require using net.Dialer{}.LocalAddr. relates to #3.

added in commit 94cceb64e78af3d62eacbcf8a1eaf0e3f0159bce


Upgrade next-transpile-modules

This branch just needs to be checked out locally and have yarn update the lock file.


[keymgr/sw] Add spinwait to advance state function calls

This commit wraps sc_keymgr_advance_state in IBEX_SPIN_FORs. I noticed that the ft_personalize test started failing because certain calls complete too late. This might cause the following code to hang.
I also wrapped the sc_keymgr_owner_advance call in ft_personalize.c in an IBEX_SPIN_FOR. Otherwise this test fails for my changes in #22114.
I think there is still something off here, since if  I wrap the sc_keymgr_owner_int_advance call on line 250 in ft_personalize.c in another IBEX_SPIN_FOR, the test fails again.
This PR can be used as a starting point but I believe there's still some debugging to do here.

Closing this draft PR, since the test already waits for the keymgr to finish. The issue seems to lie somewhere else and needs to be investigated. See #22753


Update links

Thank you for contributing to openstack/sqlalchemy-migrate!
openstack/sqlalchemy-migrate uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
https://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
https://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Fix RemoteTaskRunner's auto-scaling

Problem
Overlord leadership blink causes shutting down RemoteTaskRunner and creating a new RemoteTaskRunner. But the second RemoteTaskRunner couldn't start, because they share global ResourceManagementStrategy, which shuts down it's executor when the first RemoteTaskRunner calls resourceManagementStrategy.stopManagement().
How it is fixed
ResourceManagementStrategy is now an immutable object, it creates mutable stateful ProvisioningService objects upon request for each individual RemoteTaskRunner. Each ProvisioningService has it's own executor, which is shut down from RemoteTaskRunner.stop().
Testing
Added OverlordBlinkLeadershipTest, demonstrating this issue.
What else is changed
ResourceManagementStrategy is refactored, first of all it is renamed to ProvisioningStrategy (and all related classes are renamed as well), because Provisioning is a little more distinctive keyword within Druid codebase than plain ResourceManagement.
Also AbstractWorkerProvisioningStrategy (former AbstractWorkerResourceManagementStrategy) is refactored towards composition from inheritance, Provisioner interface is extracted.
Size of this PR
Conceptual size of this PR is smaller than you might think looking at +710 -528, e. g. in PendingTaskBasedWorkerProvisioningStrategy and SimpleWorkerProvisioningStrategy.java mostly just code indentation has changed, that generated many "changed lines".

Semi related: https://github.com/druid-io/druid/issues/3498 https://github.com/druid-io/druid/issues/3428

https://github.com/druid-io/druid/issues/2294 also semi-related.

Could anybody please review this?

I'll review tonight.

@jihoonson thanks for review. Could you please merge it?

Sure.

@jihoonson thank you!

@leventov no problem!


Should update Travis to use npm 5

npm 3 results in much slower builds. npm 5 should be a bit snappier.
This can be altered in travis.yml

Sorry, had some issues with git...


The performance is lower than reported ?

Amazing Work! When I used the provided code and followed the method in your paper, I only got val 64.9 and test 65.2 mIoU, respectively.  How can I get the same performance as reported in your paper？

Thanks for your attention.  From my experience, it looks like that you did not initialize the segmentation model with the ImageNet pre-trained weight ?  Besides, using the segmentation model trained parameters in the new round for classification will also beneficial.

@ZHANGDONG-NJUST  Thx for your reply.

Thanks for your attention. From my experience, it looks like that you did not initialize the segmentation model with the ImageNet pre-trained weight ? Besides, using the segmentation model trained parameters in the new round for classification will also beneficial.

Thank you for your answer! I downloaded the pretrained resnet-101 model on the pytorch website according to your tips, but I didn't get the desired result. Could you tell me how to download your imagenet pretrained model you mentioned above?

Thanks for your attention. From my experience, it looks like that you did not initialize the segmentation model with the ImageNet pre-trained weight ? Besides, using the segmentation model trained parameters in the new round for classification will also beneficial.

Hello,I am very confused about how to use the parameters of the segmentation model training to classify in the new round

@SunGuoYing   The classification model and the segmentation model share the same backbone network. Using the segmentation weight in a new round classification is beneficial for generating CAMs.

@hiddlephila  I just used the common pre-trained model in pytorch.


Missing Character Detection.

Hi,
SRWE is currently missing the correct "character" in French.

As I can see in the code we have Personnage but not Personnages, error of copy paste or another language that use the same word without s at the end?
https://github.com/biuuu/star-rail-warp-export/blob/8a9c7a3b56ecdf7a20c31ff7c3517bfb9478f26b/src/renderer/utils.js#L8
The weapons are properly detected by default.
Cordially.

Everything is detected properly with the update, thanks for the quick fix.

Closing the issue as solved.


Should we rename this attribute to interventions?

https://github.com/zooniverse/Panoptes/blob/15595ed92cab784c138a2aac88ba4467225a23d1/db/structure.sql#L1593
intervention_notifications -> interventions
This boolean attribute specifies if a user chooses to participate in interventions or not. I think we can remove the notifications part of the attribute name as interventions may include more than just message notifications.
PFE would have to coincide changes for the following files https://github.com/zooniverse/Panoptes-Front-End/search?q=intervention_notifications

Makes sense to me. If this flag covers all interventions, then PFE should delay adding the Sugar experiments listener until after the user is logged in, and then only add the listener if interventions is true.

:+1:


Fix wrapping links in menu bar [#99075508]

@dougmartin looks like this broke some tests of the help menu links.

Ok - to get the cucumber tests to pass I made the default menu links visible but the added projects links hidden.  This still keeps the flash of wrapped links from showing.


Unrelated interface causes assignably to change

🔎 Search Terms
5.3 regression
🕗 Version & Regression Information

This changed between versions 5.3.0-dev.20230823 and 5.3.0-dev.20230824

⏯ Playground Link
Playground Link
💻 Code
export { }
interface Map<V> extends Collection<V> {
    flatMap<VM>(): Map<VM>;
}

interface Collection<V> {
    value: V; // sprinkle some covariance
    map: Map<V>;
    concat(): Collection<unknown>;
    flatMap(): Collection<V>;
    flatMap<VM>(): Collection<VM>;
}

// Comment out and it works like in 5.2
interface Keyed extends Collection<number> {
    concat(): Keyed;
}

type R = Map<never> extends Collection<infer V> ? V : "NO";

const r = null! as R;
const t: "NO" = r;

🙁 Actual behavior
R is unknown. Removing Keyed makes R unknown, even though Keyed is unused otherwise.
🙂 Expected behavior
Not really sure. I'd settle for the stable 5.2 behavior, which is for R to be "NO" although that also seems wrong (Why doesn't Map<never> extends Collection? If we remove flatMap(): Collection<V> from Collection then Map<never> extends Collection. This seems like the correct behavior.)
Additional information about the issue
No response

Bisects to #53396, cc @ahejlsberg . Trying to find a more direct repro that involves only a single assignability check, but I suspect the self-reference in Keyed is a necessary component


Init repo

I have some addresses that I believe are for the v2 StakingController, not sure if they are still being used but they have some staking request placed transactions on them
mainnet: 0x45b13d8e6579d5C3FeC14bB9998A3640CD4F008D
rinkeby: 0x7FDd24f30fB8a3E0021e85Fdb737a3483D3C8135

I have some addresses that I believe are for the v2 StakingController, not sure if they are still being used but they have some staking request placed transactions on them mainnet: 0x45b13d8e6579d5C3FeC14bB9998A3640CD4F008D rinkeby: 0x7FDd24f30fB8a3E0021e85Fdb737a3483D3C8135

The zNS Staking Controller isn't going to come back. So we can probably just leave it out


threadpool: the number of tasks

Can Libuv add a function to get the number of tasks waiting to be processed in the thread pool ?

It could but what would you use it for?

I'm not sure whether it is useful to know the status of the thread pool, such as the number of UV__WORK_FAST_IO, and UV__WORK_SLOW_IO tasks. I think the info can be printed in the Node.js diagnostic report.

I suspect that the number of tasks is a pretty irrelevant metric. Knowing how long they stay in the queue is probably a lot more useful.
If you have a single task that's stuck for an hour, that's a problem. If you have a million tasks that are all gone the next millisecond, there's no problem.

Thanks for explanation, I will collect the cost time of task in Node.js.


query_media_url function is not working properly

query_media_url function is missing a slash(/). Please assign this issue to me.

Hi @DaudAhmad0303 , Thank you for spotting that
I have assigned the issue to you, looking forward seeing your pull request
Thank you


Update ReadMe for borderless tables

When ReadMe will be updated for processing borderless table?

I'm also interested in this information.

Do you know?
@DevashishPrasad


Default distribution does not contain all dependencies

Either:

adjust documentation for classpath
just pack everything up

Will be closed by #32


Warning "invalid case style for variable" on lamda function define.

const auto getExternalFunctionEntryPointSymbol = [&](StringRef SymName) {
auto &Context = DAG.getMachineFunction().getMMI().getContext();
MCSectionXCOFF *Sec = Context.getXCOFFSection(
(Twine(".") + Twine(SymName)).str(), XCOFF::XMC_PR, XCOFF::XTY_ER,
SectionKind::getMetadata());
return Sec->getQualNameSymbol();
};
  SymName = getExternalFunctionEntryPointSymbol(SymName)->getName().data();

I got a warning as
clang-tidy: warning: invalid case style for variable 'getFunctionEntryPointQualNameSymbol' [readability-identifier-naming]
not useful
I think it looks as getExternalFunctionEntryPointSymbol  viable, and it should ask to name as
GetExternalFunctionEntryPointSymbol , actually it is a function. I think getExternalFunctionEntryPointSymbol is correct.

Not sure how to address this issue in pre-merge testing.
I guess this is a bug in clang-tidy?

@diggerlin it seems that issue is related to clang-tidy tool, not pre-merge checks that runs it. Please reopen this issue if that is not the case.
P.S. Please attach links to phabricator review / build as they help to investigate issues.


Flatten and print Row-major

Not particularly an 'issue' I am just lost as to how one would flatten a JPEG image using this library and then print all of its contents (pixel by pixel) in row-major format.
I already have my JPEG image received no problem I just need to flatten it, if someone could point me in the right direction I'd be grateful.
ex:
callBack(JPEGDRAW *pDraw) {...}
Edit: Thought I'd add a little more information as to what I'm saying. I have a screen that I am trying to write images to that only accepts pixels sent via row-major format. And allthough I've created functions that can iterate through my decoded jpeg file in row-major fashion it's clear that the information isn't "stored" like that - MCUs and all. I am just requesting a callBack of which will iterate through my decoded jpeg file in a way that is row-major so my screen can re-assemble the image. Am dealing with images greater than 300x300 pixels if that is of any help.
Anyway, thank you.

I understand your question, but can't change the nature of JPEG encoding to suit your use case. You will need to temporarily store each row of MCUs and then send them a row at a time to your display. The JPEGDRAW callback will always complete a row of MCUs without wrapping around to the next. e.g. if the row has 24 MCUs horizontally, it might call JPEGDRAW with 20 followed by 4, but one or more calls will always add up to the full row width.


Add a --quiet flag to suppress terragrunt-related output

The CLI output is quite chatty, which is very nice but in some cases annoying.
Example: using atlantis to generate plan and apply outputs as GitHub PR comments, it creates very long comments that sometimes even have to be splitted by GitHub.
An idea would be to optionally disable the terragrunt output, using a --quiet flag, for instance. This would suppress the [terragrunt] prefixed lines and keep only the terraform output.
For the record, the corresponding terraform issue: https://github.com/hashicorp/terraform/issues/10507

Duplicate of #432. PRs welcome!


Problems with VelocityTransitionGroup on react-templates

Hi,
I get the next error to use VelocityTransistionGroup in a react-template
Error: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component'srender method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).
This is the code of the template:
<rt-require dependency="react-bootstrap/lib/Grid" as="Grid" />
<rt-require dependency="react-bootstrap/lib/Row" as="Row" />
<rt-require dependency="react-bootstrap/lib/ListGroup" as="ListGroup"/>
<rt-require dependency="react-bootstrap/lib/ListGroupItem" as="ListGroupItem"/>
<rt-require dependency="react-loader" as="Loader" />
<rt-require dependency="velocity-react/velocity-transition-group" as="VelocityTransitionGroup" />

<VelocityTransitionGroup component="div" enter="transition.fadeIn" leave="transition.fadeOut" duration={200}>
    <Grid>
        <Row>
                <Loader loaded="{this.state.loaded}" color='#bf5a16' top="50%" left="50%" scale={1.00} width={10}>
                    <ListGroup>
                        <ListGroupItem rt-repeat="conversation in this.state.conversations" key='{conversationIndex}' header="{conversation.title}">Tiene {conversation.messages ? conversation.messages.length : 0 } mensajes </ListGroupItem>
                    </ListGroup>
                </Loader>
        </Row>
   </Grid>
</ VelocityTransitionGroup>

In this way I have the render method:
import Template from './Conversations.rt.js'
render(){
        return Template.call(this);
 }

Thanks and greetings

Sounds like this may be something on the React Template side? VelocityTransitionGroup does not use refs itself. You could see if you get the same problem using React’s TransitionGroup, which is what VTG delegates to.

Adding my two cents, got the same issue, without using react-template. It was related to velocity-react (or one of its dependencies) pulling a different version than the one I had in the project.
Like stated in the react error message, two versions of React were running, causing issues (https://gist.github.com/jimfb/4faa6cbfb1ef476bd105).
I managed to make sure both my project and velocity-react were depending on the same react version, and it fixed the issue.
Shrinkwrapping your dependencies afterwards should help to make sure this issue doesn't arise again.


StaticInput causes OnInitializedAsync to be called 3 times

I created a fresh Blazor Server App with MudBlazor Template and noticed that OnInitializedAsync was called 3 times. This issue was resolved when I removed StaticInput from App.razor.
<script src="_content/Extensions.MudBlazor.StaticInput/NavigationObserver.js"></script>

MudBlazor Template: https://github.com/MudBlazor/Templates

Weather.razor
protected override async Task OnInitializedAsync()
{
    Console.WriteLine("{0} load forecast", DateTime.Now.Second);
    ...
}

Temporarity fix by adding a condition in App.razor
@if (RenderModeForPage is null)
{
    <script src="_content/Extensions.MudBlazor.StaticInput/NavigationObserver.js"></script>
}
...
@code {
    [CascadingParameter]
    private HttpContext HttpContext { get; set; } = default!;

    private IComponentRenderMode? RenderModeForPage => HttpContext.Request.Path.StartsWithSegments("/Account")
        ? null
        : new InteractiveServerRenderMode(prerender: true);
}


Remove initialiser for PP

The app no longer talks to the PP (all uploads happen in support-api).

I'm guessing PP is Performance Platform?

Presumably there'll be a corresponding PR in alphagov-deployment? Otherwise :+1:

@fofr  see https://github.gds/gds/alphagov-deployment/pull/915


Create akunprohihub

Summary

Screenshots (optional)

Documentation checklist

[ ] The documentation style guide has been adhered to.
[ ] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
[ ] Files which have changed name or location have been allocated redirects.

What is an akunprohihub!?!


nodes are not joined

Using v1.7, nodes are not joined. I scp /etc/kubernetes to other masters, then systemctl daemon-reload && systemctl restart kubelet followed by systemctl status kubelet. It is running; however only the initial node shows up. Should we not be sing the kubeadm join command around this point?

Can you show me the kubelet logs?

Did you setup a HA master cluster first? On k8s worker nodes, it's no need to copy /etc/kubernetes/ directory to worker nodes

Logs are complaining about the cert, which is in the successive steps, but it does show they are supposed to be seen initially. I tried to continue on, but could not due to the other issue.
Yes I went through all steps prior. These are not worker nodes, they are masters.

Did you edit the kubelet.conf file? If you edit the file's server setting to current host ip, it will show this problem, then you must create certificates by yourself.

I finished the section creating all certificates, kublets restart fine, but still 1 node only shows.

v1.7 is not stable now, but I think I will try it. And make sure you turn off the firewalld, is there hardware firewall from your cloud provider prevent the communication of your masters?

v1.7.0 is in release state. Yes, I have disabled firewalld & selinux. There is no additional firewall on the VPS. Please let me know how you fare. I am ready to give it another go, but will wait for a response from you.

node join is kubectl command or kubeadm command? Or is that v1.7.0 exclusive command?

My bad kubeadm join --token

That would join as a worker node, not a master. In v1.6.4 kubeadm reset first in k8s-master2 and k8s-master3, then copy /etc/kubernetes/kubelet.conf and /etc/kubernetes/pki to k8s-master2 and k8s-master3. You will find that

It means that kubelet in k8s-master2 and k8s-master3 up and connected the cluster, you can try it.

It means that kubelet in k8s-master2 and k8s-master3 up and connected the cluster, you can try it.

Okay I kubeadm reset masters2/3, then scp /etc/kubernetes/kubelet.conf & scp -r /etc/kubernetes/pki/* then systemctl restart docker kublet
Now I have changed from:
NAME                   STATUS    AGE       VERSION
vps135abc.vps.ovh.eu   Ready     4m        v1.7.0
vps135abc.vps.ovh.eu   Ready     2m        v1.7.0
vps135abc.vps.ovh.eu   Ready     2m        v1.7.0
[root@vps135abc ~]# kubectl get nodes
NAME                   STATUS     AGE       VERSION
vps135abc.vps.ovh.eu   Ready      1h        v1.7.0
vps135abc.vps.ovh.eu   NotReady   1h        v1.7.0
vps135abc.vps.ovh.eu   NotReady   1h        v1.7.0

Just do it step by step:

on k8s-master1 copy kube-apiserver.yaml to k8s-master2 and k8s-master3, and edit kube-apiserver.yaml file in k8s-master2 and k8s-master3, replace ${HOST_IP} to current host ip

vi /etc/kubernetes/manifests/kube-apiserver.yaml
    - --advertise-address=${HOST_IP}

restart docker and kubelet on k8s-master2 and k8s-master3

systemctl restart docker kubelet

Then you will find that apiserver and kube-proxy startup on k8s-master2 and k8s-master3
kubectl get pods --all-namespaces -o wide

Maybe you should reset all your master nodes first then redo the kubeadm init in your first master

Yes, I am having "nodelost" show from master 1 right now. I will reset.

I went through the guide exactly as listed, same exact results at the same parts. I can't get masters 2/3 to ever show up like this.

I can confirm this is working with 1.6.4, so issue is with 1.7.0. I will analyze differences in config files and report back. Should probably close these two issues. I will make another with details how to get 1.7.0 working when successful.

So you can try to use these commands to install exact version of components:
$ yum search docker --showduplicates
$ yum install docker-1.12.6-16.el7.centos.x86_64

$ yum search kubelet --showduplicates
$ yum install kubelet-1.6.4-0.x86_64

$ yum search kubeadm --showduplicates
$ yum install kubeadm-1.6.4-0.x86_64

$ yum search kubernetes-cni --showduplicates
$ yum install kubernetes-cni-0.5.1-0.x86_64

$ systemctl enable docker && systemctl start docker
$ systemctl enable kubelet && systemctl start kubelet

I will try v1.7.0 lately.

Yes I using -1.6.4 for kubelet, kubeadm, and kubectl. Everything works with 1.6 branch. 1.7 is the issue. I'm now focused on taking a few steps back, and learning other HA getups for 1.6+. I see some limitations with your setup. You should email me we can chat about this.

My gmail<EMAIL_ADDRESS>

You need to also specify kubectl-1.6.4 else it will pull 1.7.0

You are right, I have updated the document

v1.7.0 enhance security to add NodeRestriction admission control, it will prevent master nodes to join the cluster.
$ vi /etc/kubernetes/manifests/kube-apiserver.yaml
#    - --admission-control=Initializers,NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota
    - --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,ResourceQuota,DefaultTolerationSeconds

i same problem
I use kubernetes 1.8:
***$kubeadm version***
kubeadm version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-08T18:27:48Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

my config: /etc/kubernetes/manifests/kube-apiserver.yaml
``log
- --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSec
onds,ResourceQuota
run on master-2, and master-3 still:
```log
root@backend-023:~# kubectl get nodes
NAME                  STATUS    ROLES     AGE       VERSION
backend-023   Ready     master    1h        v1.8.2

@cookeem @webeindustry could be reopen issue? thanks

@mtchuyen can you show me the kubelet's log?

thanks for reply!
Here kubelet's log:

backend-052 is master-2

Nov 13 14:34:33 backend-052 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Nov 13 14:34:33 backend-052 systemd[1]: Started kubelet: The Kubernetes Node Agent.
Nov 13 14:34:33 backend-052 kubelet[2024]: I1113 14:34:33.822758    2024 feature_gate.go:156] feature gates: map[]
Nov 13 14:34:33 backend-052 kubelet[2024]: I1113 14:34:33.822842    2024 controller.go:114] kubelet config controller: starting controller
Nov 13 14:34:33 backend-052 kubelet[2024]: I1113 14:34:33.822848    2024 controller.go:118] kubelet config controller: validating combination of defaults and flags
Nov 13 14:34:34 backend-052 kubelet[2024]: I1113 14:34:34.197458    2024 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Nov 13 14:34:34 backend-052 kubelet[2024]: I1113 14:34:34.197509    2024 client.go:95] Start docker client with request timeout=2m0s
Nov 13 14:34:34 backend-052 kubelet[2024]: W1113 14:34:34.198548    2024 cni.go:196] Unable to update cni config: No networks found in /etc/cni/net.d
Nov 13 14:34:34 backend-052 kubelet[2024]: I1113 14:34:34.204017    2024 feature_gate.go:156] feature gates: map[]
Nov 13 14:34:34 backend-052 kubelet[2024]: W1113 14:34:34.204248    2024 server.go:289] --cloud-provider=auto-detect is deprecated. The desired cloud provider should be set explicitly
Nov 13 14:34:34 backend-052 kubelet[2024]: I1113 14:34:34.230757    2024 certificate_manager.go:361] Requesting new certificat

I copy /etc/cni/net.d/10-flannel.conf from master-1 then restart kubelet:
*** systemctl status kubelet****

● kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-kubeadm.conf
   Active: active (running) since Mon 2017-11-13 14:45:58 +07; 7s ago
     Docs: http://kubernetes.io/docs/
 Main PID: 8997 (kubelet)
    Tasks: 11
   Memory: 12.2M
      CPU: 196ms
   CGroup: /system.slice/kubelet.service
           └─8997 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.

Nov 13 14:45:58 backend-052 systemd[1]: Started kubelet: The Kubernetes Node Agent.
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779333    8997 feature_gate.go:156] feature gates: map[]
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779398    8997 controller.go:114] kubelet config controller: startin
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779403    8997 controller.go:118] kubelet config controller: validat
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.794076    8997 client.go:75] Connecting to docker on unix:///var/run
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.794384    8997 client.go:95] Start docker client with request timeou
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.803127    8997 feature_gate.go:156] feature gates: map[]
Nov 13 14:45:58 backend-052 kubelet[8997]: W1113 14:45:58.803332    8997 server.go:289] --cloud-provider=auto-detect is deprec
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.834492    8997 certificate_manager.go:361] Requesting new certifi

and:
Nov 13 14:45:58 backend-052 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Nov 13 14:45:58 backend-052 systemd[1]: Started kubelet: The Kubernetes Node Agent.
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779333    8997 feature_gate.go:156] feature gates: map[]
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779398    8997 controller.go:114] kubelet config controller: starting controller
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.779403    8997 controller.go:118] kubelet config controller: validating combination of defaults and flags
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.794076    8997 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.794384    8997 client.go:95] Start docker client with request timeout=2m0s
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.803127    8997 feature_gate.go:156] feature gates: map[]
Nov 13 14:45:58 backend-052 kubelet[8997]: W1113 14:45:58.803332    8997 server.go:289] --cloud-provider=auto-detect is deprecated. The desired cloud provider should be set explicitly
Nov 13 14:45:58 backend-052 kubelet[8997]: I1113 14:45:58.834492    8997 certificate_manager.go:361] Requesting new certificate.

Make sure your apiServerCertSANs and endpoints settings in kubeadm-init-v1.7.x.yaml is right, please show me your kubeadm-init-v1.7.x.yaml file, this file like below:
$ vi /root/kubeadm-ha/kubeadm-init-v1.7.x.yaml
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
kubernetesVersion: v1.7.0
networking:
  podSubnet: <IP_ADDRESS>/16
apiServerCertSANs:
- k8s-master1
- k8s-master2
- k8s-master3
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
etcd:
  endpoints:
  - http://<IP_ADDRESS>:2379
  - http://<IP_ADDRESS>:2379
  - http://<IP_ADDRESS>:2379

Because I use kube V.1.8, so I rename file config

kubeadm version

kubeadm version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-08T18:27:48Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

cat kubeadm-init-v1.8.x.yaml

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
kubernetesVersion: v1.8.0
networking:
  podSubnet: <IP_ADDRESS>/16
apiServerCertSANs:
- backend-023
- backend-052
- backend-055
- <ip_master1>
- <ip_master2>
- <ip_master3>
- <VIRTUAL_IP: ip_master2>
etcd:
  endpoints:
  - http://<ip_master1>:2379
  - http://<ip_master2>:2379
  - http://<ip_master3>:2379

Here is my container (some are newer version: flanneld,kube-xxx):

docker images

REPOSITORY                                               TAG                 IMAGE ID            CREATED             SIZE
nginx                                                    latest              40960efd7b8f        8 days ago          108 MB
gcr.io/google_containers/kube-apiserver-amd64            v1.8.2              6278a1092d08        2 weeks ago         194 MB
gcr.io/google_containers/kube-controller-manager-amd64   v1.8.2              5eabb0eae58b        2 weeks ago         129 MB
gcr.io/google_containers/kube-scheduler-amd64            v1.8.2              b48970f8473e        2 weeks ago         54.9 MB
gcr.io/google_containers/kube-proxy-amd64                v1.8.2              88e2c85d3d02        2 weeks ago         93.1 MB
gcr.io/google_containers/heapster-amd64                  v1.4.3              6450eba57f23        5 weeks ago         73.4 MB
gcr.io/google_containers/kubernetes-dashboard-amd64      v1.7.1              294879c6444e        5 weeks ago         128 MB
gcr.io/google_containers/k8s-dns-sidecar-amd64           1.14.5              fed89e8b4248        6 weeks ago         41.8 MB
gcr.io/google_containers/k8s-dns-kube-dns-amd64          1.14.5              512cd7425a73        6 weeks ago         49.4 MB
gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64     1.14.5              459944ce8cc4        6 weeks ago         41.4 MB
quay.io/coreos/flannel                                   v0.9.0-amd64        4c600a64a18a        7 weeks ago         51.3 MB
gcr.io/google_containers/heapster-influxdb-amd64         v1.3.3              577260d221db        2 months ago        12.5 MB
gcr.io/google_containers/etcd-amd64                      3.0.17              243830dae7dd        8 months ago        169 MB
gcr.io/google_containers/heapster-grafana-amd64          v4.0.2              a1956d2a1a16        9 months ago        131 MB
gcr.io/google_containers/pause-amd64                     3.0                 99e59f495ffa        18 months ago       747 kB

thanks.

Check log in master-1:

kubectl logs -n kube-system kube-controller-manager-backend-023

E1113 12:42:41.061323       1 certificate_controller.go:139] Sync csr-6zgzk failed with : recognized csr "csr-6zgzk" as [nodeclient] but subject access review was not approved
E1113 12:43:56.948538       1 certificate_controller.go:139] Sync csr-7v85l failed with : recognized csr "csr-7v85l" as [nodeclient] but subject access review was not approved
E1113 12:46:13.572616       1 certificate_controller.go:139] Sync csr-4wgsj failed with : recognized csr "csr-4wgsj" as [nodeclient] but subject access review was not approved
E1113 12:48:05.949856       1 certificate_controller.go:139] Sync csr-f24wn failed with : recognized csr "csr-f24wn" as [nodeclient] but subject access review was not approved
E1113 12:49:24.632010       1 certificate_controller.go:139] Sync csr-7v85l failed with : recognized csr "csr-7v85l" as [nodeclient] but subject access review was not approved
E1113 12:53:36.424552       1 certificate_controller.go:139] Sync csr-6zgzk failed with : recognized csr "csr-6zgzk" as [nodeclient] but subject access review was not approved

kubectl logs -n kube-system kube-scheduler-backend-023

E1113 12:06:46.443935       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
E1113 12:06:46.444638       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1beta1.StatefulSet: Get https://<IP_ADDRESS>:6443/apis/apps/v1beta1/statefulsets?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
E1113 12:06:46.445821       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1beta1.ReplicaSet: Get https://<IP_ADDRESS>:6443/apis/extensions/v1beta1/replicasets?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
E1113 12:06:46.446870       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:73: Failed to list *v1.ReplicationController: Get https://<IP_ADDRESS>:6443/api/v1/replicationcontrollers?resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused

Hi @cookeem , the problem is livenessProbe in apiserver.
see comment by pipejakob in https://github.com/kubernetes/kubeadm/issues/193
thanks.

It seems that certs not match, so livenessProbe failed, the nodes can not joined the cluster.
E1113 12:42:41.061323       1 certificate_controller.go:139] Sync csr-6zgzk failed with : recognized csr "csr-6zgzk" as [nodeclient] but subject access review was not approved
E1113 12:43:56.948538       1 certificate_controller.go:139] Sync csr-7v85l failed with : recognized csr "csr-7v85l" as [nodeclient] but subject access review was not approved
E1113 12:46:13.572616       1 certificate_controller.go:139] Sync csr-4wgsj failed with : recognized csr "csr-4wgsj" as [nodeclient] but subject access review was not approved
E1113 12:48:05.949856       1 certificate_controller.go:139] Sync csr-f24wn failed with : recognized csr "csr-f24wn" as [nodeclient] but subject access review was not approved
E1113 12:49:24.632010       1 certificate_controller.go:139] Sync csr-7v85l failed with : recognized csr "csr-7v85l" as [nodeclient] but subject access review was not approved
E1113 12:53:36.424552       1 certificate_controller.go:139] Sync csr-6zgzk failed with : recognized csr "csr-6zgzk" as [nodeclient] but subject access review was not approved

Check this document: https://kubernetes.io/docs/admin/kubeadm/, make sure your certs create correctly.

I use certificates was generated by kubeadm (auto) and nothing change from your guide,

If create certificates failed, you can try to create by manual.
Just comment apiServerCertSANs settings in kubeadm-init-v1.8.x.yaml file:
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
kubernetesVersion: v1.8.0
networking:
  podSubnet: <IP_ADDRESS>/16
#apiServerCertSANs:
#- backend-023
#- backend-052
#- backend-055
#- <ip_master1>
#- <ip_master2>
#- <ip_master3>
#- <VIRTUAL_IP: ip_master2>
etcd:
  endpoints:
  - http://<ip_master1>:2379
  - http://<ip_master2>:2379
  - http://<ip_master3>:2379

On all master nodes create certificates by manual:

Create key file  apiserver-manual.key:

openssl genrsa -out apiserver-manual.key 2048

Create csr file apiserver-manual.csr:

openssl req -new -key apiserver-wudang.key -subj "/CN=kube-apiserver," -out apiserver-manual.csr

Create ext file apiserver-manual.ext:

vi apiserver-manual.ext
subjectAltName = DNS:${CURRENT_HOSTNAME},DNS:kubernetes,DNS:kubernetes.default,DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster.local, IP:${MASTER1_IP}, IP:${MASTER2_IP}, IP:${MASTER3_IP}, IP:${VIRTUAL_IP}

Use /etc/kubernetes/pki/ca.crt to create certificates apiserver-manual.crt:

openssl x509 -req -in apiserver-manual.csr -CA /etc/kubernetes/pki/ca.crt -CAkey /etc/kubernetes/pki/ca.key -CAcreateserial -out apiserver-manual.crt -days 365 -extfile apiserver-manual.ext

Replace kube-apiserver.yaml settings:

vi kube-apiserver.yaml
- --tls-cert-file=${YOUR_PATH}/apiserver-manual.crt
- --tls-private-key-file=${YOUR_PATH}/apiserver-manual.key

Restart your cluster and check it:

systemctl restart kubelet docker

thank @cookeem !


Automatic rule extraction based on routing.

Hi,
I've created a small addition which automatically extracts methods from the routing, because I always forget to update the config.
I think the bundle should have a feature like this (in an opt-in version of course).
https://gist.github.com/Padam87/ad4434502de71e32626fbb4daa7f1b47
If its okay, i will submit a PR. Alernatively, we could create a command which dumps the path rules to yaml.

I am not quite sure I understand what this is supposed to do. Can you explain a little more?

Instead of you having to specify the paths, this one does it automatically by going through the route collection.
For example if you have two routes for the /user/{id} url, it merges the methods used into an array.
It will end up almost as the same as the path collection you can specify in yml. You can check it in the gist, the cors.cache.php file is dumped by the cache warmer.
Then the config provider reads the rules...
The priority of this provider is 1, so the yml config takes precedence.

OK but.. is it automatically mapping all routes to allow cors on them? If so why not just allow all URLs in the config and be done with it?

This is specific. Exact methods for every route.

OK I see. Would be good to combine this with #43 to do it only for annotated routes and then it'd be quite powerful I think.

Closing as it seems nobody had any interest in pushing this further.


allow users to use a credis native setup

... instead of testing an unused variable
this change allows us to pass a credis_cluster object as $server and thus use a preconfigured sentinel setup.
and it is already tested in production
best regards.

Seeing as the current code lets you do the same exact thing by passing the object as the third argument instead of the first... Without modifications... This change is a backwards compatibility break, and doesn't actually add anything that isn't already there, so it probably won't be merged.

The only place i can locate, where Resque::$redis is assigned, seems to be here:
https://github.com/chrisboulton/php-resque/blob/968b7e6a307a2079051dfc571d2fc2be0546209f/lib/Resque.php#L62
(and maybe two lines above that).
You might notice the apparent lack of a third argument.
So yes, the current implementation of Resque_Redis does allow for a native setup, but the current implementation of Resque does not.
But i am always open for a configuration example with the current release that can use a sentinel setup.

Let me rephrase, then. If the issue is that nothing is actually passing the third argument to the Resque\Redis constructor, then the correct fix is to update the calling code to make use of this parameter, rather than negate its very existence by changing the one pair of lines that uses it.


Select box validation

How do i validate select  box with validator?
here is my react js code snippet

You're probably better asking this question over at https://stackoverflow.com/. There might be some wrapper libraries you could use.


Check if date is hidden, if so let the title go full width

before

after

Coverage remained the same at 15.91% when pulling bde766945394f014468ff065370424465072aeed on cleanup-rss-again into 52fcf00650652027f73e0e22c00cc3aec8892c5a on master.

:+1: