deployment - Can't deploy my App Engine since SDK 1.9.46 -

-

since upgraded gradle build deploy app engine application sdk 1.9.46, deployment conflict messages, 1 below.

beginning interaction module admin... 0% created staging directory at: '/var/folders/m8/6z4h4k2x11s3whxrqmd79lym0000gn/t/appcfg2292422843793738444.tmp' 5% scanning jsp files. 8% generated git repository information file. 20% scanning files on local disk. 25% scanned 250 files. 28% scanned 500 files. 31% scanned 750 files. 33% scanned 1000 files. 34% initiating update. nov 13, 2016 11:11:41 com.google.appengine.tools.admin.abstractserverconnection send1 warning: error posting url: https://appengine.google.com/api/appversion/create?module=admin&app_id=the-outdoor-game&version=dev& 409 conflict there operation pending application: applock held "updating engine_version_id='dev' within engine_id='default'." acquired peter.fortuin @ 2016-11-13 09:15:05.482616 gmt.  please wait , try again or use 'appcfg rollback' attempt cleanly abort current operation. try #0

a rollback if not solving problem. thing seems work downgrading app engine sdk 1.9.44. gives me other problems don't want solve.

anybody has idea how solve this? can bug in 1.9.46 sdk? else seeing same thing?

i have resolved problem changing 'service' 'module' in appengine-web.xml of module. see https://github.com/googlecloudplatform/gradle-appengine-plugin/issues/268 more information.


Comments

Post a Comment

Popular posts from this blog

php - How to display all orders for a single product showing the most recent first? Woocommerce -

-
i have password protected page on frontend. on page, want display full list of purchases associated single woocommerce product id. option 1: i've looked through woocommerce docs , , found: wc_cli_order , list_( $args, $assoc_args ) function lists orders. presumably, orders can filtered product id [--=] filter orders based on order property. line item fields (numeric array, started index zero): line_items.0.product_id option 2: i found article , based on customer id. i've modified code based on guesses meta_key , meta_value. $customer_orders = get_posts( array( 'numberposts' => -1, 'meta_key' => '_product', 'meta_value' => get_product_id(), 'post_type' => wc_get_order_types(), 'post_status' => array_keys( wc_get_order_statuses() ), ) ); how display orders single product showing recent order first? here solution put based on these articles: http://www.w...
Read more

asp.net - How to correctly use QUERY_STRING in ISAPI rewrite? -

-
i'm having difficult time , hope guys can help. using helicon isapi rewrite version 3.1.0.104 on our iis server. edit http.conf file , have tried , still fail. this trying do: redirect url: https://www.domain.com/switch-by-version?version=2.8.5.2594 to: https://test.domain.com/load/load.aspx?tver=2.8.5.2594 the version number @ end source url change, , need target url have same version number @ end of url example above shows. i tried following not work: rewritecond %{query_string} ^version=(\d\d?)\.(\d\d?)\.(\d\d?)\.(.*)$ [nc] rewriterule ^/switch-by-version(.*)$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l] any appreciated! thanks. if it's running in equivalent context of .htaccess , rule shouldn't start / . here's simpler version: rewritecond %{query_string} ^version=(\d+\.\d+\.\d+(?:\..+)?)$ [nc] rewriterule ^switch-by-version/?$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l]
Read more

angularjs - How restrict admin panel using in backend laravel and admin panel on angular? -

-
https://scotch.io/tutorials/token-based-authentication-for-angularjs-and-laravel-apps following tutorials, try write authentication restrict admin panel, didn't understood how can that. this admin panel, admin panel don't want show , request database unauthenticated users. my laravel-routes route::get('/admin',function(){ return view('index'); }); route::get('/api/v1/employees/{id?}', 'employees@index'); route::get('/api/v1/users/{id?}', 'employees@users'); route::post('/api/v1/employees', 'employees@store'); route::post('/api/v1/employees/{id}', 'employees@update'); route::delete('/api/v1/employees/{id}', 'employees@destroy'); route::group(['prefix' => 'api'], function() { route::resource('authenticate', 'authenticatecontroller', ['only' => ['index']]); route::post('authenticate', 'authentic...
Read more