Graph Transformer: A Generalization of Transformers to Graphs.

Vijay Prakash Dwivedi. Graph Transformer: A Generalization of Transformers to Graphs.

Overview
This blog is based on the paper A Generalization of Transformer Networks to Graphs with Xavier Bresson at 2021 AAAI Workshop on Deep Learning on Graphs: Methods and Applications (DLG-AAAI’21).

We present Graph Transformer, a transformer neural network that can operate on arbitrary graphs.

Background
Lets start with the two keywords, Transformers and Graphs, for a background.
Transformers
Transformers [1] based neural networks are the most successful architectures for representation learning in Natural Language Processing (NLP)

overcoming the bottlenecks of Recurrent Neural Networks (RNNs) caused by sequential processing.

As the core building block of Transformers, there exists the multi-head attention mechanism, represented by this formula:

Fig: The feature update equation for the word $i$ using the multi-head attention mechanism. The symbols represent the usual meanings.
Using multi-head attention, a word attends to each other word in a sentence and combines the received information to generate its abstract feature representations.
Graphs
Graphs are ubiquitous data structures. There is a wide range of application domains where datasets can be represented as graphs. For example, molecular graphs in chemistry, interactions among particles in physics, drug protein interactions in medicine, user and their social and commercial connections in social media, problems in combinatorial optimization, etc.

Fig: Representative domains with graph-structured datasets. Link
For learning on graphs, graph neural networks (GNNs) have emerged as the most powerful tool in deep learning.
In short, GNNs consist of several parameterized layers, with each layer taking in a graph with node (and edge) features and builds abstract feature representations of nodes (and edges)

by taking the available explicit connectivity structure (i.e., graph structure) into account.

The so-generated features are then passed to downstream classification layers, usually MLPs, and the target property is predicted.

Objective
Now, the target is to generalize transformer neural networks to graphs so that it can learn on graphs and datasets

with arbitrary structure rather than just the sequential (as can be interpreted to be done by the NLP Transformers).

To proceed with the objective, we focus on extending the key design principles of Transformers from NLP to graphs in general.

Key Design Aspects for Graph Transformer
We find that attention using graph sparsity and positional encodings are two key design aspects for the generalization of transformers to arbitrary graphs.
Now, we discuss these from the contexts of both NLP and graphs to make the proposed extensions clear for Graph Transformers.
Graph Sparsity
In NLP, Transformers consider full attention while building feature representations for words. That is, a transformer treats a sentence as a fully connected graph of words. This choice of full attention can be justified for two reasons:
First, it is difficult to find meaningful sparse interactions or connections among the words in a sentence. For instance, the dependency of a word in a sentence on another word can vary with context, user’s perspective, and application at hand. There can be numerous plausible ground truth connections among words in a sentence and therefore, text datasets of sentences do not often have explicit word interactions available. It thereby makes sense to perform full attention and let the model decide how the words depend on others.
Second, the so-interpreted fully connected graph in NLP often has less than tens of hundreds of nodes (i.e., sentences are often less than tens or hundreds of words). On this size of graphs, attention to every node is computationally feasible in memory and time.

For these two reasons, full attention can be performed in NLP transformers and subsequent works [2,3,4] have shown it to be fruitful in language modeling and several NLP tasks.

Fig: Full attention v/s attention restricted to local neighborhood.
However, in the case of actual graph datasets, graphs have arbitrary connectivity structure available based on the application domain, and have node sizes in ranges of up to millions, or even billions. The available structure presents us with a rich source of information to exploit while learning in the neural network, whereas the node sizes practically makes it impossible to have a fully connected graph for such datasets.

On these accounts, it is practical (for feasibility) and advantageous (for utilizing sparse structure information) to have a Graph Transformer where a node attends to local node neighbors, similar to Graph Attention Networks (GATs)[5].

In fact, the local information aggregation is at the core of GNNs, indicative of the fact that sparsity is a good inductive bias for generalization.
Positional Encodings
The attention mechanism in Transformer is invariant to the ordering of the nodes. It does not have any notion of where in the sequence (or the sentence) the word is located. This means that, the Transformer regards a multi-set of words rather than the sequence of words in NLP, as illustrated by the following comparison:

Fig: For the multi-head attention mechanism, the input can be interpreted to be a multi-set of words.
That would mean losing out some information about the ordering of the words, isn’t it?
To avoid this and making Transformer aware of the sequential information, some kind of positional encoding is necessary in the transformer. The original transformer by Vaswani et al. [1] uses sinusoidal positional encoding that is added to each word’s feature vector at the inputs. This helps encode the necessary prevalent (sequential) relationship among the words into the model.
We extend this critical design block of positional information encoding for Graph Transformer. In fact, a line of research in GNNs [6,7,8] has recently shown that

positional information improves GNNs and overcomes the failure of GNNs for several fundamental tasks.

We, therefore, leverage the success of the recent works on positional information in GNNs and use Laplacian Positional Encodings [8] in Graph Transformer. We use precomputed Laplacian eigenvectors [9] to add to the node features before the first layer, similar to how positional encodings are added in the original Transformer [1].

Fig: Positional Encodings (PEs) in original Transformer v/s proposed Graph Transformer.

Laplacian PEs are a natural generalization of the sinusoidal PEs used in the original transformer, as the sinusoidal PEs can be interpreted as eigenvectors of the line graph, which is the sentence in NLP.

Hence, sparse graph structure during attention and positional encodings at the inputs are the two important things we consider while generalizing transformers to arbitrary graphs.

May James want to utilize the learned representation to approximate Laplacian PEs?

Proposed Graph Transformer Architecture
We now present the proposed architecture - the Graph Transformer Layer and the Graph Transformer Layer with edge features. The schematic diagram of a layer shown as follows consist of the major components:

the input with PEs,
the multi-head attention mechanism with attention restricted to local neighbors,
the feed forward module.

Compared to the standard transformer of Vaswani et al. [1], the key differences (or the extensions) which generalizes transformer to graphs to result in a Graph Transformer are:

The attention mechanism is a function of the neighborhood connectivity for each node (strict adjacency matrix mask), which is shown by the formula:

Positional Encoding is represented by Laplacian PEs. In particular, the eigenvectors of graph Laplacian are precomputed for every graph before training and the k-smallest non-trivial eigenvectors of a node are assigned as the node’s PE.
The feed forward module employs batch normalization [10] instead of layer normalization [11] that was used in the original transformer [1]. This is supported by our empirical evidences that the use of batch normalization leads to better performance in place of layer normalization.
Graph Transformer is extended to have edge representation (see the Graph Transformer Layer with edge features at right of the architecture diagram). This architecture can be critical to datasets with rich information along the edges, for instance - bond information along the edges in molecular graphs, or relationship types in knowledge graphs. There are two things to note in this edge-extended architecture: the edge features are fused to the corresponding pairwise implicit attention scores, and there is a designated edge feature pipeline at every layer, as shown by the layer update equations as follows:

This concludes the description of the proposed Graph Transformer. We refer to the paper for the complete layer update equations.

Remarks from the experiments
We evaluate Graph Transformer on benchmark datasets and validate our design choices, alongside an attempt to answer some open research questions on:

whether local attention or full attention for generalization of transformers to graphs,
how to encode sparse structure information?,
positional encoding candidates.

We remark the following results:

As already discussed, graph sparsity is critical and its use in attention mechanism always gives better performance as compared to use full attention. The result that sparsity is a good inductive bias for graph datasets has already been shown by the success of GNNs on several application areas.

Among several combination of design choices on attention, use of PEs, normalization candidate, etc., the architecture using

attention to local neighbors,
Laplacian PEs,
batch normalization layer in feed forward module,

has the best performance across all datasets used for evaluation. This empirically validates the choice of using these components for the targeted generalization of transformers.

Since Laplacian PEs have desirable properties of having

distance-aware information,
distinguishable node features,
being a generalization of original transformer’s PE’s to general graphs,

it fares as a suitable PE candidate to be used as Graph Transformer, even empirically, as compared to the PE candidates used in the literature for research on Graph Transformer (the related works are discussed in detail in the paper).

Overall, Graph Transformer achieves competitive performance among the GNNs compared with on the evaluated datasets. The proposed architecture performs significantly better than baseline GNNs (GCNs [12] and GATs [5]), and helps close the gap between the original transformer and transformer for graphs. Thus, Graph Transformer emerges as a fresh powerful attention based GNN baseline and we hope can easily be extended for future research, provided its simplicity and straightforward generalization from transformers.

Code
The tables of the numerical experiments are in the paper, the code implementation is open-sourced on GitHub, and an accompanying video presentation is on YouTube, with the corresponding links as follows:
Paper: https://arxiv.org/abs/2012.09699
GitHub: https://github.com/graphdeeplearning/graphtransformer
Video: https://youtu.be/h-_HNeBmaaU?t=240

Reference

Vaswani, A., Shazeer, N., Parmar, N., Uszkoreit, J., Jones, L., Gomez, A.N., Kaiser, Ł. and Polosukhin, I. (2017). Attention is all you need.
Devlin, J., Chang, M.W., Lee, K. and Toutanova, K., (2018). Bert: Pre-training of deep bidirectional transformers for language understanding.
Radford, A., Narasimhan, K., Salimans, T. and Sutskever, I., (2018). Improving language understanding by generative pre-training.
Brown, T.B., Mann, B., Ryder, N., Subbiah, M., Kaplan, J., Dhariwal, P., Neelakantan, A., Shyam, P., Sastry, G., Askell, A. and Agarwal, S., (2020). Language models are few-shot learners.
Veličković, P., Cucurull, G., Casanova, A., Romero, A., Lio, P. and Bengio, Y. (2018). Graph attention networks.
Srinivasan, B. and Ribeiro, B., (2019). On the equivalence between positional node embeddings and structural graph representations.
You, J., Ying, R. and Leskovec, J., (2019). Position-aware graph neural networks.
Dwivedi, V. P., Joshi, C. K., Laurent, T., Bengio, Y., and Bresson, X. (2020). Benchmarking graph neural networks.
Belkin, M. and Niyogi, P. (2003). Laplacian eigenmaps for dimensionality reduction and data representation.
Ioffe, S. and Szegedy, C., (2015). Batch normalization: Accelerating deep network training by reducing internal covariate shift.
Ba, J.L., Kiros, J.R. and Hinton, G.E., (2016). Layer normalization.
Kipf, T. N., and Welling, M. (2016). Semi-supervised classification with graph convolutional networks.


iac gcp update

Summary
Updating CLI iac-generate command to match terraform-gcp-audit-log variables
Advanced filters option:

How did you test this change?
Unit and integration testing
Issue
ALLY-923

See now that some of these variables are present in gcp-config TF module.


Key 'latest_receipt_info' missing in receipt data from App Store

The key 'latest_receipt_info' is missing in receipt data from App Store. As specified here:
https://developer.apple.com/library/ios/releasenotes/General/ValidateAppStoreReceipt/Chapters/ValidateRemotely.html.
The other keys, like "receipt" and "status" etc seems to be included.
Is there any specific reason to leave 'latest_receipt_info' out?
This is needed to be able to get in-app subscriptions validated.

Hi @Niklas9, the documentation states for both latest_receipt and latest_receipt_info

Only returned for iOS 6 style transaction receipts for auto-renewable subscriptions

As iOS 7 is available since 2013 together with the new receipt style, I never thought of supporting these deprecated fields.
I think you can get the same information about subscriptions from the receipt data. This object contains a in_app field which is documented to hold all auto-renewable subscription indefinitely:

The in-app purchase receipt for a consumable product or non-renewing subscription is added to the receipt when the purchase is made. It is kept in the receipt until your app finishes that transaction. After that point, it is removed from the receipt the next time the receipt is updated—for example, when the user makes another purchase or if your app explicitly refreshes the receipt.
The in-app purchase receipt for a non-consumable product, auto-renewable subscription, or free subscription remains in the receipt indefinitely.

https://developer.apple.com/library/ios/releasenotes/General/ValidateAppStoreReceipt/Chapters/ReceiptFields.html#//apple_ref/doc/uid/TP40010573-CH106-SW1
Do you have a use case which really requires these fields? We can think about supporting at least the latest_receipt_info field (if available).

The Apple documentation is outdated in this regard, unfortunately. It has caused me lots of confusion lately as well :)
A subscription, only gets into the "receipt" for the first purchase (signing up for subscriptions).. then the continuous receipts for the recurring period gets added into the latest_receipt_info array.
I can PM you examples if you want.

Thanks for addressing the issues I'm posting so fast and gently btw.. I hope I'll be able to contribute back to the project in code as well soon :)

This is definitely good to know, as I didn't worked with subscriptions yet. I'll happily accept PRs for this issue or perhaps I'll find some time for this to implement. (In this case examples would be great)
This should be straight forward as the actual "interpretation" of the results from Apple's servers isn't included into the gem. (At the end the gem helps to communicate with the servers, but you have to "check" for the correct content of the receipt in the application logic). So for me it would be OK to just parse the JSON result into objects and provide it together with the Receipt.
Sadly I'm out of time in the next two weeks, but will definitely return to this issue later.

Hey @jnbt, just thought I'd let you know that I'm working on subscription support, such as getting the latest expiration date and seeing if the subscription is part of a trial period. I'll send you a PR soon.

Sounds great!

Work is done in #6

I'm currently very short in time. As @klaseskilson already developed the subscription support you can use this gem directly from GitHub if you need the feature:
In Gemfile:
gem 'candy_check', git: 'https://github.com/jnbt/candy_check.git'

{
environment = Sandbox;
"latest_receipt" = "MIJSeQYJKoZIhvcNAQcCoIJSajCCUmYCAQExCzAJBgUrDgMCGgUAMIJCGgYJKoZIhvcNAQcBoIJCCwSCQgcxgkIDMAoCAQgCAQEEAhYAMAoCARQCAQEEAgwAMAsCAQECAQEEAwIBADALAgEDAgEBBAMMATMwCwIBCwIBAQQDAgEAMAsCAQ4CAQEEAwIBWjALAgEPAgEBBAMCAQAwCwIBEAIBAQQDAgEAMAsCARkCAQEEAwIBAzAMAgEKAgEBBAQWAjQrMA0CAQ0CAQEEBQIDAYaiMA0CARMCAQEEBQwDMS4wMA4CAQkCAQEEBgIEUDI0NzAYAgEEAgECBBDwvjVsCFLuYGsSBs0s0myTMBsCAQACAQEEEwwRUHJvZHVjdGlvblNhbmRib3gwHAIBBQIBAQQU2ein5dvem18hdmiA0PMz7f7ehj4wHgIBDAIBAQQWFhQyMDE2LTEwLTIxVDA3OjAyOjQxWjAeAgESAgEBBBYWFDIwMTMtMDgtMDFUMDc6MDA6MDBaMCACAQICAQEEGAwWY29tLnRpY2tldHl0YXAucGljbmFkbzBCAgEGAgEBBDrEblyI7tr8QK8g+cjfppGm0XU2lebiS5cDtEIyVPnFg2D6lMgJA/9DvhIHO1i+21wXg1rT3kUPoFcJMEMCAQcCAQEEO5Y4BAs3xeZ9OdFccV/JE3mi4X6mu8ZxzDYIuTjEBH80YV5uYluzuoJb/xevz5yaV6e8h7sxkvMbTgCqMIIBfQIBEQIBAQSCAXMxggFvMAsCAgatAgEBBAIMADALAgIGsAIBAQQCFgAwCwICBrICAQEEAgwAMAsCAgazAgEBBAIMADALAgIGtAIBAQQCDAAwCwICBrUCAQEEAgwAMAsCAga2AgEBBAIMADAMAgIGpQIBAQQDAgEBMAwCAgarAgEBBAMCAQMwDAICBq4CAQEEAwIBADAMAgIGsQIBAQQDAgEAMB
}
I got this response, not getting any other information. help me.

@anilappvolution I'm willing to help here, but please open a new issue for your problem. Also some steps to reproduce your problem would be great.


Incorrect Implementation of addControlBits()

addControlBits does not work and needs to be reimplemented.

corrected in 0.2.0


Trino Gateway unable to connect to trino cluster with self signed certificate

Hi,
I am running a Trino cluster in k8s. It has a self signed certificate, whenever I am adding a backend I am getting below error. Please point me to correct direction for a fix.
curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

If I am trying to curl my Trino cluster from Trino gateway pod
curl https://mytrino.com/v1/info fails
but
curl -k https://mytrino.com/v1/info 200 ok
Is there way to control curl -k via config.
Thanks
Any help is appreciated

@Nexengineer One option I can think of is by adding the self-signed certificate CA to default Java keystore(JAVA_HOME/jre/lib/security/cacerts) or system truststore in the pod.

@avinashdesireddy I was able to resolve it using creating a custom image details are attached below
FROM trinodb/trine-gateway:8

RUN mkdir -p /etc/pki/ca-trust/extracted/pem/ && \
    mkdir -p /etc/pki/ca-trust/extracted/openssl/

USER root

RUN mkdir -p /tmp/certs
WORKDIR /tmp/app
COPY ca.pem /tmp/app/ca.pem

# For health using curl
RUN cat /tmp/app/ca.pem >> /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
RUN cat /tmp/app/ca.pem >> /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt

# For calling actual enviroment
COPY ca.cer $JAVA_HOME/lib/security
RUN \
    cd $JAVA_HOME/lib/security \
    && keytool -keystore cacerts -storepass changeit -noprompt -trustcacerts -importcert -alias ldapcert -file ca.cer

Is there a better way?


change package name to respect npm naming conventions

NPM does not allow uppercase letters in package names, so I changed it to all lowercase in order to be able to publish it there.

Can't be automatically merged, but I'll change this in the next version (pretty odd restriction though...)

Cool, thanks a bunch!
Yeah, it is pretty odd. Uppercase letters were allowed in the beginning and got banned eventually. Don't really understand why, but that's the current state.
I'll keep an eye on your repo and publish to npm with the next release :-)

Nice, good job on adding the plugin to NPM :+1:
Is it possible to add a reference to this in the documents? I'd do a pull request for it, but I don't have access to your website's content :wink:


OrderByDescending(...).First() returns random for a not mapped property

For an unmapped property:
        public DateTime TimeStampInternal { get; set; }

        [NotMapped]
        public Instant TimeStamp
        {
            get { return TimeStampInternal.AsUtc().ToInstant(); }
            set { TimeStampInternal = value.ToDateTimeUtc(); }
        }

This code returns a random value
var latestSnapshot = _context
                .TagsSnapshots
                .Include(snapshot => snapshot.Tags)
                .Where(snapshot => snapshot.SiteId == siteId)
                .OrderByDescending(snapshot => snapshot.TimeStamp)
                .FirstOrDefault();

This one however works fine
var latestSnapshot = _context
                .TagsSnapshots
                .Include(snapshot => snapshot.Tags)
                .Where(snapshot => snapshot.SiteId == siteId)
                .OrderByDescending(snapshot => snapshot.TimeStamp)
                .ToList()
                .FirstOrDefault();

The same with First, FirstAsync, FirstOrDefaultAsync

Thanks for reporting.

I think this is an issue with FirstOrDefault being translated to SQL even though the ordering is client-eval.

@anpete That's also my guess.

If you want to send a PR, the issue is likely around this line:
https://github.com/aspnet/EntityFramework/blob/dev/src/EntityFramework.Relational/Query/Internal/RelationalResultOperatorHandler.cs#L141

Currently I'm totally out of time. :(

No problem :smile:

I'll try to fix it

Is it fixed in this commit? https://github.com/aspnet/EntityFramework/blob/5fd6b00457b8b005cdedb6200de8c7989113221e/src/EntityFramework.Relational/Query/Internal/RelationalResultOperatorHandler.cs#L138

Fixed


VS Code' Explorer menu item is not added

Installing VS Code using Winget does not add the menu item "open file in VS Code" to Explorer while it is added by default using the standalone installer.
As it is a very convenient feature, and other software like 7-Zip are added to the menu, it would be great to have this menu item added.

By default only PATH is checked so silent installer does in fact work correctly.

You can override this behavior by passing in additional parameters

winget install Microsoft.VisualStudioCode -e --override "/verysilent /suppressmsgboxes /tasks=!runCode,desktopicon,quicklaunchicon,addcontextmenufiles,addcontextmenufolders,associatewithfiles,addtopath"

Prepending tasks with ! disables them.

This is exactly what I am looking for; it works like a charm.
However, I think without any explanation, most users would miss this option. I don't even know how to get this list of tasks.

Tradeoff for silent install, not much that can be done unless VS Code team decides these default values should be changed. Tasks can be found in VS Code setup manifest. https://github.com/microsoft/vscode/blob/aa98d29af94188825cbe2cf32864f1f33dc90b6e/build/win32/code.iss#L75-L82


Merge dmca changes into master

Creating a new branch because we need to move some of these changes to lbry-redux

@seanyesmunt can we push this to get it into the RC?


Create Documentation “api-integration”

Automatically generated by Netlify CMS

👷 Deploy Preview for elastic-yonath-a8509d processing.
🔨 Explore the source changes: 33c768ca94de9ba9e5e95a53e04cd2faa19e7b95
🔍 Inspect the deploy log: https://app.netlify.com/sites/elastic-yonath-a8509d/deploys/618b49b35f0d5d000791b21d


[Core] Feat: update config CVar in tool.invoke

ooc what's the issue

tools don't get the configurable values passed in


JUL logging is messy

I went with JUL logging so as to avoid any external libraries. Unfortunately trying to check whether Level.FINEST is set doesn't seem to work for the way that I am programmatically setting the logging in the unit tests. At the moment the logging is doing things like print(bytes) that is generating a lot of strings that are ignored if logging is disabled.
The workaround might be to (a) set logging via a properties file in the unit tests so that checking the log level works, or (b) check that asserts are enabled before doing fine logging. That isn't ideal as it makes logging a 'debug only' activity but realistically that is the scenario where the finest logging is actually used which is when we have a repeatable failing unit test.

removing the performance matter as it is now using the tactical "(b) check that asserts are enabled before doing fine logging" but it is still messy.

Phew! JUL supports using a lamba for the message that is lazily invoked. I will do that.

fixed on master


"Valea Mare" is listed in the drop-down menu

Description:
"Valea Mare" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Valea Mare" in the search bar.

Expected results
The location is listed in the drop-down menu as "Valea Mare, Alba (Ceru-Băcăinți)".


ImportError: cannot import name 'create_nested_mesh' from 'SimPEG.utils.drivers'

Run SimPEG DC&IP 3D Inversion or another data inversion as Online Documentation,with error bellow:
Traceback (most recent call last):
File "d:\ProgramData\Anaconda3\envs\geoapps\lib\runpy.py", line 188, in _run_module_as_main
mod_name, mod_spec, code = get_module_details(mod_name, Error)
File "d:\ProgramData\Anaconda3\envs\geoapps\lib\runpy.py", line 111, in get_module_details
import(pkg_name)
File "d:\geoapps-develop\geoapps\drivers_init.py", line 8, in
from . import components
File "d:\geoapps-develop\geoapps\drivers\components_init.py", line 8, in
from .data import InversionData
File "d:\geoapps-develop\geoapps\drivers\components\data.py", line 25, in
from SimPEG.utils.drivers import create_nested_mesh
ImportError: cannot import name 'create_nested_mesh' from 'SimPEG.utils.drivers' (d:\ProgramData\Anaconda3\envs\geoapps\lib\site-packages\SimPEG\utils\drivers_init.py)
How can I fix it?

Hi @geophylika,
This sounds like an installation issue with simpeg.
Try the following:
1- Open an anaconda terminal.
2- Run: conda activate geoapps
3- Run: pip install<EMAIL_ADDRESS>4- Re-start the apps and run again.
Let us know how this goes.

@geophylika
Can we close this?


The dialog's white edge

Hi,
When I use the Dialog to show with a Custom View, but the dialog allow has a white edge, I had set the background which is not white.

I have fixed it. You can try <IP_ADDRESS>-SNAPSHOT version.


Generate Ward nights from CSV data

@diaholliday Is leading a project to compile all of the ward night schedules into a spreadsheet. We can read this in and generate events using that schedule for all of the wards.

Yes! here's the link to that spreadsheet. We currently have Documenters
calling every alderman's office so it's not complete but it will be by
Sept. 8 at the latest:
https://docs.google.com/spreadsheets/d/1xnt4kZI9Ruinw91wM-nnWftsFD-ZaKaozepdNXeIrpo/edit
On Tue, Aug 29, 2017 at 5:59 PM, Jim Benton<EMAIL_ADDRESS>wrote:

@diaholliday https://github.com/diaholliday Is leading a project to
compile all of the ward night schedules into a spreadsheet. We can read
this in and generate events using that schedule for all of the wards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/City-Bureau/documenters-aggregator/issues/83, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD1NKnKjleOjneLbABCQrDwtsHaUb_g_ks5sdJe3gaJpZM4PGqCS
.

--
773-819-5188
Diaholliday.com http://diaholliday.com/
https://twitter.com/d_holli https://www.facebook.com/dIa.holliday
https://instagram.com/dia_holliday/

Closing in favor of #120.


fix:loader-module-webpack

Description
Fixes (issue #2807)
This PR addresses an issue with the webpack loader in @shopify/web-worker where output.chunkFilename could be either a string or a function returning a string.
The loader previously assumed it was always a string, leading to TypeError: file.includes is not a function errors.
The solution now checks if output.chunkFilename is a function and handles it correctly.
Changes Made

Default Values: Default values [worker].js are provided for compiler.options.output.filename and compiler.options.output.chunkFilename in case they are undefined.
Type Handling in addWorkerSubExtension:
If file is a string, the function directly performs the replacement to add the .worker suffix.
If file is a function, the function wraps it in another function that performs the replacement on its return value.

Can we merge?  @craigbrunner

Done, also added a check to avoid this from happening @jesstelford


how is the Server worker working on http request, Can you please elaborate

Could you please give me more details on on which command you're running to start the server?

@perinikhil
npm run development : is the command over which server is getting started

'npm run eevelopment' builds and runs the server on 'localhost', and since localhost is considered a secure server by service workers, they execute even though it's on http protocol :)

https://www.chromium.org/blink/serviceworker/service-worker-faq
Read the answer to the third question "Q: I get an error message about "Only secure origins are allowed". Why?" which clearly says so 😃


HB performs an unnecessary copying of extracted sourceballs

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

I've noticed that when installing a formula, HB is extracting the source tarball to Dir1, and then for some reason is copying Dir1/* into Dir2.  This seems totally unnecessary and doesn't match how HB used to behave.
Here's what it looks like now (with HOMEBREW_VERBOSE set).  You can see that there is what appears to be a totally unnecessary copying:
==> Verifying ed7152de7b320534c4128639c05fdc149fe4db285abb8f62f8b89d6d21f631bc--blueutil-2.2.0.tar.xz checksum
tar xf /stuff/brache/downloads/ed7152de7b320534c4128639c05fdc149fe4db285abb8f62f8b89d6d21f631bc--blueutil-2.2.0.tar.xz -C /Users/chdiza/.tmp/tmpdir/d20181019-31151-4xjgj3
cp -pR /Users/chdiza/.tmp/tmpdir/d20181019-31151-4xjgj3/blueutil-2.2.0/. /Users/chdiza/.tmp/tmpdir/blueutil-20181019-31151-gjhv3j/blueutil-2.2.0

Why is it copying the unpacked contents from one temp dir to another, instead of either (a) moving them, or (b) just extracting them directly to the desired tmpdir in the first place?  HB used to not do this.  Here's what it used to look like:
==> Verifying blueutil-2.2.0.tar.xz checksum
tar xf /stuff/brache/blueutil-2.2.0.tar.xz -C /Users/chdiza/.tmp/tmpdir/blueutil-20181019-30795-1vujpyc

Copying them makes the build take longer (particularly for large source dirs, and particularly for sequences of many builds in a row like when I fresh-install all my packages from a script), and also is putting needless writes on my SSD.
Backtracking through the commit history, I've found that 556e76b037dcc65ea6 is the first commit to show the extra copy step in my local testing.
Doctor: Only the warning about HOMEBREW_VERBOSE, but it needs to be set in order to display the bug.
Config:
HOMEBREW_VERSION: 1.7.7-82-g4a0e97d
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4a0e97d85a28921b3abe90c8a96094c58576136f
Last commit: 3 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 11df5159a651449eec40150aa8d80f5e69e166a1
Core tap last commit: 87 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/hb
HOMEBREW_CACHE: /stuff/brache
HOMEBREW_TEMP: /Users/chdiza/.tmp/tmpdir
HOMEBREW_BUILD_FROM_SOURCE: 1
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_LOGS: /Users/chdiza/Library/Homebrew
HOMEBREW_NO_ANALYTICS: 1
HOMEBREW_NO_AUTO_UPDATE: 1
HOMEBREW_NO_EMOJI: 1
HOMEBREW_NO_GITHUB_API: 1
HOMEBREW_VERBOSE: 1
CPU: quad-core 64-bit ivybridge
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1000
Git: 2.19.1 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1535735448
Xcode: 10.0

We don't know if the tar step will be the last one, since there could be a nested archive inside it. We run cp -R as the last step since this works with all archive types. Sadly there is no such thing as mv -R.

since this works with all archive types

Since we know the archive type (otherwise we don't know how to unarchive it), can't we: copy only if needed and move otherwise?

since there could be a nested archive inside it

But if there isn't, then HB should not be wastefully copying.  Outside of cask, I'm not sure when this would ever happen anyway (except for the trivial case of .tar.[compression-suffix]).


Adopt plznavigate in puppeteer

Recentrly, plznavigate was enabled on Chromium Trunk.
plznavigate changed protocol behavior in a few subtle ways that we relied upon in pptr
plznavigate causes a protocol bug that blocks our adoption

crbug.com/767683

For the reference: a wip of pptr migration over to plznvigate: aslushnikov/puppeteer:plznavigate
The plan is to roll with --disable-browser-side-navigation flag passed over to launcher and
remove it as soon as the upstream is fixed.

Two blocking upstream bugs:

crbug.com/759388
crbug.com/767683


Flatpaks not working with KDE Discover

Describe the bug
I added discover and flatpak to the config after installing installing v24.05. Packages were initially showing up in Discover but it stopped working all of as sudden.
Steps To Reproduce
Steps to reproduce the behaviour:

I added to kdePackages.discover and flatpak to environment.systemPackages = with pkgs within configuration.nix.
Used sudo nixos-rebuild and rebooted my PC.
Opened Discover and pressed add flathub.
Browsed the available flatpaks and closed the app.
I reopened Discover and was greeted by an "NixOS is not configured for installing apps through Discover"
I opened Discover settings to install my prefer module as directed but it's blank.

Expected behaviour
When doing this on v23 it worked with no issue. The apps would install and run fine.
Screenshots

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.33, NixOS, 24.05 (Uakari), 24.05.1409.cc54fb41d137`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

I added to kdePackages.discover and flatpak to environment.systemPackages = with pkgs within configuration.nix

What happens if instead you enable flatpaks with:
services.flatpak.enable = true;

in your configuration.nix?

https://github.com/KDE/discover/blob/6254dd2e71c6ee847817ca05eedc5801f837548a/discover/DiscoverObject.cpp#L180-L182 indicates there's no discover backend available, which means you need to  make one available. Most likely this should be sorted by the instructions above.

This worked thanks.


merge from arlac77/npm-package-template

.travis.yml

chore(travis): add node versions -10,-11,-12,12.9.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bbf5f7f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #567   +/-   ##
=========================================
  Coverage          ?   95.81%
=========================================
  Files             ?        6
  Lines             ?      478
  Branches          ?       65
=========================================
  Hits              ?      458
  Misses            ?       20
  Partials          ?        0

Continue to review full report at Codecov.

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


[ci skip] adding user @ljoakim

Hi! This is the friendly automated conda-forge-webservice.
I've added user @ljoakim as instructed in #7.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #7

I'm happy to be maintainer!


Added new xml property to add possibility to set animator for current indicator

Added new xml property to add possibility to set animator for current indicator

Sorry, I forget this pull request.
I found current animator was not perfect on previous indicator.


Create CorrelationFilter Rule on ServiceBus Topic Subscription

This is autogenerated. Please review and update as needed.
Describe the bug
Trying to create a correlation filter rule (Label = xxx) on a topic subscription. The same was successfully created in C# using the SubscriptionClient.AddRuleAsync:
            _subscriptionClient.AddRuleAsync(new RuleDescription()             {                 Name = "Rule1",                 Filter = new CorrelationFilter { Label = "test" }             }).GetAwaiter().GetResult();
Command Name
az servicebus topic subscription rule create
Errors:
BadRequest - Value cannot be null.

Parameter name: sqlExpression CorrelationId: a9cf8052-c375-4235-aba4-3a153f9aaf33

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az servicebus topic subscription rule create --name {} --namespace-name {} --subscription-name {} --topic-name {} --resource-group {} --subscription {} --enable-action-preprocessing false --enable-correlation-preprocessing true --enable-sql-preprocessing false --label {}

Expected Behavior
Create a correlation filter rule, with a label filter.
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6

azure-cli 2.1.0

Extensions:
application-insights 0.1.3
interactive 0.4.3
storage-preview 0.2.10

Additional Context
Is this a bug or am I missing something in the az servicebus topic subscription rule create command?
Also tries specifying --filter-sql-expression but this creates a SqlFilter type rule.

service bus

Hi , any update on the fix for this bug?

@v-Ajnava , could you please take a look at this one?

Duplicate of https://github.com/Azure/azure-cli/issues/11389.

For some reason, it seems that the --filter-sql-expression parameter is required, even though it is marked as optional in the docs.
Whether this is by design in Azure or a mistake in Azure CLI, I don't know.
As a workaround, try adding this parameter to your command:
--filter-sql-expression 1=1

For example:
az servicebus topic subscription rule create --resource-group myresourcegroup --namespace-name mynamespace --topic-name mytopic --subscription-name mysubscription --name myrule --filter-sql-expression 1=1

Here's the test for this command:
https://github.com/Azure/azure-cli/blob/8adf97355a605d147afc26f6c1b6f6afb6651c2f/src/azure-cli/azure/cli/command_modules/servicebus/tests/latest/test_servicebus_commands.py#L376-L379
There's no test for running the command without the --filter-sql-expression parameter, which it sets to test=test
Here's the recorded request and response generated by the test:
https://github.com/Azure/azure-cli/blob/6185cbbf0136ffb1ec12de3efdcc3136ec3c2235/src/azure-cli/azure/cli/command_modules/servicebus/tests/latest/recordings/test_sb_rules.yaml#L539-L599

Internal Tracking
devdivcsef 359125

Are there any workarounds or do we just have to wait for a fix?

Are there any workarounds or do we just have to wait for a fix?

Still no fix? That is really annoying

is this issue still not fixed? has anyone found a workaround? :(

service bus team should look into this

I'm experiencing the same issue. I know the workaround is there using C# and REST, but this is not ideal for a company that it's using your services and expects manage infrastructure with AZ CLI the same one that it's promoted if you are an IT professional. Also, what is the point to study and pass certifications exams when in real life things you expected to work are actually broken.
This affects the credibility of all IT professionals.
When can we wait for a fix on this? Please increase priority.

Can you please allow us to create correlation filters through the CLI? Not much use encouraging correlation filters over sql expressions but then not giving us useful ways to implement it.

Hi Team,
Sincere apologies for the delay in response here.
We will triage internally and get back to you with an update soon.

Can we get an update please. This is a fairly critical issue considering how important correlation rules are for any kind of meaningful, performant, advanced routing in Azure ServiceBus via the az cli. This has been an issue for over 2 years now.

Hi Team,
Thanks for your patience here. Our dev team has been working on coming up with a fix ( as I type this comment). With everything in place, I am positive that we should be able to roll out a fix for this one by this month's end ( rough estimate).
I would circle back with update soon.

Hi Team,
I am here to share some good news!
We could fix this issue in the latest release (https://docs.microsoft.com/en-us/cli/azure/release-notes-azure-cli?view=azure-cli-latest#service-bus). Please try the rule creation at your side and let us know in case you observe any other discrepancies. Thanks

Hi, thanks for getting back to us about the update. I've just tested this and I can finally confirm that this is now working. Here is the syntax I'm using:
az servicebus topic subscription rule create -g rgtest --namespace-name sbtest --topic-name mytopicname --subscription-name mysubname -n mycorrelationfilterrulename --filter-type CorrelationFilter --label=mycorrelationfilterstring

This is working as expected using the syntax by DanoThom.
@DanoThom thank you.


trust-ncg in ScipyMinimize argument issue

Hi! I've been trying to use the scipy wrapper for the trust-ncg method. When I do this, I'm prompted to pass the hessian vector product as an argument. The source code for the _run method is as follows (from the documentation):
res = osp.optimize.minimize(scipy_fun, jnp_to_onp(init_params, self.dtype),                                 jac=True,                                 bounds=bounds,                                 method=self.method,                                 options=self.options)
Which doesn't allow the hess argument to be passed to scipy. indeed when I pass the hess argument inside options I get an exception telling me scipy has received hess twice and when I don't pass it the resulting exception tells me that I haven't specified the hessian.

Thanks for the bug report. When trust-ncg is used, we should provide the Hessian vector product automatically for the user.
CC @fllinares

Just adding that I hit this bug as well. Couldn't figure out a way to pass the hessian.


02Tools - AutoML Logging

Hi @statmike, I am creating this pull request for new notebook 02Tools - AutoML Logging. Appreciate your help in reviewing this pull request.

Awesome First Draft!!! I look forward to integrating this into the 02 folders notebooks next update pass!


Unable to establish WebSocket connection with Firebase C++ SDK

[REQUIRED] Please fill in the following fields:

Pre-built SDK from the website or open-source from this repo: Open-source from this repo
Firebase C++ SDK version: 10.7.0
Main Firebase Components in concern: Auth
Other Firebase Components in use: Database
Platform you are using the C++ SDK on: Linux
Platform you are targeting: Desktop

[REQUIRED] Please describe the question here:
Expected behavior:
I expect to be able to establish a WebSocket connection using the Firebase C++ SDK and receive real-time updates of the database.
Actual behavior:
The WebSocket connection fails to establish using the Firebase C++ SDK, but a simple WebSocket client I wrote could build a secure connection (wss) to a public websocket server on the same device. The Firebase Realtime Database REST API connection works without any issues.
Description:
I am experiencing an issue with the Firebase C++ SDK, where I am unable to establish a WebSocket connection to the Firebase Realtime Database server. Here is the log message:
DEBUG: [conn_1170] websocket error occurred.  Uri: wss://....firebaseio.com/.ws?ns=...&v=5
DEBUG: Error occurred while establishing connection to wss://....firebaseio.com/.ws?ns=...&v=5
DEBUG: [conn_1170] Closing connection. Reason: 4
DEBUG: [pc_0] Got on disconnect due to 4

However, when I tested the connection using a simple WebSocket client I wrote on the same device, it was able to connect successfully. So it might not be a router's firewall setting issue.
I also tested the connection using the Firebase Realtime Database REST API with the same credential by doing
$ curl "https://....firebaseio.com/.../msg.json?auth=$(cat token)"
<response message>

and it worked without any issues. This suggests that the issue is specific to the WebSocket functionality of the Firebase C++ SDK.
I have checked my code for any errors or issues and ensured that I am using the correct credentials and endpoint URLs. I am using the latest version of the Firebase C++ SDK, and have followed the documentation provided by Firebase.

HI, thanks for reporting this issue.
Could you provide sample code for how you are using the C++ SDK to initialize firebase and interact with the database?

HI, thanks for reporting this issue.
To help us reproduce and understand the issue, could you provide sample code for how you are using the C++ SDK to initialize firebase and interact with the database?

Hi Matt,
Thanks for your reply. In the beginning, I create an App object by doing
m_options.set_api_key(m_api_key.c_str());
m_options.set_project_id(m_project_id.c_str());
m_options.set_database_url(m_database_url.c_str());
m_options.set_app_id(m_app_id.c_str());

m_app = firebase::App::Create(m_options, m_namespace.c_str());

Then I use the initializer to initialize Auth and Database by doing
firebase::ModuleInitializer initializer;
void* initialize_targets[] = {&m_database, &m_auth};

const firebase::ModuleInitializer::InitializerFn initializers[] = {
      [](::firebase::App* app_inner, void* data) {
        void** targets = static_cast<void**>(data);
        ::firebase::InitResult result;
        *static_cast<::firebase::database::Database**>(targets[0]) =
            ::firebase::database::Database::GetInstance(app_inner, &result);
        return result;
      },
      [](::firebase::App* app_inner, void* data) {
        void** targets = static_cast<void**>(data);
        ::firebase::InitResult result;
        *static_cast<::firebase::auth::Auth**>(targets[1]) =
            ::firebase::auth::Auth::GetAuth(app_inner, &result);
        return result;
      },
  };

  initializer.Initialize(
      m_app, initialize_targets, initializers, sizeof(initializers) / sizeof(initializers[0]));

After that, I start to sign in with a custom token by doing
auto sign_in_future = m_auth->SignInWithCustomToken(token);
wait();

Finally, I get database references and add listeners to listen to database change events. We also listen to connection status by subscribing to .info/connected.
I think the codes I provided above were implemented by following the official instructions and I'm sure that the token I used to sign in is valid. I also reviewed the realtime database security rules and no issue was found. I actually have a few devices running the same code but in different networks, most of them are talking to the rtdb without any issues. To rule out the network/firewall issue, I also wrote a simple websocket client using the same version of the uWebSockets library that Firebase SDK uses and it was able to establish a secure connection to a public websocket server, so the router's firewall might not be the root cause.
Right now I'm still not sure if it's a SDK issue or a network issue or even a server issue. Any thoughts or ideas will be very helpful. Thanks!
By the way, do your team have any plan of updating the version of uWebSockets library? It looks really old to me and it might be out of date.

Sorry for the late reply.  Unfortunately, we haven't had any luck reproducing the problem on our end, so still not clear what the root cause might be.
For the question about the version of uWebSockets, it is a bit complicated, as newer versions basically rewrote the entire library from scratch, so updating it requires changing the underlying code a bit.  It is in our backlog to do so though.


Get reel_ids as paramtr. If it empty - it will make a query for get it

Wrong pull request. Just discard it.


[Page Content] Arch Linux LicheeRV outdated

Please Choose

[ ] I'm working on fixing this issue.
[X] I confirmed that there is no similar issue.

I am visiting this page
https://github.com/ruyisdk/support-matrix/blob/main/D1_LicheeRV/ArchLinux/README.md
I found new information here.
https://archriscv.felixc.at/images/archriscv-2024-09-22.tar.zst
Give out some notes.
No response

Updated/Closed via https://github.com/ruyisdk/support-matrix/pull/115


Stating default Windows generated package size

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
Stating default Windows generated package size on README.md

How can a README.md change make travis build fail?

I would rather have approximate sizes for all of the different targets in a table, so I don't keep getting PRs for this kind of thing.
Also, the test failure is likely due to tests timing out.

I decided on pointing to the Electron releases page(s) instead, as the sizes of the zips there are approximately the same as zipped, minimal Electron apps (for a given platform/arch/Electron version).


fix(deps): update module github.com/pterm/pterm to v0.12.69

This PR contains the following updates:

Package
Type
Update
Change

github.com/pterm/pterm
require
patch
v0.12.67 -> v0.12.69

Release Notes

pterm/pterm (github.com/pterm/pterm)
v0.12.69
Compare Source

What's Changed
Exciting New Features 🎉

feat(select): added additional navigation keys by @hpcsc in https://github.com/pterm/pterm/pull/572

New Contributors

@hpcsc made their first contribution in https://github.com/pterm/pterm/pull/572

Full Changelog: https://github.com/pterm/pterm/compare/v0.12.68...v0.12.69
v0.12.68
Compare Source

What's Changed
Fixes 🔧

fix: upgrade Go version to 1.21 by @juburr in https://github.com/pterm/pterm/pull/569
fix: don't intercept os signals by @MarvinJWendt in https://github.com/pterm/pterm/pull/570

New Contributors

@juburr made their first contribution in https://github.com/pterm/pterm/pull/569

Full Changelog: https://github.com/pterm/pterm/compare/v0.12.67...v0.12.68

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: go get -d -t ./...
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>unexpected EOF


Fix sentences ,grammar, and punctuation in description in docshub

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


null safety upgrade

Just wanted to help moving things along for this.  I know there is another PR for null safety but there are conflicts and it may be getting stale.  I did a quick upgrade from master and checked the tests are still passing.
It looks like vscode dart plugin thinks lines were getting too long, so it automatically did some linting to multi-lines in some cases.  If this is undesirable, lmk and I'll try to revert it.
On a separate note, I noticed travis build hasn't been setup for this repo.  Would be as simple as adding .travis.yml file with just language: dart.

Thanks @jcramer. Would you mind to become maintainer of https://github.com/dart-bitcoin/bitcoin_flutter

This cool PR is pre-step to resolved https://github.com/dart-bitcoin/bitcoin_flutter/issues/50

@SFzxc will look into it!


Jhome.java:82-85: The javac binary might not be available...

The puzzle 5-ee2a7bdc from #5 has to be resolved:
https://github.com/yegor256/jhome/blob/2268a06bdb739258ad1aee0adcf543e79c057d7d/src/main/java/com/yegor256/Jhome.java#L82-L85
The puzzle was created by @volodya-lombrozo on 22-Nov-23.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@yegor256 Maybe we should just thrown an exception, if javac is absent on the current system. What do you think?

btw, I can solve this issue

@volodya-lombrozo yes, throwing an exception seems to be the right solution. Please, go ahead.

@rultor release, tag is 0.0.4

@rultor release, tag is 0.0.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.4

@yegor256 Done! FYI, the full log is here (took me 5min)


Region / EndRegion not in line with PowerShell ISE

VSCode Version: 1.6.1
OS Version: Windows 7 Pro
PowerShell Version: v5

Steps to Reproduce:

create #Region and #EndRegion tags at the same column tab
put code between region tags and make sure they line up at the same column tab
VSCode does not allow you to expand or collapse code between region tags when the code between the tags line up with the region tags themselves (where as it does allow you to collapse in PowerShell ISE).

Example:

based on the final example in screenshot above, it seems like region tagging isn't even working, and just seems to be working due to VSCode's default settings

Code folding is just based on indentation, it's not actually looking at the region tags. #12146


Add android.hardware.location.gps to manifest

Address this:

Hello Google Play Developer,
We're writing to let you know that the apps listed at the end of this email may be affected by an upcoming platform change.
Action required: If your app requires GPS hardware to operate properly, you will need to explicitly add the "android.hardware.location.gps" uses-feature to your manifest.
What’s changing
We’re making a change on October 15th, 2016 that will affect apps targeting API version 21 (Android 5.0, Lollipop) or higher that use ACCESS_FINE_LOCATION but don't explicitly have the "android.hardware.location.gps" uses-feature. Going forward, these apps will be available to install on devices that don't have GPS hardware. In most cases this won't be an issue since Wi-Fi and Cell-ID based location provides high enough fidelity for the typical operation of these apps. However, any apps that require GPS hardware, such as GPS navigators, should explicitly add the "android.hardware.location.gps" uses-feature to their manifest.
If your app requires GPS to function properly and you do not include android.hardware.location.gps in your manifest declaration, your users may have a poor app experience.
Also, if you’re using the fused location provider and wish to receive the most accurate location samples from GPS (i.e. with PRIORITY_HIGH_ACCURACY), you must include the "android.hardware.location.gps" feature in your app’s manifest to ensure that Google Play only distributes your app to devices with GPS sensors.
You can read more about this change in the Android Developers Help Center.
Regards,
The Google Play Team
Up to 20 affected app(s) and version(s) are listed below. If you have more than 20 apps in your catalogue, make sure to check each app for this issue.
com.codeforgvl.trolleytrackerclient   15

:+1:
On Tue, Sep 20, 2016 at 2:44 PM, Adam Hodges<EMAIL_ADDRESS>wrote:

Address this:
Hello Google Play Developer,
We're writing to let you know that the apps listed at the end of this
email may be affected by an upcoming platform change.
Action required: If your app requires GPS hardware to operate properly,
you will need to explicitly add the "android.hardware.location.gps"
uses-feature to your manifest.
What’s changing
We’re making a change on October 15th, 2016 that will affect apps
targeting API version 21 (Android 5.0, Lollipop) or higher that use
ACCESS_FINE_LOCATION but don't explicitly have the
"android.hardware.location.gps" uses-feature. Going forward, these apps
will be available to install on devices that don't have GPS hardware. In
most cases this won't be an issue since Wi-Fi and Cell-ID based location
provides high enough fidelity for the typical operation of these apps.
However, any apps that require GPS hardware, such as GPS navigators, should
explicitly add the "android.hardware.location.gps" uses-feature to their
manifest.
If your app requires GPS to function properly and you do not include
android.hardware.location.gps in your manifest declaration, your users may
have a poor app experience.
Also, if you’re using the fused location provider and wish to receive the
most accurate location samples from GPS (i.e. with PRIORITY_HIGH_ACCURACY),
you must include the "android.hardware.location.gps" feature in your
app’s manifest to ensure that Google Play only distributes your app to
devices with GPS sensors.
You can read more about this change in the Android Developers Help Center.
Regards,
The Google Play Team
Up to 20 affected app(s) and version(s) are listed below. If you have more
than 20 apps in your catalogue, make sure to check each app for this issue.
com.codeforgvl.trolleytrackerclient 15
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforgreenville/trolley-tracker-android-client/issues/36,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3RYAR-JwFlrY8GyQyo_zqLgFgBD8sCks5qsCl8gaJpZM4KB-v1
.


[RFC] Utilize CUDA Enhanced Compatibility

Currently, we are maintaining binary packages for 8 minor versions of CUDA (10.2 & 11.0 ~ 11.6).
However, now that CUDA minor releases are cut every 3~4 months, it is becoming unsustainable to build and distribute wheels for each minor release, both in terms of PyPI's limit and our release load.
This PR aims to make CuPy binary package utilize CUDA Enhanced Compatibility (it seems now a part of Minor Version Compatibility). This way we can reduce the number of packages to one for each CUDA major version.

cupy-cuda102 # for CUDA 10.2
cupy-cuda110 # for CUDA 11.0
cupy-cuda111 # for CUDA 11.1
cupy-cuda11x # for CUDA 11.2 ~ 11.x
cupy-cuda12x # for CUDA 12.x (in future)

Note: CUDA Enhanced Compatibility is a new feature in CUDA 11.1, but NVRTC support has been added in CUDA 11.2. So we still need a separate package for CUDA 11.1 or earlier.
What's done in this PR
This PR fixes each CUDA library binding to "lazy" load symbols for APIs added in CUDA minor releases. By implementing a symbol resolution in Python, instead of letting a dynamic loader do it, CuPy binaries can be compatible across all CUDA 11.2 ~ 11.x releases. This is a similar approach to what's done in CUDA Python except for the following differences:

CUDA Python resolves all symbols in Python. This PR instead only resolves the new APIs added within CUDA minor releases to reduce the development cost.
CUDA Python directly uses dlfcn/win32api. This PR instead uses ctypes to let Python handle the platform differences.

Note that this PR only fixes NVRTC. Once we agree with this idea, I'll fix the remaining ones in a separate PR. Feature availability check must also be fixed to use cudaRuntimeGetVersion instead of CUPY_CUDA_VERSION constant.

/test mini

I am worried that using ctypes may affect performance

I am worried that using ctypes may affect performance

ctypes is only used to retrieve a C function pointer. This is done when loading a module (import cupy):
https://github.com/cupy/cupy/blob/567456dc0fa3c4ff8747154ec6d797f17734b57c/cupy_backends/cuda/_softlink.pyx#L20-L31
The actual function call is done by calling a function pointer so it does not involve ctypes overhead:
https://github.com/cupy/cupy/blob/567456dc0fa3c4ff8747154ec6d797f17734b57c/cupy_backends/cuda/libs/nvrtc.pyx#L50-L64

Performance aside, I am concerned with some issues:

The dependency on the build-time version should be eliminated to the maximally possible extent.
The mix-n-match of symbols: Let's say cupy_backends.cuda.libs.nvrtc is linked to NVRTC from CTK 11.6, but ctypes mistakenly finds NVRTC from 11.0 for whatever reason. If the dynamically loaded symbols are used first, the 11.0 NVRTC would be loaded first, which would not be the desired outcome.
This is duplicating the effort of CUDA Python. What can it do to help CuPy? I feel the ultimate solution should be using CUDA Python for such nasty issues, and so our needs here should be reported to upstream 🙂

Thanks for the feedback @leofang!

The dependency on the build-time version should be eliminated to the maximally possible extent.

I agree with this direction. In this PR I intend to relax the build-time version dependency from the CUDA minor version to the major version.

The mix-n-match of symbols: Let's say cupy_backends.cuda.libs.nvrtc is linked to NVRTC from CTK 11.6, but ctypes mistakenly finds NVRTC from 11.0 for whatever reason. If the dynamically loaded symbols are used first, the 11.0 NVRTC would be loaded first, which would not be the desired outcome.

Thanks for pointing this out. For Linux, I believe this is safe as the dynamic loader (which resolves a hard library dependency embedded in the binary: nvrtc.*cpython*.so -> libnvrtc.so.11.2) and dlopen("libnvrtc.so.11.2") (which is done behind ctypes) uses the same strategy to find the library:
https://man7.org/linux/man-pages/man8/ld.so.8.html

If a shared object dependency does not contain a slash, then it
is searched for in the following order:
...

https://man7.org/linux/man-pages/man3/dlopen.3.html

If filename contains a slash ("/"), then ... Otherwise, the
dynamic linker searches for the object as follows (see ld.so(8)
for further details):
...

However, I'm not very confident with the Windows' behavior, so let me check later.

This is duplicating the effort of CUDA Python. What can it do to help CuPy? I feel the ultimate solution should be using CUDA Python for such nasty issues, and so our needs here should be reported to upstream 🙂

I think we are on the same page :smile: As discussed before, I'm thinking of fully moving to CUDA Python in the end, once CUDA Python supports other toolkit libraries.
In this PR, I focused on fixing NVRTC to get the idea, but cuSPARSE/cuSOLVER wrappers in CuPy are also CUDA minor version dependent, so they need to be fixed like this to utilize CUDA enhanced compatibility.

Duplication of CUDA Python aside, it doesn't seem like the separate 11.0/11.1 packages are needed? Seems like there should only need be a single 11.x package.

Note: CUDA Enhanced Compatibility is a new feature in CUDA 11.1

That isn't quite accurate. CUDA 11.0 supports minor version compat, it's just the driver initially released with 11.0 didn't support it.
See the note in the docs:

CUDA 11.0 was released with an earlier driver version, but by upgrading to Tesla Recommended Drivers 450.80.02 (Linux) / 452.39 (Windows) as indicated, minor version compatibility is possible across the CUDA 11.x family of toolkits.

If this is just for NVRTC and the fact that a major versioned libnvrtc.so wasn't added until 11.2, it should be pretty easy to account for that in the dlopen strategy. For example, here's Jitify's code for dlopening NVRTC: https://github.com/NVIDIA/jitify/blob/2b4139e618123109f8740e69f194c33f2f9b38ca/jitify2.hpp#L2318-L2348

@jrhemstad, thanks for the input!
Actually, CuPy built with CUDA 11.0 does not run with CUDA 11.1, or vice versa.
This is because cuSOLVER's SONAME changed between CUDA 11.0 and 11.1:
% ls -al /usr/local/cuda-11*/lib64/libcusolver.so.1?
... /usr/local/cuda-11.0.3/lib64/libcusolver.so.10 -> libcusolver.so.<IP_ADDRESS>  # <- SONAME 10
... /usr/local/cuda-11.1.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>   # <- SONAME 11
... /usr/local/cuda-11.1.1/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.2.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.2.1/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.2.2/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.3.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.3.1/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.4.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.4.1/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.5.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.5.1/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>
... /usr/local/cuda-11.6.0/lib64/libcusolver.so.11 -> libcusolver.so.<IP_ADDRESS>

Similarly, NVRTC's SONAME is different between CUDA 11.0, 11.1, and 11.2+ (as documented here: Figure 3. NVRTC supports minor version compatibility from CUDA 11.3 onwards):
% ls -al /usr/local/cuda-11*/lib64/libnvrtc.so.11.?
... /usr/local/cuda-11.0.3/lib64/libnvrtc.so.11.0 -> libnvrtc.so.11.0.221  # <- SONAME 11.0
... /usr/local/cuda-11.1.0/lib64/libnvrtc.so.11.1 -> libnvrtc.so.11.1.74   # <- SONAME 11.1
... /usr/local/cuda-11.1.1/lib64/libnvrtc.so.11.1 -> libnvrtc.so.11.1.105
... /usr/local/cuda-11.2.0/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.2.67   # <- SONAME 11.2
... /usr/local/cuda-11.2.1/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.2.142
... /usr/local/cuda-11.2.2/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.2.152
... /usr/local/cuda-11.3.0/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.3.58
... /usr/local/cuda-11.3.1/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.3.109
... /usr/local/cuda-11.4.0/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.4.50
... /usr/local/cuda-11.4.1/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.4.100
... /usr/local/cuda-11.5.0/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.5.50
... /usr/local/cuda-11.5.1/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.5.119
... /usr/local/cuda-11.6.0/lib64/libnvrtc.so.11.2 -> libnvrtc.so.11.6.55

The point is that we are linking to these shared libs at build time and not using dlopen (except for the code I'm trying to add in this PR). So we still need separate packages for pre CUDA 11.2.

It seems it's safe on Windows as well 😃
https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order

Factors That Affect Searching
The following factors affect whether the system searches for a DLL:
If a DLL with the same module name is already loaded in memory, the system checks only for redirection and a manifest before resolving to the loaded DLL, no matter which directory it is in. The system does not search for the DLL.

As discussed offline CuPy is overlinking, and I was playing around with LD_DEBUG=libs to see the impact. I found once CuPy is imported, all shared libraries are loaded so at least on Linux ctypes.CDLL() is not doing too much work.

/test mini


#152797380 Implement the add center page with react

What does this PR do?
It uses react and redux to implement the add-center page
Description of Task to be completed?
User should be able to add a new center
How should this be manually tested?

clone the repo
cd into the project directory
Run npm install to install all the dependency
Run npm run react:dev
visit the port where the webpack-dev-server started
log in as an admin
navigate to the add centers page
try posting some centers
when you get back to the centers page, those centers should be listed there.

Any background context you want to provide?

The frontend still uses the locally hosted server, so you would have to create a .env file to fulfill all the needed environment variables, the run npm run server:dev
Though the front end has an option for adding images, the image that you add won't reflect on the centers page and this is because I am yet to add the cloud image hosting service to help handle the image storage. The image that would be displayed would be the default image that I set when rendering the page.
If you really want an image, you can do so by posting the link to an image when creating a center using just the API endpoint with an API testing tool.

What are the relevant pivotal tracker stories?
#152797380
Screenshots (if appropriate)

Questions:
None

Changes Unknown when pulling 3c982ecb040f7a51fe2487ade6fd8fd2e7d7ff84 on ft-UI-add-center-152797380 into ** on develop**.

Changes Unknown when pulling 0eccea03bc18ea1e9a83697db7d8d6dfcc414d7e on ft-UI-add-center-152797380 into ** on develop**.


[WIP] Add rclone support

Hi @rjkernick !
We've prepared alternative docker-nexus-backup image with RClone tool in order to support a variety of cloud object stores as a backend for backup.
We tested it with AWS, so would be great if someone can re-test with GCE's GS and provide some feedback.
In addition to that, since the change is not backward compatible in values.yaml we have to consider major version bump, need your opinion on that @rjkernick
Please feel free to ping @MohamedZ3kri or @dene14, we really want to get that merged :)

Definitely a major version bump will be needed, which isn't really an issue since we have done it a few times now. Definitely push that change so the testing passes. I'll take a look through the rest this afternoon.

Please update the maintainer email in the image as well: https://github.com/dbccompany/docker-nexus-backup/blob/master/Dockerfile

Failed linting on a couple things:
charts/sonatype-nexus/values.yaml
158:18    error    trailing spaces  (trailing-spaces)
159:18    error    trailing spaces  (trailing-spaces)
187:7     error    wrong indentation: expected 4 but found 6  (indentation)

@rjkernick fixed


Build status queued after triggering build from REST API

Build shows under RUN tab, but is forever queued. Tried to Abort and run again, and it works, but initially after starting build from REST API it remains in Queued state.

Same here. Worked before I migrated to workflow.


Minor refactors

@empireu These are the minor changes that Cameron suggested (mostly around not using if (condition) return statements).
There's also #162 which captures some larger concerns that he will probably look into later but are not relevant to this PR.
We also don't really see the utility in the @In annotation and it's somewhat incorrect in some places where the code is called on both the client and the server side; we should simply replace it with javadoc documentation around where we want to have these things indicated to developers.

Codacy can be ignored here. It's angry that I moved a line around with a generic exception.


Default for "Measurement date" should be creation date of the uploaded file

Instead of having the "Measurement date" default to today's date, it should default to the creation date of the file.

I think the file's date is not uploaded, because it is part of the metadata of the filesystem and not part of the file contents.
I'm closing this, because then this is becomes effectively the same as #433.


fabric:/System/InfraustructureService is not healthy on Service Fabric Cluster

SF cluster infrastructure service is in unhealthy state for quite sometime now. We are seeing below error.

System.InfrastructureService' reported Warning for property 'CoordinatorStatus'.
Failed to create infrastructure coordinator: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Fabric.InfrastructureService.ManagementException: Unable to get tenant policy agent endpoint from registry; verify that tenant settings match InfrastructureService configuration

We have already compared the durability settings between VMSS and SF cluster setting as mentioned here and this doesnt appear to be an issue.
Primary nodes have silver durability where as other nodes types have bronze durability tier.
Reliability tier is Silver.

For context this is specific for Azure SF clusters, and I have seen this come up as a result of CRP/VMAgent behavior. Incident 196691804 is currently tracking the investigation on the VMAgent side.

Incident filed and triaged. Posting new guidance for reference https://github.com/microsoft/service-fabric/blob/0ed99b8b37b91f46d2481c5a784179c1a6c7e7df/CONTRIBUTING.md#production-issues


Update Readme reg- docker setup of pg-osc

Hey,
please update readme regarding the installation of pg-osc through docker and give steps to use it using docker.

Also, explain the fields and could you please provide the values of the fields.

There description here links to the Github Readme which has some examples. Do you think thats good? If not, PRs welcome with more examples in the Readme 🙌🏾

Closing the issue, but open to PRs or any other suggestions. Thanks!


nodejs: 8.1.0 -> 8.1.4

Motivation for this change
A high impact DoS vulnerability was fixed in Node 8.1.4
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

I’ve just tested this on macos, everything works fine.


FlashCard Generator

Generates Flashcards

Kindly use the feature request for raising this Issues. Also not accepting any sample projects over extensions.
Closing it @AmrutaJayanti


[New game]: ADVENTURES OF CAPTAIN CALLISTO 👾

🎮 Game Request
Game logic and basic description

A short 3D action game with aesthetic visuals.
Our hero, Captain Callisto, blasts through space, seeking adventure. What will he find?

Point down the features
Game points
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @0xabdulkhalid !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @0xabdulkhalid ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add option of distinguishing between East and West (Fixes #3)

Using the option --east-west-coast. East is defined to start at -100
longitude.
Also clean up the demographic code a little using vector operations.
Fixes #3

Awesome, thanks!


Add support for Mustache templates

Eco, Jade and Haml are nice, but Mustache would let us re-use our templates server-side.

I'm +1 on this. Assigned milestone to 0.10.

Excellent!  As a work-around here is what I'm doing for now:

add mustache.js to /src/vendor/
place mustache templates in /src/app/templates/ with a .eco extension (better than having the mustache template as a string in the view)
in view, render template with Mustache.to_html require("templates/whatever")(), data

Nice!

This wouldn't be fixed until mustache guys fix janl/mustache.js#150.

brunch now supports mustache templates (with hogan.js help). https://github.com/brunch/brunch-extensions/pull/3
it would be included in the next beta in a few days.


Split node-vault in different npm packages

My idea is to split this library in different npm packages because the functionality of vault is growing so fast. We could have a basic client for system backend and then extended clients for secret backends, auth backends and plugin backends as well. I would love to keep the repo and manage the publishing of the npm packages with a tool like lerna (https://github.com/lerna/lerna). WDYT?

Closing because of the reasons mentioned here


[feat] add the batch monitor tool

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@81fbfa9). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@          Coverage Diff           @@
##             main     #23   +/-   ##
======================================
  Coverage        ?   71.7%
======================================
  Files           ?      15
  Lines           ?     584
  Branches        ?      70
======================================
  Hits            ?     419
  Misses          ?     153
  Partials        ?      12


Clear-HgsClientHostKey command not working

I am running Windows 10 Enterprise version 10.0.18362,
PowerShell version 5.1

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f498ebf8-8cda-7e68-c70c-9ecd0e7bd7df
Version Independent ID: b710fea4-0d4e-5fdd-03e8-ce2679fa18c2
Content: Tutorial: Getting Started with Always Encrypted with secure enclaves using SSMS - SQL Server
Content Source: docs/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves.md
Product: sql
Technology: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

@arafubeatbox -- Futai, thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around the general task.

Thank you William, for your response. Excuse me for asking such an ambiguous question.
I was setting up my SQL server computer, following the instructions of
https://docs.microsoft.com/en-us/sql/relational-databases/security/tutorial-getting-started-with-always-encrypted-enclaves?view=sql-server-ver15
In step 2. part 8, I was not able to attest to the HGS computer, so I ran the "Clear-HgsClientHostKey" command, as told.
It didn't work on neither the HGS computer or the SQL server computer, telling me "is not recognized as the name of a cmdlet, function, script file, or operable program."

Hi @arafubeatbox --
I’m a PM for Always Encrypted in SQL Server.
First of all, thank for trying AE with enclaves. Sorry about the issues you have hit. Hopefully, we can unblock you soon.
First of all, we confirmed the correct cmdlet name is Remove-HgsClientHostKey, not Clear-HgsClientHostKey. We will fix it in the doc.
Please, try to run it and retry the steps again. If that does not help, please open System Information (msinfo32.exe) on the machine running SQL Server and check the value of Virtualization-based security - it should say "Running" if you successfully completed Step 2.4. If it is not running, please share the values of other VBS fields from System information.
Thanks,
Jakub (@jaszymas)

Hello @jaszymas --
I am sorry for my late response.
I was able to configure secure enclaves for my SQL Server properly.
Thank you for your sincere support.


Add check for presence of dependencies in the public API

When designing a public API, it is generally good to ensure there are no third party items in the public API surface. That way it is easier to guarantee long term public API stability, for example.
It would be useful to add a flag that makes cargo public-api exit with an error if it finds foreign/external items in the public API. Except for items that belong to libstd and similar.
Let's go with cargo public-api --deny external-items until we come up with something better.
The general idea comes from https://users.rust-lang.org/t/tool-to-check-if-any-dependencies-sneaked-into-my-public-api/89903.

I think this would need a way to allow certain items, e.g I may want to have http items in my api surface, but not others
this should probably also take crate versions into account.
So maybe a config would be easiest, something like
[workspace.metadata.public-api]
disallow-external = true
[[workspace.metadata.public-api.allowed-externals]]
package = "http"
items = [] # effectively all items, or maybe it should be it's own field

I have seen an RFC related to this. see the question `What is a public dependency?'
My though is it is better to be implemented as clippy lint (rather than manually running cargo public-api)

Nice, I didn't know about that RFC. I completely agree it is much better to solve this properly once and for all upstream in rustdoc.
So let's close this from our side.


WIP Changes required to add service bindings to the Bluemix plugin

Essentially just added some publicly exported functions, which called the private versions.  This helped to have a smaller ripple effect across the code base as some of the functions that we needed to export would force changes across the entire API.
This can still be done, but at least for the time being I'd prefer to do it this way and then fix this up (i.e. removing the duplicate methods that only have a difference in their case of the first character of the name and just making the required methods publicly exported) .   This way we can meet the deadline with less risk as there wouldn't be as many changes across the entire cli code base.

@mdeuser ^^

@jessealva - in general, when the pr is merged, no additional technical debt is expected.  in this case, let's bite the bullet and make the sweeping change prior to the pr merge.  for now, it's ok to do what you have suggested for quicker testing.

@jessealva oh.. also, you will want to submit open cli PRs against the apache/incubator-openwhisk repo instead of this repo.  changes from the apache/incubator-openwhisk repo are then merged into this repo.
/cc @houshengbo

Closed as this was the incorrect repo in which to submit changes in.


Create Taxons

Add functionality to create taxons from an import spreadsheet.
https://trello.com/c/bsZAwZ35/450-improve-alpha-taxonomy-tagging

This looks like a good idea, but I'm a bit worried by alpha taxons being able to be created by two apps (collections-publisher and content-tagger).  In particular, what will happen if content-tagger creates a taxon, and then collections-publisher is used to edit it?  I think publishing-api only allows a single app to own a content item, so I think it may give a conflict error in that situation (not certain if this is still how it works, though).
I'm also a bit concerned that the details of what goes into the taxons will now need to be updated in two places when we want to change it - the schemas will help here, but things like optional fields, or default values for fields, will still need to be maintained carefully.  Also, we're not yet checking that everything going to the publishing api satisfies the schemas (but we will be soonish, hopefully).
Could you put a bit more detail in the pull request and commit descriptions, please? (links to trello are good, but tend to break after a while).  It would be good to rebase away the accidentally committed merge conflict (in https://github.com/alphagov/content-tagger/commit/598839c427075f376d00a3d8e45b2d9c5cd61924), and make sure to explain why changes are being made in the commit messages (eg, https://github.com/alphagov/content-tagger/commit/7477fb17f06fbb97020bb1f1fb8cb3fda34f450c - what's changed about the linter, and why?)

Heart of the problem is which functionality to put where. We already know that there are some parts of the tagging world that could be in both content tagger and collections publisher. They are very closely related and might even turn out to be the same app.
I think the bulk creation of tags should be possible in the same flow as bulk tagging, so for now I think it might be reasonable to allow content-tagger to create taxons too.
Once we get a better understanding of how everything fits together, we could decide to merge collections-publisher and content-tagger, or move the taxonomy manager to content-tagger.
It would be good to have a whiteboard about the the responsibilities of the different apps.

Perhaps it would be easier to simply put everything in one place for now? Rather than having duplication and/or muddied responsibilities between two apps, we could simply build out this new taxonomy functionality in collections-publisher. If a clear boundary for extraction emerges then we can do so later on. Keeping the taxonomy-related code decently encapsulated and well-named will make that easier.
Unless of course this doesn't matter. For example, are there any significant negative implications of the app names we've chosen in lines 16-17 here?: https://github.com/alphagov/content-tagger/pull/13/files#diff-ff4e30814d2d29ca33294961ca432cd8R16
I've incorporated the PR feedback and got the lint checks passing. Some Jenkins config update was required. This is ready for review again, @tijmenb and @rboulton .

If we are putting it in one app, I would prefer moving the taxonomy manager here. This alpha taxonomy feature is part of the future bulk tagger, which should probably be in this application.

That seems like a sound approach. Taxonomy-related functionality should exist in one place, irrespective of where we decide that is. Anything is better than dealing with taxons/mappings in two apps.

@tijmenb reworked the jenkins script. That was a royal mess because I didn't realise that the failures in CI were due to the RSpec after(:suite) callback running the linter, not the stuff in jenkins.sh. WDYT.


Add version: Microsoft.UI.Xaml.2.8 version 8.2305.5001.0

Pull request has been created with komac v2.1.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-No-Executables


filter is not working properly in equals to and not equals to condition for those column where value consists special characters

Bug report
Title
**filter is not working properly in equals to and not equals to condition for those column where value consists special characters **

Issue Description:
for ex. if any column consists value invoice#01 then while applying filter for that column if equals to condition has been selected and same value given then it is searching  only invoice.
Preconditions
1. framework Version: 0.1.6

Steps to reproduce
1. step1- complete invoice setting
2. step2- place an order
3. step3- use filter for id column in order section of sales

Expected result
should check condition  according to complete given value

Actual result-
its not working according to complete given value

Revamped the entire discount system.


Fix issue with linking email to anonymous accounts on desktop

Description

Provide details of the change, and generalize the change in the PR title above.

Changes to email enumeration protection broke some functionality on the backend with email accounts. One of those is upgrading anonymous accounts to have email and password.  This can be fixed by using a slightly different rest call, so this makes that change for desktop, mobile platforms will be fixed in the underlying mobile SDKs.

Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.

Testing locally with a custom project that has email enumeration protection turned on.

Type of Change
Place an x the applicable box:

[x] Bug fix. Add the issue # below if applicable.
[ ] New feature. A non-breaking change which adds functionality.
[ ] Other, such as a build process or documentation change.

Notes

Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
Read the contribution guidelines CONTRIBUTING.md.
Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.

Removing tests failed tag, since it is just caused by backend problems that aren't part of this change


fixed from https://github.com/ishikota/PyPokerGUI/issues/6

Thanks @Ns85
@ishikota please let me know if there's anything else you'd like me to do to spruce this up.

+1


List dependencies for Ubuntu / apt

Please could you list the dependencies for an Ubuntu / apt-based repo in the readme?

@alexellis Are you talking about the stuff we have to build buildah?
Travis has
    - sudo add-apt-repository -y ppa:duggan/bats
    - sudo apt-get -qq update
    - sudo apt-get -qq install bats btrfs-tools git libapparmor-dev libdevmapper-dev libglib2.0-dev libgpgme11-dev libselinux1-dev
    - sudo apt-get -qq remove libseccomp2

Yes - the bootstrap, so yum is mentioned on the README front page, but coming from a background working mainly with Ubuntu it might help interest if it was updated to show instructions for both.

This is obviously missing the point of the project - but it might also be worth adding a Dockerfile that documents the complete build - is repeatable and testable and can be run easily by MacOS users to evaluate the project without having to install a Linux VM.

Open a pull request for what you would like to see.  Also please review 244, to tell me if it works.

Thanks! It'll be a few days if you can wait.

i think this should probably be closed, considering #244 is merged and #354 is pending.

Makes sense to me.  Closing.


Adds settings button and the reset button into it.

This adds a new settings app, the new window for it, and the reset button back with functionality.

looks good and works well


Treat negative tests as passed - as expected by JCK

Updates xslt logic to detect and count test "failures" and excludes the case where a negative-test fails.
Resolves backlog/issues/191

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

Before the PR: Test_grinder/job/Grinder/4462/testReport/
After the PR: Test_grinder/job/Grinder/4463/testReport/


Content is selected when dragging track

Describe the bug
After listeners were made passive content is now selected when scrolling by dragging track.
And there is warning in the log:
Ignoring ‘preventDefault()’ call on event of type ‘click’ from a listener registered as ‘passive’.

To Reproduce
Steps to reproduce the behavior:

Go to https://grsmto.github.io/simplebar/
Scroll by dragging vertical track
Content is selected

Expected behavior
Content should not be selected when dragging track.
Reproducible example
https://grsmto.github.io/simplebar/
Additional context
There is preventDefault that fixes content being selected, but it is now ignored as listeners are passive.
I think most of the listeners can be made passive but not all of them.
Your environment

Software
Version(s)

SimpleBar
v4.2.0

Browser
Firefox

npm/Yarn
n/a

Operating System
Arch

I noticed the error but I can't reproduce the issue. I'm testing on Chrome latest/mac osx.

My bad, it is working in Chrome right now. But content is selected in Firefox

Actually I see that content underlying is clickable (so you can highlight text on double click). But it doesn't select it on drag.

Maybe it is possible to add user-select: none; to content when dragging and just remove preventDefault.

@Demivan no because you'll still be able to click for example a clickable element under the track.

And what about pointer-events: none or is it a bit overkill? It will disable all pointer events on content so clicks will be prevented. But it will prevent hover on content too, not sure if it is an issue

Excellent idea. Actually I couldn't find another solution so I just did that. Seems to be working fine.


#6: Revert changes to rultor config

This closes #6

@rultor merge pls

@rultor merge pls

@aliceice OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge pls

@aliceice Done! FYI, the full log is here (took me 3min)