Try static analyzers on the Solidity code

Like the ones listed in
https://ethereum.stackexchange.com/questions/31519/security-analysis-tool-for-ethereum-smart-contracts?rq=1

Manticore
Mythril
Echdna
Oyente
Solgraph
Solcheck
solint
solium
solhint

(venv) parupunte% myth -x --solc-args ".=. lib=contracts/lib raiden=contracts/raiden test=contracts/test services=contracts/services" contracts/raiden/TokenNetwork.sol

The analysis was completed successfully. No issues were detected.

==== Integer Overflow ====
SWC ID: 101
Severity: High
Contract: SecretRegistry
Function name: registerSecretBatch(bytes32[])
PC address: 392
Estimated Gas Usage: 340 - 435
The binary multiplication can overflow.
The operands of the multiplication operation are not sufficiently constrained. The multiplication could therefore result in an integer overflow. Prevent the overflow by checking inputs or ensure sure that the overflow is caught by an assertion.
--------------------

Everything that can be easily be done has been done.


Indexing into EagerTensor returns all zeros (on Windows w/ CUDA)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): YES
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): WIN 10 LTSC BUILD 17763
TensorFlow installed from (source or binary): BINARY - https://pypi.org/project/tensorflow/2.3.0/
TensorFlow version (use command below): 2.3.0
Python version: 3.6.8
CUDA/cuDNN version: 10.1, CUDNN 7.6.5
GPU model and memory: Quadro M2000M, 4096MiB

TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
v2.3.0-rc2-23-gb36436b087 2.3.0
Describe the current behavior
Specifically on this Windows system, with CUDA enabled (not happening w/ os.environ["CUDA_VISIBLE_DEVICES"] = "-1", and not happening on my Linux system at all), reading a tfrecord with tf.data.* returns an EagerTensor which attempting to index results in incorrect zero output.
Describe the expected behavior
Indexing into the EagerTensor should return the correct output!
Standalone code to reproduce the issue
Gist: https://gist.github.com/optiluca/ff34d153c9ff339adedf5f905cdc8240
On a working system the output is:
tf.Tensor([100. 105. 110. 115. 120.], shape=(5,), dtype=float32)
100.0
100.0
On my windows system:
tf.Tensor([100. 105. 110. 115. 120.], shape=(5,), dtype=float32)
0.0
100.0

I have tried in colab with TF version 2.3 and i am not seeing any issue.Please, find the gist here.
I have not tested on windows.Thanks!

Hi @ravikyram.  As per issue #42506 I've tried with:
W10 + M2000M (as per original issue) -> broken
Ubuntu+ V100 -> working
W10 + T2000 -> working
So it appears to be specific to my card, presumably because CUDA architecture 5.0 is no longer supported.  The particular failure mode in this case still leaves something to be desired, I'd expect some sort of error to be thrown at least!
Thanks,
Luca

So it appears to be specific to my card, presumably because CUDA architecture 5.0 is no longer supported.

Can you please check TF nightly?  If this works on TF nightly (which includes SASS for 5.0) then it should work on TF 2.4 as well.
I agree that the (lack of) error reporting is surprising, can you please attach the full logs from your run?

@optiluca
Could you please refer to this gist and confirm if this issue can be closed.


Arrow bounces when window is resized

Was not able to reproduce in both Firefox and Brave. Is this still an issue with the arrow?
The resizing of the inner light grey card could be replaced with some flex positioning though.

yah, seems like that is no longer issue. But the container is limited by some max size, I guess this is what you mean by the flex positioning?

Yes exactly


[BUG] - Apple doesn't like the extra brew step to make it "WORK"

Description
Ventura ate my installer, and then ventura ate my brew installer -- it worked fine the first time, and brew will tell me it STILL EXISTS, but  Ventura made me trash the app, and the command you gave to make my OS behave must only work on catalina because Ventura goes "Doesnt exist parental screech"
Not your fault btw, just warning you that the only way to get it to work on mac is the following at the moment for ventura and above:

do the linux install
Realize that it won't accept the brew install of tkinkter, and while you will use half of that so install it via brew ANYWAYS via: brew install python-tk
Cry because you still have 5 more manual packages your OS ignores from the brew install.
Once you get those, it works via the terminal command.

Reproduction steps

Attempted brew install again
Wouldln't update because we updated it last time
After updating it told us 'CORRUPTED' (whcih is ventura speak for: 99 dolla baby)
Tried the manual way
Ventura corrupted the INSTALLER AGAIN.
Used the linux way.

You'll get about 3 "Module not founds" in and you'll want to do: brew install python-tk
You'll still have a miniscule amount of stuff to install but within 2-5 extra modules..
VOILA! sd-prompt reader finally loads!

Again: this is more a mac/ventura issue, it's not the developers issue, it's just that sadly if you're on VENTURA or above, you'll have to use the linux version and then step by step panic when yo urealize you can't use "sudo apt'
For security reasons i don't want to screenshot my WHOLE terminal, (because i dont know if showing my location in my drive is safe or not, it probably is.. i don 't know?) - plus tracking each specific issue is a nightmare in this, it's just Ventura yeeting the easy ways for hard ways.
Image file

Version
1.3.4
OS
Mac (Intel)
Tool
A1111's webUI

just letting you know, that in return: you don't have to try and FIX the easy install for ventura etc-  just that the linux install will be the safest bet to move around the 99 dollar a year nutsoid requirement for a free app that is priceless <3

Darn! This is just a nightmare! Everything is fine with my Intel MBP 2019 and Sonoma. Maybe you should ask ChatGPT how to fix your brew :)
If I remember correctly, brew reinstall will ignore existing installations and reinstall. So you can try:
brew reinstall --no-quarantine receyuki/sd-prompt-reader/sd-prompt-reader
Actually, aside from using pip, you could also try the methods here, although they might be a bit troublesome.
https://github.com/receyuki/stable-diffusion-prompt-reader#sd-prompt-readerapp-is-damaged-and-cant-be-opened-you-should-move-it-to-the-trash


Class vs Struct for Decoding

Let's say I have this simple XML:
let sample = """
            <wrapper>
                <firstName>Peter</firstName>
                <lastName>Ent</lastName>
                <address>Atlanta, GA</address>
            </wrapper>
        """

And I wish to decode it into the following Swift classes:
class MyBase: Codable {
    var firstName: String?
    var lastName: String?
}

class MyAddress: MyBase {
    var address: String?
}

I've set up set up a function like this:
func decodeMessage<T: Codable>(_ data: Data) -> T? {
        let response = try? XMLDecoder().decode(T.self, from: data)
        return response
}

When I call it as follows:
let dataIn = sample.data(using: .utf8)!
if let person = parser.decodeMessage(dataIn) as MyAddress? {
        print("Decode works: \(String(describing: person.firstName)) \(String(describing: person.lastName)) at \(String(describing: person.address))")
}

It only parses the MyBase class (firstName and lastName), ignoring address in the MyAddress class. Why is that?
I can work around this by using CodingKeys and implementing encode and decode functions, but I shouldn't have to, right?
Or am I missing something?

Unfortunately, you have to implement init(from decoder:) and encode functions manually when using classes with inheritance, this is how Codable works. This is also the case for JSONDecoder.

Unfortunately, you have to implement init(from decoder:) and encode functions manually when using classes with inheritance, this is how Codable works. This is also the case for JSONDecoder.

A workaround could be to use composition instead of inheritance:
struct Person: Codable {
    let nameDetails: NameDetails
    let address: Address

    init(from decoder: Decoder) throws {
        let container = try decoder.singleValueContainer()
        nameDetails = try container.decode(NameDetails.self)
        address = try container.decode(Address.self)
    }

    func encode(to encoder: Encoder) throws {
        var container = encoder.singleValueContainer()
        try container.encode(nameDetails)
        try container.encode(address)
    }
}

struct NameDetails: Codable {
    var firstName: String?
    var lastName: String?
}

struct Address: Codable {
    var address: String?
}

let personJSON = #"{ "firstName": "Peter", "address": "Atlanta, Georgia, USA" }"#.data(using: .utf8)!
let addressJSON = #"{ "address": "London, United Kingdom" }"#.data(using: .utf8)!

let decoder = JSONDecoder()
let person = try! decoder.decode(Person.self, from: personJSON)
let address = try! decoder.decode(Address.self, from: addressJSON)

This way you'd only need to maintain custom Codable implementation only for the base Person type, while any fields added to NameDetails or Address would be handled automatically. I'm using JSON as an example here, but I would expect it to work the same with XMLCoder.
@peterent does that help with your issue?

A workaround could be to use composition instead of inheritance:
struct Person: Codable {
    let nameDetails: NameDetails
    let address: Address

    init(from decoder: Decoder) throws {
        let container = try decoder.singleValueContainer()
        nameDetails = try container.decode(NameDetails.self)
        address = try container.decode(Address.self)
    }

    func encode(to encoder: Encoder) throws {
        var container = encoder.singleValueContainer()
        try container.encode(nameDetails)
        try container.encode(address)
    }
}

struct NameDetails: Codable {
    var firstName: String?
    var lastName: String?
}

struct Address: Codable {
    var address: String?
}

let personJSON = #"{ "firstName": "Peter", "address": "Atlanta, Georgia, USA" }"#.data(using: .utf8)!
let addressJSON = #"{ "address": "London, United Kingdom" }"#.data(using: .utf8)!

let decoder = JSONDecoder()
let person = try! decoder.decode(Person.self, from: personJSON)
let address = try! decoder.decode(Address.self, from: addressJSON)

This way you'd only need to maintain custom Codable implementation only for the base Person type, while any fields added to NameDetails or Address would be handled automatically. I'm using JSON as an example here, but I would expect it to work the same with XMLCoder.
@peterent does that help with your issue?

Another option is declare custom Codable conformance in your derived MyAddress class as shown in this SO answer. But you still have to tell the decoder that you're decoding MyAddress upfront, it won't be able to figure out whether to decode a base class or a derived class dynamically.

Another option is declare custom Codable conformance in your derived MyAddress class as shown in this SO answer. But you still have to tell the decoder that you're decoding MyAddress upfront, it won't be able to figure out whether to decode a base class or a derived class dynamically.

@MaxDesiatov Another question related to Class vs Struct. I've got decoding working with a class but when i change that class to a struct, the decoding no longer works. Why would that be?

It's very hard to say without looking at the actual code. Do you have an isolated reproducible test case for this?

I'll try to set something up.


Add this library to vcpkg

Hi all,
Thanks for this wonderful library. It would be awesome if we could add this to vcpkg, so that I can have all of my dependencies installed in one command 😁

Great idea :)
I submitted PRs to vcpkg:

qcoro-qt5: https://github.com/microsoft/vcpkg/pull/33272/
qcoro-qt6: https://github.com/microsoft/vcpkg/pull/33273

For now without OSX support, because the release build in the CI crashes the Apple Clang compiler, but I'll look into later.


LauncherSpec: Let it work on Windows

Relates to #703.
Overview

LauncherSpec used posix commands for testing.
This substitutes equivalent commands when running on windows.

Rebased and fixed the OS detection, so now the tests pass.

bors r+


Updating README

Codecov Report

Merging #35 (6de10a7) into master (4697232) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6de10a7 differs from pull request most recent head 888a53d. Consider uploading reports for the commit 888a53d to get more accurate results

@@           Coverage Diff           @@
##           master      #35   +/-   ##
=======================================
  Coverage   95.06%   95.06%
=======================================
  Files          12       12
  Lines         365      365
=======================================
  Hits          347      347
  Misses         18       18

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4697232...888a53d. Read the comment docs.


Twitter uses new color

Twitter updated it's colour to #1DA1F2
See https://cdn.cms-twdigitalassets.com/content/dam/brand-twitter/asset-download-zip-files/Twitter_Brand_Guidelines.pdf

Fixed in my pull request in #123


Clock divider changes without rising edge

Clock div should only change on rising edge of clockdiv pin. But it changes as input pins change

Not sure about this


saving basic transaction hangs

I'm following the datastore docs, and trying to do an example save in a transaction, but the code just hangs.
I am guessing that the docs for transactions is incomplete.   Please inform me of the actual way to do transactions, and update the docs a bit (add at least 1 transaction example?)
the following code never executes any of the callbacks.  running this example outside a transaction works fine.

    // Save data to your dataset.
    var blogPostData = {
        title: 'How to make the perfect homemade pasta',
        author: 'Andrew Chilton',
        isDraft: true
    };

    var blogPostKey = dataset.key('BlogPost');

    dataset.runInTransaction((transaction, done) => {

        transaction.save({
            key: blogPostKey,
            data: blogPostData
        }, function (err) {
            if (err) {
                return transaction.rollback((err, apiResponse) => {
                    console.log("in xact rollback callback 1", { err, apiResponse });
                });
            }
            console.log("preview save 1", arguments);
            // `blogPostKey` has been updated with an ID so you can do more operations
            // with it, such as an update.
            blogPostData.isDraft = false;

            transaction.save({
                key: blogPostKey,
                data: blogPostData
            }, function (err) {
                if (err) {
                    return transaction.rollback((err, apiResponse) => {
                        console.log("in xact rollback callback 2", { err, apiResponse });
                    });
                }

                // The blog post is now published!
                console.log("preview save 2 DONE!", arguments);
                done();

            });
        });

    }, (err) => {
        console.log("xact insert err", err);
    });

We just overhauled the docs, and it looks like there is indeed a bug: https://googlecloudplatform.github.io/gcloud-node/#/docs/v0.27.0/datastore/transaction?method=save
If you go there, you'll see it describes save but using a Dataset object for the examples. If you scroll down past those examples, you'll see another section for save, but this time the examples use a transaction.
Here's how to make your example code above work:
// Save data to your dataset.
var blogPostData = {
    title: 'How to make the perfect homemade pasta',
    author: 'Andrew Chilton',
    isDraft: true
};

var blogPostKey = dataset.key('BlogPost');
var transaction;

dataset.runInTransaction((transaction_, done) => {
    transaction = transaction_;

    transaction.save({
        key: blogPostKey,
        data: blogPostData
    });
}, function (err) {
    if (err) {
        console.log("xact insert err", err);
        return transaction.rollback((err, apiResponse) => {
            console.log("in xact rollback callback 1", { err, apiResponse });
        });
    }
});

Related:

http://stackoverflow.com/a/34321469/776934
https://github.com/GoogleCloudPlatform/gcloud-node/issues/633

@callmehiphop -- can you see if you know what's up with the docs duplication?

@stephenplusplus Thanks for the help, I see the proper docs now.
some time in the future, is there going to be a callback for transaction.save?  For method=insert purposes.   I suppose I can emulate this with a transaction.get() call ?

No problem, thanks for helping us catch the issue.

some time in the future, is there going to be a callback for transaction.save?

Would you mind showing an example of what you're looking to do?

I wrote an orm layer for datastore (well, writing I suppose) so it's hard to show the code for what i'm trying to do, the general idea is to ensure inserts into multiple Kinds all succeed, otherwise potentially take alternate actions at various steps (like retry with another key)
Here's my actual scenario:  new user registers for website:
1 .insert a new entity to the "Quota" Kind using "a-long-apiKey-string" as it's name Key.
2. insert a new entity to the "Users" Kind, using<EMAIL_ADDRESS>as it's name Key.
I was originally figuring I could get a callback on the insert, so I could retry with a different apiKey.  Not that big of a deal I suppose, I can just rollback the entire transaction.
ps:  thanks for linking to #633, i will have to figure out how to handle that in my orm too... though now I have some questions on how exactly done() and rollback() work...   I'll play with it a bit (I'm new to NoSql)

I just realized a real need for the transaction.save() callback:  atomic modifications    How else can we atomically increment/decrement numeric information?
here is a proof of concept, showing that the callback is required.

    var accountKey = dataset.key(["Account", "joe"]);
    dataset.insert({
        key: accountKey,
        data: {
            balance: 100,
        }
    }, (err, apiResponse) => {

        if (err != null) {
            console.log("error inserting account", err);
            return;
        }
        dataset.runInTransaction((transaction, done) => {
            transaction.get(accountKey, (err, entity) => {
                var balance = entity.data["balance"];

                balance -= 1;

                transaction.update({
                    key: accountKey,
                    data: {
                        balance: balance,
                    }
                }, (err, apiResponse) => {
                    if (err != null) {
                        console.log("error subtracting balance", err);
                        return transaction.rollback((err, apiResponse) => { if (err != null) { console.log("error rollback after decrement error", err); } });
                    } else {
                        transaction.get(accountKey, (err, entity) => {
                            if (err != null) {
                                console.log("error getting newBalance", err);
                                return transaction.rollback((err, apiResponse) => { if (err != null) { console.log("error rollback after getting newBalance", err); } });
                            }
                            var newBalance = entity.data["balance"];
                            if (newBalance !== balance - 1) {
                                console.log("unable to atomically decrement.  rollback to try again");
                                return transaction.rollback((err, apiResponse) => { if (err != null) { console.log("error rollback after unable to atomically decrement", err); } });
                            } else {
                                console.log("atomic decrement successful");
                                return done();
                            }
                        });
                    }
                });
            });
        }, (err, apiResponse) => {
            if (err != null) {
                console.log("error committing transaction", err);
                return;
            } else {
                console.log("transaction committed", apiResponse);
                return;
            }
        });
    });

I think I'm going to ask the resident expert on Datastore advise the right way to handle the use case you described. Paging @pcostell!

Thank you @stephenplusplus , I am hoping that between the first transaction.get() and the transaction.update() the entity is locked, but I will test that theory out tonight.

No problem, I think you discovered a place where our code is busted...
Our Transaction object inherits from a base class, DatastoreRequest. That class defines all of the methods that are shared between a Dataset and Transaction object: get, delete, save, etc. Because Transactions wait until done() is called to commit the transaction, Transaction#save is overridden to not actually run the save operation; instead, it just queues the changes you want to make in an array until you call done().
I think the slip we made was not overriding the other methods: insert, update, and upsert. Those should behave the save as transaction.save:
transaction.save({ key: postKey, data: postData }); // no callback
transaction.upsert({ key: postKey, data: postData }); // **should** have no callback!

:bug:

Think I'm wrong about our implementation not handling the use case above... turns out, it does handle it! So no more bug, sorry for the confusion.
To sum it all up in case I lost us both; A transaction is just a bunch of requests made all in one request. If a single one fails, the whole transaction fails.
Your example above probably just needs to be refactored with this understanding in mind.

could you please post an example on how to atomically increment a numeric?  (I'm still a bit confused on how done() works)

I think your example simply becomes:
var accountKey = dataset.key(["Account", "joe"]);
dataset.insert({
    key: accountKey,
    data: {
        balance: 100,
    }
}, (err, apiResponse) => {

    if (err != null) {
        console.log("error inserting account", err);
        return;
    }
    dataset.runInTransaction((transaction, done) => {
        transaction.get(accountKey, (err, entity) => {
            var balance = entity.data["balance"];

            balance -= 1;

            transaction.update({
                key: accountKey,
                data: {
                    balance: balance,
                }
            });

            done();

        });
    , (err, apiResponse) => {
        if (err != null) {
            console.log("error committing transaction", err);
            return;
        } else {
            console.log("transaction committed", apiResponse);
            return;
        }
    });
});

The atomic guarantee is that everything you ask of a transaction is changed as you requested, otherwise, nothing is changed.
I think the confusion is it seems like transactions are:

Open
Make changes to entities (delete, insert, save, etc)
Close

When in fact it's just:

Open
Make changes to entities (delete, insert, save, etc)

The "close" (done()) occurs when the changes are made to the entities.

ok thank you, I will test that out tonight!

fyi I tested atomic increment and it works fine:  20 simultanious processes incrementing 100 times each.   Took 8min, but i already read in the docs it'd be slow.
here's my test code if anyone needs it:
var accountKey = dataset.key(["Account", "joe"]);
    //dataset.insert({
    //    key: accountKey,
    //    data: {
    //        balance: 100,
    //    }
    //}, (err, apiResponse) => {

    //if (err != null) {
    //    console.log("error inserting account", err);
    //    return;
    //}

    let testStart = __.moment();
    function atomicTest(iterationsLeft: number) {
        if (iterationsLeft === 0) {
            console.log("*********** DONE! ***********");
            let testEnd = __.moment();
            console.log("duration = " + __.moment.duration(testEnd.diff(testStart)).toISOString());
            return;
        } else {
            console.log("iterationsLeft="+iterationsLeft);
        }
        dataset.runInTransaction((transaction, done) => {
            transaction.get(accountKey, (err, entity) => {
                var balance = entity.data["balance"];

                balance += 1;

                transaction.update({
                    key: accountKey,
                    data: {
                        balance: balance,
                    }
                });

                return done();
            });
        }, (err, apiResponse) => {
            if (err != null) {
                //console.log("\terror committing transaction", err);
                atomicTest(iterationsLeft);
                return;
            } else {
                //console.log("\ttransaction committed", apiResponse);
                atomicTest(iterationsLeft-1);
                return;
            }
        });
    }

    atomicTest(100);

So, I guess I'll close this issue, everything's hunky-dory!

by the way,   I am making an orm layer (and this is my first ever orm actually) but it's a bit of a pain how there are 2 different code-paths for calls in a transaction vs calls outside a transaction.   I ended up writing a promise wrapper for Dataset and Transaction that abstracts this out   (transaction.save will return a dummy promise).
so please keep that in mind for the next api rewrite!


Fix marketplace provisioning for asynchronous services

Frontend Deployment type

[X] Cloud Foundry Application (cf push)
[ ] Kubernetes, using a helm chart
[ ] Docker, using docker compose
[ ] Docker, single container deploying all components
[ ] npm run start
[ ] Other (please specify below)

Expected behaviour
I expect to be able to provision services provided by any asynchronous broker (Example: AWS Service Broker) in the Stratos Marketplace
Actual behaviour
Provisioning fails. As I look at the OSBAPI spec, it seems like this might be because Stratos is not passing the correct parameter to the Cloud Controller. (See spec)

Steps to reproduce the behavior

Register any Open Service Broker API service which uses asynchronous operations (See spec) with Cloud Foundry
Login to Stratos and attempt to provision that service
Notice how provisioning fails with a message similar to the one in the screenshot above.

Log output covering before error and any error statements
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT WARN[Fri Sep 28 23:33:14 UTC 2018] Passthrough response: URL: https://api.[REDACTED]/v2/service_instances, Status Code: 400, Status: 400 Bad Request, Content Type: application/json;charset=utf-8, Length: 323
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT WARN[Fri Sep 28 23:33:14 UTC 2018] {
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT   "description": "This service plan requires client support for asynchronous service operations.",
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT   "error_code": "CF-AsyncRequired",
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT   "code": 10001,
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT   "http": {
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT     "uri": "https://[REDACTED]/v2/service_instances/b2c5919b-3f24-4443-b72e-be71c9d74217",
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT     "method": "PUT",
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT     "status": 422
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT   }
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT }
   2018-09-28T17:33:14.80-0600 [APP/PROC/WEB/0] OUT Request: [2018-09-28T23:33:14Z] Remote-IP:"<IP_ADDRESS>, <IP_ADDRESS>" Method:"POST" Path:"/pp/v1/proxy/v2/service_instances" Status:200 Latency:1.425451536s Bytes-In:185 Bytes-Out:389

FYI, I've confirmed that this error is due to the missing "accepts_incomplete=true" parameter on the request.
cf curl without accepts_incomplete=true fails
▶ cf curl /v2/service_instances -d '{"name":"my-async-svc","space_guid":"5a2029d2-61d1-4cbe-bec0-b7e870394c9c","service_plan_guid":"c93197f5-65be-4dfc-b2bf-c074421ea0e8"}'
{
   "description": "This service plan requires client support for asynchronous service operations.",
   "error_code": "CF-AsyncRequired",
   "code": 10001,
   "http": {
      "uri": "https://[REDACTED]/v2/service_instances/e133897a-dec8-437e-b703-ee6e41450e4f",
      "method": "PUT",
      "status": 422
   }
}

cf curl with accepts_incomplete=true succeeds!
~
▶ cf curl /v2/service_instances?accepts_incomplete=true -d '{"name":"my-async-svc","space_guid":"5a2029d2-61d1-4cbe-bec0-b7e870394c9c","service_plan_guid":"c93197f5-65be-4dfc-b2bf-c074421ea0e8"}'
{
   "metadata": {
      "guid": "0e14d1a3-63fc-4f6d-a68a-e71844057e56",
      "url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56",
      "created_at": "2018-10-01T16:13:25Z",
      "updated_at": "2018-10-01T16:13:25Z"
   },
   "entity": {
      "name": "my-async-svc",
      "credentials": {},
      "service_plan_guid": "c93197f5-65be-4dfc-b2bf-c074421ea0e8",
      "space_guid": "5a2029d2-61d1-4cbe-bec0-b7e870394c9c",
      "gateway_data": null,
      "dashboard_url": null,
      "type": "managed_service_instance",
      "last_operation": {
         "type": "create",
         "state": "in progress",
         "description": "",
         "updated_at": "2018-10-01T16:13:25Z",
         "created_at": "2018-10-01T16:13:25Z"
      },
      "tags": [],
      "service_guid": "66b6b0f8-35e8-48f1-9b51-e6cfd0334037",
      "space_url": "/v2/spaces/5a2029d2-61d1-4cbe-bec0-b7e870394c9c",
      "service_plan_url": "/v2/service_plans/c93197f5-65be-4dfc-b2bf-c074421ea0e8",
      "service_bindings_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/service_bindings",
      "service_keys_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/service_keys",
      "routes_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/routes",
      "service_url": "/v2/services/66b6b0f8-35e8-48f1-9b51-e6cfd0334037",
      "shared_from_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/shared_from",
      "shared_to_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/shared_to",
      "service_instance_parameters_url": "/v2/service_instances/0e14d1a3-63fc-4f6d-a68a-e71844057e56/parameters"
   }
}


eliminate_duplicates seems not work for integers?

I'm solving an optimization problem with n_var=5, where all variable should be unrepeatable integers in range between x_min and x_max, however when I set eliminate_duplicates = True, did't work fine?
Here is my snapshot of code:
algorithm = NSGA2(         pop_size=6,          sampling=IntegerRandomSampling(),         crossover=SBX(repair=RoundingRepair()),         mutation=PM(repair=RoundingRepair()),         eliminate_duplicates=True )
And the Results give out as:
Best solution found: [[ 4  2  9  4 30]  [13 36 23  5  6]  [13 35 22  5  6]  [ 4 36 22 14 36]
which obviously variable did't meet the requirement of unrepeatable.
It will appreciate if any advice is give.

It seems that I misunderstood the eliminate_duplicates, maybe I should apply the unrepeatable by adding constains

Yes, the eliminate_duplicates operators on a population level. Not individual level.
Adding a constraint with a Repair operator is the best fix for what you want to achieve!


Dokku 0.3.26 compliance

Some updates to be compliant with latest dokku :)

Thanks!

You’re welcome :)


example_input_array dtype

Currently assumed that example_input_array dtype to be equal to model dtype. This is not necessarily correct - e.g. if input is a vector of INT.
https://github.com/PyTorchLightning/pytorch-lightning/blob/7dc58bd286b1e81ca4d293f05bddff5e93361020/pytorch_lightning/core/memory.py#L192

Hi, I don't understand. Does it throw an error or does it display nothing?
I don't think we can very accurately define the "input shape" for anything other than tensors.
For this reason we exclude things like dicts from the overview, because it is not very practical to visualize this in a table.

Hi, currently the model is run with input_ as an input. If the model expects a tensor of INTs then it will crash if floats come. I encountered this issue when pretraining an ALBERT-like model. This receives word embeddings as inputs, which have to be integers as they're going into a nn.Embedding

okay I see, so we should not change the dtype as given by example_input_array.
I can't recall why I added this conversion, maybe  it was because of amp and the half conversions. I'll have a closer look, thanks for bringing it up.

as a workaround until it is fixed, cast your input to int before feeding to the embedding layer, or don't use the example_input_array.


Jit some expensive functions

This jits some expensive to compute but fixed functions, we observe speedups of almost 2x in fixedwing and about 1.3x in quadx for now.

Results!
This is the test script, it just spawns 64 drones (either a quadx or a fixedwing), and simulates them for 2000 environment timesteps (4000 physics steps), then records the time for both executions.
import time

import numpy as np

from PyFlyt.core import Aviary

def get_starting_pos():
    x_range = np.linspace(-5.0, 5.0, 4)
    y_range = np.linspace(-5.0, 5.0, 4)
    z_range = np.linspace(1.0, 3.0, 2)

    xx, yy, zz = np.meshgrid(x_range, y_range, z_range)

    xx = xx.flatten()
    yy = yy.flatten()
    zz = zz.flatten()

    return np.stack([xx, yy, zz], axis=-1)

def speed_test_quadx():
    # the starting position and orientations
    start_pos = get_starting_pos()
    start_orn = np.zeros_like(start_pos)

    # environment setup
    env = Aviary(
        start_pos=start_pos,
        start_orn=start_orn,
        render=False,
        drone_type="quadx",
    )

    # set to position control
    env.set_mode(7)

    start = time.time()
    for i in range(2000):
        env.step()
    env.disconnect()
    end = time.time()

    return end - start

def speed_test_fixedwing():
    # the starting position and orientations
    start_pos = get_starting_pos()
    start_orn = np.zeros_like(start_pos)

    # environment setup
    env = Aviary(
        start_pos=start_pos,
        start_orn=start_orn,
        render=False,
        drone_type="fixedwing",
    )

    # set to position control
    env.set_mode(0)

    start = time.time()
    for i in range(2000):
        env.step()
    env.disconnect()
    end = time.time()

    return end - start

if __name__ == "__main__":
    print(speed_test_quadx())
    print(speed_test_fixedwing())

Without jitting:
16.968219995498657
26.871124744415283

With jitting:
16.968219995498657
26.871124744415283

Turns out, we can't really go much faster with the quadx, the main bottleneck seems to be the cascaded PID scheme which is built using jitted individual PID modules.
We obtain a significant speedup on the fixedwing, however, because the expensive aero computation is now compiled and so runs much faster.


over 98% packet loss when large network traffic

Is it because of cgo's performance? the speed can not catch up with libpcap, its' buffer is full, then throw the packets away?

hi @imroc
libpcap has its pitfalls with large network traffic. It's not really related to cgo based on my understanding but on lowel level packet manipulation.
Did you tried other sockets like AF_PACKET or PF_RING which are also supported by gopacket ?
By the way, @gconnell has also published a stack for high performance packet capture : https://github.com/gconnell/stenographer
Cheers
Laurent

hi @lhausermann , thanks for answing me. I tried PF_RING, it got almost the same result. In my mind, cgo calling's performance is a issue, in large network traffic, the calling frequency should be very very high, I strongly believe that cgo will cause packets loss in some degree. I thought using c directly will be better in large network traffic

Hey, @imroc,
A quick note:  AF_PACKET doesn't do cgo calls for every packet (in fact, I believe it only does cgo calls during setup), so it should get around any cgo-related performance issues you're facing.

@gconnell  thank you, I'll try it later 😊


[Focus/Shortcuts] TextField allows key presses to be handled by shortcuts before text input engine

Steps to Reproduce (macOS)

Execute flutter run -d macos on the code sample
Trigger/focus the search TextField by clicking on it, or with any of the keyboard shortcuts: [⌘F] [/] [S]
Type text "text to search"

Expected results:
Text "text to search" should be entered/displayed in the search TextField
Actual results:
Text "text to earch" is displayed in the search TextField
Additional thoughts
I can understand why this might happen. A keyboard shortcut is registered for the key [S]. And I understand that there is difference in the keyboard shortcut system of handling key events and the text input engine. And I also understand that it might be considered rare or an edge case to have a single character/letter as the activator for a shortcut.
However the thing which I find most counter intuitive in the precedence in which the 2 different keyboard input handling methods are invoked here.
Let's break it down a little more...
We have a FocusableActionDetector defined at the page level, which handles the keyboard shortcut [S] to trigger/focus the search TextField.
The page has a child TextField widget which should do all the normal things a TextField should... namely accept text typed into the user's keyboard.
And if we are to follow the ideology that I rightly or wrongly have in my head (can't point to specific point in docs for this) - that when keys are pressed by the user, the childmost widget in the focus path, which can handle that specific key/combination, does handle that keyboard input.
So then if we were to apply that thinking to this code sample, when the TextField has focus, and the user hits the [S] key, I would expect the TextField / text input engine to handle that by putting a letter S into the TextField, and not trigger the keyboard shortcut defined at the page level.
Workarounds
I know I would be able to work around this by wrapping my TextFields with the following:
return Shortcuts(
  shortcuts: const <ShortcutActivator, Intent>{
    SingleActivator(LogicalKeyboardKey.keyS):
        DoNothingAndStopPropagationTextIntent(),
  },
  child: TextField(
    // ...
  ),
);

But feel like this is a bit hacky, and frankly that I shouldn't have to do that!

Code sample
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material $TextField Shortcuts Issue',
      theme: ThemeData(
        primarySwatch: Colors.deepPurple,
      ),
      home: MyHomePage(
        title: 'Material $TextField Shortcuts Issue',
      ),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);
  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  late final FocusNode _pageFocusNode;
  late final FocusNode _searchFocusNode;

  @override
  void initState() {
    super.initState();
    _pageFocusNode = FocusNode(
      debugLabel: '$MyHomePage·Page',
      skipTraversal: true,
    )..requestFocus();
    _searchFocusNode = FocusNode(
      debugLabel: '$MyHomePage·Search',
      skipTraversal: false,
    );
  }

  @override
  void dispose() {
    _pageFocusNode.dispose();
    _searchFocusNode.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return FocusableActionDetector(
      focusNode: _pageFocusNode,
      shortcuts: const <ShortcutActivator, Intent>{
        SingleActivator(LogicalKeyboardKey.keyF, meta: true): SearchIntent(),
        CharacterActivator('/'): SearchIntent(),
        SingleActivator(LogicalKeyboardKey.keyS): SearchIntent(),
      },
      actions: <Type, Action<Intent>>{
        SearchIntent: CallbackAction<SearchIntent>(
          onInvoke: (_) => _searchFocusNode.requestFocus(),
        ),
        DismissIntent: CallbackAction<DismissIntent>(
          onInvoke: (_) => _pageFocusNode.requestFocus(),
        ),
      },
      child: Scaffold(
        appBar: AppBar(
          title: Text(widget.title),
        ),
        body: ListView.builder(
          itemCount: 16,
          itemBuilder: (context, index) {
            if (index == 0) {
              return SearchInputField(
                focusNode: _searchFocusNode,
              );
            }

            return ListTile(
              title: Text('Item: $index'),
            );
          },
        ),
      ),
    );
  }
}

class SearchInputField extends StatelessWidget {
  const SearchInputField({Key? key, required this.focusNode}) : super(key: key);
  final FocusNode focusNode;

  @override
  Widget build(BuildContext context) {
    return Padding(
      padding: const EdgeInsets.all(8),
      child: DecoratedBox(
        decoration: BoxDecoration(
          color: Theme.of(context).colorScheme.background.withOpacity(0.3),
          borderRadius: BorderRadius.circular(8),
        ),
        child: Padding(
          padding: const EdgeInsets.all(8),
          child: TextField(
            focusNode: focusNode,
            decoration: const InputDecoration(
              hintText: 'Focus search field: [ ⌘F ] [ / ] [ S ]',
            ),
          ),
        ),
      ),
    );
  }
}

class SearchIntent extends Intent {
  const SearchIntent();
}

Logs (analyze)
➜  flutter analyze
Analyzing material_text_field_shortcuts_issue...
No issues found! (ran in 2.1s)

Logs (doctor)
➜  flutter doctor -v
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.4 21F79 darwin-x64, locale en-GB)
    • Flutter version 3.0.1 at /Users/cillian/git/flutter/google/flutter
    • Upstream repository git@github.com:/flutter/flutter.git
    • Framework revision fb57da5f94 (6 weeks ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/cillian/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/cillian/Library/Android/sdk
    • Java binary at: /Users/cillian/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8512546/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Android Studio (version 2021.2)
    • Android Studio at /Users/cillian/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8512546/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5591.58

[✓] VS Code (version 1.59.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.25.0

[✓] Connected device (1 available)
    • macOS (desktop) • macos • darwin-x64 • macOS 12.4 21F79 darwin-x64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Demo:

@huycozy anything I can do to help make it easier to give opinion/investigation, please let me know!

Thank you for your detailed writeup.
I think your "workaround" is the intended solution. What you want is actually:

If I'm focusing on anywhere of the app (or not focusing at all), s should be considered a shortcut.
Except if I'm focusing on the text field, then s should not be considered a shortcut. It should be a text input.

It's opening a "hole" in the shortcut definition, which is exactly what your "workaround" is.
The core reason is indeed as you pointed out, key events are processed before the text input. Only events unhandled by any key handlers will be sent to the text input system. This is by design, and followed across all platforms.
As far as I understand (which might be wrong), this design choice is mostly made due to how most (if not all) native platforms design their event flow, where the text systems come after the normal event processing, and "absorb" the events so that there is no way to get the event "back" once you sent them to the text system. The text system have to be the last stop of the event processing system.

So then if we were to apply that thinking to this code sample, when the TextField has focus, and the user hits the [S] key, I would expect the TextField / text input engine to handle that by putting a letter S into the TextField, and not trigger the keyboard shortcut defined at the page level.

Thank you for the explanation!
To be honest, even though I have never build a input text processing system which handles shortcuts and IME, I still find it a bit unintuitive that a text field which has focus would let a raw character be processed by the keyboard shortcut system before IME, but at least now I know that this is a conscious decision and the desired behaviour in this case.


blanket try-catch to ensure following unpatch code

Following from feedback on https://github.com/Azure/azure-cli/pull/6381
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

View a preview at https://prompt.ws/r/Azure/azure-cli/6385
This is an experimental preview for @microsoft users.

@troydai addressed your comments

Merge once CI passes.

Codecov Report

Merging #6385 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##           dev   #6385   +/-   ##
===================================
  Coverage    0%      0%
===================================
  Files       11      11
  Lines      133     133
  Branches     8       9    +1
===================================
  Misses     133     133

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 301ddd7...cb85b4f. Read the comment docs.


Make the app look more canonical

Just looked into your code, and found that it is weird, in term of organization and usage style. Some thought:

In development, people have to "install" the project code itself, with pip install -e .. I agree that we have to install the dependencies, but install the app itself is unnecessary and weird, given that we are standing right in the code base folder.
Suggestion:

Just tell people to do pip install -r requirements.txt to install dependencies, or better, use Poetry to organize dependencies.

The project has some CLI tools. That is good, but the way people have to cd phonlp/models in order to use the CLI tools is silly.
Suggestion:

Organize the project so that, people just stay at the top folder and run:

python3 -m phonlp.tools train ...

With this organization, you also solve the 1st issue (no need to pip install -e .).

You are modifying import path:
https://github.com/VinAIResearch/PhoNLP/blob/efda60735a0b596c7df948fb49eeb8f835cd3734/phonlp/models/run_phonlp.py#L6-L9
With a proper organization, you don't have to do this. It is ugly when having normal code before import statements.

Code doesn't follow standard Python coding style (PEP-8).

Hard-code absolute folder path.
https://github.com/VinAIResearch/PhoNLP/blob/efda60735a0b596c7df948fb49eeb8f835cd3734/phonlp/models/run_phonlp.py#L28-L29
It won't run on other people machine, because "/home/ubuntu/linhnt140/" doesn't exist there.
Suggestion:

Use ~/ or ~/Documents, it always points to user's home folder, no matter what his/her username is.

Command options don't follow common style. Look at this usage:
python3 run_phonlp.py --mode train --save_dir ./phonlp_tmp --pretrained_lm "vinai/phobert-base"

The popular style for CLI on Linux is GNU style, by which, the above command should be:
python3 run_phonlp.py --mode train --save-dir ./phonlp_tmp --pretrained-lm "vinai/phobert-base"

Or, combined with suggestion at 2nd issue, it should be:
python3 -m phonlp.tools train --save-dir ./phonlp_tmp --pretrained-lm "vinai/phobert-base"

Thanks for your comment's great details.
We will take into account your comment in the future development of the toolkit!


Add Travis CI and Poetry

Are the file deletions intentional?

Are the file deletions intentional?

Yes, I deleted setup.py because it is no longer needed with poetry, and deleted one of the licenses because I accidentally added duplicate licenses with different filenames.

One issue with poetry that I don't love: https://github.com/python-poetry/poetry/issues/2073
since we are importing and using __version__ in model_metadata_v3

I think I'm missing a step here — I'm not sure how __version__ relates to that issue.

I think I'm missing a step here — I'm not sure how __version__ relates to that issue.

Sorry, should have elaborated. The package version is specified once in pyproject.toml, but the package itself uses the variable __version__ to include in the model metadata what version of the library serialized the model. If we want to bump the package version, we need to update it in two places, or use one of the alternate suggestions on the github issue linked above.

I'm still confused. That Github issue seems to talk about an issue where package extras are not persisted by poetry across lockfiles. Here we're talking about defining our own package's version in only a single place. I'm sorry =/ I still don't see the connection between extras on dependencies of our package, and our own package's version.

Oops I linked the wrong issue! https://github.com/python-poetry/poetry/issues/144

@obi1kenobi @mikeyshulman finally got builds to pass! Right now it is using black, isort, flake8, and pydocstyle for linting, and we can potentially add pylint, mypy, and bandit later on. I also have it running tests for python 3.6 and 3.7 (TF doesn't yet support 3.8 it looks like).


View [builder_root] not found

Tried in linux. When i call the front-end-builder url, I get the error message
"View [builder_root] not found"
I think, the directory "Views" in resources path should be lower case. I temporary fixed this on my local installation to lower case, and its working now.

Hello, @thomaswacker,
It's working fine from my side I require the package on new project and it work fine, please share the code for the issue.
Thanks

@allamo123  yes i also faced same issue in linux because in linux folder name are case sensitive and in windows / mac it is not case sensitive . when we publish LaravelGrapesServiceProvider Views folder will not be published in linux due to this line
$this->loadViewsFrom(__DIR__.'/../resources/views', 'lg');
views lower case but in package folder name is Views as shared in screenshot. you should fix it or i can even submit pr

@allamo123 sir its not updated yet geting same error please update: the folder name capital Views to views into vendor/msa/laravel-grapes/resources/

@Gagandeep188  try deleting vendor folder and run composer install it will update vendor code


Re: 'Publishing' instructions, can we publish to a company's private GitHub? Securely?

Thank you in advance for your help.  My question is put in the subject line of this issue.
Regards,

GitHub Enterprise, or a private repo on GitHub.com?

Actually i am curious about both. Thank you for the fast reply!
On Mon, Aug 21, 2017 at 9:04 PM Robert Lord<EMAIL_ADDRESS>wrote:

GitHub Enterprise, or a private repo on GitHub.com?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lord/slate/issues/859#issuecomment-323913345, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHeLwsRuG3675122eeLBJwEDMtuQOxivks5salNRgaJpZM4O9_kw
.

--
Sent from Gmail Mobile

Private repos can be published to the same way, but all GitHub pages are public, so it'd be public. GitHub Enterprise should also allow publishing in the same way, and would presumably be protected behind the corp firewall, but you'll have to copy the repo to your instance since you can't just fork it.


impossible to share my solution in github as gist. the browser return "about blank"

Challenge Bonfire: Everything Be True has an issue.
User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:42.0) Gecko/20100101 Firefox/42.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function every(collection, pre) {
  var paquet = [];
  console.log(paquet);
  for(var i = 0; i < collection.length; i ++) {
    var Gc = collection[i];
    for(var key in Gc) {
        console.log(Gc[key], " ", key);

      if ((Gc.key === pre || key === pre) && Gc[pre] ) {
        paquet.push(true);
        console.log(paquet);
      }
    }
  }
  console.log(collection.length, '&', paquet.length);
  if (collection.length === paquet.length) {
    return true;
  }
  else {return false;}
  // Is everyone being true?

}

every([{"user": "Tinky-Winky", "sex": "male", "age": 0},
{"user": "Dipsy", "sex": "male", "age": 3},
{"user": "Laa-Laa", "sex": "female", "age": 5},
{"user": "Po", "sex": "female", "age": 4}], "age");

the url of the exercise: http://www.freecodecamp.com/challenges/bonfire-everything-be-true#?solution=function every(collection%2C pre) {
  var paquet %3D []%3B
  console.log(paquet)%3B
  for(var i %3D 0%3B i < collection.length%3B i %2B%2B) {
    var Gc %3D collection[i]%3B
    for(var key in Gc) {
        console.log(Gc[key]%2C " "%2C key)%3B

      if ((Gc.key %3D%3D%3D pre || key %3D%3D%3D pre) %26%26 Gc[pre] ) {
        paquet.push(true)%3B
        console.log(paquet)%3B
      }
    }%0A%20%20}%0A%20%20console.log%28collection.length%2C%20%27%26%27%2C%20paquet.length%29%3B%0A%20%20if%20%28collection.length%20%3D%3D%3D%20paquet.length%29%20{%0A%20%20%20%20return%20true%3B%0A%20%20}%0A%20%20else%20{return%20false%3B}%0A%20%20%2F%2F%20Is%20everyone%20being%20true%3F%0A%20%0A}%0A%0Aevery%28[{%22user%22%3A%20%22Tinky-Winky%22%2C%20%22sex%22%3A%20%22male%22%2C%20%22age%22%3A%200}%2C%20%0A{%22user%22%3A%20%22Dipsy%22%2C%20%22sex%22%3A%20%22male%22%2C%20%22age%22%3A%203}%2C%20%0A{%22user%22%3A%20%22Laa-Laa%22%2C%20%22sex%22%3A%20%22female%22%2C%20%22age%22%3A%205}%2C%20%0A{%22user%22%3A%20%22Po%22%2C%20%22sex%22%3A%20%22female%22%2C%20%22age%22%3A%204}]%2C%20%22age%22%29%3B
the url after the click about:blank

Currently sharing solutions as gists isn't working anywhere, looking into it, seems another refactor related issue.

for me the problem remain the same, exactly th same

@koouty this issue is fixed and, hopefully, will be in production soon.


Update UI image

Compared with our DG (which has a working table of content), our UG has an extra space behind the {:toc} part, testing if that is the reason why

Ok updated


Fab add does not take generator as an argument

Describe the bug: We're trying to run fab add to add new branches to the service HLD to accomplish rings, but generator is not an accepted argument so it takes the form of component which is default, when we would like to choose helm as the generator.
2019-06-02T01:19:49.6306672Z fab add hello-rings-master --source https://github.com/bnookala/hello-rings --branch master --method git --path chart --generator helm
2019-06-02T01:19:49.6324713Z Error: unknown flag: --generator
2019-06-02T01:19:49.6327923Z Usage:
2019-06-02T01:19:49.6328879Z   fab add <component-name> --source <component-source> [--type component] [--method git] [--path .] [flags]
2019-06-02T01:19:49.6329308Z
2019-06-02T01:19:49.6329514Z Flags:
2019-06-02T01:19:49.6330440Z       --branch string   Branch of git repo to use (default: master) (default "master")
2019-06-02T01:19:49.6330915Z   -h, --help            help for add
2019-06-02T01:19:49.6331420Z       --method string   Method to use to fetch this component (default: git) (default "git")
2019-06-02T01:19:49.6331971Z       --path string     Path of git repo to use (default: ./)
2019-06-02T01:19:49.6332440Z       --source string   Source for this component
2019-06-02T01:19:49.6333681Z       --type string     Type of this component (default: component) (default "component")
2019-06-02T01:19:49.6333998Z
2019-06-02T01:19:49.6334229Z Global Flags:
2019-06-02T01:19:49.6334721Z       --verbose   Use verbose output logs

Just realized type is equivalent to generator :)


Build against libxcrypt on Linux

sshd is currently linked against libcrypt.so.1 which we want to phase
out. For details, see:
https://github.com/conda-forge/linux-sysroot-feedstock/issues/52

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

LGTM!
2023-12-23T16:57:44.1445968Z    INFO (openssh,bin/sshd): Needed DSO lib/libcrypt.so.2 found in conda-forge/linux-64::libxcrypt==4.4.36=hd590300_1

LGTM!
2023-12-23T16:57:44.1445968Z    INFO (openssh,bin/sshd): Needed DSO lib/libcrypt.so.2 found in conda-forge/linux-64::libxcrypt==4.4.36=hd590300_1

Great, thanks for confirming!


Iterating a simple array

Can I pass in a simple array suppose [2,3,4,5,6,10,2]? If yes, what values shall I provide for 'button-label' and 'item-label'? Leaving them empty simply return an error.

Hi @makriss ,
No, you need to pass array of object.


Spring @WebMvcTest stopped working with ShedLock 6.0.1

Since version 6.0.1, Spring @WebMvcTest stopped working with the following error message
No qualifying bean of type 'net.javacrumbs.shedlock.core.LockProvider' available: No LockProvider bean found.

According to documentation, @WebMvcTest only enables auto-configuration that is relevant to MVC tests, which is why our LockProvider Bean cannot be found.
However, it should not be needed in the first place (as it was in 5.x.x), and providing it via @Import(SchedlockConfig.class) is no viable solution because that requires a DataSource bean which is exactly what a @WebMvcTest should not need.
our configuration:
@Configuration
public class SchedlockConfig {

    @Bean
    public LockProvider lockProvider(DataSource dataSource) {
        return new JdbcTemplateLockProvider(
                JdbcTemplateLockProvider.Configuration.builder()
                        .withJdbcTemplate(new JdbcTemplate(dataSource))
                        .usingDbTime()
                        .build()
        );
    }
}

Our application is annotated with @EnableSchedulerLock(interceptMode = PROXY_METHOD)

As a workaround you can move the @EnableSchedulerLock to the SchedlockConfig. Applying it to Application is not necessary.
The behavior indeed changed in 6.0.1. I like the new behavior better - to fail on startup if LockProvider is missing, but I prefer maintianing backward compatiblility more, so I will most likely revert it to the original behavior https://github.com/lukas-krecan/ShedLock/pull/2274.
Thanks again for reporting

Released in 6.0.2


Enhancement - protoc - service definitions - generate gRPC service definitions

I need some clarification on how to proceed with a hello world protobuffer example
There is such a library here
https://github.com/hosopy/grpc-mobile-demo-ios/blob/master/GrpcMobileDemo/HelloWorldViewController.swift
but it's not using the swift-protobuf code base.
I am using this code base - but running into some troubles.
https://github.com/johndpope/swift3-grpc-example
Namely - it appears that the service part of proto file is not generated
https://developers.google.com/protocol-buffers/docs/proto3
syntax = "proto3";

package cali.nlp;

import "syntaxnet/sentence.proto";

message ParseyRequest {
  repeated string text = 1;
};

message ParseyResponse {
  repeated syntaxnet.Sentence result = 1;
};

**service ParseyService** {
  rpc Parse(ParseyRequest) returns (ParseyResponse);
}

According to google's webpages for third party plugins
https://github.com/google/protobuf/blob/master/docs/third_party.md

Are there any plans to support this?

after some digging found this -
https://github.com/grpc/grpc/tree/master/src/objective-c
The --objcgrpc_out plugin generates a pair of .pbrpc.h/.pbrpc.m files for each .proto file with
a service defined.
s.subspec 'Services' do |ss|
ss.source_files = "#{dir}/*.pbrpc.{h,m}"
ss.header_mappings_dir = dir
ss.requires_arc = true
# The generated files depend on the gRPC runtime, and on the files generated by --objc_out.
ss.dependency 'gRPC-ProtoRPC'
ss.dependency "#{s.name}/Messages"
end
we need a --swiftgrpc_out

grpc is a different project that layers on top of protocol buffers.  So similar to https://github.com/google/protobuf/ not directly things with services, something else is free to layer that on top of this project.  Odds are https://github.com/grpc/grpc will provide one once this project is more complete.

Hey John, until we have a native gRPC Swift library, you might want to use ObjC gRPC from Swift. The automatic syntax translation makes it look pretty decent (I personally prefer to use it from Swift rather than directly in ObjC). Here's an example (to try it you just need to run pod install in its directory and that'll generate the protos and configure the dependencies).

Thanks Jorge,
Looking forward to the day gRPC supports swift3 server side
https://github.com/grpc/grpc/issues/8470

Realized I forgot to add one other thing the other day.  grpc spells out one means to send the protos back and forth.  But I've seen other methods used for other projects.  So by keeping it out of the core protobuf project, we provide a common protobuf that can be used with all those different transport specs.

breaking news  - https://github.com/grpc/grpc-swift/issues/2


memcached: 1.5.4 -> 1.5.5

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached -h got 0 exit code
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached --help got 0 exit code
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached -V and found version 1.5.5
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached --version and found version 1.5.5
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached -h and found version 1.5.5
ran /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached --help and found version 1.5.5
found 1.5.5 with grep in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5
found 1.5.5 in filename of file in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5

cc "@coconnor"

Success on x86_64-darwin (full log)
Partial log (click to expand)
 /nix/store/6b3jzg40vibmrjg85i46vvidyy915428-coreutils-8.29/bin/install -c -m 644 protocol_binary.h '/nix/store/jy1l5b8dr5kc9v8az44swkhgqx4024fv-memcached-1.5.5/include/memcached'
make[3]: Leaving directory '/private/tmp/nix-build-memcached-1.5.5.drv-0/memcached-1.5.5'
make[2]: Leaving directory '/private/tmp/nix-build-memcached-1.5.5.drv-0/memcached-1.5.5'
make[1]: Leaving directory '/private/tmp/nix-build-memcached-1.5.5.drv-0/memcached-1.5.5'
post-installation fixup
gzipping man pages under /nix/store/jy1l5b8dr5kc9v8az44swkhgqx4024fv-memcached-1.5.5/share/man/
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/jy1l5b8dr5kc9v8az44swkhgqx4024fv-memcached-1.5.5/bin
patching script interpreter paths in /nix/store/jy1l5b8dr5kc9v8az44swkhgqx4024fv-memcached-1.5.5
/nix/store/jy1l5b8dr5kc9v8az44swkhgqx4024fv-memcached-1.5.5

Success on x86_64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/tmp/nix-build-memcached-1.5.5.drv-0/memcached-1.5.5'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5
shrinking /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin/memcached
gzipping man pages under /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5/bin
patching script interpreter paths in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5
checking for references to /tmp/nix-build-memcached-1.5.5.drv-0 in /nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5...
/nix/store/6b8zx40j50ccjwn2z2s94zsgbzyghzxy-memcached-1.5.5

Success on aarch64-linux (full log)
Partial log (click to expand)
these paths will be fetched (0.07 MiB download, 0.19 MiB unpacked):
  /nix/store/w2micscbnhplv20d7pa087h8n8ndlraq-memcached-1.5.5
copying path '/nix/store/w2micscbnhplv20d7pa087h8n8ndlraq-memcached-1.5.5' from 'https://cache.nixos.org'...
/nix/store/w2micscbnhplv20d7pa087h8n8ndlraq-memcached-1.5.5


service-proxy: implement routing delegate header

r @Raynos @jcorbin
If there's a routing delegate we defer to it as soon as possible.
Should this actually hit the rate limiting logic, at least for total RPS?

Please also handleRequest for eager support.

Weird that tests didnt fail without eager.
I think we default into lazy now and need to update the travis to re-run the entire test suite through eager.
Can you update the travis test config thingy ?

Split travis config fix into https://github.com/uber/hyperbahn/pull/180

Good ship it.

lgtm.


Add community resource for grouping posts by year

My community contribution for grouping posts by year using a custom collection

Thank you!

Thank you!


I found an error in the official document

Document link:https://shardingsphere.apache.org/document/current/en/manual/sharding-jdbc/usage/encrypt/

This word should be column but not comlum.

Can you pull request?

we fixed this error.

fixed it. issue link:  https://github.com/apache/incubator-shardingsphere/issues/3126
document link:  https://shardingsphere.apache.org/document/current/en/manual/sharding-jdbc/usage/encrypt/


Manual dependency installation instructions outputs error.

On Fresh install on Raspberry Pi Zero W with Raspberry Pi OS (Full)
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
## Installing the NodeSource Node.js 10.x repo...

## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js 4 and later.

https://docs.magicmirror.builders/getting-started/installation.html#manual-installation

yes, you need to use my scripted install which configures the system in split mode, server with chromium  over it.
see the installation script here
https://github.com/sdetweil/MagicMirror_scripts

you can use sam's script for this as he already mentioned above. The official version from the docs: pi 0/1 are not supported.

Thanks!


Prompt Structure

Hey Team,
Thank you for your excellent work. I'm having trouble locating information regarding the recommended prompt structure for fine-tuning when using this repository for LLM evaluation. Alternatively, if I've used a format like "### Question: .., ### Answer: ...," how can I specify it for evaluation? I am using the Hugging Face TRL library for fine-tuning.
Regards,
Yash

We already support this on big-refactor! Check out the task guide for details.


[Discuss] revealgo roadmap proposal

Hi @yusukebe!
I did not wish to be intrusive, so I preferred to open a ticket here to discuss an idea. As I told you before in #5, years ago, I drafted a tool similar to yours but with a different goal in mind, and I want to know if you are open to taking it. And please, do not feel pressured by any chance; if you don't like it, feel free to decline it is fine :)
To summarize, I was looking forward to port part of the features you find on webpro/reveal-md, creating a self-contained (no external dependencies) and portable (cross-compiled) binary.
Of course, I would be writting the code for those changes. So, please let me know if you have an appetite for this significant change on the revealgo roadmap, and I can elaborate on specific features I would like to port.
Regards

Hi @jossemarGT ! Thank you for your comment!
I think there are advantages that revealgo is portable and having no external dependencies. So, It's significant to port the parts of such as webpro/reveal-md. I want that other people who did not know revelgo use revealgo. And then, I will write the code, BUT at whim. Therefore, your PRs are very helpful.
I don't have definite roadmap. Though there are rough ideas:

No dependencies: Ex. include reveal.js in this repository, not use git submodules.
Add other options not implemented yet. Ex. live reloading, auto launch.
Make it more potable. Distribute cross-compiled binary.
Promotion.

Some ideas will be on Issues or PRs on this repository.
Then let me know the features which you want implement if you have :)

Thank you for your comment. These are great ideas!
Especially, "publish homebrew" is I was looking for. To make it possible, we should do making binary and automate release process. However I don't know how to make homebrew package. So, I'll check it up👍
Shall we write the code to make it come true? little by little :)

Sure thing, I hope to start woking between this weekend and the next one. My only request would be to create the hacktoberfest-accepted label on this project, so I can use them on my hacktoberfest participation.
PS: The PR's you do for your own projects count as well, so you might be interested joining to hacktoberfest as well. There are cool prices down the line :octocat:

I decided revealgo participate in hacktoberfest. Added hacktoberfetst topic to this project. Thanks!


Update migration mark down with note

Add alternative approaches for C++/CLI

/cc @tgani-msft @jkotas @dotnet/interop-contrib

@AaronRobinsonMSFT @richlander Do we want to set an absolute date for getting this marked as ready for review. Just peeking at this I noticed:

This is almost 2 years old.
The links used in the article are using absolute html links, but they should be relative file links.
Merge conflict.
We'll need to run it through acrolinx for an editing pass.

I'll close this for now. There was some pushback from the C++ side so that needs to be handled offline first.


add logs for preheat e2e test

Add logs to track problems, and find out why the preheat e2e test sometimes goes down.

Codecov Report

Merging #718 (1645a0e) into main (3e3680c) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #718      +/-   ##
==========================================
+ Coverage   38.60%   38.66%   +0.05%
==========================================
  Files          89       89
  Lines        6968     6968
==========================================
+ Hits         2690     2694       +4
+ Misses       3896     3891       -5
- Partials      382      383       +1

Flag
Coverage Δ

unittests
38.66% <ø> (+0.05%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/daemon/peer/peertask_base.go
34.51% <0.00%> (-0.63%)
:arrow_down:

client/daemon/peer/peertask_stream.go
57.92% <0.00%> (+2.26%)
:arrow_up:

Please run go mod tidy.


Swap css-minify with lightningcss

lightningcss  is used by ParcelJS and uses the Servo cssparser libraries.

Thanks for raising this, I've replaced css-minify with lightningcss in version 0.13.0.


Updates Account filtering Algo for Autofill and adds sorting

Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL:  https://app.asana.com/0/1204099484721401/1204529101794549/f
iOS PR:  https://github.com/duckduckgo/iOS/pull/1702
macOS PR: https://github.com/duckduckgo/macos-browser/pull/1122
What kind of version bump will this require?: Minor
Description:

Add custom sorting/filtering extension to [SecureVaultmodels.WebsiteAccount] for suggested domains.
New tests to validate sorting works as expected
Updates the password hashing keychain store to use the kSecClassInternetPassword category

Steps to test this PR:

Sorting and filtering order is covered by unit tests
Smoke test Autofill on macOS and iOS

Internal references:
Software Engineering Expectations
Technical Design Template

@amddg44 I think we're good here now.   I have also updated Autofill to 7.01, which removes the Manage Logins button in macOS Catalina.


npm install failing at frida install

Describe the bug
Failing at the frida install stage
To reproduce  / to understand
After pre-req of Java and nodejs are installed, npm install -g dexcalibur
Expected behavior
It should work
Log
5374 silly install<EMAIL_ADDRESS>5375 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>5376 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
5377 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/lib/node_modules/dexcalibur/node_modules/frida/node_modules/.bin:/usr/lib/node_modules/dexcalibur/node_modules/.bin:/usr/lib/node_modules/.bin:/home/user/Desktop/platform-tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
5378 verbose lifecycle<EMAIL_ADDRESS>CWD: /usr/lib/node_modules/dexcalibur/node_modules/frida
5379 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'prebuild-install || node-gyp rebuild' ]
5380 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
5381 info lifecycle<EMAIL_ADDRESS>Failed to exec install script
5382 timing action:install Completed in 1710ms
5383 verbose unlock done using /home/user/.npm/_locks/staging-a072192f34a17023.lock for /usr/lib/node_modules/.staging
5384 timing stage:rollbackFailedOptional Completed in 686ms
5385 timing stage:runTopLevelLifecycles Completed in 18774ms
5386 verbose stack Error<EMAIL_ADDRESS>install: `prebuild-install || node-gyp rebuild`
5386 verbose stack Exit status 1
5386 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
5386 verbose stack     at EventEmitter.emit (events.js:315:20)
5386 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
5386 verbose stack     at ChildProcess.emit (events.js:315:20)
5386 verbose stack     at maybeClose (internal/child_process.js:1051:16)
5386 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
5387 verbose pkgid<EMAIL_ADDRESS>5388 verbose cwd /home/user/Desktop
5389 verbose Linux 5.4.0-29-generic
5390 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "dexcalibur"
5391 verbose node v14.2.0
5392 verbose npm  v6.14.4
5393 error code ELIFECYCLE
5394 error errno 1
5395 error<EMAIL_ADDRESS>install: `prebuild-install || node-gyp rebuild`
5395 error Exit status 1
5396 error Failed at the<EMAIL_ADDRESS>install script.
5396 error This is probably not a problem with npm. There is likely additional logging output above.
5397 verbose exit [ 1, true ]

Desktop (please complete the following information):

OS: Ubuntu 20.04
Node JS version: 14.2.0
Dexcalibur version (see 'package.json' or output) : 0.7

Hello :)
There is no prebuilt binaries of frida-node for Node 14.2. I highly recommend to use Node 12.x LTS version.
I will fix it into readme. If you work with several Nodejs version on same computer, NVM can help you to install/switch to  different version of nodejs  with a distinct npm local repo for each.

Thanks for your quick response! It's working with 12.x LTS.


Add support for certname parameter

The certname and server name as set to PUPPETSERVER_HOSTNAME in docker-entrypoint.d/50-set-certname.sh. It would be useful if these could be declared separately. An example would be to have multiple puppetservers behind a load balancer. The certname would be the fqdn of each server, and the server parameter would match the load balancer fqdn. Each node would have the load balancer fqdn setup as a dns_alt_name.

I think the $CERTNAME isn't needed here. The server parameter isn't used inside the container. It would be interesting for a normal compiler with an own agent, but in the container there is no agent running. It is installed, but not used for the puppetserver. It is from an older version, when Puppet Inc. itself maintained this repo, but I see no benefit now in keeping this.
so the hostname and dns_alt_names is sufficient for a ha setup. 🤔
it tested this already and have a PR open at crafty https://github.com/voxpupuli/crafty/pull/29
is this the thing you also wanted to do? Is this enough or did i miss something?

it tested this already and have a PR open at crafty https://github.com/voxpupuli/crafty/pull/29

Thanks for sharing that HA example. I am also doing something similar but with k8s using minikube. It's a currently a work in progress, and I was leveraging puppet to do the csr_attributes.yaml + autosign handshake in the container. If you go this route, then you don't have to manage the ssl certs outside of it.

It is installed, but not used for the puppetserver. It is from an older version, when Puppet Inc. itself maintained this repo, but I see no benefit now in keeping this.

I see it being useful as it would minimize the amount of data that needs to be managed and mounted outside the container.

in regards of the certname, is here still something to do? otherwise i would close this issue?

Yes, I think this parameter is useful and would like to use it.

a bit late, but here you go 😅


StyleCop for UnitTest-ColorPickerUI

Summary of the Pull Request
StyleCop for StyleCop for UnitTest-ColorPickerUI
Almost all whitespace changes
PR Checklist

[ ] Applies to #8094
[ ] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

@enricogior, who do you want to review this?


chore: release main

:robot: I have created a release beep boop
kubb: 1.4.2
1.4.2 (2023-06-28)
📦 Miscellaneous Chores

kubb: Synchronize undefined versions

@kubb/core: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/cli: 1.4.2
1.4.2 (2023-06-28)
📦 Miscellaneous Chores

@kubb/cli: Synchronize undefined versions

@kubb/ts-codegen: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-ts: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-client: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-tanstack-query: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-faker: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-zod: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-zodios: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-swr: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

@kubb/swagger-form: 1.4.2
1.4.2 (2023-06-28)
🐞 Bug Fixes

types fix exports based on https://arethetypeswrong.github.io/ (f942def)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/ts-codegen-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-ts-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-client-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-faker-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-zod-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-swr-v1.4.2 :sunflower:

:robot: Release is at https://github.com/kubb-project/kubb/releases/tag/%40kubb/swagger-form-v1.4.2 :sunflower:


Accessibility tests

See https://wave.webaim.org/report#/https://hugoplate.netlify.app/ (I'd suggest you install their extension and test every page of the theme thoroughly in both light and dark modes)

Thank you for you findings @dryscord . We are going to fix this issue soon.

Hi @dryscord
I have fixed the errors. now some alerts are still showing. Since it's a starter template, the alerts will go out when developers will build a site on it.  Let me know what you think.


fix: unify varchar format_type display with PostgreSQL

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Make format type display of RisingWave consistent with PostgreSQL.
The original purpose of this PR is to fix the problem that the varchar type in superset cannot be recognized.
superset uses sqlalchemy as the ORM, and the different format type from PostgreSQL makes the type unrecognizable to sqlalchemy.
The inconsistencies are:
SELECT format_type(1043, '-1');

result of RisingWave: varchar; of PostgreSQL: character varying.
SqlAlchemy test:
CREATE TABLE test (a int, b varchar);

from sqlalchemy import create_engine
from sqlalchemy import inspect

def main():
    # engine = create_engine("postgresql://jinser:pssswd@localhost:5432/playground") # PostgreSQL
    engine = create_engine("postgresql://root@localhost:4566/dev") # RisingWave
    inspector = inspect(engine)

    columns = inspector.get_columns("test", "public")
    for column in columns:
        print(column)

related #9938.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

Hi, should work fine now.


ingress-shim controller: Re-queuing item "default/helloworld" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-prod" not found

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
I got the following error after creating an ingress with the tls-acme annotation set to true.
E0127 11:05:36.980788       1 controller.go:156] ingress-shim controller: Re-queuing item "default/scoutr" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-prod" not found
I0127 11:13:11.600975       1 controller.go:147] ingress-shim controller: syncing item 'default/scoutr-staging'
E0127 11:13:11.601318       1 controller.go:156] ingress-shim controller: Re-queuing item "default/scoutr-staging" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-prod" not found
I0127 11:22:16.981195       1 controller.go:147] ingress-shim controller: syncing item 'default/scoutr'
E0127 11:22:16.981286       1 controller.go:156] ingress-shim controller: Re-queuing item "default/scoutr" due to error processing: clusterissuer.certmanager.k8s.io "letsencrypt-prod" not found

What you expected to happen:
Cert Manager to get a cert from let's encrypt for my ingress
How to reproduce it (as minimally and precisely as possible):
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/force-ssl-redirect: "false"
    kubernetes.io/ingress.global-static-ip-name: scoutr-staging-ip
    kubernetes.io/tls-acme: "true"
  labels:
    app: staging
  name: staging
  namespace: default
spec:
  backend:
    serviceName: staging
    servicePort: 8080
  tls:
  - secretName: cert-secret
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>

Anything else we need to know?:
I installed Cert manager with
helm install \
                                   --name cert-manager \
                                   --namespace kube-system \
                                   contrib/charts/cert-manager \
                                   --set ingressShim.extraArgs='{--default-issuer-name=letsencrypt-prod,--default-issuer-kind=ClusterIssuer}'

Environment:

Kubernetes version (use kubectl version): v1.7.11-gke.1
Cloud provider or hardware configuration**: GKE
Install tools: Gcloud
Others:

I'm going to close this now as we have improved the deployment NOTES.txt to include a note similar to above. Feel free to re-open if you are still experiencing issues!

helm install \
    --name cm \
    --namespace kube-system \
    --set ingressShim.extraArgs='{--default-issuer-name=letsencrypt-prod,--default-issuer-kind=ClusterIssuer}' \
    stable/cert-manager
NAME:   cm
LAST DEPLOYED: Tue Dec  4 22:57:46 2018
NAMESPACE: kube-system
STATUS: DEPLOYED

RESOURCES:
==> v1beta1/Deployment
NAME             AGE
cm-cert-manager  0s

==> v1/Pod(related)

NAME                              READY  STATUS             RESTARTS  AGE
cm-cert-manager-5bdfdb66bc-fvfm4  0/1    ContainerCreating  0         0s

==> v1/ServiceAccount

NAME             AGE
cm-cert-manager  0s

==> v1beta1/ClusterRole
cm-cert-manager  0s

==> v1beta1/ClusterRoleBinding
cm-cert-manager  0s

NOTES:
cert-manager has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.readthedocs.io/en/latest/reference/issuers.html

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.readthedocs.io/en/latest/reference/ingress-shim.html

This succeeds but then I see this in the logs.
I have added kubectl get clusterissuer letsencrypt-prod as well.
 "ingress-shim controller: Re-queuing item "default/hello" due to error processing: issuer.certmanager.k8s.io "" not found"

E  ingress-shim controller: Re-queuing item "default/hello" due to error processing: issuer.certmanager.k8s.io "" not found
I  ingress-shim controller: syncing item 'default/hello'


ecaltime not building in some Unix systems

Describe the bug
The bug is located at contrib/ecaltime/CMakeLists.txt
Please replace if(UNIX AND NOT APPLE) with if(CMAKE_SYSTEM_NAME STREQUAL "Linux")
To Reproduce
Build eCAL in a Unix and non-Linux system.

@hannemn Can you please take a look at this? It looks better to use the built-in CMake system variables.

Hi @pablorcum, I think if(.... AND NOT QNXNTO) looks a bit nicer, but your approach is more safer for further operation systems that should exclude from linuxptp plugin.

Issue will be solved with PR #284


[bug]: Unable to install on Laravel 11.x

Describe the bug
Cannot Install shadcn-ui on Laravel Inertia React while using Javascript .jsx
✔ Preflight checks.
✔ Verifying framework. Found Laravel.
✔ Validating Tailwind CSS.
✖ Validating import alias.
No import alias found in your tsconfig.json file.
Visit https://ui.shadcn.com/docs/installation/laravel to learn how to set an import alias.
Affected component/components
npx shadcn@latest init
How to reproduce
npx shadcn@latest init
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Windows 10 x64

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

You need to add
 "paths": {
      "@/*": ["./*"]
    }

To your tsconfig. So shadcn can use @ for imports.

You need to add
 "paths": {
      "@/*": ["./*"]
    }

To your tsconfig. So shadcn can use @ for imports.

I mean, when the project is first initialized, tsconfig and jsconfig haven't been created yet.

Create tsconfig.json
You need to add
{
"compilerOptions": {
"paths": {
"@/": ["./resources/js/"],
"ziggy-js": ["./vendor/tightenco/ziggy"]
}
}
}

Having this issue aswell, I cant even create a laravel project following shadcn's documentation.
https://ui.shadcn.com/docs/installation/laravel
Tells me I cant use --typescript and when I install it manually I get that issue

same here, the issue still persist, any solution about this?

I found the solution: you need to first create a tsconfig.json file in the project root, and then run the installation command
{
  "compilerOptions": {
    "paths": {
        "@/*": ["./*"]
    }
  }
}

then run the command npx shadcn@latest init

For the latest Laravel version its not working. Please check this issue
https://github.com/shadcn-ui/ui/issues/5743

Thanks @raviMukti. Worked for me


librviz : Creating a MotionPlanning display in Noetic without crashing

Hello,
I've been using librviz successfully for the past two years in my own Qt application for the visualization of a robot doing finishing tasks in ROS Kinetic with Ubuntu 16.04. Here's a code snippet of how I initialized librviz classes and added rviz::Display objects :
    // Construct and lay out render panel.
    rviz_render_panel_ = new rviz::RenderPanel();

    // Next we initialize the main RViz classes.
    rviz_manager_ = new rviz::VisualizationManager(rviz_render_panel_);
    rviz_render_panel_->initialize(rviz_manager_->getSceneManager(), rviz_manager_);
    rviz_manager_->initialize();
    rviz_manager_->startUpdate();

    // Create a display for MotionPlanning
    moveit_display_ = rviz_manager_->createDisplay("moveit_rviz_plugin/MotionPlanning", "MotionPlanning", true);

This used to work very well, but I've recently migrated from Kinetic to Noetic, and now, the last line (createDisplay) crashes without any warning or error for "moveit_rviz_plugin/MotionPlanning". It still works with any other rviz::Display objects, but crashes everytime when using "MotionPlanning". If I use rViz directly, I can easily create a MotionPlanning display and do A to B trajectories. Interestingly enough, it doesn't crash if I disable the display (isEnabled -> false) :
    moveit_display_ = rviz_manager_->createDisplay("moveit_rviz_plugin/MotionPlanning", "MotionPlanning", false);

But it crashes as soon as I enable it : moveit_display__->setEnabled(true)
So, my question is :
Is the MotionPlanning display object deprecated in the Noetic version of librviz (I wouldn't think so since it works in rViz)?
You can easily replicate the error using the librviz tutorial :
https://github.com/ros-visualization/visualization_tutorials/tree/noetic-devel/librviz_tutorial
And adding the following line after manager_->startupdate() :
rviz_manager_->createDisplay("moveit_rviz_plugin/MotionPlanning", "MotionPlanning", true);
It results as a "Segmentation fault (core dumped)" in this case.
Using gdb :
Thread 1 "myviz" received signal SIGSEGV, Segmentation fault.
#0  0x00007ffff7a96932 in QWidget::show() ()
    at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#1  0x00007fff802005cf in moveit_rviz_plugin::MotionPlanningFrame::enable() ()
    at /opt/ros/noetic/lib/libmoveit_motion_planning_rviz_plugin_core.so.1.1.5
#2  0x00007ffff7783315 in rviz::Display::onEnableChanged() ()
    at /opt/ros/noetic/lib/librviz.so
#3  0x00007ffff776eab8 in  () at /opt/ros/noetic/lib/librviz.so
#4  0x00007ffff6c47300 in QMetaObject::activate(QObject*, int, int, void**) ()
    at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ffff78054ab in rviz::Property::setValue(QVariant const&) ()
    at /opt/ros/noetic/lib/librviz.so
#6  0x00007ffff778311b in rviz::Display::setEnabled(bool) ()
    at /opt/ros/noetic/lib/librviz.so
#7  0x00007ffff7862b28 in rviz::VisualizationManager::createDisplay(QString const&, QString const&, bool) () at /opt/ros/noetic/lib/librviz.so
#8  0x000055555556921c in MyViz::MyViz(QWidget*)
...

Using valgrind :
==10405== Invalid read of size 8
==10405==    at 0x4A32932: QWidget::show() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8)
==10405==    by 0x2F5525CE: moveit_rviz_plugin::MotionPlanningFrame::enable() (in /opt/ros/noetic/lib/libmoveit_motion_planning_rviz_plugin_core.so.1.1.5)
==10405==    by 0x502E314: rviz::Display::onEnableChanged() (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x5019AB7: ??? (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x5BE72FF: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8)
==10405==    by 0x50B04AA: rviz::Property::setValue(QVariant const&) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x502E11A: rviz::Display::setEnabled(bool) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x510DB27: rviz::VisualizationManager::createDisplay(QString const&, QString const&, bool) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x11D21B: MyViz::MyViz(QWidget*) (myviz.cpp:62)
==10405==    by 0x123073: main (main.cpp:14)
==10405==  Address 0x28 is not stack'd, malloc'd or (recently) free'd
==10405==
==10405==
==10405== Process terminating with default action of signal 11 (SIGSEGV)
==10405==  Access not within mapped region at address 0x28
==10405==    at 0x4A32932: QWidget::show() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.12.8)
==10405==    by 0x2F5525CE: moveit_rviz_plugin::MotionPlanningFrame::enable() (in /opt/ros/noetic/lib/libmoveit_motion_planning_rviz_plugin_core.so.1.1.5)
==10405==    by 0x502E314: rviz::Display::onEnableChanged() (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x5019AB7: ??? (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x5BE72FF: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8)
==10405==    by 0x50B04AA: rviz::Property::setValue(QVariant const&) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x502E11A: rviz::Display::setEnabled(bool) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x510DB27: rviz::VisualizationManager::createDisplay(QString const&, QString const&, bool) (in /opt/ros/noetic/lib/librviz.so)
==10405==    by 0x11D21B: MyViz::MyViz(QWidget*) (myviz.cpp:62)
==10405==    by 0x123073: main (main.cpp:14)

I've investigated a bit and it seems like the parent QWidget of the MotionPlanningFrame is not initialized correctly (nullptr). Should I ask the question at the moveit repository?
Here's the link to the cpp files :
MotionPlanningFrame
MotionPlanningDisplay
At line 229 of MotionPlanningDisplay, we have the initialization of MotionPlanningFrame :
rviz::WindowManagerInterface* window_context = context_->getWindowManager();
frame_ = new MotionPlanningFrame(this, context_, window_context ? window_context->getParentWindow() : nullptr);

I guess the last argument of the second line is where the parent QWidget is initialized to a nullptr. context_ (rviz::DisplayContext) comes from the base class of MotionPlanningDisplay, that is rviz::Display, so I wouldn't think it is the problem.
Now, I've built Moveit from source and it seems like window_context is a nullptr. Is getWindowManager() deprecated?
Your environment

OS Version: Ubuntu 20.04
ROS Distro: Noetic
RViz, Qt, OGRE, OpenGl version as printed by rviz:
[ INFO] [1628191103.549857876]: rviz version 1.14.8
[ INFO] [1628191103.549899909]: compiled against Qt version 5.12.8
[ INFO] [1628191103.549912271]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1628191103.555191462]: Forcing OpenGl version 0.
[ INFO] [1628191104.598819039]: Stereo is NOT SUPPORTED
[ INFO] [1628191104.598860163]: OpenGL device: Mesa Intel(R) UHD Graphics (CML GT2)
[ INFO] [1628191104.598878252]: OpenGl version: 4.6 (GLSL 4.6) limited to GLSL 1.4 on Mesa system.

Sorry for the late reply. I think the core problem is that you (and the librviz tutorial) don't use a window manager at all:
The VisualizationManager is initialized w/o a second argument. Thus, getWindowManager returns NULL. In order to display the associated widget panel you need to specify a window manager.
Have you ever seen the panel in Kinetic? I'm not yet sure how/why it worked in Kinetic...
I will file a fixup in MoveIt to avoid the segfault, though.

Sorry for not getting back to you sooner, I was away for two weeks. And you're right, I don't use a window manager at all. Still confused with why it worked in Kinetic. Thank you for the fixup! I'll try it tonight and then close the issue.