drbg sample fails on revision 1728

In both trunk and tag/v1.0.4,
$ app/acvp_app --verbose --drbg --sample
...
***ACVP [STATUS][acvp_dispatch_vector_set:2511]--> Algorithm: hashDRBG
***ACVP [INFO][acvp_drbg_kat_handler:87]-->     DRBG alg: hashDRBG
***ACVP [INFO][acvp_drbg_kat_handler:129]--> Number of TestGroups: 198
***ACVP [INFO][acvp_drbg_kat_handler:237]-->     Test group:
***ACVP [INFO][acvp_drbg_kat_handler:238]-->     DRBG mode: SHA-1
***ACVP [INFO][acvp_drbg_kat_handler:239]-->     derFunc: false
***ACVP [INFO][acvp_drbg_kat_handler:240]-->     predResistance: true
***ACVP [INFO][acvp_drbg_kat_handler:241]-->     entropyInputLen: 128
***ACVP [INFO][acvp_drbg_kat_handler:243]-->     additionalInputLen: 0
***ACVP [INFO][acvp_drbg_kat_handler:245]-->     persoStringLen: 0
***ACVP [INFO][acvp_drbg_kat_handler:246]-->     nonceLen: 96
***ACVP [INFO][acvp_drbg_kat_handler:247]-->     returnedBitsLen: 160
***ACVP [INFO][acvp_drbg_kat_handler:254]--> Number of Tests: 15
***ACVP [INFO][acvp_drbg_kat_handler:263]--> Found new DRBG test vector...
***ACVP [INFO][acvp_drbg_kat_handler:268]--> json testval count: 0
{
"tcId": 1,
"entropyInput": "202A07C33F10531B16F51599FC0E5922",
"nonce": "04A73E59815520CE4C7D3324",
"persoString": "",
"otherInput": [
{
"intendedUse": "generate",
"additionalInput": "",
"entropyInput": "4255BFDC893EB59E320503FAC17D392B"
},
{
"intendedUse": "generate",
"additionalInput": "",
"entropyInput": "12C535BB84C7F61A3EDFAA6949023D39"
}
]
}
***ACVP [INFO][acvp_drbg_kat_handler:315]-->         Test case: 0
***ACVP [INFO][acvp_drbg_kat_handler:316]-->              tcId: 1
***ACVP [INFO][acvp_drbg_kat_handler:317]-->              entropyInput: 202A07C33F10531B16F51599FC0E5922
***ACVP [INFO][acvp_drbg_kat_handler:318]-->              perso_string:
***ACVP [INFO][acvp_drbg_kat_handler:319]-->              nonce: 04A73E59815520CE4C7D3324
***ACVP [INFO][acvp_drbg_kat_handler:338]--> Found new DRBG Prediction Input...
***ACVP [ERR][acvp_drbg_kat_handler:437]--> crypto module failed the operation
***ACVP [ERR][acvp_process_tests:2246]--> Unable to process vector set! Error: 12
***ACVP [ERR][acvp_run:3032]--> Failed to process vectors
In another test with my own FIPS module (not OPENSSL), I set predResistance to false in ebable_drbg() function, I got a similar failure:
***ACVP [STATUS][acvp_dispatch_vector_set:2510]--> Processing vector set: 274021
***ACVP [STATUS][acvp_dispatch_vector_set:2511]--> Algorithm: hashDRBG
***ACVP [INFO][acvp_drbg_kat_handler:87]-->     DRBG alg: hashDRBG
***ACVP [INFO][acvp_drbg_kat_handler:129]--> Number of TestGroups: 20
***ACVP [INFO][acvp_drbg_kat_handler:237]-->     Test group:
***ACVP [INFO][acvp_drbg_kat_handler:238]-->     DRBG mode: SHA-1
***ACVP [INFO][acvp_drbg_kat_handler:239]-->     derFunc: false
***ACVP [INFO][acvp_drbg_kat_handler:240]-->     predResistance: false
***ACVP [INFO][acvp_drbg_kat_handler:241]-->     entropyInputLen: 128
***ACVP [INFO][acvp_drbg_kat_handler:245]-->     persoStringLen: 0
***ACVP [INFO][acvp_drbg_kat_handler:246]-->     nonceLen: 64
***ACVP [INFO][acvp_drbg_kat_handler:247]-->     returnedBitsLen: 640
***ACVP [INFO][acvp_drbg_kat_handler:254]--> Number of Tests: 15
***ACVP [INFO][acvp_drbg_kat_handler:263]--> Found new DRBG test vector...
***ACVP [INFO][acvp_drbg_kat_handler:268]--> json testval count: 0
{
"tcId": 1,
"entropyInput": "DBC62FA0F988F91FC2D1F0435D54756B",
"nonce": "468BB5181FC7B195",
"persoString": "",
"otherInput": [
{
"intendedUse": "reSeed",
"additionalInput": "",
"entropyInput": "99689DB522ED4665B58E903F6844D909"
},
{
"intendedUse": "generate",
"additionalInput": "",
"entropyInput": ""
},
{
"intendedUse": "generate",
"additionalInput": "",
"entropyInput": ""
}
]
}
***ACVP [INFO][acvp_drbg_kat_handler:315]-->         Test case: 0
***ACVP [INFO][acvp_drbg_kat_handler:316]-->              tcId: 1
***ACVP [INFO][acvp_drbg_kat_handler:317]-->              entropyInput: DBC62FA0F988F91FC2D1F0435D54756B
***ACVP [INFO][acvp_drbg_kat_handler:318]-->              perso_string:
***ACVP [INFO][acvp_drbg_kat_handler:319]-->              nonce: 468BB5181FC7B195
***ACVP [INFO][acvp_drbg_kat_handler:338]--> Found new DRBG Prediction Input...
***ACVP [ERR][acvp_drbg_kat_handler:437]--> crypto module failed the operation
***ACVP [ERR][acvp_process_tests:2246]--> Unable to process vector set! Error: 12
***ACVP [ERR][acvp_run:3080]--> Failed to process vectors

When I look at acvp_drbg_kat_handler() in acvp_drbg.c, it says:
        /*
         * Handle pred_resist_input array. Has at most 2 elements
         */

But for my test case,  which set predResistance to false, pred_resist_input array always have 3 elements:
"testGroups": [
    {
        "tgId": 1,
        "testType": "AFT",
        "derFunc": false,
        "reSeed": true,
        "predResistance": false,
        "entropyInputLen": 128,
        "nonceLen": 64,
        "persoStringLen": 0,
        "additionalInputLen": 0,
        "returnedBitsLen": 640,
        "mode": "SHA-1",
        "tests": [
                "tcId": 1,
                "entropyInput": "7C79AD7B8553B5E2121D36F89FF27736",
                "nonce": "DFB962EEFE162C4B",
                "persoString": "",
                "otherInput": [
                    {
                        "intendedUse": "reSeed",
                        "additionalInput": "",
                        "entropyInput": "5A2AE7B437CE784CCAA9CBE391DC8589"
                    },
                    {
                        "intendedUse": "generate",
                        "additionalInput": "",
                        "entropyInput": ""
                    },
                    {
                        "intendedUse": "generate",
                        "additionalInput": "",
                        "entropyInput": ""
                    }
                ]

or
"tcId": 16,
"entropyInput": "B48FAD87CDEA68C97F39249EB80F056D",
"nonce": "98F0EAE7DAA5B8C4",
"persoString": "",
"otherInput": [
{
"intendedUse": "reSeed",
"additionalInput": "5B756D42777C18D90E6803369EAADB19",
"entropyInput": "254DA7159061E2C2B4FDD36F7C6FF117"
},
{
"intendedUse": "generate",
"additionalInput": "C353247EBB7C68B4421299EB28085C81",
"entropyInput": ""
},
{
"intendedUse": "generate",
"additionalInput": "5572865657A36088144AE96B8A8667D2",
"entropyInput": ""
}
]

The base registration works properly with openssl FOM. If you've made changes to the registration you'll need to provide that so we can investigate. If you're not using the openssl FOM, then you may have issues with your crypto module.
Regarding the comment "Has at most 2 elements", that statement is inaccurate we see 3 using the base registration.

Looked a little deeper into this and determined that the current app and library implementation supports only the first Predictions Resistance Assurance Option from section 4.1 of the acvp_sub_drbg specification. You're attempting to use the second option which includes a reseed during testing and currently that is not supported.
Our open source implementation does not support every option available in the ACVP spec.
We will add a task to implement this, however I cannot commit to any timeline as we have many other higher priority tasks in our queue.
You are welcome to implement it yourself and we would welcome a PR if you would like to contribute back to the community.
Regards,
Barry

Just some clarification:
There are 2 issues:

The  drbg sample failure happened to "OpenSSL 1.1.1  11 Sep 2018", without any libacvp source change on revision 1728.
With my own module, I need to test "Prediction Resistance Not Enabled" case for drbg, which libacvp doesn't support at the moment. Looks like I will need to do it myself.

Thank you for your replies.
Harry

The sample failure is due to the fact that openssl 1.1.1 has no FOM with HASH DRBG and therefore DRBG testing is disabled in libacvp since ACVP_NO_RUNTIME is not set. We do allow vector download for DRBG when ACVP_NO_RUNTIME is not set, but cannot support --sample because DRBG upload is required by the server in order to get sample results.

Thank you, Barry.

I have added the "Prediction Resistance Not Enabled"  support for drbg test. It's verified by running my own module. And I believe it won't break anything.
I don't know if I have the permission to create PR. I just attach the diff file here. Will appreciate it if you can review and merge it.
The diff is generated in trunk against svn revision 1730.
Harry
diff.txt

We've added the enhancement, all options from section 4.1 are now supported via PR #455


How to avoid getLatestLocation returning outdated location

As the title.Thanks in advance.

I'm seeing this as well in the android emulator even though google maps returns a valid location


Compiling bootstrap and font-awesome's less files is slow

Can we default to having some commented out or use a compiled version?

No longer compiling font awesome :)


Broken index.ts file

New Battery service and ErrorCode is missing in version 0.7.0

fixed in 0.7.1


Themr breaks shouldComponentUpdate shallow equal optimization

Themr breaks shouldComponentUpdate shallow equal optimization.
Every new render themr returns a new object reference for theme object, so all subsequent optimizations based on shallowEqual like pure recompose enhancer always returns true.
As nextProps.theme !== props.theme.
I'll create a PR to fix.

Please describe why do you think it's a responsibity of themr to handle optimizations like pure-rendering out of the box?
I believe if one has to use objects in props instead of plain values then such cases should be handled explicitly.
IMO nothing is broken here, it's an expected behavior of using shallowEqual and if you need special behavior you should enhance your shouldComponentUpdate to handle theme-objects and to check them deeply.

@raveclassic It's not the responsibility of themr to handle optimizations, but it should not break the usual components lifecycles if it added.
As it is a enhancer it should not affect component behaviour, so it should not generate a new properties every rerender as it will break optimized component logic.

@istarkov Agree, but it actually is the default behavior - themr HOC addes an object to child's props. Why should shallowEqual ignore this object implicitly?

It is not ignored. The only change here is an optimization allowing not to recalculate theme objects if nothing has changed. And a good news this optimization solves other non wide issue

@istarkov Yes, you are right, sorry =)
Well, what about detecting context changes?

I thought about context - the problem that in that case you should implement something like, like in react-router (new) and redux, where you should subscribe on context changes explicitly.
Not sure that it's needed for this small library.
But may be I'm wrong.
(We does not use context for themr, and not sure that anybody who use it changes it on the fly)

@istarkov But now this.theme_ is composed without context even if pure-rendering is disabled, this is a breaking change then.

Where is no dependency here on pure rendering at all, we can forget word pure.
context is used only if one of three property has changed, and not used in usual rerendering.
From one sight it is a problem, from the other are not, as at current themr version there is also no mechanism to notify component about that context has changed.
So the only difference that in current themr version some random render will update theme props and in this PR some custom render will update context props. I see no difference as both situations are wrong.

I do not state that theme should be updatable by context changes. As you've already pointed it's another problem and it should be solved with the ways like in react-router.
I meant that initial theme composition in constructor and in componentWillReceiveProps does not take context into account anymore and therefore it's a breaking change.

Why it does not take a context as it is the same source as before? As this.getContextTheme() was called as it's called not, no difference.

@raveclassic also please look at tests all tests are passed https://github.com/javivelasco/react-css-themr/blob/master/test/components/themr.spec.js

@istarkov Ahh makes sense now, sorry, didn't notice. At last we need to wait @javivelasco to take a look.

Seems like a good library to solve context issues https://github.com/ReactTraining/react-broadcast

Thank you @istarkov and @raveclassic, beautiful conversation 😄 I'm merging 👍 there are no breaking changes and I agree that updating context should not be solved in here. I'm also releasing a patch


[WiP] Markdownlint + light editing

Markdownlint yells at me when I open these, so I'm simultaneously (re-)reading everything and cleaning up the formatting (and phrasing in some places) as I go.

I think that should go into the 0.6.0 RC2 release!

@mojodna is this no longer a WiP and ready to merge then?

I’m still working on it, but it represents incremental improvement, so it could be merged now with a follow up for the rest.


Improve the account recovery experience

Description
After successfully recovering an account the user gets redirected to an empty page that mentions that the account was recovered successfully. in this page there's no option to close it and it doesn't disappear automatically after a couple of seconds. and there's no way to close it other than pressing the back button on the upper left corner which isn't really user friendly since the user didn't choose to navigate to this page from the start.
https://github.com/threefoldtech/threefold_connect/assets/101194226/f8d43ecd-93a8-41f8-b286-4e14e876a854
a better experience would be showing a popup with the same message and the user should be redirected to the home page after the account recovery.
Environment

Android Version: 13
Threefold Connect version: 3.7.3 - 173

verified could recover the account smoothly

insert your old seeds and name

testcase


How to compile package supporting Python2 in carla-0.9.11

Ubuntu18.04
carla-0.9.11
I downloaded the source code of carla-0.9.11 and compiled it，but it's only available in the python3 version .
How to compile package supporting Python2 ?

You can either use make PythonAPI.2 or change line 15 in file Util/BuildTools/Setup.sh to PY_VERSION_LIST=2,3 in order to always compile with Python2 support.

You should also be able to compile for Python 2 with the command make PythonAPI ARGS="--python-version=2"


Correlation	- Pearson's correlation coefficient

Wonderful! I will just assign it to you

Pull request submitted


Restructured project to hide rlbot interface from user

As mentioned, I think the rlbot interface and similar stuff should hiden from the user so it doesn't gets mixed with their bot code. So I put src, inc, and lib into a folder called rlbot, and removed rlbot from the name of rlbot-release and rlbot-dev.
The resulting structure looks like this:

I hope you agree with this structure.
Everything still works and readme is updated.

I do agree that they should be seperated, however, I think I want to completely seperate the example bot and framework code.
If the example bot lives in a seperate repository you can fork the example bot and work from there. Just like all the other RLBot languages.
I am currently experimenting with git submodules and it seems like that would result in the same folder structure as you showed. Except the framework code won't need to be included in the example bot repository.

Yes, that would be preferable. This was just a small step in the right direction, but if you are already approaching a better solution, then you don't have to merge this.

Framework code is now completely seperate from user code.
All code relevant to the user lives in https://github.com/kipje13/CPPExampleBot
This should simplify the process of updating your own bot to use the latest framework code.


Content should support multi language

We should change the object model in the whole project.

duplicate of #47.


Finding definitions exported by string key does not work

From @Flamefire on June 9, 2018 12:35

VSCode Version: 1.24.0
OS Version: WIn10 x64

Steps to Reproduce:

Export by string key:

function parse(){return 1;}
exports["parse"] = parse; // exports.parse = parse;

Import and try GoTo Def:
require("./foo")
foo.parse(); // Not found

Does this issue occur when all extensions are disabled?: Yes
Both versions (exports["parse"] = parse; // exports.parse = parse;) should work exactly the same.
Copied from original issue: Microsoft/vscode#51520

Confirmed this in TS 3.0-insiders 20180608
When writing exports.parse = parse; intellisense works as expected


[MM-28714] Check if subscription is paid before showing any upgrade warnings

Summary
Now that we're storing whether a subscription is paid (upgraded) or not in stripe metadata, we can use that field override the displaying of any upgrade warnings. This PR will hide the banners along the top of the screen, as well as the upgrade modal (when clicking the invite people button when at or over the limit, as an administrator)
Ticket Link
https://mattermost.atlassian.net/browse/MM-28714
Related Pull Requests
n/a
Screenshots
n/a

Some of the changes for this ticket happened directly in another branch: https://github.com/mattermost/mattermost-webapp/pull/6679

@stevemudie this can be tested as part of the epic post-merge.

/cherry-pick cloud-ga

Cherry pick is scheduled.


create ipaddr update cmd

Motivation
Addressing issue 904: https://github.com/OLSF/libra/issues/904
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update or suggest changes to the docs at https://developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

 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.


-GMOD- Error

Hello, i have this error, i don't know how to do.
[ FAIL ] Starting gmod-server: Unable to start [FR] Militaryrp l VIP l Armee VS [ FAIL ] Starting gmod-server: Unable to start [FR] Militaryrp l VIP l Armee VS Gang l ClanSMG.fr: Tmux error:
Command
tmux new-session -d -s gmod-server ./srcds_run -game garrysmod -strictportbind -ip <IP_ADDRESS> -port 27015 +host_workshop_collection 460261521 -authkey B652B0CC4CF26BE857C036030AE54165 +clientport 27005 +tv_port 27020 +gamemode militaryrp +map rp_locality +servercfgfile gmod-server.cfg -maxplayers 70
Error
can't create socket: No space left on device
Fix
No known fix currently. Please log an issue.
http://gameservermanagers.com/issues
Thanks you to help me

But when i do df -hT, putty say to me:
http://realitygaming.fr/proxy.php?image=http%3A%2F%2Fi.imgur.com%2FIdKdQHe.png&hash=b07108bdf2b943c0110824fdd2e38cd8

/dev/root is 100% full. This is probably the issue

Okey, and how to do ? Because i have 4To in total

You have 1.8TB in /dev/md3 (/home) and only 20GB in /dev/root (/) you need to figure out what is using up all the storage in the  /dev/md3 partition. Try ncdu command might be useful

http://prntscr.com/7gu1b2
ncdu command don't work
I'm on Debian

Install the program  ....This is more of an issue of you not yet understanding your server. I recommend learning a little more about Debian.
apt-get install ncdu

This is my first debian server sorry :/
I will look on internet for a tutorial about ncdu

No problem we all started somewhere :). Google is your greatest tool in learning Linux. Helped me hundreds of times.

Don't found, can you give me just a simply command to do ?
I think
ncdu /root/
But after i don't know what to do, all tutorial are in english and i don't speak realy good english :/

ncdu /

should work

http://prntscr.com/7gu7g9

There is your issue. your /var directory is filling up the server. you can drill down further to figure out exactly what the issue it

I don't understand Oo

look in the /var directory

http://prntscr.com/7gu9ej
Log is full
I think is Fail2Ban but not sure

Is not Fail2Ban
http://prntscr.com/7guags

I Remove kern.log and kern.log.1 ?

yeah I would clear the logs that are too big

Work thx i love you <3 Give me your PayPal adress :D

<EMAIL_ADDRESS>. Glad I could help :)

You accept € ?

PayPal Converts it

I send you, this is not a lot but i don't have lot of money :)

Its ok buddy.  I will enjoy a drink on you :D thanks
—
Reply to this email directly or view it on GitHub
https://github.com/dgibbs64/linuxgsm/issues/420#issuecomment-111840963.


addes basic optional support and support for nsnull in dictionary values

Awesome stuff @NicholasBellucci ! One of the issues I have encountered with using your library is that it cannot support values that may be nil. One particular problem is that there is no way to send null values for keys in dictionaries.
For more clarification, here is the use case: The API expects an attributes argument, which is a dictionary representing the fields on the object. Some of these fields may be nil/null. Typically, to avoid removing a key/value pair from a Swift dictionary, we will use NSNull() to nullify a field. This resulted in a completely empty field and graphQL parsing error instead of the null value we would expect. This work will change that.
I also added some basic support for optional values, but if the wrapped type does not conform to ArgumentValueRepresentable it will have to default to null. This may not be the behavior you would expect but I think its worth adding so users of the library can have more support for nullifying fields.
I also added a value of 1 for the Current Project Version build setting, without this you cannot include it in a application that is uploaded to the app store.

Thanks for the contribution on this issue! Did not realize this case existed. Code looks good so I will merge.


fix for widen-search-field

Test link
Issues
Pull Requests
Labels
Releases
Before
Issue page

Pull requests page

Labels page (my repository)

Labels page

After
Issue page

Pull requests page

Labels page

Releases page

Releases page (forked repository)

Thanks for the PR! However the intent of widen-search-field is to... make the search field longer. I don't see that in your screenshots. It should look like this:

@fregante mine is that short all the time, like normal github

@fregante mine is that short all the time, like normal github

That's the point. Refined GitHub should make it longer.

@fregante these custom css works for me, others place above remains works as well
Custom CSS

Issues

Pull Requests

Can you update this PR with the required code?

@fregante added, test passed too, all good

I think that there's a lot of overlap between the rules now, some rules are just undoing the previous rules and some rules no longer apply. Also the comments need to be fixed and shortened, don't add linebreaks unless it's a new different sentence.

@fregante i shorten comments
I already commented what those rules i add are doing.
The old .subnav .float-right { rule on line 14 for those buttons Select tag, Draft a new release on the right of Releases page

I already commented what those rules i add are doing.

You might have misunderstood. By undoing I meant that the first rule sets flex-grow: 1 and then your new rule resets it to flex-grow: 0. This PR should just make sure that flex-grow: 1 is not applied there at all, instead of adding it and undoing it later.
You can see this in the developer tools:

I think all your new code justs undoes something that the old code does. Instead, you should just fix the old code.

@fregante but you said .subnav is all over place, so i can't delete it, just apply on those button T.T

@fregante i think remove .subnav at line 2, remove .subnav > :first-child:not(a) { on line 24
Replace with
.subnav {
	display: flex;
}


Combine per-linter and per-file configurations

It would be nice to be able to do this:
[pylama:pylint:plots.py]
good_names=x,y,i,j

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This would be really nice. I'd like to give my team more freedom in naming things in unit tests; for example:
[pylama:pylint:tests/*.py]
variable_rgx =

But I don't want to disable the pylint C0103 error entirely because I still want reasonable restrictions.


Update sql-database-connect-query.md

Fixed minor typos and improved clarity.

Hi @joseidz, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (joseidz). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


What methods did you use to convert the text annotations from Refer-Youtube-VOS?

Hello, can you give some shell scripts to convert the text annotations from the raw meta_expressions.json file?

The original scripts have been lost, and you can use those from ReferFormer and manually modify the dataloader.


Unable to detect runtime context i.e crx-bridge can't figure out what to do

In my MV3 extension, I've tried to send a dummy message from a content script to the
background service worker and I get the following error from the extension
Uncaught Error: Unable to detect runtime context i.e crx-bridge can't figure out what to do

which seems to me that it can't even find the background "namespace". I'm not using the "window" so wouldn't that
work out of the box?
P.S Thanks for this excellent package!

Workers of any kind are not supported at this point.
Load crx-bridge in the background script as usual, then leverage v-thread to create the workers. Proxy the function calls through it.
v-thread is not a popular package. Perhaps workers itself are not as common as I think they are, or I just didn't use proper keywords. But if you spot any problems or questions, do create the issue in the repo.

Perhaps I didn't explain the issue clearly (or I don't understand the reply). I get the error just by loading the background service worker. I don't want to create any
workers there.
In chrome extensions with Manifest Version 3 (MV3), the background script is replaced by a background service worker.

same issue

This should be fixed in<EMAIL_ADDRESS>the successor to crx-bridge


Initial 'Foodies Experience' Section Figma design

Summary:
Design the 'Foodies Experience' section for 'Le Jardin' website on Figma. Customes can view reviews and ratings left by other cutomers by other customers. Testimonials on the website help generate Social proof (method of persuasion).
Acceptance criteria:
1.Follow the Web Content Accessibility Guidelines (WCAG) to make the website accessible to all.
2 Add reviews for each customer.
3.Give rarings bellow each customer.
4.Use multiple methods of persuasions to attract cutomers for this website.
2.Use Component Library like MUI and NextUI. https://nextui.org/docs/components/card#composition
3.Adhere to the Brand Archetype persona 'Explorer'.
4.Use Adobe color wheel for color selection of the Website components.

testimonials figma link https://www.figma.com/file/puog0pDY0mW5VGzuivGCi1/Final-Group-Project--Bakery?type=design&node-id=0%3A1&mode=design&t=QsCIpjv2i3C0tP7D-1


cob_supported_robots: 0.6.12-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_supported_robots to 0.6.12-1:

upstream repository: https://github.com/ipa320/cob_supported_robots.git
release repository: https://github.com/ipa320/cob_supported_robots-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: null

cob_supported_robots
* Merge pull request #21 <https://github.com/ipa320/cob_supported_robots/issues/21> from fmessmer/melodify
  [Melodic] add melodic checks
* add melodic support
* add cob4-22
* Contributors: Felix Messmer, Florian Weisshardt, fmessmer

Since I've merged cob_extern, this now conflicts.  Can you rebase?  Thanks.

rebase done
I will rebase the other cob_X prs one by one (oldest to newest) - once the previous has been merge...as it will lead to conflicts again otherwise...


Weird React Native error: property is not configurable

I need to make time to remake a small repo.
I am on RN 0.71.6
I notice when i load a recycler list view wrapped in a styled component that i get an error "property is not configurable".
if i remove the wrapped styled components the list renders.  I did patch reanimated that had this
https://github.com/software-mansion/react-native-reanimated/pull/4252
but im not sure why it comes up here. i dont notice any similar changes to the console on styled comps and other views/components wrapped work fine.
not sure its a bug, but also wondering if anyone saw this before?
if this is not the place for this please close.
Here is a screen of the error.
https://ibb.co/vcKhhwJ
Environment
System:

OS: macOS 12.6.3
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 176.54 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh

Binaries:

Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
Yarn: 1.9.2 - ~/.yvm/shim/yarn
npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman

npmPackages:

styled-components: ^5.3.9 => 5.3.9
"react-native-reanimated": "^3.0.2" => 3.0.2
"recyclerlistview": "^4.2.0" => 4.2.0

Reproduction

wrap RecyclerListView in styled
allow content to render

import {RecyclerListView} from "recyclerlistview";
import styled from "styled-components/native";

export const StyledRecyclerListView = styled(RecyclerListView)`
  flex: 1;
`;

      return (
        <StyledRecyclerListView
          onEndReached={loadMore}
          onScroll={scrollHandler}
          onEndReachedThreshold={200}
          layoutProvider={layoutProvider.current}
          dataProvider={dataProvider}
          rowRenderer={(_, item, index, uno) => {
            return renderPost({_, item, index}, isHeaderVisible);
          }}
          snapToInterval={snapToInterval}
          decelerationRate={0.83}
          onVisibleIndicesChanged={onVisibleIndicesChanged}
          applyWindowCorrection={windowCorrection}
          externalScrollView={ExtendedScrollView}
          scrollViewProps={{
            contentContainerStyle: {
              flexGrow: 1,
            },
            alwaysBounceVertical: false,
            ...panResponder?.panHandlers,
            simultaneousHandlers: scrollViewSimultaneousHandlers,
            scrollRef: scrollViewRef,
            refreshControl: disableRefresh ? undefined : (
              <StyledRefreshControl
                refreshing={isLoading}
                onRefresh={async () => {
                  setIsLoading(true);
                  await dispatch(fetchFeed());
                  setIsLoading(false);
                }}
              />
            ),
          }}
          ref={listRef}
          initialRenderIndex={initialRenderIndex}
        />
      );

Your link to the error is dead and you don't provide it's content either. Hard to help...


[v3.16] Add About eBPF guide.

Description

Backport: Merge pull request #4045 from fasaxc/bpf-guide
Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit c49895b74bd6124764c45cadbe0337011d4eb07d
https://deploy-preview-4062--calico.netlify.app


Including subtitle from local folder

src: 'http://localhost/movies/subtitles/extracted/%3Ftype=1&mediaid=205221/cobbler.srt',
Shouldn't this work?

No, subtitles should be available directly from webtor servers.


Arrow color changed

I've just done a clean setup of Vim, and after installing NERDTree, noticed that the arrows on the directories are now a separate color, regardless of theme.

+1

Closes I don't see anything in the history to indicate the syntax had changed. Regardless, I like the change submitted by @Leeiio .


Add Exam data

This is the resulting data from scrapping from the UT Dallas Exam sites for IP, AP, CLEP, and ALEKS, per #66.
This will need to be incorporated to the database deployments as seen fit.
This is mostly done by hand as I haven't had internet access to develop and debug the scraper. I hope to have that finished before 3/28/2022, but depending on our priorities may have to push that further down the road.

What is the status on refactoring the data obtained by the exam scraper per @jmyrick02's observations?

I think I'm not entirely caught up on how we are establishing the Course ObjectIds.
I've been assuming they will be generated. If that is the case, then we will have to employ a separate script to build the associations between courses as outlined here (with prefix/number combinations) and their respective ObjectIds in the database, as they will be deployment/cluster specific.
If this is not the case, can you point me to the strings we are basing the ObjectIds off of?
Even so, I think this data should exist separate from the implementation specific details on that level, as this is still in active development.

The course ObjectIDs are generated by the scraper upon scraping the course data, after which the course data is pushed to MongoDB. In order to link courses to their IDs from other things, then, you'll need to poll MongoDB for the courses and find the IDs of matching courses.
I hope this helps to clarify.

Yes, this is what I thought. I will assume that the scraper data will be available as seen on @hochladen's fork.
I will create a script to build those associations, but I still think this data should exist independently, as re-scraping the data will break the associations, requiring the exam data to be reassembled into this form in order to repair the associations.
There are a few other edge cases not properly represented with the Exam schema/data, as with AP Physics where for "Physics Majors: Credit for 2326 + 2126 is applied only if PHYS 3416 is passed with a grade of C or higher; otherwise you earn 4 SCH of free electives". All are AP credit specific, and are outlined by the endnotes on the AP Credit website.

That mostly looks good to me.
I do however think that since SCH elective credits often have prefix/school associated with them, a number alone will not suffice. Either something like @jmyrick02's solution, or creating a new type, is probably the way to go.

Ah, that is a good point. I think just making a new type would be cleaner than making some sort of psuedo-course for representing them, but I'm open.


Istio/tools: automate performance regression locating process

Under designing

https://github.com/istio/test-infra/issues/2937


Can't save models.

🐛 Bug
Can't save models using torch.save() function.
To Reproduce
class Net(torch.nn.Module):
    def __init__(self):
        super(Net, self).__init__()
        self.conv1 = tgm.nn.ChebConv(11, 4, K=2, node_dim=1)

    def forward(self, x, adj):
        x = torch.nn.functional.relu(self.conv1(x,adj))
        x = torch.nn.functional.dropout(x, training=self.training)
        return torch.nn.functional.log_softmax(x.flatten(start_dim=1), dim=1)

x = torch.rand((7,23,11)) # some random dataset [batch_size,nodes,in_feature]
adj = torch.ones(size=(2,10),dtype=torch.int64) # coo matrix

model = Net()
y = model(x,adj)

torch.save(model,'temp')

Just illustrating a simple model with a ChebConv layer. The model works fine.
But, when I try to save the model, it produces an error message.
When I replace the ChebConv layer with a Conv2D layer (native torch), everything works fine.

Traceback (most recent call last):
File "/home/diz/PycharmProjects/BloodP/Graph/py_geo.py", line 89, in
torch.save(model,'temp')
File "/home/diz/.virtualenvs/env2/lib/python3.6/site-packages/torch/serialization.py", line 370, in save
_legacy_save(obj, opened_file, pickle_module, pickle_protocol)
File "/home/diz/.virtualenvs/env2/lib/python3.6/site-packages/torch/serialization.py", line 443, in _legacy_save
pickler.dump(obj)
_pickle.PicklingError: Can't pickle typing.Union[torch.Tensor, NoneType]: it's not the same object as typing.Union

Environment

OS: Ubuntu 16.04 LTS
Python version: 3.6.1 (also tested in 3.6.4)
PyTorch version: '1.5.1+cpu' (also tested in 1.6.0+cpu)
CUDA/cuDNN version: -
GCC version:  5.4.0
Any other relevant information: -

Additional context

Hi and thanks for reporting! This is an interesting issue, especially because I'm not able to reproduce it (PyTorch 1.6.0, Python 3.7). This seems related to pickling type information, and there are some issues regarding this, see, e.g., here. I expect it to be a Python 3.6 issue, so maybe you can try to upgrade Python to see if this issue disappears?

Hi, Thank you for the response. I upgraded my Python version to 3.7.1 and now everything works fine.


Error validating Australian mobile numbers starting with 460

Any number starting with +614 60 gets validated as false, even though it is a valid Australian mobile number.
It seems to be falsely checking a non existent region code as well as the country code (61)

Yes, It was an upstream bug but was fixed in the metadata v8.10.20
I've been working on the update but it is not ready yet.

Also having issues with Australian mobile numbers starting with 471 (ie. +61 471). Parsing the number then querying the number type returns :unknown, instead of :mobile or :fixed_line_or_mobile.

Closing as this will be solved by #43.


Cranelift: Signed SIMD vectors aren't allowed by IR parser

Various opcodes (such as SaddSat) only make sense if SIMD vectors can contain negative values, however the IR parser raises an error if a negative immediate is supplied, requiring explicitly u8 decimal immediates.
By supplying the 2's complement of the negative value in a SIMD vector, converting the values lanewise to signed values, and then performing a signed operation on the converted values, the correct results can be achieved (albeit again returned as the 2's complement, as unsigned values).
I would think given the existence of opcodes that rely on signed SIMD vectors, signed immediates should be allowed. Perhaps an unsigned variant (eg, u64x2) of each vector would make sense? These unsigned variants could behave as the current SIMD implementation does, but i64x2 could behave as a vector of signed values, instead.

Adding u64x2 would require adding u64 too. Cranelift IR currently doesn't distinguish between unsigned and signed integers, only between unsigned and signed instructions, with many instructions working on both due to the way 2s-complement works. I would like it to stay this way.
I think it would be better to allow both unsigned and signed immediates just like for scalar operations.

We discussed this somewhat in #3059, not specifically for SIMD, but allowing a range of negative and positive integers based on the size of the type. I think it would also make sense to apply those same rules for the lane type in SIMD consts.
I agree with @bjorn3, keeping a single type, but allowing signed and unsigned immediates seems like the best way to go about this.

If the un/signed distinction occurs based on the instruction, then that makes sense.

Hi, sorry, after further testing, it turns out my description of this isn't entirely correct anyway. The problem here lies solely in i8x16 vectors, as the parser specifically checks for u8 immediates in vectors; if this is incorrect behaviour anyway, I'm happy to try fix that, but I wanted to check first if there was a specific reason for it. i16x8 and above do support signed values.

I think it is reasonable to parse i8x16 as lanes of i8--I can't recall precisely why u8 was used but it may have just been because it was available and i8 parsing was not. Adding i8 parsing makes sense to me.


Show default value of all attributes in ReadMe

I see in ReadMe > Attribute, you list all custom attributes of RopeProgressBar. Could you please also list its default value? For example, app:max has default value is 100.

Sure thing! Fixed in b2790a0.


support nc dataformat for lrn

Hi,
Incase of mnist which has fc->lrn->fc we are unable to pass the fc output memory primitive of data format nc to lrn , since the lrn does not have nc implementation it is failing during the setup.
It would be helpful if you could add the nc support for lrn. As of now we have implemented a workaround checking if the format is nc then creating a new primitive with nchw and executing the lrn layer in nchw format.
Thanks

It seems a really specific use case. Is it possible for you to create the fc primitive with output format 'nchw'?  then you wouldn't need to create new primitive with nchw,


density plot on zero series throws exception

  pd.Series(np.zeros(4)).to_frame().plot(kind='kde')

Executing the above line throws the below exception.
LinAlgError                               Traceback (most recent call last)
<ipython-input-118-eac1a90078a2> in <module>()
----> 1 pd.Series(np.zeros(4)).to_frame().plot(kind='kde')

pandas version 0.16.2

We use scipy's gaussian kde.
from scipy import stats
stats.kde.gaussian_kde([0, 0, 0])

I suppose the density is defined to be one in this case, but perhaps the failure is the bandwidth being zero since it's probably using Silverman's rule? You might raise this in the scipy repo, but I suspect that their kde isn't meant to be used on constant series.

I agree this is a scipy issue. However, when you try to plot a Dataframe without inspection, this throws up the nasty exception when such an attribute is encountered. Why dont we just log the exception and go ahead with plotting other columns in dataframe?

Hmm, good point I see how that's annoying. But I'm not a huge fan of warnings.  We could catch the exception and reraise with a more informative error message saying which column failed, making it easier to df.crop([static_column], axis=1).plot(kind='kde'). Would you be interested in submitting a pull request for that?

Yeah, sure. Let me give it a try.


Simplify SBOM integration test

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Context: Pack v0.27 has Platform API 0.9 support which allows the legacy SBOM to go into the <layers>/sbom/launch/sbom.legacy.json location instead of existing as a label.

Context: Lifecycle v0.14.0/Platform API 0.9 support from pack v0.26 allows the legacy SBOM to go into the /sbom/launch/sbom.legacy.json location instead of existing as a label.


This page answered my questions

[Enter feedback here]

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

ID: bc48efcd-ad3f-1b01-6a6a-a6865b4b7624
Version Independent ID: 84184d50-3c9b-cce9-6007-3ef2e954cdf5
Content: Load images and assets tailored for scale, theme, high contrast, and others - UWP applications
Content Source: windows-apps-src/app-resources/images-tailored-for-scale-theme-contrast.md
Product: uwp
Technology: data-and-files
GitHub Login: @lastnameholiu
Microsoft Alias: alholiu

Thanks!


[Save Measurements] issues when measurements are retrieved

Bug Report
Issue 1: Retrieved measurements are always displayed on the first viewport when we have multiple viewports
When user has multiple viewports and tries to navigate between the measurements (by clicking on each measurement inside the measurements panel), the measurements retrieved are displayed only in the first viewport.
If user activates another viewport and clicks on any measurement inside the right panel, the retrieved measurement will be loaded on the first viewport, ignoring the user selection.
Steps to Reproduce:

Load a Patient Study that has Measurements saved (i.e. Juno)
Set viewport layout to at least 3
Open Measurements panel
Click on first measurement item, under Measurements panel
Verify that the measurement annotation will be retrieved on the first viewport
Set the second viewport active by clicking on it
Click on any measurement item, under Measurements panel
Verify that the measurement annotation will be retrieved on the first viewport and not on the second viewport

Expected Result

Retrieved measurements should be displayed in the active viewport and not always in the first one.

Issue 2: Some annotations are not being retrieved when Image has multiple measurements saved
When image frame has multiple measurements on it, some annotations are not being displayed in the viewport. Although all the measurements are listed under the panel, if user clicks on each of them, some are not being displayed on the viewport. If user makes any changes to existing displayed measurements, the "missing" measurements start to load/show up. (please see gif below)
Steps to Reproduce:

Load Patient Study: Juno
Select 3rd thumbnail (Serie 4), and scroll to Frame 71 (Img: 71 71/174)
Open Measurements panel
Verify that only 5 measurements are displayed on this frame
Click on Measurement items with index from 11 to 18
Verify that none of them will be retrieved
Change some of the existing annotations on this frame
Verify that the missing annotations will start to show up

Expected Results:

All measurements should be displayed on the viewport
All measurements should have a distance/size displayed in the panel. The smallest measurement size/distance accepted should be 0.0 mm and not ....

These are great reports! Thank you. I think we need to do a bit of digging and discussion before we start on solutions for these, but I'll shift this to a verified bug that we intend to address.

@jbocce can you verify this against latest master?

No longer reproducible in master.


Unknown CPI error 'Unknown' with message 'Segment port with attachment id:  not found' in 'set_vm_metadata' CPI method

Describe the bug
When apply changes, CPI cannot find attachment id, I guess it's because Policy API is declarative, async call, which actually needs the caller to wait, see there are latest commit that changed the max wait time to 300, but actually I think we need to wait for the segment port realization right after the creation call, and make the wait timeout much longer. Or we can consult with some Policy API expert for a better solution.
Retry could make the case pass, but it's easy to reproduce.
To Reproduce
Steps to reproduce the behavior:

Create two instances in one AZ and disk .....
Sections of cloud config relevant to bug reproducibility

CPI Error Log
Can be obtained by running bosh <env params> task <failed-task-id> --cpi
Task 31 | 06:26:31 | Compiling packages: pks-nsx-t-curl/6bddcc90025505da7810d01040d8b9b01932ab35 (00:06:55)
                  L Error: Unknown CPI error 'Unknown' with message 'Segment port with attachment id: c186ec25-f580-49f1-bfee-bd7b49de90d8 not found' in 'set_vm_metadata' CPI method (CPI request ID: 'cpi-777113')
Task 31 | 06:26:39 | Compiling packages: pks-nsx-t-scripts/40fc194621b470e096284741f8bd80e005cd856e (00:07:03)
                  L Error: Unknown CPI error 'Unknown' with message 'Segment port with attachment id: 7c6591e4-5dbc-4c33-b725-16d556c601f7 not found' in 'set_vm_metadata' CPI method (CPI request ID: 'cpi-100837')
Task 31 | 06:26:43 | Compiling packages: pks-nsx-t-govc/7ecd5d2e99384bff262c681a78256c8d76923df3 (00:07:07)
                  L Error: Unknown CPI error 'Unknown' with message 'Segment port with attachment id: 45208491-39b0-4801-85a5-9a93e816f7f0 not found' in 'set_vm_metadata' CPI method (CPI request ID: 'cpi-954440')
Task 31 | 06:26:44 | Compiling packages: pks-nsx-t-jq/6fe9c981d95d718336b92bafc09b187ebdb2a85a (00:07:08)
                  L Error: Unknown CPI error 'Unknown' with message 'Segment port with attachment id: 64eae140-bb99-491f-92bb-5d92d6d72c5c not found' in 'set_vm_metadata' CPI method (CPI request ID: 'cpi-345031')
Task 31 | 06:26:44 | Error: Unknown CPI error 'Unknown' with message 'Segment port with attachment id: c186ec25-f580-49f1-bfee-bd7b49de90d8 not found' in 'set_vm_metadata' CPI method (CPI request ID: 'cpi-777113')

Expected behavior

Maybe should wait for segment port is realized to continue to execute
Wait for realization timeout should be longer

Screenshots
If applicable, add screenshots to help explain your problem.
Release Version & Related Info (please complete the following information):

CPI Version
BOSH Director Version
Stemcell Name & Version
vCenter Version
NSX(T/V) Version (If using)

Additional context
Add any other context about the problem here.

@ydp Please see the latest release https://github.com/cloudfoundry/bosh-vsphere-cpi-release/releases/tag/v57 It should solve this issue.

Please feel free to open an issue if it still fails.


Option to not sync SCM

Along with other checkboxes, new "sync" to ignore SCM.
Obviously this would carry a caveat that build steps would have to be carefully crafted since some SCMs provide different functionality than others; however, that would be upto the user not the plugin.

I downloaded the original commit as a patch and applied it locally.


LLMRouterChain should easily support multiple inputs

Feature request
As it stands, LLMRouterChain basically only supports a single input. Here is the template:
https://github.com/langchain-ai/langchain/blob/v0.0.314/libs/langchain/langchain/chains/router/multi_prompt_prompt.py
While it is currently supported to define multiple input variables on a PromptTemplate, the LLMRouterChain basically doesn't support it because of the way the output from the LLM call is handled.
{{{{
    "destination": string \\ name of the prompt to use or "DEFAULT"
    "next_inputs": string \\ a potentially modified version of the original input
}}}}

With a lot of massaging, you can get to a place where an LLM causes next_inputs to be a comma-separated dict-like object but, down the chain (pun intended), you end up with an explosion because the way inputs are passed to chains doesn't handle this.
Overall, this implementation is odd. It expects the LLM to massage the original input(s) and then wants to use that output directly in future things.
Wouldn't it make more sense to simply ask the LLM to reason out which destination to send to (alone) and then take the original inputs and pass them along?
This current implementation is combining two things into one:

a routing decision
paraphrasing user input

The whole purpose of Langchain is to chain things, so why wouldn't you have "paraphrase/rephrase user input" as a chain step, instead of smushing it into the router implementation?
Motivation
I have a use case where various inputs are collected separately and need to be maintained separately for a custom-tuned LLM later on. This caused me to attempt to use LLMRouterChain with multiple inputs, whereby I hit the roadblock described above.
It doesn't seem that wild to want to be able to make a routing decision based on input A, input B, or multiple inputs, and subsequently send all of those inputs to different templates later.
Your contribution
I don't really have sufficient coding skills to help. I could maybe make some diagrams that help illustrate how this could work.

Hi, we are a group of 4 Computer Science students. We think this issue is interesting and would like to work on this. We are confused about why LLM causes next_inputs to be a comma-separated dict-like object. By saying "multiple inputs", do you mean instead of taking in 1 string as input, it should be able to take in a list of strings. In that case, what kind of output are you expecting? Can you please provide more information on this so we can understand better, thank you!

Imagine you have a user query, "What sandwich can I make?" and then you have an RAG that has added available ingredients. These would be two inputs that go into specific places in a prompt template.
The router then would say, "Oh, since the user is asking about sandwiches and I have an ingredient list, I should use the sandwich-maker-tool."
I have a scenario that is essentially like this where the user's query is combined with some additional context that then needs to be routed.


adding davinci-002 to the gpt autocomplete set

Arising from a conversation with Nate on Discord

looks perfect, thank you!


owners: add Greg Greenway

Congrats Greg and thanks for all your hard work!

@ggreenway @envoyproxy/maintainers

@ggreenway you should be able to merge this PR and your other PR. Please make sure it works.


default steps bugfix

Description
change to set the number of steps DEFAULT_NUM_STEPS when steps is None. This happens for a command line "go left 1 feet". We cannot parse 1 feet and thus default to a fixed number of steps.
Type of change
Please check the options that are relevant.

[x] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change

Type of requested review

[ ] I want a thorough review of the implementation.
[x] I want a high level review.
[ ] I want a deep design review.

Checklist:

[x] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.

Closing because of staleness.


Include your Feature Requests Here!

Comment below for any features you would like to be added. Please add some example to make it easier to understand :)

I would like to have a concat2 var x:[] u8 please

A format function implementation to allow for String to be printed directly.
I already have a working update for this.
pub fn format(
    self: *const String,
    comptime _: []const u8,
    _: std.fmt.FormatOptions,
   writer: anytype
) std.os.WriteError!void {
    if (self.buffer) | buffer | {
        return writer.print("{s}", .{buffer[0..self.size]});
    }
}

An implementation of format() to allow for the String to be written to a writer.
I was thinking as simple as this.
pub fn format(
    self: *const String,
    comptime _: []const u8,
    _: std.fmt.FormatOptions,
    writer: anytype
) std.os.WriteError!void {
    if (self.buffer) | buffer | {
        return writer.print("{s}", .{buffer[0..self.size]});
    }
}

If need be the format options can be tapped into and the resulting print being formatted according to the options

Could you please update the time complexity column? It doesn't make sense to say f(n) is at best O(g(n)), as Big-O notation tells us upper bound already, at best tells us about lower bound, so the sentence 'f(n) is at best O(g(n))`' basically says nothing.
Or am I getting wrong the meaning of "best"? Either way best case big-O is confusing.

Just removed that column since its kind of pointless. I doubt myself when I use Big-O all the time haha.

I'd like a string replacement function!
Reference C code: https://stackoverflow.com/questions/779875/what-function-is-to-replace-a-substring-from-a-string-in-c

I have been working with unicode and lexing lately. Maybe it could be in the scope of the library to offer unicode classification and regex matching.
I experimented with Zig's comptime to see if it was possible to generate a minimal automaton for regex recognition, and indeed it is (I love comptime ❤).
I also experimented with binary search to detect if a character belongs to a unicode class (which I parsed from the official database).
If I have time, and if it is of interest, I'll make a repo with a demo for both features.

Maybe make the zig-string.zig file it's own struct so instead of doing
const String = @import("string").String; you do const String = @import("string");
if you don't understand me, here is an example of what it looks like make the file the entire struct


Please update library deps to GMS 9.2.1 or higher

develop branch has an even updated version (v9.6.1). Closing this for now.


Feature Request: Downloading of Playlists

I know the actual web browser doesn't support downloading of playlists (but does albums and individual songs which strikes me as a very peculiar decision) but would there be a way of pseudo circumnavigating the restriction? The only way I can think of getting around this would be to have the app 'play' the playlist and cache to AppData/ProgramFiles and then when playing a song have it check for it in cache first before streaming.
Cheers

Unfortunately this isn't something we can or want to tackle. Downloading music in the application is not something supported by this player.


ChannelEditTopic

Literally just a copy. The other pull request (not from me) about this was closed, so this is another.

Most likely this will be solved with https://github.com/bwmarrin/discordgo/pull/322 by making ChannelEdit work like GuildEdit to accept a range of settable values.

Yep, good idea!


Implement Cairo0 class hash calculation

Can you please provide more context? I thought we already agreed to only compute it on the rust side.

I thought we already agreed to only compute it on the rust side.

It is an additional rust dependency. It would be nice if we could avoid it. But we can decide to keep depending on it until the regenesis.

If it is as simple as reverting a previous commit where we removed Cairo0 Class Hash then we should do it.


Python 3.6 dependency?

Is Python 3.6 required?

Pipfile says yes
https://github.com/pwyf/iati-canary/blob/1a01ce71933b7f8dd1e6d0c96e95fa18f95833c3/Pipfile#L26
I expect 3.7 will also be fine.
I suspect I’ve used f-strings, which require python 3.6+.


Cellular phone breath broadcast cannot accept, how solve

Cellular phone breath broadcast cannot accept, how solve

Closing due to missing details. Please re-open if you can share a code example or small example project that reproduces this issue. -ut


[Testing] Prefer pre-generated keys in tests

Objective
Enabling faster and more deterministic tests.
Origin Document

Goals

Ability to pre-generate an arbitrary number of keys
Pre-generated keys are accessible via vanilla go imports (see: storj/common testidentity pkg)
Pre-generated keys are tracked in version control (same keys everywhere: devs, CI, etc.)

Deliverable

[ ] Add a make target which generates the keys, output as go source code.
[ ] Add a package (e.g. testkeys; also see  #609) which exports a means by which to retrieve the pre-generated as cryptoPocket.PrivateKeys

I think the iterator pattern is nice for this because it fits well with our use case as we typically don't want to reuse keys (identity), across nodes for example.
It would be prudent to ensure that we can also retrieve specific identities, I think via index should suffice.

Non-goals / Non-deliverables

Refactoring existing tests to use pre-generated identities.

General issue deliverables

[ ] Update the appropriate CHANGELOG(s)
[ ] Update any relevant local/global README(s)
[ ] Update relevant source code tree explanations
[ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @bryanchriswhite
Co-Owners: @deblasis

@bryanchriswhite Though it is not pre-generated, we do have runtime/test_artifacts/keygen/keygen.go  which enables determinstic keys:
func (k *keyGenerator) SetSeed(seed int) (teardown func()) {
	k.privateKeySeed = seed
	return func() {
		k.reset()
	}
}

func (k *keyGenerator) Next() (privateKey, publicKey, address string) {
	k.privateKeySeed += 1 // Different on every call but deterministic

Do you think that's enough in terms of our testing utility to validate the need for this scope of work?

@Olshansk thanks for surfacing that! :raised_hands:
That should address the determinism aspect. The only other improvement I was anticipating would potentially be a speed improvement in CI (depending on "things" which I haven't looked into yet).
This issue was based on observations I made while debugging tests. It's definitely not urgent but I'm not sure how important it is (or could be, depending on "things").


Copy fails (CannotVerifyCopySource) when storage account firewall is enabled

Using azcopy 10.13.0 (Windows), with a storage account firewall enabled on the source and destination, copy between containers fails with CannotVerifyCopySource.
Sample command
azcopy cp "https://mysourceaccount.blob.core.windows.net/project/path/file.csv?sp=r&st=2022-02-15T15:59:11Z&se=2022-02-15T23:59:11Z&spr=https&sv=2020-08-04&sr=b&sig=asdfsafasdf%34ddfdsfas%sadf%af%3D" "https://mydestinationaccount.blob.core.windows.net/container/path/filename.csv?sp=rw&st=2022-02-15T17:32:00Z&se=2022-02-16T01:32:00Z&sv=2020-08-04&sr=c&sig=asdfsadfdsafdsf%afsdsaf%3D"

Sample Error -
RequestId:ceac92c2-f01e-0065-1a5b-23c0e2000002
Time:2022-02-16T17:34:46.1621358Z, Details:
   Code: CannotVerifyCopySource
   PUT https://destinationstorageaccoun.blob.core.windows.net/project/path/file.csv?se=2022-02-17t01%3A32%3A00z&sig=-REDACTED-&sp=rw&sr=c&st=2022-02-16t17%3A32%3A00z&sv=2020-08-04&timeout=901
   Content-Length: [0]
   User-Agent: [AzCopy/10.13.0 Azure-Storage/0.14 (go1.16; Windows_NT)]
   X-Ms-Access-Tier: [Hot]
   X-Ms-Blob-Cache-Control: []
   X-Ms-Blob-Content-Disposition: []
   X-Ms-Blob-Content-Encoding: []
   X-Ms-Blob-Content-Language: []
   X-Ms-Blob-Content-Type: [application/vnd.ms-excel]
   X-Ms-Blob-Type: [BlockBlob]
   X-Ms-Client-Request-Id: [c2f412be-17f1-4415-659f-eeeaa88f1127]
   X-Ms-Copy-Source: [https://sourcestorageaccount.blob.core.windows.net/project/path/file.csv?se=2022-02-16t23%3A59%3A11z&sig=-REDACTED-&sp=r&spr=https&sr=b&st=2022-02-16t15%3A59%3A11z&sv=2020-08-04]
   X-Ms-Version: [2020-08-04]
   --------------------------------------------------------------------------------
   RESPONSE Status: 403 This request is not authorized to perform this operation.
   Content-Length: [248]
   Content-Type: [application/xml]
   Date: [Wed, 16 Feb 2022 17:34:45 GMT]
   Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]
   X-Ms-Client-Request-Id: [c2f412be-17f1-4415-659f-eeeaa88f1127]
   X-Ms-Error-Code: [CannotVerifyCopySource]
   X-Ms-Request-Id: [ceac92c2-f01e-0065-1a5b-23c0e2000000]
   X-Ms-Version: [2020-08-04]

Problem can be replicated by attempting a copy between shares on different storage accounts which both have a storage account firewall configured.
Disabling the storage account firewall on both the source and destination works.
The same problem is reported and closed @ https://github.com/Azure/azure-storage-azcopy/issues/755

@vijred you need to add vm or machine where AzCopy runs to allowlist on both source and destination storage accounts. Further the source storage account must be reachable from destination account.

That means absolutely nothing. @nakulkar-msft

The networking config for a storage account has no connection for VMs or allowed IPs.
How come this thing is not well documented? This is Azure! paid for with hundred thousand dollars a month by the average customer. not some unsupported open source project.

Same question, it should not be closed, does the azcopy copies data from destination instead of using the local machine ?

Hi all! This issue is not something AzCopy can fix or handle. The destination cannot read the source in this scenario. The best solution is to whitelist IPs. Please view this documentation for additional information: https://github.com/Azure/azure-storage-azcopy/wiki/Troubleshooting---FAQ#firewallprivate-endpoint-issues


Suggestion: Option to import and export sets

Option to import and export a set from/to the clipboard via copy and paste buttons or hotkeys

Duplicate of #19


add 'copy address' button to already active addresses on android wallet

Feature title
Add 'copy address' button on mobile wallet
Describe the current situation we have
The only way to copy an address in mobile wallet is to create a new receiving key
Describe the solution you'd like
To stop cluttering the wallet with many new keys, enable the reuse of previous addresses.
Describe alternatives you've considered (if relevant)
n/a
Additional context
thank you

@kaminskyelina @sasha-abramovich Can you help with it? It's really looks inconvenient

checked


Setup OCaml Foundation

Overview
This is the proof-of-concept for an attempt of creating a highly reproducible build system inspired by Nix and other hermetically sealed build systems.
WIP

[x] storing files in a "store"
[x] hashing versions with Sha256

lgtm


Sass 1075 - Differentiate overview page

Description
Differentiating the overview page based on whether in year or at the end of year
Add a link to the relevant story in Jira
SASS-1075
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ]  Have you checked to ensure its been rebased against the current version of master?

Whilst Reviewing

[x]  Have you run the tests?

[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current master that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of master?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[ ]  Have you checked the PR Builder passes?

can we also bump some dependancies please


Layer support

Is your feature request related to a problem? Please describe.
Some compositors like niri will tile the launcher, and other applications can go above onagre
Describe the solution you'd like
support setting as top layer on wayland
Additional context
I have done a brief search and found a crate which supports iced layers
https://github.com/waycrate/exwlshelleventloop and more specifically https://crates.io/crates/iced-layershell

I forgot, as an alternative supporting https://gitlab.freedesktop.org/mstoeckl/windowtolayer would be nice, currently in testing it just becomes a maximized window


Add native unit test support for desktop in flutter/plugins

We're currently working on ensuring that most plugins have native unit tests set up (historically the focus has been on integration tests), which highlighted the fact that we don't currently have any solution in place for unit testing native desktop plugin code.
What we need for each platform (Windows, macOS, and Linux) is to:

decide on a unit testing framework
add a proof-of-concept to at least one plugin
add knowledge of how to run those tests to flutter_plugin_tools

My expectation is that we would likely use XCTest for macOS (it's already what we're using for iOS, so should be very straightforward), gtest or CTest for Linux (@robert-ancell, thoughts?), and likely the same for Windows as for Linux (since they both use CMake, so should be able to be similar, reducing the number of test systems people need to know).
/cc @cbracken
We could track this with separate issues per platform, but my hope is that this is going to be straightforward enough that we won't need to, and can just check of platforms here:

[ ] Windows
[x] macOS
[ ] Linux

I haven't used CTest, but have used GTest quite a bit. I think the latter would be an appropriate match given the use of GLib code.

I haven't used CTest, but have used GTest quite a bit. I think the latter would be an appropriate match given the use of GLib code.

I just realized that you were presumably talking about GTest whereas I meant gtest aka GoogleTest. I wasn't aware of the former.
It would be good to understand how different the setup for the two would be, and the advantages of GTest over GoogleTest (since I expect we'll be using the latter for Windows already).

gtest or CTest for Linux (@robert-ancell, thoughts?), and likely the same for Windows as for Linux (since they both use CMake, so should be able to be similar, reducing the number of test systems people need to know).

One aspect that I hadn't considered until today is that because we want to add unit test support to the template (https://github.com/flutter/flutter/issues/82458), something that requires extra installation like GoogleTest probably isn't ideal. While we don't have to use the same test format as the template, it would be potentially confusing for people looking to flutter/plugins as a model.

Looking at CTest more, it turns out it's not a framework for writing unit tests, just for building and running them, so that wouldn't cover what we need.
VS includes GoogleTest, so hopefully we acn use that pretty easily on Windows. @robert-ancell Does our current set of library dependencies include GTest transitively, or would we need to have people install it?

Ah, but we could also consider having a GoogleTest dependency pulled by CMake itself: https://google.github.io/googletest/quickstart-cmake.html#set-up-a-project


Adding files for Range Dome Analysis

Adding files for Range Dome Analysis.
Added: Toolboxes, Common Data for symbology rules from city engine and data examples for the tools to run properly.
┆Issue is synchronized with this Asana task

Going through the Range Dome PR and got a few things that aren’t looking good for these tools. I know you didn't create them, but between the two of us we need to figure this out before we can merge them. I'm not confident this is a time where we can just merge it as-is and fix it later. In general the stuff here doesn't seem to match what I'm reading on the Solutions Page (http://solutions.arcgis.com/defense/templates/range-dome-analysis/).

There are two toolboxes, the names are funny and don't match the others, and one of them has no tools. Also neither of the toolbox names matches what is on the Solutions page.

My recommendation here is to kill the empty toolbox and keep the existing one (with name change) to match the other tools in the repo, and in the ArcGIS platform.

The one tool in RangeDomePyProTools.pyt is Detect non-closed volumes (not creating range domes?) and does't have any tool help (the associated XML has header info but no content). Looking at the Solutions page isn't there a tool to create Range Dome Corridor,

My recommendation here is much harder. We need documentation for this tool. We cannot have tools without doc.

There are two geodatabases RangeDomeAnalysis.gdb which is empty, and rangeoutput.gdb which has a bunch of features in it. It seems that rangeoutput.gdb is data output from the tools used in the template which doesn't server a purpose here. The tooldata stuff is where data the tool requires to run is stored. This also doesn't quite match what is listed in the Solutions page.

Again here, my recommendation is to drop the tooldata.

@mfunk
Addressing your issues:
1.
Just added the tools that were missing and changed the name of the toolboxes to include the PYT toolbox.

This is a relic of the old template that I am not sure has much use. This has been deleted.

Closing this one without merging as Range Dome Analysis is being deprecated.


Flatten buttons, support any label for dual button, fix dual hover, fix unbranded wide content

@vishakha94 updated code, lemme know if you have any comments!


Rubotium doesn't find any tests when using Espresso with AndroidJUnitRunner

In our project we are using Espresso to create UI tests. Since Espresso 2.0 Google supplies a new test runner for projects to use called android.support.test.runner.AndroidJUnitRunner.
When running these tests from gradle via ./gradlew clean connectedAndroidTests 1 test is executed per device.
But calling rubotium via
rubotium -t app-test.apk -a  aop,apk -r android.support.test.runner.AndroidJUnitRunner
I'm getting a lot of output but lastly resulting in calls like
EXECUTING_COMMAND: adb -s<PHONE_NUMBER>4348585753 shell am instrument -w -r -e log true com.example.myapp.test/android.support.test.runner.AndroidJUnitRunner
There are 0 tests to run

with result.xml as
<testsuites></testsuites>

What do I do wrong?

could you double check please? there seems to be a bug in the line you've pasted aop,apk .
We call it in the following way and all flies:
rubotium -a application.apk -t tests.apk -r android.support.test.runner.AndroidJUnitRunner

Sorry, that was just an error by me avoiding leaking any private project info. The line was correct without my redaction.

That's strange, the Android's shell command am instrument

Which device have you used?

for some strange reason, with Espresso the logOnly flag does not work
adb shell am instrument -w -r -e log true  your.package/android.support.test.runner.AndroidJUnitRunner results in tests being executed but the -e log true should actually prevent that.

@ssmiech Yeah, @brigitlyons posted a bug report that is supposedly fixed in the next release of the testrunner.

https://code.google.com/p/android/issues/detail?id=196066

@stefanhoth @brigitlyons
Surprisingly, removing @RunWith annotation fixes the issue.

The issue comes from AndroidAnnotatedBuilder which completely ignores the logOnly parameter and creates AndroidJUnit4 runner instead of NonExecutingJUnit4ClassRunner


refactor: reorganize Tags.lua for easier contribution

Most people will be likely be interested in editing the dungeonTags table.

#50
#49  👈
working-trunk

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

Join @juemrami and the rest of your teammates on  Graphite

Merge activity

May 20, 8:46 PM EDT: @juemrami started a stack merge that includes this pull request via Graphite.


Copy button improved and few other tweaks

solved #355
copy button is improved.

Hi @dk3775 is it good now?

It works perfect in desktop view and looks fine too, but here's the issue

Fix the button beside To Geek text.
Also Fix or redesign twitter button.

Should it look like galaxy S9 (both buttons side by side) or like pixel 3a xl (both buttons one over the other)

I think it should look something like this

PS: ignore my drawing but get the idea, still tell me if I am not clear enough.

Is it necessary to put copy button above Twitter button or it can be like pixel 3a XL i.e. Twitter button above and copy button below

order works fine
but layout is what I am pushing on

Ok 👍
Got it

Solved?

@dk3775 I guess it solved pretty much everything now.
Still tell me if something left

Perfect as per needed.
Still if you want to go on then fix this text box margin or tell me I will merge this PR.
Once again thanks !!

Which text box and which side are you talking about. Can you please explain.

I think maybe we should change the background color of that Twitter button. Your thoughts? & I've also edited the margin of the text area kindly check it out: https://github.com/swapagarwal/geeksay/pull/392. One thing more, I was also thinking about making the code cleaner eg, creating a separate CSS file, making JS code better, etc.

Hey @RohanTheProgrammer the texbox overflow issue is fixed by #392 from @Muhammed-Moinuddin no longer need to work on it.

oh! noice work @Muhammed-Moinuddin.
and I personally liked your suggestions


Replace git log with more targeted commands in release flow

git log was being used to verify whether the tag exists and points to
correct commit and to see whether the version bump commit was correct.
Both usages are now replaced with more appropriate commands to reduce
noise from large git log output in CI logs.

This is what each of them output for example on current release:
hashhar@Ashhars-MacBook-Pro docker-images % git show tags/66
tag 66
Tagger: Trino release automation<EMAIL_ADDRESS>Date:   Thu Aug 18 07:30:58 2022 +0000

commit 9baef94e75ebeb33f96150c07ee9f3c73182876b (tag: 66)
Author: Trino release automation<EMAIL_ADDRESS>Date:   Thu Aug 18 07:30:58 2022 +0000

    Release: 66

diff --git a/version b/version
index 212dba8..69a893a 100644
--- a/version
+++ b/version
@@ -1 +1 @@
-66-SNAPSHOT
+66

and
hashhar@Ashhars-MacBook-Pro docker-images % git show HEAD
commit f14e32639c5adc8f41990240151cf22d94922f8a (upstream/master, origin/master, origin/HEAD, master)
Author: Trino release automation<EMAIL_ADDRESS>Date:   Thu Aug 18 07:58:09 2022 +0000

    Prepare for next development iteration

diff --git a/version b/version
index 69a893a..967ac01 100644
--- a/version
+++ b/version
@@ -1 +1 @@
-66
+67-SNAPSHOT


Powersheell -> Powershell

Fix spelling mistake in Azure CLI V2 task

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


updated readme

Coverage remained the same at 66.949% when pulling ad2e69373db40db75fac9d3c13c034ea5c8dcab8 on readme into ca3339eeadda1ac39fdc6fb7ffccb5f627346664 on master.

Coverage remained the same at 66.949% when pulling 75e0a4e001bf21f04a6cbea136d107e19c750269 on readme into ca3339eeadda1ac39fdc6fb7ffccb5f627346664 on master.


feat: Calendar and scheduled drops preview 📅

PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context
❗❗ Needs https://github.com/kodadot/private-workers/pull/91

[x] Closes #9634

Needs QA check

@kodadot/qa-guild please review

Needs Design check

@exezbcz please review

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI;

Ready for release? 🫡

@yangwao probably not as its still draft

Ready for release? 🫡

ready , needs https://github.com/kodadot/private-workers/pull/91

otherwise we can merge?

otherwise we can merge?

not from this pr -> issue https://github.com/kodadot/nft-gallery/issues/9827

Thanks!
pay 80 usd

😍 Perfect, I’ve sent the payout
💵 $80 @ 9.38 USD/DOT ~ 8.529 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0xc8983deac748955cf22687d67e01f73879285ab6eef04de54cd527088484ebb7
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

@hassnian Could you please check the request error regarding the empty drop calendar?


Manual Python 3.9 Migration

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are recommended to have a lower bound on minimum python bound. This recommendation will become requirement in a future version.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Why is this needed, isn't this package noarch: python?

Currently I can not install it in a Python 3.9 environment, I get the following error:
six[version='>=1.14.0'] -> python[version='>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0']

In addition there was a python 3.8 migration before.

mamba create --name test python=3.9 six works so I think it's just conda's conflict message being unclear (it's probably found a corner of the space where it uses an older build of six).
Can you share the conda command that fails? (Or the PR if it's a conda-build that's failing)

I try to update our test environment:
https://github.com/pyiron/pyiron/pull/1130

I've not looked why it hasn't been migrated but this should help get you there, else we can continue on gitter:
$ mamba env create --file environment.yml --name pyiron
conda-forge/linux-64     Using cache
conda-forge/noarch       Using cache
pkgs/main/linux-64       [====================] (00m:00s) No change
pkgs/main/noarch         [====================] (00m:00s) No change
pkgs/r/noarch            [====================] (00m:00s) No change
pkgs/r/linux-64          [====================] (00m:00s) No change

Looking for: ['python=3.9', "ase[version='>=3.20']", 'coveralls', 'coverage', 'codacy-coverage', "defusedxml[version='>=0.6.0']", "dill[version='>=<IP_ADDRESS>']", "future[version='>=0.18.2']", "h5py[version='>=2.10.0']", "matplotlib[version='>=3.2.0']", "mendeleev[version='>=0.5.2']", "molmod[version='>=1.4.5']", "numpy[version='>=1.18.1']", "pandas[version='>=1.0.1']", "phonopy[version='>=2.4.2']", "pymatgen[version='>=2020.9.14']", "pyiron_base[version='>=0.1.24']", "pyscal[version='>=2.7.5']", "pytables[version='>=3.6.1']", "quickff[version='>=2.2.4']", "scipy[version='>=1.4.1']", "seekpath[version='>=1.9.4']", "six[version='>=1.14.0']", "scikit-learn[version='>=0.22']", "spglib[version='>=1.14.1']", "tamkin[version='>=1.2.6']", "tqdm[version='>=4.43.0']", "yaff[version='>=1.4.2']"]

Encountered problems while solving.
Problem: package yaff-1.4.2-py27h516909a_2 requires python >=2.7,<2.8.0a0, but none of the providers can be installed


Feature Request / Discussion: Airframe group definitions for Planes

Feature Request / Discussion
The PX4/QGC airframes  for planes are in my opinion somewhat ambiguously defined. The obviously good concept of grouping airframes was contributed here. Currently, there is the groups "standard plane" and "Plane A-Tail", i.e. we group them by tail configuration. However, the planes in these groups also seem to differ by their flap configuration (Plane A-Tail: Two separate flaps, Standard Plane: Flaps on same servo output or not even connected).
Overall Question: Why were the groups chosen that way? I assume just because at that time there was only a limited amount of platforms. Overall however, I could think of the airframe types:

Plane A/V-Tail, with 2 separate flaps
Plane A/V-Tail, with 0/1 flaps
Plane T-Tail, with 2 separate flaps
Plane T-Tail, with 0/1 flaps (current group: Standard plane)

These groups would cover a wider range of configurations. Specifically I am thinking about adding a) Multiplex EasyGlider (proposed group 4), HobbyUAV Techpod (proposed group 3) and RP Flight Systems Vigilant C (proposed group 1).
@hamishwillee Seems like you were heavily involved in this.

Keep this open


Optimise cached_head_ptr calls within process block

Closes #4972

Let me know if the sections for process_block could be better, i was unclear how to divide it into more sections


Refactor fetching token information: symbol, decimals, etc

Current logic for fetching token information is overcomplicated and not working properly (https://github.com/gnosis/safe-react/issues/1068).
So, the problem:
Currently token information is fetched for a transaction inside fetchTransactions (https://github.com/gnosis/safe-react/issues/1070). This shouldn't be a thing, imagine the following example:

we get a transaction with an unknown token, we fail to fetch info and now showing UNKNOWN
later we get this token info from the backend
UNKNOWN will still be shown because the token info is tied to the transaction

Possible solution:
Implement a react component for displaying token symbols with a usage like this: <TokenSymbol address={}
It should get the symbol from state, if there's no info in state, fetch it
This function should work as a good base: https://github.com/gnosis/safe-react/blob/a5b45850494097e7b288e84dc25e0b8a8a017564/src/logic/tokens/store/actions/fetchTokens.ts#L60

While working on this I realized that there are tokens logos that are correctly fetched from the backend, but we got a forbidden when we try to display it on the UI.
Here are two examples for both Rinkeby and Mainnet:
Rinkeby:
address: "0xddea378A6dDC8AfeC82C36E9b0078826bf9e68B6"
name: "0x"
logoUri: "https://gnosis-safe-token-logos.s3.amazonaws.com/0xddea378A6dDC8AfeC82C36E9b0078826bf9e68B6.png"

Mainnet:
address: "0xDcbeD5AC782fCE3F4379186ce773D80CCceC5f88"
name:"Ethereum Classic"
logoUri:"https://gnosis-safe-token-logos.s3.amazonaws.com/0xDcbeD5AC782fCE3F4379186ce773D80CCceC5f88.png"

Could be this a problem relayed to the configuration of aws that devops should give it a look? @lukasschor @mikheevm @Uxio0

@Agupane I cannot access those token logos

I'm not really sure, it's the info that comes from the backend, I cannot access to them too

so this is 0X token logo (notice it has a different address on mainnet): https://gnosis-safe-token-logos.s3.amazonaws.com/0xE41d2489571d322189246DaFA5ebDe1F4699F498.png

and for ethereum classic it doesn't seem to be a token address on mainnet: https://etherscan.io/address/0xDcbeD5AC782fCE3F4379186ce773D80CCceC5f88

@Agupane Backend returns a link for every image automatically generated using the token address, but some does not exist so you cannot access them

Ahhh got it, now it makes sense, thanks for the clarification! @Uxio0


Update _index.md

👷 Deploy Preview for rohitshubankar processing.

Name
Link

🔨 Latest commit
1cb4fe5cf678f2d2626bc8d726c142d0a76936b3

🔍 Latest deploy log
https://app.netlify.com/sites/rohitshubankar/deploys/64f6e5ed7df7e30008e0572f


Version bump to 2.0 after adding Tailwind 1.0 support

Hey @brandonpittman,
Introducing support for Tailwind 1.0 is a breaking change and the package should probably be bumped to 2.0.0.
We have "gridsome-plugin-tailwindcss": "^1.0.6" in our package.json and when our build system (Netlify) get's the packages it pulls in the latest version 1.3.2 which breaks because the config is completely different. We've locked the package to 1.0.6 now but it took an hour to figure out what was going on as there's no clear error explaining what has happened. Also this issue really didn't help as we assumed this plugin hadn't updated to 1.0.
Anyway just posting this here to hopefully help other people and appreciate you maintaining the plugin 👍

Thanks. Should've paid more attention to semver. It's been bumped to 2.0.0.

Nice one, thanks @brandonpittman


Updated UI, user experience and README for "Air-Quality" project

🛠 Issue (#827)
Closes #827
Description
I have addressed the UI concerns and implemented several feature improvements for the "Air-Quality" project. This pull request aims to enhance the user experience and make the application more visually appealing and interactive. Also README is updated .
Type of change

*Updated README * : I have updated README with current changes made to projects by adding sections like features, contributing and how to get started.
Updated Color Scheme and Theme: I have revamped the color scheme and theme of the application to provide a more pleasant and comfortable viewing experience for users. The new colors are carefully chosen to create a harmonious and visually appealing interface.
Improved Text and Coordinates Search UI: I have resolved the misalignment issue in the coordinates search component. The text and input fields are now properly aligned, ensuring a more organized and user-friendly interface. Users can now input the desired coordinates accurately and effortlessly.
Enhanced Result Presentation: Instead of displaying the results below the page, I have implemented a modal popup to showcase the air quality details. Now, upon clicking the "search" button, the results appear in an interactive modal, eliminating the need for users to scroll down. This improvement significantly enhances the usability and accessibility of the application.
Attractive Section Layout: I have redesigned the other sections within the page to improve their visual appeal and engagement. The layout has been optimized, and font size and style have been adjusted to create a more aesthetically pleasing appearance.
Error Handling and Validation: I have implemented edge case handling for the input fields. Now, if any of the fields are empty, appropriate error messages are displayed, guiding users to provide the required information correctly.
Animation for Interactivity: To make the application more interactive, I have added animations to the modal popup. The modal now appears from the bottom with a smooth animation, providing a delightful user experience. Additionally, when the "close" button is clicked, the modal vanishes with a top animation effect.

Screenshot :
Now ⬇

Before ⬇

Testing
I have thoroughly tested these enhancements to ensure their correctness and compatibility across different devices and screen sizes. The application now offers an improved UI, better user experience, and addresses the concerns raised in the initial issue.

@Arun9739 @TusharKesarwani @harshit-paneri Sir Please review and merge this pull request. This resolves the concerns raised in issue #827.

hey may i know the reason of being marked as spam. What's the problem in requesting a review for my PR ? it was a single comment just to ping for review.

sry by mistake.

ohh it's fine sir


Make queue declaration optional

Current implementation calls QueueDeclare automatically for RabbitMQTriggerAttribute queue.
I want to manage queues manually.
Could you, please, add some option to disable automatic queue declaration?

@asud-solvve  Aplogies for the late reply.
Is this something your still experiencing with the latest version of Azure.
ThankYou  for the patience

@jeffhollan FYI for things to track for GA
/cc @pragnagopa

@asud-solvve - We do support binding to the rabbitmq client
Here is an example on how to do that:
https://github.com/Azure/azure-functions-rabbitmq-extension/blob/214497c70e28208022c16acf71bf21fb77721da8/test/WebJobs.Extensions.RabbitMQ.Samples/RabbitMQSamples.cs#L79-L87
Is that what you are looking for?

@pragnagopa Is this also possible to do with the RabbitMQTrigger? I want to bind to a queue with the trigger, but I do not have access to create queues, which results in getting rejected.

@cachai2 for tracking

Closing this since we removed the ability to create queue as part of extension that was tracked here #109


fluid.bufstats~ should treat a buffer of zeroes like any other equal values

As discussed in #198, there is a use case when loudness-weighting descriptors and analyzing digital silence where fluid.bufstats~ throws up a yellow Invalid Buffer error message.
I'm of the opinion that this is an engineering problem rather than a user problem where what the user is asking for (in this case, loudness-weighted descriptors) creates a technical edge case that they shouldn't have to think about (similar to rounding numbers for fft sizes, or scaling the internal envelope follower in ampslice so it doesn't start at negative infinity etc....).
I can't read through the code well enough to determine whether this is the case, but I would be surprised if AudioGuide/IRCAM approaches to loudness-weighting throw up similar errors when presented with digital silence.

I closed #198, but posted this code example there.
Basically there's audio you can't analyze unless you build in some edge-case detection stuff around the objects.
----------begin_max5_patcher----------
799.3ocuVssbaBCD8Y6uBM7LwitAH5S9+nSmLxfvVIXIFPD61LIe6ck.mFm3
1ZhcxKwQqVocOmytK5w4yhVY2q5hPeC8czrYONe1rfIugYiqmEsUtunV1EbK
ZqpqStVEEOrmSs2ErWoqqQ3EjCazzp5TFmzoslaq0FUgs2DbkN5goeqs2Uqb
gKlLZcvj6mMpgrJJB8iCWozUrQaVeaqpvMraFMaQdJgJDILVhPvSDwnLxBBI
gIH4rTFilQhQb7BbLhRWfe41fvqMGh9gbRWF.ic0c2jG4M8z749+DegrSmS1
5pZkaUHHOVIMqithrPBaAmCnkJvXlflJ.Rfm6QLAmNYfKtl.err3Zh1TA6rz
bFaxPO8i.ciZGb12g7U8UUp1mQNUmCzAL9zb.8uwAU0VoKJFtHe0xjIDBl+N
FIO+eyHj2yHrqHiTU2qKW.7BzM35dFsrSUCf.sUIMnkPlTpZ0OzgHSjo7jzj
6OnvHAFOkv4zbg.HuLNXLGuHAbLIICnLbRlm0l1TC9mBg0.XoUV2sQ1n7Dms
usPMTZsrpx0A7A.4NDMIEkxQIDJZIDA+V5eofwe4oAFtXiz.Db3+CiiFNxxF
6NUq2duQ67+1HKKgaDQeQkJfo4sVcIppV5LP69gz8ng67u.o6Tk1zz72qboS
oRmREeJRWgrNHY9u.3oeD9XkPaZ.VwtCcCLjXb4F85Md+Jp0MMdYfcRxldkI
aFkehAIBvHkgy3bLmmmiSow9hF+nDVxDH3rOE9s11W5qFeaWwqo3cZSocWnS
HTsCA3UlFZN1XaBqftmk2uSABfuixKBt1dUiRd+nvcTaygtjSJOruD44DMCr
gO84eBvYqNGM2Jbp.XdyaCCYk29wJ1.yOhigGOEi9SrKAEQaBOE7U9vF74j0
Dmab3mQbf5tKOPhyHPGmL1V3yY9cwWTf8ik9+gNm+Egw2lNufRxEE5ryFjjK
DjoenJygFBYSyCp1tQmCg.FVcmMP.h3vRsYXYn4OpU8f9f+gltHYKzV6fd59
1PZEsOkGMbTKPkld8HaBfCBYXPnwOwoQNfiv7x4OM+2.KncTUB
-----------end_max5_patcher-----------

Basically there's audio you can't analyze unless you build in some edge-case detection stuff around the objects.

I've said a couple of times now that the reason the object squawks on all-0-weights is that there isn't a sensible default action to take that covers all cases because those numbers could be anything, and a sensible thing to do ends up being task dependent. So we have to leave the responsibility to the caller to either avoid it or decide what to do. If you want to convince us to change it, then we'll need a proposal for a sensible default that would make sense in a very wide range of situations, not just one.
As for whether this is an edge case when dealing with loudness data, I don't think it is:  it's inherent to using loudness as a control source that silent frames need to be safely dealt with. I can't think of anything I've done with loudness that hasn't needed this to be handled.
If all you need in this case is for silent frames to be unweighted rather than ditched, then add @outputlow 0.1 (or whatever number) to your bufscale~.

I've said a couple of times now that the reason the object squawks on all-0-weights is that there isn't a sensible default action to take that covers all cases because those numbers could be anything, and a sensible thing to do ends up being task dependent. So we have to leave the responsibility to the caller to either avoid it or decide what to do. If you want to convince us to change it, then we'll need a proposal for a sensible default that would make sense in a very wide range of situations, not just one.

I'm struggling to think of a case where having the object throw up an error and dump out dummy values is beneficial. Is there a type of weighting where having zeros treated as "all values are equal" would be bad, or even a less-than-ideal? The main (only?) use cases for having weights as inputs I can think of are loudness weighting (the main reason the object was created if I remember right) and pitch confidence. In either of those cases if your loudness/confidence are zeros (loudness more clearly so), the object should just pass on the stats unweighted as at the moment it spits out zeroes (which for loudness would be "pretty loud"), which would actually be bad data.
Just imagining a similar UX for other objects like setting the @minfreq of fluid.bufmelbands~ to something like @minfreq 200 and then worrying or building code for the potential edge case of analyzing something that has frequency content below that.

The main (only?) use cases for having weights as inputs I can think of are loudness weighting (the main reason the object was created if I remember right) and pitch confidence

These are by no means the only things one could use as weights, because the weights are simply some probability distribution-like bunch of numbers. They could be counts of some things, they could be the results of sampling some generative process. They could be arbitrary weightings tied to time indexes to reflect some domain specific knowledge the coder has about their data.
Loudness and pitch confidence were certainly motivating uses, but the weights were added as a general mechanism that happened to allow those specific things. All it requires is that the numbers in the weights can be made to sum to 1. So, all 0s and things that cross the 0 boundary are bad and require the caller to do some extra work reflecting their knowledge of the task at hand.

it spits out zeroes (which for loudness would be "pretty loud")

Or very quiet, depending on the loudness units. Which bufstats~ can't know.

Just imagining a similar UX for other objects like setting the @minfreq of fluid.bufmelbands~ to something like @minfreq 200 and then worrying or building code for the potential edge case of analyzing something that has frequency content below that.

This is beginning to feel needlessly snarky for something where you can literally get the behaviour you want by changing a single attribute value upstream. melbands::minfreq is just saying 'well, if you're making a filter bank, start here' – it's completely tied to the domain of the object, and interpretable. Even asking for garbage like @minfreq ∞ is easier to reason about than 'a probability distribution for which there is 0 probability of anything happening'.

So we can agree that when weights of zeros come in that that is problematic. The current solution is to spit out zeros as the output (regardless of the input), which I'm arguing would never be a preferable alternative to just spitting out the stats with no weights applied (another (IMO) "valid" interpretation of the weights).
At minimum, I would think that the current implementation would be such that a red warning should be issued and no output should be passed since that is more in line with the philosophy of the implementation: "there is a problem".
That was a post-flight late night post, so I appoligize for coming across extra sassily.

I'm much more amenable to treating it as an error, and it turns out that on its first commit, that was indeed what happened. I think it changed because without (yet) having programmatic error handling, it was deemed too disruptive to doing big batch analyses (though spitting out junk instead doesn't really delight me any more than it does you).
So, for me this bumps the need for programmatic error handling up the queue somewhat (because we have a motivating example), and once that's in place it's easy enough to justify just treating this as an error instead.

That was a post-flight late night post, so I appoligize for coming across extra sassily.

❤