text:
Move the mutation rate from class to algorithm.

If there was a specific reason for having the mutation rate in the
params class
let me know but I've moved it to better reflect that it's a property of
the algorithm. This is more in line with the fact that the
representation we write to file does not hold the mutation rate for
example.
This doesn't stop having algorithms that would have different
mutation rates for different parameter instances (it's just that the
algorithm would have to keep track of it).

Looks great, just one comment.
In utils.py should the method mutate change to mutate(self, mutation_rate) in class Params?

Thanks @Nikoleta-v3, good catch have fixed.

This doesn't stop having algorithms that would have different
mutation rates for different parameter instances (it's just that the
algorithm would have to keep track of it).

That was the point and this seemed like the easiest way to do it -- how would we do it now? With a map of  instances to mutation rates?

That's the kind of thing I was thinking (it would need to keep track of what to do with births/deaths). How do you feel about having it as I've done it here and when/if we write an algorithm with different mutation rates, if a mapping type thing in the algorithm class doesn't do the trick then we cross that bridge?

I might have a better idea (out walking, will do when I get back👍).

I might have a better idea (out walking, will do when I get back).

No my "better idea" doesn't feel right: I tried to have def mutate(self) but adding a def receive_mutation_rate(self, mutation_rate) that the algorithm would use but that feels like extra complications than necessary. I would suggest that when/if we algorithms with heterogeneous mutation rate we let the algorithm take care of it and simply use def mutate(self, mutation_rate).
Another question:
88         if random.random() < self.mutation_rate / 10:

I've only just noticed the /10 there! Is there any reason for that? (unless I'm missing something trivial we need to remember to modify the values reported in the manuscripts).

I've removed the /10 in fc5ef4b.

Also: any objection to renaming mutation_rate -> mutation_probability?

Also: any objection to renaming mutation_rate -> mutation_probability?

Sure.

How do you feel about having it as I've done it here and when/if we write an algorithm with different mutation rates, if a mapping type thing in the algorithm class doesn't do the trick then we cross that bridge?

For the speciation use case we discussed elsewhere my plan was to use the params as representations of the individuals and possibly allow the mutation rate to vary (to find the mutation-selection equilibrium, for example). So if we're going to move this inside the algorithm then I'd like to make sure we can handle that case. Otherwise I'd prefer to leave it as is and fix the non-logging of the mutation rate. We can also fix the logging in general -- the way I initially did it was quick and dirty, it would be better to write a dictionary, JSON, or something less ad hoc.
On the conceptual side, while I can certainly see why it seems better to have the mutation rate as a property of the evolutionary algorithm, I can think of cases in biological evolution where the mutation rate can vary for individuals of the same population, or between related species. I recall experimenting with a decaying mutation rate for the neural network strategy (since many training algorithms have the learning rate decrease over time), but I can't recall that it made a substantial difference.

For the speciation use case we discussed elsewhere my plan was to use the params as representations of the individuals and possibly allow the mutation rate to vary (to find the mutation-selection equilibrium, for example). So if we're going to move this inside the algorithm then I'd like to make sure we can handle that case.

I think my latest attempt ensures this can be handled now. The change is pretty minimilistic now:

Change the argument passed from the algorithm to the instance to kwargs (as opposed to the args tuple) - this is just to make things a bit more robust going forward.
The algorithm is passed a mutation rate and it passes this to the kwargs
The algorithm just calls instance.mutate() as before

Let me know what you think :)

Is this is going to break the other trainers? The name change to mutation_probability and args -> kwargs ...
This is better. Can we add a check so that if the agent params have mutation_probability then it's not overwritten, otherwise the algorithm will supply its "global" value? Then I think we're covered in all cases. Plus we can still just write the agent params dictionary to disk and they'll be correct in all cases.

Can we add a check so that if the agent params have mutation_probability then it's not overwritten, otherwise the algorithm will supply its "global" value? Then I think we're covered in all cases. Plus we can still just write the agent params dictionary to disk and they'll be correct in all cases.

Good shout will make that change.
I'll fix the other scripts. Perhaps we should/could remove them all together from here? As they're not tested any change etc becomes a bit of a pain.

I believe b0e321b catches everything but let me know if not. (If you're happy could you squash and merge just to keep the history tidy and make the changelog super simple :+1:)

Perhaps we should/could remove them all together from here? As they're not tested any change etc becomes a bit of a pain.

(Obviously we shouldn't do this until we've written the other parameter classes in to the library itself, so no rush at all with that call. Once we've moved them in to the library and they're all tested perhaps removing the scripts because of testing concerns won't be relevant.)

authors: Nikoleta-v3 drvinceknight marcharper

repo: Axelrod-Python/axelrod-dojo


text:
A variety of edits for the paper

Some suggestions:
The point of figure 6 needs to be more clear. At a glance the figure seems to say that our results don't match theory, which is not the case.
We should use a different color for dotted neutral lines in the boxplot charts
Move figure 14 to start of invasion section and figure 16 to start of resistance section. These give the most information and are the most interesting IMO. If the paper were nothing but two diagrams summarizing the results I would want it to be these two.
Fig 14-16: grid lines make some strategies hard to see -- perhaps an all white background is better.
Can tables 3 and 4 be simplified? There is a lot of redundant information. Perhaps a separate table listing the memory depth and stochasticity of all strategies mentioned in the paper would be a good idea. However I understand the desire to point out that the strategies are not complex.
Table 5: We should insert lines between the good invaders, good resistors, and good ZD strategies.
We may have taken the third-person approach a little too far:
"In this section the focus is on the ability of a mutant strategy to invade" might be better as "We now focus on the ability of a mutant to invade".
The size of the tables of invasion and fixation are hiding something about TF*. True they are not in the top 5 invaders but they are 7, 9, and 14 for N=2 and TF3 is rank 16 for N=14 (top 10%). They are also all near the top for resistance for and N/2. Other than CS and Evolved LookerUp 1_1_1 no other strategy is very good at both consistently, so by training at a starting state of (N/2, N/2) we got good invaders and great resistors. I recommend that we extend the top 5 tables to give a better picture.
On that topic I added a discussion section that argues that we can't really do better unless players know the population distribution (or you had a tag with the opponent's type). Let me know if that section doesn't make sense. I convinced myself it does...
WinStayLoseShift should be abbreviated WSLS.

We may have taken the third-person approach a little too far:
"In this section the focus is on the ability of a mutant strategy to invade" might be better as "We now focus on the ability of a mutant to invade".

I'd stick with the first if this was only me but that's purely based on a really painful review a while back (ridiculous back and forth that escalated over this petty stuff) after which I just decided to stick with third person. I also find when working collaboratively it helps because it avoids confusion between we, I etc... I'm easy if we want to change though (if we happen to get a silly reviewer it's an easy enough thing to change back). I pointed out some "We"s in your changes just in case we do go with third person.

On that topic I added a discussion section that argues that we can't really do better unless players know the population distribution (or you had a tag with the opponent's type). Let me know if that section doesn't make sense. I convinced myself it does...

It made sense to me. :+1: I thought the discussion section was great actually.

The point of figure 6 needs to be more clear. At a glance the figure seems to say that our results don't match theory, which is not the case.

Can you expand on this a bit? My understanding was that figure 6 shows the shortcoming of the theory which is based on a particular theoretic result based on the average payoff.

It's a shortcoming of using average payoff to compute the transition probabilities. We could compute the transition probabilities directly, in which case the formula that uses only the transition probabilities would be correct. Given the transition probabilities the fixation probability (in the two type case) can be computed exactly.
The issue is that it is difficult to come up with a formula for an arbitrary strategy because the fitness landscape is difficult to compute for strategies with memory depth > 1, for arbitrary match lengths, etc. The formula doesn't apply to repeated games (rather it's for one-shot games), that's why previous authors used the stationary score -- it reduces a match to a single score if the stationary distribution can be computed (and there are infinitely many rounds).

The issue is that it is difficult to come up with a formula for an arbitrary strategy because the fitness landscape is difficult to compute for strategies with memory depth > 1, for arbitrary match lengths, etc. The formula doesn't apply to repeated games (rather it's for one-shot games), that's why previous authors used the stationary score -- it reduces a match to a single score if the stationary distribution can be computed (and there are infinitely many rounds).

That makes sense, I'll open a PR with a suggested edit around that but feel free to just ignore it and write what you feel is best. :+1:

https://github.com/Axelrod-Python/axelrod-moran/pull/37

Have opened #38 which resizes the boxplots to fit on a single page, this looks good for the multiple ones for invasion and resistance but a tiny bit funky for the lonely plot for N=2 (but I still think it's an improvement over status quo).

https://github.com/Axelrod-Python/axelrod-moran/pull/39 adds a bit more discussion around the longer tables, interestingly for the reistors even within the top 16 strategies: none of them are stochastic.

source: gharchive/pull-request

authors: drvinceknight marcharper

repo: Axelrod-Python/axelrod-moran

license: mit

license_type: permissive

license_source: bigquery


text:
Triggers component change every check

Hi there,
Everytime the script runs (*/5) it updates the status of the component to Operational, which triggers an email alert to subscribers. Is there anyway to avoid that?
Essentially, I want to check the uptimerobot status and if down change to down and trigger the email then. Each time is OK I don't need to know....

I don't know how to do that, if you find a way feel free to send a PR or update this issue. Thanks.

source: gharchive/issue

repo: Axiacore/cachet-uptime-robot

license: MIT

license_source: github-api


text:
IllegalMonitorStateException

java.lang.IllegalMonitorStateException: null
at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) ~[na:1.8.0_91]
at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) ~[na:1.8.0_91]
at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) ~[na:1.8.0_91]
at org.axonframework.common.lock.PessimisticLockFactory$DisposableLock.release(PessimisticLockFactory.java:122) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.model.LockingRepository.lambda$doLoad$3(LockingRepository.java:140) ~[axon-core-3.0.jar:3.0]
at org.axonframework.messaging.unitofwork.MessageProcessingContext.notifyHandlers(MessageProcessingContext.java:68) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.disruptor.DisruptorUnitOfWork.notifyHandlers(DisruptorUnitOfWork.java:89) ~[axon-core-3.0.jar:3.0]
at org.axonframework.messaging.unitofwork.AbstractUnitOfWork.changePhase(AbstractUnitOfWork.java:214) ~[axon-core-3.0.jar:3.0]
at org.axonframework.messaging.unitofwork.AbstractUnitOfWork.commitAsRoot(AbstractUnitOfWork.java:93) ~[axon-core-3.0.jar:3.0]
at org.axonframework.messaging.unitofwork.AbstractUnitOfWork.commit(AbstractUnitOfWork.java:71) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.disruptor.EventPublisher.performCommit(EventPublisher.java:146) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.disruptor.EventPublisher.processPublication(EventPublisher.java:109) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.disruptor.EventPublisher.onEvent(EventPublisher.java:78) ~[axon-core-3.0.jar:3.0]
at org.axonframework.commandhandling.disruptor.EventPublisher.onEvent(EventPublisher.java:40) ~[axon-core-3.0.jar:3.0]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129) ~[disruptor-3.3.6.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]

Could you share a bit of context? What does your configuration look like?

`public class AxonDistributedConfig {
@PersistenceUnit
private EntityManagerFactory entityManagerFactory;

@Autowired
private SpringTransactionManager springTransactionManager;

@Autowired
private EventStore eventStore;

@Bean
public Serializer serializer() {
    return new XStreamSerializer();
}

@Bean
public JGroupsConnectorFactoryBean jGroupsConnectorFactoryBean() throws Exception {
    DisruptorCommandBus localSegment = new DisruptorCommandBus(eventStore);
    JGroupsConnectorFactoryBean jGroupsConnectorFactoryBean = new JGroupsConnectorFactoryBean();
    jGroupsConnectorFactoryBean.setLocalSegment(localSegment);
    return jGroupsConnectorFactoryBean;
}

@Bean
public CommandBus distributedCommandBus() throws Exception {
    JGroupsConnector jGroupsConnector = jGroupsConnectorFactoryBean().getObject();
    return new DistributedCommandBus(jGroupsConnector, jGroupsConnector);
}

@Bean
public EventStorageEngine eventStorageEngine() throws Exception {
    return new JpaEventStorageEngine(entityManagerProvider());
}

@Bean
public EntityManagerProvider entityManagerProvider() {
    return new ContainerManagedEntityManagerProvider();
}

@Bean
public SpringTransactionManager springTransactionManager() throws Exception {
    return new SpringTransactionManager(transactionManager());
}

@Bean
public PlatformTransactionManager transactionManager() throws PropertyVetoException {
    return new JpaTransactionManager(entityManagerFactory);
}

@Bean
public TransactionManagerFactoryBean transactionManagerFactoryBean() throws PropertyVetoException {
    TransactionManagerFactoryBean factoryBean = new TransactionManagerFactoryBean();
    factoryBean.setTransactionManager(transactionManager());
    return factoryBean;
}

@Bean
public SagaStore<Object> jpaSagaStore() {
    return new JpaSagaStore(entityManagerProvider());
}

}`

When using the DisruptorCommandBus, you can't use regular repositories. I didn't see any Repositories be explicitly declared (might be in another context file) in the given configuration, but they're probably EventSourcingRepository instances.
Instead, you should use the DisruptorCommandBus.createRepository() method. The reason is that the DisruptorCommandBus uses 2 threads to execute part of the command processing logic each (invocation vs publication of changes). The locking strategy of the EventSourcingRepository isn't capable of dealing with that.

Thank you, configuration context error

authors: abuijze codehappy

repo: AxonFramework/AxonFramework


text:
crashes my server

So I'm coding a server with my friend and lately the wand addon has crashed the server. We've tried to re-code some of the lua files but we haven't made any progress. It usually happens when people stand right next to each other. If you have any tips to fix this issue, please answer because I love this addon.
thank you.
// Zac

any other observations?

authors: Ayditor xReelox


text:
Refreshing API Token through Terraform login fails if current token is expired

Bug description 🐞
When you use Terraform Login to generate a Token to authenticate you machine against Terrakube this works fine. The token depending on your Dex configuration will have a certain lifespan (by default 24H) .
The thing next I am not sure if this a Terrakube of Terraform CLI issue is that when this token has reached it's time limit will have expired and you can't authenticate against Terrakube. This is expected behaviour, however when you want to recreate a token through Terraform Login you will receive a error 401 Unauthorized. Although it seems reasonable since the token is expired the other thought is that you are able to authenticate when you do not have a token. So I would think there is some mechanism to allow renewal of a existing token. I do not have any other environment to which I can compare this to.
If this is default Terraform CLI behaviour feel free to close this bug 😄
│ Error: Service discovery failed for terrakube.xx.xxxxx.xx
│
│ failed to request discovery document: 401 Unauthorized.

Steps to reproduce
Run Terraform Login
Let the token Expire ( wait 24 with default configuration )
Run Terraform Login again a error will show
Expected behavior
I would expect that although the current token is expired you would be able to retreive a new token if you are able to authenticate against Terrakube. So a login flow should be started.
Example repository
No response
Anything else?
Workaround ofcourse is using self generated API Tokens from the Terrakube UI or API directly in this file instead of using terraform login.

Hello @iam-take
When you run terraform login the terraform cli send a request  with an empty bearer token to this endpoint https://terrakube-api.minikube.net/.well-known/terraform.json because it didn't find any token in your credentials.tfrc.json. This endpoint is public and does not have any authorization in spring security
Once you have a token in your credentials.tfrc.json the terraform cli take the expired token from credentials.tfrc.json and send the same request with the bearer token to https://terrakube-api.minikube.net/.well-known/terraform.json where spring security take the token and check if the token is valid even if the endpoint does not require any kind of authorization and that is the reason you see the HTTP 401 error.
I tried to fixed this a long time ago but I was not able to find a way to change that behavior spring security configuration and as you mentioned the workaround is to use a PAT or simple delete the token from your  credentials.tfrc.json.
We can leave this issue open and maybe in the future we can find a way to fix it, for now this issue can be used as a reference for someone else having the same problem.

repo: AzBuilder/terrakube


text:
Add Support for linux/arm64/v8 Architecture in aztecprotocol/aztec Docker Image

While following the Aztec guide to install the aztec toolchain using the aztec-install script, I encountered the following error:
latest: Pulling from aztecprotocol/aztec
no matching manifest for linux/arm64/v8 in the manifest list entries

I’m using a MacBook Pro with an M3 Pro chip running macOS 15.2 (arm64). After checking the available Docker Hub tags for the aztecprotocol/aztec package, I noticed there wasn’t a matching version for the aarm64 architecture.
To work around this issue, I modified the script to explicitly specify the platform using:
docker pull --platform linux/arm64 aztecprotocol/aztec

This allowed me to proceed, but this approach isn’t ideal because it forces emulation of the execution environment, which may introduce performance or compatibility issues. A better solution would be to publish the required tags for native arm64 support on Docker Hub.
Let me know if you need any additional information!

having the same issue, particularly in versions >=0.68.0

Hey @varex83
It works on M* Macs. There was an issue with Mac builds in the last release which is why you see that error. This will be fixed in the next release.
In the meantime, can you try installing slightly older version VERSION=0.68.0 aztec-up

repo: AztecProtocol/aztec-packages


text:
aztec test doesn't produce the same result as the TypeScript testing environment

Overview
I have a very simple contract that sets and gets the value of a field of the storage of Main contract. I have a pure Noir test that aims to set and retrieve this field's number. The contract compiles successfully but when executing aztec test the assertion fails with the error:
Failed assertion

error: Assertion failed: Expected 0x1f but got 0x00
   ┌─ src/main.nr:36:13
   │
36 │             get_expectedd_field == target_value, f"Expected {target_value} but got {get_expectedd_field}"
   │             -----------------------------------
   │
   = Call stack:
     1. src/main.nr:36:13

It indicates that the number that's written to the storage of the contract is 0, instead of 31. Even aztec test --show-output prints 0x00 for the output value.
The contract and Noir test
contract Main {
    use dep::aztec::prelude::PublicMutable;

    #[aztec(storage)]
    struct Storage {
        test_field: PublicMutable<Field>,
    }

    #[aztec(public)]
    fn setField(input: Field) {
        storage.test_field.write(input);
    }

    unconstrained fn getField() -> pub Field {
        storage.test_field.read()
    }

    use dep::aztec::test::helpers::test_environment::TestEnvironment;

    #[test]
    fn test_set_get_field() {
        // Setup env
        let mut env = TestEnvironment::new();

        // Deploy contract and initialize
        let counter_contract = env.deploy_self("Main").without_initializer();
        let contract_address = counter_contract.to_address();

        env.impersonate(contract_address);

        let target_value = 31;

        let _ = Main::at(contract_address).setField(target_value);
        let get_expectedd_field = getField();
        assert(
            get_expectedd_field == target_value, f"Expected {target_value} but got {get_expectedd_field}"
        );
    }
}

PoC
I've created typescript test that mimics the same Noir test. This test retrieves 31 as it should.
    test.only("if sets and gets 31", async () => {
        let value = 31;
        const contract = await MainContract
            .deploy(wallets[0])
            .send()
            .deployed();

        await contract.methods.setField(value).send().wait();
        const field = await contract.methods.getField().simulate();
        console.log('expected field is: ', field);
        console.log('target value are: ', value);
    }, 30000);

The issue
The pure Noir tests and the testing environment as a whole doesn't produce the same result as the typescript testing environment for given Noir smart contract program.

I think the issue is that you need to send the call to the private function in the test, using
env.call_private_void(call_interface);

See this section of the docs for reference.

I believe you need to read public state differently as well. See this section: https://docs.aztec.network/guides/developer_guides/smart_contracts/testing_contracts/testing#checking-state


text:
chore: All pedersen compress_native methods now return a grumpkin::fq

Depends on #2955
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

This is not blocked by #2592 and should go in after it has been merged

Closing as this has now been included in the mega PR


text:
fix: increase default number of proving agents

Increase default number of proving agents from 1 to 8 to speed up nodes.

#6146  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @alexghr and the rest of your teammates on  Graphite

Merge activity

May 3, 5:11 AM EDT: @alexghr merged this pull request with Graphite.


text:
feat: Sync from noir

Automated pull of development from the noir programming language, a dependency of Aztec.
BEGIN_COMMIT_OVERRIDE
fix: Implement generic functions in the interpreter (https://github.com/noir-lang/noir/pull/5330)
feat: Insert trait impls into the program from type annotations (https://github.com/noir-lang/noir/pull/5327)
feat: Sync from aztec-packages (https://github.com/noir-lang/noir/pull/5340)
chore: address TODO in compat.nr (https://github.com/noir-lang/noir/pull/5339)
chore: use push_err more in elaborator (https://github.com/noir-lang/noir/pull/5336)
chore: remove is_unconstrained_fn field from elaborator (https://github.com/noir-lang/noir/pull/5335)
fix: Error when a local function is called in a comptime context (https://github.com/noir-lang/noir/pull/5334)
feat: Add map, fold, reduce, any, and all for slices (https://github.com/noir-lang/noir/pull/5331)
fix: Avoid panic in type system (https://github.com/noir-lang/noir/pull/5332)
chore: remove panic for unimplemented trait dispatch (https://github.com/noir-lang/noir/pull/5329)
feat: Use runtime loops for brillig array initialization (https://github.com/noir-lang/noir/pull/5243)
fix: Fix tokenization of unquoted types in macros (https://github.com/noir-lang/noir/pull/5326)
chore: replace cached in_contract with in_contract() method (https://github.com/noir-lang/noir/pull/5324)
fix: fix usage of #[abi(tag)] attribute with elaborator (https://github.com/noir-lang/noir/pull/5298)
fix: don't benchmark the "prove" command as it doesn't exist anymore (https://github.com/noir-lang/noir/pull/5323)
feat(stdlib): Update stdlib to use explicit numeric generics (https://github.com/noir-lang/noir/pull/5306)
feat: let should_fail_with check that the failure reason contains the expected message (https://github.com/noir-lang/noir/pull/5319)
chore: bump bb to 0.43.0 (https://github.com/noir-lang/noir/pull/5321)
feat(frontend): Explicit numeric generics and type kinds (https://github.com/noir-lang/noir/pull/5155)
feat(frontend): Where clause on impl (https://github.com/noir-lang/noir/pull/5320)
END_COMMIT_OVERRIDE

@vezenovm We're also getting errors on where clauses related to the NoteInterface trait which looks like it could stem from your PR.

For reference, this is the error

For reference, this is the error

I know what is happening I will investigate the fix. I may end up just switching them over to explicit numeric generics.

Thanks!

Thanks! Would be good to pull a regression test over to the main repo as part of this.

I was struggling to reproduce a small example. I think the order of resolution across crates matters in this bug which complicates things. The bug was exclusive to the legacy resolver as well so I just fixed it here.

Benchmark results
Metrics with a significant change:

protocol_circuit_simulation_time_in_ms (public-kernel-setup): 636 (-19%)
avm_simulation_time_ms (GasToken:_increase_public_balance): 66.8 (-41%)
avm_simulation_time_ms (Token:mint_public): 70.6 (-89%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 209 (+124%)

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.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_30_ms
11,507
3,191 (+3%)
1,390 (-5%)
1,427 (-15%)
1,462 (-5%)

proof_construction_time_sha256_100_ms
44,304
11,869
5,462
5,389
5,369

proof_construction_time_poseidon_hash_ms
79.0
34.0
34.0
58.0
87.0

proof_construction_time_poseidon_hash_30_ms
1,534
419
201
222 (-1%)
268 (+2%)

proof_construction_time_poseidon_hash_100_ms
5,814
1,582
724
771 (-2%)
798

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,464
9,462
9,464

l1_rollup_execution_gas
610,285
610,283
610,285

l2_block_processing_time_in_ms
760 (-1%)
1,427
2,715

l2_block_building_time_in_ms
24,567 (-4%)
49,792 (-3%)
96,095 (-4%)

l2_block_rollup_simulation_time_in_ms
24,567 (-4%)
49,791 (-3%)
96,095 (-4%)

l2_block_public_tx_process_time_in_ms
21,114 (-4%)
46,099 (-3%)
92,498 (-4%)

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

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,077
9,999

node_database_size_in_bytes
12,177,488
16,035,920

pxe_database_size_in_bytes
16,254
26,813

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

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
proving_time_in_ms
input_size_in_bytes
output_size_in_bytes
proof_size_in_bytes
num_public_inputs
size_in_gates

private-kernel-init
116 (-5%)
455 (-2%)
12,823 (-4%)
20,634
67,190
92,352
2,819
524,288

private-kernel-inner
359 (-7%)
1,109 (+15%)
48,204 (-8%)
94,902
67,190
92,352
2,819
2,097,152

private-kernel-tail
301 (-5%)
1,720 (-2%)
50,287 (-6%)
99,121
71,733
14,912
399
2,097,152

base-parity
6.40 (-3%)
1,825 (-5%)
2,755 (-1%)
128
64.0
2,208
2.00
131,072

root-parity
49.1 (-5%)
70.1 (-7%)
40,299 (-1%)
27,100
64.0
2,720
18.0
2,097,152

base-rollup
7,734 (-3%)
4,941
83,965 (-5%)
170,330
756
3,648
47.0
4,194,304

root-rollup
110
96.7 (+7%)
22,500 (-8%)
25,309
620
3,456
41.0
1,048,576

public-kernel-setup
:warning: 636 (-19%)
3,699 (-2%)
45,825 (-1%)
116,905
93,334
125,344
3,850
2,097,152

public-kernel-app-logic
586 (-8%)
4,745
45,354 (-2%)
116,905
93,334
125,344
3,850
2,097,152

public-kernel-tail
1,389 (-1%)
39,462 (+7%)
191,617 (-1%)
511,910
10,014
14,912
399
8,388,608

private-kernel-reset-small
553 (-2%)
1,921 (-10%)
45,818 (-4%)
123,313
67,190
92,352
2,819
2,097,152

public-kernel-teardown
580 (-9%)
4,762
46,527 (+2%)
116,905
93,334
125,344
3,850
2,097,152

merge-rollup
29.0
N/A
N/A
16,542
756
N/A
N/A
N/A

private-kernel-tail-to-public
N/A
7,828 (+8%)
98,923 (-3%)
N/A
N/A
125,344
3,850
4,194,304

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms
proof_size_in_bytes
proving_time_in_ms
size_in_gates
num_public_inputs

ContractClassRegisterer:register
1,344
9,944
409 (-4%)
N/A
N/A
N/A
N/A

ContractInstanceDeployer:deploy
1,408
9,944
39.6 (-2%)
N/A
N/A
N/A
N/A

MultiCallEntrypoint:entrypoint
1,920
9,944
1,762 (-2%)
N/A
N/A
N/A
N/A

GasToken:deploy
1,376
9,944
957 (-4%)
N/A
N/A
N/A
N/A

SchnorrAccount:constructor
1,312
9,944
1,407
N/A
N/A
N/A
N/A

SchnorrAccount:entrypoint
2,304
9,944
2,799 (-3%)
16,768
54,233 (-5%)
2,097,152
457

Token:privately_mint_private_note
1,280
9,944
1,614 (-13%)
N/A
N/A
N/A
N/A

FPC:fee_entrypoint_public
1,344
9,944
351 (-4%)
16,768
11,891 (+3%)
524,288
457

Token:transfer
1,312
9,944
4,458 (-10%)
16,768
48,100 (-1%)
2,097,152
457

AuthRegistry:set_authorized (avm)
21,043
N/A
N/A
87,552
1,389
N/A
N/A

FPC:prepare_fee (avm)
28,484
N/A
N/A
88,448
5,842 (+2%)
N/A
N/A

Token:transfer_public (avm)
44,885
N/A
N/A
88,170
3,881 (-5%)
N/A
N/A

AuthRegistry:consume (avm)
34,973
N/A
N/A
87,968
2,876 (-6%)
N/A
N/A

FPC:pay_refund (avm)
38,649 (-7%)
N/A
N/A
89,248
23,011 (-2%)
N/A
N/A

Benchmarking:create_note
1,344
9,944
1,394
N/A
N/A
N/A
N/A

SchnorrAccount:verify_private_authwit
1,280
9,944
72.6 (-1%)
N/A
N/A
N/A
N/A

Token:unshield
1,376
9,944
3,708 (-13%)
N/A
N/A
N/A
N/A

FPC:fee_entrypoint_private
1,376
9,944
4,609 (-15%)
N/A
N/A
N/A
N/A

AVM Simulation
Time to simulate various public functions in the AVM.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
:warning: 66.8 (-41%)
13,873

GasToken:set_portal
19.6 (+11%)
3,495

Token:constructor
81.6 (-11%)
24,207

FPC:constructor
62.7 (-3%)
13,893

GasToken:mint_public
52.1 (-2%)
10,241

Token:mint_public
:warning: 70.6 (-89%)
19,216

Token:assert_minter_and_mint
:warning: 209 (+124%)
13,034

AuthRegistry:set_authorized
31.2 (-11%)
7,869

FPC:prepare_fee
183 (+12%)
15,118

Token:transfer_public
31.8 (-5%)
31,425

FPC:pay_refund
163 (-26%)
25,316 (-10%)

Benchmarking:increment_balance
2,616 (-4%)
15,396

Token:_increase_public_balance
62.5 (-11%)
15,089

FPC:pay_refund_with_shielded_rebate
199 (+1%)
26,403 (-9%)

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.158 (-2%)

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
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.601
0.516
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.7
76.7
132 (+1%)
248 (+1%)
474

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.497
0.471 (+1%)
0.454 (+1%)
0.448 (+1%)
0.443 (+1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.9
113
184 (+1%)
356
697

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.506
0.504
0.487 (+1%)
0.481
0.478

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
73.1
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.520
N/A
N/A
N/A
N/A

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
85,672
670,983

Transaction size based on fee payment method
| Metric |  |
| - |  |

authors: AztecBot TomAFrench vezenovm


text:
Read placeholder size from graph

Purpose
Fixed issue #39 - the Custom Vision exported model has a changed input size. According to other samples it is now expected that the input size is read from the graph rather than hardcoded at 227.

...

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:

How to Test

Get the code

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

Test the code
Train and export new custom vision model. Previously would not work, now does.

What to Check
Verify that the following are valid

...

Other Information

Used the pattern described in the official sample


text:
Going to /UserProfile after signing-in causes error

After signing-in into a local account, navigating to https://localhost:44323/UserProfile produces this error:
Server Error in '/' Application.`
Invalid object name 'dbo.TokenCacheEntries'.
...
Line 24:
Line 25:             // look up the entry in the DB
Line 26:             Cache = db.TokenCacheEntries.FirstOrDefault(c => c.userObjId == userObjId);
Line 27:             // place the entry in memory
Line 28:             this.Deserialize((Cache == null) ? null : Cache.cacheBits);
--
Source File: C:\Users\...\Documents\Visual Studio 2017\Projects\adal-graph\WebApp\Models\TokenDbCache.cs    Line: 26

Looks like your database does not have the TokenCacheEntries table...

Looks like I figured it out by taking hints from this similar issue: https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-oauth2-useridentity/issues/4
I should point out that I'm using Visual Studio 2017, in case it affects anything.
Steps taken:

Downloaded sample project, and opened it in VS 2017
Followed Step 2: Register the sample with your Azure Active Directory tenant and Step 3: Configure the sample to use your Azure AD tenant with the only difference being I named my app differently
In the Azure AD App Settings area, in the Reply URLs I added https://localhost:44323/OAuth

Without this I got an error when signing into my AAD account on the /UserProfile page
This step is not (at the time of writing this) mentioned in the walkthrough steps.

In the project, in Package Manager Console I restored the missing references
Again in the Package Manager Console I type:
Enable-Migrations
Add-Migration initial-migration
Update-Database

This was needed to create the TokenCacheEntries table

I'm now able to run the app, register as a local user, proceed to navigate to the User Profile page, and sign into AAD.

The sample has been rewritten completely, please give it a try again let us know if you still face an issue

It's been a whole, so I'm guessing the original page is this one: https://azure.microsoft.com/en-us/resources/samples/active-directory-dotnet-webapp-webapi-oauth2-useridentity/
I'm using Visual Studio Professional 2017 v15.9.6, I use Firefox 64-bit v65.0 as my browser to launch this in.

A link near the start of Step 2 leading to "App Creation Scripts" is broken: https://azure.microsoft.com/en-us/resources/samples/active-directory-dotnet-webapp-webapi-oauth2-useridentity/appcreationscripts/appcreationscripts.md

In the "Register the service app (OAuth2-UserIdentity)" section, in step 2, it asks us to enter two URLs but there is only one box (doesn't seem to be a combo box as described) with no description of how to add more:

2.a Looks like I can add more once I'm on the Authentication page during Step 5 of the same section, so I would suggest moving this part of Step 2 into Step 5

There is a space missing between "flow" and "to" in this sentence: "the Implicit grant flowto be enabled"

In "Configure the service project" it might help to clarify that "AppKey" is the same as the secret generated earlier, and that you can get the Tenant Id from the Overview page of the App Registration.

Able to clean and rebuild the app with no errors, but once loaded it sends me to an error page saying "Server Error in '/' Application.
Could not find a part of the path 'C:\removed\Desktop\ADOauth2Test\active-directory-dotnet-webapp-webapi-oauth2-useridentity\OAuth2-UserIdentity\bin\roslyn\csc.exe'. ":

That's as far as I've gotten.

Thanks for taking the time to review this. To get rid of the roslyn error
Could not find a part of the path … bin\roslyn\csc.exe
Please open the Nuget package manage window (View->Other windows->Package Manager Console
and execute the following command
Uninstall-package Microsoft.CodeDom.Providers.DotNetCompilerPlatform
We're incorporating the rest of your suggestions as well

Uninstalling that package did the trick and I'm now able to move forward with the tutorial:

In the Create and publish the OAuth2-UserIdentity to an Azure Web Site section:

Step 2, it asks me to click Web + Mobile --> Web App, currently there is no Web + Mobile option. There is both Web and Mobile though, as separate choices:

Clicking on Web will get you to the Web App option

Step 3, it asks to click "Create a new database", looks like the wording has changed to Add. Similar for DB Connection String Name, changed to Database name
Step 7, "Settings" has changed to "Configure"

In the Update the Active Directory tenant application registration for OAuth2-UserIdentity section:

Step 2, not positive but I think the "Directory list" has been moved behind the "Switch directory" link
Step 3, I think the "applications tab" has been changed to "App Services"
Step 4, unsure where the Settings page is for my Application in Azure since the Settings section -> Application settings does not contain a way for me to change my logout URL

Looks like this is supposed to be in Azure Active Directory -> App registrations (Preview) (Normal doesn't show my app at all) -> Click on my app -> Under Manage click Authentication
It's here I'm able to update the Logout URL

Step 5, following the Step 4 changes move from Authentication to Branding and add the Home page URL
Step 6, move back to the Authentication and add the URL to the Redirect URIs (changed from "Reply URLs", though still referenced as such in the manifest as replyUrlsWithType)

After doing all this I go and test the app following the same steps listed in Step 4: Run the sample, but I just get the generic An error occurred while processing your request. message when loading any page that makes a call to the database (Submitting a registration, logging in)
I think this is because of some missteps around Section Create and publish the OAuth2-UserIdentity to an Azure Web Site Step 3.
Pretty sure the intended result is to update the Connection String in the App Service page -> Settings section -> Application Settings (Configuration (Preview) looks to be replacing this in the future) -> Connection Strings section -> Add new Connection String with a name of DefaultConnection (instead of actually naming the Database DefaultConnection) and a value of the SQL Database created for this tutorial with the username and password edited in.

@kalyankrishna1 : may I let you handle this one?

yes, PR with fixes out for review

The steps to deploy on Azure has been updated again. Thanks for your patience.

Closing this as the user hasn't responded

authors: RyanTaite gsacavdm jmprieur kalyankrishna1


text:
Fix launch.json .net7.0

Purpose

After the latest commit, it's not possible to launch the sample as before. I've updated the launch.json file to target the new dll location

Does this introduce a breaking change?
[x] Yes
[ ] 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:
How to Test

Get the code
Launch the task in vscode

Thanks @jbpaux

authors: cljung jbpaux


text:
[Issue] Broken Relative paths

These files / heading references no longer exist on the repo.
Need to reference correct files

File Full Path
Issues

./docs/productionizing.md
1. ../README.md#enabling-authentication

./docs/deploy_features.md
1. ../README.md#deploying

./docs/login_and_acl.md
1. ./app/backend/core/authentication.py  2. ./scripts/adlsgen2setup.ps1  3. ./scripts/sampleacls.json  4. ./scripts/sampleacls.json  5. ./scripts/sampleacls.json  6. ./scripts/sampleacls.json  7. ./scripts/prepdocs.py  8. ./scripts/manageacl.ps1  9. ./scripts/manageacl.ps1  10. ./scripts/manageacl.sh

./docs/azd.md
1. ../README.md#deploying-from-scratch

./docs/deploy_existing.md
1. ../README.md#deploying

./docs/deploy_lowcost.md
1. ../README.md#deploying  2. ../README.md#existing-azure-ai-search-resource  3. ../README.md#deploying-from-scratch

./docs/localdev.md
1. ../README.md#azure-deployment

./.github/PULL_REQUEST_TEMPLATE.md
1. ../CONTRIBUTING.md#submit-pr

Originally posted by @github-actions[bot] in https://github.com/Azure-Samples/azure-search-openai-demo/issues/1386#issuecomment-1992538667

I'll fix those up now, thanks!

@pamelafox there is a bug, I have dealt with links that have # at the end of them.
please ignore these errors. I will release a fix now to stop these errors.

I noticed that they weren't all actually broken. I did decide to change all those to absolute URLs, seems more robust for the future anyway?

Yeah, It is.
I also removed the # from the cached URL.
releasing it to Pypi now.

I didn't realize that's what you meant by absolute URLs.
The Script won't catch these URLs now..
It needs the relative path to either start with ./ or ../ to be able to evaluate it.

Ohh interesting. It cant see URLs starting with "/" and know that they're repo links?

I'm skipping if it doesn't have a . or .. in front of the URL.
But even If I don't skip (which will produce other problems)
The script won't be able to evaluate the URL as it won't know which folder is parent to it.
It won't know how to access it.
How it works is that It takes the current path + relative path AND evaluates them and tries to access the generated path if it doesn't exist it will be flagged as broken.
If we don't provide the relative path either . or .. it won't be able to evaluate suff

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


text:
Redeploying existing app on a new OpenAI resource

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)

I have a received a quota increase in a OpenAI location (North Central US) different from the one where I deployed my app in (CanadaEast). The deployment works very well and I've put a lot of time in the frontend, uploading a high volume of docs, as well as fine-tuning the indexes and the prompts for my specific needs and it works really well.
Is there a smooth way of making this transition to take advantage of the increased quotas? I'm new to this and don't want to risk breaking what I already have.
My initial thought was to delete the OpenAI resource from the portal, then run azd up and create a new one in the new location when prompted. Any guidance would be helpful.

Can you follow these steps? https://github.com/Azure-Samples/azure-search-openai-demo#existing-openai-resource

authors: amreales pamelafox


text:
Updates to login docs (login step, Entra branding)

Purpose
This PR was originally made to clarify that you must login to your auth tenant if its different from main tenant. But then I also fixed the Markdown lint issues and updated all Azure AD mentions.
Fixes #1571
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
[ ] Yes
[X] No

Does this require changes to learn.microsoft.com docs?
This repository is referenced by this tutorial
which includes deployment, settings and usage instructions. If text or screenshot need to change in the tutorial,
check the box below and notify the tutorial author. A Microsoft employee can do this for you if you're an external contributor.
[ ] Yes
[X] No

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

Code quality checklist
See CONTRIBUTING.md for more details.
N/A

CI checks passing now, ready for review.

@mattgotteiner Ready for review :)


text:
Newer keyword models won't load in iOS sdk

Error during Wakeword Listen: 0x5 (SPXERR_INVALID_ARG) Exception with an error code: 0x5 (SPXERR_INVALID_ARG)
[CALL STACK BEGIN]
3   MicrosoftCognitiveServicesSpeech    0x00000001036e28a0 GetModuleObject + 2417632
4   MicrosoftCognitiveServicesSpeech    0x00000001036e41a8 GetModuleObject + 2424040
5   MicrosoftCognitiveServicesSpeech    0x00000001034c9564 GetModuleObject + 217252
6   MicrosoftCognitiveServicesSpeech    0x00000001034b52ac GetModuleObject + 134636
7   MicrosoftCognitiveServicesSpeech    0x00000001034b4bec GetModuleObject + 132908
8   MicrosoftCognitiveServicesSpeech    0x00000001034b4700 GetModuleObject + 131648
9   MicrosoftCognitiveServicesSpeech    0x00000001034a30a4 GetModuleObject + 60388
10  MicrosoftCognitiveServicesSpeech    0x00000001034a1018 GetModuleObject + 52056
11  MicrosoftCognitiveServicesSpeech    0x00000001034a06b0 GetModuleObject + 49648
12  MicrosoftCognitiveServicesSpeech    0x00000001034c28c0 GetModuleObject + 189440
13  MicrosoftCognitiveServicesSpeech    0x00000001034bc4b4 GetModuleObject + 163828
14  MicrosoftCognitiveServicesSpeech    0x00000001035e6a04 GetModuleObject + 1385796
15  MicrosoftCognitiveServicesSpeech    0x00000001035e6990 GetModuleObject + 1385680
16  MicrosoftCognitiveServicesSpeech    0x00000001035e8830 GetModuleObject + 1393520
17  MicrosoftCognitiveServicesSpeech    0x00000001035e6b68 GetModuleObject + 1386152
18  MicrosoftCognitiveServicesSpeech    0x00000001035e99a4 GetModuleObject + 1397988
19  libsystem_pthread.dylib             0x00000001ee2ec06c _pthread_start + 136
[CALL STACK END]
func loadWakeword() throws -> Void {
        do {
            let str = WAKEWORD_MODEL.components(separatedBy: ".")[0]
            let model = URL(fileURLWithPath:Bundle.main.path(forResource: str, ofType: "table")!);
            wakewordModel = try SPXKeywordRecognitionModel(fromFile: model.path);
            _reloadWakewordRecognizer()
        } catch let error{
            throw RuntimeError("Error during Wakeword Load: " + error.localizedDescription)
        }

private func wakewordCancelled(recog: SPXKeywordRecognizer, eventArg: SPXKeywordRecognitionCanceledEventArgs) {
        switch eventArg.reason {
        case SPXCancellationReason.error:
            print("Error during Wakeword Listen: " + eventArg.errorDetails!);
// THIS WAS TRIGGERED IN THE ERROR
            try! startWakeword(flutterResult: { _ in return });
            break;
}

Describe the bug
When I load in a keyword from the Speech Studio in my iOS application, the keyword does not work. We have multiple keywords, and all the other ones work. The last one I made was 2 months ago, and that one is working fine, even when I re-download it and place it in my XCode. I tried with another model I made 2 days ago, that one was not working either. That is why I suspect it might be something on the Speech Studio side.
I tried with the SDK we are currently using (1.35) and the updated one (1.38). It seems that 1.40 is not available for iOS yet.
Note: on Android, the keyword worked out of the box, even in SDK 1.30, so I do not think it is the model itself.
To Reproduce
Steps to reproduce the behavior:

Create a keyword with the Speech Studio, use the Advanced model.
Try to load it in an iOS app, with the code provided, or use a sample code

Version of the Cognitive Services Speech SDK

SDK version: 1.38.0/1.35.0

Platform, Operating System, and Programming Language

OS: iOS
Programming language: Swift
SDK version: 1.38.0

There was an trunk push failure I did not notice earlier.  I've republished 1.40.0 again, so you should be able to try it now.  That is unlerated the the above issue, but thanks for pointing out this missing package release.

@Lirry18 The error is probably due to a format change for advanced keyword models at least. Support for the new format was originally included in SDK releases but withdrawn due to complaints about the binary size growth, now it's only available in the "embedded speech" package that contains non-default functionality. However, documentation seems not have been updated to reflect this.
Please download the package from https://aka.ms/csspeech/iosbinaryembedded that currently points to MicrosoftCognitiveServicesSpeech-EmbeddedXCFramework-1.40.0.zip and build your application using that instead of the default package.

@pankopon , Thanks I will try that out then! Will this be in the official SDK 1.40 as well?

@Lirry18 MicrosoftCognitiveServicesSpeech-EmbeddedXCFramework-1.40.0.zip is an official 1.40.0 release package, it's just an alternative to the default MicrosoftCognitiveServicesSpeech-XCFramework-1.40.0.zip (from https://aka.ms/csspeech/iosbinary) due to the mentioned binary size difference for keyword support and because most customers don't use embedded speech.

Public documentation has been updated in the Speech SDK 1.41.1 release to point out the correct package.

authors: BrianMouncer Lirry18 pankopon


text:
Advanced Messages SDK python samples

Purpose

ACS Advanced Messaging :
https://learn.microsoft.com/en-us/azure/communication-services/concepts/advanced-messaging/whatsapp/whatsapp-overview
Adding Advanced Messages SDK python samples

Does this introduce a breaking change?

[ ] Yes
[ ] No

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

[ ] Bugfix
[ ] 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

Test the code

What to Check
Verify that the following are valid

...

Other Information

Can we delete messages-quickstart.py if all scenarios are covered in the individual scripts?

#sign-off

#sign-off

#sign-off

#sign-off

authors: DominikMe Shamkh arifibrahim4 natekimball-msft


text:
[BUG]Unable to Deploy Graph Rag Backend

When I try to deploy Graph Rag - I get the following error when deploying image
Deploying docker image 'graphrag:backend' to container registry 'crtc6ln7gltg66c.azurecr.io'...Error deploying docker image, exiting...

Pls post more details.

@adnanakram82 - see this issue and comment for some troubleshooting tips.
https://github.com/Azure-Samples/graphrag-accelerator/issues/67#issuecomment-2217752539

repo: Azure-Samples/graphrag-accelerator


text:
Add Metrics to OPC PLC

Purpose
Enable metrics emission from OPC PLC in addition to OTEL tracing added previously

Also, increase the version in version.json

@saixiaohui please confirm with LGTM.

authors: bhnaphade luiscantero

repo: Azure-Samples/iot-edge-opc-plc


text:
[Deployment]  Can not perform requested operation on nested resource. Parent resource 'mdwdops-kv-dev-snpk' not found

I get the following error, to deploy E2E example Synapse Parking Sensor.    I used "snpk" as   DEPLOYMENT_ID .
export GITHUB_REPO="msdya/modern-data-warehouse-dataops"
export GITHUB_PAT_TOKEN="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"
export AZURE_LOCATION="westeurope"
export AZURE_SUBSCRIPTION_ID="8a207ddf-b53c-48df-9525-fc806b8ca6c8"
export DEPLOYMENT_ID="snpk"
export AZDO_PIPELINES_BRANCH_NAME="main"
export AZDO_PROJECT="parking_sensors_synapse_ci_cd"
export AZDO_ORGANIZATION_URL="https://dev.azure.com/daweiyaolab/"
===================================================
Below is the error message, and details.
"Can not perform requested operation on nested resource. Parent resource 'mdwdops-kv-dev-snpk' not found
-======================================================
Details:
ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n    "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n    "details": [\r\n      {\r\n        "code": "DeploymentFailed",\r\n        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",\r\n        "details": [\r\n          {\r\n            "code": "BadRequest",\r\n            "message": "{\r\n  \"error\": {\r\n    \"code\": \"BadRequest\",\r\n    \"message\": \"Invalid value found at accessPolicies[0].ObjectId: null\"\r\n  }\r\n}"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"},{"code":"Conflict","message":"{\r\n  "status": "Failed",\r\n  "error": {\r\n    "code": "ResourceDeploymentFailure",\r\n    "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n    "details": [\r\n      {\r\n        "code": "DeploymentFailed",\r\n        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",\r\n        "details": [\r\n          {\r\n            "code": "Conflict",\r\n            "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"OperationTimedOut\",\r\n        \"message\": \"The operation timed out and automatically rolled back. Please retry the operation.\"\r\n      }\r\n    ]\r\n  }\r\n}"\r\n          },\r\n          {\r\n            "code": "NotFound",\r\n            "message": "{\r\n  \"error\": {\r\n    \"code\": \"ParentResourceNotFound\",\r\n    \"message\": \"Can not perform requested operation on nested resource. Parent resource 'mdwdops-kv-dev-snpk' not found.\"\r\n  }\r\n}"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"}]}}

Hi @msdya, I cannot replicate this. This error is telling me that the KeyVault that is part of the deployment does not exist -- which tells me perhaps KeyVault was not deployed successfully. One thing to check is make sure KV is deployment successful. A common error is related to same names to a previously deployed and deleted KeyVault. Specifically if you do not purge a deleted KeyVault from a previous deployment with the same name (deployment id), succeeding deployments will fail.
I'll close this issue for now. Please reopen if you are still experiencing this.

authors: devlace msdya


text:
Fixes dev environment

It now implements the Dev interface again which fixes interface assertions such as this:
https://github.com/Azure/ARO-RP/blob/cdbe75feeb35ce1a524832b661dc673206cb500e/cmd/aro/rp.go#L45-L60

Thank-you!

repo: Azure/ARO-RP


text:
feat: containerinsights 3.1.10 release

What type of PR is this?
/kind feature

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

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

Special notes for your reviewer:
Release note:
(https://github.com/microsoft/Docker-Provider/blob/ci_prod/ReleaseNotes.md)

Pull Request Test Coverage Report for Build 5480640034

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on longw/ci-release-3.1.10 at 61.507%

Totals

Change from base Build 5479147129:
61.5%

Covered Lines:
2563

Relevant Lines:
4167

💛  - Coveralls

authors: coveralls wanlonghenry

repo: Azure/AgentBaker


text:
TCPandUDP Port Description Watchlist

This watchlist is meant to create a table of offical and unoffical tcp and udp port information. This watchlist can be used to provide context to other network based logs that do not contain port description or application service information running on port.
Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@anki-narravula Please review and provide your approve.

@anki-narravula Please review and provide your approve.

@anki-narravula: Could you please review the watchlist. Thanks!

@NikTripathi :Please review the watchlist and provide your approve.

Hi @NikTripathi
Can you please review and approve the PR.
Thanks

Looking into this.

Hi @NikTripathi
Can you please review and approve the PR.
Thanks

Hi @NikTripathi,
Can you please review or assign it to someone who can work on it.
Thanks

Hi @NikTripathi ,
Could you please provide update on this.
Thanks

Hi @NikTripathi ,
Could you please provide update on this.
Thanks

Hi @NikTripathi,
Could you please provide update on this.
Thanks

Hi @NikTripathi,
Could you please provide update on this.
Thanks

Sorry for the delay. I am working on this.

Hi @NikTripathi,
Could you please provide update on this.
Thanks

authors: NikTripathi swiftsolves-msft v-mchatla v-spadarthi vmanojreddy

repo: Azure/Azure-Sentinel


text:
[Logic Apps] Range query does not find entity created by batch API

Which service(blob, file, queue, table) does this issue concern?
table
Which version of the Azurite was used?
Latest from table branch (948e5eb7efc8f76182d4ad6e0e248583d8a9886e)
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Local npm build
What's the Node.js version?
v14.16.0
What problem was encountered?
Range query is not able to find entity that was created by batch API
Steps to reproduce the issue?
Azurite
Create rows via batch API

2021-04-08T00:49:45.811Z 830cdc55-3f5f-4417-849a-cc04c466d90b info: TableStorageContextMiddleware: RequestMethod=POST RequestURL=http://127.0.0.1/devstoreaccount1/$batch?sv=2018-03-28&sig=PIbzxevR9LNa4rHkaAb7ARBkPVOzkzvH2r%2FmVuy%2FSpI%3D&se=2023-04-08T00%3A49%3A44Z&srt=sco&ss=bqt&sp=racupwdl&timeout=6 RequestHeaders:{"user-agent":"ResourceStack/6.0.0.1265","x-ms-version":"2018-03-28","x-ms-client-request-id":"5804f189-a274-4e73-8462-fe0dbbdc1fcf","accept":"application/json;odata=nometadata","content-type":"multipart/mixed; boundary=batch_de4bb254-744a-4020-9813-f911fb2e2fd7","host":"127.0.0.1:10002","content-length":"2540","expect":"100-continue"} ClientIP=127.0.0.1 Protocol=http HTTPVersion=1.1

2021-04-08T00:49:45.813Z 830cdc55-3f5f-4417-849a-cc04c466d90b debug: TableHandler:batch() Raw request string is "--batch_de4bb254-744a-4020-9813-f911fb2e2fd7\r\nContent-Type: multipart/mixed; boundary=changeset_de4bb254-744a-4020-9813-f911fb2e2fd7\r\n\r\n--changeset_de4bb254-744a-4020-9813-f911fb2e2fd7\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\n\r\nPUT http://127.0.0.1:10002/devstoreaccount1/storagedataprovidercit(PartitionKey='DCABC',RowKey='7eeb8009-9440-4cfe-ad83-eb617cf9806b_A-A') HTTP/1.1\r\nAccept: application/json;odata=nometadata\r\nContent-Type: application/json\r\n\r\n{\"MyOtherKey\":1,\"CreatedTime\":\"2021-04-08T00:49:44.8627149Z\",\"CreatedTime@odata.type\":\"Edm.DateTime\",\"ChangedTime\":\"2021-04-08T00:49:44.9938785Z\",\"ChangedTime@odata.type\":\"Edm.DateTime\",\"DeletedTime\":\"1970-01-01T00:00:00Z\",\"DeletedTime@odata.type\":\"Edm.DateTime\",\"ChangedOperationId\":\"5804f189-a274-4e73-8462-fe0dbbdc1fcf\",\"UseCustomIndexes\":false,\"MyPartitionKey\":\"7eeb8009-9440-4cfe-ad83-eb617cf9806b\",\"MyRowKey\":\"A-A\"}\r\n--changeset_de4bb254-744a-4020-9813-f911fb2e2fd7\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\n\r\nPUT http://127.0.0.1:10002/devstoreaccount1/storagedataprovidercit(PartitionKey='DCABC',RowKey='7eeb8009-9440-4cfe-ad83-eb617cf9806b_A-B') HTTP/1.1\r\nAccept: application/json;odata=nometadata\r\nContent-Type: application/json\r\n\r\n{\"MyOtherKey\":2,\"CreatedTime\":\"2021-04-08T00:49:44.8782291Z\",\"CreatedTime@odata.type\":\"Edm.DateTime\",\"ChangedTime\":\"2021-04-08T00:49:44.9938785Z\",\"ChangedTime@odata.type\":\"Edm.DateTime\",\"DeletedTime\":\"1970-01-01T00:00:00Z\",\"DeletedTime@odata.type\":\"Edm.DateTime\",\"ChangedOperationId\":\"5804f189-a274-4e73-8462-fe0dbbdc1fcf\",\"UseCustomIndexes\":false,\"MyPartitionKey\":\"7eeb8009-9440-4cfe-ad83-eb617cf9806b\",\"MyRowKey\":\"A-B\"}\r\n--changeset_de4bb254-744a-4020-9813-f911fb2e2fd7\r\nContent-Type: application/http\r\nContent-Transfer-Encoding: binary\r\n\r\nPUT http://127.0.0.1:10002/devstoreaccount1/storagedataprovidercit(PartitionKey='DCABC',RowKey='7eeb8009-9440-4cfe-ad83-eb617cf9806b_B-A') HTTP/1.1\r\nAccept: application/json;odata=nometadata\r\nContent-Type: application/json\r\n\r\n{\"MyOtherKey\":2,\"CreatedTime\":\"2021-04-08T00:49:44.8782463Z\",\"CreatedTime@odata.type\":\"Edm.DateTime\",\"ChangedTime\":\"2021-04-08T00:49:44.9938785Z\",\"ChangedTime@odata.type\":\"Edm.DateTime\",\"DeletedTime\":\"1970-01-01T00:00:00Z\",\"DeletedTime@odata.type\":\"Edm.DateTime\",\"ChangedOperationId\":\"5804f189-a274-4e73-8462-fe0dbbdc1fcf\",\"UseCustomIndexes\":false,\"MyPartitionKey\":\"7eeb8009-9440-4cfe-ad83-eb617cf9806b\",\"MyRowKey\":\"B-A\"}\r\n--changeset_de4bb254-744a-4020-9813-f911fb2e2fd7--\r\n--batch_de4bb254-744a-4020-9813-f911fb2e2fd7--\r\n"

2021-04-08T00:49:45.814Z 830cdc55-3f5f-4417-849a-cc04c466d90b info: EndMiddleware: End response. TotalTimeInMS=3 StatusCode=202 StatusMessage=Accepted Headers={"server":"Azurite-Table/3.9.0-table-alpha.1","content-type":"multipart/mixed; boundary=batchresponse_de4bb254-744a-4020-9813-f911fb2e2fd7","x-ms-request-id":"830cdc55-3f5f-4417-849a-cc04c466d90b","x-ms-version":"2019-12-12","date":"Thu, 08 Apr 2021 00:49:45 GMT"}

Range query to get row

2021-04-08T00:49:45.840Z 6ce348c3-0f2a-4c83-b5e4-a75e97bb8a56 info: TableStorageContextMiddleware: RequestMethod=GET RequestURL=http://127.0.0.1/devstoreaccount1/storagedataprovidercit?sv=2018-03-28&sig=PIbzxevR9LNa4rHkaAb7ARBkPVOzkzvH2r%2FmVuy%2FSpI%3D&se=2023-04-08T00%3A49%3A44Z&srt=sco&ss=bqt&sp=racupwdl&$filter=%28%28PartitionKey%20eq%20%27DCABC%27%29%20and%20%28%28RowKey%20ge%20%277eeb8009-9440-4cfe-ad83-eb617cf9806b_A-%27%29%20and%20%28RowKey%20lt%20%277eeb8009-9440-4cfe-ad83-eb617cf9806b_A.%27%29%29%29%20and%20%28DeletedTime%20eq%20datetime%271970-01-01T00%3A00%3A00.0000000Z%27%29&$select=CreatedTime%2CChangedTime%2CChangedOperationId%2CDeletedTime%2CSlidingTimeToLiveInDays%2CPartitionKey%2CRowKey%2CTimestamp&$top=1&timeout=6 RequestHeaders:{"user-agent":"ResourceStack/6.0.0.1265","x-ms-version":"2018-03-28","x-ms-client-request-id":"99459a9e-6e6b-48a3-93a0-ed6099d91298","accept":"application/json;odata=minimalmetadata","host":"127.0.0.1:10002"} ClientIP=127.0.0.1 Protocol=http HTTPVersion=1.1

2021-04-08T00:49:45.841Z 6ce348c3-0f2a-4c83-b5e4-a75e97bb8a56 debug: TableHandler:queryEntities() Raw response string is "{\"odata.metadata\":\"http://127.0.0.1:10002/devstoreaccount1/$metadata#Tables/@Element\",\"value\":[]}"

Have you found a mitigation/solution?
No

Should be fixed by #752

authors: edwin-huber laveeshb

repo: Azure/Azurite


text:
Provide customer information on how to create the admin user.

Is your feature request related to a problem? Please describe.
There is no documentation on how to create the first admin user.
Describe the solution you'd like
Provide information that the admin email is supposed to be a the friendly user table and provide screenshots.
Describe alternatives you've considered
Alternatively the ARM deployment script creation should prompt for the admin email in the Portal textfield and push it to the deployed DB.

I went by your inputs and accomodated this as an input parameter to the ARM template. The template would add the admin users to the application configuration. The admin portal consumes this detail and initializes the admin users at the time of startup.


text:
ConfigureForAzureWithTokenCredentialAsync failed with ManagedIdentityCredential failed with SocketException after retries

Hello,
We are in the process of rolling out Redis with AAD Authentication for our service. However, we started seeing SocketException failures when trying to establish a new connection:
Note: We are using DefaultAzureCredential() to authenticate and SDK version in 2.0.0
 await options.ConfigureForAzureWithTokenCredentialAsync(authToken.ObjectId, new DefaultAzureCredential());
 ConnectionMultiplexer multiplexer = await ConnectionMultiplexer.ConnectAsync(options).ConfigureAwait(false);

Connection failed with MI: **System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.5.9:2377** **07-10-2024 15:10:49**
Investigating this failure, we found that the token used to authenticate has an expiration date of:
AccesTokenExpirationDate=7/11/2024 3:05:08 PM
This might correlate with the auth failure on 07/10 15:10PM, since the token expires every 24 hrs probably around that period of time the SDK was refreshing a new token and hence the failures during the connection attempt? However, my understanding is that Microsoft.Azure.StackExchangeRedis will refresh the token when 75% of the lifetime of the current token has passed.
The connection then succeded around 15:16PM:

What version of the package are you on? You may need to upgrade to 3.1.0 to get this fix: #52

What version of the package are you on? You may need to upgrade to 3.1.0 to get this fix: #52

version 2.0.0

authors: isacruzramos philon-msft


text:
[Feature Request from Discussions] Automation account module don't pass all parameters for runbooks

Discussed in https://github.com/Azure/ResourceModules/discussions/3282

Originally posted by dibcar May 27, 2023
Hi,
Is there a reason why the automation account module don't pass every parameter to the runbook sub module ? The parameters scriptStorageAccountId and sasTokenValidityLenght are not passed to the runbook module.
Thanks,

This used to be a very nasty bug in the original module that was thankfully fixed in the meantime. The latest version can be found here: https://github.com/Azure/bicep-registry-modules/blob/86cfa8621eec707cba22912affb179b641960b92/avm/res/automation/automation-account/main.bicep#L238-L239

Closing as per previous comment

authors: AlexanderSehr eriqua

repo: Azure/ResourceModules


text:
Nodes FabricNode Certificate Expiration.md broken content

https://github.com/Azure/Service-Fabric-Troubleshooting-Guides/blob/master/Known_Issues/Nodes FabricNode Certificate Expiration.md has missing content in the end of Mitigation section, and broken links formatting in Resolution section.

this is fixed, thanks for reporting.

authors: sedwardstx v-karbovnichy


text:
[cdrp] add compute-sku-recommender command group

Add compute-sku-recommender command group for spot placement cli
cli pr: https://github.com/Azure/azure-cli/pull/28750

@joal42, please attach the cli PR link.

@joal42, please attach the cli PR link.

https://github.com/Azure/azure-cli/pull/28750

Please help resolve conflicts.

Please help resolve conflicts.

Done.

repo: Azure/aaz


text:
Enabling Azure CNI for Windows

What this PR does / why we need it:
This PR enables Azure CNI for Windows nodes. This PR allows Windows/hybrid kubernetes clusters to take advantage of Azure CNI.
Which issue this PR fixes
fixes #1504
Special notes for your reviewer:
This PR requires Azure CNI v1.0.2.

I had an issue with getting a mixed cluster (Linux and windows agent pool) working, kube dns not starting with networkPolicy:none. As described in this:
Built acs-engine with this pullrequest, and networkPolicy:azure, cluster camre right up 👍

@saiyan86 permission to rebase/force push (so we can run this through E2E with recent improvements)?

Will this also fix #2027 ? @JiangtianLi

@JiangtianLi I rebased this to test using recent E2E improvements. Wanted to clarify: do we want this PR to turn on Azure CNI by default for Windows?

@duedal That issue is unrelated.

@jackfrancis Yes, we want Azure CNI by default for Windows. We want to run deep test once I bring in the windows patch. For now, we can make sure e2e test pass.
@saiyan86 You mentioned yesterday to hold for your testing?

Just ran a successful round of Windows E2E tests backed by Azure CNI. I advocate we merge and start doing some manual testing.

@saiyan86 Will wait for your go-ahead to merge.

Thanks @jackfrancis, @JiangtianLi  Can you sign off if there is no regression and azure cni is not default.
In our testing of azure-cni, most of the scenarios are working, except we think we are hitting the issue similar to the issue where service-ip connectivity was broken: BUG 15422319 [RS3] Backport: Create remote endpoint on L2Bridge fails
May be we need to follow up with windows team to understand what is going on there for service vip.l

As per @saiyan86 we're changing the default back to kubenet. We'll merge this PR as-is and fix bugs in follow-up PRs. This PR allows us to test Azure CNI in Windows clusters by building them explicitly with "networkPolicy": "azure".
Thanks again @saiyan86 !

/cc @sharmasushant, @tamilmani1989, @saiyan86, could you give some context to Onur about CNI status and update the description here?
/cc @jackfrancis

@ofiliz This is not the same PR. This PR does not enable use of both calico (when available) and azure at the same time. So vnetIntegration related stuff is removed.

Hello guys, acs-engines 0.12.5 with windows and linux pool still generates nodes with kube-dns-v20 crashing !! any quick fix ? recompiling master is no an option, as it's not stable at all.
Is there any stable version where Linux and Windows pods can communicate without any problems ??
Thank you very much.

@magnock are you able to reproduce the issue easily? If so, and if you are able to build acs-engine from master, you could re-try a cluster deployment using HEAD, which as of this morning includes Windows RS3 fixes that may address your symptoms.

@magnock I can build K8i cluster with 0.12.5 where the kube-dns-v20 is stable and up and running.
One thing that you can check is that your ServicePrincipalProfile is correct. It had threw me for a loop, since there is no validation and it's not being used provisioning the cluster, but it's used later on.
I'm not the only one bitten by this ;-)
How ever windows pods can't talk to other pods without a workaround.
But the kube-dns should be stable from my experience.

authors: JiangtianLi duedal jackfrancis magnock msorby saiyan86 sharmasushant

repo: Azure/acs-engine


text:
Sync template service broker deployment with latest o-a

Syncs us with https://github.com/openshift/openshift-ansible/pull/8479
Should fix https://github.com/Azure/acs-engine/issues/3067
@jim-minter @kwoodson

/label orchestrator/openshift

/approve

@jim-minter @pweil- fyi we are using explicit approvals here

@jim-minter @pweil- fyi we are using explicit approvals here

:tada: :balloon: :clinking_glasses:
@CecileRobertMichon can we add some extra color for the labels?  So many grey labels! :smile:
example: https://github.com/kubernetes/kubernetes/pull/64275

We have label config that syncs colors, I am going to add it in a follow-up.

This PR is good to go, there is still an issue with asb - opened https://github.com/openshift/openshift-ansible/issues/8526

/lgtm

@CecileRobertMichon can we add some extra color for the labels? So many grey labels! 😄

Done

authors: CecileRobertMichon jim-minter kargakis pweil-


text:
no proper error if training file path is wrong

if user gives wrong "runconfig_python_file", or the path is wrong , the code throws below error

this error is not explicit why issue has come and looks like the code inherently threw an error.  while actually there was in exception during module import execution

@ashishonce This will be adressed in the next release. I found the issue by using unit tests.

authors: ashishonce marvinbuss

repo: Azure/aml-run


text:
Add System.Text.Json support to Utf8JsonWriterExtensions

Fixes https://github.com/Azure/azure-sdk-for-net/issues/20051

Test?

authors: chamons pakrym


text:
Handling of empty objects

typespec: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/apicenter/ApiCenter.Management/models.tsp#L492

swagger:
    "CustomProperties": {
      "type": "object",
      "description": "The custom metadata defined for API catalog entities."
    },

tsp:
@summary("Custom Properties")
@doc("The custom metadata defined for API catalog entities.")
model CustomProperties {}

Can you confirm that an empty object is the proper tsp to model any?

If name is generated and has no properties then it's an any type.

It should be the tsp definition issue.

authors: Alancere jhendrixMSFT tadelesh


text:
generate assemblyinfo.cs for azure

original PR: #1376
reverted by: #1380
TODO: 1. insert header 2. update version during adapt parent

/azp run autorest.powershell - PR Validation via azure-powershell-generation-m4 (Service: Kusto)

/azp run

/azp run


text:
Keep the filter column visible while scrolling through template cards

We want to be able to have our filter column persist while scrolling through the template cards. Today, if you scroll too far down the page you will have to scroll back up to view / select filters.

Marked as P1. Not a blocker for build
cc @gkulin @kristenwomack

repo: Azure/awesome-azd


text:
[New azd-template] msdocs-flask-postgresql-sample-app

New azd-template Submission
Fill in the sections below to populate a new Gallery card for your template. An example of a valid template object is given at the end for reference. All fields are mandatory unless explicitly identified as optional
1. Title
Python (Flask) Web App with PostGreSQL
2. Description
A restaurants review web app with a PostGreSQL database, written in the Python Flask framework plus SQL-Alchemy plus Alembic for database interactions. Ready for deployment on App Service with a PostGreSQL Flexible Server inside a VNet.
3. Author Profile
https://github.com/Azure-samples
4. Author Name
Azure samples
5. Template Repo
https://github.com/pamelafox/msdocs-flask-postgresql-sample-app-azd
This will be merged into Azure-samples once approved. I want to get your feedback first to minimize the number of PRs I need to make to Azure-samples.
Note that these changes are very similar to the django app I recently submitted.
6. Link to PR where you made your repo azd compatible
https://github.com/Azure-Samples/msdocs-flask-postgresql-sample-app/compare/main...pamelafox:msdocs-flask-postgresql-sample-app-azd:main
7. Standard Tags
python, web apps, azure db for postgresql, azure app service, vnet
7. Additional Tags (optional)
flask
8. Architecture Diagram or Application Screenshot
Used as default image for template card - must be representative of solution being enabled. Submit image by adding it as file upload to this issue

Example Of Valid Template
  {
    title: 'ToDo Application - React C# CosmosDB SQL',
    description:
      'Complete React.js ToDo application, C# for the API, Azure Cosmos DB SQL API for storage, and Azure Monitor for monitoring and logging',
      preview: `todo-csharp.png`,
    website: 'https://github.com/danieljurek',
    author: 'Daniel Jurek',
    source: 'https://github.com/Azure-Samples/todo-csharp-cosmos-sql',
    tags: ['featured','csharp','dotnet','javascript','appservice','cosmosdb','monitor','keyvault','reactjs'],
  },

Next Steps
Once submitted the issue will be reviewed - we plan to do reviews on a rolling basis at regular intervals. The process will involve checking that template information is complete, and the template is valid.

If we have questions or enhancements, we will add comments in issue thread (issue stays open)
If the contribution is approved, we'll update the gallery directly (issue will then be closed)

@hemarina - LGTM

Great, my pull request to Azure-Samples is https://github.com/Azure-Samples/msdocs-flask-postgresql-sample-app/pull/16
I can't merge it myself as the content team owns that repo, but the owner is fairly responsive. I'll ping him tomorrow if it's still unmerged.

It was merged earlier this week, so this is all set.

authors: jongio pamelafox


text:
{AKS} az aks create: Update help message of option --enable-managed-identity

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} az aks create: Update help message of option --enable-managed-identity
Related command

General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS

authors: FumingZhang yonzhan

repo: Azure/azure-cli-extensions


text:
Model Capacities - List an Ai_service

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
Show capacity for Azure AI models
az ai_service show capacity --api-version "2024-10-01" --model-format "OpenAI" --model-name "gpt-4" --model-version "turbo-2024-04-09"
General Guidelines

[X] Have you run azdev style ai_service locally? (pip install azdev required) yes
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[X] My extension version conforms to the Extension version schema

For new extensions:

[X] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

/azp run

Hi @ovidiu10, did you go through to Apex onboarding process? CC @Jacekey23

@ovidui10,
Before creating the PR with our dev team,
please refer to APEX process to be onboarded with Azure CLI.
OnboardSurvey and it will have us to get more info to help you later.
Thanks

@Jacekey23 let me know what else I need to do :) thanks

Hi @ovidiu10, if seems you can use the aaz-dev-tools to generate the command.

@kairu-ms sorry but not sure if I get this :)
"if seems you can use the aaz-dev-tools to generate the command."
can you let me know what else I need to do
thanks


text:
Wrong example for remove exclude

Explanation is for exclude and example is for include. Change the following command
az storage remove -c MyContainer -n path/to/directory --recursive --include "foo*;*bar"
to
az storage remove -c MyContainer -n path/to/directory --recursive --exclude "foo*;*bar"

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

ID: b8c4e415-fc8d-26d5-3213-da937fd6932c
Version Independent ID: dcb2f2d6-fd80-495d-8582-8be859d68792
Content: az storage
Content Source: src/azure-cli/azure/cli/command_modules/storage/_help.py
Service: storage
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S165.

@Juliehzl, @jsntcy , please help take a look.

Hi @subashsivaji, thanks a lot for your feedback!
What I hope you know is that there is a breaking change in az storage remove command: --include and --exclude parameters have been changed to --include-path, --include-pattern, --exclude-path and --exclude-pattern parameters to have more flexibility.

authors: Juliehzl jsntcy subashsivaji yonzhan

repo: Azure/azure-cli


text:
cannot create storage account

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
I cannot create storage account of particular name - 'ubuntusa'.
I get error message that this name is already taken.
When I get the list of storage accounts in my resource group, there's no such account with this name.
To Reproduce
root@Alexey-HP:~# az storage account create \

--name ubuntusa
--resource-group ubunturesourcegroup
--location northeurope
--sku Standard_LRS
The storage account named ubuntusa is already taken.

root@Alexey-HP:~# az storage account list --resource-group ubunturesourcegroup
AccessTier    CreationTime                      EnableHttpsTrafficOnly    Kind       Location     Name       PrimaryLocation    ProvisioningState    ResourceGroup        StatusOfPrimary

Hot           2020-07-21T08:37:00.700165+00:00  True                      StorageV2  northeurope  ubuntusa2  northeurope        Succeeded            ubunturesourcegroup  available
Expected behavior
I expect to create storage account 'ubuntusa' the same way that I've created storage account 'ubuntusa2'.
Environment summary
root@Alexey-HP:~# az --version
azure-cli                          2.9.1
command-modules-nspkg              2.0.3
core                               2.9.1
nspkg                              3.0.4
telemetry                          1.0.4
Python location '/opt/az/bin/python3'
Extensions directory '/root/.azure/cliextensions'
Python (Linux) 3.6.10 (default, Jul 16 2020, 08:13:20)
[GCC 7.5.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy
root@Alexey-HP:~#
Additional context

add to S174

Hi @alexeyshishkin01, it may be caused that your subscription enable https policy.  please add --https-only in your command to enable https transfer.

hello @Juliehzl, so you're saying I can create storage account with name 'ubuntusa2' and cannot create 'ubuntusa' due to 'https policy' ?
it really sounds strange - could you pls. explain your thoughts ?
you see the error message is 'The storage account named ubuntusa is already taken' and in fact there's no such storage account in the list

Hi @alexeyshishkin01, sorry for misunderstanding.
although you cannot find the account name in your resource group, storage account name should be unique around the world, not only resource group or sunscription.

oh, really ?
is it possible to find out what storage account names are already taken in the world ?

you can use az storage account check-name to check.

ok, here we are:
root@Alexey-HP:~# az storage account check-name --name ubuntusa
NameAvailable
True
root@Alexey-HP:~#
root@Alexey-HP:~# az storage account check-name --name ubuntusa2
NameAvailable
True
root@Alexey-HP:~#
so, both names are available, but I cannot create storage account with 'ubuntusa' name and can create with 'ubuntusa2'
really odd

❯ az storage account create -n ubuntusa -g zuh --location northeurope --sku Standard_LRS
{
  "accessTier": "Hot",
  "allowBlobPublicAccess": null,
  "azureFilesIdentityBasedAuthentication": null,
  "blobRestoreStatus": null,
  "creationTime": "2020-08-03T05:27:14.856133+00:00",
  "customDomain": null,
  "enableHttpsTrafficOnly": true,
  "encryption": {
    "keySource": "Microsoft.Storage",
    "keyVaultProperties": null,
    "requireInfrastructureEncryption": null,
    "services": {
      "blob": {
        "enabled": true,
        "keyType": "Account",
        "lastEnabledTime": "2020-08-03T05:27:14.934270+00:00"
      },
      "file": {
        "enabled": true,
...

now it works!
root@Alexey-HP:~# az storage account create \

--name ubuntusa
--resource-group ubunturesourcegroup
--location northeurope
--sku Standard_LRS
AccessTier    CreationTime                      EnableHttpsTrafficOnly    Kind       Location     Name      PrimaryLocation    ProvisioningState    ResourceGroup        StatusOfPrimary

Hot           2020-08-05T18:56:24.677927+00:00  True                      StorageV2  northeurope  ubuntusa  northeurope        Succeeded            ubunturesourcegroup  available
but what's been changed since my last failure to do that ?

Hi @alexeyshishkin01, actually we do nothing in CLI side. I am not sure if there is anything change in server die. anyway it works as expected, so we close it now. If you have any furthur issue, feel free to let us know.

really strange, it did not work, you did not change anything, now it works - ok, let's close the case

Hello, all!
I have the same issue with 'dockersa' account.
Could you pls. shed more light on it ?

authors: Juliehzl alexeyshishkin01 yonzhan


text:
Azure-Cli install script doesn't work, issue with the Microsoft ubuntu repository?

Since approximately 8PM Pacific Time, our CI/CD system fails to build new images due to an issue with packages.microsoft.com.
This is currently still reproducible by using the Azure-Cli install script provided in the cli documentation
curl -sL https://aka.ms/InstallAzureCLIDeb | bash
[...]
Fetched 3964 B in 0s (8129 B/s)
Reading package lists... Done
W: Conflicting distribution: https://packages.microsoft.com/repos/azure-cli focal InRelease (expected focal but got xenial)
E: Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/focal/main/binary-amd64/Packages.gz  File has unexpected size (8601 != 18731). Mirror sync in progress? [IP: 40.117.131.251 443]
   Hashes of expected file:
    - Filesize:18731 [weak]
    - SHA512:d2791dca6a9339e8f57a5d5ec6922f1c072a7baa0bad951e11551849df01b86776c28da810f05353e20cf4e48e980d307d243a232e25735fe89fa9554696fb8e
    - SHA256:4f529a893071dc1985f3ea3c806d0efc6790761bc4dca0c955ea59d6ccb05318
    - SHA1:9aef2de691b04069761dcad22906d00f0ecb3461 [weak]
    - MD5Sum:46be8f6e68b2c5efede1017b9ce99f37 [weak]
   Release file created at: Thu, 03 Mar 2022 03:27:53 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

To Reproduce
Run the bash script provided at https://aka.ms/InstallAzureCLIDeb from a debian distribution. Tested on:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"

Expected behavior
Install script should work as usual.
Environment summary

Additional context

It just started working again, it looks like this issue was happening for about ~30 to 50 minutes, I am wondering if there is a way to see status of the registry?

@jiasli for awareness

We have contacted https://packages.microsoft.com/ team and this issue should now have been fixed.

Thanks!
I can confirm that it started working less than an hour after the initial issue, it did cause us some small troubles during that time since we had to restart a bunch of builds.
I am wondering if there are any actionable items that we can track, for example is there any way to track the status/health of this registry?

@jeremy-albuixech, apologize for the inconvenience caused. This issue was caused by a regression introduced by a recent update to  https://packages.microsoft.com/ and the change had been rolled back.

I am wondering if there are any actionable items that we can track, for example is there any way to track the status/health of this registry, or is there a better/more appropriate place to see communication and issues about this platform?

Currently there is no health dashboard for https://packages.microsoft.com/. If you see any problems, please feel free to open a GitHub issue and put something like "URGENT" in the title so that we can notice it and work on it with high priority. 😊

authors: jeremy-albuixech jiasli yonzhan


text:
compatibility issues between azure-core and azure-cli: cannot import name 'case_insensitive_dict' from 'azure.core.utils'

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
Describe the bug
We are noticing compatibility issues between azure-core and azure-cli: cannot import name 'case_insensitive_dict' from 'azure.core.utils'.
Until cli 2.37.0, AZ CLI had the dependency azure-core==1.21.1
Starting 2.38.0, AZ CLI is having dependency azure-core==1.24.0
In case, we install a package that has a direct or indirect dependency on the lower azure-core==1.21.1, the AZ CLI encounters the compatibility issues between azure-core and azure-cli and emits the error: cannot import name 'case_insensitive_dict' from 'azure.core.utils'
To Reproduce
Two ways of reproducing the issue:

Install latest az cli
Install any package that depends on lower older version of azure-core

or

Install az cli (2.37.0 or lower)
Install cli ML extension 2.5.0. (ML Extension brings in the latest azure-storage-blob package that depends on latest azure-core=1.24.0).
az extension add --name ml --version 2.5.0

Expected behavior
CLI should not fail.

@jiasli for awareness

The dependency on azure-core was bumped by https://github.com/Azure/azure-cli/pull/22676.
It's ml's responsibility to use latest azure-core.
Latest azure-storage-blob-12.13.0.zip downloaded from https://pypi.org/project/azure-storage-blob/#files has "azure-core<2.0.0,>=1.23.1" in setup.py.
    install_requires=[
        "azure-core<2.0.0,>=1.23.1",
        "msrest>=0.6.21",
        "cryptography>=2.1.4"
    ],

ML has already shipped a mitigation for this issue in the following release 2.6.1 by pinning the azure-storage-blob. But this is one common issue that is being encountered outside the scope of the ML extension.
The failure may be encountered in 2 ways.

With the new az cli (2.38.0) wherever the user packages have direct or indirect dependencies on the older version of azure-core.
With older az cli (2.37.0 or less), if the user packages have direct or indirect dependencies on the latest azure-core. For e.g., using azure-storage-blob 12.13.0 with az cli 2.37.0 or less.

We are also seeing this on az cli 2.37.0 and the latest version (0.5.92) of aks-preview extension.
https://dev.azure.com/AzureContainerUpstream/Azure Workload Identity/_build/results?buildId=52370&view=logs&j=3a3ff92c-2ab0-5cd5-ecad-e283f5e1d802&t=6d5f3379-e684-5896-70a5-701deb97a928
Pinning aks-preview to 0.5.87 resolved it.

Bump as well as this is failing for me too.

failing for me, three.

failing for me, three.

i am using AMLs CI, so i just provisioned another CI and the problem goes away.  i just have to avoid installing other software that will pull that dependency back in... :-(

I am following this tutorial ->
https://learn.microsoft.com/en-us/azure/machine-learning/v1/tutorial-pipeline-python-sdk
Getting error in train.oy ->
azure-ml-error.txt
Can you please help to resolve.
Thanks

Also getting this issue with Azure ML notebooks.

Hi,
Is the issue is resolved? I'm also facing the same issue while importing a package.
Currently My azure-core is a version of 1.26.0 so while executing the module using this version of azure-core it throws me an error

So here by observing the error I get to know that module requires an azure-core of version <=1.22.1. So if downgrade the version to 1.22.1 or less than that, then I'm facing an error

did anyone have the solution how to resolve the error and successfully import the module?

authors: Uditanshu1612 afogarty85 delbert harneetvirk jiasli sarbaniAi sethreidnz sozercan yonzhan