# No extensions in extension manager

**URL:** <https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705>\
**Category:** Support\
**Created:** [August 8, 2018, 11:49am UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705 "2018-08-08T11:49:59Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![torquil](https://avatars.discourse-cdn.com/v4/letter/t/e79b87/32.png) [@torquil](https://discourse.slicer.org/u/torquil)\
**Post date:** [August 8, 2018, 11:49am UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/1 "2018-08-08T11:49:59Z")

</div>

Hi! After installing Slicer 4.9.0 2018-08-07, there are no extensions listed in the extension manager.

In the application settings, the “Extensions server URL” is [http://slicer.kitware.com/midas3](http://slicer.kitware.com/midas3), which I have not changed.

In the extensions manager, I get the message: “No extensions found for win:64-bit, revision: ‘27339’. Please try a different combination”.

If I go to [https://slicer.kitware.com/midas3/slicerappstore](https://slicer.kitware.com/midas3/slicerappstore) with a web browser, I get the same error.

This is the whole Slicer error log:

“Session start time …: 2018-08-08 13:37:45  
Slicer version …: 4.9.0-2018-08-07 (revision 27339) win-amd64 - installed release  
Operating system …: Windows / Professional / (Build 9200) - 64-bit  
Memory …: 16262 MB physical, 16262 MB virtual  
CPU …: GenuineIntel , 8 cores, 8 logical processors  
VTK configuration …: OpenGL2 rendering, TBB threading  
Developer mode enabled …: no  
Prefer executable CLI …: yes  
Additional module paths …: (none)  
Popen([‘git’, ‘version’], cwd=C:\Program Files\Slicer 4.9.0-2018-08-07, universal\_newlines=False, shell=None)  
Popen([‘git’, ‘version’], cwd=C:\Program Files\Slicer 4.9.0-2018-08-07, universal\_newlines=False, shell=None)  
Scripted subject hierarchy plugin registered: Annotations  
Scripted subject hierarchy plugin registered: SegmentEditor  
Scripted subject hierarchy plugin registered: SegmentStatistics  
Switch to module: “Welcome”  
An OpenGL Core Profile was requested, but it is not supported on the current platform. Falling back to a non-Core profile. Note that this might cause rendering issues.”

Best regards,  
Torquil Sørensen

---

<div class="post-metadata">

**Author:** ![Sunny](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@Sunny](https://discourse.slicer.org/u/Sunny)\
**Post date:** [August 8, 2018, 10:29am UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/2 "2018-08-08T10:29:22Z")

</div>

I am facing this same problem (“No extensions found for win:64-bit, revision: ‘27339’. Please try a different combination”) with the latest Nightly build which I downloaded from the Slicer homepage.

Appreciate your help, thanks!

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [August 8, 2018, 10:50am UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/3 "2018-08-08T10:50:14Z")

</div>

Indeed, for some reason there are only extensions for Linux and Mac at this moment. It is possible that the factory computers have not finished the builds yet. You can wait to see if this is true, or download yesterday’s nightly that looks OK on the dashboard:  
[http://download.slicer.org/?offset=-1](http://download.slicer.org/?offset=-1)

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [August 8, 2018, 1:49pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/4 "2018-08-08T13:49:02Z")

</div>

note: I moved two posts in to this thread from an old one ([No extensions for latest nightly](https://discourse.slicer.org/t/no-extensions-for-latest-nightly/865/5))

@torquil please see suggestion above.

---

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [August 8, 2018, 2:01pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/5 "2018-08-08T14:01:14Z")

</div>

Windows extension builds are now coming up from the factory machine. It seems to be later than they have been in the past. I will take a look at the factory system log to see if something weird happened. If not, perhaps we should consider moving the factory build start earlier.

---

<div class="post-metadata">

**Author:** ![torquil](https://avatars.discourse-cdn.com/v4/letter/t/e79b87/32.png) [@torquil](https://discourse.slicer.org/u/torquil)\
**Post date:** [August 9, 2018, 11:03am UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/6 "2018-08-09T11:03:09Z")

</div>

Thanks people, it is working again now.

---

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [August 9, 2018, 2:58pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/7 "2018-08-09T14:58:37Z")

</div>

@jcfr

So I think we should consider moving the start time earlier for the nightly build, or changing up the build order. Currently, we build the stable extensions before the preview (except if its Sunday …?). Each build (slicer, stable extensions, preview extensions) appears to be taking ~4 hrs according to the logs, so most days the preview extensions don’t finish until late morning.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 9, 2018, 3:33pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/8 "2018-08-09T15:33:06Z")

</div>

This was originally done to accommodate @fedorov. See [Slicer/DashboardScripts@41b143d1f](https://github.com/Slicer/DashboardScripts/commit/41b143d1fa3e9c665498918f3361c00deb8938ca) for more background

Also, for either the Preview or Stable extension, considering that some extension used branches like `origin/master-XY` or `origin/master`, we have no way of knowing if we can skip the build of the index or not.

We could also update the nighty build time. It is currently set in [Slicer/CTestConfig.cmake](https://github.com/Slicer/Slicer/blob/master/CTestConfig.cmake) as `3:00:00 UTC` (`23:00 EDT`). May be we could start all nightly build at (8pm) `20:00 EDT` (`0:00:00 UTC`) ?

For reference, the order of build is specified here:

> <https://github.com/Slicer/DashboardScripts/blob/cbacb3abab4aff9e6e577d23d2716c793a299766/overload.bat#L36-L44>

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 9, 2018, 3:37pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/9 "2018-08-09T15:37:22Z")

</div>

> [@jcfr](#):
>
> This was originally done to accommodate @fedorov

@jcfr, according to @Sam_Horvath:

> [@Sam\_Horvath](#):
>
> Currently, we build the stable extensions before the preview

However, the comment from the commit you mentioned states that it should implement the behavior suggested by Sam:

> Lacking automatic detection of the 4.5 extensions index changes and  
> building of the modified extensions only, it is proposed that the order  
> between 4.5 and nightly is changed manually on as needed basis. It is  
> expected that nightly builds will be changing at a faster pace than 4.5,  
> thus it is natural to have nightly built in the first place.

So I think something changed since that commit, if indeed stable extensions are built before the preview.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 9, 2018, 3:51pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/10 "2018-08-09T15:51:26Z")

</div>

Another option would be to show yesterday’s nightly build (…?offset=-1) on the download page. Developers and advanced users would know that a more recent, potentially incomplete build is available for early testing.

---

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [August 9, 2018, 4:20pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/11 "2018-08-09T16:20:30Z")

</div>

The change to building stable before nighlt/preview on weekedays occured here:

> <https://github.com/Slicer/DashboardScripts/commit/d8507c2983659f0293705f613c610160068de333#diff-fa3827b70d282260aba2befb7f945454>

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 9, 2018, 10:41pm UTC](https://discourse.slicer.org/t/no-extensions-in-extension-manager/3705/12 "2018-08-09T22:41:07Z")

</div>

If there is no specific technical reason to build stable extension first, I would change the order to build nightly Slicer core and extensions first.