feat(cheatcodes): add expect*Call cheatcodes

Component
Forge
Describe the feature you would like
Follow up of https://github.com/foundry-rs/foundry/issues/4072 for adding remaining expect*Call cheatcodes

[ ] expect*Call cheatcodes: similar to expectEmit, these let us specify the expected call with its callee and calldata. We use these less frequently, but I think they can be useful even for fuzzing tests.

[ ] expectRegularCall: Expect a call using the CALL opcode and specified parameters
[ ] expectStaticCall: Expect a call using the STATICCALL opcode and specified parameters
[ ] expectDelegateCall: Expect a call using the DELEGATECALL opcode and specified parameters
[ ] expectNoCall: Expect no calls to be made after this cheat code
[ ] expectCreate: Expects the deployment of the specified bytecode by the specified address using the CREATE opcode
[ ] expectCreate2: Expects the deployment of the specified bytecode by the specified address using the CREATE2 opcode

Additional context
No response

I would love to handle this issue. I will probably need the files that will be affected and where to draw inspiration from in the codebase.

Can I work on this, please?

May I take care of this?

@grandizzy hi! i'm interested in working on this :)

@anukul awesome, thanks! I assigned it to you

From the existing expectCall overloads, which is the ideal set of parameters to use for each  expect*Call cheatcode? 🤔
https://github.com/foundry-rs/foundry/blob/dabacecdc14d074a108c18f97d1e1f63ade37a37/crates/cheatcodes/spec/src/vm.rs#L930-L962
There is this option:
function expectRegularCall(address callee, uint256 msgValue, uint64 gas, bytes calldata data) external;
function expectRegularCall(address callee, uint256 msgValue, uint64 gas, bytes calldata data, uint64 count) external;

or the possibility of another function, something like:
struct CallType {
  Regular,
  Static,
  Delegate
}

struct ExpectCallOptions {
    CallType kind;

    // optional gas fields (0 = don't check)
    uint64 exactGas;
    uint64 minGas;
    // optional count (0 = expect at least once)
    uint64 count;

    // optional msg.value
    uint256 msgValue;
    // flag for ambiguous zero value fields
    bool checkMsgValue;
}

function expectCall(
    address callee,
    bytes calldata data,
    ExpectCallOptions calldata options
) external;

Somewhat related - https://github.com/foundry-rs/foundry/issues/8845, to make data optional


About pc.calculate_interactions and complete environment config

Dear authors,
Thanks for sharing this amazing work.
However, we met errors when we run pc.calculate_interactions():
Traceback (most recent call last):
File "/homre/miniconda3/envs/pc/lib/python3.8/site-packages/ loguru/_locks_machinery.py", line 29, in release_locks
def release locks():
File "/home/miniconda3/envs/pc/lib/python3.8/site-packages/gsd/_init__.py", line 24, in <lambda>
signal.signal(signal.SIGTERM，lambda n,f; sys.exit(1)
SystemExit: 1
Exception ignored in: <function release locks at 0x7fa895bcb940>
Traceback (most recent call last):File "/home/miniconda3/envs/pc/lib/python3.8/site-packages/loguru/_locks_machinery.py", line 29,in release_locks
def release locks():
File "/home/miniconda3/envs/pc/lib/python3.8/site-packages/gsd/ init .py", line 24,in <lambda>
signal.signal(signal.SIGTERM,lambda n,f: sys.exit(1))
SystemExit: 1

Can you suggest what to do?
And could you please provide the complete environment configs of posecheck? that would be helpful.

Hi Zerin
Thanks for your kind words and sorry for the delay in replying to your issue. I have not encountered that problem before but will look into it. (Although I suspect your python may be too old).
In the meantime, I have pushed the full environment config to the main branch.
Charlie


Reduce number of queries and make updates batched in SearchIndex

JIRA Ticket: https://jira.lyrasis.org/browse/FCREPO-3455
What does this Pull Request do?
Reduces the number of for loops with individual queries or inserts in favour of single batchs of multiple records.
How should this be tested?
The ol' @awoods batch ingest test would be best.
Interested parties
@fcrepo/committers

I should note I stole some lines from @awoods's PR (1 and 2)

Actually hold on to this. I'm still seeing some early RepositoryRuntimeExceptions, wondering if this is a thread-safe issue.

Ok so apparently main throws an Exception at the start of a JMeter run and this PR still throws the exact same Exception.
Not sure why but my guess is 2 requests being handled, neither sees the other and so they both try to add a resource. Seemingly one fails to insert but then would query the ID that the other inserted.
Not sure how we handle that or if we need to, so long as one has inserted the rdf type then the other should query the ID out of the database.
This does seem to speed up the addUpdateIndex method though. This PR is on the left and current main is on the right for 6 minutes of 2 thread container creation.

Ok went to using the database specific way of Ignoring conflicts, except H2 which has no way to do that. In which case I basically just update the existing record with the same URI.
No more multi-threaded exception appearing so this also handles https://jira.lyrasis.org/browse/FCREPO-3449

Showing addUpdateIndex p99 and average for 6 minutes each with MySQL, Mariadb, Postgres and then H2


Example missing the group GUID

Example 1 isn't a complete example.  The group listed in the description is not included in the command.  If a group is not specified, then this error is displayed "New-DeviceTenantRule : Missing an argument for parameter 'ExclusionList'. Specify a parameter of type 'System.Object' and try again."  The correct example would be something like this 'New-DeviceTenantRule -ExclusionList <GUID of Group>'

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

ID: ccb34850-6729-d166-a2d9-7d8dec89a24b
Version Independent ID: 2b9e2cd9-bea1-67f9-d2d0-e9bfe017e2e1
Content: New-DeviceTenantRule (exchange)
Content Source: exchange/exchange-ps/exchange/devices/New-DeviceTenantRule.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@damianscoles, I fixed it.
Thanks for the feedback.


update RxMoyaProvider.request to return a Single

Implements #1011, and changes the signature of RxMoyaProvider.request to return a Single<Response> instead of an Observable<Response>.
cc/ @andreyfel @damienrambout: would love both of you to sign off on this before it's merged in

This is breaking and should go in 9.0.0 and not master, right?

Also, some Cocoapods package versions don't match up with Cartfile anymore.

I think it would be better to create new Provider, like RxSingleMoyaProvider to make this change non-breaking. In this way we will support both Observable and Single. And it will be easier to migrate to the Single.

@BasThomas: In its current state, it is breaking. @BasThomas can you match the Cocoapods package versions that I missed?
@andreyfel: I don't know if adding another choice to a very simple module is a smart idea long-term. I feel as though we should either stick with Observable and not make this change, or embrace RxSwift's new semantics and publish Single. But not try to inelegantly solve both
After understanding the change, the easy path to migrate to the new RxMoya syntax will simply be for a consumer to extend RxMoyaProvider and supply a method that returns an Observable<Response>, which .asObservable()'s the new RxMoyaProvider.request

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

          1 Warning

:warning:
Consider adding supporting documentation to this change. Documentation can be found in the docs directory.

  Generated by :no_entry_sign: danger

This PR revert the changes introduced in #993... This can't be merge yet

I think we should first deal with #1013 (which is also reverting #993)

@AndrewSB please rebase

@AndrewSB can you rebase against 9.0.0-dev and reapply your changes? (See #1017) :wink:

All rebased! cc/ @gperdomor can you approve?
I need to fix a couple tests to get CI passing, working on them soon 😄

#993 is still reverted in this PR

Codecov Report

Merging #1016 into 9.0.0-dev will increase coverage by 0.44%.
The diff coverage is 60%.

@@              Coverage Diff              @@
##           9.0.0-dev    #1016      +/-   ##
=============================================
+ Coverage      73.25%   73.69%   +0.44%
=============================================
  Files             22       22
  Lines            729      726       -3
=============================================
+ Hits             534      535       +1
+ Misses           195      191       -4

Impacted Files
Coverage Δ

Sources/ReactiveMoya/SignalProducer+Response.swift
90% <0%> (ø)
:white_check_mark:

Sources/RxMoya/RxMoyaProvider.swift
43.58% <100%> (+1.48%)
:white_check_mark:

Sources/Moya/MoyaProvider.swift
90.9% <50%> (+6.16%)
:white_check_mark:

Sources/Moya/MoyaError.swift
31.81% <50%> (ø)
:white_check_mark:

Sources/Moya/MoyaProvider+Internal.swift
62.27% <66.66%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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

@gperdomor @AndrewSB Hey, I fixed the branch by cherry-picking all changes on top of 9.0.0-dev: https://github.com/Moya/Moya/commits/observable-single-9.0
We can:
1 - Open a new PR from that branch
2 - Push force to observable-single, meaning everyone will have to delete the branch locally and fetch again (but we keep this PR)
I'm ok either way 😄

Option 1 is more cleaner i guess

I'm not a user of RxSwift, but just cruising through their API (you know, trying to form an educated opinion), it looks like Single<MoyaResponse> IS the most analogous structure to represent a network request, unless the request is repeating, in which case, Observable would make sense. In the case of a repeating request however, it should be on the developer to format their signal in that way.
Realistically, I don't think we should not embrace this change just because our API already utilizes Observable, but rather note it as a breaking change and release.
Forcing people to make changes to existing code bases to implement the best practices from one of our dependencies for a new version should be expected, and as @AndrewSB mentioned, you can just add asObservable() if you're a client who wants to continue to use Observable.

Thank you for sharing your thoughts @justinmakaila!
@pedrovereza: I'm lazy, and I don't see the harm in #2, but feel free to go ahead with whichever one makes you more comfortable

@BasThomas @AndrewSB @gperdomor @justinmakaila @andreyfel
Hey I created #1020 to avoid more branch issues. Please continue the discussion in that PR and use branch observable-single-9.0 for new additions. I'll delete observable-singleto avoid confusions :wink:

Thanks Pedro 😊
On Wed, Mar 22, 2017 at 11:34 AM Pedro Vereza<EMAIL_ADDRESS>wrote:

Closed #1016 https://github.com/Moya/Moya/pull/1016.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Moya/Moya/pull/1016#event-1011047362, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADo1dLgc60B1bdVsvKubatVJR95BZ8QDks5roWmggaJpZM4MfFHB
.


feat:  messagebox

Title:
proposed implementation for a messagebox feature
Description:
closes https://github.com/hyperledger/aries-framework-go/issues/811
Summary:
Introduction of a messagepickup service for storing messages until and edge agent collects.
I'd like to credit @pfeairheller for the original implementation.
Since this violates the ~500 line PR rule I wanted to get it out early for discussion.
I am still evaluating what BDD tests might be needed and will mark this current PR as draft.
I am making a corresponding PR to aries-rfcs, to update the type values of messages.
https://github.com/hyperledger/aries-rfcs/pull/500

@m00sey I think it's headed in the right direction. I am afraid of the coupled getInbox/putInbox pairs in AddMessage and pullMessages, especially the latter. Looks dangerous and prone to data loss. I think a lock on theirDID is needed.

@m00sey I think it's headed in the right direction. I am afraid of the coupled getInbox/putInbox pairs in AddMessage and pullMessages, especially the latter. Looks dangerous and prone to data loss. I think a lock on theirDID is needed.

I added additional locks around each theirDID and a map to manage those mutex.
I am looking into why it thinks I have touched the additional six files, I don't see them in my Files Changed list and make checks passes locally.

@m00sey

@m00sey I think it's headed in the right direction. I am afraid of the coupled getInbox/putInbox pairs in AddMessage and pullMessages, especially the latter. Looks dangerous and prone to data loss. I think a lock on theirDID is needed.

I added additional locks around each theirDID and a map to manage those mutex.
I am looking into why it thinks I have touched the additional six files, I don't see them in my Files Changed list and make checks passes locally.

Sorry for the late reply. I think the code looks correct, but now I regret having suggested to use locks. The code gets so complicated.
But don't worry - we can merge this because it looks like it works without data loss. Just need to pass the checks and I think we can merge it.

Agreed locking has increased the complexity, open to other thoughts on how to block access to avoid data loss.

@m00sey please rebase on master

@m00sey please rebase on master

Hm, so I rebased using git rebase=true upstream master where upstream is git@github.com:hyperledger/aries-framework-go.git resolved the conflicts and pushed, I wasn't expecting the additional changes to be tracked in my PR...
Is there a different/preferred way? Apologies.

I'll work on the coverage today, I thought I had scraped past 85%, I am guessing it's a lines vs statements difference?
┌─[±][issue-811 → origin ✓][messagepickup][]
└─▪ go test -coverprofile=coverage.out && go tool cover -html=coverage.out
PASS
coverage: 87.0% of statements
ok  	github.com/hyperledger/aries-framework-go/pkg/didcomm/protocol/messagepickup	0.004s

It's the coverage on the patch (delta) that's holding this back. See the report here.

Title:
proposed implementation for a messagebox feature
Description:
closes #811

@m00sey Thanks for the pull request.
One minor note - This PR doesn't close #811 as this only implements service layer. We would need to add following to make this feature complete.

Store the messages when registered agent is unavailable
Integrate with framework
Client Layer
BDD tests

@rolsonquadras understood, I was overzealous. I will remove that from the description in order to keep this PR moving. I plan to address the subsequent parts in future PRs.

@m00sey thanks!


Question about the Locale function and AVS running under different area.

Hi AVS team,
I have questions about the "locale" defined in AlexaClientSDKConfig.json and related definition in AVS/Echo behaviors.
Q1 - The locale defined in AVS SDK, it seems only for change the "en-US",  "en-GB", "de-DE" value, but it seems do nothing with this "locale" value.  Will it do anything different while the "locale" value is different in configuration (eg. AlexaClientSDKConfig.json) ?
Q2 - Should I change different endpoint by different locale settings before SampleAPP start up, or Alexa server will change it by Event from LWA ?
Q3 - I need to contact with Sensory or KittAi to get different Alexa data model for different locale ? But I think the AVS SDK now does not change different KWD data model while local changed ?
Q4 - The Alexa services are bundled by use's account (user's address or country setting), not SampleAPP settings.  So while user changed their settings, SampleAPP will receive event from LWA to change locale automatically ?
Q5 - Should I need to change time zone (eg. the SampleAPP launch command: TZ=UTC) while the locale is not in States? or TZ=UTC is a fixed data, LWA will adjust it in cloud automatically ?
Sorry to raise so many questions here, please kindly help to have comments.

Hi @zeusshuang,
Q1: The value of locale in the AlexaClientSDKConfig.json is used if there isn't already a Settings database file available for the SDK to grab a setting from. When you change your locale, you are updating that database.
Q2: You can change the default endpoint to connect to through the json config file. If the service detects that another endpoint would better serve your device, a SetEndpoint directive will instruct your device to switch. See https://developer.amazon.com/docs/alexa-voice-service/system.html#setendpoint
Q3: If you are interested in different model files you should definitely consider contacting Sensory or KittAi.
Q4: Yes that seems to be correct. Again, see https://developer.amazon.com/docs/alexa-voice-service/system.html#setendpoint
Q5: TZ=UTC was being used for SDK-specific calculations. In a future release, we will be removing the dependency on that flag.
Hope that helps,
Fede

Hi @frozenberg ,
Thanks for the comments!!
For Q1 and Q4, I have some tests with SDK1.4.
I tried to change my account's address to different country, and while I question the "time", it's actually respond the local time according to my address.
However, I did not receive any settings change event (SetEndpoint ) from LWA by AVS log.
Should I enable any compile option for such events ?
And for Q2, to change a better endpoint, I think it will also detect by server site and SampleAPP will receive "SetEndpoint" by endpoint handler ?
Thanks,

Did you change your address through alexa.amazon.com?

Hi @frozenberg ,
Yes, I changed it from this site.
And I also check it by question "what time is it", it's actually changed to local time by different country and address.
But from AVS log, I did not receive any message from the log.

Hi @frozenberg ,
I have another question and would like to clarify.
How Amazon server respond to different language ? If device listen DE language, will it respond if the account is registered in Amazon UK ?  From my test, it will not respond if I play DE language to my US account but address is set to Germany.

Ok I have asked around and gotten some clarifications on certain things:

The locale setting determines what language/accent Alexa should speak with and what language/accent Alexa expects you to speak. All locales are available in all endpoints.

The endpoint you hit is determined by your account country settings.

The time that Alexa will report is based on your Timezone setting in your alexa.amazon.com portal. Have you checked that setting? (Not country/address)

Hi @frozenberg ,
Thanks for the comments, it's clear now.
We can close this ticket.


[20w18a-1.0.1] Saturation, light and smoker issues

A few issues I found with the 1.16 snapshot version.
The saturation doesn't seem right, changing the value in config doesn't seem to affect it.
All foods beside soups seem to give 10 saturation (soups 6), and with AppleSkin added they show huge values between 14 to even 54 for saturation.
The new plants give off light when planted, don't know if that's indended.
Fresh Tofu and Dough can't be cooked in a smoker.
Mod Version: TheVeggieWay_Fabric_20w18a-1.0.1
Fabric Version: fabric-loader-0.8.2+build.194-20w18a
Fabric API version: fabric-api-0.10.3+build.338-1.16

fixed in next update


fix: Error: opam package "melange-jest.dev" requires npm package "jes…

Fixes:
Error: opam package "melange-jest.dev" requires npm package "jest" with constraint "^27.0.0", but the version installed found in file "/node_modules/jest/package.json" is "29.7.0"

Thanks, @jakubrpawlowski!


t.maybe creates keys for undefined values

Version
3.2.2
Expected behaviour
const Foo = t.struct({ bar: t.maybe(t.String) });
new Foo({}); // Struct{}

Actual behaviour
new Foo({}); // Struct { bar: undefined }

Issue
The resolution of #183 makes it very difficult for me to upgrade our application to<EMAIL_ADDRESS>because our tests have expected data written in JSON files and you cannot define undefined in JSON.
JSON.stringify({ bar: undefined }); // "{}"

None of this would be a problem if the following Jasmine test would pass:
expect({ bar: undefined }).toEqual({});
// Expected Object({ bar: undefined }) to equal Object({  })

Possible Solutions
I can see two possible solutions to this problem:

Just don't create the key-value pair for undefined values in a t.maybe scenario.
Allow us to define a default value (like null or "") for a t.maybe scenario.

Unfortunately, I don't see a way to fix this w/o introducing another breaking change. Do you have a better suggestion?

Allow us to define a default value (like null or "") for a t.maybe scenario

Actually you can, from v3.2.0 (https://github.com/gcanti/tcomb/releases/tag/v3.2.0)
import t from 'tcomb'

const Foo = t.struct({ bar: t.maybe(t.String) }, { defaultProps: { bar: null } })

console.log(new Foo({})) // => Struct {bar: null}

Ahh, OK. Thanks.


Mergify: configuration update

This change has been made by @Rubix982 from https://mergify.io config editor.

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


Connection via Ethernet Module QJ71E71-100

Hi there!
May I check with you regarding setup I'm facing some issue to communicate with Python
So the current setup now is there is ethernet 1, 2 and 3 (All Ethernet) as follows

)
May I check with you what did I do wrong over here?
For my Python side,
pymc3e = pymcprotocol.Type3E()
pymc3e.setaccessopt(commtype="binary",network=3)
pymc3e.connect("<IP_ADDRESS>",7000)
Always encounter WinError 10060
Thanks in advance

Thank you very much for using pymcprotocol.
In fact, I have never connected to PLC via Ethernet Module.
So my answer would be just assumption.
Did you assigned <IP_ADDRESS> to Ethernet Module?
Can you show me what WinError 10060 says?
Best regards,

Oh the ethernet module itself ip is <IP_ADDRESS> and for the rest you can refer to the image attached below

I've exhausted all means to test out...

In your code, you are trying to access <IP_ADDRESS>, but Ethernet module is assigned <IP_ADDRESS>.
Can you check this problem.
I think this problem is not MCProtocol settings but IP address.
Please use ping command and confirm Ethernet module responses.

<IP_ADDRESS> is occupied by the ethernet module I'm able to ping it and confirm it response.
Furthermore, because it is occupied by the PLC itself if I try to connect it, it will deny my access so my only luck is to try to setup a secondary connection within it to access it
An Connection Refused Error [WinError 10061] stating no connection could be made because the target machine actively refused it

I guess it is not possible to connect via Ethernet module since once it is handshake with the PLC it will be always occupied and can only accept socket connection from other device. Hence, it is concluded that the its only possible via CPU. Thanks for assistance.


enh: configurable latex delimiters

Is your feature request related to a problem? Please describe.
OpenWebUI is able to render TeX markup when it's enclosed in double $ signs, such as $$y = f(x)$$. I did my best but failed to explain that to Llama-3. It still uses single $ once in a while.
Describe the solution you'd like
It would be nice to have a way to configure the renderer, so that single $ entries would also be treated as TeX markup. Even better if $ quotes would be automatically treated and correctly rendered as an inline markup.
Describe alternatives you've considered

Use ChatGPT... It just works.
Invent a prompt that would prevent a model from using single-$ styled formulas.

Additional context
Sample output: https://openwebui.com/c/korvin/340ca756-a00b-4408-8acc-bc0c39fbb426
Note that some formulas are syntactically correct but not rendered properly due to single $ quotation.
It looks even worse in the UI:

Me, too. Sometimes the math doesn't work

Sometimes the math doesn't work

https://github.com/open-webui/open-webui/pull/3930 Look at this. I tried to solve this problem

why not fix it?

why not fix it?

The version is not the same, the author can pay attention to the latest dev version after the fix, and provide corresponding examples so that the author can better fix

For me it breaks in version 0.3.16 still when models are using $$ without newlines. And if it uses align or equation environments, it would break also.

If told to do newlines with $$ then it's ok

Same issue, the tex rendering is not working:


Newly added project not showing on dev

Hi all,
Thanks for building this. Big Netlify here.
I'm busy trying to add a new headless CMS that we're building, but I find on my local machine that the project is not showing up after adding the relevant markdown file to content/projects. When I run the production build and serve locally it is showing, but it also shows an outdated version and not my latest changes. Seems like the caching is a bit sticky.
Even after deleting both the dist and tmp directories, it is not showing. Is this something that someone else has experienced as well? Any idea how to fix?

For some reason React Static (or at least the version used here, which may be outdated) doesn't update things well when changes only happen to content files locally. If you change a JavaScript file, especially while running the local development server, that tends to get things moving.


generateClassName is a performance bottleneck in Server Side Rendering

Due to the way how generateClassName currently works (murmur hash of json stringified stylesheet), it has become quite a bottleneck in the application that I'm working on. It easily takes up 30% to 50% of the whole server side render time.

In this part of the flamegraph (created with 0x), you can see the top time consumers to be mumurhash and v8's internal JSON.stringify. Everywhere it says (anonymous) it is using the function returned by createGenerateClassName.
Is there any way to speed this up? I know about the counter based implementation, but it doesn't work with SSR, as the class names end up being different. However, it did provide an average speed up of about 150ms taking the average rendering time from 470ms to 320ms.
My best guess is that it will likely require a new implementation that traverses the objects directly updating the hash as it goes, and uses an even faster hashing method (xxHash looks interesting).

We don't use a hash base solution anymore. What version are you using?

I'm on 3.9.4, because I didn't yet have the time to migrate to the 4.x releases.
I've backported both https://github.com/mui-org/material-ui/blob/master/packages/material-ui-styles/src/createGenerateClassName/createGenerateClassNameHash.js and https://github.com/mui-org/material-ui/blob/master/packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.js before filing the issue, and found that the counter based approach didn't work with SSR (in Next.js) in my case, as I did get different class names (different counter values) between SSR and client side rendering.
If it is supposed to work with SSR, and I'm just doing it wrong, I'll take that answer too.

As far as I know, we only starred using the hash base approach for the alpha version of the style package. The simplest would be to stope using it or to use v4.


Do not allow size to be set for "ROOT" volumes when creating VMs.

Rancher Version: Build form master
When creating VMs ( as standalone containers/ services) , currently user is allowed to pick a size for ROOT disk.
Since ROOT volume size is going to be always based off the image , we should not allow users to set a size for ROOT volumes. They should be allowed to set size only for DATA volumes.

Version - master 5/13
Verified fixed


Add testcase and fix for attributes deduplication in form and empty elements

This is an attempt to handle deduplication of attributes in form-elements and should fix #1949

(BTW, I am happy to make that change myself if you prefer, LMK.)

Thank you for responding to my PR. I took a quick look at the code path and I'm not familiar enough with the code to try any refactoring of the code path but I can certainly factor out the deduplication code.

When moving the deduplication code to it's own method, I realized that deduplication was not applied for empty tags either so I added another test case and fix for empty tags as well.

Thanks, merged!


"Aw, Snap!" page crashes

After clicking the "Start Rekognition" button, the webpage tries to refresh, and gives "Aw, Snap!" error.

Closing this issue due to inactivity as it appears to be an issue caused by third party software/extensions.


Added user and student endpoints.

Added the API routes needed for students, should all work as advertised.

lol the commas on Student.js:5 and Student.js:8 cause syntax error 😂


Reset upgrade

My customers tenant shows a Reset upgrade button. I don't see this mentioned in the documentation. Will clicking this have any affect on objects in production?

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

ID: 31f9c429-7db9-e07b-475b-88e01c605912
Version Independent ID: 194ca6f2-7356-804b-d342-b6b457ca5adf
Content: Errors and resolutions when upgrading previous version of Common Data Service.
Content Source: common-data-service/upgradecds/errors-resolutions.md
Service: commondataservice
GitHub Login: @JimDaly
Microsoft Alias: jdaly

The Reset upgrade button appears when a step fails and must be re-started.

Closing the issue.


[DocDB] ChangeFailoverPriority error

Hi @dmakwana
I was able to write this in Python:
 async_change = self.client.database_accounts.failover_priority_change(
            self.group_name,
            account_name,
            [{
                'location_name': self.region,
                'failover_priority': 0
            }]
        )

This leads to this payload:
[{"failoverPriority": 0, "locationName": "westus"}]

But ARM refuses the query:
{
	"code": "BadRequest",
	"message": "Unable to parse request payload. ActivityId: 41515b46-a6ad-11e6-a275-ecb1d756380e"
}

What do you think? Is the swagger leading to incorrect JSON payload? Or I miss some required parameter? Or  a bug in the Python serializer?
Thanks,

It was incorrectly modeled in the swagger file. The generated output should look like this:
{
  "failoverPolicies": [
    {
      "locationName": "West US",
      "failoverPriority": 1
    },
    {
      "locationName": "East US",
      "failoverPriority": 0
    }
  ]
}

I've created PR: #702 to address this.

PR merged with the fix.


Honor all contributors

Question
We have the good fortune to receive wonderfull help from the Stryker community. However, we've been pretty lousy in honoring them 😔. We need to change this 💖!
The question is, how do we want to do that? Who better to ask than our contributors themselves? Please (in no particular order) @JoshuaKGoldberg @ollelauribostrom @bharaninb @simondel @Archcry @mthmulders @brodybits @kmdrGroch @philippw @mshogren @sharikovvladislav @mscharley @tommilligan (and all the people I've forgot to include here (don't hesitate to add more)): How do you want to be honored?
There is a tool out there called all-contributors-bot than can add you're face to a readme file. Would you mind that? Since we have more than 1 readme file (1 per package), I suggest using the main readme file. However, I think we can also choose multiple readme files (or use the CLI tool to do that). So we can choose the main readme and the stryker core readme for example.
Other suggestions are welcome as well!

Looks cool!

I think we should have a nice group talk all together like we had one day with Nico and Simon :)

Haha I feel a bit silly being a tagged person here, given I've contributed almost nothing 😉
. Which is probably why I'm totally fine with the way things are now. The built-in https://github.com/stryker-mutator/stryker/graphs/contributors charts are fine with me.
README.md face mentions seem like a nice thing to do either way!

Haha I feel a bit silly being a tagged person here, given I've contributed almost nothing

I did it mostly for the future PR you're going to do regarding emoji support in the console reporter #1189 😁
All jokes aside, the bot is called "all-contributors-bot". I think you would qualify, amigo 🤠

Joshua, don't feel silly. My only contribution is doing maintenance stuff with TSLINT and ESLINT which is mostly "save, switch red lines, save, PR" ;D

I’d feel honoured.
On Sat, 12 Dec 2020 at 17:25, stale[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stryker-mutator/stryker/issues/1921#issuecomment-743779771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADKNFOYEIF3MVRI3SX6STLSUOKQVANCNFSM4J2JRDYQ
.

I have made some contributions years ago but I wouldn't say I am actively contributing towards Stryker at this point in time. I would not feel comfortable being credited for contributing since I haven't made a lot of contributions lately.


If you this action, say thanks here!

Here is the place to say thank you to folks who are working hard on this project.
« One of the greatest ways to show your appreciation to open source projects you enjoy is to open an issue that let people say thank you »
Disclaimer: I don't have any kind of connexion or personal interest with maintainers(s) of this project. Pure gratitude here.
Cheers!

Good idea, and I love this project. Thanks @GregBrimble!


Link broken in building.md

Describe the bug
The link for using the depth engine in the Linux Dependencies section is broken in https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/develop/docs/building.md. When I click it it shows 404 error.

Desktop (please complete the following information):

OS with Version: Ubuntu 18.04
SDK Version:  Latest

Thanks, its updated now.


Netty Inconsistent results for Asynchronous requests

Hi Everyone,
I am new to Netty and I am using Netty-4.0.30 version. I am writting a small application which sends some messages from client socket to server socket and expects a response back from server.
I am sending asynchronus requests to a server socket from a range of client sockets. But in few scenarios the time taken to complete/receive responses from server for the entire range of client sockets is taking 10 times  greater than the actual time.
My Client Handler extends ReadTimeOutHandler and my server handler extends ChannelInboundHandlerAdapter.
Note: I am considering only success connections.
Example: 100 asynchronus client requests to a server socket will be servered in approximately 300-400 milliseconds.
But, In some cases, it takes 3000-4000 millis to serve 100 success client requests. More over it is unpredictable.
I am getting consistent results if I send the requests synchronusly.
Can somebody tell me if it is a unresolved bug in Netty? Or What is the reason behind this inconsistent behaviour by Netty for asynchronus requests?
Thanks in Advance.

@maheshbabu1907 please use stack overflow for questions, this is for bug-reports only.


Fix tiles

Also updated the version of the frontend-maven-plugin and the version of node to the latest LTS release.


Aws test container

Preliminary code which expose the current problems during test containers setup

DynamoDB discovery is working, you could try it.

At the moment we are creating dependencies for our selves (clients), so that it becomes difficult to inject localstack clients into the code. We need to expose private methods. But that also not working. Even deeper we also create such dependancy (S3 discovery is not working due to that perspective)
Otherwise with current clients we are trying to reach the real AWS.
1.1. I'm thinking about lightweight ServiceDiscovery pattern, but we need to keep clients being configured for different Regions being requested (e.g DynamoDB_AWS_GLOBAL / DynamoDB_US_WEST_1 )

Seems like AWS Java SDK doesn't provide possibility to override AWS Endpoint globally for all clients link

For a demo purpose we could setup localstack separately but we need to bypass localstack docker URL to reach it. Meanwhile there no possibility for that in code

Proposal:
We could create our AWS Clients based on env variable being passed on the stage of execution - > if nothing passed fallback to the default one - https://aws.amazon.com/
[To not merge yet]

Added:

CF update-stack command usage for dynamic resource configuration for various tests using readable .yml template format
Fixed us-east-1 bucket bug processing
Added PR review fixes based on suggestion

Builded and tested against the real AWS Services


refactor(eventStack): make eventStack immutable

Why?
Sometime ago I tried to attack #1473, I've fully reworked the Sidebar component and docs. But then I found a strange problem when tested the component: event handlers simply called before they should be called. I've found the problem, it was in the mutable array of handlers in the EventTarget.
This PR performs the deep refactoring and adds more test coverage for internals of the eventStack.
The easiest way to show problem: just clone feat/sidebar-closable-property  branch and try to run the Sidebar examples without & with these changes.

Codecov Report

Merging #2837 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2837      +/-   ##
==========================================
- Coverage   99.74%   99.74%   -0.01%
==========================================
  Files         160      160
  Lines        2777     2773       -4
==========================================
- Hits         2770     2766       -4
  Misses          7        7

Impacted Files
Coverage Δ

src/behaviors/Visibility/Visibility.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Merging for progress.  Any doc tweaks can happen in another PR 💪

Released in<EMAIL_ADDRESS>


Hubitat nodes crashing Node-RED

Hi!
I am hitting an issue with (some) node-red-contrib-hubitat nodes crashing node-RED, requiring a --safe restart and disabling flows until i can get it to stay working. The following error appears in an SSH terminal during the crash, grateful for any guidance to identify the culprit:
24 Nov 08:51:40 - [info] Started flows
24 Nov 08:51:40 - [red] Uncaught Exception:
24 Nov 08:51:40 - TypeError: Cannot read property 'attributes' of undefined
at HubitatDeviceNode._inputCallback (/home/bkdfkup/.node-red/node_modules/node-red-contrib-hubitat/nodes/device.js:171:56)
at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:203:26
at Object.trigger (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/hooks.js:113:9)
at HubitatDeviceNode.Node._emitInput (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:195:11)
at HubitatDeviceNode.Node.emit (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:179:25)
at HubitatDeviceNode.Node.receive (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:476:10)
at Immediate. (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:657:52)
at processImmediate (node:internal/timers:463:21)
at process.topLevelDomainCallback (node:domain:144:15)
at process.callbackTrampoline (node:internal/async_hooks:127:14)

OK, i have narrowed it down to this only occurring if "Inject once after 0.1 seconds, then" is enabled in the inject node. If this is disabled, all works as expected, with the Hubitat node updating its values every 1 second. It seems odd that the initial injection is having an impact.

Fixed in 1.4.2 :smiley:

Thanks very much!!! Will test tonight.


View for propose-downstream

I also added fake data for propose-downstream job because dashboard-stg can't see propose-downstream jobs at all and I guess we will be developing the Propose Downstream part in dashboard in future.
Current solution how to "insert" the fake data to dashboard-stg is really bad :grinning:  You need to pass this json file to corresponding jsonToRow function. e.g. here

Propose downstream demo:
https://user-images.githubusercontent.com/70757578/157068611-10614fbe-e7af-44d3-a548-24527fe95ec8.mov
Successfully submitted target demo:
https://user-images.githubusercontent.com/70757578/157068651-fa16f24a-bb17-44fd-8b49-7bff045ab9ab.mov
Running target:

Fixes #155
Merge after packit-service#1337

You can view information about ongoing propose-downstream jobs via our dashboard.

Just a note for the examples, we don't run propose-downstream for PRs, but that's just a detail. Otherwise, the views will be really handy! I am really looking forward to it!

I know but we have issue packit-service#1293. Don't this one mean that we will have PR which triggers propose-downstream?

I know but we have issue https://github.com/packit/packit-service/issues/1293. Don't this one mean that we will have PR which triggers propose-downstream?

No, I don't see it being useful -- mainly branch pushes or releases are relevant. And maybe issues or something else used for triggering the failed run.


Chore/java17: Upgrade Gradle to 8.1.1 to build with Java 17

Upgrade Gradle and associated gradle plugins.
Compile with Java 17 but keep Java 11 target compatibility for now.
Covers DEV-320

Repo error... Sorry


Update certs

Codecov Report

Merging #1397 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1397   +/-   ##
=======================================
  Coverage   90.01%   90.01%
=======================================
  Files         121      121
  Lines        8406     8406
=======================================
  Hits         7566     7566
  Misses        550      550
  Partials      290      290

Continue to review full report at Codecov.

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


Output logs to stdout instead of stderr

Previously logs were sent to the same writer as errors which was
using os.Stderr, or the user had the option to discard all logs.
This change continues to send errors to os.Stderr, but uses os.Stdout
for logs. Users can still discard logs using -silent flag, or redirect
output themselves.
This allows me to run the application via cron with ghbackup [opts] >> /var/log/ghbackup and have cron email me any errors but I can still keep the logs.

thanks @bradleyfalzon, totally reasonable to do it this way.


OmniSharp Agenda » Meeting Monday April 3rd, 2017 @ 18:00 UTC

PST (UTC-8)
EST (UTC-4)
London (UTC+1)
Zürich (UTC+2)
Helsinki (UTC+3)
Sydney (UTC+11)

11:00 AM
2:00 PM
7:00 PM
8:00 PM
9:00 PM
5:00 AM

Meeting info
TBD -- We need a new skype meeting last time @dmccaffery helped out. -- @sayedihashimi @DustinCampbell
Agenda
If you can think of any more agenda items, feel free to edit the issue (if you have permissions) or just comment on this thread and we'll make sure to group them up before the meeting.
Also feel free to discuss any agenda items early as part of this issue, we can make sure to recap during the start of the meeting, and may cut down on the time we have to spend on some of them.
.NET Foundation
We are on track to join the foundation.  The initial list of projects to join are:

omnisharp-roslyn
omnisharp-node-client
generator-aspnet
OmniSharp.github.io
omnisharp-atom
omnisharp-vscode

Additional ones will be on an as required basis (feel free to correct me if I'm wrong @jongalloway)
Transition, things will still be pretty much the same.  We will be enabling CLA signing on the above repos, but beyond that nothing should really change.  Going forward the foundation will help us keep the project going and provide us the tools we need to keep moving forward ( mac builds anyone? 😄 ).
Things we (I?) need to get together:

List of committers with > 2500 lines of code or more.

(In progress)

Get those committers accurate contact information (Name and current email)

New Project System
Anything to update?
Language Server Protocol

Currently working on an implementation of LSP in C#.
Available @ https://github.com/david-driscoll/csharp-language-server-protocol
I have wired in the models, and gotten them to serialize nicely
Next step is setting up the server to communicate over Stdio, and properly shuffle Requests / Responses / Notifications.
Trying to be heads down on this, to better support other editor implementations such as Eclipse, Eclipse Che, etc.  omnisharp-node-client is a great alternative at the moment however something that is more standalone is more ideal.
I have a feeling LSP will be in waves as we try to move our current endpoints over to it, and replace the current ones with shims.
We need a full plan going forward at some point for sure.

OmniSharp-atom

Trying to find time to sit and solve the issues surrounding this... I have a new computer, so it'll be easier to handle.  Still splitting time between this LSP, and other work obligations.
Some problems are left unresolved.
My hope is that this can be upgraded once atom supports a subset of LSP,  @damieng 😉

Atom-LangaugeClient

https://github.com/OmniSharp/atom-languageclient
The goal is to get this up to the feature support of OmniSharp-Atom, and then work on UI / Stability before major movements.
The atom team has reached out for some information, so there may be some more moment behind this.

OmniSharp-node-client

Added custom endpoints to accommodate OmniSharp features that the language server protocol doesn't support.
LSP 3 support soon

OmniSharp-vscode

Updates? Progress? Goals?
Looking at LSP as a possible option in the future

OmniSharp-vim

Any information / updates?

OmniSharp-emacs

Any information / updates?

cc @OmniSharp/all
Additional agenda items?
Either update the issue, or add them in the comments below!

Contributor List
OmniSharp-roslyn

@DustinCampbell
@david-driscoll
@nosami
@troydai
@filipw
@jrieken
@davidfowl
@Yantrio

OmniSharp-vscode

@DustinCampbell
@eamodio
@jrieken
@gregg-miskelly

OmniSharp-atom

@david-driscoll
@Mpdreamz

OmniSharp-node-client

@david-driscoll

aspnet-generator

@peterblazejewicz
@aeschli

OmniSharp.github.io

@Mpdreamz
@peterblazejewicz
@shanselman

List of committers with > 2500 lines of code or more.

this is an awkward threshold, you could add a single binary file into the repo and have tens of thousands of lines contributed. Shouldn't this be based on #contributions?

I feel that "committers" is a misleading term.   Each project also had founding members which saw it reach a certain point for the initial PoC / announcement...
It is difficult to use a metric to determine real value.  In my opinion number of contributions is equally flawed.  Github already does a brilliant job of showing the history of activity - is this not enough?
I guess we need to ask, what are we trying to do?  Promote and praise a select few committers that will be arbitrarily determined from a group of people who all made it work, using a methodology that is potentially flawed?  Or highlight who the people are to go to if you want to know who is actively devoted to the project and are spending time today to keep it alive?
I feel these are two very different things.  (and much respect to you guys who are keeping it alive!)

@stephen-james: I think this is for the documentation for joining the .NET foundation. I don't believe it's about promoting/praising people or creating a leaderboard or anything like that.

@stephen-james Dustin is correct. Those names are based on who has
significant commits today or in the past. Jon said anything over 2500 lines
or so, and your name lands there.
On Thu, Mar 30, 2017 at 9:26 AM Dustin Campbell<EMAIL_ADDRESS>wrote:

@stephen-james https://github.com/stephen-james: I think this is for
the documentation for joining the .NET foundation. I don't believe it's
about promoting/praising people or creating a leaderboard or anything like
that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/OmniSharp/issues/17#issuecomment-290409981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNdpeoU7hr3pTKEC3Er-FnMs4dMCTf2ks5rq62ggaJpZM4Mtwbb
.

--
Thanks,
David

is the emacs and vim stuff not going into the foundation?

@filipw @david-driscoll @david-driscoll @DustinCampbell Correct, this isn't about giving anyone any additional credit, ownership, etc., it's just a general cutoff on who should sign off. I checked in with our legal adviser (who is absolutely awesome, knows open source, etc.) and we came up with that as a general guideline. The goal is to get a good level of confidence that:

The project "owners" (as your project defines it) are okay with joining the foundation
Nobody is going to pop up and say "Wait a minute, I wrote the transmogrifier component and you know, I actually stole it from my work..." or something

It's definitely not an exact science or a rigid rule, we're just trying to do due diligence here.

The project "owners" (as your project defines it) are okay with joining the foundation

I should be added for generator-aspnet based on the above.

Hey @eamodio! Did you ever imagine that committing the full lodash TypeScript definition file (18,545 lines) and removing it in your very next commit would get you included here? Nice work!  😃

@jchannon not yet known at this time.  I don't think there is any specific reason they can't join however we're not usually that connected to the developers over on those repos.  When I opened discussions, I didn't want to make any assumptions about what they would want to do.   @jongalloway can correct me, but additional projects can join over time as things move forward.

@DustinCampbell lol -- yeah, when I saw my name here, I was really confused until I went back into the commits and ooohh. But hey I wasn't going to say anything ;)

Ah thanks for clarifying that!  I was missing context :)

I will send Skype meeting details -- least I can do. :)

@eamodio @DustinCampbell @david-driscoll We can definitely add and remove people from the list of signers on your recommendation. We figure that some big adds / removes are libraries, we really just can't look at commits for every project that's joining, and figure the project leads are much more qualified to evaluate than we are, anyways.

@jongalloway @DustinCampbell @david-driscoll if it makes things easier/better feel free to take me off the list -- if not, I'm perfectly happy to sign anything needed

I will send Skype meeting details -- least I can do. :)

FWIW, I already sent a Skype meeting to @david-driscoll the other day.

I notice Atom is on the agenda - would like to join and let the team know
where we are at with LSP.
On Fri, Mar 31, 2017 at 10:40 AM Dustin Campbell<EMAIL_ADDRESS>wrote:

I will send Skype meeting details -- least I can do. :)
FWIW, I already sent a Skype meeting to @david-driscoll
https://github.com/david-driscoll the other day.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/OmniSharp/issues/17#issuecomment-290779169,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHQp3vCezYsNUkOwFxH_UWWNykJtL_eks5rrTpvgaJpZM4Mtwbb
.

@eamodio we can probably remove you if that was the only contribution.  I just went against the github changes thingy as a quick way to get the list.  I didn't actually go look into everyones commits just yet :slightly_smiling_face:.

@dustincampbell ... way to be an over achiever. :-P

@sayedihashimi can we finally work to get scaffolding off the ground? I'd also love to work on expanding templating support to allow external sources.

@damieng you are welcome to join! 👍

can we finally work to get scaffolding off the ground? I'd also love to work on expanding templating support to allow external sources.

Let's chat more during the meeting. I should be able to attend.

Updated with meeting link / number.


typo's in example docs README.md

https://github.com/microsoft/AzureADToolkit/blob/main/README.md
Connect-MgGragh -Scopes Application.Read.All
schould be
Connect-MgGraph -Scopes Application.Read.All
and
Build-AzureADAppConsentGrantReport -ReportOutputType ExcelWorkbook -ExcelWorkbookPath C:\temp\export.xlsx
should be
Build-AADToolkitAppConsentGrantReport -ReportOutputType ExcelWorkbook -ExcelWorkbookPath C:\temp\export.xlsx

I just submitted PR #17 and then noticed that a PR has already been submitted (#15) with fixes for those typos. Pretty sure this isn't being maintained any more, but it might be nice to still see final fixed merged before it gets archived. :)


Update migration document

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1669

Relevant Lines:
1720

💛  - Coveralls


refactor: use lodash.memoize for log cache

Instead of rolling our own basic caching use lodash.memoize. It is a minimal dependency and makes the code cleaner.

Coverage remained the same at 100.0% when pulling 38e9855698dab22b6d73f6555807b373fc4961b8 on refactor-use-lodash-memoize-for-log-cache into 156e0d02904bdf0071b5a8d7779f3bce37a7f3ea on main.

:tada: This PR is included in version 1.0.13 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Update a Github dependency with --precise <short_id> fails

Problem
Updating a Github dependency with a short commit id fails with such log:
error: Unable to update https://github.com/rust-lang/regex#837fd85

Caused by:
  object not found - no match for id (837fd85000000000000000000000000000000000); class=Odb (9); code=NotFound (-3)

Steps
cargo new test-cargo-precise
cd test-cargo-precise
cargo add --git https://github.com/rust-lang/regex regex
CARGO_LOG=trace cargo update -p regex --precise 837fd85

Resulting cargo update log:
   0.000038417s TRACE cargo: start="2023-12-21T07:57:53.908041000Z"
   0.000538542s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_ALIAS_UPDATE", parts: [("alias", 5), ("update", 11)] }
   0.000570375s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_TERM", parts: [("term", 5)] }
   0.000589250s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_NET", parts: [("net", 5)] }
   0.001122417s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_HTTP", parts: [("http", 5)] }
   0.001523083s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_BUILD", parts: [("build", 5)] }
   0.001558208s TRACE cargo::util::toml: read_manifest; path=/Users/julienenoch/tmp/test-cargo-precise/Cargo.toml; source-id=/Users/julienenoch/tmp/test-cargo-precise
   0.001857042s DEBUG cargo::core::workspace: find_members - only me as a member
   0.002212917s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_PATCH", parts: [("patch", 5)] }
   0.002268583s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_REGISTRY_INDEX", parts: [("registry", 5), ("index", 14)] }
   0.002286292s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_REGISTRIES_CRATES_IO_PROTOCOL", parts: [("registries", 5), ("crates-io", 16), ("protocol", 26)] }
   0.002298250s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_REGISTRIES_CRATES_IO_PROTOCOL", parts: [("registries", 5), ("crates-io", 16), ("protocol", 26)] }
   0.002305875s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_REGISTRY_INDEX", parts: [("registry", 5), ("index", 14)] }
   0.002316875s TRACE cargo::util::config: get cv ConfigKey { env: "CARGO_SOURCE", parts: [("source", 5)] }
   0.002328917s DEBUG cargo::core::registry: load/missing  https://github.com/rust-lang/regex#837fd85
   0.002347417s DEBUG cargo::core::registry: loading source https://github.com/rust-lang/regex#837fd85
   0.002353417s DEBUG cargo::sources::config: loading: https://github.com/rust-lang/regex#837fd85
   0.002360000s TRACE cargo::core::source_id: loading SourceId; https://github.com/rust-lang/regex#837fd85
    Updating git repository `https://github.com/rust-lang/regex`
   0.009446625s TRACE cargo::sources::git::source: updating git source `GitRemote { url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("github.com")), port: None, path: "/rust-lang/regex", query: None, fragment: None } }`
   0.010665208s DEBUG cargo::sources::git::utils: attempting GitHub fast path for https://api.github.com/repos/rust-lang/regex/commits/837fd85000000000000000000000000000000000
   0.225184458s DEBUG cargo::sources::git::utils: skipping gc as there's only 2 pack files
   0.225689625s DEBUG cargo::sources::git::utils: doing a fetch for https://github.com/rust-lang/regex
   0.226630292s DEBUG cargo::sources::git::utils: initiating fetch of ["+refs/heads/*:refs/remotes/origin/*", "+HEAD:refs/remotes/origin/HEAD"] from https://github.com/rust-lang/regex
   0.716648583s DEBUG cargo::sources::git::utils: attempting GitHub fast path for https://api.github.com/repos/rust-lang/regex/commits/837fd85000000000000000000000000000000000
   0.739785417s DEBUG cargo::sources::git::utils: skipping gc as there's only 0 pack files
   0.739872500s DEBUG cargo::sources::git::utils: doing a fetch for https://github.com/rust-lang/regex
   0.740022625s DEBUG cargo::sources::git::utils: initiating fetch of ["+refs/heads/*:refs/remotes/origin/*", "+HEAD:refs/remotes/origin/HEAD"] from https://github.com/rust-lang/regex
   2.332392833s DEBUG cargo: exit_with_error; err=CliError { error: Some(Unable to update https://github.com/rust-lang/regex#837fd85

Caused by:
    object not found - no match for id (837fd85000000000000000000000000000000000); class=Odb (9); code=NotFound (-3)), exit_code: 101 }
   2.332410958s DEBUG cargo: display_error; err=Unable to update https://github.com/rust-lang/regex#837fd85

Caused by:
    object not found - no match for id (837fd85000000000000000000000000000000000); class=Odb (9); code=NotFound (-3)
error: Unable to update https://github.com/rust-lang/regex#837fd85

Caused by:
  object not found - no match for id (837fd85000000000000000000000000000000000); class=Odb (9); code=NotFound (-3)

Possible Solution(s)
No response
Notes
This Github API URL used by cargo returns an error:
https://api.github.com/repos/rust-lang/regex/commits/837fd85000000000000000000000000000000000
While the same but with short commit id succeeds:
https://api.github.com/repos/rust-lang/regex/commits/837fd85
What's strange is that I successfully used such cargo update -p <dep> --precise <short_id> few weeks ago.
Could it be that Github changed its API ?
Version
cargo 1.74.1 (ecb9851af 2023-10-18)
release: 1.74.1
commit-hash: ecb9851afd3095e988daaa35a48bc7f3cb748e04
commit-date: 2023-10-18
host: aarch64-apple-darwin
libgit2: 1.7.1 (sys:0.18.0 vendored)
libcurl: 8.1.2 (sys:0.4.68+curl-8.4.0 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1u  30 May 2023
os: Mac OS 14.1.2 [64-bit]

--
Also same issue with:

cargo 1.71.0 (cfd3bbd8f 2023-06-08)
release: 1.71.0
commit-hash: cfd3bbd8fe4fd92074dfad04b7eb9a923646839f
commit-date: 2023-06-08
host: aarch64-apple-darwin
libgit2: 1.6.4 (sys:0.17.1 vendored)
libcurl: 8.1.2 (sys:0.4.61+curl-8.0.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1t  7 Feb 2023
os: Mac OS 14.1.2 [64-bit]

Got an impression that @Eh2406 just talked about this somewhere. @Eh2406 do you remember anything?

Digging into the code, I see this completion with 0s of short commit id comes from usage of git2::Oid::from_str(s) in SourceId::precise_git_oid().
It somehow ends up to be used in github_fast_path(), probably after conversion from git2::Oid to GitReference::Rev(String). Possibly this one ?
Could the regression come from https://github.com/rust-lang/cargo/pull/12849 ?
But that wouldn't explain why the issue also occurs with cargo 1.71.0 that was release before this PR.

Good finding! Thank you.
I've tested several toolchains. Starting from 1.46.0 Cargo contains this bug, which contains the PR https://github.com/rust-lang/cargo/pull/8363 that you observed the potential bad commit. The Cargo started using Oid::from_str to parse precise field since then:
https://github.com/rust-lang/cargo/blob/ddc27999c17c55170e1812b50d27121cf43894ee/src/cargo/sources/git/source.rs#L35-L37
The zero-padding behavior is a documented behavior in libgit2 like from the beginning, so not a dependency issue.
It might or might not be GitHub has changed the API. I cannot tell, as Cargo had no such a test exercising --precise <SHA> until recently. And that doesn't even test against short ID.
Feel like SourceId::from_url has an assumption that precise for Git source is always a valid long-enough Git SHA (the format is opaque to cargo users btw). One fix I can think of is comparing if the value of --precise is a hex string of 40/64 characters here, and give a nice error if not. This is only a fix on the surface, if we find more commands have this kind of bug, we might want to push the fix down to lower-level.

One fix I can think of is comparing if the value of --precise is a hex string of 40/64 characters here, and give a nice error if not.

I will provide a PR to fix it based on this

This is only a fix on the surface, if we find more commands have this kind of bug, we might want to push the fix down to lower-level.

This is worth a look, I will check the relevant code by the way, once there is any feasible plan I will make a corresponding plan
@rustbot claim

One fix I can think of is comparing if the value of --precise is a hex string of 40/64 characters here, and give a nice error if not.

If possible I would like to still have the possibility to use --precise with short SHA.
As a use case in Zenoh: there are some plugins (shared libraries) for which the dependency to the zenoh crate must be the exact same commit than the hosting binary (to avoid ABI incompatibility). The short commit id can be retrieved via --version that return the result of git describe.
Using this short commit id in --precise would avoid the user to search for the long commit id.
I think a solution could be the following:

github_fast_path() could trim the extra 0s from the GitReference::Rev(rev) before querying https://api.github.com/repos/{username}/{repository}/commits/{rev}.
Thus the query will succeed with short SHA. The long SHA is returned in FastPathRev::NeedsFetch(oid_to_fetch).
Then the fetch() operation could return this oid_to_fetch returned by github_fast_path() as an Option<Oid>
Finally, in checkout(), if fetch() returns Some(rev) this rev is the long SHA and should be tested if contained in db

I tested such a patch here, and it seems to work.
What do you think?

Thanks for looking into the issue! The effort is much appreciated :)
However, there are probably two things we need to take care of:

The patch seems for GitHub only. I would like to see a general fix, as this issue is not GitHub-specific. GitLab or even a local git repository has the bug.
Changing locked_rev is not desired, as the new rev might not be the same as the old one, which we lose the meaning of "locked". Git short hashes can also be generated deliberately, and it doesn't seem too safe to trim and query over network.

That said, it doesn't mean we cannot support short hashes. We need to find a reliable way to pass down the value from --precise, and get it resolved to a full SHA. If the solution is not yet ready, for now we can give a nice message of "short hash not supported".

Understood, that makes sense.
I think the root of the issue is that the conversion from short SHA to git2::Oid leads to a 20 bytes SHA completed with 0s that cannot be found in the git2::Repository via call to revparse_single().
I made some tests with git2:
revparse_single() accepts short SHA and returns the full SHA. It detects short SHA collisions, returning such this error message: "ambiguous OID prefix - found multiple offsets for pack entry". So I think it's safe to use it to resolve a short SHA into a long SHA before storing it as locked_rev.
Actually,  GitDatabase::resolve(&self, r: &GitReference) uses it and will return a Oid containing the long SHA.
This call to GitDatabase::resolve() for long SHA retrieval could be done in [GitSource::new()] as a replacement to source_id.precise_git_oid() call. But this requires to create the GitDatabase here, while it's only created in GitSource::block_until_ready() so far. Not sure if it's a problem.
An alternative is to retrieval the long SHA in GitSource::block_until_ready(), just after GitDatabase creation. No need to replace self.locked_rev, but just to use the retrieved long SHA instead in the following match (self.locked_rev, db)

I think the root of the issue is that the conversion from short SHA to git2::Oid leads to a 20 bytes SHA completed with 0s that cannot be found in the git2::Repository via call to revparse_single().

Yeah. Totally agree on the root cause.
There seems to be an “implicit assumption” that a git SourceId has a precise field of a full SHA. cargo update is an exception that makes use of --precise to have a transient precise value presenting a arbitrary git revision. It would eventually become a full SHA when the revision is resolved.
The proposed solutions aren't wrong, though I would like to see locked_rev to be a type that represent a "revision", so we could have either full SHA (oid), or an arbitrary git revision. That would also make the behavior aligned to the doc:

--precise precise
When used with spec, allows you to specify a specific version number to set
the package to. If the package comes from a git repository, this can be a git
revision (such as a SHA hash or tag).

BTW, I accidentally have a working patch of this during code exploration. I may post a PR later but feel free to propose more better solutions :)

One fix I can think of is comparing if the value of --precise is a hex string of 40/64 characters here, and give a nice error if not.

I will provide a PR to fix it based on this

This is only a fix on the surface, if we find more commands have this kind of bug, we might want to push the fix down to lower-level.

This is worth a look, I will check the relevant code by the way, once there is any feasible plan I will make a corresponding plan
@rustbot claim

Sorry, I haven't started this work yet.  It's nice to see a better solution being proposed. :thumbsup:

Oops. I didn't realize this is claimed. Sorry for that, @linyihai 😔
Actually I was trying to provide guidance but ended up writing a fix

Oops. I didn't realize this is claimed. Sorry for that, @linyihai 😔
Actually I was trying to provide guidance but ended up writing a fix

The content to be changed is already very different from what I have been exposed to before,  So feel free to continue it.  Your PR is also a good guidance for me.

BTW, I accidentally have a working patch of this during code exploration. I may post a PR later but feel free to propose more better solutions :)

You PR is more advanced than my proposal. I agree that having a Revision enum that can be a GitReference to be resolved when required is more accurately reflecting reality. Nice job! 😃


How to work with mutations with foreignkeys

Hi Bellini,
I have some problems, as always, I'm sorry.
I don't think it should be an issue, but maybe you can show me in one sentence how to make things better/easier/properly?
I am trying set some fields + a ForeignKey in the Create Mutation.
mutation createMapService {
  createMapService(input: {url: "https://bbbb.eu", mapSet: 5}) {
    pk
  }
}

As I see here: https://strawberry.rocks/docs/types/object-types I define the field: map_set: "MapSet" (Im using "" because the MapSet type is defined in my code later).
This works in another scenario (without strawberry-django-plus), but with strawberry-django-plus the mutation fails and I can find this code in strawberry_django_plus/mutations/resolvers.py, line 276.
        elif isinstance(field, models.ForeignKey) and isinstance(
            value,
            (ParsedObject, strawberry.ID),
        ):

This fails (isinstance() arg 2 must be a type, a tuple of types, or a union) which comes I believe from the comparision with strawberry.id. I can the code here make perfectly good for my goals - type() to prevent the error, int to allow plain id).
        elif isinstance(field, models.ForeignKey) and isinstance(
            value,
            (ParsedObject, type(strawberry.ID), int),
        ):

However I am really week in typing in python, so I don't know if such change is acceptable.

Seems it works for me with call mapSet: 5 without this int I mentioned earlier too.
So just such code change works:
        elif isinstance(field, models.ForeignKey) and isinstance(
            value,
            (ParsedObject, type(strawberry.ID)),
        ):

Seems without int and with int it works identical (the instance is created), however if int is used, then the elif... branch is triggered, otherwise (without int) it is skipped.

Hello, just jumping in. Are you using the latest version? Release 1.20.2 has a fix just for the issue you're running into.


add macros examples

Wanted to make some lessons for macros, since I've seen enough confusion about those. I added some hints; do you think they're good-but-not-direct enough?
I haven't added the examples to the readme, but that should be simple enough. I couldn't get prlink to build, though. >_>

Just added one more simple example that still doesn't have to get into what matches what. I figure this can be kept simple, and if people want to know more about macros they can check the book or TLBORM.

Love it!! Nice and gentle :) I think the hints are perfect! 🌺

I couldn't get prlink to build, though. >_>

i got u fam!!!!


Add support to configure an HTTP proxy

Add a HttpHandler to the client options so the user can configure a HTTP proxy

Are HTTP proxies used in production environment or only for development?
Few options for HTTP proxy support are

Customizable IWebProxy
HttpHandler (similar to V2): Some ambiguity around V3 handler
V3 proxy handler (ex: CosmosHttpProxyHandler): Kind of sugar coated V2 version

IWebProxy is basic required contract/abstraction. Handler are nice wrappers around proxies.
Will just IWebProxy based contract suffice?

The other thing that the HttpHandler allowed was disabling SSL verification which is needed for linux environments.


feat: Add Routes

Lets Add Different routes in App.js file
As the time goes the project will have multiple pages like Home,profile,Detailed developer profile etc...
Solution :
Lets Add the different routes in App.js file and make the code  look good , simple

@shyamtawli i would like to work on it .

Hello @shyamtawli,
Just saw an invite in my Twitter DM to contribute.
I'd like to work on the routing, if the issue is still open for contribution.

And could I get a full list of the pages the application will have?

Currently you can add routes on App.js because we don't have that much routes.
There is no team I am only the team, lol.
Now only one page is there and that is home page and in future will soon add separate pages like individual pages for profiles, how to add profile page and more. You can set the routes in that way that we can use it in future.
Any help than feel free to contact me.

Alright. Thanks for the clarification.
Guess it's you and me for now. 😂💪🏾
I'll see if I can whip up something up soon. 💯
On Tue, Jun 20, 2023, 19:48 Shyam Tawli @.***> wrote:

Currently you can add routes on App.js because we don't have that much
routes.
There is no team I am only the team, lol.
Now only one page is there and that is home page and in future will soon
add separate pages like individual pages for profiles, how to add profile
page and more. You can set the routes in that way that we can use it in
future.
Any help than feel free to contact me.
—
Reply to this email directly, view it on GitHub
https://github.com/shyamtawli/devFind/issues/143#issuecomment-1599155170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY7OZT6HMKPYEA2QY76EO6TXMHH63ANCNFSM6AAAAAAX46H2KQ
.

The issue explicitly says the routes be added in the App.js file, but I propose to have a routes folder which will hold all the routing logic.
Would that be okay with the team?

Where do I come in,I specialized in backend and will like to contribute

Will Migrate to NextJS


Error compiling takeoff_and_land example on Docker.

Hello,
I'm having an issue while running the takeoff_and_land example on a docker machine.
What I want to do is simply communicate to my simulator with an app made by me using MAVSDK, running on a docker container. However, I'm facing an issue when compiling the takeoff_and_land example on docker.
takeoff_and_land.cpp:115:39: error: 'Success' is not a member of 'mavsdk::Action::Result'

Here is my dockerfile:
FROM ubuntu:18.04

WORKDIR /home

RUN apt-get update -y && \
    apt-get install build-essential cmake -y

COPY MAVSDK /home
COPY mavsdk_0.24.0_ubuntu18.04_amd64.deb /home

RUN dpkg -i mavsdk_0.24.0_ubuntu18.04_amd64.deb
RUN cd /home/examples/takeoff_land/ && mkdir build && cd build && cmake .. && make

CMD tail -f /dev/null

The error with a bit of cmake output :
Step 7/8 : RUN cd /home/examples/takeoff_land/ && mkdir build && cd build && cmake .. && make
 ---> Running in 321ff9fb4186
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/examples/takeoff_land/build
Scanning dependencies of target takeoff_and_land
[ 50%] Building CXX object CMakeFiles/takeoff_and_land.dir/takeoff_and_land.cpp.o
/home/examples/takeoff_land/takeoff_and_land.cpp: In function 'int main(int, char**)':
/home/examples/takeoff_land/takeoff_and_land.cpp:115:39: error: 'Success' is not a member of 'mavsdk::Action::Result'
     if (arm_result != Action::Result::Success) {
                                       ^~~~~~~
/home/examples/takeoff_land/takeoff_and_land.cpp:124:43: error: 'Success' is not a member of 'mavsdk::Action::Result'
     if (takeoff_result != Action::Result::Success) {
                                           ^~~~~~~
/home/examples/takeoff_land/takeoff_and_land.cpp:135:40: error: 'Success' is not a member of 'mavsdk::Action::Result'
     if (land_result != Action::Result::Success) {
                                        ^~~~~~~
CMakeFiles/takeoff_and_land.dir/build.make:62: recipe for target 'CMakeFiles/takeoff_and_land.dir/takeoff_and_land.cpp.o' failed
make[2]: *** [CMakeFiles/takeoff_and_land.dir/takeoff_and_land.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/takeoff_and_land.dir/all' failed
make[1]: *** [CMakeFiles/takeoff_and_land.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

Thank you !

There have been changes in the meantime and the examples are not updated because they are not tested in CI (yet), see #1027.
We'll fix it asap but basically there are some changes coming in the API that we keep track of in https://github.com/mavlink/MAVSDK-docs/pull/191.
For the error here, it's just Action::Result::Success -> Action::Result::SUCCESS.


[docs] Demo LoadingButtonsTransition crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/es/components/buttons/
??
demo LoadingButtonsTransition crashes

Your Environment

Tech
Version

MUI
v5.0.0

netlify deploy
https://614b1f0f5bede80007dca3b8--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36

What do you mean crashes? It works fine on my side.

Duplicate of https://github.com/mui-org/material-ui/issues/27853


ActionPlugins and ActionDefinitions on Ispn backend

@jshaughn, I have started to add support to both C* and Ispn backend.
In an iterative way I've started with easy ones.
Plan to continue tomorrow, but I wanted to consolidate this instead to send an uber-PR.

I'll merge this in. I'm still getting familiar.  From what I can see we're limiting our use of Hibernate Search annotations to just those used for indexing.  I assume that it's by design that we're not using JPA annotations like @Entity, or the various relationship annotations like To, so that we're not bound to a JPA datastore.  Is that right?

Correct. With Hibernate Search and Ispn user can control what to index in fine granularity.
So, no need to use JPA or similar, just a high level API to Lucene (backed engine for indexes).


AVS SDK 1.6::Music streaming Barge-in use-case

We are seeing a considerable delay in receiving a STOP_CAPTURE when a user barges in with "Hey Alexa" but does not speak any phrase .
Here is the use-case

Prime music is going on and User barges in by speaking "Hey Alexa". Alexa enters LISTENING state.

Jul 13 06:16:57 apq8009 AlexaClientApp[1587]: ############################
Jul 13 06:16:57 apq8009 AlexaClientApp[1587]: #       Listening...       #
Jul 13 06:16:57 apq8009 AlexaClientApp[1587]: ############################

Now user does not speak anything in the microphone. There is only silence. STOP_CAPTURE comes after considerable time

Jul 13 06:17:03 apq8009 AlexaClientApp[1587]: 2018-07-13 06:17:03.117 [ 10] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"c2412e51-c1ac-4a77-9a66-2ece868ce81c",dialogRequestId:"cc59eb6e-2600-4cad-b23d-d3aa0a4d6380"}

Now SDK goes into THINKING state but since there is no SPEAK directive the transitionFromThinkingTimedOut in DialogUXStateAggregator gets kicked in. This value is set to 5 seconds.

Jul 13 06:17:08 apq8009 AlexaClientApp[1587]: ########################################
Jul 13 06:17:08 apq8009 AlexaClientApp[1587]: #       Alexa is currently idle!       #
Jul 13 06:17:08 apq8009 AlexaClientApp[1587]: ########################################
Total time is 11 seconds (SDK delay time) before music has a chance to resume. Add a couple of seconds to restart the stream. Sometimes we have seen the STOP CAPTURE can take a considerable time to be received from the cloud. This is only when User barges in but does not SPEAK.
Can we optimize the SDK further to match echo dot ~ roughly 6-7 seconds? It seems to me that SDK should not be going to THINKING considering that cloud would know nothing has been SPOKEN by the user, as there is no SPEAK. It should simply move to IDLE state.

Hi @adpandit,
Thanks for bringing this issue into our attention.  Even though the cloud knows nothing is spoken, the device has no such knowledge and does not know if the last utterance would result in a SPEAK directive or not.  That is why the SDK has this transitionFromThinkingTimedOut timer so that it would transition back to idle state when no directives are received from AVS.
Hope this answers your question.
Thanks,
Kenneth

Yes. Thank you for getting back to me. Looks like there is no way for us to reduce this timeout.
Perhaps, in the later versions of the SDK, you can consider adding the enhancement for the device going back to IDLE state. Cloud can signal such a scenario.
Regards.

Hi @adpandit,
Thanks for your suggestion. We'll investigate it internally.
Thanks,
Benny


Wire events for unray encoding models

Adds events on encoding models, and wire them up internally and on plot models.

Fixes #22.


handle missing license key in [aur]

Fixes #4142

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against<PHONE_NUMBER>bb4ded8f2b3c901285ef598e006148


Make sure package is built with dask compatibility

I think this will be useful for lazy-loading dataset we discussed. With dask compatibility, we might even not need our custom image loading functionality.

https://github.com/google/jax/issues/395
It seems that JAX needs the data to be on-memory for now.

For transform, we can definitely make it compatible with dask.

done in #80


Triangles with thick strokes

Version of embedded-graphics in use (if applicable): 0.6.2
Target: simulator

Description of the problem/feature request/other
Triangle ignores stroke thickness
Test case (if applicable)
use embedded_graphics_simulator::{
    BinaryColorTheme, OutputSettingsBuilder, SimulatorDisplay, Window,
};

use embedded_graphics::{
    pixelcolor::BinaryColor, prelude::*, primitives::Triangle, style::PrimitiveStyle,
};

fn main() -> Result<(), core::convert::Infallible> {
    let mut display: SimulatorDisplay<BinaryColor> = SimulatorDisplay::new(Size::new(128, 64));

    let output_settings = OutputSettingsBuilder::new()
        .theme(BinaryColorTheme::OledBlue)
        .build();

    let thick_stroke = PrimitiveStyle::with_stroke(BinaryColor::On, 3);

    Triangle::new(Point::new(0, 0), Point::new(12, 0), Point::new(6, 12))
        .into_styled(thick_stroke)
        .draw(&mut display)
        .unwrap();

    Window::new("Triangle", &output_settings).show_static(&display);
    Ok(())
}

Haven't checked master very closely, only a cursory glance on the git history, but I haven't seen any explicit commit targeted towards triangles.

Thanks for reporting this. This is a known problem as we haven’t solved the issue of line joiners yet, resulting in both triangles and poly lines not supporting thickness at the moment.
We can probably repurpose this issue as a tracking issue for thick lines on triangles and poly lines.

Hm, I didn't know that, maybe worth a mention somewhere? But truth be told, I was just assuming it would work, haven't checked the docs beforehand.


Provide infra requirements for setting up UEI network on GCP

Description
Based on the discussion withe GCP team, it has been agreed that they will help setup the prod and pre-prod env's on GCP. in order for them to allocate the necessary credits to the GCP account, they would like to understand the infra required for setting up the UEI network.
Looking at the existing AWS infra document the infra details required for setting up the following on GCP. This info need sto be shared with bharath and the GCP team (Nitin and Monojith).

Gateway
Registry

It is ideal if the prod has a bigger capacity compared to pre-prod env.
Goals

[ ] Document the infra requirements based on the existing infra utilisation on AWS and provide the details to GCP team
[ ] Infra Requirements for setting up gateway and registry on prod and pre-prod env.

Expected Outcome
Document the infra details, based on the current AWS UEI infra
Acceptance Criteria

[ ] Document the  infra details and share it with GCP Team

Implementation Details
NA
Mockups / Wireframes
NA

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]
Product Name
Gateway and Registry
Domain
UEI

Thanks @vbabuEM
@bharath-ganapathy , Please see the infra requirements for prod and pre-prod


Bad network indicator on ME when camer set to low

Scenario:
simulcastEncodings :
[
{ maxBitRate: 250000 },
{ maxBitRate: 750000 }
],
2 clients, both start in camera "medium"
1 switches the camera to "low" and gets on the ME window the red mark for the connection. On the remote side no indicator. This is related to #319 that for camera set to low, the worst simulcast video is only sent (I see it on the stats 250kb sending). Can it be that there is an bug in the calculation of the quality of the network for low resolution streams? That could explain this and the things from 319. Or maybe just the interpretation on the sender side is buggy as the receiver does not get the indicator?

@Astagor  What is ME window?

Own video, ME in the English interface.

 :)

@Astagor  Can you retest on letsmeet.no? I don't experience it. Can you help to reproduce the issue?


[ENH] Allow to press SHIFT while hovering macros in actionbar to see the macro name (and not the spell tooltip)

Is your feature request related to a problem? Please describe.
Once you have added your GSE macros onto your actionbar:

A- some of these GSE macros directly show the first spell that is in the macro
B- other GSE macros show the "?" icon (but once you start a fight, the icon changes and displays each spell icon, successively, so this is not a problem)

If you hover these "macros A" with your cursor, you will see tooltips showing the next spell, the one that is ready to be casted:

If you hover "macros B", you can see a small tooltip showing the GSE macro name (and this is very convenient to know where you have placed which macro on which action bar slot):

Describe the solution you'd like

Let GSE display the spell tooltips if the player hovers GSE macros (in fact, don't change anything).
But would it be possible to make GSE display the following tooltip if the player presses SHIFT + hovering macros ?

This small tooltip (with macro name) is very useful.
If am asking to display this tooltip on SHIFT keypress it's because, I guess, it's not possible to add the Macro name to these tooltips, is it?
Mock-up:

GSE has no control over what is shown.  WoW interprets the current block and shows whatever it thinks is appropriate.  GSE doesn't interact with this at all.

ok. Too bad.
Thank you Timothy for this explanation.


[Feature Request] Allow for disabling of Select dropdown's auto-positioning

Existing Component
Yes
Component Name
el-select
Description
The dropdown can auto-position excessively on user input when filterable. This issue may be exacerbated on custom filter methods.

Please provide a demo of your problem.

Link to demo from gif: https://codepen.io/yancyknight/pen/oPLaXN?editors=1010
If the dropdown is too close to the bottom for the unfiltered list, it appears above the select. Then as the list is filtered, it can suddenly jump below the select, creating a jarring experience for users. We expect that if it starts above the select, it should stay above regardless of scrolling or filtering.

IMO: Ideally the positioning should be sticky, unless user scrolls the page.


App Crashed When Making Video Call

The application getting crashed in linux when making video call.
To Reproduce
Steps to reproduce the behavior:

Clone the repo
Run the sample code
Connect it with asterisk server
Now try to make a video call
You will see that app crashed without any errors/warning.

Expected behavior
The application shouldn't get crashed
System Infomation()
Flutter SDK Version: 3.22.2
OS: Linux Ubuntu 24.04 LTS

Yeah! I'm too facing this same issue, anyone know the the solution???


remove version key

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (c391cae) 51.85% compared to head (86ccc76) 51.78%.

Files
Patch %
Lines

...ft/exchange/common/processor/ReloadProcessor.scala
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master     #194      +/-   ##
============================================
- Coverage     51.85%   51.78%   -0.08%
  Complexity       89       89
============================================
  Files            21       21
  Lines          1913     1908       -5
  Branches        378      378
============================================
- Hits            992      988       -4
+ Misses          733      732       -1
  Partials        188      188

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


onedb change-body removes CDATA on update

Description
When onedb change-body is used to update an entry in the VM's XML for example, the updated value is without CDATA enclosure.
To Reproduce
Edit any element in a XML using onedb change-body
Review the resulting  XML - the updated value is without CDATA
Expected behavior
The updated value should be with CDATA, at least for consistency with the other elements.
Details

Version: [5.10.0]

Additional context

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

CDATA value is generated by oned. Next time that the element is updated the CDDATA value will be added.
On a side node this operation is for advance recovery processes, if the generated XML is not correct it may break the DB. It'd be better to not remove the CDDATA's.

Agree. But the alternatives are worst:
For example, if there is a need to change the IP mask of an VM NIC interface you have the following options(ordered by the implementation difficulty):

detach NIC and attach it again - there is a risk to change the NIC's order
alter the exact xpath with onedb change-body ... and update the mask inside the VM (* this topic*)
alter using onedb update-body ... with interactive editor (Insane but I am using from time to time)
alter using onedb update-body ... with a custom script exported as the $EDITOR variable
alter using onedb patch ... with custom patch script. Writing it just for completeness because it is offline patching...

I'd say that options 1 and 2 are much safer than the rest...

So maybe what we are looking for is not modifying onedb (which is a recovery/admin tool) but extend update conf to change configuration attributes per NIC? Do you have an example, what the current updateconf/CONTEXT is missing?

Well I think that onedb should be fixed to have XML consistency at least.
Extending the onevm updateconf is different topic IMO :)
At first glance an option to edit FILTER_*_SPOOFING per VM NIC interface could address https://github.com/OpenNebula/one/issues/684
There are probably other usecases, for example to change the VN_MAD from bridge to bridge+fw, etc.


Colours learning feature

I propose to integrate an interactive page within the Learn app to educate children about color names.
Features:
Colourful UI: Designed a visually appealing UI
Voice Output: Implemented voice prompts that provide audio pronunciation of color names

Please assign this feature request to me so that I can proceed with creating a pull request.

Okay if you come with intuitive GUI I'll give it more priority for now it's Level 1

Okay, I'll focus on improving the GUI further, and then I'll proceed to generate a pull request.

I have made some changes:

Let me know if there are any further improvements.

Great! Just keep in mind that we have to use svg files such that application size doesn't increase a lot.😊

Ohh, didn't know that, I converted those files back to SVG. and can you update the level?

Done at #19


confirm()  delete of account suggestion

I'm enjoying this fine starter template.
Here is a small suggestion that I think everyone would want.
File: profile.pug
Original:
line:  69
    form.form-horizontal(action='/account/delete', method='POST')

Suggestion with confirm()
    form.form-horizontal(action='/account/delete', method='POST', onsubmit="return confirm('Are you sure you want to delete your account?');")

👍

@mrmccormack Can you submit a PR for this please? Thanks.

Sure... I did a Pull request at:
https://github.com/mrmccormack/hackathon-starter/pull/1/commits
but it doesn't show up here yet?
Hope that helps.
Rob

@mrmccormack you'll need to open a PR on this repo requesting to merge the changes from your fork. Thanks.

PR: https://github.com/sahat/hackathon-starter/pull/797

Fixed in v4.4.0 release


Bugs discovered

Save button is not working for member page.
Changing team name and saving creates a new copy of team instead of modifying the team name.

Thanks for your notice. I have fixed that.


I really want to just copy-and-paste the DB script

Hi Daz, thank you very much for the pull request :)
Would you mind signing the CLA - we have to ask contributors to sign the CLA even for very small changes. Would be happy to merge your changes in.


⚠ Spryr has degraded performance

In 9b3e875, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 500
Response time: 18580 ms

Resolved: Spryr performance has improved in 45dee4e after 8 minutes.


a bug when fomat style tag

Operating System (+Version): win10 x64
VS Code Version: 1.12.2
beautify Version: 1.0.2

NOTE: Please provide code snippets instead of screen shots. Your issue needs to be replicated, and we need the failing code (text) to do this.
Provide the settings you use:
(VS Code workspace and user settings, .jsbeautifyrc, .editorconfig)
eg.:
Create a file which language been set to 'html',then type these code:
<style>
/*something*/

.a {
  width: 100px;
}

/*something*/

.a {
  width: 100px;
}

</style>

.jsbeautifyrc
{
  "indent_size": 2,
  "indent_char": " ",
  "end_with_newline": true,
  "indent_with_tabs": false,
  "preserve_newlines": true,
  "max_preserve_newlines": 2,
  "html": {
    "allowed_file_extensions": ["htm", "html", "xhtml", "shtml", "xml", "svg", "vue"],
    "brace_style": "collapse",
    "indent_handlebars": false,
    "indent_inner_html": false,
    "indent_scripts": "keep",
    "max_preserve_newlines": 2,
    "preserve_newlines": true,
    "unformatted": ["a", "span", "img", "code", "pre", "sub", "sup", "em", "strong", "b", "i", "u", "strike", "big", "small", "pre", "h1", "h2", "h3", "h4", "h5", "h6"],
    "wrap_line_length": 0
  },
  "css": {
    "allowed_file_extensions": ["css", "scss", "sass", "less"],
    "newline_between_rules": true,
    "selector_separator": " ",
    "selector_separator_newline": true
  },
  "js": {
    "allowed_file_extensions": ["js", "json", "jshintrc", "jsbeautifyrc"],
    "brace_style": "collapse",
    "break_chained_methods": false,
    "e4x": false,
    "indent_level": 0,
    "jslint_happy": false,
    "keep_array_indentation": true,
    "keep_function_indentation": true,
    "space_after_anon_function": false, // Should the space before an anonymous function's parens be added, "function()" vs "function ()"
    "space_before_conditional": true, // Should the space before conditional statement be added, "if(true)" vs "if (true)"
    "space_in_empty_paren": false,
    "space_in_paren": false,
    "unescape_strings": false,
    "wrap_line_length": 0
  }
}

Action performed
Format javascript file with HookyQR.beautifyFile command
provide example code
Right Click-->format document
Expected results
Expected ... to ...
provide example (expected) output
Actual results
Details of what happened ...
provide example (actual) output

Error line when format many times

Same here. But adding a few more details, it  behaves differently depending on how you add your comment.
block comment outside brackets adds an extra line before and after the comment each time you format.
block comment inside brackets works fine.
inline comment outside brackets works fine.
inline comment inside removes all spaces between comment and last character.
Example before formatting:

Example after formatting:

It's weird. If you use inline comment outside brackets and block comment inside brackets, everything works fine.

This is an upstream bug unfortunately: https://github.com/beautify-web/js-beautify/issues/1185

Same problem！

A right pain in the rear!

Same problem


Handle racing conditions for common meta-data

The bulkblocks API internally has racing conditions, see full discussion https://github.com/dmwm/WMCore/issues/11106
To resolve this we can use Queue'ing system to insert common meta-data:

Create independent Queues for individual DBS database tables, e.g. ProcessedDatasetQueue
adjust bulkblocks API to use appropriate queue for given metadata, e.g. adjust getProcessedDatasetID  to use ProcessedDatasetQueue instead of GetRecID call, see line-354
each individual queue will process requests sequentially, e.g. FIFO. This will eliminate racing condition among independent and competing HTTP requests since the specific common meta-data will be either injected or obtained its ID from its queue.

We need:

new queueProcess injector which will consume requests for injection and process them in FIFO order
blocking channel which will be used before we inject the data

For instance,
type QueueDataRecord struct {
  Record dbs.DBRecord
  Out chan bool
}

rec // represent data record we received from bulkblocks API
// process engine to process records in Queue
go processQueue()

// channel will block us until all records are injected
ch := make(chan bool)

// send data record to the queue
queue <- QueueDataRecord{Record: rec, Out: ch}

// consume data when it is ready
for {
   select {
   case r := <- ch
        // call GetIDs of common meta-data
   }
}

and processQueue function will do something like
func processQueue() {
   for {
      select {
         case rec := <- queue {
             // process given record
             // send out its status that it is ready
             rec.Out <- true
         default:
             time.Sleep(time.Duration(1) * time.Second) // wait for new task
      }
   }
}

Further thoughts on this:

this approach will not work if we'll have multiple independent DBSWriters (k8s pods) since they do not share the queue
therefore, in order to make it work we either need to have persistent queue storage (among all k8s pods) or have individual ONE additional server which will process these records sequentially