(closed) Postman can't be opened properly - postman

I'm trying to open my newly installed Postman when an error occurs which says something like this:
**Could not open Postman**
Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded succesfully after `dexie.open`.
Please try restarting the app. If the issue persists, please refer to http://go.pstmn.io/troubleshoot-could-not-open
As it says, the error really persists. The website above only provides suggestions like "reinstall the app" "upgrade the app", which are not really helpful. And as I dig into the Internet, it occurs to me that such error hardly happens (found nobody have the same question like me).
"IndexedDb" was mentioned in the error message, and I just know (from the Internet) that it's a nosql database provided by explorer. Maybe the problem can be solved by reinstalling the database, I guess?

I had a similar problem and found this description: https://github.com/postmanlabs/postman-app-support/issues/4897
Short answer is, delete the Postman configs directory at ~/.config/Postman (for Linux) and then try running again. This will delete any saved Postman data you have, but for a newly-installed instance that's not an issue.

Go to installation folder of Postman:
C:\Users\Davoud\AppData\Local\Postman
delete the older version's folder. It fixed my problem. Actually I also deleted update.exe too.

Can you try just by deleting the “Postman” folder or renaming it to “Postman.old” from below two locations and then reinstall the latest version from here and see if that helps?
C:\Users\<user>\AppData\Local and C:\Users\<user>\AppData\Roaming
I tried it as I was facing the same issue and, it solved for me.

Use this: It worked for me.
pkill -fi Postman

For Windows 10 - in my case, I have to:
Open Task Manager and kill/end the Postman application.
Go to %appdata% and search the "Postman" folder.
Inside "Postman" folder, select the "Postman_Config" folder1. Delete it.
Try to open your Postman instance again.
1 The "Postman_Config" folder contained (in my case) another folder called "0" and inside this folder, an "userconfigs.json" file - which only contained these characters:
{}
If you have additional information,please, make a copy of these files in order to have a backup - if needed.

For Windows -
Kill the process that says, postman from the task manager
Run the installer again, it resolved the issue for me.

disable hardware acceleration in the Postman menu in macOS, or the Help menu in Windows or Linux.

I had a similar problem installing Postman when I was on a VPN (on Windows). It started up but then got a popup error saying "TypeError: Cannot read property 'id' of undefined," and a blank white screen afterwards. So I uninstalled it, deleted any Postman folders, turned off the VPN, and re-installed it with no problems! After it installed successfully, I was able to turn on my VPN and had no further issues.
For reference, I had these errors in my C:\Users\<user>\AppData\Roaming\Postman\logs\renderer-requester.log file
[20076][1645655031650][requester][info]["Migrations: Committing IndexedDB upgrade"]
[20076][1645655031665][requester][error]["Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031673][requester][error]["Migration: Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031676][requester][info]["booted - requester"]
[20076][1645655031686][requester][error]["Could not complete migration.",{"name":"TypeError","message":"Cannot read property 'id' of undefined","stack":"TypeError: Cannot read property 'id' of undefined\n at t.default (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1193039)\n at
......

Related

Missing Jenkins Job Information

Recently I restarted my AWS instance and got a new IP address but after I restarted both Jenkins and AWS, the information about my previous jobs was no longer shown in Jenkins.
I checked the path and it still exists in the instance but it is not shown on the web. I tried to create another project and it still created in the same path just that only the newly created project is in. Any suggestions on how to recover my missing projects??
FYI
I have lots of old plugins that mentions "xxx failed to load" so I do not know if that is causing it.
one of my plugins does not match and all those that depends on it will fail to show on the installed section of the plugin. Thus I remove all the plugins by deleting it directly from the plugin folder and check for the working copy that was on my previous version and download the same version of plugins. After which, all the jobs come back on screen

Deleting Team Project in Azure DevOps ends in strange folders in Sourcecode Explorer of VS

Following Azure DevOps documentation, I have deleted a number of projects. The project is removed from the online view but strange folders now appear in VS 2017 source control explorer. These folders contain source code from the deleted projects.
I tried to delete and resync my workspace but the unwanted folders synced again. Can anyone who has seen this behavior advise how i can get rid of them?
br Nico
Edit:
It seems like this is not a new issue. I am able to reproduce this with TFVC projects only. Take a look at this post about how to remove "deleted" team projects. Hopefully that gets you moving in the right direction.
If all else fails... use Git :)
Original:
It seems to me like VS is holding onto some information about the remote and which projects it expects to be there.
You may simply need to refresh the connection in VS.
If the refresh still shows the deleted projects, try removing the server connection completely, and adding it fresh.

Azure DevOps project build returning with log4net error

I'm trying to build a visual studio 2015 dot-net application which has log4net reference in the code.
When I build in Azure DevOps using Nuget restore, Nuget Tool installer, Visual studio build, Publish Build artifacts I am getting an error:
Error CS0246: The type or namespace name 'log4net' could not be found (are you missing a using directive or an assembly reference?) Process 'msbuild.exe' exited with code '1'.
Please someone suggest whether I have to add another agent or make some reference to the package/nuget in Azure DevOps. need details since I'm new to Azure DevOps.
The error message suggests that either the using is missing or the assembly could not be found, meaning that probably the nuget restoration has failed.
If you can't figure out the issue by looking at the log, the first step should be to set system.debug to true, then you might get more info about what the issue might be.
My first instinct when I don't know what's going on would alsways be to look into the s folder of an agent but I don't have experience with hosted agents and as far as I know you cannot access the working folder of a hosted agent.
So as a workaround (only if everything else fails) I would suggest to zip the s folder ("$(Build.Sources)") or special parts of it into the a folder ("$(Build.Artefacts)") and publish that zip as an artefact. Then you can download it and look at it in great detail, e.g. look at the packages folder or open the solution and see why it doesn't compile.
Problem was partly solved as there was .gitignore and .gitattribute files in my source directory which i guess had entries to ignore the third party .dlls like log4net and several folders which were not getting checked-in when i did vsts push. But there arose some other errors in vsts build now which i am trying to figure out. I will create a new thread for that.
Thanks.
For some reason I lost ability to see it in
Tools -> Manage Nuget Packages for Solution
However from the docs
I used
Install-Package log4net
in Package Manager Console
That solved the issue.
Previously I had noticed the yellow triangle against log4net In Manage Packages For Solution, and may have tried removing it via Nuget.
However it was still showing as a reference

Why Google Maintenance broke PostreSQL in project 763485212249?

yesterday on our tahmeel-postgresql-prod instance there was a maintenance update https://dzwonsemrish7.cloudfront.net/items/0t253L361v411g060n26/Image%202018-10-09%20at%201.46.38%20PM.png
Thanks to that update, we started to see errors ERROR: could not access file "$libdir/postgis-2.3": No such file or directory when we tried to use postgis https://dzwonsemrish7.cloudfront.net/items/2G371k0D2j1K1J2x3q0P/Image%202018-10-09%20at%201.48.04%20PM.png
Here you can see logs from the database, problems started to arise when the maintenance started https://dzwonsemrish7.cloudfront.net/items/2g3a28171l1v3R2H2838/Image%202018-10-09%20at%201.53.09%20PM.png
so what we did was to clone the db as tahmeel-postgresql-prod-clone and switch the app to use new db.
My question is -- what happened and why?

Sitecore 8 Path Analyser -PathMap is null

I've installed a new Sitecore 8 instance, setup a MongoDB instance and started it running.
I've deployed the analytics definitions.
When I go to The Path Analyser I get the following Error.
There was an error loading data, please try again. PathExplorer.PathMapDataLoaded() - PathMap is null.
Any idea what might be wrong? Any other steps I need to perform?
I logged this with support - This has been reported as a bug.