TX rejected: failed to validate input -  signature not empty on failed checksig

Hi, I am following the examples code of this repo to try to send some tBTC by code and encountering this error
{"jsonrpc":"1.0","result":null,"error":{"code":-25,"message":"TX rejected: failed to validate input 653c237ebbdb97df2921a9a5d7c1ebf45779e74ce5052578bb174c5b281f52f1:0 which references output db453592e58a931430d88d1c1f1f96fde9c5fe390f759f7a0634625bc900c221:2 - signature not empty on failed checksig (input witness [3045022100dfc0860a8a3d0bc5fcc798fcc32bd3ae8848ce7b04b788e6cde2fdf6fd63b90802205041579d33dd1ad5a5d321909359764f93ad3b5a7fe2a61ea990ec3cecd4901201 03054de00e5d1c6e69fb1452fbc7956e3e169673fdbd1a554d5219634b51fd65f9], input script bytes , prev output script bytes 0014c4d538549b9d6cbdcdfdde9a29c0a9640fa1f503)"},"id":"curltest"}

here is my code only change a bit params and secret key to my Xverse wallet private key.
fn main() {
    let secp = Secp256k1::new();

    // Get a secret key we control and the pubkeyhash of the associated pubkey.
    // In a real application these would come from a stored secret.
    let (sk, wpkh) = senders_keys(&secp);

    // Get an address to send to.
    let address = receivers_address();

    // Get an unspent output that is locked to the key above that we control.
    // In a real application these would come from the chain.
    let (dummy_out_point, dummy_utxo) = dummy_unspent_transaction_output(&wpkh);

    // The input for the transaction we are constructing.
    let input = TxIn {
        previous_output: dummy_out_point, // The dummy output we are spending.
        script_sig: ScriptBuf::default(), // For a p2wpkh script_sig is empty.
        sequence: Sequence::ENABLE_RBF_NO_LOCKTIME,
        witness: Witness::default(), // Filled in after signing.
    };

    // The spend output is locked to a key controlled by the receiver.
    let spend = TxOut {
        value: SPEND_AMOUNT,
        script_pubkey: address.script_pubkey(),
    };

    // The change output is locked to a key controlled by us.
    let change = TxOut {
        value: CHANGE_AMOUNT,
        script_pubkey: ScriptBuf::new_p2wpkh(&wpkh), // Change comes back to us.
    };

    // The transaction we want to sign and broadcast.
    let mut unsigned_tx = Transaction {
        version: transaction::Version::TWO,  // Post BIP-68.
        lock_time: absolute::LockTime::ZERO, // Ignore the locktime.
        input: vec![input],                  // Input goes into index 0.
        output: vec![spend, change],         // Outputs, order does not matter.
    };
    let input_index = 0;

    // Get the sighash to sign.
    let sighash_type = EcdsaSighashType::All;
    let mut sighasher = SighashCache::new(&mut unsigned_tx);
    let sighash = sighasher
        .p2wpkh_signature_hash(
            input_index,
            &dummy_utxo.script_pubkey,
            SPEND_AMOUNT,
            sighash_type,
        )
        .expect("failed to create sighash");

    // Sign the sighash using the secp256k1 library (exported by rust-bitcoin).
    let msg = Message::from(sighash);
    let signature = secp.sign_ecdsa(&msg, &sk);

    // Update the witness stack.
    let signature = Signature {
        sig: signature,
        hash_ty: sighash_type,
    };
    let pk = sk.public_key(&secp);
    *sighasher.witness_mut(input_index).unwrap() = Witness::p2wpkh(&signature, &pk);

    // Get the signed transaction.
    let tx = sighasher.into_transaction();

    let raw_tx = tx.raw_hex();

    // BOOM! Transaction signed and ready to broadcast.
    println!("tx ne {:#?}", tx);

    let rpc_url = "https://<IP_ADDRESS>:80/52c09aec49931a38d7e6b256e1363096";

    // Connect to the Bitcoin node
    let rpc = Client::new(rpc_url, Auth::None).unwrap();
    let txid = rpc.send_raw_transaction(raw_tx).unwrap();

    println!("txid {:?}", txid);
}

/// An example of keys controlled by the transaction sender.
///
/// In a real application these would be actual secrets.
fn senders_keys<C: Signing>(secp: &Secp256k1<C>) -> (SecretKey, WPubkeyHash) {
    let sk =
        SecretKey::from_str("I-put-my-private-key-from-xverse-wallet-to-here")
            .unwrap();
    let pk = bitcoin::PublicKey::new(sk.public_key(secp));
    let wpkh = pk.wpubkey_hash().expect("key is compressed");

    (sk, wpkh)
}

/// A dummy address for the receiver.
///
/// We lock the spend output to the key associated with this address.
///
/// (FWIW this is a random mainnet address from block 80219.)
fn receivers_address() -> Address {
    Address::from_str("tb1q2v02yxwwktwxml5mx8aqjherkslh8newlcttx9")
        .expect("a valid address")
        .require_network(Network::Testnet)
        .expect("valid address for mainnet")
}

/// Creates a p2wpkh output locked to the key associated with `wpkh`.
///
/// An utxo is described by the `OutPoint` (txid and index within the transaction that it was
/// created). Using the out point one can get the transaction by `txid` and using the `vout` get the
/// transaction value and script pubkey (`TxOut`) of the utxo.
///
/// This output is locked to keys that we control, in a real application this would be a valid
/// output taken from a transaction that appears in the chain.
fn dummy_unspent_transaction_output(wpkh: &WPubkeyHash) -> (OutPoint, TxOut) {
    let script_pubkey = ScriptBuf::new_p2wpkh(wpkh);

    let out_point =
        OutPoint::from_str("db453592e58a931430d88d1c1f1f96fde9c5fe390f759f7a0634625bc900c221:2")
            .unwrap();
    let utxo = TxOut {
        value: DUMMY_UTXO_AMOUNT,
        script_pubkey,
    };

    (out_point, utxo)
}

Also wonder Is there any code or high level libs api for more genetic of others output ? It would be great if you guys can provide an example.

It looks like you're trying to sign and spend a dummy UTXO, which will not exist on testnet or any other chain. You need to sign and spend real coins.

@apoelstra Hi, I update but get the same error this is the tx https://mempool.space/testnet/tx/db453592e58a931430d88d1c1f1f96fde9c5fe390f759f7a0634625bc900c221.
fn dummy_unspent_transaction_output(wpkh: &WPubkeyHash) -> (OutPoint, TxOut) {
    let out_point =
        OutPoint::from_str("db453592e58a931430d88d1c1f1f96fde9c5fe390f759f7a0634625bc900c221:2")
            .unwrap();
    let utxo = TxOut {
        value: DUMMY_UTXO_AMOUNT,
        script_pubkey: ScriptBuf::new_p2wpkh(&WPubkeyHash::from_str(
            "c4d538549b9d6cbdcdfdde9a29c0a9640fa1f503",
        ).unwrap()),
    };

    (out_point, utxo)
}

I am new to btc chain, might have some silly mistake, is there anything wrong

One obvious thing that jumps out is that DUMMY_UTXO_AMOUNT does not match your output.

Sr for not enough infomation,  here it is  const DUMMY_UTXO_AMOUNT: Amount = Amount::from_sat(1305);

Oh actually might the CHANGE_AMOUNT mean DUMMY_UTXO_AMOUNT - SPEND_AMOUNT I input is not correct. So sorry for silly mistake. Now get other error tho Tx has insufficient priority but Thanks a lot. I will close this one

Glad you figured it out!
In general, it seems like a hard problem to get this data correct. Probably we could provide some form of sanity-checking function where you could, for example, provide the entire previous transactions for each input.

Hi @apoelstra actually I should include the fee for CHANGE AMOUNT to get rid of Tx has insufficient priority error. Then it come back with the TX rejected: failed to validate input  😭 . here is my updated code, just change the utxo, nothing new.
use std::str::FromStr;

use bitcoin::ecdsa::Signature;
use bitcoin::locktime::absolute;
use bitcoin::secp256k1::{Message, PublicKey, Secp256k1, SecretKey, Signing};
use bitcoin::sighash::{EcdsaSighashType, SighashCache};
use bitcoin::{
    transaction, Address, Amount, Network, OutPoint, ScriptBuf, Sequence, Transaction, TxIn, TxOut,
    Txid, WPubkeyHash, Witness,
};
use bitcoincore_rpc_sotatek::{Auth, Client, RawTx, RpcApi};

const DUMMY_UTXO_AMOUNT: Amount = Amount::from_sat(10000);
const SPEND_AMOUNT: Amount = Amount::from_sat(500);
const CHANGE_AMOUNT: Amount = Amount::from_sat(8500); // 1000 sat fee.

fn main() {
    let secp = Secp256k1::new();

    // Get a secret key we control and the pubkeyhash of the associated pubkey.
    // In a real application these would come from a stored secret.
    let (sk, wpkh) = senders_keys(&secp);

    // Get an address to send to.
    let address = receivers_address();

    // Get an unspent output that is locked to the key above that we control.
    // In a real application these would come from the chain.
    let (dummy_out_point, dummy_utxo) = dummy_unspent_transaction_output(&wpkh);

    // The input for the transaction we are constructing.
    let input = TxIn {
        previous_output: dummy_out_point, // The dummy output we are spending.
        script_sig: ScriptBuf::default(), // For a p2wpkh script_sig is empty.
        sequence: Sequence::ENABLE_RBF_NO_LOCKTIME,
        witness: Witness::default(), // Filled in after signing.
    };

    // The spend output is locked to a key controlled by the receiver.
    let spend = TxOut {
        value: SPEND_AMOUNT,
        script_pubkey: address.script_pubkey(),
    };

    // The change output is locked to a key controlled by us.
    let change = TxOut {
        value: CHANGE_AMOUNT,
        script_pubkey: ScriptBuf::new_p2wpkh(&wpkh), // Change comes back to us.
    };

    // The transaction we want to sign and broadcast.
    let mut unsigned_tx = Transaction {
        version: transaction::Version::TWO,  // Post BIP-68.
        lock_time: absolute::LockTime::ZERO, // Ignore the locktime.
        input: vec![input],                  // Input goes into index 0.
        output: vec![spend, change],         // Outputs, order does not matter.
    };
    let input_index = 0;

    // Get the sighash to sign.
    let sighash_type = EcdsaSighashType::All;
    let mut sighasher = SighashCache::new(&mut unsigned_tx);
    let sighash = sighasher
        .p2wpkh_signature_hash(
            input_index,
            &dummy_utxo.script_pubkey,
            SPEND_AMOUNT,
            sighash_type,
        )
        .expect("failed to create sighash");

    // Sign the sighash using the secp256k1 library (exported by rust-bitcoin).
    let msg = Message::from(sighash);
    let signature = secp.sign_ecdsa(&msg, &sk);

    // Update the witness stack.
    let signature = Signature {
        sig: signature,
        hash_ty: sighash_type,
    };
    let pk = sk.public_key(&secp);
    *sighasher.witness_mut(input_index).unwrap() = Witness::p2wpkh(&signature, &pk);

    // Get the signed transaction.
    let tx = sighasher.into_transaction();

    let raw_tx = tx.raw_hex();

    // BOOM! Transaction signed and ready to broadcast.
    println!("tx ne {:#?}", tx);

    let auth = Auth::UserPass("bitcoin_testnet".to_string(), "1".to_string());
    let rpc_url = "https://btc-testnet.rpc.works";
    // Connect to the Bitcoin node
    let rpc = Client::new(
        rpc_url,
        auth,
    )
    .unwrap();

    // Connect to the Bitcoin node
    // let rpc = Client::new(rpc_url, Auth::None).unwrap();
    let txid = rpc.send_raw_transaction(raw_tx).unwrap();

    println!("txid {:?}", txid);
}

/// An example of keys controlled by the transaction sender.
///
/// In a real application these would be actual secrets.
fn senders_keys<C: Signing>(secp: &Secp256k1<C>) -> (SecretKey, WPubkeyHash) {
    let sk = SecretKey::from_str("I-put-my-private-key-from-xverse-wallet-to-here").unwrap();
    let pk = bitcoin::PublicKey::new(sk.public_key(secp));
    let wpkh = pk.wpubkey_hash().expect("key is compressed");

    (sk, wpkh)
}

/// A dummy address for the receiver.
///
/// We lock the spend output to the key associated with this address.
///
/// (FWIW this is a random mainnet address from block 80219.)
fn receivers_address() -> Address {
    Address::from_str("tb1q2v02yxwwktwxml5mx8aqjherkslh8newlcttx9")
        .expect("a valid address")
        .require_network(Network::Testnet)
        .expect("valid address for mainnet")
}

/// Creates a p2wpkh output locked to the key associated with `wpkh`.
///
/// An utxo is described by the `OutPoint` (txid and index within the transaction that it was
/// created). Using the out point one can get the transaction by `txid` and using the `vout` get the
/// transaction value and script pubkey (`TxOut`) of the utxo.
///
/// This output is locked to keys that we control, in a real application this would be a valid
/// output taken from a transaction that appears in the chain.
fn dummy_unspent_transaction_output(wpkh: &WPubkeyHash) -> (OutPoint, TxOut) {
    let out_point =
        OutPoint::from_str("5a23d3d58057c061a6211608aab4328d01d94bc664dc5b204a4d0064ad70ea95:0")
            .unwrap();
    let utxo = TxOut {
        value: DUMMY_UTXO_AMOUNT,
        script_pubkey: ScriptBuf::new_p2wpkh(&WPubkeyHash::from_str(
            "c4d538549b9d6cbdcdfdde9a29c0a9640fa1f503",
        ).unwrap()),
    };

    (out_point, utxo)
}

Is bitcoincore_rpc_sotatek a fork of rust-bitcoincore-rpc?  I don't see the failed to validate input in the rust-bitcoincore-rpc crate..

@yancyribbens yes, just a custom fix to apply https. Won't have any effect

just a custom fork to fix to apply https. Won't have any effect with the error. I updated the code back to prevent any confused.

Hmm ok sounds good.  Well, I guess that error message is being bubbled from core then?

Is the output returned by dummy_unspent_transaction_output a real utxo taken from the testnet chain and locked to the secret key returned by senders_keys i.e., did  you create the utxo by sending testnet coins to an address created using  the senders keys?

@tcharding Hi here the full scenario, my wallet in senders_keys that I put secret key in code which is tb1qcn2ns4ymn4ktmn0am6dzns9fvs86ragrr9tw7l received  0,0001 btc from my other wallet. ( I did this by wallet extension).  Now I try to spend UTXO 5a23d3d58057c061a6211608aab4328d01d94bc664dc5b204a4d0064ad70ea95:0 by the secret key of address tb1qcn2ns4ymn4ktmn0am6dzns9fvs86ragrr9tw7l and got the error.
Is there anything wrong, I am still very new with btc chain.

You inspired me to write some tests against a regtest node which I've been meaning to get around to. I got just far enough today to hit that the bug is in the example code.
I'll investigate it further, just wanted to let you know I'm working on it. Thanks for raising the issue, super useful to uncover bugs!

@Sotatek-VuNguyen2 have you tried using create_raw_transaction and then use the results to send_raw_transaction?

fwiw after using create_raw_transaction, there is also sign_raw_transaction which you could do after calling create but before calling send.

Found it :) - I wrote that bug, sorry about that.

Found it :) - I wrote that bug, sorry about that.

What exactly is the bug?  Is it a bug with rust-bitcoin-rpc?

Noticed this PR.  Linking it so others can follow https://github.com/rust-bitcoin/rust-bitcoin/pull/2696

I guess Github linked it earlier


Idea: Build index of inputNodes -> dataNodes or React.js

This would slow down loading, but probably vastly improve traversing a form.
The cleverSelector approach needs to compare lots of attribute strings with the jQuery *= selector.

Some areas where we could significant performance improvements:
1 transformation: we could populate default language strings with reactjs (on server) to make transformation take a fraction of the time it does currently
2 widgets rendering: instead of the very slow DOM manipulation we could build the widgets DOM on the server
3 branches: it will be almost built-in to not render irrelevant branches nor evaluate anything inside the. This may make revealing branches slower, but loading time, and recalculating skip logic and calculates would be so much faster for many forms.

Treating repeats as subforms internally, might be a good approach. They'll still have to use the same model, because logic can cross from repeat to repeat or from non-repeat to repeat.

or use a virtual DOM for querying


serialize default retirement criteria in workflow dumps

closes #1417

What would happen if we just change Workflow#retirement to return the default? Wouldn't that make the frontend happy too, by handing it the defaults instead of (probably?) having to duplicate them over there?

Yeah - we do this in the serializer for the UI. I felt like it was more a presentation issue and not model layer responsibility but didn't like that i was duplicating code...happy to rework it to default in the model layer, will update.


Added app.yaml file to help deploy app on google cloud

an app.yaml file is necessary to deploy an app on google cloud using Google Cloud SDK
this file will help deploy the Open Event webapp on Google Cloud

Current coverage is 34.08% (diff: 100%)

Merging #920 into development will not change coverage

@@           development       #920   diff @@
=============================================
  Files                7          7
  Lines             1021       1021
  Methods            131        131
  Messages             0          0
  Branches           157        157
=============================================
  Hits               348        348
  Misses             673        673
  Partials             0          0

Powered by Codecov. Last update 3ee077e...84b678f


Add a GitHub presubmit that the flutter/plugins CI is green

Similar to the "flutter-build" indication we have on framework PRs.
It's too easy to not notice that the build is red when landing a PR.

I have a WIP change to do this (on cocoon).

Is this implemented already? I see PRs get red status if the dashboard on appengine is red (and it includes plugins).

@stuartmorgan is this something we still want to implement?

This was added at some point via https://github.com/apps/submit-queue.


Ability to update/edit custom ssl certs

Is your feature request related to a problem? Please describe.
I personally use bought wildcard ssl certs from ssls.com for the majority of my domains.  They are valid for 1 year and in order to update them, I need to either remove/re-add via the GUI or ssh into the box and update the certs manually.
Describe the solution you'd like
Have an option to edit/update custom SSL certs and potentially expiration tracking via the web app.
Describe alternatives you've considered
Only alternative is to remove/re-add via the web app, and then update each host or ssh into the box and manually update the cert files.
Additional context
This is strictly a QoL update, and may only affect a small subset of users that prefer to use their bought certs instead of LE.  However, the expiration tracking would be nice for all.

https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/2317

Need this feature too


eclint fix * does not fix the max_line_length rule violation

I am trying to use eclint fix command to do the batch fix, unfortunately, I found I still saw the eclint check issue after applying the command.
For example this file, https://github.com/chenrui333/website/blob/fix-editorconfig-style-issue/OWNERS_ALIASES
Firstly, I applied eclint fix OWNERS_ALIASES, silently passed.
Then, I run eclint check OWNERS_ALIASES, it still throws bunch of errors:
$ eclint check OWNERS_ALIASES
OWNERS_ALIASES
    002:80 ❌ invalid line length: 97, exceeds: 80  (EditorConfig max_line_length https://goo.gl/DI51mx)
    008:80 ❌ invalid line length: 160, exceeds: 80 (EditorConfig max_line_length https://goo.gl/DI51mx)
    066:80 ❌ invalid line length: 86, exceeds: 80  (EditorConfig max_line_length https://goo.gl/DI51mx)
    088:80 ❌ invalid line length: 86, exceeds: 80  (EditorConfig max_line_length https://goo.gl/DI51mx)
    188:80 ❌ invalid line length: 88, exceeds: 80  (EditorConfig max_line_length https://goo.gl/DI51mx)
    197:80 ❌ invalid line length: 180, exceeds: 80 (EditorConfig max_line_length https://goo.gl/DI51mx)
    206:80 ❌ invalid line length: 98, exceeds: 80  (EditorConfig max_line_length https://goo.gl/DI51mx)
    216:80 ❌ invalid line length: 109, exceeds: 80 (EditorConfig max_line_length https://goo.gl/DI51mx)

Let me know if I want to do something special, thanks!

This tool very intentionally does not "fix" max_line_length violations, as that would require knowledge of whatever language is contained within the file (AST).

Yes, because, again, it requires AST or knowledge of the language in question. I don't even believe in the concept behind this project any more for this very reason.


Suggestion: Config identifier

It would be great if one could define an optional config identifier to the connection string. That could then be passed to the InvenTree API as a header and be used server side to identify which host is using which config. Would be usedfull to detect outdated configs.

That could definitely be a thing. I'm assuming that the plugin you wrote would have to check this value? would the ODBC driver not then have to hit a specific API as opposed to a header when fetching some other data like parts, or categories?
Is this just to be able to report on the InvenTree side what hosts are using outdated configs? I don't think we'll be able to display anything meaningful to the user on the KiCad side of things (short of a fatal error from the ODBC driver).

@clj I think adding the info into the request headers of all API requests would be the easiest solution. We can listen for those headers pretty easily in Django.
I would only use it for reporting on InvenTree, alerting is not really something that should be handled by a database driver.

Could you provide a concrete example of how you think this should look? E.g. header name and value? I mean I guess the value can be fairly opaque to the driver: a value passed in the connection string that is just supplied to inventree.

@clj I am imagining a header INVENTREE-CONIFG-IDENTIFIER - anything passed in the DSN as the kwarg identifier or null - that is passed with every request, the rest can be handled on InvenTree's side.


google authentication

I tried to login with google authentication (oauth) in this case I tested with gmail.com but I couldn't authenticate. it shows unknown error.

Step to reproduce

open the custom build chromium
try to login normally (my account has multi-factor authentication enabled)
got the error.

Closing, please re-open the issue if it is still a problem.


updated Read.me

What ❔
Added a colon ":" for ending the statement, it's much better to read with giving the options below.
Why ❔
it's much better for readability with giving the options below.
Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zk fmt and zk lint.
[ ] Spellcheck has been run via zk spellcheck.
[ ] Linkcheck has been run via zk linkcheck.

Hello! Thank you for the contribution, but due to a large influx we currently do not accept  minor non-functional contributions

Ok cool, thanks.


Fix pod security standard for loki backend sidecar

Towards https://github.com/giantswarm/giantswarm/issues/28412 and following on https://github.com/giantswarm/retagger/pull/882
In the latest versions of the loki chart, the loki-backend is now equipped with a sidecar, let's fix it so it respects the pod security standard

All that's left is deprecation of apis but it's related to the storage backend of the api-server:
4m         Warning   PolicyViolation           poddisruptionbudget/loki-read                   policy check-deprecated-apis-1-25/validate-v1-25-removals fail: policy/v1beta1/PodDisruptionBudget is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
18m         Warning   PolicyViolation           poddisruptionbudget/loki-gateway                policy check-deprecated-apis-1-25/validate-v1-25-removals fail: policy/v1beta1/PodDisruptionBudget is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
13m         Warning   PolicyViolation           endpointslice/loki-backend-headless-rpp88       policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
14m         Warning   PolicyViolation           endpointslice/query-scheduler-discovery-dr6nq   policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
3m2s        Warning   PolicyViolation           endpointslice/loki-memberlist-7sp7t             policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
14m         Warning   PolicyViolation           endpointslice/loki-backend-nh95p                policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
2m25s       Warning   PolicyViolation           endpointslice/query-scheduler-discovery-dr6nq   policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
13m         Warning   PolicyViolation           endpointslice/loki-memberlist-7sp7t             policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
2m25s       Warning   PolicyViolation           endpointslice/loki-backend-nh95p                policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
3m2s        Warning   PolicyViolation           endpointslice/loki-backend-headless-rpp88       policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
2m25s       Warning   PolicyViolation           endpointslice/loki-memberlist-7sp7t             policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
3m2s        Warning   PolicyViolation           endpointslice/loki-backend-nh95p                policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
3m2s        Warning   PolicyViolation           endpointslice/query-scheduler-discovery-dr6nq   policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
2m25s       Warning   PolicyViolation           endpointslice/loki-backend-headless-rpp88       policy check-deprecated-apis-1-25/validate-v1-25-removals fail: discovery.k8s.io/v1beta1/EndpointSlice is deprecated and will be removed in v1.25. See: https://kubernetes.io/docs/reference/using-api/deprecation-guide/


REL: Add whatsnew for Zipline 1.2.0

Just a note:
Zipline now requests data for SPY, the default benchmark used for Zipline backtests,
using the `IEX Trading <https://iextrading.com>__` API, and no longer uses
``pandas-datareader``. You can run a backtest up to 5 years from the current day
using this data.

That's...sort of true? pandas-datareader is still used for this one test.

Coverage decreased (-0.4%) to 87.208% when pulling 2aad2450f8db99c8b430a4e769c73a0fa40f5d56 on whatsnew-1.1.2 into 70f8d14778a16f771d8c2ee196a5dba0788e920a on master.

These updates look great to me!

(I expect they're slightly out of date now.)

I think the only thing I need to update here is adding the --bundle-timestamp fix and latest empyrical bump

Sounds right to me.

Anddd just now updated the whatsnew here

👍 from me

Thanks @richafrank!


SIMSBIOHUB 324 - Multiple Ecological Variables (Intended Outcomes)

Links to Jira Tickets

SIMSBIOHUB-324

Description of Changes

Added a migration that removes the intended_outcome_id column from the survey table and shifts the responsibility onto a join table called survey_intended_outcome. This makes it possible to have multiple intended outcomes associated with a single survey.
Modified the frontend and API to support this change. The dropdown in the add and edit forms for the survey have been replaced with a multiselect. Multiselect will still display the subtext associated with these elements.
In various cases where a single intended outcome was displayed before, they display as a comma deliminated list instead.
These items now display with the label of "Ecological Variables" in the frontend survey components.

Running this locally I found some issues:
* I can create a survey with no eco variables selected

* If I edit a survey with eco variables and remove any of them and save, I get an error from the api

These should be resolved now.


sz_capabilities might be incorrect for AVX512

The sz_capabilities function seems to return incorrect values for certain AVX512 instruction sets.
lscpu gives:
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       36 bits physical, 48 bits virtual
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               94
Model name:          Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz
Stepping:            3
CPU MHz:             2496.000
CPU max MHz:         2496.0000
BogoMIPS:            4992.00
Hypervisor vendor:   Windows Subsystem for Linux
Virtualization type: container
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse
                        sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm pni pclmulqdq dtes64 est tm2 ssse3 fma cx16 xtpr pdcm
                        pcid sse4_1 sse4_2 movbe popcnt aes xsave osxsave avx f16c rdrand hypervisor lahf_lm abm
                        3dnowprefetch fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap
                        clflushopt ibrs ibpb stibp ssbd

But the python stringzilla.__capabilities__ gives:
'serial,avx2,avx512vbmi,gfni,'

If I understand cpuid correctly, info1 refers to calling cpuid with eax==1 (From https://en.wikipedia.org/wiki/CPUID).
Then the following code in sz_capabilites is incorrect.
https://github.com/ashvardanian/StringZilla/blob/1a4b05d8d6b7bc617b8e857d36b5dc1869685a7d/c/lib.c#L78-L83
So the info1s should instead be info7s.
As currently:

supports_avx512vbmi: Actually represents pclmulqdq (Supported).
supports_avx512vbmi2: Actually represents smx (Not Supported).
supports_gfni: Actually represents tm2 (Supported).

Yes, @ashbob999! You may be right. If you have a patch, will be happy to test on my end as well 🤗

I haven't made a patch yet, but it should be simply enough to do.
Just replace the 3 info1s with info7s.
I can create a PR with the patch, and test it myself, but it won't be till the weekend.

Yes, that fixes the issue! It would be great if we had similar CPU-capability checks for Arm.

:tada: This issue has been resolved in version 3.8.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


java.lang.NoClassDefFoundError: Could not initialize class com.azure.identity.implementation.IdentityClient [BUG]

I have multimodule spring boot project, In parent pom.xml I have dependencies like below
1.Spring boot dependency
org.springframework.boot
spring-boot-dependencies
2.3.4.RELEASE
pom
import
azure dependency
com.microsoft.azure azure-spring-boot-bom 2.3.3 pom import
and more..
In one of my child project, I am using spring security for that I have used below maven dependencies,
org.springframework.security spring-security-core

org.springframework.boot
spring-boot-starter-security

com.microsoft.azure
azure-active-directory-spring-boot-starter

com.nimbusds
nimbus-jose-jwt

org.springframework.security.oauth
spring-security-oauth2
2.1.5.RELEASE

org.codehaus.jackson
jackson-mapper-asl

com.microsoft.azure azure-keyvault-secrets-spring-boot-starter org.springframework.boot spring-boot-starter-logging com.nimbusds nimbus-jose-jwt
Description of child module:
It is accessing azure key vault and validate whether all properties are present or not.
I did blackduck scan on above child project , I have found 1 issue for spring-security5.3.4.
To fix this issue I follow below link,
https://tanzu.vmware.com/security/cve-2021-22112
The above link clearly says that upgrade spring-security related dependency to version 5.3.8. All the version are coming from parent pom.xml spring boot dependency, So I need to upgrade parent spring boot version to 2.3.9 to get spring security 5.3.8 related jars.
If I upgrade the spring boot version I am getting Below Error.
Error:
java.lang.NoClassDefFoundError: Could not initialize class com.azure.identity.implementation.IdentityClient
Can anyone suggest me which spring boot and azure version are compatible to fix this issue?

Hi @AAvaghade, could you please provide a copy of your pom.xml?

parentpom.xml.txt
childpom.xml.txt
Please find attached copy of parent and child pom.xml

Hi @AAvaghade , thank you for reminding the issue in spring-security. I try to use the azure-boot 2.3.3 and the latest 3.1.0 with spring-boot respective version 2.3.4.RELEASE and 2.3.9.RELEASE, but failed to reproduce your exception, based on your pom file and the sample 2.3.3 and sample 3.1.0, they can work together, could you please provide more details?

@moarychan I have tried as you mentioned with updating spring boot version 2.3.9 and azure-boot version 2.3.3 but still facing same error.
error - Could not initialize class com.azure.identity.implementation.IdentityClient
Any change needs to do in pom.xml?

Hi @AAvaghade , azure boot version is 2.3.3, spring-boot version is 2.3.9, please try to use these pom files
pom - parent.xml.txt
pom.xml.txt
,

@AAvaghade is the problem fixed yet?

Closing this issue now. Please re-open it if the problem still exists.


Fix publish workflow

Fixes #305 by using cargo-publish-all which creates a workspace first, then publishes lychee-lib into it, then publishes lychee-bin using what it just published. So now we can increment the version of lychee-lib and lychee-bin to the next iteration which is the code that we have now on master.
This requires a newer version of rust-type-builder with the fix for https://github.com/idanarye/rust-typed-builder/issues/57.

Hey that's great, thanks!

I think the actual publication should also change to use cargo-publish-all, I'll leave this to you.

🤔 you have a point there


Vulnerability in Django 1.8.10 of OWASP/django-DefectDojo

Your Django 1.8.10 library, a direct dependency in your OWASP/django-DefectDojo repository, is subject to vulnerability SID-2561: Cross-site Scripting (XSS).
A direct dependency is a library that is specified in your project’s setup.py.  A vulnerability in a direct dependency can be fixed by updating the version of the library in your project and rebuilding it.
This issue was fixed in version 1.8.14. However, that version may itself be subject to other vulnerabilities. We suggest that you upgrade to version 1.9.11, which is considered safe.
Be sure to build, test, and re-scan your project to ensure this fix has been successful.
setup.py
...
django == 1.9.11
...

For more information on this vulnerability, please visit the SourceClear Registry.

I took the time to look at all the Source Clear issues entered against Dojo back on April 6th- full details are in this Google Doc.  I figured I should actually add the results to the issues so any of our users can see that we take these things seriously.
Overall for all the issues, I found:

3 False Positives
1 Duplicate
3 Already planned updates of Python modules which we're either not vulnerable or maybe in certain edge cases.

For this specific issue, the TLDR is: This will get fixed in our update to a newer Django - see Issue #250  and I wouldn’t change the priority of that work based on this issue.

I'd like to add that this vulnerability is tied to 'Editor Snippet' a Django CMS feature that let's people using Django for articles to denote code. We do not use the editor snippet. All data stored in DefectDojo goes through the form.is_valid() function (to the best of my knowledge) which escapes data submissions before storage.


runner: create Subscriber interface

Subscriber is a new interface to replace polling (and especially polling that has to just call StatusAll)
Eventually, this should be folded into Runner. It might even (eventually) replace Erase() and Clear() because the Semantics of Subscribing are clearer.
This is just the interface for now (as we discussed)

This is a good concept to explore,  need more background on the use case...  I don't think this is the right venue to discuss my questions... can we cover this in a vc?
In the meantime, here is a summary of my understanding and questions.
I'm interpreting the use case as follows:
The user wants the ability to continuously receive the status of run(s).
They will do so by

defining a subscription as a list of Scoot Daemon runIds, with an optional state filter (mask)
subscribing (Subscribe()) to the definition
actually receive subscribed events in one of 2 ways:
a. via a channel
i.  requesting that the daemon start streaming run status events, starting at an event sequence number (Stream())
ii. loop pulling events from this channel
b. via a Poll request
i. receive a list of events matching the subscription definition once the subscribed runs have met the state filter or a timeout parameter is satisfied
unsubscribing when they no longer want to receive events

questions:

What is the user's motivation? - why do they need to continuously receive the state of runs?
The users would have to write a loop to pull values off the Stream() channel - isn't it simpler for them to just poll each time and not deal with setting up stream?
How does the user obtain the starting event sequence number? (from prior streaming?)
Does unsubscribe only apply with Stream()?
The users would have to write a loop to pull values off the Stream() channel - isn't it simpler for them to just poll each time and not deal with setting up stream?
The users would have to write a loop to pull values off the Stream() channel - isn't it simpler for them to just poll each time and not deal with setting up stream?

I like the subscription idea from the perspective that it could simplify poll-and-wait (or add flexibility to that).  I'm not totally sold on how this would address that, though. Echoing some of Jeanette's comments:

Presumably the subscriber is on the client side - how are they getting the events off of a channel?  Is the subscriber implementation polling the server and populating it?  Or is this the server side logic that will need a corresponding client interface later?
Stream and Poll being based on Event seems odd (plus this seems to be a chicken-and-egg problem where we need an event to start streaming events) - why not use the subscription ID? The "server-side" could keep track of what was sent to a subscriber, and drop events as they are consumed (prevents rewinding).


How can I play flash video content in Basilisk?

So I can play flash content .swf in Basilisk web browser but I can't play .flv flash video.
Basilisk says it cannott recognise the file format amd mime type.
Here is a sample web page.
How can I play flash video content in Basilisk?

Hello, can you try the new Flash installer?
https://github.com/CleanFlash/installer/releases/latest
This should properly install the Flash Player plugin for Basilisk. Let me know if it works.

That installer only installs the chinese version of flash, and it's based on version <IP_ADDRESS>, not <IP_ADDRESS>5

That version of Flash is the newest version out there. It's newer than <IP_ADDRESS>5. It used to be digitally signed by Adobe, meaning it was built by the official Adobe build servers.


Update measuring-experiments.mdx

stableID persistence using a cookie for Sidecar testers

🚀 Deployed on https://666caece273aa917b303b41e--cozy-fox-0defec.netlify.app


support cudnn reproductivity

Config cudnn to be reproducible according to Pytorch doc.

This does not completely support reproducible with CUDA. Only using a single process is reproducible. Reproductivity is still not guaranteed with multiprocessing.


Create method to dynamically enable / disable performance counters

The leveldb performance counters now default to a disabled state. They are enabled when the file "/etc/riak/perf_counters" exists. The content of the file is irrelevant. leveldb's background thread polls for the file once a minute. This allows enabling and disabling the performance counters without restarting leveldb / Riak.
Detailed discussion is here:
https://github.com/basho/leveldb/wiki/mv-perfcounter-disable

:+1:
I've reviewed the code and manually tested the mechanism. I did not re-run your performance benchmarks.
The location of the file is a bit hacky. The location of the check for the file is convenient but hacky. I'm sure I don't have to tell you this :). Hopefully we can make it more sophisticated when we work on exposing more of the stats to Riak.


Generation of CGRect property is changed to Pointer after upgrade ffigen to 10.0.0

When use ffigen 9.0.0 to generate CoreImage bindings, the bounds property of CIFeature is generated like this:
class CIFeature extends NSObject {
  ...
  CGRect get bounds {
    return _lib._objc_msgSend_56(_id, _lib._sel_bounds1);
  }
  ...

But after upgrade ffi to 10.0.0 or 11.0.0, the bounds property is changed to a method with a Pointer arguments:

class CIFeature extends NSObject {
  ...
  void getBounds(ffi.Pointer<CGRect> stret) {
    _lib._objc_msgSend_61(stret, _id, _lib._sel_bounds1);
  }
  ...

Is this behavior correct?
Here is my ffigen.yaml file.
# Run with `dart run ffigen --config ffigen.yaml`.
name: CoreImage
description: |
  Bindings for CoreImage.

  Regenerate bindings with `dart run ffigen --config ffigen.yaml`.
language: objc
output: 'lib/src/core_image.dart'
exclude-all-by-default: true
objc-interfaces:
  include:
    - 'CIDetector'
    - 'CIImage'
    - 'CIFeature'
headers:
  entry-points:
    - '/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreImage.framework/Headers/CoreImage.h'
preamble: |
  // ignore_for_file: always_specify_types
  // ignore_for_file: camel_case_types
  // ignore_for_file: non_constant_identifier_names

This is working as intended. CGRect is a struct, and you can't reliably return structs by value from ObjC methods on all platforms. The old signature was a bug. See https://github.com/dart-lang/native/issues/449


UnboundLocalError: local variable 'x' referenced before assignment

Platform (like ubuntu 16.04/win10):ubuntu 18.04
Python version:3.6.7
Source framework with version (like Tensorflow 1.4.1 with GPU):Tensorflow 1.13.1
Destination framework with version (like CNTK 2.3 with GPU):
Pre-trained model path (webpath or webdisk path):
Running scripts:
WARNING:tensorflow:From /home/wangyuejiao/.local/lib/python3.6/site-packages/tensorflow/python/tools/strip_unused_lib.py:86: extract_sub_graph (from tensorflow.python.framework.graph_util_impl) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.compat.v1.graph_util.extract_sub_graph
Traceback (most recent call last):
File "/media/wangyuejiao/DATA/MMdnn-master/mmdnn/conversion/_script/convert.py", line 123, in
_main()
File "/media/wangyuejiao/DATA/MMdnn-master/mmdnn/conversion/_script/convert.py", line 102, in _main
ret = convertToIR._convert(ir_args)
File "/media/wangyuejiao/DATA/MMdnn-master/mmdnn/conversion/_script/convertToIR.py", line 59, in _convert
parser = TensorflowParser2(args.weights, inputshape, args.inNodeName, args.dstNodeName)
File "/media/wangyuejiao/DATA/MMdnn-master/mmdnn/conversion/tensorflow/tensorflow_frozenparser.py", line 157, in init
input_map[in_nodes[i] + ':0'] = x
UnboundLocalError: local variable 'x' referenced before assignment

@rainLiuplus
Thx for your help,It works!
but I got new issue here:
"Tensorflow has not supported operator [IteratorFromStringHandleV2] with name [superpoint/IteratorFromStringHandleV2]. "
I thought it means the MMdnn can not support this op when convert the pb file to the caffe model.
Do you have any suggestion for this issue?
Thanks!

Hi @moonjiaoer
Seems it is an operator related to data processing. But MMdnn does not support such ops for that they vary from framework to framework.  Thus just converting the network architecture may skip this issue. Thanks!

Hi @rainLiuplus
Thx for your reply.
but I don't know how to skip this op?
Do you mean I can modify the MMdnn code?
Or I need to generate a new pb without this op?

@moonjiaoer,
just skip them via specifying input and output names like  --inNodeName your_input  --dstNodeName your_dst

/home/wangyuejiao/图片/2019-06-04 19-16-55 的屏幕截图.png
Hi I tried your method it's good but still can't solve my issue.
the figure I uploaded is part of my network.
The new issue is quantification.
You can see the node which named "FakeQuantWithMinMaxVars" that's the new problem.
This node will set in the whole network for much times I think it's hard to skip.
Could I modified the code to skip this node?

Hi @moonjiaoer,
could you upload this model then I can help you add this op? Thanks

Hi @rainLiuplus
Thanks for your help.
could you send me your email address?
the model is nearly 78mb.

@moonjiaoer,
<EMAIL_ADDRESS>

Hi @rainLiuplus
Sorry for the late reply.
Here is the link :链接: https://pan.baidu.com/s/1B5ZOghcilm3ZywqLMcIXqg
password(some Chinese characters like"提取码”): 84iw
BTW this is my colleague‘s account.

Hi @zxp771, may I ask the target framework? Thanks

Hi @rainLiuplus
This network is SuperPoint which based on tensorflow, We want to convert the tensorflow's pb file to the caffe model.
Thx for your help and patience.

Hi @rainLiuplus
Sorry to disturb.
Have you tried to convert the model we sent to you?
Thx

Hi @rainLiuplus
Do you have any update for this issue?

Hi @moonjiaoer, sorry, I am busy recently. For this issue, the key problem is that the quant op has no counterpart in Caffe. Thus to solve this issue need to register a new quant op in Caffe.
I will add the support of this op into the work plan. Or maybe you could try to add it first? For guidance on how to add operators, please refer to this. Thanks!

Hi @rainLiuplus
Thx for your reply.
We'll try it first and hope you can bring some good news soon
Thx


Invalid argument:  Input to reshape is a tensor with 307 values, but the requested shape requires a multiple of 14

Hi,
I'm using my own dataset to train the tf2 model. The tfrecord generation process went good, thought I went into a few issues initially but they were sorted out. Pasting the tfrecord generation and hyperparams code:
train_img_dir = f"{BASE_DIR}/images_rows_v4/train/img";
train_anno_dir = f"{BASE_DIR}/images_rows_v4/train/xml";
class_list_file = f"{BASE_DIR}/classes.txt";

gtf.set_train_dataset(train_img_dir, train_anno_dir, class_list_file, batch_size=4)

val_img_dir = f"{BASE_DIR}/images_rows_v4/test/img";
val_anno_dir = f"{BASE_DIR}/images_rows_v4/test/xml";

gtf.set_val_dataset(val_img_dir, val_anno_dir)

gtf.create_tfrecord(data_output_dir=f"{BASE_DIR}/data_tfrecord")

gtf.set_model_params(model_name="ssd_resnet50_v1_fpn_640")
gtf.set_hyper_params(num_train_steps=100000, lr=0.03)

gtf.export_params(output_directory=f"{BASE_DIR}/export_dir2");

This generated the tfrecords and when I run the following script:
python 13_tf_obj_2/lib/train.py
I get the following errors:
Traceback (most recent call last):
  File "13_tf_obj_2/lib/train.py", line 47, in <module>
    tf.compat.v1.app.run(main=main)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/absl/app.py", line 303, in run
    _run_main(main, args)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/absl/app.py", line 251, in _run_main
    sys.exit(main(argv))
  File "13_tf_obj_2/lib/train.py", line 45, in main
    record_summaries=args_["record_summaries"])
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/13_tf_obj_2/lib/models/research/object_detection/model_lib_v2.py", line 631, in train_loop
    loss = _dist_train_step(train_input_iter)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 780, in __call__
    result = self._call(*args, **kwds)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 807, in _call
    return self._stateless_fn(*args, **kwds)  # pylint: disable=not-callable
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 2829, in __call__
    return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1848, in _filtered_call
    cancellation_manager=cancellation_manager)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1924, in _call_flat
    ctx, args, cancellation_manager=cancellation_manager))
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 550, in call
    ctx=ctx)
  File "/home/faizan/code/computer_vision/Monk_Object_Detection/env/lib/python3.7/site-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
    inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument:  Input to reshape is a tensor with 307 values, but the requested shape requires a multiple of 14
	 [[{{node Reshape_5}}]]
	 [[MultiDeviceIteratorGetNextFromShard]]
	 [[RemoteCall]]
	 [[IteratorGetNext]]
	 [[Loss/classification_loss_1/write_summary/ReadVariableOp/_48]]
  (1) Invalid argument:  Input to reshape is a tensor with 307 values, but the requested shape requires a multiple of 14
	 [[{{node Reshape_5}}]]
	 [[MultiDeviceIteratorGetNextFromShard]]
	 [[RemoteCall]]
	 [[IteratorGetNext]]
0 successful operations.
0 derived errors ignored. [Op:__inference__dist_train_step_35102]

Function call stack:
_dist_train_step -> _dist_train_step

Also, I tried setting the batch_size to 1. I have following gpu configs:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.45.01    Driver Version: 455.45.01    CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Quadro K2200        On   | 00000000:04:00.0 Off |                  N/A |
| 42%   27C    P8     1W /  39W |     11MiB /  4043MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    On   | 00000000:05:00.0  On |                  N/A |
|  0%   42C    P2    31W / 151W |    583MiB /  8118MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Thank you for trying out monk. I am glad you found it useful. I will soon look into the error. The development of the library is a little slow these days due to some personal work. I will try my best to find a solution soon.

Actually, the number of classes was wrong in val.record as the those images didn't have the classes which were in the 'train' set. This was resolved after adding more examples in 'val' set so that we have right number of classes there as well.


edit: add schema_id in TableData

Rationale
Closes https://github.com/CeresDB/ceresdb/issues/1157
To be able to get the catalog from the table
Detailed Changes
I found that the Schema was already saved in TableData, so I just added the catalog name.
I added the catalog name to AddTableMeta, But this can't create ceresdb's AddTableMeta structure from manifest_pb::AddTableMeta, I should look for other better ways
I added the schema id to MetaEditRequest, but because MetaEdit involves passing the protoc protocol, I don't save the schema id here
Test Plan
pass

Actually, schema and table schema are not the same things although with a same name... This confused me at the beginning, too.Schema can be seemed as something like tenant, database. We don't have detailed design about How to create schema and Where to store the schema now...
This is my current idea for the issue:

Now schema id is sent to datanode through CreateTableRequest and OpenTableRequest , we just use it and don't need to care persistence of it currently.
Just simply place it into LoadRequest and MetaEditRequest, and then place it into TableData.

Ok, let me revise it

I see this pr has conflicts with main branch now, let me solve it?

Just a moment, please. I'll sort it out😂

See codes, and I found schema_name and catalog_name may be needed, too currently for the final target about expose schema_name and catalog_name through Table interface...
Can please help to add thems with schema_id together in this pr...?

sure!

Thanks @dust1 .


[BEAM-12950] Not delete orphaned files to avoid missing events

Sometimes, when using WriteToFiles in a streaming pipeline in Dataflow, there are missing events. The reason seems to be a race condition that makes some files to be deleted from the temporary folder before moving them to the destination.
https://issues.apache.org/jira/browse/BEAM-12950
The easiest and safest approach right now would be to not delete any files and log a message to warn that some files might be left orphaned in the temporary folder. Eventually, in the next execution, that orphaned file will be moved to the destination, so we don’t lose any event. In addition, the log level should be always INFO, because Dataflow doesn’t accept DEBUG.level.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aaltay

Thank you @davidpr91 for your contribution. I added a few folks who could review. In the meantime, could you look at the failing tests and linter issues?

@aaltay Thank you. I've fixed the linter issues. Regarding the failing test, I would like to understand first what are the orphaned files for and what was the purpose of deleting them, since the test is verifying that the deletion works.

@aaltay Thank you. I've fixed the linter issues. Regarding the failing test, I would like to understand first what are the orphaned files for and what was the purpose of deleting them, since the test is verifying that the deletion works.

Thank you. And I added reviewers, they can help if you have specific questions.

Hi @chamikaramj, @pabloem
The failing test is checking that the orphaned files are deleted, which is not done anymore in this pull request. I would remove the test.
What do you think? What was the purpose of deleting orphaned files?
Thank you

Hi @chamikaramj, @pabloem,

In this screenshot you can see the logs of what happened during an execution with the following conditions:

This line was commented: https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/fileio.py#L677
Running in Dataflow. Logs were switched from DEBUG to INFO to be able to see them in Dataflow logs.

As you can see:

first it writes the file in the temporary folder (https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/fileio.py#L715).
Right after it tried to delete the same file (https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/fileio.py#L676). Taking into account the small time difference between the write and delete logs, I think it could be a race condition.
Since we had the deletion commented, it's not really deleted and afterwards, it's moved to the final destination:
(https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/fileio.py#L638)

If the orphaned file had been deleted, it would never have been moved to the final destination. That's why I propose the workaround in this Pull Request.
Let me know if you need further details.

sorry about the delay on this. Currently we're removing files at an erroneous time. I think we need to delete orphaned files in a subsequent step (after we're sure that there won't be retries). But for now, and since Beam 2.34.0 is around the corner, I think we can move forward with this, because we want to make sure no data is dropped - I will review this by tomorrow and merge it if it looks good

Thanks @pabloem,
Ok. Once you review it, let me know what is the best approach with the unit test in this case. Since it's a temporary solution until the orphaned files are deleted at the correct time, we could comment it.

ooops I used the wrong technique to merge. I apologize to others who will find this improperly merged PR


RFC 5285 header extension support

An initial implementation of RFC 5285 header extensions based on previous work in #17. Please provide feedback :)
This is a breaking change unfortunately. We could probably avoid that with some added complexity if we'd like to.

Not sure why the test is failing on Test WASM 1.13

不知道为什么测试失败 Test WASM 1.13
FAIL
402The command "GOOS=js GOARCH=wasm go test
403  -coverpkg=${coverpkgs} -coverprofile=cover.out -covermode=atomic
404  -exec="${GO_JS_WASM_EXEC}"
405  -v ${testpkgs}
406" exited with 1.

LGTM！

=== RUN   TestRFC8285MultipleExtensions
--- FAIL: TestRFC8285MultipleExtensions (0.00s)
    packet_test.go:238: Marshal failed raw
        Marshaled: [144 224 105 143 217 194 147 218 28 100 39 130 190 222 0 3 51 204 204 204 204 16 170 33 187 187 152 54 190 136 158],
        rawPkt:     [144 224 105 143 217 194 147 218 28 100 39 130 190 222 0 3 16 170 33 187 187 51 204 204 204 204 152 54 190 136 158]

https://travis-ci.org/github/pion/rtp/jobs/685901555#L276

I think I fixed the issue and the test didn't run with the new code. I can try trigger it again. Also, the code coverage is better now but that plugin is also having issues. If you click through to the code coverage page you can see.
@Sean-Der how would you like to handle this PR since it is a breaking change?

The reason the tests are flaky is the iteration order of a map is not guaranteed. So i think we should switch Extensions to use an array instead.

I've added back ExtensionPayload for RFC3550 extensions. This makes these changes backward compatible. Hopefully that means we can merge them into master 😁

I think this is good to go!


Update documentation on typings

Enhancement proposal
Our docs on typings is outdated and does not reflect best practices and consensus on how typings should be added to the codebase.
Additional comments

Has been reworked with the introduction of the typing module. Still incomplete, but at least no longer out of date. Closing this.


Add cancel action to ConfirmController

Fixes #3067

Clean input value

Thanks @mds325!

@mds325 Thanks! if you'd like a suggestion for a next issue to work on, please say so and I'll suggest one. :)

@brainwane Of course I'd like a suggestion

Thanks, @mds325! How about #1303?
Also, remind me, will you be joining us at any of the packaging-related sprints?


[BEAM-11417] Use Cache with time eviction policy for commitCallbacks

r: @dpmills
cc: @kennknowles

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM

Run Java PreCommit


Refactor classPathArg method

classPathsArg => classPathArg
move j2objc default libs to getClassPathArg(…)
indentation

@confile - please take a look

Looks good to me!


got "Utils should be provided" error

Please tell me what i am wrong?
Environment

Tech
Version

material-ui-pickers
1.0.0-rc2

material-ui
next

React
16.2.0

Browser

Platform

Expected behavior

render DatePicker
Actual behavior

Utils should be provided
The above error occourred in the  component
Live example
https://codesandbox.io/s/xo9jo4n85o

Please read the Readme.

this looks like the part of the readme that @dmtrKovalenko is talking about

https://github.com/dmtrKovalenko/material-ui-pickers


Fleshes out the Date module and a bit of the DOM API

NOTE: This PR has been heavily expanded post-submission.
This mostly completes the following modules:

Date
Document
Element down to HTMLElement
History
Location
Range
Selection

And partly implements many more.
It breaks backwards compatibility with (at least) the following:

Window.window
Window.addEventListener
Window..Location.href
Document.getElementById
Document.getElementsByClassName
Promise functions rhave been enamed and converted to pipe form
functions previously in Document have been moved to more appropriate modules.
All Dom bindings with @@bs.set have been converted to pipe form. This does not include setters and other modules like GL.
Pretty much everything that used Js.null or Js.boolean (they're now transformed into option and bool respectively)

Open questions:

How to organize things? Where should enums and constants go and how should they be structured? Where should forward declarations go? Should variants be wrapped in a module (for namespacing and bundling of related logic)?
Should all types be forward declared, just in case?
Should enum variants fail on encode or decode? Or should enums have an Unknown variant hat encodes to some nonsense that will break something later (current approach)?
What should the convention for constants be? Currently _MyConstant.
Should "down-casting" be done with polymorphic or regular variants?
Should setters manually be converted to pipe form?
 Should some or all of it be considered and documented as unstable?
What are the guidelines on what ought to be included here? And what should be implemented in the BuckleScript std lib instead? E.g. String and Array are (partially) implemented in BuckleScript.
What should the policy be for including experimental, deprecated, and "de-facto standard" APIs?
It's not always clear where dom APIs should go. E.g. CanvasElement which is a dom element but also exposes webgl functionality. Should it be put in dom, and the dom depend on GL? Is that future-proof?
What should the convention for overloads be? The current convention of "*With" followed by a list of the parameter names included is a bit verbose (lol at Date)
What shouold the naming convention for abbreviations be? Due to OCaml's rules for which identifiers can be lower case and upper case, the current convention is PascalCase/camelCase, e.g. "Html", "Json", "dom" etc.

Todo:

Event type-specific functions should be pulled out of Event
HtmlElement type-specific functions should be pulled out of HtmlElement
Lots of the dom still missing
Lots of other functionality still missing?
Functional tests, not just "cosmetic"

Initial PR text:
Based roughly on MDN for reference:
https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Date
Notes:

Gecko-specific methods were skipped
Overloads have been given a somewhat ridiculous naming scheme
makeWithString overload skipped for the equivalent and better named parse function
Some deprecated methods have been included, but marked as deprecated
Overloads for the toLocale* methods have been skipped because they're pretty complicated, but they're also not widely supported, so I'm sure it's fine to leave them for now.

@chenglou Ok, module names have been mangled and aliased on ReasonJs. I've also updated the PR description. Any feedback, on the open questions or otherwise, would be greatly appreciated.
Do you need me to chill out a bit so you can go through this, or can I continue to expand the API?

See https://github.com/glennsl/rehydrate/commit/ac7b1b8561fc1b71ef80f3012202c33cd79690da for an example of the changes needed after merging this PR.
 Thanks so much!

I don't even know what squashing is, but thanks! :)


Added compatibility for v2.2.0 LTCGI

Thank you for your PR and I'm sorry for the late reply.
Now I'm working on v3 and I will add some LTC implementation to v3.


Use more toned colors for selected line

How does it look in dark theme?

@lafriks It's very subtle change for arc-green; not that the older color was ever used properly in arc-green to begin with, so...

ping LG-TM

please send backport


scripting: add "selector from array" and "show-set rules from dictionary" snippets

This PR adds snippets for two tasks:

creating a selector (and then show rule) matching any element in a given array
creating show-set rules based on a dictionary, where keys are things to select with show, and values are things to set

The first snippet is relatively trivial, and the second is from this message by Laurenz, bought to my attention by the lovely folks over at the discord :)

Hello there, thank you! I'm really sorry for having you waiting that long. I've totally missed that PR. My bad.
I'm going to spend some time on the book in nearest time, so I'm going to merge the PR as soon as possible. However, there are few changes I want to apply, so hold on a bit.
P.S. Please ping me if I will be missing again. :)

Okay, I will just go on and merge it.

Thank you again!


New package: Psychrometrics v0.1.0

Registering package: Psychrometrics
Repository: https://github.com/aumpierre-unb/Psychrometrics.jl
Created by: @aumpierre-unb
Version: v0.1.0
Commit: a07df0937ca2b807d55a4daf8d6ec5ad4b4c43bb
Reviewed by: @aumpierre-unb
Reference: https://github.com/aumpierre-unb/Psychrometrics.jl/commit/a07df0937ca2b807d55a4daf8d6ec5ad4b4c43bb#commitcomment-94739165
Description: A toolbox for air-water vapor psychrometrics for Julia

I run a few tests and it seems to be working just fine in Julia 1.9.0-beta
(Not sure if this is where i should state it)
[noblock]


--version or -v should print current version, need to work with release pattern as well

resolved in https://github.com/newnoiseworks/omgd/pull/180


New release and pr-commit scripts

These two commits contain two changes:

The first commit modifies the release scripts to move to a branch-then-release model.
The second commit adds a script script/commit-pr.sh that automates the process of FF merging a PR from the command line.

Branch-then-release model
Recently, someone (@ryan-williams?) mentioned the idea of moving to a branch-then-release model. Here, we would make a branch, and then make the release off of this branch. The release commits would not show up on the master branch. This would make it easier to make maintenance releases. Although the Maven release plugin contains a goal for releasing from a branch, the general consensus is that this goal works with SVN but not with Git (I tested this out and this does seem to be the case). It seems like many people advocate the "Gitflow" release approach; however, that seemed like a radical departure from our current model, so I decided not to go that route.
In this PR, we make an update on the starting branch (presumably master, but this is not hardcoded in the scripts, in case we want to make a maintenance release) to the CHANGES.md file. We then make a branch for the Scala 2.10 release, and run the typical Maven release process there. Finally, we make a branch from our starting branch for the Scala 2.11 release. On this branch, we move the pom.xml files from Scala 2.10 to Scala 2.11, and then run the Maven release process. If we start with this structure:

Once the release completes, our repo will look like this:

Once both Scala 2.10 and 2.11 releases succeed, the release script updates the pom.xml's on the master branch to the new development version.
PR Commit scripts
There are two problems with the PR merge button in Github:

The button creates a merge commit per PR.
The hook does not require all merges to be fast-forwards; this means that changes can be merged even if they are not based on the latest commit on master.

The ./scripts/commit-pr.sh script will checkout a single PR, rebase those changes on master, and then merge the changes into master as a fast-forward merge. If there are multiple commits in a pull request, the script will prompt the user as to whether they would like to continue with the merge. If it is a PR where the multiple commits should not be squashed down (like this one), the user can say y to continue, and the merge will go on. If the commits should be squashed, the user can say n to stop the merge, and then manually squash the commits from there. The script will print out the directions for finishing the merge, in the case that it aborts.
If we want to merge a pull request (#1) started from the docs branch in the picture below:

We would run ./scripts/commit-pr.sh 1, which will do the above, and lead to the following branch structure:

Looks awesome, @fnothaft!  One question: with the commit-pr.sh script, will it automatically perform a rebase?  It's probably safer that the script should only automatically proceed if the PR branch is directly dnstream from master.  If not, the person should manually rebase onto master, no?

One thing I noticed with the 0.17.1 release process, the link to CHANGES.md on the releases page does not contain the 0.17.1-related changes
https://github.com/bigdatagenomics/adam/blob/adam-parent_2.11-0.17.1/CHANGES.md
linked from here
https://github.com/bigdatagenomics/adam/releases/tag/adam-parent_2.11-0.17.1
→ Release Notes

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/992/
Test PASSed.

@heuermh

One thing I noticed with the 0.17.1 release process, the link to CHANGES.md on the releases page does not contain the 0.17.1-related changes

This PR resolves that issue.
@laserson

One question: with the commit-pr.sh script, will it automatically perform a rebase? It's probably safer that the script should only automatically proceed if the PR branch is directly dnstream from master. If not, the person should manually rebase onto master, no?

That is correct; it will automatically rebase. My general thought is that as long as the branch has no merge conflicts, doing a rebase will achieve the same results as Jenkins achieves when it merges the branch into master when testing in the PR builder.

@fnothaft (catching up on some GH notifications) So Jenkins doesn't just check out the PR branch, but it actually creates a merge commit before running tests?  This is not how I would expect it to work.  In my experience, there have definitely been rebases/merges that finish smoothly but produce unexpected results.

If we look at the latest ADAM-prb build, it is doing:
Started by upstream project "ADAM-prb" build number 1002
originally caused by:
 GitHub pull request #858 of commit e6c33c1f0a03f323c21d3f2ce142ce583bc75557 automatically merged.
[EnvInject] - Loading node environment variables.
Building remotely on amp-jenkins-worker-04 (centos spark-test) in workspace /home/jenkins/workspace/ADAM-prb/HADOOP_VERSION/2.6.0/SCALAVER/2.11/SPARK_VERSION/1.4.1/label/centos
Cloning the remote Git repository
Cloning repository https://github.com/bigdatagenomics/adam.git
 > git init /home/jenkins/workspace/ADAM-prb/HADOOP_VERSION/2.6.0/SCALAVER/2.11/SPARK_VERSION/1.4.1/label/centos # timeout=10
Fetching upstream changes from https://github.com/bigdatagenomics/adam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://github.com/bigdatagenomics/adam.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/bigdatagenomics/adam.git # timeout=10
Fetching upstream changes from https://github.com/bigdatagenomics/adam.git
 > git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/*:refs/remotes/origin/pr/*
Checking out Revision fcf1d09d57b84b9222f4de34b8941d27348328c9 (origin/pr/858/merge)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f fcf1d09d57b84b9222f4de34b8941d27348328c9
 > git rev-list fac5d5fa86324aebc4128afcbf4bf70a6d4bf9c7 # timeout=10
First time build. Skipping changelog.
[centos] $ /bin/bash /tmp/hudson2880986315095922623.sh

The last line (/bin/bash /tmp/hudson2880986315095922623.sh) runs the start of the build in Jenkins. The important lines are:
 > git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/*:refs/remotes/origin/pr/*
Checking out Revision fcf1d09d57b84b9222f4de34b8941d27348328c9 (origin/pr/858/merge)

Long story short, the branch origin/pr/<number>/merge is a branch that corresponds to what you would get if you pressed the Github merge button for PR <number>.


Problem with the composers?

Hello,
iTunes Web Sources is truly perfect, I was looking for this kind of tool for several years now. Although, I think there is a problem with the composers (maybe Apple changed something on its side), because every single time the composer = the name of the artists. I am using the France version, but the problem also appears with the U.S. version.
Any idea maybe?
Thanks!

Composers uses the same name as artist field
Because iTunes API doesn't provide composer information.


take channel-reserve into account when determining the rebalance amt

Especially when rapid-rebalancing we want to take the channel-reserve into account to not fail prematurely.
Scenario:
This optimizes the follow problem. Imagine we are able to rapid-rebalance a channel up to the reserve amount (using pfrom or pto of around >80%. Then in the
current rapid-rebalance logic we fail because when not taking the channel-reserves into account we assume to high amounts for the next rebalance and fail building
the route most likely with an error like: could not find outgoing channel ...
Therefore this PR introduces to account to a generous reserve of 2% to not run into edge-cases where we cannot actually reach the protocol defined 1% of the
capacity because the commitment fee when building up the htlc can mess things up.
This helps allow the rapid-rebalancer to "hit the wall" and also try the small amount when the big amount failed.

I'll try to take a look on weekend, I know this PR was open for too long already but I always had something important to do in my free time. Sorry!

Tested on Polar, works as expected. Thanks!


future: fix tests

This fixes three test failures/errors, and adds tests for OutputWriter (for the moved annotation code).
(this is included in #169)

@nvie
Without this being merged the Travis build results for new PRs are not that useful (because they will all fail).
Therefore, please merge / review this.

@nvie
Please re-open?!

Sorry 'bout that — reopened.

Thanks a lot!

This is now merged into master, so I'll manually close this PR that targets the future branch.


Downloading Chromium r737027 - 118.4 Mb [====================] 99% 0.0s ⸨                  ⸩

Chromium r737027 never completes to download.
Expected this to be 100% so it works.

@rodoabad this works for me:
node ./install.js
Downloading Chromium r737027 - 118.4 Mb [====================] 100% 0.0s
Chromium (737027) downloaded to /Users/<redacted>/.local-chromium/mac-737027

Can you provide for information on your environment?


Android Basics: Activities and intents

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-activities-intents?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-activities-intents#5
In which task and step of the codelab can this issue be found?
Step 6(Se tup DetailActivity) paragraph 5
Describe the problem
This is paragraph 5:
While you're at it, you can also move any other hard coded value into the companion object in DetailActivity. Remember when you performed the implicit intent in the WordAdapter, you passed in part of the URL to perform a Google search? Go ahead and move this to the companion object as a new constant called SEARCH_PREFIX. The companion object should now contain two constants.
The problem is that the step described as already done, is on the next step "7 Set up Implicit Intent. So it is confusing for somebody trying to remember and go searching backwards for something that it was never there, and finaly when gives up searching recalling his memory and moves to the next step, finding out that paragraph 5 refers to a next step. It is no big deal but I'm trying to help others from wasting time.
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

@Titanium933
Thank you so much for reporting this issue. This is fixed and will be published soon.

@Titanium933
Thank you so much for reporting this issue. This is fixed and will be published soon.


No exons in transcript model.

When a transcript is used in the name checker, error ESELECTORMODELNOEXONS may be raised. The name checker can and should continue in this case, by assuming that the whole transcript is one big exon.

Fixed. However, there is no info/warning message provided. I leave it open until we implement that functionality.


Regenerate patch files for gettext 0.21.1

Fixes build failure on macOS 13 whose patch program does not apply fuzzy patches.
Fixes #781

Thanks!


[WIP] Generalize gcc dependency relto v1.0

This does not install gcc but the newer Anaconda compilers (see https://conda.io/docs/user-guide/tasks/build-packages/compiler-tools.html).  Tests will fail until GNUCompiler honors environment variables hinting to the GCC binary to use.

Note that #282 might quite radically change the installation instructions and at the same time simplify what's necessary to add to the documentation in this PR.
To wrap this PR up, we'll need to create three env files covering the dependencies for Linux,
for OSX, and for Windows as detailed in the recipe for the conda-forge package, and then have Travis use the Linux file.

@erikvansebille This PR now only adds / modifies the env files which use what I learned during https://github.com/conda-forge/parcels-feedstock/pull/9 and https://github.com/conda-forge/parcels-feedstock/commit/d2c04f79aee4d9d11299ce02f7d68303fc34eaaf.  I've reverted changes to the compiler.py as these should only be made after some discussion in #284.

@erikvansebille: Documentation updates accounting for the new env files are not done yet.  But let's wait what you think of #282.

I think it's all done.
Changes:

There are three env files now which define the dependencies for Linux, OSX, and Windows.  They are mirroring the dependencies of the conda-forge package.
Travis runs everything that was done before this PR on a Linux VM.
Travis runs parcels_get_examples and the units tests from tests/ on an OSX VM (I've skipped the notebooks and flake / link checking).
Documentation points to the three env files in developer's installation instructions.

@erikvansebille: This is quite messy now.  Could you have a look and rebase / squash before merge using the Github GUI?  I could also rebase locally and open a new PR to give you a cleaner history to merge from.

I'll make the example download Linux-only as well and rebase in a fresh PR then.

See #294 for a rebased version.  Closing here.


R__ and V__ Script change list. Reopening after bugfix merge

My original PR for this closed when I merged the bugfix from PR 149 into my fork. This is just reopening after resolving any conflicts from bugfix to my branch.
Issue: 148
Original PR: PR 145
@sfc-gh-jhansen Versions and such are all up to date.

@eaguilera23 I updated the readme and the argeparse help value.

@sfc-gh-jhansen Were there other items that needed to be addressed for this?

Here there @CermitDFrog, sorry for the delay here. I've just been slammed with work lately and haven't had time to test/review this. Hoping to get to this in the next few days 🤞 .

Probably something that could wait to be a follow-up, but thoughts on the flag accepting a pattern?

Hello @afeld, Thank you for bringing up the idea. Could you open a new issue and describe the --path option with an example and expected output.

Hello @CermitDFrog
We have started reviewing open issues and PRs. This PR still has merge conflicts. Could you help again by taking a look and see if you can resolve your fixes to the latest release ?
Thank you for your contributions!


Sound library reference: saveSound page contains a bad link

Most appropriate sections of the p5.js website?
Libraries
What is your operating system?
Mac OS
Web browser and version
Safari 17.2
Actual Behavior
On the reference page for saveSound(): "For uploading audio to a server, use p5.SoundFile.saveBlob" the link is no longer valid.
Expected Behavior
Information about saveBlob
Steps to reproduce
go to the page and click on the link.
Would you like to work on the issue?
I'm not sure how to help. Sorry

Hey, @MattObject are you working on this issue ,if not i would love to work on this issue and fix the link ASAP.

Hi there. I was reporting the issue, and not sure how to fix. I just reported it. I'd like to fix as well, but have no clue!


query and Binary data?

(still getting my feet wet - apologies if I missed something)

The CosmWasm docs and examples show that it's allowed for a contract to return Binary data. However, I don't see this when I look in the TxLogs ... is there a different way of getting this data via Terra.JS? I do see attributes...

Similarly, the CosmWasm docs show a separate ability for Query messages. I don't see this in Terra.JS

oh I see query is on the .wasm module... but binary data?

Sorry - let me clarify. For Queries it all works fine - contract returns binary data and it shows up as JSON on the client side.
However, for Execute, I call set_data on the contract but I do not see it in the transaction logs

It's could not be fully compatible because we integrated CosmWasm in very early stage.


importer cannot handle spaces in places where data is intended to be missing

Our importer cannot handle situations where we have a space in a in a tab delimited row which is remnant from editing data. When you open up the attached file in Excel, you'll see that there is a space in cell L8.
The importer will create the set of occupancy types, but not import any because they all have this extra space character. No message is provided to the user.
occTypes-allNormal.txt

@Brennan1994 bad news ... there is something wrong with this file (I couldn't figure it out) that 1.4.3 could handle, that our importer cannot

I successfully imported into 1.4.3, then re-exported, and successfully imported into 2.0

I assigned a priority label to this because I think that the format issue came out of a typical workflow in editing occupancy type files, and so typical format issue that our 1990s software handles it.

It looks like the primary difference between the file that works in 2.0 and that which does not (but does work for 1.4.3) is a missing -901.

THERE IS MORE THAN 1000 LINES OF CODE SPECIFICALLY FOR HANDLING OCC TYPE IMPORT!


Error when trying to pull hello-world-nginx image

Expected behavior
Image successfully be created
Actual behavior
failed to register layer
Information about the Issue
failed to register layer: re-exec error: exit status 1: output: ProcessBaseLayer C:\ProgramData\Docker\windowsfilter\ee4f41db28e1642fc9997ee63580fe1709c72f714d578bfa6879449f1ea380fc: The system cannot find the path specified.
Steps to reproduce the behavior

Run Kitematic
Try Create hello-world-nginx:latest iamge

this is a docker issue not KItematic's issue.
try creating a container using PowerShell

docker container run -d -p 80:80 nginx:latest

if this also doesn't work correctly then it's a docker containerization issue.
try changing Docker service from Windows to "Switch to Linux Container" and try to pull the images.


Issue with poetry add and poetry add git+ install of deepbench

Describe the bug
I had some issues with package conflicts when trying to install deepbench in my poetry environment. I specifically was unable to install it using poetry add deepbench==0.2.01 and poetry add git+https://github.com/deepskies/DeepBench.git. See error report below. The technique that ended up working for me was running pip install deepbench==0.2.01 in the poetry shell.
To Reproduce
Steps to reproduce the behavior:

Open a poetry environment.
poetry add deepbench==0.2.01
poetry add git+https://github.com/deepskies/DeepBench.git
See error

Expected behavior
Expect poetry to be able to install deepbench via resolving conflicts between dependencies.
Error printout
`(hierarchical-pendulum-draw-py3.10) (base) rnevin@mac-141002 notebooks % poetry add deepbench==0.2.01
Configuration file exists at /Users/rnevin/Library/Preferences/pypoetry, reusing this directory.
Consider moving TOML configuration files to /Users/rnevin/Library/Application Support/pypoetry, as support for the legacy directory will be removed in an upcoming release.
Updating dependencies
Resolving dependencies... (1.2s)
Because no versions of scikit-image match >0.20.0,<0.21.0

and deepbench (0.2.1) depends on scikit-image (>=0.20.0,<0.21.0), deepbench (0.2.1) requires scikit-image (0.20.0).
(1) So, because scikit-image (0.20.0) depends on scipy (>=1.8,<1.9.2), deepbench (0.2.1) requires scipy (>=1.8,<1.9.2).
Because no versions of scipy match >1.8,<1.8.1 || >1.8.1,<1.9.0 || >1.9.0,<1.9.1 || >1.9.1,<1.9.2

and scipy (1.8.0) depends on numpy (>=1.17.3,<1.25.0), scipy (>=1.8,<1.8.1 || >1.8.1,<1.9.0 || >1.9.0,<1.9.1 || >1.9.1,<1.9.2) requires numpy (>=1.17.3,<1.25.0).
And because scipy (1.8.1) depends on numpy (>=1.17.3,<1.25.0), scipy (>=1.8,<1.9.0 || >1.9.0,<1.9.1 || >1.9.1,<1.9.2) requires numpy (>=1.17.3,<1.25.0).
And because scipy (1.9.0) depends on numpy (>=1.18.5,<1.25.0)
and scipy (1.9.1) depends on numpy (>=1.18.5,<1.25.0), scipy (>=1.8,<1.9.2) requires numpy (>=1.17.3,<1.25.0).
And because deepbench (0.2.1) requires scipy (>=1.8,<1.9.2) (1), deepbench (0.2.1) requires numpy (>=1.17.3,<1.25.0)
So, because hierarchical-pendulum-draw depends on both numpy (^1.25.0) and deepbench (0.2.01), version solving failed.`
`(hierarchical-pendulum-draw-py3.10) (base) rnevin@mac-141002 notebooks % poetry add git+https://github.com/deepskies/DeepBench.git
Configuration file exists at /Users/rnevin/Library/Preferences/pypoetry, reusing this directory.
Consider moving TOML configuration files to /Users/rnevin/Library/Application Support/pypoetry, as support for the legacy directory will be removed in an upcoming release.
Updating dependencies
Resolving dependencies... (0.0s)
The current project's Python requirement (>=3.9,<4.0) is not compatible with some of the required packages Python requirement:

deepbench requires Python >=3.8,<3.11,, so it will not be satisfied for Python >=3.11,<4.0

Because hierarchical-pendulum-draw depends on deepbench (0.1.0) @ git+https://github.com/deepskies/DeepBench.git@HEAD which requires Python >=3.8,<3.11,, version solving failed.
• Check your dependencies Python requirement: The Python requirement can be specified via the python or markers properties
For deepbench, a possible solution would be to set the `python` property to ">=3.9,<3.11"

https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
https://python-poetry.org/docs/dependency-specification/#using-environment-markers`

And then the one that worked (pip install):
`(hierarchical-pendulum-draw-py3.10) (base) rnevin@mac-141002 notebooks % pip install deepbench==0.2.01
Collecting deepbench==0.2.01
Downloading deepbench-0.2.1-py3-none-any.whl (33 kB)
Collecting astropy<6.0.0,>=5.2.2 (from deepbench==0.2.01)
Downloading astropy-5.3.2-cp310-cp310-macosx_11_0_arm64.whl (7.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.0/7.0 MB 12.7 MB/s eta 0:00:00
Collecting autograd<2.0,>=1.5 (from deepbench==0.2.01)
Downloading autograd-1.6.2-py3-none-any.whl (49 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 49.3/49.3 kB 3.7 MB/s eta 0:00:00
Requirement already satisfied: h5py>=3.9.0 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from deepbench==0.2.01) (3.9.0)
Requirement already satisfied: matplotlib<4.0.0,>=3.7.1 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from deepbench==0.2.01) (3.7.1)
Requirement already satisfied: numpy<2.0.0,>=1.24.3 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from deepbench==0.2.01) (1.25.0)
Requirement already satisfied: pyyaml<7.0,>=6.0 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from deepbench==0.2.01) (6.0)
Collecting scikit-image<0.21.0,>=0.20.0 (from deepbench==0.2.01)
Downloading scikit_image-0.20.0-cp310-cp310-macosx_12_0_arm64.whl (12.7 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 12.7/12.7 MB 9.7 MB/s eta 0:00:00
Collecting pyerfa>=2.0 (from astropy<6.0.0,>=5.2.2->deepbench==0.2.01)
Downloading pyerfa-<IP_ADDRESS>-cp310-cp310-macosx_11_0_arm64.whl (333 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 333.2/333.2 kB 8.7 MB/s eta 0:00:00
Requirement already satisfied: packaging>=19.0 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from astropy<6.0.0,>=5.2.2->deepbench==0.2.01) (23.1)
Collecting future>=0.15.2 (from autograd<2.0,>=1.5->deepbench==0.2.01)
Downloading future-0.18.3.tar.gz (840 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 840.9/840.9 kB 5.4 MB/s eta 0:00:00
Preparing metadata (setup.py) ... done
Requirement already satisfied: contourpy>=1.0.1 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (1.1.0)
Requirement already satisfied: cycler>=0.10 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (0.11.0)
Requirement already satisfied: fonttools>=4.22.0 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (4.40.0)
Requirement already satisfied: kiwisolver>=1.0.1 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (1.4.4)
Requirement already satisfied: pillow>=6.2.0 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (9.5.0)
Requirement already satisfied: pyparsing>=2.3.1 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (3.1.0)
Requirement already satisfied: python-dateutil>=2.7 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (2.8.2)
Requirement already satisfied: scipy>=1.8 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01) (1.9.3)
Collecting networkx>=2.8 (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01)
Downloading networkx-3.1-py3-none-any.whl (2.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 14.4 MB/s eta 0:00:00
Collecting imageio>=2.4.1 (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01)
Downloading imageio-2.31.1-py3-none-any.whl (313 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 313.2/313.2 kB 18.8 MB/s eta 0:00:00
Collecting tifffile>=2019.7.26 (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01)
Downloading tifffile-2023.8.12-py3-none-any.whl (220 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 221.0/221.0 kB 13.6 MB/s eta 0:00:00
Collecting PyWavelets>=1.1.1 (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01)
Downloading PyWavelets-1.4.1-cp310-cp310-macosx_11_0_arm64.whl (4.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.3/4.3 MB 13.6 MB/s eta 0:00:00
Collecting lazy_loader>=0.1 (from scikit-image<0.21.0,>=0.20.0->deepbench==0.2.01)
Downloading lazy_loader-0.3-py3-none-any.whl (9.1 kB)
Requirement already satisfied: six>=1.5 in /Users/rnevin/Library/Caches/pypoetry/virtualenvs/hierarchical-pendulum-draw-aBerWqfY-py3.10/lib/python3.10/site-packages (from python-dateutil>=2.7->matplotlib<4.0.0,>=3.7.1->deepbench==0.2.01) (1.16.0)
Building wheels for collected packages: future
Building wheel for future (setup.py) ... done
Created wheel for future: filename=future-0.18.3-py3-none-any.whl size=492022 sha256=5ac3efa78a619ca8a7f3bfd8511b5a16a44bf0a656d1ae227d634b7ca9f985b4
Stored in directory: /Users/rnevin/Library/Caches/pip/wheels/5e/a9/47/f118e66afd12240e4662752cc22cefae5d97275623aa8ef57d
Successfully built future
Installing collected packages: tifffile, PyWavelets, pyerfa, networkx, lazy_loader, imageio, future, scikit-image, autograd, astropy, deepbench
Successfully installed PyWavelets-1.4.1 astropy-5.3.2 autograd-1.6.2 deepbench-0.2.1 future-0.18.3 imageio-2.31.1 lazy_loader-0.3 networkx-3.1 pyerfa-<IP_ADDRESS> scikit-image-0.20.0 tifffile-2023.8.12
[notice] A new release of pip is available: 23.1.2 -> 23.2.1
[notice] To update, run: pip install --upgrade pip
(hierarchical-pendulum-draw-py3.10) (base) rnevin@mac-141002 notebooks % python
Python 3.10.12 (main, Jun 20 2023, 19:43:52) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import deepbench`

Desktop (please complete the following information):

OS: Ventura 13.5 M1 Max

No longer using deepbench, so closing this


Remove new cmake builtins

Rework the CMakeLists.txt file so we don't need to require a very new version of CMake.

Found stuff in #1117 that touches some part of this


⚠ Bofrost.be has degraded performance

In bf9deea, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1635 ms

Resolved: Bofrost.be performance has improved in fc65905 after 7 minutes.


adding several more advisories for aiohttp-session and ansible

Of course, I'm still working to validate that things are working as I'd expect, but I can describe generally what I'm doing.  For the past several months I've been manually building up a catalog of package names to relevant CPE components at https://github.com/westonsteimel/package-metadata/.  It is mostly created from taking the information from the GitHub Security Advisory Feed which has package name, then if there is a CVE, looking that up and grabbing all of the CPEs off of it, filtering some stuff out, generating the toml file, and then manually reviewing all of them.  I have a quickly hacked-together python script at https://github.com/westonsteimel/nvd-data-analysis/blob/main/ghsa.py that I use to generate or update the config files before reviewing them.
Anyways, for now I've created a slightly modified version of the triage tool at https://github.com/westonsteimel/osv/tree/use-package-metadata that can take a file with all of that package -> CPE configs information for pypi packages and possibly find a match that wouldn't otherwise be found.  Now I haven't actually done much looking at how many extra advisories it generates vs the normal triage tool.  I've run it on the entire history of the nvd cve feed from 2002, and I am very slowly going through and checking each of the output files.


Own strategies

Hi,
I would like to disable plugin logic, in this case I would be able to disable some configuration like auto save token in local storage and override it by my own strategies in login(credentials).then promise function.
For me this plugin can be used only for communicate with server and exchange token correctly, the logic is independent and it change based on the user strategy.
Can this is a possible future request?

Nobody?