topic Re: JavaScript Optimizer "queued" status in ArcGIS JavaScript Maps SDK Questions

JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Wed, 21 May 2014 16:51:04 GMT

I've been working with the Optimizer for a couple days, and having a tough time getting everything configured the way it likes. It's a nontrivial application. At first, I just got a "queued" status. Then, for a while I was getting actual output. But, now I'm back to getting "queued". These builds remain queued for a long time, until I delete them.

I'm wondering, is there some kind of error or misconfiguration in my code that would cause the "queued" status? Or, is it really queued? Is there some kind of metering that's causing me to wait?

Re: JavaScript Optimizer "queued" status

derekswingley1 — Wed, 21 May 2014 20:00:48 GMT

We have pretty tight limits on how many builds can run concurrently so our servers for the app don't grind to a halt. My guess would be that your build is legitimately queued.

To investigate further, please answer:

Is the account you're using an organizational or developer account?

How long did you wait for your build to run?

Re: JavaScript Optimizer "queued" status

ReneRubalcava — Wed, 21 May 2014 21:54:13 GMT

Just to test yesterday, I uploaded the zip fo the CSV Layer example (as-is) and just checked, it's still at status of "queued".
Maybe that's a bad sample to test off, but it's fairly simple, so not sure what's holding it up.

Developer Account and running around 24 hours now probably.

Re: JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Sat, 11 Dec 2021 18:36:16 GMT

My account is an organizational account, and my builds were queued for 24 hours now. I deleted them all this morning, since I'm pretty sure they were stuck.

I'll bet that the fault lies with my application. Sometimes I can get the build to "Scan". But, sometimes it won't "Scan", and it just sits queued.

A great addition to the help screen would be a demo layout, showing the dojoConfig, and a package.json. Maybe a trivial project in GitHub that builds successfully?

The application I'm uploading is a zip file (Windows compressed folder, if the algorithm matters). My app is very similar to the Spriggs project, with the addition of a buildFile and the package.json files. Here's a simplified structure inside the zip, and maybe you can see any obvious errors:

ZipFile
  Scripts
    buildFile.html
    someWidget.js
    someOtherWidget.js
    app
      packages.json
      MyApp.js
    gis
      package.json
      dijit
        Draw.js
        Draw
          css
            ...
          images
            ...
          templates
            ...

Maybe you're wondering what this buildFile is all about. Since the actual html host page is complex, I've just created a simplified html file for the build system. It looks like this:

[HTML]
<!DOCTYPE html>
<html>
<head>
<title>Map Build File</title>
</head>
<body>
        <script>
            var debugMode = true;
            var dojoConfig = {
                isDebug: debugMode,
                packages: [{
                    name: "/js",
                    location: ''
                },
                {
                    name: "/gis",
                    location: '/gis'
                },
                {
                    name: "/widget",
                    location: '/widget'
                },
                {
                    name: "/tool",
                    location: '/tool'
                },
                {
                    name: "/app",
                    location: '/app'
                }]
            };
        </script>
        <script src="//js.arcgis.com/3.9/"></script>
        <script>
            require([
                'app/MyApp',
                'dojo/io-query',
                'dojo/parser',
                'dojo/ready',
            ],
                function (MyApp, ioQuery, parser, ready) {

                    ready(function () {
                     parser.parse();
                        var options = {
                          debug: debugMode
                        };
                        var app = new MyApp(options);
                        app.startup();

                    }); // end ready

                } // end function

            ); //end require

        </script>
</body>
</html>
[/HTML]

I had been specifying my start point as the build file. Instead, I specified the start point as my application file, but got the same results. Then, when I unchecked the advanced option "only include build files", the build doesn't even queue. It just hangs on the "Building" screen.

I should also mention, just in case, the my zip file includes both source and minified versions of all my javascript files. That's because I've configured Visual Studio to minify the files automatically. I assume the builder will ignore those.

Re: JavaScript Optimizer "queued" status

derekswingley1 — Thu, 22 May 2014 23:19:01 GMT

We had an issue from some time Tuesday through this morning where the queue was not working correctly. It's working now.

AJ: why do you have slashes in your package names? I'm not used to seeing that and don't think it's something we tested. Can you try with names that don't use the slashes? As for minified files, yes, the app will ignore those.

Re: JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Fri, 23 May 2014 10:49:03 GMT

I received a build success notification last night. But, that's strange because I had deleted all of my queued builds except one. And, that one is still listed as queued since yesterday. So, maybe a result of the broken queue flushing? Or, something else happening, like the status of the builds is different than what's displayed on screen? Or, clicking "cancel" on a build doesn't actual remove it from the queue?

Derek: The quotes are in the package name because I have fat fingers. Thanks for finding that error. I removed them from my build file. In addition to fixing the package names, I simplified the layout of my project. And, I got on board with Grunt, so my files have much less lint. I thought that might have been an issue. Unfortunately, this build that I uploaded this morning is listed as queued, too.

Two more angles that could be causing an issue. First, my understanding is that the builder doesn't actually execute any JavaScript. Rather, is just scans the files for requires. So, things like document.location.protocol, and initialization parameters in the build file, won't be an issue. Second, I have to wonder about my build file. Suppose I forget about the build file, and just point the builder to the application entry point (javascript file). Since there would be no dojoConfig, how would the builder be able to locate my other packages, such as "tool", "widget", etc?

Re: JavaScript Optimizer "queued" status

derekswingley1 — Fri, 23 May 2014 13:47:45 GMT

Quotes or slashes?

Please don't start assuming "queued" means "broken". There are legitimate times when builds are queued. That being said, if your build is still queued now, something went wrong again (I just ran a build successfully).

If you have errors in your code you're likely to have problems generating a build.

If you don't have a dojoConfig that defines where to find custom packages you're referencing in your require or define calls the optimizer will fail.

Re: JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Fri, 23 May 2014 14:06:02 GMT

Quotes or slashes?

I mean to say slashes. They are gone now.

If your build is still queued now, something went wrong again.

Indeed, something is wrong. The optimizer doesn't like my code. I'll strip it down to the most basic, and add pieces back until it breaks. Then, I'll report back.

Re: JavaScript Optimizer "queued" status

derekswingley1 — Fri, 23 May 2014 14:57:02 GMT

Indeed, something is wrong. The optimizer doesn't like my code. I'll strip it down to the most basic, and add pieces back until it breaks. Then, I'll report back.

Thanks. I would expect the build to fail rather than stall out as "queued". If you're able to isolate what's causing this then that will help us all in the long run.

Re: JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Fri, 23 May 2014 15:18:11 GMT

Even with the most trivial html page, without external scripts, I can't get past the "queued" status. In fact, I can't even do a build by clicking and checking the modules. I don't think that this is a problem with the optimizer. Rather, it could be a problem with AGO authorization, or my account is throttled for too many cancelled builds.

Re: JavaScript Optimizer "queued" status

derekswingley1 — Fri, 23 May 2014 15:37:51 GMT

Can you email your org name and account name to js_feedback@esri.com? I'll try to get this sorted out.

Re: JavaScript Optimizer "queued" status

JeffPace — Fri, 23 May 2014 17:54:44 GMT

I tried my site, and get

Crawl and Analyze
Detecting Configuration
Crawling Your Code
Unable to find a script tag referencing dojo.js or the ArcGIS JS API.

I dont think it likes my reference to a local API

link

http://www.mymanatee.org/gisapps/mobile/index.html

Re: JavaScript Optimizer "queued" status

deleted-user-Jie3eyjOl9XM — Sat, 11 Dec 2021 18:36:18 GMT

Jeff:

Unable to find a script tag referencing dojo.js or the ArcGIS JS API.

This same thing happened to me when I tried to point the JSO at a URL. But, mine was not a local API. I thought was because I was referencing like this:

<script src="//js.arcgis.com/3.9/"></script>

But even when I added the prefix, it didn't matter. I wish I could say I solved it, but instead I went back to uploading the zip.

Re: JavaScript Optimizer "queued" status

RahulMetangale1 — Sat, 11 Dec 2021 18:36:21 GMT

Hi All,

I am also facing the same issue. Build is getting queued. I have tried following approaches:
Approach 1:
Uploaded module list

dijit/_WidgetBase
dijit/_Widget
dijit/_TemplatedMixin
dijit/_WidgetsInTemplateMixin
dijit/Dialog
dijit/registry
dijit/form/ComboBox
dijit/form/DateTextBox
dijit/form/MultiSelect
dijit/form/TextBox
dojox/charting/themes/Desert
dojox/charting/plot2d/Pie
dojox/charting/widget/Legend
dojo/domReady
dojo/dom-class
dojo/dom-attr
dojo/text
dojo/on
dojo/dom
dojo/aspect
dojo/_base/lang
dojo/Stateful
dojo/Deferred
dojo/_base/declare
dojo/_base/array
dojo/DeferredList
dojo/dom-style
dojo/dom-construct
dojo/_base/Color
dojo/_base/connect
dojo/store/Memory
dojo/data/ItemFileReadStore
dojo/when
dojo/date/locale
dojo/query
dojo/_base/fx
dojo/fx/easing
dojo/dom-geometry
dojo/_base/event
dojo/NodeList-traverse
dojo/NodeList-manipulate
esri/tasks/QueryTask
esri/tasks/query
esri/layers/layer
esri/layers/ArcGISTiledMapServiceLayer
esri/tasks/BufferParameters
esri/tasks/GeometryService
esri/tasks/RelationParameters
esri/graphic
esri/layers/GraphicsLayer
esri/layers/FeatureLayer
esri/renderers/SimpleRenderer
esri/symbols/SimpleMarkerSymbol
esri/symbols/PictureMarkerSymbol
esri/symbols/SimpleLineSymbol
esri/symbols/SimpleFillSymbol
esri/geometry/Point
esri/geometry/Polygon
esri/geometry/Polyline
esri/toolbars/draw
esri/tasks/Geoprocessor
esri/graphicsUtils
esri/request
esri/renderers/UniqueValueRenderer
esri/map
esri/layers/ArcGISDynamicMapServiceLayer
esri/layers/ArcGISImageServiceLayer
esri/layers/ArcGISTiledMapServiceLayer
esri/dijit/Popup
esri/dijit/PopupTemplate
esri/toolbars/navigation
esri/dijit/Legend
esri/TimeExtent
esri/dijit/TimeSlider

Approach 2:
When I upload a ZIP file of entire application only one file (that is main.js ) is selected in module list. Is this expected behavior? Here is my main.js file

(function () {
    require({
        async: 1,
        parseOnLoad: true,
        aliases: [
            ["text", "dojo/text"]
        ],
        packages: [{
            name: "widgets",
            location: location.href.slice(0, location.href.lastIndexOf("/")) + "/widgets"
        }, {
            name: "core_library",
            location: location.href.slice(0, location.href.lastIndexOf("/")) + "/core_library"
        }, {
            name: "images",
            location: location.href.slice(0, location.href.lastIndexOf("/")) + "/images"
        }, {
            name: "nls",
            location: location.href.slice(0, location.href.lastIndexOf("/")) + "/nls"
        }, {
            name: "app",
            location: location.href.slice(0, location.href.lastIndexOf("/")),
            main: "app"
        }]
    });

    require(["app", "dojo/ready"], function (App, ready) {
        return ready(function () {
            dojoConfig = {
                "modulePath": "",
                "baseURL": location.href.slice(0, location.href.lastIndexOf("/")),
                "theme": "default"
            };
            return App.initialize();
        });
    });

}).call(this);

Any thoughts?