C++ MessageContent crash 1.7.0

Hi, I'm using C++14 with TD 1.7.0. I'm trying to do a small client for users. I can get the chats properly but all the time I try to access:
td::td_api::message::content_ (td::td_api::MessageContent), my app just crash, and I just don't see why. Here is my sample:
    //The messages comes from getChatHistory     std::cout << "Adding an msg!" << std::endl;     td::td_api::message *object = std::move(msg);     if (!object->content_) {         std::cout << "Invalid MSG content :/" << std::endl;         return;     }
Just trying to access the message's content causes a crash...
If you have a tip or anything...

The line
td::td_api::message *object = std::move(msg);

have no sense. What are you trying to move there?

I tried std::move here, that was just a try... My function:
void MSList::handleNewMessage(td::td_api::object_ptr<td::td_api::message> &msg)  /*What I sent*/ }
But with or without the std::move, it gives the same (and I know this try was dumb as I use &).

So I tried to debug. And all the outputs says that accessing any method of td::tl::unique_ptr cause a crash, seems to be the reason why I can't access td::td_api::MessageContent from td::td_api::message. But I don't know why...

It seems that msg == nullptr in your code.

Ok, so I checked in all my code and the issue was in the use of T *ptr, td::td_api::object_ptr::get() and other stuff. Now works well, unique_ptr are sometimes a mess for me, sry :/ All is good in your lib :+1:


Update weather.js to work with changes to Yahoo API

Hi @LanyonConrad, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@LanyonConrad, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thank you for your contribution. We've accepted a different pull request that provides updated code that obtains a zip code based on geo coordinates.


Replace some LiveData with Flow/StateFlow

LiveData shouldn't be used at non-UI layers, I've replaced it with Flow
LiveData at UI layer (ViewModel) has been replaced to StateFlow
Fixes #112

@hieuwu Conflicts have been resolved

@hieuwu Conflicts have been resolved

Cool. I am reviewing while the job is running

Hi @hieuwu,
I took a new pull after this PR merge. Looks like the cart feature is broken.
Steps to reproduce.

Launch the app and add some item from shop fragment using plus icon
open cart bottom sheet. (added items are shown properly till here)
now close this bottom sheet and add another item same as step 1
open the cart bottom sheet again. Now you will not see the recently added item in the list

This bug was not there before. The last stable merge was #128.
Can we please revert the changes or make the main branch stable until this Issue is fixed.
I have implemented #116, but due to this bug I have not pushed it yet. Let me know if its ok to push my code or should I wait.
Please check the video attached.
Thanks!
https://user-images.githubusercontent.com/51832211/193946013-965e3d7e-5c2a-48b6-88b2-f917232f622c.mp4

Is this bug effect your work? If not, you can push yours, I will create another issue for this bug. Thanks for pointing this out @Devendra34

@all-contributors please add @DeKaN for code


Correct typo in configuration file

Fix the typo in the example for the configuration file

@antalszava @josh146 do the docs need to be updated at all in a similar way?

This was the reason for the weird TOML parsing traceback - in TOML, booleans are all lower case (previously it was True like Python).
This is the only place in the docs it needs to be updated --- the existing config file in the repository was already correct (and tested), it was just a typo in the documentation.
We should also implement a function in PennyLane to easily generate a config file for users


Create AirTable script to generate statuses based on fields provided by sponsor

I think the best way to determine status will be within AirTable, so I will create a field for the status of an application and populate it with a formula that derives the status from the fields indicated by the sponsor in the document received 4/15/22.

Here is the full formula for reference purposes (as of 4/16/22)
IF(   AND(     {Funding Sent} = 1,     {Date Awarded} != "",     OR(       {Online Payment Issues} = "",       {Online Payment Issues} = "No Issue",       {Online Payment Issues} = "Issue Cleared",       {Online Payment Issues} = "Search by $Cashtag"     ),     OR(       {Check Payment Issues} = "",       {Check Payment Issues} = "No Issue",       {Check Payment Issues} = "Issue cleared"     )   ),   "Confirmed Funding Sent", IF(   AND(     {Funding Approved} = 1,     OR(       AND(         {Online Payment Issues} != "",         NOT(           OR(             {Online Payment Issues} = "No Issue",             {Online Payment Issues} = "Issue Cleared",             {Online Payment Issues} = "Search by $Cashtag"           )         )       ),       AND(         {Check Payment Issues} != "",         NOT(           OR(             {Check Payment Issues} = "No Issue",             {Check Payment Issues} = "Issue cleared"           )         )       )     )   ),   "Payment Problem", IF(   AND(     {Intake Complete} = 1,     {BRF Application Status} = "Ok to fund",     {Funding Approved} = 1   ),   "Payment Pending", IF(   OR(     {BRF Application Status} = "Disqualified",      {BRF Application Status} = "Duplicate"   ),    "Cancelled",  IF(   AND(     {BRF Application Status} = "Does not want funding",      {Intake Complete} = 1   ),   "Declined", IF(   {BRF Application Status} = "Ineligible",    "Ineligible", IF(   AND(     {Intake Complete} = 1,     {BRF Application Status} = "Ok to fund"   ),   "Approved", IF({Intake Scheduled Date Time} != "",   "Scheduled", IF(   OR(     {Invited to Intake Email} != "",     {Invited to Intake Text} != "",     {Invited to intake phone call} != ""   ),   "Invited",   "Submitted" ) ) ) ) ) ) ) ) )

And the formula for the descriptions:
IF({PWA Status} = "Confirmed Funding Sent",
  "Approved: Payment has been sent.",
IF({PWA Status} = "Payment Problem",
  "Payment details need correcting.",
IF({PWA Status} = "Payment Pending",
  "Application has been approved. Please allow up to several weeks for funding.",
IF({PWA Status} = "Cancelled",
  "This application has been cancelled.",
IF({PWA Status} = "Declined",
  "This application has been declined.",
IF({PWA Status} = "Ineligible",
  "This application does not meet eligibility requirements.",
IF({PWA Status} = "Approved",
  "Application has been approved. Please allow up to several weeks for funding.",
IF({PWA Status} = "Scheduled",
  "Intake interview has been scheduled.",
IF({PWA Status} = "Invited",
  "Invitation to schedule intake interview has been sent.",
IF({PWA Status} = "Submitted",
  "Application received.",
  "No description set."
)
)
)
)
)
)
)
)
)
)


Add an argument to Makefile.example to enable building debug/release version only

Right now make all from the bootstrap directory builds both debug and release builds of CPF and all the components (llvm, noelle, etc)
On my system, this quickly exhausted all the available disk quota.
Please add a makefile argument allowing to choose either debug or release configuration to build.
Yours,
Andrey
===
Advanced Software Technology Lab
Huawei

The whole compilation takes 31G on my machine, and most of which is used by compiling LLVM.
Currently, the framework is far from stable so compiling both DEBUG and RELEASE is still crucial for us and as you might find is pretty much hardcoded in the Makefiles. It will take some effort to decouple this and I'll put "adding argument to compile release or debug version only" as a low priority task, and we will work on it after September 2021.
As a workaround, here are the step by step guide to avoid build llvm in debug mode (saves 20.8G; will use around 10G instead of 31G to build the whole toolchain after this change).

Follow the Dockerfile till apply patch (line 23)
cp /home/cpf-workspace/cpf/bootstrap/Makefile.llvm /home/cpf-workspace/
make -f Makefile.llvm llvm-objects-release
In Makefile (copied from Makefile.example), change compile-llvm=1 to compile-llvm=0 and change both llvm-install-dir-debug and llvm-install-dir-release to /home/cpf-workspace/llvm-install-release
Run make all with the modified Makefile

The whole compilation takes 31G on my machine, and most of which is used by compiling LLVM.
Currently, the framework is far from stable so compiling both DEBUG and RELEASE is still crucial for us and as you might find is pretty much hardcoded in the Makefiles. It will take some effort to decouple this and I'll put "adding argument to compile release or debug version only" as a low priority task, and we will work on it after September 2021.

OK, got it. Makes sense.

As a workaround, here are the step by step guide to avoid build llvm in debug mode (saves 20.8G; will use around 10G instead of 31G to build the whole toolchain after this change).

Follow the Dockerfile till apply patch (line 23)
cp /home/cpf-workspace/cpf/bootstrap/Makefile.llvm /home/cpf-workspace/
make -f Makefile.llvm llvm-objects-release
In Makefile (copied from Makefile.example), change compile-llvm=1 to compile-llvm=0 and change both llvm-install-dir-debug and llvm-install-dir-release to /home/cpf-workspace/llvm-install-release
Run make all with the modified Makefile

Thanks!


Support max_parallel_api_rate to call InvokeModel API parallelly to shorten the embedding time

From the following code,  it seems that BedrockEmbedding is currently calling API sequentially based on the given list.
https://github.com/langchain-ai/langchain-aws/blob/4aebf1709d31220bcf248acdc9094f4547d6ef0c/libs/aws/langchain_aws/embeddings/bedrock.py#L164-L175
Typically, chunk sizes are not large, and the time required for embedding is also minimal, which results in a large number of API calls being executed sequentially.
As a result, the impact of network latency becomes significant and cannot be ignored.
Additionally, due to differences in the availability of models by country, specifying a model that is only available in another country can further increase latency, causing the majority of the embedding time to be spent waiting for a response due to network latency.
The provided chunks are in a list, and by calling the embedding API in parallel, it should be possible to reduce the impact of latency.

Why not use aembed_documents ? It is an async call and will give far better performance.


Group in docs, I think is wrong

Sentry::group()->create('mynewgroup');
says a string, but it's an array that is required
Sentry::group()->create(array('name' => 'mynewgroup', 'level' => 100));

Nice catches.. I swear I updated those.. oh well.  Will update first thing tomorrow.


Wrong engine version crashes binary that is using OpenSSL

When engine (for example gost.so) compiled for openssl-1.1.1, but accidentally loaded in binary linked with openssl-3 this binary just crashes. This is very confusing for a user.
Crash cause if that binary is linked with libcrypto.so.1, but gost.so is linked with libcrypto.so.3 and when gost.so is loaded there is multiple libcrypto.sos causing mess.
Currently, there is no way in the engine to prevent a crash and to output polite explanatory message to the user. While engine could return 0 in initialization sequence it does not know when to do it. We cannot just all to OpenSSL_version since it's versioned symbol and will call libcrypto.so linked with gost.so, not that's calling us. Cannot iterate over loaded engines (with ENGINE_get_first+ENGINE_get_next) since loading engine is not loaded yet.
It would be beneficial for end users and for engine authors if there's a way to check that engine is loaded into libcrypto of different version than it's compiled for (to prevent its loading).
ps. @beldmit @levitte Perhaps, you may be interested in this feature.

One idea I got is to iterate over dl_iterate_phdr (when engine initializes) and if more than 1 *libcrypto.so* is found fail engine loading with an explanatory error message.

I've got a different idea.
But I don't know for sure if it works in practice:
how about this?
--- a/include/openssl/engine.h
+++ b/include/openssl/engine.h
@@ -722,6 +722,7 @@ typedef int (*dynamic_bind_engine) (ENGINE *e, const char *i
             CRYPTO_set_mem_functions(fns->mem_fns.malloc_fn, \
                                      fns->mem_fns.realloc_fn, \
                                      fns->mem_fns.free_fn); \
+            OPENSSL_init_crypto(OPENSSL_INIT_NO_ATEXIT, NULL); \
         skip_cbs: \
             if (!fn(e, id)) return 0; \
             return 1; }

So, I tried that, and it seems to "fix" the common case, where a statically built application loads an engine with the same openssl version, but EVP objects created by 1.1.1 cannot be used by the 3.0 application, that is probably the reason why the crash happens for you.
I guess we should increment the OSSL_DYNAMIC_VERSION and make the engines officially incompatible,
see #17106

seems like the PR to increment the dynamic version has been completed, and so this can be closed.
Marking as inactive, to be closed at the end of the 3.4 dev cycle, barring further input


Incorrect links:  Readme and Quick Start pages

On the Homepage / Readme

“Result mixers” link in the 5th bullet under "Features" goes to the top of the User Guide, not to the Result Mixers section:  https://github.com/sidprobstein/swirl-search/wiki/2.-User-Guide#mixers
“to-do list” link under "Contributing" returns a 404:  https://github.com/sidprobstein/swirl-search/blob/main/docs/TO_DO.md
"Documentation" section, those links are the only one that display horizontally; were they supposed to be a vertical, bulleted list?

On the Quick Start page

"Next Steps" section, the “Relevancy Explanation” link leads to raw content version of the page, here:
https://raw.githubusercontent.com/wiki/sidprobstein/swirl-search/2.-User-Guide.md#relevancy-explanation

Fixed in main, will be released in 1.3_final, THANK YOU!

Fixed in 1.3 Final


Add a button to remove memory view from drop down list

Is your feature request related to a problem? Please describe.
I want to remove some memory view from drop down list, but currently there is only add and modify button.
Describe the solution you'd like
maybe add a remove button for deleting current memory view?
Describe alternatives you've considered
maybe add button at Edit popup window to delete the memory view?

Did you see the button on the top right of the Window? This is where most close buttons are in VSCode Panels.

oh, i just see that button, thanks!
But i still think close button is not that obvious, and might be too far away from main function zone. I feel it might be a little better to move the button closer to main function zone.

I partially agree. But, we are following the VSCode design language. If we add it to the main toolbar, then we have to create/add a prompt because you can accidentally hit it.
I will see if VSCode has a more prominent Close button. Even these, we don't make our own.


[BUG] Assertion when you add static class into didFinishLaunchingWithOptions

Adding the code below causes this Assertion failed: top_size>=3 [0, 3]
We should prevent/warn the user about what they are doing
    func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
        // Override point for customization after application launch.

        class CardDeck: RLMObject {
            dynamic var name = ""
        }

        let deck = CardDeck()
        deck.name = "New Deck"
        let realm = RLMRealm.defaultRealm()
        realm.beginWriteTransaction()
        realm.addObject(deck)
        realm.commitWriteTransaction()

        return true
    }

The problem that's happening here is that CardDeck is being defined as a nested class, scoped to application(application:didFinishLaunchingWithOptions:).
Swift's mangling doesn't provide enough information to determine all the details we need from this class when we initialize the schema.
I recall seeing this a few months ago and briefly looking into whether or not we could inform the user of what they were doing wrong, but we clearly didn't find a suitable solution. It's worth looking into it again, though.

We currently only check if a class definition is nested inside another class, clearly we need to also see if the mangled name points to it being nested inside a function, struct, or enum as well.


fix: add permissions to auto-commit.

It is no longer necessary to activate
settings -> actions -> general -> read and write && allow approve pull request
Description
Please provide a brief description of your changes here.
Checklist
Setupping Frames:

[ ] I Have disabled the actions/init-banner.
[ ] I Have changed the frameiterator file to 1.
[ ] I Have setupped the config.conf.
[ ] I Have deleted the old frames and replaced the new frames.
[ ] I Have created a new Album and get the Album ID (optional).
[ ] I Have setupped the subtitles (optional).

QA: After you pushed the changes:

[ ] Have you enabled actions/init-banner?
[ ] I Have confimed it is working.
[ ] Is it visible to public?

Checklist for Feats
Please review and complete these items before submitting your pull request:

[ ] I have tested my changes thoroughly and they work as expected.
[ ] I have included appropriate tests for any new features or bug fixes.
[ ] My code is well-formatted and complies with the ShellCheck standards.
[ ] I have updated the documentation (if applicable).
[ ] I have read and agree to the code of conduct and contribution guidelines.

Prevents the error of forgetting read and write permissions for the github interface.
Prevents the bot from looping by never updating the frameiterator


Tesla presence seems unreliable

Just a heads-up, not an issue until confirmed by someone else. Twice in two days the Presence has remained “Away” after I returned to the garage from an outing. The only way I could restore correct operation was by rebooting my HA machine (RPi5, HA in a Container, located right beside the Tesla in the garage). The Pi5 talks WiFi to an access point which is also located in close proximity. The Tesla shows up in BLE Hero on my phone. I do not have the HA BLE Tracker installed. As best I can recall, the Presence indication has been quite accurate and responsive prior to this. Summer is warming up the garage down here in AU, so it may be a chip temperature problem, although I do have the Pi in an enclosure with a fan.

It happened again today. Three times in a row now.

Others have reported similar issues. I have not had the issue myself and have been unable to reproduce. Temperature might be a factor, it's winter here in the UK so no chance of it getting too hot for me

Hi Iain,I don’t know if your stuff and the iBeacon tracker play together (I’m guessing that you don’t even use the beacon), but I am going to try to compare their outputs. I might also build the ESPHome ESP32 iBeacon hub and see what it says. Neil Higgins @.*** 19 Nov 2024, at 6:26 PM, Iain Bullock @.***> wrote:
Others have reported similar issues. I have not had the issue myself and have been unable to reproduce. Temperature might be a factor, it's winter here in the UK so no chance of it getting too hot for me
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I have Googled around a bit (a sad excuse for research, I admit) and I must say I can’t find any confirmation that the Model Y puts out a conforming iBeacon. That leaves open the question as to why Presence ever worked for me (if it relies on an iBeacon) but might also explain why it stopped working (I have recently had two Tesla software updates in quick succession). So if I can scan for Bluetooth devices of any kind (not just iBeacons), I might have better luck. Neil Higgins @.*** 20 Nov 2024, at 2:40 AM, Iain Bullock @.***> wrote:
Not sure. I am experimenting with https://gateway.theengs.io/ to track my Apple watch using the same RPi. Seems to work fine. I therefore suggest you can run another iBeacon tracker on the same device, which might turn out to be more reliable than the Presence detection used on this project
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

FWIW, I took a deep breath and had a look at the _core source code. It appears (to me) that Presence is not derived from an iBeacon. And for the fourth day in a row, my Tesla is shown as “Away” when it’s at home. It behaved in more-or-less random fashion between about 5:30am and 11:00am, then settled to “Away”.
From: Iain Bullock @.>
Sent: Wednesday, 20 November 2024 2:40 AM
To: tesla-local-control/tesla_ble_mqtt_docker @.>
Cc: etherbrat @.>; Author @.>
Subject: Re: [tesla-local-control/tesla_ble_mqtt_docker] Tesla presence seems unreliable (Issue #65)
Not sure. I am experimenting with https://gateway.theengs.io/ to track my Apple watch using the same RPi. Seems to work fine. I therefore suggest you can run another iBeacon tracker on the same device, which might turn out to be more reliable than the Presence detection used on this project
—
Reply to this email directly, view it on GitHub https://github.com/tesla-local-control/tesla_ble_mqtt_docker/issues/65#issuecomment-2486215088 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKEPQNHZVSWPM6XGQQ6DFC32BNSWRAVCNFSM6AAAAABR7MZLH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGIYTKMBYHA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AKEPQNADGB5JT2OIOC66W5L2BNSWRA5CNFSM6AAAAABR7MZLH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUUGCQ3A.gif Message ID: @.*** @.***> >

Sorry I misunderstood your previous quetion. You are right the code doesn't look for iBeacons it just scans for the BLE MAC; which should work reliably, but clearly it doesn't.
I recommend you try turning off Presence detection in this code and using another docker container on your device which can provide the required functionality. I haven't tested any project for doing this for the car, but as I said earlier I have got  https://gateway.theengs.io working for tracking my Apple watch, so maybe it can be configured to track your car

Yes, I’ll try that.
I have raised an Issue on the _core project – hopefully their powers of diagnosis are better than mine.
Cheers,
Neil
From: Iain Bullock @.>
Sent: Wednesday, 20 November 2024 4:39 PM
To: tesla-local-control/tesla_ble_mqtt_docker @.>
Cc: etherbrat @.>; Author @.>
Subject: Re: [tesla-local-control/tesla_ble_mqtt_docker] Tesla presence seems unreliable (Issue #65)
Sorry I misunderstood your previous quetion. You are right the code doesn't look for iBeacons it just scans for the BLE MAC; which should work reliably, but clearly it doesn't.
I recommend you try turning off Presence detection in this code and using another docker container on your device which can provide the required functionality. I haven't tested any project for doing this for the car, but as I said earlier I have got https://gateway.theengs.io working for tracking my Apple watch, so maybe it can be configured to track your car
—
Reply to this email directly, view it on GitHub https://github.com/tesla-local-control/tesla_ble_mqtt_docker/issues/65#issuecomment-2487621861 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKEPQNA2C6VWVJIDLVK52T32BQU77AVCNFSM6AAAAABR7MZLH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBXGYZDCOBWGE .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AKEPQNBTCJA6XNBIUFSM2FT2BQU77A5CNFSM6AAAAABR7MZLH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUUIYMOK.gif Message ID: @.*** @.***> >

I'm a dev on the core project too, so it might become a circular conversation.
@raphmur @baylanger have a look to see what you think, there are issues with presence detection but I can 't replicate it myself

Good for you! (seriously). Bear in mind that I am now uncertain whether charge rate setting controls will get to the Tesla when the Presence is “Away”. If not, the whole bloody exercise is pointless, yah?Neil Higgins @.*** 20 Nov 2024, at 5:22 PM, Iain Bullock @.***> wrote:
I'm a dev on the core project too, so it might become a circular conversation.
@raphmur @baylanger have a look to see what you think, there are issues with presence detection but I can 't replicate it myself
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

As long as the car is not really away, the commands will still work. The presence detection and command sending are completely seperate and independent of each other in the code. Others who have reported this issue have found command sending still works even when presence doesn't

That’s reassuring. Thanks. Neil Higgins @.*** 20 Nov 2024, at 6:55 PM, Iain Bullock @.***> wrote:
As long as the car is not really away, the commands will still work. The presence detection and command sending are completely seperate and independent of each other in the code. Others who have reported this issue have found command sending still works even when presence doesn't
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Correct typo in RFModel docstring

Codecov Report

Merging #258 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #258      +/-   ##
==========================================
- Coverage   77.58%   77.54%   -0.04%
==========================================
  Files          97       95       -2
  Lines        4622     4601      -21
==========================================
- Hits         3586     3568      -18
+ Misses       1036     1033       -3

Impacted Files
Coverage Δ

GPyOpt/models/rfmodel.py
53.33% <ø> (ø)
:arrow_up:

GPyOpt/util/__init__.py

GPyOpt/testing/__init__.py

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 ab291b9...112dd65. Read the comment docs.


chore: New naming scheme for attributes

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ
Complexity Δ

src/FlatMapper.php
98.98% <100.00%> (ø)
44.00 <0.00> (ø)

src/Mapping/Identifier.php
0.00% <ø> (ø)
1.00 <0.00> (?)

src/Mapping/ReferenceArray.php
0.00% <ø> (ø)
1.00 <0.00> (?)

src/Mapping/Scalar.php
0.00% <ø> (ø)
1.00 <0.00> (?)

src/Mapping/ScalarArray.php
0.00% <ø> (ø)
1.00 <0.00> (?)


objectId is no longer returned when using "az ad sp show --id  xxxxx-xxxx-xxxx-xxxx-xxxxxx

Describe the bug
Documentation states you can retrieve the objectID this is not the case
Related command
az ad sp show
az ad sp list
Errors
objectID  is not returned in the json
Issue script & Debug output
objectID  is not returned in the json
Expected behavior
objectId should be returned
Environment Summary
az --version
azure-cli                         2.53.1
core                              2.53.1
telemetry                          1.1.0
Extensions:
azure-devops                      0.25.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Additional context
No response

Thank you for opening this issue, we will look into it.

I am hitting this as well with azure cli 2.53.1. Basically if you create any azure resource using Azure CLI (key vault, storage account, etc.) and you immediately try to view that resource it will fail. This is going to break a lot of stuff.

I'm seeing it take up to 90 seconds for an azure cli show command to work after an azure cli create completes against the same resource. I'm testing against key vaults and storage accounts.

@tazd007, your issue is a duplicate of https://github.com/Azure/azure-cli/issues/22328.

Documentation states you can retrieve the objectID this is not the case

BTW, could you let us know which document states that?

@doherty100, it looks like you are facing a different issue. It is not related to the missing property objectId in the service principal object, but ARM not being able to retrieving the resource immediately after creation. According to my experience, this is usually caused by some caching or syncing issue in ARM.
Azure CLI is a client calling ARM API. You can add --debug argument to see the network trace. I would recommend creating a support ticket at https://azure.microsoft.com/en-us/support/create-ticket to contact service team.

Your assumption is in correct these resources are already present in fact some even years. My code uses the objectId and has worked fine, however now the objectId is not returned where previously it was


[Bug]: Xiaomi Smart Plug dosen't report the temperature to ioB anymore

Contact Details
<EMAIL_ADDRESS>What happened?
Xiaomi Smart Plug dosen't report the temperature anymore. I can't tell exactly since when/what changed but it was working previously.
What I've changed as known:

iobroker node update to v16.16.0
iobroker js update to 8.11.0
Phoscon-GW version 2.17.01 / 7/1/2022 Firmware 26720700

The temperature get shown in deCONZ but not transmitted to ioBroker:

Adapter Version
1.3.21
deConz (Phoscon) Version
2.17.01
JS-Controller Version
n/a
Node JS Version
16.16.0
NPM Version
8.11.0
Operating System
Ubuntu
Relevant log output
The os / dvice I use is Raspbian (rpi 4)

Anything else?
No response

Is this issue still there?
If yes a log in debug mode will help to figure out whats the problem.

Closing while no response.


Our contract should be able to support ERC20 without return value

Issue Type
As OMG contract is implemented in a way that does not return "true" when transfer, as we want to be able to support OMG token, our contract need to support ERC20 transferFrom function without a return value.
For details, see this: https://medium.com/coinmonks/missing-return-value-bug-at-least-130-tokens-affected-d67bf08521ca
[ ] bug report
[x] feature request

Current Behavior
In  function depositFrom(bytes _depositTx)
// Warning, check your ERC20 implementation. TransferFrom should return bool
require(ERC20(decodedTx.outputs[0].token).transferFrom(msg.sender, address(this), decodedTx.outputs[0].amount));

Expected Behavior
Does not need the transferFrom to return bool.
Suggested Fix
Perhaps use address.call directly, and in solidity 0.5, it returns success or failed + return value. We can rely on the result of "success" or "failed' directly instead.
Or the article above (in Issue Type) do provide some wrapper example code as well.
Motivation for Change
To support OMG token

Hi, this is a fair request, assuming that the affected tokens don't migrate to their fixed versions. However, note that there have been some preliminary steps taken to fix this issue for OMG. I don't know what is the status of this effort now.


Name issues

So my full deadname is Alexander but I frequently went as Alex and I find it just as much a vexation on my existence as my full deadname. Can I get the option to filter alternate versions of my deadname that I used to go by. Also add an alternative name that I also go by as well

Thanks for the suggestion! The next update is going to have nickname support as well as alternate name forms, so stay tuned


help: How can I disable ENTER key with cmp

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9
Operating system/version
Arch linux
Describe the bug
While using cmp, pressing enter key acts completion. I didn't map to it. I seem to not find a way to disable it

When I want to move the cursor to below the line pressing enter against to what I  wanted.
Before convert to lazyvim it was fine, no complete action.
My config like using super tab so there's nothing related to Enter below the code I am sure.
Steps To Reproduce

I could manage to setup super tab
but can not disable enter key
quit neovim and enter again not works
at the moment using ^j to nbsp

Expected Behavior
It's not a bug I think. I want to find a way to configure this
Repro
No response

Thank you! Solved because of you :)

@Cruising0904 How did you fix it?

I have the same question... I followed the link and added the suggested configuration to my own but I still am accepting the first autocomplete suggestion every time I hit enter and its maddening

@rkabrick What did you add to your configuration? Show the code.

return {
  {
    "hrsh7th/nvim-cmp",
    dependencies = {
      "hrsh7th/cmp-emoji",
      "windwp/nvim-autopairs",
      opts = {},
    },
    keys = {
      {
        "<C-y>",
        function()
          require("cmp").mapping.confirm({ select = true })
        end,
      },
    },
    opts = function(_, opts)
      local cmp = require("cmp")
      local cmp_autopairs = require("nvim-autopairs.completion.cmp")
      cmp.event:on("confirm_done", cmp_autopairs.on_confirm_done())
      table.insert(opts.sources, { name = "emoji" })
      -- Disable ENTER completion
      opts.mapping = cmp.mapping.preset.insert(vim.tbl_deep_extend("force", opts.mapping, {
        ["<CR>"] = vim.NIL,
      }))
    end,
  },
}

This is my configuration if it helps, it fixed the problem for me

@victorbonato You don't need the cmp.mapping.preset.insert, just the vim.tbl_deep_extend function to make it work. I don't know if you took it from some previous answer of mine that I gave in the past, but that was due to my lack of knowledge at the time. Also i don't quite understand why you define <C-y> in the keys section instead of in opts.mapping where you also disable the Enter key as well.


Bar Chart - different color for negative numbers

This is a feature request to make possible to change color for negative numbers. For example:

@szyb Can you share a sample code based on what you see and a screenshot for our reference?

@gvreddy04 I've created this chart based on demo sample (with my data) and I've made a screenshot and edited it in Paint (filled bars with red color for negative values). This feature could look like this (at least I wish). Would it be possible to setup different color for negative values of the series?


Fixes for django 2.0

Coverage decreased (-61.5%) to 28.045% when pulling ec0de6a126486164a264b8f5079ffa549914365a on IFLead:master into e7fe61b3edc6c81a2da5343a1fad7c7bdacea1cf on digi604:master.

Coverage decreased (-58.2%) to 31.373% when pulling 0a37d3ee5534c078577b6e84a0564aac03e10dad on IFLead:master into e7fe61b3edc6c81a2da5343a1fad7c7bdacea1cf on digi604:master.


Memory managment of serialization lib on javascript

Hi, I am currently trying to implement proper memory management and disposal of the CML objects in the projects I have that use this library, but I would like to understand how far I need to go to properly dispose of all the objects, do I need to call free on every object that I create using one of the constructors, or is it enough to free the parent object?, for example, when creating a transaction we need to provide all sort of objects (redeemers, datums, signatures, input, outputs etc), is it enough to free the transaction where these objects have been added to it or we must free all of the objects individually? The same question goes for objects we get from other objects, do we need to manually free all these objects returned by the getters, or is it enough to free the parent object?.

I would like to understand how far I need to go to properly dispose of all the objects, do I need to call free on every object that I create using one of the constructors, or is it enough to free the parent object?

AFAIK every wasm struct (e.g. not primitives that wasm_bindgen converts) passed to constructors are done by reference then cloned to avoid nasty issues/crashes like accessing a variable that would get moved out (and thus deallocated) after it's passed in. So you'll need to free those parameters as well if you want to avoid memory leaks.

The same question goes for objects we get from other objects, do we need to manually free all these objects returned by the getters, or is it enough to free the parent object?.

AFAIK every getter should return a cloned version to avoid nasty accessing freed memory issues, so you'll want to call free() on those too.
It's a bit of a shame that this needs to be done, but it's hard to avoid when using wasm_bindgen since rust and javascript have such fundamentally different ways of memory management (RAII vs GC) which don't play well together. And the alternative of returning references/taking in parameters by value leads to easy accidental accessing of freed memory in a way that can't be nicely checked against at compile time like when using from rust, so that's why we went with the clone-happy approach.

The ipv4 object is being cloned. so is this a forced memory leak in this particular case?

What happens in the other cases is we take it by reference, so it isn't moved into the function in rust (leading to it being freed in wasm), so we need to clone it. Here it's being moved into the function, and I believe that clone is actually not necessary for Option<T>. There shouldn't be a leak unless there's an issue with wasm_bindgen in how it implements the to/from wasm traits for Option<T> where T implements those traits.


Is it possible to make a multi-window app use less resources?

Electron uses BrowserWindow to create a new window. It means a new render process which taking up ~100MB memory will be created. An application managing multiple windows will take up lots of resources because of this. Any ideas or improvements about it? Thanks!

No, I'm afraid this is the price you have to pay for using Chromium.
If you really want to save resources for showing simple windows, you can write a native module to create native windows instead.

The math isn't completely accurate if you're just looking at Task Manager, because a lot of that memory will be shared between the processes, but @zcbenz is also right that Chromium ain't cheap

OK, I see. Thanks!


Warning: missing dependency

WARNING in ./node_modules/ng-bootstrap-form-validation/node_modules/<EMAIL_ADDRESS>5659:15-36 Critical dependency: the request of a dependency is an expression
    at ImportLazyContextDependency.getWarnings (/node_modules/webpack/lib/dependencies/ContextDependency.js:39:18)

How to fix this?

It looks like it has to do with angular 5 version and not this library, sorry.


[WIP] Use RTC for elementwise and broadcast ops

Description
As described in https://github.com/apache/incubator-mxnet/issues/18280#issuecomment-627010252, MXNet currently contains too many CUDA kernels, that affect negatively compile time, size of the resulting binary (resulting in issues like #17045 and #18205), and GPU memory consumption (as all of those kernels need to be loaded during the first GPU context creation to GPU memory).
The reason of those problems is the number of templates that need to be instantiated, especially in the case of NumPy operators which need to accept different input/output types - this results in multiple nested MSHADOW_TYPE_SWITCH macros and great increase in the number of kernels generated, most of them pretty much never used. For example, executing this command:
cuobjdump -symbols -arch sm_70 /usr/local/lib/python3.6/dist-packages/mxnet/libmxnet.so | grep GLOBAL | wc -l

on the nightly build of mxnet-cu102 from 6/25 shows 69169 kernels (the same command executed on the library built with this PR at the time of writing gives 51511 kernels).
The proposed approach is to use RTC (runtime compilation) in order to generate the needed kernels at runtime. This saves the ahead-of-time compilation time and binary size as well as the GPU memory utilization (since only the needed kernels are generated, not all combinations).
This PR uses that approach to handle elementwise and broadcast kernels (as well as their backward), which constitute a big portion of the total number of kernels in MXNet.
FYI @leezu @sxjscience @eric-haibin-lin
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[ ] Code is well-documented:
For new C++ functions in header files, their functionalities and arguments are documented.
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

RTC is now required for using CUDA in MXNet
Unary, binary, binary with scalar, binary broadcast ops and their backward counterparts were changed to use RTC

Comments

Things left to do:

[ ] Test the performance impact of cache lookup for kernel code
[ ] Convert MixedUnaryBackward functions
[ ] Update PR description with the change in GPU memory utilization and binary size resulting from this PR

After this PR the next step would be to use the same approach for reduce kernels - this PR already contains a ground work for this as reduction was needed for backward of broadcast ops, but it does not apply that path to standalone reduction ops. Grepping for reduce_kernel in the symbols visible in libmxnet.so after application of this PR:

cuobjdump -symbols -arch sm_70 /usr/local/lib/python3.6/dist-packages/mxnet/libmxnet.so | grep GLOBAL | grep reduce_kernel | wc -l

gives 12057 entries. This would also help with reducing the amount of code duplication that this PR introduces (to maintain both RTC and non-RTC paths).

Thank you @ptrendx! As this makes nvrtc feature mandatory, it may be necessary to first/prior to next release also fix https://github.com/apache/incubator-mxnet/issues/17858? It seems that there are a number of users that try to open GPU builds on machines without libcuda.so and this is broken since 1.6 due to https://github.com/apache/incubator-mxnet/issues/17858 (but currently there is the workaround of disabling nvrtc)

Yeah, we will need to sort it out before the release - I actually thought that if we manage to get everything via RTC (which seems daunting though), we could actually dynamically load both libcuda and libnvrtc and have a single build that supports everything instead of mxnet-cu*. That said, RTC for everything is a big task and I would definitely need help from community if we were to pull it off.

Also, I thought that you made the compilation use C++17 (so I use if constexpr), but now I see that the CUDA part is compiled with C++14 (and fails). What is the reason of that?

Also, I thought that you made the compilation use C++17 (so I use if constexpr), but now I see that the CUDA part is compiled with C++14 (and fails). What is the reason of that?

The reason is that CUDA does not support C++17 prior to CUDA11. We can consider requiring CUDA11 for MXNet 2

Yeah, I wasn't aware of that. I decided to change the if constexpr to #ifdefs for now as the gpu portion is still compiled with nvcc.
Another thing - it seems that the docker for jetson does not include NVRTC, who can change that?

Another thing - it seems that the docker for jetson does not include NVRTC, who can change that?

You can just edit the Dockerfile. But there might be a problem that NVidia fails to publish a NVRTC cross-compilation package. If so, you'll first need to get it published internally. (That's the case for TensorRT. But hopefully NVRTC is already available)

Hi @ChaiBapchya could you tell me whether there is any difference in hw/sw of centos-gpu runners compared to unix-gpu runners? I see some failures on centos-gpu that do not happen on unix-gpu.

Based on the existing CI infra setup, both centos-gpu & unix-gpu run on the same AMI
Same AMI translates essentially to same HW/SW.
However, after the instance is created, it runs the CI on a docker file. That dockerfile setup is different from unix & centos
Centos BUILD: https://github.com/apache/incubator-mxnet/blob/master/ci/docker/Dockerfile.build.centos7
Centos Test: https://github.com/apache/incubator-mxnet/blob/master/ci/docker/Dockerfile.publish.test.centos7
The variables used in these dockerfiles are defined in https://github.com/apache/incubator-mxnet/blob/master/ci/docker/docker-compose.yml
For e.g.
In your case: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fcentos-gpu/detail/PR-18622/9/pipeline
Fails at
ci/build.py --docker-registry mxnetci --nvidiadocker --platform centos7_gpu_cu92 --docker-build-retries 3 --shm-size 500m /work/runtime_functions.sh unittest_centos7_gpu

Thus the platform centos7_gpu_cu92 defined here
https://github.com/apache/incubator-mxnet/blob/master/ci/docker/docker-compose.yml#L44-L53

@mxnet-bot run ci [windows-gpu, unix-gpu, miscellaneous, website, centos-gpu, sanity, clang]

@ChaiBapchya The Jetson CI pipeline fails with not being able to find NVRTC - I confirmed it is part of jetpack, so I guess it is not included in the package of libs you have in S3. Can you update it? (And yes, I'm aware of issue #18637).

@ptrendx these are the files available in the S3 bucket. You may need to edit the Dockerfile to install one of the debs:
% aws s3 ls --recursive s3://mxnet-ci-prod-private-slave-data/nvidia                                                                                6s ~
2020-04-11 02:46:49          0 nvidia/
2020-04-11 02:47:05          0 nvidia/sdkm_downloads/
2020-04-11 03:07:04  237414931 nvidia/sdkm_downloads/Jetson-210_Linux_R32.3.1_aarch64.tbz2
2020-04-11 03:03:33  288481398 nvidia/sdkm_downloads/NVIDIA_Nsight_Graphics_L4T_2019.5.19322.deb
2020-04-11 03:24:00    5350765 nvidia/sdkm_downloads/NVIDIA_VisionWorks_References.zip
2020-04-11 03:17:26  113581742 nvidia/sdkm_downloads/NsightSystems-linux-public-2<IP_ADDRESS>-3ffb807.deb
2020-04-11 03:24:08    1022926 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-dev.deb
2020-04-11 03:23:59    9920774 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-libs.deb
2020-04-11 03:24:13      14240 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-licenses.deb
2020-04-11 03:24:07    2350538 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-python.deb
2020-04-11 03:24:11     192038 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-samples.deb
2020-04-11 03:24:09    1027754 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-x86_64-dev.deb
2020-04-11 03:21:58   45701978 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-x86_64-libs.deb
2020-04-11 03:24:12      18306 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-x86_64-licenses.deb
2020-04-11 03:24:03    2576742 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-x86_64-python.deb
2020-04-11 03:24:11     192030 nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-x86_64-samples.deb
2020-04-11 03:24:11     143245 nvidia/sdkm_downloads/SDKM_logs_JetPack_4.3_Linux_for_Jetson_TX1_2020-04-10_17-43-23.zip
2020-04-11 02:51:29<PHONE_NUMBER> nvidia/sdkm_downloads/Tegra_Linux_Sample-Root-Filesystem_R32.3.1_aarch64.tbz2
2020-04-11 02:51:29  394475774 nvidia/sdkm_downloads/cuda-repo-cross-aarch64-10-0-local-10.0.326_1.0-1_all.deb
2020-04-11 02:51:29<PHONE_NUMBER> nvidia/sdkm_downloads/cuda-repo-l4t-10-0-local-10.0.326_1.0-1_arm64.deb
2020-04-11 02:51:29<PHONE_NUMBER> nvidia/sdkm_downloads/cuda-repo-ubuntu1804-10-0-local-10.0.326-410.108_1.0-1_amd64.deb
2020-04-11 03:22:38   25538902 nvidia/sdkm_downloads/devtools_docs.zip
2020-04-11 03:24:13      16108 nvidia/sdkm_downloads/graphsurgeon-tf_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:13:51  161324708 nvidia/sdkm_downloads/libcudnn7-dev_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:23:55    6627420 nvidia/sdkm_downloads/libcudnn7-doc_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:13:18  181721612 nvidia/sdkm_downloads/libcudnn7_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:24:13      12596 nvidia/sdkm_downloads/libnvidia-container-tools_0.9.0_beta.1_arm64.deb
2020-04-11 03:24:12      42744 nvidia/sdkm_downloads/libnvidia-container0_0.9.0_beta.1_arm64.deb
2020-04-11 03:24:12      69900 nvidia/sdkm_downloads/libnvinfer-bin_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:20:36   57300292 nvidia/sdkm_downloads/libnvinfer-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:02    4460940 nvidia/sdkm_downloads/libnvinfer-doc_6.0.1-1+cuda10.0_all.deb
2020-04-11 03:24:08    1546362 nvidia/sdkm_downloads/libnvinfer-plugin-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:06    1489314 nvidia/sdkm_downloads/libnvinfer-plugin6_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 02:51:29  451737338 nvidia/sdkm_downloads/libnvinfer-samples_6.0.1-1+cuda10.0_all.deb
2020-04-11 03:21:10   56443400 nvidia/sdkm_downloads/libnvinfer6_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:11     164522 nvidia/sdkm_downloads/libnvonnxparsers-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:09     578042 nvidia/sdkm_downloads/libnvonnxparsers6_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:10     538398 nvidia/sdkm_downloads/libnvparsers-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:08     707550 nvidia/sdkm_downloads/libnvparsers6_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:19:50   66561472 nvidia/sdkm_downloads/libvisionworks-repo_<IP_ADDRESS>0n_amd64.deb
2020-04-11 03:20:07   60780704 nvidia/sdkm_downloads/libvisionworks-repo_<IP_ADDRESS>0n_arm64.deb
2020-04-11 03:22:59   20597586 nvidia/sdkm_downloads/libvisionworks-sfm-repo_0.90.4_amd64.deb
2020-04-11 03:23:08   20216850 nvidia/sdkm_downloads/libvisionworks-sfm-repo_0.90.4_arm64.deb
2020-04-11 03:23:29   13113238 nvidia/sdkm_downloads/libvisionworks-tracking-repo_0.88.2_amd64.deb
2020-04-11 03:23:56   13107966 nvidia/sdkm_downloads/libvisionworks-tracking-repo_0.88.2_arm64.deb
2020-04-11 03:24:13      14842 nvidia/sdkm_downloads/nvidia-container-csv-cuda_10.0.326-1_arm64.deb
2020-04-11 03:24:14       6176 nvidia/sdkm_downloads/nvidia-container-csv-cudnn_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:24:13      13686 nvidia/sdkm_downloads/nvidia-container-csv-tensorrt_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:24:12      29796 nvidia/sdkm_downloads/nvidia-container-csv-visionworks_<IP_ADDRESS>0n_arm64.deb
2020-04-11 03:24:09     534888 nvidia/sdkm_downloads/nvidia-container-runtime_3.1.0-1_arm64.deb
2020-04-11 03:24:10     501768 nvidia/sdkm_downloads/nvidia-container-toolkit_1.0.1-1_arm64.deb
2020-04-11 03:24:15       2940 nvidia/sdkm_downloads/nvidia-docker2_2.2.0-1_all.deb
2020-04-11 03:18:20   70425180 nvidia/sdkm_downloads/nvidia-l4t-jetson-multimedia-api_32.3.1-20191209225816_arm64.deb
2020-04-11 03:24:14       3632 nvidia/sdkm_downloads/python-libnvinfer-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:10     363394 nvidia/sdkm_downloads/python-libnvinfer_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:14       3648 nvidia/sdkm_downloads/python3-libnvinfer-dev_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:10     360882 nvidia/sdkm_downloads/python3-libnvinfer_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:24:11     182539 nvidia/sdkm_downloads/sdkml3_jetpack_l4t_43_ga.json
2020-04-11 03:24:14       3652 nvidia/sdkm_downloads/tensorrt_<IP_ADDRESS>-1+cuda10.0_arm64.deb
2020-04-11 03:24:12      37802 nvidia/sdkm_downloads/uff-converter-tf_6.0.1-1+cuda10.0_arm64.deb
2020-04-11 03:23:54    7959372 nvidia/sdkm_downloads/vpi-dev-0.1.0-r2-l4t-aarch64.deb
2020-04-11 03:22:11   26794560 nvidia/sdkm_downloads/vpi-lib-0.1.0-r2-l4t-aarch64.deb
2020-04-11 03:23:58    4491602 nvidia/sdkm_downloads/vpi-samples-0.1.0-r2-l4t-aarch64.deb

@leezu Thanks for listing the files - I am now looking into the contents of the right cross compilation package. I think you are right that everything should already be there and it is possibly just a package that was not installed in the Dockerfile itself, so I should be able to do this in the PR :-).

I looked at the performance impact of RTC and it adds ~2us of CPU time to the launch, mostly due to string manipulation.

@mxnet-bot run ci [windows-gpu]

@eric-haibin-lin Yes. A lot of the code (compilation related as well as the function definitions) was moved around to be able to be reused. Support for NumPy-style mixed types were also added.

@mxnet-bot run ci [windows-gpu]
Flaky test test_gluon_dirichlet, tracked in #18809

@eric-haibin-lin Yes. The overhead comes from preparing a string with kernel options (like the datatypes) and searching for the kernel function in cache. CUDA graph caches the resulting function so the lookup does not occur anymore.
That said, this overhead is lower than the overhead of cudaLaunchKernel itself and is barely noticeable - I tried it with a worst case scenario of fully hybridized model that was adding tensors with single element (to be 100% CPU limited) and got ~10% slowdown. More realistic workload with kernels taking longer than a few us would not show any difference. The same CPU limited test with non-hybridized model did not show noticeable slowdown (overheads of imperative mode are way higher than this).

@mxnet-bot run ci [unix-cpu]


Accessing chartInstance without refs

Hi,
is there any way to get into chartInstance without references?
For example as in vue-chartjs:

Hi no you can't access chartInstance like that because it's not the same behaviour as vue-chartjs. They need you to declare a new component for each Chart whereas here you juste have to import the pre-made component.
So like this:
<template>
  <DoughnutChart ref="doughtnutRef" />
</template>

<script>
import { DoughnutChart } from 'vue-chart-3';

export default defineComponent({
  name: 'Home',
  components: { DoughnutChart },
  setup() {
    const doughtnutRef = ref();
    // ....
    onMounted(() => {
      doughtnutRef.value.chartInstance.toBase64Image();
    });

    return { doughtnutRef };
  },
});
</script>

Hi no you can't access chartInstance like that because it's not the same behaviour as vue-chartjs. They need you to declare a new component for each Chart whereas here you juste have to import the pre-made component.
So like this:
<template>
  <DoughnutChart ref="doughtnutRef" />
</template>

<script>
import { DoughnutChart } from 'vue-chart-3';

export default defineComponent({
  name: 'Home',
  components: { DoughnutChart },
  setup() {
    const doughtnutRef = ref();
    // ....
    onMounted(() => {
      doughtnutRef.value.chartInstance.toBase64Image();
    });

    return { doughtnutRef };
  },
});
</script>

On 0.3.2 version refs value was undefined.
After upgrading to the newest version (0.3.7), it seems that this version is not working at all?

@Krulaks upgraded to the newest version 0.4.7, there were breaking changes and fixes to get it working on both Vue 2 & 3

On 0.4.7,
using this code:
<template>
  <LineChart ref="lineRef" :chartData="chartData" :options="computeOptions" :styles="chartStyle" />
</template>

<script>
import { defineComponent, onMounted, ref } from "@vue/composition-api";
import { LineChart } from "vue-chart-3";
import "chartjs-adapter-moment";

export default defineComponent({
  components: { LineChart },
  props: ["chartdata", "options", "parsestyles"],
  setup() {
    const lineRef = ref();

    onMounted(() => {
      console.log(lineRef.value);
    })
    return lineRef;
  },

It returns:

Nevermind, I forgot about adding { } to return


refactor:  split common into multiple crates

Signed-off-by: Gustavo Inacio<EMAIL_ADDRESS>Gustavo Inacio<EMAIL_ADDRESS>

The code makes total sense. Could you just amend a the last commit message to match with conventional commits?
d9686c6b12f9aa0ae0f817e803285825faf95fdc is a refactor

done


CGAL can;t be used after exporting

After installing CGAL I exported it, so that I can use it in appveyor. I downloaded my zip file, extracted and try to build after setting the DCMAKE_TOOLCHAIN..  file as the vcpkg.cmake file. But when trying to build, even though all libraries are found, CGAL vomits this error.

Line 47 in the CMakeLists.txt file is include( ${CGAL_USE_FILE} ) but CGAL_USE_FILE is pointing to the file in my home computer(D:/Dev/vcpkg/packages/cgal_x64-windows/lib/CGAL/UseCGAL.cmake), which appveyor can't obviously find.
This is what the CGAL section looks like.
# CGAL config
find_package(CGAL REQUIRED)
include( ${CGAL_USE_FILE} )
include( CGAL_CreateSingleSourceCGALProgram )
include_directories ("${CGAL_ROOT}/include/CGAL")
include_directories (BEFORE "../../include")

I can successfully build my project in my home computer by the way.

I tried to build my project using the exported zip file from my laptop as well, I get the same error.

CGAL's CMake is very non standard. I will try to figure out whether this should be fixed from the upstream or vcpkg patch. It looks to me that some of the cmake config files that is in the install folder is referencing something in the packages folder.
Can you let me know which file exactly has the CGAL_USE_FILE that points to the wrong location? CMakeLists.txt looks like something from the buildtree folder and not something from the install folder.

I didn't understand your question, do you want to know which file is CGAL_USE_FILE pointing to ?

Which file has this line include( ${CGAL_USE_FILE} )?

My CMakeLists.txt file.

That way of using it is outdated, try
cmake_minimum_required(VERSION 3.9)

project(Example)

set(PROJECT_SRCS ${PROJECT_SOURCE_DIR}/main.cpp)

find_package( CGAL REQUIRED )

add_executable(${PROJECT_NAME} ${PROJECT_SRCS})

target_link_libraries(${PROJECT_NAME} CGAL::CGAL)

YUSSS !, it works now. Thank you for giving the correct config.

@jasjuang ....yeahhhhhh....but this config won't work for linux

works on my linux and my main devs happens on linux

Look at this log https://travis-ci.org/justinjk007/Pentagonal-tiling

Where is your cgal from? Must be an old version. Try building current master with my PR https://github.com/CGAL/cgal/pull/2700

I installed this libcgal-dev package, not sure about its version. I update and come back.

That's way too old. If you don't want to build from master at least build with the latest release like vcpkg.

Yeah...I realised it is version 4.2 I will update that and the problem should go away, thanks for pointing me in the right direction.

Yep installing latest version from source and rebuilding gives me no more errors phewww!

Hi, this issue is still present, is there any long term fix that can be added, other than manually run a fixup script after unpacking the exported package?
Thanks

@studiofuga commented on Dec 14, 2018, 10:01 AM GMT+1:

Hi, this issue is still present, is there any long term fix that can be added, other than manually run a fixup script after unpacking the exported package?
Thanks

I think the recent PR https://github.com/CGAL/cgal/pull/3922 might have fixed the issue.


Unify platform related code

All platform(x86, arm, etc) related code, like distance calculation and prefetch, need to be centralized in Knowhere's utils under the hook mechanism.

using the hook mechanism for prefetching is a horrible idea


latest/admin-manual/manual.html#installation page not found

http://cloudera.github.io/hue/latest/admin-manual/manual.html#installation

From the README.md I guess, link is now fixed: http://cloudera.github.io/hue/latest/administrator/installation/
Thanks!

From the README.md I guess, link is now fixed: http://cloudera.github.io/hue/latest/administrator/installation/
Thanks!

Thanks!


Migrate UnivariateFinite (for categorical distributions) out to new package

In line with #416, I propose we move UnivariateFinite out to a new package called CategoricalDistributions.jl.
If this were okay with the current host of MLJBase.jl (I need to check this @vollmersj) it might make sense for this package to live at JuliaData (host of CategoricalArrays.jl) or JuliaStats (host of Distrtibutions.jl). I wonder what curators of those organisations think of that idea?
@nalimilan @bkamins @andreasnoack @devmotion @matbesancon
Recall that UnivariateFinite consists of the following:

A composite type UnivariateFinite{S,V,R,P<:Real} for encoding the probability distribution associated with a finite labelled set of points, as opposed to the distribution Categorical from Distributions.jl, whose sample space is always a collection of integers. The sample space of a UnivariateFinite instance is a CategoricalPool object from CategoricalArrays.jl.

Implementation of relevant parts of the Distributions.jl API, including rand, pdf, logpdf support, params, mode, and fit (which fits to a CatgoricalVector).

A wrapper UnivariateFiniteArray for arrays of such objects (sharing a common sample space / pool). This type, implementing the AbstractArray API, is optimised for fast indexing, and for broadcasting of pdf, and logpdf (which turned out to be essential in our applications to machine learning).

A fairly elaborate constructor for UnivariateFiniteArray objects from matrices of probabilities. See this docstring

Technical note. I'm hoping this migration should be fairly painless but there is one issue to be aware of: Currently the UnivariateFinite constructor stub lives in MLJModelInterface but the type and all real functionality lives in MLJBase (which depends on MLJModelInterface). The reason for this was to keep MLJModelInterface (the sole dependency of third party packages inplementing MLJ's model API) super lightweight. So this needs sorting out.

cc @OkonSamuel

cc @OkonSamuel

@cscherrer might also be interested in this.

@cscherrer might also be interested in this.

* as opposed to the distribution `Categorical` from Distributions.jl, whose sample space is always a collection of integers.

While this is correct for Categorical, the support of the more general DiscreteNonParametric, of which Categorical is a special case, can be an arbitrary finite set.

* as opposed to the distribution `Categorical` from Distributions.jl, whose sample space is always a collection of integers.

While this is correct for Categorical, the support of the more general DiscreteNonParametric, of which Categorical is a special case, can be an arbitrary finite set.

Thanks @DilumAluthge . I guess it will get a little complicated since we're moving away from Distributions.jl, but I think we'll still be able to import this and wrap it as a Measure

Thanks @DilumAluthge . I guess it will get a little complicated since we're moving away from Distributions.jl, but I think we'll still be able to import this and wrap it as a Measure

I guess it will get a little complicated since we're moving away from Distributions.jl,

Yes, Distributions is a hefty dependency. The new package could probable avoid Distributions as dependency and just implement the "functional" side of the Distributions API. Ie, drop the sub typing UnivariateFinite{...} <: Distribution or whatever.

I guess it will get a little complicated since we're moving away from Distributions.jl,

Yes, Distributions is a hefty dependency. The new package could probable avoid Distributions as dependency and just implement the "functional" side of the Distributions API. Ie, drop the sub typing UnivariateFinite{...} <: Distribution or whatever.

I guess it would be easier if Distributions.jl has a separate package containing basic functions which we can extend

I guess it would be easier if Distributions.jl has a separate package containing basic functions which we can extend

This was suggested and discussed in https://github.com/JuliaStats/Distributions.jl/issues/1139 but it seems it was not supported by the maintainers.

This was suggested and discussed in https://github.com/JuliaStats/Distributions.jl/issues/1139 but it seems it was not supported by the maintainers.

Yes, Distributions is a hefty dependency.

Yes, but it's so widely used I don't see much getting around it. We actually have it as a dependency for MeasureTheory anyway, and use it for some of the sampling routines.
I'd love if this can be made nicely compatible with MeasureTheory, if it's not already. Here are some guidelines for that:

Structs themselves should not constrain types beyond what's necessary. For example, <: Real constraints impose a boundary for symbolic analysis that takes special care to get around.
Any constructor with bounds checking should call to another function without it. The keyword-argument approach in Distributions.jl is awkward because it changes from one distribution to the next.
I'd love if there's a way to call this with different parameterizations. For example, log-weights or as input to the UnitVector transform from TransformVariables. Or the one from Bijectors, though honestly that one still confuses me since it's not bijective. We have a nice way to write parameterized measures in MeasureTheory.
If possible, any normalization constants should be computed separately

These are just off the top of my head, and partly for my notes as well.

Yes, Distributions is a hefty dependency.

Yes, but it's so widely used I don't see much getting around it. We actually have it as a dependency for MeasureTheory anyway, and use it for some of the sampling routines.
I'd love if this can be made nicely compatible with MeasureTheory, if it's not already. Here are some guidelines for that:

Structs themselves should not constrain types beyond what's necessary. For example, <: Real constraints impose a boundary for symbolic analysis that takes special care to get around.
Any constructor with bounds checking should call to another function without it. The keyword-argument approach in Distributions.jl is awkward because it changes from one distribution to the next.
I'd love if there's a way to call this with different parameterizations. For example, log-weights or as input to the UnitVector transform from TransformVariables. Or the one from Bijectors, though honestly that one still confuses me since it's not bijective. We have a nice way to write parameterized measures in MeasureTheory.
If possible, any normalization constants should be computed separately

These are just off the top of my head, and partly for my notes as well.

CategoricalDistributions.jl really sounds like a narrow scope for a package. And IIUC it would define a lot of the Distributions.jl API (like pdf and such), and Distributions would have to depend on it (otherwise names would conflict)? At that point, we have to admit it would be very close to what a potential DistributionsBase package would be.
Why can't UnivariateFinite live in Distributions? Is it because you don't want to depend on Rmath?

CategoricalDistributions.jl really sounds like a narrow scope for a package. And IIUC it would define a lot of the Distributions.jl API (like pdf and such), and Distributions would have to depend on it (otherwise names would conflict)? At that point, we have to admit it would be very close to what a potential DistributionsBase package would be.
Why can't UnivariateFinite live in Distributions? Is it because you don't want to depend on Rmath?

I think this issue should be taken a bit broader than categorical distributions only, but my overall observation is that Distributions has become very hard to maintain because it is a central utility with few and rarely available maintainers. Most people just drop by for an issue or PR but don't want (understandably) to get involved in its maintenance, and many former maintainers are not involved anymore.
I agree with @nalimilan that splitting a package just for categorical distributions would be too fragmenting, but splitting a DistributionsBase, and possibly using this opportunity to clean the house, should be considered

I think this issue should be taken a bit broader than categorical distributions only, but my overall observation is that Distributions has become very hard to maintain because it is a central utility with few and rarely available maintainers. Most people just drop by for an issue or PR but don't want (understandably) to get involved in its maintenance, and many former maintainers are not involved anymore.
I agree with @nalimilan that splitting a package just for categorical distributions would be too fragmenting, but splitting a DistributionsBase, and possibly using this opportunity to clean the house, should be considered

Why can't UnivariateFinite live in Distributions?

There were conversations but resistance. They said "you can just have Distributions as a dependency and overload..." I think the main objection was to include anything with a sample space that was not Array{Float64,N} or Array{Int,N}.

Why can't UnivariateFinite live in Distributions?

There were conversations but resistance. They said "you can just have Distributions as a dependency and overload..." I think the main objection was to include anything with a sample space that was not Array{Float64,N} or Array{Int,N}.

include anything with a sample space that was not Array{Float64,N} or Array{Int,N}

(or Float64 / Int themselves). But overall I agree that this has been one of the biggest blocking points in Distributions, because some parts of the code base were non-trivial to adapt to something more generic. That being said, the type parameters of distributions can be extended (VariateForm and ValueSupport)

include anything with a sample space that was not Array{Float64,N} or Array{Int,N}

(or Float64 / Int themselves). But overall I agree that this has been one of the biggest blocking points in Distributions, because some parts of the code base were non-trivial to adapt to something more generic. That being said, the type parameters of distributions can be extended (VariateForm and ValueSupport)

but my overall observation is that Distributions has become very hard to maintain because it is a central utility with few and rarely available maintainers. Most people just drop by for an issue or PR but don't want (understandably) to get involved in its maintenance, and many former maintainers are not involved anymore.

This is also my impression and, if true, a real issue for Julia, in my opinion. The concept of a distribution extends far beyond what is in Distributions.jl (objects sampled using Monte-Carlo-Markov-Chain, pdfs on manifolds, priors for tree-like parameter spaces, etc). It may not make sense to add to what is there, but without a base API package it's very messy to extend.

but my overall observation is that Distributions has become very hard to maintain because it is a central utility with few and rarely available maintainers. Most people just drop by for an issue or PR but don't want (understandably) to get involved in its maintenance, and many former maintainers are not involved anymore.

This is also my impression and, if true, a real issue for Julia, in my opinion. The concept of a distribution extends far beyond what is in Distributions.jl (objects sampled using Monte-Carlo-Markov-Chain, pdfs on manifolds, priors for tree-like parameter spaces, etc). It may not make sense to add to what is there, but without a base API package it's very messy to extend.

That being said, the type parameters of distributions can be extended (VariateForm and ValueSupport)

Yes, that is what we currently do in MLJ. But it means having Distributions.jl as a dependency in places we'd rather not. We had to perform some acrobatics to create our light-weight MLJModelInterface, partly for this reason.

That being said, the type parameters of distributions can be extended (VariateForm and ValueSupport)

Yes, that is what we currently do in MLJ. But it means having Distributions.jl as a dependency in places we'd rather not. We had to perform some acrobatics to create our light-weight MLJModelInterface, partly for this reason.

Thanks to contributors to this discussion.
Update: UnivariateFinite is now generalized, in the sense that is no longer assumed or enforced that probabilities add to one. Ie, one can use it to represent arbitrary measures over a "labelled" finite set. This would appear to make it more useful re the MeasureTheory project (see above  https://github.com/alan-turing-institute/MLJBase.jl/issues/504#issuecomment-764686174)
I think I should like to proceed with moving this functionality to new package, dependent on Distributions for pdf, logpdf, support, mode , and params with the great hope that sometime in the future these methods will be moved to StatsBase or a new DistributionsBase.
Some technical details for myself or whoever takes this on. Currently the super-lightweight MLJModelInterface defines a method only, UnivariateFinite. This method is needed for 3rd party packages implementing the MLJ api for classifiers, for example. However, the method has only dummy behaviour, unless MLJBase is also in scope. MLJBase adds the true functionality, ie, makes it a bone-fide constructor, now that the type UnivariateConstructor actually exists. This is handled with  something resembling trait-dispatch where the trait is "is MLJBase loaded?". These gymnastics were necessary to avoid having Distributions and CategoricalArrays as a dependencies of MLJModelInterface.jl. See here and here for details.
Moving forward, no changes are made to MLJModelInterface. The new package will not depend on MLJ in any way, and in particular does not extend the constructor from MLJModelInterface. Rather:

The new package, FiniteMeasures.jl, say, defines both a new type FiniteMeasure (and FiniteMeasureArray) and all constructors ab initio, using the code from MLJBase with renaming UnivariateFinite -> FiniteMeasure. The only change is we are not extending some other constructor, just making a new one.
MLJBase, which imports FiniteMeasures.jl, continues to extend the UnivariateFinite constructor from MLJModelInterface; however the added functionality is just to call the FiniteMeasures.FiniteMeasure constructor, returning a FiniteMeasure object. MLJBase will now re-export both MLJModelInterface.UnivariateFinite and FiniteMeasures.FiniteMeasure. A deprecation warning is added to  the "MLJBase" version of the method (the version dispatching on FullInterface) as we intend MLJ users to move to FiniteMeasure, but deprecation itself means only that we stop exporting UnivariateFinite; we want to keep UnivariateFinite in MLJModelInterface, as this would be too painful to change now, in my opinion.

In principle the renaming is not necessary, but it simplifies the explanation and makes sense given the recent generalization.


GitHub release tags are being mutated by CI Bot (?)

Hmm, our CI just notified me a commit has been pushed to master is tagged as: 270.5.0
author: CI Bot
author_date: 2019-09-10 00:14:20 +0000
commit: 84287681c21b12ad15292ad5e8b4d8944144f32f
message: Bumping bosh to version 270.5.0
tags: 270.5.0

However our history in Concourse shows me that a different commit was tagged as 270.5.0 a few weeks ago:
author: CI Bot
author_date: 2019-08-31 00:58:40 +0000
commit: 4c3cd95759fdacd96df8dcbaec572373541fa133
message: Bumping bosh to version 270.5.0
tags: 270.5.0

Is this intentional? I was of the impression that tags (unlike branches) should be regarded as roughly immutable. I'd have thought that re-tagging a different commit to an existing tag in a public project would be roughly akin for force-pushing master, ie not good form.
In any case, this is making it very difficult for us to reason which is the legimate or correct release, and I'm hoping this is a bug in your CI Bot. I don't I've ever seen any other project do this...
(btw, I'm very happy to see this repo now actually get releases and tagging!)
Hmm - this commit looks like it might be the culprit:
https://github.com/cloudfoundry/bosh-deployment/commit/bd2abbef088284377e21a397076573db503c9b9a

An impact of this is that we are unable to use the Concourse git-resource to mirror this repository locally, we receive errors such as:
Identity added: /tmp/git-resource-private-key (/tmp/git-resource-private-key)
To ssh://xxxxxxxx/yyyyy/bosh-deployment.git
   fca68da..7fad441  HEAD -> master
 * [new tag]         270.6.0 -> 270.6.0
 ! [rejected]        270.5.0 -> 270.5.0 (already exists)
error: failed to push some refs to<EMAIL_ADDRESS>hint: Updates were rejected because the tag already exists in the remote.

I realise that we could likely set force attribute to true - however that isn't a good workaround.

After the team talked it over, bosh-deployment is only supposed to be consumed from master. We do not want to support people consuming tagged "releases". The tags were only added for internal consumption in a ci pipeline, which we don't really need. We are no longer tagging bosh-deployment at all, mutating tags should no longer be an issue.


circular double linked list

Not accepting CPP/C DSA codes
Alternative ->
1)Create a page using HTML & CSS Add DSA problem statement and solution in that
2)You can contribute in python and java OR
Ask for an issue assign
3)Contribute to Web Project


Add more recent rubies for travis

These pass the test. So let's add them to the test suite.

Hmm? Travis, rvm install problem for 2.3
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3 --install --binary --fuzzy" failed and exited with 2 during .

Coverage remained the same at 94.203% when pulling 911996ff048546895cdea55dfe30d3d93fa24753 on philoserf:master into d5eef8f3081f00d10a70595dd8bcce0d4049f104 on rafalchmiel:master.

Coverage remained the same at 94.203% when pulling c875b6ae0467f64e86110278c30d25373a2312da on philoserf:master into d5eef8f3081f00d10a70595dd8bcce0d4049f104 on rafalchmiel:master.

Coverage remained the same at 94.203% when pulling 2c0d0de97f92fde0061074ef9791a27a5ce32eac on philoserf:master into d5eef8f3081f00d10a70595dd8bcce0d4049f104 on rafalchmiel:master.

Thanks a lot.


CI is failing for node 12

https://travis-ci.org/db-migrate/node-db-migrate/builds/555795572
npm install fails for node 12. It seems that update sqlite3 to latest fixes the problem.

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

This is a common problem on upgrades, indeed an upgrade on the sqlite driver will fix this.


Mark configuration fields optional to make lua lsp's diagnostics happy

Problem
A user of the library receives warnings from LUA LSP's diagnostic, about some configuration parameters are missing, even tho they are not strictly required

Solution
Annotate configuration fields as optional

Thanks @epwalsh for the pointer. Let me do another take on this change.


Suggestion: StaticTextField Component

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

There would be a component to display static text data in an app.
Current Behavior

There exists no component to display static text data in an app.
Steps to Reproduce (for bugs)

N/A
Context

In several apps I've developed over the years, I've needed a way to display static text data on a page. Here is an example from Bootstrap: http://getbootstrap.com/docs/3.3/css/#forms-controls-static
I've gone ahead and created a very basic, preliminary component (code below). Here are some screenshots of this component, rendered:

It might also make sense to provide an option enabling the choice between either vertical (with label on top) or horizontal (with label to the side) presentation.
Your Environment

Tech
Version

Material-UI
v1.0.0-beta.35

React
16

browser

etc

Code
'use strict';

import React from 'react';
import PropTypes from 'prop-types';
import {withStyles} from 'material-ui/styles';
import Typography from 'material-ui/Typography';

const styles = (theme) => ({
    root: {
        display: 'inline-flex',
        flexDirection: 'column',
        minWidth: 166,
        marginTop: theme.spacing.unit,
        marginBottom: theme.spacing.unit,
        marginLeft: 0,
        marginRight: theme.spacing.unit * 2
    },
    label: {
        fontWeight: 600,
        lineHeight: '16px'
    },
    text: {
        marginTop: theme.spacing.unit,
        lineHeight: '16px',
        width: '100%',
        padding: '6px 0 7px'
    }
});

const StaticTextField = (props) => {
    const {classes} = props;

    return (
        <Typography component="div" className={classes.root}>
            {props.label}

{props.value}

        </Typography>
    );
};

StaticTextField.propTypes = {
    classes: PropTypes.object.isRequired,
    theme: PropTypes.object.isRequired,
    label: PropTypes.string,
    value: PropTypes.oneOfType([
        PropTypes.string,
        PropTypes.array
    ])
};

export default withStyles(styles, {withTheme: true})(StaticTextField);

And some usage:
<StaticTextField label="Date" value={dateHelper.format(order.createdAt)} />

<StaticTextField label="Address" value={[
    <Typography component="div" key="address1">123 Main St.</Typography>,
    <Typography component="div" key="address2">Austin, TX 78727</Typography>,
    <Typography component="div" key="country">United States</Typography>
]} />

@chaddjohnson Thanks for reaching us out. We don't "really" have the notion of form control like Bootstrap has. As far as I know, there is nothing close to Bootstrap from control in the Material specification.
The Material way to solve your problem is to use a div alongside the FormControl and FormLabel.
I would suggest you publish your component as a third party library :).

@oliviertassinari Nice, using FormControl and FormLabel works well:
'use strict';

import React from 'react';
import PropTypes from 'prop-types';
import {withStyles} from 'material-ui/styles';
import {FormControl, FormLabel} from 'material-ui/Form';
import Typography from 'material-ui/Typography';

const styles = (theme) => ({
    root: {
        minWidth: 166,
        marginTop: theme.spacing.unit,
        marginBottom: theme.spacing.unit,
        marginLeft: 0,
        marginRight: theme.spacing.unit * 2
    },
    content: {
        marginTop: theme.spacing.unit,
        padding: '6px 0 7px'
    }
});

const StaticTextField = (props) => {
    const {classes} = props;

    return (
        <FormControl className={classes.root}>
            <FormLabel>{props.label}</FormLabel>

{props.value}

        </FormControl>
    );
};

StaticTextField.propTypes = {
    classes: PropTypes.object.isRequired,
    theme: PropTypes.object.isRequired,
    label: PropTypes.string,
    value: PropTypes.oneOfType([
        PropTypes.string,
        PropTypes.array
    ])
};

export default withStyles(styles, {withTheme: true})(StaticTextField);

If anyone posts here and requests this, I'll see about publishing this as a third-party component.


QBO - Changing to other option does not save for the first time

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.37-0
Reproducible in staging?: Y
Reproducible in production?: N
Found when validation PR: https://github.com/Expensify/App/pull/48277
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Prerequisite: Your workspace needs to connect with QBO.

Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/e1e4a21c-cba3-47ac-841b-2c83e7495d4f

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @aldo-expensify

I added 2 labels because I am not sure what I need to use. The behavior with Use Staging Server disabled is different when running in production and staging with Use Staging Server enabled. Check my video please
https://github.com/user-attachments/assets/de976eb3-e323-4eb3-b80e-3045c3dbc866

Potentially related to https://github.com/Expensify/App/pull/48277

Hm yeah it's on prod... And I just double checked the new code from your PR, it's effectively no different from the old code. @aldo-expensify do you think this might be the sync issue we're dealing with separately? Like the initial sync hasn't yet completed?

yeah i think this is the sync issue - I just tried on my own staging account, the first time i switched the setting (right after connecting) it switched back, but then i just tried it again after waiting a few seconds, and it worked.
@izarutskaya can you confirm if changing the setting - after waiting at least 10 seconds or so after connecting QBO - does work as intended? If so, I think we can close this and handle the syncing separately.

@dangrous if you need any frontend work for it, I can help 😊

@dangrous the bug is specific to the first time

testing again now

I made a new workspace and waited 10 min but no avail the 1st time
Seems the  funky update is coming from this `getMissingONYXUpdates` call @dangrous

Right after I call
UpdateQuickbooksOnlineReceivableAccount
{
    "jsonCode": 200,
    "requestID": "8c528932cdf5bd9d-LHR",
    "onyxData": [
        {
            "key": "policy_96C3808269C266A8",
            "onyxMethod": "merge",
            "value": {
                "connections": {
                    "quickbooksOnline": {
                        "config": {
                            "receivableAccount": {
                                "currency": "USD",
                                "glCode": "",
                                "id": "1150040001",
                                "name": "Testing New Dot"
                            }
                        }
                    }
                }
            }
        }
    ],
    "previousUpdateID":<PHONE_NUMBER>,
    "lastUpdateID":<PHONE_NUMBER>
}

I see a call to GetMissingOnyxMessages
        {
            "key": "policy_96C3808269C266A8",
            "onyxMethod": "merge",
            "value": {
                "connections": {
                    "quickbooksOnline": {
                        "config": {
                            "receivableAccount": {
                                "currency": "USD",
                                "glCode": "",
                                "id": "53",
                                "name": "Accounts Receivable"
                            }
                        }
                    }
                }
            }
        },

Demoting as an app blocker since it's an erroneous onyx update

Triaged but I'm already working on a wave-collect issue, unassigning

I'll try to fix this

Why did Melv put this to Monthly? Changing it back.

I'm having problems reproducing this in either dev or staging:
https://github.com/user-attachments/assets/7eabf7a6-170c-40dc-9dec-9012c19c90ab
From reading the thread above, it sounds like there may be some race condition where not all the updates containing the initial connection have arrived and we change the setting. This results in an old onyx update changing the setting back. Would be nice to be able to reproduce this more consistently.
I have problems with the pusher updates in dev, they are very flakey or they simply don't arrive at all.. which is making it though for me to debug/reproduce.

As @grgia mentioned, there is a call to GetMissingOnyxMessages (two really in my case) that happen after the connection is stablished without me taking any extra action:

Maybe I can investigate what is triggering these GetMissingOnyxMessages requests and try to prevent that.

Was OOO yesterday, I'll try to get back to this on Wednesday or Thursday

haven't have time yet 😬 , I'll try again next week.

Didn't have time today.

I'm getting back to this after lunch

So.. when I was preparing to work on this, I destroyed my VM by mistake and now I have been struggling with certificates for hours and I still can't get past it. I'll continue on this on Tuesday.

Does this need help?

Does this need help?

Not for now, I plan to get back to this today

I haven't checked it yet. I can try to take a look from FE side.

Now I have my dev env fully working again. From testing I can see that the IS code call several times SavePolicy during import and during sync. Each call to SavePolicy will save some onyx updates to the database that are later processed by the job www-prod/SendFetchableOnyxUpdates that pushes them to the clients.
Considering this, I guess it is expected that the onyx updates will arrived in any order since:

The jobs www-prod/SendFetchableOnyxUpdates are not executed in order, and
The pushed events not necessarily arrive in order because of the network (specially if they come from different jobs).

This makes it very likely that some calls to GetMissingOnyxUpdates will happen because of the bad order.

No updates, I've been focusing on this other QBO quality issue: https://github.com/Expensify/App/issues/49371 which has a more clear solution.

Holding on https://github.com/Expensify/App/issues/49371 before continuing in case the fix there helps with this too.

Still waiting for the PR to be reviewed...

https://github.com/Expensify/App/pull/51110 was merged, I'll get back on testing this asap

Great!

So I have been working today on this, and I have manage to reproduce it a few times, but is hard... most of the time you don't  have enough time to go to the setting and change it. I have tried with slow connections and it doesn't make it easier.
I'll be also OOO next week, so considering that and the above, I'll lower the priority to Weekly because I don't think this can happen easily for a real user.
Having said that, I think I have an idea of how to fix this in the Integration-Server. The current behaviour is:

We import the data from QBO
Call the command Policy_Connection_Set to store it
Pick default configs using the data read in step 1
Call the command Policy_Connection_Set to store the default configs

I think I can change this to:

We import the data from QBO
Pick default configs using the data read in step 1
Call the command Policy_Connection_Set to store the imported data and the default configs

If we do a single Policy_Connection_Set call, it won't be possible that the frontend receives the imported data in a separate update from the one containing the default configs.

PR up: https://github.com/Expensify/Integration-Server/pull/8184

Closing this, the backend PR was deployed last week: https://github.com/Expensify/Integration-Server/pull/8184

Thanks for sticking with this one, Aldo.


Support for Ruby Characters

In asian scripts like Japanese or Chinese there is a concept of Ruby Characters, annotative characters which accompany complex characters. In Japanese these are known as Furigana, and in Chinese as Bopomofo.
Vocascan could benefit from displaying these characters in the right way. Modern browsers all support  Ruby Characters, and if they don't there is a fallback available.
I have made the functionality already for the Vocab Cards.

I do not have permission to make a branch right now. If I can be given that permission then I will share my code.
The Ruby Characters need to be entered in the database in a standard format. Use [] to enclose the base characters, and {} to encase the Ruby characters.

This is then parsed to create the appropriate HTML tags.

The PR is available with a couple questions: #148


Updating alamofire package versions.

Issue
Getting complaints from Apple regarding Missing API Declaration around System Boot Time, the only library that we use that accesses that is Alamofire + AlamofireImage since it includes a ref to the problematic Alamofire instance.
Solution
Updating the Alamofire package referenced in this project to use the latest version that includes a privacy manifest.

didn't seem to resolve the issue, closing

didn't seem to resolve the issue, closing

Were you able to solve it?.. Having same issue

@cedricbahirwe as of my last release pointing directly to the forked version with the package updated I was still getting the warning from apple about missing API declaration. I think there's just something broken about how Apple is grabbing privacy info from SPM packages, so for my next release I'm just adding the privacy info to my own project until it's resolved.


What is warpd -l for, or how can I set up my activation key?

Hi,
I would like to have "Alt_L-Alt_R-Control_R-Shift_R-q" as my activation key. Unfortunately, when I put this in my config file, warpd gives me an error:
ERROR: Alt_L-Alt_R-Control_R-Shift_R-q is not a valid key name.
So, in which format should I specify my keys, and what is the purpose of the "-l" parameter?
Thank you!

That's a good question, I am also not sure what's the point of keys listed by -l, given warpd isn't able to process them.
The correct format would be A-C-q, this is similar to what you can find in README here. However, due to a bug this not gonna work even if provided in correct format.


Information regarding file policies

Dear,
I've been playing around with file policies myself, and tried to follow the following advice in the article.
"When using the file policy filters, Contains will search only for full words – separated by commas, dots, or spaces to search.
Spaces between words function like OR. For example, if you search for malware virus it will find all files with either malware or virus in the name, so it will find both malware-virus.exe and virus.exe."
I tried doing this myself, but none of the options work.
Is there a bug that prevents this in Microsoft Defender for Cloud Apps?

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

ID: f258bad7-5c1a-ad1d-ee3b-a0298a49d855
Version Independent ID: c254079f-f5d9-bac4-2966-bcbb8031f1c9
Content: Understanding file data and filters available in Defender for Cloud Apps
Content Source: CloudAppSecurityDocs/file-filters.md
Service: defender-for-cloud-apps
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

This isn't a documentation issue and requires further investigation. The best way to get help is to open a support ticket.

Hi dcurwin,
I indeed opened a support ticket, but played around with it some more.
I found how to make it working, maybe it helps for people with the same issue.
The "OR" functionality seems to work with quotation marks, but without spaces.
e.g. ("hello""world") will find files with only the single word "hello", "world" and files with either of the words in it.
("hello" "world") would not find the files with the single words.
Hope it helps :)


Add support for required keyword

Enable required properties to be marked as required in SwaggerGen.
Resolves https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/2764

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.71%. Comparing base (45a2cb7) to head (041a937).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2810      +/-   ##
==========================================
+ Coverage   91.70%   91.71%   +0.01%
==========================================
  Files          91       91
  Lines        3025     3031       +6
  Branches      519      519
==========================================
+ Hits         2774     2780       +6
  Misses        251      251

Flag
Coverage Δ

Linux
91.71% <100.00%> (+0.01%)
:arrow_up:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

is this going to be released anytime soon?

It will be released in the next release when other changes marked for that release have been reviewed and merged too.


Publish 09/26/2022 3:30 PM PT

Docs Build status updates of commit 993f8c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[FLINK-32031] Flink GCP Connector having issues with Conscrypt library

What is the purpose of this change
The Flink GCP Pubsub Connector uses the gcp-cloud-libraries-bom which internally uses conscrypt library.
This was causing an issue in Dataproc 2.1 image where the Dataproc cluster had more recent version of conscrypt library compared to what was available in the connector jar.
This fix upgrades the gcp-cloud-libraries-bom from 8.1.0 to 26.1.0 which removes the conscrypt library and few other libraries and updates couple of API changes due to version upgrades
Brief change log
This fix upgrades the gcp-cloud-libraries-bom from 8.1.0 to 26.1.0 which removes the conscrypt library and few other libraries and updates couple of API changes due to version upgrades
Verifying this change
Ran a sample code to read from Google Cloud Pubsub and write to GCS

@MartijnVisser - I closed the earlier PR and raised a new one, my local workspace had got corrupted so I cleaned it up and added back the changes. Please take a look. Apologies for the confusion

@jayadeep-jayaraman Thanks. Will you also create the backport to the v3.0 branch?

Sure, I have submitted another PR to merge into v3.0 branch


Missing examples

Need new lines at the end of the README examples block:
assert.ok(isCallable(Function(''));
assert.ok(isCallable(new Function);
assert.ok(isCallable(new Function(''));
assert.ok(isCallable(new Function([], ''));

Since Function should never be used, I'm not sure why it would be a good idea to include them in examples?

I suppose that’s fair, but has there ever been an instance in any engine when a Function produced something distinguishable from a normal function? Why would anyone have any expectation that using Function changes anything?