research | accessible via a futuristic natural language interface

I got below error message when I run model_main_tf2.py on Object Detection API:

I have just started a new project using Bootstrap 5 and I am trying to set up theme-colors with some custom values. However doing it the way that I have always done it is giving me some issues.

I have created three colors: $primary, $secondary, $tertiary. However if I add any classes such as bg-tertiary, then nothing changes as if it doesn't exist. bg-primary simply uses the default color defined by Bootstrap.

My code below:

I was programming a game using Python and a sound effect needed to be played, so I used the playsound module:

Until yesterday (20 Jan) I could connect to another google drive account (using drive._mount), but when I tried this today, google colab showed me this error:

here is an MRE (showing two attempts, with debug left in to be helpful) to try and get 2d subscripting working with AT-POS across a DataFrame that has columns of Series...

There are so many ways to define colour scales within ggplot2. After just loading ggplot2 I count 22 functions beginging with scale_color_* (or scale_colour_*) and same number beginging with scale_fill_*. Is it possible to briefly name the purpose of the functions below? Particularly I struggle with the differences of some of the functions and when to use them.

• scale_*_binned()
• scale_*_brewer()
• scale_*_continuous()
• scale_*_date()
• scale_*_datetime()
• scale_*_discrete()
• scale_*_distiller()
• scale_*_fermenter()
• scale_*_gradient()
• scale_*_gradient2()
• scale_*_gradientn()
• scale_*_grey()
• scale_*_hue()
• scale_*_identity()
• scale_*_manual()
• scale_*_ordinal()
• scale_*_steps()
• scale_*_steps2()
• scale_*_stepsn()
• scale_*_viridis_b()
• scale_*_viridis_c()
• scale_*_viridis_d()

What I tried

I've tried to make some research on the web but the more I read the more I get onfused. To drop some random example: "The default scale for continuous fill scales is scale_fill_continuous() which in turn defaults to scale_fill_gradient()". I do not get what the difference of both functions is. Again, this is just an example. Same is true for scale_color_binned() and scale_color_discrete() where I can not name the difference. And in case of scale_color_date() and scale_color_datetime() the destription says "scale_*_gradient creates a two colour gradient (low-high), scale_*_gradient2 creates a diverging colour gradient (low-mid-high), scale_*_gradientn creates a n-colour gradient." which is nice to know but how is this related to scale_color_date() and scale_color_datetime()? Looking for those functions on the web does not give me very informative sources either. Reading on this topic gets also chaotic because there are tons of color palettes in different packages which are sequential/ diverging/ qualitative plus one can set same color in different ways, i.e. by color name, rgb, number, hex code or palette name. In part this is not directly related to the question about the 2*22 functions but in some cases it is because providing a "wrong" palette results in an error (e.g. the error"Continuous value supplied to discrete scale).

Why I ask this

I need to do many plots for my work and I am supposed to provide some function that returns all kind of plots. The plots are supposed to have similiar layout so that they fit well together. One aspect I need to consider here is that the colour scales of the plots go well together. See here for example, where so many different kind of plots have same colour scale. I was hoping I could use some general function which provides a colour palette to any data, regardless of whether the data is continuous or categorical, whether it is a fill or col easthetic. But since this is not how colour scales are defined in ggplot2 I need to understand what all those functions are good for.

We have an enterprise account, and till iOS 14 there were no issues, but as soon as user update their phones to iOS 15, they are getting this alert.

The Developer of this app needs to update it to work with this version of iOS

Now, this issue is coming only for enterprise apps running on iOS 15. I have done some research and found this article. https://developer.apple.com/documentation/xcode/using-the-latest-code-signature-format.

In here it states that

To check whether an app called MyApp.app has the new signature, you can use the

codesign utility: % codesign -dv /path/to/MyApp.app

Look in the output for a string such as CodeDirectory v=20500. For any value of v less than 20400, you need to re-sign your app.

I did that and my output was indeed v=20400. I have signed the app using Xcode 12.5 running on Mac OS 11.2.3. I don't think Apple documents are correct for this. (I could be wrong)

Can anyone please help and let me know, what exactly we need to do to get this issue fixed?

EDIT: I was able to solve this issue by upgrading OS to Big Sur. Xcode version was 12.5.

For my research I need to cURL the fqdns and get their status codes. (For Http, Https services) But some http urls open as https although it returns 200 with cURL. (successful request, no redirect)

I have been testing my iOS app on my physical iPhone XS for quite some time now and all of a sudden it threw an error when I tried to run it saying:

"APP NAME" is no longer available.

So I went to re-build via Xcode into my device again to reinstall it. But I was getting an error message saying "Untrusted Developer".

So I tried to go to the Settings > General > VPN and Device Management screen to see if I need to 'Trust' my own developer profile again. But it's not appearing on that screen or any other new developer profile for that matter.

Did a bit of research and tried to troubleshoot. One of the solutions I've found and worked was to actually create a new developer account and use that to build and install the app on my device. I does work but I don't want to use another developer account to to build this app as the bundle identifier that I wanted to use was already tied up to that old account. And I have a bunch of other apps tied up to that old account as well.

The other reason why the above solution also wouldn't be ideal as I already have months worth of data in my device that was saved in that app. If created a new build using a new account it wouldn't be able to access the data of the old app built using the other account.

Just to note, that old account was formerly a paid account but now it expired. But I didn't have that problem until recently. So I am guessing it has something to do with the recent iOS 15 beta builds.

I will be filing a bug report for this. But does anyone have any idea or workaround to get rid of this issue? Any information that could potentially point me towards the right direction would be appreciated. Thanks!

I've filed this as a bug on AppleFeedback Assitant. They've reached out to me to ask for logs and the certificate I used to re-build the project. I'm guessing this this a bug and they are trying to fix it.