I'm using GOLAND and import a package by go mod vendor.
It works good with compiling and building.
I can find types under this package other than the problematic file
I can't find any types defined in the problematic file
I've tried invalidate caches and restart the IDE, however it still not works.
I've find out why. Golang is failed to recognize file larger than 4.19M. Can change the file size limit accroding to https://youtrack.jetbrains.com/issue/GO-5029
Related
I am unable to have my screenshot automatically embed itself into the RobotFramework log file after my test is run. I am using:
SikuliX 1.1.4
RobotFramework 3.0.4 JAR distribution (placed in C:\Users[user]\AppData\Roaming\Sikulix\Extensions
I am able to run my simple test and also have a report/log kicked out - along with a screenshot. The only trouble is that the screenshot is not visible in the log file when viewed in a browser (tried Chrome and FF).
This is my code as written in Sikuli:
runScript("""
robot
*** Settings ***
Library Screenshot
*** Test Cases ***
Try to take a screenshot
Take Screenshot mypic 80%
""")
My folder where the logs are outputted looks like this after the test is run:
./log.html
./mypic_1.jpg
./output.xml
./report.html
./test2.robot
So far, all I have come across when searching the net is that the embed should 'just happen automatically' when using the 'Take Screenshot' keyword.
I have not tried this scenario with RobotFramework by itself - I think that may be my next step, but hoped someone would have an easy solution since I am wanting to use these two packages together. I am wanting to leverage Sikuli to help with my GUI intensive tests and RF for its' reporting and screenshotting capability.
I also had a similar problem with Sikurix 1.1.4 (with RF 3.0.0)
When overwriting the Robot directory of Robot Framework 3.0.4 in "C:\Users\xxxx\AppData\Roaming\Sikulix\Lib\robot", images are now embedded in Log.html.
Even though the comment made by temp temp didn't solve my issue right away, it did put me on the right track. After copying over the pip installed version of RF as mentioned in the comment, I removed the RF JAR file from my Extensions folder (not even sure why I tried this). Once I removed the JAR file, the image started embedding itself in the log. So it seems the combination of the RF version included with Sikuli combined with the RF JAR file was causing my issue.
I am developing a package and I would like to know what is the best way to execute a script at installation time.
Essentially I want to make sure that third-party tools are installed,
retrieve them when I can and raise an error if some dependency is missing.
I am not referring only to R packages, but also to system-wide headers, fonts and similar dependencies.
What is the best strategy to follow in this case?
Scripts to be run before installation should be placed in an executable file called configure (will be executed on Linux/Unix/Mac computers) or in a file called configure.win (will be executed in Windows computers).
I've been working on a program called RoboJournal for a long time. The next release has full documentation included; Whenever the user presses F1 or clicks the Help item in the RoboJournal program, the help file is displayed in Qt Assistant (way classier than simply opening a browser window to some online documentation).
In its base form, the documentation consists of lots of loose HTML and image files included in the source package. These loose files are supposed to be compiled into a QCH compiled help file and QHC collection file during build time so Qt Assistant can display the documentation properly. On Windows, this was fairly easy because I was able to write a batch script to automate the entire build process (including compiling the documentation and moving the output files to the right place).
On Linux, it's a bit more complicated. True, I could write a Bash or Perl script that compiles the documentation along with the rest of the program but I have no guarantee that the people who will eventually create my app's Debian packages from the source package I give them will use the script. The source package is used to create all the Debian packages so everything has to work flawlessly with the standard build procedure (or the source package is worthless). Therefore, I need the compile process to produce the same results whether the user runs the script or not. As it is now, the user has to build and install the documentation manually. Surely there's some way to automate this.
Is it possible to have Qmake add instructions to run qcollectiongenerator to the makefile (in order to build my application's help files) so it gets handled properly during the "make" step? That way, the QHC and QCH files will be ready to install to their proper locations (in my case, /usr/share/doc/robojournal-0.4.1) along with everything else when the user runs "make install". I've considered compiling the QCH and QHC files in advance and providing them in the source package but the whole point of building from source is to be able to re-create the entire app from its base components.
I know I probably have to add additional instructions to my .PRO file but I’m not sure what or how. I've found something that looks promising (http://www.qtcentre.org/archive/index.php/t-49484.html) and gives me hope that it's possible for Qmake to do what I need but I’m not sure how applicable those instructions are to my situation. Do I have to create a PRI file just for this or can I add the instructions directly to the main project file?
You can try to use the QMAKE_POST_LINK variable:
QMAKE_POST_LINK += build_help.sh
P.S.
I have no guarantee that the people who will eventually create my
app's Debian packages from the source package I give them will use the
script.
I think this is really not your problem :) It's up to them to properly build the package.
I Apologize if this question has already been asked. i can't seem to find it anywhere if it has.
I have a custom build script use to syntax check some php files and upload them to a server, and this is executed as a part of the build process. since this script is used to parse inline php statements (embedded in objective c blocks using macros) it's fairly critical this script happens on each build. the actual execution is working fine, i'd just also like to be able to open a particular file when there is an error, and locate the cursor in the approximate location.
i have found that since xcode is configured on my system to open .php files by default (not sure if that's the norm or if i did it manually at some point), using
open filename.php
in a shell script opens the file.
i'd like to be able to specify the line number too.
eg something along the lines of
open filename.php --args --jump-to-line 1234
(--args is a switch for "open" meaning pass the arguments on to Xcode)
any ideas?
You can use the xed command. Only works for Xcode 3 though, not other editors. For Xcode 4, try this
See man xed
I am running mxmlc in the command-line with -incremental=true. Flex is building the cache file using a checksum the first time. Subsequent compilations fail with this message:
Failed to match the compile target with path_to_cache/projectname_329043.cache. The cache file will not be reused.
path_to_cache exists
the cache file exists in path_to_cache
the compiler is not trying to create a new cache file, so I assume it is generating the same checksum
My environment:
Flex 3.0
Mac - OSX 10.4.x
I just ran across this issue myself and after not finding the answer anywhere on the web, I bashed my head against mxmlc in practically trail-and-error until finding the answer. In my case, I was regenerating the flex config xml file each time I compiled from within ant. It turns out that this is the error you get in the case where it thinks the config has changed. You can test this by simply touching your config file and running against unmodified sources. So, if the timestamp is changing on your flex config.xml between compiles, that is likely the culprit.
It could be a permissions issue. Have you tried running with sudo? I wouldn't recommend doing that permanently, but if using sudo makes the error message go away, then you know it's a permissions issue; and you can move on to the proper way to resolve it.
You could also try going into Disk Utility and doing a check/repair of disk permissions. OSX has been notorious for needing this done occasionally.