how to uncover signal using this code

Can this code be useful for  this paper "Uncovering the microseismic signals from noisy data for high-fidelity 3D source-location imaging using deep learning". Or please suggest the related link so that the code for the mentioned paper can be found as this paper is more interesting and useful.Thanks.

I will prepare the open-source package for the paper you mentioned and send
it to you as soon as possible.
Best,
Omar
On Fri, Apr 29, 2022 at 4:19 PM starr34 @.***> wrote:

Hope developers may response to my query.
—
Reply to this email directly, view it on GitHub
https://github.com/omarmohamed15/Scalo_CAE/issues/1#issuecomment-1113374420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4SKVBAKXX52ZJAJTZUBZDVHPVYTANCNFSM5UM4A6OA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for your response.I hope it will be published soon.


Are intrinsic parameters of the IR camera involved in depth computation?

This is a follow up to #803. It makes sense to re-estimate the intrinsic parameters for a multi-device system because of bundle adjustment. That is exactly what I did, the alignment result is better, but it is still not completely aligned.
I am not familiar with the ToF method to calculate depth. My question is when using the ToF method to calculate depth, are the intrinsic parameters of the IR camera involved during the computation of the depth? If yes, how is it involved?
I am guessing once I re-estimate the intrinsic parameters, the depth values in the depth image has to be adjusted somehow to reflect the change. Otherwise, if I use the depth image directly, the depth values might be based on the old intrinsics, hence the alignment still fails. I know for sure the depth will have to be re-estimated on a traditional depth from stereo system if the intrinsic is re-estimated, but I am not that sure about ToF.

Or to put it another way, do we need a method for users to write their own intrinsic values to the device. Given the factory intrinsic values do not seem to be accurate enough..

@wes-b Can we please get an answer on this one? I really want to get #803 to work.

@jasjuang To answer the question in the title, depth engine uses intrinsics to compute z depth. ToF principle computes radial depth internally and we convert to z depth for SDK to expose as depth image. We also use intrinsics for laser/sensor offset compensation as well.
Regarding your comment about needing to re-estimate intrinsics parameter, @rajeev-msft may comment on this, but it is surprising to me that you need to recalibrate intrisics instead of fix it and only calibrate extrinsics between cameras.
Regarding the question of whether can write your own intrisics values to the device, I do not think it is supported now, but @wes-b might be comment about this.
However, if you really want to locally try use your own calibrated value and pass into depth engine with current status of the SDK, you can look into https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/90f77529f5ad19efd1e8f155a240c329e3bcbbdf/src/dewrapper/dewrapper.c#L149, and you can see the depth engine took the k4a_calibration_camera_t pointer, you can give it a try to hack this line with your own values. For transformation API, you only need to initialize the transformation object with updated k4a_calibration_t object with your own values.
Hope these help.

Regarding the question of whether can write your own intrisics values to the device, I do not think it is supported now, but @wes-b might be comment about this.

Sorry, we don't support saving custom calibration to the device.

@rabbitdaxi thanks for the detailed response, I will look into the code you pointed to and report back any findings.

@rabbitdaxi After digging through the code, I was able to make some progress but one thing that confuses me is when I print out the focal and principal points like the below right at the code you pointed to
printf("fx %f\n",dewrapper->calibration->intrinsics.parameters.param.fx);
printf("fy %f\n",dewrapper->calibration->intrinsics.parameters.param.fy);
printf("cx %f\n",dewrapper->calibration->intrinsics.parameters.param.cx);
printf("cy %f\n",dewrapper->calibration->intrinsics.parameters.param.cy);

the output is
fx 0.493066
fy 0.493119
cx 0.500009
cy 0.507625

It seems like the values are normalized. I can understand cx and cy normalized according to the image width and image height, but what is fx and fy normalized according to?

@jasjuang in this specific location, the fx and fy normalized with image width and height respectively. Anyway, this particular code path is using an internal format that pass to depth engine, therefore, we expect the factory intrinsics is consumed here. If you are interested to know, you can refer to this function which may help you understand how we convert between the internal normalized intrinsics values and the opencv-like intrinsics.
By the way, regarding that your original goal is trying to calibrate multi-device extrinsics, may be you can also try use solvepnp from opencv (with intrinsics fixed) and see whether that can give you a good result? If the factory intrinsics is not accurate on your device, then you might see weird 3d result even with just single device, e.g. flat surface might not be flat.

@rabbitdaxi I guessed fx and fy were normalized with image width and height respectively, so thanks for the confirmation. I just finished modifying the SDK in a really hacky way to manually input our own intrinsics into the depth engine. I am going to re-capture again and report back my findings.
I wouldn't say the factory intrinsics are not accurate. It's just not optimal. When we run calibration, which is basically non-linear optimization with LM, there are way more than one combination of parameters that will yield results with low re-projection error, it's non-linear, hence there's no global minimum. Chances are very little an individually calibrated result will happen to satisfy the additional constraints imposed by multi-device calibration. There's a reason bundle adjustment exist. Bundle adjustment basically finds another combination of parameters that will also yield results with low re-projection error but at the same time satisfy additional constraints imposed by the multi-device calibration.

@jasjuang yup, agree with you that you might find optimal parameters including camera calibration and pose and so on with bundle adjustment (potentially you even take into account other unit specific systematic depth error in your optimization and letting you achieve good results). Glad to know that you can hack around with the open sourced SDK.

@amonnphillip Are you having difficulties extracting the corners? I remember you were using charuco boards, right? The resolution of the IR images is low and there is still a lot of noise even when lighted by an IR floodlight. Did you try using a conventional checkboard?
I am able to recalibrate and bundle adjust everything but.... it still doesn't align. I am still trying to pinpoint the problem.

@jasjuang Thanks for the response on this. I took another look at my code and realized I used world points where I should be using image points and vice versa (oh!).. Anyway now I can get a rectified image that looks good. I wrote some code based on a paper to test the depth accuracy via points projected obtained through checkerboard corners from the color image (using a high accuracy board + high accuracy corner detection algo). I will run the calibration results through that code tomorrow and let you know if it is any more accurate than the pre-calibrated values from the camera.

@jasjuang So what I see is that calibration of the IR and color camera does indeed help. I still haven't managed to get the accuracy that I would get from something like the RealSense cameras for example. In my tests the RMS goes from cm to ~2mm after calibration. It should be noted that can get ~1mm or so RMS from the RealSense camera at a resolution of 1280x720.
After going through all that calibration and pose estimation stuff I removed my calibration values and did some quick tests with different resolutions (with the factory calibration). I discovered that simply changing the color resolution to something higher helped RMS by more than 50%. I ran 10 iterations of my test (a low number, so not very scientific, but more of a sanity check that indicates it was not a outlier reading). The results showed that the RMS drops for a color resolution of 2048x1536 and 4096x3072. Now you can attribute this to the fact that you are using a higher color resolution so corner accuracy and therefor pnp accuracy will be much better, but would it be that much better than 1280x720??
Then I tried upping the IR resolution to 1024x1024 (WFOV) and the RMS went right up again??
Like I said, these are just quick tests to try to make some sense of what I am seeing. I wonder if someone could also give this a try.. Test lower color resolutions against higher and see what the RMS is for each..

@amonnphillip How is your RMS error calculated? Judging from your unit is it some sort of distance in 3d space?
Here's what I observed so far. I recalibrate and bundle adjust everything based on the reprojection error of the checkerboard corners. I plotted the reprojected corners and on the images and they all look on point, which aligns with the reported numbers, so that means my calibration code is doing its job correctly. However, the interesting thing is if I plot the checkerboard corners in 3d point clouds based on the calibration results, and then compare with simply using the depth map provided by Azure Kinect to turn the checkerboard corners into point clouds, they are actually off by around 1cm when I view them in meshlab. I can think of two explanation for this

The depth provided by Azure Kinect is not accurate.
Even with bundle adjustment and constraints imposed by multi-device, it's still not enough to constrain the non-linear optimization to arrive with a correct answer, mostly due to the distortion parameters that introduce too many degrees of freedom.

I am hoping it's case 2 because I am about to try adding the depth map provided by Azure Kinect into the calibration. I am not sure if I should keep using reprojection error as the main minimization objective for the non-linear optimization and simply add another penalty term for the difference between pnp and depth provided by Azure Kinect, or do I need to make a huge change to my calibration code so that the main minimization objective becomes the difference in Euclidian distance in 3d for the corners instead of the good old reprojection error. Regardless of which way I add the depth information into calibration, a huge challenge is in order to make this happen, I have to somehow extract the depth engine out of the SDK and include it into the non-linear optimization for calibration.
Question for @wes-b and @rabbitdaxi, what are the inputs required for the depth engine? Besides the intrinsics, is it simply just the IR image? or is there something like a ToF buffer that we have to figure out how to save?

The depth engine input is multiple ToF frames from the camera.


Enhancing the Blog Writing Page for Wordwise

Description
The current blog writing page lacks user-friendly features that would make it easier for users, especially laymen, to create and format blog posts. To improve usability, we propose adding a text editor to the blog writing page. This will enable users to easily create, edit, and format their blog posts without needing technical knowledge.
Proposed Solution

Integrate a rich text editor that includes features such as:

Bold, italic, and underline text formatting
Bullet and numbered lists
Image uploads
Hyperlinking text
Text alignment options

Provide a preview option so users can see how their blog post will look before publishing.

Benefits

Makes the blog writing process more intuitive and accessible for all users.
Reduces the learning curve for users who are not familiar with HTML or Markdown.
Enhances the overall quality of blog posts by allowing for better formatting and presentation.

Additional Notes

Ensure the text editor is responsive and works well on both desktop and mobile devices.

This is a Demo not Exact page:

I will implement it in a way that it looks well with the UI of the Application

@ANSHIKA-26 this issue got closed without even a review. pls look into it.


chore: update globals

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@31a88cf). Click here to learn what that means.

:exclamation: Current head f18b3c6 differs from pull request most recent head 1cc27c8. Consider uploading reports for the commit 1cc27c8 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage        ?   98.79%
=======================================
  Files           ?       25
  Lines           ?     1573
  Branches        ?      289
=======================================
  Hits            ?     1554
  Misses          ?       19
  Partials        ?        0

Flag
Coverage Δ

unittests
98.79% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Show axis and scale bar when showing widget

This shows the axes and scale bar overlay on the canvas whenever the widget is shown. This adds convenience since a large part of this widget is related to what is shown on those. This might be a minor annoyance to some users who want these to be non-visible, but they can still use the napari built-in controls to turn them off.

Codecov Report

Merging #39 (8d86c20) into main (9879d2c) will decrease coverage by 0.26%.
The diff coverage is 33.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #39      +/-   ##
==========================================
- Coverage   93.61%   93.36%   -0.26%
==========================================
  Files          16       16
  Lines        1410     1416       +6
==========================================
+ Hits         1320     1322       +2
- Misses         90       94       +4

Impacted Files
Coverage Δ

src/napari_metadata/_widget.py
93.04% <33.33%> (-1.35%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Can't initilize with resources option

serverSideTranslations function's resources option is ignored.
It returned only common namespace like below.
_nextI18Next: {
  initialI18nStore: {
    en: {
      common: { ... },
      // where is "test" namespace?
    }
  },
  ...
}

Occurs in next-i18next version
8.2.0
Steps to reproduce
export const getServerSideProps = async ({ locale }) => {
  return {
    props: {
      await serverSideTranslations(locale, ["common"], {
        i18n: {
          defaultLocale: "en",
          locales: ["en"],
        },
        resources: {
          en: {
            test: {
              testKey: "123"
            }
          }
        }
      })
    },
  };
};

Expected behaviour
// return of serverSideTranslations
_nextI18Next: {
  initialI18nStore: {
    en: {
      common: { ... },
      test: {
        testKey: "123"
      }
    }
  },
  ...
}

Relevant line is here. Have you been able to debug?

@isaachinman
https://github.com/isaachinman/next-i18next/blob/0162dbd825be1ea6b68f444eb6be735b09a50de2/src/serverSideTranslations.ts#L47
I think this code is bug.
because i18next.config.js will use instead of merge with configOverride arg.

Sorry. this bug fixed v8.5.3
I will upgrade my package version.

@isaachinman
still not working with resources.
passing resources arg, return only arg namespace,
and don't pass resources arg, return other translation files.

@mastrayer The backend option is one which we deep merge between the user provided config, and the default config.
You can see in the i18next documentation that a backend option will override the resources option.
So given next-i18next's current behaviour, you will need to override backend, or provide a custom backend.

@isaachinman How do you override backend?

@adithep By passing the relevant config options in next-i18next.config.js.


LD2410C is no connect

I have LD2410S and this sensor is displayed in the found ones but does not connect. It is possible to connect to the sensor through the application on the phone and get all the data, but in Home Assistant there is an error when connecting. I did not change the password

Connection is via Bluetooth dongle. It is on a chip that supports Home Assistant


Add getters for current configuration values

This was inspired by suggestions provided in #598, thanks a lot to @VictorKoenders.
Fixes #598.

Sorry for the late response, I was going to think about this over the weekend and then Factorio happened and now it's a month later.
A couple of things we've been thinking about:

Not sure what derive attributes we want on the enums, PartialEq, Eq is maybe not needed, Clone or Debug might be? We're not sure
It would be nice if we could have const fn in traits. We were thinking of adding #[inline(always)] to the implementation functions but I don't want to do that before we actually benchmark that it is faster/slower, and I think that's outside of the scope of this PR.

Other than that it looks good, thanks for the contribution!

You understood my question correctly.

I think PartialEq and Eq are needed to ensure you can actually do something with the config values

You can still match on the variants. This is what we do in bincode currently, the following code will still work without PartialEq, Eq:
                Ok(match D::C::ENDIAN {
                    Endianness::Little => u16::from_le_bytes(bytes),
                    Endianness::Big => u16::from_be_bytes(bytes),
                })

But this will not:
if D::C::ENDIAN ==  Endianness::Little {
    panic!("Only big endian supported");
}

But I'm also not sure if there's a downside to adding this


javascript: window.open()   Don't work

"vue-cli-plugin-tauri": "~1.0.0-beta.2",
"@tauri-apps/cli": "^1.0.0-beta.2",
Tauri that I plugged into the Vue project,
The    @@@'window.open' method is executed in js, but does not work

@zuckschwerdt @deftsp @liusong1111 @roryok  Please help me, thank you

@mxismean - why did you ping these people? They are not (to the best of my knowledge) involved in tauri

do you want to open a new tauri window?
look here: https://tauri.studio/en/docs/api/js/classes/window.webviewwindow

do you want to open a new tauri window?
look here: https://tauri.studio/en/docs/api/js/classes/window.webviewwindow

I want to open it in a local browser. Can't I use window.open?

do you want to open a new tauri window?
look here: https://tauri.studio/en/docs/api/js/classes/window.webviewwindow

I want to open it in a local browser. Can't I use window.open?

Check the shell open API: https://tauri.studio/en/docs/api/js/modules/shell#open
Using window.open is being tracked on issue #1657

Thanks


Making babel to use the babelrc file if we find it

This PR tells babel where the babelrc file is if it has been found in the project root. I know you guys are relying on babel to find it when you tell babel the filename and sourceFilename, this works fine in normal js/node projects, here is an example where this will not work.
We have a big repo that can contain a few react-native / js projects. Our build system is similar to BUCK and we keep our third party dependencies in a separate folder (having a global package.json at the project route is not feasible as everyone will have to install every apps dependencies even when they don't need them), the structure looks a bit like this:
third_party/js/. packages from node_modules
common/js/ common code used by numerous apps, common components, services etc.
my_app/native the app
What's happening is something from my_app/native (where the .babelrc file is) is requiring something from common/js which is then requiring something from third_party/js and so babel has no idea what .babelrc file to use and we get compilation errors.
This PR fixes that by telling babel to extend the .babelrc file found in the first project root.

@skevy does this seem good to you? LGTM if you think so.

Any update on this. I assume I have to fix that ci check failure?

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @skevy as a potential reviewer. Could you take a look please or cc someone with more context?

Does this merge the .babelrc or uses only the new .babelrc?

It extends the supplied babelrc (as described here: https://babeljs.io/docs/usage/options/). Which then get's extended by the following line with react-natives extraConfig:
let config = Object.assign({}, babelRC, extraConfig);

@facebook-github-bot shipit


chore: updating Pod to add Yoga style to HEADER_SEARCH_PATHS for new arch

Fix react native (0.73.X) build failing when new architecture is enabled on iOS: https://github.com/react-native-webview/react-native-webview/issues/3218

@brandon-austin-lark You're welcome

Thank you very much

@tominou Happy to help!

This has been fixed by #3231


Add cause to error when setting log level

Summary
Small PR to add more context when we fail to set the log level.
Description
Just a one line change to add the cause to the error when we fail to set the log level.
Related Issue
None
Additional Reviewers
@alexr-bq
@NerdLogic

 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.


[8.x] Revert isDownForMaintenance function to use file_exists()

After updating one of our applications to Laravel 8.x, we noticed a recurring issue with our queue workers after deployments. When we would run php artisan queue:restart during the deployment process, the worker processes would restart as expected, but they would no longer work jobs from the queue.
After some investigation, we determined this issue was specifically occurring because our deployment script executes php artisan queue:restart while the application is still in maintenance mode. It appeared that even after we brought the application out of maintenance mode, the isDownForMaintenance check from within the worker processes was still returning true.
It appears the issue was introduced in this PR, which would explain why we never encountered this issue prior to updating to Laravel 8.x. We believe the issue is related to differences in how the statcache is utilized between is_file() and file_exists().
Steps to reproduce issue

Setup a supervised process to run the php artisan queue:work command.
Start the queue worker.
Run php artisan down to bring the application into maintenance mode.
Run php artisan queue:restart to restart the queue worker.
Run php artisan up to bring the application out of maintenance mode.
Dispatch a job onto the worker's queue. The job will never be processed.

Ping @GrahamCampbell

Fine by me. Should go to 6.x if relevant.


let _safeProtoExtend function safer.

_safeProtoExtend function will reset a non-exist function to 'undefined', so it is not safe enough.

This issue was moved to NEYouFan/nej-framework#5


Install Basler Pylon dependency into continuous integration environment

Installing pypylon into the remote continuous integration environment (Travis/Appveyor).
This is a little tricky, since it seems you can't download Pylon without filling in a web form. I could email Basler to ask, or we could try filling in web forms with curl and wget.
After Pylon is installed, the python wheel installation of pypylon is easy, on linux you'd just do this:
wget -O pypylon.whl https://github.com/basler/pypylon/releases/download/1.4.0/pypylon-1.4.0-cp36-cp36m-linux_x86_64.whl
pip install pypylon.whl

TODO:

[ ] MD5 for Linux Pylon download: certutil -hashfile ${FILENAME} md5 (see instructions)
[ ] MD5 for Windows Pylon download:  certutil -hashfile ${FILENAME} md5 (see instructions)
[ ] Email Basler
[ ] Try web form filling with curl

https://www.baslerweb.com/fp-1551786516/media/downloads/software/pylon_software/pylon-<IP_ADDRESS>57-x86_64.tar.gz
https://www.baslerweb.com/fp-1551786641/media/downloads/software/pylon_software/Basler_pylon_<IP_ADDRESS>57.exe

Md5 hashes for the pypylon wheels
certutil -hashfile pypylon-1.4.0-cp35-cp35m-win32.whl
SHA1 hash of pypylon-1.4.0-cp35-cp35m-win32.whl:
02a00260e3f66309a0ed9ecfb014665714d54589
CertUtil: -hashfile command completed successfully.

certutil -hashfile pypylon-1.4.0-cp36-cp36m-win32.whl
SHA1 hash of pypylon-1.4.0-cp36-cp36m-win32.whl:
d46ad418f31571ef201b4639bfcf2d6fd44d366c
CertUtil: -hashfile command completed successfully.

certutil -hashfile pypylon-1.4.0-cp37-cp37m-win32.whl
SHA1 hash of pypylon-1.4.0-cp37-cp37m-win32.whl:
4689784aeaf7627486e1ba44923718ba16a585c6
CertUtil: -hashfile command completed successfully.

Closed via https://github.com/DeMarcoLab/piescope/pull/4


Fix #1984: recursively reference all assemblies for document persistence

See #1984 for bug description.
A similar bug was fixed in #1851, I've used the same assembly walking strategy to fix this bug.

 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.:x: lngr sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I'm gonna call a stop guys, hold on. This assembly walking is done in LamarCompiler itself. So what is the actual bug? And this "fix" if one is necessary, should be done there if that assembly walking isn't being done correctly.

The PR contains a test case that triggers the bug.

@jeremydmiller Quick note, fix added in https://github.com/JasperFx/marten/issues/1851 by @rwasef1830 which you had checked and merged only addressed it for CompiledQuerySourceBuilder. The same fix is required for DocumentPersistenceBuilder as well which @lngr has added now.

Take this as is, it's not something you can handle in Lamar. Not sure that I would ever recommend folks using generic documents in Marten, but it's come up from multiple people, so let support this.


the requestData not support the map[string]interface{}?

I need post a json data, there're int ,string value, so I use the map[string]interface{}, but it's error.
the info is : map[string]interface{} not  implement  io.Reader（missing Read method）
Could you tell me how I shiuld do?

Maybe I had know, need json.Marshal the map,then bytes.Buffuer.


Code refactoring

The package was turned into class based model.
Changed data storing from python file to json file.
Added Error checking.
Added validations.
Improved the performance overall.

thank you for your editing


 Getting a JNI error - java.lang.UnsatisfiedLinkError

This is on RHEL 7. I've installed cloudhsm JCE 5.6.0:
$ rpm -qa | grep cloud
cloudhsm-jce-5.6.0-1.el7.x86_64

I also ran the configure-jce step:
$ sudo /opt/cloudhsm/bin/configure-jce -a $HSM_IP

Is there something else to install to get the shared libraries for SDK 5?
When I try to run the fat jar built with Maven from the Github repo (on sdk5 branch), I get this:
java -ea -jar login-runner.jar --method explicit --user user --password pass
Exception in thread "main" java.lang.ExceptionInInitializerError
	at com.amazonaws.cloudhsm.examples.LoginRunner.loginWithExplicitCredentials(LoginRunner.java:113)
	at com.amazonaws.cloudhsm.examples.LoginRunner.main(LoginRunner.java:90)
Caused by: com.amazonaws.cloudhsm.jce.jni.exception.InternalException: Failed to load cloudhsm_jce native library. Error: java.lang.UnsatisfiedLinkError: /tmp/CloudHsmNativeLibraryTemporaryDir7438679742437118261/libcloudhsm_jce.so: /tmp/CloudHsmNativeLibraryTemporaryDir7438679742437118261/libcloudhsm_jce.so: failed to map segment from shared object: Operation not permitted
	at com.amazonaws.cloudhsm.jce.provider.CloudHsmProvider.<clinit>(CloudHsmProvider.java:539)
	... 2 more
Caused by: java.lang.UnsatisfiedLinkError: /tmp/CloudHsmNativeLibraryTemporaryDir7438679742437118261/libcloudhsm_jce.so: /tmp/CloudHsmNativeLibraryTemporaryDir7438679742437118261/libcloudhsm_jce.so: failed to map segment from shared object: Operation not permitted
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
	at java.lang.Runtime.load0(Runtime.java:810)
	at java.lang.System.load(System.java:1088)
	at com.amazonaws.cloudhsm.jce.provider.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:53)
	at com.amazonaws.cloudhsm.jce.provider.CloudHsmProvider.<clinit>(CloudHsmProvider.java:535)
	... 2 more

Following up. Turns out the jar already has the shared object, and I guess it's a security-related issue for /tmp, so I remounted /tmp with the right options, and it now works.
sudo mount /tmp -o remount,exec

Thank you for the update! I'll close this out, please re-open if there are further issues.

I have the similar issue about provider initialisation for JCE sdk 5 ? any clue? thanks
Exception in thread "main" java.lang.ExceptionInInitializerError
at com.amazonaws.cloudhsm.examples.AESGCMEncryptDecryptRunner.main(AESGCMEncryptDecryptRunner.java:45)
Caused by: com.amazonaws.cloudhsm.jce.jni.exception.InternalException: Failed to load cloudhsm_jce native library. Error: java.lang.UnsatisfiedLinkError: /tmp/CloudHsmNativeLibraryTemporaryDir8118521319059094837/libcloudhsm_jce.so: /tmp/CloudHsmNativeLibraryTemporaryDir8118521319059094837/libcloudhsm_jce.so: failed to map segment from shared object
at com.amazonaws.cloudhsm.jce.provider.CloudHsmProvider.(CloudHsmProvider.java:719)
... 1 more
Caused by: java.lang.UnsatisfiedLinkError: /tmp/CloudHsmNativeLibraryTemporaryDir8118521319059094837/libcloudhsm_jce.so: /tmp/CloudHsmNativeLibraryTemporaryDir8118521319059094837/libcloudhsm_jce.so: failed to map segment from shared object
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
at java.lang.Runtime.load0(Runtime.java:782)
at java.lang.System.load(System.java:1100)
at com.amazonaws.cloudhsm.jce.provider.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:51)
at com.amazonaws.cloudhsm.jce.provider.CloudHsmProvider.(CloudHsmProvider.java:715)
... 1 more


Running into OOM, is my GPU too bad ?

Im trying to run this on a gtx1060 with 6gb ram.
 Ihave these vegas laying around gathering dust.

I'm training from a different repo, but trying using "--gpu_fraction 0.85" in the command line for the training.  Sometimes it tries to to 100% of your GPU mem and it chokes.

@L2ne For gtx1060, try changing outputs_per_step to 2 or 3, or even 4, and reducing max_mel_frames. It will reduce sound quality a bit, but it will help with memory.

I'm also having this problem, with the same GPU (GTX 1060 with 6Gb or RAM). How much RAM and GPU RAM should we have to train this without having to decrease any parameter?

@Rayhane-mamah when you worked on this (by the way, thanks a lot for this amazing work) what setup did you use to reach maximal quality?

I met similar problem, I can start training tacotron with bathcsize 32 for a few steps, then suddenly  got OOM. Even reduce to 16, it only works for some more steps, then OOM.
I already set sess.graph.finalize() before training loop, no error occurred, but the OOM after several steps. Have no idea about this.


compile error

ERROR in ./node_modules/angular2-google-chart/directives/angular2-google-chart.directive.ts
Module build failed: Error: /Users/jingshaochen/Documents/pgm/hashmon/node_modules/angular2-google-chart/directives/angular2-google-chart.directive.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
    at AngularCompilerPlugin.getCompiledFile (/Users/jingshaochen/Documents/pgm/hashmon/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:656:23)
    at plugin.done.then (/Users/jingshaochen/Documents/pgm/hashmon/node_modules/@ngtools/webpack/src/loader.js:467:39)
    at process._tickCallback (internal/process/next_tick.js:109:7)
 @ ./src/app/app.module.ts 13:40-115
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://<IP_ADDRESS>:0 ./src/main.ts

having the same issue here

I also have same issue here

Same Error

same error


fix(startWith): fix incorrect types

Description:
I think (not sure) that the function definition of startWith is incorrectly typed. Because startWith has function overloads, this incorrect typing has no direct user impact. Except! this incorrect function signature is shown in the documentation for startWith (at the top), creating a source of confusion: https://rxjs-dev.firebaseapp.com/api/operators/startWith
This change can be thought of as a documentation fix, though it is also updates (fixes) the internal typing of the startWith operator function.
Related issue (if exists):

Nope. IMO, it is correctly typed. The D refers to the type of the argument passed to the operator and the T refers to the type of the value received from the source.

@cartant what you said sounds correct, but I don't that startWith currently has that function signature... ?
Currently startWith looks like:
startWith<T, D>(...array: Array<T | SchedulerLike>)

But shouldn't it look like?
startWith<T, D>(...array: Array<D | SchedulerLike>)

After all,

D refers to the type of the argument passed to the operator

As a point of comparison, the type signature of the startWith function itself appears to be incompatible with its second function overload.
i.e. this is the first function overload:
function startWith<T, D>(v1: D, scheduler: SchedulerLike): OperatorFunction<T, T | D>;

and this is the type signature of the function:
function startWith<T, D>(...array: Array<T | SchedulerLike>): OperatorFunction<T, T | D>

Yeah. You're right. I read the diff backwards.


Fix story and responsiveness or RichTextEditor

I want to merge this change because it adds simple responsiveness to rich text editor. Also updates story to include all blocks and styles.
Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] Database migration files are up to date.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.
[x] Changes are mentioned in the changelog.

Here is the report for 26ff83341c57d621e898baed236dc0cd575a6420 (mirumee/saleor @ fix-rich-text)
Base comparison is 7eded6db55abaf4be55ec56a97d4654c62a3b41f.
No differences were found. (click me)

# api.benchmark checkout
  test name                           	left count 	right count
  ------------------------------------	-----------	-----------
  add billing address to checkout     	         41	         41
  add shipping to checkout            	          7	          7
  checkout payment charge             	         16	         16
  complete checkout                   	          6	          6
  create checkout                     	         45	         45

# api.benchmark homepage
  test name                           	left count 	right count
  ------------------------------------	-----------	-----------
  retrieve main menu                  	          5	          5
  retrieve product list               	          4	          4
  retrieve secondary menu             	          5	          5
  retrieve shop                       	          2	          2

# api.benchmark product
  test name                           	left count 	right count
  ------------------------------------	-----------	-----------
  product details                     	         16	         16

# api.benchmark variant
  test name                           	left count 	right count
  ------------------------------------	-----------	-----------
  retrieve variant list               	         13	         13


about UI customize

Hi Yehuda,
This isn't a issue, but I didn't find "send message" on github.
I split a page into many components for reusing,, such as user login, user avatar, footer and header.
each component is wrapped in a , Then I wrote a helper {{include}} to load the components in the page
(I also wrote a handlebars.java helper to render page on server too), eg:

...

{{include "/common/header"}}
...

...

	{{include "/user/login"}}

...
{{include "/common/footer"}}

The problem is: every time I create a new page, I have to write code manually,
Is there a source projects can help me to design page in browser?
For example, A blank page is a bootstrap like grid system , we can create rows, columns and cells using menu,
then add the handlebars component that we defined to grid, finally,
save the component information(page layout, path, width, height...) to the DB?
Do you know some open source project like that?

I'm not aware of any such projects that are targeting Handlebars. If you write something I'd be glad to link to it from the projects using handlebars section!


Update pola-rs and remove workaround

trying to fix CI failures like in https://github.com/duckdb/duckdb-rs/actions/runs/12446619688

It looks like there is some other additional CI breakage, maybe version skew with arrow2:
   Compiling duckdb v1.1.1 (D:\a\duckdb-rs\duckdb-rs\crates\duckdb)
error[E0609]: no field `data_type` on type `ArrowField`
Error:    --> crates\duckdb\src\raw_statement.rs:178:103
    |
178 |             let import_arrow2_array = arrow2::ffi::import_array_from_c(ffi_arrow2_array, arrow2_field.data_type);
    |                                                                                ^^^^^^^^^ unknown field
    |
    = note: available fields are: `name`, `dtype`, `is_nullable`, `metadata`

For more information about this error, try `rustc --explain E0609`.
error: could not compile `duckdb` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 1.


Update the documentation / readme

add sections / document newly added providers
document required configuration (env vars)

The documentation still doesn't contain anything about how to setup a Vault instance that is able to handle token management, how to start Pipeline and get a valid token, and what is a token signing key and how do I get one.
If there are descriptions about these in other readmes then links are perfectly fine, but the current documentation still falls short of being a proper resource to start an authentication-enabled Telescopes API in a few minutes.

Pipeline / Vault setup description:
https://github.com/banzaicloud/pipeline/blob/master/docs/github-app.md


searchpair breaks with nomagic

call searchpair('\[','',']','bW') <- behaves differently with set nomagic contrary to the docs
other code here

[
" cursor here
]

thanks for the patch!


cEmbed function

I made an embed function, which is modular short, comes with default values
Use it wisely, you need to do it like this
await message.channel.send(embed=cembed(title=title,description=something,color=color,thumbnail=picture_url,picture=picture_url1)

thumbnail and picture is optional
Also I set a color for you, you can change if you want

cool


Add command line completion support for :breakadd and :breakdel commands

Thank you very much for implementing this.
Relevant todo item:

Implement completion for "breakadd".  Should expand the second argument, e.g.
"func", and then function names after ":breakadd func".  Including
script-local functions.
Also for ":profile".

At some point, it would be nice to also provide completions for :profile file and :profile func.

Hi,
On Mon, Mar 14, 2022 at 10:45 AM lacygoill @.***>
wrote:

Thank you very much for implementing this.
Relevant todo item:
Implement completion for "breakadd". Should expand the second argument,
e.g.
"func", and then function names after ":breakadd func". Including
script-local functions.
Also for ":profile".
At some point, it would be nice to also provide completions for :profile
file and :profile func.

Created PR https://github.com/vim/vim/pull/9955 for this.

Yegappan


feat: Randomize stray selection

Debating this be an option, I want providers to maintain control of their machines to the fullest, but this prevents machines from racing after the same strays which makes it better for the protocol and oftentimes the providers themselves. I think eventually, some providers would benefit from attempting to claim big files over small files, so having a few different "stray operation modes" could be really good for future-proofing. Let me know what you think.
@karnthis @BiPhan4

I think it is a good plan to make generic random the default, and add on additional customizations later. The process currently is horribly inefficient.


No draw_strokes link in API docs

The "util.draw_strokes" entry in the "utilities" table at the bottom of the Drawing Classifier API docs looks like a link and should be a link, but isn't actually a link.
Also when building the documentation this warning appears hundreds of time:
<partial node>:: WARNING: toctree contains reference to nonexisting document 'generated/util.draw_strokes'

Pulling into 5.7 since I expect this to be a simple fix...


BUG: during setup of integration (v0.0.16)

I added the integration from scratch; got the following errors:
Logger: custom_components.smart_irrigation.sensor
Source: custom_components/smart_irrigation/sensor.py:170

not enough values to unpack (expected 2, got 1)
'float' object has no attribute 'split'

sensor is reporting correct values though:
number_of_sprinklers: 7
flow: 1.12 l
throughput: 7.840000000000001 liter/minute
reference_evapotranspiration: [0.46, 0.73, 1.29, 2.09, 3.01, 3.29, 3.45, 3.02, 1.87, 1.1, 0.57, 0.42] mm
peak_evapotranspiration: 3.45 mm
area: 26.0 m2
precipitation_rate: 18.092307692307692 mm/hour
base_schedule_index_minutes: 11.44 min
unit_of_measurement: s
friendly_name: Smart Irrigation Base Schedule Index
icon: mdi:sprinkler
i will monitor if errors appear after the setup, or if this is on time only

To be complete: here are the complete error entries from the hass logfile:
2020-05-28 12:19:20 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Voortuin for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 296, in async_unload
hass, self
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 64, in async_unload_entry
return await hass.data[DOMAIN].async_unload_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 180, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2020-05-28 12:19:20 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Voortuin for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 217, in async_setup
hass, self
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 59, in async_setup_entry
return await hass.data[DOMAIN].async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 163, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:19:20 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:57:45 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Achtertuin for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 296, in async_unload
hass, self
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 64, in async_unload_entry
return await hass.data[DOMAIN].async_unload_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 180, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] not enough values to unpack (expected 2, got 1)
2020-05-28 12:57:45 ERROR (MainThread) [custom_components.smart_irrigation.sensor] 'float' object has no attribute 'split'
2020-05-28 12:57:45 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Achtertuin for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 217, in async_setup
hass, self
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 59, in async_setup_entry
return await hass.data[DOMAIN].async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 163, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

This only happens after changing options on the integration page, so it looks like updating old settings does need some extra work

Hmpf. Annoying. Closing it here if favor of the other issue


Creating a special application class for testing disabling unnecessary components

The following components have been removed from testing:

Application lifecycle callbacks. This was used to detect when the application was launched from the background while it was running, which will not happen in the current tests.
Crashlytics/Fabric crash reporting.
Facebook SDK intialization.
Parse notifications initialization and subscription.
Checking for application upgrades, and repairing download statuses and clearing the web view cookie cache.

See https://openedx.atlassian.net/browse/MA-821

:+1:


Add KeyVault Certificate Functions

Apologies if this was already worked on or out of spec, adapted directly from secret.rs, welcome any improvements.

moved enum RecoveryLevel to the key_vault lib.rs
added certificate.rs based directly off secret.rs
potentially fn _update_certificate_policy() is not needed/required
documentation may not be suitable

Thanks for your comments Heath, I (think) I've addressed all but the CertificateClient issue - do you have a rust code example I can build off, otherwise I'll decipher from the MS docs.
Let me know if anything else needs changing, potentially (probably) there are some cleaner ways to address some of the fixes I've implemented.
Thanks again.

Apologies for the messy history, I think I have resolved all the changes requested but I am unsure on how to mark them properly? Is marking comments as resolved incorrect?
Cheers

Apologies for the messy history, it took me a while to understand the ins and outs of the code, especially the tests, sorry, but I think I have resolved all the changes requested.
However, I am unsure on how to mark them properly? Is marking comments as resolved incorrect?
Cheers

@rylev
Hi, I'm pretty keen to get this reviewed, as we're currently using a fork in production, I understand @heaths is busy with a bunch of projects, are you (Ryan) able to review this?
Thanks

Could you resolve the conflicts and I'll take a look? I expect a few significant changes.

@heaths - are you able to complete this/provide further feedback? Do the remaining tasks require any further improvement? I also opened issue: https://github.com/Azure/azure-sdk-for-rust/issues/516.
Thanks


Stuck channel open pending with confirmed TX on-chain.

Background
Open channel stuck in pending because LND appears to have missed ZMQ notification. Only resolution was to shutdown LND and run with lnd --reset-wallet-transactions in order to rescan chain. This resulted in channel open TX being found and channel opening immediately.
Your environment

v 0.13.1
Linux btc 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
bitcoind backend
running on custom signet

Steps to reproduce
Exactly how LND missed the ZMQ notification of the TX being included on the chain is unknown, I can only assume it has something to do with the wimpy VM this process is running on which includes the signet mining process which can suck up all the CPU cycles for up to 10-15 seconds while grinding on next block it produces.
Expected behaviour
Would be nice if there was a method to repoll for the channel open TX so as to not go thru the potentially long and painful process of rescanning the chain since the seed word birthday. As this was on a small signet chain it was fairly quick. but on mainnet this could get very ugly.
Actual behaviour
Channel would be stuck in pending forever it appears as currently implemented. I attempted restarting lnd a few times, but only working resolution I found was forcing a L1 rescan.

?> I can only assume it has something to do with the wimpy VM this process is running on which includes the signet mining process which can suck up all the CPU cycles for up to 10-15 seconds while grinding on next block it produces.
Do you have the instance in the logs where this happened handy? The notifier sub-system has logic in place to handle missed blocks/confirmations which should have caught this.

Would be nice if there was a method to repoll for the channel open TX so as to not go thru the potentially long and painful process of rescanning the chain since the seed word birthday

You can trigger this by setting the --height-hint-cache-query-disable flag. You may have longer initial start up, but after it starts up, you can stop setting the flag.

?> I can only assume it has something to do with the wimpy VM this process is running on which includes the signet mining process which can suck up all the CPU cycles for up to 10-15 seconds while grinding on next block it produces.
Do you have the instance in the logs where this happened handy? The notifier sub-system has logic in place to handle missed blocks/confirmations which should have caught this.

I will check, I should have full logs on that server

quick grep for the channelpoint that was affected:
2021-08-10 20:17:04.159 [INF] FNDG: completing pending_id(57a9733c95a8e70b1a0cb3bc885bcafa667ce3d9152c17b3686fad058876bd47) with ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 20:17:04.169 [INF] FNDG: sending FundingSigned for pending_id(57a9733c95a8e70b1a0cb3bc885bcafa667ce3d9152c17b3686fad058876bd47) over ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 20:17:04.170 [INF] CNCT: Creating new ChannelArbitrator for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 20:17:04.172 [INF] CNCT: ChannelArbitrator(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=6003
2021-08-10 20:17:04.174 [INF] NTFN: New spend subscription: spend_id=8, outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, height_hint=6003
2021-08-10 20:17:04.175 [INF] NTFN: Dispatching historical spend rescan for outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, start=6003, end=6003
2021-08-10 20:17:04.185 [INF] CNCT: Close observer for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) active
2021-08-10 20:17:04.185 [INF] NTFN: New confirmation subscription: conf_id=1, txid=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38, num_confs=6 height_hint=6003
2021-08-10 20:17:04.186 [INF] FNDG: Waiting for funding tx (f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38) to reach 6 confirmations
2021-08-10 20:17:04.189 [INF] NTFN: Historical spend dispatch finished for request outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61 (start=6003 end=6003) with details:
2021-08-10 23:47:13.166 [ERR] FNDG: Unable to advance pending state of ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): error waiting for funding confirmation for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): epoch client shutting down
2021-08-10 23:47:13.166 [WRN] FNDG: ChainNotifier shutting down, cannot complete funding flow for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 23:47:38.344 [INF] NTFN: New spend subscription: spend_id=8, outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, height_hint=6057
2021-08-10 23:47:38.344 [INF] NTFN: Dispatching historical spend rescan for outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, start=6057, end=6057
2021-08-10 23:47:38.366 [INF] CNCT: Close observer for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) active
2021-08-10 23:47:38.373 [INF] NTFN: Historical spend dispatch finished for request outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61 (start=6057 end=6057) with details:
2021-08-10 23:47:38.452 [INF] CNCT: ChannelArbitrator(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=6057
2021-08-10 23:47:38.507 [INF] NTFN: New confirmation subscription: conf_id=1, txid=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38, num_confs=6 height_hint=6057
2021-08-10 23:47:38.521 [WRN] CHBU: Replacing disk backup for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) w/ newer version
2021-08-10 23:47:38.524 [INF] FNDG: Waiting for funding tx (f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38) to reach 6 confirmations
2021-08-10 23:47:44.526 [INF] PEER: NodeKey(02d92fb4956c5f0efb497f5ca077922791b506122b5ddbb4e2cde10d08b6285ad5) loading ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 23:47:44.527 [WRN] PEER: Unable to find our forwarding policy for channel f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, using default values
2021-08-10 23:57:45.144 [INF] PEER: NodeKey(02d92fb4956c5f0efb497f5ca077922791b506122b5ddbb4e2cde10d08b6285ad5) loading ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 23:57:45.145 [WRN] PEER: Unable to find our forwarding policy for channel f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, using default values
2021-08-10 23:57:47.253 [INF] PEER: NodeKey(02d92fb4956c5f0efb497f5ca077922791b506122b5ddbb4e2cde10d08b6285ad5) loading ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-10 23:57:47.254 [WRN] PEER: Unable to find our forwarding policy for channel f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, using default values
2021-08-11 00:17:49.228 [INF] NTFN: Dispatching 6 confirmation notification for txid=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38
2021-08-11 00:17:49.228 [INF] FNDG: ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) is now active: ChannelID(38ac3aac38187ee66e4e8a698b3af2805b032f5ed8ab9590bf8c2dc05d15b1f9)
2021-08-11 00:17:49.261 [WRN] CHBU: Replacing disk backup for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) w/ newer version
2021-08-11 00:17:49.285 [INF] NTFN: New confirmation subscription: conf_id=2, txid=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38, num_confs=6 height_hint=6061
2021-08-11 00:17:49.286 [INF] NTFN: Dispatching 6 confirmation notification for txid=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38
2021-08-11 00:17:49.286 [INF] FNDG: Announcing ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0), short_chan_id=6061:1:0
2021-08-11 00:17:49.426 [INF] PEER: New channel active ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) with NodeKey(02d92fb4956c5f0efb497f5ca077922791b506122b5ddbb4e2cde10d08b6285ad5)
2021-08-11 00:17:49.436 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-11 00:22:48.669 [INF] NTFN: New spend subscription: spend_id=2, outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, height_hint=6068
2021-08-11 00:22:48.669 [INF] NTFN: Dispatching historical spend rescan for outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, start=6068, end=6068
2021-08-11 00:22:48.697 [INF] CNCT: Close observer for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) active
2021-08-11 00:22:48.770 [INF] CNCT: ChannelArbitrator(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=6068
2021-08-11 00:22:48.885 [WRN] CHBU: Replacing disk backup for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) w/ newer version
2021-08-11 00:22:48.916 [INF] PEER: NodeKey(02d92fb4956c5f0efb497f5ca077922791b506122b5ddbb4e2cde10d08b6285ad5) loading ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-11 00:22:48.926 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0)
2021-08-11 00:23:38.415 [INF] NTFN: New spend subscription: spend_id=3, outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, height_hint=6068
2021-08-11 00:23:38.415 [INF] NTFN: Dispatching historical spend rescan for outpoint=f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0, script=0 39754f094bb947a7fd4b3875a8297097b726e8bbeca6c77664b314a5e722fc61, start=6068, end=6068
2021-08-11 00:23:38.466 [INF] CNCT: Close observer for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) active
2021-08-11 00:23:38.535 [INF] CNCT: ChannelArbitrator(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=6068
2021-08-11 00:23:38.601 [WRN] CHBU: Replacing disk backup for ChannelPoint(f9b1155dc02d8cbf9095abd85e2f035b80f23a8b698a4e6ee67e1838ac3aac38:0) w/ newer version

--height-hint-cache-query-disable

The description says "Disable queries from the height-hint cache to try to recover channels stuck in
; the pending close state" would this even have an effect on a now showing open? If so perhaps documentation needs updated, as it is not apparent in the description

It'll try to scan for open channels from the initial broadcast height. We use a "height hint" to know where we need to start from so we don't need to scan the chain all over again if a node doesn't have a txindex active. If you have a txindex active, then it's a bit different.

It'll try to scan for open channels from the initial broadcast height. We use a "height hint" to know where we need to start from so we don't need to scan the chain all over again if a node doesn't have a txindex active. If you have a txindex active, then it's a bit different.

txindex=1 is enabled

Ok, at this point it appears you've resolved the issue? If txindex is enabled, then we'll just query that each time whenever we get a request for a confirmation notification: https://github.com/lightningnetwork/lnd/blob/951e2164fdbc77cac604881d689177a179577261/chainntnfs/bitcoindnotify/bitcoind.go#L466

Ok, at this point it appears you've resolved the issue? If txindex is enabled, then we'll just query that each time whenever we get a request for a confirmation notification:
https://github.com/lightningnetwork/lnd/blob/951e2164fdbc77cac604881d689177a179577261/chainntnfs/bitcoindnotify/bitcoind.go#L466

Yes issue is resolved at this point.


Update schema to reflect updated Data Model

Related to #16: This issue is to track the updated schema that allows for the following:

Allows for Shapefiles to be edited by an admin as laws get updated
Allows for updated contextual restrictions such as:

State/Federal holidays
Time of day
Number of party

Related whiteboard drawing


Update install-configure-powershell.md

Fix link to repo

Change reviewed by article sme. Thanks for the contribution.


delete an endpiont which is used by replication rule should give meaningful error

delete an endpiont which is used by replication rule should give meaningful error

1)API should return 412
2)When getting a 412 UI should be specific about the restriction.

The API returns 412 now.


Should cookiecutter increment serial_number?

If I already have a folder named 0000-paper_title then it seems like cookiecutter should detect this an increment the serial number, i.e., download my new paper to 0001-paper_title. Currently, if I trying to just hit return through everything I get:
Error: "0000-paper_title" directory already exists

There are two parts to this:

Getting this type of logic into cookiecutter problably requires us to write a front-end that wraps cookiecutter and injects additional values into the Jinja2 template environment. Something like: http://cookiecutter.readthedocs.io/en/latest/advanced/injecting_content.html
If the numbers are global across DESC (I think they are), then you'll want to have a centralized server tell clients like cookiecutter what the next available serial number is. In LSST DM we'll be using DocHub's API for this (eventually).

Since we have moved away from cookiecutter, I think this issue can be closed in accord with #65.


Fix the ModelError type

ModelError type seems to be copied from SchemaError. This fixes the type issue.

Pull Request Test Coverage Report for Build 571

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 84.061%

Totals

Change from base Build 563:
0.2%

Covered Lines:
1846

Relevant Lines:
2124

💛  - Coveralls

@xiananfan Thanks for this!


Consider adding the Relative Table Position information

Your idea
Background
The relative table position is essential to convert from the "patient" coordinate system to the "scanner" coordinate system. For our application in MRI, it would allow to know the location of the isocenter in every acquisition, not just in acquisitions where the table was not moved, which would be the origin when converted to RAS+ using the qform affine matrix. This has been a requested feature in an issue opened in Dcm2niix for another application; to perform offline gradwarp correction.
The different vendors have different ways of encoding this information in the DICOMs. So there would need to be a discussion about how to unify it.
I have gathered some relevant information here:
From @neurolabusc (comment)
(0043,10b2) LO [956.1\320.1\-17.3125\0\75.3604\58.0479] # GE MR Table Position Information
(0019,1014) IS [0\0\0]                                  # Siemens V* TablePosition
(0021,1005) IS [0\0\0]                                  # Siemens XA TablePosition
(2005,143c) FL 0                                        # Philips MRStackTablePosLong
(2005,143d) FL 0                                        # Philips MRStackTablePosLat
(0065,1023) LO [0]                                      # UIH TablePosition

From @mr-jaemin (comment):
GE Private tag (0043,10b2) MR Table Position Information consists of

isoVectorZ (Distance from ISO to ALIGN)
landmark
tablePosition
dzPETMR
topOfHead
distanceFromTopOfHead
Ex) (0043,10b2) LO [956.1\320.1-17.3125\0\75.3604\58.0479]

Proposition
All manufacturers include information in the Inferior/Superior direction but others also allow some Posterior/Anterior and Left/Right information. I therefore suggest to have a tag, possibly "RelativeTablePosition" that would be a 3 value vector containing the relative table displacement in RAS+ coordinates from when it was first set to isocenter.
"RelativeTablePosition": [x, y, z]
Let me know what you think :)

Is there any guidance on how to proceed from here?

What about the standard data element Slice Location (0020,1041) which is defined to be the "Relative position of the image plane expressed in mm" but relative to an unspecified origin (i.e,, is not required to be table position relative to isocenter, but could be). This is used in MR, though not by all vendors. See for example the result of running this query on IDC data:
SELECT SliceLocation, Manufacturer
FROM canceridc-data.idc_current.dicom_all
WHERE Modality = 'MR'
LIMIT 10

Also, the Enhanced CT IOD in DICOM added a specific Table Position data element, with the definition "Relative longitudinal position of acquisition location of this frame in mm from an implementation specific reference point. Shall be relative to the same reference point for all frames in this SOP Instance, but may be different from the reference point in other SOP Instances. Positions as the table moves into the gantry viewed from the front are more negative." but this has never been officially retrofitted to MR. There is no reason it cannot be added as Standard Extended SOP Class though, and I have seen it one vendor's MR images (do a similar query for it in IDC).

but before that - may be worth checking with DICOM WG-16 on what they know/think about this lack of agreement? (I will drop a quick question)

@yarikoptic Any news from DICOM WG-16? :)

they are above . someone needs to wrap their head around the situation here

@yarikoptic thanks, I did not realize that.

What about the standard data element Slice Location (0020,1041)

I believe this element is what allows to correctly register images that are acquired during the same imaging session (change of tablePosition, change of FOV, translation along a direction). However, it does not say where the table was when the scans were acquired. Here is some data to back this up:
First scan acquired at -20mm FH, slice1:
(0020,1041) -- SliceLocation: 78
(2005,143c) -- Philips MRStackTablePosLong: 0

Second scan acquired with the same parameters acquired at -60mm FH ($\Delta$-40 mm), slice 1:
(0020,1041) -- SliceLocation: 118
(2005,143c) -- Philips MRStackTablePosLong: -60.3

Third scan acquired with the same parameters acquired at +20 FH, slice 1:
(0020,1041) -- SliceLocation: 38
(2005,143c) -- Philips MRStackTablePosLong: 0

The SliceLocation follows the location of the slice with respect to an origin (with an opposite polarity coordinate system in the FH direction in this case). However, the table does not necessarily follow that. I believe the table only moves if the center of the FOV is outside of a specified range from the origin (I think ~50mm for Philips by default). I believe that to know where isocenter is, we need both the sliceLocation (given by the qform/sliceLocation) and the table position.
In any case, this shows the importance of the tablePosition as it gives different information from the SliceLocation tag. I'm all for having a Standard Extended SOP Class, it would standardize the information. For now, I think the information is available in the private tags.


added russian, serbian, 2 chinese, dutch languages in game

i have added multiple languages in the game now, but of course the chinese text wont show because the game's current font being used does not support chinese characters (we may need to find one)

run the game from the editor and go to options, the languages should be visible and selectable from there.


Does not work with server-side Blazor in 3.0.0-preview7

When attempting to use this package with a server-side rendered Blazor application, the page fails to render when the package tries to cast the RemoteJSRuntime instead of the client one (I assume).
Stack Trace:
System.InvalidCastException: Unable to cast object of type 'Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime' to type 'Microsoft.JSInterop.IJSInProcessRuntime'.
   at Cloudcrate.AspNetCore.Blazor.Browser.Storage.StorageBase..ctor(IJSRuntime jsRuntime)
   at ResolveService(ILEmitResolverBuilderRuntimeContext , ServiceProviderEngineScope )
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
   at Microsoft.AspNetCore.Components.ComponentFactory.<>c__DisplayClass6_0.<CreateInitializer>b__2(IComponent instance)
   at Microsoft.AspNetCore.Components.ComponentFactory.PerformPropertyInjection(IComponent instance)
   at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(Type componentType)
   at Microsoft.AspNetCore.Components.Rendering.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame& frame, Int32 parentComponentId)

Edit: Reduced stacktrace

Intresting, i guess it is not really considered to be used in the server-side setup. But could be possible with RemoteJsRuntime, if i understand correctly.
What is your use case if i can ask?
Normally you would have far better options in a server-side setup than local storage.

Just wanted to track a theme setting in localstorage so far. Doing it through JavaScript is trivial but ideally I'd like as little manual JSInterop as possible.
I'm mostly making stuff with blazor without any form of client identification ex. user accounts, so storing settings on the client is necessary.

I've fixed it for server-side blazor in this PR
https://github.com/cloudcrate/BlazorStorage/pull/15
You can download the project and simply reference it until nuget is ready, there is an example available that's doing exactly that.

This is fixed with Version 3.0.0-preview8.19405.7.1on nuget. Thanks to @konradbartecki!


feat(plugin-chart-echarts): add x-filter for MixedTimeseries

use cleaned_sales_data to test x-filter of MixedTimeseries.
Multiplegroup and labelMap should be merged?

Closing in favor of https://github.com/apache-superset/superset-ui/pull/1256
@stephenLYZ @zhaoyongjie feel free to re-open if I'm mistaken and this PR has any different intent.


Very low entropy of code word and short english only word list.

I notice that the word list is only 512 words.
This leaves log2(512^2)=18 bits of entropy for the use of 2 code words. Really it is 16 bits since words must alternate between even and odd for error detection.
Using a larger 2048 word list from the standard BIP39 word lists is an easy way to greatly increase this entropy, while adding multi-language support.
Due to the use of nameplates the chance of collision is low, but not the usual cryptographically-secure-astronomical-scale-chance-of-happening type of low that I would have expected.

Without using the even-odd error detection this would increase 2 word entropy to 22 bits, up from the current 16 bits.

It would be 33 bits with 3 words.

The BIP39 word lists also have support for various languages other than english.

These word lists are carefully selected so that 3 characters uniquely identifies every word, which is useful for auto completion.

While there may be good reasons to use other word-lists, the "lack of entropy" isn't an issue; see for example https://github.com/magic-wormhole/magic-wormhole/issues/359 or https://github.com/magic-wormhole/magic-wormhole/issues/191
For the internationalization / non-english aspect, please see https://github.com/magic-wormhole/magic-wormhole-protocols/issues/31


Parsing name fails if game has colon in title (eg. Deathbase 900,000,000)

CSV stands for "Comma-separated values". But what happens when the value has a comma in it?
Per standard, all^W most implementations will quote the value, like this:
1,"Deathbase 900,000,000",3
pkgi fails to parse here, resulting in things like screenshot:
https://files.catbox.moe/dspr1d.jpg

Comma is currently not supported in name - this is stated in readme. Quoted format also not yet supported, but will be.
Not sure why colon is not supported - afaik it should be supported just fine.


DO NOT MERGE - RFC envoy integration

This PR adds three Envoy-related subdirectories to Cilium repo:
envoy: Envoy proxy in a git submodule (in envoy/envoy) and cilium
filters. Running tests verifies that Envoy binary was successfully
built.
envoy-api: Envoy-api protobuf definitions in submodule
envoy-api/envoy-api, and it's google dependency in submodule
envoy-api/google. A small test program (test.go) is included to test
launching of Envoy and operating it's LDS and RDS APIs.
pkg/envoy: Go packge for interfacing with Envoy, currently used only
by test.go mentioned above.
This is still work-in-progress, but should be good enough for making
CI have all the required dependencies for successful builds.
Note that for time being the envoy and envoy-api dependencies point to
my forks on Github as we depend on additional functionality not yet
available in Envoy upstream.

Updated to pass "make tests"

Pushed forced updates to clean up the go style to make hound happy.

Further modularized oxy code to a new file (pkg/proxy/oxyproxy.go), made Redirect an interface that should be able to deal with all proxy types. CreateOrUpdateRedirect needs to be aware of all support types to be able to call the right factory method, but otherwise proxy.go is now completely independent of oxy code and should be reusable for Envoy.

Further modularized oxy code to a new file (pkg/proxy/oxyproxy.go), made Redirect an interface that should be able to deal with all proxy types. CreateOrUpdateRedirect needs to be aware of all support types to be able to call the right factory method, but otherwise proxy.go is now completely independent of oxy code and should be reusable for Envoy.

@manalibhutiyani This is probably exactly what you need as well for the Kafka parser. Maybe we can extract this commit and merge it earlier.

Some test cases are now successful.

Added command line option to enable Envoy integration and rebased to master.

Added a new auto_http2 feature to Envoy and rebased to master.

Access logging refined and rebased to master.

@raybejjani @tgraf Your point about using a bazel-managed dependency to Envoy (or our fork of Envoy in this case) instead of the git submodule might help with the caching problem Thomas encountered w.r.t. Envoy object files. I'll experiment with this.

@raybejjani On checking that Envoy starts: I have a follow-up PR in progress that allows the caller to wait for ACK/NACK from Envoy after redirect is created or updated. I'll make sure it also returns an error in that case if Envoy failed to start.

I wrote envoy-api/test.go as an development tool, rather than a unit- or runtime-test program and as such the output is different when it works vs. doesn't, but I'll update this after I have the ACK/NACK visible to the caller.

@jrajahalme Everything you said sounds good. My request changes was mostly for the infinite loop so don't feel locked or obliged to respond to the other comments (although you have and that's all cool too).

@aanm Ref. envoy directory vs. pkg/envoy: I'm looking at merging the envoy and envoy-api directories to envoy directory and getting rid of the subprojects. After this the envoy directory contains only C++ files, Makefile and some bazel configuration files. Not sure if it is a good idea to put these in a go-package directory?

@aanm GitHub does not let me comment on this in-line, so here this is separately:
"Isn't the mutex only being used because of line 179? (l := s.listeners[name])"
The mutex also protects against concurrent removal while we are updating the listener's policy so that we are less likely to update the policy of the listener after it has been removed.

Thanks for the reviews! I'll post an update with a rebase in a few hours.

Should we move envoy/ and submodules to pkg/envoy?

@aanm Ref. envoy directory vs. pkg/envoy: I'm looking at merging the envoy and envoy-api directories to envoy directory and getting rid of the subprojects. After this the envoy directory contains only C++ files, Makefile and some bazel configuration files. Not sure if it is a good idea to put these in a go-package directory?

@tgraf ^^^

I tried with this latest branch:
____Cloning https://github.com/jrajahalme/envoy-api.git: Resolving deltas (72 / 410)
____Cloning https://github.com/jrajahalme/envoy-api.git: Updating references (0 / 4)
____Loading package:
WARNING: /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.bzl:18:5: Fetching external dependencies....
WARNING: /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.bzl:24:5: External dep build exited with return code: 256.
WARNING: /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.bzl:25:5: .
WARNING: /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.bzl:26:5: java.io.IOException: Cannot run program "/root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy_deps/./repositories.sh" (in directory "/root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy_deps"): error=13, Permission denied.
ERROR: error loading package '': Encountered error while reading extension file 'protobuf.bzl': no such package '@protobuf_bzl//': no such package '@envoy_deps//thirdparty/protobuf': External dep build failed.
____Elapsed time: 19.590s
make[1]: *** [bazel-out/local-fastbuild/bin/envoy] Error 1

@tgraf external/envoy_deps/./repositories.sh is a symlink to a symlink to a file. Should check that those are ok and the final file has +x flag and permissions OK? Any way to do that?

@tgraf external/envoy_deps/./repositories.sh is a symlink to a symlink to a file. Should check that those are ok and the final file has +x flag and permissions OK? Any way to do that?

It is a symlink:
$ ls -l /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy_deps
/./repositories.sh
lrwxrwxrwx 1 root root 100 Nov 15 23:39 /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy_deps/./repositories.sh -> /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.sh

But the destination is not executable:
-rw-r--r-- 1 root root 1287 Nov 15 23:39 /root/.cache/bazel/_bazel_root/e3bb2978717df7858b43846d8c1242eb/external/envoy/bazel/repositories.sh

Changed to use bazel http_archive instead of git_repository to get around the permissions issue when building as root.

@tgraf @ianvernon For some reason the CI is building an old head of this PR. It is still entering (successfully) the envoy-api directory that is removed in the current head. This could also explain why the envoy build started from scratch, as the build script does "make clean", which I made to not call Basel clean a while ago, but it is still doing that in the CI builds.

runtime tests pass now on CI, trying to get the k8s tests to start.

Cleaned up and rebased with master. k8s tests vagrant box needs Bazel, otherwise should be good to go.


Replace require for load_function.

Hi @jozephbrasil, Either include method will work but this is perhaps a little more future proof so we're going to accept your change. Thanks!


✨ Adds slots for each page

Brief
In a work project, I needed a way to inject some text per page being rendered. I couldn't find an out-of-the-box solution, so i forked the repo and added this new slot capability:
<vue-pdf-embed
  :source="{
    cMapUrl: 'https://unpkg.com/pdfjs-dist/cmaps/',
    url: pdfSource,
  }"
>
<template v-slot:page="{ page }">
  The page number is {{ page }}
</template>
</vue-pdf-embed>

Now you can conditionally render something inside each page

Went ahead and made the changes requested @hrynko. I appreciate the package, its help us quickly solve a PDF embedding problem.

Hi @m4rcoperuano,
Please apply and commit a patch to resolve merge conflicts and a patch to resolve annotation/text layer issues

Hi @m4rcoperuano,
Please apply and commit a patch to resolve merge conflicts and a patch to resolve annotation/text layer issues

Please let me know if I can be of any assistance

Never mind, I did it myself so you don't have to.
Thank you for your inputs!


[Designer] Color definitions limitations and suggestion

I think the text color definitions are not very meaningful, and also I think we should be able to use HEX color codes for the color selections and not be boxed into just a handful of colors that might not work for us.

Hello @kahopkin - appreciate this feedback.
Part of the rationale behind having semantic color names rather than allowing for free form RGB color definitions is that it allows a card to be displayed with colors that adapt to the apps hosting them. Consider if instead of the good color definition a card author specified a nice dark green text color. The card might look good in their situation, but what happens when that same card is hosted in an app using a dark theme? The card could end up being rendered in such a way that the text would be difficult to read. By using semantic colors, good can be a nice dark green in light-colored hosts and perhaps a nice light green in dark-colored hosts.
Additionally, this allows hosts to have various card colors match the theme of the surrounding app, which wouldn't be possible if card authors specified arbitrary RGB colors.
@matthidinger - care to add anything here?


Split CSKG browser from benchmarks portal

So does that mean we won't be able to link from benchmark to cskg?
Say for node page from paths (edited)
Good point. These may be external links. We’ll have to figure it out.
Or the benchmark browser may have to have the CSKG browser inside it
I’ll think about how to structure the code, it will end up being two interfaces but they may share a common code base.

Currently (20200707) the benchmark Routes.tsx refers to kg pages, which use the kg Frame. Those pages will need their guts extracted so that there's no dependency from benchmark->kg, only benchmark->shared and kg->shared.

Closing this issue, will file follow-ons.


Add 0.1 refinement factor in bench

Codecov Report

Merging #223 (c1fc631) into main (a5d8734) will decrease coverage by 7.65%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #223      +/-   ##
==========================================
- Coverage   90.41%   82.77%   -7.65%
==========================================
  Files          40       40
  Lines        1095     1184      +89
==========================================
- Hits          990      980      -10
- Misses        105      204      +99

see 18 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


i enters Vim insert mode from Jupyter command mode

This addresses #70.

@wmayner I forgot that the interrupt shortcut is I,I so like vim, jupyterlab waits a while to resolve this shortcut. Raises the question if we should remap the interrupt shortcut?

I prefer using Ctrl + c as the interrupt hotkey, similar to the command line. But that's a personal preference, and I'm also hesitant to remap jupyterlab defaults. It's a shame though, since i is so fundamental to using Vim.
At least if we add the command, users can remap as they see fit. Perhaps we can just add the command for now and defer the binding to a later PR?

I just realized I was actually wrong about the original functionality: in jupyter-vim-binding, i would only enter Vim command mode. So in fact your initial suggestion was totally right if the goal is to duplicate the jupyter-vim-binding functionality, and all I need to is override the default bindings in jupyterlab.

Perhaps we could use Ctrl + I as a binding to go directly into Vim insert mode, and leave it up to users to override the I + I binding if they want. Ctrl + I doesn't seem to interfere with jupyterlab bindings.

This sounds like a good compromise to me, thanks for the suggestion. I'll merge this in now. Sometime in the next few days I'll cut a new release.


Fix error in #19

timestamp_created should be timestamp_checked, otherwise timestamp and timestamp_checked would result in the same number.

Thanks; sorry about that. I should've taken an extra pass looking over it for sure.


ipfetch: init at unstable-2022-03-14

Project description
Neofetch like tool that can lookup IPs. :earth_americas:
Metadata

homepage URL: https://github.com/trakBan/ipfetch
source URL: https://github.com/trakBan/ipfetch
license: gpl3
platforms: posix shell

I'll do this myself.


Question: Memory usage

Hello.
I have following question:
When consuming message and responding on it using context.Respond() and using IRequestClient<T,U>.Request()  for getting response i see following information in memory diagnostics:

There many objects of Newtonsoft.Json.* type.(Newtonsoft.Json.Serialization.DynamicValueProvider for example)
Consuming and responding on new types of messages increase references count of those objects.

Please, could someone explain: is this intentional behavior and why it is happening?
Steps can be reproduced by using program content from below in "Client" project of "Sample-RequestResponse" and analysing memory before and after request.
Thank you.
class Program
    {
        static void Main()
        {
            ConfigureLogger();

            // MassTransit to use Log4Net
            Log4NetLogger.Use();

            IBusControl busControl = CreateBus();

            BusHandle busHandle = busControl.Start();

            try
            {

                int n = 2;
                for (;;)
                {
                    IRequestClient<ISimpleRequest, ISimpleResponse> client = CreateRequestClient(busControl);
                    Console.Write("Enter customer id (quit exits): ");
                    string customerId = n.ToString();
                    if (customerId == "quit")
                        break;

                    ISimpleRequest request;
                    if (n % 3 != 0)
                    {
                        request = new SimpleRequest(customerId);
                    }
                    else
                    {
                        request = new SimpleRequest2(customerId);
                    }
                    // this is run as a Task to avoid weird console application issues
                    Task.Run(async () =>
                        {
                            ISimpleResponse response = await client.Request(request);

                            Console.WriteLine("Customer Name: {0}", response.CusomerName);
                        }).Wait();

                    n++;
                }

            }
            catch (Exception ex)
            {
                Console.WriteLine("Exception!!! OMG!!! {0}", ex);
            }
            finally
            {
                busHandle.Stop(TimeSpan.FromSeconds(30));
            }
        }

        static IRequestClient<ISimpleRequest, ISimpleResponse> CreateRequestClient(IBusControl busControl)
        {
            var serviceAddress = new Uri(ConfigurationManager.AppSettings["ServiceAddress"]);
            IRequestClient<ISimpleRequest, ISimpleResponse> client =
                busControl.CreateRequestClient<ISimpleRequest, ISimpleResponse>(serviceAddress, TimeSpan.FromSeconds(30));

            return client;
        }

        static IBusControl CreateBus()
        {
            return Bus.Factory.CreateUsingRabbitMq(x => x.Host(new Uri(ConfigurationManager.AppSettings["RabbitMQHost"]), h =>
            {
                h.Username("admin");
                h.Password("Programming");
            }));
        }

        static void ConfigureLogger()
        {
            const string logConfig = @"<?xml version=""1.0"" encoding=""utf-8"" ?><log4net>  <root>    <level value=""INFO"" />    <appender-ref ref=""console"" />  </root>  <appender name=""console"" type=""log4net.Appender.ColoredConsoleAppender"">    <layout type=""log4net.Layout.PatternLayout"">      <conversionPattern value=""%m%n"" />    </layout>  </appender></log4net>";

            using (var stream = new MemoryStream(Encoding.UTF8.GetBytes(logConfig)))
            {
                XmlConfigurator.Configure(stream);
            }
        }

        class SimpleRequest :
            ISimpleRequest
        {
            readonly string _customerId;
            readonly DateTime _timestamp;

            public SimpleRequest(string customerId)
            {
                _customerId = customerId;
                _timestamp = DateTime.UtcNow;
            }

            public DateTime Timestamp
            {
                get { return _timestamp; }
            }

            public string CustomerId
            {
                get { return _customerId; }
            }
        }

        class SimpleRequest2 :
            ISimpleRequest
        {
            readonly string _customerId;
            readonly DateTime _timestamp;

            public SimpleRequest2(string customerId)
            {
                _customerId = customerId;
                _timestamp = DateTime.UtcNow;
            }

            public DateTime Timestamp
            {
                get { return _timestamp; }
            }

            public string CustomerId
            {
                get { return _customerId; }
            }
        }
    }

Are you seeing memory leaks in the process that never get garbage collected, to the point that the process crashes? Or are you just seeing normal memory usage of the serialization components within JSON.NET?

Those objects are never collected by GC and consume just a little more memory for each new message type: maybe this is normal memory usage of the serialization components within JSON.NET for faster serealizing/deserializing. I dont know, so decided to ask. Process will not crash because there are just some very minor memory usage per new message type what is responded for the first time.

I'm pretty sure this is a per-type reflection and/or code-generation cache that is used to optimize the performance over time of JSON.NET. As long as it is only once per type it shouldn't be a burden on system memory.
If you agree, feel free to close this issue.

I thought about it too but was not shure. Thank you.


add source to movestart, move, moveend, zoomstart, zoom and zoomend events

It would be very useful to know when the map is moved or zoomed due to user interaction.
So here‘s a pull request which adds a 'source' property to movestart, move, moveend, zoomstart, zoom, and zoomend events.
The source is either user(.[a-z]+)? or imperative(.[a-z]+)?, depending on how was triggered the event.
This pull request is mostly based on this one #5247 which is three years old and was never merged for some unknown reason.

As I said before, I'm not convinced by this approach. Something in the back of my brain tells me that there's gonna be some edge case where an event handler calls another event handler and things go inconsistent.
This would be better with some unit tests, specifically in the parts where we test user interaction via touch and mouse drag, e.g. https://github.com/Leaflet/Leaflet/issues/2934#issuecomment-512766397. The code in the PR looks good, but unfortunately doesn't give me any assurance that it'll work.

Wait before merging this pull request, I want to refactor these changes, instead of adding a parameter to a lot of methods, I'm going to use the parameter options. This way all the plugins which redefine methods of Leaflet will continue to work.

Any update on this ?

I've merged it on my fork, and it works fine.
If there is any other approach how to detect user, please let me know

Any update? Would be nice to have this feature.

Any updates on this ? Would be great !

And all this should be covered by tests..

Any update on this? Very interested and happy to investigate, wasn't sure if this is just being disregarded now in favour of other methods of tracking event source?

I need this feature as well. I've seen posts more than 10 years old from people asking for this, and I feel this is a rather essential.

What are the usecases / why do you need the source?

For my purpose – some map moves occur due to Leaflet features, like ensuring that a marker popup is in view. Others occur due to user input.
Being able to determine which is which is very helpful. For example in my use-case we only want to load new map pins when the user moved the map, not due to an automated move.