mined block disappeared ?

Hello,
I'm mining in solo with GPU. everything goes well until I saw the wallet notify me for find a new block but when I open the wallet there is not trace of the transaction.
strange ???
I opened the log file, found the submitted block section, took the hash then verify it into https://html.mastercalls.io/search
not any single trace of this transaction.
my wallet was locked when I was mining but normally it don't have to be unlocked right ?
want to attach log but don't know if it's safe or if I have to remove some informations ?
your help will be very appreciated.
PS : sorry for my bad english :)

This can happen if someone else mined the same block at the same time and their confirmation beat you to consensus.

It is safe to attach the debug.log from your client and/or miner.
Mined blocks do sometimes get orphaned when a competing block at the same height as yours gets another block added to it before yours does making their block part of the longer chain.

what your are saying guys is that I'm in very bad luck...
I think it's harder to do that than finding a block right ?
It should be a reward for that :))
here is the log by the way, I removed some informations.
htmlcoin_debug.log

I wonder if you are fully synced with block gain. Normally, it should be 0.999 for progress. If you are not correct height mined block will never be accepted.

Looking at the log explains it, you found block 160825, 5 seconds someone released blocks 160825 and 160826 on to the network making yours an orphan. This is probably not an accident but someone mining "greedily", it is pretty typical of those with greater hash power than the majority.

thank you very much for your help.
I have a better understanding now.
It's not an issue, but it was the first time I'm facing this situation.
by the way I believe in this this coin and I gone continue to mine it no matter what even with my ridiculous hashrate. :)

@bushstar so having more difficult hash doesn't give you the reward? Two blocks always win out one block?

The longest chain has the most work and will become the main chain over a shorter chain, that's how clients choose between different chains. A longer chain will win over a shorter chain.


Upmerge 2020 jul 13

Bring in upstream to 4ef29b34e3a29d7b77fddf7baf09990145ab1fed.
nrf: https://github.com/nrfconnect/sdk-nrf/pull/2585

@mbolivar Should Revert "[nrf noup] flash_map: remove PM related code" be added back?

@mbolivar Should Revert "[nrf noup] flash_map: remove PM related code" be added back?

@joerchan it is; it's been squashed. See the "cherry picked from" lines in the commit log for 5485a448018f495ecd17d09d2c80b8ecb00a62ea.

@mbolivar We will need https://github.com/zephyrproject-rtos/zephyr/pull/26925
Currently crashing in the LLPM sample without this. CC: @rugeGerritsen

Some checks failed. Please fix and resubmit.
Gitlint issues
Commit 1c8d0e1feb:
1: UC5 Title exceeds max length (80>75): "[nrf fromtree] Bluetooth: host: Fix infinite recursion in persistent advertising"
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.


Remove adobefonts override on the DSIG check

We have just updated the policy implemented on check/dsig to WARN users that they should remove the DSIG table (unless they're specially interested in still supporting OpenType features on fonts used on MS Office 2013).
See issue #3398 for more info.
This change in check behavior means the Adobe Fonts check override is not needed anymore (now it would actually be incorrect if kept unchanged):

@cjchapman FYI: I am removing that override on the adobefonts profile since the logic in the check implementation has flipped to suggest (with a WARN) the complete removal of the DSIG table instead of demanding (with a FAIL) the inclusion of a dummy signature.


How can I handle on scroll event?

I need to load more data while scrolling to the bottom. Please guide me how can I do that?

Here's how you can achieve infinite scrolling. Note that this solution does not limit the number of DOM nodes nor scopes or watchers inside the scrollable container. The more content you load the more memory gets used. ng-scrollable does also not consider the size or layout of individual content blocks. It's entirely up to you to calculate when and how much extra content you fetch.
First you listen to the scrollable.dimensions event in your controller.
$scope.$on('scrollable.dimensions', updateDimensions);

The event gets fired whenever dimensions of either the container or the content change.
Second, you set a scroll spy on the directive in your template. You need to use an expression that  evaluates to a settable variable or otherwise ng-scrollable will not write to it (the example assumes you export your controller under the name ctrl to the scope (using the controller as syntax):
<div scrollable data-spy-y="ctrl.spy"></div>

Third, you watch the spy variable in your controller and call your own update function on change
$scope.$watch('ctrl.scrollSpy', scrollUpdate);

I have implemented third one already. Anyway, thanks much for you response
$scope.$watch('ctrl.scrollSpy', scrollUpdate);


Update background image

Update text to fit current text.  You don't need to, it's just a background image to show I like to code!"

Made it fit current text but no easter egg


fix kafka CVE-2023-25194, update kafka client to 3.4.0

Description

fix kafka CVE-2023-25194
upgrade kafka client to 3.4.0, and upgrade three related jar
upgrade spring kafka test to 2.9.6, add one more kafka coordinator package

Issues Resolved

Resolves #2431
Related #2434
Related #2481

Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #2484 (517c3fe) into main (2df8acd) will decrease coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head 517c3fe differs from pull request most recent head fd9cb92. Consider uploading reports for the commit fd9cb92 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2484      +/-   ##
============================================
- Coverage     61.19%   61.17%   -0.03%
+ Complexity     3325     3323       -2
============================================
  Files           260      260
  Lines         18494    18494
  Branches       3268     3268
============================================
- Hits          11318    11314       -4
- Misses         5578     5581       +3
- Partials       1598     1599       +1

Impacted Files
Coverage Δ

...security/auditlog/sink/InternalOpenSearchSink.java
69.23% <0.00%> (-11.54%)
:arrow_down:

...search/security/transport/SecurityInterceptor.java
75.38% <0.00%> (-0.77%)
:arrow_down:

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

Backwards Compatibility failure for Windows CI is unrelated to changes in this PR.

@scrawfor99 FYI - these changes will not clearly backport to the 1.X/1.3 branches.  They will need to manually be converted since the build script were rewrittne


Add arm64 support

Or more arch support

It's not in plan, will consider it in the future.

arm64 supported, you can test from our testing repo
https://debian-repo.xxx.sb/nginx/

Thanks


gitomator-make-teams freaks out if trying to give maintainer role an organization admin

Happens that Gadal is admin (shouldn't be, but that's another story)
sorry it won't let me attach .yml
302-maintainer-issue.zip

Just so it's more visible, here's the error (from the log in your attached zip file):
E, [2017-02-04T18:49:48.520190 #69] ERROR -- : Cannot create/update Gadal's membership in ItWorkedYesterday - PUT https://api.github.com/teams/2260470/memberships/Gadal: 422 - User is already an admin of this organization, so they can't be promoted to a team maintainer.
Error summary:
  code: already_org_admin
  field: user
  resource: TeamMember // See: https://developer.github.com/v3/orgs/teams/#add-or-update-team-membership.
/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/response/raise_error.rb:16:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:9:in `block in call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:61:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:8:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/rack_builder.rb:139:in `build_response'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:377:in `run_request'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:177:in `put'
	/usr/local/bundle/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:37:in `put'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/client/organizations.rb:537:in `add_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/github/hosting_provider.rb:263:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service.rb:49:in `service_call'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service/hosting.rb:93:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:51:in `create_or_update_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:28:in `block in run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/util/script_util.rb:50:in `run_task'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:17:in `block in <top (required)>'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `<top (required)>'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `load'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `<main>'
I, [2017-02-04T18:49:48.758620 #69]  INFO -- : Creating team: MountBahen
I, [2017-02-04T18:49:49.489932 #69]  INFO -- : Adding ShisunXia to team MountBahen (role: member).
I, [2017-02-04T18:49:49.950047 #69]  INFO -- : Adding c4khatta to team MountBahen (role: member).
I, [2017-02-04T18:49:50.382930 #69]  INFO -- : Adding singhkaran to team MountBahen (role: member).
I, [2017-02-04T18:49:50.825951 #69]  INFO -- : Adding responsive309 to team MountBahen (role: member).
I, [2017-02-04T18:49:51.276991 #69]  INFO -- : Adding Iakis to team MountBahen (role: member).
I, [2017-02-04T18:49:51.792690 #69]  INFO -- : Adding JLyX to team MountBahen (role: member).
I, [2017-02-04T18:49:52.270662 #69]  INFO -- : Adding PhilHernandez to team MountBahen (role: member).
I, [2017-02-04T18:49:52.711119 #69]  INFO -- : Adding Gadal to team MountBahen (role: maintainer).
E, [2017-02-04T18:49:52.966691 #69] ERROR -- : Cannot create/update Gadal's membership in MountBahen - PUT https://api.github.com/teams/2260471/memberships/Gadal: 422 - User is already an admin of this organization, so they can't be promoted to a team maintainer.
Error summary:
  code: already_org_admin
  field: user
  resource: TeamMember // See: https://developer.github.com/v3/orgs/teams/#add-or-update-team-membership.
/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/response/raise_error.rb:16:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:9:in `block in call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:61:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:8:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/rack_builder.rb:139:in `build_response'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:377:in `run_request'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:177:in `put'
	/usr/local/bundle/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:37:in `put'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/client/organizations.rb:537:in `add_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/github/hosting_provider.rb:263:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service.rb:49:in `service_call'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service/hosting.rb:93:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:51:in `create_or_update_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:28:in `block in run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/util/script_util.rb:50:in `run_task'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:17:in `block in <top (required)>'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `<top (required)>'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `load'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `<main>'
I, [2017-02-04T18:49:53.200867 #69]  INFO -- : Creating team: GeninSquad
I, [2017-02-04T18:49:53.914619 #69]  INFO -- : Adding eddiequan to team GeninSquad (role: member).
I, [2017-02-04T18:49:54.354414 #69]  INFO -- : Adding chargadesilva to team GeninSquad (role: member).
I, [2017-02-04T18:49:54.806122 #69]  INFO -- : Adding Lyjame to team GeninSquad (role: member).
I, [2017-02-04T18:49:55.250809 #69]  INFO -- : Adding matt-duell to team GeninSquad (role: member).
I, [2017-02-04T18:49:55.687154 #69]  INFO -- : Adding Aaron-Tang to team GeninSquad (role: member).
I, [2017-02-04T18:49:56.121458 #69]  INFO -- : Adding admiralcoco to team GeninSquad (role: member).
I, [2017-02-04T18:49:56.580641 #69]  INFO -- : Adding tylerpham to team GeninSquad (role: member).
I, [2017-02-04T18:49:57.018386 #69]  INFO -- : Adding garysong23 to team GeninSquad (role: maintainer).
I, [2017-02-04T18:49:57.511232 #69]  INFO -- : Creating team: Awol
I, [2017-02-04T18:49:58.226787 #69]  INFO -- : Adding ChoJohn to team Awol (role: member).
I, [2017-02-04T18:49:58.697933 #69]  INFO -- : Adding racormaz to team Awol (role: member).
I, [2017-02-04T18:49:59.170070 #69]  INFO -- : Adding shreymahendru to team Awol (role: member).
I, [2017-02-04T18:49:59.658713 #69]  INFO -- : Adding TenzinLama to team Awol (role: member).
I, [2017-02-04T18:50:00.155015 #69]  INFO -- : Adding shubDhond to team Awol (role: member).
I, [2017-02-04T18:50:00.605999 #69]  INFO -- : Adding waynellin to team Awol (role: member).
I, [2017-02-04T18:50:01.098385 #69]  INFO -- : Adding davjhan to team Awol (role: member).
I, [2017-02-04T18:50:01.697714 #69]  INFO -- : Adding priyen to team Awol (role: maintainer).
I, [2017-02-04T18:50:02.421811 #69]  INFO -- : Creating team: LemonDudes
I, [2017-02-04T18:50:03.375469 #69]  INFO -- : Adding g3wanghc to team LemonDudes (role: member).
I, [2017-02-04T18:50:03.921848 #69]  INFO -- : Adding freeatnet to team LemonDudes (role: member).
I, [2017-02-04T18:50:04.541586 #69]  INFO -- : Adding sinaghaffari to team LemonDudes (role: member).
I, [2017-02-04T18:50:05.083471 #69]  INFO -- : Adding gohnicho to team LemonDudes (role: member).
I, [2017-02-04T18:50:05.591617 #69]  INFO -- : Adding bountygiver to team LemonDudes (role: member).
I, [2017-02-04T18:50:06.046333 #69]  INFO -- : Adding gomuramatsu to team LemonDudes (role: member).
I, [2017-02-04T18:50:06.681028 #69]  INFO -- : Adding Gadal to team LemonDudes (role: maintainer).
E, [2017-02-04T18:50:06.991851 #69] ERROR -- : Cannot create/update Gadal's membership in LemonDudes - PUT https://api.github.com/teams/2260474/memberships/Gadal: 422 - User is already an admin of this organization, so they can't be promoted to a team maintainer.
Error summary:
  code: already_org_admin
  field: user
  resource: TeamMember // See: https://developer.github.com/v3/orgs/teams/#add-or-update-team-membership.
/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/response/raise_error.rb:16:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:9:in `block in call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:61:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:8:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/rack_builder.rb:139:in `build_response'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:377:in `run_request'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:177:in `put'
	/usr/local/bundle/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:37:in `put'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/client/organizations.rb:537:in `add_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/github/hosting_provider.rb:263:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service.rb:49:in `service_call'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service/hosting.rb:93:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:51:in `create_or_update_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:28:in `block in run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/util/script_util.rb:50:in `run_task'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:17:in `block in <top (required)>'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `<top (required)>'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `load'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `<main>'
I, [2017-02-04T18:50:07.251186 #69]  INFO -- : Creating team: GhostBusters
I, [2017-02-04T18:50:08.101420 #69]  INFO -- : Adding gypsyfeng to team GhostBusters (role: member).
I, [2017-02-04T18:50:08.554901 #69]  INFO -- : Adding marc22alain to team GhostBusters (role: member).
I, [2017-02-04T18:50:09.022516 #69]  INFO -- : Adding JPinkney to team GhostBusters (role: member).
I, [2017-02-04T18:50:09.499593 #69]  INFO -- : Adding Rbandon64sp to team GhostBusters (role: member).
I, [2017-02-04T18:50:09.965734 #69]  INFO -- : Adding aa3993 to team GhostBusters (role: member).
I, [2017-02-04T18:50:10.479449 #69]  INFO -- : Adding garysong23 to team GhostBusters (role: maintainer).
I, [2017-02-04T18:50:10.990804 #69]  INFO -- : Creating team: Enterprise
I, [2017-02-04T18:50:11.732757 #69]  INFO -- : Adding allenaerostar to team Enterprise (role: member).
I, [2017-02-04T18:50:12.271078 #69]  INFO -- : Adding nguyenphillip to team Enterprise (role: member).
I, [2017-02-04T18:50:12.726997 #69]  INFO -- : Adding kevin-kc to team Enterprise (role: member).
I, [2017-02-04T18:50:13.179831 #69]  INFO -- : Adding anders-leung to team Enterprise (role: member).
I, [2017-02-04T18:50:13.626133 #69]  INFO -- : Adding cainky to team Enterprise (role: member).
I, [2017-02-04T18:50:14.087034 #69]  INFO -- : Adding Gadal to team Enterprise (role: maintainer).
E, [2017-02-04T18:50:14.352581 #69] ERROR -- : Cannot create/update Gadal's membership in Enterprise - PUT https://api.github.com/teams/2260476/memberships/Gadal: 422 - User is already an admin of this organization, so they can't be promoted to a team maintainer.
Error summary:
  code: already_org_admin
  field: user
  resource: TeamMember // See: https://developer.github.com/v3/orgs/teams/#add-or-update-team-membership.
/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/response/raise_error.rb:16:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:9:in `block in call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:61:in `on_complete'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/response.rb:8:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/rack_builder.rb:139:in `build_response'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:377:in `run_request'
	/usr/local/bundle/gems/faraday-0.11.0/lib/faraday/connection.rb:177:in `put'
	/usr/local/bundle/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/connection.rb:37:in `put'
	/usr/local/bundle/gems/octokit-4.6.2/lib/octokit/client/organizations.rb:537:in `add_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/github/hosting_provider.rb:263:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service.rb:49:in `service_call'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/service/hosting.rb:93:in `create_team_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:51:in `create_or_update_membership'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:28:in `block in run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/task/setup_team.rb:26:in `run'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/lib/gitomator/util/script_util.rb:50:in `run_task'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:17:in `block in <top (required)>'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `each'
	/usr/local/bundle/gems/gitomator-<IP_ADDRESS>/bin/gitomator-make-teams:16:in `<top (required)>'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `load'
	/usr/local/bundle/bin/gitomator-make-teams:22:in `<main>'
gitomator-image-root@d5e2c583fddd:/gitomator#

I'll have to read a little more about why the authors of Octokit chose this behaviour.
I understand that an organization admin already has maintainer permissions for all teams in the organization, but I don't understand why one would throw an error.
In fact, I can see a case where someone is demoted from an organization admin to a regular member of the organization, yet you still want them to keep their maintainer privileges for some team(s).


forbidden

Describe the bug
i have subcribe pro plan, but whenever i prompt it show forbidden

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-fvvthj
Steps to reproduce

go to bolt.new
prompt anything
get forbidden error

Expected behavior

after prompt, it should generate an answer based on what i have prompt

Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

https://github.com/stackblitz/bolt.new/issues/77#issuecomment-2395503410

Closing this in favour of #77.


Upload of Json file hanging

Upload a Json file on Friday March 15th and file is still not loaded. Status of file says Queued. Here is the log file from Cosmo DB
{
"id": "dXBsb2FkL0NsaW5pY2FsX3RyYWlscy9jbGluaWNhbF90cmFpbHMuanNvbg==",
"file_path": "upload/Clinical_trails/clinical_trails.json",
"file_name": "clinical_trails.json",
"state": "Queued",
"start_timestamp": "2024-03-15 18:55:59",
"state_description": "",
"state_timestamp": "2024-03-15 19:26:35",
"status_updates": [
{
"status": "File uploaded from browser to Azure Blob Storage",
"status_timestamp": "2024-03-15 18:55:59",
"status_classification": "Info"
},
{
"status": "Pipeline triggered by Blob Upload",
"status_timestamp": "2024-03-15 18:56:09",
"status_classification": "Info"
},
{
"status": "FileUploadedFunc - FileUploadedFunc function started",
"status_timestamp": "2024-03-15 18:56:09",
"status_classification": "Debug"
},
{
"status": "FileUploadedFunc - json file sent to submit queue. Visible in 249 seconds",
"status_timestamp": "2024-03-15 18:56:09",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - Starting to parse the non-PDF file",
"status_timestamp": "2024-03-15 19:00:43",
"status_classification": "Info"
},
{
"status": "FileLayoutParsingOther - Message received from non-pdf submit queue",
"status_timestamp": "2024-03-15 19:00:43",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - SAS token generated to access the file",
"status_timestamp": "2024-03-15 19:00:43",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - partitioning complete",
"status_timestamp": "2024-03-15 19:03:49",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - chunking complete. 19021 chunks created",
"status_timestamp": "2024-03-15 19:03:52",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - chunking stored.",
"status_timestamp": "2024-03-15 19:26:35",
"status_classification": "Debug"
},
{
"status": "FileLayoutParsingOther - message sent to enrichment queue",
"status_timestamp": "2024-03-15 19:26:35",
"status_classification": "Debug"
}
],
"_rid": "5hNMAOg52NbbAAAAAAAAAA==",
"_self": "dbs/5hNMAA==/colls/5hNMAOg52NY=/docs/5hNMAOg52NbbAAAAAAAAAA==/",
"_etag": ""13006aeb-0000-0100-0000-65f4a0eb0000"",
"_attachments": "attachments/",
"_ts":<PHONE_NUMBER>
}

I have sent over the email, with the files that are not uploading. Please let me know if there is anything else that you need from me.

Closing this as it seems the issue is related to large csv processing which was fixed in a recent push to main. If you encounter this do a pull from main, rebuild the functions app and resubmit the files.


Version mismatch?

Question
A couple of days ago a release v4.6.0 has been created. The version tag in the package.json still states 4.5.0. Do I oversee something or is there a missing update of the package.json? If this is the case we should make this a bug report.
I have some problems running the local development setup of geostyler-demo which pointed me to that and might be related.

Forgot to push to upstream. Sorry. Should be fixed now.


Port Subscriber from ZapJS to Python

Summary
Port Subscriber from ZapJS to Python
Reference
https://github.com/zapproject/zap-monorepo/blob/master/packages/Subscriber/src/index.ts
Definition of Done
All the functions are able to called and return the correct values.

Please refer to pull request #44  for review of this port.


Synthesize INSERT statements for structs

Is your feature request related to a problem? Please describe.
sqlx is an amazing crate and I love the ability to write compile-time-checked queries. The only thing that bothers me whenever I'm using the library is that INSERT statements are very verbose.  I always thought that there should be a "write-equivalent" to the "read-only" interface query_as! that allows me to automatically map Rust types to the underlying tables for INSERT statements.
Describe the solution you'd like
The most natural way to handle this would, in my opinion, be the implementation of a trait (let's call it sqlx::Insert) on structs that can be inserted into a database. The trait implementation can easily be synthesized via a macro. For example, the user could implement
#[derive(sqlx::Insert)]
#[sqlx(table_name = "users")]
struct User {
    email: String,
    name: String,
    age: u8,
}

which then synthesizes a method sqlx_insert which executes
sqlx::query!("INSERT INTO users (email, name, age) VALUES ($1, $2, $3)", self.email, self.name, self.age)

and which is compile-time-checked!
The real power of sqlx can be leveraged by synthesizing ON CONFLICT ... UPDATE queries by querying a table's primary key during compilation. Assuming email is a primary key, we can synthesize (again, compile-time-checked) queries like this:
sqlx::query!(r#"
    INSERT INTO users (email, name, age) VALUES ($1, $2, $3)
    ON CONFLICT (email) DO UPDATE SET name = EXCLUDED.name, age = EXCLUDED.age
"#, self.email, self.name, self.age)

The user would not be required to do anything but define the struct above.
Describe alternatives you've considered
n/a
Additional context
The main purpose of this issue is to gauge whether the proposal (or something along these lines) would be in scope for sqlx. If so, I would be happy to contribute, @delsner and I already implemented this as a third-party crate (which is, unfortunately, not yet published). Besides our shared love for open-source, a major driver for the desire to contribute is that synthesizing the ON CONFLICT ... UPDATE queries requires storing the primary key information for offline compilation which currently requires us to duplicate much of the logic in sqlx-cli.

@borchero this sounds really useful. If you end up publishing your own crate instead of submitting to sqlx, would you mind updating the issue, so anyone interested can try it out?

Related to this functionality - from https://github.com/launchbadge/sqlx/issues/2399#issuecomment-1812989849:

https://github.com/launchbadge/sqlx/issues/328 and sqlxinsert may be of interest also.

Any progress on this?

Creating a separate crate does not make sense as

synthesizing the ON CONFLICT ... UPDATE queries requires storing the primary key information for offline compilation which currently requires us to duplicate much of the logic in sqlx-cli

I'd be happy to add the functionality to this crate but this would require one of the maintainers to generally approve this idea first :)

I made my own ORM already, will upload it later, there is no need in this anymore


[Bug report] runtime-core.cjs.js missing validation

Description
For some odd reason, when i have a look at runtime-core.cjs.js inside of @vue/runtime-core/dist/runtime-core.cjs.js
It looks like this:

The validation is missing, i was expecting it to look like:
                    if ((process.env.NODE_ENV !== 'production') || __VUE_PROD_DEVTOOLS__) {
                        app._instance = vnode.component;
                        devtoolsInitApp(app, version);
                    }

I've patched it on my local, but i'm not sure exactly what's up with that it seems to be fine with the esm bundler.. but setting
process.env.NODE_ENV = 'production'

Seems to make it not use the esm but rather the runtime-core in which it lacks this check.
Reproduction
Repro doesn't have node_modules
Used Package Manager
npm
System Info
System:
    OS: Linux 5.15 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 1.14 GB / 15.05 GB
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 19.1.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 8.19.3 - /usr/local/bin/npm
  Utilities:
    Git: 2.30.2 - /usr/bin/git
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @vuepress/bundler-vite:  2.0.0-beta.53
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli:  2.0.0-beta.53
    @vuepress/client:  2.0.0-beta.53
    @vuepress/core:  2.0.0-beta.53
    @vuepress/markdown:  1.9.7 (2.0.0-beta.53)
    @vuepress/plugin-active-header-links: ^2.0.0-beta.53 => 2.0.0-beta.53
    @vuepress/plugin-back-to-top:  2.0.0-beta.53
    @vuepress/plugin-container:  2.0.0-beta.53
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon:  2.0.0-beta.53
    @vuepress/plugin-git:  2.0.0-beta.53
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.53
    @vuepress/plugin-nprogress:  2.0.0-beta.53
    @vuepress/plugin-palette:  2.0.0-beta.53
    @vuepress/plugin-prismjs: ^2.0.0-beta.53 => 2.0.0-beta.53
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: ^2.0.0-beta.53 => 2.0.0-beta.53
    @vuepress/plugin-search: ^2.0.0-beta.53 => 2.0.0-beta.53
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.53
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.53
    @vuepress/theme-default:  2.0.0-beta.53
    @vuepress/utils:  2.0.0-beta.53
    vue: ^3.2.25 => 3.2.45
    vue-loader: Not Found
    vue-router:  4.1.6
    vuepress: ^2.0.0-beta.53 => 2.0.0-beta.53
    vuepress-vite:  2.0.0-beta.53
    vuepress-webpack: Not Found

If you do think fist file should preserve those values, post your question in the package repo


Add a wiki: NintendoWiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://nintendo.fandom.com/wiki/Nintendo_Wiki
Link to destination (independent) wiki: https://niwanetwork.org/wiki/Main_Page

There's a huge content gap here (34k vs 2k articles).


The field contains single quotation marks. It is written by proxy and will report an error.

Bug Report
Test  Topology
(1) python driver ------> proxy ------> mysql
(2) python driver ------> mysql
row info:
rows =
((datetime.datetime(2019, 3, 11, 14, 6, 11), datetime.datetime(2019, 3, 11, 14, 6, 11), 1, u"abc'"),)
insert statement
sql = """
insert into tbl_key_test (data_create_time,data_update_time,id,key_name_partial) values
(%s, %s, %s, %s )
"""
Test1 python driver ------> proxy ------> mysql
connect to  proxy
conn_d = get_mysql_connection('10.10.5.xxx:3306', 'test')
cur_d = conn_d.cursor()
cur_d.executemany(sql , rows)
error info:
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/site-packages/pymysql/cursors.py", line 169, in executemany
self.rowcount = sum(self.execute(query, arg) for arg in args)
File "/usr/local/lib/python2.7/site-packages/pymysql/cursors.py", line 169, in
self.rowcount = sum(self.execute(query, arg) for arg in args)
File "/usr/local/lib/python2.7/site-packages/pymysql/cursors.py", line 146, in execute
result = self._query(query)
File "/usr/local/lib/python2.7/site-packages/pymysql/cursors.py", line 296, in _query
conn.query(q)
File "/usr/local/lib/python2.7/site-packages/pymysql/connections.py", line 781, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File "/usr/local/lib/python2.7/site-packages/pymysql/connections.py", line 942, in _read_query_result
result.read()
File "/usr/local/lib/python2.7/site-packages/pymysql/connections.py", line 1138, in read
first_packet = self.connection._read_packet()
File "/usr/local/lib/python2.7/site-packages/pymysql/connections.py", line 906, in _read_packet
packet.check_error()
File "/usr/local/lib/python2.7/site-packages/pymysql/connections.py", line 367, in check_error
err.raise_mysql_exception(self._data)
File "/usr/local/lib/python2.7/site-packages/pymysql/err.py", line 120, in raise_mysql_exception
_check_mysql_exception(errinfo)
File "/usr/local/lib/python2.7/site-packages/pymysql/err.py", line 115, in _check_mysql_exception
raise InternalError(errno, errorvalue)
pymysql.err.InternalError: (3054, u"Unknown exception: Illegal input, unterminated '''.")
Test2 python driver ------> mysql
connect to mysql
conn_d = get_mysql_connection('10.10.4.xxx:3307', 'test')
cur_d = conn_d.cursor()
cur_d.executemany(sql , rows)
conn_d.commit()
insert sucessfully

@bruceyan1220 , thanks for your report. This issue will be fixed in 4.0.0.

@tuohai666  Has this issue been fixed in RC?

@bruceyan1220 , yes.
Has been fixed via https://github.com/apache/incubator-shardingsphere/issues/1674.


Fix typo when consuming context

Fixes missing . when consuming ctx_assigns.
Great work on the library so far, really enjoying the developer ergonomics this offers.

@bwittenbrook3 thanks for the PR! We missed a test for that scenario. I took a look at test/context_through_slot_test.exs and we don't have a test for context working with named slots, only default. In case you can write one, I'd appreciate 🙂
Otherwise, I'll add it sometime next week.
Cheers.


Abitclose/fix 0419

1、Sometimes the server cannot correctly obtain the http header of x_ollama_host, so server\middleware\ollama.ts is modified to make ollama interface configuration compatible and optimized.
2、Modified the .env.example file and added an optional environment variable OLLAMA_HOST

@abitclose Thanks for looking into it.
May I query in what cases, the server can't obtain the http header? It's better to understand the situation and try to make it reproducible?


Add a plugin to warn if the source type is ambiguous

What kind of change does this PR introduce?
feature
Did you add tests for your changes?
yes
If relevant, link to documentation update:
n/a
Summary
In order to stay future-proof, webpack must migrate away of javascript/auto type. This PR adds a new plugin that emit a warning if the source type is ambiguous: it uses Harmony modules and CommonJS or AMD global bindings.
Does this PR introduce a breaking change?
no

What kind of change does this PR introduce?
feature
Did you add tests for your changes?
yes
If relevant, link to documentation update:
n/a
Summary
In order to stay future-proof, webpack must migrate away of javascript/auto type. This PR adds a new plugin that emit a warning if the source type is ambiguous: it uses Harmony modules and CommonJS or AMD global bindings.
Does this PR introduce a breaking change?
no

I have signed the CLA. Feel free to take over this PR (or any of my past contributions)!


Add "py_modules" to setup.py, to fix incompatibility with Setuptools in Version 61 and 62

This fixes an incompatibility with Setuptools in Version 61 and 62, see the Issue:
https://github.com/vmware/vsphere-automation-sdk-python/issues/303
For more Information on the py_modules option, check out:
https://docs.python.org/3/distutils/setupscript.html#listing-individual-modules
Thank you all for the great work on the vsphere python sdk!

I am sorry, But it appears I am unable to please the @vmwclabot, I used git commit -s as described in the linked Document, and the Information is matching up with my GitHub configuration, anyone, any Idea, what I might be doing wrong ^^?

Can someone on the vmware team please help out here? The pip SDK install has been broken for almost a month.

Hi @bradhvr ,
Can you please check again, the issue has already been fixed in the latest commits.

Hi @vmehtavmware thank you, are there plans to put out a new release with these changes? We lock our requirements.txt to a specific tag to ensure stability.

Hi @vmehtavmware thank you, are there plans to put out a new release with these changes? We lock our requirements.txt to a specific tag to ensure stability.

Hi @bradhvr ,
Yes, we will put out a new release for these changes after adding few new samples. We will release mostly today or max by tomorrow.

@vanditsmehta would it be possible for you to create a bug fix release of 7.x with these fixes? We have customers that are still running VSphere 6.x so we cannot upgrade to 8.x, yet we would like to not be blocked by this bug.

@sodul you can still take the latest release of the SDK, it is compatible with vSphere 8.0, 7.x, 6.x. Of course, some of the APIs that are available in the latest SDK version will not be present on earlier versions of vSphere and you have to be mindful about it.

@mtsvetanov The SDK release notes state "Removed support for older versions of vCenter Server 6.5/6.7" if the latest version is actually compatible the notes are misleading.

vCenter Server 6.5/6.7 already reached End of General support last year, and are reaching End of Support Life later this year.
https://lifecycle.vmware.com/#/
https://www.vmware.com/support/lifecycle-policies.html
I agree that messaging on the SDK side is a bit aggressive. Technically there isn't anything that prevents using 8.0 SDK with vCenter 6.7 or 6.5.


Jwilson.0317.kt

This is 2 commits.
Commit 1 is the actual Kotlinization:
https://github.com/square/okhttp/pull/4741/commits/3a29e5525591c4162405c911a1a4d47c646501fa
Commit 2 just renames .kt files to .java files.


core: sort native methods in ASCII-compatible way

Port https://github.com/neo-project/neo/pull/2768.
This partially reverts commit ca127f161596c2d7b26f9fe20b526ae648333986.

It' OK, but will be merged only after the C# PR merge.


Will this integration continue?

Hi there,
Can anyone update this community on whether this integration will continue? There were some problems with Haier company and too many API requests earlier this year. Now we can see that new version has not been introduced since few months...
I fully understand that this is a voluntary and unpaid activity and I fully respect and am deeply grateful that someone took the time to create this integration, but I'd just like to know :)
Thank you

For me is simple, I did bite the bullet and bought a refrigerator ... but I'll not buy anything else from Haier, initially wanted to buy washer dryer etc ...
I sow this integration and say ok lets give it a try, but since is not ok, I'll go LG or Samsung way!

For the time being I am using https://github.com/gvigroux/hon. I only have 6 Haier AirConditioners, and it handles them quite well. It lacked some features present in Andre's integration, but now (in the recent update) some of them were added (silent mode, display off and something else), so hopefully it will be better and better. And what is most important - it is stable. I haven't had any issues with some unexpected changes causing the integration to stop, which unfortunately was the case for this integration. It's a pity that Andre stopped working on his version, I liked it and highly apprieciated the effort he needed to put to make it working, but it is also another pity that Andre is not telling his plans, so we don't know if to count this integration to evolve or we should just let it go.

Why would a lawyer be involved? Sorry, but did Andre break the law? Where? I assume you're joking. I don't see any reason why the HomeAssistant integration would be a violation.