I am using https://github.com/nuxt-community/sentry-module which in turn is also pushing the code for source map to work (internally https://github.com/getsentry/sentry-webpack-plugin).
I have enabled the integration for gitlab. I have created a .sentryclirc file with project, org and token as variables to fill.
The token has proj:read proj:write and proj:release permissions enabled.
This is my config for sentry webpack
release: pkg.version, // 1.0.0
// dryRun: isDev,
setCommits: {
repo: "company_name/project_name",
auto: true,
},
I am using my SENTRY_DSN properly.
I am able to push a source map under release 1.0.0, and when I go to an issue it is tagged as 1.0.0.
Under the release tab, I get the message Releases aren't 100% set up and redirects me to tag an error. I don't really understand what it is suggesting I do. The config should just use the recent commit.
I look under the issues tab and the issues are tagged with the version 1.0.0 and say it is linked to it. Yet, the minified version is still showing up.
Looking around I click on the link View new issues seen in this release in the stream to see what issues I have filtered for that version. I looked at the query in the url and the query is first-release-1.0.0.
I am not sure why it defaults to filtering it like that.
This leads me to believe that the release I am deploying isn't by synced up with the issues that sentry is pushing.
Related
I have installed Alfresco using docker images as explained in this Angel Borrow's github repos. All goes fine.
But some translation key are not processed. On this image you can see that the translation key "LOGIN.LABEL.USERNAME" is not replaced by it' value.
There are several other issues like that on some popups in ADW (Alfresco Digital Workspace) app.
What is the best way to fix that?
PS : The same localization issues also exist on alfresco cloud.
The first think to check is if you have an adBlock extension activated on your browser page, if it's the case, disable adblock for Alfresco digitale workspace and reload.
You can debug error by using developer tools on your browser (F12)
in network you can see errors related to labels blocked and have more details.
O.
I have successfully installed an instance of Read-the-Docs locally and integrated with the public instance of Github.
I have successfully imported and built three projects (even a private one after some minor code alterations, though it is not normally supported). One of these projects is the default template project that RTD suggests for testing.
I can view the docs in the machine where the RTD instance is installed. However, when I press the green "View Docs" button a 404 status code occurs. Supposedly, the docs should be under /docs/template/en/latest. As you can see there is no docs prefix in the available URLs:enter image description here
My assumption was that the endpoints regarding the docs are updated dynamically and the Django application reloads, yet I have been searching the code and I have not found anything to support this assumption.
My question is, if anyone has ever come upon this issue and how / if it was resolved?
Explanation
I'm having an issue with Workbox where my website doesn't update when a file's content is changed, unless I manually clear storage/site data in my browser.
Since v4 release this year, the cleanupOutdatedCaches, which is in my code, should take care of this, but the problem persists.
Example
I created this website to exemplify. Once you access it, Workbox will install the service worker, but if I change, for example, test1 to test2, you won't see the change, unless you clear the site data in your browser and refresh.
I also tried only unregistering the sw; it shows the updated version (test2), but when refreshing twice it goes back to the old version (test1).
You can see the website's code in GitHub here.
Thanks in advance,
Luiz.
cleanOutdatedCaches will only clean caches created by older versions of the workbox library. In this case, since you are using the same version fo workbox, the call to this method does nothing.
https://developers.google.com/web/tools/workbox/reference-docs/latest/workbox.precaching#.cleanupOutdatedCaches
Once a particular file is precached by Workbox, it will never attempt to retrieve that file from the network, unless the revision you have specified in the precacheAndRoute call is different from what was previously cached.
Since you changed index.html but not the revision in precacheAndRoute, workbox assumes the file is unchanged. So,what you need to do is to update the precacheAndRoute with a new hash that corresponds to the new version of index.html
You can achieve this by either using injectManifest
https://developers.google.com/web/tools/workbox/modules/workbox-build
or any other build tooling you use.
Edit:
You can invoke skipWaiting programmatically as well
https://developers.google.com/web/tools/workbox/modules/workbox-core#skip_waiting_and_clients_claim
But you do need to use it with caution. Here is one way to do it :
https://developers.google.com/web/tools/workbox/guides/advanced-recipes
The system environment check returned errors. Those errors will affect the functionality and stability of your TYPO3 CMS instance. Please check the install tool "System environment" for all details.
The first image shows the typo3 backend status report error:
Here is the error on browser when I tried to access the frontend of the website:
About the exception you are getting: It seems you stumbled upon a bug which is fixed in latest version 7.6.26. Please update to the latest version. Make sure you follow the correct procedure for updating.
If the problem still occurs, clear the system cache in the install tool.
More general hints:
Always keep your TYPO3 system up to date. Either subscribe to the typo3-announce mailing list or keep track of the channel #announcements in the typo3 slack workspace. That way you will be notified as soon as a new TYPO3 version is released. If you don't have access to the TYPO3 slack workspace yet, register for an invite.
first:
go to Install-Tool and verify that all checks are green or at least yellow.
then:
if you only got a blank screen your system is probably in production mode where no error messages are shown as they could reveal information for abuse.
So configure developer mode in the Install-Tool.
You also may need to remove the exception handler in your typoscript (setup) with:
config.contentObjectExceptionHandler = 0
to get plain php error messages.
activating developermode :
Install Tool
Configuration Presets
Debug Settings
Debug
Activate settings
I am trying to setup a CI server on my Macbook, I have followed the documentation on the apple website up to the point of creating a bot and integrating my build. When I attempt to integrate the build I repeatedly get the following error:
Bot Issue: error. Build Service Error.
Issue: '/Library/Developer/XcodeServer/Integrations/Caches/14a8ea2a72904f1abcecd38b1c02196b' exists and is not an empty directory (-4).
Integration Number: 13.
Integration URL: https://DavidMcQueens-MacBook-Pro-2.local/xcode/bots/BF817C9/integrations
Description: '/Library/Developer/XcodeServer/Integrations/Caches/14a8ea2a72904f1abcecd38b1c02196b' exists and is not an empty directory (-4).
I have manually deleted the folders in this location, as well as changing the permissions incase the server was having issues writing. Each time I run, I receive the same error. Even after I have deleted the folder so it is empty before the integration.
Does anyone have any ideas on how to solve this issue? I have built my iOS application in Swift (which I believe should still work with the CI server)
I am running OSX Server 4.0 and the latest version of XCode.
I followed Apple's documentation for creating bots
Thanks,
EDIT:
After some experimenting and trying different things to see what the issue is, I disabled 2-factor authentication on my GitHub hosting. This appeared to solve the issue, despite the fact that I was generating a specific application key to get around 2-factor. It solved the issue for a small amount of time, and I managed to successfully get the bot to integrate a few times. However it appears to have gone back to its old tricks.
If anyone has any other knowledge on this, or has managed to get it working on their own machines it will be good to know.
So I believe I have solved this issue, the GitHub 2-factor authentication issue looks to be a red herring.
When setting up the bot, there is a section that says "Checkout the repository", I did not do this step because I already had the repository on my local machine and presumed that it would simply create the repository in another location, and server no other purpose.
However, after some investigation this step is very necessary. From what I understand, checking out the repository does create it again in another location, however this is necessary as this new repository is where the Bot's will pull changes into and build in order to perform the tests. I was trying to use the same repo for development and for the Bots, which it did not like.
Creating a clean checkout of the project (on the server), and configuring the bots in that project then allowed me to progress and get everything setup correctly. It comes down to user error. In hindsight, it makes perfect sense to have a separate repo for the bots (this is my first CI server setup), however the error messages were not helpful and I can't remember seeing this emphasised in the setup guide.