how to configure two gpio pins as deep sleep  (IDFGH-2243)

how to configure two gpio pins as deep sleep .
I configured two pins as deep sleep   but deep sleep is  not enabling on two pins . only one pin is supporting .
how to configure deep sleep on two gpio pins?

https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/system/sleep_modes.html#_CPPv428esp_sleep_enable_ext1_wakeup8uint64_t28esp_sleep_ext1_wakeup_mode_t

I want to configure , Gpio 32 and Gpio 35 for deep sleep.
what is the mask value to be configure in ext1_wakeup function ?
i kept the value (1<<gpio_32)| (1<gpio 35 )in fiunction . but wake up is not setting .

Use 64-bit value 1ULL<<32

@manojsai17 as @negativekelvin says, the bit shift command needs to use 64bit values.  The compiler defaults to 32bit when it sees a constant without a type override. so this means (1 <<32) would set a 32bit int to 1 then shift it left 32 places, with would cause the 1 to shift past the 31st bit position. so the result would be 0.
uint64_t mask = ( 1ULL <<32 ) |  ( 1ULL << 35 );

Chuck.

@manojsai17 Has your issue been resolved? Thanks.

Thanks for reporting, feel free to reopen.


Onion tree m tree

mmmm onion tree 😋

mmmm onion tree 😋

You remind me that I can probably close this issue since VPTree are basically better than those anyway.

You remind me that I can probably close this issue since VPTree are basically better than those anyway.


Itamarreif/composer init

This PR implements the tasks in #120, #101 and #102.

A couple questions on managing memory in async rust & error handling:

in Searcher::run_subtasks(), I borrow fields from self and those are moved into the task that's spawned. this doesn't compile since the task with the borrowed values may outlive self. What is the proper way to launch this task?

how should i structure the error handling in async rust?
i'm generally a bit confused about how to structure my error handling strategy in a rust async program.
my general intuition is that errors that can't be handled internally by a task will be bubbled up to the searcher's run function, and if they cant be handled by searcher they should be bubbled up to main.
however i am unclear on how to return a SearcherError from Searcher::run_subtasks() to Searcher::run() from within a subtask that's spawned in run_subtasks()?

quick summary before handoff 7/10
tx collector
The collector (wrapper around ethers provider) is implemented in src/searcher/collector.rs. The constructor initializes from config info and run() subscribes to a stream of pending transactions from the node, converting each transaction that arrives to a NewTx Event (defined in searcher/mod.rs). These events are forwarded into the event channel.
bundler
The bundler currently takes a single NewTx event and turns the ethers::Transaction in it to a SendSequencerSecondaryTx action with an sequencer::Unsigned inside it. While I got a sanity check from Janis that the approach works, I haven't had the time to test this so there are likely small things to catch there.
executor
Executor is similarly implemented but not tested. The main thing remaining to implement here is handling transactions that fail because of a bad nonce. The approach i would take is resetting the bundler's nonce counter (there's an unused helper method for this that i added) and putting the unsigned transaction back into the channel for processing (will have to be signed again for new nonce).
remaining work

features
[ ] add events and actions endpoints to api, to inspect current pending events and actions (nice to have, shouldn't be too much work)
fixes

[ ] logic for handling invalid nonce on a sequencer. see the todo! in searcher::run().
[ ] change the healthz api endpoint to readyz

code cleanup

[ ] some of the errors can probably be cleaned up or improved
[ ] some function names can probably be renamed
[ ] move the event and action channel buffer sizes to config (currently just hard coded to 512)

sequencer & sequencer_client-related items

[ ] the constructor for sequence::action::Action in the sequencer crate needs to be made public (i made this change locally but didn't commit because wasn't sure if there was context to this I was missing)
[ ] sequencer transaction types (Unsigned, Signed, Action, etc.) should be reexported from the sequencer_client so that composer (and other users of the sequencer_client) do not need to depend on the sequencer crate.
[ ] SigningKey should be exported from sequencer_client instead of requiring and extra dependency on ed25519_consensus for using sequencer_client

tests

[ ] unit test for bundler's:

[ ] get_nonce()
[ ] NewTx handler (after moving out of )

[ ] unit test for executor's SendSequencerSecondaryTx handler
[ ] e2e tests for pulling a transaction from the geth node and submitting to the sequencer
[ ] set up k8s stuff in tests?

general housekeeping

[ ] get rid of cli args and replace with env variables
[ ] containerization and adding to ci


已经确定捐赠可以继续看到EX站的内容

对于想要下载自己收藏夹里萝莉正太本的人来说，打开  https://e-hentai.org/bitcoin.php  选择捐赠成为铜星无疑是个好方法，也就是最少20刀就能在E站看到Ex站的内容，可以在E站搜索到萝莉正太本。
当然E站也有可能会在2020年关闭，值不值就见仁见智了，作为老用户我觉得捐赠也是感谢大菠萝这么多年来的运营了

用ehv也可以看吗

用ehv也可以看吗

是的，在ehv选择e-hentai就行了，网页上能看之后客户端也能看

这种事不要到处宣传啊。。并且issue也不是用来宣传这些的吧。。

Site Retirement
A Message to the Community - E-Hentai Forums.png
For further official updates please check recent forum posts by Tenboro.
FAQ
Is the site shutting down?
This is no longer the case, at least for the foreseeable future.
Was anything deleted / lost?
No.
Can we upload / tag / comment on galleries?
Yes. All gallery activities are continuing as per usual.
Please do not intentionally mistag galleries, especially for tags involving controversial content. This will be met with a ban. If you are uncertain please post in the forums.
Should I send money?
Donations are appreciated but not necessary. This is not (and never was) a financial issue.


Optimize images

Moved transition.png to folder with others screenshots + optimized
Optimized all images in themes/vue/source/images. Total -147kb

@Alex-Sokolov Looks good! If you could resolve the conflict with a re-optimized transition.png, it'll be ready to accept.

Evan moved file before my pull-request :) conflict resolved


Support Heightmaps of Any Texel Density

Description
It would be great if there was an option to support heightmaps of arbitrary texel density. For example a 4k by 4k heightmap that represents a 1km by 1km landscape.
This would enable the creation of terrain in any scale. An example would be "It Takes Two", a game where the player is scaled down and the gameplay happens at a very small scale. A resolution of 1px per meter would not be enough here, but working in realworld model scale is still desirable.
In general this would be useful for very very large terrains and also for very small terrains.
I would be happy to try to implement this myself, if you could point me in the right direction. From reading the code, I think the first step wold be to implement a scaling factor where the world UV gets calculated in the main.glsl. https://github.com/TokisanGames/Terrain3D/blob/1cc15ac819bfde5c703e7ea173aeeac96fdab42c/src/shaders/main.glsl#L114
It might also be neccessary to adjust the density of the landscape mesh depending on heightmap resolution. This might be the much more difficult task.
Thank you for your work on these terrain tools!

Is there any reason this is not a duplicate of #131 or #77? Also see #198.

UV = v_vertex.xz;

This has to do with the scaling of the textures on the terrain and will do nothing to scale the mesh or heightmap. You can see it is reduced and used here:
https://github.com/TokisanGames/Terrain3D/blob/1cc15ac819bfde5c703e7ea173aeeac96fdab42c/src/shaders/main.glsl#L195

This might be the much more difficult task.

It is indeed not trivial.

I did not see #198 while searching because it was closed, sorry about that. That issue sounds like pretty much the same thing.
#131 talks about mesh density, not texel density. Mesh density can be independent of texel density, but I think the texel density could be added to the issue as the two are related.
#77 to my understanding talks about the size of the regions, not the texel density of the heightmap or the density of the mesh.
Sorry about the misunderstandings, this issue is hard to talk about because of wording (texel, texture, mesh, density, size, scale, etc).
I am unsure if thats viable, but making the default Godot Transformation controls work on the Terrain node would enable us to change these densities all together. In HTerrain, thats how I can achieve different densities.

Texels are pixels on a texture, as opposed to pixels on a screen. It doesn't have density by itself.
Density is a ratio, and in the case of the mesh, it is the vertices per unit distance.
The only things that exist in this context are the heightmap texture and the mesh.
You can already import a heightmap of any size up to 16k.
It's only the density ratio of 1 texture pixel to 1 mesh vertex that is fixed. #131 allows this to be adjustable, so this ticket is a duplicate as was #198.
@tcoxon has a pending branch to enable transformation controls.

Texel density refers to the number of texture pixels (texels) per unit of 3D surface area.
I am not requesting the uncoupling of the "ratio of 1 texture pixel to 1 mesh vertex". Instead, I am requesting the uncoupling of "1 texel to 1 meter(=unit)". I give up now, I am sure both issues will be fixed at the same time.


Add buildKitShort command, add shortName property to kits

This change addresses item #462
This changes visible behavior
The following changes are proposed:

add buildKitShort command
add shortName property to kits

Other Notes/Information
My first time with Typescript, please review carefully :)
Also I used TS 3.7 feature, don't know if it's possible.
I could not get tests running, I'm not sure why.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: janspisiak sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I suggest use buildKitName buildKitTarget buildKitMajorVersion buildKitFullVersion instead

Thanks for you wonderfull work

@janspisiak Hello, do you any objection about my idea?
If you don't have the time to update the pull-request, I'd like to update it:)

@lygstate sorry for the delay, and thanks for suggestions :)
However I am not qualified enough to know, if there are any drawbacks to supporting that many commands (performance or other). I am now using cmake-kits.json to define my own name (thus also changing the build directory), and I think adding shortName property to kits is great as it makes possible to customize build dir, without having to overwrite full kit name.
But what you suggest could be possible, and there is some documentation https://code.visualstudio.com/api/extension-guides/command
which to me seems it should be possible to refactor buildKit commands into common namespace eg. cmake.buildKit.{major, targetArch, targetOs}, or maybe parametrize buildKit? I don't know how would passing arguments from settings work however.
In summary, I would love to hear from the maintainers what do they think and if they would accept such big change :)

@janspisiak Gocha, so shortName can be customized in JSON file, and we can auto detect cmake.buildKit.{major, targetArch, targetOs}

At least, we need to make sure that the re-scan would not cause the shortName disappear, or it's would be no-lucky. And for shortName, can it be committed in workspace settings?, that's what I worried about shortName

I've create a updated version at https://github.com/microsoft/vscode-cmake-tools/pull/1337, that not using the shortName, but offer vendor hostOs targetOs targetArch versionMajor versionMinor separately,
so the user can choose what they want.

This can also be closed now


Storm-456 cannot navigate to topology page when name contains spaces

@Parth-Brahmbhatt
I had pull request open for this but I deleted it accidentally.
You were rite the decode only fixed the space issue but caused issues with percent sign.  After looking thru the code I found where the url is being encoded and changed it to use the ring encoder.  This fixed the issue for both percent and space.

@Parth-Brahmbhatt, @NareshKosgi , Does #360 sufficiently resolve STORM-456?  If so, we should close this pull request and resolve STORM-456.

Yes, I think its ok to close the jira. @NareshKosgi can you test and comment. The changes are merged into master so should be easy to test.

@Parth-Brahmbhatt I tried to build the lastest storm but i'm having the following issue:
[ERROR] Error resolving version for plugin 'org.apache.storm:storm-maven-plugins' from the repositories [local (/Users/nareshkosgi/.m2/repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository
I spent sometime trying to see if its something local to mine but haven't had success.  am I missing something new that was added to storm that I need in order to build the latest master?  I installed node which was the only new thing I saw.

We put in some changes so the storm build now uses a plugin that is also built as part of the build.  This makes it so you cannot run mvn compile on its own any more, you need to run at least mvn package because needs a jar on the classpath.  If you plan on building in just storm-core you need to have installed the plugin  into your local repo first.  We are working on a way to fix this, but don't have a perfect solution yet https://issues.apache.org/jira/browse/STORM-639.

@revans2 @Parth-Brahmbhatt I was able to build and run by using mvn install.  I checked with topo name with space and '%' sign.  They are working.  Do I just close the pull request and jira ticket in that case?

@NareshKosgi Thanks for testing the feature, yes you can just close it.


TextureButton Fix logic for drawing only the focused texture

If focused texture was the same as some other texture (pressed, hover, etc.) that should be drawn and the button wasn't focused then no texture would be drawn because of incorrect check silently assuming that focused is different than the other assigned textures. Should be fixed now.
Fixes #57388.
To clarify: the issue was that no texture was drawn at all; nothing was hidden and there was no issue with parent being top-level.

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.3.


Add Genie samples and improve heuristics

Description
Samples:

Genie/web.gs

Source: https://github.com/korylprince/WebKiosk/blob/22c6c656ba8080451167c4d52d950fc75b9844df/web.gs
License: Public Domain

Genie/IDataLoader.gs

Source: https://github.com/darkoverlordofdata/liboverlap2d/blob/53f66d46e3d992bdb303f356b919d3c1ef66d0ea/src/resources/IDataLoader.gs
License: Apache 2

Improve Gosu heuristic and add Genie heuristic for the common
[indent=\d+\] construct.

Checklist:

[x] I am fixing a misclassified language

[x] I have included a new sample for the misclassified language: (see above)
[x] I have included a change to the heuristics to distinguish my language from others using the same extension.

Cross-validation results change:
< samples/Genie/Class.gs BAD(Gosu)
> samples/Genie/Class.gs GOOD
> samples/Genie/IDataLoader.gs GOOD
> samples/Genie/web.gs BAD(JavaScript)


What about type Command?

How to use /command type of text from telegram? Like /start or /help

Commands are basically text messages that start with / character. There is no additional type defined for them. Could be potentially added in future though as it has been suggested by other people too.

Commands are basically text messages that start with / character. There is no additional type defined for them. Could be potentially added in future though as it has been suggested by other people too.

Oh my... I'd never even bother you if only startswith() would come to my mind earlier :D.
Thanks for your code, I'm going to use it as a starting point to backend telegram crypto currency tip bot :)
Take care!


Add Auto welcome email

It looks like we can send a custom email but we need to set up email provider first on Auth0

@braddf

you ever set up any of these before?

@peterdudfield yep I have used Sendgrid, Mailgun and Mandrill before – much over muchness I think they were all fairly easy to set up/integrate

Ill put the feedback in here

This is a little bit raw, so could be made a page
- Could also add an email address to contact OCF with in this message. quartz.support@openclimatefix.org


Ordered Message Document Picture Error ?

Order Message

Maybe it should be here Log3<-Log2<-Log1 ,right?

Hi @BlackChen277  official website has submitted pr to fix it. apache/rocketmq-site#399. @RongtongJin  can you merge this pr

Hi @BlackChen277 official website has submitted pr to fix it. apache/rocketmq-site#399. @RongtongJin can you merge this pr

Done


Unable to delete binding when instance name isn't unique

Issue Template
Step 1: Is this issue for here?
The issue is indeed for the cli.
Step 2: Describe the problem (very short text description):
Trying to delete binding fails if it belongs to an instance with a non-unique name (i.e. there are additional instances with the same name)
Step 3: Describe the problem (steps):
Steps to reproduce:

Create an instance with name 'abc' and binding
Create a second instance with the same name
Use the cli 'unbind' to delete the first binding

Observed Results:
Error message that the deletion failed since the instance name isn't unique:
Error: more than one service instance with name logging-bnr-standard found. Use --id flag to specify id of the binding to be deleted
Expected Results:
Being able to delete the binding
Relevant Code Snippet:
For unbind I can't supply an id for the instance. Only the name is used. I believe the problem is in https://github.com/Peripli/service-manager-cli/blob/master/internal/cmd/binding/unbind.go#L90

Closing.
It turns out that I can unbind with the binding id: smctl unbind --id='...'.
The difficulty was that the binding id isn't listed in the cockpit.
However, it can be found using list-bindings.


pytest fixture setup reported as additional test

The fixture setup is reported as a separate (additional) test.
When the base test is expanded in the build log, the fixture setup line also appears, indented under the base test, but expanding does nothing except display "Loading..." indefinitely.
The fixture setup should NOT be registered as a separate test.
The fixture setup should be expandable under the base test.
Thanks for taking a look,
-Shawn
platform win32 -- Python 2.7.3, pytest-2.8.5, py-1.4.31, pluggy-0.3.1
TeamCity 9.1.5 (build 37377), teamcity-messages 1.17
build log collapsed:
[13:03:23][Step 1/13] Test_pytest.TestClass.test_brie
[13:03:23][Step 1/13]
[13:03:23][Step 1/13] Test_pytest.TestClass.test_brie_setup
[13:03:23][Step 1/13]
[13:03:23][Step 1/13]
[13:03:23][Step 1/13] .

build log expanded:
[13:03:23][Step 1/13] Test_pytest.TestClass.test_brie
[13:03:23]   [Test_pytest.TestClass.test_brie]
[13:03:23]   [Test_pytest.TestClass.test_brie] Test_pytest.TestClass.test_brie_setup
 Loading...
[13:03:23]   [Test_pytest.TestClass.test_brie]
[13:03:23]   [Test_pytest.TestClass.test_brie]
[13:03:23]   [Test_pytest.TestClass.test_brie] .
[13:03:23]
			 [Test_pytest.TestClass.test_brie] [Test Output]
			 in test_brie()
[13:03:23]   [Test_pytest.TestClass.test_brie]
[13:03:23][Step 1/13]
[13:03:23][Step 1/13] Test_pytest.TestClass.test_brie_setup
[13:03:23]   [Test_pytest.TestClass.test_brie_setup]
[13:03:23]
			 [Test_pytest.TestClass.test_brie_setup] [Test Output]

			 [setup] cheese_db, connect to db
[13:03:23]   [Test_pytest.TestClass.test_brie_setup]
[13:03:23][Step 1/13]
[13:03:23][Step 1/13]
[13:03:23][Step 1/13] .

test code
class TestClass:
	@pytest.fixture()
	def cheese_db(self, request):
		print('\n[setup] cheese_db, connect to db')
		# code to connect to your db
		a_dictionary_for_now = {'Brie': 'No.', 'Camenbert': 'We do!'}

		def fin():
			print('\n[teardown] cheese_db finalizer, disconnect from db')
			request.addfinalizer(fin)

		return a_dictionary_for_now

	def test_brie(self, cheese_db):
		print('in test_brie()')
		assert cheese_db['Brie'] == 'No.'

Note: When "[Test_pytest.TestClass.test_brie] Test_pytest.TestClass.test_brie_setup" finishes loading, it it is a child (indented) of the base test [Test_pytest.TestClass.test_brie] and contains the expected output from the setup function.
When the duplicate test [Test_pytest.TestClass.test_brie_setup] is clicked, it contains no data, but toggles the child of the base test in the log above ([Test_pytest.TestClass.test_brie] Test_pytest.TestClass.test_brie_setup)

I still need to report setup fixture output somewhere.
I'll try to use message blocks https://confluence.jetbrains.com/display/TCD9/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-BlocksofServiceMessages
That way test output will be in the build log, expandable/collapsible, but not in the tests list.
Failed setup fixtures will be still reported as failed tests

@shalupov,
Thanks for your work on this!
Message blocks is a great idea.
Is it possible for a failed setup fixture to force all dependent tests to report as failed, but not create a separate (additional) test for the fixture itself?
If the fixture reports as a separate test, then the test count changes, which is misleading.

force all dependent tests to report as failed
We're reporting what pytest is reporting to test listener, so it's somewhat limited

I see now- as expected, pytest is identifying and reporting only the defined tests (not setup).
If I have two tests that depend on fixture setup, then pytest reports two tests.
When there is an error in fixture setup, pytest reports 2 tests failed:
python -m py.test -r a Test_pytest.py
...
=========================== short test summary info ===========================
ERROR Test_pytest.py::TestClass::()::test_brie[cheese_db]
ERROR Test_pytest.py::TestClass::()::test_cheddar[cheese_db]
================= 2 error in 1.79 seconds ==================

But, TeamCity captures the following tests:

3 tests when fixture setup is successful

TestClass.test_brie[cheese_db]
TestClass.test_brie[cheese_db]_setup
TestClass.test_cheddar[cheese_db]

4 tests when there is an error in fixture setup

TestClass.test_brie[cheese_db]
TestClass.test_brie[cheese_db]_setup
TestClass.test_cheddar[cheese_db]
TestClass.test_cheddar[cheese_db]_setup

This request is to make TeamCity report the same number of tests that pytest reports.
I like the idea of capturing fixture setup output as a sub-block in the build log under each dependent test without reporting "*_setup" as distinct test(s).

Any progress on this?

Sorry, not yet. I thin I'll return to the project in a couple of weeks

Finally fixed

Sweet, awesome news! Good work. Any idea when a new version will be released so we can take advantage of this change?

released 1.18


Update Dockerfile

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

raghav

raghav tandon


Unable to create new VM's. UTM not able to save in sandboxed file path.

For some reason I am no longer able to create new VM's. After you finish the creation wizard the new VM shows up in the left panel but gives QEMU error on launch. I am unable to move/clone/delete the VM.
It seems it is not able to save the files in the container. Deleting and reinstalling UTM does not fix this issue. I also notice I am unable to "open in UTM" from the UTM gallery web page. It downloads the file but once it is complete it says it can not be found. It seems like UTM is not able to write to the container sandbox.
This started happening after I moved 2 VMs to a new location outside the sandbox. I moved them to ~/user/Documents/UTM. Maybe this broke something I am not sure. If after VM creation I try and "show in finder" nothing happens.
UTM: 4.2.5
OS: 13.3.1
M1 Max

Ok I figured this out. In a previous version of UTM I was using hdutil to mount a sparseimage to the "Documents" folder in the sandboxed container. After I updated UTM to a version that allowed the moving of VM's I no longer needed that.
To keep it short UTM will not allow you to create a new VM if "~/Library/Containers/com.utmapp.UTM/Data/Document" does not exist. You may want to add error handling to let the user know why.

You may want to add error handling to let the user know why.

It’s tough because we can’t possibly anticipate what people may do to mess with the container outside. For example, if you mess with certain files inside the container, you can cause UTM to crash. We rely on Apple’s standard functionalities to do things and we cannot add error checks every time we call some API to, say, make a new file in the sandbox for every possible way it could have gone wrong.

I agree with you in principle. I just thought having it check that its actually writing the file to disk would make sense. Right now as it stands it does not verify that anything was actually written to the drive. You can create a new VM and everything looks like normal except you can not run the VM or interact with it in any way. Only once you restart UTM does it showed as greyed out saying it does not exist. Nothing in the logs would alert you to the cause.
Again I agree with your statement I just figured it would be simple enough to have UTM verify it actually wrote to disk when you hit save would make sense. Even though this was obvious user error it is one that parsing logs would not show. I did not see anything in the logs stating it could not write to the non-existent folder.
Thanks again for all your hard work.

I see


C-Chain trannsaction traces

Pull Request Test Coverage Report for Build 602635559

43 of 170 (25.29%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 26.849%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/idbmodel.go
43
47
91.49%

services/idbmodel_mock.go
0
16
0.0%

services/indexes/cvm/writer.go
0
33
0.0%

services/indexes/avax/reader.go
0
74
0.0%

Totals

Change from base Build 599583977:
-0.04%

Covered Lines:
1692

Relevant Lines:
6302

💛  - Coveralls


Update quickstart-sdk.md (Typo "Azure Open AI"→"Azure OpenAI")

https://learn.microsoft.com/en-us/azure/ai-services/qnamaker/quickstarts/quickstart-sdk?pivots=rest
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/ai-services/qnamaker/Quickstarts/quickstart-sdk.md
#PingMSFTDocs

@jboback
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Embed functionality breaks when using Vite import()

Describe the bug
sveltekit-embed doesn't embed content when it's rendered as a dynamic markdown import.
To Reproduce
Steps to reproduce the behavior:

Go to Test Page
No YouTube content loads under "Test Page: YouTube Embed"

Expected behavior
YouTube content should load normally.
Additional context
GitHub Repo: https://github.com/acidtone/sveltekit-embed-test/
The above repo is a reproduction of the problem I'm experiencing on a larger markdown website. Content is loaded dynamically using Vite's import() function in /routes/+page.server.js.
The package works great with normal .svelte and .md content but breaks when I import at compile time. This makes sense to me but is there any way around this?

Hey @acidtone thanks for stopping by!
So, I'm not sure if this is an MDSveX limitation here or not, short answer is I have no idea! 😅
Sorry,
I think this may be similar situation to what @swyxio was trying to do with https://github.com/swyxio/swyxkit/issues/149
Is there nothing in the terminal to hint at an issue when building or running in dev?

Is there nothing in the terminal to hint at an issue when building or running in dev?

No errors in either the browser or in the terminal. And there's no indication that the page is trying to fetch the YouTube link in the Network tab.
I don't know enough about the lifecycle of Vite/SK/Mdsvex to really know what's going on. I guess the backend compilation isn't triggering the embed by the time it renders in the DOM?


Add support for EIP-1613 Relays for 'claim' meta-transactions

With the current implementation, the user who receives a transfer of funds via a URL link has to make a claim on a blockchain.
In case the user does not have a sufficient amount of native token to perform such a transaction, he can make an HTTP request to the xDai relay server to have that claim made for him.
This creates a centralized single point of failure for Burner Wallet, as the address of such relay is hardcoded and it has no way to look up alternative trusted relays.
EIP 1613 targets this specific use case and solves it in a compatible, yet decentralized way. Its benefits can be achieved by implementing RelayRecipient interface in Links contract and using 'tabookey-gasless' library to perform a 'claim' transaction.
I've made a pull request here https://github.com/austintgriffith/burner-wallet/pull/86
It contains a minimal implementation that allows a gasless wallet to make a claim from the Links contract using the RelayHub & relay client.
The easiest way to run the relay is in our Docker container:
docker run -p 8090:8090 tabookey/gsn-dev-server:v0.3
Please hit me or Yoav (@yoav-tabookey) up at any time if you have any questions.

PR #86 was merged. Can someone familiar with the situation comment on whether this issue can hence be closed. Thanks!

Right, the Burner Wallet has been running with Gas Station Network for some time now. Closing the issue.


Adding Services in the Graph

Hello,
For rqt_graph, can an enhancement be made so that services are visualized, in addition to topics?
Thanks,
Nathan

While this is a great feature idea it is not something the maintainers will have time to implement. Please consider contributing a pull request for this enhancement.

Sounds good. Could you give me some guidance in how to technically do that, in this package?

Thanks. Sometime in the next month, I'll let you know if I think I can create a PR, cause this looks complicated.

Actually I don't even think the necessary information is available through any API. Therefore I don't think this feature is implementable.
Therefore I will close this ticket for now. Please feel free to comment on it anyway.

O that's too bad; let me know if something changes.


[Bug] Infinity loop in Consume() method

Versions

Sarama
Kafka
Go

v1.34.1
-
1.18

Configuration
What configuration values are you using for Sarama and Kafka?
        // default reader configuration
        readerOptions := make([]kafka.ReaderOption, 0)
        readerOptions = append(readerOptions, kafka.WithReaderTlSConfig(nil))
	readerOptions = append(readerOptions, kafka.WithReaderSaslConfig(user, password, kafka.SaslAlgorithm("SHA512")))

	reader, err := kafka.NewReader(brokers, consumerGroup, readerOptions...)

Logs
logs: CLICK ME

[Sarama] 2023/01/25 15:27:40 client/coordinator retrying after 250ms... (3 attempts remaining)
[Sarama] 2023/01/25 15:27:40 client/coordinator requesting coordinator for consumergroup kafka-demo from <ip>
[Sarama] 2023/01/25 15:27:40 client was not authorized to access group kafka-demo while attempting to find coordinator
[Sarama] 2023/01/25 15:27:40 client/coordinator retrying after 250ms... (2 attempts remaining)
[Sarama] 2023/01/25 15:27:40 client/coordinator requesting coordinator for consumergroup kafka-demo from <ip>
[Sarama] 2023/01/25 15:27:41 client was not authorized to access group kafka-demo while attempting to find coordinator
[Sarama] 2023/01/25 15:27:41 client/coordinator retrying after 250ms... (1 attempts remaining)
[Sarama] 2023/01/25 15:27:41 client/coordinator requesting coordinator for consumergroup kafka-demo from <ip>
[Sarama] 2023/01/25 15:27:41 client was not authorized to access group kafka-demo while attempting to find coordinator
[Sarama] 2023/01/25 15:27:43 client/coordinator requesting coordinator for consumergroup kafka-demo from <ip>
[Sarama] 2023/01/25 15:27:43 client was not authorized to access group kafka-demo while attempting to find coordinator
[Sarama] 2023/01/25 15:27:43 client/coordinator retrying after 250ms... (3 attempts remaining)

...infinity loop...

Problem Description
If the client is not authorized to access the consumer group, the Consume() method is expected to return an error, but this does not happen. Instead, the Consume() method freezes.
Suggested error location: from the analysis of the sarama code, it can be seen that the code execution is endlessly looping on the func (c *consumer Group) retryNewSession() method (file consumer_group.go). Inside this method, a recursive construction is performed, which in this case leads to an infinite attempt to update the session in 3 attempts (default value: 3). After three attempts, an error is expected to return, but instead, the retryNewSession() method is recursively called again, which again fails with an error.

@vitalygudza thanks for reporting this, good catch — have pushed up a PR that should hopefully resolve this for you

Thank you very much! Now it works!


Swig fails when the SWIGOUTDIR doesn't exist.

This issue was originally created at: 2009-02-25 04:46:22.
This issue was reported by: teajay.
teajay said at 2009-02-25 04:46:22

When using SWIG we like to specify a SWIGOUTDIR in order for the generated code to fall into a seperate directory. This works great as long as the output directory already exists. If the directy happens to be missing the call to swig fails as it can't write it's output files.
I worked around the problem in my SConstruct files but it would definitly be nicer if Swig builder created the SWIGOUTDIR if it doesn't exist.
Thanks for the great work.
Thomas Bernard.

gregnoel said at 2009-03-05 15:22:44

Bug party triage.  Greg to find out who previous SWIG expert was and report back.

gregnoel said at 2009-03-13 13:27:35

Ben, we believe that SWIGOUTDIR should cause the directory to be created.  Can you look into this and let us know what's wrong?  Add a comment to the issue and change the milestone back to -unspecified- so we'll pick it up for retriage.  Tks

benmwebb said at 2009-03-14 09:00:34

Sure, I'll take a look. What I can say for sure is that SWIG's -outdir option does not create the directory, so scons will have to do it. I'll make up some test cases to see what's going on here.

benmwebb said at 2009-03-15 11:54:05

Created an attachment (id=594)
scons-python-outdir.patch

benmwebb said at 2009-03-15 11:57:30

Thomas, are you using SWIG to generate Python wrappers? Looking at the SWIG tool, it looks like SWIGOUTDIR should work correctly if you are generating Java wrappers - there's even a test for this in the test suite. But SWIGOUTDIR appears to be ignored when generating Python wrappers.
The attached patch (to scons SVN trunk, r4074) adds support for SWIGOUTDIR with Python wrappers, and adds a test case for this. Please let me know if this fixes the issue for you (if not, please provide a minimal test case to demonstrate your problem).

teajay said at 2009-03-15 23:18:25

Acutally i'm using swig to generate com and C# wrappers for now. I also intend to generate lua wrappers but I know they don't produce any script side files so it shouldn't be a problem.
I'll have a look at the patch you made and i'll provide a test case for the issue i'm facing. If I get that far, I might as well try to provide a patch.

benmwebb said at 2009-03-16 08:34:22

Well, there's your problem - the SWIG builder currently only knows about language-dependent files for Python and Java. It has no support for C# or any other language for that matter. So it'll work, but it won't track the dependencies of the language-dependent files at all, so won't rebuild them if you delete them, won't clean them with -c, and (when using SWIGOUTDIR) won't create the directory they're supposed to end up in.
It wouldn't be that hard to teach the builder about language dependent files for other languages (although it would be tedious to add support for every language). But it would add a lot of dependencies to the build system if the current tests for Python and Java, which build all the way from .i to .so, were extended to test every SWIG-supported language (since you'd need to install the C API headers and libraries for each language to compile and link the wrappers). As a compromise the tests could just go from .i to *_wrap.c for now.

teajay said at 2009-03-16 08:40:19

I tried earlier today to get the tests concerning swig running on my machine so I could try and have a go at the patch you provided. The problem was I didn't get the tests to work in the first place ... I didn't have time to work any longer on the problem so I left that aside.
Anyway that would really be great to get support for all the generated interface types supported by swig ...
If I get those tests running I might have a go at it ( at least for C#, COM and
lua )

gregnoel said at 2009-03-16 16:31:43

Setting this back to -unspecified- so it will be retriaged.

gregnoel said at 2009-03-19 02:11:40

Bug party triage.  Ben, we are most impressed.  We only asked for an analysis of the problem, but you provide a patch with tests, plus determined that the OP is looking for something we don't currently support.
Would you be willing to be a developer?  Unless you volunteer for something, it basically means that we'd nag you with issues like this one from time to time.  (For example, if you want to volunteer to tackle adding support for the missing SWIG languages, you'd be a hero to us.)
If you do want to be a developer, let me know and I'll enable you so you can go ahead and apply this patch.  And also apply that documentation patch you posted for review a few days ago.

benmwebb said at 2009-03-21 19:33:20

Certainly, I would be happy to be a developer. I am unfortunately rather busy with other things right now, however, so can't promise to be able to do much more than fix the occasional SWIG problem here and there.
I don't think it would be hard to add support for at least the major languages currently supported by SWIG, so I'll take a look at that in the near future. (Some other languages such as R might be hard to test, because I think that would require a very recent version of SWIG.)

garyo said at 2012-09-01 10:01:49

Bumping all old issues targeted for past releases to 2.x.

benmwebb attached scons-python-outdir.patch at 2009-03-15 11:54:05.

scons-python-outdir.patch

Just a note on history: the patch referenced here was applied in 2009. Knowing this, I'm removing the "Has Patch" label (which I added recently), because it doesn't have a pending patch.  I presume since the the original topic, which was about a different language, remains unresolved we should just leave the bug as it?

Looks like the issue description is inaccurate.
It should be SWIGOUTDIR not created if language output from swig isn't one of java, python, c  ?


Add validation between input_col and fn for Callable DataPipes

🚀 The feature
Using inspect to validate the input_col matching fn input for Mapper, Flatmapper and other DataPipe using both input_col and fn as the arguments.

Mapper
Filter
etc

Motivation, pitch
This would help users to identify the wrong arguments at the construction time for such IterDataPipe rather than at iteration time.
Alternatives
No response
Additional context
No response

I'd like to work on this if possible

Was this ever worked on?

Hi @davidegavio, do you still have plan to work on this issue?

I'll give this a try when I get home

@ejguan just to check, is this to check that fn has type annotations for returning a Sequence?

If the provided fn has type annotations, we should validate the number of function's arguments matches input_col.
Let's say there is only 1 argument in fn, but input_col is specified as 1. We should raise Error.

What does input_col refer to in this scenario? Is it the dimension?

Yeah. Let's say you have a DataPipe yielding tuples like (1, 2), (3, 4), ....
dp = IterableWrapper([(1, 2), (3, 4), ...])
dp = dp.map(lambda x: x + 1, input_col=1)

And, input_col would specify which element in each tuple should be applied by the fn. In this case, as input_col=1, the function will apply to 2, 4, ....
We should add inline doc to explain the behavior of input_col

Alright, I will work on this and open a PR.


Help

Hello,
Thx for your work, but i have a probleme with it. See my code :
<masonry column-width="200">
      <div class="masonry-brick" ng-repeat="news in newsList">
                 <news-item news="news" view-mode="viewMode"></news-item>
       </div>
</masonry>

But the width of columns is not correct in view :

Can you help me please ?

It didnt work for me neither. I just added css to '.masonry-brick'.
.masonry-brick{width:25%;}


Image in the "Content Enricher" Doc need to be updated

Description
The indicated places of the below image need to be updated according to the updated approach. In the updated approach, a local entry is created but it is not saved as a registry resource. Therefore, mentioning Governance Registry can be omitted. Also the term WSO2 ESB need to be updated.

Describe the problem(s)

A detailed description of the purpose of this improvement.

Describe your solution(s)

A detailed description of how this improvement will solve the problem described above.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Fixed via https://github.com/wso2/docs-mi/pull/806/files.


Add circular crafting rule to 3-microblock stairs

This allows chopping 3-microblock stairs back into microblocks like other shapes (stairs, slabs, panels) can be crafted back into microblocks.

Where did the half-stair "flipping" go?

New recipe is defined this way: 3 microblocks → half-stair → other half-stair → 3 microblocks

Okay, makes sense.


Change decode default 'ascii' codec to 'utf-8'

Change decode default 'ascii' codec to 'utf-8' for the benefit of other languages

ho yes, nice


Registration

The document says: "Currently, a device can only be registered in a single tenant. This limit means that only one work or school account in the Microsoft Authenticator app can be enabled for phone sign-in."
I think this must be intended to say: "Currently, a device can only be enabled for passwordless sign-in in a single tenant." The Authenticator app itself can be registered in multiple tenants.

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

ID: ee6ac70d-5853-6a3a-0964-23b46910b4c4
Version Independent ID: a5beda87-9845-8807-6221-7fdc64079587
Content: Passwordless sign-in with the Microsoft Authenticator app - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-authentication-passwordless-phone.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@Air-Git Thank you for your feedback . We will investigate and update the thread.

@Air-Git Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue. #please-close


Add Hypercorn as an alternative ASGI server

:memo: Add Hypercorn as an alternative ASGI server.

This should fix https://github.com/tiangolo/fastapi/issues/80


Add 'Tricks' section in the readme

Easy LoadProgressBar to fix #10

Thanks to @nikgt 's pr this will be no longer necessary.


AI 72and73 - Documentation

Documentation PR - Includes GODoc description comments for public functions and a README

PR looks good to me. Can you verify if the model path in the test files is correct for the 3 models you added?

PR looks good to me. Can you verify if the model path in the test files is correct for the 3 models you added?

Yep! When called using the syntax provided in the readme (ie go test -run ^TestString ./tests), it needs the relative path from the tests folder.


PROPOSAL: Chart spec: Template output for non-k8s endpoints

In order to make the chart format better able to handle future needs, we'd like to augment the chart spec to explicitly talk about the output of the engine.
As it works right now:

An engine takes a chart and (optionally) some values.
It's output is a map of string identifiers (usually treated like filenames) and values (a string or []byte)

The current assumption is that the values in that map are valid Kubernetes manifests (containing only resource definitions).
We'd like to add two things:

The value may begin with a header of the form #@ [....] \n (described below), which contains an annotation to tell the system what resource generator to delegate to.
By default, if no header exists, it will be assumed to be a Kubernetes manifest

The Resource Generator Header
A resource generator takes the output of a template run and generates resources. The default resource generator is Tiller's Kubernetes client, which sends resources to the Kubernetes API for provisioning. In the future, we can support other resource generators (e.g. GCP's resourcifier for Google APIs). The Resource Generator header is an annotation that tells the processing system (e.g. Tiller) which resource generator to use.
An example resource generator header may look like this:
#@resourcifier

Note that this sequence begins with #@ and ends with a newline. Any generated output that contains begins with the #@ sequence is considered to be a resource generator header. The a character sequence of UTF-8 [a-zA-Z0-9_-]+ indicates the name of the target resource generator. If that sequence is terminated by a space character, then any remaining data that is not \n is collected to pass into the generator as input.
#@resourcifier cluster=internal use-flavanoids=true

In the example above, the processing system (e.g. Tiller) would invoke a resource generator named resourcifier and pass it the string cluster=internal use-flavanoids=true as input.
Any processing system that can handle resource generator headers should act accordingly:

If the resource generator type (string) is recognized, it should strip the resource header line and  pass the resources to that generator and report any errors accordingly
If the resource generator type is unrecognized, it should respond with an error indicating the type is unknown
If no resource generator type is declared, it should pass the resources to the Kubernetes resource generator, and pass back any errors.

@vaikas-google How does that sound? Close to what we talked about?


Updating all Welsh translations receieved.

Updating Welsh translations for Registration journey.
Outstanding pages to translate (Content TBC before translations are received):

start-page.json
application-submitted.json

CI: No security warnings found


Mybatis issue while generating Model Java file

Actually i am not clear this issue is Java ,JSP or Mybatis .
Currently facing issue is as follows :
Front End
Java JSP Struts 2 Spring
Back End
PostgreSQL 9.3.XX
Issue
In PostgreSQL
birthday date;
In jsp Page code written
<sj:datepicker
    name="birthday"
    id="birthday"
></sj:datepicker>

In Java File using mybatis generator its generated following code
private Date birthday;
In Mybatis File
insert into "TABLE" (birthday) values (#{birthday, jdbcType=DATE});
When inserting value from jsp page [1988/01/13] then in java console getting [Sat Jun 11 00:00:00 JST 18] value.this is wrong.
If i change private Date birthday to private String birthday then console don't have any issue but inserting value in database generating error.
Error Code :42804
birthday is a date trying to insert character varying.

Tried different ways ,still did not found answer.
please tell me solution.
Or
please tell me while generating Model [XXX.java file]using mybatis generator at that type how can i change particular object  Date to String in java.
Thank you in advance.

As stated in the issue template, we don't accept questions on this tracker.
And it is a Struts 2 issue :wink:


Change diskann parameters (cached number nodes) to (search cache budget)

Signed-off-by: cqy123456<EMAIL_ADDRESS>issue: #253

/lgtm
/approve


Trouble with Query Params

I am having some issues implementing params to specify the content on my page.
Some background - I started defining my routes within a headless CMS (contentful). I use a script to build a JS file for inclusion with my server.js file. This allows my content authors to define new landing pages, change page names (seo) and other wonderful things. It also allows me to potentially make it so the page within next (ex /index.js) is just a template, and I should be able to pass different ids to my datasource.
In my server, I do something like this to define routes.
  for (const { route, locale, renderer, additions, referrer, id } of routes.routes) {
    server.get(route, (req, res) => {
      if (config.APP_ENV !== 'localhost') {
        renderAndCache(req, res, renderer, { id, locale, referrer, additions });
      } else {
        app.render(req, res, renderer, { id, locale, referrer, additions });
      }
    });
  }

We use a configuration option to prevent SSR-cache if we are developing.
Then on my page, I use
  static async getInitialProps({ query: { id } }) {
    const initProps = await new Promise((resolve) => {
      const cms = new Connector();
      const cmsRet = cms.retrieve(id);
      resolve(cmsRet);
    });
    return initProps || {};
  }

Connector() and cms.retrieve(id) is a wrapper to get data specified by the id. It then parses it and returns it for us to pass back as part of the initial props.
When loading into index.js, the page renders fine. Meaning that the ID works without any issues. When navigating to another page and them returning, I see -

This tells me that the browser history (back button) or client side routing (clicking on site logo from another page) is not preserving that ID. What is the realistic solution?
Keep in mind that every page of the site has it's own unique ID. So passing id as a query param using Router seems like a massive limitation.

How are you passing the id param if it's not by query param?
On the client side you can do something like this to implicitly pass the query param but keep pretty URLs:
<Link
  href={`/index?id=${pageId}`}
  as={`/${prettyName}`}
>
</Link>

What's the URL you are using when doing client side routing?

@quentin-sommer - i am trying to find a solution that does not meet the ID as query params. On client side this is a lot of link rewritting. Additionally, I do not want the link to have the query params in the route. That would be less than idea to show the long has value each time.

Your next application use the ID query param to render (because you give it here)
app.render(req, res, renderer, { id, locale, referrer, additions });
You can't distinguish between pages on the client without it

@quentin-sommer - i agree. I am just curious if there is a alternative.
The issue is that the CMS defines a link to home as /. So if I use the incoming href, and attach the ID that I need to it. Then use the as param to control the appearance and restore it to the originally linked URL?
<Link
  href={`/?id=${pageId}`}
  as={`/`}
>

This would work, it will direct you to pages/index.js with / as browser url and populate query string id in your code. It's actually the same principle used in this example:
<Link
 href="/route?item=subitem"
 as="/route/subitem"
>
nav : /route/subitem
code querystring : {item: "subitem"}

@quentin-sommer - ok this makes me feel better. Thank you!


vimPlugins.qmk-nvim: init at 2024-02-15

Description of changes
Add qmk.nvim.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

There was an attempt in #296208 but the diff is enormous. I would suggest to merge this PR instead.
cc @DanNixon


Implement Laplace Distribution

Wikipedia: https://en.wikipedia.org/wiki/Laplace_distribution
Java BLOG implementation: https://github.com/BayesianLogic/blog/blob/master/src/main/java/blog/distrib/Laplace.java

Done


feat: updated notification-list's gotoAction to use fetch when redirect is false

resolves #91

Hi @jonathanmtran, can we revisit this one?

Sure thing. I have rebased this branch against master for review and feedback.


New version: EAGO v0.2.0

Registering package: EAGO
Repository: https://github.com/PSORLab/EAGO.jl
Created by: @mewilhel
Version: v0.2.0
Commit: 8c8d7afab967e1e178163f39c896cc004dda067d
Reviewed by: @mewilhel
Reference: https://github.com/PSORLab/EAGO.jl/commit/8c8d7afab967e1e178163f39c896cc004dda067d#commitcomment-33943092

Please add
[compat]
julia = "1"

to your project file and retrigger the bot. Ideally also for the other deps.


[test] Small lit cleanups

This PR slightly refactors how we set DYLD_LIBRARY_PATH/LD_LIBRARY_PATH in the %target-run pattern, so that we only set a single variable that is correct for the target platform and has the appropriate prefix (SIMCTL_CHILD_, IOS_CHILD_, REMOTE_RUN_CHILD_ or nothing at all, depending on Various Things).
More importantly, this also improves what gets logged to build output, hopefully helping me to track down a potential configuration issue in some CI bots.

@swift-ci test

@swift-ci test


[Common component] Header

Create the header, including the main navigation and section for the logo

Resolve in #16


v1.6 backports 2019-08-16

#8925 -- Fix proxy port leak on endpoint delete (@joestringer)
#8918 -- operator: generate cmdref (@ianvernon)
#8929 -- endpoint: check if returned FinalizeFunc is nil before executing it (@ianvernon)
#8926 -- update cilium-docker-plugin, cilium-operator to golang 1.12.8 (@ianvernon)
#8928 -- daemon: Do not start L7 proxy support if --install-iptables-rules="false" (@jrajahalme)
#8875 -- Add NodePort BPF CI tests (@brb)

Once this PR is merged, you can update the PR labels via:
$ for pr in 8925 8918 8929 8926 8928 8875; do contrib/backporting/set-labels.py $pr done 1.6; done

This change is

Travis failed due to issues retrieving packages:
E: Package 'kernel-package' has no installation candidate
apt-get.diagnostics
429apt-get install failed
518The command "sudo -E apt-get -yq --no-install-suggests --no-install-recommends $(travis_apt_get_options) install kernel-package libc6-dev-i386" failed and exited with 100 during .

never-tell-me-the-odds

BPF NodePort tests (added in this backport) failed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14436/testReport/junit/Suite-k8s-1/10/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_vxlan/

test-me-please

Another failure: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14438/

test-me-please


L2 Announcements missing Role Permision

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I installed cilium in a new dev cluster using kubeadm.  I based it on the following doc the cluster creation, Cilium kube-proxy-free Doc. After that I changed from legacy to ebpf using the cilum cli.  Then I added the load balancer CR and the L2AnnouncementPolicy. Later I used this doc Cilium L2 Announcement doc with the L2 Pod to finish configuring it.
I checked cilium logs and Role was missing all these permision
- verbs:
  - get
  - create
  - update
  apiGroups:
  - coordination.k8s.io
  resources:
  - leases

Cilium Version
1.15.1
Kernel Version
Linux cnv-svmi-ctrlp01 5.15.0-97-generic #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: v1.28.7
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.7
Regression
No response
Sysdump
Uploading cilium-sysdump-20240307-210254.zip…
Relevant log output
error retrieving resource lock kube-system/cilium-l2announce-default-nginx: leases.coordination.k8s.io "cilium-l2announce-default-nginx" is forbidden: User "system:serviceaccount:kube-system:cilium" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"

Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @dalcorta, thanks for the report. Unfortunately the sysdump is truncated, can you re-upload that? Also, where does the "relevant log output" come from? Is that from cilium-agent, cilium-operator, another component?
Glancing at the way that the Helm charts check for the l2announcements.enabled setting, the relevant permissions should be granted if that option is specified. Can you share the exact commands you initially used to install and later used to upgrade Cilium? This will help others to reproduce the exact behaviour you found.

@joestringer  Hi the log is from cilium pod. I used clilium cli, not helm.  What I did first was create a cluster kube-proxy free using kubeadm as specified in the doc. I always used cilium cli to add new parameters ( cilium config set  ).

@dalcorta I see. Could you be more specific about the exact commands you used? On the page that you referenced, I can see multiple commands which all directly use Helm. If you are configuring the L2 announcements feature only with the cilium CLI then it will be important for anyone to understand/reproduce the issue if they can tell exactly how you are configuring the feature.

kubeadm init --skip-phases=addon/kube-proxy --pod-network-cidr=<IP_ADDRESS>/16 --upload-certs --control-plane-endpoint=:6443
Added 2 control plane nodes and 1 worker nodes
cilium install --version 1.15.1 --namespace kube-system --set kubeProxyReplacement=true
--set k8sServiceHost=
--set k8sServicePort=6443
cilium config set enable-bpf-masquerade true
cilium config set enable-l2-announcements true
cilium config set l2-pod-announcements-interface ens33

Client config ended up like this
agent-not-ready-taint-key: node.cilium.io/agent-not-ready
  arping-refresh-period: 30s
  auto-direct-node-routes: 'false'
  bpf-lb-acceleration: disabled
  bpf-lb-external-clusterip: 'false'
  bpf-lb-map-max: '65536'
  bpf-lb-sock: 'false'
  bpf-lb-sock-hostns-only: 'true'
  bpf-map-dynamic-size-ratio: '0.0025'
  bpf-policy-map-max: '16384'
  bpf-root: /sys/fs/bpf
  cgroup-root: /run/cilium/cgroupv2
  cilium-endpoint-gc-interval: 5m0s
  cluster-id: '0'
  cluster-name: default
  cluster-pool-ipv4-cidr: <IP_ADDRESS>/8
  cluster-pool-ipv4-mask-size: '24'
  cni-exclusive: 'true'
  cni-log-file: /var/run/cilium/cilium-cni.log
  custom-cni-conf: 'false'
  debug: 'false'
  debug-verbose: ''
  dnsproxy-enable-transparent-mode: 'true'
  egress-gateway-reconciliation-trigger-interval: 1s
  enable-auto-protect-node-port-range: 'true'
  enable-bgp-control-plane: 'false'
  enable-bpf-clock-probe: 'false'
  enable-bpf-masquerade: 'true'
  enable-endpoint-health-checking: 'true'
  enable-health-check-loadbalancer-ip: 'false'
  enable-health-check-nodeport: 'true'
  enable-health-checking: 'true'
  enable-hubble: 'true'
  enable-ipv4: 'true'
  enable-ipv4-big-tcp: 'false'
  enable-ipv4-masquerade: 'true'
  enable-ipv6: 'false'
  enable-ipv6-big-tcp: 'false'
  enable-ipv6-masquerade: 'true'
  enable-k8s-networkpolicy: 'true'
  enable-k8s-terminating-endpoint: 'true'
  enable-l2-announcements: 'true'
  enable-l2-neigh-discovery: 'true'
  enable-l2-pod-announcements: 'true'
  enable-l7-proxy: 'true'
  enable-local-redirect-policy: 'false'
  enable-masquerade-to-route-source: 'false'
  enable-metrics: 'true'
  enable-policy: default
  enable-remote-node-identity: 'true'
  enable-sctp: 'false'
  enable-svc-source-range-check: 'true'
  enable-vtep: 'false'
  enable-well-known-identities: 'false'
  enable-xt-socket-fallback: 'true'
  external-envoy-proxy: 'false'
  hubble-disable-tls: 'false'
  hubble-export-file-max-backups: '5'
  hubble-export-file-max-size-mb: '10'
  hubble-listen-address: ':4244'
  hubble-socket-path: /var/run/cilium/hubble.sock
  hubble-tls-cert-file: /var/lib/cilium/tls/hubble/server.crt
  hubble-tls-client-ca-files: /var/lib/cilium/tls/hubble/client-ca.crt
  hubble-tls-key-file: /var/lib/cilium/tls/hubble/server.key
  identity-allocation-mode: crd
  identity-gc-interval: 15m0s
  identity-heartbeat-timeout: 30m0s
  install-no-conntrack-iptables-rules: 'false'
  ipam: cluster-pool
  ipam-cilium-node-update-rate: 15s
  k8s-client-burst: '20'
  k8s-client-qps: '10'
  kube-proxy-replacement: strict
  kube-proxy-replacement-healthz-bind-address: ''
  l2-pod-announcements-interface: ens33
  max-connected-clusters: '255'
  mesh-auth-enabled: 'true'
  mesh-auth-gc-interval: 5m0s
  mesh-auth-queue-size: '1024'
  mesh-auth-rotated-identities-queue-size: '1024'
  monitor-aggregation: medium
  monitor-aggregation-flags: all
  monitor-aggregation-interval: 5s
  node-port-bind-protection: 'true'
  nodes-gc-interval: 5m0s
  operator-api-serve-addr: <IP_ADDRESS>:9234
  operator-prometheus-serve-addr: ':9963'
  policy-cidr-match-mode: ''
  preallocate-bpf-maps: 'false'
  procfs: /host/proc
  proxy-connect-timeout: '2'
  proxy-max-connection-duration-seconds: '0'
  proxy-max-requests-per-connection: '0'
  proxy-prometheus-port: '9964'
  remove-cilium-node-taints: 'true'
  routing-mode: tunnel
  service-no-backend-response: reject
  set-cilium-is-up-condition: 'true'
  set-cilium-node-taints: 'true'
  sidecar-istio-proxy-image: cilium/istio_proxy
  skip-cnp-status-startup-clean: 'false'
  synchronize-k8s-nodes: 'true'
  tofqdns-dns-reject-response-code: refused
  tofqdns-enable-dns-compression: 'true'
  tofqdns-endpoint-max-ip-per-hostname: '50'
  tofqdns-idle-connection-grace-period: 0s
  tofqdns-max-deferred-connection-deletes: '10000'
  tofqdns-proxy-response-max-delay: 100ms
  tunnel-protocol: vxlan
  unmanaged-pod-watcher-interval: '15'
  vtep-cidr: ''
  vtep-endpoint: ''
  vtep-mac: ''
  vtep-mask: ''
  write-cni-conf-when-ready: /host/etc/cni/net.d/05-cilium.conflist

OK thanks. There is currently no way to solve this problem with cilium config set, because this only modifies the ConfigMap and not the other resources. If you follow the guide directly, those instructions should work.
I've filed https://github.com/cilium/cilium-cli/issues/2389 to follow up on whether there is a way to support this sort of reconfiguration with cilium config set, but for now you'll need to use the Helm options. Any install you've created with a recent version of the cilium CLI should be managed by Helm under the hood, so I would expect it to be possible to apply the changes directly using Helm.


PyroCMS

PyroCMS - based on CodeIgniter https://www.pyrocms.com/

Unfortunately doesn't scale well at 1000px


Only second image in list is getting updated

Describe the bug
When using argocd image updater with two images, only the second is updated. The first image remains at the initially defined tag version.
It looks like it has something to do with this info message:
time="2024-01-31T20:09:50Z" level=info msg="Successfully updated image 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.8' to 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.9', but pending spec update (dry run=false)" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.8 registry="git.internalnet.com:4567"

To Reproduce
I've also tried several variations of this including:

Using aliases for pull-secret and strategy
Only using aliases for the strategy
Stripping aliases out entirely

Images in the registry:
sms: v1.0.1 through v1.0.2
email: v1.0.1 through v1.0.9
In this example, the version deployed with sms updates to the most recent image properly, but the email image remains at the originally deployed version (ie sms=1.0.2 and email=1.0.8). When I swap sms and email in the image-list, the results are reversed (sms=1.0.1 and email=1.0.9).
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: psa
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
  annotations:
    argocd-image-updater.argoproj.io/image-list: sms=git.internalnet.com:4567/software-engineers/psa/sms-consumer/stg:v1.0.x,email=git.internalnet.com:4567/software-engineers/psa/email-consumer/stg:v1.0.x
    argocd-image-updater.argoproj.io/pull-secret: pullsecret:argocd/git-software-engineers-registry-credentials
    argocd-image-updater.argoproj.io/email.update-strategy: semver
    argocd-image-updater.argoproj.io/sms.update-strategy: semver
spec:
  project: default

  source:
    repoURL: git@git.internalnet.com:netops/kubernetes/k8s-apps.git
    targetRevision: HEAD
    path: stg/psa
  destination:
    server: https://kubernetes.default.svc
    namespace: psa

  syncPolicy:
    syncOptions:
      - CreateNamespace=true

    automated:
      selfHeal: true
      prune: true

kind: Deployment
metadata:
  name: email-consumer
  namespace: psa
  labels:
    app: email-consumer
spec:
  replicas: 1
  selector:
    matchLabels:
      app: email-consumer
  template:
    metadata:
      labels:
        app: email-consumer
    spec:
      containers:
      - name: email-consumer
        image: git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.8
        envFrom:
        - configMapRef:
            name: email-consumer-env-cm
        resources:
          limits:
            memory: "512Mi"
            cpu: "200m"
      imagePullSecrets:
      - name: argocd-deploy-token

apiVersion: apps/v1
kind: Deployment
metadata:
  name: sms-consumer
  namespace: psa
  labels:
    app: sms-consumer
spec:
  replicas: 1
  selector:
    matchLabels:
      app: sms-consumer
  template:
    metadata:
      labels:
        app: sms-consumer
    spec:
      containers:
      - name: sms-consumer
        image: git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.1
        envFrom:
        - configMapRef:
            name: sms-consumer-env-cm
        resources:
          limits:
            memory: "512Mi"
            cpu: "200m"
      imagePullSecrets:
      - name: argocd-deploy-token

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ./email-consumer-deployment.yaml
- ./sms-consumer-deployment.yaml
namespace: psa

Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
I did manually alter the logs and annotations to remove a customer name from the path and to not expose the name of our internal registry server.
Version
Using v0.12.2
Logs
Please paste any relevant logs here
Original Configuration - email last
time="2024-01-31T20:03:48Z" level=debug msg="Considering this image for update" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.9 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:48Z" level=debug msg="Using version constraint 'v1.0.x' when looking for a new tag" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.9 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:49Z" level=debug msg="found 2 from 2 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.9"
time="2024-01-31T20:03:49Z" level=debug msg="Image 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.9' already on latest allowed version" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.9 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:49Z" level=debug msg="Considering this image for update" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.1 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:49Z" level=debug msg="Using version constraint 'v1.0.x' when looking for a new tag" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.1 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:49Z" level=debug msg="found 2 from 2 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.1"
time="2024-01-31T20:03:49Z" level=info msg="Setting new image to git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.2" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.1 registry="git.internalnet.com:4567"
time="2024-01-31T20:03:49Z" level=info msg="Successfully updated image 'git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.1' to 'git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.2', but pending spec update (dry run=false)" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.1 registry="git.internalnet.com:4567"

Swap to sms last
time="2024-01-31T20:09:50Z" level=debug msg="Considering this image for update" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.2 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=debug msg="Using version constraint 'v1.0.x' when looking for a new tag" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.2 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=debug msg="found 2 from 2 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.2"
time="2024-01-31T20:09:50Z" level=debug msg="Image 'git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.2' already on latest allowed version" alias=sms application=psa-upon image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.2 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=debug msg="Considering this image for update" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.8 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=debug msg="Using version constraint 'v1.0.x' when looking for a new tag" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.8 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=debug msg="found 2 from 2 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.8"
time="2024-01-31T20:09:50Z" level=info msg="Setting new image to git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.9" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.8 registry="git.internalnet.com:4567"
time="2024-01-31T20:09:50Z" level=info msg="Successfully updated image 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.8' to 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.9', but pending spec update (dry run=false)" alias=email application=psa-upon image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.8 registry="git.internalnet.com:4567"

Does anybody have a workaround for this?

I have some more details on this.
First, the Application resource is not getting updated.
Also, I turned on trace for the logs. Slightly modified to remove private information. In this log, I updated two images in the registry. This is the first run after doing that.
time="2024-02-08T21:29:49Z" level=debug msg="Processing application psa"
time="2024-02-08T21:29:49Z" level=debug msg="Considering this image for update" alias=sms application=psa image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.3 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=debug msg="Using version constraint '1.0.x' when looking for a new tag" alias=sms application=psa image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.3 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Found update strategy semver" image_alias=sms image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="No ignore-tags annotation found" image_alias=sms image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Using runtime platform constraint linux/amd64" image_alias=sms image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Fetching credentials for registry https://git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Performing HTTP GET https://git.internalnet.com:4567/v2/software-engineers/ameren/ameren-public-api/stg/tags/list"
time="2024-02-08T21:29:49Z" level=trace msg="Performing HTTP GET https://git.internalnet.com:4567/v2/software-engineers/psa/upon/sms-consumer/stg/tags/list"
time="2024-02-08T21:29:49Z" level=error msg="Could not get tags from registry: name unknown: repository name not known to registry" alias= application=ameren-public-api image_name=software-engineers/ameren/ameren-public-api/stg image_tag=latest registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="List of available tags found: [v1.0.3 v1.0.4 v1.0.1 v1.0.2]" alias=sms application=psa image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.3 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.1 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.2 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.3 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.4 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3"
time="2024-02-08T21:29:49Z" level=debug msg="found 4 from 4 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3"
time="2024-02-08T21:29:49Z" level=info msg="Setting new image to git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.4" alias=sms application=psa image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.3 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Setting Kustomize parameter git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.4" application=psa
time="2024-02-08T21:29:49Z" level=info msg="Successfully updated image 'git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.3' to 'git.internalnet.com:4567/software-engineers/psa/upon/sms-consumer/stg:v1.0.4', but pending spec update (dry run=false)" alias=sms application=psa image_name=software-engineers/psa/upon/sms-consumer/stg image_tag=v1.0.3 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=debug msg="Considering this image for update" alias=email application=psa image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.11 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=debug msg="Using version constraint '1.0.x' when looking for a new tag" alias=email application=psa image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.11 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Found update strategy semver" image_alias=email image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="No ignore-tags annotation found" image_alias=email image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Using runtime platform constraint linux/amd64" image_alias=email image_digest= image_name="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg" image_tag=1.0.x registry_url="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Fetching credentials for registry https://git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Performing HTTP GET https://git.internalnet.com:4567/v2/software-engineers/psa/upon/email-consumer/stg/tags/list"
time="2024-02-08T21:29:49Z" level=trace msg="List of available tags found: [v1.0.10 v1.0.11 v1.0.12 v1.0.8 v1.0.9]" alias=email application=psa image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.11 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.8 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.9 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.10 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.11 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=trace msg="Finding out whether to consider v1.0.12 for being updateable" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=debug msg="found 5 from 5 tags eligible for consideration" image="git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11"
time="2024-02-08T21:29:49Z" level=info msg="Setting new image to git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.12" alias=email application=psa image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.11 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=trace msg="Setting Kustomize parameter git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.12" application=psa
time="2024-02-08T21:29:49Z" level=info msg="Successfully updated image 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.11' to 'git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.12', but pending spec update (dry run=false)" alias=email application=psa image_name=software-engineers/psa/upon/email-consumer/stg image_tag=v1.0.11 registry="git.internalnet.com:4567"
time="2024-02-08T21:29:49Z" level=debug msg="Using commit message: "
time="2024-02-08T21:29:49Z" level=info msg="Committing 2 parameter update(s) for application psa" application=psa
time="2024-02-08T21:29:49Z" level=info msg="Successfully updated the live application spec" application=psa
time="2024-02-08T21:29:49Z" level=info msg="Processing results: applications=6 images_considered=7 images_skipped=0 images_updated=2 errors=0"

This is what the manifest looks like. Even though I updated both, only one is showing up:
project: default
source:
  repoURL: 'git@git.internalnet.com:netops/kubernetes/k8s-apps.git'
  path: stg/psa-upon
  targetRevision: HEAD
  kustomize:
    images:
      - >-
        git.internalnet.com:4567/software-engineers/psa/upon/email-consumer/stg:v1.0.12
destination:
  server: 'https://kubernetes.default.svc'
  namespace: psa
syncPolicy:
  automated:
    prune: true
    selfHeal: true
  syncOptions:
    - CreateNamespace=true

After messing with this for hours and hours, I was finally able to get something that worked.
I believe the trick was using kustomization name to reference a tag in Deployment (not the registry) and using newName in kustomization.yaml to replace the image name in the Deployment.
kustomization.yam
kind: Kustomization
resources:
- ./email-consumer-deployment.yaml
- ./sms-consumer-deployment.yaml
namespace: psa
images:
- name: email-consumer
  newName: git.internalnet.com:4567/software-engineers/psa/email-consumer/stg
  newTag: "v1.0.8"
- name: sms-consumer
  newName: git.internalnet.com:4567/software-engineers/psa/sms-consumer/stg
  newTag: "v1.0.3"

deployment1.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: sms-consumer
  namespace: psa
  labels:
    app: sms-consumer
spec:
  replicas: 1
  selector:
    matchLabels:
      app: sms-consumer
  template:
    metadata:
      labels:
        app: sms-consumer
    spec:
      containers:
      - name: sms-consumer
        image: sms-consumer
        envFrom:
        - configMapRef:
            name: sms-consumer-env-cm
        resources:
          limits:
            memory: "512Mi"
            cpu: "200m"
      imagePullSecrets:
      - name: argocd-deploy-token

deployment2.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: email-consumer
  namespace: psa
  labels:
    app: email-consumer
spec:
  replicas: 1
  selector:
    matchLabels:
      app: email-consumer
  template:
    metadata:
      labels:
        app: email-consumer
    spec:
      containers:
      - name: email-consumer
        image: email-consumer
        envFrom:
        - configMapRef:
            name: email-consumer-env-cm
        resources:
          limits:
            memory: "512Mi"
            cpu: "200m"
      imagePullSecrets:
      - name: argocd-deploy-token

argocd-application.yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: psa
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
  annotations:
    argocd-image-updater.argoproj.io/image-list: "sms-consumer=git.internalnet.com:4567/software-engineers/psa/sms-consumer/stg:1.0.x, email-consumer=git.internalnet.com:4567/software-engineers/psa/email-consumer/stg:1.0.x"

    # email-consumer
    argocd-image-updater.argoproj.io/email-consumer.kustomize.image-name: "email-consumer"
    argocd-image-updater.argoproj.io/email-consumer.allow-tags: "regexp:^v1\\.0\\..*$"
    argocd-image-updater.argoproj.io/email-consumer.pull-secret: pullsecret:argocd/git-software-engineers-registry-credentials
    argocd-image-updater.argoproj.io/email-consumer.update-strategy: semver

    # sms-consumer
    argocd-image-updater.argoproj.io/sms-consumer.kustomize.image-name: "sms-consumer"
    argocd-image-updater.argoproj.io/sms-consumer.allow-tags: "regexp:^v1\\.0\\..*$"
    argocd-image-updater.argoproj.io/sms-consumer.pull-secret: pullsecret:argocd/git-software-engineers-registry-credentials
    argocd-image-updater.argoproj.io/sms-consumer.update-strategy: semver

spec:
  project: default

  source:
    repoURL: git@git.internalnet.com:netops/kubernetes/k8s-apps.git
    targetRevision: HEAD
    path: stg/psa
    kustomize: {}
  destination:
    server: https://kubernetes.default.svc
    namespace: psa

  syncPolicy:
    syncOptions:
      - CreateNamespace=true
    automated:
      selfHeal: true
      prune: true

@joelgriffiths thanks for reporting the issue. There are some tests that are similar to your case, and both are passing now. From running these tests, I can see all images are successfully updated.
"Test kustomize w/ multiple images w/ different registry w/ different tags"
https://github.com/argoproj-labs/argocd-image-updater/blob/79de6d5df9c0ebee010a5410a32d3f69daea7b66/pkg/argocd/update_test.go#L36
"Test successful update two images"
https://github.com/argoproj-labs/argocd-image-updater/blob/79de6d5df9c0ebee010a5410a32d3f69daea7b66/pkg/argocd/update_test.go#L161


Update Docs to explain how to customize floating button

I'd like to understand how to:

Customize where the button is displayed upon first viewing (I don't like where it starts)
Customize the icon/image
Perhaps change it from floating to stationary
I use an onboarding repo called Instructions which can hook a label onto a UI element .. like
UIelement.helpLabel.text = "This is the exciting UIelement" ..  How can I do that with the floating button? I'm using Swift and know little about poking around in objc

Hi @bbookman - my sincere for the atrociously late response here, this one somehow flew under our radar.
The floating bug button API is rather limited; we don't have plans to expand the API at the moment, since the vast majority of users use the screenshot or shake APIs. We do recommend the screenshot API in general, as this tends to be the most intuitive to end-users. That said, we always welcome pull requests :)
If you're still looking to customize the floating bug button, I can recommend one of three approaches:
A) Fork this repo, and make the necessary changes to LIFEBugButtonWindow.m
B) Use method-swizzling to override methods related to presentation of LIFEBugButtonWindow
C) Disable the bug button entirely, and create your own bug button by copying code from LIFEBugButtonWindow
Please let me know if any of this is unclear. :)

Odd, in my memory you had already responded.  No problem.  Since obj-c is a no go for me, I just decided against the floating bug and went with the other options

Ah yes, it may have been via a support email ;) glad it worked out!


Propagate TLS security profile config to kube-controller-manager and kube-scheduler

In HyperShift, TLS security profiles are configurable for OCP control plane components via the kind: APIServer definition from the cluster configuration items in the HostedCluster.
Currently, the TLS security profile (CipherSuites and MinTLSVersion) gets honored for the below components:

kube-apiserver
oauth-openshift
openshift-apiserver
openshift-controller-manager

..but not for:

kube-controller-manager
kube-scheduler

Fixed in https://github.com/openshift/hypershift/pull/1388
/close


Height of nested columns is not calculated correctly

Hi,
I'm playing around with iced. I tried GTK rs and OrbTK before. So far I like iced the most. Thanks a lot for all your hard work on that!
I'm building a small test program to search files. The search results are limited to 100 and the user is able to fetch more results with a load more button on the bottom of the results. When clicking on a search result the programm will try to open the file with the associated default program.
Since I need to configure where to search I embedded the search mask into a small tab control. Now It seems that the height of the column inside the tab control does not calculate correctly, because the last five results or so are not visible and the scrollbar is cut off.
See screenshots here:
https://www.notion.so/Search-UI-clipped-scrolbar-1dd435b4ee604e4ab4060971942becc7
For now I set the height of the inner column to fixed to fixed height of 600. If you want to reproduce the issue you can comment out that in line 113 of the /file_search/src/search.rs
The code can be found here
https://github.com/njust/file_search
Thank you again for such a great GUI library!

Hey @njust, thanks for the kind words! I am glad you like the library and very happy to see interesting test apps being built with it!
This bug is caused by a wrong implementation of Widget::height in some widgets. I fixed it in #60.
However, the current flex layout algorithm always uses the parent container max limits for children that does not have a Length::Fill in the main axis. I am guessing we could subtract from that the size of the previous children to try to make content fit properly. I'll give it a bit more thought!
Therefore, in order to make it work for now, you will need to explicitly set the height of the column to Length::Fill (simply replace Units(600) with Fill).

Thank you so much for the quick answer. Unfortunately it makes no difference if I leave out .height(Length::Units(600)) or use Length::Fill. Both times the scrollbar will be cut off.

@njust Did you try it with the branch of #60? It should work with the fixes there. I just double checked, and these simple changes work as expected for me:
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -7,6 +7,6 @@ edition = "2018"
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

 [dependencies]
-iced = {git = "https://github.com/hecrj/iced.git"}
+iced = {git = "https://github.com/hecrj/iced.git", branch = "fix/required-width-height"}

--- a/src/search.rs
+++ b/src/search.rs
@@ -110,7 +110,7 @@ impl SearchUi {
         Column::new()
             .push(search_bar)
             .push(result_scrollable)
-            .height(Length::Units(600))
+            .height(Length::Fill)
             .into()
     }

Sorry, I missed the fact, that it's fixed in a separate branch. I checked it with the branch and it works fine. Thank you very much!


One Dimensional Tensor Transformer with TensorFlow Graph

What changes are proposed in this pull request?
Apply TensorFlow graphs with 1D tensor inputs as Transformers.
How is this patch tested?

[x] Unit tests
[x] Manual tests

Codecov Report

Merging #39 into master will increase coverage by 0.67%.
The diff coverage is 95.74%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
+ Coverage   85.06%   85.74%   +0.67%
==========================================
  Files          19       20       +1
  Lines         991     1038      +47
  Branches        5        5
==========================================
+ Hits          843      890      +47
  Misses        148      148

Impacted Files
Coverage Δ

python/sparkdl/transformers/param.py
84.61% <83.33%> (+4.18%)
:arrow_up:

python/sparkdl/transformers/tf_tensor.py
97.56% <97.56%> (ø)

Continue to review full report at Codecov.

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

I am designing the API around TensorFlow Graph + Input/Output Tensors.
The TFoS API takes a checkpoint directory for the (meta) graph. We can get a utility function to convert it to a TensorFlow Graph.

@phi-dbq I have merged #45, which should unblock you now. Let me know if you encounter some issues.

@phi-dbq, left you a few more comments skimming the latest but I'm not sure if I'm supposed to review again yet. Let me know when it's ready.

Closing this PR in favor of the stacked PR holistic view
https://github.com/phi-dbq/spark-deep-learning/pull/12


[CELEBORN-1147] Added a dedicated API for RPC messages which also accepts an RpcResponseCallback instance

What changes were proposed in this pull request?
Currently in BaseMessageHandler there is a single API for receive which is used for all messages. This makes handling messages when multiple handlers are added messy.

req.body.release() is only invoked when the handler actually process the message and not delegates it.
every handler will have to create an instance of RpcResponseCallback for Rpc messages which is exactly the same.

Instead, releasing the message body and creating a callback for Rpc messages can be done in TransportRequestHandler. This avoids:

code duplication related to RpcResponseCallback in every RPC handler
every new request handler doesn't need to release the request body. It will be always be done in TransportRequestHandler.

Please note that this is how it is in Apache Spark and with Sasl Authentication, we will add a SaslRpcHandler (https://github.com/apache/incubator-celeborn/pull/2105) which wraps the underlying message handler.
Why are the changes needed?
The changes are needed for adding authentication to Celeborn. See CELEBORN-1011.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing UTs and added some more UTs.

@waitinfuture  @mridulm @RexXiong @FMX @pan3793 @akpatnam25 @rmcyang
Could you please take a look.

@waitinfuture @RexXiong @FMX @pan3793 gentle ping. There has been an initial review. Please help review.

The class name BaseMessageHandler is quite confusing, as we have another irrelevant class MessageHandler, would it be better to rename it to RpcHandler as Spark does? @waitinfuture

The class name BaseMessageHandler is quite confusing, as we have another irrelevant class MessageHandler, would it be better to rename it to RpcHandler as Spark does? @waitinfuture

BaseMessageHandler's children include FetchHandler, PushDataHandler and NettyRpcHandler, so it'll be confusing if renamed to RpcHandler. Maybe we can think of a better one in future PR.


[C++][Parquet] XCode 8.0 breaks builds

Exactly the same issues as
https://issues.apache.org/jira/browse/ARROW-313
cmake_modules/CompilerInfo.cmake has a hard-coded search for "clang-7", so it can't find the just-release Xcode 8 tools.
I can submit the patch if so desired.
Environment: Mac OS X, XCode 8.0, Apple LLVM version 8.0.0 (clang-800.0.38)
Reporter: Christopher Aycock / @chrisaycock
Assignee: Uwe Korn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uwe) / @xhochy
Note: This issue was originally created as PARQUET-736. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
Issue resolved by pull request 170
https://github.com/apache/parquet-cpp/pull/170

Uwe Korn / @xhochy:
PR: https://github.com/apache/parquet-cpp/pull/170


[!] The profile you selected did not result in a successful exploit EARU EAWCBT-P

hello. i  have smart breaker from EARU  EAWCBT-P  device that using CBU module. i have already tried  to cloud-cutting it using cloud cutter but  i have no luck of it. the device using 1.0.15 MCU. and i have tried using BK7231N / oem_bk7231n_slide_strip_ty as the profile but it is always  say [!] The profile you selected did not result in a successful exploit.
is there any suggestion for this?

1.0.15 is on the known patched list.  Serial flashing will be the only option for this device.


Changed reference of DocumentFormat.OpenXml to nuget

Hi @tarunchopra, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Tarun Chopra). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Did you look at taylors comment on my response ?
Thanks
TC | Sr. EE
On Feb 28, 2017, at 10:13 AM, tomjebo <notifications<EMAIL_ADDRESS>wrote:
Merged #113https://github.com/OfficeDev/Open-Xml-PowerTools/pull/113.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/Open-Xml-PowerTools/pull/113#event-980609954, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APiljZkeT4LROJNLBUS4jJcaeFqnErOuks5rhGPHgaJpZM4MBA4T.

@tarunchopra are you going to change this to project.json? otherwise, I'll leave it for now (assuming you've tested).

@twsouthwick : I'm under the impression that with introduction of vs2017, we are migrating from xproj to csproj. If this understanding is true; do we actually need this switch to xproj as you suggested?


Color.isCSSColorString is buggy

Color isCSSColorString was added in https://github.com/phetsims/scenery/commit/4e26f602ea3aea483fc2777ed5ec70eec076f4b7 for https://github.com/phetsims/scenery/issues/1115.
This is affecting work in bamboo, and I'll need to work around it.
It's buggy, and these examples are failing:
Color.isCSSColorString( null )
Color.isCSSColorString( undefined )
Color.isCSSColorString( {} )
There's no reason that isCSSColorString should ever fail; it should return true or false.
For example:
> phet.scenery.Color.isCSSColorString( null )
Color.js:812 Uncaught TypeError: Cannot read property 'replace' of null
    at Function.preprocessCSS (Color.js:812)
    at Function.isCSSColorString (Color.js:831)
    at eval (eval at window.assertions.assertFunction (assert.js:25), <anonymous>:1:20)
    at window.assertions.assertFunction (assert.js:25)
    at Color.set (Color.js:90)
    at new Color (Color.js:47)
    at Function.toColor (Color.js:623)
    at <anonymous>:1:20

Should Color.isCSSColorString( null ) -> 'transparent' ?  That's essentially what PaintDef does.

Should Color.isCSSColorString( null ) -> 'transparent' ?  That's essentially what PaintDef does.

On Slack, @jonathanolson says that isCSSColorString is documented to only support string.  If that's the case, please add an assertion.

On Slack, @jonathanolson says that isCSSColorString is documented to only support string.  If that's the case, please add an assertion.

Added an assertion. Presumably we could have a place checking to see if something is a valid color value if needed (and a type check included there), I'd prefer not to add type-checks in this type of function.

Added an assertion. Presumably we could have a place checking to see if something is a valid color value if needed (and a type check included there), I'd prefer not to add type-checks in this type of function.