License Manager

License Manager micro service.

As I said, we’re just designing it. Any suggestions?
Ideas so far:
Versioning[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=6]
It's quite common to version APIs to make sure that existing integrations continue to run while still making improvements, fixes and adding or removing functionality. [1]
The API will also start being versioned. As discussed in [2], there are basically three ways to implement API versioning:
by far the most commonly used way is to include it in the URL:
examples: calls to .../api/v1/ and .../api/v2/
pros: it's simple, most APIs are doing it;
cons: when the version changes, clients have to change the URLs used and we are 'artificially' changing the
by using a version HTTP header when making a request:
examples: calls to .../api/ with HTTP header X-API-Version (e.g.) set to 1 or 2
pros: we're keeping the same URL when changing the version;
cons: this is really mimicking the Accept HTTP header (see below) feature;
by using the Accept HTTP header when making a request:
examples: calls to .../api/ with HTTP header Accept set to application/vnd.example.v1+json or application/vnd.example.v2+json
pros: you're following what the HTTP specification has meant for this header, is seen as the future of APIs (Content Negotiation)
cons: harder to test (you have to know how to work with lower level too like cURL, instead of just passing a URL around for a tester to click on it)
Calls to a non-existing version will return 404. Calls without any version reference will have the same results as calling the most recent version.
Which option should we take?
What format for the version?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=7]
Shall we use a simple integer, like in the 2. example above? A string like in v1 or Y1_Release? A date, like in 2016-11-25?
How to version messages?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=8]
First: should we version messages? Yes, since what is said above about services evolving is also applicable to them.
References[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=9]
Kong (request) Versioning of APIs and Microservices https://github.com/Mashape/kong/issues/402, Montana Flynn;
Your API versioning is wrong, which is why I decided to do it 3 different wrong ways https://www.troyhunt.com/your-api-versioning-is-wrong-which-is/, by Troy Hunt;
Versioning RESTful ServicesPosted http://codebetter.com/howarddierking/2012/11/09/versioning-restful-services/, by Howard Dierking;
GitHub API Media Types https://developer.github.com/v3/media/;
thanks
José Bonnet
<EMAIL_ADDRESS>
On 22 Nov 2016, at 17:52, Bernardo Ferreira<EMAIL_ADDRESS>wrote:
@Bernardomrf commented on this pull request.
In son-gtklic/docs/swagger.yaml https://github.com/sonata-nfv/son-gkeeper/pull/351:

@@ -0,0 +1,547 @@
+# this is an example of the Uber API
+# as a demonstration of an API spec in YAML
+swagger: '2.0'
+info:

title: Sonata's License Manager
description: Manage licenses Sonata services.
version: "1"
+# the domain of the service
+host: sonata-vm1.aws.atnog.av.it.pt
+# array of all schemes that your API supports
+schemes:

http
+# will be prefixed to all paths
+basePath: /api/v1
We have looked for python solutions for using that versioning system, and we found a library that uses the Accept header for versioning. We've never tried it, but we think it might work. We just need to know more or less the content and format of the header, to start implementing.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAuQ9-G8cDuyL68Ajq4rVVIBUaXPk92ks5rAyvogaJpZM4K25C-.

Thing is, API’s don’t change that often. Versioning the URI makes things stable and explicit, also easier to debug which was the all reason we dropped SOAP and boarded REST.
I would stick to URI versioning

On 23 Nov 2016, at 16:10, José Bonnet<EMAIL_ADDRESS>wrote:
As I said, we’re just designing it. Any suggestions?
Ideas so far:
Versioning[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=6]
It's quite common to version APIs to make sure that existing integrations continue to run while still making improvements, fixes and adding or removing functionality. [1]
The API will also start being versioned. As discussed in [2], there are basically three ways to implement API versioning:
by far the most commonly used way is to include it in the URL:
examples: calls to .../api/v1/ and .../api/v2/
pros: it's simple, most APIs are doing it;
cons: when the version changes, clients have to change the URLs used and we are 'artificially' changing the
by using a version HTTP header when making a request:
examples: calls to .../api/ with HTTP header X-API-Version (e.g.) set to 1 or 2
pros: we're keeping the same URL when changing the version;
cons: this is really mimicking the Accept HTTP header (see below) feature;
by using the Accept HTTP header when making a request:
examples: calls to .../api/ with HTTP header Accept set to application/vnd.example.v1+json or application/vnd.example.v2+json
pros: you're following what the HTTP specification has meant for this header, is seen as the future of APIs (Content Negotiation)
cons: harder to test (you have to know how to work with lower level too like cURL, instead of just passing a URL around for a tester to click on it)
Calls to a non-existing version will return 404. Calls without any version reference will have the same results as calling the most recent version.
Which option should we take?
What format for the version?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=7]
Shall we use a simple integer, like in the 2. example above? A string like in v1 or Y1_Release? A date, like in 2016-11-25?
How to version messages?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=8]
First: should we version messages? Yes, since what is said above about services evolving is also applicable to them.
References[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=9]
Kong (request) Versioning of APIs and Microservices https://github.com/Mashape/kong/issues/402, Montana Flynn;
Your API versioning is wrong, which is why I decided to do it 3 different wrong ways https://www.troyhunt.com/your-api-versioning-is-wrong-which-is/, by Troy Hunt;
Versioning RESTful ServicesPosted http://codebetter.com/howarddierking/2012/11/09/versioning-restful-services/, by Howard Dierking;
GitHub API Media Types https://developer.github.com/v3/media/;
thanks
José Bonnet
<EMAIL_ADDRESS>
On 22 Nov 2016, at 17:52, Bernardo Ferreira<EMAIL_ADDRESS>wrote:
@Bernardomrf commented on this pull request.
In son-gtklic/docs/swagger.yaml https://github.com/sonata-nfv/son-gkeeper/pull/351:

@@ -0,0 +1,547 @@
+# this is an example of the Uber API
+# as a demonstration of an API spec in YAML
+swagger: '2.0'
+info:

title: Sonata's License Manager
description: Manage licenses Sonata services.
version: "1"
+# the domain of the service
+host: sonata-vm1.aws.atnog.av.it.pt
+# array of all schemes that your API supports
+schemes:

http
+# will be prefixed to all paths
+basePath: /api/v1
We have looked for python solutions for using that versioning system, and we found a library that uses the Accept header for versioning. We've never tried it, but we think it might work. We just need to know more or less the content and format of the header, to start implementing.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAuQ9-G8cDuyL68Ajq4rVVIBUaXPk92ks5rAyvogaJpZM4K25C-.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351#issuecomment-262558651, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ1NuGdyrbNWpgufMenrzh09fcTIaAks5rBGWAgaJpZM4K25C-.

It’s not API versioning we’re dealing with here, it’s end-to-end. The API ‘just' has to have a way to express which version is desired by the API’s clients.
Anyway, the decision has been taken: we’re going with case 1) above, URL with a version, v1, v2, etc., as you’re suggesting.

On 23 Nov 2016, at 21:06, Diogo Gomes<EMAIL_ADDRESS>wrote:
Thing is, API’s don’t change that often. Versioning the URI makes things stable and explicit, also easier to debug which was the all reason we dropped SOAP and boarded REST.
I would stick to URI versioning

On 23 Nov 2016, at 16:10, José Bonnet<EMAIL_ADDRESS>wrote:
As I said, we’re just designing it. Any suggestions?
Ideas so far:
Versioning[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=6]
It's quite common to version APIs to make sure that existing integrations continue to run while still making improvements, fixes and adding or removing functionality. [1]
The API will also start being versioned. As discussed in [2], there are basically three ways to implement API versioning:
by far the most commonly used way is to include it in the URL:
examples: calls to .../api/v1/ and .../api/v2/
pros: it's simple, most APIs are doing it;
cons: when the version changes, clients have to change the URLs used and we are 'artificially' changing the
by using a version HTTP header when making a request:
examples: calls to .../api/ with HTTP header X-API-Version (e.g.) set to 1 or 2
pros: we're keeping the same URL when changing the version;
cons: this is really mimicking the Accept HTTP header (see below) feature;
by using the Accept HTTP header when making a request:
examples: calls to .../api/ with HTTP header Accept set to application/vnd.example.v1+json or application/vnd.example.v2+json
pros: you're following what the HTTP specification has meant for this header, is seen as the future of APIs (Content Negotiation)
cons: harder to test (you have to know how to work with lower level too like cURL, instead of just passing a URL around for a tester to click on it)
Calls to a non-existing version will return 404. Calls without any version reference will have the same results as calling the most recent version.
Which option should we take?
What format for the version?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=7]
Shall we use a simple integer, like in the 2. example above? A string like in v1 or Y1_Release? A date, like in 2016-11-25?
How to version messages?[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=8]
First: should we version messages? Yes, since what is said above about services evolving is also applicable to them.
References[edit http://wiki.sonata-nfv.eu/index.php?title=WP4_topics_for_the_F2F_Porto_meeting&action=edit&section=9]
Kong (request) Versioning of APIs and Microservices https://github.com/Mashape/kong/issues/402, Montana Flynn;
Your API versioning is wrong, which is why I decided to do it 3 different wrong ways https://www.troyhunt.com/your-api-versioning-is-wrong-which-is/, by Troy Hunt;
Versioning RESTful ServicesPosted http://codebetter.com/howarddierking/2012/11/09/versioning-restful-services/, by Howard Dierking;
GitHub API Media Types https://developer.github.com/v3/media/;
thanks
José Bonnet
<EMAIL_ADDRESS>
On 22 Nov 2016, at 17:52, Bernardo Ferreira<EMAIL_ADDRESS>wrote:
@Bernardomrf commented on this pull request.
In son-gtklic/docs/swagger.yaml https://github.com/sonata-nfv/son-gkeeper/pull/351:

@@ -0,0 +1,547 @@
+# this is an example of the Uber API
+# as a demonstration of an API spec in YAML
+swagger: '2.0'
+info:

title: Sonata's License Manager
description: Manage licenses Sonata services.
version: "1"
+# the domain of the service
+host: sonata-vm1.aws.atnog.av.it.pt
+# array of all schemes that your API supports
+schemes:

http
+# will be prefixed to all paths
+basePath: /api/v1
We have looked for python solutions for using that versioning system, and we found a library that uses the Accept header for versioning. We've never tried it, but we think it might work. We just need to know more or less the content and format of the header, to start implementing.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAuQ9-G8cDuyL68Ajq4rVVIBUaXPk92ks5rAyvogaJpZM4K25C-.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351#issuecomment-262558651, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ1NuGdyrbNWpgufMenrzh09fcTIaAks5rBGWAgaJpZM4K25C-.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/sonata-nfv/son-gkeeper/pull/351#issuecomment-262630048, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAuQ507v__u4Gumiulmv6mHC5lyeUCtks5rBKrtgaJpZM4K25C-.

Hi,
PR accepted. We now need to add the container generation phase to the integration Jenkins (I'll do it ASAP).


Fix incorrect references to "HttpClientFactory"

Summary

Revise main article about the "HttpClientFactory"
Fix references

Fixes https://github.com/dotnet/docs/issues/16422

@mvelosop resolve conflicts?

Done @nishanil

@nishanil, don't approve/merge this just yet, I'm checking another related issue and might add something.

Done @nishanil

Conflicts and warnings :(


How to finetune some special layers of model converted from caffemodel

I am trying to reproduce the result of Automatic Colorization.
I plan to finetune the net from vgg16 and have converted the vgg16 caffe model file and net file to mxnet format. Now the problem is I think if I want to change one layer's structure and finetune it, I must have a python file that defined the net structure which consist with the mxnet json format net file. How can I get the python file from json format net file?

under tools/caffe_converter there is a convert_symbol script. Use it to generate python script for creating the symbol.

Generated successfully, thanks.


Fix issue #6

Fix eth_getFilterChanges to only include new hashes.

I did this before, but it will lead to a problem. When the client sends a transaction, it will probably be packaged very quickly, then when the client call eth_getFilterChanges ,  it won't get the block just packed, so I include the current block in the method.

Could you elaborate a bit on this issue and why your proposed code could fix this issue? Especially:

Does only the first block cause an issue? Because in the constructor you would only include the previous block before subscribing.
Why does subscribing to the filter before sending the transaction does not fix this problem?

But why would this be an issue with vechain but not with ethereum? Are the vechain blocks so much faster?

I am using vechain's --on-demand mode, it immediately packs after receiving a transaction. So if I send a transaction first, then subscribe, I will not get the result of the transaction.
The correct way is to subscribe first, then send the transaction. But I can't assume that the user will do this. So every time I return to the current block (this is also wrong, I think it should be only the first time to return to the current block.).

Including the first block will only delay the problem. If two blocks are mined nearly instantly (or network delays ...), the transaction won't be included either.

Yes. So this is the Truffle own problem, when I run truffle test:
INFO - gear.rpc[line:178] - received rpc request - eth_sendTransaction
INFO - gear.rpc[line:229] - received rpc request - eth_newBlockFilter
INFO - gear.rpc[line:241] - received rpc request - eth_getFilterChanges
INFO - gear.rpc[line:201] - received rpc request - eth_getTransactionReceipt
INFO - gear.rpc[line:149] - received rpc request - eth_getCode
INFO - gear.rpc[line:235] - received rpc request - eth_uninstallFilter

Should be subscribed first...
I will think again about any better solution. If you have it, please let me know.

We could store all transactions from sendTransaction and if a new blockfilter is created, we begin with the block that contained the transaction (if any). Then delete the stored transactions.
This would ensure that:

Transactions are included
Send empty changes if subscribed without a sent transaction

Just all transactions?

Or we could map them by the id they send with? This sounds like a good idea.

The problem is that new blockfilter does not have any additional information, so I can't know which block to begin with.

Every application should send a unique id with every request. We could then map each eth_sendTransaction with the id. When a new blockfilter is requested with the same id we include the previous transaction-block matched by the id.

If sendTransactionand  I map [tx id => block num], then I may have the following mapping:
0x1111111: block num
0x222222:block num
...

So, when newBlockFilter, Which block num does it begin with?

What you mean is to modify the interface like eth_newBlockFilter(client_id)?

The web3-gear internal interface, yes. This would not change the user application nor the communication with thor.

Changing client.py.new_block_filter() ->client.py.new_block_filter(clientId). Because if you look at the Ethereum RPC interface, the id is already added.

Look down to the examples listed under every command, there should always be a field "id" added.
Estimate Gas for example:
// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_estimateGas","params":[{see above}],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x5208" // 21000
}

This id is not client id, it is to make the response consistent with the request. You can see json-rpc-what-is-the-id-for.

This id can't be obtained in the rpc method, it is used internally by json rpc.
Within the rpc method, only params can be obtained, you can try it.

I see the problem. I would say we implement the hack with the constructor including the previous block? Maybe with a flag to disable it?

Or create an issue at truffle itself.

But this not be an issue  with ethereum, because when ethereum receives a transaction, there will be pow, so the transaction will not be packaged immediately.

I Think the current solution is to apply your changes first, but move block num forward one when constructing the BlockFilter.


Create basic Azure Arc GitOps flow for AKS

Description
Create basic Azure Arc GitOps flow for AKS
Implementation Requirements

Parameterize deployment wherever possible
Detailed README & instructions
Reference in the main README

Supporting Docs
https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/use-gitops-connected-cluster

Closing
https://github.com/likamrat/azure_arc/blob/master/azure_arc_k8s_jumpstart/docs/aks_gitops.md


create: Refactor NewContent to be testable

NewContent is refactored to use the afero.Fs interface that should allow
full testing.  This commit also pulls the metadata creation logic out of
NewContent and into a separate function to decrease the cyclomatic
complexity of NewContent.

Merged in 9323707


Bot still shows as online after calling DisconnectAsync & LogoutAsync

This is not the library. Discord has a delay, to give a chance for reconnect.


The latest working config for GAN example?

Can someone please indicate which of the latest DIGITS, CUDA, cuDNN and Tensorflow combo is working for GAN example? I have failed to make it work with (Digits6.1+Cuda9.1+cuDNN7.1+TF1.6)
Thanks,
Alp

Ok here is a working config; Ubuntu 16.04, cuda 8.0, cuDNN 6, tensorflow 1.4.1, nvidia 384 driver.


backport removing jmxtrans in stub roles

and check if alias already exists in keystore

Thanks @leochen4891, this is a good fix for folks with duplicate certificates running around I suspect. As I'm on a cellphone at the moment, would you please share what the not_if guard prints if the alias is found versus not? (Please use a public cert from /usr/share/ca-certificates if you would.)


Custom buttons

I am considering adding a userscript that lets you add clickable buttons with user defined links  (suggested in a refined-github issue by @ben-eb)...
The following things need to be addressed:

Would this work along with or be separate from the custom hotkey userscript?
Where should the button(s) be placed?
Should the button only be visible on specific pages?
Would a dropdown that can contain numerous custom buttons be better than a bunch of single buttons which may overflow?

Added GitHub Custom Navigation userscript in https://github.com/Mottie/GitHub-userscripts/commit/50bffd918943b8f7d1d6ec0ab43ad12cfe17d800.


Decompose endpoint.hpp into endpoint.hpp and endpoint_base.hpp

Right now we have a very large amount of functionality bundled into the same class, and I think we could enhance understandability by breaking this class into two parts.
EndpointBase <- This class would have all of the functionality that's completely generic to the type of message being sent/received. This includes the machinery for interacting with the socket directly, and the async read/write code.
Endpoint <- This class would build off of the low level machinery provided by EndpointBase.
I believe that decomposing the code like this would be 99% a cut-and-paste operation.

We could go even further, and have an EndpointClient and EndpointServer.
For example, there's not a lot of overlap between the functionality needed to support servers versus the functionality needed for clients.
Clients send connect, and receive connack, servers receive connect, and send connack. That type of thing.

What do you think?
If I opened a pull request to support something like the above, would you be interested in that?

Right now we have a very large amount of functionality bundled into the same class, and I think we could enhance understandability by breaking this class into two parts.
EndpointBase <- This class would have all of the functionality that's completely generic to the type of message being sent/received. This includes the machinery for interacting with the socket directly, and the async read/write code.
Endpoint <- This class would build off of the low level machinery provided by EndpointBase.
I believe that decomposing the code like this would be 99% a cut-and-paste operation.

I think that it's worth trying. However, I'm implementing MQTT v5 functionality on the current endpoint.hpp.
Please wait a moment. I will let you know.

Ok. Will wait.

So I think we need to discuss this concept more.
I spent a couple of hours today investigating what would have to happen, and i'm not sure the best way to implement this.
A few options:

Make the template class endpoint, accept two new template parameters. Sender, Receiver. This would allow the user of the class to switch between async or non-async implementations of the low level sending / receiving functionality.
Right now I notice that receiving data always happens with async calls. I'm not sure one way or another if that's the best design, so I'm not real trying to address that.

Once the raw send/receive operations are handled by template calls, we can merge all of the various functions used to send data async/sync into a single set of implementations.
Problems with this approach: When doing blocking sends, typically lifetime doesn't need to be handled. By merging the calls into a single set of calls, we'll either have to always handle lifetime, or will need to have some other kind of magic to detect if lifetime needs to be handled.

Move functionality that isn't concerned with sending / receiving data into the base class. That's things like callback functions for data that have already been received (e.g., the handle_payload() function). The registration of the other various handlers, that kind of thing.
Then, on top of that, we would have AsyncEndpoint.hpp, and SyncEndpoint.hpp. This allows for blocking / nonblocking functionality to live separately. E.g., instead of "async_publish()", it would just be "publish" and the specific implementation of it would be handled by whether or not the AsyncEndpoint was used, or the SyncEndpoint.

Personally, I'm not really sure there's a lot of value in supporting a synchronous API, but it's your project so we can keep supporting it.

I'd like to allow to user both async/sync API call from the same endpoint object. Boost.Asio support it. I don't want to limit it on the upper layer, mqtt_cpp.
It seems that option 1 and 2 can't do that.
I think that we need to confirm what is the real problem with the big one file.
 If it is the problem, simply separating file could be a solution.
I mean

endpoint.hpp contains full of the class definition. The class definition contains member functions declaration but not contains definition.
endpoint_impl_xxx.[hpp|ipp contains member function definitions. xxx can be various name. e.g. sync async publish subscribe acquired.
endpoint.hpp includes endpoint_impl_xxx.[hpp|ipp]s from the bottom line.

I'd like to allow to user both async/sync API call from the same endpoint object. Boost.Asio support it. I don't want to limit it on the upper layer, mqtt_cpp.

But you made async_client.hpp and sync_client.hpp specifically because allowing sync and async on the same object doesn't work.
Further, right now, it's not possible to pass an mqtt::server instance to another type, like test_broker, and have the passed in instance decide if it's async or sync. In order to make test_broker.hpp use the server asynchronously, the code for test_broker.hpp has to be changed to explicitly call the async versions of functions.

I think that we need to confirm what is the real problem with the big one file.

The file is difficult to navigate, making it hard to understand how things work. It's just a huge maze.
Functionality is very closely intertwined, making it difficult to replace logic with alternative choices.
A lot of repeated functionality (There are 16 versions of async_unsubscribe(), 6 of acquired_async_unsubscribe, and 4 acquired_async_unsubscribe_impl).
Slower compile times. For example: I don't want to use the syncronous api at all. But my build still needs to pay the cost of parsing the code, even if the compiler doesn't generate machine code for it.
The current code is very heavily coupled, but low cohesion. Endpoint.hpp does basically everything, but there are several parts of it that don't interact with other parts. There's several ways it can be broken up into smaller parts, it's just a question of which design to use.

endpoint.hpp contains full of the class definition. The class definition contains member functions declaration but not contains definition.

This would be an improvement, but it doesn't address all of my concerns.

I'd like to allow to user both async/sync API call from the same endpoint object. Boost.Asio support it. I don't want to limit it on the upper layer, mqtt_cpp.

But you made async_client.hpp and sync_client.hpp specifically because allowing sync and async on the same object doesn't work.

It is just a wrapper. The purpose is avoid misuse.
If I use client.hpp, I can use mixed operation.

Further, right now, it's not possible to pass an mqtt::server instance to another type, like test_broker, and have the passed in instance decide if it's async or sync. In order to make test_broker.hpp use the server asynchronously, the code for test_broker.hpp has to be changed to explicitly call the async versions of functions.

This is the functionality just I want to keep. Broker implementer can choose async_publish() or publish(). test_broker.hpp is just for test purpose. So I use sync one. The benefit of sync one is easy to implement. User doesn't need to care about resource management. It is good enough for test broker.
I think that switching sync/async from outside is not practical.  Concept is slightly different.
When I use Boost.Asio, I can choose send() or async_send()` via socket.
https://www.boost.org/doc/libs/1_70_0/doc/html/boost_asio/reference/basic_stream_socket/async_send.html
https://www.boost.org/doc/libs/1_70_0/doc/html/boost_asio/reference/basic_stream_socket/send.html
I want to continue to provide the similar functionality on mqtt_cpp.

I wrote the design decision introducing Sync and Async client.
https://github.com/redboltz/mqtt_cpp/pull/208#issuecomment-480594751

Why don't you create asnyc_client and sync_client as the base classes of client?

It requires big design change.
I don't have good design concept.

I think that I can accept something good mixin approach.
Here is code image:
struct endpoint_base {};

struct async_endpoint {
    async_endpoint(endpoint_base& base):base(base) {}
    endpoint_base& base_;
};

struct sync_endpoint {
    sync_endpoint(endpoint_base& base):base(base) {}
    endpoint_base& base_;
};

struct endpoint : publish sync_endpoint, public sync_endpoint {
    endpoint(endpoint_base& base):async_endpoint(base),  sync_endpoint(base){}
};

I think that ultimately 3 layers might be best.

Is this similar to your 3 layers approach?

A mixin approach would be similar to what I described, and I'd be happy to help implement that.

Thank you.

The file is difficult to navigate, making it hard to understand how things work. It's just a huge maze.
Functionality is very closely intertwined, making it difficult to replace logic with alternative choices.
A lot of repeated functionality (There are 16 versions of async_unsubscribe(), 6 of acquired_async_unsubscribe, and 4 acquired_async_unsubscribe_impl).
Slower compile times. For example: I don't want to use the syncronous api at all. But my build still needs to pay the cost of parsing the code, even if the compiler doesn't generate machine code for it.
The current code is very heavily coupled, but low cohesion. Endpoint.hpp does basically everything, but there are several parts of it that don't interact with other parts. There's several ways it can be broken up into smaller parts, it's just a question of which design to use.

I think that this approach can achieve the benefit you mentioned above. In addition, it can achieve providing both sync/async API on the one endpoint object.
I can accept async_endpoint has publish() function not async_publish() as you proposed.
Mixed in endpoint can provide async_publish() as follows:
struct endpoint_base {};

struct async_endpoint {
    async_endpoint(endpoint_base& base):base(base) {}
    void publish(...); // async publish
    endpoint_base& base_;
};

struct sync_endpoint {
    sync_endpoint(endpoint_base& base):base(base) {}
    void publish(...); // sync publish
    endpoint_base& base_;
};

struct endpoint : public sync_endpoint, public sync_endpoint {
    endpoint(endpoint_base& base):async_endpoint(base),  sync_endpoint(base){}
    void publish(...) {
        sync_endpoint::publish(...);
    }
    void async_publish(...) {
        async_endpoint::publish(...);
    }
};

But I don't want to introduce virtual function based polymorphism.
I mean
struct endpoint_base {
    ~endpoint_base() {}
};

struct async_endpoint : virtual endpoint_base {
    async_endpoint(endpoint_base& base):base(base) {}
    void publish(...); // async publish
    // endpoint_base& base_; // remove composition, use inheritance
};

struct sync_endpoint : virtual endpoint_base {
    sync_endpoint(endpoint_base& base):base(base) {}
    void publish(...); // sync publish
    // endpoint_base& base_; // remove composition, use inheritance
};

struct endpoint : public sync_endpoint, public sync_endpoint {
    endpoint(endpoint_base& base):async_endpoint(base),  sync_endpoint(base){}
    void publish(...) {
        sync_endpoint::publish(...);
    }
    void async_publish(...) {
        async_endpoint::publish(...);
    }
};

I can't accept the approach above.

I think that one of the big issue of mixed in approach is how to treat well std::enable_shared_from_this. And I don't have a good solution yet.
Anyway, let's start implementing.
I want to discuss based on small running code. https://wandbox.org/ will help us.


WriteImage squeezes 4th and later dimensions of size 1

It appears that WriteImage squeezes 4th and up dimensions when they have a size of 1 when reading the image back using ReadImage.
Example:
image = image = sitk.Image([64,64,64,1], sitk.sitkFloat32)
sitk.WriteImage(image, 'temp.nii.gz')
image = sitk.ReadImage('temp.nii.gz')
print(image)

In the example above, the image read back is 3-dimensional instead of 4.
Using SITK 2.0.2

Bug is in ITK, and has to do with the reading, not the writing. Using nibabel illustrates this:
import SimpleITK as sitk
import nibabel as nib

image = sitk.Image([64,64,64,1], sitk.sitkFloat32)

print(image.GetSize())

sitk.WriteImage(image, 'temp.nii.gz')
image = sitk.ReadImage('temp.nii.gz')

print(image.GetSize())

image = nib.load('temp.nii.gz')
print(image.shape)

Requires a bit more digging to see where this happens in ITK.

Hello @nicktasios,
A quick ad-hock solution using SimpleITK:
image = sitk.JoinSeries([sitk.ReadImage('temp.nii.gz')])

Looks like this is intentional in ITK, see this code.
That code should not have been accepted. The user can squeeze the 3D image out of the 4D image after reading. The reader shouldn't try to guess that the image was incorrectly written as 4D instead of 3D. The problem is that this code and behavior have been in ITK for 13 years so if it is changed it may cause problems for any code written in the past 13 years that relies on this "feature". I will create a bug report on ITK's issue tracker, but it likely won't be changed because of the history.

Hi @zivy , thanks for looking into it. Indeed, this is not behaviour I'd expect, and it caught me by surprise. Writing a file and reading-back something different is not what you'd generally expect. I would think that at the very least there should be a flag controlling the pruning.
Your temporary solution unfortunately doesn't work in my case since I don't know a priori if the image I'm reading is indeed 4D. I would have to use a different loader like nibabel to first find out the true dimensions.

Closing this bug report after opening one on the ITK issue tracker.


create fresh project nuxt js but got error

Hi i got issue after npx create-nuxt-app. im using node version 16.16
npx create-nuxt-app learn-nuxt-js-v2 --edge

create-nuxt-app v5.0.0
✨  Generating Nuxt.js project in learn-nuxt-js-v2
? Project name: learn-nuxt-js-v2
? Programming language: TypeScript
? Package manager: Npm
? UI framework: Tailwind CSS
? Template engine: HTML
? Nuxt.js modules: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Linting tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Continuous integration: GitHub Actions (GitHub only)
? What is your GitHub username? andorukun
? Version control system: Git
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org
/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email
 at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm ERR! code EACCES
npm ERR! syscall link
npm ERR! path /Users/andrewlim/.npm/_cacache/tmp/3536c822
npm ERR! dest /Users/andrewlim/.npm/_cacache/content-v2/sha512/e2/00/e7b73ae27c59c212fca83bc3eac890e682e5e054fc4a888c6b04a8c8a30bcbf65f8debad7debeef65d5611f0105fd54bf5160b776c67af27eb049b17d
9cf
npm ERR! errno -13
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 501:20 "/Users/andrewlim/.npm"

npm ERR!      /Users/andrewlim/.npm/_logs/2023-07-17T08_06_39_162Z-debug-0.log

/Users/andrewlim/.npm/_npx/ea7c6e7510ea3309/node_modules/sao/lib/installPackages.js:108
        throw new SAOError(`Failed to install ${packageName} in ${cwd}`)
        ^

SAOError: Failed to install packages in /Users/andrewlim/Development/Nuxt Project Example/nuxt-js-project/learn-nuxt-js-v2
    at ChildProcess.<anonymous> (/Users/andrewlim/.npm/_npx/ea7c6e7510ea3309/node_modules/sao/lib/installPackages.js:108:15)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  __sao: true
}

can anyone same problem like me?
Version
create-nuxt-app: v5.0.0

This is not a Nuxt issue - try following the instructions in the error message to resolve.


Fixed typo for Unity Editor version 2020.3.6f1.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Similar to the previous PR. The link is valid (I didn't change it), but there's some error with the pipeline.
##[error] Installer https://download.unity3d.com/download_unity/338bb68529b2/Windows64EditorInstaller/UnitySetup64-2020.3.6f1.exe
##[error] Result: Failed
##vso[task.logissue type=error] Error occurred while downloading installer from https://download.unity3d.com/download_unity/338bb68529b2/Windows64EditorInstaller/UnitySetup64-2020.3.6f1.exe. 0x80072EE2.
Error information:
Http Response: OK
Http Reason Phrase: OK

/azp run


Upgrade the build environment

Updates:

[x] Upgrade the build environment (a docker with new version of rust).
[x] Format all source codes by rustfmt (cargo fmt --all  -- --emit files).
[ ] Fix sodiumoxide .

What's the problem of 'sodiumoxide' ?

Nothing changed, only rebase and upgrade docker.
Waiting for building the new docker, then rerun the CI.


fix: socket io

This solution is working for me, thanks

What is status of this ?

@dliuproduction would it be possible for you to approve this PR please ? This is a breaking bug.

Hi, I think this would solve the following open discussion:
https://github.com/botfront/botfront/discussions/979
Also I think a version of the compiled JS needs to be added to CDN.
e.g<EMAIL_ADDRESS>e.g.: https://storage.googleapis.com/cdn.botfront.cloud/botfront-widget-latest.js
Thanks!

Please add CDN of javascript for

Thank you @MatthieuJnon and @kenrilea  :)


MKL optimized Tensorflow does not support EIGEN_USE_MKL_ALL currently.

Can one of the admins verify this patch?


Hotfix block selection linebreaks in conhost

This regressed in a1f42e8 which only made changes to Windows Terminal
but forgot to make equivalent ones in OpenConsole/conhost.
Without this fix, line breaks in block selections are missing if the
line doesn't force a wrap via an explicit newline.
Closes #15153
Validation Steps Performed

Run Far or print long lines of text
Trigger block selection via Ctrl+M or Edit > Mark
Clipboard contains N-1 newlines lines for N selected rows ✅

I'm cool with this, but since openconsole isn't shipping in 1.17 or 1.18 for its UI, it doesn't meet the servicing bar.

Eh, I thought since it's basically a one line change, we might as well ship it... But I'm personally a bit impartial about it.


WIP [53440] iOS: Increased spacing at the bottom of how it works page

Closing this and replacing with a new one


update counters doesn't work

in Mailer.php:276-293
counter per language is broken and not a requirement

replace the "every-translation" counter with a the-on-node  counter
Needs a better knowledge of the  simplenews spooler.

Fixed as per https://www.drupal.org/project/simplenews/issues/3106374


Unable to install package paho-mqtt==1.5.0: ERROR: Cannot install paho-mqtt==1.5.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Unable to install package paho-mqtt==1.5.0: ERROR: Cannot install paho-mqtt==1.5.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
After updating to core-2022.3.0. I receive this message.

my working install is throwing a similar error after the latest upgrade to core-2022.3.0
Setup failed for sengledapi: Requirements for sengledapi not found: ['paho-mqtt==1.5.0'].

Seeing other users have this issue, I've decided not to upgrade to 2022.3 just yet. I did notice however that there are a bunch of forks of this repository, and one of them has a very recent commit (an hour ago) that changes the paho-mqtt version:
https://github.com/nate-marshall/ha-sengledapi/commit/18356be6674770bdc2a1323df33c9e773240d956
Is that the change that is required to fix this issue? If so can the same thing be done to this main repository?

I looked in to the change @Valdorama linked to and removing the requirement failed for me but updating paho-mqtt==1.5.0 to paho-mqtt==1.6.1 did work for me so far with minimal testing.

Thanks @BeardUp. How do you actually deploy this change? Do you just update the contents of manifest.json and then restart HA?

Yes, thats exactly what I did.

Thanks @BeardUp. How do you actually deploy this change? Do you just update the contents of manifest.json and then restart HA?

Where is that file, im sorry im new to this

JK i figured it out. thanks everyone lol

Where is that file, im sorry im new to this
/config/custom_components/sengledapi   - you can find your location of your config folder by navigating to your Configuration section in Home Assistant and then clicking on the Info tab.

SSH in to your server and navigate to your Home Assistant config folder. Then navigate to /custom_components/sengledapi  Once you are in the sengledapi folder, you should see the manaifest.json file. Use your text editor to make the update.

Do I just have to hard reset my instance? I still get a configuration issue when trying to restart HA through server control

Do I just have to hard reset my instance? I still get a configuration issue when trying to restart HA through server control

I think I got that too. I am running HA in a container to I just restarted the container. Yes, try the hard restart.

I also am new to Github... so looking at that link that shows the manifest.json. Do i completely remove the line that has the paho line in and leave the blank [] or does it need both?

I also am new to Github... so looking at that link that shows the manifest.json. Do i completely remove the line that has the paho line in and leave the blank [] or does it need both?

No, that threw an error and I could not restart HA. I updated mine from 1.5.0 to 1.6.1 then saved and restarted.

Upgraded to 2022.3, sengled integration failed, made the change to manifest.json, restarted by HA container -> all working now.

Hopefully this helps. I now this needs alot more help, but I have update the mqtt requirement as stated in this thread. I have not tested the release.

Changing it to paho-mqtt>=1.5.0 should keep it working if  paho-mqtt updates.

In case somebody sees this. Issue has been fixed in master. In HAC, redownload the "master" version.

HCAS>INTEGRATIONS>SEGLED>3 DOTS>REDOWNLOAD
scroll to the bottom of versions to find master
fixed it for me
Thanks all,
Gramps

So, i updated to Master and i still having this issue. Anyone else?

https://github.com/jfarmer08/ha-sengledapi/releases/tag/v0.2.3


Conditionally compiled availability annotations?

I tried to set up a GitHub workflow with tests on Linux (#60) (#63), but I discovered that the Swift 5.7 compiler is broken. In particular, it cannot parse the following in some situations. It works on Swift 5.8, and on Xcode 14.2 after I pushed a hot-fix, but it still fails on Swift 5.7 using Linux.
#if SBI && swift(>=5.8)
@available(iOS 16.4, macCatalyst 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4, *)
#endif

The supposed problem is that @available expects a declaration, which is provided below #endif.

Edit: It seems like this is a Swift 5.8 feature (SE-0367). If so, then why does it compile on Xcode 14.2?

The supposed problem is that @available expects a declaration, which is provided below #endif.

It seems like this is a Swift 5.8 feature: SE-0367. But why does it compile on Xcode 14.2 then?

You can try it like this:
#if SBI && swift(>=5.8)
@available(iOS 16.4, macCatalyst 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4, *)
extension NBKDoubleWidth {
#else
extension NBKDoubleWidth {
#endif

Sadly extension NBKDoubleWidth { does not count as a declaration:
#if SBI && swift(>=5.8)
@available(iOS 16.4, macCatalyst 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4, *)
extension NBKDoubleWidth {
#else
extension NBKDoubleWidth {
#endif // 🛑 Expected '}' at end of extension 🛑 Expected declaration
}      // 🛑 Extraneous '}' at top level

Arghhh. They should rewrite the compiler into Swift and redo the parser and macro preprocessor. Too many bugs. When you do a lot of metaprogramming it starts to crash on proper code. Had a couple of type workarounds in my libs because the compiler crashes non-stop.


check for multiple drivers of a net

Description
We had the problem that we accidently had multiple drivers for a net, which would have resulted in a short-circuit on the ASIC. There were no warnings about it in the OpenLane flow, so we requested warnings from yosys, and got a result now: https://github.com/YosysHQ/yosys/issues/3793
Proposal
Please ensure to use the "check" command of yosys to detect such issues.

check is called here https://github.com/The-OpenROAD-Project/OpenLane/blob/3bc9d02d0b34ad032921553e512fbe4bebf1d833/scripts/yosys/synth.tcl#L273. It seems that it is an issue that was recently fixed by yosys so we will look into updating yosys in OpenLane.

@thesourcerer8 do you have a specific test case where you faced this issue?

@thesourcerer8 Found it. Thanks


Some seed cause the model to fail to converge

I use knowledge distillation for ASR-wav2vec2, I discovered something interesting about seed. When using seed to init weight for model students, it causes the model to fail to converge.
Eg, when I use seed 1001, train loss and valid loss are always like this
epoch: 1, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.94 - valid loss: 3.97
epoch: 2, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.88 - valid loss: 3.04
epoch: 3, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.88 - valid loss: 2.98
epoch: 4, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.88 - valid loss: 2.97
epoch: 5, lr_model: 8.00e-01, lr_wav2vec: 9.00e-05 - train loss: 2.88 - valid loss: 2.98
epoch: 6, lr_model: 6.40e-01, lr_wav2vec: 8.10e-05 - train loss: 2.88 - valid loss: 3.04
epoch: 7, lr_model: 5.12e-01, lr_wav2vec: 7.29e-05 - train loss: 2.87 - valid loss: 3.02

But, when I use seed 1002, It's very normal
epoch: 1, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.74 - valid loss: 2.65
epoch: 2, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 2.21 - valid loss: 2.09
epoch: 3, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 1.67 - valid loss: 1.68
epoch: 4, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 1.39 - valid loss: 1.44
epoch: 5, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 1.23 - valid loss: 1.38
epoch: 6, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 1.13 - valid loss: 1.26
epoch: 7, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 1.04 - valid loss: 1.18
epoch: 8, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 9.71e-01 - valid loss: 1.06
epoch: 9, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 9.15e-01 - valid loss: 9.99e-01
epoch: 10, lr_model: 1.00e+00, lr_wav2vec: 1.00e-04 - train loss: 8.56e-01 - valid loss: 1.06

I never thought random seed affects so much, have you ever encountered this situation?

Deep learning mystery .... you could try replacing the scheduler with one containing a warmup instead.

Hello,
As Mirco explained, some initialization might be more problematic than others (e.g your model can get stuck in a local minima far away from the optimum solution due to the initialization, lr, lr schedule...).
As it seems that we have answered your question, I will close this issue. Feel free to reopen it if you need more information. Thanks! 😃


How to use early stop when training VGG16?

Hi, thanks for sharing your great work. Just wondering if we have a validation set, how can we use it for an early stop when training the VGG16 model in your case? I noticed you trained all epochs and saved the checkpoint of the last epoch as the final model for pruning.

Thanks for the question.
We would suggest to early stop if the group sparsity becomes stationary and the validation accuracy becomes satisfactory.
Once group sparsity is stationary, the checkpoint with the best validation accuracy serves as the better checkpoint to return than the last checkpoint. We will revise the logic in the next release of OTO framework.

Hi,
Thanks for your reply. Sorry, another question, how to apply OTO to the embedding layers? Will it be the same as applying in MLPs?
I am looking forward to your reply.

It depends, if the embedding layers are prescribed, i.e., they are not trainable, ZIG partition would skip these parameters. Otherwise, if the embedding layers are trainable, the ZIG should perform similarly to the fully connected or linear layers.

In particular, ZIG is essentially the minimal removal structure of DNN. If applying onto trainable embedding layer, we need to remove the same amount scalars from all embedding vectors to keep the followup operators valid.
If we stack all embedding vectors as an embedding matrix, where each column is one embedding vector, then similarly to the linear layer, each row serves as one ZIG.
Let me know if any further question.


CSP Error on fp.js

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
When using the filter by directly on a column the list should filter by that choice and not throw an error.
Observed Behavior
When using the filter by directly on a column in a list an error occurs. "Cannot read property 'replace' of undefined'. The filtering works by going to the filter icon to the right but not directly on the columns.
Occurs on many browsers: Chrome Version 76.0.3809.87, Firefox 68.0 and Microsoft Edge 44.17763.1.0.
The error message from Chrome is (same on the others but in my own language):
suiteux.shell.header.98bb5695a3deb798f239.js:11 Refused to load the script 'https://r4.res.office365.com/footprint/v2.9/scripts/fp.js' because it violates the following Content Security Policy directive: "script-src 'self' https://contentstorage.osi.office.net https://swx.cdn.skype.com https://res.delve.office.com https://lpcres.delve.office.com https://static.sharepointonline.com https://widget.uservoice.com https://by2.uservoice.com https://www.bing.com/api/maps/ https://www.bing.com/rms/ https://spoprod-a.akamaihd.net https://fabriciss.azureedge.net https://publiccdn.sharepointonline.com https://ajax.aspnetcdn.com https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-07-19-sts_20190725.002/ https://r1.res.office365.com https://webshell.suite.office.com https://shellux.msocdn.com https://shellprod.msocdn.com https://shellppe.msocdn.com https://shellprod.msocdn.com https://c1-excel-15.cdn.office.net https://c1-onenote-15.cdn.office.net https://c1-powerpoint-15.cdn.office.net https://c1-visio-15.cdn.office.net https://c1-word-view-15.cdn.office.net 'unsafe-eval' 'nonce-698a3de8-180a-49d2-ba96-9f085a70f06d'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
As you can see the r4.res.office365.com is not included. And the pages response headers include this CSP row (also seen in the error):
content-security-policy: script-src 'self' https://contentstorage.osi.office.net https://swx.cdn.skype.com https://res.delve.office.com https://lpcres.delve.office.com https://static.sharepointonline.com https://widget.uservoice.com https://by2.uservoice.com https://www.bing.com/api/maps/ https://www.bing.com/rms/ https://spoprod-a.akamaihd.net https://fabriciss.azureedge.net https://publiccdn.sharepointonline.com https://ajax.aspnetcdn.com https://spoprod-a.akamaihd.net/files/odsp-next-prod_2019-07-19-sts_20190725.002/ https://r1.res.office365.com https://webshell.suite.office.com https://shellux.msocdn.com https://shellprod.msocdn.com https://shellppe.msocdn.com https://shellprod.msocdn.com https://c1-excel-15.cdn.office.net https://c1-onenote-15.cdn.office.net https://c1-powerpoint-15.cdn.office.net https://c1-visio-15.cdn.office.net https://c1-word-view-15.cdn.office.net 'unsafe-eval' 'nonce-a711bf48-0f64-47bc-999f-dc70ff16a343'
Sharepoint Online Modern on a communication site is the one we are using with version:
vti_encoding:SR|utf8-nl
vti_extenderversion:SR|<IP_ADDRESS>24
Have tried on multiple tenants and multiple lists with the same result.
Any suggestions or workarounds?
Steps to Reproduce
Make a modern communication site in SPO and make a list. Then try to filter by a specific value in a column and the error should appear. Do not filter by the icon because it works there.

I believe this is an issue with the OOTB experience, not custom code as I don't see anything in your issue related to a custom component you're working on, correct?
Thank you for your submission. This GitHub issue list is targeted only for SharePoint development issues. If this is a capability question/discussion, please use the SharePoint TechCommunity.
If it is an issue is related to out-of-the-box capabilities of SharePoint or not related to SharePoint, we cannot process is through this channel. Please submit your finding using the Tenant administrator support channels in your tenant or using Premier support, if that’s available for you. Sorry for the inconvenience.


Remove old note about EKS

What this PR does / why we need it:
This is no longer the case 😄
Release note:
NONE

/milestone v0.7
/cc @DanielMorsing

/lgtm


Markdown list generation bug

Hi all,
I've been really impressed with this project. Just wanted to inform you about a bug I seem to have discovered.
I made a very simple list (GitHub documentation): (formatting is messed up)

1. Item 1
2. Item 2
3. Item 3
   * Item 3a
   * Item 3b
4. Item 4
5. Item 5
6. Item 6

GitBucket does not seem to process the list after the sub points correctly. It marks items 4,5,6 as 1,2,3
making it looks like two separate lists.
Thanks

1. Item 1
2. Item 2
3. Item 3
    * Item 3b
4. Item 4
5. Item 5
6. Item 6

... looks OK on Github and on Gitbucket:

I don't see any bug.

Gitbucket 3.0 running on Windows 7 IIS
New Issue (write):

preview:

Oh ok. I see. You have to have 4 spaces on the sub item before it becomes visible.


ARFaceTrackingConfiguration not recorder correctly

Rendering of face mesh is absolutely wrong

I also encountered the same problem and look forward to the answer

Rendering of face mesh is absolutely wrong

You can set
contentMode = .aspectFill
and then try again.

@

Rendering of face mesh is absolutely wrong

You can set contentMode = .aspectFill and then try again.

你是在哪儿设置的，我设置后还是变形的

@Ksen17 please provide screenshots of actual recorded image you see.
@cleexiang nobody understands you


thank u for your contribution, my email adress is<EMAIL_ADDRESS>

thank u for your contribution, my email adress is<EMAIL_ADDRESS>

Request the ultra-high precision model you trained and training code


[5.8] Use Name of Factory as Model

Use the name of factory as the model if --model is not specified
php artisan make:factory UserFactory

the Model will be User here

This is will works when you only enter Factory or when you write a name with no Factory
! strpos($name, 'Factory') ? 'Model' : ucfirst(str_replace('Factory', '', $name));

IMO, deleting the last 7 characters is “more correct”, and that was your intention also :)
Good PR, hopefully will make it into the core.

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


Areas masked out in certain situations

No idea why this is happening, but we need to investigate.

Closed by #10.


[fix][gws] errors during destroying all

Coverage increased (+0.01%) to 84.866% when pulling c51dd0e71ec2ba3606ef3af2ae7a0b3b07bc506f on fix-destroying-all into 00dbd81da2e13237f7e3f557c696df952d0b1cce on master.


Upgrade Go GRPC library to commit 3e7b7e58f491074e9577050058fb95d2351a60b0 [phab:D540]

Created by schroederc at 2015-10-06 17:01:44:

zarko accepted this revision at 2015-10-07 20:53:20

schroederc closed via commit 297d769e828d610eaeefdb4f36b35549135ed261 at 2015-10-07 21:04:48


Release v0.2.0: Tasty Tabule

Codecov Report

Merging #583 (1d8d8bf) into main (c76dbf6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #583   +/-   ##
=======================================
  Coverage   95.49%   95.49%
=======================================
  Files         112      112
  Lines       19008    19008
=======================================
  Hits        18151    18151
  Misses        857      857

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Get-SPOProvisioningTemplate - not working

Hello,
I am trying to use Get-SPOProvisioningTemplate but keep getting an error:
Connect-SPOnline https://abcdef.sharepoint.com/sites/prov_source -Credentials $cred
Get-SPOProvisioningTemplate -Out template.xml
Get-SPOProvisioningTemplate : Specified argument was out of the range of valid values.
Parameter name: controlId
At line:1 char:1

Get-SPOProvisioningTemplate -Out template.xml

  + CategoryInfo          : WriteError: (:) [Get-SPOProvisioningTemplate], ServerException
  + FullyQualifiedErrorId : EXCEPTION,OfficeDevPnP.PowerShell.Commands.Branding.GetProvisioningTemplate

The command runs ok for a while but it seems to crash when extracting the Page contents.
My site is pretty simple, a brand new team site with a few site columns and content types. Only home page with the documents library webpart on it.
Similar post: https://github.com/OfficeDev/PnP/issues/1127
Any idea?

Directly after you receive the error, in PowerShell, can you enter
$error[0].Exception.Stacktrace

and post the result of that command? Thanks!

PS C:\Users\Robert> $error[0].Exception.Stacktrace
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryImplementation(ClientRuntimeContext clientContext
, Int32 retryCount, Int32 delay)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectPageContents.ExtractObjects(Web web, ProvisioningTe
mplate template, ProvisioningTemplateCreationInformation creationInfo)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.SiteToTemplateConversion.GetRemoteTemplate(Web web, Provi
sioningTemplateCreationInformation creationInfo)
at OfficeDevPnP.PowerShell.Commands.Branding.GetProvisioningTemplate.GetProvisioningTemplateXML(XMLPnPSchemaVersion
schema, String path)
at OfficeDevPnP.PowerShell.Commands.Branding.GetProvisioningTemplate.ExecuteCmdlet()
at OfficeDevPnP.PowerShell.Commands.SPOCmdlet.ProcessRecord()

I managed to make it work... not 100% sure why.
I decided to debug the code in OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectPageContents so I forked it and started debugging with VS attached to powershell.exe
At the same time I edited my wikipage (homepage) on the site to add a bit of content.
As I started debugging, it worked on the first try, no error or anything... My guess is that either the page was messed up and it fixed itself when I added some content (I love SharePoint RTE) or I had an older version of the code library code in memory and it caused some error?
Hope it helps someone

Hi, i have had the same issue on Wiki Pages. As @aboredman stated, if you clean the wiki field value from "old" Webpart Id's it works.
In my case i have had a default Teamsite (O365) and removed the microfeed and document library webpart's.
After that the wikiField Content still had this Markup:

After removing this Markup with Ribbon Action "Edit Source", i could get the ProvisioningTemplate with -Handlers Pages, PageContents

Thanks Cedric. I managed to replicate the issue and correct it using your method.

Hi, I have had the same issue but my error result was different:
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryImplementation(ClientRuntimeContext clientContext, Int32 retry
Count, Int32 delay)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectTermGroups.CreateTerm[T](Web web, Term modelTerm, TaxonomyItem p
arent, TermStore termStore, TokenParser parser, PnPMonitoredScope scope)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectTermGroups.ProvisionObjects(Web web, ProvisioningTemplate templa
te, TokenParser parser, ProvisioningTemplateApplyingInformation applyingInformation)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.SiteToTemplateConversion.ApplyRemoteTemplate(Web web, ProvisioningTemp
late template, ProvisioningTemplateApplyingInformation provisioningInfo)
at SharePointPnP.PowerShell.Commands.Branding.ApplyProvisioningTemplate.ExecuteCmdlet()
at SharePointPnP.PowerShell.Commands.SPOCmdlet.ProcessRecord()
I try implement a remote provisioning site.
Thanks for all support


How to retrain card.io model to include non-embossed digits?

As mentioned in all issues, card.io fails in detecting non-embossed digits on credit cards.
There are few questions regarding this:

Is the model not trained on OCR-B digits, or is this problem related to non-embossed only?
Is there any hacky way to implement this using Tesseract, or a new model using Tensorflow?
Why are non-embossed cards a problem?

So I tried training on a TF model with computer generated digits, which gave little accuracy. nearly 50%
Then I found out a repo which does it.
https://github.com/SmartEngines
This works as expected.
I would be happy to train a tf model on non embossed cards if anyone provides me with a dataset, since computer generated datasets are futile here.

does anyone got solution of non-embossed card digits scan ?


New Contributor Added

Description and hyperlink added. Thanks!

Thanks @TheDeola ! You just got rewarded for your contribution!  Claim it now🎉


Update nodes.md to remove ambiguity

I think the sentence 'Each node contains the services necessary to run Pods, managed by the control plane.' is a little bit ambiguous because it is not clear which word the 'managed' modifies.
I think it can be 'node', 'services', and even 'Pods' semantically, but I think it should be clear.
when I see this sentence translated by all the other languages, they are translated in many ways which are semantically different.
I thought the original intention is that 'managed' modifies 'node' and I made it clear.

This fix makes sense to me.
/lgtm

/approve


Download Maven from apache.org

Previously, Maven distributions were downloaded from Heroku's JVM language S3 bucket. These distributions were custom made for Heroku. The main benefit was that their internal directory structure matched what we wanted to have in the cache layer. These distributions also had support to pre-priming the cache for that Maven version, but all currently available Maven versions didn't use that feature.
This PR changes the download source to apache.org, the same location Maven Wrapper fetches the distributions from. To make that work, the installation logic had to change slightly due to the different directory layout. This also means the scripts to package the custom Maven distributions can be removed.
Ref: GUS-W-13912071

I forgot to say - thank you for the detailed/clear PR description - it helped my understand a lot :-)


3D grid for sphere instances generated randomly

It was added a knob to setup the number of spheres rendered in the scene. One sphere uses one drawcall.
It renders up to 3000 spheres.

This PR added a 3D grid of sphere instances generated randomly.

Ready for review.

Ready for review!

I rebased this PR with the origin/main branch. I think it is ready to be merged.

Ready for review.

I declined to include a deterministic random number generator. This is because the generated random numbers can vary based on how the shuffle method is implemented. To simplify things, I am reverting to the original approach of using JSON files to generate deterministic random numbers for the sphere indices.

I declined to include a deterministic random number generator. This is because the generated random numbers can vary based on how the shuffle method is implemented. To simplify things, I am reverting to the original approach of using JSON files to generate deterministic random numbers for the sphere indices.

Which PRNG implementation can vary?
Isn't https://en.cppreference.com/w/cpp/numeric/random/mersenne_twister_engine guaranteed to behave the same?
std::mt19937 gen(my_seed);
std::shuffle(my_vector.begin(), me_vector.end(), gen);

It's std::shuffle, which can vary between different standard libraries.

😢.... thanks!

Although a deterministic shuffle takes 3 lines to implement.

Yes, since this would be used to shuffle not only drawcalls, but also attributes etc, we might want to have a proper shuffle function than, and store the seed in the config (instead of storing the generated sequence in a json file)

Although a deterministic shuffle takes 3 lines to implement.

Yes, since this would be used to shuffle not only drawcalls, but also attributes etc, we might want to have a proper shuffle function than, and store the seed in the config (instead of storing the generated sequence in a json file)

MS's implementation is basically
template <typename Iter, typename F>
void vs_shuffle(Iter begin, Iter end, F&& f) {
  size_t count = end - begin;
  for (size_t i = 1; i < count ; i++) {
    using std::swap;
    swap(begin[i], begin[f() % (i + 1)]);
  }
}

glibc's shuffle have a specialization for count < f() / count

Thanks for the feedback. I added an own implementation for the Shuffle function and I used a deterministic random number generator as suggested. Ready for review.


Retrolambda doesn't strip calls to addSuppressed when using try-with-resources in 3.3.0

lint produces a warning about this issue (and I've checked generated files as well - 3.2.5 ok, 3.3.0 broken)
classpath 'com.android.tools.build:gradle:2.2.0'
classpath 'me.tatarka:gradle-retrolambda:3.3.0'

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

minSdkVersion 15

classpath 'com.android.tools.build:gradle:2.1.3' doesn't work, too

This is not the right project for that issue. You want https://github.com/evant/gradle-retrolambda

@JakeWharton I've checked 3.2.5 + retrolabda 2.3.0 and it is still broken, so something definitely changed in plugin itself (maybe some compatibility not passed properly?).

@JakeWharton ic, my bad

https://github.com/evant/gradle-retrolambda/issues/208


UVM Create possible nil dereference

Could nil dereference if passed options is nil.

So? Options is not user input. We should only protect against nil deref on user input (OCI specs, etc.).

You added this check in a recent PR (without review). It should be removed.

UVM is still a work in progress - full end-to-end review remains a little way off (but close). The added nil-dereference check is valid.


Integration with Bootstrap grid system

Hey everyone,
First of all, congratulations on the nice library :)
I'd like to know whether it's possible to make it work with an arbitrary number of rows when we use Bootstrap grids, for example. In my example, it only works with a single row:

Actually, it's the same behaviour as RubaXa/Sortable's List B and Multi examples: https://rubaxa.github.io/Sortable/

Hey @eliseumds!
As long as your elements are of equal width and height, you'll be able to enable grid sorting by passing a value of 'xy' to the ˋaxis` prop of your enhanced SortableContainer component.

Of course, it was in the docs :S Thanks @clauderic!

Oh, it worked so well! I had an outdated version installed lol

How beautiful is it? :)


Update headers to 1.3.261

Skip extension: VK_AMDX_shader_enqueue
Deal with KHR suffix's VkFlags64 for ToString

CI gfxreconstruct build queued with queue ID 22283.

CI gfxreconstruct build # 3082 running.

CI gfxreconstruct build # 3082 passed.


[Backport - Mitaka] Change default console to novnc

This commit does the following:

Add nova_console_type: novnc into the osa default variable file
Make the necessary changes in maas for the console check to support
both novnc and spice
Change the rpc_support role to conditionally include the spice-specific
bit
Add an f5 'pool part' in the f5-config.py script for the novnc console
type

This is not a clean backport, the changes to make this work in mitaka are:

Added vars_files to the setup_maas.yml playbook so it can utilize the
nova_console_type variable
Defined the nova_console_port in the console check, since this
variable isn't used in mitaka.

Connects https://github.com/rcbops/u-suk-dev/issues/131
(cherry picked from commit 5be24a69104bf1f4268e63e1638bf6d2b8868b97)
Conflicts:
scripts/f5-config.py

recheck_ceph

recheck_upgrade

recheck_upgrade


Proposal: go/list adds another flag to support showing major upgrade available for module

⚠ DEPRECATED ⚠
Please see the linked issue that has replaced this one.
Proposal
Currently, with SIV there isn't an automated way to understand that you may want to upgrade a package to a new major.
For example, if I have a mod that looks like this:
module github.com/test/test

go 1.14

require (
	github.com/peterbourgon/ff v1.7.0 // indirect
	rsc.io/sampler v1.2.1 //indirect
)

and I use go list like so:
go list -m -u all

I am going to get output like this:
github.com/test/test
github.com/BurntSushi/toml v0.3.1
github.com/davecgh/go-spew v1.1.1
github.com/mitchellh/go-wordwrap v1.0.0
github.com/pelletier/go-toml v1.6.0 [v1.7.0]
github.com/peterbourgon/ff v1.7.0
golang.org/x/text v0.0.0-20170915032832-14c0d48ead0c [v0.3.2]
golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7 [v0.0.0-20191204190536-9bdfabe68543]
gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405 [v1.0.0-20200227125254-8fa46927fb4f]
gopkg.in/yaml.v2 v2.2.4 [v2.2.8]
rsc.io/sampler v1.2.1 [v1.99.99]

Now github.com/peterbourgon/ff as a module actually has a v2 and a v3 and I would like go list to tell me of their existence sort of like pkg.go.dev does now when I visit the versions page:

Adding a flag to go list seems like a good step to signal to a user that they may want to upgrade their package to a newer major.

The presence of a new major version does not necessarily imply lack of support for the previous version.
For example, if /v2 is implemented in terms of /v3, then there is no pressing need for users to “upgrade”, as the previous API can remain supported indefinitely. (And, in that case, the upgrade is properly a task for an automated refactoring tool (such as proposed in #32816) instead of go list: it's more a matter of code cleanup than “upgrading” per se.)
On the other hand, if a package author intends to signal that part or all of a particular API is unsupported and cannot be expressed as a wrapper around a supported API, they can already mark its contents Deprecated to discourage new uses, and the deprecation comment can refer to the supported replacement explicitly. (So go list is probably still not the right place to surface this information, because it would be redundant: the user would need to read the documentation in order to understand the non-trivial migration path anyway, and tools such as staticcheck already display warnings about use of deprecated APIs.)
CC @jayconrod @matloob @ianthehat @marwan-at-work @myitcv @stamblerre

I agree with the above. However, the Go command should still provide a way to tell a user that a certain package has newer major versions. There two important use cases for this:

If you are trying to go get a package, and you don't realize there's a /vN suffix, you could be a few major versions behind. I argue that "go getters" should try their best to read package documentation before running a go get, but I think it's still a valid use case.

You just might want to be able to list all major versions for a given module. Yes, to the machine, they are technically separate modules and can be even imported together. But to humans, it can be quite useful for many reasons such as discoverability, tooling/analysis or documentation. pkg.go.dev for example already does this (not sure how yet as it's still closed source): https://pkg.go.dev/github.com/InVisionApp/go-health?tab=versions

gopls also shows suggestions for the user to upgrade to the latest version of a module. https://github.com/golang/go/issues/38339 is tracking work on improving this behavior to be more user-friendly.

@stamblerre - this is really awesome, I am definitely going to keeping checking in on this!
@marwan-at-work - I agree with both of your points. I don't necessarily know whether go list is 100% the right place for this but it felt right for the time being. I also want to point out that it is my hope that surfacing these major versions (we don't even need to show their patch levels) would encourage user to read the docs and then decide if they wanted to upgrade. It's more of a nudge.
@bcmills - thanks for bringing in all of these other folks! RE: Deprecated I've not seen a project actually use this flag and I think its asking quite a bit of authors when technically a package could be seen as Deprecated when they stop providing minor + patch updates. I want the tooling to signal to users "hey you could upgrade" and push them toward reading the docs. Honestly, most users in their day-to-day workflow need all the help they can get when it comes to versions of packages.

I think its asking quite a bit of authors when technically a package could be seen as Deprecated when they stop providing minor + patch updates

A project could quite reasonably stop providing minor + patch updates without deprecating the API, simply because they are not making further changes to the old API and have no important open bugs to fix. (For example, I would not be surprised if github.com/golang/protobuf reaches that state very soon, because ~all of the improvements will be in the underlying implementation at google.golang.org/protobuf.)
Moreover, there is no guarantee that a maintainer will stop providing minor + patch updates to v1 just because they have released v2. (Many maintainers backport critical fixes to one or more previous versions, as the Go project itself does with Go releases.)
So it really is important to explicitly deprecate a package when it is no longer suitable for new usage.

I think its asking quite a bit of authors when technically a package could be seen as Deprecated when they stop providing minor + patch updates

A project could quite reasonably stop providing minor + patch updates without deprecating the API, simply because they are not making further changes to the old API and have no important open bugs to fix. (For example, I would not be surprised if github.com/golang/protobuf reaches that state very soon, because ~all of the improvements will be in the underlying implementation at google.golang.org/protobuf.)
Moreover, there is no guarantee that a maintainer will stop providing minor + patch updates to v1 just because they have released v2. (Many maintainers backport critical fixes to one or more previous versions, as the Go project itself does with Go releases.)
So it really is important to explicitly deprecate a package when it is no longer suitable for new usage.

I want the tooling to signal to users "hey you could upgrade" and push them toward reading the docs.

Maybe? But we don't want to induce “upgrade fatigue” when it isn't needed. (“You could upgrade” is very different from “you should upgrade”: using an older version of that API is fine if that API is maintained, but dangerous if that API is no longer receiving security fixes.)

Maybe? But we don't want to induce “upgrade fatigue” when it isn't needed.

I very much agree with this. I think having a flag in go list (that is not on by default) should make it that users are dealing with minor versions most of the time but they can run it with some other flag that then will tell them about packages that have majors available?
The proposal doesn't go into how this flag operates, I want to come to agreement on the core idea of surfacing this information to users via the go tool so that they can take whatever meaningful action they see fit.

I think a flag like this could make sense as part of a larger vision for upgrading across major versions. But I don't think we should start taking steps on that path until we know where we're going.
The problem is there's not much a developer can usefully do with the go command, knowing a new major version is available. A major version is a breaking change by definition, so some refactoring is going to be required. Tools don't yet provide much help with that.
Another question is whether the new major version can coexist with the old version. A developer may have dependencies that still require the old version, so if they upgrade, they'll have to link packages from both versions into the same project. If there's global state, that can be a problem. Ideally, the author of the new major version has taken care of that, but it's not always the case in practice.

This is now deprecated in favor of a combine proposal that is linked to this issue

Retracted.


Upstream Inlay Hints

Now that LSP supports inlay hints, and rust-analyzer has upstreamed them it makes sense to upstream inlay hints too so we can finally use the latest version of rust-analyzer instead of the backdated version which uses the legacy system (#73).
There are a few things that need to happen before this PR is merged, I haven't updated the config files to expose all the new features in rust-analyzer as I am not sure what they are and inlay hints appear to still be a bit early days as they're a bit busted at least on my machine (see this comment).
I have gone ahead and removed all the relevant inlay hint code as it doesn't appear to be required with the new system. rust-analyzer.inlayHints.smallerHints appears to be broken as well. The other parameters relating to inlay hints seem to work though.
Inlay hints can be enabled in the latest github dev version of LSP by setting "show_inlay_hints": true in LSP's settings.
Thanks,
Aaron.

I appreciate your work but I think it will be more efficient if I just do this and more in a separate PR since we should also update settings and schema to match new server version.

Replaced by https://github.com/sublimelsp/LSP-rust-analyzer/pull/77

Cheers mate I'm glad it's being looked at!


[v2 bug]  error on set_size and set_position: invalid value: map, expected map with a single key

Describe the bug
I can no use setSize and setPosition, this doesn't happen on other beta versions but I run cargo update - npm update and an error start appearing.
[2024-04-13][00:01:37][ERROR][webview::unknown]  "Unhandled Rejection - invalid args value for command set_size: invalid value: map, expected map with a single key"
[2024-04-13][00:01:37][ERROR][webview::unknown]  "Unhandled Rejection - invalid args value for command set_position: invalid value: map, expected map with a single key"
Reproduction
just using the setSize or setPosition methods on JS
const webview = getCurrent();
const screenWidth = Math.floor(window.screen.width * window.devicePixelRatio);
const screenHeight = Math.floor(window.screen.height * window.devicePixelRatio);
webview.setSize(new PhysicalSize(screenWidth, screenHeight));
Expected behavior
normal work
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 123.0.2420.81
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.77.1 (7cf61ebde 2024-03-27)
    ✔ cargo: 1.77.1 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.10.0
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 2.0.0-beta.14
    - tauri-build [RUST]: 2.0.0-beta.11
    - wry [RUST]: 0.39.0
    - tao [RUST]: 0.27.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.7
    - @tauri-apps/cli [NPM]: 2.0.0-beta.12

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: dist
    - framework: React

Stack trace
No response
Additional context
No response

I am facing the same problem on Windows 10 and Tauri 2.0.

Duplicate of https://github.com/tauri-apps/tauri/issues/9370, will be fixed in the next release by https://github.com/tauri-apps/tauri/pull/9376


Migrating from manual pivotRole to cdkRole makes table shares unrevokable

Describe the bug
If you created a share using a manually created pivotRole then the resource link for that table will be owned by that role. pivotRole is the only role that can drop this resource link without additional permissions. Any other role that would want to drop this resource link would need to be granted explicit drop permissions.
If you then switch data.all from using manual pivot role to pivot role created with CDK (as we did when migrating from 2.2 to 2.3) and then attempt to revoke a table share that was created with the old role then the revoke will fail with error like this:
Failed to revoke S3 permissions to table gidmetadata from source account 123//us-east-1 with target account 123/us-east-1 due to: An error occurred (AccessDeniedException) when calling the DeleteTable operation: Insufficient Lake Formation permission(s): Required Drop on foo_table
This happens because the new pivotRole-cdk does not have drop permissions on the table because it is not the owner of that table.
My proposal would be to either run an upgrade script on all environments to update all resource links to get a drop permission or add a check whether the new role has a drop permission and if not to grant it to itself before dropping. In general I think it's a weird glitch that LF ask LakeFormation admins to have DROP before dropping.. I think that should be reported as a bug.
How to Reproduce

create a table share using manually created pivot role
switch data.all to use cdk pivot role
attempt to revoke the table share

Expected behavior
Revoking should work after switching from manually created pivotRole to automatically created one.
Your project
No response
Screenshots
No response
OS
Linux
Python version
3.9
AWS data.all version
2.3
Additional context
No response

Hi @zsaltys thanks for opening an issue. This is actually an error that should be solved by the automated tasks that update the dataset stack and sync tables. Let us have a look and get back to you

Hi @zsaltys we confirm that this is a bug and we are working on a fix in https://github.com/data-dot-all/dataall/pull/1055. Instead of approaching it as a migration issue, we will add the grant as a robustness measurement to ensure even manual changes or inferences from customers do not result in failed revoked tables.
The PR adds the grant of DROP permissions as a preliminary check to the deletion of the resource link tables.

Implemented sharing guardrails as part of PR #1055 - closing this issue as complete, please re-open if any additional comments / concerns


Occasional crash

This is built from master at 6c1579c
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/main.rs:414:37

Haven't yet worked out to reproduce it.

It looks like IDE send a did_change_text_document notification with missing range.

I guess so - I turned on tracing and this is what appears in the log:
[Trace - 10:17:03 PM] Sending notification 'textDocument/didChange'.
Params: {
  "textDocument": {
    "uri": "file:///home2/len/foo/foo.scad",
    "version": 1
  },
  "contentChanges": [
    {
      "text": "\nfunction bar(x) = x * x;\n\nmodule bar() {\n  bAr = bar(2);\n  translate([0, 0, 0]) circle(r = 10);\n}\n\nuse<bar.scad>\n"
    }
  ]
}

It would be nice if the server didn't crash though :-)

BTW, it sent the entirety of the document in the text parameter, so maybe range is optional in that case?

@Lenbok which text editor/IDE do you use?

I am using emacs with lsp-mode. According to the lsp specs "An event describing a change to a text document. If only a text is provided it is considered to be the full content of the document.", so it seems a valid thing to do. (I don't know under what conditions emacs lsp-mode decides to do whole content vs ranged sections).

@Lenbok Try this https://github.com/Leathong/openscad-LSP/commit/6ead5f8452ab8a63f723779d398889763ed3eb6d.


A required delay when pressing Cmd key to trigger shortcuts like Cmd + Z

If on macOS you quickly press Cmd+Z, Cmd+S or a similar shortcut, as I usually do in the rest of 99% of software, nothing happens. Patrena requires more calm pressing, some delay in pressing Cmd so that the modifier is taken into account when pressing the next key, otherwise they get out of sync and are pressed "one after another".
I don't know exactly where the problem is here - in Panthera or in Defold. If in Defold, it can be solved by adding some short timer after releasing the modifier key.

Done in https://github.com/Insality/panthera/releases/tag/editor.804
Hotkeys should be handled a little bit better, please report how it feels

Works perfect! now Thanks!


Change retry count to isize

This might resolve the bug seen in https://github.com/film42/sidekiq-rs/issues/15
cc @justmark

Closing because this hasn't come up again. If someone runs into this bug (only one person has one time), let me know and we can take a look again.


Improve unit tests coverage of cellery init and test commands

Description:
Unit test coverage of init command should be increased after introducing the --project option.
Unit tests should be written to test the code related to cellery test command.

https://github.com/wso2/cellery/issues/919


i'm having difficulty running this tool

i installed go (armx64)
opened terminal on my mac
checked the version to ensure it was working
i cd to my go folder and ran the report and run commands

Thank you for letting me know about the difficulty you are experiencing running the tool. I'd be happy to assist you with this issue. Could you please provide me with some additional information?

Can you provide the specific error message or behavior you are experiencing when attempting to run the tool?
Could you please share the exact commands you ran in the terminal when attempting to run the tool, including any flags or arguments used?
Additionally, could you please provide any logs or error messages that were generated when you tried to run the tool?

With this information, I'll be better able to diagnose the issue and provide you with a solution.

I see. Try to install import-gitlab-commits first:
go install github.com/alexandear/import-gitlab-commits@latest

and execute:
import-gitlab-commits

Or run the following command with go run:
go run github.com/alexandear/import-gitlab-commits@latest

i have the same problem like that. when i run without export it will give this
10:50:35 main.go:14: Error: app run: get current user: get current user: GET https://gitlab.com/users/sign_in: 403 failed to parse unknown error format
when i run with export like
export GITLAB_BASE_URL=url
export GITLAB_TOKEN="token"
export COMMITTER_NAME="name"
export COMMITTER_EMAIL="email"
go run import-gitlab-commits
it will give error
cannot find package "import-gitlab-commits" in:
/usr/local/go/src/import-gitlab-commits

@alexandear Thank you for the useful package! Unfortunately, the command from the README didn't work for me, so I had to use go run github.com/alexandear/import-gitlab-commits@latest to get things running.
Otherwise, I get this error:
./import.sh: line 8: import-gitlab-commits: command not found

Should the README be updated?

@kubk thanks, updated README.
Also, you could extend PATH with $GOPATH/bin and import-gitlab-commits will work:
export PATH=$PATH:$(go env GOPATH)/bin

https://go.dev/doc/gopath_code#GOPATH


Return pending transactions in batches

Feature request
Return BatchedResponse<Vec<SignedTransaction>> instead of Vec<SignedTransaction>
Motivation
It's hard to decode on our side without BatchedResponse
Who can help?
@mversic

duplicate of #4072

Closing the issue in favour of the new one #4183


source descriptions lose formatting

the other day, making a source description, I noticed this field is no longer WYSIWYG as it was on OldCantus--I had to add html tags to get paragraph breaks, which was a little annoying (especially since I didn't know I would need to until after the fact.)
Today I noticed that this also affected some source descriptions of already existing sources:
https://cantus.uwaterloo.ca/source/693689:

vs
https://cantusdatabase.org/source/693689:

Huh, I see what you mean.
We have a special WYSIWYG editor for creating news articles which we could use here, but that would be overkill if I understand correctly - the issue is just that line breaks should be preserved, correct?

let me look into whether there's an easy way to preserve line breaks when displaying fields containing lots of text. I'd be really surprised if this was not a problem other people have already encountered and solved.

@jacobdgm The source linked here is still a big block of text; so is e.g. https://cantusdatabase.org/source/710572 even though in the edit page there are breaks

Is this expected?

All that's happening is that this change has not yet made its way to the staging or production servers. It's behaving as expected on my local setup.


hipBlasLt F8 support parity with rocBlas (HH_F8/F8B8/B8F8_H_S)

ticket: https://ontrack-internal.amd.com/browse/SWDEV-440166

Currently waiting for the PR that adds of F8 compute type in hipblas.
https://github.com/ROCm/hipBLAS/pull/798

Ongoing:
Add hipblaslt_hip_f8bf8_impl
Add hipblaslt_hip_bf8f8_impl
require HIP_R_8F_E4M3_E5M2FNUZ
require HIP_R_8F_E5M2E4M3_FNUZ


Upgrade to .NET 8

Closes #612

For now I update only .NET target, should I upgrade all corresponding dependencies also?

Yes, please

Made it in a separate commit, because I'm not sure that it makes sense to upgrade to preview versions which are available now.

Any updates?

I'll probably merge it soon and publish a -preview to nuget


@kanaabe => Update start, end, expired date passed to Sailthru to match their format

Problem
Follow up on https://github.com/artsy/force/pull/723, @sperle mentioned that Sailthru also expect specific date format "2012-06-01 10:05:00" and they can't parse our current ("2016-12-13T12:00:00.000Z") format.

Ah ha 👍


Resharper 10

Just installed the latest version into R# 10 RTM and no output appears in the output window.

Sadly, this is a bug in ReSharper. It's already been fixed, and a hot fix will be available in the next few days, likely sometime next week. There's a workaround in the release notes.


+textprop feature should not contain popup windows.  add +popupwin feature.

+textprop feature contains Text properties and Popup windows now.  But I think It is unreasonable that +textprop feature reminiscent of  Popup windows.

We've been trying to simplify the #ifdefs in the code.  I don't know a good reason to include popup windows and not text properties, or the other way around.  It's true that the FEAT_TEXT_PROP name is misleading.  But what would be better without making it very long?  FEAT_PROP_POPUP ?  FEAT_TXTPROP_POPWIN ?

We've been trying to simplify the #ifdefs in the code.

I got it.

But what would be better without making it very long? FEAT_PROP_POPUP ? FEAT_TXTPROP_POPWIN ?

I think that even if it is long,  prefer FEAT_TXTPROP_POPWIN  to FEAT_PROP_POPUP and +textprop to +textprop/popupwin

I found a typo.  POPUP_NONE →　USEPOPUP_NONE
If not merge this PR, please fix it.
https://github.com/vim/vim/blob/master/src/popupmenu.c#L764

Naruhiko Nishino wrote:

We've been trying to simplify the #ifdefs in the code.

I got it.

But what would be better without making it very long? FEAT_PROP_POPUP ? FEAT_TXTPROP_POPWIN ?

I think that even if it is long,  prefer FEAT_TXTPROP_POPWIN  to FEAT_PROP_POPUP and +textprop to +textprop/popupwin

I suppose FEAT_PROP_POPUP is good enough.  Can you update the pull
request for that?
We could define both +textprop and +popupwin.  This is user visible.
Adding a slash is unusual.
--
hundred-and-one symptoms of being an internet addict:
155.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Naruhiko Nishino wrote:

I found a typo.  POPUP_NONE →　USEPOPUP_NONE
If not merge this PR, please fix it.
https://github.com/vim/vim/blob/master/src/popupmenu.c#L764

Thanks for noticing, I'll include the fix.
--
hundred-and-one symptoms of being an internet addict:
154. You fondle your mouse.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I suppose FEAT_PROP_POPUP is good enough.  Can you update the pull
request for that?
We could define both +textprop and +popupwin.  This is user visible.
Adding a slash is unusual.

I got it. I'll update it.

I suppose FEAT_PROP_POPUP is good enough. Can you update the pull
request for that?
We could define both +textprop and +popupwin. This is user visible.
Adding a slash is unusual.

I got it. I'll update it.

I create new PR for this and close this PR.
https://github.com/vim/vim/pull/5291


Update Readme with instructions for running the tests locally.

Hi @bmanikm, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


ironic is shipping unbounded

Currently we ship ironic with an unbounded number of API workers. This could become an issue on the platform. We should consider bounding ironic to 12 workers (similar to how we do things in TripleO today [however, not with ironic]).

Inside the ironic container ```
[root@f13-h02-000-1029u /]# ps aux | grep ironic | wc -l
68

Just a heads up, we are going to capture numbers of Ironic response times with 12 workers, and compare them to the unbounded # of workers in our test env. @hardys @bfournie

I pushed a fix for this to https://github.com/metalkube/metalkube-ironic/pull/34, please review, I just hard coded a limit of 12 as mentioned above.

Closed via https://github.com/metalkube/metalkube-ironic/pull/34


Making the appointment editor page work more smoothly

For things to work correctly right now you have to click on the subject and then click again for it to register.
We want it to be where when you click to add an appointment, the event numbers are populated and that the groups have correctly been removed from the the selection.

Unsure what this is requesting. Will review later when I am more familiar with the app.


Clarify dependencies for SDK installation

I noticed the docs don't mention a few implicit dependencies that were necessary to get the SDK to install on a basic debian container.  In particular some of the SDK dependencies needed a few libssl and other dev headers available to build their extensions, here's a bit from a Dockerfile that I found works great:
FROM balenalib/armv7hf-debian:stretch

# Install python 3 and balena SDK dependencies.
RUN install_packages build-essential python3 python3-pip python3-setuptools \
    python3-dev python3-wheel libffi-dev libssl-dev

# Install balena python SDK in python 3.
RUN pip3 install balena-sdk

It could be handy to update the docs here and show or mention a similar install: https://www.balena.io/docs/reference/sdk/python-sdk/

Another user hits this.