Issue loading vcf file

Hi Sam,
I'm very curious about trying Gretel on my data but I'm having trouble loading the vcf file (same issue with the test data provided); I've tried various approaches to solve the issue but to no avail. It keeps throwing me the following error:

Traceback (most recent call last):
File "/Users/#####/opt/anaconda3/bin/gretel", line 8, in
sys.exit(main())
File "/Users/#####/opt/anaconda3/lib/python3.8/site-packages/gretel/cmd.py", line 69, in main
VCF_h = util.process_vcf(ARGS.vcf, ARGS.contig, ARGS.start, ARGS.end)
File "/Users/#####/opt/anaconda3/lib/python3.8/site-packages/gretel/util.py", line 389, in process_vcf
vcf_records = vcf.Reader(fp)
File "/Users/#####/opt/anaconda3/lib/python3.8/site-packages/vcf/parser.py", line 300, in init
self._parse_metainfo()
File "/Users/#####/opt/anaconda3/lib/python3.8/site-packages/vcf/parser.py", line 318, in _parse_metainfo
while line.startswith('##'):
TypeError: startswith first arg must be bytes or a tuple of bytes, not str

Hmm, this looks like a problem inside PyVCF and sounds like a Python
str/bytes problem.
Are you compressing the VCF as per the (admittedly not perfect)
instructions?
https://gretel.readthedocs.io/en/latest/protocol.html#variant-calling
On Tue, May 25, 2021 at 1:49 PM MarkNioc @.***> wrote:

Hi Sam,
I'm very curious about trying Gretel on my data but I'm having trouble
loading the vcf file (same issue with the test data provided); I've tried
various approaches to solve the issue but to no avail. It keeps throwing me
the following error:
Traceback (most recent call last):
File "/Users/#####/opt/anaconda3/bin/gretel", line 8, in
sys.exit(main())
File
"/Users/#####/opt/anaconda3/lib/python3.8/site-packages/gretel/cmd.py",
line 69, in main
VCF_h = util.process_vcf(ARGS.vcf, ARGS.contig, ARGS.start, ARGS.end)
File
"/Users/#####/opt/anaconda3/lib/python3.8/site-packages/gretel/util.py",
line 389, in process_vcf
vcf_records = vcf.Reader(fp)
File
"/Users/#####/opt/anaconda3/lib/python3.8/site-packages/vcf/parser.py",
line 300, in init
self._parse_metainfo()
File
"/Users/#####/opt/anaconda3/lib/python3.8/site-packages/vcf/parser.py",
line 318, in _parse_metainfo
while line.startswith('##'):
TypeError: startswith first arg must be bytes or a tuple of bytes, not
str
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SamStudio8/gretel/issues/37, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIN6ORGHT4LO3XNMTMNIG3TPOMFJANCNFSM45PJLROQ
.

Hi Sam, thanks for the prompt reply.
Yes, I've followed the instructions to compress/index the vcf file. I've tried modifying util.py, using other approaches to load the vcf file, but I just bump into other problems. For example I've tried loading the file with vcf_records = vcf.Reader(filename=vcf_path) instead, and it threw me this error: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte (which I understand means the vcf file is still gzipped).
Checked my locale (in case), checked also all dependencies, they're all installed and up to date.

OK. The plot thickens...
I've just installed gretel using pip as per the README. I downloaded a copy of the repo and ran pytest which runs a basic regression test suite (https://github.com/SamStudio8/gretel/blob/master/tests/test_test.py) and I had no problems related to the VCF (or anything else, which is a good start).
Immediately I'm thinking this can't be a pyVCF problem as I've likely installed the latest as the versions are not pinned by the gretel installer. Indeed I've just installed pyVCF 0.6.8, which is the latest on pyPI (https://pypi.org/project/PyVCF/). I see from your example you're on Python 3.8 (I'm on 3.7 still), so I made a conda environment with Python 3.8 and reinstalled everything with pip and cannot repeat this error.
I've tried install gretel with conda instead, and get an UnsatisfiableError error if I use Python 3.7 or 3.8, which doesn't make any sense because I was under the impression the way I'd configured the meta.yml would cover those versions. Dropping the fixed Python version, I was able to install gretel through conda as per the README and run pytest and that seems to work OK too...!
Just in case it was pytest, I navigated to the test dir and ran gretel manually and it seemed to be OK:
(gretel-37) [sam@epona data]$ python --version
Python 3.8.10
(gretel-37) [sam@epona data]$ pwd
/home/sam/git/gretel/tests/data
(gretel-37) [sam@epona data]$ gretel -s 1 -e 19 test.bam test.vcf.gz 'hoot'
[2]
[None]
[NOTE] Loaded 8 breadcrumbs from 4 bread slices.
[NOTE] Setting Gretel.L to 3
i       pos     gap     A       C       G       T       N       -       _       tot
0       0       0       0       0       0       0       0       0       4       4
1       1       1       1       1       0       2       0       0       0       4
2       2       1       1       1       0       0       0       0       0       2
3       10      8       1       1       0       0       0       0       0       2
[NOTE] *Establishing next path
[RWGT] Ratio 0.500, Removed 4.0
[NOTE] *Establishing next path
[RWGT] Ratio 0.500, Removed 2.0
[NOTE] *Establishing next path
[NOTE] Unable to select next branch from SNP 1 to 2
       By design, Gretel will attempt to recover haplotypes until a hole in the graph has been found.
       Recovery will intentionally terminate now.

Can I ask that you try a fresh pip/conda install and check all the versions?

Thanks for taking time to check what might be going wrong.
I've done a fresh installation of Gretel.
gretel                    0.0.94             pyh864c0ab_1    bioconda
hanselx                   0.0.92                   pypi_0    pypi

The error I now get, using your test data (or mine), is
AttributeError: Can't pickle local object 'load_from_bam.<locals>.bam_worker'
which could be an issue linked to Python 3.8 (like here: https://github.com/spack/spack/issues/14102)
Unless of course it is something to do with my python environment being too messy (https://xkcd.com/1987/)...

Eek. Not exactly a fix but if you're using conda you could try fixing
Python to say, 3.7 in a new environment:
conda create -n gretel-py37 python=3.7
That might at least rule out some Py3.8 weirdness...
Sam
On Tue, May 25, 2021 at 9:15 PM GoneAwry @.***> wrote:

Thanks for taking time to check what might be going wrong.
I've done a fresh installation of Gretel.
gretel                    0.0.94             pyh864c0ab_1    bioconda
hanselx                   0.0.92                   pypi_0    pypi
The error I now get, using your test data (or mine), is
AttributeError: Can't pickle local object
'load_from_bam..bam_worker'
which could be an issue linked to Python 3.8 (like here: spack/spack#14102
https://github.com/spack/spack/issues/14102)
Unless of course it is something to do with my python environment being
too messy (https://xkcd.com/1987/)...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SamStudio8/gretel/issues/37#issuecomment-848229190,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIN6OXAFR6PTD2HIZIGETDTPQANVANCNFSM45PJLROQ
.

So, turns out it is indeed an issue with Python 3.8
Running Gretel in a new environment with Python 3.7 works just fine
Thanks for your help and for being so reactive!

Sorry that it's not an actual fix but I'm glad that workaround is working!
Hope Gretel gives you some interesting results :)
On Wed, 26 May 2021, 08:04 GoneAwry, @.***> wrote:

Closed #37 https://github.com/SamStudio8/gretel/issues/37.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SamStudio8/gretel/issues/37#event-4797182106, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIN6OUFCAR7WTPU6QTWNWTTPSMODANCNFSM45PJLROQ
.


About the performance of pretrained model

The pre-trained model you provided is not well-performing over the Celeb-A-HQ dataset. So I've got a question that for how many epochs you have trained the pre-trained model and on what data set.
Another question is that my use case applies glasses to the face, so I need to know that if I trained a new model from scratch over the Celeb-A-HQ dataset it will help us to achieve my task.
can we train the model over a single attribute like eyeglasses or a smile?
Thanks in advance.

In the output folder, you can find settings.yml, there is the setting of the pre-trained model. Actually, this method does not perform well on eyeglasses. If you want a model that is better on a single and local attribute, I suggest SaGAN.

In the output folder, you can find settings.yml, there is the setting of the pre-trained model. Actually, this method does not perform well on eyeglasses. If you want a model that is better on a single and local attribute, I suggest SaGAN.

Thanks for your reply.
As you were suggesting the SaGAN, I'll take a look at it.
By the way, my use case is I'm gonna pass a face image to the GAN model and it should return the same image with eyeglasses.
I'm going through all the issues of this repo ill found that for testing any image we need to pass the label attributes corresponding to the same image as you suggest that i looked into the STGAN repo for attribute classification. I was looking at it but haven't found a way to do it I think the code was hardcoded for a CelebA dataset. Is there any way to do attribute classification for a custom image?

Thanks for your reply.
As you were suggesting the SaGAN, I'll take a look at it.
By the way, my use case is I'm gonna pass a face image to the GAN model and it should return the same image with eyeglasses.
I'm going through all the issues of this repo ill found that for testing any image we need to pass the label attributes corresponding to the same image as you suggest that i looked into the STGAN repo for attribute classification. I was looking at it but haven't found a way to do it I think the code was hardcoded for a CelebA dataset. Is there any way to do attribute classification for a custom image?

I looked at SaGAN(Slf Attention GAN) but not found a way to do my job, because the whole code written about training the dataset. But there is no mention for what purpose it actually used for.

I looked at SaGAN(Slf Attention GAN) but not found a way to do my job, because the whole code written about training the dataset. But there is no mention for what purpose it actually used for.

I mean this paper, Zhang, Gang, et al. "Generative adversarial network with spatial attention for face attribute editing." Proceedings of the European conference on computer vision (ECCV). 2018.
Or you can refer to another solution like https://github.com/genforce/interfacegan

I mean this paper, Zhang, Gang, et al. "Generative adversarial network with spatial attention for face attribute editing." Proceedings of the European conference on computer vision (ECCV). 2018.
Or you can refer to another solution like https://github.com/genforce/interfacegan

hey, I was following the interface gan for my task, it is very good but for sunglasses, they are not well enough. In the interface gan they are using some pre-trained boundaries to do the different types of attribute editing and they are working perfectly. I'm working to train over custom boundaries. So, to train boundaries I need the attribute score, so I exactly don't know what it is.
Can you tell me what it is exactly and how can i get it?


[DO-NOT-MERGE] Drop support for Kubernetes v1.10

What this PR does / why we need it:
Drop support for Kubernetes v1.10.
Ref https://github.com/gardener/gardener/issues/1118#issuecomment-506496883
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

:warning: Gardener does no longer support Kubernetes v1.10. You must upgrade all shoot cluster to at least Kubernetes v1.11 before upgrading Gardener. This also means that no seed clusters with versions prior to v1.11 are supported anymore. Please upgrade all seed clusters to at least v1.11 as well before upgrading Gardener cluster itself to v1.11.

/hold

Thank you for the review! Applied the suggestions.

Closing for now.


Add public contact bundle type

In the long-term the client should be able to query the server for a contact (either via wallet address, or via device identity key), and receive one or more contact bundles (public device identity key, public one time key). This PR adds the contact bundle type. Some simplifications for the prototype:

The contact bundle is served directly from the client rather than the server
The 'one time key' in the bundle is the fallback key, and it never changes

Verified existing tests pass.
I could propagate these changes into js, but I think ultimately we want to fetch these bundles directly from the server.
I think I can prototype publishing and fetching bundles as part of multi-device support next. My thought is that we upload a large bundle of keys (PreKeyTopUpBundle) for ourself (e.g. 1000 one time keys and a fallback key), and we retrieve a small bundle (ContactBundle) for others (device identity key, one time key). The server is responsible for constructing the contact bundle from the prekey topup bundle.

The server is responsible for constructing the contact bundle from the prekey topup bundle.

I'd like to understand what is being proposed here. Any change where the server is returning something other than a byte-perfect representation of what was uploaded comes with complications as we decentralize the network.
Few questions:

Are we expecting the server to maintain some sort of state of which one time keys have already been used?
If not, what logic would be used to select the one time key?
What would be signed in this scheme? How do we verify that the server-constructed bundles were not tampered with?

(either via wallet address, or via device identity key)

Does this mean that two versions are submitted the network? One indexed by Address and one by IdentityKey? Or are Contact Bundles powered by a different service?


Make hadoop-lzo a managed dependency

Then we won't need a snapshot of the .jar file in source control.
This will need to wait until version 0.4.20 of the library is released.

Migrated from https://github.com/snowplow/snowplow/issues/1321

done in #93, closing


Discussion/investigation for OneOf/AnyOf improvements

We want to support oneOf better. Here's an example of a JSON schema using oneOf (for an actual sample from an Azure service, see this JSON schema and this Swagger spec):
Example OneOf JSON schema
{
    "Animal": {
        "type": "object",
        "oneOf": [
            {
                "$ref": "#/definitions/Cat"
            },
            {
                "$ref": "#/definitions/Dog"
            }
        ]
    },
    "Cat": {
        "type": "object",
        "properties": {
            "claws": {
                "type": "integer"
            }
        }
    },
    "Dog": {
        "type": "object",
        "properties": {
            "paws": {
                "type": "integer"
            }
        }
    }
}

Here's how we could render into Kubernetes CRDs with CRD API version apiextensions.k8s.io/v1beta1 (skipping over how to do it in Kubebuilder for a second):
        spec:
          oneOf:
            - type: object
              properties:
                claws:
                  type: integer
              required: ["claws"]
            - type: object
              properties:
                paws:
                  type: integer
              required: ["paws"]```

There is an issue though which is that, starting with Kubernetes CRD API version v1 (which presumably we will want to target), Kubernetes doesn't actually support a full set of OpenAPI, it restricts things to what it calls the structural schema. You can read more about structural schema here.

A structural schema is an OpenAPI v3.0 validation schema which:

specifies a non-empty type (via type in OpenAPI) for the root, for each specified field of an object node (via properties or additionalProperties in OpenAPI) and for each item in an array node (via items in OpenAPI), with the exception of:
a node with x-kubernetes-int-or-string: true
a node with x-kubernetes-preserve-unknown-fields: true
for each field in an object and each item in an array which is specified within any of allOf, anyOf, oneOf or not, the schema also specifies the field/item outside of those logical junctors (compare example 1 and 2).
does not set description, type, default, additionalProperties, nullable within an allOf, anyOf, oneOf or not, with the exception of the two pattern for x-kubernetes-int-or-string: true (see below).

The major issue is item number 2 - this basically means that you can't model oneOf exactly how it's modeled in ARM (or in OpenAPI in general).
Kubernetes has specific guidance with regard to discriminated unions and how they should be represented here, which effectively suggests that you define a single type with a property for each possible DU option and then enforce in the OpenAPI that exactly one property is specified. With my CatDog example above that would look like this in CRD-land:
apiextensions.k8s.io/v1 supported CRD
        spec:
          properties:
            cat:
              type: object
              properties:
                claws:
                  type: integer
            dog:
              type: obect
              properties:
                paws:
                  type: integer
          oneOf:
            - required: ["cat"]
            - required: ["dog"]
          type: object

Some notes:

controller-gen doesn't give control over what the openapi schema of a given type is, we had found https://github.com/kubernetes/kube-openapi/tree/master/pkg/generators#custom-openapi-type-definitions but that only applies to kube-openapi (a different tool than controller-gen as far as I can tell).
There is some good discussion/examples in this GitHub issue about how this would be supported in Kubebuilder - as far as I can tell, there currently is no support for generating CRDs with the Kubernetes suggested DU structure (1 property for each option, must fill exactly 1 property) using controller-gen - @devigned are you aware of this?

Conclusion
This leaves us in a bit of an awkward situation:

We currently generate a Go type with interface{} for each type which is a oneOf - but controller-gen doesn't know what to do with interface{} and will error out on it if it's in one of our model types.
We can't just "do what the schema does" because Go doesn't support DUs directly, and Kubebuilder's generated CRDs don't support that either.
Kubernetes recommends against polymorphic types (including oneOf/anyOf) here - see: "Note: we explicitly accept that polymorphic types (like IntOrString) are an anti-pattern for Kubernetes-like types and we do not want to encourage its use beyond IntOrString."

Proposed solution
Given all of the above, I think we may need to take a path that turns OneOf schemas into Go types that fit the structural schema requirements. This is more inline with what Kubernetes wants CRDs to look like but means that we don't look exactly like the ARM API.
For the linked schema that type would look like:
type Animal struct {
    Cat *Cat `json:"cat,omitempty"`
    Dog *Dog `json:"dog,omitempty"`
}

type Cat struct {
    Claws int `json:"claws"`
}

type Dog struct {
    Paws int `json:"paws"`
}

See #98, which implements this

Resolving this as the discussion is complete and we have a PR implementing our decision pending (#98)


Bundle pre-built generic use cases

Bundle pre-built generic use cases. For example, basic Ansible roles, generic J2 templates and Robot tests.
Either as part of the webapp or something else. Or maybe just improved documentation?

Get examples from https://github.com/aburston/vmx-test-lab


run Custom tflite Model fails in TfLiteInferenceCalculator

train model by deeplapV3+ for tf2.0 and optimizar it by tensorflow_model_optimization 0.3.0
debug it and got log below:
2020-07-03 16:01:52.416 18260-18293/? D/mediapipeDebug: Following operations are not supported by GPU delegate:
BATCH_TO_SPACE_ND: Operation is not supported.
EXP: Operation is not supported.
REDUCE_MAX: Operation is not supported.
SPACE_TO_BATCH_ND: Operation is not supported.
SUM: Operation is not supported.
148 operations will run on the GPU, and the remaining 90 operations will run on the CPU.
2020-07-03 16:01:52.422 18260-18293/? D/mediapipeDebug: TfLiteGpuDelegate Prepare: Only identical batch dimension is supported
2020-07-03 16:01:52.422 18260-18293/? D/mediapipeDebug: Node number 238 (TfLiteGpuDelegate) failed to prepare.
2020-07-03 16:01:52.422 18260-18293/? D/mediapipeDebug: external/org_tensorflow/tensorflow/lite/kernels/conv.cc:345 bias->type != input_type (10 != 1)
2020-07-03 16:01:52.422 18260-18293/? D/mediapipeDebug: Node number 2 (CONV_2D) failed to prepare
could anyone help me?

The error message is BATCH_TO_SPACE_ND: Operation is not supported. EXP: Operation is not supported. REDUCE_MAX: Operation is not supported. SPACE_TO_BATCH_ND: Operation is not supported.. So, those ops are not supported by TFLite gpu. You need to either remove those ops from the graph or define those custom ops like we did here: https://github.com/google/mediapipe/tree/master/mediapipe/util/tflite/operations.

The error message is BATCH_TO_SPACE_ND: Operation is not supported. EXP: Operation is not supported. REDUCE_MAX: Operation is not supported. SPACE_TO_BATCH_ND: Operation is not supported.. So, those ops are not supported by TFLite GPU by default. You need to either remove those ops from the graph or define those custom ops like we did here: https://github.com/google/mediapipe/tree/master/mediapipe/util/tflite/operations.

i did it by your suggestion,but it does not work
i added code below:
TfLiteRegistration * BATCH_TO_SPACE_ND = tflite::ops::builtin::Register_BATCH_TO_SPACE_ND();
AddCustom("BATCH_TO_SPACE_ND", BATCH_TO_SPACE_ND);
and i got the same log:
BATCH_TO_SPACE_ND: Operation is not supported.
what's wrong with my code?


Pull request - Hello world project.

In this stage I did the following steps:

Add linters.
Create a descriptive README.md file.
Add Index.html as the main file.
Add a .gitgnore file.  in the main directory.
Fix some bugs according to linter errors.
Create a new branch Hello_Microverse.
Update some sections in the README.md file.

Thanks for your time @NduatiKagiri ...  You also did it this possible 🙂🙏👍✅


Array-based data adapter supports pagination via 'pageSize' option.

After a fair amount of searching, it looks like a lot of people are interested in supporting infinite scrolling in conjunction with the array-based adapter for large data sets. I've added support for pagination in the Select adapter. It respects a 'pageSize' argument, defaulting to the old behavior if not found.

I like the idea, and I almost went through with doing something similar to this.
Just a few notes

This needs tests
You may have better luck generating the array of matches and then slicing that you match the page.

I think this might also have issues for cases like nested representations (results that are grouped) as self.matches will filter those down and then return the root element.

Hi Kevin,
I made the first suggested change and track the full set of results and use slice() on subsequent queries. I was concerned that the first query for a single letter would take too long here, but this doesn't appear to be the case.  Code is cleaner this way and subsequent paging is perfectly fast (I can't ever see the "Loading more..." div)
Overall the behavior is quite nice for reasonably sized lists.  My current test has 2,000 items and searching is very smooth, even with 1 character. For much longer lists, we may need an adapter that can do sub-sequence matching (eg, K > Ke > Kev ...) and smart caching when deleting a term-- although adjusting the minimum query length can go a long way.
Frankly my use-case as an address book matcher puts me in the low thousands of entries and the performance is reasonable for now.

Why not create a new adapter inherit from ArrayAdapter to achieve this? for example:
define([
'./array',
'../utils',
'jquery'
], function (ArrayAdapter, Utils, $) {
  function LazyAdapter ($element, options) {
    this.lazyOptions = $.extend({}, options.get('lazy'), true);
    this.lazyOptions.pageSize = this.lazyOptions.pageSize || 30;
    this.lazyOptions.data = this.lazyOptions.data || [];

    ArrayAdapter.__super__.constructor.call(this, $element, options);
  }

  Utils.Extend(LazyAdapter, ArrayAdapter);

  LazyAdapter.prototype._genPaginatedData = function (data, params) {
    var options = this.lazyOptions;
    var page = params.page || 1;
    var term = params.term || '';
    var pageSize = this.lazyOptions.pageSize;
    var _items = [];

    try {
       _items = data.filter(function(item){
        return (item.text.indexOf(term) >= 0);
      });
    } catch (e) {
      // TODO: handle exceptions here
    }

    return {
      items: _items.slice( (page-1)*pageSize, page*pageSize ),
      totalCount: _items.length
    };
  };

  LazyAdapter.prototype._formatPaginatedResult = function (data, params) {
    params.page = params.page || 1;
    return {
      results: data.items,
      pagination: {
        more: (params.page * this.lazyOptions.pageSize) < data.totalCount
      }
    };
  };

  LazyAdapter.prototype.query = function (params, callback) {
    var data = this._genPaginatedData(this.lazyOptions.data, params);
    var results = this._formatPaginatedResult(data, params);

    callback(results);
  };

  return LazyAdapter;
});

I would love to see this feature in Select2 4.0. I use code quite similar to this which gives really nice pagination for large local datasets in Select2 3.5. I'm having quite some trouble to get this functionality working in 4.0 though.

Unfortunately this pull request contains files in the dist folder, and as a result there is a merge conflict. Because this pull request is also pretty old (our fault), we are closing this off.
If you are still interested in making this contribution, feel free to remove the dist changes from this pull request and leave a comment asking for this to be re-reviewed. Or make a new pull request from the same branch, and we'll try to get around to reviewing it this time.


Can you please publish<EMAIL_ADDRESS>to pypi?

The last version is 1.1.11 on pypi:
https://pypi.org/project/libeospy

uploaded.


feat: Add a Wallet interface

In the beginning, one part of warp was to deal with cryptocurrency (though was not limited to it). The base at the time was solana, and although solana was used initially for identity and friending (apart from other smart contract aspects), one part that was discussed a bit but never implemented was a interface to handle wallet side such as transacting, etc. Currently we use ipfs as the main component for identity, files and chat in warp, however we still lack such a interface (and thus any implementation) for dealing with crypto wallets.
The interface should provide functions for (but not limited too):

Listing addresses and transactions
Listing tokens from smart contracts
Transacting (sending/receiving crypto between users)
Signing and validating messages (although this can be done with the private/public key directly, cryptocurrencies are known to have derivation path, which can generate its own set of keys that can be used for signing/verifying messages (including transactions) so this could be done on the interface itself based on the provided key).

While it would be preferred to have each wallet implementation to be separate (to reduce complexity and provide options for those who wish to switch between different implementations in the future), a single implementation can include multiple wallet implementations. The interface may also introduce associated types to reflect for specific address types (if the interface doesnt come with a generic item to represent different address formats and allow the implementation to parse accordingly), different cryptocurrencies (if multiple is implemented in a single implementation), etc.
Note:

This interface should be detach from the other components, but internally, the implementation can interact with other components as needed (eg sending addresses between friends would require interacting with MultiPass and RayGun, etc.)
warp core library has a helper function to generate a ed25519 keypair based on the mnemonic phrase (the implementation is based on ed25519-dalek-bip32). If other implementations are used, this helper function should probably be changed to represent the correct keypair.

warp-ipfs also depends on ed25519 so if the main keypair is going to be used, this should be kept in mind if attempting to derive from the keypair used there.
We can also store the seed generated in tesseract and allow implementations to derive a keypair from that accordingly.
Could possibly benefit from #324

Information here TBD

I think it's worth considering implementing this as an uplink extension.
The backend of a wallet is really its blockchain. And there isn't really a universal way to interact with all the different types of blockchains - they all have different features or different ways of implementing them that directly affect how the the end-user would interact with it.
That said, we probably still want to be able to use the same recovery phrase for all of them, so we'd need at least some interaction with Warp still.
I think it would make sense for third parties to want to create their own wallet extensions. And ours could serve as a model for anyone wishing to do so.

Do keep in mind the extensions on uplink is different than what is here on warp as the extensions there are more of a plugin that add interaction to the UI.
With that said, might be more appropriate to have it on warp, although I do agree there isnt a universal or simple way of interacting with different blockchains, but having a interface that would use common functions that implementations can use would be a start for its usage as the implementations would handle the bulk load of dealing with it. Of course if @InfamousVague wish to have this solely on uplink side, then that could be done there instead.

Also, one big benefit of having it on the warp side is it might make it easier to unify info from multiple blockchains together. For example with wrapped or bridged assets across multiple chains. Creating implementations for every type of blockchain would be endless work though, so we'd probably end up creating implementations for just the most popular ones.
If the uplink extensions are only intended to add interaction to the UI, then perhaps it's best to stick to this pattern. Although I suppose we can't stop a 3rd party from adding whatever functionality they want through an uplink extension, be it a wallet or anything else.


Disable TODO App example test

This test is failing in master but I am not able to reproduce the issue. Disabling it for the moment since it doesn't test any particular feature of the plugin.

/lgtm


Refine webauthn verifier

Refine WebAuthnVerifier to conform to precompiled p256 verifier (RIP-7212).

Summary:
Tested successfully with the following wAAllet extensions:

Local PasskeyAccount v0.6 (Irara MacOS keychain)
Local PasskeyAccount v0.7 (Irara MacOS keychain)


dalfox as a library

Hi @hahwul ,
Hope you are all well !
It would be awesome to use dalfox as a library like that:
package main

import (
  "fmt"
  "time"

  dalfox "github.com/hahwul/dalfox/v2/lib"
)

func main() {
  opts := dalfox.Options{Worker: 100, ...}
  targeter := dalfox.NewScan(dalfox.Target{
    Options: opts,
    Method: "GET",
    URL:    "http://localhost:9100/",
  })
  scanner := targeter.Run()

  fmt.Printf("results: %s\n", scanner.Data)
}

Is it something that we can expect on the roadmap ?
Cheers,
Luc Michalski

Hi @lucmichalski
Yes, that's right! What I'm ultimately after is the support to library of scanner. This project have a cool contributors, but I'm noob and I don't have much time, so I don't know how soon I can support to the lib 😭
I need to roll up our sleeves. even if it's boring, please wait a little bit! 😎🚀

lol you are crazy dude :-) completamente loco
On a more serious note, it would be really useful to contribute to dalfox if bundled as library, maybe go plugins ^^

The part about the scan and model, structure be implemented to some extent and included in v2.4.0. (beta feature)

@lucmichalski
Sample of code
package main

import (
	"fmt"

	dalfox "github.com/hahwul/dalfox/v2/lib"
)

func main() {
	opt := dalfox.Options{
		Cookie:     "ABCD=1234",
	}
	result, err := dalfox.NewScan(dalfox.Target{
		URL:     "https://xss-game.appspot.com/level1/frame",
		Method:  "GET",
		Options: opt,
	})
	if err != {
		fmt.Println(err)
	} else {
		fmt.Println(result)
	}
}

result from NewScan() is interface > Result struct
https://github.com/hahwul/dalfox/blob/ea1a4482d97a5acd7e36f077482f968527a61393/lib/interface.go#L44
https://github.com/hahwul/dalfox/blob/ea1a4482d97a5acd7e36f077482f968527a61393/pkg/model/result.go#L8


Notify users about incorrect installation

The Problem To Be Solved
Can this be reviewed/added https://github.com/Open-CMSIS-Pack/devtools/pull/1600
Suggest A Solution
Change messages to:
"error: no compiler registered. Add path to compiler with environment variable CMSIS_COMPILER_ROOT=<name>_TOOLCHAIN_<major>_<minor>_<patch>. <name> is one of AC6, GCC, IAR, CLANG."
If the cmake files in ./etc directory are missing, output:
"error: no toolchain cmake files found. Check ./etc directory and verify CMSIS-Toolbox installation."

CMSIS_COMPILER_ROOT  cannot be used to specify a compiler registration environment variable. This variable is used to point to an alternative directory to the ./etc directory of the CMSIS-Toolbox installation, containing e.g. the *.cmake files for the supported toolchains (see: https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/installation.md#environment-variables)

@jkrech you are correct.
Suggest to make the message a bit shorter
"error: no compiler registered. Add path to compiler ./bin directory with environment variable <name>_TOOLCHAIN_<major>_<minor>_<patch>. <name> is one of AC6, GCC, IAR, CLANG."


Hex offline not finding packages

Issue description
In attempting to get Elixir's Phoenix up and running on Nix, I ran into the small issue that the package was out of date- as were some of its dependencies- either way, it will not build out-of-the-box in its currently offered state.
So I started updating/adding to a checkout of master.
I'm finding that I have to edit ./mix.exs such that all of its dependencies are local path entries rather than hex entries. Otherwise the builds fail.
For example, when building plug_1_8_0, I get this error for some of its dependencies:
Unchecked dependencies for environment prod:
* telemetry (Hex package)
  the dependency is not available, run "mix deps.get"
* mime (Hex package)
  the dependency is not available, run "mix deps.get"
* plug_crypto (Hex package)
  the dependency is not available, run "mix deps.get"

Steps to reproduce

Clone nixpkgs
Add entry in beamPackages for cowlib_2_7_3 (buildErlangMk)
Update cowlib to cowlib_2_7_3
Add entry in beamPackages for cowboy_2_6_3 (buildErlangMk)
Update cowboy to cowboy_2_6_3
Add entry in beamPackages for telemetry_0_4_0 (buildRebar3)
Add entry in beamPackages for telemetry and set it to telemetry_0_4_0
Add entry in beamPackages for mime_1_3_1 (buildMix)
Update mime to mime_1_3_1
Add entry in beamPackages for plug_crypto_1_0_0 (buildMix)
Add entry in beamPackages for plug_crypto and set it to plug_crypto_1_0_0
Add entry in beamPackages for plug_1_8_0 (buildMix)

making sure the argument set includes telemetry, mime, and plug_crypto (change cowboy_x_y_z to cowboy)
and that the beamDeps attribute passed into buildMix contains these, as well cowboy

Update plug to plug_1_8_0
nix-env -if "</possibly/relative/path/to>/nixpkgs" -A beamPackages.plug

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.34, NixOS, 19.03.172231.7b36963e7a7 (Koi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(root): `nixos-19.03.172231.7b36963e7a7`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This issue is caused by https://github.com/NixOS/nixpkgs/pull/25655.

Closed by #64884.


add sequence chaining

Modified the Openwhisk wrapper to unflatten sequence action payload
Make use of wsk cli to create sequence
Obtain individual metrics for each action in the compose

Added hello world split->sort sequence example


Comparison to dust?

When searching for NCDU alternatives dust and dua come up, and both projects are written in Rust, but neither project mentions the other.

Created a similar issue with dust: https://github.com/bootandy/dust/issues/145

I am not using dust and hence wouldn't know what the major differences are.
Maybe starting to mention similar tools would be helpful to people landing on either one of these projects.

FWIW having tried both briefly dust doesn't seem like a very suitable ncdu replacement since I don't think it has an interactive mode.

It seems the motivation for this issue is mainly the comparison to NCDU and it will help me to close this issue.
My reasoning here is that NCDU users will know what they get from the tool and are able to check the video provided on the landing page to get an idea of what dua is for. Then they will probably know if it can or can't replace their usage of ncdu, or is rather a specialized utility to use on top of NCDU.
Thanks for your understanding.


Add Content: " Heart Disease Classification Using Machine Learning"?

Aim:  Given medical patient's attributes, is it possible for a Machine Learning model to predict whether or not the patient has a heart disease?
Dataset: https://archive.ics.uci.edu/dataset/45/heart+disease

@kRiShNa-429407   will you please assign this to me because i worked on such issues previously


Fix outdated timing information in host_guest_instructions.md

Fix some timing info in the host-guest instructions we'd forgotten to update when we brought in the SAMPLing challenge info

@andrrizzi can you check?


session.get no longer working? New API?

I haven't tried for quite some time and it worked before. But now, I get the following error:
  File ...\scrape.py", line 47, in download_story
    story_title = storyinfo['title']
KeyError: 'title'

Line 47 contains the following call:
story_title = storyinfo['title']
It seems storyinfo is empty. Calling it results in the following error:
{'error_code': 1001, 'error_type': 'InvalidEndpoint', 'message': 'API method not found'}
-> I suspect the API has changed. Is there any chance we can get it working under the new API?
Best regards

spitfire

It looks like it still works, I can check with a specific story if you can give me the link.
I'm not really maintaining this project at the moment. Most of the functionality got added to https://github.com/JimmXinu/FanFicFare though, you can try it. FanFicFare is usable on the command line or as a Calibre plugin

Thx very much, must have something to do with my local installation, then. I tried FanFicFare and it works perfectly, thx for pointing me to it! Best regards, Pesche


Add more builds to CI

CI currently only runs the build process for Windows; we should add builds for Mac (and possibly Linux) too.

We won’t be able to do this (for Mac) until issue #33 is resolved, so this may be shelved for a while.


[Bug]: panic "should have dependency id" in import_meta_context_dependency

Details
https://github.com/web-infra-dev/rspack/blob/9e92b5c76b930c98d68c271f21a53170131979f3/crates/rspack_plugin_javascript/src/dependency/context/import_meta_context_dependency.rs#L92
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  should have dependency id
Location: crates/rspack_plugin_javascript/src/dependency/context/import_meta_context_dependency.rs:92

Reproduce link
No response
Reproduce Steps
webpack-test/configCases/resolve/issue-15580

I'm facing with the same issue:
$ rsbuild dev
  Rsbuild v0.3.11

  > Local:    http://localhost:8080/
  > Network:  http://<IP_ADDRESS>:8080/

start   Compiling...
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  should have dependency id
Location: crates/rspack_plugin_javascript/src/dependency/context/import_context_dependency.rs:100

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _napi_register_module_v1
    at <unknown source file>
 6: _napi_register_module_v1
    at <unknown source file>
 7: _napi_register_module_v1
    at <unknown source file>
 8: _napi_register_module_v1
    at <unknown source file>
 9: _napi_register_module_v1
    at <unknown source file>
10: _napi_register_module_v1
    at <unknown source file>
11: _napi_register_module_v1
    at <unknown source file>
12: _napi_register_module_v1
    at <unknown source file>
13: _napi_register_module_v1
    at <unknown source file>
14: _napi_register_module_v1
    at <unknown source file>
15: _napi_register_module_v1
    at <unknown source file>
16: _napi_register_module_v1
    at <unknown source file>
17: _napi_register_module_v1
    at <unknown source file>
18: _napi_register_module_v1
    at <unknown source file>
19: _napi_register_module_v1
    at <unknown source file>
20: _napi_register_module_v1
    at <unknown source file>
21: _napi_register_module_v1
    at <unknown source file>
22: _napi_register_module_v1
    at <unknown source file>
23: _napi_register_module_v1
    at <unknown source file>
24: _napi_register_module_v1
    at <unknown source file>
25: _napi_register_module_v1
    at <unknown source file>
26: _napi_register_module_v1
    at <unknown source file>
27: _napi_register_module_v1
    at <unknown source file>
28: _napi_register_module_v1
    at <unknown source file>
29: _napi_register_module_v1
    at <unknown source file>
30: _napi_register_module_v1
    at <unknown source file>
31: _napi_register_module_v1
    at <unknown source file>
32: _napi_register_module_v1
    at <unknown source file>
33: __pthread_joiner_wake
    at <unknown source file>
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I am getting this error
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  internal error: entered unreachable code
Location: crates/rspack_plugin_javascript/src/dependency/esm/provide_dependency.rs:82

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.

@sachin-walunj this doesn't appear to be the same error. Can you create a new issue and provide a repository to enable us to reproduce the error?

I am getting this error
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  internal error: entered unreachable code
Location: crates/rspack_plugin_javascript/src/dependency/esm/provide_dependency.rs:82

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  internal error: entered unreachable code
Location: crates/rspack_plugin_javascript/src/dependency/esm/provide_dependency.rs:82

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _napi_register_module_v1
    at <unknown source file>
 6: _napi_register_module_v1
    at <unknown source file>
 7: _napi_register_module_v1
    at <unknown source file>
 8: _napi_register_module_v1
    at <unknown source file>
 9: _napi_register_module_v1
    at <unknown source file>
10: _napi_register_module_v1
    at <unknown source file>
11: _napi_register_module_v1
    at <unknown source file>

I used the " jszip" and this error occurred


how use it with a empty view

i solved the problem by putting the PullRefreshLayout in a RelativeLayout and it worked fine.
but i faced another problem : I'm needing to put a TextView inside the PullRefreshLayout , but no way
any help please .... ?? thanks

The same error for the recycler view when trying to show a text view if there is no data.


Add example code and instructions for an overlay style search interface

Should by default be designed for web collections. Core base features to include:

[ ] overlay base css
[ ] overlay animate in on trigger
[x] logo left on desktop, on top on mobile style layout, click logo to exit
[x] close button in top right
[x] search box in top bar
[x] results rendering in main section under top bar
[ ] esc to exit

And:

[ ] readme explaining how to build and release.
[ ] add animated gif showing what it does in action

@tbillington i think most of this is done now?

There is an example but it needs a little bit more work. https://github.com/sajari/sajari-sdk-react/tree/master/examples/overlay.

@tbillington can we close this out as we put up the other example?

Done. See: https://github.com/sajari/website-search-integration


Textures appear black when Smooth Lighting is off

It isn't sodium or any other mod bc I tested just by itself.

Thanks for reporting, I honestly have never tested with smooth lighting off. I’ll get it fixed 👍

I use smooth lighting because of the nostalgia aspect to it. Feels like beta days with it off.

Well I'd hate to ruin the nostalgia - it's fixed in 0.17.3 (only on 1.19.2 at the moment)


parent_team_id is an integer identifier, not a string

Using the code as written in the NestedTeamsPreview branch produces an error when talking to the GitHub API:
panic: PATCH https://api.github.com/teams/2514825: 422 Invalid request.

For 'properties/parent_team_id', "2514824" is not a number or null. []

The documentation states that this parameter is an id type which--for the GitHub API--appears to mean an integer, not a string.

:eyes: @elliott-beach @gmlewis

LGTM,
but I think GitHub should fix their docs. This may be the first JSON parameter in the API that has the type of id, and when the API returns ids, the type is an integer, not a string. It seems the documentation is ambiguous on the argument type - I will email GitHub.

Response from GitHub:

Thanks for writing back to clarify! I see what you mean now and agree it would be helpful to update the type there. I've opened an issue internally for our Documentation team to take a look and consider updating for future iterations. Please let us know if you spot anything else like this and we'd be happy to take another look!

So, we will have to wait for this to be fixed, or not.

So the response doesn't really confirm that the type is an integer, does it?

I got another email that confirmed that the type is an integer. I also realized that my thinking on this had been backward the whole time - it makes perfect sense for ID to be an int, it should not have required emailing GitHub at all.

This has my and Elliott's approvals. I'll merge this PR into NestedTeamsPreview branch and we can continue discussion/review there. Thanks @alindeman!


Travis CI Integration scripts

This PR introduces minimal Travis-CI integration scripts. This was earlier discussed here #118 and didn't got enough attention
I am now using Travis with one other project and I really see that it is usefull to see if incoming PR breaks code or not
Travis will make automatic compilation of dtest (and execute it with --runall) and all examples (no running - build only) on each incoming PR and PR change. Author of PR will show integration result immediately with no need to as Davis to check his code.
This does not replace existing way to test dlib on existing servers, but can be usefull as an additional automatic CI tool visible to PR authors
How to integrate:

register on https://travis-ci.org/ with using github account (Free for open-source)
"My repositiories" -> press "+" -> select repository (press switch) and press "settings"
enable "Build only if .travis.yml is present" and "Build pull requests"
If you want to check direct pushes to a master branch - enable  "Build pushes"  too
test with sample PR

After that every new PR and changes on existing PR will get additional testing results information
Testing time is about 15 minutes long
I can extend this scripts to make automatic python and tools test-building too
Cuda is not supported now, but i think its possible to test cuda + cudnn compilation too. Running CUDA tests will not be possible
Its possible to add Clang compiler testing too
May be - mingw/linux
Visual Studio - now not possible, but may be in a future
Code coverage measurement - possible as next steps
If you will want to remove it in a future - delete .travis.yml file and dlib/travis directory

Sweet.  I'll try it out.  Does github automatically display the rest of testing on a PR or do we need to add something to github?


ngrok share not work

share_1  | [07/05/16 17:55:38] [INFO] Reading configuration file /.ngrok
share_1  | [07/05/16 17:55:38] [INFO] [client] Trusting root CAs: [assets/client/tls/ngrokroot.crt]
share_1  | [07/05/16 17:55:38] [INFO] [view] [web] Serving web interface on <IP_ADDRESS>:4040
share_1  | [07/05/16 17:55:38] [INFO] Checking for update
share_1  | [07/05/16 17:55:38] [EROR] control recovering from failure dial tcp: lookup ngrokd.ngrok.com: no such host
share_1  | [07/05/16 17:55:38] [INFO] Waiting 1 seconds before reconnecting
share_1  | [07/05/16 17:55:39] [EROR] Error while checking for update: Post https://api.equinox.io/1/Updates: x509: failed to load system roots and no roots provided
share_1  | [07/05/16 17:55:44] [EROR] control recovering from failure dial tcp: lookup ngrokd.ngrok.com: no such host
share_1  | [07/05/16 17:55:44] [INFO] Waiting 2 seconds before reconnecting
share_1  | [07/05/16 17:55:46] [EROR] control recovering from failure dial tcp: lookup ngrokd.ngrok.com: no such host
share_1  | [07/05/16 17:55:46] [INFO] Waiting 4 seconds before reconnecting
share_1  | [07/05/16 17:55:50] [EROR] control recovering from failure dial tcp: lookup ngrokd.ngrok.com: no such host
share_1  | [07/05/16 17:55:50] [INFO] Waiting 8 seconds before reconnecting
share_1  | [07/05/16 17:55:58] [EROR] control recovering from failure dial tcp: lookup ngrokd.ngrok.com: no such host
share_1  | [07/05/16 17:55:58] [INFO] Waiting 16 seconds before reconnecting

@sy2nyk that's for reporting this. I guess no one used this in a while and something got outdated.

sy2nyk/docker-ngrok
For getting url i'm use docker-compose logs share | grep "URL"

@sy2nyk here's a more recent docker image for ngrok (I guess we should have our own): wernight/ngrok
Try it like this. In docker-compose.yml:
share:
  hostname: share
  image: wernight/ngrok
  ports:
    - "4040:4040"
  links:
    - web:app

then run
docker-compose rm -vf share
dsh up

You can get the assigned domain name by accessing ngrok's web UI at http://<IP_ADDRESS>:4040
...
Just saw your new comment. If that works for you - great :)
Going to keep this issue open until we have our own ngrok image and a PR to updates the docs.
I'm also now thinking about having ngrok as a global system service in Drude, however that will make domain management and request inspection per project difficult. As a project level service each ngrok instance is serving a single project, which makes things easier.


Separate review for dubious applications

Find a way to mark dubious applications, review them separately and then get them back to the voting system.
My first approach would be to:

Have an extra button in the vote view that separates it for an in-depth review.
Applications that need in-depth review should not be in the review tab rotation.
Have a list view of this separated applications.
View to review a single application and bring it back to voting/reject it.
Add comments to the application automatically when marked as to be reviewed, and marked as valid or invalid so that further people reviewing it have context around it.

We would need to add an extra state on the application model for this. Everything else should be easy to do.

Status:

Dubious - Not contacted
Dubious - Contacted (requires a user assigned to task)
Invalid

Need to assign organizers to it. Thanks @dreaqdp for the feedback!


User's display name encoding

UserController.SignInCompleted returns userState in json. But this will not be able to handle accent characters like my name László. I suggest adding some encoding and UserStateProvider.OnSignInStateChanged method should decode or fire
CurrentUser = await HttpClient.GetJsonAsync<UserState>($"/user");

I suspect that what's happening here is actually that the decoding is busted. Blazor currently using SimpleJSON which has had lots of random bugs for us. We're switching to use System.Text.Json for preview 6 and I'll try this out then.


Need example/method for Txy, Pxy, and xy diagrams for binary systems

Txy, Pxy, and xy diagrams are some of the simplest and most fundamental thermodynamic diagrams for characterizing a binary system, and something any thermo user (or student) would want to produce.
There are no examples of, or methods for, generating Txy, Pxy, or xy diagrams.  The closest is the plot_TP method of Flash.
They were implemented once here, but this is now relegated to the Legacy Property Packages module.

Hi Alex,
I may be able to get to this. Two-component systems are essentially two phase, and the flash algorithms for that are pretty good. It is only near the critical point that issues occur, or at very low pressures.
To improve the behavior and allow convergence near the critical point, I want to figure out and understand Dr. Ulrich Deiters and Dr. Ian Bell's paper on the topic:
Deiters, Ulrich K., and Ian H. Bell. “Calculation of Phase Envelopes of Fluid Mixtures through Parametric Marching.” AIChE Journal 0, no. 0 (n.d.): e16730. https://doi.org/10.1002/aic.16730.
I haven't made progress on understanding it so far, however.
Caleb

This functionality is now implemented. Binary systems are shown with the Modified UNIFAC model for the liquid phase and Peng-Robinson for the vapor phase, here.
Phase envelope functionality for multicomponent systems also has an example, in this case the nitrogen-oxygen-argon system, here.
Limited improvements to the convergence of bubble and dew points has been made in the mean time, as well.


Bug when running on windows

When running on windows, there is an issue with the formatting and how it interacts with pelican formatting. The first indication of this issue was the URLS were showing up like this: http://<IP_ADDRESS>:8000/%7Bfilename%7D/reference/Databricks/Databricks Tables.md
In the section of code where the paths are assigned and built: https://github.com/jonathan-s/pelican-obsidian/blob/0180f425355bfdce2fe4ab4b5a658ed95dd23565/pelican/plugins/obsidian/obsidian.py#L55-L60
I added some debug line to see what was going on.
Path: \reference\Databricks/
Filename: Databricks Tables
Fullpath: \reference\Databricks/Databricks Tables
Replaced Link:[Databricks Tables]({filename}\reference\Databricks/Databricks Tables.md)

I suspected that the two slashes - back and forward slash - were causing issues. After going in and manually putting links in markdown files it was discovered that ANY backslashes do not work correctly.
Doesn't work: [Databricks Tables]({filename}\reference\Databricks\Databricks Tables.md)
Doesn't work: [Databricks Tables]({filename}\reference\Databricks/Databricks Tables.md)
Does work: [Databricks Tables]({filename}/reference/Databricks/Databricks Tables.md)
Because of this behavior, I think that this issue is actually with how Pelican parses links - it jsut doesn't work with Windows style links
Solution:
Replace all separators with forward slashes regardless of operating system:
link_structure = link_structure.replace(os.sep, '/')

I plan on making a PR for this soon, but this is a temporary work around until then.

Thank you, since I'm not running windows, I won't be able to check this. Happy to accept a PR for it though.

Though rather than doing str.replace, it might be better to use pathlib.Path to build up the path first and then get the string version of that.

@acherrera FYI I have solved this by using vscode + devcontainer in my Windows machine for now.

@acherrera This has been fixed in this PR #13.
Could you check and close the same?


Don't overwrite nameClean if it has already been set

If a pseudo-pattern has a documentation file, nameClean might already be set in the data store. This PR adds a check for an existing nameClean. If an existing nameClean is found, it will not be overwritten by the default value set in PseudoPatternRule.

Merged into master as well and released as v2.7.6


Water Sensors: NYC VA W

This site is completely offline.

received data download from this farm and it looks good


Support of wss connections

We want to use nginx proxy with ssl termination but it seems that selenoid-ui doesn't support of secure websockets. I have the following error in console:
Failed when connecting: Error while connecting (SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.)

ws now hardcoded here:
https://github.com/aerokube/selenoid-ui/blob/master/web/src/components/Log/index.js#L53
and here:
https://github.com/aerokube/selenoid-ui/blob/master/web/src/components/VncCard/VncScreen.js#L66
If you have any thought on how to make it customizable, you are welcome ;)

@alexandrvb Do you mind posting the nginx configuration? I couldn´t make it work behind an nginx proxy.
Thanks


Replace /usr/bin/env with env-friendly

/usr/bin/env never ends up in PATH, and is only used for shebang lines, which permit passing only a single argument (the executable) to env, and definitely don't require full GNU coreutils env(1).
This replaces it with a minimal, small (21K) statically-linked binary.
(I expect this change to be somewhat controversial, but I'd rather have the discussion around a PR with actual working code, so here it is)

What exactly do we gain by using this variant of /usr/bin/env instead of the one from coreutils or busybox?

stdenv.mkDerivation depends on coreutils anyway, so using this variant  during builds would actually add code to the environment rather than save some.

Build products might contain scripts that refer to /usr/bin/env, but in practice they don't because the patchShebangs hook removes them.

I'm not sure whether I see the benefits.

@peti I'm using this for my minimal Nix-based containers — I'd like to prevent accidentally pulling in coreutils. In addition, I've found that the build chroot still occasionally ends up requiring /usr/bin/env, and the same applies.
In addition: the things that rely on /usr/bin/env should only be using it for this one rather simple case. I'd like to ensure it won't be used for anything else.

I understand that for normal NixOS systems, this will increase the size of the closure (by 21 kilobytes), but limiting the impurity of /usr/bin/env by ensuring it is only used for the one thing that requires it seems worth 21K to me. For my containers, glibc isn't even necessarily present, so it does affect closure size.

I'm using this for my minimal Nix-based containers — I'd like to prevent accidentally pulling in coreutils.

Well, as I said, build products should not depend on /usr/bin/env due to patchShebangs. If they do, then that's a bug that should be fixed.

I've found that the build chroot still occasionally ends up requiring /usr/bin/env, and the same applies.

Chrooted builds have no /usr/bin/env. Packages that rely on that path at built time will fail (https://github.com/NixOS/nixpkgs/issues/6227).

Assuming this is really needed, we shouldn't implement our own env but either have a tiny package that copies env from coreutils, or put env in a separate output of coreutils. Having /usr/bin/env differ from the one in coreutils is going to give lots of confusion/breakage.
However, given that this is probably a fairly special use case, it may be better to override /usr/bin/env in your own configurations by doing something like system.activationScripts.usrbinenv = mkForce "...".

@peti I'm aware, and I've ended up adding it to my chroot nevertheless because I've run into cases where packages were broken.
However, this isn't very relevant. My real issue is: if we're shipping an impurity in NixOS, wouldn't we want it to be the most minimally-featured version of the program for the task at hand?
Does /usr/bin/env for shebang usage need the full feature set of GNU coreutils env(1), and should we encourage relying on that? I'd consider the basic version I've added here the lesser of two evils.

@edolstra I'm purposely not implementing the full feature set of coreutils env, because I'd like to ensure it's unusable for anything but its sole intended use-case: shebangs.
It's unavoidable to use it for shell scripts (even if just to invoke nix-shell), and that's the only case that won't use it from PATH. This program will never make its way into PATH, so shouldn't break compatibility with anything existing.

For specific cases this can surely be useful, but having a different env in by default seems dangerous, e.g. in many cases /usr/bin will be in $PATH...

@vcunat It won't be on NixOS, to my knowledge — am I mistaken here?
On any other OS, this won't be used.

So, in case I'm misunderstanding things here: Is there any valid reason to call /usr/bin/env by that exact PATH on NixOS that isn't a shebang? Do we specifically intend to have a full GNU-compatible /usr/bin/env?

Is there any valid reason to call /usr/bin/env by that exact PATH on NixOS that isn't a shebang?

There is no reason to call /usr/bin/env from Nixpkgs/NixOS whatsoever. If packages rely on that path, then they are broken and should be fixed. That path exists solely for NixOS users who want to write portable script that need to call, say bash, but in a way that works on non-NixOS machines, too, i.e.:
#! /usr/bin/env bash

Packages that are controlled by Nix, however, should not do that.

@peti I'm aware, and this is the sole use case I want to support. Heck, even, maintainer scripts in the nixpkgs tree use this. I just don't understand how it requires coreutils env to allow this, or why it is positive to expose the extra API surface that the GNU version provides.

It won't be on NixOS, to my knowledge — am I mistaken here?

No, NixOS doesn't put /usr/bin into $PATH but many packages do probe such paths because upstream made it so. We've patched some of these cases, but surely not all.

@vcunat Paraphrasing @peti:
If packages rely on /usr/bin/env being the GNU coreutils version, then they are broken and should be fixed. That path exists solely for NixOS users who want to write portable scripts that need to call, say bash, but in a way that works on non-NixOS machines, too, i.e.:
#! /usr/bin/env bash

@edolstra even if we put it in a separate output, it still depends on glibc, which is a pretty hefty requirement for something that doesn't really need to do anything, and which nobody should be using from that path except for occasional compatibility hacks.

I just don't understand how it requires coreutils env to allow this, or why it is positive to expose the extra API surface that the GNU version provides.

There is no NixOS system in the world that doesn't have coreutils installed anyway, so using a special variant of env just adds complexity instead of reducing it.

There is no NixOS system in the world that doesn't have coreutils installed

I thought that was exactly what he was claiming to have made this for. Minimal statically managed containers/images that have the closure of the programs they need and nothing else.

I thought that was exactly what he was claiming to have made this for. Minimal statically managed containers/images that have the closure of the programs they need and nothing else.

If these programs are installed through Nix, then they should not depend on /usr/bin/env in the first place due to patchShebangs.

@peti yeah, but the system closure will contain it regardless of the actual closure of your program due to the NixOS activation script (which you can see him patching in this PR) depending on it.

If @nathan7 is using this for small containers, wouldn't it be best to just be able to disable /usr/bin/env then?

If packages rely on that path, then they are broken and should be fixed. That path exists solely for NixOS users who want to write portable scripts that need to call, say bash, […]

This is literally all of my goal: removing the leniency from /usr/bin/env so that is its sole purpose.

@domenkozar I can do that, but the implicit claim being made is that the full coreutils functionality is somehow essential to the functioning of NixOS or portable shell scripts.

OK, then we can make /usr/bin/env pluggable and for such special cases you can easily override it.

@nathan7 perhaps just make the /usr/bin/env path (and perhaps /bin/sh while we're at it) parameters to a NixOS module that default to coreutils and bash, but don't have to be? Then just drop env-friendly into nixpkgs and use it for your image configurations?

@domenkozar @copumpkin Again, the implicit claim being made is that the full coreutils functionality is somehow essential to the functioning of NixOS or portable shell scripts — if this behaviour is available, it will be relied on.
Hence I would need to support it for my customers' containers too, since there is no effective commitment to not relying on it on the NixOS side.

@nathan7 I'm not following, what are you trying to say? Can you explain without pronouns?

@copumpkin Making /bin/sh pluggable is a great idea, though! I was told (by a comment in nixpkgs, iirc) that many things in NixOS rely on /bin/sh being bash, so while I doubt I'd use that in production, it's probably worth assessing what breaks if we switch it to, say, dash, or even busybox ash.

@domenkozar the question is about what is the basic assumed "API" of NixOS? We expect to have a working Nix installation, plus two impurities, /bin/sh and /usr/bin/env. Now the question is what do we assume about the two impurities? Is /bin/sh expected to be bash or is anything compatible with sh enough? Is /usr/bin/env expected to be coreutils env or will any env work?
If we explicitly want to commit to a gnu coreutils-compatible /usr/bin/env, we should say so somewhere, but I think that's mostly incidental. At the same time, with no official policy, people might start assuming that and do fancier things in their shebangs. Having said that, I have never seen anyone do anything nontrivial with /usr/bin/env, so that's why I think @nathan7's proposal is almost certainly fine, and a meaningful improvement to a use case I have as well.

@copumpkin @nathan7 from NixOS perspective it doesn't really matter. What matters is, what does the invoked shell script expect. I'm sure you'll find software that doesn't work with either of solutions.
We're very much GNU based and I'd prefer it says this way (especially compared to ad-hoc solutions tested with "works for me").
I do think it's great value if /bin/sh and /usr/bin/env are pluggable for adventurous folks needing flexibility.

One last point I made on IRC:

I'm also fine with us being generally GNU-based, but not unnecessarily so. I can't make /usr/bin/env gnu coreutils in darwin, and nor can folks installing it on other systems/distros. The impurities outside of Nix's control should be as minimal as possible.

Basically, as you say, " what matters is, what does the invoked shell script expect." Given that they generally run across all Unixes, most shebangs don't expect fancy features in either /bin/sh or /usr/bin/env, so I think it should generally be fine for us to use minimal implementations of at least the latter, and perhaps the former someday (but that's another can of worms we should discuss separately).
Anyone want to go ahead and make a couple of attributes in the NixOS module that governs the activation script, so we can plug and play with the /bin/sh and /usr/bin/env links? Ideally I'd like them to be nullable values that default to ${bash}/bin/bash and ${coreutils}/bin/env, but if null, we don't even create the symlinks at all. Mostly to allow those of us who are interested to experiment with killing the impurities altogether.

I've been looking through the configuration.nix man page trying to find the option that determines where /bin/sh symlinks to, but I cannot find any. That's quite puzzling, because I could have sworn that I have added that option personally a while ago. Either my memory betrays me or that option has been removed. Duh! Anyway, my thoughts on this issue so far are:

No code in NixOS should use /usr/bin/env. This implies that

no code in Nixpkgs uses /usr/bin/env either, and we kind-of know that it doesn't because that path doesn't exist in chroot environments that build Nixpkgs.

The contents / existence of the path /usr/bin/env on NixOS machines should be configurable via configuration.nix.

This particular pull request simply replaces the current /usr/bin/env symlink with something else, and I see no advantage in doing that, therefore I'd say :-1: on this patch in its current form.

@peti agree, and I think we're all roughly aligned with the path forward:

Someone makes a PR to add the options for repointing the activation script symlinks to other locations
@nathan7 submits his env-friendly as a regular package which he can then point the new NixOS config options at
We amend the documentation to clarify that we aren't committing to /usr/bin/env being coreutils
???
Profit

We amend the documentation to clarify that we aren't committing to /usr/bin/env being coreutils.

It seems reasonable, though, to expect an env binary that conforms to POSIX: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/env.html.

@peti that seems reasonable, which I guess this PR doesn't meet, but the one on OS X does and I assume most others do too.
@nathan7 it seems like you could package this up and see what breaks, and then add the -i option as needed for your deployments

One last thing: I'd very much prefer the source code for env-friendly to live on Github or elsewhere and be download from there. I don't think Nixpkgs is the right place to check that code into directly.

@peti :+1:

With https://github.com/NixOS/nixpkgs/pull/12481 merged, I suppose this PR can be closed.


SDK: Increment child_count in Span when creating child Spans

child_count is currently initialized to 0 in Span and never incremented. The OTLP spec marks child_count as optional, but if it is provided, it should represent the count of child spans created for a span. We're in violation of the spec by providing it, but always setting to 0.
child_count is problematic in general, because we may not know the count of (immediate) child spans by the time we finish a span, and because we can create a child span without having a direct reference to its parent. Examples:

Call tracer.start_span('child', with_parent_context: context).
Enqueue a job in Resque. Optimistically assume it will be run exactly once, so increment the child_count of the producer span.

Regardless, we can try to count correctly when we have a reference to the unfinished parent. Firstly, we need a way to notify the parent span, e.g. parent_span.increment_child_count. Secondly, we need to increment at the appropriate places. We only want to do this when span.recording? and parent_span.recording?, or when we can reasonably assume a child span will be created in a remote process:

In Tracer#start_span we need to propagate with_parent to internal_create_span, and in internal_create_span in the branch creating a SDK Span, we need to parent_span.increment_child_count if parent_span&.recording?.
In each adapter that assumes creation of a remote child span, when calling e.g. formatter.inject(span.context, request.headers) also call span.increment_child_count. This one is 💩 from an API perspective, since it requires adding #increment_child_count to the public API for Span, and it's kinda hard to use and explain. It does mean we can avoid the if parent_span.recording? check in the previous case. It might get more complicated if we want to assume remote processes respect our sampling decision.

Relevant spec issue: https://github.com/open-telemetry/opentelemetry-specification/issues/355

Related conversations are now indicating that only local (which I take to mean in process) spans should count towards this metric https://github.com/open-telemetry/opentelemetry-proto/pull/72 maybe someone else is able to confirm if that is the case, I don't see a change to the spec itself to reflect that

It looks like we don't need this and can probably remove it altogether: https://github.com/open-telemetry/opentelemetry-proto/pull/107


Consider supporting Quarkus Dev UI in our extensions

Since Quarkus 1.11.0.Final, there is Quarkus Dev UI, see https://quarkus.io/guides/dev-ui
It allows to quickly visualise all the extensions currently loaded, see their status and go directly to their documentation.
The good news is that the docs links work for Camel Quarkus extensions.
On top of that, each extension can add:

Custom useful bits of runtime information in the overview
Full custom pages
Interactive pages with actions

I wonder which of the above should we support?
See also https://github.com/quarkusio/quarkus/issues/14471

To hide an extension from the Dev console, it should be enough to remove the docs link from the metadata. We should consider doing it for at least those support extensions which expose no Quarkus configuration.

There are 2 interesting ideas I have, but there are just ideas from a non frontend person, and I don't know if those are easy to tackle:

Looking at this kind of Dev UI developed recently : https://github.com/quarkusio/quarkus/issues/21059
Or go for a more common UI around Camel projects, and have a dedicated back-end for Quarkus Dev UI. As for Kogito's demo on Quarkus insights. This idea is kind of a way bigger project.

Camel 3.15 comes with API for developer console (camel-console JAR).
It is an early prototype that comes with a set of out of the box consoles to provide various information about your running Camel application. More consoles will be added.
These consoles currently are text based, but we need to spec the data in JSon so graphical consoles in camel-quarkus can use the data and display nicely.
It seems the website has not updated yet with camel 3.15 docs, but there are some early details here
https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-console.adoc

@davsclaus Nice. I'd try to give the camel-console a look when I have time.

I'm looking into this for a POC with camel-console, so I'm assigning myself. Let me know if you are working on this


cannot enabled resize

Hi, I'm using gridster with polymer.
When trying to enabled resize (with this.gridster.enabled_resize() ) an error occured
Uncaught TypeError: Cannot read property 'enable' of undefined
It seems that resize_api is not defined

It seems that, when creating the gridster element, the resize.enabled should be define at true

I can confirm this.
resize: {
    enabled: false,
},

Fails when using grid.enable_resize() and grid.disable_resize().
resize: {
    enabled: true,
},

Will work.
Currently, to work around it, simply do:
var grid = $("#container").gridster({
    resize: {
        enabled: true,
    },
});
grid.disable_resize();


Add api contracts for roadmap-site

The PR contains the API Contracts which are required for the RDS Roadmap-Site.

Can we just enclose the user object in 3 backticks for a better view? Can you please check this for some preview -https://media.discordapp.net/attachments/735598747949465640/771607280332046347/unknown.png?width=1026&height=295

Good one!


feat: use server inferenced types on statement describe

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Fixes #2017
Try to inference parameter types on postgres Describe command. And use these server types for parameter deserialization on extended query when client doesn't specified parameter types.
Upstream changes:
https://github.com/sunng87/pgwire/pull/106
Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

the types still seems have some error

  the types still seems have some error类型似乎仍然有一些错误

用
v0.4.0-nightly-20230814
没有问题了


RFC: Move mcugmr functionality as internal Zephyr service

The PR consists of two commits that:

copy mcumgr code into Zephyr source code tree;
remove mcumgr module from west.yml

Resolves: #36017

@de-nordic thank you for the PR.
I assume that this is a first step, to later then start modifying the source accordingly in order to get rid of the shim layers that are no longer required now that the code is in-tree. I would also suggest not having a lib/ folder in the end, but rather the code directly in subsys/mgmt/mcumgr/ with folders for transports and other logically independent parts.

@de-nordic thank you for the PR.
I assume that this is a first step, to later then start modifying the source accordingly in order to get rid of the shim layers that are no longer required now that the code is in-tree. I would also suggest not having a lib/ folder in the end, but rather the code directly in subsys/mgmt/mcumgr/ with folders for transports and other logically independent parts.

Yes. This is first step. I want to bring code as it is, of course with filled in missing licenses, compliance and style fixes here and there, so that it would past tests.
Then plan is to change structure of subsys/mgmg/mcumgr' into something like: commands, protocol, transports` and move files around; then specialize and reorganize the code to work efficiently with Zephry and so on.
I want to keep the thing moving and I have decided to make changes in steps;  as I have more priority task to complete and some of them collide, regarding the mcumgr changes, I need to structure work in a way that lets me keep the changes going in gradually while working on other items.

@rerickson1 and @lairdjm please review

@ahedin25

@lairdjm Can you ping me on discord so we could have brief talk on further plans for the mcumgr?


Update Operator CRDs to v1

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit e477ac0f203fc0245aaf248681bc4679afa7bd4c
https://deploy-preview-3660--calico.netlify.app


Sandbox contract calls responding with 400 errors

Describe the bug
Certain contract calls from the sandbox are failing with HTTP 400 errors starting after the instability this weekend.

If I call get-pox-info from ST000000000000000000002AMW42H.pox on testnet, the payload info is:
URL:
https://stacks-node-api.testnet.stacks.co/v2/contracts/call-read/ST000000000000000000002AMW42H/pox/get-pox-info

Payload:
{"sender":"ST113N3MMPZRMJJRZH6JTHA5CB7TBZH1EH4C22GFV","arguments":[]}

and the response is:
(ok (tuple (current-rejection-votes u0) (first-burnchain-block-height u2000000) (min-amount-ustx u5175407755455) (prepare-cycle-length u50) (rejection-fraction u12) (reward-cycle-id u398) (reward-cycle-length u1050) (total-liquid-supply-ustx u41403262043641960)))

If I call is-pox-active from ST000000000000000000002AMW42H.pox on testnet and pass a reward cycle, I receive the HTTP 400 error. The payload info is:
URL:
https://stacks-node-api.testnet.stacks.co/v2/contracts/call-read/ST000000000000000000002AMW42H/pox/is-pox-active

Payload:
{"sender":"ST113N3MMPZRMJJRZH6JTHA5CB7TBZH1EH4C22GFV","arguments":["0x1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,55"]}

and the response is:
Failed to load resource: the server responded with a status of 400 ()

If I call get-stacker-info from ST000000000000000000002AMW42H.pox on testnet and pass a principal, I receive the HTTP 400 error. The payload info is:
URL:
https://stacks-node-api.testnet.stacks.co/v2/contracts/call-read/ST000000000000000000002AMW42H/pox/get-stacker-info

Payload:
{"sender":"ST113N3MMPZRMJJRZH6JTHA5CB7TBZH1EH4C22GFV","arguments":["0x5,26,66,58,142,148,183,241,73,75,31,137,165,168,168,172,89,244,191,196,46,137"]}

To Reproduce
This was noticed initially with the CityCoins contracts, but seems to affect anything that passes the values above as payloads. Iirc these should be hex-encoded Clarity values but above looks like a raw Buffer or Uint8Array with the Clarity type as the first value.
Expected behavior
Contract calls from the sandbox return a response.
Screenshots

FYI - this was fixed after @He1DAr rolled back some changes, here are the differences in the contract call payload from the working version.
Calling is-pox-active from ST000000000000000000002AMW42H.pox with a uint:
{"sender":"ST113N3MMPZRMJJRZH6JTHA5CB7TBZH1EH4C22GFV","arguments":["0x010000000000000000000000000000018e"]}
Calling executed-at in ST355N8734E5PVX9538H2QGMFP38RE211D9E2B4X5.base-dao with a principal:
{"sender":"ST113N3MMPZRMJJRZH6JTHA5CB7TBZH1EH4C22GFV","arguments":["0x061aca5aa0e3238b6df5251a222bc28fb0d18708216a14636369703031322d626f6f7473747261702d7632"]}

@BLuEScioN let's keep this in mind for when we bring back postconditions


Add the release drafter

https://github.com/meilisearch/integration-guides/blob/main/guides/release-drafter.md
This would be helpful in managing the changelogs

I could add the release drafter without having a package manager I suppose?

Yes, it is only to make the draft of the GitHub release :) Nothing else

Should we start before there is a working version?

No, this is one of the final steps I think ;)


CPP test case fails to compile using gcc 4.8.5 when MKLDNN enabled

Description
When compiling the CPP test cases using GCC 4.8.5 with MKLDNN enabled, a compiling error will be raised as below:
tests/cpp/operator/mkldnn.cc:37:10: error: ‘align’ is not a member of ‘std’
ret2 = std::align(alignment, size, mem, space2);
This is because std::align requires GCC 5.0 or above, since the minimum requirement for MXNET is gcc 4.8, it is supposed std::align should be replaced.
Environment info (Required)
CentOS 7.2 64bit
Package used (Python/R/Scala/Julia):
Python
Build info (Required if built from source)
make -j($nproc) USE_MKLDNN=1 USE_BLAS=mkl test
Compiler (gcc/clang/mingw/visual studio):
GCC 4.8.5
MXNet commit hash:
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
Error Message:
Compiling error:
tests/cpp/operator/mkldnn.cc:37:10: error: ‘align’ is not a member of ‘std’
ret2 = std::align(alignment, size, mem, space2);
Steps to reproduce
(Paste the commands you ran that produced the error.)
make -j($nproc) USE_MKLDNN=1 USE_BLAS=mkl USE_OPENCV=1 test

@pengzhao-intel

@zheng-da

https://github.com/apache/incubator-mxnet/blob/926f2e231334c5a2832b3b79b31cb4e47dde2b1c/src/operator/nn/mkldnn/mkldnn_base.cc#L28
There is a standalone implementation for std::align and we can do a replacement for CPP test.
@juliusshufan do you have interested in submitting a PR?

This is a unit test to check the correctness of the custom alignment function.

@zheng-da @marcoabreu Do you mind to skip this test when GCC < 5.0? I cannot find a good approach to replace std::align here. Actually, mxnet::AlignMem in this test was designed to replace std::align and this test was set for comparing the functionality of mxnet::AlignMem and std::align. If we provide a new align function here, maybe it should be tested too.

I don't think this is possible. It's my mistake that I used the wrong GCC version on our CentOS builds and this went through, but in the end we're supposed to support that compiler and apparently there are customers using that version.

@marcoabreu Thanks for the information, I think per the description here, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57350, from GCC5.0, the std::align is supported, if my understanding is correct, the minimum requirement of of MXNET is gcc 4.8.
Specifically for this issue, the posix_memalign provided by stdlib might help to replace std::align, but this function is platform-dependent.
What do you think.

Puh that's a bit too much for me, I hope somebody else with a bit more experience in that field could help out here.

Where are the minimum requirements for compiler versions for MXNet builds listed?

They are listed at http://mxnet.incubator.apache.org/install/index.html if you press "Build from Source"

I think the version should be one that we are running on the ci. Maybe we can update the documentation on the website? Because it's effectively already 5.0 and clang is not even mentioned (we have ci builds with it AFAIK). Or maybe a question in the dev list?

I think we should rather run CI in accordance with our specifications - it was my mistake I used a wrong version. The problem is that customers using CentOS usually rely on older versions of applications and compilers, so I don't think we can drop support for GCC < 5.
@juliusshufan do I understand it right that GCC 4.8.5 is hard constraint for you?

@marcoabreu Thanks again for the follow-up.
For me, as I am running CentOS, and the default gcc with it is 4.8.5, it is a better OOB experience that MXNET can keep on supporting this version of the gcc, and I also agree with you that the necessity of supporting to GCC<5.
Thanks.

Okay, thank you for your confirmation. I have created a PR to ensure we're validating 4.8.* on CentOS. https://github.com/apache/incubator-mxnet/pull/10200

@juliusshufan apparently, our CI is able to compile MXNet using GCC 4.8.5 without any erros: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-10200/1/pipeline/48 Could you please try to find the difference between your and our approach?

@TaoLv I see. So std::align is only used as a verification method in our tests and nowhere in our actual codebase?

Yes. The compiling failure only occures in mkldnn cpp test case.

I see. Would you mind adding MKLDNN support to our CentOS 7 cpu environment?

@marcoabreu Hah, your PR #10200 has passed CI successfully! So I wonder what I can do now.

Our CentOS 7 environment is using OpenBLAS and not MKL. The best would probably be to change the configuration to MKLDNN and then fix all upcoming errors.

Sorry, I don't know much about changing CI environment. I will ping @pengzhao-intel and @xinyu-intel for help. They worked on mkldnn and clang environment before.

I agree with @TaoLv that we should disable this test for any compiler that doesn't support std::align. This is just a test. Any CI that uses higher-version compilers can test it.

I also agree, in this case we can make an exception since we're validating the results in other environments with a more recent compiler version.

@juliusshufan Please try the latest master branch to see if this issue is still there. Thanks @marcoabreu for merging #10218

I think this issue is cleared now. Thanks for all your effort. 👍


Fix simulated Quincy cost model hack.

The simulated Quincy cost model has a hack to allow direct mapping of tasks to racks, rather than via task equivalence classes.

Is this still current given the recent Quincy cost model overhaul?

Nope. It has been fixed.


[0.2.4] Low-level details in JSONDecodeError message by mistake?

Hi!
I'm happy to find that hyperjson rejects single surrogates as invalid characters but the exception text looks more low-level than expected. Is this a bug? Can the exception message be made more highlevel like "single surrogates not allowed"?
In [8]: hyperjson.__version__
Out[8]: '0.2.4'

In [9]: hyperjson.loads('"\\ud800"')
[..]
JSONDecodeError: Value: PyObject(0x7f481b3a1530), Error: PyErr { type: Py(0x7f48262225c0, PhantomData) }: line 1 column 1 (char 0)

Thanks and best, Sebastian

Apologies for never replying to your message. Even though my answer is too late, for all means and purposes, orjson is the better alternative nowadays.

@mre understood but with 6 other issues still open why close this issue if it's not fixed? This issue being open and unfixed for 3 years communicates well that the project is dead, far better than it being closed. Why close?

You have a point. I see two options:

Reopen
Close all issues and/or archive the project.

I'm gravitating towards the second option. Realistically, I won't get around to work on hyperjson anymore. Perhaps someone wants to step up, but even then the time would be spent more wisely to work on orjson or try a different approach altogether. Apart from that, it's mostly a learning resources to see how to work with pyo3/serde.
What do you think?

@mre my vote for re-opening the issue and then archiving the repo. It would unhide the bug and send a signal that is harder to miss than the not in the readme about project status. Would be a mix of 1 and 2. Just my 2 cents. What do you think?

Yes, I like that. 👍


Specifying examples for Query Parameters of a primitive type

Hi. Is there currently a way to specify examples for query params of a primitive type (int, string,...)? I can set param type to be a custom schema and specify examples there using Meta, but i'm not aware of a way to define schema of simple type string, i can only define objects. And also I don't see a way to set examples for query params directly in handler docstring. Is it possible?

Hi Michal,
I did this module for use in a project in my previous job, we weren't
particularly "fond" of examples.  I will plan out an update for this.
Thanks,
RNDuldulao,Jr.
On Fri, Apr 17, 2020 at 10:30 PM Michal Filippi<EMAIL_ADDRESS>wrote:

Hi. Is there currently a way to specify examples for query params of a
primitive type (int, string,...)? I can set param type to be a custom
schema and specify examples there using Meta, but i'm not aware of a way
to define schema of simple type string, i can only define objects. And
also I don't see a way to set examples for query params directly in handler
docstring. Is it possible?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rnduldulaojr/tornado-swirl/issues/40, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCEXQRX3KMAHQDSJKOVXH3RNBRYBANCNFSM4MKZKJAA
.

I totally understand. Some other tools like schemathesis can take an advantage of examples in spec to test API. This would be a wonderful feature to have.
I don't want to put any pressure on you, but do you have any rough time estimate? It would just help me plan my following steps.
Thanks a lot, Michal

Hi Michal,
I am starting to review the project again and also looking at OpenAPI
example spec to see how it can be integrated in the py doc.  Will update
you later re: estimate, I am working on some contracts now though so the
schedule might be a bit tight.
On Mon, Apr 20, 2020 at 4:29 PM Michal Filippi<EMAIL_ADDRESS>wrote:

I totally understand. Some other tools like schemathesis
https://github.com/kiwicom/schemathesis can take an advantage of
examples in spec to test API. This would be a wonderful feature to have.
I don't want to put any pressure on you, but do you have any rough time
estimate? It would just help me plan my following steps.
Thanks a lot, Michal
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rnduldulaojr/tornado-swirl/issues/40#issuecomment-616394092,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCEXQXN63YYVMM3PR7WYB3RNQBVJANCNFSM4MKZKJAA
.


New component for My Latest content

New component for My Latest content that is a table and will live on the dashboard. This component can really be used for all tabular data moving forward.

Resolves #538
DCO 1.1 Signed-off-by: NICK TILDEN<EMAIL_ADDRESS>

Had some challenges getting the data setup correctly for the time being. Maybe this is a moot point since we will be importing real data eventually.

As for the links problem, you can do something like the following in your template:
{% for row in data.rows %}

  {% for header in data.headers %}
  {% set r = row[loop.index] %}
  {% if r.url and r.title %}{{r.title}}{% else %}{{r}}{% endif %}
  {% endfor %}

{% endfor %}

This will check to see if the row is an object that contains the url and title keys and, if it does, prints out a link instead of printing out the static content

Here is what the final data model and HTML should look like. Please look it over and ask any questions (doing this instead of committing directly so you can see the content)
Data Model
'use strict';

/*
 * Sample Data for Styles Route
 *
 * @returns {object} - Object containing sample data to use when rendering samples in the Style Guide
 */

module.exports = {
  tableData: {
    name: 'My Latest',
    headers: [
      'content',
      'last edited',
      'actions',
      ' ',
    ],
    body: [
      [
        'Conversation API',
        'Tue Nov 15 2016 11:09:03 GMT+0000 (UTC)',
        'Edit Latest Revision',
        {
          url: '/drafts',
          title: 'Draft',
        },
      ],
      [
        'Conversation Overview',
        'Mon Nov 14 2016 03:22:12 GMT+0000 (UTC)',
        'Edit Latest Revision',
        'Draft',
      ],
      [
        'Python SDK',
        'Fri Nov 11 2016 12:12:01 GMT+0000 (UTC)',
        'Edit Latest Revision',
        'Draft',
      ],
      [
        'News Intelligence',
        'Wed Oct 26 2016 11:31:26 GMT+0000 (UTC)',
        'Edit Latest Revision',
        'Approved',
      ],
      [
        'Cognitive Head Hunter',
        'Wed Oct 26 2016 18:42:40 GMT+0000 (UTC)',
        'Edit Latest Revision',
        'Needs Approval',
      ],
    ],
  },
};

Nunjucks
{% macro table(data) %}

{{data.name}}

      {% for header in data.headers %}
      {{header}}
      {% endfor %}

    {% for rows in data.body %}

      {% for header in data.headers %}
      {% set row = rows[loop.index0] %}
      {% if row.url and row.title %}{{row.title}}{% else %}{{row}}{% endif %}
      {% endfor %}

    {% endfor %}

{% endmacro %}

The caption is going to need custom styling (for instance, by default it's center aligned, and there's probably some spacing we're going to want to add). We're also likely going to want to check to see if there's a name or not before adding a caption.

@Snugug - got everything to show up thanks to your recommendations. Still had some trouble/questions about the schema stuff.
Also, my build is failing, but I'm not sure why. Tests run fine locally.

@Snugug - I think we are good to go on this.


Automator: update common-files@master in istio/ztunnel@master

Generated by Automator - 2023-09-26T19:26:18+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
2d35d7e893d24de48b07ebe83bd3f01e44c0413a
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test test


Need support for OAuth 2 client credentials grant

Meetup announced by email on June 14, 2019,

API Keys will be replaced by OAuth: We will be removing API keys on August 15, 2019 and requiring you to authenticate with OAuth.

Backend and unattended applications cannot use either the server and implicit OAuth 2 protocol flows offered by Meetup because those flows require user interaction and a redirect URL. An example of an unattended application is Meetup2Xibo, which transfers Meetup events to an organization's Xibo digital signage system. Meetup2Xibo authenticates to Meetup with an API key, but authenticates to Xibo with OAuth 2 client credential grants.
The OAuth 2 protocol includes client credential grants for clients to provide an access token outside of the context of a user. Clients must securely store a client ID and a client secret issued by the server (Meetup or Xibo, for example). The client presents those credentials to obtain an access token. Client credential grants are the ideal replacement for API keys used by applications without users.

Yes, we need this very much- considering the fact that there are no good and officially maintained libraries with oauth 2 support