guys.
I faced to confusing problem.
I use aws(ecr / ecs), and circle ci to deploy.
and using ecs-deploy command.
circle ci deployment has timeouted.
but, deployment has been successful until last week(Friday).
we changed any modules kotlin class and anything after last successful deployment.
then, our deployment had get timeouted.
— what I did —
06/10/2021 module changed and deploy successful
06/17/2021 module changed and deploy failure
————
what happen is this?
is anyone experienced similer problem?
our changes is production module; then I can’t show you it.
Sorry we can't show you any evidence; if you need more infomation, I'll give you as possible.
I think our changes cause this problem;
but it is small changes.
I have no idea to solve this problem.
if you had got similer situation, please tell me what solution it.
Thanks.
Related
I'm facing this No such module 'SomeModule' error in an XCode solution that I've inherited from some other developers. Initially the error is No such module 'ObjectMapper', but I find that if I swap the position of that line with the one below, it becomes No such module 'Alamofire'.
I've tried all the simple things suggested on this site (and others), making sure I'm opening the .xcworkspace file, deleting everything and re-installing (derived data, the whole Pods directory, etc.), updating cocoapods, etc.
I suspect that what's actually going on is that either the pods themselves aren't building, but for some reason the errors there are making their way to XCode's obtuse errors list, or that they are building but somehow not being linked correctly.
This is actually a project I've inherited from some other developers, so it's hard to know what weird or wonderful configuration they've done to break things. They are using an approach that I've not seen before where there's 3 build schemes for different environments (in this case Develop, Stage and Prod) then this kind of parent scheme for all the other three.
I've also tried going to 'Manage Schemes' then ticking the 'Show' checkbox for the Pods-Sunflower project. When I try to build just that project, I get a bunch of errors (mainly for Facebook, Google and Realm pods) that say things like:
Unable to load contents of file list: '/Target Support Files/FBSDKCoreKit/FBSDKCoreKit-xcframeworks-input-files.xcfilelist'
I don't expect anyone will be able to provide me a set of steps on how to solve this issue (I mean, that would be great), but I am hoping that someone can help me find ways to just work out what the problem is here, like:
How can I verify that all the separate pods are actually building?
Is there some folder where I can see all the built pods?
When you get a No such module 'SomeModule' error, where is Xcode trying to find the modules (like, in the file system? where?)
Thanks. I know this is one of those perennial issues, appreciate any advice.
The solution which worked for me was:
First thing i do when i got project from another developer is make a copy of pods and completely delete following files
Podfile
Pods folder
Podfile.lock
xcworkspace
In case you already once use that same project try deleting derived data
After deleting pods, reinstall pods and open project and let xcode do indexing of your project and after indexing look left side where warnings and errors shows, In there sometime you just have to just click and update or convert whatever xcode suggesting.
Note: - Sometimes doing same thing doesn't work try changing sequence because its xcode sometimes become dumb. Also try restarting
Honestly in these situation all i do is hit and try.
But above steps generallt works for me.
I apologize if this has been answered in another post, I can't seem to find it if it has. Anyway, I have built a back end utility for a fellow streamer friend of mine but I can't seem to figure out what I'm doing wrong when it comes to deploying it. This is a project that will be expanded on in the future, and possibly have more windows form projects. So here is what I am running into (With Pictures):
Here is my solution explorer with the projects:
When I go to build the deployment I've tried making all the projects "outputs" and got this error. Thinking it was there were too many Project Outputs I changed it to where the startup project would be the output and the others would be either source or content files. Still got these errors. Here is the File System Setup:
And when I go to run the build to create the deployment, here are the errors I receive:
I don't know/don't see what I am doing wrong here and would very much appreciate a point in the right direction. Thank you all so much in advance.
Check your updates. I remember there is an option to review or check the status of latest updates.
I found this article about that issue but it looks like a general error with updates or the installation
It is not too long but maybe it does not help. I hope it helps, good luck
When I try to run a project (Only this project and others work fine), it always stucks at the publishing(copy and paste point). It can work perfectly fine until one time I(not sure) accidentally click incrementally publish and then stop it forcefully. Then this problem persists. I try to clean the server and also try to empty the domain folder but none of them works. It is like very strange bug.
I don't want to try creating a new domain since I have add JAAS configuration and JNDI in this domain. Or can anyone tell me how to import the configuration into a new domain?
If I wait long time for it to finish, random problem occurs:
The problem is other project can be run in debug and this project also can previously. It is all just out of sudden when I forcefully stop some process in eclipse tho I am not sure whether it is because of.
This is so annoying and can anyone give some constructive advice? Thx a lot!
Anyone encountering similar situation and sharing his/her experience here will be appreciated. It does not have to be exactly same and any lead or hint are welcome, please.
Actually, I think it is definitely an eclipse bug.
Creating a new workspace and importing all the related projects and glassfish servers can solve the problems though I don't know the actual reason.
I've a question about the upgrade of Kentico V11 --> V12.
After the correct migration, I got these errors messages (20 times).
When I'll check the website, all design are blank. I just have the menu link without design.
I already re-sign the macro.
I've check all version of CMS.*.dll --> V12.
Do you have any idea for this blocking issue ?
Kind regards !
The error message
did you resign all the macros after the upgrade?
Typically there are a few things which can cause this. First being the hash salt changed in the web.config. If this changed, you need to resign your macros. Even if your hash salt hasn't changed the easiest thing is to go to System > Macros and check both boxes and resign all the macros.
The second thing, highly unlikely, would be you need to clear your browsers cache. Sometimes JS errors arise from the upgrade and cause problems with the system not running code.
What is the entire error message? What is the source URL and where is the code which is throwing the error? Isn't it possible it is coming from some transformation? I am asking since there were some API changes and the GetFileUrlFromAlias method was removed. See the API changes. You may want to use the Code upgrade tool to detect such changes.
I just give you a feedback.
The problem seems to be during the migration...
Due to the VPN low speed, that possible there was some timeout for many steps. (mandatory because the COVID19 =( )
I just get the database on my local computer and redone the migration, and all seems to be good now.
Thank you for your help on this subject :)
Take care of you in this period !
I am looking to override protractors click method because we are getting some sporadic test failures due to some intermittent problems in our app. We are looking to override the click so we can add some custom functionality so overcome this issue and all our automation scripts to continue to run despite this issue.
Tests are to test if everything in your app is working as it should. If something causes tests to be unreliable you should refrain from hacking in a temp workaround and instead mark a test as pending (xit instead of it) and try to fix the issue either in the tests or in the client side to make it reliable again. Pending tests will be listed in the final report and will give you a reminder to test it manually or nag you about fixing it properly :)
If you provide more information about the nature of the problem maybe we could come up with an idea to solve it?