memory – Can i change the location of page table to another NUMA node?

Hi i’m studying memory management of linux kernel.

My machine has multiple NUMA nodes, and i wonder if i can change the location of page table from NUMA 0 to NUMA N.
I studied that, at the page table initialization, CR3 register has pointer to where the page table will be initialized. And the location is on NUMA 0(first NUMA node)’s memory(kernel space).

So at the initialization, can i set the placement of page table to NUMA N?

If possible, kernel modification is all i supposed to do or more works are have to be done?

I’m using x86_64 processor and centos 7.7

bitcoin core – Is it possible to query a node for all addresses containing value?

Bitcoin-core (the full node implementation that makes up the majority of the network) does not keep an index of all addresses and balances, so without writing additional code to do the job, it is not possible. Bitcoin-core keeps track of coins via the UTXO model– the idea of ‘an address with a balance’ is just an abstraction of this that makes for a more user-friendly interface.

Of course, you could write some code to create an index of addresses and their respective balances, or perhaps find an already-existing open-source block explorer project that accomplishes this.

8 – How update programmatically node entity with empty field_image?

i need to make an import from one mysql table in my base.

I create node with :

$value= array(
                'type' => strtolower($typeProduit),
                'field_1'=>"test",
                'title'=>"test",
                'body' => array(
                    'value' => "test",
                    'format' => 'full_html',
                ),
                'field_2'=>"",
                'field_3'=>"",
                'field_4'=>"",                
            );

 $nodeEntity=Drupal::entityTypeManager()
        ->getStorage('node')
        ->create($value);

    $nodeEntity->save();

All node are create and if i have an image, i add it to my $value before save() :

$value('field_image_video')=array(
                    'target_id' => $fileImageVideo->id(),
                    'alt' => $catalogue->titreVideo,
                    'title' => $catalogue->titreVideo,
                );

if i have no image, i do nothing for this field.

I need to update some node programmatically after this first step.

And when i just try to change the title like this :

     $nodeEntityUpdate = Drupal::entityTypeManager()
                    ->getStorage('node')                
                    ->load(273);

     $nodeEntityUpdate->title="blabla";
     $nodeEntityUpdate->save();

if node don”t have image field set, i got this error :

PHP Fatal error: Call to a member function getFileUri()

If node has image, update work.

How can i set my image_field to null ?

i try to set my image field like that on creation :

$value('field_image_video')=array();

But that didn’t work.

this image field is set to unlimited values

node.js – Montar json para lib soap do node , erro ao integrar WS

Estou usando a lib https://www.npmjs.com/package/soap para fazer uma integração soap wsdl, porem ao executar a funçao

    let result;


    try{
      console.log(data.dataToEnvelope);
      const client = await this.wsdl.createClientAsync(this.wsdlFile);
      client.setSecurity(new this.wsdl.BasicAuthSecurity(username, password));
      const result = await client.MyFunctionAsync(data.dataToEnvelope);
      //result = await this.sendRequest(this.wsdlFile, myws.url);


      return result;

    }catch(error){
      console.log("ERROR", error)
    }


  }

Como cria um json com base no contrato do wsdl? porque estou trabalhando com um wsdl que usa sequence , e ai tem alguma coisa errada com o objeto e o WS retorna erro

Is it possible to query a node for all addresses?

For instance, can I run a query on a bitcoin node, that returns all addresses with more than 1 bitcoin on them?

8 – Can’t get referenced node to appear in view block

I have recipe and food nodes, and recipe nodes (e.g. My Favourite Cake Recipe) link to parent food types (e.g. Cake). This link is done via a Parent Food content reference field on the recipe node type.

Now I’d like to display a block titled Linked Food next to all recipes. To do this I created a food content view with the following:

  • Add a relationship with item Content referenced from field_parent_food so that I can display the content of the food node referenced from the recipe page I’m viewing.
  • Add a contextual ID filter, and set WHEN THE FILTER VALUE IS NOT AVAILABLE to Provide Default -> Content ID from URL so that I only look at nodes with an ID equal to the current page.
  • Add a field with ID Parent Food so that I display the content of the referenced food.

I then set up this block to display on the recipe content type. When I navigate to a recipe I was now expecting to see the parent food node detailed in the block, but instead I just see the same recipe repeated in the block. What am I doing wrong here?

I’ve had a look at a view tutorials and I’m as someone who is familiar with relational databases I find the concept of views (or at least the documentation) really impenetrable, so I’m just going to ask…

bitcoinjs – Elements Regtest Node LBTC Asset Hash Inconsistency

I’m having a strange problem that I can’t seem to wrap my head around; having started over from scratch now numerous times, I just can’t figure this out.

I have followed the tutorial on the Elements Project website (https://elementsproject.org/elements-code-tutorial/overview) to setup a Regtest Bitcoin node along with a Regtest Elements node. It’s Regtest, so I don’t mind sharing my bitcoin.conf and elements.conf:

bitcoin.conf

regtest=1
daemon=1
txindex=1
regtest.rpcport=18888
regtest.port=18889
rpcuser=user3
rpcpassword=password3

elements.conf

daemon=1
chain=elementsregtest
rpcuser=user1
rpcpassword=password1
elementsregtest.rpcport=18884
elementsregtest.port=18886
txindex=1
validatepegin=1
mainchainrpcport=18888
mainchainrpcuser=user3
mainchainrpcpassword=password3
initialfreecoins=2100000000000000

I did simplify the environment a little bit, removing the second Elements node from the equation. I proceeded to follow the tutorial to claim the anyone-can-spend coins, and generate 101 blocks to make them spendable:

ADDRGEN1=$(e1-cli getnewaddress)
e1-cli sendtoaddress $(e1-cli getnewaddress) 21000000 "" "" true
e1-cli generatetoaddress 101 $ADDRGEN1

Then I created an address offline using elementsjs-lib.

const bip39 = require("bip39")
const bip32 = require("bip32")
const slip77 = require("slip77")
const liquid = require('liquidjs-lib')

const regtest = liquid.networks.regtest
const mnemonic = bip39.generateMnemonic()
const seed = await bip39.mnemonicToSeed(mnemonic)

const node = bip32.fromSeed(seed, regtest)
const nodeBlinding = slip77.fromSeed(seed)

const addressIndex = 0
const child = node.derivePath(`m/1776'/0'/0'/0/${addressIndex}`)

let p2pkh = liquid.payments.p2pkh({ pubkey: child.publicKey, network:regtest })
const blindingKeyPair = nodeBlinding.derive(p2pkh.output)
p2pkh = liquid.payments.p2pkh({ pubkey: child.publicKey, blindkey: blindingKeyPair.publicKey, network: regtest })

console.log("address", p2pkh.address)
console.log("private key:", child.toWIF())
console.log("public key:", p2pkh.pubkey.toString('hex'))
console.log("output:", p2pkh.output.toString('hex'))
console.log("confidential address:", p2pkh.confidentialAddress)

console.log("blindingKeyPair masterKey", blindingKeyPair.masterKey.toString('hex'))
console.log("blindingKeyPair privateKey:", blindingKeyPair.privateKey.toString('hex'))
console.log("blindingKeyPair publicKey:", blindingKeyPair.publicKey.toString('hex'))
console.log("blindingKeyPair extra:", blindingKeyPair.extra.toString('hex'))
console.log("blindingKeyPair script:", blindingKeyPair.extra.toString('hex'))

Then I sent some LBTC to the confidential address I created, and generated one more block on my elements node to mine it.

e1-cli sendtoaddress CTEneiZiqsxx9mV9cbk3J8V14zC8jJrnWXqvpWYzjSF4J2D38rE49c4EEKZhmC7ito3TKdxCHmstzmZZ 100 "" "" false
e1-cli generatetoaddress 1 $ADDRGEN1

I was doing this so I can test the unblinding of transactions using liquidjs-lib, which I was successful. The problem I am writing about was observed when I began testing my transaction building code using liquidjs-lib’s psbt, specifically regarding asset hashes.

According to liquidjs-lib.networks.regtest.assetHash, the standard asset hash for liquid bitcoin is 5ac9f65c0efcc4775e0baec4ec03abdde22473cd3cf33c0419ca290e0751b225.

In liquidjs-lib’s transaction examples, it is understood that the asset hash should be formatted for psbt as the concatenation of the buffer for 01 in hex and the reversed buffer of liquid.networks.regtest.assetHash in hex. This resulting buffer is <Buffer 01 25 b2 51 07 0e 29 ca 19 04 3c f3 3c cd 73 24 e2 dd ab 03 ec c4 ae 0b 5e 77 c4 fc 0e 5c f6 c9 5a>.

When I started working with psbt, and inspecting values along the way, I noticed something odd. The asset hash in the outputs of the transaction representing the LBTC I sent from my elements node to my offline address did not match either of the asset values above. I sent regtest LBTC, but the asset hash of the output does not match the standard regtest LBTC asset hash.

On my node, when I check the transaction e1-cli gettransaction 2179604703e75d761cde9fa04ef06c4b63e1f3d9954e843a7c536c0e2aa82456` the output shows:

"details": (
    {
        "address": "2dgdgpvJv8P779i5r2i8YHkAgyvZZi6B8GX",
        "category": "send",
        "amount": -100.00000000,
        "amountblinder": "da05a84bcfd65ff7c59c5fc56577c6af324f3e15cce1e4423b62e0c4b111745e",
        "asset": "b2e15d0d7a0c94e4e2ce0fe6e8691b9e451377f6e46e8045a86f7c4b5d4f0f23",
        "assetblinder": "29f7e3a291f7c163474f90d235925594feb8ad55235da83557312f994ba55a1d",
        "vout": 0,
        "fee": 0.00005036,
        "abandoned": false
    }
)

In the details above, the asset hash b2e15d0d7a0c94e4e2ce0fe6e8691b9e451377f6e46e8045a86f7c4b5d4f0f23 is nowhere near the standard Regtest LBTC asset hash.

Here’s where it gets even crazier. If I use the rawtransaction and unblind the outputs with liquidjs-lib, I get all the right unblinded output values, but I get completely different asset hashes:

My UTXO output: <Buffer 23 0f 4f 5d 4b 7c 6f a8 45 80 6e e4 f6 77 13 45 9e 1b 69 e8 e6 0f ce e2 e4 94 0c 7a 0d 5d e1 b2>

Change Output: <Buffer b2 e1 5d 0d 7a 0c 94 e4 e2 ce 0f e6 e8 69 1b 9e 45 13 77 f6 e4 6e 80 45 a8 6f 7c 4b 5d 4f 0f 23>

The change output here has the same asset hash my node reported, which is not the standard Regtest LBTC hash. The UTXO asset hash has a different asset hash all together. What gives?!

Apologies for the extremely long-winded question; I have just tried so many different things at this point that I wanted to be sure to include as much information in my post as I can, including all steps to reproduce.

Node js and express js shwoing listing directory whenever I run server locally at port

Whenever I try to open my server locally using node and express everytime its shwoing me listing directory files. But the course from where I studied is displaying the frontend html site created. I have attached the code and expected output vs output I am getting. Please help.
My code

Expected output

My output

Does Drupal 8 have ‘Check boxes/radio buttons’ widget for ‘List (text)’ node fields?

In Drupal 7, you can select either checkboxes or a select list widget for the list (text) data type. Is there a similar config somewhere in d8?

I think the select lists won’t be intuitive to the content editors (ctrl+click functionality).

amazon web services – EKS node not responding and not exposing container ports

So I’ve been struggling with the fact that I’m unable to expose any deployment in my eks cluster.

I got down to this:

  1. My LoadBalancer service public IP never responds
  2. Went to the load balancer section in my aws console
  3. Load balancer is no working because my cluster node is not passing the heath checks
  4. SSHd to my cluster node and found out that containers do not have ports associated to them:

enter image description here

This makes the cluster node fail the health checks, so no traffic is forwarded that way.

enter image description here

I tried running a simple nginx container manually, without kubectl directly in my cluster node:

docker run -p 80:80 nginx

and using the node public IP in my browser. No luck:

enter image description here

then I tried curling to the nginx container directly from the cluster node via ssh:

 curl localhost

And I’m getting this response: “curl: (7) Failed to connect to localhost port 80: Connection refused”

  1. Why are containers in the cluster node not showing ports?
  2. How can I make the cluster node pass the load balancer health checks?
  3. Could it have something to do with the fact that I created a single node cluster with eksctl?
  4. What other options do I have to easily run a kubernetes cluster in AWS?