text:
Add a property to enable or disable the PointerWheelEvent on the Calendar-control

What does the pull request do?
First of all this PR changes the way how the pointer wheel event is handled. Instead of selecting a different date it should only switch the displayed date. This prevents from accidently chaning the SelectedDate. Moreover the user can opt out this behavior in order to handle the PointerWheelChanged-Event on his own.
What is the current behavior?
The SelectedDate will change if you turn the pointer wheel
What is the updated/expected behavior with this PR?
Instead of chaning the SelectedDate only the DisplayDate should change if the pointer wheel was turned. Moreover the user should be able to handle the pointer wheel on his own.
How was the solution implemented (if it's not obvious)?

Changed the void OnPointerWheelChanged
Added a new StyledProperty named SwitchPageOnPointerWheel

Checklist

[ ] Added unit tests (if possible)?
[X] Added XML documentation to any related classes? ► For the new property
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation ► Has to be done after this PR is marked as OK.

Breaking changes

Pointer wheel will behave differntly after this PR is merged

Obsoletions / Deprecations

None
Fixed issues
Fixes #6579

Instead of selecting a different date it should only switch the displayed date. This prevents from accidently chaning the SelectedDate.

Yes, this is an excellent change - scrolling definitely should not change the selected date!

Moreover the user can opt out this behavior in order to handle the PointerWheelChanged-Event on his own.

However this I'm not so sure about - I can't really think of any precedent for adding a property to disable the scrollwheel. Feels like a niche feature and moreover one that could easily be implemented by intercepting the tunnelling scrollwheel event if needed (common with other controls that handle the scroll wheel).
It's true that adding the property isn't exactly high-cost, but my concerns are more about consistency with other controls. Do we also add this property to ScrollViewer, NumericUpDown etc?

Hi @grokys
first of all thank you for the feedback. But I think this change is not sooo easy to decide. Let me share my additional thoughts with you.

scrolling definitely should not change the selected date!

Yes, that was the root cause for me. But hitting the PageUp and PageDown keys still changes the selected date instead of just the display date. What is your feeling about this? Is this intended or also not intended? If not intended, I think I should also change this in the PR.

I can't really think of any precedent for adding a property to disable the scrollwheel

For this please imagine the following situation: You have a long page within a ScrollViewer. The user spins the mouse wheel to scroll down. Most controls will just let the user scroll down, but as soon as a Calendar is under the pointer the scroll stops and instead the calender changes the displayed month. This is different for different controls. Maybe I should open a seperate issue for this and provide a sample App there. The solution may be an attached property instead which can then be used by other controls as well.
To sum it up, I'll delete this property here and consider a different solution if needed.
/cc @maxkatz6
Happy coding
Tim

The solution may be an attached property instead which can then be used by other controls as well.

That may indeed be a good solution!

To sum it up, I'll delete this property here and consider a different solution if needed.

Yeah if you make this PR be just about not changing calendar selection with the scrollwheel that would be better.

I made a new PR for this as I think this solution was not the best.

authors: grokys timunie


text:
🐛: Automatic Copyright.

:red_circle: Title : Automatic Copyright.
:red_circle: Bug : Not a dynamic code
:red_circle: Changes :   I want to add a dynamic code in the footer so that year changes automatically every year.
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Tarushi Farainjiya
What is your participant role?  GSSOC

Hi I am Vibha Gupta and I would like to fix the issue.
I am working under GSSoC'24. Please assign me this issue.

@tarushi29 go ahead.

source: gharchive/issue

repo: Avdhesh-Varshney/WebMasterLog

license: MIT

license_type: permissive

license_source: github-api


text:
📃: Add Vowel Counter

:red_circle: Title : Vowel Counter
:red_circle: Aim : Counts the number of vowels in the entered input string by the user .
:red_circle: Tech Stack Used : HTML,CSS,JavaScript
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Meet Arora
What is your participant role? GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@meetarora10 go ahead.


text:
added Interview report project

Closes: #567

Title : Interview Report
Name: : -Maheshwari  Love
Idenitfy yourself: : GSSOC

Describe the add-ons or changes you've made 📃
How Has This Been Tested? ⚙

Screenshots 📷

Type of change ☑

What sort of change have you made:
added new project

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney please review this pr

@Avdhesh-Varshney please review this pr

enlist your project in readme file.

Done

source: gharchive/pull-request


text:
🛑 Mojang's Public API is down

In ace3d93, Mojang's Public API (https://api.mojang.com/) was down:

HTTP code: 429
Response time: 66 ms

Resolved: Mojang's Public API is back up in 440d263.

repo: AventiumSoftworks/helios-status-page


text:
Session Expired Component Only in French

Issue and Steps to Reproduce
Once application has been successfully configured, when the session expires the component rendered is only in French. It would be great to be able to pass in a custom component for this - is there already a way?

Versions
3.1.7
Screenshots

Thanks so much @guillaume-chervet! Do you know how to simulate a "session lost" instance without having to wait for a session to actually expire? Also, are there props that get passed down to the sessionLostComponent parameter? Wondering if there is a refresh prop already available that's being passed in or if I have to explicitly call from the custom button...

It hard to simulate, it is easier with the comming v4 version => https://www.npmjs.com/package/@axa-fr/react-oidc-context
code here => https://github.com/AxaGuilDEv/react-oidc/pull/687

repo: AxaGuilDEv/react-oidc


text:
Saved scans have wrong date

XC-108, DT forum

Dates were right

repo: AxelFougues/ZINC-public-resources


text:
UnicodeEncodeError: 'ascii' codec can't encode character '\xe3' in position 36: ordinal not in range(128)

Hello,
after add 3 monitors appears the error:

Traceback (most recent call last):
File "/root/cachet-uptime-robot/update_status.py", line 252, in
MONITOR.update()
File "/root/cachet-uptime-robot/update_status.py", line 219, in update
monitor['id'],
UnicodeEncodeError: 'ascii' codec can't encode character '\xe3' in position 36: ordinal not in range(128)

Are you sure you are using python3 ?

authors: ElJoelReis camilonova

repo: Axiacore/cachet-uptime-robot


text:
Make the shutdown timeout configurable

Hi,
I am not entirely sure whether I would classify this as a bug or as a missing feature. Summarized: It should be possible to make the shutdown timeout in DefaultConfigurer (which is five seconds) configurable, as it is possible that some components take longer to stop.
Please consider the following demo application which uses Axon's Spring Boot Starter.
@SpringBootApplication
public class DemoApplication {

	public static void main( final String[] args ) {
		final var applicationContext = new SpringApplicationBuilder( DemoApplication.class )
				.properties( "axon.axonserver.enabled=false" )
				.run( args );

		final var eventGateway = applicationContext.getBean( EventGateway.class );
		eventGateway.publish( 0 );

		await( ).until( ( ) -> MyEventHandler.elementProcessed.get( ) );

		applicationContext.close( );
	}

	@Autowired
	private void configure( final EventProcessingConfigurer configurer ) {
		configurer.registerTrackingEventProcessorConfiguration( MyEventHandler.PROCESSING_GROUP, c -> TrackingEventProcessorConfiguration
				.forParallelProcessing( 4 )
				.andEventAvailabilityTimeout( 20, TimeUnit.SECONDS ) );
	}

	@Component
	@ProcessingGroup( MyEventHandler.PROCESSING_GROUP )
	static class MyEventHandler {

		public static final String PROCESSING_GROUP = "MyEventHandler";

		private static AtomicBoolean elementProcessed = new AtomicBoolean( );

		@EventHandler
		public void on( final Integer i ) {
			elementProcessed.set( true );
		}

	}

}

In this demo application, we have a tracking event processor with four segments and an event awailability timeout of 20 seconds. We publish a single "event" for this handler (the zero) and wait until the event has been processed (we use Awaitility to wait for this to happen). Now we close the application context and - by doing so - shut the Axon infrastructure down. What we get is the following:
2021-10-19 13:14:32.802  INFO 22484 --- [           main] o.a.e.TrackingEventProcessor             : Shutdown state set for Processor 'MyEventHandler'.
2021-10-19 13:14:32.803  INFO 22484 --- [nPool-worker-19] o.a.e.TrackingEventProcessor             : Processor 'MyEventHandler' awaiting termination...
2021-10-19 13:14:37.812  WARN 22484 --- [           main] o.a.config.DefaultConfigurer             : Timed out during shutdown phase [1073741823] after 5 seconds. Proceeding to following phase

Notice that the DefaultConfigurer gives up after five seconds and simply continues. However, the threads of the TrackingEventProcessor are still running. This leads to a lot of exceptions after approximately 20 seconds (which is exactly the configured event awailability timeout). We start and stop application contexts very often in our integration tests. This behaviour is problematic for multiple reasons:

Some processors are still active once the framework executes the following tests. I am not entirely sure whether this can lead to weird and flaky test behaviour or not.
The log is full of error messages which are not related to the actual test. This makes it very difficult for us to see whether the test has actual issues.
Stopping and starting the event processor during tests (e.g. to test the reset behaviour) takes a long time. This might rather be our own fault, because the API clearly states: "Note that some storage engines for the EmbeddedEventStore do not support streaming. They may [...] wait for the timeout to occur."

I have two ideas how this might be solved:

As originally stated: Make the shutdown timeout configurable. We could set it to safe 25 seconds and be done with it.
Interrupt the tracking event processor during the shutdown and force him out of the processing loop.

Current Behaviour
The DefaultConfigurer waits exactly five seconds for all components to handle the current lifecycle phase.
Wanted Behaviour
Provide a possibility to configure the timeout duration for each lifecycle phase.
Workarounds
One could use a custom SmartLifecycle which runs before Axon and stops all event handlers asynchronously with a longer timeout.
	@Bean
	SmartLifecycle eventProcessorStoppingSmartLifecycle( @Autowired final EventProcessingConfiguration eventProcessingConfiguration ) {
		return new SmartLifecycle( ) {

			private boolean running;

			@Override
			public void stop( ) {
				try {
					eventProcessingConfiguration.eventProcessors( )
							.values( )
							.stream( )
							.map( EventProcessor::shutdownAsync )
							.reduce( ( cf1, cf2 ) -> CompletableFuture.allOf( cf1, cf2 ) )
							.orElse( CompletableFuture.completedFuture( null ) )
							.get( 25, TimeUnit.SECONDS );
				} catch ( InterruptedException | ExecutionException | TimeoutException e ) {
					// Do something smart with the exception
				}
				running = false;
			}

			@Override
			public void start( ) {
				running = true;
			}

			@Override
			public boolean isRunning( ) {
				return running;
			}
		};
	}

Thank you and best regards,
Nils

Hi @smcvb,
as #1999 seems to be related to this issue we gave it a try. I just would like to give you the feedback that it does not reduce the number of token updates in our application.
No offense intended, because you never mentioned any relationship between this issue and #1999. Nevertheless, we had some hope that it might help us, too.
That being said, are there any further ideas how to improve the situation. As far as I can see we need to interrupt the blocking (org.axonframework.common.stream.BlockingStream.hasNextAvailable(int, TimeUnit)) in case the application' shutdown process is triggered.

That being said, are there any further ideas how to improve the situation?

First and foremost through this pull request, which allows configuration of the lifecycle phase's timeout.
Secondly, I'll take a look at interrupting the event handling tasks in the TEP on a shutdown. I'll be sure to reference this issue once I have something workable for this.

First and foremost through this pull request, which allows configuration of the lifecycle phase's timeout.

Great! Thanks!

Secondly, I'll take a look at interrupting the event handling tasks in the TEP on a shutdown. I'll be sure to reference this issue once I have something workable for this.

When you achieve the something workable stage we can offer to run that snapshot against our test suite in order to ensure that the solution fits our needs and to address issues as early as possible.

When you achieve the something workable stage we can offer to run that snapshot against our test suite in order to ensure that the solution fits our needs and to address issues as early as possible.
That's awesome! I'll be sure to nudge you once the PR is out there :+1:

This issue's closed as a consequence of #2037 being merged.
This doesn't mean the aforementioned TEP adjustments aren't still underway. So, stay tuned!

Yo @nils-christian and @OLibutzki!
We've just finalized the changes made in issue #2041, which will interrupt the TEP's worker threads on a shutdown.
We are pretty confident this should provide better characteristics for your tests.
Nonetheless, we're curious to hear from your end whether the mentioned problems are tackled right now.
Although release 4.6.0 is still a way out, you can already validate the results by (temporarily) using the snapshot release we publish.

Yep, that assumption is correct, @OLibutzki. I'll kick it off again, as it seems to break because of some tokens it should simply have...

Is there any other chance than building the framework locally from the sources?

Nope, that would be simplest at the moment, I think.
Or, you can wait until I've got the build working again, of course :-)

I'm happy to share some numbers.
The execution time for our test suite decreased by 36% (from 308 seconds to 198 seconds), just by using the 4.6.0-SNAPSHOT instead of 4.5.5.
We applied this to another project and had similar results: Decrease from 142 seconds to 90 seconds.
We highly appreciate your efforts and resolving this issue was a nice pre-christmas present :-)
One minor note: The tests still pass which might be relevant as well ;-)

Thanks for sharing that with us, @OLibutzki!
Happy to hear it has the desired effect.
I also wanted to share that I spotted some issues within our GitHub Actions due to (I assume) merge conflicts.
I've just resolved the issues, so a recent SNAPSHOT release should be available right now.

One minor note: The tests still pass which might be relevant as well ;-)

Haha, definitely not unimportant! :-)

Hi @smcvb,
as the 4.6.0 release seems to take some more time, is there a chance to backport these enhancements to the 4.5.x stream?
Best regards
Oliver

Hi Oliver, nice to hear from you again.
Just to clarify, are you talking about PR #2037 and PR #2041?
Or just one of them?
I can see what we can do, but I can't make any promises at this stage yet.

Hi @OLibutzki!
I have found sometime to move #2037 and #2041 to axon-4.5.x.
This means they'll be part of Axon Framework release 4.5.13.
Furthermore, I hope to release 4.5.13 this week. Hence you'll be able to use these changes (hopefully) very soon. :-)

@smcvb, thank you so much!
You helped us a lot by moving this to the 4.5.x stream.
Keep up this great support / community work. It often is more important than just focussing on frequent releases and new features. Highly appreciated.

Just notifying you here @OLibutzki because I've released 4.5.13 about two hours ago. :-)

authors: OLibutzki nils-christian smcvb

repo: AxonFramework/AxonFramework


text:
Addition of Data Structures programs

Hey @Ayon-SSP, I can add programs of linked lists, stack, queues and other data structures. Please assign it to me.

@Ayon-SSP I have added some programs in linked lists and some algos in greedy too and sent a PR... Do check it out pls :)

repo: Ayon-SSP/The-SDE-Prep


text:
Relativity  [Problem Code: RELATIVE] Codechef

Problem Statement
In Chefland, the speed of light is c m/s, and acceleration due to gravity is g m/s2.
Find the smallest height (in meters) from which Chef should jump such that during his journey down only under the effect of gravity and independent of any air resistance, he achieves the speed of light and verifies Einstein's theory of special relativity.
Assume he jumps at zero velocity and at any time, his velocity (v) and depth of descent (H) are related as
v2=2⋅g⋅H.
Input
The first line contains an integer T, the number of test cases. Then the test cases follow.
Each test case contains a single line of input, two integers g, c.
Output
For each test case, output in a single line the answer to the problem. We can show that under the constraints, the answer is an integer.
Constraints
1≤T≤5⋅103
1≤g≤10
1000≤c≤3000
2⋅g divides c2.
Subtasks
Subtask #1 (100 points): Original constraints
Sample Input
3
7 1400
5 1000
10 1000
Sample Output
140000
100000
50000
Explanation
Test Case 1: For Chef to achieve the speed of light, the minimum height required is c22⋅g = 1400⋅140014 = 140000 meters.
Test Case 3: For Chef to achieve the speed of light, the minimum height required is c22⋅g = 1000⋅100020 = 50000 meters.
Fixes #1756
Type of change

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

Checklist:

[ ] My code follows the style guidelines(Clean Code) of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] My changes generate no new warnings

@Ayush7614 Kindly review my PR and merge it to the main branch !


text:
B6 - player can't connect if they didn't sleep after getting crystals

As of Beta6, when a player get initial hint from crystals, then disconnect before sleeping, he/she'll no longer be able to connect to a dedicated server.
There's a long chain of thaumcraft.common.lib.events.PlayerEvents.wakeUp related exception, that leads to this final one before kicking the player:
[17:30:39] [Server thread/WARN]: Failed to handle packet for /xxxxx:56680
net.minecraft.util.ReportedException: Loading entity NBT
>       at net.minecraft.entity.Entity.func_70020_e(Entity.java:1716) ~[rw.class:?]
>       at net.minecraft.world.storage.SaveHandler.func_75752_b(SaveHandler.java:222) ~[azy.class:?]
>       at net.minecraft.server.management.PlayerList.func_72380_a(PlayerList.java:322) ~[mp.class:?]
>       at net.minecraft.server.management.PlayerList.initializeConnectionToPlayer(PlayerList.java:1428) ~[mp.class:?]
>       at net.minecraftforge.fml.common.network.handshake.NetworkDispatcher.completeServerSideConnection(NetworkDispatcher.java:260) ~[NetworkDispatcher.class:?]
>       at net.minecraftforge.fml.common.network.handshake.NetworkDispatcher.access$100(NetworkDispatcher.java:73) ~[NetworkDispatcher.class:?]
>       at net.minecraftforge.fml.common.network.handshake.NetworkDispatcher$1.func_73660_a(NetworkDispatcher.java:209) ~[NetworkDispatcher$1.class:?]
>       at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:287) ~[eo.class:?]
>       at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:180) [md.class:?]
>       at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:732) [MinecraftServer.class:?]
>       at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:387) [ld.class:?]
>       at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:613) [MinecraftServer.class:?]
>       at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:471) [MinecraftServer.class:?]
>       at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
Caused by: java.lang.NullPointerException
>       at net.minecraft.entity.player.EntityPlayerMP.sendMessage(EntityPlayerMP.java:3741) ~[lu.class:?]
>       at org.spongepowered.api.text.channel.MessageChannel.lambda$send$3(MessageChannel.java:196) ~[MessageChannel.class:1.10.2-2477-5.2.0-BETA-2793]
>       at java.util.Optional.ifPresent(Optional.java:159) ~[?:1.8.0_151]
>       at org.spongepowered.api.text.channel.MessageChannel.send(MessageChannel.java:196) ~[MessageChannel.class:1.10.2-2477-5.2.0-BETA-2793]
>       at org.spongepowered.common.text.chat.ChatUtil.sendMessage(ChatUtil.java:58) ~[ChatUtil.class:1.10.2-2477-5.2.0-BETA-2793]
>       at net.minecraft.entity.player.EntityPlayerMP.func_145747_a(EntityPlayerMP.java:3755) ~[lu.class:?]
>       at thaumcraft.common.lib.events.PlayerEvents.wakeUp(PlayerEvents.java:123) ~[PlayerEvents.class:?]
>       at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_576_PlayerEvents_wakeUp_PlayerWakeUpEvent.invoke(.dynamic) ~[?:?]
>       at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90) ~[ASMEventHandler.class:?]
>       at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:632) ~[EventBus.class:?]
>       at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:588) ~[EventBus.class:?]
>       at net.minecraftforge.event.ForgeEventFactory.onPlayerWakeup(ForgeEventFactory.java:447) ~[ForgeEventFactory.class:?]
>       at net.minecraft.entity.player.EntityPlayer.func_70999_a(EntityPlayer.java:4094) ~[zs.class:?]
>       at net.minecraft.entity.player.EntityPlayerMP.func_70999_a(EntityPlayerMP.java:653) ~[lu.class:?]
>       at net.minecraft.entity.player.EntityPlayer.func_70037_a(EntityPlayer.java:905) ~[zs.class:?]
>       at net.minecraft.entity.player.EntityPlayerMP.func_70037_a(EntityPlayerMP.java:178) ~[lu.class:?]
>       at net.minecraft.entity.Entity.func_70020_e(Entity.java:1704) ~[rw.class:?]
>       ... 13 more
[17:30:39] [Server thread/INFO]: xxxx lost connection: Internal server error

Manually removing the crystal knowledge from its player data fixed it.

Issue isn't reproduced in single player.

Looks like shenanigens caused by spongepowered, but I will try and catch the exception on my side.

authors: Azanor LemADEC

repo: Azanor/thaumcraft-beta


text:
[Epic] Proof Timeliness and Prover Coordination

Overview
Design docs of proof timeliness and prover coordination.
I'm lumping them together within this one epic because they're tightly related in practice/development, though the key  observation is that the Proof Timeliness work is largely enshrined and on L1, and the Prover Coordination work is not.
As a quick overview of the functionality we want with this epic.
Proof timeliness
An epoch is comprised of many blocks (e.g. 32).
On L1, we keep track of a pending chain tip, and a proven chain tip (which is a prefix of the pending chain).
The committee can post blocks to the pending chain, once per L2 slot (e.g. every 36 seconds).
One epoch is proven at a time, and verified on L1.
When epoch n ends, its proof must land in epoch n+1.
The first 13 proposers in an epoch have the ability to post a prover commitment bond, and subsequently the proof.
Doing so claims the TST block rewards that will be distributed once the epoch is proven according to the fee specified by the prover.
The bond they post must come out of an escrow specifically designed for holding prover commitment bonds.
If a bond to prove epoch n-1 doesn't land in the first 13 slots of epoch n, then the pending chain tip get reorged back to point to the last proven block (i.e., the last block in epoch n-2).
If a bond to prove epoch n-1 does land in time, but a proof does not land in epoch n, this results in the same reorg back to the last proven block.
Prover coordination
It is doubtful that the proposers will actually be running their own proving infrastructure. They will, instead, be coordinating with proving marketplaces to get bonds and proofs posted; this is what "prover coordination" refers to.
There will be an optional p2p layer to allow prover marketplaces to submit quotes, which will allow proposers to immediately submit the quote to L1.
The quotes will be signed such that the proposers can use the provers funds in escrow for the purpose of the prover commitment bond.
Stress test of functional requirements
We must demonstrate that 20 actors representing proving marketplaces can submit bids, that at most 1 bid can be accepted on L1 during, the bid can only be accepted during the proof claim period of a prescribed epoch, the bid is only actionable on L1 if the prover has the requisite bond in TST, and that all the above works when there are 300 nodes on the p2p network, and the chain is operating at 1TPS with proving turned on.
### Tasks
- [x] Spec design
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8401
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/8679

closed in favor of the two supporting, distinct epics

repo: AztecProtocol/aztec-packages


text:
test: Rangecheck with consistent bit size

Please read contributing guidelines and remove this line.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 3063bf32 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,956
181,604
724,196

l1_rollup_calldata_gas
227,108
888,764
3,535,976

l1_rollup_execution_gas
320,299
1,007,212
3,756,354

l2_block_processing_time_in_ms
1,171 (+1%)
4,674 (+7%)
17,292

note_successful_decrypting_time_in_ms
315
1,037 (+7%)
3,650 (+2%)

note_trial_decrypting_time_in_ms
23.9 (-2%)
42.7 (-56%)
145 (-3%)

l2_block_building_time_in_ms
18,216
72,299 (+1%)
289,727

l2_block_rollup_simulation_time_in_ms
13,485
53,537
215,098

l2_block_public_tx_process_time_in_ms
4,699 (+1%)
18,685 (+1%)
74,372 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,790 (+2%)
28,898 (+5%)

note_history_successful_decrypting_time_in_ms
2,353
4,754 (+4%)

note_history_trial_decrypting_time_in_ms
92.0 (-7%)
162 (-31%)

node_database_size_in_bytes
17,272,912
33,157,200

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
330 (+1%)
44,528
25,313

private-kernel-ordering
197 (+1%)
43,633
16,193

base-rollup
1,458
129,774
933

root-rollup
91.0 (+10%)
4,192
729

private-kernel-inner
439 (+1%)
70,819
25,313

public-kernel-private-input
240
33,663
26,945

public-kernel-non-first-iteration
240 (+1%)
33,705
26,945

merge-rollup
8.02 (+2%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
128 leaves
64 leaves
512 leaves
1024 leaves
2048 leaves
8192 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.2
10.6 (-10%)
12.9 (+2%)
17.2 (+2%)
28.6 (+26%)
64.2 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
143
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.594 (-1%)
0.594 (-10%)
0.548 (+2%)
0.532 (+1%)
0.600 (+26%)
0.442 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
74.7 (-1%)
47.6 (-1%)
240
463
902
3,562

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
159
96.0
543
1,055
2,079
8,223

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.462 (-1%)
0.488 (-1%)
0.437
0.434
0.429
0.428

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
104 (+1%)
57.0
354 (-1%)
688
1,372
5,433

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
197
104
691
1,363
2,707
10,771

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.492
0.499
0.477 (-2%)
0.473
0.476
0.472

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
56.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
94.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
0.578
N/A
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
16,859
39,794

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
556
1,450

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.524
577 (+1%)

authors: AztecBot sirasistant


text:
chore: move alpine containers to ubuntu

Move bb alpine containers to be built in ubuntu.
Closes #4708

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (8): 11.2 (-89%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 5cccc78e and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,700
18,884
36,452

l1_rollup_calldata_gas
66,492
239,336
470,216

l1_rollup_execution_gas
194,440
500,642
909,474

l2_block_processing_time_in_ms
1,183 (-1%)
4,484 (-1%)
8,924 (-1%)

note_successful_decrypting_time_in_ms
202 (+3%)
555 (+1%)
1,006 (-1%)

note_trial_decrypting_time_in_ms
:warning: 11.2 (-89%)
80.2 (+23%)
35.0 (-35%)

l2_block_building_time_in_ms
11,141
44,340
89,243

l2_block_rollup_simulation_time_in_ms
7,309 (-1%)
29,368
59,024

l2_block_public_tx_process_time_in_ms
3,800
14,907
30,069 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,156 (-1%)
27,018 (-2%)

note_history_successful_decrypting_time_in_ms
1,206 (-2%)
2,381

note_history_trial_decrypting_time_in_ms
66.1 (-8%)
98.8 (+1%)

node_database_size_in_bytes
18,776,144
35,573,840

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
253
44,736
28,001

private-kernel-ordering
195 (+1%)
52,625
14,627

base-rollup
652 (-1%)
177,932
997

root-rollup
68.0 (-1%)
4,320
825

private-kernel-inner
321
73,715
28,001

public-kernel-app-logic
164 (-1%)
32,256
25,380

merge-rollup
8.49 (-1%)
2,840
997

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves

batch_insert_into_append_only_tree_16_depth_ms
9.86 (+1%)
10.3 (-6%)
12.4 (-27%)
15.8 (-3%)
22.1 (-1%)
35.5 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
79.0
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.574 (+1%)
0.577 (-6%)
0.523 (-28%)
0.489 (-3%)
0.462 (-1%)
0.442
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
46.0 (+1%)
71.6 (-1%)
230 (-2%)
436 (-2%)
870 (-1%)
1,727 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
96.0
159
543
1,055
2,079
4,127

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.472 (+1%)
0.442 (-1%)
0.420 (-2%)
0.409 (-2%)
0.414 (-1%)
0.414 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
52.8 (-1%)
107
335
646 (-2%)
1,308 (-2%)
2,612

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
104
207
691
1,363
2,707
5,395

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.472 (-1%)
0.481
0.456
0.445 (-2%)
0.454 (-2%)
0.453

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
60.4 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
109
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
0.529 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts

tx_size_in_bytes
19,179

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
2,610 (-4%)
1,374

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
5.58 (+1%)
461 (-1%)

authors: AztecBot IlyasRidhuan


text:
fix(avm): Do not scale CALLDATACOPY base cost with size

As discussed with @fcarreiro, base gas cost should only scale if we do something with the data. If we're just copying it, then the additional memory accesses take care of reflecting the additional effort.

Docs Preview
Hey there! 👋 You can check your preview at https://6622aa1c67b320095e4ac4d0--aztec-docs-dev.netlify.app

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (8): 239 (+21%)
note_trial_decrypting_time_in_ms (32): 70.6 (+276%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,820
6,820
6,784 (-1%)

l1_rollup_execution_gas
587,301
587,301
587,265

l2_block_processing_time_in_ms
1,516 (+4%)
5,722 (+9%)
10,490 (+1%)

note_successful_decrypting_time_in_ms
:warning: 239 (+21%)
570 (+10%)
1,113 (+4%)

note_trial_decrypting_time_in_ms
31.1 (-64%)
:warning: 70.6 (+276%)
23.6 (-1%)

l2_block_building_time_in_ms
19,043 (+2%)
74,242 (+1%)
147,880 (+1%)

l2_block_rollup_simulation_time_in_ms
18,831 (+2%)
73,502 (+1%)
146,279 (+1%)

l2_block_public_tx_process_time_in_ms
8,652 (+2%)
33,836 (+1%)
67,445 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,577 (+6%)
32,040 (+8%)

note_history_successful_decrypting_time_in_ms
1,407
2,710

note_history_trial_decrypting_time_in_ms
80.8 (-28%)
79.1 (-27%)

node_database_size_in_bytes
20,762,704 (+9%)
37,396,560 (+4%)

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
158
47,763
31,978

private-kernel-inner
178 (+1%)
80,794
31,978

private-kernel-ordering
138 (+1%)
57,732
49,313 (-1%)

base-parity
9.10 (-3%)
128
265

root-parity
67.9 (-10%)
1,244
265

base-rollup
11,971
110,926
957

root-rollup
49.6
4,551
821

public-kernel-app-logic
1,578 (+1%)
62,017
26,202

public-kernel-tail
4,253 (+1%)
168,566
3,812

merge-rollup
3,162 (-2%)
2,760
957

public-kernel-teardown
121 (+2%)
62,017
34,711

public-kernel-setup
132 (-1%)
62,017
34,711

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.9 (-2%)
17.8 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.639 (-1%)
0.547
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.8 (+1%)
80.2
261 (+1%)
503
993 (+1%)
1,949 (+1%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.531 (+1%)
0.496
0.475 (+1%)
0.470
0.470
0.467 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
60.8 (+1%)
120 (+1%)
375 (+1%)
740
1,470 (+1%)
2,921 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.536
0.540 (+1%)
0.511
0.510
0.507
0.508
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
66.9 (-1%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108 (-1%)

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.589

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
51,411
536,920 (-1%)

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
897
1,145
1,345

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,226 (-2%)
867
3,484 (-2%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
841
760 (-1%)
1,356 (-1%)
899 (-2%)
2,073 (-1%)
1,077 (-2%)

authors: AztecBot spalladino


text:
test user for mydriving

Hi
I need to test mydriving app on my lenovo android tab
How can I test it.
I got hocky app account and i go to my account but i didn't got how to add mydriving app and ltest it
Notice i didn't attend build.
Thanks

Please check out the directions here https://azure.microsoft.com/en-us/documentation/articles/iot-solution-get-started/

repo: Azure-Samples/MyDriving

license: mit

license_source: bigquery


text:
Dockerize

Purpose

Enable the app to run in docker
Establish ENV variables and consolidate to a single file

Does this introduce a breaking change?
[ X ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ X ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Run the code in docker

dockerImage=angular-cosmosdb
port=3001
docker build -t $dockerImage .

# create and run the container
docker run  -d -p $port:3001 -p 5858:5858 -e "TWITTER_CALLBACK_URL=http://localhost:$port/api/auth/twitter/callback" $dockerImage

open http://localhost:$port

What to Check
Verify that the following are valid

The app loads in the browser
You are unable to save changes without logging in
The login button logs you in, and no errors in console
The logout button logs you out

Other Information

Smile

@johnpapa,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

authors: johnpapa msftclas

repo: Azure-Samples/angular-cosmosdb


text:
How i automatize replacing of a file/document with a new version ?

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

The prepdocs script can be used with modifiers to remove a file and add a new file, per the documentation here:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/data_ingestion.md#indexing-additional-documents
Can you specify what you mean by automate?

You might also look into integrated vectorization if you're looking for scheduled ingestion. That's also detailed in the same guide.

may be a dumb or obvious question are there any additional costs that come along with scheduling ingestion for say every 2 hours?

Hi,
I read the following part from the guide.
To add additional documents to the index, first upload them to your data source (Blob storage, by default). Then navigate to the Azure portal, find the index, and run it. The Azure AI Search indexer will identify the new documents and ingest them into the index.
But I still couldn't do it. :(
I uploaded my own data into the blob. Then I opened it to the Search service via the portal.
How can I run the current index from the index page?
Isn't an indexer needed to update the existing index? When I want to create an indexer for the current index, what skillset should I create before this? (I added the relevant blob in the Data sources tab in the Search service.)

repo: Azure-Samples/azure-search-openai-demo


text:
How to categorize data for indexing

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

scripts/prepdocs.sh1 --category ExampleCategory
Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 11

azd version?

run azd version and copy paste here.
azd version 1.10.4

Versions

Mention any other details that might be useful
I want to know how to categorize the data if I have three type types of documents.
I understand that adding an extra tag of --category will enable me to do that.
Lets say there HR, Finance.
How do I add in under the data folder
data/HR/file1.pdf
data/HR/file2.pdf
and
data/Finance/file1.pdf
data/Finance/file2.pdf
I will run
scripts/prepdocs.ps1 --category HR
It will do the steps and ingest the data into the Vector index in AI Search and add the category to the metadata fields.
But the scripts keeps running and enter the next folder on its own. Since there is a folder switch does it automatically take in the next category ?
Or
Should I interuppt the previous script after all documents are done.
And run
scripts/prepdocs.ps1 --category Finance
And then it starts the ingestion process again.
Please guide me into understanding what is the ideal way.

Thanks! We'll be in touch soon.

cc @bnodir who has worked more with categories and may have advice.

@mrisahoo1 - To categorize your documents for indexing, you can run the ingestion script for each category separately as you already figured out, or you can modify the .\scripts\prepdocs.ps1 script as follows for your needs:
./scripts/load_python_env.ps1

$venvPythonPath = "./.venv/scripts/python.exe"
if (Test-Path -Path "/usr") {
  # fallback to Linux venv path
  $venvPythonPath = "./.venv/bin/python"
}

Write-Host 'Running "prepdocs.py"'

$cwd = (Get-Location)
$dataDir = "$cwd/data"

# Iterate over directories in ./data
Get-ChildItem -Path $dataDir -Directory | ForEach-Object {
  $dir = $_.FullName
  $CONTENT_CATEGORY = $_.Name
  $dataArg = "`"$dir/*`""
  $additionalArgs = ""
  if ($args) {
    $additionalArgs = "$args"
  }

  $argumentList = "./app/backend/prepdocs.py $dataArg --verbose --category $CONTENT_CATEGORY $additionalArgs"

  Write-Host ">>> !!! Processing category: $CONTENT_CATEGORY !!! <<<"
  Start-Process -FilePath $venvPythonPath -ArgumentList $argumentList -Wait -NoNewWindow
}

This script iterates over each subdirectory in the data directory and processes the files within it, passing the folder name as the category. Note that folder names (which in this case become category names) should not include spaces, as category names are not allowed to have any.

authors: bnodir mrisahoo1 pamelafox


text:
ACA deployment does not configure built-in auth

This issue is for a: (mark with an x)
- [ X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

The authentication setup process completes without any visible errors, but the login screen does not appear before the application opens.
This functionality was working correctly for me in previous versions or deployments.
Minimal steps to reproduce

Set the environment variables:azd env set AZURE_USE_AUTHENTICATION true
azd env set AZURE_AUTH_TENANT_ID <YOUR-TENANT-ID>
azd env set AZURE_ENFORCE_ACCESS_CONTROL true

Run the deployment command:azd up

Any log messages given by the failure

Checking if authentication should be setup...
AZURE_USE_AUTHENTICATION is set, proceeding with authentication setup...
Creating Python virtual environment "app/backend/.venv"...
Installing dependencies from "requirements.txt" into virtual environment (in quiet mode)...
Setting up authentication for tenant
Checking if application exists
Application already exists, not creating new one
Setting up server application permissions...
Checking if application  exists
Application already exists, not creating new one
Setting up server known client applications...
Authentication setup complete.

Expected/desired behavior

Show login screen before opening the application.

OS and Version?

GitHub Codespace

azd version?

azd version 1.11.0

Instead the following information is shown in the chat input bar:

It seems to me that the application's behavior has changed, requiring users to log in via the "Login" button located at the top-right corner. Is that correct? If so, I’m not sure this change improves the user experience.

The new default deployment environment is ACA, which we didnt configure "built-in auth" for. We could set that up for ACA, though I was thinking of removing it entirely, since it's somewhat redundant with our use of the MSAL SDKs for authentication. Do you prefer the behavior where it doesn't even show you the app and forces login? The ACA behavior mimics how it has always worked locally, by the way.
cc @mattgotteiner

This solution doesn’t quite work for my project for two main reasons. First, the application is currently accessible to everyone, even users who aren’t logged in, which we can’t allow. Second, our users shouldn’t have to search for the login button—they should be able to log in through the familiar Microsoft login screen to keep things secure and user-friendly. For now, I’ll switch back to using an App Service.

Got it. I can add the ACA built-in auth configuration. I'll work on that shortly.

When I use the command:
azd env set DEPLOYMENT_TARGET appserviceI
I encounter the following error during deployment:
`Deploying services (azd deploy)
(x) Failed: Deploying service backend
ERROR: error executing step command 'deploy --all': failed deploying service 'backend': validating target resource: resource 'app-backend-poapuqez675su' with type 'Microsoft.Web/sites' does not match expected resource type 'Microsoft.App/containerApps'`
It seems like there's a mismatch between the deployed resource type (Microsoft.Web/sites) and the expected resource type (Microsoft.App/containerApps) for the backend service. To troubleshoot, I’ve already taken the following steps:

Used azd down to remove the existing resources.
Used azd env new to create a fresh environment and resource group.

Despite this, the issue persists. Any insights on how to resolve this?

Did you do step 1, the commenting out in azure.yaml?
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/azure_app_service.md
Unfortunately we cant control that with just env vars yet.

Did you do step 1, the commenting out in azure.yaml? https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/azure_app_service.md Unfortunately we cant control that with just env vars yet.

You’re right—I missed that step. I assumed the earlier steps were the same as before. Thanks for pointing it out!

authors: jeannotdamoiseaux pamelafox


text:
ERROR: failed packaging service 'backend': failed invoking event handlers for 'prepackage', 'prepackage' hook failed with exit code: '137', Path: '/tmp/azd-prepackage-3839507466.sh'. : exit code: 137

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ x ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

run azd up for existing resources. it runs for some time and then errors out.

Expected/desired behavior

should work quickly

OS and Version?

Linux Ubuntu 20.04 LTS

Mention any other details that might be useful

Thanks! We'll be in touch soon.

able to resolve by increasing the size of my VM


text:
docs: replace chat screenshot

replace chat screenshot in readme.

The size is much smaller than previously and it's hard to see...

bumped resolution.


text:
Enable switching cameras

Purpose

Adds the ability to switch front/back cameras

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Test the code
Verify that the following are valid
On real and emulated devices, verify that the switch camera button is available when camera is enabled
Verify that you can switch from the front and back cameras without issues
NOTE: On Android Emulators, when you switch to the back camera, an extra tap is required afterwards, since focus was brought away from the emulator to show you that you can pan the back camera.  You won't find this same behaviour on a real device.

Other Information

Tested on the pixel 4a, the camera switch works on all different cases of layout during the call (only self screen, 1 on 1 and grid).
One thing I am not sure, if we need to align the upper boundary of camera switch button with the upper boundary of participants' count notification bar or not.

Tested on the pixel 4a, the camera switch works on all different cases of layout during the call (only self screen, 1 on 1 and grid).
One thing I am not sure, if we need to align the upper boundary of camera switch button with the upper boundary of participants' count notification bar or not.

@waynemo What do you think?  I can align it when it appears, but it may throw users off when the button jumps location.  Or I can move it down a bit in a static fashion.  I suspect this button will be covered up by the compliance messages in Teams interop.

As per https://skype.visualstudio.com/SPOOL/_workitems/edit/2407134/ I've placed the button on the right center now

Thanks to @cheukchuen's feedback, I've put the button back to the top right only in the PIP window.

tested yesterday during call with Yukon

authors: Gemakk iaulakh lpx1989


text:
[Docs] Local and pipeline testing

I think the playwright docs could use a little framing so someone understands what needs to run and how to develope and run tests locally and to run in the pipeline.
For example, in order to run the playwright e2e tests, the web app and apis need to be running. That might seem like a precondition/conf for playwright in the test package itself, or something that is done outside the playwright testing package at the root level with npm workspaces.
An architectural drawing of how this works and then a package/file level view of which files are involved would be helpful.

I think the playwright docs could use a little framing so someone understands what needs to run and how to develope and run tests locally and to run in the pipeline.
For example, in order to run the playwright e2e tests, the web app and apis need to be running. That might seem like a precondition/conf for playwright in the test package itself, or something that is done outside the playwright testing package at the root level with npm workspaces.
An architectural drawing of how this works and then a package/file level view of which files are involved would be helpful.

This is absolutely fantastic feedback - thank you for the issue @core-dev-out!
I am currently in the process of writing/migrating a "docs" package over that will act as a developer guide for the entire repo - and it has a Playwright section in it. I'll update this thread with the link when that gets merged (likely to take a week or so)

Sorry for the delay - just updating this thread to say that I've started refactoring the  packages/testing to reflect new capabilities (and recommendations) from Playwright team so expect changes soon. I should have a first version in later this week and will update this discussion thread with details then
On the documentation front - just added a packages/docs section that is adding a more detailed developer guide that can be run in local preview mode. I will be adding a Testing section to that guide next week that will address the great feedback on diagrams and project structure if that helps. _You can see a GitHub Pages hosted version of the guide in my personal fork.

authors: core-dev-out nitya

repo: Azure-Samples/contoso-real-estate


text:
adding service account for mqtt-client

Purpose

adding service account for mqtt-client

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

@dominicbetts can you approve this?

repo: Azure-Samples/explore-iot-operations


text:
Improve Intel SGX SDK Attestation Sample

Purpose

I was trying out the Intel SGX based SDK attestation sample, and had to do multiple changes to the steps which are currently mentioned for quote generation and quote validation. Creating this PR with changes I had to do in the steps to make it work, to help in easing the consumption of this sample by others in future.
Following is the summary of all the changes in this PR,

Adding more packages which are required to be installed

Without these various related errors are observed at various steps

Adding details about installing Azure DCAP

Otherwise PCCS is tried to be contacted instead of Azure THIM

Add instruction about performing Azure login using Azure CLI which is required for the Quote verification step
Changing the sample quote validation code

This change is as suggested by a related issue in azure-sdk-for-net (https://github.com/Azure/azure-sdk-for-net/issues/17052#issuecomment-729998843)
Without this change, quote validation step was not going through

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code

Follow the instructions in the Intel SGX SDK based Attestation Sample

Other Information
This was observed and tested on a Intel SGX based Azure VM with Ubuntu 20.04 as the Operating System

@microsoft-github-policy-service agree


text:
The reference document link in README.md is Implicit grant flow.

In Readme.md line 55, The link to "For more information, see the documentation" in 1.3 of "Running the sample" is below,
but this is the Quickstart of Implict grant Flow.
https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-javascript
The following authentication code flow Quickstart also exists, so it is better to change.
https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-javascript-auth-code
Can I create Pull Requests to fix link?

@g-child good catch! Please go ahead and make a PR if you like.

@derisen
Can you review PR?
I tried to set the reviewer to PR, but it doesn't seem to work with my account.

authors: derisen g-child


text:
Allow relocation of VHDX for Mariner VM - honor HyperV Settings

Describe the bug
On a system with a small system drive but a larger second drive, it should be possible to install the VM using an alternate path for the VHDX or to honor the settings in HyperV.
It appears the installer script is simply comparing the requested "DataSizeInGB" with available space on the C: drive.
 "DataSizeInGB": 500
Drives:
C                 554.12        376.69 FileSystem    C:\
E                   0.13        894.13 FileSystem    E:\
HyperV is correctly configured to store VHDX files in a folder on the E: Drive.
To Reproduce
Set DataSizeInGB lrager than free space on C: while HyperV is configured to store VHDX on a drive with plenty of space.
Run: New-AksEdgeDeployment -JsonConfigFilePath .\aksedge-config-full.json
[05/04/2023 14:53:28] Verifying Host Requirements for Linux node(s)

 - Verifying static IP support for selected configuration
 - Verifying host requirements for selected configuration (510 GB disk size, 16884 MB memory, 4 CPUs)

[05/04/2023 14:53:28] Verifying Host OS can support requested configuration

[05/04/2023 14:53:28] Verifying required storage, RAM and number of cores are available

 - Drive 'C:' has 376 GB free
 - A minimum of 510 GB disk space is required on drive 'C:'

[05/04/2023 14:53:28] Exception Caught!!!

 - Not enough disk space is available on drive 'C:'. (AksEdge-Core.psm1:6734)

[05/04/2023 14:53:29] Host machine does not fulfill system requirements for Linux deployment

Expected behavior
Allow the user to configure where to store VHDX besides C: or honor current HyperV settings.
Environment (please complete the following information):

AKS Edge Essentials Version [e.g. 3.22]

  "SchemaVersion": "1.6",
  "Version": "1.0",
  "DeploymentType": "ScalableCluster",

Kubernetes version ??
Windows Host OS (please complete the following information):

Edition: Enterprise
Version: 21H2  22000.1817
Virtual Machine: Linux

Additional context
Add any other context about the problem here.

Hyper-V settings are not used here. Please refer to https://learn.microsoft.com/en-us/azure/aks/hybrid/aks-edge-howto-setup-machine#install-aks-edge-essentials for configuring the vhdxdir during the msi install process.

So more of a documentation issue.  I see the option in the msi command line. If I read the docs more carefully I see it mentioned as an option.  Maybe have a side note calling out, "If you want to locate the Mariner/Windows vhdx on another drive you should use the VHDXDIR option" might be helpful.
msiexec.exe /i AksEdge-kXs-x.x.xxx.x.msi INSTALLDIR=C:\Programs\AksEdge VHDXDIR=C:\vhdx
Thanks!  I think you can close this as "not a bug"....  Or resolved.
I did find the vhdx, it is in the "Program Files" folder, not where I expected it.

authors: kvietmeier parameshbabu

repo: Azure/AKS-Edge


text:
Use configurable OCP release branch for vendor dependencies

Which issue this PR addresses:

What this PR does / why we need it:
Use configurable OCP release branch for vendor dependencies.
The OCP release branch was by default 4.10, and since it is quite old and users/devs might want to use newer versions then modifying it on the makefile could simplify this procedure
Also, it includes some markdownlint suggestions in the last commit.

Test plan for issue:

Is there any documentation that needs to be updated for this PR?
Yes, and it was updated in docs/upstream-differences.md.

How do you know this will function as expected in production?

Also see https://github.com/Azure/ARO-RP/pull/3451

Thanks @hawkowl I can see it will be updated and set to 4.12, but isn't making it configurable from Makefile wouldn't be easier to maintain and use?

This is on a fork and as such won't be able to run CI. You'l need to switch to a branch off master

Your review @tiguelu @mociarain slipped out of my notifications and I saw @bitoku work, so I believe this PR can be closed.
But if any of my comments/ideas of this PR could be valid (and helpful) in the other repo, then I would create a new PR for the https://github.com/openshift/installer-aro-wrapper repo.
Any thoughts? @bitoku

authors: hawkowl mociarain razo7

repo: Azure/ARO-RP


text:
remove deprecate flag keep-terminated-pod-volumes

What type of PR is this?
/kind feature
/kind deprecation
What this PR does / why we need it:
Romove deprecate flag --keep-terminated-pod-volumes
Which issue(s) this PR fixes:
Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build 10575495028
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.409%

Totals

Change from base Build 10573719317:
0.0%

Covered Lines:
2620

Relevant Lines:
3669

💛  - Coveralls

has there already been a change on the RP side for removing this flag?

RP will delete this flag in pr that supports 1.31 version.  This flag has been deprecated since 2017

I'm not sure about the sequential dependency between this part of the change and the change of the RP, and how to change the testdata of the RP, can you help to explain it?

it looks like your changes are only removing hard-coded references to this flag from testing code, which should be fine to merge right now
it sounds like we're letting RP dictate when to correctly set the flag, so I think we're fine in terms of dependency ordering regardless

authors: cameronmeissner coveralls wenhug

repo: Azure/AgentBaker


text:
App Configuration Data Plane resource GET After PUT Return 404

A GET after successful PUT should not return 404 (NOT FOUND). Occationally(Not 100% reproducible) the App Configuration Key resource would return 404 for GET after PUT.
Swagger file: https://github.com/Azure/azure-rest-api-specs/blob/280a956db30d829fa65a9c0fdede073261ad76bf/specification/appconfiguration/data-plane/Microsoft.AppConfiguration/stable/1.0/appconfiguration.json#L372-L378
detailed log from https://github.com/hashicorp/terraform-provider-azurerm/issues/21939
The PUT request:
200 OK
X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
X-Ms-Request-Id: ee4c4537-3097-4cc9-9c06-79b0fd945fc1
2023-05-13T07:36:22.8165342Z 2023-05-13T07:36:22.144Z [DEBUG] provider.terraform-provider-azurerm_v3.56.0_x5: AzureRM Request:
2023-05-13T07:36:22.8168672Z PUT /kv/keyvault.access.policy.update.complete?api-version=1.0&label=aaaa-000 HTTP/1.1
2023-05-13T07:36:22.8171436Z Host: my-appcs-name.azconfig.io
2023-05-13T07:36:22.8175050Z User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 tombuildsstuff/kermit/v0.20230424.1090808 appconfiguration/1.0 HashiCorp Terraform/1.2.1 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev pid-222c6c49-1b0a-5959-a213-6608f9eb8820
2023-05-13T07:36:22.8178312Z Content-Length: 153
2023-05-13T07:36:22.8180210Z Content-Type: application/json; charset=utf-8
2023-05-13T07:36:22.8182486Z X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
2023-05-13T07:36:22.8184679Z Accept-Encoding: gzip
2023-05-13T07:36:22.8185623Z
2023-05-13T07:36:22.8187824Z {"content_type":"","key":"keyvault.access.policy.update.complete","label":"aaaa-000","tags":{},"value":"2023-05-13T07:36:13Z"}: timestamp=2023-05-13T07:36:22.144Z
2023-05-13T07:36:22.8192685Z 2023-05-13T07:36:22.184Z [DEBUG] provider.terraform-provider-azurerm_v3.56.0_x5: AzureRM Response for https://my-appcs-name.azconfig.io/kv/keyvault.access.policy.update.complete?api-version=1.0&label=aaaa-000:
2023-05-13T07:36:22.8196232Z HTTP/2.0 200 OK
2023-05-13T07:36:22.8197947Z Connection: close
2023-05-13T07:36:22.8199876Z Access-Control-Allow-Credentials: true
2023-05-13T07:36:22.8201893Z Access-Control-Allow-Origin: *
2023-05-13T07:36:22.8207509Z Access-Control-Expose-Headers: DNT, X-CustomHeader, Keep-Alive, User-Agent, X-Requested-With, If-Modified-Since, Cache-Control, Content-Type, Authorization, x-ms-client-request-id, x-ms-useragent, x-ms-content-sha256, x-ms-date, host, Accept, Accept-Datetime, Date, If-Match, If-None-Match, Sync-Token, x-ms-return-client-request-id, ETag, Last-Modified, Link, Memento-Datetime, retry-after-ms, x-ms-request-id, x-ms-client-session-id, x-ms-effective-locale, WWW-Authenticate, traceparent, tracestate, Operation-Location, Retry-After
2023-05-13T07:36:22.8213136Z Content-Type: application/vnd.microsoft.appconfig.kv+json; charset=utf-8
2023-05-13T07:36:22.8215555Z Date: Sat, 13 May 2023 07:36:22 GMT
2023-05-13T07:36:22.8217594Z Etag: "hDUh946-LTi2E3ajFPyOC1e4Y7cuDq_kD-RzFUutYZ8"
2023-05-13T07:36:22.8219752Z Last-Modified: Sat, 13 May 2023 07:36:22 GMT
2023-05-13T07:36:22.8221693Z Server: openresty/1.21.4.1
2023-05-13T07:36:22.8223720Z Strict-Transport-Security: max-age=15724800; includeSubDomains
2023-05-13T07:36:22.8226032Z Sync-Token: my-sync-token
2023-05-13T07:36:22.8228405Z X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
2023-05-13T07:36:22.8230800Z X-Ms-Request-Id: ee4c4537-3097-4cc9-9c06-79b0fd945fc1
2023-05-13T07:36:22.8232168Z
2023-05-13T07:36:22.8235114Z {"etag":"hDUh946-LTi2E3ajFPyOC1e4Y7cuDq_kD-RzFUutYZ8","key":"keyvault.access.policy.update.complete","label":"aaaa-000","content_type":"","value":"2023-05-13T07:36:13Z","tags":{},"locked":false,"last_modified":"2023-05-13T07:36:22+00:00"}: timestamp=2023-05-13T07:36:22.184Z

The GET request after the above PUT:
404 Not Found
X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
X-Ms-Request-Id: 43e09eb2-33c7-4cf7-9fa7-edb9fbc6efc2
2023-05-13T07:36:22.8244714Z 2023-05-13T07:36:22.238Z [DEBUG] provider.terraform-provider-azurerm_v3.56.0_x5: AzureRM Request:
2023-05-13T07:36:22.8248037Z GET /kv/keyvault.access.policy.update.complete?api-version=1.0&label=aaaa-000 HTTP/1.1
2023-05-13T07:36:22.8250768Z Host: my-appcs-name.azconfig.io
2023-05-13T07:36:22.8254421Z User-Agent: Go/go1.19.3 (amd64-linux) go-autorest/v14.2.1 tombuildsstuff/kermit/v0.20230424.1090808 appconfiguration/1.0 HashiCorp Terraform/1.2.1 (+https://www.terraform.io) Terraform Plugin SDK/2.10.1 terraform-provider-azurerm/dev pid-222c6c49-1b0a-5959-a213-6608f9eb8820
2023-05-13T07:36:22.8258190Z X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
2023-05-13T07:36:22.8260639Z Accept-Encoding: gzip: timestamp=2023-05-13T07:36:22.238Z
2023-05-13T07:36:22.8264499Z 2023-05-13T07:36:22.325Z [DEBUG] provider.terraform-provider-azurerm_v3.56.0_x5: AzureRM Response for https://my-appcs-name.azconfig.io/kv/keyvault.access.policy.update.complete?api-version=1.0&label=aaaa-000:
2023-05-13T07:36:22.8267778Z HTTP/2.0 404 Not Found
2023-05-13T07:36:22.8269664Z Access-Control-Allow-Credentials: true
2023-05-13T07:36:22.8271828Z Access-Control-Allow-Origin: *
2023-05-13T07:36:22.8278539Z Access-Control-Expose-Headers: DNT, X-CustomHeader, Keep-Alive, User-Agent, X-Requested-With, If-Modified-Since, Cache-Control, Content-Type, Authorization, x-ms-client-request-id, x-ms-useragent, x-ms-content-sha256, x-ms-date, host, Accept, Accept-Datetime, Date, If-Match, If-None-Match, Sync-Token, x-ms-return-client-request-id, ETag, Last-Modified, Link, Memento-Datetime, retry-after-ms, x-ms-request-id, x-ms-client-session-id, x-ms-effective-locale, WWW-Authenticate, traceparent, tracestate, Operation-Location, Retry-After
2023-05-13T07:36:22.8283593Z Date: Sat, 13 May 2023 07:36:22 GMT
2023-05-13T07:36:22.8285704Z Server: openresty/1.21.4.1
2023-05-13T07:36:22.8288192Z Strict-Transport-Security: max-age=15724800; includeSubDomains
2023-05-13T07:36:22.8290840Z Sync-Token: my-sync-token
2023-05-13T07:36:22.8293228Z X-Ms-Correlation-Request-Id: 79482ff0-aa1a-8be3-e0e1-8e9158d88250
2023-05-13T07:36:22.8295648Z X-Ms-Request-Id: 43e09eb2-33c7-4cf7-9fa7-edb9fbc6efc2
2023-05-13T07:36:22.8297907Z Content-Length: 0: timestamp=2023-05-13T07:36:22.325Z

This is by design. Please see more information in the consistency model document:
https://learn.microsoft.com/en-us/azure/azure-app-configuration/rest-api-consistency

Thanks for providing this!

authors: teowa zhenlan

repo: Azure/AppConfiguration


text:
Node.js 12, set-output and save-state is deprecated in Github Actions

Describe the bug
The workflows provided by Azure/AzOps-Accelerator is using actions and functions that is deprecated and will be disabled soon.
More information:

Node.js 12 is deprecated: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
'set-output' and 'save-state' is deprecated: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

As a current user of AzOps I`m not sure how to best handle this. Should we update our own workflows or can we for instance pull updated versions of the workflows provided in AzOps-Accelerator?
Steps to reproduce
Run either of the following workflows in Github Actions:

'AzOps - Pull'
'AzOps - Push'
'AzOps - Validate'

Screenshots

Thank you for raising this. It is certainly on our radar and we will update the starter accelerator pipelines a.s.a.p.
For existing customers, we will add some guidance in our FAQ - but in short, the recommendation will be to update this manually in the pipelines.

authors: daltondhcp ole-bkk

repo: Azure/AzOps


text:
add fusion incident investigation notebook

Created the fusion incident investigation notebook on top of the Incident Investigation notebook, added a few things (all the rest stay the same as original one) to show the key/core context of the fusion incident:

calculated the fused entities on which sentinel built-in fusion incident is created/fused and added column 'IsFusedEntity' to indicating this information (see the screen shot below)

summary of associated incidents created on those entities (with the column "Number of associated incidents", "status of associated incidents" and "classification of associated incidents") (listed in the column "" of other incidents fire on the entity in the current entity (see the screen shot below)

Query all the alerts from SecurityAlert Table fired in last 7 days on the Fused Entities (indicated by the column "IsExpandedAlert") and show them together with the alerts in the incidents

@zbills please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree [company="Microsoft"]

@microsoft-github-policy-service agree company=Microsoft

@microsoft-github-policy-service agree
On Mon, Nov 28, 2022 at 4:06 PM microsoft-github-policy-service[bot] <
@.***> wrote:

@zbills https://github.com/zbills please read the following Contributor
License Agreement(CLA). If you agree with the CLA, please reply with the
following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of
intellectual property rights to my Submissions and I am not making
Submissions in the course of work for my employer.
(when company given) I am making Submissions in the course of work
for my employer (or my employer has intellectual property rights in my
Submissions by contract or applicable law). I have permission from my
employer to make Submissions and enter into this Agreement on behalf of my
employer. By signing below, the defined term “You” includes me and my
employer.

Contributor License Agreement Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the
party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its
affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is
effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable
or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft
and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or
distributing code or other content to any
Project, including but not limited to communication on electronic
mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf
of, the Project for the purpose of
discussing and improving that Project, but excluding communication
that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material
Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement
before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now
or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions
is entirely Your original work.
Should You wish to Submit materials that are not Your original work,
You may Submit them separately
to the Project if You (a) retain all copyright and license information
that was in the materials as You
received them, (b) in the description accompanying Your Submission,
include the phrase “Submission
containing materials of a third party:” followed by the names of the
third party and any licenses or other
restrictions of which You are aware, and (c) follow any other
instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include
Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a
contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your
employer has intellectual
property rights in Your Submission by contract or applicable law, You
must secure permission from Your
employer to make the Submission before signing this Agreement. In that
case, the term “You” in this
Agreement will refer to You and the employer collectively. If You
change employers in the future and
desire to Submit additional Submissions for the new employer, then You
agree to sign a new Agreement
and secure permission from the new employer before Submitting those
Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly
display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all
of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or
the combination of the
Submission with the Project to which it was Submitted to make, have
made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the
Project.
Other Rights Reserved. Each party reserves all rights not
expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without
limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are
legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your
original work (except as You may
have disclosed under Section 3). You represent that You have secured
permission from Your employer to
make the Submission in cases where Your Submission is made in the
course of Your work for Your
employer or Your employer has intellectual property rights in Your
Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You
represent and warrant that You
have the necessary authority to bind the listed employer to the
obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless
You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE
WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED
UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of
any facts or circumstances of which
You later become aware that would make Your representations in this
Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to
Projects and information about
contributions may be maintained indefinitely and disclosed publicly,
including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the
laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal
courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in
which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County,
Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire
agreement between the parties, and
supersedes any and all prior agreements, understandings or
communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may
be assigned by Microsoft.

—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Azure-Sentinel-Notebooks/pull/179#issuecomment-1329904567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APP2UCZZTGROS2SQSQLOWCDWKVCJPANCNFSM6AAAAAASN4LWVI
.
You are receiving this because you were mentioned.Message ID:
@.***>

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

authors: ianhelle petebryan zbills

repo: Azure/Azure-Sentinel-Notebooks


text:
Tools expecting OSSEM schema break due to case convention

Describe the bug
This is really more a request for clarification than an actual bug.
Parsers that are supposed to implement OSSEM schemas are pascal case (not snake case).
Additional context
PRs like #1040 imply that they're implementing OSSEM but are in fact using pascal case variants of OSSEM entities and properties.
Is this intentional (i.e. Microsoft is adopting this variant of OSSEM as its officially supported schema, not OSSEM)?

@YaronFruchtmann  and @Cyb3rWard0g - Can you two respond to this feedback?

Thanks, lukiffer, for your interest and comments.
This is intentional to be consistent with all other LA tables.

Thanks @YaronFruchtmann for confirming. @Cyb3rWard0g is are the OSSEM schemas meant to be fluid in this way? Or would is this variant a different animal with which we should expect direct integration/compatibility with other OSSEM tools?

Hello @lukiffer ! OSSEM schemas were initially created to follow "snake_case". Azure Sentinel is adopting OSSEM schemas, but Azure Sentinel is being consistent with "PascalCase" format already set for other LA tables as mentioned in the previous comment. OSSEM is meant to be "snake_case" by default. We are in conversations to potentially move to "PascalCase" or allow an easy translation with a simple bash or python script. I believe that since everything is YAML, it should be easy to do the conversion programmatically while using OSSEM as code.

@Cyb3rWard0g thanks for the insight. Are these conversations happening in the OSS space? If so could you provide a link?
It just occurred to me that the whole model could be abstracted behind a declarative projection mechanism, not just case. But that could defeat (at least part of) the purpose.
In any case, would love to contribute to the solution regardless of its implementation.

authors: Cyb3rWard0g YaronFruchtmann lukiffer shainw

repo: Azure/Azure-Sentinel


text:
Add TargetAccount field to "Multiple Password resets by User"

I think it would be a good option to add the "TargetAccount" field to the query, in order to see which account the password was tried to change at a glance.
https://github.com/Azure/Azure-Sentinel/blob/master/Detections/MultipleDataSources/MultiplePasswordresetsbyUser.yaml
https://github.com/Azure/Azure-Sentinel/pull/2665

https://github.com/Azure/Azure-Sentinel/pull/2665

Thank you for submitting issue with PR. I have suggested a change, rest looks good. once changes done and PR is merged, this issue should get closed automatically.

authors: ashwin-patil jonyluke


text:
SlackAudit: dataconnector+workbook

Proposed Changes

added SlackAudit data connector
added Workbook for Slack Audit log data

There are merge conflicts on this PR, Please resolve them. Thanks!!!

@shainw : Could you please review Parser, Detection and Hunting Queries Files

@averbn : Can you please resolve merge conflicts and review comments.
Thanks!!

authors: averbn v-rucdu


text:
CRash when Binding Volumes

Describe the bug
I have tried to deploy the module on iot edge, from marketplace, bu adding a volume binding to where my publishnodes.json is. Edge Agent fails to start the module. See error log at https://pastebin.com/nXYZDZ72
To Reproduce
Steps to reproduce the behavior:

create a folder on the edge device and add a valid publishnodes.json file
get the module from market place, edit container create options to bind the folder where publishnodes.json is
publish
See error

Hi, could you also provide the create options you specified during deployment?  Thanks!

authors: lucarv marcschier

repo: Azure/Industrial-IoT