[WIP] fix issue 18789 - std.stdio messes up UTF conversions on output

I think I'm soon ready to give up on this. Latest surprise: Microsoft's fwide is useless ("unimplemented"). So orientation_ is bogus on that platform. With Microsoft, the distinction is ANSI/Unicode, not narrow/wide.
I can probably split off the wchar -> char case, though. That doesn't involve any file mode madness, as far as I can see. I'm going to look into that tomorrow.

I can probably split off the wchar -> char case, though. That doesn't involve any file mode madness, as far as I can see. I'm going to look into that tomorrow.

#6474

Rebooted without out the stuff that has already been merged and the debugging commits. Let's see where it breaks this time around.

I think we need to clarify what LockingTextWriter's mission statement is. Is it (A) print text in a readable form (to a terminal)? Or is it (B) write UTF-8 always?
If A, we should always enforce wide/Unicode mode, transcode to wchar_t, and call FPUTWC. This would fix writeln("Hello, wörld!"); on MICROSOFT_STDIO Windows, without needing chcp 65001 or similar nonsense. I don't know if DIGITAL_MARS_STDIO Windows can be made to work, because it doesn't seem to have a Unicode mode.
If B, we should always enforce binary mode, transcode to UTF-8, and call FPUTC.
If neither, what is LockingTextWriter's mission?

I think we need to clarify what LockingTextWriter's mission statement is.

Ignoring that, I've rewritten the unittest. Might pass now.

I think this is finally ready for review. buildkite says druntime is failing, but that seems unrelated.

I think this is finally ready for review.

Still waiting for someone to take a look at this.

I guess auto-merge doesn't work when buildkite is red? As far as I can tell, this is the error in druntime:
generated/linux/release/64/benchmark.o:benchmark/runbench.d:function _D3std5regex8internal9kickstart__T7ShiftOrTaZQl6__ctorMFNcNeKSQCiQChQCe2ir__T5RegexTaZQjAkZSQDmQDlQDiQDc__TQCvTaZQDb: error: undefined reference to '_D3std5range__T11SortedRangeTAkVAyaa6_61203c3d2062VEQByQBx18SortedRangeOptionsi0ZQCo6lengthMFNaNbNdNiNfZm'
I can't reproduce that locally. And I don't see how this PR could cause that undefined reference. What do I do now?

Yeah it's a known issue that sometimes the wrong druntime gets checked out


Migrate the diagnostics-app to Angular 16

Migrate the diagnostics app to angular 16.
Angular 12 has been deprecated, here we upgrade the angular version and remove the Angular flex layout deprecated dependency.
BUG: b: 295125382

BUG: b: 295125382

Just curious, do you have see how other team mark the bug id in PR?
Another thing, is it necessary to upgrade the version one by one? Is that not recommended to upgrade to v16 directly?

It seems we will also need to update CI bot version. Above test seems it is using 14.x

Codecov Report
Patch coverage has no change and project coverage change: -23.79% :warning:

Comparison is base (6ba4ce9) 73.17% compared to head (d7fb252) 49.38%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #36       +/-   ##
===========================================
- Coverage   73.17%   49.38%   -23.79%
===========================================
  Files           6       10        +4
  Lines         123       81       -42
  Branches       17        6       -11
===========================================
- Hits           90       40       -50
- Misses         33       41        +8

Files Changed
Coverage Δ

diagnostics-app/src/app/shared/shared.module.ts
100.00% <ø> (ø)

... and 15 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

For updating the version, the official guide [1] asks to update version one by one. Github can squash-merge this branch if we want to combine them all when we merge.

I don't really mind if you upload PR in squash or separate one. Just sharing that you can feel free to merge them if it takes time to separate PR.

Empty-Commit to refresh workflow cache

I guess there is some refresh button you can click?


ESLint Flat Config

Please support ESLint Flat Config.
I received the following error message when I try to use ES6 eslint.config.js:
Cannot start nuxt:  No ESLint configuration found in

Reproduction link: https://stackblitz.com/edit/nuxt-starter-41k9jt?file=eslint.config.js

+1

+1

how do you handle this issue ? what's the best way to do it work ?

Guys, please track https://github.com/nuxt-modules/eslint/pull/124.
If you are in a rush and can't wait to merge, use patch-pacakge for npm and yarn v1, use pnpm patch for pnpm, use yarn patch for yarn v2 and above.
And please reconsider. You may not need to run eslint in build process. See https://github.com/ModyQyW/vite-plugin-eslint2#faq for more info.


Align with spark's time zone awareness in handling unix timestamp

Describe the bug
In from_unixtiem/unix_timstamp, the result is different with spark's. The root cause is the current handling is not aware of the local time zone.
To Reproduce
Run query test with the stated expr.
Expected behavior
Get same result as spark.

Fixed by #1021.


dockerpty causing docker-compose run to exit with return code 1?

Hi,
I have this issue open on docker/compose and I think it might possibly belong here. I've tried looking around but I can pinpoint the problem. Can anyone help?
https://github.com/docker/compose/issues/1424
Thanks!

Also probably related to docker/compose#1483 and docker/compose#1429

Thanks for reporting - this was already known but we hadn't gotten round to fixing it and I didn't realise it had broken Compose. Fixed in https://github.com/d11wtq/dockerpty/pull/44.


pull request for e2e test at 12/16/2016 07:56:18

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


Add 280 characters support

Twitter now allows to post 280-character long posts. Rainbostream is currently cuts long tweets in a timeline with a link.
Please add 280 char tweets support both for composing and view.

280 char for composing should already be supported.
For viewing, I just opened a PR : #250

I need this in my life. Hope they merge your PR soon!

bump

Merged 13 days ago in #250, can be closed?


Benzene uses incorrect chemical formula

Benzene does not display as C6H6 in the UI.

Details
Fix on Nexus Mods: https://www.nexusmods.com/starfield/mods/5874
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Acquire Benzene or scan a planet that has Benzene on it.

Fixed in https://github.com/Starfield-Community-Patch/Starfield-Community-Patch/commit/872197c038e28e0296b3dffaf308cf887c09c803


[Feature request] Vencord or other client mod port?

We'd love to use this but we use Vencord ( a more lightweight easy-to-use mod for discord) but unfortunately, there's no compatibility layer. would love a port but know its difficult so no biggies ^^

yeah im gonna be real i can barely muster the energy to maintain one version of this plugin lol
if anyone wants to make and maintain a fork they are 100% welcome and greatly appreciated but i personally can't afford to do this. apologies

whoops wrong closure reason


Fix Rails 5 env deprecation warning

Using Rails 5.0.0.rc1 and the remember_me controller method from Devise::Controllers::Rememberable I was getting this warning a lot in my tests DEPRECATION WARNING: env is deprecated and will be removed from Rails 5.1

Thanks!


TypeError: Not Enough Arguements To Format A String

I've looked around but can't find a solution to this problem.
So every time i try to download a video or playlist it comes up with "TypeError: Not Enough Arguements To Format A String", I don't know why it's coming up or anything.

The question I am going to answer is "How should I report an issue with a supported site so that someone who is not a mind-reader can help with it?" and the answer is "Start here: https://github.com/ytdl-org/youtube-dl/issues/new?assignees=&labels=&template=1_broken_site.md".


expose pvc/pod level metrics (if not already exposed by kubelet and cadvisor)

Required k8s persistent volume & filesystem level metrics along with their grafana dashboards and few sane alerts preferably in kube-prometheus mixin format. I believe many of them are already exposed by kubelet (or embedded cadvisor), but we need to check and expose them for cgroup v2 hierarchy as well.

Utilisation metrics (both inodes and bytes usage) along with total space available. - Already being exposed by kubelet. Grafana dashboards and prometheus alerts are already provided by kube-prometheus stack.
Volume read and write throughput metrics both in terms of iops and bytes per second. - These seems to be exposed by cadvisor, but somehow not visible for cgroup v2 hierarchy.
Disk read & write IO latency -  Need to check if cadvisor already exposes these for cgroup v2.
No. of outstanding IO operations (preferably both queued as well as waiting for block device).
PV abnormality metrics due to degrading of underlying disk attached to node, fs corruption, accidental volume deletion on node etc. See if we can leverage volume health monitoring for the same.

Additionally we require following metrics related to pvc failure & provisioning to generate appropriate alerts.

pvc pending from long time. Explore if we can leverage kube-state-metrics to expose the same. Or we need to see if external provisioner already provide these metrics.
Other plugin level metrics (both controller and node driver) like client-go metrics, creation/expansion/deletion rpc rates, latency & failures.

Environment:

Kubernetes version (use kubectl version): >= 1.19
OS (e.g. from /etc/os-release): Debian 10

Most of the metrics are available via:

kube-state-metrics
cAdvisor
Node exporter (standard and include kubelet mount point metrics )

In addition to the above, the LVM node-plugin will expose metrics (in addition to what exposed by sample LVM textfile exporter) with required labels attached to the metrics to co-relate with metrics exposed via standard exporters enabled in the cluster.
Sample dashboard with workload using LVM Local PV showing the PV utilization and performance metrics

Thanks @kmova. Let me know as the dashboard gets ready & pushed somewhere. I would like to try them out in our playground clusters.

Need to verify the metrics. Previous comments mention that metrics are available. @abhilashshetty04  Could you please check this.

Not yet picked up to prioritise.

@abhilashshetty04 @w3aman please confirm if the dashboard contains the needed metrics.


create preset for a Depot

Currently, the presets don't offer a good option for mapping vehicle depots. I've seen people use amenity=bus_station and landuse=garages since they were the only suggested presets.
industrial=depot is already suggested by the landuse=industrial preset, so this PR creates a dedicated preset for that combination, and adds a field for depot=*

for tram depots, I've seen landuse=railway + railway=depot + depot=tram being used (although often only the landuse=railway is used), e.g. https://www.openstreetmap.org/way/82083538. By extension, tagging of other rail stock (e.g. subway, light_rail, train, etc.) could make more sense to live in the railway name space?!

okay, this may be more complicated than anticipated :/ It would also be nice to call the preset "Vehicle Depot", but that wouldn't make sense for depot=container

@tyrasd I think that it would be ok to ignore them. ìndustriial=depot has 4.1k instances, while railway=depot has 121 instances. There are also quite a few other options to tag vehicle depots, so having a preset would help to unify the tagging.

Fair point. It's fine to have only the "generic" depot preset for now. Though, I think we should remove "tram/train/… depot" from the terms of the new preset.
Later, a dedicated tram/train/… depot preset can be added easily.

unify the tagging

This would be a job for a proper tagging proposal :wink:

okay, terms updated


USHIFT-4081: Skip new sig-network-edge idling tests

Which issue(s) this PR addresses:

Closes #

/lgtm

/test ocp-full-conformance-rhel-eus


[4-bit optim] Update doc on torch version requirement

See https://github.com/pytorch/ao/issues/744#issuecomment-2312462039

Fixed issue with 4-bit Adam. Now 4-bit Adam works with PyTorch 2.3 likes in the past. Hopefully CI is grenn. The issue seems to be related to this https://github.com/pytorch/pytorch/issues/128649
I kinda feel conflicted about this change, since now the optimizer state is flattened, instead of having the same shape as param. Will try a better solution in the future. I think it has to do with dynamic compile also. 4-bit optim is giving us a lot of headaches 🤣.


[Proposal] Upgrade helm and tiller to v2.6.0

Hi, Rancher team
Since Kubernetes has been upgrade to v1.7 from rancher v1.6.6, but old helm version does not support many features of K8S 1.7 until helm v2.6.0, can you please upgrade tiller and helm client to v2.6.0 from Rancher v1.6.8 stable? Thanks a lot.

We added some documentation on updating tiller and helm here: http://rancher.com/docs/rancher/v1.6/en/kubernetes/addons/#upgrading-helm
For v1.8 we have tasks to update the addons as described here: https://github.com/rancher/rancher/issues/9776
Let me check what the plan is for v1.7 in the next release.

The upgrade document can be considered as a workaround, if kubernetes-addon container restarted it should be changed back to the old version right? Currently I have to customize the rancher k8s image to replace till version.

True, we have this issue to cover that. https://github.com/rancher/rancher/issues/10045
Closing this as both cases are covered, please reply if you don't agree.


Add an option to support renderToStaticMarkup method

Reactjs provides the method renderToStaticMarkup which is very useful when we need to render a page server side but not edit it client side. This method doesn't add all the extra react specific data-attributes so the produced markup is lot cleaner.

I am working on a pull request to resolve this

Merged the pull request, thank you! :)


Register event on creation and delete on deletion.

Needs to be rebased after unused var is removed.

cherry-picked and pushed to master


Fix building with llvm 13

std::string getName(ID Id, ArrayRef<Type *> Tys); was removed in https://github.com/llvm/llvm-project/commit/bb8ce25e88218be60d2a4ea9c9b0b721809eff27 and is contained in llvmorg-13.0.0-rc1 and onward.

@junrushao1994 Please take a quick look at this simple change.

This was already fixed as a part of PR9138.


Publish security advisories via github

The security audit uncovered some issues, it would be great to have those published
https://github.com/falcosecurity/falco/security/advisories

/assign @leodido

/open
On Sat, 22 Feb 2020 at 18:26, stale[bot]<EMAIL_ADDRESS>wrote:

Closed #978 https://github.com/falcosecurity/falco/issues/978.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/978?email_source=notifications&email_token=AAA5J4ZXBSDGSHLUZS3SR2LREFN4ZA5CNFSM4J3XS42KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOW2HYVMI#event-3062860465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5J43TKC7LXDXZRGSRDSLREFN4ZANCNFSM4J3XS42A
.

--
L.

Thanks stalebot but no thanks

Keep it open. We need to revamp the discussion about this.
L.
On Fri, Jun 26, 2020 at 1:03 PM stale[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/978#issuecomment-650120974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5J42RQMJKADQHJLYNJMLRYR6AJANCNFSM4J3XS42A
.

/help

@leodido:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


vscodium: 1.60.0 -> 1.60.1

Motivation for this change
Upgrades vscodium from 1.60.0 to 1.60.1
This PR was automatically generated by nixpkgs-upkeep.

CI workflow that created this PR.
Internal tag: 026ff2586fa5e6377d2474337ac7a1c2.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 138003 at 6ddc49fa run on x86_64-linux 1

2 packages built successfully:

vscodium
vscodium-fhs

Result of nixpkgs-review pr 138003 run on x86_64-darwin 1

1 package built:

vscodium

Thank you!

vscodium is failing on x86_64-linux on hydra due to a hash mismatch
https://hydra.nixos.org/build/153218137

Thanks for pointing this out!
I don't understand this one however, the log say https://hydra.nixos.org/build/153218137/nixlog/1
hash mismatch in fixed-output derivation '/nix/store/4wlfdjg5z3hw9g74s4pwgyd65hcv61kz-VSCodium-linux-x64-1.60.1.tar.gz':
  wanted: sha256:1lzw3svnaf11g8g50w3plymy16rbb71lcag46y1q3xdh62jbq8nc
  got:    sha256:03z6wpzbvf046sl1mjvvcshy5czvr4bq2f3ajlr8bj39y9df93h9

and master has exactly that hash
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/vscode/vscodium.nix#L16

oh it's the opposite, I'm not thinking clearly, it's a bit late.

fix is at https://github.com/NixOS/nixpkgs/pull/138161


Pull in cop benchmarks into the repo itself

Looking through issues and pull requests to understand context is no fun. Allows easy checking if a cop is still relevant and properly documents why a cop exists.
I'd appreciate some feedback on the format if anyone got some. I'm not entirely convinced yet myself:
# frozen_string_literal: true

require_relative 'helper'

# https://github.com/rubocop/rubocop-performance/pull/92

umethod = String.instance_method(:start_with?)
bench_perf_and_mem(result: <<~RESULT) do |x|
  ********* IPS *********
  ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [x86_64-linux]
  Warming up --------------------------------------
             bind.call   592.951k i/100ms
             bind_call     1.151M i/100ms
  Calculating -------------------------------------
             bind.call      5.925M (± 0.5%) i/s  (168.78 ns/i) -     29.648M in   5.003961s
             bind_call     11.575M (± 1.4%) i/s   (86.40 ns/i) -     58.722M in   5.074287s

  Comparison:
             bind_call: 11574705.6 i/s
             bind.call:  5924959.7 i/s - 1.95x  slower

  ********* MEMORY *********
  Calculating -------------------------------------
             bind.call    80.000  memsize (     0.000  retained)
                           1.000  objects (     0.000  retained)
                           0.000  strings (     0.000  retained)
             bind_call     0.000  memsize (     0.000  retained)
                           0.000  objects (     0.000  retained)
                           0.000  strings (     0.000  retained)

  Comparison:
             bind_call:          0 allocated
             bind.call:         80 allocated - Infx more
RESULT
  x.report('bind.call') { umethod.bind('hello, world').call('hello') }
  x.report('bind_call') { umethod.bind_call('hello, world', 'hello') }
end

Draft for now, pulling these all an is a bit of a chore. I plan to add remaining ones over time.

@koic would you merge this when finished? For example, you could have added the benchmark from #469 here: https://github.com/rubocop/rubocop-performance/blob/8003a18f36f0d14522a46e55768bca6e6de2ee1b/bench/big_decimal_with_numeric_argument.rb


Compact mode hides the whole header

Lovelace configuration:
custom_header:
  compact_mode: true

Installation: HACS
Lovelave mode: Storage

pip packages:
hacs-frontend<PHONE_NUMBER>58
hass-nabucasa           0.35.0
home-assistant-frontend 20200824.0
homeassistant           0.114.3

custom-header version: 1.7.2
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

Do you only have one Lovelace view?

Any errors from the two places mentioned in the bots comment above?

Sorry I should have included a screenshot with the header, here it is:

Yes version 1.7.2:

I have multiple Lovelace views
No error in the logs (I have it set to error by default)
Both Chromium and Firefox are affected

Please let me know how I can help you reproduce/trace the problem :pig:

Strange. The only config you use is what you shared above, just compact_mode: true?

Yes exactly, nothing more, nothing less

Just got home and did some testing on my Linux machine and can't replicate this. With no errors either I don't have much to go on. What other custom frontend addons do you have installed?

I have removed some HACS integrations (google dark theme, simple thermostat) and now it works.
'Problem' is that if I add these integrations again it still works.
I restart home assistant and wait for a minute for everything to be completely started when I install/uninstall anything in HACS.
Sorry for the trouble, if it happens again I'll track more carefully the integrations


Bad default initializer values for messages with enum types

When yielding Enum definitions in ProtoFile.generate_header() using NamingStyleC, __str()__ will call enum_entry() which will return self.underscore(name).upper().
Soon afterwards, the initializer values for message structs are also yielded, but Field.get_initializer() will not make any special treatment for enum default values and hence will set inner_init = str(self.default).
Now, if the enum was defined with mixed case names of the type and/or entries, the initializer values will be illegal since the generated enum definitions in the header file is upper case.
Something as simple as adding the following to nanopb_generator.py:874 will do, but there might be other side effects in doing so (?):
elif self.pbtype in ('ENUM', 'UENUM'):
  inner_init = str(self.default).upper()

Can you include a proto file that reproduces this issue?

Test.zip
The attached file will typedef a my_enum_t enum with two upper case value names and a msg_t message. The #define MSG_INIT_DEFAULT will have an undefined camel case value set.
Please disregard my quick and dirty suggestion in the first message, it solved my immediate problem but does not work on the attached example (it will not underscore the upper case values correctly), so it feels as if some conversion of the Field to an Enum is required for this to work, otherwise it will not reproduce the same naming convention.


Pasting new line char into settings field causing problem, see gif

Description
Pasting new line char into settings field causing problem, see gif
Steps to Reproduce

Copy invisible newline char
Paste it into settings field
It starts pasting white spaces automatically( still works even if you close settings tab and reopen it again )

Reproduces how often: [100%]
Versions
atom --version
Atom    : 1.15.0
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
apm -v
apm  1.15.3
npm  3.10.5
node 4.4.5 x64
python 2.7.10
git 2.11.0
Additional Information

Does this happen with any package setting or just the settings for the package in your GIF?  Also which package is that?  I'm not quite fast enough to see it in the GIF.

@rsese It is not related to any particular package, you can try in Settings -> Editor -> Font Family

Great thanks for confirming :+1:  I can reproduce on macOS 10.12.3 and in safe mode with the Settings > Editor > Font Family field.
I did notice however that I can't reproduce in other fields (e.g. Settings > Editor > Font Size and Settings > Packages > autocomplete-plus > Scope Blacklist both don't show the same behavior).
Do you see the behavior on any field or just certain fields?

@rsese yes, it happens only on some fields

Thanks for confirming - I updated the issue body to mention the specific field where we could reproduce and the other fields where we couldn't.


Some devices have problem with tap

Hi,
I've tested the library on a lot of simulator devices and also on real devices (iphone 5,6,6s and 7)
Everything was playing perfect except iphone 7 (the simulator with the same ios version was playing good). When I try to tap the second item to be selected nothing happens then I tried to tap it very quick and a lot of times it worked (No clue why) but again to tap the other one I had to tap it a lot of times and very quick.
I deleted my app, restarted my phone, deleted derived data and install it again but the problem insist
Edit
I use xcode 9 and my iphone 7 that has this problem runs with ios 11.

Thanks for creating an issue @mvorisis. The problem should have been fixed in v2.0.2.


release 0.3.0

Updated changelog

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

Merging [#239][cc-pull] into [master][cc-base-branch] will not change coverage

File ...igchaindb/version.py was modified. more

Misses 0
Partials 0
Hits +2

@@             master       #239   diff @@
==========================================
  Files            19         19
  Lines          1092       1092
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            950        950
  Misses          142        142
  Partials          0          0

Powered by Codecov. Last updated by [bf46d7d...2ac3e36][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bigchaindb/bigchaindb/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bigchaindb/bigchaindb/compare/bf46d7d497e5f74e049be8b33d5733aa8b073247...2ac3e360f7b7cea6726d7904651c1baca4b31ec8
[cc-pull]: https://codecov.io/gh/bigchaindb/bigchaindb/pull/239?src=pr


Hue Shift Brushes

Hey, I replied in #8 here https://github.com/Deevad/deevad-krita-brushpresets/pull/8#issuecomment-370398219 , I'll close this one. :-)


mkDep with other inputs doesn't merge recursively

I was going through your code trying to adapt it (mainly for pr-tracker module) but looked at the flakegen flake.in.nix
take for example
nix-on-droid = mkDep {
		...
        inputs.home-manager.follows = "home-manager";
};

If you look at the nix flake metadata or in the flake.lock you can see there is two home-manager instances. home-manager_2 exists because in the flake.nix the home-manager follows statement is missing.
Seems in mkDep the // won't work with recursive merges.
I found this https://stackoverflow.com/a/54505212/8608146 but don't know how I can get the lib from nixpkgs when it is one of the inputs itself. This is all getting too complicated to just avoid copy pasting one  inputs.nixpkgs.follows = "nixpkgs"; line.
I'm not critisising your config just an observation. I too am trying to modularise/refactor too much in my config.

 Thank you for telling me, never would've realised lmao. I can't imagine if i had gotten a bug because of that.

Let me know in case you do fix it. I personally have dropped using genflake/flakegen.

Fixed! You can see my latest commit. I think that should cover it since there are no other attribute sets under each input?

Ok I'll check it out, you may close the issue.


[FSDE-1099] Removed localhost:8000 from Cypress tests

https://ctl.atlassian.net/browse/FSDE-1099

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-95/1/. :white_check_mark:

You can check this PRs instance in https://ad301899150479bf1731d7591a5eccbb13b1dd26-chi-pr.enterprise.ctl.io

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-95/2/. :white_check_mark:

You can check this PRs instance in https://be8b5aec6eecb7d842013610c059a11a2a6af2e4-chi-pr.enterprise.ctl.io


feat: equals() should be nullable

close https://github.com/ocpddev/jsensible/issues/4

mark as draft since this is WIP

Please resolve the conflicts and provide the test cases for this.

Getting no responses, I implemented this myself in fb478e7711d792c95df976be523573c2dea566b6


Order confirmed page

Edit the order confirmed page based on Miro wireframes: https://miro.com/app/board/uXjVK5bTFAc=/?track=true&utm_source=notification&utm_medium=email&utm_campaign=approve-request&utm_content=go-to-miro

For all confirmed orders

add coshop logo
order reference number not order num
add coshop orders support email address

For credit card payments:

display pick up info

For bank payment

display bank payment instructions
display pick up details

Screenshot of order confirmation page for stripe payment for review:

Screenshot of order confirmation for manual bank payment option.
Questions:
How will the payment be recorded and customer be informed of pick up instructions?


Feature request: Allow creation of nested folders from 'New Folder' button in Explorer

VSCode Version: Version 1.11.1 (1.11.1) d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39
OS Version: Mac OS X... uh.. OS X... er... macOS 10.12.4 (16E195)

Steps to Reproduce:

Open a folder (File -> Open -> any folder)
Click the 'New Folder' button in the mini-toobar in Explorer.
Type a nested folder name, such as src/main/java

Current Behavior:
An error stating The name 'src/main/java' is not valid as a file or folder name.  Please choose a different name.
Requested behavior:
Allow creation of nested folders when creating a new folder.
(Basically, do what mkdir -p src/main/java would do)
Motivation:
In the world of Java development, the need to create nested folders happens all over the place.
If you follow Maven and Java standards, even a 'hello world' program will end up in src/main/java/com/example/helloworld/HelloWorld.java.  As much as I wish Java development wasn't filled with nested folders, It would be really handy to be able to generate all of those folders at once.  (Java IDEs like IntelliJ IDEA in fact let you do just this).

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.

@bpasero I did search through the issue log as thorough as I could before reporting this, but was unable to find it.  My apologies.  Do you have a reference to the issue?

https://github.com/Microsoft/vscode/issues/12893


Use absolute path the realization config when calling ngen

https://github.com/NOAA-OWP/ngen-cal/blob/a52c1534a6f0b5525396488ed58d1cc15d9cb464/python/ngen_cal/src/ngen/cal/ngen.py#L206-L208
Is there a reason we aren't using realization or realization.resolve()?

I get why we do this now. We should do a better job to check in the realization config file that we are given that it does not contain any relative directories and if it does, we should try to resolve them. Likewise, if ngen fails to run, we should emit a message that using relative paths in any config file is likely to cause issues give the way that we execute models in their own directory.


Find or write a snapsvg plugin for setting x and y position individually

so you can change one without changing the other.  Currently you have to set the transform property, which controls both x and y position.

https://github.com/ibrierley/Snap.svg.FreeTransform seems to be working fine!


npm package: do not publish examples dir

configure npmignore to avoid publishing examples directory
(https://github.com/jaanauati/react-dfp/issues/85).

https://github.com/jaanauati/react-dfp/issues/85


Refactor

Refactor the contract:
* Add common and story dir
* Add event
* Code style: init_scenes -> initScenes ...
* public -> external
* Add modifier
* location: uint8 -> uint256

Warning: Continuous integration has not been set up!

yeah, I should add ci first. For that, i should refactor the test case first.


how to test images with the size of 512 ?

I have trained the model with images which's size is equal to 512. However, the error occured when I test the images with the size of 512.  The error is shown as RuntimeError: shape '[1, 24532, 5]' is invalid for input of size 122640.    File "/layers/functions/detection.py", line 38, in forward
self.num_classes).transpose(2, 1). how can I solve the problem? thank you very much

Were you able to fix this problem?


Not compatible with npm --ignore-scripts

If using the security best practice with ignore-scripts (either through --ignore-scripts npm CLI flag, or in .npmrc), the asset generator fails with:
transforming (1) index.html
PWA v0.19.0
WARNING: you must install the following dev dependencies to use the PWA assets generator:
- "@vite-pwa/assets-generator"
- "sharp" (should be installed when installing @vite-pwa/assets-generator)
- "sharp-ico" (should be installed when installing @vite-pwa/assets-generator) Error:
Something went wrong installing the "sharp" module

Cannot find module '../build/Release/sharp-linux-x64.node'

This looks to be related to usage of --ignore-scripts. Not seen any other packages in vite ecosystem that requires the ability of running install/post-install scripts, so if the above analysis is correct, should this requirement (possibility to run install scripts) be mentioned in the docs? :slightly_smiling_face:

https://cheatsheetseries.owasp.org/cheatsheets/NPM_Security_Cheat_Sheet.html#3-minimize-attack-surfaces-by-ignoring-run-scripts
Number 3 at https://snyk.io/blog/ten-npm-security-best-practices/

Looks like this problem solves itself when updating sharp dependency (https://github.com/lovell/sharp/issues/3750#issuecomment-1751172728). I.e. #38 also solves this issue.


Implement Self-Spawn

Implement the SVM Self-Spawn SMIP.

Closing this issue since the [Simple Coin Iteration #4](is:issue is:open label:simple-coin-iteration-4 ) is all about the Self Spawn.


Removing the reference guide from the docs.

I should have prepared a speech.

Hmm, sorry to spoil the celebration, but would it be possible to keep the old section links working somehow? I'm sure there are lots of links to it on the web, especially to the compilation page.
https://duckduckgo.com/?kg=p&q="docs.cython.org%2Fen%2Flatest%2Fsrc%2Freference"

Sorry, my bad. The github diff was hiding the back-links you added in the huge deletion diff. Excellent job!

Nice!


 There is no hard and fast rule for determining what adds value to the project, or what is small enough: use common sense.

However, it's common sense that common sense the least common of the senses.
A commit should implement one (and only one) thing. If commit A renders the project in an inconsistent state, and it has to be followed by another commit B, which tidies up A, it follows that A+B is a logically atomic commit, since neither A nor B stand by themselves.
Examples (in chronological order)

First feat: implement a feature with some bug then  fix: fix the bug in the feature. The initial implementation of the feature should not include such a bug.
First build: remove foo dependency then refactor: refactor code not to use foo (removing a dependency does not stand by itself, the project cannot be built until the refactor has been applied)
First refactor: refactor code not to use foo then build: remove foo dependency (unless it's an incremental refactoring that gradually removes foo up to the point where foo can be safely removed, it seems that the second commit is an immediate consequece of the first one, and none of them would stand by itself).

See also #1 and #12
Proposal: clarify that a logically atomic commit stands by itself
- These guidelines encourage logically atomic commits, i.e. commits that
+ These guidelines encourage logically atomic commits, i.e. commits that stand by themselves,
are big enough to add value to the project, and small enough to read, review and revert.

Note that "WIP" commits are necessarily not atomically.


Expose coverage script as an npm script

https://github.com/anvilresearch/connect/pull/273 adds as npm script. Thanks for catching this!


install error.

I tried Windows XP Professional SP3 x86 - Integral Edition 2022.9.9.
It installed without errors on a Lenovo T61P.
However when I try to install "LegacyUpdate-1.4.1.exe" I receive an error.

Known issue with 1.4.1 at the moment, see #37 for more info. Workaround is to use 1.4 for now. Will close this since it's already covered by that issue thread.


Issue #4160: Clearer log messages during upgrade

Added a log message indicating that the server will be shutdown after the
database upgrade
Suppressed log messages after the upgrade by disabling features that are
started after the Upgrade feature and before the shutdown

link issue #4160


Oracle testing for the Ethereum

Motivation
The Oracle has been implemented for the Linera protocol. We need effective testing.
Proposal
The following was done:

Implement the Linera smart contract that tracks the state.
It works in the following way: An Ethereum update is done and events are emitted. Then the Linera smart contract can be pinged to update its state.
Data types are added to the ethereum.rs to provide the data types for the smart contract.
The end-to-end test is introduced.
The linera-ethereum crate can now compile under WASM though the test cannot pass under WASM.

The Ethereum-tracker should be enabled only if the Ethereum feature is enabled. But I am not sure that this is possible.
Test Plan
The end-to-end test is introduced. Currently, it does not pass because of the linking stage for WASM.
Release Plan
When it passes, the documentation should be added.
Links

reviewer checklist

That PR is ended because another one has been introduced which changes the code a lot so a rebase would have been more work.


global: Fail ExecCmdWithStdout if no nodes were found to execute command

Otherwise retry functions using this will not retry if no nodes are found(transient conditon after reboot).

Removing after discussion with @klaskosk


Add ability to create clusterIsuser and certificates after crd creation

What this PR does / why we need it: This PR creates certificate and clusterIssuers crd during helm installation. This was not possible before helm introduced  "helm.sh/hook": crd-install annotations.
I could create the crds, certificates and clusterIssuer on a fresh cluster.  It requires helm >= 2.10.0
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Create certificates and clusterIssuers crds with helm

I'd like to understand your requirements and use case for this.
Notably, why do you want to create these resources as part of the over-arching installation of cert-manager, rather than either as a separate chart (or further decentralised in individual application charts).
Creating these here introduces more complexity to our chart, and given the configuration options exposed in values.yaml, I don't feel provide a meaningful/useful layer of abstraction for users.
Now that we use the crd-install hooks, it should even be possible to define your own chart containing just the Issuer/Certificate resources you want, with a helm dependency on the cert-manager chart too (if you do want to create your Issuer/Certificate resources alongside the same helm release as cert-manager itself).

thanks @munnerz, I ended up creating a new local chart with these objects.


Update buildspec.yml

Thank you for the PR, @dpandurskilabforty.
Sadly, since I am no longer with Stelligent, I cannot merge it.
Even though I am the original author, the repo is owned by the stelligent organization.
More importantly, mu is no longer being maintained, per mu's README.md.  Stelligent was great fun, back in the day!


Changed distribution function to upload via Twine per issue #828

Fixes issue #828

The --repository-url https://test.pypi.org/legacy/ should probably be removed. I don't think distributing via the PyPI test server is a good idea.


Improve process aound feature freeze exceptions

Follow up to escalation path and post freeze exceptions, ideas for improving the process:

Any changes raised for exception need to be complete, approved and ready for merge. (also approved by assignee)
Changes need to be first discussed and brought to the attention of the release management working group (Escalation to the TSC should not be the first step). Maintainers of the given subsystem that the change touches should be involved.
Reestablish a CCB (Change Control Board) as the second step in the escalation process to deal with exceptions for a release. Define CCB structure, ie. 4-5 TSC members.
As the final step, a change can be escalated to the TSC and a vote is called.

Process WG:

@nashif: this is related to an exception request we received to merge a PR in the v3.2 feature freeze. The idea is that there should be an escalation path where the TSC is not the first place we raise requests for exceptions. Gaps here are to document the escalation process and establish a decision making body that can deal with these issues before the TSC.
@mbolivar-nordic so you're looking concretely for changes to https://docs.zephyrproject.org/latest/project/release_process.html#stabilization-phase that we will hold release managers to
Take it to the TSC - no objections to the proposal or its language

Where can I found the proposed changes to the stabilisation phase documentation?

Approved at TSC


Translate May 8 covid report into Russian

Happy weekend @nextstrain/russian,
The situation report from 2020-05-08 is ready to be translated to Russian. This week's report is short and sweet and focuses on Asia. We tried to tie the trees in with other epidemiological info; I'm curious to hear what you think of it. As with other regional reports (and really all reports) if you don't have time or are not able to translate this report, totally fine. Just let me know.
We've been publishing weekly reports on covid for two months now! As such, we're taking time this next week to re-evaluate narratives and figure out how we can make these reports as useful as possible going forward. I'd welcome your feedback on the situation reports -- what you find useful, what you don't, how often you think reports should be published, how these reports help (or don't help) Russian speakers.
Branch to translate on: sit-rep_ru
File to translate: https://github.com/nextstrain/translations/blob/sit-rep_ru/narratives/translations_ncov_sit-rep_ru_2020-05-08.md You can translate directly in this file, but please remember to push often as other people may be working on the translation!
Link to preview: https://nextstrain.org/community/narratives/nextstrain/translations@sit-rep_ru/ncov/sit-rep/ru/2020-05-08
Twitter post to translate:
“Want to learn more about outbreaks in Asia? This week's situation report uses #SARSCoV2 genomes to track the recent spread of #COVID19 in Asia. The report is now available in Russian. Thank you @, @, and @ for the rapid translation."
Thanks so much for your help -- it's always a pleasure to work with you. See below for standard translation stuff.
Best,
Cassia
Logistics
Please update the translations board as you work on the translation: https://github.com/orgs/nextstrain/projects/7
Please assign yourself to the translation if you’re working on it this week.
When a translation is ready for publication -- at minimum meaning two people have worked on it and both agree that it’s ready -- please create a pull request to merge to master and tag me and the issue in it!
Discussion board for your team is here: https://github.com/orgs/nextstrain/teams/russian
Standard rules for translation:
Note that the file to translate is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.) Comments to help with translation are noted in comment symbols like <! -- Comment -->.
Please add your name under translators: with new line, tab, and dash, formatted just like authors are. Please also add a link to your professional page (can use Twitter) under translatorLinks:.
Note: You may know of other great resources available in Russian; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Thanks for understanding.
At minimum, I require two sets of eyes on every translation; one of those people should have a background in phylogenetics. Although if you have more, that’s fine too.
Feel free to use a live, online editor like hackmd (sign in with GitHub) to translate together.

I’ve finished proofreading, it looks great, I added just a few wording suggestions. Thank you to @irina95511  for doing all the work this time!
Here is the tweet translation:
"Хотите узнать больше о вспышках в Азии? На этой неделе ситуационный отчет использует геномные данные #SARSCoV2, чтобы отслеживать недавнее распространение #COVID19 в Азии. Отчет теперь доступен на русском языке. Спасибо @MEKlab и @varvarakozyreva за быстрый перевод. "

Published and tweeted: https://nextstrain.org/narratives/ncov/sit-rep/ru/2020-05-08
Thank you gals! If you have feedback on these reports, I'd welcome it :)


Remove storing provision request info into map[]

Need to fix the storing part of provision request info.

Fixed


Can't close an Application that listenes to an stdin-subscription

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
I am trying to listen to stdin and send a Message every time a line is read.
It works, but I can't close the program.
I am unsure if this issue is related to #1670.
Example code:
use tokio::io::{stdin, AsyncReadExt};
use iced::{
    widget::{Text, Button, column},
    Application, Element, Settings, Theme, Command, Subscription,
};

struct App {
    s: String,
}

#[derive(Debug, Clone)]
enum Message {
    Update(String),
    Pressed,
}

impl Application for App {
    type Message = Message;
    type Theme = Theme;
    type Executor = iced::executor::Default;
    type Flags = ();

    fn new(_flags: Self::Flags) -> (Self, Command<Message>) {
        (Self { s: "No Content".to_owned() }, Command::none())
    }

    fn title(&self) -> String {
        "Test".to_owned()
    }

    fn update(&mut self, msg: Message) -> Command<Self::Message> {
        use Message::*;
        match msg {
            Update(s) => self.s = s,
            Pressed => println!("pressed"),
        }
        Command::none()
    }

    fn view(&self) -> Element<'_, Message> {
        column![
            Text::new(&self.s),
            Button::new("Wallah").on_press(Message::Pressed),
        ].into()
    }

    fn subscription(&self) -> Subscription<Message> {
        some_worker()
        //Subscription::none()
    }
}

fn some_worker() -> Subscription<Message> {
    struct SomeWorker;
    iced::subscription::unfold(
        std::any::TypeId::of::<SomeWorker>(),
        (),
        |_| async move {
            let mut stdin = stdin();
            let mut buf = [0; 100];
            stdin.read(&mut buf).await.unwrap();
            (Some(Message::Update(String::from_utf8(buf.to_vec()).unwrap())), ())
        }
    )
}

fn main() -> iced::Result {
    App::run(Settings {
        exit_on_close_request: true,
       ..Default::default()
    })
}

What is the expected behavior?
Clicking on the close button closes the program.
Pressing Super+Q (shortcut to close a window) closes the program.
Version
0.7
Operative System
Linux
Do you have any log output?
No response

I encountered a similar issue a while ago.
After some digging, it looks like this is caused by tokio::Runtime's behavior to wait for all blocking tasks to finish before it drops. And looking at Stdin's implementation, it does spawn a blocking thread. Alternatively, as an example, using async_std in your case seems to work.
fn some_worker_async_std() -> Subscription<Message> {
    use async_std::io::stdin;
    use async_std::prelude::*;

    struct SomeWorker;
    iced::subscription::unfold(
        std::any::TypeId::of::<SomeWorker>(),
        (),
        |_| async move {
            let mut stdin = stdin();
            let mut buf = [0; 100];
            stdin.read(&mut buf).await.unwrap();
            (Some(Message::Update(String::from_utf8(buf.to_vec()).unwrap())), ())
        }
    )
}

I think one possible solution is to add a shutdown method to Executor, but I'm not sure what the go is here.

I encountered a similar issue a while ago.
After some digging, it looks like this is caused by tokio::Runtime's behavior to wait for all blocking tasks to finish before it drops. And looking at Stdin's implementation, it does spawn a blocking thread. Alternatively, as an example, using async_std in your case seems to work.
fn some_worker_async_std() -> Subscription<Message> {
    use async_std::io::stdin;
    use async_std::prelude::*;

    struct SomeWorker;
    iced::subscription::unfold(
        std::any::TypeId::of::<SomeWorker>(),
        (),
        |_| async move {
            let mut stdin = stdin();
            let mut buf = [0; 100];
            stdin.read(&mut buf).await.unwrap();
            (Some(Message::Update(String::from_utf8(buf.to_vec()).unwrap())), ())
        }
    )
}

I think one possible solution is to add a shutdown method to Executor, but I'm not sure what the go is here.

Thanks @schctl, now it works.


ImportError: cannot import name 'LoRAAttnAddedKVProcessor' from 'diffusers.models.attention_processor'

Hello, thanks for your amazing work! I'd like to know which diffusers the project use?

Hi,
I'm using 0.18.1 but I think most versions before diffusers introduced PEFT should work.
For this specific error you can also simply delete this line and this entire class since they are unused and just left as an example for adding new score distillation losses.


[Feature] Peer discovery and sync provider nodes

With the bootnodes coming under increasing pressure and handling mulitple responsibilities including providing peer lists and acting as sync providers to new nodes in the network, it would be desirable to create a lightweight node binary specialised in providing peer lists (perhaps working in concert with a network crawler) and sync provider nodes, designed to share their chainstate.
The (wip) setup would be as follows:

A new peer has a list of addresses of the official peer discovery nodes (we should ditch the name "bootstrapper" to avoid confusion); it could also know a list of sync providers, but they would not be the initial point of "entry" into the network.
The peer discovery nodes have regular contact with the crawler(s) and each other; the crawler can let them know what peers no longer appear live, to remove those from active peer list distribution, and recommend peers based on their available capacity and centrality.
The peering nodes might want to know which sync provider nodes have the most available capacity and provide those to new peers (perhaps at most one at once?).
If the sync nodes are capped, the peer discovery nodes would not return them.

Tracking:

[x] merge binaries with sync providers replacing bootnodes: #1101.
[x] migrate to using beacons as well as sync providers on testnet.
[x] reinstate stricter peering rules for sync providers: #1158.

Implemented by #1221.


cargo sqlx prepare only works after cargo clean

This may already be solved, as I'm running on version 0.4.0-beta.1.
Issue
I run cargo sqlx prepare -- --bin <bin name> and get a correctly specified sqlx-data.json file. However, if I run it again, I now get the "empty" file, only specifying what db I'm using:
{
  "db": "PostgreSQL"
}

And along with this, I get warning: no queries found; do you have the `offline` feature enabled, which seems off, since I do have "offline" enabled.
Indeed the same issue arises if I run cargo sqlx prepare --check -- --bin <bin name>
Workaround
If I run cargo clean before the commands, everything works fine. This is both in terms of rerunning the builder, and running --check.
What Else I've Tried

From https://github.com/launchbadge/sqlx/pull/722, I tried just manually deleting ./target/sqlx instead of full cargo clean but that didn't work - the folder is empty anyway.
I tried just deleting target/CACHEDIR.TAG, didn't work; same for target/.rustc_info.json
I trashed just ./target/debug and that worked... But this is rather similar to running cargo clean I guess
On quick search, didn't find a matching issue here or on Discord

Version
My sqlx setup:
[dependencies.sqlx]
version = "0.4.0-beta.1"
default-features = false
features = [ "runtime-tokio", "macros", "postgres", "uuid", "chrono", "migrate", "offline" ]

Postgres: postgres (PostgreSQL) 13.0 (Debian 13.0-1.pgdg100+1) running on postgres Docker (image 817f2d3d51ec)
Thanks
For the great crate!

I ran into the same issue on version 0.4.1 but my problem isn't fixed by running cargo clean or removing the target folder

I have the same issue, also on 0.4.0-beta.1. I'm not entirely sure whether this is related, but I also get the message
`cargo sqlx prepare` needs to be rerun

When I run cargo sqlx prepare --check -- --bin --<bin_name> immediately after cargo sqlx prepare -- --bin --<bin_name>.

Ah @Nehliin do you mean it works the first time for you, then refuses to work? Or you only ever get an empty sqlx-data.json file?
Also, quick update on my end: the issue persists with sqlx0.4.1, and with sqlx-cli 0.2.0. Possible it's something on my end!

@ColmanHumphrey It generates an almost empty sqlx-data.json (only contains top level databasename) but rerunning it with the empty json solved it for me.

In my case cargo can't see changes made to sql files (I use sqx::query_files_as!). I think this is the reason why cargo sqlx prepare generates empty file for me. In order to fix both cargo recompiling binary with proper sql files and generating non-empty json I need to touch src/lib.rs to make cargo see that it needs to recompile.

The query_file_as! issue is being tracked at #663. The fix should actually be relatively simple.

The cargo clean workaround is still needed in version cargo-sqlx 0.5.1.

Closing as duplicate of #663

@abonander: Please note that this issue is indeed a duplicate of #663 for the specialized case of query_as_file!, but more generally speaking a workaround is still necessary for the standard query! case as of 0.5.7.
Using cargo clean (as in the original comment) works but is obviously time-consuming.
My own workaround is to prefix both cargo sqlx prepare -- --bin <...> and cargo sqlx prepare --check -- --bin <...> with touch src/lib.rs. I haven't seen it mentioned above and it has been working for me so far.
The exact commands I use are:
## Generate sqlx metadata file
touch ./src/lib.rs && SQLX_OFFLINE=true cargo sqlx prepare -- --bin <my_bin_name>
## Check sqlx metadata file, fail if out of sync (CI)
touch ./src/lib.rs && SQLX_OFFLINE=true cargo sqlx prepare --check -- --bin <my_bin_name>

For context, I have this in my Cargo.toml:
[dependencies.sqlx]
version = "0.5.7"
default-features = false
features = [
  "runtime-actix-rustls",
  "macros",
  "postgres",
  "uuid",
  "chrono",
  "migrate",
  "offline"
]

Are there any plans to improve this experience or mention this as a caveat in the docs? Is there anything I could do that would be helpful?
Thanks (for looking into this but also for the awesome crate).

Yes. Updating cli fixed it for me.

I had the same issue and updating the CLI fixed it for me.

Same but only for a while. After doing it for a few crates in a workspace, it started failing again.

I am using "query_as!" and have this issue.
cargo sqlx prepare -- --workspace --all-targets --all-features
gives :No queries found: until cargo clean is issued.
Info

SQLx version: 0.7.1
SQLx features enabled: [ "runtime-tokio-native-tls", "postgres", "chrono", "uuid" ] }
Database server and version: Postgres 15
Operating system: Debian GNU/Linux 11
rustc --version: 1.73.0-nightly (864bdf784 2023-07-25)

I found that I experienced this issue with sqlx version 0.6.3 and sqlx-cli version 0.6.0. To fix, I ensured that I installed the exact correct CLI version on my machine;
cargo install --version 0.6.3 sqlx-cli


ArtifactResolutionException: Could not find artifact org.clojure:clojure:jar:1.7.0

Command and full output from my shell
$ clojure -A:native-image
Loading fc4.cli.wcb
Compiling fc4.cli.wcb
Exception in thread "main" org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.clojure:clojure:jar:1.7.0
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:422)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:224)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:201)
	at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:260)
	at clojure.tools.deps.alpha.extensions.maven$get_artifact.invokeStatic(maven.clj:95)
	at clojure.tools.deps.alpha.extensions.maven$get_artifact.invoke(maven.clj:91)
	at clojure.tools.deps.alpha.extensions.maven$eval395$fn__397.invoke(maven.clj:112)
	at clojure.lang.MultiFn.invoke(MultiFn.java:243)
	at clojure.tools.deps.alpha$lib_paths$fn__765.invoke(alpha.clj:203)
	at clojure.core.protocols$iter_reduce.invokeStatic(protocols.clj:49)
	at clojure.core.protocols$fn__7839.invokeStatic(protocols.clj:75)
	at clojure.core.protocols$fn__7839.invoke(protocols.clj:75)
	at clojure.core.protocols$fn__7781$G__7776__7794.invoke(protocols.clj:13)
	at clojure.core$reduce.invokeStatic(core.clj:6748)
	at clojure.core$reduce.invoke(core.clj:6730)
	at clojure.tools.deps.alpha$lib_paths.invokeStatic(alpha.clj:199)
	at clojure.tools.deps.alpha$lib_paths.invoke(alpha.clj:197)
	at clojure.tools.deps.alpha$resolve_deps.invokeStatic(alpha.clj:229)
	at clojure.tools.deps.alpha$resolve_deps.invoke(alpha.clj:210)
	at clj.native_image$deps__GT_classpath.invokeStatic(native_image.clj:12)
	at clj.native_image$deps__GT_classpath.invoke(native_image.clj:9)
	at clj.native_image$_main.invokeStatic(native_image.clj:61)
	at clj.native_image$_main.doInvoke(native_image.clj:43)
	at clojure.lang.RestFn.applyTo(RestFn.java:139)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.core$apply.invokeStatic(core.clj:657)
	at clojure.main$main_opt.invokeStatic(main.clj:317)
	at clojure.main$main_opt.invoke(main.clj:313)
	at clojure.main$main.invokeStatic(main.clj:424)
	at clojure.main$main.doInvoke(main.clj:387)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.main.main(main.java:37)
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.clojure:clojure:jar:1.7.0
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:412)
	... 32 more

My deps.edn
{:paths ["src/main" "src/cli"]
 :deps
 {org.clojure/core.async      {:mvn/version "0.4.474"}
  org.clojure/spec.alpha      {:mvn/version "0.2.168"}
  org.clojure/tools.cli       {:mvn/version "0.3.7"}
  circleci/clj-yaml           {:mvn/version "0.5.6"}
  potemkin                    {:mvn/version "0.4.5"}
  expound                     {:mvn/version "0.7.1"}
  com.cognitect/anomalies     {:mvn/version "0.1.12"}
  ;; test.chuck is in the main dependency list, rather than in the test profile,
  ;; because we’re using one of its generators in a spec in a source file.
  ;; This means we’ll also need org.clojure/test.check at runtime. Not ideal,
  ;; but worth it.
  com.gfredericks/test.chuck  {:mvn/version "0.2.9"}}

 :aliases {:dev       {:extra-deps  {org.clojure/tools.trace    {:mvn/version "0.7.9"}
                                     inspectable                {:mvn/version "0.2.2"}}}

           :test      {:extra-paths ["test" "src/test_utils"]
                       :extra-deps  {org.clojure/test.check     {:mvn/version "0.10.0-alpha3"}
                                     eftest                     {:mvn/version "0.5.3"}}}

           :test/run  {:main-opts   ["-m" "fc4.test-runner.runner"]}

           :test/coverage
                      {:extra-deps  {cloverage                  {:mvn/version "1.0.13"}}
                       :main-opts   ["-m" "cloverage.coverage"
                                     "--src-ns-path" "src/main"
                                     "--test-ns-path" "test"
                                     "--runner" ":fc4.test-runner"
                                     "--fail-threshold" "65"
                                     "--codecov"]}

           :lint      {:extra-deps  {github-JamesLaverack/cljfmt-runner
                                     {:git/url "https://github.com/JamesLaverack/cljfmt-runner"
                                      :sha     "51f85c9d6cc67107620749ceacd46120647fe107"}}
                       :main-opts   ["-m" "cljfmt-runner.check"]}

           :lint/fix  {:main-opts   ["-m" "cljfmt-runner.fix"]}

           :native-image
                      {:main-opts   ["-m clj.native-image fc4.cli.wcb"
                                     "-H:Name=wcb"]
                       :extra-deps  {clj.native-image
                                     {:git/url "https://github.com/taylorwood/clj.native-image.git"
                                      :sha "0f113d46f9f0d07e8a29545c636431ddf5360a7d"}}}

           :clj-next  {:override-deps {org.clojure/clojure {:mvn/version "1.10.0-alpha6"}}}}

 :jvm-opts ["-Dclojure.compiler.direct-linking=true"]}

If you’d like to try to reproduce in the context of my project, you can check out this branch.
I’m using these versions:

MacOS: 10.13.6
JDK: 1.8.0_171-b11
Clojure: stable <IP_ADDRESS>7, installed via Homebrew today
GraalVM Community Edition 1.0 RC7, downloaded today and manually “installed” under /usr/local/

I’d appreciate any assistance! Thank you!

Thanks for the detailed issue, I was able to reproduce it. I think there's a bug where the install- and user-level deps.edn files aren't considered, but I was able to workaround it by supplying the default Maven repo URLs and Clojure 1.9 dependency from install-level deps.edn:
 :deps {org.clojure/clojure {:mvn/version "1.9.0"}}
 ...
 :mvn/repos
 {"central" {:url "https://repo1.maven.org/maven2/"}
  "clojars" {:url "https://clojars.org/repo"}}

Another issue is the project entry point, which needs (:gen-class) added to the namespace declaration of fc4.cli.wcb, and (set! *warn-on-reflection* true) is a good idea too. native-image may also suggest --report-unsupported-elements-at-runtime and --delay-class-initialization-to-runtime=<class-name> for other issues.
But ultimately I run into what may be an issue with some usages of Clojure 1.9 as reported here https://github.com/oracle/graal/issues/612, which might be addressed in this branch https://github.com/clojure/clojure/compare/master...ghadishayban:graal-test#diff-d951a5cd799ae841ffcc6b45598180dbR1648. There's another GraalVM-specific fix in Clojure 1.10 beta, but that locking macro tweak isn't merged AFAIK.
Compiling a non-trivial project like this with native-image can be difficult (or impossible) at the moment (e.g. I haven't been able to get clojure.spec working) but regular progress is being made. FWIW I have some example projects here and here — some with fairly complex dependencies like http-kit, StanfordNLP, reflection workarounds, etc.

@taylorwood thank you so much for the investigation, explanation, the improvement to the tool, and all the super-helpful information! I really appreciate it!

I haven't been able to get clojure.spec working

@taylorwood any possible clue about this?
PS thx for making this tool


[Machine Learning] Tensorflow Multi-Person Pose Estimation with Python

Proposed title of article
Your title should be descriptive of the article/tutorial. Be Specific.
[Machine Learning](TensorFlow Multi-Person Pose Estimation with Python)
Proposed article introduction
The MoveNet model is a convolutional neural network model that runs on RGB images and predicts human joint locations of people in the image frame. The main differentiator between this MoveNet.MultiPose and its precedent, MoveNet.SinglePose model, is that this model is able to detect multiple people in the image frame at the same time while still achieving real-time speed. The model was designed to be run in the browser using TensorFlow.js or on devices using TensorFlow Lite, targeting movement/fitness activities.
In this tutorial, we will use a technique known as Multi-Person Pose Estimation to predicts human joint locations of people in an image frame. One of the most popular use cases is in kinematics.
Key takeaways
What are the 3-5 most important things the reader should understand or be able to do after reading this article?
Use this area to get your ideas down on the bulk of your article or tutorial.
By the end of this tutorial, a reader should be able to:

Install Multi-Person Movement model
Make detection using video and webcam
Draw key points and edges

References

TensorFlow Hub
MobileNetV2: Inverted Residuals and Linear Bottlenecks

Good afternoon and thank you for submitting your topic suggestion. @Bayler
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Great topic 🚀 , make sure it matches the following:

Adds value beyond what is in the official docs and what is covered in other blog sites.
To avoid potential article closure, it should not overlap with existing EngEd articles or incoming topic suggestions.

Please reference any relevant EngEd articles in yours and build a unique project - Approved.


TEP-0142: param substitutions not allowed in StepAction's script

Based on discussions in https://github.com/tektoncd/pipeline/issues/7497 and consensus in the API WG, we disallow direct parameter substitution in scripts. While we cannot do this for inlined-steps since it is a major breaking change in v1, we can do this in Step Actions.
In this PR we add validation that params cannot be directly replaced in scripts of StepActions. Based on Issue https://github.com/tektoncd/pipeline/issues/7497. The docs have been updated to inform this to the users and encourage the use of env vars in scripts instead.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has 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] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Param substitutions not allowed directly in StepAction's script

/kind feature

/assign @wlynch @vdemeester (based on discussions in API wg.)

/kind feature

/test check-pr-has-kind-label

 pkg/apis/pipeline/v1alpha1/stepaction_validation.go:79:24: S1002: should omit comparison to bool constant, can be simplified to `present` (gosimple)
	if errString != "" || present == true {

👼🏼


Karpenter infinitely launches and deletes node for a single pod

Version

Karpenter Version: v0.23.0

Kubernetes Version: v1.21.13
Expected Behavior
When karpenter is nominating the pod to be scheduled on the node, it should wait for the node to get into the Ready state and if for any reason, pod isn't getting scheduled or node got removed unexpectedly, it should nominate new node and scale up.
Actual Behavior
But in our case, it's nominating the pod for a node and by the time node gets into the ready state, karpenter nominates the pod for a different node or it could be possible that it deprovision the node first via consolidation & takes off that node. This behaviour resulted in the infinite node creation and deletion loop, and the pod remains in the pending state.
Steps to Reproduce the Problem
Don't have any specific steps to reproduce but it generally happens when there is a single pending pod.
Resource Specs and Logs
Provisioner spec:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  annotations:
    meta.helm.sh/release-name: karpenter
  labels:
    app.kubernetes.io/instance: karpenter
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: karpenter
    app.kubernetes.io/version: 0.23.0
    helm.sh/chart: karpenter-v0.23.0
  name: spot-nodes
spec:
  consolidation:
    enabled: true
  labels:
    karpenter: "true"
    node-group-category: nodes
  limits:
    resources:
      cpu: 1k
      memory: 5000Gi
  providerRef:
    name: spot-nodes
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - spot
  - key: karpenter.k8s.aws/instance-size
    operator: In
    values:
    - 2xlarge
    - 4xlarge
  - key: karpenter.k8s.aws/instance-family
    operator: In
    values:
    - c5
    - c5a
    - c4
    - m6a
    - m5
    - m5a
    - m5n
    - m4
    - m4a
    - t3
    - t3a
  - key: kubernetes.io/os
    operator: In
    values:
    - linux
  - key: kubernetes.io/arch
    operator: In
    values:
    - amd64
  weight: 50
status:
  resources:
    attachable-volumes-aws-ebs: "100"
    cpu: "32"
    ephemeral-storage: 519544512Ki
    memory: 130226392Ki
    pods: "232"

Karpenter logs
2023-04-25T03:39:35.245Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-020987220a940cc5b", "hostname": "ip-10-85-248-179.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T03:39:54.294Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-250-177.ap-south-1.compute.internal/t3a.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T03:39:54.378Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-177.ap-south-1.compute.internal"}
2023-04-25T03:40:17.133Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-177.ap-south-1.compute.internal"}
2023-04-25T03:42:41.821Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 1}
2023-04-25T03:42:41.822Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T03:42:41.822Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"4667m","memory":"5692Mi","pods":"8"} from types c5a.2xlarge, m5.2xlarge, c5.4xlarge, m5a.2xlarge, c5.2xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T03:42:43.835Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-06a3212ee8728ff96", "hostname": "ip-10-85-251-179.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T03:45:44.669Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-251-179.ap-south-1.compute.internal/t3a.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T03:45:44.708Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-179.ap-south-1.compute.internal"}
2023-04-25T03:45:44.910Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-179.ap-south-1.compute.internal"}
2023-04-25T04:10:10.800Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 4}
2023-04-25T04:10:10.800Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 4}
2023-04-25T04:10:10.813Z	INFO	controller.provisioner	launching node with 4 pods requesting {"cpu":"3467m","memory":"5288841738","pods":"11"} from types c4.4xlarge, c5a.2xlarge, m5a.2xlarge, m5a.4xlarge, m6a.2xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:10:13.037Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-039e2f2e82a7e845e", "hostname": "ip-10-85-249-177.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:10:30.334Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-251-11.ap-south-1.compute.internal/t3.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:10:30.368Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-11.ap-south-1.compute.internal"}
2023-04-25T04:11:23.112Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-11.ap-south-1.compute.internal"}
2023-04-25T04:13:17.479Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 2}
2023-04-25T04:13:17.479Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 2}
2023-04-25T04:13:17.479Z	INFO	controller.provisioner	launching node with 2 pods requesting {"cpu":"2367m","memory":"5016Mi","pods":"9"} from types m5.4xlarge, t3.2xlarge, c5a.4xlarge, t3a.2xlarge, m6a.4xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:13:19.561Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0e7b3e81af797406b", "hostname": "ip-10-85-251-246.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:18:58.954Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-249-169.ap-south-1.compute.internal/t3.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:18:58.993Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-249-169.ap-south-1.compute.internal"}
2023-04-25T04:19:41.714Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-249-169.ap-south-1.compute.internal"}
2023-04-25T04:25:28.290Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 1}
2023-04-25T04:25:28.290Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:25:28.290Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"4667m","memory":"5692Mi","pods":"8"} from types c4.2xlarge, c5a.2xlarge, m5.4xlarge, m4.2xlarge, m6a.4xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:25:30.534Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-011a04f5a0b7e6ae9", "hostname": "ip-10-85-250-104.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:25:51.093Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-248-179.ap-south-1.compute.internal/t3a.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:25:51.154Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-248-179.ap-south-1.compute.internal"}
2023-04-25T04:26:43.911Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-248-179.ap-south-1.compute.internal"}
2023-04-25T04:29:41.994Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 5}
2023-04-25T04:29:41.994Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 5}
2023-04-25T04:29:42.007Z	INFO	controller.provisioner	launching node with 5 pods requesting {"cpu":"4067m","memory":"6190857255","pods":"12"} from types m4.4xlarge, m5.4xlarge, m6a.2xlarge, m5a.2xlarge, c5a.2xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:29:44.784Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0463a4613f28d6d1c", "hostname": "ip-10-85-244-212.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1b", "capacity-type": "spot"}
2023-04-25T04:31:13.103Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-251-246.ap-south-1.compute.internal/t3a.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:31:13.139Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-246.ap-south-1.compute.internal"}
2023-04-25T04:31:13.350Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-246.ap-south-1.compute.internal"}
2023-04-25T04:33:25.978Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 1}
2023-04-25T04:33:25.978Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:33:25.978Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"1667m","memory":"2620Mi","pods":"8"} from types c5.4xlarge, c4.2xlarge, m5.2xlarge, c5a.4xlarge, m5a.4xlarge and 11 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:33:28.129Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0a14aaade8d335046", "hostname": "ip-10-85-246-22.ap-south-1.compute.internal", "instance-type": "t3a.2xlarge", "zone": "ap-south-1b", "capacity-type": "spot"}
2023-04-25T04:34:06.249Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 2}
2023-04-25T04:34:06.249Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:34:06.249Z	INFO	controller.provisioner	computed 1 unready node(s) will fit 1 pod(s)	{"commit": "5a7faa0-dirty"}
2023-04-25T04:34:06.249Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"817m","memory":"2492Mi","pods":"8"} from types m5.2xlarge, c5a.4xlarge, m5a.4xlarge, t3.2xlarge, c5.2xlarge and 7 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:34:07.972Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0c9083d2e65c44844", "hostname": "ip-10-85-251-85.ap-south-1.compute.internal", "instance-type": "t3.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:34:18.546Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-250-104.ap-south-1.compute.internal/t3a.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:34:18.594Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-104.ap-south-1.compute.internal"}
2023-04-25T04:34:41.314Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-104.ap-south-1.compute.internal"}
2023-04-25T04:35:16.322Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 2}
2023-04-25T04:35:16.322Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:35:16.322Z	INFO	controller.provisioner	computed 1 unready node(s) will fit 1 pod(s)	{"commit": "5a7faa0-dirty"}
2023-04-25T04:35:16.322Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"817m","memory":"2492Mi","pods":"8"} from types m6a.4xlarge, c5a.2xlarge, m5a.4xlarge, c5.2xlarge, t3.2xlarge and 7 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:35:18.320Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0e576df035fb40e06", "hostname": "ip-10-85-250-80.ap-south-1.compute.internal", "instance-type": "t3.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:36:20.743Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-251-85.ap-south-1.compute.internal/t3.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:36:20.833Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-85.ap-south-1.compute.internal"}
2023-04-25T04:36:21.088Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-251-85.ap-south-1.compute.internal"}
2023-04-25T04:36:21.695Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 1}
2023-04-25T04:36:21.695Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:36:21.695Z	INFO	controller.provisioner	launching node with 1 pods requesting {"cpu":"817m","memory":"2492Mi","pods":"8"} from types m6a.4xlarge, c5a.2xlarge, m5a.4xlarge, c5.2xlarge, t3.2xlarge and 7 other(s)	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes"}
2023-04-25T04:36:23.540Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "5a7faa0-dirty", "provisioner": "spot-nodes", "id": "i-0db7fc306810d776c", "hostname": "ip-10-85-251-68.ap-south-1.compute.internal", "instance-type": "t3.2xlarge", "zone": "ap-south-1c", "capacity-type": "spot"}
2023-04-25T04:37:19.456Z	INFO	controller.deprovisioning	deprovisioning via consolidation delete, terminating 1 nodes ip-10-85-250-80.ap-south-1.compute.internal/t3.2xlarge/spot	{"commit": "5a7faa0-dirty"}
2023-04-25T04:37:19.533Z	INFO	controller.termination	cordoned node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-80.ap-south-1.compute.internal"}
2023-04-25T04:37:19.727Z	INFO	controller.termination	deleted node	{"commit": "5a7faa0-dirty", "node": "ip-10-85-250-80.ap-south-1.compute.internal"}
2023-04-25T04:37:23.853Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "5a7faa0-dirty", "pods": 1}
2023-04-25T04:37:23.854Z	INFO	controller.provisioner	computed new node(s) to fit pod(s)	{"commit": "5a7faa0-dirty", "newNodes": 1, "pods": 1}
2023-04-25T04:37:23

Community Note

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

We've never seen this occur before.  Can you provide a pod spec that causes this?

We've had a lot of similar issues, where it replaced the same node type in the same AZ, supposedly because it wanted to consolidate.

Those issues appeared to have been caused by a preferred topology spread, I commented on the other issue.

Can you provide a pod spec that causes this?

It would also be good to see a kubectl describe output of the nodes that we launched so that we can see the resources that the node has vs. what the workload pod expects.

POD Spec: Its a fluentd pod
apiVersion: v1
kind: Pod
metadata:
  generateName: fluentd-
  labels:
    app: fluentd
    release: fluentd
    statefulset.kubernetes.io/pod-name: fluentd-0
  name: fluentd-0
  namespace: logging
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: StatefulSet
    name: fluentd
spec:
  containers:
  - args:
    - -c
    - /entrypoint.sh
    command:
    - /bin/bash
    env:
    - name: OUTPUT_BUFFER_CHUNK_LIMIT
      value: 3M
    - name: OUTPUT_BUFFER_QUEUE_LIMIT
      value: "20"
    - name: ES_SERVICE_ENDPOINT
      value: xxxxxxxxxxxx
    - name: ES_CLUSTER_ENDPOINT
      value: xxxxxxxxxxxx
    - name: AWS_ACCESS_KEY_ID
      valueFrom:
        secretKeyRef:
          key: accessKey
          name: xxxxxxxx
    - name: AWS_SECRET_ACCESS_KEY
      valueFrom:
        secretKeyRef:
          key: secretKey
          name: xxxxxxxx
    - name: RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR
      value: "0.5"
    - name: GEM_PATH
      value: /etc/fluent/plugin
    image: {{fluentd-image}}
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /fluentd.pod.healthcheck?json=%7B%22log%22%3A+%22health+check%22%7D
        port: 9880
        scheme: HTTP
      initialDelaySeconds: 60
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 2
    name: fluentd
    ports:
    - containerPort: 24220
      name: monitor-agent
      protocol: TCP
    - containerPort: 24224
      name: fluentd
      protocol: TCP
    - containerPort: 24231
      name: metrics
      protocol: TCP
    - containerPort: 9880
      name: http-input
      protocol: TCP
    resources:
      limits:
        cpu: 500m
        memory: 1Gi
      requests:
        cpu: 250m
        memory: 1Gi
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/fluent/config.d
      name: config-volume-fluentd
    - mountPath: /var/log/fluentd-buffers
      name: buffer
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-xxxx
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  hostname: fluentd-0
  nodeName: ip-xxxxxxxxx.ap-south-1.compute.internal
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: fluentd
  serviceAccountName: fluentd
  subdomain: fluentd
  terminationGracePeriodSeconds: 60
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: buffer
    persistentVolumeClaim:
      claimName: buffer-fluentd-0
  - configMap:
      defaultMode: 511
      name: fluentd
    name: config-volume-fluentd
  - name: kube-api-access-xxxxx
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace

Volume is in ap-south-1c, karpenter has launched t3.2xlarge node mostly every time in the same region.
Node describe output:
Name:               ip-xxxxxxxxxxxx.ap-south-1.compute.internal
Roles:              nodes,spot-worker
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=t3.2xlarge
                    beta.kubernetes.io/os=linux
                    failure-domain.beta.kubernetes.io/region=ap-south-1
                    failure-domain.beta.kubernetes.io/zone=ap-south-1c
                    k8s.io/cloud-provider-aws=xxxxxxxxxxxx
                    karpenter=true
                    karpenter.k8s.aws/instance-ami-id=ami-xxxxxxxxxxxx
                    karpenter.k8s.aws/instance-category=t
                    karpenter.k8s.aws/instance-cpu=8
                    karpenter.k8s.aws/instance-encryption-in-transit-supported=false
                    karpenter.k8s.aws/instance-family=t3
                    karpenter.k8s.aws/instance-generation=3
                    karpenter.k8s.aws/instance-hypervisor=nitro
                    karpenter.k8s.aws/instance-memory=32768
                    karpenter.k8s.aws/instance-pods=58
                    karpenter.k8s.aws/instance-size=2xlarge
                    karpenter.sh/capacity-type=spot
                    karpenter.sh/initialized=true
                    karpenter.sh/machine-name=
                    karpenter.sh/provisioner-name=spot-nodes
                    kops.k8s.io/instancegroup=nodes
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=ip-xxxxxxxxxxxx
                    kubernetes.io/os=linux
                    node-group-category=nodes
                    node-role.kubernetes.io/nodes=
                    node-role.kubernetes.io/spot-worker=true
                    node.kubernetes.io/instance-type=t3.2xlarge
                    topology.ebs.csi.aws.com/zone=ap-south-1c
                    topology.kubernetes.io/region=ap-south-1
                    topology.kubernetes.io/zone=ap-south-1c
Annotations:        csi.volume.kubernetes.io/nodeid: {"ebs.csi.aws.com":"i-xxxxxxxxxxxx"}
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  ip-xxxxxxxxxxxx.ap-south-1.compute.internal
  AcquireTime:     <unset>
Capacity:
  attachable-volumes-aws-ebs:  25
  cpu:                         8
  ephemeral-storage:           129886128Ki
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      32512568Ki
  pods:                        58
Allocatable:
  attachable-volumes-aws-ebs:  25
  cpu:                         7910m
  ephemeral-storage:<PHONE_NUMBER>43
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      31495736Ki
  pods:                        58

Are there any details in describe of the pod (in the events) around why the pod doesn't schedule? Do you see that the pod ever schedules to one of the nodes that is launched?