Error property bin does not exist in - Исправление ошибок и поиск оптимальных решений проблем

Scimmia wrote:

FIX GUIDE: For those that screwed up the filesystem update and can’t boot anymore because it can’t find /sbin/init
(since I don’t like coellobranco’s, I figured I should post my own)

1) Boot an Arch Install Disk. Set up your network if you need to (see Beginner’s Guide).
2) Mount all of the partitions you use to /mnt. This includes not only the root partition, but /usr, /var, etc (to /mnt/usr, /mnt/var/, etc).
3) Run «pacman —root /mnt -Qo /mnt/bin /mnt/sbin /mnt/usr/sbin». Ideally, it should tell you that /mnt/bin and /mnt/sbin don’t exist and that /mnt/usr/sbin is owned by «filesytem». If you get any other packages listed, they need to be fixed or uninstalled! If they’re packages from the official repos, upgrade them with «pacman —root /mnt -S <pkgname>. If they’re packages you don’t need, you can uninstall them with «pacman —root /mnt -Rs <pkgname>». Remember, if they’re not critical for your system, you can always reinstall them later once you get back up and going.
4) Run «find /mnt/bin /mnt/sbin /mnt/usr/sbin -exec pacman —root /mnt -Qo — {} + >/dev/null» This will tell you of any untracked files in the relevant directories. Any files it finds need to be deleted or moved. I suggest putting any scripts you made in /usr/local/bin so they don’t get in the way. If you removed any files from /mnt/bin or /mnt/sbin, check these dirs afterwards to see if they’re empty. If they are, delete them.
5) Run «ls -l /mnt /mnt/usr/sbin». At this point /mnt/bin and /mnt/sbin shouldn’t exist and /mnt/usr/sbin should be empty. If that’s not the case, stop. Come back here and ask for help.
6) Run «pacman —root /mnt -Su». This should install the filesystem package without any errors. Once that is done, your system should be functional again.

I’m really sorry to post here for help, but I have run into the «can’t find /sbin/init, bailing out error» after trying to follow the home page instructions. I had to first replace grub-common with grub (2.00-1) before upgrading the remaining packages (ignoring filesystem and bash). In looking at pacman.log, I only received these warnings during the the kernel build:

WARNING: Possibly missing firmware for module: aic94xx
WARNING: Possibly missing firmware for module: bfa
WARNING: Possibly missing firmware for module: smsmdtv

I didn’t think these modules needed to be dealt with at this point. I also got a message about SNA being used in the xf86-input-evdev package.

I then upgraded bash without any problems (at least according to pacman.log) and the next entry is «Running ‘pacman -Su’ but there are no additional errors or messages. At this point I think I tried to restart the system and I am not sure if filesystem was fully upgraded properly or not.

Now, on boot I get:

*** Warning ***
* The root device is not configured to be mounted *
* read-write@ It may be fsck'd again later. *
***
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.

sh: can't access tty; job control turned off
[rootfs /]#

In following Scimmia’s instructions above, I booted using an archiso USB (with filesystem 2012.10-1) and mounted the root and var partitions to /mnt and /mnt/var, respectively, and at step 3 I get:

root@archiso /mnt # pacman --root /mnt -Qo /mnt/bin /mnt/sbin /mnt/usr/sbin
error: failed to read file '/mnt/bin': No such file or directory
error: cannot determine ownership of directory '/mnt/sbin'
error: cannot determine ownership of directory '/mnt/usr/sbin'

In the /mnt directory, the /mnt/bin folder does not exist, and /mnt/sbin and /mnt/usr/sbin both exist as directories (ie not symlinks) and are empty.

I thought perhaps the linux package was not installed properly at the beginning, so I tried this to reinstall it:

root@archiso / # pacman --root /mnt -S linux
warning: linux-3.10.10-1 is up to date -- reinstalling
<snip>
(1/1) upgrading linux [###] 100%
call to execv failed (No such file or directory)
error: command failed to execute correctly
pacman --root /mnt -S linux  6.48s user 0.68s system 5% cpu 2:05.60 total

Any help would be appreciated. Again, sorry to be yet another user with difficulties.

Источник

How to Fix the Property does not exist on type Error in TypeScript All Method

The blog will help about How to Fix the “Property does not exist on type {}” Error in TypeScript & learn how to solve different problems that come from coding errors. If you get stuck or have questions at any point,simply comment below.
Question: What is the best way to approach this problem? Answer: Check out this blog code to learn how to fix errors How to Fix the “Property does not exist on type {}” Error in TypeScript. Question: “What should you do if you run into code errors?” Answer:”You can find a solution by following this blog.

Assigning properties to JavaScript objects is quite simple.

let obj = {}
obj.key1 = 1;
obj['key2'] = 'dog';

This would give me these values for obj:

obj: {
   key1: 1, 
   key2: 'dog'
}

The Problem

When we head over to TypeScript, running this code gives us the error below.

let obj = {}
obj.key1 = 1;

Property 'key1' does not exist on type '{}'.

How do we work with JSON objects in TypeScript?

Solution 1: The Quick Fix

In TypeScript, we can type a function by specifying the parameter types and return types.

Similarly, we need to type our objects, so that TypeScript knows what is and isn’t allowed for our keys and values.

Quick and dirty. A quick and dirty way of doing this is to assign the object to type any. This type is generally used for dynamic content of which we may not know the specific type. Essentially, we are opting out of type checking that variable.

let obj: any = {}
obj.key1 = 1;
obj['key2'] = 'dog';

But then, what’s the point of casting everything to type any just to use it? Doesn’t that defeat the purpose of using TypeScript?

Well, that’s why there’s the proper fix.

Solution 2: The Proper Fix

Consistency is key. In order to stay consistent with the TypeScript standard, we can define an interface that allows keys of type string and values of type any.

interface ExampleObject {
    [key: string]: any
}
let obj: ExampleObject = {};
obj.key1 = 1;
obj['key2'] = 'dog';

What if this interface is only used once? We can make our code a little more concise with the following:

let obj: {[k: string]: any} = {};
obj.key1 = 1;
obj['key2'] = 'dog';

Solution 3: The JavaScript Fix

Pure JavaScript. What if we don’t want to worry about types? Well, don’t use TypeScript 😉

Or you can use Object.assign().

let obj = {};
Object.assign(obj, {key1: 1});
Object.assign(obj, {key2: 'dog'});

What an exciting time to be alive.

Revise the code and make it more robust with proper test case and check an error there before implementing into a production environment.
Now you can solve your code error in less than a minute.

Источник

When I was trying to pass component data with property binding, I got the following typescript error : Property does not exist on value of type. This tutorial guides you how to resolve this error and also guides on how to pass recipe data with property binding.

While I was trying the below example – Passing recipe data with property binding I got the following error.

Angular is running in the development mode. Call enableProdMode() to enable the production mode.
client:52 [WDS] Live Reloading enabled.
client:150 [WDS] Errors while compiling. Reload prevented.
errors @ client:150
client:159 src/app/recipes/recipe-list/recipe-item/recipe-item.component.html:5:26 - error TS2339: Property 'recipes' does not exist on type 'RecipeItemComponent'.

5    *ngFor="let recipe of recipes">
                           ~~~~~~~

  src/app/recipes/recipe-list/recipe-item/recipe-item.component.ts:5:16
    5   templateUrl: './recipe-item.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component RecipeItemComponent.

Example : Passing recipe data with property binding

Note, the parent-child relationship for the below example is as follows.

--recipes
---- recipe.model.ts
---- recipe-detail
---- recipe-list
------ recipe-item

Display recipe name and description via recipe item component via String interpolation

recipes/recipe-list/recipe-item/recipe-item.component.html

<a href="#" 
   class="list-group-item clearfix">
    <div class="pull-left">
        <h4 class="list-group-item-heading">{{ recipe.name }}</h4>
        <p class="list-group-item-text">{{ recipe.description }}</p>
    </div>
    <span class="pull-right">
        <img 
             [src] = "recipe.imagePath"
             alt="{{ recipe.name }}" 
             class="img-responsive" 
             style="max-height: 50px;"> 
    </span>
</a>

recipes/recipe-list/recipe-item/recipe-item.component.ts

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-recipe-item',
  templateUrl: './recipe-item.component.html',
  styleUrls: ['./recipe-item.component.css']
})
export class RecipeItemComponent implements OnInit {

  constructor() { }

  ngOnInit(): void {
  }

}

recipes/recipe-list/recipe-list.component.html

For example, to pass recipe data with property binding and use ngFor loop refer below section.

<div class="row">
    <div class="col-xs-12">
        <div class="pull-left">
            <h3>My Recipe List</h3>
        </div>   
    </div>
</div>
<hr>
<div class="row">
    <div class="col-xs-12">        
        <app-recipe-item 
          *ngFor="let recipe of recipes"
          [recipe] = "recipe"></app-recipe-item>
    </div>
</div>
<hr>
<div class="row">
    <div class="col-xs-12">
        <div class="pull-right">
            <button class="btn btn-success">Add Recipe</button>
        </div>        
    </div>
</div>

recipes/recipe-list/recipe-list.component.ts

import { Component, OnInit } from '@angular/core';
import { Recipe } from '../recipe.model';

@Component({
  selector: 'app-recipe-list',
  templateUrl: './recipe-list.component.html',
  styleUrls: ['./recipe-list.component.css']
})
export class RecipeListComponent implements OnInit {

  recipes: Recipe[] = [
    new Recipe('Recipe 1', 'This is our first recipe', 'https://lilluna.com/wp-content/uploads/2017/10/spanish-rice-resize-6.jpg'),
    new Recipe('Recipe 2', 'This is our second recipe', 'https://food.fnr.sndimg.com/content/dam/images/food/fullset/2020/07/14/0/FNK_20-Minute-Sausage-And-Pepper-Ravioli-Skillet_H_s4x3.jpg.rend.hgtvcom.441.331.suffix/1594757098344.jpeg'),
    new Recipe('Recipe 3', 'This is our third recipe', 'https://images.squarespace-cdn.com/content/v1/5c089f01f93fd410a92e642a/1589512502567-CNOAIL05BVT1TI0422P2/ke17ZwdGBToddI8pDm48kLkXF2pIyv_F2eUT9F60jBl7gQa3H78H3Y0txjaiv_0fDoOvxcdMmMKkDsyUqMSsMWxHk725yiiHCCLfrh8O1z4YTzHvnKhyp6Da-NYroOW3ZGjoBKy3azqku80C789l0iyqMbMesKd95J-X4EagrgU9L3Sa3U8cogeb0tjXbfawd0urKshkc5MgdBeJmALQKw/pheasant+back+burger+recipe.jpeg'),
    new Recipe('Recipe 4', 'This is our fourth recipe', 'https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcQunf0MIpWZn3rjR-mo4u9_HKsL0Ud3SV8WTQ&usqp=CAU'),
    new Recipe('Recipe 5', 'This is our fifth recipe', 'https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcQ_9l39e7G5y_ENz6hL6l5KhaJuroOrbzqs0Q&usqp=CAU')
  ];

  constructor() { }

  ngOnInit(): void {
  }

}

recipes/recipe.model.ts

export class Recipe {
    public name : string;
    public description : string;
    public imagePath : string;

    constructor(name : string, description : string, imagePath : string){
        this.name = name;
        this.description = description;
        this.imagePath = imagePath;
    } 
}

Solution:

I figured out the reason why I was getting error Property ‘recipes’ does not exist on type ‘RecipeItemComponent’. I forgot to add the following statement in the RecipeItemComponent class.

  @Input() recipe: Recipe;

recipe-item.component.ts

import { Component, Input, OnInit } from '@angular/core';
import { Recipe } from '../../recipe.model';

@Component({
  selector: 'app-recipe-item',
  templateUrl: './recipe-item.component.html',
  styleUrls: ['./recipe-item.component.css']
})
export class RecipeItemComponent implements OnInit {

  @Input() recipe: Recipe;

  constructor() { }

  ngOnInit(): void {
  }

}

After, modifying the RecipeItemComponent class like above, the Typescript Error: Property does not exist on value of type gone away.

Hope it helped 🙂

Call ngOnInit() again from another function – Angular 9 ?
ngOnChanges get new value and previous value – Angular
Global Angular CLI version is greater than your local version
Upgrade Angular CLI to the latest version Angular 9 or 10 ?
How to use new static option in ViewChild Angular 9 ?
Project contents into angular components using ng-content
Call ngOnInit() again from another function – Angular 9 ?
ngAfterContentInit with Example – Angular
ngAfterViewInit with Example – Angular
ngAfterContentChecked with Example
ngOnDestroy Example Angular
Angular Component : In which lifecycle hook you can check value of DOM element ?
@ContentChild TypeError: Cannot read property ‘nativeElement’ of undefined
Access ng-content with @ContentChild – Angular Component
How to select an element in a component template – Angular ?
Difference between @ViewChild and @ContentChild – Angular Example
Expected 0 type arguments, but got 1 : Angular
Angular – Access template reference variables from component class ?
Pass variable from parent to custom child component – Angular 9
Cannot find name ‘Output’ – Angular
EventEmitter parameter value undefined for listener
Node Sass could not find a binding for your current environment

References:

angular.io
wikipedia

Источник