exdns: ValidateRestoreReturn() and RestoreReturn() helpers

I am on the fence with this, it is not wrong, but seems to e like we are patching something in the wrong place. If the response comes from us, then dns.SetReply(req) takes care of the message id and  all other niceties, if the message is not generated by us, I do not think we should correct it..... as I said, I am on the fence with this.

It's to be used when we modify the request before passing it over to another exchanger.

<EMAIL_ADDRESS>tagged


All scroll fixes and addition of horizontal ViewPaging

@miguelhincapie Big push today - I have a demo with all my fixes and enhancements. Please check https://github.com/vit001/CustomBottomSheetBehavior and let me know if everything works as you expect.
https://vimeo.com/203048221

I will see it tomorrow at night :D


PyTryFrom::try_from_unchecked()

This allows casting a PyObjectRef to a specific type of PyObject
with no overhead.

I have no dissenting opinion

How about rewrting try_from  and try_from_exact implementation using try_from_unchecked?
It'll make our code simpler.

Thank you, this looks like a useful addition!
It's possible to do some minor improvements (rewrite the other try_*functions as @kngwyu suggested and removing some *mut), but I'm fine with merging as-is, just say which you prefer.

Ok, the other try_ functions delegate to const and mut unchecked functions, and the const version no longer uses mut casts.

@konstin, @kngwyu, if the last changes are good, I think it's ready to merge.

Thanks!


Ginkgo version 1.0.0 release

This issue is here to track the creation of the first Ginkgo release, which could be version 1.0.0 if we can get several CUDA conversions.
I currently set the deadline to first of march. Hopefully we can get everything done sooner.
I created a milestone to track the release process, I added every issue and PR that we want for the release to this milestone. If you want something in particular to be part of this release, add an issue and add it to the release milestone. Currently there is:

All open PRs
4 out of the current 5 issues tagged with "Bug".
The issues related to the open PRs

Unassigned issues

[ ] #110
[ ] #76

TODO

[x] Create a release milestone and issue.
[x] Create a wiki help page containing the important steps for releasing Ginkgo.
[ ] Create PRs to fix the open bugs which can be fixed, at least partially.

[x] Fix #71
[ ] Fix #203 (DOING)
[x] Fix #130
[x] Fix #152
[ ] Fix #110
[ ] Fix #174 (DOING)

[ ] Add a known issues page which contains the open bugs we cannot fix right now.
[ ] Tweak the compiled kernel sizes.
[x] Update the .gitlab-ci.yml file so that the CI system generates the documentation link: https://ginkgo-project.github.io/ginkgo/doc/1.0.0
[ ] Compile a list of functionalities present in the future release.
[ ] Update the external library's commit version.
[ ] Merge all open pull requests and freeze Ginkgo.
[ ] Ensure the milestone reached completion.
[ ] Run the CI pipelines and ensure there are no unexpected problems in the freezed develop branch.
[ ] Compile both release and debug linux binaries with CPack, ensure they pass all tests and are complete.
[ ] Use Github's release system to tag the release version and add the release notes (functionalities present in this release).
[ ] Update the master branch to the release version (create a merge commit, do not fast forward).
[ ] Update the website to point on the master branch's documentation instead of develop?
[ ] Update the website to advertise the release?

Some notes:

what do we do with the OMP kernels? AFAIK, trying to use the block-Jacobi preconditioner on OMP executor will result in the NotImplemented exception. Are we allowing this exception in the release version, or should we have a policy that such exception are not allowed?
somewhat related is #53: trying to compile Ginkgo with a custom datatype will result in NotImplemented for some operations - the full list is in the issue (may not be updated). Do we consider this a problem?
you may want to check out the description of the Gitflow workflow, especially the release branches part, for a description how the release should be handled. In particular, there should be no need to "freeze" Ginkgo, as the release dos not take over the develop branch.
what do we do with the doxygen documentation? It's not very useful the way it looks now - it needs some introduction, and some sort of organized TOC by topics - what we currently have is just an index of various parts. Some parts are also missing, as the current setup only shows documented namespaces, classes, and their members. Since none of the namespaces have any documentation, there's no docs generated for any of the standalone functions (such as read, write, clone, lend, give, share, etc.).
just a technical note: even though the master branch can be fast-forwarded to the final release commit, I would still force git to generate a new merge commit, just to have a better visual indication that this is a release when looking at Ginkgo's tree.
another thing for the list: make sure that the CI system generates the docs on the correct link (that would probably be https://ginkgo-project.github.io/ginkgo/doc/1.0.0)

Not on documentation, I did hesitate to add #76 to this milestone... It should not be too long to fix but is much needed.

Thanks @gflegar for the comments. The gitflow is helpful for managing the release efforts in terms of commits. I will add this to the wiki page I am currently writing. I think the release process itself can be quite fast if we have a correct setup for testing and doing the packaging (let's say a day at most), so I think merging the fixes directly to develop and agreeing on not merging any new PR until we are done with actually pushing the release to the world should be enough. What do you think?
I also want to mention that both Github and Gitlab facilitate the release process. Here are the respective pages: Github release page and Gitlab release page.

On OpenMP kernels, it depends what we aim to support as part of this release. Either we say in the release notes we have a full OpenMP implementation but its quality is not guaranteed, in which case we have to implement all NotImplemented kernels, or we explicitly note what is not there (both as a release note and I guess a known issue in that case).
On #53, I would have a similar approach. Either we say we have full support for custom value types, or we say we have backend support but not all kernels and formats allow its use yet (the user could still use it as part of its own class).

I agree on the having an explicit merge commit in the master branch and the documentation issue. I will note this down.

#174 could also be a good candidate for the release. It's warnings so it's fine if they stay, but better if they are gone.

I created a wiki page with the instructions I could think of for the release process. Feel free to contribute. There may be multiple typos...

@ginkgo-project/developers I would like to collect everyone's thoughts on the following issues we rose with @gflegar.

Do we implement all OpenMP kernels (for example the Block Jacobi), see Goran's previous comment and my answer.
Do we implement #53 (again, check Goran's comment)
Do we improve documentation through #76 and other issues brought up in Goran's comment?
Do we maybe fix #174 ?

On the OMP issue: there are in total about 25 NOT_IMPLEMENTED in the omp branch. I would say: let's copy complete those - in the worst case with the reference implementation and some note saying that this still needs to be parallelized.

Note from the discussions, we're not doing #53 as it seems like it would take too much time. But we will try to fix all the other problems listed here.

I guess we are delaying this? The deadline is tomorrow, and there are quite a few open issues in this milestone.

Yes, the deadline was a loose tentative one. Looks like we will have to postpone it, hopefully not by much.

Do we implement all spmv for all matrix formats on all executors?
Maybe use for loop to make it work first?

I don't think that makes too much sense, having all formats for all executors. I feel: we obviously need the reference executor for all formats, and if there is a format selected that is not supported by the executor, we fall back to the reference executor. Is that a reasonable path forward?

I mean the operation apply to multiple vectors of coo, csr, dense, ell hybrid and sellp on all executor.
The following are the status of formats

have implementations and tests

coo, csr, dense, ell, hybrid, sellp on reference executor
coo, ell, sellp on cuda executor
dense on omp executor

have implementations but don't have tests

hybrid and dense on cuda executor
coo, csr, ell, sellp on omp executor

don't have implementations

csr on cuda executor

I now understand - sorry.
I guess it would be good to close the gaps... for now, a loop might be acceptable.

Thanks for the notification @yhmtsai and for already fixing a part of that. I put this in a new issue (#253) to track this separately.


track element and TextTrack object

track element and TextTrack object

This issue was imported from Google Moderator
Moderator votes: +4
Issue added by sideshowbarker on 2011-11-20
To vote this issue up or down, simply include +1 or -1 in your comment.

Available at https://caniuse.com/#feat=mdn-api_texttrack & part of https://caniuse.com/#feat=videotracks (I think)


referrer-header won't get setted on href

Here is a small example:
package.json
{
    "name": "example",
    "version":  "1",
    "main": "main.js"
}

main.js
var app = require('app');
var BrowserWindow = require('browser-window');
var mainWindow = null;
app.on('window-all-closed', function() {
    app.quit();
});
app.on('ready', function() {
    mainWindow = new BrowserWindow({width: 1280, height: 1024, "node-integration": false });
    mainWindow.loadUrl('http://<IP_ADDRESS>/index.php');
    mainWindow.openDevTools({ detach: true });
    mainWindow.on('closed', function() {
        mainWindow = null;
    });
});

index.php
<?php
error_log(array_key_exists('HTTP_REFERER', $_SERVER) ? "YES" : "NO");
echo
'

        click

';

(a http-server with php ability is up and running on port 80 and references a /index.php request to the above defined index.php).
start electron (if you are in the same directory, where you added your package.json / main.js)
electron .

If you click with electron on this link, the referrer-header won't get setted (as in your logs, there will only NOs get logged for every request.
Is there a way, to restore the original behavior of an webbrowser, which will always set the referrer header (if won't set some sort of attribute to prevent the default behavior to the link)?
Thanks!

An even more minimal example:
main.js
var app = require('app');
var BrowserWindow = require('browser-window');
var mainWindow = null;
app.on('window-all-closed', function() {
    app.quit();
});
app.on('ready', function() {
    mainWindow = new BrowserWindow({width: 800, height: 600, "node-integration": false });
    mainWindow.loadUrl('http://www.whatismyreferer.com/');
    mainWindow.openDevTools({ detach: true });
    mainWindow.on('closed', function() {
        mainWindow = null;
    });
});

Click on the link. Expected is the following response:
Your referer:

http://www.whatismyreferer.com/

I receive:
Your referer:

No referer / Hidden

hmm... If I change the Request from GET to POST, the referer get's finally transmitted.
A workaround would look like this:
Modify index.php from my first commit to the following:
index.php
<?php
error_log(array_key_exists('HTTP_REFERER', $_SERVER) ? "YES" : "NO");
echo
'

HTTP_REFERER: ' . (array_key_exists('HTTP_REFERER', $_SERVER) ? "YES: " . $_SERVER['HTTP_REFERER'] : "NO") .'

        click

';

Electron will display this after clicking on the link:
HTTP_REFERER: YES: http://localhost/index.php

click

HTTP-Serverlog will also response with YESs.
@zcbenz is this the normal procedure to receive the referer?

@zcbenz is this the normal procedure to receive the referer?

It is a bug that referrer is not set, the way link navigates in Electron is different from Chromium browser because we need to restart renderer process for every navigation, and I forgot to set the referrer.

@zcbenz thanks for digging into this :smile:. hope it get's fixed soon.

Thanks @deepak1556 and @zcbenz

The bug still exists. Electron v1.2.0


--typescript flag / disable JSDoc

I would really love it if we had a --typescript flag — I just had a slew of JSDoc added to like 200 components who's script tags didn't need a lang="ts" because svelte 4 inferred prop types correctly 🥲.

Too which command is this related? Based on the 200 components I would assume migrate?

Ah sorry, yes!
I feel like we should make issue labels for them.

The migration script is still living inside the kit repo, @benmccann would you mind moving this issue?


Menu changes

The tree has a great right click menu which I'm trying to modify. Please excuse my poor explanation of what I'm trying to do. Using the demo there is a button to create a new folder and I'm trying to integrate that into the right click menu so I don't need the buttons at all. They are kinda redundant but unfortunately even using them as an example I'm stuck. The create folder starts with  on the index.html page. The jquery.jstree.js create the menu using defatults :{ and to summarize there is create, rename,remove and ccp. I've added the following;
createf" : {
"separator_before"	: false,
"separator_after"	: true,
"label"				: "Create Folder",
"action"			: function (obj) { makeafolder();}
and then I'm trying to complete a function to create that folder using the original button menu as an example with no luck. I've been at this for days now and would appreciate some direction.
While I'm writing this I might as well ask an additional question. I also want to create another menu item that calls a function but I need to get the data that is also stored in the db id 	parent_id 	position 	left 	right 	level 	title 	type
Any assistance is appreciated. My programming skills aren't great but I'm hoping to learn more.
Thanks

if you look at $.jstree.defaults.contextmenu.items.create you can see
action: function (obj) { this.create(obj); } label: "Create" separator_after: true separator_before: false
is it that you were looking for ?
for that data in the db did you try doing a post request (jQuery.post) to a server side content like php who can get the data in the db ?

I modified the function as is has to pass the object
"createf" : {
"separator_before"	: false,
"separator_after"	: true,
"label"				: "Create Folder",
"action"			: function (obj) { makeafolder(obj);}
Then created a simple function;
function makeafolder(obj){
$("#demo").jstree("create", null, "last", { "attr" : { "rel" : 'folder' } });
}
That allow you to have the create folder in the menu list. The id of the record list in the tree db. I see the variable just having a hard time with the documentation on the scripts. I can see that the creator has put forward a great effort in doing this. Unfortunately I'm so where near the skill level of this group. I do appreciate everyone's time
The next things as I mentioned I'm working on is the ID. While I've tried many things just as an example you can see this;
"editpage" : {
"separator_before"	: false,
"separator_after"	: true,
"label"				: "Edit Page",
"action"			: function (obj) { if(this.is_selected(obj)) { obj = this._get_node(obj);alert(obj.children("ul:eq(0)").children("li")); } else { alert('f'); }}//obj.children("ul:eq(0)").children("li")
Hopefully I'll figure this part out soon too and someone will find it useful
Thanks


remove the NetApp constant

This code isn't being used, so we'll remove it for now.  Fixes #1423
/cc @gmcculloug @jrafanie

Thanks, I like this approach. Getting a :+1: from me on this is a given.

:+1:, just have the one deprecation question.  I like the change, "6 additions and 165 deletions"

@tenderlove There are a number of other files that need to be updated to properly remove the NetApp RCU logic here.  Like the references in miq_provision_vmware_workflow.rb and miq_provision_request.rb as well as removing the field references from the dialogs and the via_net_app_rcu provisioning state-machine.  How do you want to collaborate on that?  I can either point you to the other code I think should be removed or I can do the work and push commits to this PR.

@gmcculloug it's up to you.  I'd prefer you did it though, since I think you are more familiar with this code than I am. :)

@tenderlove Denied access to push to your repo.  Can you add me as a contributor?

@gmcculloug done!

What's not to like about collaborative deletions???  A team that deletes together, stays together or something?  :heart_eyes_cat:

Awesome.  @gmcculloug thanks for finishing this up for me.  Are we ready to merge?

Wow, so much :red_circle:, I :heart: it

Yes, all ready.  @jrafanie Would you like the honor of merging?

Sure...


redundancy in lib/misty/openstack

Hi,
I think the version prefix could be added more generic.
E.g. https://github.com/flystack/misty/blob/master/lib/misty/openstack/glance/glance_v1.rb always starts with /v1 and https://github.com/flystack/misty/blob/master/lib/misty/openstack/glance/glance_v2.rb always with /v2.
The only thing that does not need a version is the version discovery itself (via GET /) - maybe this can be handled separately. What do you think?
Cheers

Hi Maurice,
The API definitions are generated automatically, besides some fixes, all the definitions are coming straight from the Openstack API-ref. The prefix version is even sometimes, but not necessarily consistently, is taken away as we can see with nova [1].
I think it's better to not interfere as much as possible with the API, in order to get more automation.
[1] https://github.com/flystack/misty/blob/master/lib/misty/openstack/nova/nova_v2_1.rb

Hi Gilles,
I agree, it's better to automate this way.


missing_footprint error if a NormalComponent doesn't

may require defining missing_footprint_error as an error type in circuit json
when rendering NormalComponents throw an error if they don't have any footprint representation

/bounty $20

/attempt #249


Write a Haskell program to convert fahrenheit to celsius

Description
Write a Haskell program to convert fahrenheit to celsius
celcius = (fahrenheit - 32) * 5/9
Input ( F )  : -40
Output ( C ) : -40

How to contribute

Save the solution in convert_fahrenheit_to_celsius.hs file
Add convert_fahrenheit_to_celsius.hs file in program/convert-fahrenheit-to-celsius folder

!assign

!assign

Hey @RiteshK-611, this issue is already assigned to @esivakumar18 !!!
Please choose another issue.
Thanks for your interest in contributing to this project.

!assign

Hey @RiteshK-611, this issue is already assigned to @esivakumar18 !!!
Please choose another issue.
Thanks for your interest in contributing to this project.


RFE: Allow to set connection.autoconnect.

I have the following issue:
(This is on a RHEL 9.3, with nmstate 2.0.0)

On a system there are three interfaces that are plugged, but only one should be configured for now.
Because they are plugged, and thus an ethernet signal is detected NetworkManager tries to configure them. This fails (as there is no dhcp listening), and results also in the NetworkManager-wait-online systemd unit to fail.

I tried to disable those interfaces using nmstatectl, but that did not work. The only thing that does is doing something like:
nmcli con  mod eno8 connection.autoconnect no
I could not find out however how to disable autoconnect using nmstate. So either this is not clear from the docs, or not implemented. Could this be done?

Could you explain why your use case why eno8 should not have autoconnect and why it should be activated?


Processes that exceed the time limit are not killed

The TestingBatch does not kill goroutines that time limited and they still can push the completion result back to the complete channel.

Another use case: infinite loop program that hangs all of the computer, because it was run 10 times in parallel....


[Intel MKL]: Fixing a build issue in mkl_cpu_allocator

This PR fixes a build regression happened in mkl_cpu_allocator because of other commit:
https://github.com/tensorflow/tensorflow/commit/505b11b8c230e644cc4ff71f98a0b22e84514e7e#diff-b34307576896d87b6abd5a4c273d3fa6

Hi @penpornk, this is blocking us from building TF with MKL. Can you have a look at this fix?

@rthadur Thank you! :)

@penpornk @rthadur thank you so much for the quick response.


Improve next previous accessibility

hidden pseudo before on label element containing "." causes screen readers to take a breath between navigation and label parts of link
tested on Voiceover (Mac), Narrator, Jaws 18, NVDA (Windows)
unable to test for pseudo element content so specific tests for accessibility removed, but comment added to SCSS to prevent accidental removal

See https://trello.com/c/0kYwSKe4/222-investigate-accessibility-of-next-previous-component

This doesn't feel right to me, since it could change at any time and I'm not sure the current version without pauses is a barrier.
The advice in https://accessibility.blog.gov.uk/2017/02/08/advice-for-creating-content-that-works-well-with-screen-readers recommends not do anything specific for assistive tech but this change does seem to make it clearer.

I agree with Nick. Do we know if the lack of a pause is a problem? Can you pose the question in the accessibility community google group- would be good to get some thoughts/feedback from screen reader users.  Can you set up a couple of couple of examples using something like CodePen so that people can test out a rendered version and provide feedback.

This is a follow on from #1118 which introduced a colon in an attempt to add a pause.

To summarise what I said in our internal Slack channel:
I agree that having a link which reads "Previous Terrorism" is not great. I think the best solution is exactly what #1118 was doing, i.e. adding a colon in between, because "Previous: Terrorism" is way more semantic. That also works well when you switch off CSS. And it works for Braille display users (the solution in this PR doesn't).
This PR however is more of a hack to fix various browser or screen reader bugs. I think that's generally a bad idea. And we cannot be sure what other issues it might introduce, especially with different screen reader settings and other speech engines.
That's why I would follow Leonie's advice from the blog post Nick linked above:

don't write content that works specifically for screen readers, write content that works well for everyone. Use correct punctuation, spelling and grammar, use standard conventions for acronyms and abbreviations, and use words that are appropriate for your audience.

If you want to make sure you're doing the right thing there is no way around asking actual screen reader users, either by asking the cross-government accessibility mailinglist or doing some user research. Because everything else is just guesswork.


Revert "[DataFactory]Set servicePrincipalId,servicePrincipalKey and tenant to be optional from AzureDataExplorerLinkedServiceTypeProperties"

Reverts Azure/azure-rest-api-specs#12755

This PR is to revert a previous PR merged one day ago as the last PR is declared as a breaking change in .net SDK.


[Nostr] Nostr plugin documentation and user interface is confusing

Hey.
I made a pull request:
https://github.com/Kukks/BTCPayServerPlugins/pull/56
I would like to improve the documentation and user interface a little bit more though, the documentation is very confusing. I volunteer to write it and create pull request, but I need clarification.
1.) The official documentation (linked from the "Manage Plugin" tab) contains three things - NIP05 (verifying accounts), NIP57 (zaps), NIP47 (receiving to NWC enabled lightning wallet).
But the "Usage" part does not distinguish among these use cases. What am I setting up?
2.) The Nostr tab that appears in the sidebar contains this notice:
For Zaps, just enable a lightning address. None of the nostr settings on this page are needed for zaps anymore.

OK, so what are they needed for? What am I setting up? NIP05 verification?
Why is there a private key (and why is it optional? What happens if I put it there, what happens if I don't)?
3.) There's no mention on setting up NWC. It is not in Nostr tab, it is in setting up the wallet of the store.
I found this blog by Alby. Should we point users to it? Is there a better documentation? Should we at least briefly write about this in plug-in documentation?
Should we include any documentation for this functionality? (Or at least point them to it).
4.) Is there any maintained website that lists wallets that support NWC?

1.) The official documentation (linked from the "Manage Plugin" tab) contains three things - NIP05 (verifying accounts), NIP57 (zaps), NIP47 (receiving to NWC enabled lightning wallet).
But the "Usage" part does not distinguish among these use cases. What am I setting up?

NIP05:
Suppose your btcpay server web address is btcpay.example.com and that you have registered name myname with the nostr plugin then a GET query to https://btcpay.example.com/.well-known.nostr.json?name=myname will return a json response with the hex version of your nostr public key and your optional relays, if you included them.
In this case<EMAIL_ADDRESS>is a nostr address. Nothing more. You can have multiple nostr addresses all providing the same public key (but only one nostr address per BTCPay store, unlike lightning addresses).
NIP57:

2.) The Nostr tab that appears in the sidebar contains this notice:
For Zaps, just enable a lightning address. None of the nostr settings on this page are needed for zaps anymore.

OK, so what are they needed for? What am I setting up? NIP05 verification?

Nothing to do with NIP05 and you are not verifying anything with NIP05. The nostr address identifies a public key, it does not authenticate or verify a public key.  Only the nostr public key can be used to verify an event (such as a message) was signed by the particular private key of that public key.

Why is there a private key (and why is it optional? What happens if I put it there, what happens if I don't)?

Nothing additional happens to the NIP05 information passed back with the private key entered. The private key can be used to sign a zap receipt.
I assume if you do not have a ligntning address added in to receive a zap then any payment to your nostr address as a lightning address gets processed as a lightning payment, perhaps with an additional nostr signed receipt that you may not get otherwise with a lightning address. Perhaps @Kukks can clarify.
Interesting questions: What happens if your nostr name is the same as one your added lightning address names?  Which code flow gets precedence for processing?
Also, if nostr is enabled and you have lighning addresses enabled then your lightning address GET query will also list your nostr public key in hex
NIP47:

3.) There's no mention on setting up NWC. It is not in Nostr tab, it is in setting up the wallet of the store.

NWC is the abbreviated name for NIP47. It is just a protocol.
A nostr client can ask a lightning service for a lightning address to pay when all it knows is the nostr address.
From NIP47 (emphasis added)

client discovers wallet service by scanning a QR code, handling a deeplink or pasting in a URI.
client: Nostr app on any platform that wants to pay Lightning invoices.
wallet service: Nostr app that typically runs on an always-on computer (eg. in the cloud or on a Raspberry Pi). This app has access to the APIs of the wallets it serves.

So the plugin adds the above mentioned wallet service to BTCPay so as NIP47 (NWC) enabled nostr clients can talk to a lightning service
I will give this a try and report back.

Interesting questions: What happens if your nostr name is the same as one your added lightning address names? Which code flow gets precedence for processing?

My guess is that if the NWC protocol is used then a nostr signed zap receipt is shown. If sent direct through lightning then no nostr signed zap receipt is shown

I have a look at Amethyst in Android. You can enter an nostr address as part of a profile associated with your npub or nsec. An nsec profile is required to send a zap. If only a npub profile is associated with a sender then a zap won't be sent.
It wasn't possible to use a nostr address to send a private message without knowing the npub or @ name for it. If a nostr address is added to a profile of Amethyst, then Amethyst will tell you there is an associated nostr address and show a tick. The verfication in this case is a verfication that a web lookup returned the npub it is associated with. It did not work backwards from within Amethyst (finding an npub from nostr address). There is no user verfifcation, only a verfication of an npub with a web address.
Even with the Nostr Address ticked for a user, a zap is not sent without a lightning address associated with a profile being sent to. So an nsec is required for profile of sender and a lignting address is required for profile of receiver. An nostr address is not required.
My conclusion is that Amethyst does not implement NWC. As for the upcoming Alby wallet with NWC, the Alby wallet is not publically available. The upcoming NWC Service from Alby is for use on a server with an SDK.
I could not any association with NWC for other nostr clients. The association of Ametyst with NWC is misleading.
Conclusion: NWC is not currently available client side and there is no general SDK available server side.

As I see it (to make the interface more clear):
Zaps

To receive zaps and issue zap receipts, you need to actually fill the form. The note in the interface makes it seem that for zaps to work you don't need to, but the form is actually to be able to issue zap receipts and thus make zaps fully work. And that's the only reason to fill the form.
Without filling the form, you can receive zaps (because they are just lightning payments to a lightning address), but Zap receipts won't be issued and zaps won't be registered on Nostr network

For zaps, my suggestion is to reformulate the interface to reflect the above.
NIP-05 verification
For NIP-05 verification, we need name, public key and a list of relays. Then nip-05 verified address will work. Let's make it clear that these are used for NIP-05, because it's not clear from the interface
NWC
NWC is unrelated to this interface page. We should set it up as a Lightning node in the store. It should also be clearer from the interface.
If I am correct in my assumptions, I will provide suggestions on how to change the texts in the interface and how to alter the documentation.

Correction. I was able to get an Alby browser extension wallet to work by using the LND REST feature of BTCPay.
I did not see these addiitonal settings below come in Amethyst in the lower half:

I have confirmed the additional features are in NIP47 and  assume they are already preconfgured in BTCPay.
It looks like the purpose of the Alby NWC SDK is to split into two what BTCPay is already doing as a complete service. So functionally Ametyst wallet + Alby SDK = BTCPay.

As I see it (to make the interface more clear):

I would agree the existing interfaces could be better documented or explained. If you could add this in we would all be grateful.
My impression is that there is nothing wrong with the interface and there are no missing interfaces. Protocols don't care about interfaces.
Documentation is poor from the perspective of a user or admin trying to learn. But that is not the fault of BTCPay. Why should BTCPay be tasked with filling in the gaps?

It looks like the purpose of the Alby NWC SDK is to split into two what BTCPay is already doing as a complete service. So functionally Ametyst wallet + Alby SDK = BTCPay.

So my guess is that unless funds are held custodially by Alby Wallet or Amethyst Wallet there won't be a usable NWC service with these wallets

Btcpay presents the user interface. It's not about teaching about the protocols, my problem is I don't know what I'm setting up, what is the interface doing. Like writing you don't need this for zaps, but then you realize that zaps fully don't work without it (because there are no receipts). Or that the private key is not needed for the verification. Or that the "username" is different for zaps and for verification. I'll start with documentation.

Btcpay presents the user interface. It's not about teaching about the protocols, my problem is I don't know what I'm setting up, what is the interface doing. Like writing you don't need this for zaps, but then you realize that zaps fully don't work without it (because there are no receipts).

When I paid a zap in Ametyst I go thrown to a wallet to make a lightning payment. This was not a a NIP57 zap. I suppose a clearer explanation is that the private key field is required for NIP57 zap but no one pays zaps this way.

Or that the private key is not needed for the verification.

Agreed, except that verifcation is not user verfication.

Or that the "username" is different for zaps and for verification.

Why do you say that? The username is part of the identifcation scheme to provide a nostr public key and to link to a wallet service. The public key is what is important for nostr, a username  proves nothing in nostr.

I am about to post a Pull Request that hopefully clarifies the nostr interface to a level that avoids confusion.
I will reference this issue so I expect a link will appear below this comment.
If you want the interface clarified further and have specific suggestions as to wording, then please make them at the pull request.
If you have more general comments to make, then please continue posting to this issue.
With regard to zaps and entering the private key in the interface for the nostr plugin, if no private key is entered then a random key is made up. Yes, it would be nice if this was explicitly stated at the interface. So let's do this.
Looking at the BTCPay plugin code, it looks like plugin issues type 9735 nostr receipts to nostr relays independent of how the the zap was requested when a lightning payment is made, if there is a nostr address associated with the store the lightning address belongs to.
The filtering function below processes NIP57 zap events (kind 9734). The nostr client makes the request to a lightning wallet server using a nostr address and is only really required when a lightning address is unknown. I don't think Amethyst bothers with this, but it does not matter.
https://github.com/Kukks/BTCPayServerPlugins/blob/5cfe2e5acd40cd4b982c34871c2e084cdc0467fe/Plugins/BTCPayServer.Plugins.NIP05/LnurlDescriptionFilter.cs#L35
When a lightning payment is actually made, the plugin checks if there is a nostr address associated with any lightning address belonging to a store. If there is the plugin issues a nostr type 9735 event to relays
When a payment is made, this line uses the stored private key if it was entered. If none was entered it uses a made up random key.
result.ZapperPrivateKey ??= Convert.ToHexString(RandomUtils.GetBytes(32));

from https://github.com/Kukks/BTCPayServerPlugins/blob/5cfe2e5acd40cd4b982c34871c2e084cdc0467fe/Plugins/BTCPayServer.Plugins.NIP05/Zapper.cs#L43

The nostr client makes the request to a lightning wallet server using a nostr address and is only really required when a lightning address is unknown.

My statement is wrong. The nostr address of NIP05 has nothing to do with providing a ligtning address. Even though the nostr address and at least one lightning address could be the same, there is no requirment for this.  Also, although BTCPay might choose to process a nostr address as an unlisted lightning address, there is no obligation to do so..
This has clarifed issues for me.

Thanks to @Kukks for merging mine and @jooray commits with regard to clarifying the nostr plugin UI.
There is a lot of material that jooray can use to get way ahead with. For example, Kukks has invented a technique for a nostr client to configure a combined nostr server/btcpay store with lightning wallet, to make a one touch zap payment, rather than the other way of expecting the nostr client to fetch the approved configuration from an intermediary to the lightning wallet and nostr client, through a nostr+walletconnect deeplink.
I added in Kukks nostr server fragment into btcpay and got it configured. The instructions are very terse but the do work. By relay below I mean the nostr relay on the btcpay server, which has URI of the form wss://btcpay.example.com/nostr, when the docker fragment is loaded.
The initial AdminKey, usable as an initial hex nostr secret key for a nostr client, is sent as an error message when attempting to contact the relay from any nostr client that uses the relay for a nostr private DM to the relay (by sending a DM to oneself).  These relay error messages are not regular messages. They can be seen by Amethyst Android nostr client app by clicking on the relay name, but but not by the nostrudel nostr client web app.
In addition, currently the desired edited {CONFIG} to send back, with a new AdminKey, must NOT be sent encrypted to the relay.  This needs a fix. This means nostrudel cannot currently be used be send /admin commands for this and encryption needs to be toggled off on Amethyst for the DM.
There is no admin webui for the nostr server, unlike for the btcpay nostr plugin.
There is clever and interesting code in the nostr btcpay plugin. Kukks has reversed the onus on a wallet service to provide a one touch zap NIP-47 nostr+walletconnect deeplink to be used by the nostr client.  Instead he has invented a NIP (NIP-67) which allows the nostr server to send a nostr confirmatory event to confirm how the nostr server/btcpay server has been configured for one touch NWC zaps.  A nostr client tell the nostr server what services to provide and what secret to use to verify a payment request is genuinely from an approved nostr client. Currently no known public nostr client apps implements recognition of NIP-67 events. Presumably there is will be as an extension to the /admin command system that configures the one touch zap service and allows one or more eligible clients to receive the event with the details.
So who might these clients be receiving the NIP-67 events automatically ? I assume any nostr client that is using the same nostr secret as the formerly sent AdminKey to the nostr server with the /admin config {CONFIG} command.

Some clarity added how the above might work, step by step. Also some more background detail and what the future might bring, that I also think adds clarity, particularly as to just how flexible a UI can be with nostr and btcpay
First the nostr server code mentioned is called NNostr and is available from https://github.com/Kukks/NNostr. The title is 'A Nostr Relay and Client written in C#'. The server code can be installed with btcpay server through the well recognised technique in btcpay of including docker fragments for a rerun setup.
The client part of NNostr is a C# library to listen for events, subscribe to particular events and send events. There is no UI, but that is where its strength lies. In the usage example provided there is an example of connecting to a single relay. A specific main strength is the capacity to be used by plugins in btcpay to communicate with the nostr server of the btcpay server.
Step by step details of an example of automated configuration for one touch zap (and even zero touch zap):

Two nostr clients have added nostr accounts that are used for DM purposes with the nostr server on btcpay. The secret key for the accounts is the same as the same nostr server AdminKey.
One nostr client sends a currently, as of now, unidentified /admin command through a DM message to the btcpay nostr server to configure one touch zap payments
The nostr server stores a Kukks' NIP-67 event with the NIP-47 nostr+walletconnect:// NWC URI string.
The nostr server sends the NIP-67 event to the two clients whom it knows have the same secret key as the AdminKey
The two nostr clients decode the NWC URI and provide information to a user they can now use one touch zaps

So how might this be useful right now, given that no known clients use NIP-67 and there is no discussion of it?
As indicated above, the NNostr C# client code has one very useful feature that can be used right now! It can be used by btcpay plugins that are themselves nostr clients to the btcpay nostr server! They can also add in an admin webui for the nostr server!
So there is a lot of potential for building sophisticated solutions with further exotic plugins, including btcpay plugins providing zero touch zaps! How about setting up a zap service as a plugin that sends a series of automated zaps on a regular basis!

So why automate sending zaps rather than direct lightning payments?
Because zaps can associate payment with the payer's public key. So payment and source of payment can be proved. This allows account keeping.
I have changed the title of issue https://github.com/Kukks/BTCPayServerPlugins/issues/63#issuecomment-2372553206 and added more comments to confirm if the approach above could work.


The first picture cannot add click events。

To add a click event to each picture, the first picture click event is invalid once the loop is played again

#21


Disable/Delete Microsoft.PythonTools.Analyzer.exe

Describe the feature you are requesting
Allow me to delete Microsoft.PythonTools.Analyzer.exe without an error appearing or allow me to disable the feature.
Reasons for requesting this feature
Whenever I have my django server running this file eventually takes up all my ram (11gb from this one .exe out of 16gb).
Describe alternatives you've considered
I deleted the file so it doesn't run when I run my server for testing but I get an error, and there is no way to disable it.
Additional context
[Window Title]
devenv.exe
[Main Instruction]
An unexpected error occurred
[Content]
Please press Ctrl+C to copy the contents of this dialog and report this error to our issue tracker.
[^] Hide details  [Close]
[Expanded Information]
Build: 16.6.20100.1

System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.StartSubprocessConnection(String comment, AnalysisProcessInfo& proc)
   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<InitializeAsync>d__42.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Intellisense.VsProjectAnalyzer.<CreateForProjectAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<CreateAnalyzerAsync>d__142.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<ReanalyzeProjectHelper>d__155.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Project.PythonProjectNode.<ReanalyzeProject>d__154.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PythonTools.Infrastructure.VSTaskExtensions.<HandleAllExceptions>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

I've just merged this in, it will be in the upcoming 16.8 Preview 2.
It adds a checkbox in tools/options/python/language server to "Disable IntelliSense"
Just reload the project after checking that option, and you should no longer see the Microsoft.PythonTools.Analyzer.exe process running. The trade off is that you won't have any IntelliSense, refactoring, find references, go to definition, semantic colorization, etc.

cheers


add new token  A-TOKEN

团队背景：
农宝通证（A-TOKEN）是全球农业生态供应链数字资产，基于以太坊ERC20底层技术开发，通过国际交易所备案，恒量发行3000万枚，以智能合约保证永不增发，可通过imToken 钱包及农宝钱包交易，是新加坡农业通证基金会全球投资的唯一价值流通凭证。
项目基本情况:
A-TOKEN is a digital asset of the global agro-ecological supply chain. It is based on the ETC20 underlying technology development of Ethereum. It is filed through the international exchange, and 30 million pieces are issued in a constant quantity. The smart contract guarantees never to be issued, and can pass the imToken wallet. And the Nong Bao wallet transaction is the only value circulation certificate for the global investment of the Singapore Agricultural Pass.
更多关于 A-TOKEN 的信息
建议 gas limit: 60000

问题已在标签中注明，特别提醒：在 json 文件中请提供 website


AutoHDR compatability?

Fantastic app!
I'm currently using this with: https://github.com/Codectory/AutoHDR
This app changes the HDR status of your display. I was trying to set this up so it will turn on HDR mode for my PC alongside Playnite.
Without Gamestream Launchpad, that works fine. However, when in a Gamestream Launchpad session, it will revert back to my normal resolution if I turn on HDR mode in any way.
Anyone have experience with this situation?
I'm using a Samsung Odyssey G9 monitor, if that helps.

This is an interesting problem. I could add a way to add tasks like AutoHDR to run before the resolution is changed by launchpad. Does everything work as expected if you manually run AutoHDR before firing up a launchpad session?

Hi, i am doing the same thing here. I do not notice the problem with the resolution change causing issue with HDR.
But what i want to have is a playnite ini and bat that allows HDR_on or HDR_off.
I haven't yet figured out a way to implement this, as autoHDR relies on certain app to toggle on/off the profile.


Building strokes are too strong

Combo of stroke weight & stroke color makes it hard to read the street labels.

Geraldine completed this task.


Go full wizard 🧙

Taking inspiration from Sentry's setup tool, it would be great to take the init process a step further and do more for the user.

[x] npx command does npm install
[x] Add video.d.ts to tsconfig.json
[x] Add withNextVideo to next.config.js
[ ] Add next-video sync -w to dev script in package.json
[ ] Open Mux signup page
[ ] Open access token creation page
[ ] Prompt for token details and add to .env.local
[ ] Add example video file to /videos to test the setup
[ ] Add a demo page to the project to verify it's all working
[ ] Create a "Manual Setup" page and direct people there if they're not comfortable with the wizard, or if something goes wrong.

It would be more magic if we could generate an access token without going to the Mux dashboard. I don't think we should try to get around signup through the dashboard.

We should add messaging for what to do next at the end of wizard, otherwise it's an awkward drop off at the end of it.
Currently the next step is signing up and creating the .env.local file, which is an important one not to miss.


Make CAGradientLayerExtensions public.

For now, its has internal access level and do not accessible.

Thank you for reporting @denandreychuk :)
If the problem is just making it public, that's a good first issue if someone wants to give it a try.

https://github.com/SwifterSwift/SwifterSwift/pull/856


Create pt.json

Wow, thank you!

Available in the 0.8.10 release
https://github.com/rroller/dahua/releases/tag/0.8.10
Thanks again!


同步官方

Description

Test Steps

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

同步


refactor: es10 features

Pull Request Test Coverage Report for Build 127213141

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.02%) to 11.236%

Files with Coverage Reduction
New Missed Lines
%

lib/vue-2-breadcrumbs.common.js
18
11.24%

Totals

Change from base Build 125788482:
-2.02%

Covered Lines:
8

Relevant Lines:
49

💛  - Coveralls

Pull Request Test Coverage Report for Build 127213141

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.02%) to 11.236%

Files with Coverage Reduction
New Missed Lines
%

lib/vue-2-breadcrumbs.common.js
18
11.24%

Totals

Change from base Build 125788482:
-2.02%

Covered Lines:
8

Relevant Lines:
49

💛  - Coveralls

Pull Request Test Coverage Report for Build 127213141

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.02%) to 11.236%

Files with Coverage Reduction
New Missed Lines
%

lib/vue-2-breadcrumbs.common.js
18
11.24%

Totals

Change from base Build 125788482:
-2.02%

Covered Lines:
8

Relevant Lines:
49

💛  - Coveralls

@VladStepanov Thank you for your contribution


Really could do with more troubleshooting guidance on Export of Azure SQL databases

I've yet to get Export to work for Azure SQL as it always fails with an authentication error despite the credentials being fine in SQL Server Management Studio.
This could really do with some additional troubleshooting advice, as I've so far found nothing on this.

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

ID: 93623678-1324-6a32-33ed-6d9be4587ebb
Version Independent ID: 6dfd1d52-e034-9097-2eb4-d9b3f7c74ab8
Content: Import and export of a database takes a long time - Azure SQL Database & Azure SQL Managed Instance
Content Source: azure-sql/database/database-import-export-hang.md
Service: sql-db-mi
Sub-service: data-movement
GitHub Login: @suresh-kandoth
Microsoft Alias: sureshka

@johnmreynolds Looks like you are trying to import/export an Azure SQL Database and facing some issues but not able to find helpful information from the doc.
Could you please help us by sharing what error message you are getting.

@WilliamDAssafMSFT
Please review

@johnmreynolds Thanks for taking the time to create this issue. Sorry that we've not offered any help in this avenue, but this avenue is not for tech support or troubleshooting. I understand the angle is to request more troubleshooting in Docs, but GitHub issues offers no SLA. If you haven't already, open a support case with Microsoft to get your error scenario investigated.
If I had to guess, you might be running up against one of these two limitations:

Currently, the Import/Export service does not support Microsoft Entra ID authentication when MFA is required.
Import\Export services only support SQL authentication and Microsoft Entra ID. Import\Export is not compatible with Microsoft Identity application registration.

#please-close


Implement Random forest model

This won't be needed as we already have several models and this is close to gradient boosting. Removing this issue.


.scrollTo() gets stuck on Android

Describe the bug
I've been using detox from last few months and this issue came into my observation. On the simulator I cannot see any motion of the scroller. I do not understand any reason for it to not work properly.
Can it be the detox version issue?
The scroller was earlier working in all the test files so far till past 2 weeks and now failing in few of the files.
The testing screen halts when .scrollTo('top') action statement arises and nothing happens afterwards.
If anyone have any solution to this, please share. It would be of great help.

Steps To Reproduce

detox test -c debug

Expected behavior
Should have scrolled the screen in either direction.
Detox Trace-Logs

Full log trace ->
test_log_trace.pdf
Environment :

Detox: 18.7.0
React Native: 0.63.3
Node: 14.16.0
Device: Pixel_API_23x86
OS: macOS Big Sur 11.2.3
Test-runner: jest-circus

@Sonakshi997 it's really hard to tell what wrong this way. Could you please use the --take-screenshots all, --record-video all and --record-logs all arguments to detox test and provide the artifacts generated under the artifacts/ folder?

@d4vidi I understand. Here is what you asked for. I hope the issue gets clear now as I am facing this on various different screens now. Also, the ScrollTo() works perfectly fine on IOS.
What is expected from the ScrollTo() -> Done manually:
https://user-images.githubusercontent.com/79457969/119674108-8f459180-be59-11eb-9f3a-ba79c8cec8dd.mov
What Detox is doing via test:
https://user-images.githubusercontent.com/79457969/119674203-a4222500-be59-11eb-91c7-2bc821a223b7.mov
Console Logs Before and After the ScrollTo()  :

What happens on the terminal -

Thank you.

@Sonakshi997 this is great, thank you. Please also spot a file called process.log under the failing test and upload it as well. Thank you!

I understand @d4vidi . I tried finding this file, but could not. Can you describe in detail where can I find this file. That will help a lot.

Add the --record-logs all argument to detox test. After the execution completes, you will have such files under an artifacts/ subdirectory.

Hi @d4vidi . Here is the process.log file you requested. Let me know if anything else is required from my side.
process.log

Hi @d4vidi . I was able to overcome this stuck .scrollTo() problem by doing this.

I created a function that takes the testID as arguments and calls it in files where my scrollTo() does not work.

await element(by.id(scroller_testID)).scroll(scrollValue, 'down')
await element(by.id(scroller_testID)).tapAtPoint({
  x: 10,
  y: 10,
})
await element(by.id(screenView_testID)).tapAtPoint({
    x: 10,
    y: 20,
  })

I believe this is just a temporary solution or a hack to make things work for now. Let me know if there is any progress at your part.
Thank you.

Yikes. There shouldn't be such hacks in Detox. @jonathanmos could we get to the bottom of this together?

@jonathanmos were you able to make any progress here?

@Sonakshi997 I was not able to reproduce this issue, except when the soft keyboard was open due to typing in the textfield - in which case, I added tapReturnKey to dismiss it and the test subsequently passed properly. What is the purpose of tapAtPoint? Is it to dismiss the keyboard or for another reason?

I'm seeing this exact issue. Works fine on iOS but Android hangs until timing out on scrollTo actions:
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] INFO:  [APP_STATUS] App synchronization debug: The app appears to be idle!
detox[15977] WARN:  [PENDING_REQUESTS] The app has not responded to the network requests below:
  (id = 50) invoke: {"target":{"type":"Class","value":"com.wix.detox.espresso.EspressoDetox"},"method":"perform","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"androidx.test.espresso.Espresso"},"method":"onView","args":[{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxMatcher"},"method":"matcherForTestId","args":["create-event-preview-post"]}}]}},{"type":"Invocation","value":{"target":{"type":"Class","value":"com.wix.detox.espresso.DetoxViewActions"},"method":"click","args":[]}}]}```

@Sonakshi997 I was not able to reproduce this issue, except when the soft keyboard was open due to typing in the textfield - in which case, I added tapReturnKey to dismiss it and the test subsequently passed properly. What is the purpose of tapAtPoint? Is it to dismiss the keyboard or for another reason?

Yes, after typing on an input field, to dismiss the keyboard I used tapAtPoint(which works fine). But here the issue comes after when I think, on applying scollTo('direction') it should go in either direction, but rather the screen stays still. The console shows me initially it is busy with threads and then app is idle comes 'n' number of times and on the UI nothing happens. Just still. No particular reason I could find too for the screen stuck as there was no interruption at the screen as well.

I was able to reproduce the issue, which looks like it occurs with any view placed before a scrollview. Although I haven't found the root cause yet, I did find that adding style={{flex: 1}} to the parent view seems to fix the problem - e.g.:
  <View testID={'screenView_id'} style={{flex: 1}}>
    <TextInput testID={'textInput_id'} placeholder={'Type here'}/>
    <ScrollView testID={'scrollView_id'}>
   ...
   </ScrollView>
   </View>

@jonathanmos any action items here?

We have hit the same problem as earlier, so it seems that this is not fixed.

Still seeing this problem.  The ScrollView is inside a SafeAreaView, but ScrollTo just displays "App synchronization debug: The app appears to be idle!"
Finally setting <SafeAreaView style={{flex: 1}}> and it works.

Also had to set style={{flex: 1}} on a Flatlist's parent, which was a Native-Base HStack.

This is STILL not fixed.

Anyone else running into this could consider this workaround
if (device.getPlatform() !== 'ios') {
const scrollView = element(by.type('android.widget.ScrollView'));
try {
if (direction === 'bottom') {
await scrollView.swipe('up'); // swiping up scrolls down
} else if (direction === 'top') {
await scrollView.swipe('down');
}
} catch (e) {
console.error(e)
}
}

I have the same problem. But none of the suggested fixes did it for me.
Simply unable to use detox on android because any of the drag, swipe, scroll gestures work.
Everything fine on IOS...
I wonder why there is not more people with this issue, should be a very common issue to bump into

I tried adding flex: 1 to the style for the parent container and it seems to be working so far.  We have a lot of scrollable screens in our app and I'll need to verify them all, but confidence is high.
Long term, it would be nice to understand why that workaround unblocks things and, if possible, make a fix for it.  Happy to help out in any way I can.

Any updates about 20.13.2-smoke.0?

Any updates about 20.13.2-smoke.0?

Did not work

@poojan010 would you mind to record a video artifact with an example of what's happening there on a scroll attempt?

sure i'll provide video today

Any updates about 20.13.2-smoke.0?

I've just given this a shot in hope this might help with some of the issues we have been running into with android.
Seems to have resolved the issue with scroll getting stuck, but we are still seeing swipe getting stuck in the same way.

@Seraphiyra well, as long as it does not break something and fix something, it is good for me to release. Thanks for the confirmation!
If someone can fiddle with our Android source for swipe handlers, similarly to #4225, please share your solution. We'll make sure to release a public beta as soon as you submit and it passes our E2E tests.

Not working for Me
https://github.com/wix/Detox/assets/63223116/c1ed2d40-1981-4be7-88e5-173c5df02344
simple.test.js
describe('Example', () => {
  beforeAll(async () => {
    await device.launchApp();
  });

  beforeEach(async () => {
    // await device.reloadReactNative();
  });

  it('scroll to bottom', async () => {
    await element(by.id('scroll-view')).scrollTo('bottom');
  });

  it('scroll to top', async () => {
    await element(by.id('scroll-view')).scrollTo('top');
  });
});

App.js
import { Button, ScrollView, StyleSheet, Text, View } from 'react-native'
import React from 'react'

const App = () => {
  return (
    <View style={{flex:1,backgroundColor:'white'}}>
      <ScrollView testID='scroll-view' style={{ flex: 1}}>
        <Text testID='hello-text'>Hello</Text>
        <View  style={{height:500}}/>
        <View  style={{height:500}}/>
        <Button title='Press Me' testID='button'/>
        <View  style={{height:500}}/>
        <View  style={{height:500}}/>
      </ScrollView>
    </View>
  )
}

export default App

const styles = StyleSheet.create({})

@poojan010 , what is happening here? 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯
🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯
🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯
Do I understand correctly that a scroll gesture is interpreted as some system UI action, and it gets interpreted by Android itself?

I had a busy day today, so I'd refrain from releasing when I'm leaving the office. Tomorrow I'll release that smoke version.

@Seraphiyra well, as long as it does not break something and fix something, it is good for me to release. Thanks for the confirmation!
If someone can fiddle with our Android source for swipe handlers, similarly to #4225, please share your solution. We'll make sure to release a public beta as soon as you submit and it passes our E2E tests.

@noomorph  I had a little bit of a poke into this, but alas no success😞
I tried a few things, but in the end by changing from API 33 -> 32  was able to get swipe to work for us again.  This was a not ideal, albeit quick, fix to enable us to keep our tests running and not block releases.
We currently use significantly more swipe actions than scroll actions in our test suite. So that means this will go into my backlog to poke at again (if others don't fix beforehand 🤞)

@Seraphiyra, thanks for trying! I hope someone takes it soon. I communicated the importance of these issues to my team, but the ETA is not clear yet.

@poojan010 I think that @gosha212 will look quite soon into your case. There's a plan to fix scroll/swipe conflicting with Android's gesture handling.

Hi @poojan010,
I'm working on a solution for your problem. A temporary solution is to disable the gesture navigation on your emulator. Here is more details:

Ran into this issue today, the workaround of adding style={{flex: 1}} to the parent view fixes the scrollTo command for us..
Android API 30, detox 20.14.8
Hope, there'll be a proper fix, soon!


Remove go modules

According to https://github.com/jaegertracing/jaeger-lib/pull/75#issuecomment-528639764, enabling go modules is more complicated when the library is on a version above 1.x, which is the case with jaeger-client-go and jaeger-lib.
For now, removing go modules. Will revisit in the future along with potential renaming of the path from /uber/ to /jaegertracing/
Reopens #382

It looks like the go.mod and go.sum files were not removed, so the latest release (2.18.0) can't be installed using go modules.

The previous releases couldn't be installed with go modules either.

2.17.0 is installable as v2.17.0+incompatible because there are no go.mod and go.sum files in the release: https://github.com/jaegertracing/jaeger-client-go/tree/85825f3f682a6fb24b12a4604be2a101432c7534
2.18.0 fails with go get<EMAIL_ADDRESS><EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

Ah, sorry, I see what you mean. I will remove mod files and do another release.


following instructions but getting an error with simple gradle file.

I'm following the instructions.    Using the latest j2objc  0.97   gradle 2.3   Mac OSX 10.9  java version "1.7.0_76"
I'm using a simple gradle file.  Just a few java classes & Interfaces.    the only dependencies are mockito and junit.
I did not edit the j2objc.gradle file as the instructions did not say to do so.
I'm getting the error:
gradle --stacktrace j2objcTranslate

Where:
Script '/Users/mattpease/IdeaProjects/clean_architecture_tests/j2objc.gradle' line: 161

What went wrong:
A problem occurred evaluating script.

Failed to apply plugin [class 'j2objc']
Could not create an instance of type J2objcPluginExtension_Decorated.

Try:
Run with --info or --debug option to get more log output.

Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating script.
at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:54)

My build.gradle
apply plugin: 'java'
sourceCompatibility = 1.7
version = '1.0'
repositories {
mavenCentral()
}
dependencies {
testCompile 'junit:junit:4.12'
testCompile 'org.mockito:mockito-core:1.10.19'
}
test {
testLogging {
events "passed", "skipped", "failed"
}
testLogging.showStandardStreams = true

}
apply from: 'j2objc.gradle'
j2objcConfig {
//    MODIFY to where your unzipped j2objc directory is located
//    NOTE download the latest version from: https://github.com/google/j2objc/releases
j2objcHome "/javalibs/j2objc-0.9.7"
//    MODIFY to where generated objc files should be put for Xcode project
//    NOTE these files should be checked in to the repository and updated as needed
//    NOTE this should contain ONLY j2objc generated files, other contents will be deleted
destDir "${projectDir}/j2objc-generated"
}

I saw you wanted a --info flag for another user's similar question.
Here is my --info output:
air-2:clean_architecture_tests mattpease$ gradle --info j2objcTranslate
Starting Build
Settings evaluated using empty settings script.
Projects loaded. Root project using build file '/Users/mattpease/IdeaProjects/clean_architecture_tests/build.gradle'.
Included projects: [root project 'clean_architecture_tests']
Evaluating root project 'clean_architecture_tests' using build file '/Users/mattpease/IdeaProjects/clean_architecture_tests/build.gradle'.
FAILURE: Build failed with an exception.

Where:
Script '/Users/mattpease/IdeaProjects/clean_architecture_tests/j2objc.gradle' line: 161

What went wrong:
A problem occurred evaluating script.

Failed to apply plugin [class 'j2objc']
Could not create an instance of type J2objcPluginExtension_Decorated.

Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.

Thank you!

Hi @formvoltron,
For now, just set line 161 to "String xcodeProjectDir = null". I'll talk
with @confile about the proper fix for this.
On Sun, Apr 12, 2015 at 3:26 PM formvoltron<EMAIL_ADDRESS>wrote:

I saw you wanted a --info flag for another user's similar question.
Here is my --info output:
air-2:clean_architecture_tests mattpease$ gradle --info j2objcTranslate
Starting Build
Settings evaluated using empty settings script.
Projects loaded. Root project using build file
'/Users/mattpease/IdeaProjects/clean_architecture_tests/build.gradle'.
Included projects: [root project 'clean_architecture_tests']
Evaluating root project 'clean_architecture_tests' using build file
'/Users/mattpease/IdeaProjects/clean_architecture_tests/build.gradle'.
FAILURE: Build failed with an exception.

Where:
Script
'/Users/mattpease/IdeaProjects/clean_architecture_tests/j2objc.gradle'
line: 161
What went wrong:
A problem occurred evaluating script.
Failed to apply plugin [class 'j2objc']
Could not create an instance of type J2objcPluginExtension_Decorated.

Try:
Run with --stacktrace option to get the stack trace. Run with --debug
option to get more log output.
Thank you!
—
Reply to this email directly or view it on GitHub
https://github.com/brunobowden/j2objc-gradle/issues/25#issuecomment-92144750
.

Works now, Very good!  I knew it was something very simple.  Just didn't know which piece to fiddle with.
Now on to figuring out how to integrate into my XCode project.

@brunobowden This issue seems to be fixed now?


About memory allocation

I want to do the VQA finetuning. I do not have A100 GPUs, and I could only run on 4 2080Ti GPUs with 11019MB memory. I tried to reduce the batch size to 1 but still got "CUDA out of memory". I want to inquire whether it is normal?

@tingxueronghua Were you able to resolve the problem? I am able to start finetuning on my local gpu but on any other machine I get the same CUDA out of memory error which is not the correct behavior.

maybe you made the same mistake with me? In distributeddataparallel, the batchsize means that per GPU. So when i set batchsize to 4, it means 16 totally. and i can run the code when i set batchsize to 2.

Thanks for your quick reply!
I am running it with batchsize 1 yet getting this error even with single gpu. :/


Check all OnStop... works

Describe the bug
OnStopClient and OnStopServer dont seem to be called correctly some of the time. It seems hard to set some of these cases up in unity tests as they require 2 instances of unity to run.
These are the cases we need to check work.

Server only (OnStopServer)

[ ] GameObject.Destroy
[ ] NetworkServer.Destroy
[ ] Owner Disconnect
[ ] scene change (if destroyed locally?)
[ ] server stopped
[ ] exit play mode

Client only (OnStopClient)

[ ] Destroy Message

[ ] spawned objects
[ ] scene objects
[ ] custom UnSpawnDelegate

[ ] Hide Message

[ ] spawned objects
[ ] scene objects
[ ] custom UnSpawnDelegate

[ ] Disconnect

[ ] spawned objects
[ ] scene objects
[ ] custom UnSpawnDelegate

[ ] scene change (if destroyed locally?)

[ ] spawned objects
[ ] scene objects
[ ] custom UnSpawnDelegate

[ ] exit play mode

[ ] spawned objects
[ ] scene objects
[ ] custom UnSpawnDelegate

Host (OnStopClient+OnStopServer)
...some mix of calls above

Related Issues
https://github.com/vis2k/Mirror/issues/1940
https://github.com/vis2k/Mirror/issues/2119
https://github.com/vis2k/Mirror/issues/2232
Related Pull requests
https://github.com/vis2k/Mirror/pull/2313

need step by step instructions on how to reproduce.
closing for now.


vimPlugins.fern-vim: init at 2020-12-22

Motivation for this change
Added the fern.vim vim plugin.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Please never merge master into a branch to fix a conflict. I am going to fix that now once because I need to add another commit.

Please never merge master into a branch to fix a conflict. I am going to fix that now once because I need to add another commit.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108213 run on x86_64-linux 1

27 packages built:

spacevim
vimPlugins.Spacegray-vim
vimPlugins.YouCompleteMe
vimPlugins.coc-nvim
vimPlugins.completion-nvim
vimPlugins.defx-git
vimPlugins.deol-nvim
vimPlugins.fern-vim
vimPlugins.nvim-highlite
vimPlugins.nvim-lspconfig
vimPlugins.nvim-lsputils
vimPlugins.nvim-treesitter
vimPlugins.nvim-treesitter-context
vimPlugins.nvim-treesitter-textobjects
vimPlugins.telescope-nvim
vimPlugins.vim-airline
vimPlugins.vim-clap
vimPlugins.vim-floaterm
vimPlugins.vim-hexokinase
vimPlugins.vim-lsp
vimPlugins.vim-ocaml
vimPlugins.vim-polyglot
vimPlugins.vim-visual-multi
vimPlugins.vim-vsnip
vimPlugins.vimsence
vimPlugins.vista-vim
vimPlugins.yats-vim

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108213 run on x86_64-linux 1

27 packages built:

spacevim
vimPlugins.Spacegray-vim
vimPlugins.YouCompleteMe
vimPlugins.coc-nvim
vimPlugins.completion-nvim
vimPlugins.defx-git
vimPlugins.deol-nvim
vimPlugins.fern-vim
vimPlugins.nvim-highlite
vimPlugins.nvim-lspconfig
vimPlugins.nvim-lsputils
vimPlugins.nvim-treesitter
vimPlugins.nvim-treesitter-context
vimPlugins.nvim-treesitter-textobjects
vimPlugins.telescope-nvim
vimPlugins.vim-airline
vimPlugins.vim-clap
vimPlugins.vim-floaterm
vimPlugins.vim-hexokinase
vimPlugins.vim-lsp
vimPlugins.vim-ocaml
vimPlugins.vim-polyglot
vimPlugins.vim-visual-multi
vimPlugins.vim-vsnip
vimPlugins.vimsence
vimPlugins.vista-vim
vimPlugins.yats-vim

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108213 run on x86_64-darwin 1

4 packages built:

spacevim
vimPlugins.YouCompleteMe
vimPlugins.vim-clap
vimPlugins.vim-hexokinase

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108213 run on x86_64-darwin 1

4 packages built:

spacevim
vimPlugins.YouCompleteMe
vimPlugins.vim-clap
vimPlugins.vim-hexokinase

Please never merge master into a branch to fix a conflict. I am going to fix that now once because I need to add another commit.

Oh, I'm sorry, I followed this suggestion and thought it would be the ideal way of keeping my branch up to date. I initially tried a rebase, which pulled all of master's recent commits into the pull request, which was definitely a bad idea, so I thought a merge was the right thing to do. For future reference, what is the recommended way of doing this?
In any case, thank you for approving my request.

Please never merge master into a branch to fix a conflict. I am going to fix that now once because I need to add another commit.

Oh, I'm sorry, I followed this suggestion and thought it would be the ideal way of keeping my branch up to date. I initially tried a rebase, which pulled all of master's recent commits into the pull request, which was definitely a bad idea, so I thought a merge was the right thing to do. For future reference, what is the recommended way of doing this?
In any case, thank you for approving my request.


feat: geographic plotting of observation locations

This is something I feel I could work on! Would you feel comfortable adding metpy as a dependency, or would that be a bit heavier than you were thinking? Incorporating metpy would also give us access to easy unit handling and conversions, if we wanted to implement that in the future.

Metpy is great, and it is always a bonus for us to use unidata tools (UCAR connection).
Metpy seems really well supported and widely used, so happy to have it as a dependency if you think it is the right tool for the job!

Thinking about this a bit more, Metpy could be great to leverage for their observational data. I think prepbufr is in their roadmap, so you could use this to convert observations (e.g. prepburf, etc.) to obs_seq directly in python.


Using in CI - Github actions

hello and thanks for this awesome package.
I added a test that runs a function that uses env.NODE_ENV.
When test runs in CI, I see the following error.

This is how I try to access the env:
        env:
          NODE_ENV: ${{ env.NODE_ENV }}

But nothing seems to work.
Any ideas how to fix?

Found the answer myself, I wasn't building the project in the previous step.

You can set a custom env in your CI pipeline https://docs.github.com/en/actions/learn-github-actions/variables


[BUG] Upgrade from v1.1.2 to v1.2.1-rc1 stuck in upgrading system service, with pending rancher-monitoring pods

Describe the bug

Try to upgrade the single nodes Harvester from v1.1.2 to v1.2.1-rc1, the process stuck in Upgrading System Service

Check the hvst-upgrade-qngtb-apply-manifests job logs, it display Waiting for 1 pods to be ready...
│ hvst-upgrade-qngtb-apply-manifests-wjvsk harvester-system           pcidevices-controller   http://harvester-cluster-repo.cattle-system.svc/charts   harvester-pcidevices-controller   fal │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk harvester-system           vm-import-controller    http://harvester-cluster-repo.cattle-system.svc/charts   harvester-vm-import-controller    fal │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk wait for rollout of monitoring                                                                                │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk deployment "rancher-monitoring-operator" successfully rolled out                                                                                │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk Waiting for deployment "rancher-monitoring-prometheus-adapter" rollout to finish: 0 of 1 updated replicas are available...                        │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk deployment "rancher-monitoring-prometheus-adapter" successfully rolled out                                                                        │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk deployment "rancher-monitoring-kube-state-metrics" successfully rolled out                                                                        │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk Waiting for deployment "rancher-monitoring-grafana" rollout to finish: 0 of 1 updated replicas are available...                                   │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk deployment "rancher-monitoring-grafana" successfully rolled out                                                                                │
│ hvst-upgrade-qngtb-apply-manifests-wjvsk Waiting for 1 pods to be ready...

Two pods are keep in pending state

cattle-monitoring-system   alertmanager-rancher-monitoring-alertmanager-0
cattle-monitoring-system   prometheus-rancher-monitoring-prometheus-0

To Reproduce
Steps to reproduce the behavior:

Prepare a single node Harvester
Create the vlan1 network and another external vlan network
Set the backup target to nfs server
Create a VM and keep in running state
Create some file and record the checksum value
Create a backup from the running VM
Create another file and record the checksum value
Create a snapshot from the running VM
Create another vm and keep in stop state
Repeat step 6, 7, 8 to prepare backup and snapshot backup
Keep on VM in running and another in Stopped
Upgrade to v1.2.1-rc1

Expected behavior

Can upgrade the single nodes Harvester from v1.1.2 to v1.2.1 sucessfully
Support bundle

supportbundle_9978bde7-4d72-434a-9031-130998856615_2023-10-11T10-20-17Z.zip
Upgrade log
hvst-upgrade-qngtb-upgradelog-archive-2023-10-11T10-30-13Z.zip
Environment

Harvester ISO version: v1.1.2 to v1.2.1-rc4
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Single node on bare machine

@TachunLin
From the SB file yamls/namespaced/cattle-monitoring-system/v1/pods.yaml, those 2 PODs are the victims of Insufficient CPU.
    name: prometheus-rancher-monitoring-prometheus-0
    namespace: cattle-monitoring-system

  status:
    conditions:
    - lastProbeTime: "null"
      lastTransitionTime: "2023-10-11T07:34:58Z"
      message: '0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes
        are available: 1 No preemption victims found for incoming pod.'
      reason: Unschedulable
      status: "False"
      type: PodScheduled
    phase: Pending
    qosClass: Burstable

      time: "2023-10-11T07:34:56Z"
    name: alertmanager-rancher-monitoring-alertmanager-0
    namespace: cattle-monitoring-system
  status:
    conditions:
    - lastProbeTime: "null"
      lastTransitionTime: "2023-10-11T07:34:56Z"
      message: '0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes
        are available: 1 No preemption victims found for incoming pod.'
      reason: Unschedulable
      status: "False"
      type: PodScheduled
    phase: Pending
    qosClass: Burstable

@w13915984028 , thanks for checking the state and support bundle.
Just check the current upgrade process still stuck in upgrading system service.

The Reserved CPU reach the relatively high usage, that would probably the reason for the pod pending.
The single node harvester have 8 core cpu with two virtual machines, each allocate 1 core.

And also have two vm backups and vm snapshot backup.
Not sure whether it's the reason to cause the waiting for cpu situation.

It looks in-between the upgrade from v1.1.2 to v1.2.0, 8 cores are not enough.
https://docs.harvesterhci.io/v1.1/install/requirements

x86_64 only. Hardware-assisted virtualization is required. 8-core processor minimum for testing; 16-core or above required for production

And, the system is stuck in kubectl rollout status --watch=true -n $namespace $resource_type $name for statefulset prometheus, the later can't be scheduled.

Retried the single nodes upgrade on the node machine contains enough cpu resources (16 core)
This time we can successfully upgrade to v1.2.1-rc1, did not stuck in the upgrading system service.

@TachunLin Would you mind to close this ticket? thanks.


[BUG] the meaning of the param of the teaser solver

Describe the bug
Hello, would like to ask the meaning of the param of the teaser solver, how should it be adjusted to suit the new data set
// Prepare solver parameters
teaser::RobustRegistrationSolver::Params params;
params.noise_bound = NOISE_BOUND;
params.cbar2 = 1;
params.estimate_scaling = false;
params.rotation_max_iterations = 100;
params.rotation_gnc_factor = 1.4;
params.rotation_estimation_algorithm =
teaser::RobustRegistrationSolver::ROTATION_ESTIMATION_ALGORITHM::GNC_TLS;
params.rotation_cost_threshold = 0.01;

It's hard to explain if you didn't read the paper.


python311Packages.numpyro: 0.13.2 -> 0.14.0

Description of changes
Changelog: https://github.com/pyro-ppl/numpyro/releases/tag/0.14.0
cc @fabaff
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 293103 run on aarch64-linux 1

4 packages marked as broken and skipped:

python311Packages.bambi
python311Packages.bambi.dist
python311Packages.pymc
python311Packages.pymc.dist

4 packages built:

python311Packages.arviz
python311Packages.arviz.dist
python311Packages.numpyro
python311Packages.numpyro.dist

Result of nixpkgs-review pr 293103 run on x86_64-linux 1

8 packages built:

python311Packages.arviz
python311Packages.arviz.dist
python311Packages.bambi
python311Packages.bambi.dist
python311Packages.numpyro
python311Packages.numpyro.dist
python311Packages.pymc
python311Packages.pymc.dist


Ray tracing cube prototype

Description
Includes a prototype for ray tracing with output on a cube. This is meant to be prototype that will be integrated with rest of workflow once finalized.
Motivation and Context

Ray tracing output on a cube that can then be used for high res delay computation
Breaks, integration along LOS ray as integration over steps between different height levels
There is more room for vectorization at the expense of memory usage
Eliminates need for custom cython/ pybind11 bindings
Additional checks will be needed on parsing inputs to increase padding for ray tracing operations - depending on max altitude of model being used

How Has This Been Tested?

Golden tests still pass
Numerical sniff test for values - seems reasonable
Needs more elaborate testing

@piyushrpt Reviewed and approved! I'll let you merge in case you need to make any changes.


Backup documentation has correct --output flag

Currently, the docs point to either use:

This should be --output rather. Since if you use the flag: -output it will backup to the utput directory.

DOH! Thanks for this catch!
fixed in https://github.com/FeatureBaseDB/featurebase-docs/pull/132


Attempt to index a boolean value

Describe the bug
Since the recent update I get an error when starting nvim on linux (not on windows though). The error message is:
E5113: Error while calling lua chunk: ...site/pack/packer/start/dressing.nvim/plugin/dressing.lua:1: attempt to index a boolean value
System information

OS: linux
Neovim version: 0.8.1
Is this related to a specific vim.ui.select backend? If so, which one?
Dressing config: After some testing I removed the config and the error is still persistent

-- Paste your call to require("dressing").setup(...) in here

To Reproduce
Steps to reproduce the behavior:

Install the plugin under linux

If possible, provide a minimal file that will trigger the issue (see
tests/manual
for examples of short ways to call vim.ui.*):
minimal code here

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I tried to find out what is going on and the problem is that the call to 'require("dressing")' in plugin\dressing is equated to true and not to a reference

This is going to be because of some conflict you have in your config. If require("dressing") is returning true, it either means that you have another module in your runtimepath at lua/dressing.lua or lua/dressing/init.lua that is returning a boolean (and is resolved earlier than the one in the plugin), or it means that you've monkey patched require and it's doing something very unexpected.

 There was indeed a copy in the root of my nvim folder. It was my previous settings file for the plugin that I backed up before setting the new win_options. Somehow I seem to have forgotten to change the location. Sorry for the unnecessary work!


net: LookupTXT fails when TXT record contains multiple strings

What version of Go are you using (go version)?
Go 1.4
What operating system and processor architecture are you using?
OS X 10.10.3
What did you do?
DNS TXT lookup on _spf.facebook.com:
package main

import "fmt"
import "net"

func main() {
	txt, err := net.LookupTXT("_spf.facebook.com")
	fmt.Println(err)
	fmt.Println(txt)
}

What did you expect to see?
"v=spf1 ip4:<IP_ADDRESS> ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/24 ip4:<IP_ADDRESS>/25 i" "p4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/24 mx -all"
dig _spf.facebook.com TXT returns this:
;; QUESTION SECTION:
;_spf.facebook.com.		IN	TXT

;; ANSWER SECTION:
_spf.facebook.com.	3599	IN	TXT	"v=spf1 ip4:<IP_ADDRESS> ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/24 ip4:<IP_ADDRESS>/25 i" "p4:<IP_ADDRESS>/25 ip4:<IP_ADDRESS>/24 mx -all"

What did you see instead?
lookup _spf.facebook.com on <IP_ADDRESS>:53: no such host
Go fails to lookup TXT records which consist of multiple character strings.
RFC 1035 3.3.14.
3.3.14. TXT RDATA format

    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    /                   TXT-DATA                    /
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

where:

TXT-DATA        One or more <character-string>s.

<character-string> is defined in section 3.3. of the same RFC 1035
<character-string> is a single
length octet followed by that number of characters.  <character-string>
is treated as binary information, and can be up to 256 characters in
length (including the length octet).

Wrote a fix for it: https://go-review.googlesource.com/#/c/8966/


ReferenceInput Issue with parse prop

I need to save reference input value as an object, so according to the docs i'm using parse function
const parse => id => {/*some object with */}
<ReferenceInput
  label='post'
  source='post_id'
  reference='posts'
  allowEmpty
  parse={parse}
>
  <SelectInput optionText='title' />
</ReferenceInput>

Now, when I'm selecting something the option is not selected when I click on it, I assume because option is selected by id from value, where i have an object. Couldn't find anything in both admin-on-rest and material-ui

You might not need parse. SelectInput with object as choices' value is totally fine.

But i don't have choices, choices are fetched by reference

If your backend can provide a field, for example information, with the desired object inside, then you can set optionValue to information. Otherwise, you have to modify ReferenceInput.

Check out redux-form: in addition to parse, you probably have to use normalize.
http://redux-form.com/6.7.0/docs/api/Field.md/


how to uninstall taichi (legacy branch)

After experiencing the same issue as #40, I found all my other conda environment are crashed because when I import taichi, seems it will automatically bind to the error taichi rather than the one I pip installed... How can I uninstall the taichi(legacy branch)?

Removing the related path in ~/.zshrc would let my other conda environment work well again, but still wondering if I want to uninstall taichi(legacy branch), just deleting the taichi repo dir folder is okay?


tsc doesn't resolve module specified in the typeRoots

TypeScript Version:  2.1.5
I have the following directory structure:
tsconfig.json
a.ts
node_modules
|--- custom
     |--- rembo
           |---index.d.ts

The content of index.d.ts is the following:
export declare class Rembo {
    name: string;
}

I reference this module in a.ts:
import {Rembo} from 'rembo';
The package.json is the following:
{
  "compilerOptions": {
    "moduleResolution": "node",
    "module": "es6",
    "target": "es6",
    "typeRoots": [
      "node_modules/custom"
    ]
  }
}

The problem is that rembo module can't be resolved. When compiled, I get the following result:
$ tsc --traceResolution
======== Resolving type reference directive 'rembo', containing file 'D:/Projects/typescript/__inferred type names__.ts', root directory 'D:/Projects/typescript/node_modules/custom'. ========
Resolving with primary search path 'D:/Projects/typescript/node_modules/custom'
File 'D:/Projects/typescript/node_modules/custom/rembo/package.json' does not exist.
File 'D:/Projects/typescript/node_modules/custom/rembo/index.d.ts' exist - use it as a name resolution result.
Resolving real path for 'D:/Projects/typescript/node_modules/custom/rembo/index.d.ts', result 'D:/Projects/typescript/node_modules/custom/rembo/index.d.ts'
======== Type reference directive 'rembo' was successfully resolved to 'D:/Projects/typescript/node_modules/custom/rembo/index.d.ts', primary: true. ========
a.ts(3,21): error TS2307: Cannot find module 'rembo'.

I don't understand why the error, since it reports then:

Type reference directive 'rembo' was successfully resolved to 'D:/Projects/typescript/node_modules/custom/rembo/index.d.ts', primary: true.

TypeRoots is useful for global declarations, things that you do not import, e.g. node definition file. when the compiler starts it loads all files under typeRoots and adds them in the global scope.
Seems like this is not what you are looking for, what you need is Path mapping:
{
  "compilerOptions": {
    "moduleResolution": "node",
    "module": "es6",
    "target": "es6",
    "baseUrl": "./",
    "paths": {
      "*" : ["node_modules/custom/*"]
    }
  }
}

This tells the compiler to look under <baseUrl>/node_modules/custom for any import it sees.

Thanks, a lot for you quick reply. As I understand, the node_modules/@types are automatically added to "paths", correct? I have an import of a module residing inside node_modules/@types and don't have "paths" configured for node_modules/@types, and module is still successfully resolved.
And is my understanding correct that both "typeRoots" and "types" is used for global modules resolve?

that is correct. I would not think about typeRoots unless you are using something global, e.g. node. otherwise, just think about modules.

Got it, thanks. Where can I read about all supported patterns for paths? For example, can I match part of the module name and provide mappings for that part? Or only * pattern is supported?

What if the node_modules including node_modules/@types are outside the source directory alltogether?
SRC=$HOME/Pojects/demo
DEST=/tmp/build

ln -s $SRC/package.json $DEST/package.json
cd $DEST
npm install

cd $SRC
tsc --outDir $DEST/build --typeRoots $DEST/???

this doesn't work
(ts 2.1.6)

paths is relative to the baseUrl and not the projectRoot. so you can make the baseUrl whatever you want.


Why is verify JWS based of of the privateKey and not publicKey?

It is just a question in terms of it does not make much sense to make a signed JWS, and then someone else shall verify that, they need the signers private key?
Or am I missunderstanding its usage?

@vongohren this was a docs typo, which was fixed in the last release


Add vumi_redis_tool task for persisting keys.

Currently there is only one for expiring them.

:+1: when travis is happy.


Just wanted to say thank you for releasing the script to set up a custom signet

We used it and its great.
Question about the wallet, the seed words are stored in the browser local storage I suppose, how do you store the mnemonic safely?

For now the seed is in indexed db, we're adding an option to encrypt it as well.

Thanks for the reply, good luck I will follow the progress