Update README.md

Pull Request Test Coverage Report for Build 810

0 of 0   changed or added relevant lines in 0 files are covered.
11 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 55.187%

Files with Coverage Reduction
New Missed Lines
%

connectors/gridgo-jetty-http/src/main/java/io/gridgo/connector/jetty/server/JettyHttpServerManager.java
5
63.89%

connectors/gridgo-jetty-http/src/main/java/io/gridgo/connector/jetty/impl/AbstractJettyResponder.java
6
64.45%

Totals

Change from base Build 796:
-0.1%

Covered Lines:
3511

Relevant Lines:
6362

💛  - Coveralls


Seemingly Spurious Bot Invariants Generated

Hi!
I'm seeing a lot of bottom invariants generated when running crab-llvm from the following file. This seems unsound as the program can reach a lot of functions on legitimate inputs in particular function do_authentication2. Any assistance would be great!
./crabllvm -crab-inter -crab-print-invariants -crab-heap-analysis=llvm-dsa sshd_pp.bc

full command?

Updated

@shankarapailoor: the problem should be fixed. Please update crab and let me know if you still encounter problems.

@caballa seems fixed to me! Thanks!


Fixes start.sh to add connect attr if needed

What changed?
Adds the flexibility to pass tx_isolation as part of --connect-attributes to sql tool when creating mysql tables

Why?
The default flag passed to mysql is transaction_isolation, which is not accepted if running an older than 5.7 version of mysql.

How did you test it?
Tested on in local docker environment

Potential risks
N/A

Coverage increased (+0.09%) to 68.145% when pulling 52a39a5dc433538164e7062fad61cf8a9beffddc on kewu21:kewu-fix-start-sh into b365258b155a503d143761239736428e3a52395d on uber:master.


The universal-sentence-encoder-multilingual-qa and universal-sentence-encoder-qa seems to have extremely similar pages on AIHub.

Hi, Team.
I just notice that universal-sentence-encoder-multilingual-qa and universal-sentence-encoder-qa seems to have extremely similar pages on AIHub.
In my humble opinion, their pages should not be that similar. For example, their reference papers should be not the same. The universal-sentence-encoder-multilingual-qa should refer to 2 papers and universal-sentence-encoder-qa should refer to the original paper Universal Sentence Encoder.
So I guess the page of universal-sentence-encoder-qa should be similar to the page of the original page universal-sentence-encoder
Am I right?
I'm a SE researcher so I regard the pages as documentation, and I think it will be important. That's why I raise such an issue.
Thank you.

@XMK233
Thanks for the feedback -- I'll follow up with the model publisher internally to see what they think.

@XMK233
Hi, sorry for the delayed reply -- here's what the model publisher shared with me with respect to the differences (lightly edited for clarity):

They use different vocab / tokenization, we can see USE-QA is larger
than USE-MLING-QA as the vocab difference.

USE-QA covers English only and USE-Mling-QA covers 16 languages.

As it is English specific, USE-QA has better performance on English.

The publisher will also update the documentation (potentially as soon as today) to better clarify these differences. Hope this helps -- please reopen if you have further questions.


Uncaught DOMException: Failed to construct 'CustomElement'

Web Components which are re-added to the DOM result in the following exception:
Uncaught DOMException: Failed to construct 'CustomElement': The result must not have children

The following SO post includes some additional context around why this error may be occurring: https://stackoverflow.com/questions/59970043/custom-element-setup-constructor-vs-connectedcallback/59970158#59970158)

Should be all set


sdk/state: move iteration to be pulled from latestCloseAgreement

removes c.SetIterationNumber. The channel's current iteration number = lastCloseAgreement.IterationNumber + 1
note:

not updating lastUnconfirmedPayment yet. So adding the field as a dummy field for when it's added

@leighmcculloch the validation might be oversimplified. Basically I'm saying in ConfirmPayment if my channel is expecting a certain iteration number and the payment you gave me is different, then return an error.
That validation might get more complicated when lastUnconfirmedPayment comes into play 🤔 . But atm this seems right to me


[transactional-tests] Migrate remaining VM/Bytecode verifier IR tests

migrated remaining tests
tests left over are either for the DF or the IR compiler itself
Check for tokens after module or script in IR. Caused silent test failures

Test Plan

ran the tests

/land


Updates to the Stage 1 submission checklist (various)

 Updates to the Stage 1 submission checklist (various)


Use onMomentumScrollEnd instead of onScrollEndDrag

Using the option snapOnAndroid currently results in very bad experience where carousel snaps on the item where the drag was released. By using onMomentumScrollEnd instead of onScrollEndDrag here https://github.com/archriss/react-native-snap-carousel/blob/master/index.js#L404 the experience is made much smoother.
Example with onScrollEndDrag: https://gfycat.com/SmallCaringAfricanharrierhawk
Example with onMomentumScrollEnd: https://gfycat.com/PhysicalFearlessBarracuda

Hi @FakeYou , thanks for the suggestion. I guess we haven't noticed this since our swipers entries are usually very wide components, unlike your example, so we couldn't swipe to far away entries like you did :)
This needs to be tested on iOS and we have to check for potential drawbacks (I guess there aren't).
Maybe onScrollEndDrag behaves better in some cases. If so, I guess we could add a new prop for this.

Thanks a lot for the suggestion, it will be added to the next release.
See https://github.com/archriss/react-native-snap-carousel/pull/20

Awesome man! Thank you for the update.


Add support for reading pre-existing Federated BigQuery Data Sources in

Google Cloud Stoage.
Fixes #32
I haven't looked at integration tests yet. Doing that now.

PTAL manually ran integration tests, which passed.

LGTM.


[Release-AutoPatch] Prepare for 2023 November auto-patch release

API change check
API changes are not detected in this pull request.


poll_perf_buffers: make epollfd_ member variable

Two items around poll_perf_events:

Make epollfd a member variable. It's state that is used in multiple functions, so seems like a good candidate for that.
Expose poll_perf_events interface polling period via timeout_ms

Checklist

[x] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

I can't tell if the test failure is related to these changes. At first glance, it looks like it's not, but if it is related please let me know, and I'll investigate further.

can you rebase?

Rebased.
The failures appear unrelated (e.g. fatal: The remote end hung up unexpectedly).

CI should work again, can you rebase your work?
Sorry for the CI struggle, seems like everything broke in a short window :/


Make bundle URL relative to index.html

This allows a deploy to non-root URLs to be seamless.

I added the leading slash to resolve this. That said, he never shared if that helped. If we can confirm that nested routes can reload successfully during dev without the leading slash then I can accept this PR.
Thanks!

I think bundle.js can be either absolute or relative but it must be the same as styles.css in tools/buildHtml.js which it is currently not. Otherwise it can break in production.
For me it needs to be absolute since I have entry points that are on the second level (app at example.com and client can come in at example.com/en/something). And even if you have your app at a sub path like example.com/calculator/, if you want to support clients loading your app from example.com/calculator/en/something you will need to make it absolute with the current setup.
I opened a PR to fix the current state (styles.css being not the same as bundle.js) but feel free to close if you would rather have both relative.

@firstdoit Can I close this? Does #143 resolve this for you?

Not sure if everything absolute is what most people expect (or even how it solves the problem of deploying to multi-level paths, given that now we're restricted to root!), but sure, any decision is better than no decision!

@firstdoit I see what you mean
Relative solves the problem of deploying to multi-level paths. Absolute solves the problem of reloading an app after navigating to a multi-level path.
But, I think react-slingshot does at the current state not support reloading the site after navigating, correct me if I'm wrong. Which would make my point moot for having it absolute. If you do have navigation&reload support (which my application has) then I think it is inevitable to have it absolute.

AFAIK the expected behaviour in a React (or rather any SPA) app is to have the app itself handle all navigation and routing. I agree that for anything non-trivial, specially using History, you'll eventually have to bolt down the paths. In this case, however, I'd either document this detail or make it simple to add a base path


Sound is not working

the sound is not working
https://prnt.sc/10p83g6

Just tested and it's working for me, cannot reproduce. Are you sure you didn't mute the tab and that your volume is up? Please provide more info if you want me to reopen


Raspberry Pi/ Pi2 build

Is it possible to run opencvr on raspberry pi or raspberry pi 2?

i think it is possible, current we are split the server and client, the server can be build for any platform without GUI.

I don't think it can be built on Linux. Make tries to access scripts in non-existing ./linux directory.

?No currently this build cannot be built successfully...

From: Pdobry<EMAIL_ADDRESS>Sent: 02 December 2015 22:10
To: xsmart/opencvr
Subject: Re: [opencvr] Raspberry Pi/ Pi2 build (#35)
I don't think it can be built on Linux. Make tries to access scripts in non-existing ./linux directory.

Reply to this email directly or view it on GitHubhttps://github.com/xsmart/opencvr/issues/35#issuecomment-161449489.

how can compile only server in Raspberry pi 3 with raspbian?

hi milonet,
you are Marco Milone?the guy send mail to me?

we have start the porting for Raspberry pi 3, and it will only have the server part.
https://github.com/xsmart/opencvr/blob/master/rules-pi3.mk

Raspberry pi 3 version is ready.
https://sourceforge.net/projects/vscloud/?source=navbar


Uploading of Training-Data Request needs to be enhanced

In order for the THGA to find out, which Auto-Shop uploaded how many Scans, there needs to be an additional field in the interface and the REST function, transmitting a Workshop-ID. This should be a UUID and be given out by the THGA to each auto-shop.
An empty auto-shop-UUID (ASID) is permitted.

Is this UUID implemented in the HUB API ? @DanielNowak98

Is this UUID implemented in the HUB API ? @DanielNowak98

The UUID is the unique ID for any workshop, right?

Yes it is a unique ID that the workshops should get from the THGA so they can find out which data is send from which workshop

Yes it is a unique ID that the workshops should get from the THGA so they can find out which data is send from which workshop

Ok, I think this should be covered in the HUB. I'll find out.

@DanielNowak98 could you find out which endpoint is used in the HUB API for requesting the UUID?


JSMin Not found

I get the following error when I try to compile my assets after setup.
Fatal error: Class 'AssetPipeline\JSMin' not found in /.../extensions/asset_pipeline/lib/stream/class.APStream.php on line 95
Symphony Fatal Error: Class 'AssetPipeline\JSMin' not found

An error occurred in /.../extensions/asset_pipeline/lib/stream/class.APStream.php around line 95

I want my assets served from a 'theme' folder in my workspace folder. My assets are in this structure:
/workspace/theme/assets-src/css/
/workspace/theme/assets-src/img/
/workspace/theme/assets-src/js/
And the output folder:
/workspace/theme/assets/
I think I have the settings correct:

Whoops. Version 0.2.1 uploaded.

Awesome! Works great now. Thank you so much for this extension, it's a much needed piece to Symphony.


Can send but not receive

Hi - not sure what is happening -
message in the terminal window that I think might yield something is
"2017-11-23 17:23:23.111 MessageProxy[3658:435578] [Accounts] Failed to update account with identifier A4F9FDB3-7256-4A1A-AE87-B11A6952BF6A, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"
Any ideas ?
BTW- this looks great.

I swear to god I will forever pay for not filtering that message out. That error doesn't mean anything, it's just the OS being too verbose. What do you mean you don't receive messages?

Sorry. I can send a message from the Android which is received by an iMessage user (I also see it on my mac). I see the response coming back to me (it shows in Message on the mac) but never makes it over to the Android. BTW - I assume I don't need to use IFFFT for this part of the functionality ?

No, did you port forward the socket as well as the main API? They're two separate ports

Thats it ! I think I had an error with the port forwarding... many thanks


Fix autosigning on embedded wallet

The Chore
What we need to achieve and who for
Tasks

[ ]
[ ]

Additional details / background info

This is already fixed


Teams manifest requirements aren't listed

Almost all of the questions / issues regarding OAuth and Teams I receive are because of a faulty manifest. The manifest is missing token.botframework.com as an entry in the validDomains section, which is required by the Teams channel. If this is missing, the user won't see an error, pressing the Sign In card button will do nothing at all.
This requirement is listed in the v3 documentation of the Teams platform, however many people miss it, since they are redirected to the v4 documentation...
Could this be added to the documentation somewhere? Or at least to the FAQ.
StackOverflow example. Github example (But there are many more on SO and Github. It was also one of the most asked questions about Bot Framework during the company wide hackathon last week).

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

ID: a9a43e68-83a3-1adc-0c55-e277ddb98c6b
Version Independent ID: 5c46848d-bc20-480e-4571-00a283d930a2
Content: Add authentication to your bot via Azure Bot Service - Bot Service
Content Source: articles/v4sdk/bot-builder-authentication.md
Service: bot-service
Sub-service: abs
GitHub Login: @JonathanFingold
Microsoft Alias: v-jofing

Hi Mick, I'm taking a look at this now to see how we can get this content somewhere users will see it (either in the v4 docs or FAQ).

Thanks @emgrol! It would be great if the following note could be integrated or linked somewhere as well.

Adding a bot by GUID, for anything other than testing purposes, is not recommended. Doing so severely limits the functionality of a bot. Bots in production use should be added to Teams as part of an app. See Create a bot and Test and debug your Microsoft Teams bot

Hi @iMicknl, @JonathanFingold and I discussed the content and decided to open issue #1314 to cover portions related to 1) the token.botframework.com as an entry in the validDomains section and 2) how your note in the previous comment about adding by GUID can be worked in.
In the mean time we decided to add the code snippet in the comment here from @mdrichardson to the Prepare your bot code section of the current v4 authentication article. I've reached out to @mdrichardson about getting a Javascript sample too.

@emgrol Now that I've looked into this a little more, I'd recommend not adding any of that code into the docs. The SDK should handle all of that now. Should be as simple as this C# sample shows (Node).

We've updated the authentication article to have a Teams Authentication section. It now references the teams-auth samples and shows users which code snippets to add along with a description of the TeamsActivityHandler.
I've filed a new issue for more guidance on the content regarding the " missing token.botframework.com as an entry in the validDomains section".

Closing this issue, feel free to open a new issue if any confusion re: this topic persists.


1.25.0-Beta0 GrammarRegistry loadGrammar API changed behaviour.

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
The Atom API loadGrammar callback return has changed in 1.25.0-Beta0. It is documented and in prior versions did return up to two fields (err, grammar) using the code here and here. The err field could be relied upon to indicate an error. It now it returns a single field either (err) or (grammar) as shown here and that field can't be used to determine success or failure!!

/cc: @maxbrunsfeld

Oh wow, that's terrible. Sorry about that. I'll fix that shortly and we'll publish another beta release.

@maxbrunsfeld Thanks. Also, great work on tree-sitter, I've been looking forward to it for the past year and keeping an eye on what you've done. At last, no more TextMate grammars!


Aimbot button is fixed for every type of gun

Hi. With the old version of Osiris I used to assign aimbot key for rifle (AK, M4A4) is mouse1 and but for AWP is ALT.
But now after the last update I can only use mouse1 for all rifles. I cannot use separate button for rifles and AWP anymore
Can u fix pls

Why would you use mouse1 as an aimbot key?

Why would you use mouse1 as an aimbot key?

Some people prefer use MOUSE1 for aimbot for legit gameplay

There's no need to use mouse1 as an aimbot key because aimbot aims while shooting if you have aimlock off.

Using mouse1 worked fine for me for a while while I used to use OTC. Really
hid the aimbot with a low FOV. That was before I knew right clicking gave
me more options
On Sat, Dec 12, 2020 at 2:23 PM debooga<EMAIL_ADDRESS>wrote:

There's no need to use mouse1 as an aimbot key because aimbot aims while
shooting if you have aimlock off.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/danielkrupinski/Osiris/issues/2396#issuecomment-743803637,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCKQFEQEJTCXD7KN72ONYTSUO7KTANCNFSM4UYKQ7EA
.

https://github.com/danielkrupinski/Osiris/blob/master/Osiris/Hacks/Aimbot.cpp#L164
You shouldn't bind it to mouse1, just look at the code.

Why would you use mouse1 as an aimbot key?

I know it's weird but I have low FOV aimbot for rifles so it's always safe for me to use it on mouse1. But can u tell me the reason why you fix the aimbot key? You used to let us choose separate key why you fix only 1 key now :(

its not a fixed key, it just aimbots while shooting. enable aimlock to aimbot even when youre not shooting and bind it to some key (but please, not mouse1, as it is useless)

its not a fixed key, it just aimbots while shooting. enable aimlock to aimbot even when youre not shooting and bind it to some key (but please, not mouse1, as it is useless)

I know. But I want to be legit so I don't use aimlock :)

Why would you use mouse1 as an aimbot key?

There's no need to use mouse1 as an aimbot key because aimbot aims while shooting if you have aimlock off.

ayy but what if I want to aimlock. Then using a M1 is necessary.

 Read the code.

There's no need to use mouse1 as an aimbot key because aimbot aims while shooting if you have aimlock off.

ayy but what if I want to aimlock. Then using a M1 is necessary.

??????

???????????????????????????????????????????????????????????????????????????????????????????????????????????


Improved the logs command

The logs command is now more intuitive to use with both AWS and RAX environments. All app logs are returned by default and you can further filter those logs by a wildcard search on the message field.

Looks pretty good after a quick glance. One minor comment, see above.


Update CONTRIBUTORS.csv

Request to add Ashwin Kulkarni in the contributors list

Current behavior

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

@AshwinKul28 We'll merge this soon.
Thank you for accepting the CLA and taking time to contribute!!
Welcome to the Ockam Community 🥳
If you have questions, as you explore, join us on the contributors discord channel https://discord.gg/bewvnm6zqS


hide some options in creat class modal

fix ENG-487
now creating:

and editing:

Looking at it now, it occurs to me that showing just the four options at first, but having a small "More Options" link at the bottom that would expand and show the rest of them could be good. (We would reorder items & gems + classroom code autocomplete to be below the first four options that we do show by default.)


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tackle-285: Change default password

https://issues.redhat.com/browse/TACKLE-285
Preview: https://deploy-preview-38--tackle-documentation.netlify.app/documentation/doc-installing-and-using-tackle/master/index.html#changing-password_tackle

@mrizzi Please review

The links in the guide are all taking us to the top of the main guide "getting started" page .
Can the links navigate to the particular sections they are pointing to
====================================
https://www.keycloak.org/docs/latest/getting_started/index.html#logging-into-the-admin-console[Logging into the admin console].
https://www.keycloak.org/docs/latest/server_admin/index.html#searching-for-users[Searching for users] in the KeyCloak _Server
https://www.keycloak.org/docs/latest/server_admin/index.html#_user-credentials[User Credentials].


Vickel: Watch barnettghostwriting.com

Vickel requests the watch of the watch_keyword barnettghostwriting\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

barnettghostwriting\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


BF/Dad Animation on Step Hit?

What is your question?
I need the code for animation playing on step hit, because events are kind of buggy and don't work that well on my version.

animation functions
variables


Wrong implementation of method: simulator :: getNumberOfContracts

The method simulator :: getNumberOfContracts should return the number of contracts. If no contracts deployed, it shall return zero.
Controlling logic in function evtLoadSlot () shall be updated to reflect changes.

Completed fix with b24cf67156a66aac2ec3f74862709b179b77c634 for the frontend.


Update the README file

Hey, @marielavd I created the repo, but I could really use help with crafting a better README. Notice that I created the repo at #1.


adding Sieve of Eratosthenes program

#805 adding sieve of eratosthenes program

@chennakeshava1998 Any updates?

I have pushed the latest commit


SA1009 handles spacing for nullable !s poorly

Consider:
#nullable enable
using System;

internal class Program
{
    private static void Main()
    {
    }

    private static void Foo<T>()
    {
        if (default(T)! is null)
        {
            Console.WriteLine("default(T) is null");
        }
    }
}

This triggers SA1009 on the:
if (default(T)! is null)

correcting it to be:
#nullable enable
using System;

internal class Program
{
    private static void Main()
    {
    }

    private static void Foo<T>()
    {
        if (default(T) ! is null)
        {
            Console.WriteLine("default(T) is null");
        }
    }
}

Such spacing is non-idiomatic and error prone.  I suggest the rule be corrected when the ! in question is a nullable suppression.

Related to https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2968.  Not sure if it should be considered a dup.

StyleCop Analyzers 1.2 will be the first release to properly support new C# 8 syntax.


feat(analytics): add amplitude

Please read and mark the following check list before creating a pull request:

[] I read and followed the CONTRIBUTING.md guide.
[] I read and followed the New Feature Checklist guide.

Short description of what this resolves:

Did you able to run this?

As you can see

pls don't merge yet


Aux data not written to file for Cyton 16-Channel

The new code on the development branch solves the problem that Aux channels are not saved in the OpenBCI text file for 8-Channel, but the problem persists with 16 channels.
OpenBCI_GUI 3.1.0 development branch
3.0.0 firmware
BOARD_MODE_MARKER

Sorry posted in wrong repo


relative i18n paths

i'm getting an error that relative I18n paths are not available (Cannot use t(".register") shortcut because path is not available). Is there a know 'workaround' ?

@koenhandekyn thank you for the issue report. Might you be able to provide a PR with a failing test for this use case?

i'll revalidate the issues on a 'blank slate fresh'  rails 6 app first to see if we can reproduce them there.

Here I created an example of the failure https://github.com/joelhawksley/actionview-component-demo/pull/28/files.
Should I create a PR in this repo so that we actually see tests failing?

This should be resolved by https://github.com/github/actionview-component/pull/74. Feel free to re-open if it wasn't.

i can't reopen but see #74 for a proposed fix of the current issue. putting this comment as a reference.


Cache randomization calls

Adds a cache of the objects generated by a do_randomize/randomize calls (VariableBoundVisitor, RandInfo, Randomizer, field_model_l, constraint_l, Boolector, and Boolector expressions) keyed on a string consisting of: randstate obj ID, PrettyPrintModel output with values included, constraint names with enable bit, and variable names with rand_mode.
Skips caching on calls using ModelGenerator or distribution constraints. ModelGenerator b/c every call is a new soft constraint, or at least that's what I saw in testing. Distribution constraints b/c it's expensive to generate the bounds, array constraints, and distribution constraints for every call just to decide not to cache.
Uses copy.deepcopy on field_model_l and constraint_l to keep constraint generation and expansion and Boolector objects independent. Everything is deepcopied except the val object inside FieldScalarModel, so that value lookups with the original rand_obj work, and the var Boolector object since that cannot be deepcopied or pickled. The do_randomize call also does some manipulation on FieldArrayModel to add a variable, latest_field_l, and a function, get_field_l, to help in returning the field_l. There are references to parents in variables which I think causes deepcopy to go much further than intended to the point of copying the entire parent rand_obj. Not sure if deepcopy is the way to go, but it was an easy way to fork the function and stop state from getting shared or overwritten.
Also adds a test for pre_randomize to exercise disabling/enabling constraints and make sure the caching doesn't mix them up.
Results in a modest speed up on test_perf.py (taking the 3rd run to avoid import overhead):
master - 17.0s
rand_cache - 8.0s
On test_dist.py, which should be skipping caching, although still needs the PrettyPrintModel call to do so. I've seen these vary by about 1s, so I think the overhead for the pretty print hopefully is small enough that it works for now. A faster way to explore constraints would hopefully make that magnitudes faster.
master - 15.7
rand_cache - 14.9s

@alwilson, thanks for the all the work you've done on this! This looks like a sizable body of work, and it's going to take me a little while to do a review and get my head around it.
While I'm doing so, could you collect the set of open issues that you're aware of (I saw a few 'TODO' notes in the diff)? It might also be interesting to the cache-enabled PyVSC out with the riscv-dv project to get another data point on improvements.
We will need to determine whether to have caching on by default. To this end, can you collect timing for running the test suite with cache eanbled and with cache disabled?
Thanks again for your work towards improving PyVSC's performance!

@mballance The riscv-dv pygen tests are looking like a good exercise of these changes! The FieldArrayModel hack I had to copy references to field_l still seems to be broken and I have more changes that seem to resolve it. The tests I tried also explode in memory usage and get slower as memory grows. It looks like their testbench deepcopies rand_obj in places, which I think is multiplying the randomization caches which already deepcopy too much. So I think there's some deepcopy work that needs to be done to prevent cases like this from happening. Also only caching after the 2nd or so call would help on memory usage for one-off calls never seen again.
I can summarize those TODO / HACK comments in another comment.

I tried out riscv-dv's pygen / pyflow but I've only gotten one of the tests to run successfully. I tried it on master as well and only got that first test mentioned in the README to work. I knocked down the number of instances and instructions to run a bit faster too, but the variance between successive runs is pretty wide. Hard to measure any improvement. I did add some debug statements and saw that only some randomization calls could be cached. I'll keep looking into it, but I bet it's the dist constraints and with constraints preventing reuse.
python3 run.py --test=riscv_arithmetic_basic_test --simulator=pyflow --steps=gen
After this latest commit I've cleaned up more of the TODO / HACK comments since I was so liberal with them. I've listed them below along with their file/function. Most of the concerns are around deepcopy and syncing the FieldScalarModel and FieldArrayModel made in the deepcopy with the original references so that retreiving model values work, but making it so that we can also roll back those changes on the next randomize call. I also have some concerns about abusing the PrettyPrintModel to get a hashable string for caching. Seems like there should be a faster way to do so, and one that doesn't depend on a human-readable string that might change in the future depending on debug needs. Some scattered notes on the actual randomize function since there seems to be unused features that would make caching more complicated, but are disabled for now? And possibly unused self.btor references.
field_scalar_model.py:
def __deepcopy__(self, memo):
    # TODO This is a workaround for the deepcopy in do_randomize somewhere getting
    #      access to Boolector objects, which in turn can't be deepcopied.
    result.var = None

randomizer.py:
class Randomizer(RandIF):
    def __init__(self, randstate, debug=0, lint=0, solve_fail_debug=0,
        # TODO Reset btor cache after so many uses to circumvent Boolector instance
        #      slowing down as more expressions permanently become part of the model/formula.
        self.btor_cache_uses = 100

    def randomize(self, ri : RandInfo, bound_m : Dict[FieldModel,VariableBoundModel], cache_enabled: bool):
        # TODO What is going on with max_fields? It would probably
        #      break this caching setup.
        #max_fields = 20

                btor = Boolector()
                # TODO Is self.btor used anywhere?
                # self.btor = btor

                    # TODO: Is this part of a disabled feature to solve randsets together?
                    # rs_i += 1
                    if n_fields > max_fields or rs.order != -1:
                        break

                # TODO Is self.btor used anywhere?
                # self.btor = btor

                # TODO Does some of this need to be done while caching, too?
                if not cache_enabled:
                    reset_v = DynamicExprResetVisitor()
                    for f in rs.all_fields():
                        f.set_used_rand(False, 0)
                        f.dispose() # Get rid of the solver var, since we're done with it
                        f.accept(reset_v)
                    # for f in rs.nontarget_field_s:
                    #     f.dispose()
                    for c in rs.constraints():
                        c.accept(reset_v)
                    RandSetDisposeVisitor().dispose(rs)

do_randomize:
            # HACK Clear out field_l in FieldArrayModel from previous cache
            for fm in field_model_l:
                if hasattr(fm, 'field_l'):
                    for f in fm.field_l:
                        if hasattr(f, 'field_l') and hasattr(f, 'old_field_l'):
                            # Revert to original value
                            f.field_l = f.old_field_l
                        elif hasattr(f, 'field_l'):
                            # Save off old, original value
                            f.old_field_l = f.field_l

            # Create a unique string for this call based on object ids and mode bits
            # TODO Is there more than rand_mode and constraint_mode to cover here?
            # TODO Can we cache the base constraints so that with constraints have a prebuilt
            #      model and such to build off of?
            call_hash = Randomizer.get_pretty_call_hash(randstate, field_model_l_og, constraint_l_og)

            # Skip dist constraints b/c they cost building bounds and array/dist constraints first
            # HACK What's the best way to detect if there are dist constraints?
            if ' dist { ' in call_hash:
                cache_enabled = False

            # Make copy of field and constraint models, together to keep FieldScalarModels the same
            # TODO The deepcopy() in FieldScalarModel keeps the val reference, is that the best way?
            if cache_enabled:
                (field_model_l, constraint_l) = copy.deepcopy((field_model_l, constraint_l))

        # HACK Fill out field_l in FieldArrayModels so that array lookups work in model
        if cache_enabled:
           field_model_l = Randomizer.randomize_cache[call_hash].field_model_l
           for fm_new, fm_og in zip(field_model_l, field_model_l_og):
               if hasattr(fm_og, 'field_l'):
                   for f_new, f_og in zip(fm_new.field_l, fm_og.field_l):
                       if hasattr(f_og, 'field_l'):
                           f_og.field_l = f_new.field_l

def get_pretty_call_hash(randstate, field_model_l, constraint_l):
            # TODO This pretty print is an expensive call. Need a better way
            #      to construct a unique ID/hash that doesn't depend on
            #      object lifetimes. Can some of this be cached?
            call_hash += ModelPrettyPrinter.print(fm, print_values=True)

Yeah, the runtimes for at least that one riscv-dv test I'm running is all over the place. Hard to compare even several runtimes.
riscv_arithmetic_basic_test

1000 instructions - 1 iteration - runtime (s)
master     avg: 24.6 - 18.6, 26.1, 23.1, 30.5
rand_cache avg: 21.1 -  9.7, 31.2, 13.0, 30.5

3000 instructions - 1 iteration - runtime (s)
master     avg: 61.8 - 97.5, 22.0, 111.4, 16.1
rand_cache avg: 56.2 - 95.9, 62.8,  21.0, 45.2


Minor: fix ci break

Which issue does this PR close?

Closes #.
Rationale for this change
fix ci break after #8081 merge

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thank you @haohuaijin @jayzhan211  and @houqp  for getting the CI back up and running so quickly


General Intel CPU/GPU refactoring

Description of changes
Addresses some stuff brought up after https://github.com/NixOS/nixos-hardware/pull/1161 was merged.
Also, it turns out that the hybrid codec wasn't needed for the t480s, and it was my simultaneous changes to chromium that enabled VAAPI support. Oops.
Things done

[ ] Tested the changes in your own NixOS Configuration
[ ] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

The commit history's a bit scuffed at this point. I'll recreate the PR.


Modified check on lastKeyVal to allow for multiple radio buttons with…

… the same value across multiple forms on the same page
#1198
This changed solved my bug on my local machine.  Not sure if the same problem exists with any other types.

This isn't really a proper fix that handles all use cases, but this is definitely something that needs fixing. I will be completely rewriting the changed value stuff for 6.0 soon.


Publish preview package nuget

https://github.com/Azure/azure-functions-rabbitmq-extension/releases/tag/v0.2.2001-beta !!


Various project changes

These are changes Xcode wants to make whenever the project file is modified. And whenever the version number is modified, Xcode movies it out of the info plist and into the project.

I was thinking if there is a way to prevent Xcode from making those project file changes

I think they happen as a result of resolving merge conflicts in the project file or plist. Whenever that happens, it is a good idea to open the project and do something that forces Xcode to resave the project or plist file.


arrow navigation

lets not add ARROWS to help since we dont add navigation with mouse either and also for arrows we can use keydown for fast scrolling but for space it should stay kepyress since we dont want to do multiple switches when user holds space down


Support for UTF-16/UTF-32

Hello,
By any chance would you be able to include support for std::wstring as well?
Thanks!

It's difficult to include it in the field interface, but it is possible to add it when we inplement #60, which would allow you to read rows into structs directy.
What's your use case? Which would be your ideal interface?
Regards,
Ruben.

Well, it's mainly because our entire application is already using UTF-16 since we work with EUC-KR encoding.
Specifying a define such as BOOST_MYSQL_USE_UTF16 to simply swap std::string to std::wstring would be ideal.

Hi,
From what I've seen, EUC-KR is an encoding taking from 1 to 2 bytes per character. For example, this string contains two characters and each of them takes two bytes:
완     성
BF CF BC BA

While other characters (e.g. the ones in ASCII) only take one:
a  b  c
61 62 63

In other words, as far as I understand, EUC-KR is not UTF-16. So, a couple questions:

Which character set are you using to read results from the database? I.e. are you issuing a SET NAMES "euckr" or a similar method to tell MySQL to send results in EUC-KR?
How are you using the results that you retrieve from the database? Do you intend to pass them to the Windows native APIs (taking wchar_t strings)?
How are you encoding your query strings? The ones you use when calling connection::query() or connection::prepare_statement().
Are you using metadata strings? For example, metadata::column_name().
Are you using server diagnostics? I.e. diagnostics::server_message().

Thanks,
Ruben.

To answer the questions directly:

Q: Which character set are you using to read results from the database? I.e. are you issuing a SET NAMES "euckr" or a similar method to tell MySQL to send results in EUC-KR?

A: We are using utf16_unicode_ci. We are not issuing SET NAMES command. Upon testing the results are correctly represented in std::string.

Q: How are you using the results that you retrieve from the database? Do you intend to pass them to the Windows native APIs (taking wchar_t strings)?

The results retrieved from database get encoded into a packet that gets sent over to client for handling. Yes we are passing to Windows native API using wchar_t.

How are you encoding your query strings? The ones you use when calling connection::query() or connection::prepare_statement().

Currently we are just using utfcpp to convert std::u16string to std::string for std::make_tuple and using the same library to convert back to the format that we need, which seemingly worked fine at cost of performance.

Are you using metadata strings? For example, metadata::column_name().

We have not explored this yet.

Are you using server diagnostics? I.e. diagnostics::server_message().

Yes.

But whole TDLR is: Yes, it works fine with std::string, it is just the matter of skipping the conversion process if we can process the data directly as std::u16string or std::wstring, current workaround is mentioned previously.

Hi,
Where are you setting utf16_unicode_ci? Setting at at the table or column level (e.g. 'CREATE TABLE t (f TEXT) COLLATE utf16_general_ci) or the table level (CREATE TABLE (f1 TEXT COLLATE utf16_general_ci) won't affect to what you receive as a client at all. MySQL has the concept of "connection character set and collation", which determine the encoding of the strings you send and receive from the server. The most reliable to change this is via SET NAMES <encoding>. By default, Boost.MySQL uses utf8mb4_general_ci, so this is the encoding you're actually using right now.
The obvious thing to do (SET NAMES utf16) doesn't work because of a MySQL limitation. Some multibyte character sets can't be used like this, as per the MySQL docs.
This doesn't mean that all is lost. When you do SET NAMES <charset>, you're actually setting several system variables that control the encoding of things sent to and received from the client. The relevant vars are:

character_set_client, which controls what you send to the client. This one can't be UTF16.
character_set_results, which controls what MySQL sends to you. You can set this by using SET SESSION character_set_results = 'utf16'.

Before doing anything, please read this section of the docs explaining which variables affect what, since you're entering a potentially dangerous path down here. Things like error messages will also get affected by the character set change.
If you do that, you will start receiving UTF-16 encoded strings. They will, however, be represented as single byte string_view/std::string, but they will contain the byte representation of UTF-16 strings. To be able to use them, you need to make a byte copy into a std::wstring. For example:
row_view my_row = /* obtain a row by invoking query() or execute_statement() */
string_view utf16_string = my_row.at(0).as_string(); // This points to a UTF-16 string
std::wstring usable_string (utf16_string.size() / 2, 0); // We will copy the UTF-16 characters here
std::memcpy(usable_string.data(), utf16_string.data(), utf16_string.size()); // This requires C++17
// Now you can use usable_string normally

Beware of byte ordering: this is assuming that whatever MySQL sent to you matches the byte order of the machine you're running. By default, MySQL uses UTF-16 big endian. You've got utf16le in case you need it.
Remember that you can't just reinterpret_cast<const wchar_t*>(utf16_string.data()) because of strict aliasing and alignment issues.
TL; DR

Trying MySQL to send UTF-16 can be problematic, measure well before going down this path. You may want to consider using multi-function operations to reduce copying, instead of this.
Because of MySQL limitations, you will need some conversions. Anything you send (query strings and statement parameters) can't be UTF-16.
IIRC Windows now allows UTF-8 in its APIs, although the support is quite recent. Depending on your application, you may also consider using Boost.Nowide, which can make converting UTF8 <=> UTF16 in the context of the Windows API smoother.

Please let me know what path do you take. If you end up settings character_set_results to UTF16, I can consider implementing a solution to avoid this terrible memcpy thing. The limitation on character_set_client can't be lifted, since it's server-side.
Thanks,
Ruben.

Hi @H1X4Dev, which solution did you finally employ?
Thanks,
Ruben.

Hello,
Unfortunately it was decided to switch to utf-8 database and simply converting u16string using the library that I have mentioned previously. While the solution is ugly, we want to ensure the compatibility for our software since it the server will be deployed on Linux and the Client will be on Windows. The client software is rather old, so the compatibility is a must, even if we have to use a hacky way to achieve the goal.
I will close the issue in hopes of #60 being able to achieve the set goal.
Thanks.


el.setAttribute(name, value) not resulting in a browser visual change/update when triggered from console

Browsers showing this behavior:
Chrome 58
Firefox 54.0a2
Expected behavior:
The input textfield should show the correct updated value just like the red box will update to the new value at all times.
Actual behavior:
Red box resizes correctly but input textfield does not show the new value.
Steps to reproduce:
*Disclaimer: * I don't know why these steps are needed to reproduce it, but this is the only way you can reproduce. I tried other ways via browser events and they wouldn't reproduce it. So you have to do it exactly like this. I provided a fiddle so it's easier to reproduce for you.

Open http://jsfiddle.net/stvmyrwL/
Type any number into the textfield
Now open the developer console, in jsfiddle you need to be in the right context so change it like this:

Now enter this in the developer console: observableUser2.age = 95

As you can see, the red box rerenders with the correct value. But the input field (despite displaying the correct value when you query for it as a next possible step,) does not show it visually in the browser.

Fix:
Change line incremental-dom.js:923 from el.setAttribute(name, value); to el[name] =  value;

Dupe of https://github.com/google/incremental-dom/issues/239. We're moving to a system that allows you to tell iDOM how to patch attributes (as either an attribute or property) in https://github.com/google/incremental-dom/pull/332.


Split library

libtensor (basically the tensor namespace)
liboptim (basically the optim namespace)
libutil (non machine learning-related functionality)
libmachine (the machine learning part)

Also think of better names for these modules.
Each should have its own CMakeLists.txt and an install target.

Another suggestion:
cmin, ctensor, core, cnet

Also use different namespaces for each library.


Bump @now/build-utils to 0.9.13

Fixes canary@canary bug for now dev

Codecov Report

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

@@            Coverage Diff             @@
##           canary    #2784      +/-   ##
==========================================
- Coverage   13.89%   13.89%   -0.01%
==========================================
  Files         264      264
  Lines       10606    10618      +12
  Branches     1367     1368       +1
==========================================
+ Hits         1474     1475       +1
- Misses       8983     8994      +11
  Partials      149      149

Impacted Files
Coverage Δ

src/util/metrics.ts
61.53% <0%> (-6.65%)
:arrow_down:

src/util/prefer-v2-deployment.ts
56.25% <0%> (-5.12%)
:arrow_down:

src/util/projects/get-project-by-id-or-name.ts
20% <0%> (-5%)
:arrow_down:

Continue to review full report at Codecov.

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


Pre blocks

I added functions to create and remove PRE elements in a sensible way. I'm not fantastically happy with the removePreformatted function - I get the sense that there are easier, better ways to do this. But it has satisfying functionality at this juncture. Said functionality is also covered by some tests. These are not exhaustive, but ought to provide a good baseline for the functionality. I put the two functions under the key shortcut 'ctrl-shift-m', which will toggle based on hasFormat('pre') whether it creates or removes PREs.
(The things we do to make our systems engineers happy...)

Figured out a way to deal better with pasting into PRE tags. Will add commit shortly.

There we go. Pasting is much improved.

Do you have any suggestions as to what removePreformatted() should do if collapsed inside a PRE element? As it stands, it does nothing, which I figured was reasonable.

Did a major clean-up pass. I think I got all the style errors, and I reworked removePreformatted() a fair bit. It will still split PRE blocks at range limits, but it refrains from using the weird range juggling I was doing. As well, it uses a TreeWalker to iterate through contained PRE blocks, instead of looping through a NodeList.
I also added a test (and a fix to make it work) to ensure that a range that fully encloses a PRE block and some other stuff acts right.
Does this pass muster?

Today I noticed I had forgotten to actually push stuff so it could be reviewed. GG, Gert. Well, I've pushed the changes I mentioned above! :-)

Sorry for the delay in getting to this. So far testing this patch I have found the following issues:

Selection/cursor position is not maintained when converting to preformatted.
If my cursor is at the end of the pre block, I often have to hit enter twice to get a new line.
If I unpreformat with my cursor somewhere in the <pre>, it just splits the pre rather than converting the whole line (or block) to normal.
Some minor code formatting issues, where it isn't following the correct conventions; but I can fix this up myself if everything else is ready.

Unfortunately at this stage I can't merge this, sorry. There are too many issues.

Re. the third issue you mention, I think expanding selection to the line you're on makes sense. Inside a PRE block, you can think of the individual lines as blocks, so treating them separately for this purpose makes sense to me. I'm not a fan of expanding to the whole block - that seems like going a bit far, given the semantics in play.
I'll look into this. It's a not insignificant feature, so that it's taking a while to get right isn't fantastically surprising to me. :-)

A further issue found with this code: URLs written into PRE blocks get turned into links, which they really shouldn't.

Re. links in PREs, how do we feel about that? They're not hugely disruptive, per se, so it might be useful to keep them, at least the auto-inserted ones. But at the very least, I'll ensure that makeLink() behaves itself in there.

Anyhow, apart from the link business (which is very much a matter for discussion, I'd say), I think I've cleaned up the things you mentioned, @neilj. Let me know if you have other concerns with it. I hope I've cleaned up the messiness of it some.

Just a quick note to say I haven't forgotten about this, but haven't managed to find enough time to review it properly yet, since it's quite a large patch!

I'll be doing a little maintenance work, so I'll also rebase this onto master so it's easier to work with.

I've got some time on my hands the next little while, so I figured it might be a good time to get this in order. Let me know what you think, @neilj.


Suspend / resume support

Hi i have a question. How to support suspend /resume and remote wakeup in RTOS mode. ?

Hi, Is there any advice to suspend and resume threadx when callbacks invoked

You can refer to https://github.com/azure-rtos/threadx/tree/master/utility/low_power.

Hi
I'm using usbx in CDC mode. I'm getting the Suspend interrupt when the cable is unplugged, but the resume interrupt doesn't occur when the cable is plugged in. Has anyone experienced this or have any guidance?


Fix missing resize event in stdweb ResizeService

This is a fix for the ResizeService module with features = ["std_web"].
Currently when yew calls a registered resize callback, it will result in a panic.
The reason for the panic is that the callback is missing a ResizeEvent argument, which this commit adds.

Thanks!


Issues with X-H2 RAW files.

Think this could just be an issue with libraw versioning, but not sure.
When processing some RAW files from the relatively new X-H2 I get a black bar on the far right.

Code for generating:
import rawpy
import cv2
if __name__ == '__main__':

    # Specify the path to the RAW file
    raw_file_path = "DSCF3764.RAF"

    # Open the RAW file using rawpy
    with rawpy.imread(raw_file_path) as raw:
        # Obtain the RGB image data
        rgb = raw.postprocess()

    # Display the image using OpenCV
    cv2.imshow('RAW Image', cv2.resize(rgb, (0,0), fx=0.1, fy=0.1) )
    cv2.waitKey(0)
    cv2.destroyAllWindows()

Originally I assumed this was a problem with libraw as I had the same problem in darktable. But after upgrading to darktable (and therefore a more up to date version of libraw) the problem went away.
I think I may be missing something with where to confirm the support.

Which rawpy version are you using? What's the libraw version in darktable?

I was using Darktable version 4.2.1 so LibRaw 0.21.1.
For the python code snippet, I've run that on rawpy 0.16.0 (current one used in my project), 0.17.3 and 0.18.1, all producing the same result.

The libraw version is 0.21.1 with 0.18.1, so it shouldn't be that.
Can you share a sample file?

I've a put a raf in this google drive folder, gives me this when run with the code snippet on those versions:

This is a white balance issue. See the parameters you can use here: https://letmaik.github.io/rawpy/api/rawpy.Params.html
In your case, simply using the white balance correction stored by the camera does the trick:
rgb = raw.postprocess(use_camera_wb=True)

The WB is not the issue, the blackbar is. If I rerun the above code with the use_camera_wb=True I still get the black bar:

Apologies, you're right of course.
What's interesting is that the visible area is already smaller than the full area:
        print(raw.raw_image.shape)
        # (5196, 7872)
        print(raw.raw_image_visible.shape)
        # (5184, 7752)

My first thought was that this would be the same. For some reason, libraw doesn't determine the dimensions of the visible area properly leading to the extra black bar.
Running exiftool on the RAW file gives this:
Raw Image Full Size             : 7872x5196
Raw Image Crop Top Left         : 21 12
Raw Image Cropped Size          : 7728x5152
Raw Image Width                 : 7752
Raw Image Height                : 5184

libraw's size visible size matches Raw Image Width/Raw Image Height but not Raw Image Cropped Size. I'm not fully sure why there are three sizes, but it must be related to that.
It would be good to check if you can get the right crop using dcraw.

@kmilos Do you have any idea what's going on here? I'm not that familiar with darktable but I saw it uses both libraw and rawspeed, could that explain the difference in crop behavior? When is darktable using which library?

Thanks @kmilos.
@DuncanM-XR It looks like it's a bug in libraw, can you report the issue there and post the link to it here for tracking?

Looks like the people at libraw seem to think it is just because the X-H2 is only partially supported right now and not full supoorted. Gonna close this issue.


docs: add supported label types in features

Shall we split different features into different files? rather than put all the things in this file?

Will split the file in another pull request.


V1.0.0

V1.0.0 Patch Update
Welcome one and all to the first major stable release for the targon subnet, which occupies netuid 4 on the bittensor network. There is a great amount of changes in this patch, with a complete deletion of the learned reward model.
What Has Changed
• We have completely removed the learned reward model and have opted for a redundant deterministic verification method.
• A new reputation system that is based off successful challenge and inference queries
• Private challenge API to prevent lookup attacks
• Changed naming nomenclature from "validator"/"miner" to "verifier"/"prover"
• Removed crawling synapse
• Ready made docker compose files for running verifier or a prover

LGTM!


Fix spell zoom for countable items

Currently, the zoom effect when hovering over a spell is obstructed by the spell count overlay.
This change disables pointer events for the spell count overlay, allowing the zoom effect to function properly. The change is specifically applied to spells and does not affect items, assuming Noita doesn't allow carrying multiple copies of the same item in the same slot.

Sure!
On the user-facing wands page, where items and spells are shown, the sprite of a spell will be scaled up slightly when you hover over it. I am specifically talking about the little scaling effect when hovering over spells.

In this screenshot, I've marked the boundary boxes of each image in red. Once you're inside that square, the image will be scaled up (or popped out, w/e). If a spell has a spell count, the count itself will block the interaction with the image (shown in orange).
This PR removes any pointer interactions from the orange area, so that the image hover effect will go through. It's basically just a small detail or nitpick, depending on how you look at it!

I understand now, and see what you are talking about. By "overlay" I had thought you meant the tooltips and I was struggling to reproduce. Thanks for explaining :)
A better fix here is to change the "hover" effect to more accurately reflect the desired behavior:
Rather than:
.spellZoom:hover {
  transform: scale(120%);
}

This should be:
.spell-slot:hover .spellZoom {
  transform: scale(120%);
}

(this separately defines the "thing that is hovered" from "the thing that is zoomed", so that the hover-able area is broader than the element the zoom effect is applied to)
This fixes the problem without messing with pointer-events: none (which can cause undesirable and confusing effects).

You're right, and it makes the intent clearer as well.
Sorry for the hold-up. I've pushed the changes.

No worries on the delay, I would have made the changes myself but I wanted you to have the commit credit :)


Draft: Scaled Dot Product Attention API in JAX

Attention mechanisms, particularly the Scaled Dot Product Attention, play a vital role in modern neural architectures, especially in transformers. This PR introduces a JAX-based Scaled Dot Product Attention API, providing users with an optimized, flexible, and easy-to-use interface.

Thanks for this!
Is there a way to test that XLA:GPU is lowering indeed this to the intended cuDNN calls? (I have some ideas for how to do that, and I can give them a shot if you'd like, but I wanted to check if you already had thoughts on this.)

Thanks for this!
Is there a way to test that XLA:GPU is lowering indeed this to the intended cuDNN calls? (I have some ideas for how to do that, and I can give them a shot if you'd like, but I wanted to check if you already had thoughts on this.)

I have some internal unit tests that I'm using to validate the lowering. But it'd be great if you can give it a shot :).

This project is replaced by https://github.com/google/jax/pull/18814
So closing this PR.


Feat/email type

hi @plutov,
I have added the new question type email which is mentioned in the issue #20, I've tested the code from the UI It is working fine. Please let me know if there is any change required or you want me to add any other validations to it.
Thanks!

Hi @plutov,
I’ve added ozzo/validation to include proper checks on the email as requested. I accidentally marked the conversation as resolved, but I’m happy to make further changes if needed.

Thanks @anveshthakur the PR looks good. I will test it on my machine once I have a bit more time.

sure @plutov, thanks!

Thanks @anveshthakur your change is now in the latest release!

@anveshthakur I only noticed that the tests have failed but fixed those.

@anveshthakur I also noticed that email is not shown on the response page.


typescript errors

I'm submitting a bug report

Aurelia Skeleton Version
skeleton-typescript

Framework Version:
1.1.2

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
8.9.0

NPM Version:
5.5.1

**JSPM **
JSPM 0.16.53

Browser:
all

Language:
TypeScript

Current behavior:
When following the given readme for skeleton-typescript after trying to execute the test-skeleton. (installing etc works). The following errors (in part) occur:
X:/node_modules/typescript/lib/lib.dom.d.ts(3913,11): error TS2300: Duplicate identifier 'Headers'.
[03:05:04] gulp-notify: [Error running Gulp] Error: X:/node_modules/typescript/lib/lib.dom.d.ts(3913,11): error TS2300: Duplicate identifier 'Headers'.
X:/node_modules/typescript/lib/lib.dom.d.ts(3922,13): error TS2300: Duplicate identifier 'Headers'.
[03:05:04] gulp-notify: [Error running Gulp] Error: X:/node_modules/typescript/lib/lib.dom.d.ts(3922,13): error TS2300: Duplicate identifier 'Headers'.
X:/node_modules/typescript/lib/lib.dom.d.ts(9227,11): error TS2300: Duplicate identifier 'Request'.
[03:05:04] gulp-notify: [Error running Gulp] Error: X:/node_modules/typescript/lib/lib.dom.d.ts(9227,11): error TS2300: Duplicate identifier 'Request'.
X:/node_modules/typescript/lib/lib.dom.d.ts(9244,13): error TS2300: Duplicate identifier 'Request'.
[03:05:04] gulp-notify: [Error running Gulp] Error: X:/node_modules/typescript/lib/lib.dom.d.ts(9244,13): error TS2300: Duplicate identifier 'Request'.

...
typings\globals\whatwg-fetch\index.d.ts(3,15): error TS2300: Duplicate identifier 'Request'.
[03:16:56] gulp-notify: [Error running Gulp] Error: typings\globals\whatwg-fetch\index.d.ts(3,15): error TS2300: Duplicate identifier 'Request'.
typings\globals\whatwg-fetch\index.d.ts(41,15): error TS2300: Duplicate identifier 'Headers'.
[03:16:56] gulp-notify: [Error running Gulp] Error: typings\globals\whatwg-fetch\index.d.ts(41,15): error TS2300: Duplicate identifier 'Headers'.

I've truncated a lot of similar errors ("duplicate identifier"), the X:/ is the location where I've created the project with the skeletal build.
I've tried following the solutions given https://github.com/aurelia/skeleton-navigation/issues/775 But those don't seem to solve the problem (npm uninstall @types\whatwg-fetch) - I presume this is due to the skeletal builds not using @types declaration but rather the deprecated typings module?
Expected/desired behavior:

I expect the skeletal builds to fully work with the newest libraries of aurelia/typescript - since they're created for those?

Cloned repo.
Changed  directory to skeleton-typescript
executed yarn
executed yarn jspm install
executed yarn gulp watch
no problems found.
git clean  -d -x  -f
npm install
.\node_modules.bin\jspm install
.\node_modules.bin\gulp watch
no problems found
node -v
v8.9.4
npm --version
5.6.0
Can you retry?
Oh.. I did it with master.. will have to retry with latest release

@Alexander-Taran I have retried against master and everything is fine.  Seems to be an issue only with the released version (which is the recommended download in the docs).

Now this transforms into a huge task (-:
Check all other skeletons on master.
Update to webpack 4
Check and update all documentation referencing skeletons
and release
help_needed

This problem is indeed with the "archive download" from the documentation. ("start here").

The TypeScript skeleton has another issue it seems -
// Error: (SystemJS) Cannot read property 'base64encode' of undefined

When cloning a clean skeleton and installing fresh deps from npm and jspm this error is thrown.  Trying to figure out the cause now but I think the tests are broken on latest release.

Disregard looks like it is a known TS issue - https://github.com/Microsoft/TypeScript/issues/24638 - that has a fix about to release.

@3cp I think we can close this..


Feacture: You should add telegram ,youtube and whatsapp icon also in footer with other social media.

Is your feature request related to a problem? Please describe.
Social media icons are less you should add more .
Describe the solution you'd like
You should add telegram ,youtube channel and whatsapp icon also in footer with other social media.
So that they can follow your website everywhere and reach out to you from anywhere.

Hello Ma'am , If you think this issue is valid then please assign me this issue for GSSoC'24.
Thank you

Please assign me this issue under gssoc'24

Its not required currently in website.

Okay ma'am


can scope support mips64le

What you expected to happen?
can scope support misps64le
What happened?

How to reproduce it?

Anything else we need to know?

Versions:

$ scope version
$ docker version
$ uname -a
$ kubectl version

Logs:
$ docker logs weavescope

or, if using Kubernetes:
$ kubectl logs <weave-scope-pod> -n <namespace>

Possibly.  We don't build for that architecture in CI, but Go does target it.
You'd probably have to tweak the same files that mention ppc64le.
Let us know how you got on!


many words are not translated

when switching to different lanugages, the Switch Accounts seems stay in English
test it on https://staging.fightpandemics.work/

some of them (e.g. the Switch Account) was due to Lokalise QA warnings (see below picture), others are code issue

@ddveloper , you can search the key on home page even the word is already translated.  also you can use translation channel to get help .

for the warning , it is not blocking the display on the website.

Thanks @adorapham , this issue is duplicated with #1916 , I am closing this


Added all the stuff needed to resolve issue #8

The pom should now be compatible with the requirements specified in http://central.sonatype.org/pages/apache-maven.html
In order to deploy your release you need:

an account at Sonatype's Nexus (see http://central.sonatype.org/pages/ossrh-guide.html#review-requirements )
you must add your Sonatype Nexus credentials to your settings.xml under with "ossrh"
GPG installed on your build computer AND a GPG key to sign your deployables with

With all those things in place: just run mvn -P release clean deploy

Nice! I'm very excited. I will shoot to get it deployed this weekend! Thanks for the first PR!

@zapodot I think I have it released. Not 100% sure if I did everything correct. It also doesn't show up in maven central yet. Though I heard it can take some time for it to propagate through to search.
https://oss.sonatype.org/content/repositories/releases/com/kennycason/kumo/1.0/

        <dependency>
            <groupId>com.kennycason</groupId>
            <artifactId>kumo</artifactId>
            <version>1.0</version>
        </dependency>

seemed to work!

Nice!
Congrats @kennycason :-)
On Tue, Mar 31, 2015 at 6:27 PM, Kenny Cason<EMAIL_ADDRESS>wrote:

    <dependency>
        <groupId>com.kennycason</groupId>
        <artifactId>kumo</artifactId>
        <version>1.0</version>
    </dependency>

seemed to work!
—
Reply to this email directly or view it on GitHub
https://github.com/kennycason/kumo/pull/9#issuecomment-88158571.


Move projects to point to root project as parent

This moves the projects users are enrolled to point to the root project,
which is now detected during Minder startup. This thus removes the need
for organizations as a whole. We'll slowly start moving towards removing
this concept from the code-base.
For now, this removes the organization-related queries and makes users
point to their project instead.
User deletion is now handled by figuring out the projects a user had
grants in and removing the projects if there's no more tuples in them.
Actual removal of foregin key constraints for organizations will happen
in a subsequent PR.

I'm not sure this is a good idea.  While we have the abstract idea of all projects being equivalent, I'm worried about follow-on consequences of having a single root parent.
For example, adding this code means that any user who gets read access to the Minder Root project will be able to read statuses for every organization.  I don't think we have (for example) audit processes in place to be able to handle that.  Furthermore, with UIs coming on-line, I'm concerned about the UIs not adequately communicating whether the access is through some sort of privileged "Minder Root" or through access further down in the project hierarchy.

Well, the idea is not to grant anybody full view rights to minder root. The only roles that should be granted should be aimed for support.

@JAORMX - hey, should we close this one?

coverage: 38.412% (-0.2%) from 38.593%
when pulling 8c7cb392c125f71681e0a257296659a6ae8b76b7 on no-more-orgs-p1
into 85ff2e8cabf654d9aab459cd3886e1b32242cc87 on main.

What do you mean

agh! I need to rebase. I'll do this early tomorrow.

Rebased

I just noticed that the users table has a cascade deletion based on the org ID. So when the migration is run, the users get deleted.

Ooohoho so I do need to remove the org reference for users in this PR. I'll do that

@eleftherias thanks for the review. I just added a commit that removes the org from users. I set up a local environment with two keycloak users without the PR, then ran the upgrade. The users were still there and minder is still able to get the project associations.

@evankanderson can you revisit this?

I needed to rebase due to a conflict.


Feature request: Add ability to clear child's value of Counter object for pushgw

Proposal
When using the pushgw there is the ability to clear a counter object. This will clear all the children of the counter. However, what is needed is the ability to clear only the counter value a particular child of the counter object while keeping everything else (i.e. labelValues, labelNames) the same.
E.g. (using Java client)
`
samples = ((Counter) collector).collect();
    Collector.MetricFamilySamples mySingleSample = samples.get(0);

    for (Collector.MetricFamilySamples.Sample sample : samples.get(0).samples) {
        if (sample.labelValues.get(0).equals(myUniqueId)) {

            // *****Example of method signature*****
            sample.value.clear();

            }
        }
    }`

Alternatively, children of a counter object can become public instead of protected to allow access to them.
Use case: Say we have 10 interfaces across 3 switches where each have in_pkts metric. I am getting the count of in_pkts of the interface. If the interface counters are reset by a human or by  hardware reboot for 1 interface out of my 10 interfaces then my count needs to be cleared for only for that particular interface.
Bug Report
What did you do?
((Counter) collector).clear()
Environment
Java client of pushgw and prom
Here is a picture of what the counter being cleared looks like in prom

Posted this  issue on the wrong page. Closing issue and posted on https://github.com/prometheus/client_java/issues/512


Add helper text to CMS for alt and title fields under uploaded images

User story

As a design system contributor, I want to understand whether I should add alt text and titles to the images I'm uploading and if so, how I should write it so that I know what I'm contributing to the Design System is 508-compliant.

Background

We currently have fields for alt text and an image title for image uploads, but we don't have any guidance or helper text on those
Folks might not know why and how to write accessible ALT and title text for uploaded images. As a usability improvement, we could provide them with some short guidance through helper text for the fields.
Also, one of our maintenance principles is to not customize the Netlify CMS, so that it's easier to upgrade and maintain. I'm not sure whether vanilla Netlify offers helper text for fields or not?

Work likely involved

A little bit of technical discovery
Write helper text
Implement it

Likely cannot fix this because it uses the out-of-box image upload widget.


New game available written using DirectXTK12

It'd be great if you would like to add my game to your list in the Game Gallery page.
Link: Using the Microsoft Store App, search for "Frenetic".
YouTube video clip link:  https://www.youtube.com/watch?v=hK5uK-H_9uU
Thanks.

Done. Awesome!


⚠ LabBricks has degraded performance

In 38ca1dc, LabBricks (https://labbricks.com) experienced degraded performance:

HTTP code: 523
Response time: 3210 ms

Resolved: LabBricks performance has improved in 1f46bf4 after 12 minutes.


For transparency, remove BG for buffers and gray out the text

The transparency options don't currently set the TabLine. Here is a before & after:

Thanks!


Config order for Iceberg tables

I have recently encountered this issue when I tried to run a dbt model with the following config:
{{
    config(
        table_type='iceberg',
        materialized='incremental',
        incremental_strategy='merge',
        unique_key='id',
        schema='some_schema',
        ...
    )
 }}

The error:
Running with dbt=1.6.7
Registered adapter: athena=1.6.4
...
Encountered an error:
argument of type 'NoneType' is not iterable

This config used to work successfully.
I figured out the reason of this issue is the order of table_type and materialized.
And it is solved with the following config:
{{
    config(
        materialized='incremental',
        table_type='iceberg',
        incremental_strategy='merge',
        unique_key='id',
        schema='some_schema',
        ...
    )
 }}

Is this expected or a bug?

@talhasenSC I'm wondering if the issue is now fixed with https://github.com/dbt-athena/dbt-athena/commit/e398aecc4e78385cc79c5d0c503c0164b73efbc0, could you check that please?

@talhasenSC do you have more input on this issue? does release 1.6.4 of dbt-athena-community fix your issue?

I couldn't reproduce the issue again, will update if happens again


Carthage Firebase 6.6 reports error Unable to find module header

[READ] Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request make sure the issue title starts with "FR:".

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.

[REQUIRED] Step 2: Describe your environment

Xcode version: 10.3
Firebase SDK version: 6.6
Firebase Component: Firebase
Component version: 6.6

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
carthage update --platform iOS
upgrades to 6.6, I had to revert to 6.5 by forcing the Cartfile to point to "== 6.5"
error occurs when building my project in Xcode:
/Users/user/Projects/Dem/Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap:3:10: warning: skipping 'Firebase.h' because module declaration of 'Firebase' lacks the 'framework' qualifier
header "Firebase.h"
^
/Users/user/Projects/Dem/Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap:1:1: note: use 'framework module' to declare module 'Firebase'
module Firebase {
^
/Users/user/Projects/Dem/Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap:3:10: warning: skipping 'Firebase.h' because module declaration of 'Firebase' lacks the 'framework' qualifier
header "Firebase.h"
^
/Users/user/Projects/Dem/Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap:1:1: note: use 'framework module' to declare module 'Firebase'
module Firebase {
^
/Users/user/Projects/Dem/Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap:3:10: error: header 'Firebase.h' not found
header "Firebase.h"
^
:0: error: could not build Objective-C module 'Firebase'

@possen Thanks for the report.  We'll take a look.
Another workaround would likely be to copy the 6.5.0 Firebase.framework to a 6.6.0 installation.

I have the same problem ((

Sorry about the trouble! I'll try to get a fix up early tomorrow for this.

Had this issue (all of sudden and unexpectedly), took some time to figure out what the probable cause might be.
I simply restricted Carthage to only using version 6.5.0
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" == 6.5.0
not sure if it work for all the libraries, but the ones I'm using worked find

I simply restricted Carthage to only using version 6.5.0

It's a good, though temporary, solution.
Well, we're waiting for an update from the project maintainers.

The problem is that Firebase module definition at Carthage/Build/iOS/Firebase.framework/Modules/module.modulemap is missing the framework specifier.
The simplest workaround is to edit the file to include it:
framework module Firebase {
  export *
  header "Firebase.h"
}

We'll look into posting a 6.6.1 version of FirebaseAnalyticsBinary with the fix.

Thanks @paulb777.
Its working fine now.

Its working fine now.

Anyone who reads this and thinks it should work as planned now. Nothing like that. This works if you make changes to module.modulemap, but version 6.6.1 is still not released.

@petrovi4 Yep, sorry it doesn't look like we'll get a 6.6.1 in. Instead we expect the module.modulemap fix to occur in this week's 6.7.0.

I have the same problem ((
When I manually download Firebase.framework version 6.5.0 and replace this file, the compilation stops with an error
ld: warning: Could not find auto-linked framework 'Firebase'
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_GDTTransport", referenced from:
      objc-class-ref in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Similarly, if I replace all the files from Analytics-fe0669fafb68cf16.zip

How did you fix this issue? My CartFile has like this: binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json" == 6.5.0 and after carthage update I still have this issue.

@kkendall33 If the 6.6.0 FirebaseCoreDiagnostics.framework is included, also include the 6.6.0 GoogleDataTransport.framework.

@kkendall33 If the 6.6.0 FirebaseCoreDiagnostics.framework is included, also include the 6.6.0 GoogleDataTransport.framework.

Could you help me find the right path for that? I'm assuming you mean include it with Carthage?

It's in the Analytics folder of the Carthage distribution.

do we have a working solution yet peeps? still running into the issue  and my CI is freaking out :(

Sorry, we're transitioning to improved tooling that will make the Carthage generation and publishing more reliable in the long run.  However, going through a few hiccups in getting it right. We expect to get Carthage 6.7.0 out in the next day or two.

Apologies for the delay - Firebase 6.7.0 is now available on Carthage and should include the updated modulemap. Please re-open this issue if you're still seeing the bug after updating to 6.7.0! Thanks for everyone's patience while we transition our tooling.

When using the manual zip file to upgrade Firebase 6.5.0 to 6.7.0 the same errors occurs in Xcode, this was also the case in 6.6.0 as mentioned before in this ticket:
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_GDTTransport", referenced from:
      objc-class-ref in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
  "_GDTLog", referenced from:
      -[FIRCoreDiagnosticsLog transportBytes] in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
      _FIRPopulateProtoWithCommonInfoFromApp in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Still seeing this too. Updated using carhage 6.5.0 -> 6.7.0

@rowanmulder @ValCanBuild are you seeing the modulemap issue still, or just the Unidentified symbols issue?

The 6.7.0 zip (and Carthage distribution) include additional frameworks in the Analytics folder. Make sure that all of the additions get added to the project.

I had the same problem with undefined symbols GDTTransport and GDTLog.
I have solved the problem by adding the two new frameworks GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework in Carthage/Build/iOS directory to the project.
I also had an additional error:
error: Carthage/Build/iOS/FirebaseFirestore.framework/gRPCCertificates-Cpp.bundle: No such file or directory
The bundle has been moved from FirebaseFirestore.framework to gRPC-C++.framework.

Thanks @mariancerny that helped. Adding GoogleDataTransport.framework was enough to fix it for me (I only use Firebase for auth)

@ryanwilson Sorry my bad, I was missing the new libraries when building the project. I've added the ones @mariancerny (thx!) mentioned for Google Data Transport.
Maybe we can make the documentation more clear for upgrades when libraries get renamed/deleted/added, eg. add it to the release notes or readme.md?

@rowanmulder the doc still talk about copying the gRPCCertificates-Cpp.bundle out of the FirebaseFirestore.framework but its moved to the gRPC-C++.framework as mentioned by @mariancerny we should update the documentation.

I had the same problem with undefined symbols GDTTransport and GDTLog.
I have solved the problem by adding the two new frameworks GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework in Carthage/Build/iOS directory to the project.
I also had an additional error:
error: Carthage/Build/iOS/FirebaseFirestore.framework/gRPCCertificates-Cpp.bundle: No such file or directory
The bundle has been moved from FirebaseFirestore.framework to gRPC-C++.framework.
(The documentation at https://github.com/firebase/firebase-ios-sdk/blob/master/Carthage.md contains the old path.)

How to Add GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework ?

@RanjeetStiga Both GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework are in the Analytics folder.

This problem is still not fixed in latest release, 6.8.1.

@RanjeetStiga Both GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework are in the Analytics folder.

Thanks it's work .

I have have the same problem
I manually download Firebase.framework version 6.1.0 and Crashlytics 3.14.0
Now when I replaced the framework files while updating from 6.1.0 -> 6.9.0
ld: warning: directory not found for option '-F/Users/MyUser/MyCompany/MyApp/Frameworks'
Undefined symbols for architecture arm64:
"OBJC_CLASS$_GDTCORTransport", referenced from:
objc-class-ref in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
"_GDTCORLog", referenced from:
-[FIRCoreDiagnosticsLog transportBytes] in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
_FIRPopulateProtoWithCommonInfoFromApp in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
As suggested by @paulb777 I added the following two frameworks:
GoogleDataTransport.framework and GoogleDataTransportCCTSupport.framework
Now if I debug application on devices that already have my application, it does not stop on breakpoints.
For installing on new devices it gives error:
Could not locate installed application
Install claimed to have succeeded, but application could not be found on device. bundleId = com.XXX.XXXXXXXX
If i run it on simulator it gives error"
This app could not be installed at this time.
Could not install at this time.
Failed to load Info.plist from bundle at path /Users/myUser/Library/Developer/CoreSimulator/Devices/B9775552-65FA-4C1E-8051-06922702A4BC/data/Library/Caches/com.apple.mobile.installd.staging/temp.eJW69a/extracted/Payload/MyApp.app/Frameworks/GoogleDataTransport.framework

@shahabafridi85 Likely you have a mix of Firebase frameworks from different releases.
I'd recommend removing all of them and installing only from 6.9.0

I'm experiencing the same issue as @shahabafridi85. I downloaded the SDK and added it to the project manually. I deleted the previous files from my project and added what was newly downloaded, so there's no mix. Can't install on neither the simulator nor device. Seeing exact same errors. Any other suggestions?

@annca Yes I did resolved the issue.
Thanks @paulb777 for your suggestion. The issue was not because fo  the mix of Firebase frameworks from different releases.
Before I was adding the frameworks by adding the plus (+) on the Embedded Framework section in the Target.
The issue was resolved by deleting the frameworks from old release and then adding the new release frameworks by dragging and dropping in the Project Navigator.
I hope it help you.

Ah got it. Confirming that this helped me resolve the issue as well. Thanks!!!

I have the same error,
ld: warning: Could not find auto-linked framework 'Firebase'
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_GDTCORTransport", referenced from:
      objc-class-ref in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
  "_GDTCORLog", referenced from:
      -[FIRCoreDiagnosticsLog transportBytes] in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
      _FIRPopulateProtoWithCommonInfoFromApp in FirebaseCoreDiagnostics(FIRCoreDiagnostics.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

And not able to solve by any suggested methods. It takes all day. Still it stucks.

@ahmeric It looks like the GoogleDataTransport.framework is missing or it's an old version.

As the original poster, I just wanted to confirm that I was able to upgrade to 6.9.0, by removing the == 6.5 from the Cartfile. Thank you.

Thanks, @paulb777 it has solved my problem. But until today, it was working without adding this framework to the linked libraries.

I am still experiencing this issue. Any viable solution?


Update README to prevent future issues

Does this make sense here? Will this minimize issues in the future? The lack of a manager role seems to be the problem I was having.

:+1:

I do have the manager role listed in mine, and mine works; news to me that it was required, but at the least not gonna hurt anything; :+1: .


fix: add aria-expanded to the toggler trigger

The aria-expanded attribute should be on the trigger not the container of the toggled element(s).
References:
https://www.w3.org/WAI/GL/wiki/Using_aria-expanded_to_indicate_the_state_of_a_collapsible_element
http://3needs.org/en/testing/code/aria-expanded.html
http://www.3needs.org/en/testing/code/aria-expanded-code.html
Closes https://github.com/zurb/foundation-sites/issues/11049

Pushed an update with the proposed changes.


Refactoring form buttons #706

Refactoring few form buttons on these pages:
/products/add-product
/business-pages
/categories/add-category
For now, three screens are ready, please have a look if it is expected behavior.
Checklist

[ ] 🔽 My branch is up-to-date with "development" branch
[ ] 🔗https://github.com/ita-social-projects/horondi_admin/issues/706

CI is Failed
Please check tests  before push


Publish 8.7-20240314011331+0000

Publish 8.7-20240314011331+0000

@bot-gradle test and merge

The merge queue build has started. Click here to see all failures if any.


[openapi] Adopt enum-driven visibility

This is a tracking issue for the OpenAPI library to adopt enum-driven visibility analysis APIs and implement any enhancements to the core typespec libraries that are required to support OpenAPI's use case.
See https://github.com/microsoft/typespec/pull/4825

Hey @wanlwanl, I ended up taking this as part of the related issue for the HTTP core. There won't be anything left to do here after #5416 is merged, as OpenAPI doesn't do much with visibility outside of what the HTTP core does for it.


What happen, when i open the link on phone?

Hi @mxstbr
thank you very much for this passport strategy to support magic links. I would like to use it in my webapp. But what would happen if the user opens the link on phone instead of desktop? Would the user still be logged in on the desktop because he sent the request from there?

The user would then be logged in on their phone, but not on their desktop. Syncing both, though possible, would be considerably harder.

I am having the same issue were you able to solve it @niklasgrewe. I have a method in mind, but I'm not sure if it's the best one. i checked network logs of splitbee the site from wich this stratagy is extracted and they have multidevice support their webapp polls for the status of token is if authenticated


nixos/xdg-portals: add portals to systemPackages

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/145174
Also https://github.com/flatpak/xdg-desktop-portal-gtk/commit/3fd9e6715a98a71c09eea0f6eb00888a7ecd1970 will be installed, associating a name and icon with the name
xdg-desktop-portal-gtk, for the cases where xdg-desktop-portal-gtk fail to
associate a portal dialog with an application toplevel.
window.
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @peterhoeg @tteggel

Thanks for taking the time to figure this out! Selecting a window indeed works in OBS and Firefox.
However the picture it ends up with is grayscale for some reason? And depending on the size it is distorted, and eventually crashes both of the aforementioned applications. Resizing the captured window also makes the shared image immediately go bonkers in weird ways (captured stream only updates partially, but somehow it also updates parts of the area that no longer are part of the window?).

I sometimes get a hang of the screen that is recorded in OBS (don't know when exactly) but there definitely is progress as at least the selection window shows up. I don't know what's at fault but I also have the feeling that OBS recording don't have such a high resolution than I expect (in Firefox this works pretty well so maybe it's just my settings). Resizing breaks it in really fun ways.
Still I think this could be merged as for me it strictly is an improvement.

With this and #152697 I am now able to record application windows on plasma wayland without corruption or constant crashes.

I'd say the pkgs.runCommand solution seems cleaner than pathsToLink, especially considering how unclear this whole situation is. I'm be okay with merging that. Maybe do it only for the kde portal and only if that is enabled, to further reduce clutter?

OK it seems that it has something to do with XDG_DATA_DIRS

Sorry, I have no idea which way this PR should go. Not sure where to begin asking upstream either.

This latest iteration does not seem to work? The joinedPortals env is listed in XDG_DATA_DIRS and contains exactly the expected files, but OBS wayland capture does not work. It's probably worth noting joinedPortals is not linked to /var/run/current-system/sw whereas the previous solutions were (obviously since they modified environment.systemPackages).

On 24/01/22 13:00, jansol @.***> wrote:

This latest iteration does not seem to work? The joinedPortals env is
listed in |XDG_DATA_DIRS| and contains exactly the expected files, but
OBS wayland capture does not work. It's probably worth noting
joinedPortals is not linked to |/var/run/current-system/sw| whereas the
previous solutions were (obviously since they modified
|environment.systemPackages|).

Weird,I am trying it staight from the branch and obs works perfectly
https://gitlab.com/pasqui23/my-nixos-conf/-/blob/main/flake.nix#L70

Ah, disregard that, looks like a problem with the plasma 5.24 beta:
xdp-kde-screencast: Start called with parameters:
xdp-kde-screencast:     handle:  "/org/freedesktop/portal/desktop/request/1_59/obs6"
xdp-kde-screencast:     session_handle:  "/org/freedesktop/portal/desktop/session/1_59/obs2"
xdp-kde-screencast:     app_id:  ""
xdp-kde-screencast:     parent_window:  ""
xdp-kde-screencast:     options:  QMap()
QQmlApplicationEngine failed to load component qrc:/ScreenChooserDialog.qml:13:1: Type PWD.SystemDialog unavailable file:///nix/store/bfs2vvwnlxmarqwgwxp42vnpam8glp3w-plasma-workspace-5.23.90/lib/qt-5.15.3/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:132:9: MobileSystemDialog is not a type
QObject::connect: Cannot connect (nullptr)::accept() to ScreenChooserDialog::accept()
QObject::connect: Cannot connect (nullptr)::reject() to ScreenChooserDialog::reject()
QObject::connect: Cannot connect (nullptr)::clearSelection() to ScreenChooserDialog::clearSelection()
Failed to load dialog, cannot exec

Yep, it's an upstream plasmashell issue that has a fix already merged and with that patch applied to the beta this PR does indeed work.

Sounds good enough to me. Could you please squash the commits so one deals with the formatting and another with the change itself? Or if it is too much work, just squash everything together.

Thanks.

Thanks for seeing this through! That was quite a journey.

Could somebody add the backport release-21.11 label to the issue, please?The patch applies cleanly to the nixos-21.11 branch, and it fixes screen sharing in Firefox (tested with jit.si).


Passphrase:UI suggestion.

In the Passphrase fields,the first field defaults the first letter to lowercase.In the second field(where passphrase is repeated) the first letter defaults to Uppercase.
The first field also default to Upper Case.

Completed


Optionally warn about orphan .git directories

Overview
A .git directory found in src/ usually indicates that the code in the
enclosing directory is managed from said .git directory. This can lead
to confusion, and developers opening PRs against obsolete repos when, as
happens frequently, a formerly separate repository becomes integrated
into the primary repo.
This patch adds to the configure script the ability to warn when it
finds such .git directories, either explicitly using the --warn-git-dirs
flag, or implicitly via the --dev flag.

Testing recommendations
Example output:
$ ./configure --dev --skip-deps
==> configuring couchdb in rel/couchdb.config
WARNING unexpected .git directory src/couch_tests/.git
WARNING unexpected .git directory src/rexi/.git
WARNING unexpected .git directory src/mem3/.git
WARNING unexpected .git directory src/smoosh/.git
WARNING unexpected .git directory src/couch_mrview/.git
WARNING unexpected .git directory src/couch/.git
WARNING unexpected .git directory src/couch_replicator/.git
WARNING unexpected .git directory src/ddoc_cache/.git
WARNING unexpected .git directory src/couch_peruser/.git
WARNING unexpected .git directory src/setup/.git
WARNING unexpected .git directory src/couch_log/.git
WARNING unexpected .git directory src/couch_epi/.git
WARNING unexpected .git directory src/mango/.git
WARNING unexpected .git directory src/chttpd/.git
WARNING unexpected .git directory src/couch_stats/.git
WARNING unexpected .git directory src/global_changes/.git
WARNING unexpected .git directory src/couch_event/.git
WARNING unexpected .git directory src/fabric/.git
WARNING unexpected .git directory src/couch_plugins/.git
WARNING unexpected .git directory src/ken/.git
WARNING unexpected .git directory src/couch_index/.git
You have configured Apache CouchDB, time to relax. Relax.

Related Issues or Pull Requests

Checklist

[x] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

I'm on board with this other than making it conditional. I'd remove the toggle and just run it regardless as it seems like good hygiene for those of us that skip around between major versions fairly often.
Though that also assumes that its not super expensive though it doesn't look like it would be.

@davisp I originally did write it without the conditional, but became concerned about forcing a potentially expensivefind (which I've since improved on by adding -type dir) on everyone each time it was run. Maybe more worrisome though, I'm not sure find is available on Windows, so it seemed best to make it optional, but figured adding it to make dev would probably hit most use cases.

Windows uses the configure.ps1 command thingamajig so that shouldn't be an issue (cc @wohali). For the expensiveness I'm not overly concerned. But if you like then only adding it to --dev seems fine. I don't really see it useful as a standalone option cause I don't think it'd be an issue often enough to really get into muscle memory.

Great, let's make it non-optional since it's simpler.