⚠ Bofrost.lu has degraded performance

In a92b8b2, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1859 ms

Resolved: Bofrost.lu performance has improved in 7482306 after 1 hour, 20 minutes.


OpenSlides ♥ Trees

We should wait for #4018 to be merged to include the TreeService there

@tsiegleauq All done. Also did a better checking when dropping things in the tree. Your described case should be prevented now.


Hi,after I replace the code ,please help

Hi,
It is the problem of tensor dimension.
Just replace the code
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
with
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([-1, 1, 1, 1])).expand_as(self.weight)
Originally posted by @zcwang0702 in https://github.com/kimiyoung/ssl_bad_gan/issues/6#issuecomment-456633881
but after I replace the code
new error:
RuntimeError: The expanded size of the tensor (128) must match the existing size (3) at non-singleton dimension 0
original code error :
File "/home/gis/PycharmProjects/guo/ssl_bad_gan-master/model.py", line 165, in forward
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
RuntimeError: The expanded size of the tensor (5) must match the existing size (3) at non-singleton dimension 3
Thank you!

Hi,
It is the problem of tensor dimension.
Just replace the code
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
with
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([-1, 1, 1, 1])).expand_as(self.weight)
Originally posted by @zcwang0702 in #6 (comment)
but after I replace the code
new error:
RuntimeError: The expanded size of the tensor (128) must match the existing size (3) at non-singleton dimension 0
original code error :
File "/home/gis/PycharmProjects/guo/ssl_bad_gan-master/model.py", line 165, in forward
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
RuntimeError: The expanded size of the tensor (5) must match the existing size (3) at non-singleton dimension 3
Thank you!
try
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([1, -1, 1, 1])).expand_as(self.weight)

Thank you!
but after I replace the code
new error:
RuntimeError: The expanded size of the tensor (128) must match the existing size (3) at non-singleton dimension 0
I modify:
norm_weight = self.weight * (weight_scale[None,:,None,None] / (torch.sqrt((self.weight ** 2).sum(3,keepdim=True).sum(2,keepdim=True).sum(0,keepdim=True) + 1e-6)).expand_as(self.weight))
is ok.
But new error is:
File "/home/gis/PycharmProjects/guo/ssl_bad_gan-master/utils.py", line 34, in log_sum_exp
return ((logits - max_logits.expand_as(logits)).exp()).sum(1,keepdim=True).log().squeeze() + max_logits.squeeze()
RuntimeError: The expanded size of the tensor (10) must match the existing size (64) at non-singleton dimension 1
logits and  max_logits.expand_as(logits) is nomatch!
should I do?
Thank you
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年4月25日(星期四) 晚上8:09
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [kimiyoung/ssl_bad_gan] Hi,after I replace the code ,please help(#12)
Hi,
It is the problem of tensor dimension.
Just replace the code
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
with
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([-1, 1, 1, 1])).expand_as(self.weight)
Originally posted by @zcwang0702 in #6 (comment)
but after I replace the code
new error:
RuntimeError: The expanded size of the tensor (128) must match the existing size (3) at non-singleton dimension 0
original code error :
File "/home/gis/PycharmProjects/guo/ssl_bad_gan-master/model.py", line 165, in forward
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6)).expand_as(self.weight)
RuntimeError: The expanded size of the tensor (5) must match the existing size (3) at non-singleton dimension 3
Thank you!
try
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([1, -1, 1, 1])).expand_as(self.weight)
norm_weight = self.weight * (weight_scale[None,:,None,None] / torch.sqrt((self.weight ** 2).sum(3).sum(2).sum(0) + 1e-6).reshape([-1, 1, 1, 1])).expand_as(self.weight)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Change libWeatherGadget.a from None to Content build action.

The None action will not copy the file to XMA agent during a Windows connected build. Content action will copy it and solve the build failure from Windows.
Second attempt at https://github.com/XamarinUniversity/IOS450/pull/1

Merging! This certainly appears to be working for me on VS2017.


Deprecate name/arity notation

I thought it would be useful, but for me it is inconsistent with rest of the Elixir community.

Done


Memory exhausted

We are running Prestashop using the multi shop feature with 3 shops and approximately 5000 products in total. Our environment is running PHP 5.5 with a memory limit of 768 MB. When we're trying to create a sitemap our server runs out of memory. Tried increasing to 1024 MB and the same problem.

Try look in gsitemap.php on lne 237 the following should be there:
if ($i <= 25000 && memory_get_usage() < 100000000)
try change it to this
if ($i <= 25000 && memory_get_usage() < 50000000)
or maybe even this:
if ($i <= 25000 && memory_get_usage() < 25000000)
It limits the size of the files that you generate and helped us to generate sitemaps for sites with more than 5000 products even with small amount of memory

Thanks for your reply Casper! I'm closing this since Prestashop does not seem to take these issues seriously.

Did it help you?

I don't know. The issue is no longer relevant for me. Can't remember if we solved it or went with another solution.


Response to issue #5160, implements the skew normal distribution in stats

Implements skew normal pdf, rvs and stats functions.
rvs uses the method referenced in #5160 and has reasonable performance.
What I haven't done is implement Owen's T function, which would likely improve the speed/accuracy of the cdf function a bit compared to the default integration in _distn_infrastructure currently used.

This looks like a very good start!  I've left a few specific nitpicks. More general comments:

please add this to the list in https://github.com/scipy/scipy/blob/master/scipy/stats/init.py, so that it is included into the html and PDF docs

please add an entry to the list in https://github.com/scipy/scipy/blob/master/scipy/stats/_distr_params.py#L5. This will run a slew of generic tests for this distribution.

this is supposed to work for a being positive or negative: both need to be tested.

it would be good to test that method handle vectorized arguments (rvs is suspect)

style: spaces after commas everywhere, please. I'd also add some more whitespace around binary operators as suggested by pep8.

Added a few minor comments; overall this looks like a nice addition.

I'm not sure what's causing the CI to fail now...
It seems to be a general continuous distribution test which compares the derivative of the cdf to the pdf, but it calculates the derivative using an imaginary step, which causes the cdf function (which is calculated by integrating the pdf) to break.
Is it that there's something I need to set in the general distribution infrastructures to make the domain of the rv real and disable the check_cmplx_deriv test?

Is it that there's something I need to set in the general distribution infrastructures to make the domain of the rv real and disable the check_cmplx_deriv test?

I see this list in the test code.

OK, the remaining failure on refguide-check is trivial : stats tutorial,https://github.com/scipy/scipy/blob/master/doc/source/tutorial/stats.rst, hard coded the number of distributions and this PR adds one more :-).

Fixing norm to handle complex derivatives should be a rather simple exercise of using Faddeeva erf/erfc for complex input. This would unblock the whole set of half-, gen-, skew-norm. Best done in a separate PR though.

Took another look at this. This is basically ready. We can pick on using np.standard_normal instead of np.normal, on some unnecessary brackets, but that's fine. One thing which needs fixing is the test: int(1e6) would likely do it. And there's no way out of some bikeshedding on names: we have norm, gennorm, halfnorm and truncnorm. This one should probably be skewnorm.
Other than that, LGTM.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.

Squashed and merged in f8c02e17ac9a8097167cb3e97bf9cc9a7db89eb9
Thanks Daniel!

Shouldn't this be added to the list of continuous distributions?

Indeed. Several recent additions should be added.


Maps: Remove boarder around map

Minor detail, but would it be possible to remove the grey border around the map?

@bprusinowski I can still see a very small thin line a the bottom ;-)


Set column size on types with variable size

On SQLBindParameter calls we set the column size parameter to 0 when
binding data with variable size.
Microsoft SQL Server rejected those attempts with an HY104 error.
Therefore, we changed the behavior for types with variable size to set
the column size to the length of the data.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Bug on unnest test cases

Describe the bug
Because of lack of cheking, there're many bugs in unnest.
To Reproduce

Import & wrangle nmas_sensor_short.csv.txt
Apply nest, unnest with no idx provided (which means unnesting all elements)
Weird results, like null values, colnames wrapped with underscores and so on.

Expected behavior
Unnesting all elements properly.
Screenshots

The main reason of this bug was the test cases do not check the result of tests. Just checked if it runs without exceptions.

I happened to develop the set type by value feature. Without this feature it is harder to implement unnest.

This had been started as a bug issue, but the impact is quite big and good for every other cases.
So I've changed the label from "bug" to "new feature".
With this issue (PR #2898), when unnest a JSON type column (a.k.a. Map type or Object type) the output columns are typed properly according to how they were written in the JSON string.
For example, if an element of JSON is written without any quotes and its numeric without a decimal point, then the result type is Long (in dataprep, Integer and Float types are elevated to Long and Double types).
Currently, the final result type depends on the last row, because we change the column type per every row.


Form example

This PR includes the "Form manual app" as an example of various ways of using the Form control.
Code is located in a separate directory as it has the two separate files, with a small README to explain the roles of the files.
Should not be merged before the Form control is available in pglet.

Form control has been published: https://github.com/pglet/pglet-python/releases/tag/v0.7.2
While running Form example I'm getting:
File "/projects/pglet/examples/python/controls/form_control/manual_content.py", line 25, in <module>
    from form import Form

After changing it to from pglet import Form the same works except both "Validation" and "Cross-field validation" sections.


Provide separate built with negative margins

Since the negative margins are not provided by default.
I would be nice to provide a separate built with same.
Some people like myself are not proficient enough to compile sass.

IMHO we won't do that, because we'll get request for every possible build with different kind of options.
This is a good idea for another open source project I guess, I think it existed for v3 and v4.

How can I get a compiled Bootstrap with negative margins enabled?
Or am i missing something?

You need to compile Sass by yourself, or wait for someone to provide a build. As I said I don't think we'll provide every possible build.

Did it myself after some struggle,
thanks for motivating.


drivers: i2s: intel_s1000: I2S BCLK cannot be a fraction of reference clock

Current I2S driver for Intel S1000 SoC/board does not support an I2S BCLK generation if the BCLK frequency happens to be a fractional division of the reference clock frequency.
For example:
If reference clock is 38.4MHz and
if the I2S format is 2ch, 32bits per channel, 48KHz sample rate,
the bit clock frequency has to be 23248K = 3.072MHz
38.4MHz/3.072MHz = 12.5 (a fraction)

Pl. assign this to me, I have implemented the required changes


Testing in indoor new dataset

Hello,
I have an indoor (large hallway) dataset captured by intelrealsense camera attached to a robot publishing all the topics in ROS. So, I have extracted the rgb images (424 x 240) and rgb aligned depth images (424 x 240), and all are synced. Both of their frame ids are camera_front/camera_color_optical_frame. The total number of rgb and depth images are 1200 and all are in png file format. The camera info topic which carries the intrinsic parameters are producing the same message for the whole time. Here is the camera info topic :
header:
  seq: 49136
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 769735564
  frame_id: "camera_front/camera_color_optical_frame"
height: 240
width: 424
distortion_model: "plumb_bob"
D: [0.0, 0.0, 0.0, 0.0, 0.0]
K: [304.7262878417969, 0.0,<PHONE_NUMBER>720703, 0.0,<PHONE_NUMBER>1015625,<PHONE_NUMBER>3183594, 0.0, 0.0, 1.0]
R: [1.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]
P: [304.7262878417969, 0.0,<PHONE_NUMBER>720703, 0.0, 0.0,<PHONE_NUMBER>1015625,<PHONE_NUMBER>3183594, 0.0, 0.0, 0.0, 1.0, 0.0]
binning_x: 0
binning_y: 0
roi:
  x_offset: 0
  y_offset: 0
  height: 0
  width: 0
  do_rectify: False
---

Here is a sample picture and corresponding depth image:

Now, my questions are:

How the calibration file.txt would look like for each set of pairs ? (should be constant for each set up to 1200, only one will be enough)
Which inference file should I use ? (KITTI or NYU-V2)
Please provide the test script to run in this case (with appropriate patch width, patch height and maximum depth flags).

Thanks in advance.

Hi,

It depends. If you format your dataset/data loader as our nyuv2 or KITTI dataset, only one will be enough. However, you can also apply different intrinsics for each frame. You can modify your dataset loader accordingly.
For the outdoor scene, I suggest KITTI. As I noticed there are lots of image pairs, you can split your dataset into [training, eval, test] and finetune our KITTI model with your dataset. You will get much better results.
You can modify the nyuv2 test script accordingly. The suggested patch size is 424x240, i.e., the original image size. Our network has no requirement for input resolution.

Best
Youmin


Hide The empty rows in side menu

Hi,
How to hide the empty rows in FreshMasterDetailNavigationContainer  side Menu.

what do you mean? can you give some example?

Assume that you are talking about the iOS. This has nothing to do with the FreshMvvm or Xamarin, but thats the default behavour of iOS ListViews. You can remove the extra lines, by adding the Property Footer="" into the ListView element. If you still have issues with the framework, please feel free to open another issue with more detailed explanations and some code samples


fixed a bug related to draft losing its selection

Summary
Sometimes rangeCount <= 0 and Draft tries to access an index that's out of range. See stackoverflow for a simplified example. Chrome throws the following exception:
react-dom.development.js:10994 Uncaught DOMException: Failed to execute 'getRangeAt' on 'Selection': 0 is not a valid index.
    at addFocusToSelection (http://localhost:3002/vendor.bundle.js:47834:27)
    at setDraftEditorSelection (http://localhost:3002/vendor.bundle.js:47728:5)
    at DraftEditorLeaf._setSelection (http://localhost:3002/vendor.bundle.js:45761:5)
    at DraftEditorLeaf.componentDidUpdate (http://localhost:3002/vendor.bundle.js:45771:10)
    at commitLifeCycles (http://localhost:3002/vendor.bundle.js:34699:24)
    at commitAllLifeCycles (http://localhost:3002/vendor.bundle.js:35867:9)
    at HTMLUnknownElement.callCallback (http://localhost:3002/vendor.bundle.js:26463:14)
    at Object.invokeGuardedCallbackDev (http://localhost:3002/vendor.bundle.js:26502:16)
    at invokeGuardedCallback (http://localhost:3002/vendor.bundle.js:26359:27)
    at commitRoot (http://localhost:3002/vendor.bundle.js:35971:9)

Fix
I added a rangeCount check.

Amazing! We would love to have this!

I still experience this with Draft-js v 0.10.5, with IE in this IE specific code in setDraftEditorSelection.js:
// IE doesn't support extend. This will mean no backward selection.
// Extract the existing selection range and add focus to it.
// Additionally, clone the selection range. IE11 throws an
// InvalidStateError when attempting to access selection properties
// after the range is detached.
var range = selection.getRangeAt(0); //<-- BOOM
range.setEnd(node, offset);
selection.addRange(range.cloneRange());

I have a workaround but I had to try and hide it in a larger commit it's so ugly.

Is there any particular reason why this really simple bugfix has not been merged yet after more than 1.5 years? I am experiencing the same problem nearwood described last november and it crashes the entire app in IE11 (can't ignore IE because of client requirements). The only way I could make it work is applying this fix manually and working with a fixed local dependency, which of course is super ugly and cuts the app off from any future updates to draft.js.

ping?

hello ? I also have the same error

This was already merged in https://github.com/facebook/draft-js/pull/2271


How can I go to a particular page

Hello,
This issue is similar to a previous one. Have a look at #18

Thank you:)


removed centrify - program doesn't exist now

I've made a pull request to remove "centrify.com" from the JSON data as it appears to be unavailable.  Could you please review my contribution and let me know if it's valid?

I've made a pull request to remove Bugcrowd URL of SAP concur from the JSON data as it appears to be unavailable. I have update it with website security page URL (https://www.tripit.com/web/security). The commit checksum is: c11c3b0e8d0d07d1565c0494765162844f98f777
Could you please review my contribution and let me know if it's valid? Also, if approved, I'd appreciate being added to the list of contributors.


Added doc update how to start chaincode as a service, and how to set grpc parameters in the startup

Signed-off-by: Santosh Kumar<EMAIL_ADDRESS>https://github.com/hyperledger/fabric-chaincode-node/issues/419 Added doc update how to start chaincode as a service, and how to set grpc parameters in the startup

@bestbeforetoday Thank you for your inputs. I have made some changes as per your inputs. Please review it. Thank you!


Adding samples for integrating Azure Functions with DevTest labs

There are some remaining items to clean up:

Server side image paths will be different once the PR is checked in
The artifact name changed, needs to be updated

I'll get these fixed before we merge - but wanted to get some feedback first just in case I have changes that require retesting (since I need to leave the items above for my local testing).  Thanks!


fix scaladoc errors

Fix errors in:

CirceEncoders.scala
Document.scala
File.scala
Reactor.scala

Current coverage is 82.31% (diff: 100%)

Merging #15 into master will not change coverage

@@             master        #15   diff @@
==========================================
  Files            21         21
  Lines           458        458
  Methods         456        456
  Messages          0          0
  Branches          2          2
==========================================
  Hits            377        377
  Misses           81         81
  Partials          0          0

Powered by Codecov. Last update 0c8a022...2346d21


Support Vision Transformers

Hello, is there a beta version maybe for ViT?

Hi @raedinkhaled, not just yet, but our next release will be the first to add support for vision transformers! Stay tuned


Fix race condition with device availability

Occasionally for some reason ephemeral block devices seem to take a little while to become available.
This fixes it.

Should include a requires as well.

@marineam - added + squashed into previous commit

Sorry for the delay. Thanks!


Returning null or false from render within SVG hierarchy crashes app

When building React components it is very convenient to be able to return null (or false) when you don't want to render anything. This is a documented feature of React.
However, returning null or false from the render method of a component nested somewhere within an Svg hierarchy fails (at least on iOS - I didn't try with Android yet).
The failure mode is different depending on whether a falsy value is returned in the initial render or a subsequent render that changes the output from a renderable component to a falsy value.
For example, the following crashes the app immediately (app completely shuts down and exits to home screen):
const MyComponent = ({hide}) => {
  return null
}

const MySVG = () => {
  return (
    <View style={style}>
      <Svg width={100} height={100}>
        <MyComponent/>
      </Svg>
    </View>
  )
}

If a state or props change causes a render method to start returning falsy values where it previously returned SVG components an exception is thrown, for example:
class MyComponent extends Component {
  constructor(props){
    super(props)
    this.state = {
      oops: false
    }
  }
  componentDidMount(){
    this.setState({oops:true})
  }
  render(){
    if (this.state.oops){
      return null
    } else {
      return <Circle cx={10} cy={10} r={5} stroke='#0f0' strokeWidth={2}/>
    }
  }
}

const MySVG = () => {
  return (
    <View style={style}>
      <Svg width={100} height={100}>
        <MyComponent/>
      </Svg>
    </View>
  )
}

The exception this produces is:
Exception 'shadowView (for ID 554) not found' was thrown while invoking replaceExistingNonRootView on target RCTUIManager with params ( 554, 555 )
My current workaround is instead of returning null, return a <Nothing/> component defined as:
const MyComponent = () => {
  return <G/>
}

Thanks for reporting this.
I`ll try to get this been fixed maybe within next version.

Hi @magicismight and @steveliles, I seem to be encountering the second of these two issues as well - an exception similar to: Exception 'shadowView (for ID 554) not found' was thrown while invoking replaceExistingNonRootView on target RCTUIManager with params ( 554, 555 )
As mentioned in the original issue, It occurs when render returns null if it previously rendered a component - as per the this.setState({oops:true}) example above.
There is no error if the component initially renders null and then subsequently renders a component such as Circle.
I’ve also noticed the same exception is thrown if the element I return is of a different type from the one previously rendered, e.g. changing Rect -> Circle or Circle -> Rect:
render(){
    if (this.state.oops){
      return <Rect width="100" height="100" fill="blue" />
    } else {
      return <Circle cx={10} cy={10} r={5} stroke='#0f0' strokeWidth={2}/>
    }
  }

So it seems that:
falsy -> Circle // Ok
Circle -> falsy // Error
Circle -> Circle // Ok
Circle -> Rect // Error

Versions
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
If you have any ideas or if I might be doing something stupid please let me know 😄
Thanks, Matt

Having the same issue with "react-native-svg": "^5.2.0" but I can workaround this problem by toggling the SVG element fillOpacity and strokeOpacity instead of returning null for the component. Hopefully this will help someone


The thirdparty repository url is broken.

When I execute the command "./download-thirdparty.sh", the bash reported the errors:
===== Downloading thirdparty archives...
Downloading libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip from https://doris-incubating-repo.bj.bcebos.com/thirdparty/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip to /home/yiming/Squirrel/incubator-doris/thirdparty/src
--2020-09-29 17:16:37--  https://doris-incubating-repo.bj.bcebos.com/thirdparty/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Resolving doris-incubating-repo.bj.bcebos.com (doris-incubating-repo.bj.bcebos.com)... <IP_ADDRESS>, <IP_ADDRESS>, 2409:8c00:6c21:10ad:0:ff:b00e:67d
Connecting to doris-incubating-repo.bj.bcebos.com (doris-incubating-repo.bj.bcebos.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2020-09-29 17:16:38 ERROR 403: Forbidden.
Failed to download libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip. attemp: 1
/home/yiming/Squirrel/incubator-doris/thirdparty/src/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip md5sum check failed!
except-md5 e8b9ba50270ba3b520aec8ff1089f9d7
actual-md5 d41d8cd98f00b204e9800998ecf8427e  /home/yiming/Squirrel/incubator-doris/thirdparty/src/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Archive libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip will be removed and download again.
Failed to download libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Downloading libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip from https://doris-incubating-repo.bj.bcebos.com/thirdparty/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip to /home/yiming/Squirrel/incubator-doris/thirdparty/src
--2020-09-29 17:16:38--  https://doris-incubating-repo.bj.bcebos.com/thirdparty/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Resolving doris-incubating-repo.bj.bcebos.com (doris-incubating-repo.bj.bcebos.com)... <IP_ADDRESS>, <IP_ADDRESS>, 2409:8c00:6c21:10ad:0:ff:b00e:67d
Connecting to doris-incubating-repo.bj.bcebos.com (doris-incubating-repo.bj.bcebos.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2020-09-29 17:16:38 ERROR 403: Forbidden.
Failed to download libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip. attemp: 1
/home/yiming/Squirrel/incubator-doris/thirdparty/src/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip md5sum check failed!
except-md5 e8b9ba50270ba3b520aec8ff1089f9d7
actual-md5 d41d8cd98f00b204e9800998ecf8427e  /home/yiming/Squirrel/incubator-doris/thirdparty/src/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Archive libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip will be removed and download again.
Failed to download libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
Failed to download libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
If I check the url in the web browser, it reported the massages:
{"code":"AccountOverdue","message":"Your request is denied because there is an overdue bill of your account.","requestId":"34341815-75e4-48b3-81ac-f4fe233d58aa"}

Use this instead:
https://doris-thirdparty-repo.bj.bcebos.com/thirdparty/libevent-20180622-24236aed01798303745470e6c498bf606e88724a.zip
I will modify the code later


The Nuxt 3 build exports module "acorn" as a reference, symbolic link or how it's called in Win

Environment
Operating System: Darwin

Node Version:     v18.16.0
Nuxt Version:     3.5.2
Nitro Version:    2.4.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      nitro, app, modules, css, i18n, swiper, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Antfu's demo also has the same problem
https://github.com/antfu/nuxt-movies-demo.git
Describe the bug
How do I tell Nuxt to export a module as a standard directory (if possible), or in the worse case, how do I copy a file in Windows droping references and making real files of them instead?
https://i.imgur.com/m6JlHNr.png
Additional context
No response
Logs
No response

What is the bug here? Can you explain more and give an example of what is not working for you?

I see what you mean. Yes, on Windows we generate a different type of link as Windows lacks full link support.
I would recommend instead building your project in WSL and uploading from there if you are uploading to a Linux-based server. I think the .tar format would correctly package up the links.

It worked. Thank you！

@danielroe, I'm encountering the same issue. I'm developing on a Mac OS system, and when I run pnpm build, symbolic links are created in .output/server/node_modules, which work as expected. However, when I copy the .output folder to my debian server, these symbolic links are not recognized when I run index.mjs. I've seen your proposed solution, but I'm not entirely familiar with it. Could you please provide a more detailed explanation or perhaps suggest a more straightforward way to address this issue?


row_markdown_pattern should have access to $row

The $row should give us access to rowName and uri.detailed so we can generate the link without hardcoding the path.

Adding this requires a very simple change in ermestjs but I felt like we should discuss a little more about it before jumping into changing it. These are a few things that came to my mind and I needed confirmation for:

We use row_markdown_pattern  to get the rowname and well as the custom display for related entities. So I'm assuming we want these new attributes to be available in both places.

A while ago we added page_markdown_pattern so you can write just one markdown pattern for the custom display of related entities. Using this annotation, you have access to the page of data. So we used the $page namespace that has the following structure:
"$page": {
  "values": [
    {"col": "", "_col": "" }, // row 1 values
    {"col": "", "_col": "" } // row 2 values
  ],
 "parent": {
    "values": {"parent col": "", "_parent col": ""}, // parent row values
    "table": "parent table",
    "schema": "parent schema"
  }
}

At the time we haven't done any of the pseudo-column in templating changes, and we wanted something quick. We only needed the data and didn't need the extra information. This is a bit different from the structure that I used to represent a row of data in other places. Assuming you have an array pseudo-column in entity mode, this is what you have access to using the $self namespace.
"$self": [
  {
    "values":  {"col": "", "_col": "" },
    "rowName": "",
    "uri": { "detailed": "" }
  }, // row 1
  ...
]

So if we want to keep the consistency, I should change the $page data structure to be like the following:
"$page": {
  "rows": [
    {
      "values": {"col": "", "_col": ""},
      "rowName": "",
      "uri": {"detailed": ""}
    }, // row 1
    ...
  ],
 "parent": {
    "values": {"parent col": "", "_parent col": ""}, // parent row values
    "table": "parent table",
    "schema": "parent schema"
  }
}

To keep the consitency maybe the $row object should also have access to the values.

We had a discussion about this and decided to use $self instead of adding a new $row here. And for page, we don't need to make this change for now and it requires more discussion.

Just to add more information to the previous comment, $self is already behaving differently based on the pseudo-column type and DBA needs to know this type before writing the annotation. So we should be able to also use  $self here and it should behave differently depending on where it's used.

With the changes in #887, DBAs now have access to $self in row_markdown_pattern and citation annotations. Given that one of the properties of $self is rowName, $self is not available in row_name context where rowName value is defined.
We decided to leave $page the way it is for now given that it might break some deployments.

We would like to access the rowName and uri.detailed in page_markdown_pattern for a new use case. So we had some further discussions about this, and the following is the summary of it,

Adding $self to page_markdown_pattern might be confusing. It would be hard to understand what this $self refers to. Besides, we still want to access the "parent" information, so we would have to add an extra $parent namespace.

We should add a rows property under $page, an array where each element has values, rowName, and uri. So each object would be similar to the $self of row_markdown_pattern.
$page = {
  values: [
     {_col, col}
  ],
  parent: {
    values: [],
    table: "",
    schema: ""
  },
  rows: [
    {
       values: {_col, col},
       rowName: "",
       uri: ...
    }
  ]
}

We are going to deprecate $page.values but keep it for backwards compatibility.


Fix for "static const" literals in HLSL

Constant globals in HLSL should be static const and not just const. Without it, we get the following warnings as an example:
OpenColorIOTransformShader.ush:10:11: warning: Initializer of external global will be ignored
const int Ocio_grading_rgbcurve_knotsOffsets_0[8] = {-1, 0, -1, 0, -1, 0, 0, 9};

See WAR_CONST_INITIALIZER (3207) in the following:
https://docs.microsoft.com/en-us/windows/win32/direct3dhlsl/hlsl-errors-and-warnings
I have not extensively tested this suggested change yet, but sharing as a conversation starter. The gpu tests seem to be centered around OpenGL only.

Thanks for the PR @num3ric, it looks good to me even though like you said, we don't have DX unit test so we probably need someone to test it manually, would you be able to do that? Meanwhile it would be nice if you could fix the CLA issue by following the link from the above comment so that we can approve the PR when ready.

@remia The CLA is now applied so we should be good there. Regarding testing, I have been testing this changes (manually) with a large number of transforms - so far so good. Let me know if there's anything in particular you think should be tested. I haven't had the chance to port automated tests to DX11/12 yet however.

Actually, we do need to confirm this works with both dynamic properties enabled/disabled. My current tests only covered them disabled. Will do so and report back.

Force-fixed the DCO email mismatch error in the previous commit, so this should be good for approval now.
I'm still working on building a DX app to fully test this on the side, but with minimal testing all looks good so far.  Reading through various operators, the const functions aren't in use when dynamic properties are enabled.

@doug-walker I'll see what I can do! This is certainly something that would benefit us, so indeed worth pushing.
However what I have currently is a standalone ImGui-based DX12 app, which I built as a means of transferring Vulkan knowledge over to DX12 (skipping over DX11)... not something ready to publish at large just yet. Once I have GPU readback working, it will become more interesting for automated testing.

Thanks for the update, yes that sounds very interesting!  Please keep us posted when you might have something to share or if we can help.


Always import standard package before own package

It is a better style and it avoids some troubles,
if you always first import standard packages,
then your own third party packages
and then your own project packages.
E.g.
import sys

import smac

import importance

I fixed this in importance.importance.
btw: the package should not be called importance because it is ambiguous.

If only everyone read PEP8 :)

@sfalkner and you have time to read these issues here? I'm shocked ;-)


[WIP] BUILD-256: Conformance Tests for Shared Resource CSI Driver

Adding single namespace specific operator postgresql into the cluster to run csi driver. There is another pr for techpreview cluster configuration on prow https://github.com/openshift/release/pull/22702 . So the ultimate goal is to run make test-e2e with cluster operator on tech preview openshift cluster.

Now, of course, we log the lack of the config map. And I think we should add a new metric, if not with @alicerum's PR, with either a separate PR, or this PR on top of @alicerum 's PR, that track whether we have a valid config map, and fires an alert if we do not.

From an "operate first" perspective a metric + alert would make sense. I would do this work in a separate pull request.
We can also check if there are ways we can have the cluster storage operator mark itself degraded because a CSI driver has a bad configuration.

This pr states the functional test scenario for verifying shared resource csi driver behavior. This needs to go on top of pr https://github.com/openshift/csi-driver-shared-resource/pull/76 . Still most of the changes are req, once pr #76 merge in.

/assign @jitendar-singh
he should be the one looking at the python pieces, as he is most familiar with the BDD
I'll look at the feature files, yaml, overall scenarios, etc.
/approve

@prietyc123 is this still WIP, or should you remove that label at this point?

As this is still marked WIP, I'm acknowledging that some of the items I'm about to note possible "are coming soon" :-) .
But for clarity, I'm going to list some items I am ultimately expecting with this PR

a feature file marked manual that details the step performed when you validated @alicerum 's metric work recently
we should see a shared secret included in this PR
cover configuration via https://github.com/openshift/csi-driver-shared-resource/blob/master/docs/config.md#maintaining-the-configmap for validating the config options at https://github.com/openshift/csi-driver-shared-resource/blob/master/docs/config.md#configuration-file ... hint, we minimally have a markdown link ref error in that section :-)
some amount of scale testing would be nice

@gabemontero I totally agree with you here. Although initially as part of this PR I am planning to cover the SharedSecrets, SharedConfigmaps and metrics verification part and later in chunks I will be adding stuffs like hostpath volume mount  scenarios worked by @akram and Rhel entitlement so on with separate PRs. However I would really like to know your thoughts on this.
Secondly I also want to discuss about running these .feature file on PRs. How exactly we are thinking to run these files? Do we need to spun up another prow jobs or Existing one would work? We can discuss all these points in scrum/office hours as well.

As this is still marked WIP, I'm acknowledging that some of the items I'm about to note possible "are coming soon" :-) .
But for clarity, I'm going to list some items I am ultimately expecting with this PR

a feature file marked manual that details the step performed when you validated @alicerum 's metric work recently
we should see a shared secret included in this PR
cover configuration via https://github.com/openshift/csi-driver-shared-resource/blob/master/docs/config.md#maintaining-the-configmap for validating the config options at https://github.com/openshift/csi-driver-shared-resource/blob/master/docs/config.md#configuration-file ... hint, we minimally have a markdown link ref error in that section :-)
some amount of scale testing would be nice

@gabemontero I totally agree with you here. Although initially as part of this PR I am planning to cover the SharedSecrets, SharedConfigmaps and metrics verification part and later in chunks I will be adding stuffs like hostpath volume mount scenarios worked by @akram and Rhel entitlement so on with separate PRs. However I would really like to know your thoughts on this.

@prietyc123 I don't know what you mean by hostpath volume mounts scenarios,  but the stuff @akram was previously working on (BUILD-361 / BUILD-381) around "read only" is stuff I'm taking over as Jenkins Cpaas is taking too much time away from him.  I'm fine you handling that scenario separately from this one.
However, I will insist you take on the config map configuration change stuff either with this PR, or a follow up PR that is still part of BUILD-256.  Even if you do not automate, you should be able to try it manually in pretty short order.
As I indicated before, although we should have it eventually, I'm fine with scale testing being after BUILD-256 / 4.10 code freeze.

Secondly I also want to discuss about running these .feature file on PRs. How exactly we are thinking to run these files? Do we need to spun up another prow jobs or Existing one would work? We can discuss all these points in scrum/office hours as well.

As you know, we ended up talking about this in the retrospective today.  This is a complex undertaking that will require a separate R&D story to pursue, given our smoke/BDD dependencies around python etc. not being present in CI, and you cannot assume that you can just install stuff during CI like you do from the command line.  I'm sure as part of the notes @adambkaplan took during the retro meeting a story will be forthcoming for the 4.11 docket.
OK .... now moving on to my review of what you do have.

/retest

The smoke/features/csi-driver-e2e.feature changes we previously talked about look good @prietyc123
Next, to help facilitate what I was asking for with the various bash scripts, I posted the output from shellcheck for each of them. Install shellcheck via sudo dnf -y install shellcheck, make the changes it asks for, make sure it runs clean against each new script, and push the updates here.

Done with the shellcheck error fixes

Then, I believe I heard in scrum that you were working on the feature file for the manual configuration change test we talked about. So I'll sit tight and watch for you next PR update for that.
Lastly, while working on my BUILD-381 another important scenario that QE should cover occurred to me. Namely, after a Pod is provision with a share resource volume, if the cluster admin removes permissions for the Pod service account to use the share, the contents from the volume should be removed. Now, this happens on the controller relist, so it can take up to 10 minutes for the removal to occur. And validation require that either your pod loops on displaying the contents of the volume, or you oc rsh into the Pod and confirm the contents are gone. Bottom line, I think this is another manual test. At least initially. But if you think you can automate this, let me nkow. But this is a key "user facing" feature that should fall under the coverage of QE.
There is a development e2e test in golang in this repo that automates this test if using that for reference helps.

Sure, I will try to run the mentioned scenario manually first and then will automated it. I think it can be doable. Not sure if that needs to be handled with this pr or another pr just after it merge would work.

/label px-approved
internal only QE item

/label docs-approved
internal only QE item

/label qe-approved
internal only QE item from QE

/approve

/retest

aws failure
/retest

bump @jitendar-singh @prietyc123
I only put the hold on here because I want @jitendar-singh to review the new python code from @prietyc123
Once he does that and their are no pending updates, either of you can cancel the hold and this can merge.

/lgtm

/hold cancel


feat!: alternative key registry contract

This is a tentative redesign of the key registry contract, which lets us read all 4 keys in a single merkle inclusion proof, while also performing fewer public storage writes. It relies on PublicMutable with custom deadlines instead of SharedMutable as the key registry must be lax during reads to prevent abuse from accounts performing frequent rotation.
This is meant to be a proof of concept and reference for discussion, so there are no tests yet. If we were to adopt this contract it should be relatively straightforward to replace the current getters with get_current_public_keys.

Update: we've now decided to move forward with this design, even if whether we actually do have full key rotation is up for debate. This is a good middle ground in terms of the code being performant and easy to either add or remove rotation in the future.
What this PR does is introduce the new registry and switch all old contracts to use it. They'll be using historical mode, i.e. reading keys at a specific block in the past instead of reading the current keys, resulting in no max block number constraints. This is a departure from the current behavior, but is only temporary until we switch over from the old API to the new one (https://github.com/AztecProtocol/aztec-packages/issues/7953) so that we can then benefit from reduce gate counts (https://github.com/AztecProtocol/aztec-packages/issues/7954). I've also left the original contract, libraries, etc., unmodified so as to later delete them cleanly instead of making this PR too messy (https://github.com/AztecProtocol/aztec-packages/issues/7955).

Also losing the hard guarantee of fresh keys seems fine to me. In that catastrophic scenario of getting keys leaked I would not care that much that I would potentially lose privacy of a few more notes in the next few blocks after the keys are rotated (someone sending me new notes using my old keys).

This post argues why it's fine for senders to use old and leaked keys for some time. I think it's also fine to use new keys immediately - there's no reason we need a strict block of change since we don't need delayed actions. I see no downsides at all in this approach.

Benchmark results
Metrics with a significant change:

proof_construction_time_sha256_100_ms (16): 5,820 (-17%)
proof_construction_time_sha256_30_ms (16): 1,431 (-18%)
app_circuit_witness_generation_time_in_ms (SchnorrAccount:constructor): 104 (-41%)
app_circuit_witness_generation_time_in_ms (Token:privately_mint_private_note): 147 (-33%)
app_circuit_witness_generation_time_in_ms (Token:transfer): 338 (-25%)
app_circuit_witness_generation_time_in_ms (Benchmarking:create_note): 103 (-39%)
protocol_circuit_simulation_time_in_ms (private-kernel-tail-to-public): 2,701 (-20%)
avm_simulation_time_ms (AuthRegistry:set_authorized): 9.73 (+31%)
avm_simulation_time_ms (Token:_increase_public_balance): 12.0 (-77%)
protocol_circuit_witness_generation_time_in_ms (base-parity): 295 (-48%)
protocol_circuit_proving_time_in_ms (base-parity): 1,685 (+54%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,752 (+1%)
1,556 (+1%)
708 (+1%)
779 (+5%)
770 (+1%)

proof_construction_time_sha256_30_ms
11,995 (+2%)
3,205 (+1%)
:warning: 1,431 (-18%)
1,459 (-9%)
1,485 (-4%)

proof_construction_time_sha256_100_ms
44,162 (+1%)
12,880 (+3%)
:warning: 5,820 (-17%)
5,658 (-7%)
5,643 (-2%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
59.0 (+2%)
88.0 (+1%)

proof_construction_time_poseidon_hash_30_ms
1,527 (+1%)
438 (+6%)
200
226 (+2%)
266 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,642 (+1%)
1,526 (+1%)
675
729 (+2%)
749

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
740
740
740

l1_rollup_calldata_gas
6,716
6,722
6,716

l1_rollup_execution_gas
611,983
612,140
612,285

l2_block_processing_time_in_ms
251
445 (+2%)
806 (+2%)

l2_block_building_time_in_ms
9,450 (-1%)
18,598
36,677 (-1%)

l2_block_rollup_simulation_time_in_ms
9,449 (-1%)
18,597
36,676 (-1%)

l2_block_public_tx_process_time_in_ms
7,865 (-1%)
16,786
34,825 (-2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
2,741
3,637 (+1%)

node_database_size_in_bytes
12,578,896 (-1%)
16,773,200 (-1%)

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
94.0 (-1%)
8,139

FeeJuice:set_portal
10.1 (+4%)
2,362

Token:constructor
122 (+2%)
31,107

FPC:constructor
94.8 (+1%)
22,380

FeeJuice:mint_public
79.0
6,150

Token:mint_public
85.4 (+3%)
11,720

Token:assert_minter_and_mint
90.0 (+3%)
8,028

AuthRegistry:set_authorized
:warning: 9.73 (+31%)
4,537

FPC:prepare_fee
286 (+2%)
8,812

Token:transfer_public
36.3 (-20%)
47,374

FPC:pay_refund
61.8 (-6%)
12,114

Benchmarking:increment_balance
1,004
7,450

Token:_increase_public_balance
:warning: 12.0 (-77%)
8,960

FPC:pay_refund_with_shielded_rebate
145 (+3%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.154 (-1%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.14 (+1%)
3.84
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.111 (+1%)
0.109
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.1 (+2%)
18.4 (+3%)
30.5
59.2 (+2%)
111 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.107 (+3%)
0.107 (+3%)
0.100 (+1%)
0.102 (+2%)
0.101

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.2 (+1%)
26.4 (+1%)
42.8 (-1%)
81.7
159

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109 (+2%)
0.102 (-3%)
0.105 (-1%)
0.101 (-1%)
0.100

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.4 (+1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.106 (+1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
63,593
665,008

Transaction size based on fee payment method
| Metric |  |
| - |  |

Docs Preview
Hey there! 👋 You can check your preview at https://66bbc2f54adcc4ac5d7bdffb--aztec-docs-dev.netlify.app

Benchmark results
Metrics with a significant change:

app_circuit_witness_generation_time_in_ms (SchnorrAccount:constructor): 105 (-39%)
app_circuit_witness_generation_time_in_ms (Token:transfer): 283 (-30%)
app_circuit_witness_generation_time_in_ms (Benchmarking:create_note): 103 (-38%)
avm_simulation_time_ms (FeeJuice:set_portal): 19.0 (+94%)
avm_simulation_time_ms (Token:mint_public): 42.6 (-43%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 67.5 (+74%)
avm_simulation_time_ms (Token:transfer_public): 21.5 (-34%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,758 (-1%)
1,552
693
746 (-2%)
768

proof_construction_time_sha256_30_ms
11,836
3,179
1,409
1,423 (-3%)
1,470

proof_construction_time_sha256_100_ms
44,167 (-1%)
12,425 (+1%)
5,659
5,510 (-1%)
5,512

proof_construction_time_poseidon_hash_ms
78.0
34.0 (-29%)
34.0
59.0 (+2%)
88.0

proof_construction_time_poseidon_hash_30_ms
1,529 (-1%)
419
201
228 (-2%)
268

proof_construction_time_poseidon_hash_100_ms
5,658 (-1%)
1,530
674
753 (+4%)
749 (-2%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,324
7,844
14,852

l1_rollup_calldata_gas
49,720
92,380
177,440

l1_rollup_execution_gas
1,294,383
2,042,011
3,869,110

l2_block_processing_time_in_ms
259
446
817 (-2%)

l2_block_building_time_in_ms
9,308
18,188
36,294

l2_block_rollup_simulation_time_in_ms
9,307
18,188
36,294

l2_block_public_tx_process_time_in_ms
7,873
16,638
34,672

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
2,969 (-1%)
3,840 (+1%)

node_database_size_in_bytes
12,644,432
16,724,048 (-1%)

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
46.4 (-14%)
8,139

FeeJuice:set_portal
:warning: 19.0 (+94%)
2,362

Token:constructor
83.5 (+1%)
31,107

FPC:constructor
52.3 (+1%)
22,380

FeeJuice:mint_public
36.9 (-2%)
6,150

Token:mint_public
:warning: 42.6 (-43%)
11,720

Token:assert_minter_and_mint
:warning: 67.5 (+74%)
8,028

AuthRegistry:set_authorized
37.5 (+5%)
4,537

FPC:prepare_fee
234 (+2%)
8,812

Token:transfer_public
:warning: 21.5 (-34%)
47,374

FPC:pay_refund
58.5 (-8%)
12,114

Benchmarking:increment_balance
971 (-1%)
7,450

Token:_increase_public_balance
38.3 (-4%)
8,960

FPC:pay_refund_with_shielded_rebate
64.9 (-3%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.167 (+1%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.20
3.85 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.114
0.109
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.6 (+1%)
18.5 (+3%)
31.5
59.0 (-2%)
115 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.111 (+1%)
0.107 (+3%)
0.102 (-1%)
0.102 (-2%)
0.103 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.4 (+1%)
25.9 (-1%)
44.6 (+1%)
83.3 (-1%)
164 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109 (+1%)
0.105 (-1%)
0.104
0.103 (-2%)
0.104 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.5 (-1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.106 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

Transaction size based on fee payment method
| Metric |  |
| - |  |

Benchmark results
Metrics with a significant change:

app_circuit_witness_generation_time_in_ms (SchnorrAccount:constructor): 104 (-40%)
app_circuit_witness_generation_time_in_ms (Token:privately_mint_private_note): 137 (-37%)
app_circuit_witness_generation_time_in_ms (Token:transfer): 294 (-28%)
app_circuit_witness_generation_time_in_ms (Benchmarking:create_note): 101 (-39%)
avm_simulation_time_ms (Token:mint_public): 45.7 (-39%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 70.1 (+80%)
avm_simulation_time_ms (AuthRegistry:set_authorized): 46.8 (+31%)
avm_simulation_time_ms (Token:transfer_public): 20.7 (-37%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,795
1,566 (+1%)
719 (+3%)
769 (+1%)
776 (+1%)

proof_construction_time_sha256_30_ms
11,991 (+1%)
3,234 (+1%)
1,451 (+3%)
1,470
1,477

proof_construction_time_sha256_100_ms
45,100 (+2%)
12,764 (+4%)
6,001 (+6%)
5,813 (+5%)
5,653 (+2%)

proof_construction_time_poseidon_hash_ms
78.0
34.0 (-29%)
34.0
58.0
88.0

proof_construction_time_poseidon_hash_30_ms
1,530 (-1%)
422 (+1%)
201
224 (-3%)
267

proof_construction_time_poseidon_hash_100_ms
5,660
1,531
692 (+2%)
737 (+2%)
763

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,324
7,844
14,852

l1_rollup_calldata_gas
49,624
92,364
177,668

l1_rollup_execution_gas
1,294,287
2,041,995
3,869,338

l2_block_processing_time_in_ms
255 (-2%)
444
808 (-3%)

l2_block_building_time_in_ms
9,324
18,300
36,408

l2_block_rollup_simulation_time_in_ms
9,324
18,300
36,408

l2_block_public_tx_process_time_in_ms
7,887
16,737
34,789

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
2,985 (-1%)
3,871 (+2%)

node_database_size_in_bytes
12,673,104
16,736,336 (-1%)

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
input_size_in_bytes
output_size_in_bytes
proving_time_in_ms

private-kernel-init
95.9
395 (-1%)
21,846
44,858
N/A

private-kernel-inner
175 (+1%)
702
72,545
45,005
N/A

private-kernel-reset-tiny
504
1,194 (-1%)
69,614
44,844
N/A

private-kernel-tail
273 (+1%)
194 (-1%)
50,760
52,256
N/A

base-parity
5.56
N/A
160
96.0
N/A

root-parity
34.0 (+2%)
N/A
69,084
96.0
N/A

base-rollup
2,873
N/A
187,817
664
N/A

root-rollup
39.2 (+2%)
N/A
54,525
716
N/A

public-kernel-setup
100
N/A
103,760
71,222
N/A

public-kernel-app-logic
107 (+1%)
N/A
103,599
71,222
N/A

public-kernel-tail
573
N/A
409,190
16,414
N/A

private-kernel-reset-small
484
N/A
66,533
45,629
N/A

private-kernel-tail-to-public
1,329 (-1%)
719 (+1%)
507,554
1,697
N/A

public-kernel-teardown
94.6
N/A
104,005
71,222
N/A

merge-rollup
19.5 (+2%)
N/A
35,742
664
N/A

undefined
N/A
N/A
N/A
N/A
66,744 (-1%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
344

ContractInstanceDeployer:deploy
1,408
11,731
18.4 (+1%)

MultiCallEntrypoint:entrypoint
1,920
11,731
422 (-8%)

FeeJuice:deploy
1,376
11,731
386 (-2%)

SchnorrAccount:constructor
1,312
11,731
:warning: 104 (-40%)

SchnorrAccount:entrypoint
2,304
11,731
436 (-14%)

Token:privately_mint_private_note
1,280
11,731
:warning: 137 (-37%)

FPC:fee_entrypoint_public
1,344
11,731
29.0 (+16%)

Token:transfer
1,312
11,731
:warning: 294 (-28%)

Benchmarking:create_note
1,344
11,731
:warning: 101 (-39%)

SchnorrAccount:verify_private_authwit
1,280
11,731
27.7 (+1%)

Token:unshield
1,376
11,731
560 (-11%)

FPC:fee_entrypoint_private
1,376
11,731
763 (-10%)

AVM Simulation
Time to simulate various public functions in the AVM.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
53.4 (-1%)
8,139

FeeJuice:set_portal
10.8 (+10%)
2,362

Token:constructor
81.2 (-2%)
31,107

FPC:constructor
53.3 (+3%)
22,380

FeeJuice:mint_public
37.3 (-1%)
6,150

Token:mint_public
:warning: 45.7 (-39%)
11,720

Token:assert_minter_and_mint
:warning: 70.1 (+80%)
8,028

AuthRegistry:set_authorized
:warning: 46.8 (+31%)
4,537

FPC:prepare_fee
253 (+10%)
8,812

Token:transfer_public
:warning: 20.7 (-37%)
47,374

FPC:pay_refund
57.6 (-9%)
12,114

Benchmarking:increment_balance
980
7,450

Token:_increase_public_balance
40.0 (+1%)
8,960

FPC:pay_refund_with_shielded_rebate
67.6 (+1%)
12,663

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.161 (-2%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.24 (+2%)
3.93 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.116 (+2%)
0.111 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.5
17.7 (-1%)
30.3 (-4%)
58.8 (-3%)
112 (-3%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.110
0.102 (-2%)
0.0986 (-4%)
0.101 (-3%)
0.0998 (-4%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.3
26.8 (+3%)
42.8 (-3%)
83.7 (-1%)
159 (-4%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109 (+1%)
0.107 (+1%)
0.104 (-1%)
0.103 (-1%)
0.0999 (-5%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.6
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
132
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.106
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
64,779
668,997

Transaction size based on fee payment method
| Metric |  |
| - |  |


Get-SPOCustomAction Scope parameter

The scope parameter should either be required or defaulted to a value because if it's not supplied, the cmdlet doesn't return anything.

Thank you for reporting this (and sorry for long delay in replying). It has been fixed.


Update homework.sh

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
adding code
What did you learn from the changes you have made?
introductory to shell
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
no
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
yes, some command not covered in class, tried to do research online, too many options, not sure which one to adopt
How were these changes tested?
run in VS code to see if it's working
A reference to a related issue in your repository (if applicable)
echo " I love data " in each file under each directory, not sure if function/ for function is applicable,
@mentions of the person or team responsible for reviewing proposed changes (At least 2 people)

@dtxe @michaeladrouillard

Checklist

[y ] I can confirm that my changes are working as intended

Hi there, glad to see you have began so early and soon on your assignment! That being said, you have unfortunately made a pull request to the wrong repo. You shouldn't be making a pull request to uoft-dsi/shell, but rather your own forked shell repo.
Please read the instructions on your assignment (Submission Information) more carefully (specifically the Assignment Submission Guide)


Compatible with smart phones (Responsive design)

Compatible with smart phones.
The display on the PC will not change.

Looks good to me!


timeZone

How do we get or set the timeZone?

⛔ ⛔ ⛔    WARNING : READ BEFORE CREATING ISSUES    ⛔ ⛔ ⛔
This library was abandoned by its owner. I tried to contact him about 4 months ago with no success. Please cease to open new issues as they will not be handled by him. If you want, there is a fork created by Daniel Moncada and his team which is being currently maintained. Please don't open new issues here so that new users won't be mislead into believing this repo is still up-to-date.


Remove multi_value in "reviewer_comment”

From the following:

[ ] base_type

[ ] User_guide

relates to Issue 16


UI - Workflow view - filtering workflow nodes - re-apply filter fails when going to a more general case

When a user selects to filter nodes (select a set of nodes and apply filter), if they then apply a more specific filter the results of the new filter are immediately seen. However, if they try to apply a more general filter this will not work: the user must first clear the filter and then apply the (new) selection of the more general filter.

Same problem occurs when using "filter by sample" - a more general filter can-not be applied with out first resetting the filter. But a more specific filter can be applied.


Save_Image Error

Hi,
I'm currently attempting to run the demo.py, but I come across an error when attempting to save the file.
Specifically it prints the following error-
“File "C:\Users\palod\Desktop\pyicic\IC_Camera.py", line 479, in save_image
c_char_p(filename),
TypeError: bytes or integer address expected instead of str instance”
I attempted to fix this by using the c_wchar_p instead, but this returns another error.  I was wondering if you could offer any insight as to how I could possible alter this code/ what I need to do to get this demo to work properly. I am using a monochrome GigE camera, python 3, and I have not altered your code except for what is necessary. I am running this on windows 10, and I thought I should note that I do not currently have any light entering the camera, so it is receiving zero signal.
Thank you

Off the top of my head I'd guess this has something to do with Python 3 (I've only used this library with Python 2, which treats strings differently). You could try something like filename = b"your_filename" to ensure filename is a bytes array.

Thank you for the fast response.  Ok I will give that a try and if not I will attempt it on Python 2.
Thanks Again,
Dylan
Sent from Mail for Windows 10
From: morefigs
Sent: Friday, December 1, 2017 5:38 PM
To: morefigs/py-ic-imaging-control
Cc: dpalo325; Author
Subject: Re: [morefigs/py-ic-imaging-control] Save_Image Error (#25)
Off the top of my head I'd guess this has something to do with Python 3 (I've only used this library with Python 2, which treats strings differently). You could try something like filename = b"your_filename" to ensure filename is a bytes array.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@dpalo325 Hi , I am getting the same error. Did you happen to resolve this or did you end up using it with Python 2.xx ?

Sorry, Python 3 wasn't tested with this lib. I don't intend to update this code or debug as I no longer use these cameras.

I've just inherited an IC camera and trying to get it to work using spyder python 3.
The solution I found to this problem is to append the file name with .encode('utf-8').
So for the example on in the basic usage example in readme.md, change:
cam.save_image(''.join(['image-', str(i),'.jpg']), 1)
to
cam.save_image(''.join(['image-', str(i),'.jpg']).encode('utf-8'), 1)
and don't forget to add parentheses in the print commands.


Make --color a shakeOption

I would like to enable colouring by default using shakeOptions; it is not exposed there yet.
Also: Colours are great, they should be on by default! A bit of green makes your build system feel much friendlier.

There should also be a --no-color option, or at least some way of disabling coloring automatically.


Suspend starts during locking animation and finishes after resuming

I've noticed that when issuing systemctl suspend either via hyperidle or manually, suspend consistently takes over about halfway through the locking animation, which leaves the desktop partially visible. Upon resume, the desktop is again partially visible as the animation is finishing. Is there a way to prevent this from happening?
Arch Linux
linux 6.7.9.arch1-1
hyprland 0.37.1-2
hyprlock 0.2.0-2
GPU: AMD RX 580

disable the animation, lol


Update windows-update-troubleshooting.md

It is no longer needed to recommend customers to bypass DO.
DO will fallback internally to perform a full file download if Ranges aren't supported.

@jaimeo - can you take a look at this proposed change? Thanks!

It's fine; please merge.


support self-signed certifications in mattermost connector

Rasa version:
Rasa 1.1.4
Rasa X version (if used & relevant):
Python version:
3.6
Operating system (windows, osx, ...):
linux
Issue:
we are using it from a docker container and passing the root cacerts in the container
docker run  -p 5005:5005 -p 5055:5055 -v /etc/pki/ca-trust/source/anchors/:/etc/pki/ca-trust/source/anchors/ -v $(pwd):/app rasa:addcert run

when trying to use the mattermost connector with an ssl enable mattermost server we get an error about the certificate
Error (including full traceback):
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/rasa/core/channels/mattermost.py", line 98, in webhook
    self.url, self.team, self.user, self.pw, self.bot_channel
  File "/usr/local/lib/python3.6/site-packages/rasa/core/channels/mattermost.py", line 27, in __init__
    super(MattermostBot, self).login(user, pw)
  File "/usr/local/lib/python3.6/site-packages/mattermostwrapper/wrapper.py", line 38, in login
    p = requests.post(self.url + '/users/login', data=json.dumps(props))
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 116, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='redacted_matteromst_server.com', port=443): Max retries exceeded with url: /api/v4/users/login (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

Command or request that led to error:
outgoing hook in mattermost

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

some steps taken:
following the answer here
I did

cat Dockerfile
FROM rasa/rasa:latest-full
RUN pip install pyOpenSSL pyasn1 certifi

only to get to the next error:
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/rasa/core/channels/mattermost.py", line 98, in webhook
    self.url, self.team, self.user, self.pw, self.bot_channel
  File "/usr/local/lib/python3.6/site-packages/rasa/core/channels/mattermost.py", line 27, in __init__
    super(MattermostBot, self).login(user, pw)
  File "/usr/local/lib/python3.6/site-packages/mattermostwrapper/wrapper.py", line 38, in login
    p = requests.post(self.url + '/users/login', data=json.dumps(props))
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 116, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 668, in send
    history = [resp for resp in gen] if allow_redirects else []
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 668, in <listcomp>
    history = [resp for resp in gen] if allow_redirects else []
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 247, in resolve_redirects
    **adapter_kwargs
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host=redacted_mattermost_server.com', port=443): Max retries exceeded with url: /api/v4/users/login (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))

/usr/local/lib/python3.6/site-packages/rasa/core/channels/mattermost.py:109: ResourceWarning: unclosed <socket.socket fd=18, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 43364), raddr=('redacted address', 443)>
  pass
2019-07-03 10:19:16 ERROR    rasa.core.channels.mattermost  - Exception when trying to handle message.HTTPSConnectionPool(host='redacted_mattermost_servers.com', port=443): Max retries exceeded with url: /api/v4/users/login (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))
2019-07-03 10:19:16 DEBUG    rasa.core.channels.mattermost  - HTTPSConnectionPool(host='redacted_mattermost_server.com', port=443): Max retries exceeded with url: /api/v4/users/login (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/urllib3/contrib/pyopenssl.py", line 472, in wrap_socket
    cnx.do_handshake()
  File "/usr/local/lib/python3.6/site-packages/OpenSSL/SSL.py", line 1915, in do_handshake
    self._raise_ssl_error(self._ssl, result)
  File "/usr/local/lib/python3.6/site-packages/OpenSSL/SSL.py", line 1647, in _raise_ssl_error
    _raise_current_error()
  File "/usr/local/lib/python3.6/site-packages/OpenSSL/_util.py", line 54, in exception_from_error_queue
    raise exception_type(errors)
OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]

I have to mention that running the container and executing openssl inside it results in correct SSL connection

Thanks for raising this issue, @erohmensing  will get back to you about it soon.

Hm, this is something I haven't seen before... to be clear, have you been able to connect to the mattermost connector from within docker without the ssl enabled? Perhaps it's a general issue with the connection that's stopping the request from being received?

Hi, thanks for looking into it.
Our mattermost instance is ssl only, so no possible to connect without ssl.
As stated, the openssl utility from within he container can read and match the certificate.

I’ve been looking into different places people have run into this error with no real insights. I understand the utility checks whether the certificate matches the private key, but does it also check whether the cert is valid yet? It may be a “dumb check”, but at least 2 people I’ve seen have run into the problem because the machine they’re running on (e.g. vm) has the clock or date wrong and the certificate isn’t valid yet. Anything there?

Hi, no dumb check here, certificate valid until 2026. self signed certificate you can call it,
we have our own certificate authority running.
This we ran from inside the container
`echo | openssl s_client -servername redactedserver.com -connect redactedserver.com:443 2>/dev/null | openssl x509 -noout -dates
notBefore=Nov  8 14:47:51 2018 GMT
notAfter=Nov  7 14:47:51 2020 GMT`

Hm, then I'm not sure if its the connector or the CA that's making it not work. You could maybe try a Let's Encrypt certificate (that's what we usually use) and see if you have better luck with that...

hi,
letsencrypt is not an option for us,
as seen here
http://blog.pengyifan.com/how-to-fix-python-ssl-certificate_verify_failed/ the
problem is the way you call the connection with python, so is the connector
that needs to learn about self signed certificates.
I can help testing
Thanks!
În mar., 9 iul. 2019 la 13:48, Ella Rohm-Ensing<EMAIL_ADDRESS>a scris:

Hm, then I'm not sure if its the connector or the CA that's making it not
work. You could maybe try a Let's Encrypt certificate (that's what we
usually use) and see if you have better luck with that...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RasaHQ/rasa/issues/3919?email_source=notifications&email_token=ABECVRUKHZIGGEFE4PVRTCDP6R3J3A5CNFSM4H5ELMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQAQPI#issuecomment-509610045,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABECVRVBHWH7C7JTP2FCR2DP6R3J3ANCNFSM4H5ELMDQ
.

Hm okay. You seem to know much more about this than I do -- would you be interested in looking into this and PRing a fix?

Hi, the project is very interesting, if not a bit chaotic :), the skill level I might have. I lack the time. All I can offer now is testing.

Okay. I'll add it to our maintenance inbox we'll get around to this eventually. Let us know if you find more time in the meantime to work on it :)

yea @wochinge agreed I'll take it and add it to my backlog

some kind of workaround would be beneficial, I got inspired by the new videos masterclass but I cannot continue. thanks!

Hi friends,
I tested the connection to mattermost using Letsencrypt certificates and I'm facing the same problem.
Running Rasa Docker image 1.5.1-full
Also tested connection from inside the container and everything seems to be fine using openssl command. Using other channels with letsencrypt for example rocketchat works properly.
If there is more info I could provide please, let me know
thanks

ok thanks for the update, I have this on my radar to tackle soon.

@mihai-satmarean @alebeta90 I tried to understand what's going on here, and since these are self-signed certificated, we might need to tell the requests lib that these are valid. Did you try setting the REQUESTS_CA_BUNDLE environment variable like this?
$ export REQUESTS_CA_BUNDLE=/path/to.cert

Thanks @m-vdb for the idea to set REQUESTS_CA_BUNDLE, it works.

I tried to understand what's going on here, and since these are self-signed certificated, we might need to tell the requests lib that these are valid. Did you try setting the REQUESTS_CA_BUNDLE environment variable like this?
$ export REQUESTS_CA_BUNDLE=/path/to.cert

I've also stumbled here because of the following message in my RASA logfile:
Exception when trying to handle message.HTTPSConnectionPool(host='mattermost.[REDACTED]', port=443):
Max retries exceeded with url: /api/v4/posts (Caused by SSLError(SSLCertVerificationError(1,
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate
 (_ssl.c:1131)')))

Since I'm starting rasa-core via a systemd unit file, it was easy to set REQUESTS_CA_BUNDLE and it did the trick. Now RASA replies to inqueries comming from our internal Mattermost, which is self-signed from our internal CA.
For everyone who wonders how our unit file looks like:
[Unit]
Description=Chatbot API
After=multi-user.target
Wants=postgresql-14.service chatbot-actions-server.service

[Service]
Type=simple
Environment="PATH=/opt/rasa/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin"
Environment="PYTHONPATH=/opt/rasa/mycompanu_rasa_components_v3"
Environment="REQUESTS_CA_BUNDLE=/etc/pki/ca-trust/source/anchors/mycompany-root-ca.crt"
WorkingDirectory=/opt/rasa
ExecStart=/opt/rasa/venv/bin/rasa run --enable-api --cors '*' --log-file /var/log/chatbot/chatbot-api.log
User=chatbot
Group=daemon

The last remaining issue I've left with the mattermost connector/integration is, that every answer from RASA-core back to Mattermost emits an error about a perfectly fine 201 HTTP response - but that's a story for a seperate issue.
 [ERROR]  Failed to send message to mattermost channel [REDACTED]. Response: <Response [201]>


Wallet proposes wrong spend limit during unstaking

When I have 100 TAHO staked and I try to unstake 3 TAHO, the wallet sets the spent limit to 3 veTAHO (OK).
When I have 100 TAHO staked and I try to unstake 100 TAHO, the wallet sets the spent limit to 10 veTAHO (NOOK).
When I have 90 TAHO staked and  I try to unstake 90 TAHO, the wallet sets the spent limit to 9 veTAHO (NOOK).
https://github.com/tahowallet/dapp/assets/78352137/a32f61df-2ecc-4114-a538-019fad827537
Tested on prod env, wallet version 0.51.02922c34

Also, when I had 81 TAHO staked and tried to unstake 81, the wallet proposed 8 veTAHO spend limit. I manually changed it to 81 and the transaction failed when I proceeded:
transaction.ts:129 Failed to send transaction Error: transaction failed [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (transactionHash="0xc40b8e2764da4c562962cb48e0fd14940d1033b8ae291e500080eaddafb719bd", transaction={"hash":"0xc40b8e2764da4c562962cb48e0fd14940d1033b8ae291e500080eaddafb719bd","type":0,"accessList":null,"blockHash":"0x2d407f0b1e7b5e010ca73459ae88538491a260920179c017881fde27cf04cd51","blockNumber":1428585,"transactionIndex":1,"confirmations":1,"from":"0x2D215e6911AD32d2bb5a6240c97540Ae4c7eE3E8","gasPrice":{"type":"BigNumber","hex":"0x068e7780"},"gasLimit":{"type":"BigNumber","hex":"0xb587"},"to":"0xeae5797ba706691630A979a8f3840D01C9e9c7a4","value":{"type":"BigNumber","hex":"0x00"},"nonce":36,"data":"0x095ea7b30000000000000000000000006a3d1d9a7eb615be82b5c50bba8c6ecc7606afe60000000000000000000000000000000000000000000000046419ced7f6a40000","r":"0x57bab1a84387bf91fec6ddfb3937bb69cf694f3cd9a6982b2c71ae077e80fede","s":"0x6aa5fba357a670f86d1588bdefebb13fa596e8230d2d1dadbf28c2a3af849153","v":843263,"creates":null,"chainId":421614}, receipt={"to":"0xeae5797ba706691630A979a8f3840D01C9e9c7a4","from":"0x2D215e6911AD32d2bb5a6240c97540Ae4c7eE3E8","contractAddress":null,"transactionIndex":1,"gasUsed":{"type":"BigNumber","hex":"0xb587"},"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","blockHash":"0x2d407f0b1e7b5e010ca73459ae88538491a260920179c017881fde27cf04cd51","transactionHash":"0xc40b8e2764da4c562962cb48e0fd14940d1033b8ae291e500080eaddafb719bd","logs":[],"blockNumber":1428585,"confirmations":1,"cumulativeGasUsed":{"type":"BigNumber","hex":"0xb587"},"effectiveGasPrice":{"type":"BigNumber","hex":"0x05f5e100"},"status":0,"type":0,"byzantium":true}, code=CALL_EXCEPTION, version=providers/5.7.2)
    at l.makeError (index.js:224:23)
    at l.throwError (index.js:233:20)
    at ge.<anonymous> (base-provider.js:1365:24)
    at Generator.next (<anonymous>)
    at i (base-provider.js:5:58)

Some more data:
When I have 73 TAHO staked and I try to unstake 73 TAHO, the wallet sets the spent limit to 7 veTAHO (NOOK).
When I have 73 TAHO staked and I try to unstake 72 TAHO, the wallet sets the spent limit to 72 veTAHO (OK).

More I think about it, then more I am trying to convince myself that this a wallet error, but do not have any data to confirm it 100% yey

More I think about it, then more I am trying to convince myself that this a wallet error, but do not have any data to confirm it 100% yet

I was able to confirm it is not a wallet issue. In https://github.com/tahowallet/dapp/pull/788 we add possibility to connect to dapp with MM and when I tried to unstake 73 veTAHO from the account connected using MM, MM proposed the spending cap of 7 veTAHO.


Combining diacritics

"\u0061\u0308".StartsWith("\u0061", StringComparison.InvariantCulture)
-> false
"\u0061\u0308".Substring(0,"\u0061".Length).StartsWith("\u0061", StringComparison.InvariantCulture)
-> true
It seems to me, that a comparison with substring gives different results due to combining diacritics in unicode.

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

ID: d9d4aca5-9f7b-19de-969f-3f54d2fab15e
Version Independent ID: 394bb8e0-e246-17ef-18f8-d2b8ea72c0c7
Content: String.StartsWith Method (System)
Content Source: xml/System/String.xml
Product: .net
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for submitting this issue, @Rolschge. Unicode combining characters are considered in the comparison. If you call StartsWith to determine if "\u0061\u0308" starts with "\u00e4", the result is true for the invariant culture and for the current culture (at least when the current culture is en-US).  For culture-sensitive comparisons, the runtime does some string normalization before performing the comparison, so that the comparison is between text units rather than individual 16-bit characters. If you want a byte-by-byte or binary comparison, you should use StringComparison.Ordinal or StringComparison.OrdinalIgnoreCase.
@tarekgh, you might want to add additional detail or corrections to my response, @tarekgh.
I think that this is adequately documented throughout our documentation set. If you think that there's some area of the documentation that needs improvement, please let us know. We'll keep this issue open for the next several days so that you can respond.

The string "\u0061\u0308" string is the characters a and  ̈  which will be equivalent to the "ä"
"\u0061\u0308".StartsWith("\u0061", StringComparison.InvariantCulture) is false becaue the string "ä" doesn't start with "a" ligustically "ä" and "a" are different characters.
while
"\u0061\u0308".Substring(0,"\u0061".Length)
while return "\u0061" which is "a" and "a".StartsWith("a") is true.
This is by design.
The confusion is coming from String class treats the contents as an array of characters (no normalization or anything is done on the characters). so it treats \u0061\u0308" as 2 separate characters as long as you are not doing any linguistic operation on it (e.g. Compare, StartsWith, EndsWith, IndexOf, and LastIndexOf.

Thanks for the details on linguistic operations vs non-linguistic operations.
Maybe this could be emphasized in the docs.
A shorter example on this topic:
> "\u0062\u0308".Contains("\u0062")
true
> "\u0062\u0308".IndexOf("\u0062")
-1

@Rolschge
We have the documentation of StringComparison which talk about the different options can be used when performing the operations on the string with some examples.
https://docs.microsoft.com/en-us/dotnet/api/system.stringcomparison?view=netframework-4.7.1
I don't mind adding more specific examples as you pointed out. I'll let @rpetrusha handle that.

Thanks.


Request: [Firefox Containers] Assume Last Role in this Container

I've tried using the Automatically Assume Last Role feature, which is pretty neat. But the configuration seems to carry over between firefox containers.
Realistically, I want the setting to be saved per container, as I assign each container to a different AWS account.
I'm not even sure if this is possible, but it seems like the LocalStorage is separated between containers. Though I'm not sure if this is true for Extensions running in those containers.

I'm sorry that this feature is difficult to maintain for me.


Update zh-HANT.coffee

2016/MAY/15th leorlf2h  XarBuXar(ingameID)

Hello, @leorlf2h! Thank you for contributing. Can you sign our CLA so that I can merge your pull request?

OK,it done. :)

Great :+1:

Could you tell me how long it will take to get online?
I can't wait to introduce this game to my friend . XD

I can tell you for sure, because it depends on when a new production deploy happens, and there is not a fix schedule.
I'm glad you like the game and hope your friends like it too!


Step_counter not defined ?

optimizer.step()

File "/home/thomas/HELIX/superpoint-graph-job/superpointgraph2/learning/refactor/models/optimizers.py", line 33, in step
group['step_counter'] += 1
KeyError: 'step_counter'
Do you have any idea how it can be solved ? I would like to try it out with Radam
base_optim = RAdam(model.parameters())
return Lookahead(base_optim, k=5, alpha=0.5)
My model is special bec it is built over pytorch geometric.

@tchaton get it a try：
from radam import Radam
base_optim = RAdam(model.parameters(),lr = 0.001)
optimizer =  Lookahead(base_optim, k=5, alpha=0.5)

I try, no problem


Client Side Packages Updated and Chrome Headless

What is the context of this PR?
This PR has been lifted out of the feedback work I've been doing as:
a) it will reduce the review burden in the feedback PR
b) Switching to Chrome headless for Karma tests and Travis functional tests is a one liner but isn't relevant to the feedback work
All client dependencies have been updated to their latest versions; this made using hot-reloading via browsersync much more workable. There are knock on changes to some config (e.g. eslint) where packages had deprecated some features.
PhantomJS has been switched out in favour of Chrome headless for Karma tests only. This removes a dev dependency from the client and means the Karma tests on Travis now use the latest stable version of Chrome rather than a version of webkit that is slowly atrophying.
Sadly we can't currently make use of Chrome headless for the functional tests. Chrome in headless mode doesn't support the API that ChromeDriver currently uses to resize browser windows. The functional tests resize the browser window for its mobile testing (e.g. for testing the navigation). There are potential workarounds but sticking with Phantom until a new release of ChromeDriver is the easiest.
How to review
All yarn commands/gulp scripts should work as before. The Travis build should pass and if you look in the logs you should see that the Travis chrome add on is being used when running the Karma tests.

18 08 2017 09:22:09.378:ERROR [plugin]: Error during loading "karma-phantomjs-launcher" plugin:
  Path must be a string. Received null

Ah, overlap! Realised that I'd only switched out Chrome for PhantomJS in Karma. Was all working for me though so not sure why your functional tests bombed. Will catch up on with you about that on Slack.

Ok, Chrome headless is a no go for the functional tests :( I've updated the PR accordingly.

@adoublebarrel Squish Squash?


Improve UI colors to have more contrast

Hello! I'd love to get rid of my personal eye sore (maybe something wrong with my eyes). First, in the build view, I can barely read the username and the branch on the sidebar; I'd like to make it more legible from my point of view, if you don't mind.

Second, in the repository settings, isn't the settings panel too gray for the text? I switched it to white, and it does seem to look a bit clearer, wouldn't you agree?

To be honest, even here I would prefer the muted gray text to be slightly darker, but that I can definitely live with.

@egor-tensin Thanks for submitting this PR. There are quite some places which need some improvement regarding the contrast of the colors currently used. We are totally open for changes improving it.

thanks for the pull, as mentioned I'd love to see more suggestions :)

PS: code is unformated ... (https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/build/2587/27) - if you need help just tell us

well sure I just like to check against dark theme locally ...


Regenerate CloudRun client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace gcr.io/cloud-devrel-public-resources/elixir16 scripts/generate_client.sh CloudRun
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/metadata.py", line 63, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/CloudRun/synth.metadata'

Blocked by #1416


How is this packaged?

Hi,
Is there any documentation on how the distributed versions of torchstudio are packaged?
I see that the deb file contains a single binary and lots of Qt libraries. but, its unclear how these files get created.
This makes the package look a bit suspicious.
Another advantage of documentation on packaging would be that we (the community) can help package this in more modern formats than deb (like Flatpak and Appimage), and get the app working on almost all modern Linux distros.
Thanks for your hard work,
:slightly_smiling_face:

Hi, TorchStudio is composed of 2 components: a C++ GUI, and open source python scripts (cf the architecture drawing in the README.md). This repo contains the open source python scripts, and the official releases contains installers which deploy the compiled GUI binaries (in the appropriate application folder depending on your OS) and its the corresponding python scripts (in ~/TorchStudio/torchstudio).
I hope to clarify a bit the status, contributions, etc later this week.
Thanks for offering to help with Linux packaging, I'm indeed a bit new to this and went for the most known distribution.

I'd love to see a Flatpak format as well, since .deb only works on Ubuntu. Fedora, Arch, OpenSuse cannot install TorchStudio via conversion via the "alien" package.

Is that Flatpak really standard ? I'm not that much familiar with the Linux world, but it looks like you need to install Flatpak first before being able to install a Flatpakaged software ?

Is that Flatpak really standard ? I'm not that much familiar with the Linux world, but it looks like you need to install Flatpak first before being able to install a Flatpakaged software ?

Flatpak is able to be installed on most (if not all) Linux distributions. It's something that takes one command to install for most distributions (except for Gentoo, where it's two commands) if not already installed by default. Also, Flatpaks can be used on ChromeOS, Steam Deck, etc.

Turns out (based on the reddit comments) that flatpak is not well suited for the way TorchStudio is built.
However starting with TorchStudio 0.9.8 a RPM installer is now also provided, which with the DEB installer should cover most Linux distributions !


Replace all "Swap" in Activity tab with "Contract Execution" because heuristics was bad

Closes #2903. Ref #2902
FYI @JamesSmartCell

Bump. In case you missed it.


Disabled clear all notifications button changes color on click on some themes

https://github.com/microsoft/vscode/issues/61934

I do not reproduce that if we had this issue, it would surface for every disabled action item. Can you report this as new issue after checking that it reproduces elsewhere?

It does not surface in every action item, only that one. It reproduces with the Sapphire theme but not the built in ones. See the difference below, left is not clicked, right is clicked.

I think it's related to this rule:
.monaco-workbench a:active {
    color: inherit;
    background-color: inherit;
}

Toggling :active with devtools in  changes the color.

Verified in 0f6fd4bc87