A model glue site we use had to be moved to another physically different location. I updated all the paths in ModelGlue.xml, ColdSpring.xml and other specific files, but I keep getting the following error. Note: the current physical path is jmc.divisions.medical_oncology.admin.controller.Controller
Could not find the ColdFusion Component or Interface jmc.medical_oncology.admin.controller.Controller.
Ensure that the name is correct and that the component or interface exists.
The error occurred in E:\Inetpub\framework\ModelGlue\unity\loader\XmlConfigurationLoader.cfc: line 234
Called from E:\Inetpub\framework\ModelGlue\unity\loader\XmlConfigurationLoader.cfc: line 83
Called from E:\Inetpub\framework\ModelGlue\unity\loader\FrameworkLoader.cfc: line 98
Called from E:\Inetpub\framework\ModelGlue\unity\ModelGlue.cfm: line 116
Nevermind! Apparently, the system held onto some app-level caching for almost 48 hours. It finally works now.
Related
I am trying to automate an Excel dashboard using Openpyxl v2.3.2 . I'm using a jupyter notebook (Anaconda 4.11) to run my code using Python 2.7.
I have an existing spreadsheet that I am trying to alter and then save. After some playing around I noticed it wasn't saving properly, so I took each sheet (one by one) into a fresh spreadsheet and tried saving it again. I noticed it was throwing the same error every time. The code I'm running is below (pretty simple)
import openpyxl as xl
TVXL = xl.load_workbook('Dashboard.xlsx')
TVXL.save('TVXL.xlsx')
Which returns the error
TypeError: Argument must be bytes or unicode, got 'bool'
The most pertinent part of the full error message is:
C:\Users\v7736101\AppData\Local\Continuum\Anaconda2\lib\site-packages\openpyxl\writer\styles.pyc in write_table(self)
32 self._write_fonts()
33 self._write_fills()
---> 34 self._write_borders()
35
36 self._write_named_styles()
C:\Users\v7736101\AppData\Local\Continuum\Anaconda2\lib\site-packages\openpyxl\writer\styles.pyc in _write_borders(self)
66 borders_node = SubElement(self._root, 'borders', count="%d" % len(self.wb._borders))
67 for border in self.wb._borders:
---> 68 borders_node.append(border.to_tree())
69
70 def _write_named_styles(self):
C:\Users\v7736101\AppData\Local\Continuum\Anaconda2\lib\site-packages\openpyxl\descriptors\serialisable.pyc in to_tree(self, tagname, idx, namespace)
97 del attrs[key]
98
---> 99 el = Element(tagname, attrs)
100
101 for child_tag in self.__elements__:
lxml.etree.pyx in lxml.etree.Element (src\lxml\lxml.etree.c:75395)()
apihelpers.pxi in lxml.etree._makeElement (src\lxml\lxml.etree.c:16379)()
apihelpers.pxi in lxml.etree._makeElement (src\lxml\lxml.etree.c:16236)()
apihelpers.pxi in lxml.etree._initNodeAttributes (src\lxml\lxml.etree.c:18647)()
apihelpers.pxi in lxml.etree._addAttributeToNode (src\lxml\lxml.etree.c:18846)()
apihelpers.pxi in lxml.etree._utf8 (src\lxml\lxml.etree.c:30113)()
TypeError: Argument must be bytes or unicode, got 'bool'
The top error indicates to me that there is something wrong (or incompatible) with the border formatting but after playing around with some of the border styles I can't seem to fix it.
Here's a screenshot of the document I'm trying to save.
screenshot of daily calls that feeds into the dashboard, one of 5 similar tabs
Other information:
Dashboard.xlsx is unaffected (presumably as it is garbage collected if I restart the kernel without saving the changes) but the output doc TVXL.xlsx is corrupted and cannot be opened.
the error that is thrown is in serialisable.pyc but I can't tell from reading it what that function does or how it feeds through.
in the screenshot of my spreadsheet I have added dummy data as it's sensitive information
Hopefully you can help me fix this as it's the first real demonstration of how powerful python is within my area of the business.
Thanks in advance.
I have reinstalled emacs 24.2.50 on a new linux host and started a new dotEmacs config based on magnars emacs configuration. Since I have used CEDET to some success in my previous workflow I started configuring it. However, there is some strange behaviour whenever I load a C++ source file.
[This Part Is Solved]
As expected, semantic parses all included files (and during the initial setup parses all files specified by the semantic-add-system-include variables), but it prints this an error message that goes like this:
WARNING: semantic-find-file-noselect called for /usr/include/c++/4.7/vector while in set-auto-mode for /usr/include/c++/4.7/vector. You should call the responsible function into 'mode-local-init-hook'.
In the above example the error is printed for the STL vector but a corresponding error message is printed for every file included by the one I'm visiting and any subsequent includes. As a result it takes quite a long time to finish and unfortunately the process is repeated any type I open a new buffer.
[This Problem Is Solved Too]
Furthermore it looks like the parsing doesn't really work as when I place the point above a non-c primitive type (i.e. not int,double,float, etc) instead of printing the type's definition in the modeline an error message like
Idle Service Error semantic-idle-local-symbol-highlight-idle-function: "#<buffer DEPFETResolutionAnalysis.cc> - Wrong type argument: stringp, (((0) \"IndexMap\"))"
Idle Service Error semantic-idle-summary-idle-function: "#<buffer DEPFETResolutionAnalysis.cc> - Wrong type argument: stringp, ((\"fXBetween\" 0 nil nil))"
where DEPFETResolutionAnalysis.cc is the file & buffer I'm currently editing and IndexMap and fXBetween are types defined in files included by the file I'm editing/some file included by the file I'm editing.
I have not tested any further features of CEDET/semantic as the problem is pretty annoying. My cedet config can be found here.
EDIT: With the help of Alex Ott I kinda solved the first problem. It was due to my horrible cedet initialisation. See his first answer for the proper way to configure CEDET!
There still remains the problem with the Idle Service Error (which, when enabling global-semantic-idle-local-symbol-highlight-mode, occurs permanently, not only when checking the definition of the type at point).
And there is the new problem of how to disable the site-wise init file(s).
EDIT2: I have executed semantic-debug-idle-function in a buffer where the problem occurs and it produces a ~700kb [sic!] output. It looks like it is performing some operations on a data container which, by the looks of it, contains information on all the symbols defined in the files parsed. As I have parsed a rather large package (~20Mb source files) this table is rather large. Can semantic handle a database that large or is this impossible and the reason of my problem?
EDIT3: Deleting the content of ~/.semanticdb and reparsing all includes did the trick. I still need to disable the site-wise init files but as this is not related to CEDET I will close this question (the question related to the site-wise init files can be found here).
You need to change your init file so it will perform loading of CEDET only once, not in the hook that will be called for each .h/.hpp/.c/.cpp files. You can change this config as the base, and read more in following article.
The problem that you have is caused because Semantic is trying to analyze header files, and when it tries to open them, then its initialization routines are called again, and again...
The first problem was solved by correctly configuring CEDET which is discribed on Alex Ott's homepage. His answer solves this first problem. The config file specified in his answer is a great start for a nice config; I have used the very same to config CEDET for my needs.
The second problem vanished once I updated CEDET from 1.1 to the bazaar (repository) version, which is explained here and in Alex' article. Additionaly one must delete the content of the directory ~/.semanticdb (which contains the semantic database and was corrupted I guess).
I'd like to thank Alex Ott for his help and sticking with me throughout my journey to the solution :)
I have uploaded my data
genotype1_large_ind_large.txt
phenotype1_large_ind_large_1.txt
to the S3 system, and in the EMR UI, I set the parameter like below
RunDear.run s3n://scalability/genotype1_large_ind_large.txt s3n://scalability/phenotype1_large_ind_large_1.txt s3n://scalability/output_1phe 33 10 4
In my class RunDear.run I will distribute the file genotype1_large_ind_large.txt and phenotype1_large_ind_large_1.txt to the cache
However, after running the EMR, I get the following error:
java.io.FileNotFoundException: File does not exist: /genotype1_large_ind_large.txt
I am wondering why there is slash '/' in front of the file name?
how to make it work?
I also tried to use like below, but my program will take -cacheFile as an argument, thus also does not work,
RunDear.run -cacheFile s3n://scalability/genotype1_large_ind_large.txt#genotype.txt -cacheFile s3n://scalability/phenotype1_large_ind_large_1.txt#phenotype.txt s3n://scalability/output_1phe 33 280 4
I finally realize it is the problem of using the filesystem, so I add a code in the program like below
FileSystem fs = FileSystem.get( URI.create("s3://scalability"), conf);
I have a dump of process where the handle count in the process did reached 16 million handles (which is the maximum allowed handles per process). Hence the process got hanged.
From dump (This is second dump where the handle count is high but not max limit.) I get following data :
53778 Handles
Type Count
None 2
Event 238
Section 3
File 84
Port 16
**Directory 53120**
Mutant 35
WindowStation 2
Semaphore 151
Key 42
Token 4
Process 1
0:000> !handle 9735 f
Handle 00009735
Type Directory
Attributes 0x10
GrantedAccess 0x1:
HandleCount 53575
PointerCount 53788
Name \GLOBAL??
No object specific information available
There are many such handles open with Name : \GLOBAL?? and type Directory. Here I want to know in what scenarios do we see this particular handle being created?
Is there any way to know the code where the leak is occurring from the full dump?
I believe you are using WinDBG.
If I am not wrong, "\GLOBAL??" indicates that your symbolic link is relates to all sessions. On Win2K it was "\??". Symbolic links and Handles can be local to a session. For an example: I can create a Mutex handle and make it local to each terminal service sessions. This can be done by prefixing the mutex name explicitly with a "Global\" or "Local\" to create the object in the global or local session name space.
http://msdn.microsoft.com/en-us/library/ms682411(VS.85).aspx
Is this reproducible? If so, you should try the !htrace extension.
In Windows NT, the old DOS filesystem is essentially a set of shortcuts. This is necessary because it's a multi-user filesystem. Your H:\ drive might differ from someone elses H:\ drive. Hence, both are implemented as shortcuts or symbolic links.
SysInternals Process Monitor has a handle viewm and IIRC can capture a stack dump for each file operation. That of course adds up quickly; you'll need to learn its filters.
I'm trying to roll my own implementation of IShellBrowser because I need to have a more full-featured File Open and Save As dialog than Windows allows that is compatible with XP (and ideally with W2000)*
At this point I need to add the standard toolbar that you see in upper right of the dialog (manifest styles for XP and earlier) - a back button, a parent-folder button, a new folder button, and a "tools" drop down.
But so far I've been unsuccessful in finding these icons / images. I've looked in USER32.dll, comdlg32.dll, comctl32.dll, but haven't found anything that quite matches.
I could simply take screen shots of an application where I can find them - but it would possibly more useful to know where they come from, so I can access the various versions of these buttons (high rez, low rez, shallow color, deep color, etc.).
Any ideas?
[Edit: I need it to be compatible with Vista & Windows 7 also. Its just that starting with Vista, they broke the old common dialog model, and their new model is brain-damaged IMO - I no longer have enough access to the state of the dialog to perform the necessary duties that our dialogs used to do - so we are forced to approach the problem from another angle]
Try shell32.dll, in Windows\System32.
I found this table containing a list of system files containing embedded icons. Perhaps you might find what you're looking for in one of them:
Filename Number of Icons
-----------------------------
compstui.dll 99
comres.dll 38
cryptui.dll 20
csc.dll 22
dsuiext.dll 35
explorer.exe 18
iexplore.exe 23
inetcpl.cpl 34
inetcpl.dll 14
mmcndmgr.dll 129
mmsys.cpl 40
moricons.dll 140
netshell.dll 157
ntbackup.exe 26
pfmgr.dll 38
progman.exe 48
setupapi.dll 37
SHDOCVW.DLL 35
shell32.dll 238
stobject.dll 31
wiashext.dll 23
wmploc.dll 60
xpsp2res.dll 19
Try looking in imageres.dll. You should find most of the image resources for Vista there.
vista style
http://www.freeiconsweb.com/Vista-Style-Software-Icons-Set.html
not windows but really complete
http://www.freeiconsweb.com/Webmaster-Pixel-Icon-Set.html
just the download link is at the bottom
http://www.freeiconsweb.com/Vista_Folders_Icons.html
If you just ask the shell for it's image list, it will give it to you.
Shell_GetImageLists()
And then you can use whichever ones you want. Yay.
Edit: Looks like SHGetImageList() might be the more-better way of doing it.
Use your own icons. Resource Ids in Shell32.dll are not documented and can change in a Windows Update.
Windows has 3 "standard" toolbars. From CommCtrl.h (source):
Standard: (IDB_STD_SMALL_COLOR)
View: (IDB_VIEW_SMALL_COLOR)
History: (IDB_HIST_SMALL_COLOR)
The indexes for the images are documented, and can be found in CommCrtl.h. For example, the Standard image indexes are:
STD_CUT (0): Cut operation.
STD_COPY (1): Copy operation
STD_PASTE (2): Paste operation.
STD_UNDO (3): Undo operation.
STD_REDOW (4): Redo operation. (yes, typow)
STD_DELETE (5): Delete operation.
STD_FILENEW (6): New file operation.
STD_FILEOPEN (7): Open file operation.
STD_FILESAVE (8): Save file operation.
STD_PRINTPRE (9): Print preview operation.
STD_PROPERTIES (10): Properties operation.
STD_HELP (11): Help operation.
STD_FIND (12): Find operation.
STD_REPLACE (13): Replace operation.
STD_PRINT (14): Print operation.
You load a standard set of images into a toolbar's imagelist by sending the TB_LOADIMAGES message:
// hWndToobar is the window handle of the toolbar control.
SendMessage(hWndToolbar,
TB_LOADIMAGES,
(WPARAM)IDB_STD_SMALL_COLOR,
(LPARAM)HINST_COMMCTRL);