How does Angular ViewEncapsulation affect web pages and style maintenance?

So we have a team of developers who embraces Angular and with that comes ViewEncapsulation.

This means that when they create a Angular component, they add the styling with the component and don’t use the global css. Depending on the ViewEncapsulation mode, the CSS ends up as inline styling either in the header or in the HTML.

We do have a Design System and we want to create a library of re-usable Angular components.

During my years developing web pages, the mantra was: Inline styling is bad! I don’t know if this still applies today as the browsers get more advanced.

My arguments for not encapsulating styling in Angular components are:

  • Inline styling makes html documents bigger, thus slower to load
  • If the Angular component reads a css file on page load, it creates additional HTTP requests which again slows down page load
  • Maintaining a style guide will be difficult when you do not have control over the components used
  • Different styling may be added to similar components because it’s done by different developers. This may alter component behaviour.

Dose anyone have experience with putting styling in Angular components and at the same time manage a design system?

Automated General News with a little maintenance – Runs 100% on autopilot

Premium designed website, fully automated. No experience needed. Runs 100% on autopilot, new articles are being added every few hours. was built with an easy-to-use blogger platform, No experience needed, runs 100% on autopilot.

The website uses a template that is similar to the wordpress theme, User friendly interface, Mobile friendly.

Are there any expenses for the website?

No, 100% free hosting from blogger, only domain…

Automated General News with a little maintenance – Runs 100% on autopilot

An unexpected error has occurred. Web Parts Maintenance Page: If you have permission, you can sue this page to temporarily close Web Parts

I have updated SP2013 farm to SP2016 in a new environment. Everything went well except some customised web parts. When I click on ex “Create customer” which is a customised webpart I get the error message:

An unexpected error has occurred. Web Parts Maintenance Page: If you have permission, you can sue this page to temporarily close Web Parts or remove personal settings. I have already deleted and readded the webparts, edited the web.config with different solutions which I found on the Internet but I just got more problems. I have even deleted and reinstalled the PerformancePoint service application. When I try to add a standard SP webpart, it works fine but not the customised webpart.

Have you please any idea about this issue and how to solve it?

Regards Ashraf

How do I make sure I run maintenance on the whole disk with Ubuntu on btrfs?

I am trying to learn btrfs and have Ubuntu installed with the disk partitioned with volumes for / and /home. This is the way the Ubuntu installer did it when I selected btrfs as file system. fstab looks like this:

# <file system> <mount point>   <type>  <options>       <dump>  <pass> # / was on /dev/nvme0n1p2 during installation UUID=43b93f24-bf6a-45a9-acf4-56868d30852e /               btrfs   defaults,subvol=@ 0       1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=F868-F3FE  /boot/efi       vfat    umask=0077      0       1 # /home was on /dev/nvme0n1p2 during installation UUID=43b93f24-bf6a-45a9-acf4-56868d30852e /home           btrfs   defaults,subvol=@home 0       2 /swapfile                                 none            swap    sw              0       0 

I have installed the ‘btrfsmaintenance’ package and trying to set it up. The one thing I do not understand is how to indicate the mountpoint/filesystemts to run maintenance on. If I want to run it on the whole disk do I simply set “/” or do I have to indicate each subvolume / and /home ?

Magento 2: Automatically maintenance mode

We have several stores running on EKS (Kubernetes) and for some reason one of the stores enter on maintenance mode for no reason: Unable to proceed: the maintenance mode is enabled.

We are using Magento Enterprise 2.3.1. There is no one going into the containers to enable maintenance mode, even when there is no code deploy or users using the stores (this is a stage environment) the maintenance mode appears. When we have the OPs team take a look at the var/.maintenance.flag, the file was created by root and sometimes it takes time to be deleted. Looking at the logs I can see that sometimes the store will throw errors for an hour or just a few minutes.

Has anyone been affected by this? It looks like schedule backups and setup:upgrade commands can create the flag, but these are not running when the flag is created.


Google Cloud gone to maintenance for at least a day. No way to get it working or extract data

We having yet another critical issue with Google Cloud SQL (MySQL Gen 2). Server gone to maintenance for almost a day, and still unusable. So our production and development databases are both trapped there. We can not restart the instance, we can not download backups or do some export. In essence, all controls are blocked for this server. We clicked at Help -> Send Feedback twice with screenshot and no reaction was given.

We can not afford another $ 150 per month aka $ 1800 for year for our startup to pay for fixing possible single “disaster of the year”!

Hey, Google, I can not believe that you do not see how that server cries with pain, shock and disbelief, shaking and covered with thick layer of dirty error logs!

[ Maintenance & Repairs ] Open Question : How can you tell if a used car should have originally come with a key fob?

There are no locks on the outside of my used 2003 Ford Escape other than the one on the driver’s side door. Should I just be able to buy and program a new key fob? It’s kind of a pain especially when you have groceries, etc. that need to go in the back.

Shutdown ESXi 6.7 with a script via SSH without entering maintenance mode

I’m trying to write a script that ssh’s to an ESXi 6.7 and shuts down the host and also shuts down the VMs according to the current system shutdown policy.

I’m running Dell customized image ESXi 6.7 in a Dell R710 with a dual Xeon X5650 and 144GB RAM.

In fact what I want is the same that I can get with:

Shutdown via GUI

Shutdown via console

I have ssh enabled in the server.

I already tryed:

1) (it just gets there indefinitely).

2) /bin/ (it to gets there indefinitely).

3) halt (shutdowns the server but it does not shuts down the VMs)

I also tried:

esxcli system shutdown poweroff --reason I_want_IT 

but the system must be in maintenance mode and I want to do it without entering maintenance mode

I then discovered this thread here in Server Fault, but it does not work in my server (I suppose it only runs on ESXi 5):

How do I shutdown the Host over ssh on ESXi 5 so it shuts down the guests properly?

I think I’m too dumb to discover on my own how to do it, because I presume it must be a simple thing to do.