not working with Electron-packager

Hi there.
Was testing stuff out while making an app and noticed that events are not fired after the application was packaged.
Tested this with simple
gkm.events.on('key.*', function(data) {
  console.log(data[0]);
});

and while unpackaged it works, after electron-packager it stops triggering all possible events.

Hello,
This is unlikely to be related to gkm itself. I'm going to guess that when your electron application is packaged, the node modules are packaged within an asar file (https://electronjs.org/docs/tutorial/application-packaging) and as such, when
https://github.com/tomzx/gkm/blob/b2d7bc986b4dbc8e5d5a6027760e10e21512df32/gkm.js#L10
is called from gkm.js, java cannot find the jar file since it's not in the user file system but within that asar archive. I believe it should be possible for you to unpack the asar when installing the packaged application, which should solve this issue.

Hi,
Thank you for answering. Would you be so kind and guide me through that process?
Should I unpack the whole thing or just the gkm.js? Should I somehow point to it after unpacking? etc.
And are there any downsides to unpacking the asar doing so?

It's been quite a while since I packaged any electron application, but back then I relied on https://github.com/electron-userland/electron-packager. Given their documentation (https://github.com/electron-userland/electron-packager/blob/master/docs/api.md#asar), if you aren't packaging the source code into an asar archive, you should have nothing to do.
I'd suggest you first package your application, then install it, then go to the directory where it was installed and check whether you can find a node_modules directory inside. If you can, then check if you can find gkm directory within it. If you can, then things should work the same as if you were in your development environment. Also make sure that you can find the gkm.jar and JNativeHook.jar files.
On the other hand, if you can't find the node_modules nor the gkm directories, then it's likely that your source code is archived in an asar file. If you're using electron-packager, you can either disable using asar or only unpack a certain part of it (I never did myself). See the documentation I pointed at to know how to do that.
I'm not knowledgeable enough to know what are the downsides to unpacking, other than it exposes your source code on the file system.

Yes. That helped a lot. I was able to unpack it successfully using asar.unpackDir and unpacking node_modules. Unpacking just the gkm resulted in error since it wasn't able to locate eventemitter2 module. I did not try to unpack just those two, will maybe experiment a bit more, but quite happy with the result already.
Thank you.

Happy to see it worked out for you!


Triangulation of geo coordinates

Hi.
Thanks for the great library. I was going to use it to triangulate sets of lat/lang values. Unfortunately the algorithm throws a NullReferenceException in CalculateVertexCentroid because vertexIndices is null. Turns out that variance between points is too small (in my case longitude changes in 38.3536 - 38.3668 range, and latitude in even smaller range). If I multiply the values by 10000 triangulation runs just fine.
Is this the intended/expected behaviour?
The algorithm is too  complex for me to figure out if there is a more elegant solution than the one I use.

I also ran into this issue, with general high-resolution data - working with angles in radian, where the data points variance is sometimes as small as 0.1 millirad (1e-4 radian).

sorry, I've been away from the project for a while. If you send me some test data, I can see if I can get it to work with the raw values. Also - if I recall correctly - there are some optional tolerances that can be set.

Sorry for the delayed response. Here's the set that gives me the exception. Actually, it's 100 points, but I guess 10 should be enough.
38.359052882483887, 56.02282713353344
38.365112304786429, 56.0218508829207
38.36001531819803, 56.023416987346707
38.35803713543698, 56.023549757868032
38.357863216371037, 56.02234061233267
38.35408882004424, 56.020852611291083
38.365794195423483, 56.020557681089535
38.356048644009491, 56.022278568289735
38.365965425182253, 56.023300153013373
38.355903158948735, 56.022913716654188


Protocol version 5.2 not supported

I get this error:
[jupyter-kernel.jar] python kernel started.
Exception in thread "Thread-0" java.lang.RuntimeException: [jupyter-kernel] Protocol version 5.2not supported by this kernel
        at org.jupyterkernel.kernel.MessageObject.checkAllowedProtocolVersion(MessageObject.java:106)
        at org.jupyterkernel.kernel.MessageObject.read(MessageObject.java:176)
        at org.jupyterkernel.kernel.Kernel.dispatch(Kernel.java:136)
        at org.jupyterkernel.kernel.Session.run(Session.java:239)

@debjan Did you get this to work?  I'm trying to use this kernel now and I've getting the same error, but just for protocol version 5.3.
@fiber-space any chance of getting this fixed?

unfortunately not, thou I didn't try too hard, as this is not the only kernel that can't cope with jupyter dev

Thanks for the reply @debjan .  I did try bypassing the version check, but then then ran into other issues with the communication.  It seems the newer versions of the protocol do need explicit support added.

Protocol version 5.3 is now supported. Message structures have changed very little but Jupyter sends now a comm_info_request at startup which wasn't handled yet. I also removed a dependency on javax/xml/bind/DatatypeConverter which caused some trouble in Java 9.

Thanks for your work on this @fiber-space , I'll give this another shot and try to load up Lucee Server.

Hi @fiber-space , it's still not working for me on the latest version:
Exception in thread "Thread-0" java.lang.NullPointerException
        at org.jupyterkernel.json.messages.T_JSON.toJSON(T_JSON.java:149)
        at org.jupyterkernel.json.messages.T_JSON.toJSON(T_JSON.java:149)
        at org.jupyterkernel.kernel.MessageObject.send(MessageObject.java:192)
        at org.jupyterkernel.kernel.Kernel.dispatch(Kernel.java:173)
        at org.jupyterkernel.kernel.Session.run(Session.java:239)

I created a new issue here: https://github.com/fiber-space/jupyter-kernel-jsr223/issues/15


simple RTMP bottlenecks

I have a RTMP application that is realy simple I mean there is no encoding stuff on it:
application push {
    live on;
}

I think the only bottleneck will be network one yeah? Because I think it likes simple file serving in webservers (Nginx, Apache, or etc) then there will be no other limitation in push and play and if server has the enough network connection then can Publish and Play N numbers of videos on RTMP, Am I right?

Why was this closed without a response? Did you find a solution to your question?


Incompatibility with IE/Enchiridion/Optifine

I think this is Optifine's doing but I thought I'd open a issue here anyway to make you aware of the problem:
https://github.com/sp614x/optifine/issues/244

I wouldn't even know where to begin, since there's zero mention in the log

Crash log with this issue:
http://pastebin.com/RU1R8Kv1
Seems to say nothing but I'm not very good at reading logs.

The error:
[11:57:15] [Client thread/ERROR] [FML/]: Caught exception from immersiveengineering
java.lang.StackOverflowError
at net.minecraft.client.gui.FontRenderer.func_78263_a(FontRenderer.java:745) ~[bdl.class:?]
at blusunrize.immersiveengineering.client.IEItemFontRender.getCharWidthFloat(IEItemFontRender.java:118) ~[IEItemFontRender.class:?]
at net.minecraft.client.gui.FontRenderer.func_78263_a(FontRenderer.java:745) ~[bdl.class:?]
at blusunrize.immersiveengineering.client.IEItemFontRender.getCharWidthFloat(IEItemFontRender.java:118) ~[IEItemFontRender.class:?]
at net.minecraft.client.gui.FontRenderer.func_78263_a(FontRenderer.java:745) ~[bdl.class:?]
at blusunrize.immersiveengineering.client.IEItemFontRender.getCharWidthFloat(IEItemFontRender.java:118) ~[IEItemFontRender.class:?]
at net.minecraft.client.gui.FontRenderer.func_78263_a(FontRenderer.java:745) ~[bdl.class:?]
at blusunrize.immersiveengineering.client.IEItemFontRender.getCharWidthFloat(IEItemFontRender.java:118) ~[IEItemFontRender.class:?]
It looks like IE is patching the FontRenderer to call IEItemFontRender.getCharWidthFloat(), which calls back the original method, which causes an endless loop.
Because IE and OptiFine seem to work, then most probably Enchiridion is also patching FontRenderer and causing the IE patch to generate a wrong code.
Summary:

OptiFine changes FontRenderer (required)
Enchiridion probably patches FontRenderer (no idea why)
IE tries to patch the patched FontRenderer and generates invalid code causing the endless loop

Because of problems like that, the class patching should be avoided and all base class changes should be delegated to Forge. OptiFine takes care to reflect all base class changes which Forge does and to be compatible with it.

My font and ie's font don't interact at all. We're both extending FontRenderer and using our own font instances. Not patching the class. They work fine without optifine.

Understandable that you can't work around every other mod out there though I'm sad to have to keep Enchiridion disabled. Can't play with this many mods without Optifine and IE just brings more to my world.
You've done a great mod though and next world I make I might go without IE.

Then the question is why is the IE FontRenderer causing an endless loop only when Enchiridion is added to the mix?

This may be a total coincidence.
OptiFine is adding a private method getCharWidthFloat() which is being called at line 745. This is absolutely safe as the private method can not be overriden by a subclass.
If IE is extending the class and adding a public method with the same name AND someone else is changing the FontRenderer method signature to public via ASM then the IE method will override the OptiFine method and it will cause the problem exactly as the stack trace shows.
Is someone changing the private FontRenderer methods to public via ASM? Forge maybe?

That would explain it then. I have all things being made public in my AT. I was lazy :P. I should just change it to the specific things I need.

Confirmed, changing my AT from 4 lines to 23 fixed the issue.

What a convoluted bug :-)


Absolute path

Not sure if there is a better way to do this, but I'd like to be able to reference the absolute path of the assets folder so I can place js/json files there from transactions which can be easily imported into my planaria.js by calling require().

sorry just saw this because github never sends me notifications. going to have to find a way to track all the project activities somehow because github doesn't.
is this still relevant after the file system addition? If so i will look into it and merge

Nope. Totally not relevent any more.


Installation problem - (OSX version - 10.11.3 (15D21) , Xcode Version - 7.3 (7D175))

sudo gem install jazzy
Building native extensions.  This could take a while...
ERROR:  Error installing jazzy:
ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile
make "DESTDIR="
make: *** No rule to make target "/Applications/Xcode', needed by autolink.o'.  Stop.
Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/redcarpet-3.3.4 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/gems/redcarpet-3.3.4/ext/redcarpet/gem_make.out

Hi,
It's not clear from what you've provided that this is a nokogiri issue. I'm going to close; if you can, please provide details specific to Nokogiri not installing, including:

command that you ran (preferably gem install nokogiri and not through bundler)
if bundler, then provide bundler configuation options
output from the command
additional logfiles (e.g. mkmf.log)

I'm happy to reopen if you can provide additional details.

I have just run the command : "  sudo gem install jazzy " .... As mentioned in the documentation. It throws me the above mentioned error.


Consider using children prop instead of label for Button component.

Children prop for button is more practical then label prop.

Fixed in #92


Make it clearer that this is the new official site, with a clearer link to the old one

Describe the problem
As talked about in #179 it was unclear to me (and others) that there is a new version of the site and that you can find the old one on another subdomain. Currently there is a paragraph that kind of explains this with a link to the old version. But this is in my opinion very easily missed. And seeing as this site does not yet have all the information of the old one, I think it would benefit everyone if this was made more clear.
Describe the proposed solution
I am not an UX designer, but I think a banner in the header of every page would be the most clear. Maybe in yellow so that it looks like a warning. Something along the lines of: "You're browsing the new improved version of the website, not everything is already here so click here to go to the old version."
Maybe retain the banner for a while even when all information is here, just so that people know this is the new official one.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Sorry for the late comment, but I like this. Not too much in your face and especially the "Old Wiki" link in the navbar makes things really clear to me. Thanks for your quick work!


Unable to Install version 1.3.1 via npm install

Hi There.  Unable to Install version 1.3.1 via npm install.  Is it possible this has not been pushed to npm?

@alexmasita Just published it. Sorry for the delay!

Super @trmcnvn.  Thank you.


feat(zrepl): bumping the replica version

As we have made rebuilding protocol changes, so bumping the replica verison here and also adding support for backward compatibility.
Signed-off-by: Pawan<EMAIL_ADDRESS>

merging this as this depends on https://github.com/openebs/cstor/pull/262


Approved payments erroneously cancelled

Approved payments erroneously cancelled
An approved payment will be erroneously cancelled if a user has two tabs open on the Zip pay hosted page and chooses to return to the store in one of those tabs and then completes the payment process in the other tab.
Steps to reproduce
This issue is easiest to replicate using two browser tabs and these steps assume that the user is at the payment step of the checkout.

Select Zip as the payment method and proceed to the Zip hosted payment page.
In a second tab, select Zip again and proceed to the Zip hosted payment page.
In the second tab, click the "Back to Store" link. (Logs indicate a call to /zippayment/complete/?result=cancelled...).
In the first tab, proceed through the payment steps on the Zip hosted payment page.
Upon returning to the store a payment error will be encountered.

After completing the payment and returning to the store, logs will first show a call to /zippayment/complete/?result=approved..., then a charge request is attempted with logged Charge Payload:- {"authority":{... which will receive a 403 with the message Authority request - xxxxxxx is not approved.
Upon receiving the 403, the approved order is then erroneously cancelled and the user is shown a generic error page, which likely states something along the lines of "General Error An error occurred while processing your request.".
The cause
The charge request uses the incorrect Zip checkout ID due to Zip\ZipPayment\Helper\Payload::getAuthority() fetching this from the additional_information field in the quote payment object, which may have changed since the user initially proceeded to the Zip hosted payment page.
This incorrect Zip checkout ID is used in the charge payload and results in an error after which the module cancels the order.
The fix
Either use the checkout ID returned by the Zip hosted payment page instead of fetching it from the quote payment, or alternatively, track multiple payments against a quote instead of assuming that there will be only one.
Example logs
[2021-06-21 10:35:27] zipMoneyLog.INFO: Starting Checkout [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Checkout Method:- guest [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Is Allowed Guest Checkout :- 1 [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Is Customer Logged In :-  [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Shipping Required:- Yes [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: 499-0-0-499 [] []
[2021-06-21 10:35:27] zipMoneyLog.DEBUG: Checkout Request:- {"type":"standard","shopper":{"first_name":"Testee","last_name":"Tester","phone":"+61412123123","email":"test@test.com","billing_address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"order":{"reference":"67000000078","amount":499,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"items":[{"name":"Gnarly Bedside","amount":499,"reference":"62263","description":"The Gnarly two-drawer bedside is just gnarly.","quantity":1,"type":"sku","image_uri":"http:\/\/blah.localhost\/static\/version1623719616\/frontend\/Testing\/blah\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/blah.localhost\/Gnarly-bedside","product_code":"123363"}],"cart_reference":"265392"},"metadata":{},"config":{"redirect_uri":"http:\/\/blah.localhost\/zippayment\/complete\/"}} [] []
[2021-06-21 10:35:30] zipMoneyLog.DEBUG: Checkout Response:- {"id":"au-co_FZCvATHzEw9VPTxxxxxxxx","uri":"https:\/\/account.sandbox.zipmoney.com.au\/?co=co_FZCvATHzEw9VPTxxxxxxxx&m=6c998223-aaaa-bbbb-cccc-xxxxxxxxxxxxx","type":"standard","shopper":{"first_name":"Testee","last_name":"Tester","phone":"+61412123123","email":"test@test.com","birth_date":"0001-01-01T00:00:00+00:00","gender":"Other","statistics":{"sales_total_count":0,"sales_total_amount":0,"sales_avg_amount":0,"sales_max_amount":0,"refunds_total_amount":0,"previous_chargeback":false,"currency":"AUD"},"billing_address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"order":{"reference":"67000000078","amount":499,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"items":[{"name":"Gnarly Bedside","amount":499,"reference":"62263","description":"The Gnarly two-drawer bedside is just gnarly.","quantity":1,"type":"sku","image_uri":"http:\/\/blah.localhost\/static\/version1623719616\/frontend\/Testing\/blah\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/blah.localhost\/Gnarly-bedside","product_code":"123363"}],"cart_reference":"265392"},"config":{"redirect_uri":"http:\/\/blah.localhost\/zippayment\/complete\/"},"created":"2021-06-21T10:35:30+00:00","state":"created","metadata":{}} [] []
[2021-06-21 10:35:30] zipMoneyLog.INFO: Successful to get redirect url [ https://account.sandbox.zipmoney.com.au/?co=co_FZCvATHzEw9VPTxxxxxxxx&m=6c998223-aaaa-bbbb-cccc-xxxxxxxxxxxxx ]  [] []
[2021-06-21 10:36:05] zipMoneyLog.INFO: Starting Checkout [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Checkout Method:- guest [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Is Allowed Guest Checkout :- 1 [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Is Customer Logged In :-  [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Shipping Required:- Yes [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: 499-0-0-499 [] []
[2021-06-21 10:36:05] zipMoneyLog.DEBUG: Checkout Request:- {"type":"standard","shopper":{"first_name":"Testee","last_name":"Tester","phone":"+61412123123","email":"test@test.com","billing_address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"order":{"reference":"67000000078","amount":499,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"items":[{"name":"Gnarly Bedside","amount":499,"reference":"62263","description":"The Gnarly two-drawer bedside is just gnarly.","quantity":1,"type":"sku","image_uri":"http:\/\/blah.localhost\/static\/version1623719616\/frontend\/Testing\/blah\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/blah.localhost\/Gnarly-bedside","product_code":"123363"}],"cart_reference":"265392"},"metadata":{},"config":{"redirect_uri":"http:\/\/blah.localhost\/zippayment\/complete\/"}} [] []
[2021-06-21 10:36:06] zipMoneyLog.DEBUG: Checkout Response:- {"id":"au-co_qQSg86sBKq291yxxxxxxxx","uri":"https:\/\/account.sandbox.zipmoney.com.au\/?co=co_qQSg86sBKq291yxxxxxxxx&m=6c998223-aaaa-bbbb-cccc-xxxxxxxxxxxxx","type":"standard","shopper":{"first_name":"Testee","last_name":"Tester","phone":"+61412123123","email":"test@test.com","birth_date":"0001-01-01T00:00:00+00:00","gender":"Other","statistics":{"sales_total_count":0,"sales_total_amount":0,"sales_avg_amount":0,"sales_max_amount":0,"refunds_total_amount":0,"previous_chargeback":false,"currency":"AUD"},"billing_address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"order":{"reference":"67000000078","amount":499,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"items":[{"name":"Gnarly Bedside","amount":499,"reference":"62263","description":"The Gnarly two-drawer bedside is just gnarly.","quantity":1,"type":"sku","image_uri":"http:\/\/blah.localhost\/static\/version1623719616\/frontend\/Testing\/blah\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/blah.localhost\/Gnarly-bedside","product_code":"123363"}],"cart_reference":"265392"},"config":{"redirect_uri":"http:\/\/blah.localhost\/zippayment\/complete\/"},"created":"2021-06-21T10:36:05+00:00","state":"created","metadata":{}} [] []
[2021-06-21 10:36:06] zipMoneyLog.INFO: Successful to get redirect url [ https://account.sandbox.zipmoney.com.au/?co=co_qQSg86sBKq291yxxxxxxxx&m=6c998223-aaaa-bbbb-cccc-xxxxxxxxxxxxx ]  [] []
[2021-06-21 10:36:47] zipMoneyLog.DEBUG: On Complete Controller [] []
[2021-06-21 10:36:47] zipMoneyLog.DEBUG: /zippayment/complete/?result=cancelled&checkoutId=au-co_qQSg86sBKq291yxxxxxxxx [] []
[2021-06-21 10:36:47] zipMoneyLog.DEBUG: Result:- %s [] []
[2021-06-21 10:36:47] zipMoneyLog.DEBUG: Current Customer Id:- %s Quote Customer Id:- %s Quote checkout method:- %s [] []
[2021-06-21 10:36:47] zipMoneyLog.DEBUG: Calling cancelledAction [] []
[2021-06-21 10:38:48] zipMoneyLog.DEBUG: On Complete Controller [] []
[2021-06-21 10:38:48] zipMoneyLog.DEBUG: /zippayment/complete/?result=approved&checkoutId=au-co_FZCvATHzEw9VPTxxxxxxxx [] []
[2021-06-21 10:38:48] zipMoneyLog.DEBUG: Result:- %s [] []
[2021-06-21 10:38:48] zipMoneyLog.ERROR: Checkout Id does not match with the session quote. [] []
[2021-06-21 10:38:51] zipMoneyLog.INFO: Loading Quote by using zip checkout get api [] []
[2021-06-21 10:38:51] zipMoneyLog.DEBUG: Current Customer Id:- %s Quote Customer Id:- %s Quote checkout method:- %s [] []
[2021-06-21 10:38:52] zipMoneyLog.DEBUG: Quote Grand Total:- 499.0000 Quote Customer Id:-  Checkout Method:- guest [] []
[2021-06-21 10:38:55] zipMoneyLog.INFO: Successfull to place the order [] []
[2021-06-21 10:38:56] zipMoneyLog.DEBUG: Shipping Required:- Yes [] []
[2021-06-21 10:38:56] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] []
[2021-06-21 10:38:56] zipMoneyLog.DEBUG: 499-0-0-499 [] []
[2021-06-21 10:38:56] zipMoneyLog.DEBUG: Charge Payload:- {"authority":{"type":"checkout_id","value":"au-co_qQSg86sBKq291yxxxxxxxx"},"reference":"67000000078","amount":499,"currency":"AUD","capture":true,"order":{"reference":"67000000078","shipping":{"pickup":false,"address":{"line1":"2 Beans St","city":"PERTH","state":"WA","postal_code":"6000","country":"AU","first_name":"Testee","last_name":"Tester"}},"items":[{"name":"Gnarly Bedside","amount":499,"reference":"4729","description":"The Gnarly two-drawer bedside is just gnarly.","quantity":1,"type":"sku","image_uri":"http:\/\/blah.localhost\/static\/version1623719616\/frontend\/Testing\/blah\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/blah.localhost\/Gnarly-bedside","product_code":"123363"}]},"metadata":{}} [] []
[2021-06-21 10:38:59] zipMoneyLog.DEBUG: ApiError:- [403] Error connecting to the API (https://global-api.sand.au.edge.zip.co/merchant/charges)-{"error":{"code":"unauthorised_operation","message":"Authority request - co_qQSg86sBKq291yxxxxxxxx is not approved.  Check that request is not expired or completed."}} [] []
[2021-06-21 10:38:59] zipMoneyLog.DEBUG: Cancelling the order [] []
[2021-06-21 10:38:59] zipMoneyLog.DEBUG: Could not process the payment [] []
[2021-06-21 10:38:59] zipMoneyLog.INFO: In errorAction [] []
[2021-06-21 10:38:59] zipMoneyLog.INFO: An error occurred. [] []

Hi Simon,
I can't able to replicate the issue. I am able to place the order .please see the below log file.
[2021-06-24 23:19:00] zipMoneyLog.INFO: Starting Checkout [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Checkout Method:- guest [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Is Allowed Guest Checkout :- 1 [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Is Customer Logged In :-  [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Shipping Required:- Yes [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: 5--5-5-5 [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Checkout Request:- {"type":"standard","shopper":{"first_name":"zip","last_name":"test","phone":"400000","email":"mahbubur.rahman@zip.co","billing_address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"order":{"reference":"AU141020000000088","amount":5,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"507","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}],"cart_reference":"183"},"metadata":{},"config":{"redirect_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/zippayment\/complete\/"}} [] [] [2021-06-24 23:19:00] zipMoneyLog.DEBUG: Checkout Response:- {"id":"au-co_W84Xx2fj04zAwqB1VyeCj6","uri":"https:\/\/sandbox.zip.co\/customer\/account-selector?co=co_W84Xx2fj04zAwqB1VyeCj6&m=52ca96a6-3286-4e2e-a085-06918554fc4f","type":"standard","shopper":{"first_name":"zip","last_name":"test","phone":"400000","email":"mahbubur.rahman@zip.co","birth_date":"0001-01-01T00:00:00+00:00","gender":"Other","statistics":{"sales_total_count":0,"sales_total_amount":0,"sales_avg_amount":0,"sales_max_amount":0,"refunds_total_amount":0,"previous_chargeback":false,"currency":"AUD"},"billing_address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"order":{"reference":"AU141020000000088","amount":5,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"507","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}],"cart_reference":"183"},"config":{"redirect_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/zippayment\/complete\/"},"created":"2021-06-24T23:19:00+00:00","state":"created","metadata":{}} [] [] [2021-06-24 23:19:00] zipMoneyLog.INFO: Successful to get redirect url [ https://sandbox.zip.co/customer/account-selector?co=co_W84Xx2fj04zAwqB1VyeCj6&m=52ca96a6-3286-4e2e-a085-06918554fc4f ]  [] [] [2021-06-24 23:19:37] zipMoneyLog.INFO: Starting Checkout [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Checkout Method:- guest [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Is Allowed Guest Checkout :- 1 [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Is Customer Logged In :-  [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Shipping Required:- Yes [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: 5--5-5-5 [] [] [2021-06-24 23:19:37] zipMoneyLog.DEBUG: Checkout Request:- {"type":"standard","shopper":{"first_name":"zip","last_name":"test","phone":"400000","email":"mahbubur.rahman@zip.co","billing_address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"order":{"reference":"AU141020000000088","amount":5,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"507","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}],"cart_reference":"183"},"metadata":{},"config":{"redirect_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/zippayment\/complete\/"}} [] [] [2021-06-24 23:19:38] zipMoneyLog.DEBUG: Checkout Response:- {"id":"au-co_E7Q0mwyWFo5A0JPcG6lF24","uri":"https:\/\/sandbox.zip.co\/customer\/account-selector?co=co_E7Q0mwyWFo5A0JPcG6lF24&m=52ca96a6-3286-4e2e-a085-06918554fc4f","type":"standard","shopper":{"first_name":"zip","last_name":"test","phone":"400000","email":"mahbubur.rahman@zip.co","birth_date":"0001-01-01T00:00:00+00:00","gender":"Other","statistics":{"sales_total_count":0,"sales_total_amount":0,"sales_avg_amount":0,"sales_max_amount":0,"refunds_total_amount":0,"previous_chargeback":false,"currency":"AUD"},"billing_address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"order":{"reference":"AU141020000000088","amount":5,"currency":"AUD","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"507","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}],"cart_reference":"183"},"config":{"redirect_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/zippayment\/complete\/"},"created":"2021-06-24T23:19:38+00:00","state":"created","metadata":{}} [] [] [2021-06-24 23:19:38] zipMoneyLog.INFO: Successful to get redirect url [ https://sandbox.zip.co/customer/account-selector?co=co_E7Q0mwyWFo5A0JPcG6lF24&m=52ca96a6-3286-4e2e-a085-06918554fc4f ]  [] [] [2021-06-24 23:19:48] zipMoneyLog.DEBUG: On Complete Controller [] [] [2021-06-24 23:19:48] zipMoneyLog.DEBUG: /magento240/default/zippayment/complete/?result=cancelled&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24 [] [] [2021-06-24 23:19:48] zipMoneyLog.DEBUG: Result:- %s [] [] [2021-06-24 23:19:48] zipMoneyLog.DEBUG: Current Customer Id:- %s Quote Customer Id:- %s Quote checkout method:- %s [] [] [2021-06-24 23:19:48] zipMoneyLog.DEBUG: Calling cancelledAction [] [] [2021-06-24 23:20:00] zipMoneyLog.DEBUG: On Complete Controller [] [] [2021-06-24 23:20:00] zipMoneyLog.DEBUG: /magento240/default/zippayment/complete/?result=approved&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24 [] [] [2021-06-24 23:20:00] zipMoneyLog.DEBUG: Result:- %s [] [] [2021-06-24 23:20:00] zipMoneyLog.DEBUG: Current Customer Id:- %s Quote Customer Id:- %s Quote checkout method:- %s [] [] [2021-06-24 23:20:01] zipMoneyLog.DEBUG: Quote Grand Total:- 5.0000 Quote Customer Id:-  Checkout Method:- guest [] [] [2021-06-24 23:20:06] zipMoneyLog.INFO: Successfull to place the order [] [] [2021-06-24 23:20:06] zipMoneyLog.DEBUG: Shipping Required:- Yes [] [] [2021-06-24 23:20:06] zipMoneyLog.DEBUG: Gift Card Amount:- 0 [] [] [2021-06-24 23:20:06] zipMoneyLog.DEBUG: 5--5-5-5 [] [] [2021-06-24 23:20:06] zipMoneyLog.DEBUG: Charge Payload:- {"authority":{"type":"checkout_id","value":"au-co_E7Q0mwyWFo5A0JPcG6lF24"},"reference":"AU141020000000088","amount":5,"currency":"AUD","capture":true,"order":{"reference":"AU141020000000088","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"379","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}]},"metadata":{}} [] [] [2021-06-24 23:20:08] zipMoneyLog.DEBUG: Charge Response:- {"id":"au-ch_zfYW3cheLgVIVyyORD4322","reference":"AU141020000000088","amount":5,"currency":"AUD","state":"captured","captured_amount":5,"refunded_amount":0,"created_date":"2021-06-24T23:20:07+00:00","order":{"reference":"AU141020000000088","shipping":{"pickup":false,"address":{"line1":"10 spring st","city":"sydney","state":"NSW","postal_code":"2000","country":"AU","first_name":"zip","last_name":"test"}},"items":[{"name":"Argus All-Weather Tank","amount":5,"reference":"379","quantity":1,"type":"sku","image_uri":"http:\/\/<IP_ADDRESS>\/magento240\/pub\/static\/version1623885585\/frontend\/Magento\/luma\/en_AU\/Magento_Catalog\/images\/product\/placeholder\/.jpg","item_uri":"http:\/\/<IP_ADDRESS>\/magento240\/default\/argus-all-weather-tank.html","product_code":"MT07-M-Gray"},{"name":"Discount","amount":-5,"reference":"Discount","quantity":1,"type":"discount"},{"name":"Shipping","amount":5,"reference":"Shipping","quantity":1,"type":"shipping"}],"cart_reference":"183"},"metadata":[],"receipt_number":"1882879"} [] [] [2021-06-24 23:20:08] zipMoneyLog.DEBUG: Charge State:- captured [] [] [2021-06-24 23:20:08] zipMoneyLog.INFO: Payment Captured [] [] [2021-06-24 23:20:08] zipMoneyLog.DEBUG: Order captured setting order state: processing status: processing [] []

@mahbub-zip It seems that you processed a payment for the same checkout ID that you cancelled. You need to cancel the one checkout and process the other.
Your logs show these two requests with the same checkout ID
/magento240/default/zippayment/complete/?result=cancelled&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24
/magento240/default/zippayment/complete/?result=approved&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24 [] []

Whereas my logs showed the two different checkout IDs
/zippayment/complete/?result=cancelled&checkoutId=au-co_qQSg86sBKq291yxxxxxxxx [] []
/zippayment/complete/?result=approved&checkoutId=au-co_FZCvATHzEw9VPTxxxxxxxx [] []

@simonworkhouse yes i can see the same checkout id for cancelled and approved. But whatever steps you mentioned i have followed those steps.  please have a look on the below video link
https://user-images.githubusercontent.com/62676065/123365590-e3a77280-d5b9-11eb-99f3-cacfadac3e76.mp4

@mahbub-zip That's an incomplete video of the process, and your logs indicate that it's fetching the same checkout ID from the database as what's in the request parameters. In our logs we received Checkout Id does not match with the session quote..
Which branch are you running these tests on?

Using master branch. I followed same steps whatever you mentioned. I attached another video.
https://user-images.githubusercontent.com/62676065/123373307-86ff8400-d5c8-11eb-8ff1-7b54b91f3a3d.mp4

@mahbub-zip It would be helpful to have the logs tailed at the same time as that order was being placed, but probably not necessary as I think that I may be able to guess what the issue is based on the previous logs that you supplied.
As I highlighted previously, your logs indicate that the cancelled order checkout ID is what's provided in the redirect query parameters:
/magento240/default/zippayment/complete/?result=cancelled&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24
/magento240/default/zippayment/complete/?result=approved&checkoutId=au-co_E7Q0mwyWFo5A0JPcG6lF24 [] []

This leads to the question as to why you are being redirected back to Magento with a different checkout ID (co_E7Q0mwyWFo5A0JPcG6lF24) than the one that was used in the hosted payment page URL (https://sandbox.zip.co/customer/account-selector?co=co_W84Xx2fj04zAwqB1VyeCj6&m=52ca96a6-3286-4e2e-a085-06918554fc4f).
My guess is that it's due to the fact that you are already logged in to your Zip account, so retry all tests in an incognito/private session and only log in once you are about to process the payment.
This is just a guess, but if it's incorrect, then we would need to determine why the redirect back to Magento uses the incorrect checkout ID.

@simonworkhouse I have checked this in an incognito. I cannot replicate the issue. Before redirect to merchant from zip, zip can able to map with latest checkout id. When it is redirect to merchant that time URL has the latest checkout id. In this video  i am not showing login process for security reason. I believe this video make you more clear.
https://user-images.githubusercontent.com/62676065/123391362-495a2580-d5df-11eb-83eb-5e92be658bc4.mp4

@mahbub-zip What mechanism is Zip supposedly using to map the user to the latest checkout ID? Session based? Mapped by order reference? Linked to a Zip account? Or something else? You can clearly see from the logs that I have provided that we are not being redirected to the latest checkout ID. Is there a setting on a merchant account that prevents cancelled orders from being approved?
Regardless of this mechanism, the module requires a fix to address situations where multiple payments have been created for an order.

@simonworkhouse could you please apply this https://github.com/zipMoney/zip.magento2/pull/45/files change on top our latest plugin and let me know is this resolve the issue?

@mahbub-zip as per my comment above - this issue happened again today even after applying the suggested code change above. It happens rarely but it still happens.
Any idea? You never replied to my comment above.

Hey @Swiftless ,
Do you have staging site where same issue is happening? is it possible to send me the staging website url then i can have a look?
Thanks


Implement KVC collection operators

[x] for RLMResults
[x] for RLMArray (fixes #2937)

/c @bdash

A few of the error cases could do with increased test coverage, but it looks good beyond that. :+1:

Increased test coverage, made an improvement to the error handling in a particular case (see the last commit) and reorganized the tests. Now they are for RLMResults all in one dedicated method (testValueForCollectionOperationKeyPath), but I omitted to test all the types to aggregate on, that should be well covered by other tests.

This looks good to me! :+1:

:+1:


how to get azure-cli-2.0.52 (Which has bot service 0.4.3)

how to get azure-cli-2.0.52 (Which has bot service 0.4.3)

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

ID: 8b7bd326-07b2-caaa-7155-5852fc2dfa3f
Version Independent ID: c44d0547-d5cd-8934-00f8-79e2f4df53ac
Content: Install the Azure CLI
Content Source: docs-ref-conceptual/install-azure-cli.md
Product: azure
GitHub Login: @sptramer
Microsoft Alias: sttramer

I think you should be able to get it if you use https://azurecliprod.azureedge.net/msi/azure-cli-2.0.52.msi

All older releases are available via https://github.com/Azure/azure-cli/releases. We don't officially offer older releases as an MSI. If you have a need for a specific release due to a bug that was introduced or a feature which is now missing, file a bug report with CLI engineering.


Create Hosted Engine Wizard -> Storage Settings -> Fibre Channel -> Storage options disabled when space is still available

VM Portal version number:
oVirt version number: 4.4.1
Browser and version: Firefox 68.10.0esr (64-bit)
Steps to Reproduce:

Create a Hosted Engine
Get to the storage options step and select Fibre Channel
Once a few LUNs have been discovered, increase the Disk Size (under Advanced) to something like 100GiB
Notice that the options are disabled even though they have enough disk space

Actual results:

Radio options to select luns are disabled
Expected results:
Radio buttons should be enabled until requested disk size is greater than the available size on the luns
Additional info:
Work around is available - Open developer tools and remove "disabled" from radio button and select the preferred luns

Screenshot shows selected luns after workaround implemented

@HunterGerlach hi, thanks for filing this issue but it seems like you used a wrong tracker. This ovirt-web-ui repository deals only with VM Portal issues while this issue is related to Hosted Engine wizard and therefore should be opened via Bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine (Component set to BLL.hostedEngine).
Can you please file a bug so that we can close this? Thanks

@HunterGerlach hi, thanks for filing this issue but it seems like you used a wrong tracker. This ovirt-web-ui repository deals only with VM Portal issues while this issue is related to Hosted Engine wizard and therefore should be opened via Bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine (Component set to BLL.hostedEngine).
Can you please file a bug so that we can close this? Thanks

@sandrobonazzola are you aware of that or should we open a bug?
Meanwhile, I'm closing this issue since not relevant to web-ui


Add tests for stream module [TE-414]

Introduced generalized readers and writers
Added tests for them

@bkontur  Fixed according to your comments. Also criterion is used now for benchmarking. Added a test on an empty chunk, it fails, so ignoring it for now.

@akoptelov
Alex, please add one of that benches to drone run:
like here:
https://github.com/simplestaking/tezedge/blob/develop/.drone.yml#L197
https://github.com/simplestaking/tezedge/blob/develop/.drone.yml#L231
https://github.com/simplestaking/tezedge/blob/develop/.drone.yml#L358
https://github.com/simplestaking/tezedge/blob/develop/.drone.yml#L378
https://github.com/simplestaking/tezedge/blob/develop/.drone.yml#L388
we will later separate this benches to separate pipeline


add pursuit-of-simplicity.pages.dev

this adds my blogs page domain to join the club

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[x] This site is not an ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: pursuit-of-simplicity.pages.dev
  url: https://pursuit-of-simplicity.pages.dev/
  size: 11.27
  last_checked: 2024-03-02

Cloudflare Report: https://radar.cloudflare.com/scan/13a01179-8a72-410d-99c7-261413792701/summary

hi @kevquirk just wanted to check-in if something is missing in the pr? After the vercel pipeline got fixed I updated my entry so it gets re-run to have a valid deployment.

Thanks for doing that! I'm currently out and about and can't really update the PRs. I didn't really want to poke every author of open PRs. This one can be merged though. 🙂


why don't helm  pass --insecure-skip-tls-verify into plugin?

Output of helm version:
helm v3.14.2
Output of kubectl version:
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
why don't helm  pass --insecure-skip-tls-verify into plugin?
see: https://github.com/helm/helm/pull/10944/files  maybe it's a typo?

To avoid confusion, do you mean "why don't helm pass --kube- insecure-skip-tls-verify into plugin?"

To avoid confusion, do you mean "why don't helm pass --kube- insecure-skip-tls-verify into plugin?"

no. it don't need to chaneged. thanks.

ping


[FeatureRequest] Renew Cookie before it expires

Read Cookie Lifetime on acquire
Renew Cookie 5 Minutes before expiration

Cookie Expire-Value is always set to  Thu, 01 Jan 1970 00:00:00 GMT
Thats not good, but it seems that it is always 2h valid.

Fixed in V1.0.2
https://github.com/Schnup89/ioBroker.pbx-3cx/commit/93f610cf90869a51a072861f745662bfa06a27c2


Support :link pseudo class

This will be done using a compile-to-CSS helper later. Right now there's no way to implement either :link or :visited` pseudo classes.


Documenting lsb_release -u

Would it also be possible to add the -u option to the documentation?
I've managed to manually reconfigure lsb_release -u for apt-get on elementary OS (after losing the forked version from an Ubuntu PPA) following this commit: https://github.com/JoliOS/lsb/commit/fde07bfec0935784e5caa6cd6a2ff5f81c3d0ad4
Documentation may assist further adoption and use of this option. I've submitted a PR to the JoliOS repo but I realise this may not be the ideal place to submit it as this OS has been discontinued:
https://github.com/JoliOS/lsb/pull/1

In fact, the -u option is already documented in this repository readme, together with the same reference to the JoliOS folks.
I do believe that implementing the -u option across all Ubuntu derivative distros (or at least in the most popular ones) is the best solution. Distro developers all know their roots, so, it'd be no challenge for them to place it. This solution isn't just popular enough, because it isn't standard. This repository was just a proof of concept I written for Docker, and this has kind of influenced the setup script at https://get.docker.com/ .
However, the greatest challenge is to convince these distro developers to include the -u option. I haven't tried anything else, but the first step would be to list the 10 most popular Ubuntu distros and post in their forums about this issue. It worths to note that it's already implemented in elementary OS and Linux Mint.
This isn't an issue for many people, but it's something simple that may ease life of many developers depending on APT packages to create automatic setup scripts, making these distros easier to use. Perhaps that's an argument to speak with them.
What do you think?

Oh and about the pull request to JoliOS folks, unfortunately their project is discontinued. :cry:

Sorry I should clarify that the PR to JoliOS was to demonstrate how to add lsb_release -u to the manual so that it is displayed in the output of man lsb_release or lsb_release -h.
Adding the changes submitted in the PR, compressing the lsb_release.1 into a gzip, and using this to replace the file in the /usr/share/man/man1 directory works on my elementary OS (Freya) machine.
I agree that this functionality would be useful in such forked distros. However if you want this adopted widely there are some challenges. I am not sure what one would put as upstream of a forked distro from elementary: would you put the elementary version or the ubuntu version? Note also that the debian (jessie for eOS Freya/Trusty) lsb-release package has number of files and documenting --upstream in all of the relevant files would assist further use.
I've been able to figure out how to fix it from the JoliOS github repo and trawling READMEs (RTFM actually worked!) but it would be easier if it just worked. When my elementary OS distro reverted to the ubuntu lsb-release package,  typed lsb_release --help into  terminal when option -u not found

Oh I see. Sorry for misundertanding.
I agree about adding it to the manual. I only learned about this option while asking for help at elementary OS forums here.
It worths having the -u option only if the distro uses an APT repository from a base distro, which in case is the upstream one. That is, elementary OS and Mint would always have its corresponding Ubuntu version as the upstream. If somebody makes a distro derivated from elementary OS or Mint, I think it would be reasonable to have Ubuntu as upstream too. I don't think it should be ported and documented to Debian because they don't have to resolve to an APT repository of another developer.
Just to clarify, why don't you have the -u option in Freya? I've used it too, and I had it in mine. You mean the package was reverted? Was it during a system update? I'd file a bug in elementary OS Launchpad because they already have it implemented, so, losing it is more likely to be a bug.
I think the greatest challenges to make it widely adopted is to spread it to distro developers. But if we start it right away this should be solved withint one year or so in the major forked distros. I hope the developers to welcome this feature. :)

I've managed to fix it. I think it's my own fault updating from Ubuntu PPA's rather than a bug of eOS. I had two eOS machines running and the other runs lsb_release -u as expected:
$ lsb_release -usc
trusty

I could probably have got assistance from the eOS developers but this experience has given me a deeper understanding of *nix systems. However neither eOS machine has -u included in the help and manual so it seemed strange for me that worked on one system (and presumably the other before apt-get died) without being in the built-in help system.
It didn't take me more than an hour or two to configure this change myself (without apt-get working) and I'm a geneticist with no formal training in computer science. I'm sure it wouldn't be too much trouble for the devs to include if they're motivated to do so. Including these changes to the help system would help end users and the changes have already been made if the devs want to git cherry-pick this commit. Hopefully making it easier for them to adopt will encourage them to do so!


Fix add user button in groups

This button was broken on the rebranding:

Please CR @MariaCheca

:kiss: thanks @javitonino

LGTM 👍


Update ctb_encrypted.py

File seek on wrong side of for loop; did not advance through file

do it


AD Connect Server Failed

The AD Connect server failed for our client and we decided not to replace it, but to migrate fully to Azure AD.
How can this be disabled when you no longer have an on-prem server?

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

ID: 9eb97eff-d72e-ffa6-1365-5419e93ed82a
Version Independent ID: 5c8b677b-f4cd-0bb5-c7d6-9b1ef903dad4
Content: Azure AD Connect: Seamless Single Sign-On - Frequently asked questions
Content Source: articles/active-directory/hybrid/how-to-connect-sso-faq.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@mexidus Thanks for your feedback! We will investigate and update as appropriate.

@mexidus you can refer to blog to remove the azure ad connect.

That article also states that I need to log onto the server and uninstall AD Connect. I do not have a server to login to due to the failure.
How do you uninstall all connections for AD Connect when you no longer have access to the AD Connect server?

@mexidus To further assist you on this issue I suggest you to please open a Azure Support Ticket so that Identity Support engineer can check further on this issue. In case you limitations in your support plan to open support ticket please let me know.

@mexidus We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


fix (deps) : update dependency typeorm to v0.3.6

Needs another pull request for database creation because the method used is deprecated.

Thanks for helping out!
It looks OK, let's see if the checks pass :)

You’re welcome.
Do you think it can be merged soon?


Rewrite through the use of the Context API

Do you want to request a feature or report a bug?
Don't know how to classify. It works, but very soon it will stop working.
(related to #426)
What is the current behavior?
I'm opening this issue in order to have a clean place where we can discuss what to do in order to migrate the use of react-side-effect, a package which gives us problem considering it uses componentWillMount and it's outdated (referring to abramov's own words.
The two main things that should be decided are: how to provide this update to users that already use this package and how.
How to provide the update
Should a new major version just come out and specify the new react minimum version (since the use of the Context) or keep both the implementation for an old react version and give time to developers to adjust their implementation?
How do we change the code?
I don't think it should be too hard to reimplement this module.
I also found out the existence of this module: https://github.com/staylor/react-helmet-async
Is your intention to bring it in? In this way we would solve the reason why that package has been created and we'd successfully avoid troubles with the new react version that is coming.
Unluckily you could argue that there is already another working module, the point is that this one is generally more notorious, it's found in a lot of "how to get started" react tutorials and also produces a warning hard to trace back.
If you don't want / can't maintain this module we could also understand what to do, but action should be taken

Any update on this? I still see the error:

react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: SideEffect(NullComponent)

@cwelch5 @dhoward @doctyper

Any update on this? I still see the error:

react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: SideEffect(NullComponent)

Any update on this? I still see the error:

react-dom.development.js:88 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: SideEffect(NullComponent)

me too

me too

In strict mode

I suggest looking at how styled-components do it. The implementation is pretty simple and usage very intuitive (I found it better than react-helmet-async).


The URL example is missing some underscores

[Enter feedback here]
The example syntax for query-string URL immediately preceding the "Special characters in values" section is incorrect - some of the escaped characters are missing a leading underscore (specifically the square brackets).
PK
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 70b360f3-21a7-adc2-896a-b1dfd5d9e384
Version Independent ID: 15e8c09f-46ad-68f9-75e6-c3d5c2c214e5
Content: Filter a report using query string parameters in the URL - Power BI
Content Source: powerbi-docs/collaborate-share/service-url-filters.md
Service: powerbi
Sub-service: pbi-collaborate-share
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi @Piquet65, thanks for your comments. I am forwarding it on to the doc author for consideration.

Hi @Piquet65, thanks for your comments. I am forwarding it on to the doc author for consideration.

Hi, @Piquet65 -- I believe the brackets and underscores are correct now. Please do let me know if not.
Thanks!


Allowing values to be assigned to bools

I would like to be able to pass a value to a bool flag. I would like to be able to pass the value of the boolean like:
./my-program --my-flag=true --my-other-flag=false

Which would be equivalent to calling:
./my-program --my-flag

I agree that the current flagging functionality is a lot cleaner than the additional functionality I'm proposing. However my use-case is to support my users who are calling my-program from a script (e.g. bash, python, etc.)
Here's an example of how I would like to use this functionality:

myfunc () {
  myflagvalue=$1
  myotherflagvalue=$2
  ./my-program --my-flag=$myflagvalue --my-other-flag=$myotherflagvalue
}

# then I might call it with the flags set or not:
myfunc "true" "false"
myfunc "false" "false"

Where as currently my users would have to write this instead:

myfunc () {
  myflagvalue=$1
  myotherflagvalue=$2
  if [ "$myflagvalue" = "true" ]; then
    if [ "$myotherflagvalue" = "true" ]; then
      ./my-program --my-flag --my-other-flag
    else
      ./my-program --my-flag
    fi
  else
    if [ "$myotherflagvalue" = "true" ]; then
      ./my-program --my-other-flag
    else
      ./my-program
    fi

  fi
}

# then I might call it with the flags set or not:
myfunc "true" "false"
myfunc "false" "false"

Note that in contrast to https://github.com/jessevdk/go-flags/issues/80 I am not suggesting the ability to change the default value of a bool flag.
If you're open to such a feature, I would be happy to contribute a PR and could make this functionality optional via a:
	// AllowBoolValues allows a user to assign true/false to a boolean value
	// rather than raising an error stating it cannot have an argument.
	AllowBoolValues

option.
(for reference my real use-case is to support https://github.com/earthly/earthly/issues/1109 and not bash, but it covers a very similar use-case).

Merged.

welcome back @jessevdk, good to see you're still kicking.


[BUG] "Start animation index must be strictly lower than end animation index" on wipe example

Description
Hi there, I'm trying to use wipes in my presentation and it seems not to be working properly.
Even just running the Wipe example from the documentation gives me an error.
Code:
from manim import *
from manim_slides import Slide

class WipeExample(Slide):
    def construct(self):
        circle = Circle(radius=3, color=BLUE)
        square = Square()
        text = Text("This is a wipe example").next_to(square, DOWN)
        beautiful = Text("Beautiful, no?")

        self.play(FadeIn(circle))
        self.next_slide()

        self.wipe(circle, Group(square, text))
        self.next_slide()

        self.wipe(Group(square, text), beautiful, direction=UP)
        self.next_slide()

        self.wipe(beautiful, circle, direction=DOWN + RIGHT)

Command:
manim -ql wipeexample.py WipeExample

Error:
ValidationError: 1 validation error for SlideConfig
  Value error, Start animation index must be strictly lower than end animation index [type=value_error, input_value={'type':
<SlideType.slide...mation': 1, 'number': 2}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.4/v/value_error

Version
Using manim-slides v4.16.1, manim community v0.17.3
Platform
Windows
Screenshots
No response
Additional information
No response

That works fine, thank you!


Reading dowloaded file

Hi. I can get isochrone requests to work, but since I don't want to slam the server I downloaded the data files. I can't seem to get the package to read the downloaded files. How does one do that?

If you repeat the same request a second time it will just load the downloaded isochrones from a local cache. Is the caching not working for you?

I didn't realize it was storing things like that. That's useful but it would still be nice if I could open files I've downloaded beforehand.

For sure. :+1: Feel free to fork the code and modify it for your own applications. I'm not actively using or maintaining it anymore.


Too many things are called Video

Although Rust's namespacing makes it absolutely possible to have different structs called Video, it is confusing in practice, especially in Rustdoc. Rustdoc does not show module name when displaying types in function signatures, so the API reference is unclear when something takes/returns frames or codecs. Same with structs called Input. Rustdoc's search also doesn't search module names, so it's not possible to search for video frame specifically.

ffmpeg::codec::decoder::video::Video
ffmpeg::codec::encoder::video::Video
ffmpeg::codec::video::Video
ffmpeg::util::frame::video::Video

Another problem is that since ffmpeg-rs doesn't have its own documentation, it's necessary to read ffmpeg's C documentation instead. However, renamed/namespaced Rust names don't match ffmpeg's C names (e.g. AVFrame and AVCodec are both called Video here), which makes it extra difficult to cross-reference documentation with this crate.
I suggest using C names, just without the AV prefix.

The issue is this is not a straightforward wrapper, if you want behavior compatible with FFmpeg you should be using the ffmpeg-sys, this is a higher level wrapper trying to be more rustic.
I agree that the lack of documentation is actually a problem tho, and the rustdoc output is suboptimal at best.

I'd rather not work with ffmpeg-sys directly. I prefer the higher-level usability and safety that the wrapper is providing.
I'm hoping this crate is "like ffmpeg, but with C-isms turned into Rust-isms" rather than a new library that's trying to abstract ffmpeg away with a different architecture that just happens to use ffmpeg as a back-end.
That's because the audiovideo domain is full of quirks, so a thick abstraction layer is likely to be a leaky abstraction and I'm worried that a non-straightforward wrapper is just going to make debugging of what ffmpeg is doing harder.

Related rustdoc bug: https://github.com/rust-lang/rfcs/pull/2114


feat: add receipt decoder

Closes #914
This PR moves receipt decoding to the new ReceiptParser. The key difference is that the ReceiptParser owns a copy of the receipts and will consume an entry when a value is generated.
I've also found that test_contract_raw_slice is duplicated so I removed one instance of it.
Checklist

[x] I have linked to any relevant issues.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

I added suggestions that go with the overall idea of consuming receipts once parsed.
I'm wondering what we gain by removing a receipt once used. It doesn't seem to me like somebody is going to erroneously match against it since we have the contract_id checks. The only case I can think about is the extra receipt we generate for vector returns. If its contract id is all zeroes as well, somebody decoding a script return could maybe match against the vector data. But that would mean being given receipts from both a Script and a Contract call as well, which I'm not sure we ever do.
It does add complexity. You have to think about iterator invalidation and removing from vectors and avoiding cloning n stuff.
Maybe we should have just kept them as they are and filter through them every time.
If it is about performance, chances are that shuffling elements inside vectors on a remove eats up whatever we gained by not iterating through the full set of receipts every time.
Decoding doesn't need ownership of the bytes so even if great care is taken to avoid cloning it will be for nothing since we could have passed references around anyway.

Removing receipts ensures that a multi call doesn't decode the same receipt for two different calls.
The case you described is also not unlikely if you consider that a user can load a script that contains a contract call. I'm not sure if the latter has some other implications, I will try to test it later.
An alternative would be to somehow track the already consumed receipts without removing them but that would add complexity.

The case you described is also not unlikely if you consider that a user can load a script that contains a contract call. I'm not sure if the latter has some other implications, I will try to test it later.

We should probably look into this case more. I'm thinking if a script calls a contract that returns a vector, the receipt for that would only contain the metadata of the vector and it would have the contract_id in it. The additional receipt only happens because we inject the instructions to load from the vm's memory.
With the contract id in the receipt, it can't be consumed by us parsing the script receipts through the receipts parser.

Removing receipts ensures that a multi call doesn't decode the same receipt for two different calls.

Good catch.

Maybe it would make sense to move ReceiptParser to a separate file.

Can we sync this branch with master, please? 😁

This looks good; I Left just that one nit; feel free to push back, though. Once that discussion is resolved, feel free to merge if I don't come back to approve in time.


Issue-137, import exmol not working with python 3.11

dataclass second import commented out

@whitead looks like this error is fixed now. Do we want to add a test for python 3.11 as well?
Error was due to incompatible variable declaration in dataclasses for python 3.11
See answer

Yeah please change the test workflow matrix to include 3.11. To thanks!

@whitead Ready for review


docs: describe format for Buffers (#2412)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 26.98%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3651

Relevant Lines:
14262

💛  - Coveralls

Sounds good, how about this?


Ensure SSH keys are in place

Closes https://github.com/dokku/ansible-dokku/issues/2.
Haven't tested this manually.
Hopefully #28 will help with this going forward.

Is this necessary now that 0.19.5 is out?

I don't know, did you fix this in 0.19.5? Feel free to close if so.

I think I did, but can you test?

I won't have time to chase this up but will close optimistically :+1:

@josegonzalez  - i have tested it and it now gives an error message 👍
Let me know if the issue requires any more testing.


Azure Functions extension compatibility

With the support in Azure functions for extensions starting with runtime 2.0 but still no planned implementation of a batch trigger for azure queues (see this thread), I was hoping to use the GroupQueueTrigger in a function project but failed to make the Azure Functions runtime detect the methods decorated with the [GroupQueueTrigger] attribute.
Is it compatible in its current state with this scenario or only with WebJobs? Does it require any additional tooling or dependencies to be used in function apps?

I have the same exact issue. I need to subscribe to a "batch" of queue messages instead of just one.

Sorry for the delay, somehow lost track of this repo's notifications 😞
This was originally intended just for Webjobs, I'll add it to my backlog, maybe I can actually make it happen at some point depending on my free time (have to read the Functions runtime repo and understand the wiring).


Test ruler

@rultor hello

@rultor hello

@avatar46 Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


Add example workflow

Since setting up scarb is necessary for starknet foundry to run, we should add an example workflow showcasting the complete usage.

https://github.com/foundry-rs/starknet_forge_template/blob/master/.github/workflows/checks.yml


Can it be used for image to video generation?

Can it be used for image to video generation?

The current repo doesn't support image-to-video. We're working on image-to-video capabilities.


As a Judge, I would like to use my keyboard to indicate my voting preference, so that my voting velocity can be increased

As a Judge, I would like to use my keyboard to indicate my voting preference, so that my voting velocity can be increased

N key or 1 key for "No"
M key or 2 key for "Maybe"
Y key or 3 key for "Yes"


Code generation doesn't support generic classes

When attempting to write a benchmark in a generic class, I have failures because the code generation seems to just rely on type.Name.
trivial example:
var summary = BenchmarkRunner.Run<CsvParsingBenchmarks<TCSV>>();

where I'm doing independent runs to benchmark different CSV configurations

Thanks for the report. Will be fixed soon.


Add fallback for setup_auto_root() to be executed if no root is found

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.misc
Description
setup_auto_root can set the root directory as the parent directory of the current buffer if there is no root directory found by names, which is useful for editing a single file.

Thanks for the suggestion!
Setting current working directory to be a parent of the current file is a bit extreme (and is not a good practice for my taste). However, having a way to replicate 'autochdir' in some kind of fallback action is a good idea. I'll think about it.

This should now be possible in main branch using new fallback argument.
Your use case of emulating 'autchdir' if no root is found with vim.fs.find() can be addressed with this code:
-- Use `names` to your liking
MiniMisc.setup_auto_root(nil, function(path) return vim.fs.dirname(path) end)


default to auto_reload in debug mode

fixes: https://github.com/channelcat/sanic/issues/1158

@r0fls now that the auto_reload option is set to True in debug mode, maybe we can add it to the documentation? I have created a PR for it if you have any ideas or feedback it will be welcomed :)

hmm i rebased but the build is still hanging

@yunstanford any ideas?

oops! @r0fls we can't do this now! We talked here before. Enabling auto-reloading causes failing some tests those need DEBUG=True so I separated DEBUG mode from auto-reloading.

@Yaser-Amiri thanks for the heads up, I just disabled auto_reload in the test client for now: https://github.com/channelcat/sanic/pull/1159/files#diff-8ff5a7907a8a3e558aa2868b65263a87R48


Possible bug in triangle-triangle intersection algorithm

A user-provided mesh was flagging some triangles as self-intersecting.
Based on visual inspection, the triangles do not in fact appear to actually intersect.

Is some non-zero "fuzz" tolerance used, or do the red triangles intersect at a vertex (it's hard to tell from the image)?

I'm still looking into it, but the mesh vertices have been "welded" before checking for self-intersections and the common vertex is shared between the two triangles.  I.e. there are only 5 unique vertices for the two triangles that are reported as self-intersecting.
However since nearly all the triangles in this mesh look similar, I suspect that there is a bug in one of the subcases of the triangle-triangle intersection algorithm, possibly related to fuzzed tolerances and/or specific triangle orientations.

Yeah -- the intersection code probably is not distinguishing between overlapping triangles and "valid" intersections, e.g., vertex- or edge- intersections

But, it's weird that it would happen in this one case and not a bunch of others, no?

Actually, I have a few other meshes from the same user with similar problems.  (sorry for not mentioning that above.
For all of these meshes:

meshlab is not reporting any self-intersections
the InOutOctree is successfully able to initialize and categorize all regions as inside/outside

The problem ended up being related to a hidden "magic" tolerance deep within the intersect(Triangle,Triangle) implementation.  I exposed this to the user in #265.
Details:
The default tolerance was 1E-12 and the problematic triangles in the above case were within 3E-12 of each other. All problems with the meshes provided by this user went away when I set the tolerance to 1E-08.
Note also that above mesh is pretty far from the origin:
[INFO] Mesh bounding box: { min:(-8873.55,-14673.2,111294);
                            max:(3140.59,-11252.2,112666);
                            range:<12014.1,3420.99,1371.77> }

Ugh! hidden "magic" tolerances strike again 😄


Spark_connection_url do not contain workspace_id while connecting to databricks

Hi
I tried connecting databricks via http. The dbt debug was failing at connection step.
Later I checked that spark_connection_url do not contain the workspace id of databricks (my organization's)
When I updated spark_connection_url my local computer's dbt-spark connector (with help of an engineering colleague) everything worked out

Hey @drewbanin -  I'm not having the same level of luck as @akhildhingra , but since we didn't get this documented, I definitely wanted to chime in.
In dbt/adapters/spark/connection.py, I see this:
SPARK_CONNECTION_URL = "https://{host}:{port}/sql/protocolv1/o/0/{cluster}"
based on Databricks' documentation:
https://docs.azuredatabricks.net/user-guide/bi/jdbc-odbc-bi.html#http-path
You'd typically be setting it to this:
SPARK_CONNECTION_URL = "https://{host}:{port}/sql/protocolv1/o/{organization}/{cluster}"
One grabs organization from the Databricks service itself, and I believe it's roughly equivalent to an id that uniquely represents your instance of the service.
I'm not able to get this working by editing that file yet, but wanted to try and jumpstart the conversation since you guys have something really interesting going here with this package!

Hey @poidra02 - that's pretty interesting! We actually initially developed this plugin against Databricks Spark, but I remember following this guide for connecting to a cluster via JDBC. You can see the /sql/protocolv1/o/0/{cluster}string in the screenshot on that page.
Can you say just a tiny bit more about this?

One grabs organization from the Databricks service itself, and I believe it's roughly equivalent to an id that uniquely represents your instance of the service.

I'm super happy to add an organization config to the target config for Spark connections, and we can probably make the default value 0 for backwards compatibility. I would like to wrap my head around the difference between using 0 and the organization before making that change though!
Let me know if you'd like a hand with making this change in a fork of dbt-spark. If you're able to get it working locally, then I'd happily accept a PR for the change :)

Thanks so much for getting back to me @drewbanin - and happy to collaborate on this!  Submitted a pull request with a stab at showing how it could work.  I'm able to connect to Azure Databricks after the change, but I don't have an AWS version to regression test against.
The organization seems to be an internal number generated in Azure Databricks when you provision a workspace.  All the Azure docs reference it when you want to connect to the spark cluster, and I wasn't able to connect before these changes.
It seems like 0 may be the default from spark, and perhaps how AWS' version of Databricks works?  But 0 doesn't work at all on the Azure side... perhaps there was an Azure specific nuance they had to work around in how they provision clusters.
Happy to discuss further and react to any feedback!  (I might be misunderstanding a few things in the code still as I'm learning dbt).  Lastly, I get an SSL warning in the logs after successfully connecting.
There probably are some more tests on the model side of things to confirm Azure Databricks works as expected... I have a test cluster we can collaborate on if needed.


[EN] Feedback for: /web/tools/chrome-devtools/iterate/inspect-styles/shortcuts?hl=en

@sh0wTuan2016 do you have feedback that you want to report?


Connection Timed Out Error

Hi, I added this plugin to my application which is ionic 2 not the phonegap. So I installed the plugin but when I'm going to build project it shows me this error:
`
Error: cmd: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring root project 'android'.

Could not resolve all dependencies for configuration ':_debugCompile'.
Could not resolve com.adobe.creativesdk.foundation:auth:0.9.1062+.
Required by:
:android:unspecified
Could not resolve com.adobe.creativesdk.foundation:auth:0.9.1062+.
Failed to list versions for com.adobe.creativesdk.foundation:auth.
Unable to load Maven meta-data from https://repo.adobe.com/nexus/c
ontent/repositories/releases/com/adobe/creativesdk/foundation/auth/maven-metadat
a.xml.
Could not GET 'https://repo.adobe.com/nexus/content/repositorie
s/releases/com/adobe/creativesdk/foundation/auth/maven-metadata.xml'.
Connect to repo.adobe.com:443 [repo.adobe.com/<IP_ADDRESS>
1] failed: Connection timed out: connect
Could not resolve com.adobe.creativesdk:image:4.6.3+.
Required by:
:android:unspecified
Could not resolve com.adobe.creativesdk:image:4.6.3+.
Failed to list versions for com.adobe.creativesdk:image.
Unable to load Maven meta-data from https://repo.adobe.com/nexus/c
ontent/repositories/releases/com/adobe/creativesdk/image/maven-metadata.xml.
Could not GET 'https://repo.adobe.com/nexus/content/repositorie
s/releases/com/adobe/creativesdk/image/maven-metadata.xml'.
Connect to repo.adobe.com:443 [repo.adobe.com/<IP_ADDRESS>
1] failed: Connection timed out: connect`

@hahmadicorp hey, I can't reproduce your issue. It seems like you have an issue getting a network connection to repo.adobe.com. Can you see if you can load this URL from the browser:
https://repo.adobe.com/nexus/content/repositories/releases/com/adobe/creativesdk/foundation/auth/maven-metadata.xml
If you can't it's a network issue for sure.

Getting the same issue building after installing the plugin. Internet connection is fine and link loads fine.


Startup Issue

Extension Name: git
Extension Version: 1.0.0
OS Version: Windows_NT x64 6.1.7601
VSCode version: 1.28.0

We have written the needed data into your clipboard. Please paste:

This issue was closed because it doesn't meet our standards of a properly filled issue. Please read our guide about Submitting Bugs and Suggestions.


Node Manager not starting in live network

Hi!
I'm trying to setup a network between multiple machines in my office. When I create my first node in the network, it stops after saying "When asked, enter <IP_ADDRESS> for Existing Node IP... ".
It looks like this:

It doesn't show the Node Manager starting and when I try to access the UI, it doesn't work.

Looks like the Geth is not starting probably waiting forever for Constellation to start. Please check the geth and constellation logs.

I think I solved the problem, I wasn't specifying a correct ip


Reasons for hash changes explained

I got a scenario here, that I would like to discuss and hopefully create a source for docs, for what a developer should really think about to prevent causing hash changes.
I'm making something, that might seem like a very small change in my code, which has quite large effect on long-term caching.
I'm writing this issue in docs, because I'm sure it's expected, just that I want to be able to understand why this is happening, and hopefully help others as well.
Example repo is here (using<EMAIL_ADDRESS>and webpack-chunk-hash@0.3.0):
https://github.com/jouni-kantola/webpack-output-by-build-type/tree/why-hash-change
Here goes the scenario:

I build:

Asset
Size
Chunks

0.9bbf83cf4b0bde5cdd21.dev.js.map
512 bytes
0, 6
[emitted]

0.9bbf83cf4b0bde5cdd21.dev.js
756 bytes
0, 6
[emitted]

2.a01031186175de379984.dev.js
455 bytes
2, 6
[emitted]

3.64a0d1a6257d07bf9c8e.dev.js
455 bytes
3, 6
[emitted]

vendor.72eb1607924636054b21.dev.js
254 kB
4, 6
[emitted]

app.d67c37259cfc27adf14e.dev.js
16.9 kB
5, 6
[emitted]

1.b255a8ecec8dd054c7f3.dev.js
756 bytes
1, 6
[emitted]

1.b255a8ecec8dd054c7f3.dev.js.map
512 bytes
1, 6
[emitted]

2.a01031186175de379984.dev.js.map
424 bytes
2, 6
[emitted]

3.64a0d1a6257d07bf9c8e.dev.js.map
430 bytes
3, 6
[emitted]

vendor.72eb1607924636054b21.dev.js.map
335 kB
4, 6
[emitted]

app.d67c37259cfc27adf14e.dev.js.map
18.9 kB
5, 6
[emitted]

index.html
6.35 kB

[emitted]

I change module-a.js from:

import is from 'is-thirteen';

export const a = () => console.log('module a says 12 + 1 === 13', is(12 + 1).thirteen());

to:
export const a = () => console.log('hello world');

I build yet again:

Asset
Size
Chunks

0.3f19b2e7372b486647de.dev.js.map
512 bytes
0, 6
[emitted]

0.3f19b2e7372b486647de.dev.js
756 bytes
0, 6
[emitted]

2.a01031186175de379984.dev.js
455 bytes
2, 6
[emitted]

3.64a0d1a6257d07bf9c8e.dev.js
455 bytes
3, 6
[emitted]

vendor.503164abc295ee5b7ca1.dev.js
254 kB
4, 6
[emitted]

app.928d94b1c06014c2234b.dev.js
16.9 kB
5, 6
[emitted]

1.84b1d26493dcab2a97e9.dev.js
429 bytes
1, 6
[emitted]

1.84b1d26493dcab2a97e9.dev.js.map
370 bytes
1, 6
[emitted]

2.a01031186175de379984.dev.js.map
424 bytes
2, 6
[emitted]

3.64a0d1a6257d07bf9c8e.dev.js.map
430 bytes
3, 6
[emitted]

vendor.503164abc295ee5b7ca1.dev.js.map
335 kB
4, 6
[emitted]

app.928d94b1c06014c2234b.dev.js.map
18.9 kB
5, 6
[emitted]

index.html
6.35 kB

[emitted]

So to what I think needs to be documented:

What types of changes should a developer really be aware of when making changes.
In this build, is-thirteen changed ID from 59 to 85, and that caused three bundles to be cache busted. In a larger app that could be quite a lot of code that needs to be shipped again to the end-user. Is there anyway to prevent this small change, from having this large effect?
Is there anyway of preventing the vendor bundle from changing hash, when changing consuming code?

I think I've done the most important bit, to extract the manifest, but still it's very easy to get chunks cache busted. There are loads of blogs discussing this, but I still believe the truly nitty gritty is missing to be documented.

If I replace require('webpack-chunk-hash') with webpack.HashedModuleIdsPlugin() all seems to play nice.
Only changed bundle hash after that is 1.f948e0e64b866b43bc18.dev.js to 1.41c92261bb86681d218a.dev.js. Rest stays the same.
So I removed the inlining of the manifest to generate a manifest file, and it seems like it updates fine.
1.41c92261bb86681d218a.dev.js -> 1.f948e0e64b866b43bc18.dev.js
manifest.9262854228a18bb6d1d6.dev.js -> manifest.ff60e3d222a7b3d2143b.dev.js
Rest stays the same.
All bundles grew a bit, but in the long-run I think that definitely is worth it.
Anything else I need to be aware of?

Btw, the reason why I extracted the manifest is because of this issue, when manifest has not been inlined:
https://github.com/erm0l0v/webpack-md5-hash/issues/9

@jouni-kantola HashedModuleIdsPlugin does most of the work (easier than module ids). I would recommend using NamedModulesPlugin (same but without hashing) during development (better output). Extracting manifest in a way or another becomes crucial when you split bundles (otherwise manifest changes can invalidate something you don't want).
There's one more option - records. Storing records across builds is apparently the ultimate option. You get an extra file to track in your repository then. The nice thing is that this works reliably with code splitting.
I think webpack should come with stronger defaults and treat numbered module ids as a special case that's enabled through a plugin rather than vice versa. I would default with NamedModulesPlugin myself. If webpack knew something about build targets, I would pick the hashed variant for production. In fact I might go as far as to merge these plugins as one and expose hashing through a plugin option. They are essentially the same after all apart from that tiny bit. Less to remember.

I'm working with updating the docs at the moment. I realised I got things a bit backwards after-all yesterday.
Yes, use HashedModuleIdsPlugin to generate IDs that preserves over builds. However,  webpack-chunk-hash/webpack-md5-hash needs to be used to base the file hashes on file contents.
So this is the simplest config I'm suggesting:
var path = require('path');
var webpack = require('webpack');
var ChunkManifestPlugin = require('chunk-manifest-webpack-plugin');
var WebpackChunkHash = require('webpack-chunk-hash');

module.exports = {
  entry: {
    vendor: './src/vendor.js',
    main: './src/index.js'
  },
  output: {
    path: path.join(__dirname, 'build'),
    filename: '[name].[chunkhash].js',
    chunkFilename: '[name].[chunkhash].js'
  },
  plugins: [
    new webpack.optimize.CommonsChunkPlugin({
      name: ["vendor", "manifest"],
      minChunks: Infinity,
    }),
    new webpack.HashedModuleIdsPlugin(),
    new WebpackChunkHash(),
    new ChunkManifestPlugin({
      filename: "chunk-manifest.json",
      manifestVariable: "webpackManifest"
    })
  ]
};

Directly related issue: https://github.com/webpack/webpack/issues/1479
(which in-turn links to the resource: https://github.com/dmitry/webpack-hash-test)

All right. I went through a whole bunch of scenarios to check what updated hash.
I use:

HashedModuleIdsPlugin
WebpackChunkHash
CommonsChunkPlugin for vendor chunk
code splitting with import()

This is what I came up with:
https://gist.github.com/jouni-kantola/1c1e2bfaebf30de50d1b6a71b869da13
I'll try to document it in docs, in some kind of overview. I'm probably leaving out the files and only describe list the actions.

I also tried adding recordsPath, recordsPath: path.resolve(__dirname, './recordsPath.json').

reordering code splits
renaming sub modules dir names
still have large effects on long-term caching.

@sokra: Wouldn't at least the long-term caching problems caused by renamed code splitted chunks, be fixed if they weren't prefixed with the ordering number?

@jouni-kantola would making sure that a chunkId doesn't change in combination with HashedModuleIdsPlugin, fix most of these problems?
When using WebpackChunkHashPlugin and an entry is added or removed, the chunkId's would change, but the ChunkHash generated by WebpackChunkHashPlugin would not and the function call webpackJsonp inside the chunk, is providing different chunkIds even though its referring to the same hash. If the ChunkId's were somehow fixed, (eg entry name, or hashed path), then you may not even need to use the WebpackChunkHashPlugin.

Related: #131.

I'll try to document it in docs, in some kind of overview. I'm probably leaving out the files and only describe list the actions.

@jouni-kantola are you still interested in pr-ing some updates or a new article? It seems this is somewhat covered in the caching guide but could probably be improved.

@jouni-kantola I found your Gist very helpful, thanks fore that. Can I ask why you added WebpackChunkHash to your set? Is HashedModuleIdsPlugin documented anywhere? I find adding a new chunk causes all chunk ids to change. Should I not use name in chunkFilename: 'js/[name]-[chunkhash].js'?

@jouni-kantola I think between @timse's post and the caching guide we can probably push this past the finish line. We should definitely link to @timse's post from that guide and make any other changes necessary to bring it up to date. Once that happens, I think this issue can be closed.

Hello! Sorry for not getting back to you guys in quite some time. The reason why I created this issue and went through the steps in the gist is to make developers aware that many things will affect long-term caching.
If @timse's post is the baseline for creating long-term cacheable assets, I think that should be the caching docs from now on. Added to that I think many steps could be elaborated a bit more, just to show the effect of i.e. an extra module dependency.

Regarding official webpack blogs posts that basically are written to be docs, I think they should be created in the docs repo directly. Redundant information is one of the reasons https://github.com/webpack/webpack/issues/1315 is what it is. Many sources of truth just adds to confusion (/cc @TheLarkInn & @sokra).

@jouni-kantola no worries, and I'm glad we agree on how it should be updated. I've been cleaning up issues and trying to turn the remaining ones into actionable items that we can continue knocking off the list.

Regarding official webpack blogs posts that basically are written to be docs, I think they should be created in the docs repo directly. Redundant information is one of the reasons webpack/webpack#1315 is what it is. Many sources of truth just adds to confusion.

I agree although I do think the blog serves a slightly different purpose for more loose discussion and walkthroughs. However, we need to be better about first, finishing the backlog, and second, keeping things up to date and staying on top it so we don't find ourselves in the same situation of a huge backlog of things that need to be documented or resolved. The problem is, webpack is a big tool with a lot of things that need doing and, as with all open source work, people only have so much time to spare. I'm hopeful that we'll get there but it is definitely taking some time.
Re this issue though, yeah I think we basically need to just review the caching guide, see what's missing, and add that. Then this issue, and probably a whole list of other ones on the main repo, can be closed out.

Going to try to tackle this now...

@jouni-kantola so I think I've pretty much covered everything in #1436. I didn't mention webpack-chunk-hash within the guide as it seems we can use [chunkhash] within chunkFilename without any extra plugins in webpack 3. Could you remind me why that plugin was/is necessary?

@skipjack: When I was testing the hashes were more consistent with the extra hashing plugins. However after a while I've seen this resulting in runtime errors. Better to leave the hashing only to webpack's substitutions.

@jouni-kantola yeah I agree -- I think the simpler we can keep that guide the better. That's why I started from scratch with TheDutchCoder/webpack-guides-code-examples#17 and tried to only use the plugins that seemed necessary while testing. I think if any issues arise with the current guide we should first try to reproduce them in the examples repo, and then decide if it's a common enough issue to mention in the guide.