Incorrect Google Play storage space calculations?

Why exactly does this message "More storage space required" appear when installing an app through Google Play Store while sufficient space is theoretically available (x more than Mo required)? And on top of that, after deleting one or more apps, this message keeps popping up, asking for extra space. Interestingly, sometimes x's turns out to be higher than before the removal of some apps. This is only when I delete very large applications that Store proceeds with the installation. Is it because the game store reserves a portion of the storage space that is then no longer available?

usability – Incorrect iframe implementation

It sounds like a failure of responsiveness for me.

The result appears as a technical problem – which is the case, on the device's surface – but the first step towards a fix may lie in more explicit instructions on the UI specifications on the device. Dev implementation, which I will discuss later.

An iframe is essentially a window to another content embedded in a window.

A good example frequently used is the map view (usually small to extended) in applications such as Yelp, OpenTable (gastronomy) or Strava, Fitbit (sport) or even Uber, where the map shows you the rides available nearby is essential.

These cards are usually powered by an external service from Google or Apple (you can usually tell by their graphics), which is why you have to tell your device to allow tracking of my location. Since the applications I mention must display other dashboard style information next to the map content, the UI designers assign a size (W and H) and a location ( X and Y) carefully calibrated to the "hosting" the map. This is strictly all that is required. The iframe becomes a portal to the part of the map of interest for the purpose of the application (the surrounding area serving as a "mask"), but you can usually pan, zoom, and scroll in the iframe. And, of course, switch the map to full screen and back.

Scrolling in the frame is the standard behavior of iframes – it should not be enabled as such.

Iframes are usually implemented responsively – provided that the front end is done right: when loading the iframe, it "asks" the target device. What is your height and width? and adjust its size and location accordingly. Maybe the width is not defined in absolute pixels but by an equal left and right fill, presenting you with a proportionally larger portal on a larger device. Or at a more abstract level by sticking to a column layout. It's essentially what you describe. However, I am not sure that these rules have been respected. Some nagging questions well placed can enlighten us.

If an iframe was dimensioned in absolute terms, and these absolute terms were based on a larger device, perhaps even in the desktop browser window, it would anchor its upper left corner to the specified X and Y positions on a larger screen. small, while exceeding the available display. area to the right and down, rather than adapting.

In case of failure of all other approaches, you can handle this by an explicit instruction above the iframe to use gestures to pan or zoom to the desired content (if these gestures are recognized), but it goes without saying that this is necessary. extremely UX poor, who calls for me the business model of using a third-party offer via iframe in question.

Make the product manager / owner your ally – trust me, I recognize such remote fallback situations! A third iframe, if that's the way forward, must work perfectly.

In terms of due diligence, be sure to include explicit specifications in your documentation or UI documentation, or ask the UI designer you are collaborating with to do so if you are not familiar with it. It is not your primary responsibility to consider reactive or adaptive iframe sizing. You can always add some real-world examples by searching for the smallest and largest screens of smartphones and tablets – iPhone, Samsung, etc. – and make a visual representation of the problem. Essentially, and this is essential to repel a policy that should not overflow with blame: as designers, we must explain in our specifications to developers that undesirable effects of the UI should not occur, namely iframes with "blind zones" according to your example. above. It is up to the developer to determine how to build it. Your UI specs may need to be more explicit in terms of iframe behavior rules – and this will help to make the technical team understand that you are a business. Dev's repeated experience responds well to design intentions presented with finality and accuracy.

Of course, your case is even more complicated because it is not a map that you can zoom and resize freely, but a canned third shape of a given size (and probably fixed). Do you know what is this size – esp. its width? With this, you may be able to define sizing rules in your specifications. Suppose the rightmost 15% is off on most devices. In this case, you can ask developers to specify a scale factor expressed as a percentage, until the form fills the entire width without scrolling sideways. It is difficult for a forum audience to continue on this path without further details on the specific content. Good luck!

SQL Server – Query slow in production, incorrect execution plan or incorrect index?

I just fixed a production performance issue by removing an index and recreating it.
I guess the deletion of the index also resulted in the abandonment of the execution plans that used it and that one of them was bad.

Arguments in favor of a bad execution plan:

  • Before deleting the index, I searched for the last update date for the statistics in the given table and they were up to date.
  • My database administrator has implemented Hallengren index and statistics maintenance solution
  • The slow query was a select statement executed from sp_executesql with the date settings. Execute the same select statement without sp_executesql was fast, but did not use the same execution plan either.

Arguments against the bad plan of execution:

  • Before dropping the index, we went crazy and executed the forbidden dbcc freeproccache to erase any bad plan, but that did not solve the performance problem.


  • The slow query uses a table indexed by date. however,
    there are big differences in the amount of records for each date. In
    other word, any given date ranges from a few records to over 100k
    and it's pretty random.

  • The database runs under compatibility level 140 (SQL Server

Was the source of the problem a bad plan or an obsolete index?
If it's a bad plan, then why dbcc freeproccache did not work to get rid of it?

web application – PHP | Can the incorrect operation of `mysql_query () or die (mysql_error ())` be used to exfiltrate data?

I've encountered legacy code that uses mysql_query($sql) or die(mysql_error())

Was curious and noticed that with a " in the email entry … I am shown output of mysql_error () as the user.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"""' at line 1

mysql_query('SELECT * FROM users WHERE users_email_address = "'.$email.'") or die(mysql_error());

I managed to crash the browser with" OR "" = … since I guess that caused an infinite loop

The first part of the question is … how could I exfiltrate information with this " condition that I found? Is there a special name for this application other than the SQL injection on which I can find out more?

The second part of the question is: mysql_error the exit seems to be advantageous for a potential intruder, but I am not aware of the depth of the information it could provide.

Msg 102, Level 15, State 1, Line 28 Syntax Incorrect Near (& # 39;

do not understand what I miss, how to correct this error

enter the description of the image here

Customs and Immigration – Incorrect Name of a Character on a Kuwaiti Plane Ticket

The immigration officer does not care so much about your ticket.

Airlines are often the major problem: the left hand does not know what the right hand does. On the other hand, I have traveled a lot with typing errors on the names (especially on my companions: if you want me to reserve a flight, expect that I can not type correctly ;-)), and no one complained.

Do not worry. Next time, try to check better (but I only discover half of the errors).

magento2 – 400 incorrect queries on the customer registration page

In my project, on the customer registration page, there was an error on the console as below.

GET 400 (Bad Request)

The script called in the Magento_Core module under the CyberSource Core Block Fingerprint.php block file

How can I fix the error. ?

magento 1.9 – DateTime type: incorrect display

I want to create a grid to display the hours of a collection.
I've therefore added the date column like this:

    $this->addColumn ( 'date_birthday', array (
            'header' => 'Date of birthday',
            'align' => 'right',
            'width' => '100px',
            'type' => 'datetime'
            'index' => 'mydate'
    ) );

In my collection there is: (it's simplified)

1 2017-11-08 18:00:00
2 2011-11-08 12:00:00
3 3017-11-08 10:00:00

The grid displayed is:

1 2017-11-08 19:00:00
2 2011-11-08 13:00:00
3 3017-11-08 11:00:00

With the attributes "datetime", you can see that all my displayed hours have 1 hour more than the collection.
And without this attribute, the hours are displayed correctly.

An idea ?
Thank you !

woocommerce – The function returned by nested tax query arguments returns incorrect arguments

I produce skus products that meet my tax request requirement in which several tax requests are nested by "AND". here is my code

$args = my_brands_loop(('brand_name'=>'mytag','shapes'=>'circle'));
    $loop = new WP_Query( $args );
    if ( $loop->have_posts() ) {
       while ( $loop->have_posts() ) : $loop->the_post();
           //wc_get_template_part( 'content', 'product' );
           $product = wc_get_product(get_the_ID());
           echo "
" . $product->sku ."
"; endwhile; } else { echo __( 'No products found' ); } wp_reset_postdata(); function my_brands_loop($term_taxonomies){ $term_array = array(); foreach($term_taxonomies as $k=>$v){ array_push($term_array, array( 'taxonomy' => $k, 'field' =>'slug', 'terms' => $v ) ); } $x = implode(",",$term_array); $args = array( 'post_type' => 'product', 'tax_query' => array( 'relation' => 'AND', $x ), ); return $args; }

This generates incorrect SKU values. I get the correct SKU values, if I'm between the arguments like this in the loop

    $args = array(
       'post_type' => 'product',
       'tax_query' => array(
          'relation' => 'AND',
             'taxonomy' => 'brand_name',
             'field'    => 'slug',
             'terms'    => 'mytag',
              'taxonomy' => 'shapes',
               'field'   =>'slug',
               'terms'  =>'circle',


But how to get the arguments via the function and get the correct sku values?

magento2 – 400 incorrect queries when paying with Amazon 3.0.10 in Magento 2

I updated Amazon Extention 3.0.10, when I clicked on my command, this error is visible

400 Bad Request
The domain on which you are using the JavaScript SDK has not been 
whitelisted for your application. Please add your website domain 
in the 'Allowed JavaScript Origins' section under 'Web Settings' 
on the Amazon Seller Central App Console for Login with Amazon.

I have an amazon account, how to add my website domain in Authorized Javascript Origins? I can not find it.

enter the description of the image here

Help me, please.