Snyk parser enhancements

This PR addresses the following features:

Support for Snyk JSON reports generated with the --all-projects (e.g: Maven multi module projects).

Added the following missing fields for each Finding generated from a report:

CVSS3
Severity justification
Mitigation
References

Minor visual changes:

Added link to the Snyk Vulnerability Database for the referenced Snyk IDs.
Added bold format to the details section within the issue description.

Hi, Can you provide sample scans for these new features? Can you set component_name and component_version fields?

Hi, Can you provide sample scans for these new features? Can you set component_name and component_version fields?

Hi, Can you provide sample scans for these new features? Can you set component_name and component_version fields?

Hi @valentijnscholten , I have generated two sample files you can find it here
What do you mean by set component_name and component_version fields?
I think the value that is currently being assigned may be correct.
Regards.

Hi, Can you provide sample scans for these new features? Can you set component_name and component_version fields?

Hi @valentijnscholten , I have generated two sample files you can find it here
What do you mean by set component_name and component_version fields?
I think the value that is currently being assigned may be correct.
Regards.

I meant can you extend the unit tests to use samples with the new features.
And sorry, didn't notice that component_name/version are already set correctly :-)

I meant can you extend the unit tests to use samples with the new features.
And sorry, didn't notice that component_name/version are already set correctly :-)

There is one last thing that could be done.
cwe attribute of findings are integer. depending on the data the parser return an integer or a string.
Could you improve a little bit your pull request to manage this?
Some conversion in integer is required in this part I think:
https://github.com/DefectDojo/django-DefectDojo/blob/master/dojo/tools/snyk/parser.py#L65-L73

Hi @damiencarol ,
Made a refactor for the CWE parsing addressing the following points:

Parse CWE as an integer
Change JSON property checks, as the report will always contain an "identifiers" object. "CVE" and "CWE" will be lists even if they are empty.

Regards

There is one last thing that could be done.
cwe attribute of findings are integer. depending on the data the parser return an integer or a string.
Could you improve a little bit your pull request to manage this?
Some conversion in integer is required in this part I think:
https://github.com/DefectDojo/django-DefectDojo/blob/master/dojo/tools/snyk/parser.py#L65-L73

Hi @damiencarol ,
Made a refactor for the CWE parsing addressing the following points:

Parse CWE as an integer
Change JSON property checks, as the report will always contain an "identifiers" object. "CVE" and "CWE" will be lists even if they are empty.

Regards


Sorting

Checklist

[X] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved
I'd like to sort Users as described here: https://auth0.com/docs/api/management/v2#!/Users/get_users
Describe the ideal solution
Having a func Sort(s string) RequestOption { ... } function similar to Query in management/management_request.go
Alternatives and current workarounds
No response
Additional context
No response

I got it working by adding a  management.Parameter("sort", "email") as an additional parameter to User.List. But would be awesome to have a function for that similar to func Page(page int) RequestOption

Hey @vendelin8 I think supporting a Sort request option would make sense given we have other helpers like that, happy to accept a PR if you'd be interested but otherwise we'll factor this into the v1 release we have planned

Hi @ewanharris , I wanted to take a shot at contributing and created a fork to add a helper - https://github.com/ssudaraka/go-auth0/blob/a7c6db764bdc53d2336ed3b6eb55e16fbb99f00a/management/management_request.go#L295-L302
However, I need some guidance on how to locally test my change with the local repo. If you have some spare time, can you share some details on that? I'll make sure to add that to "How to contribute" file also. Thank you!

It's great to see the interest in making a contribution so thank you @ssudaraka!
For this test I would add something similar to the existing options like TestOptionParameter, that should then be testable using make test (no need for any configuring of a .env file). There's some instructions on running the tests in the contributing document but please feel free to edit them if there's some more information that would be helpful


Docs is offline

The docs are still offline. Looks like dreamhost reset the CNAME to some weird google host. The correct value should be hosting.gitbook.com.

We need to get in touch with dreamhost about this as this field is not editable.

I updated the CMAKE settings, contacted customer support and refreshed the DNS.  Might take up to 12 hours...

It's back.


webdav server

For OS X fs mounting.  Use same interfaces as FUSE, probably.

golang.org/x/net/webdav is shaping up nicely (still missing some bits, like PROPPATCH, but it's getting there) so this might be a good time to revive this.
Do we want this as a Camlistore app, or baked in Camlistore proper? The only benefit of the latter option I see is piggybacking on Camlistore's authentication.

Can't we reuse (and extend if needed) what's in pkg/app/app.go to do the auth for webdav too?

Yes, I think that would be the best approach.
On 25 Mar 2015 18:43, "mpl"<EMAIL_ADDRESS>wrote:

Can't we reuse (and extend if needed) what's in pkg/app/app.go to do the
auth for webdav too?
—
Reply to this email directly or view it on GitHub
https://github.com/camlistore/camlistore/issues/38#issuecomment-86088197
.

maybe we could add a Camlistore plugin to https://github.com/mattn/davfs :-)

cf #146


Breaking change in output bundle from v2.13.0 to v2.14.0

Be sure to search for your issue before opening a new one.
Current Behavior
This is very hard for me to identify but I will try to do my best. We're using react-player for a React app that powers a Meta Quest game called GOLF+ and the UIs that are not made in Unity. Long story short, we were on version 2.12.0 and tried to upgrade to 2.16.0 recently and all of our youtube videos broke. I went through one by one version update and pinpointed it to the 2.13.0 update being the last one that worked properly. 2.14.0 starts the breaking change. I'll do my best to describe the issue.
Essentially, when looking at the output bundle, you can search for the term YouTube- and see that in v2.13.0 it does not appear in the output JS. However, if you run that same search in v2.14.0 and onward, you will see the following bit of code:

This in turn, on the headset, results in a broken build because it cannot find that import, thus leaving us with no choice but to stay on an older version of this library. I'm hoping that this may trigger something in the maintainer's mind about a possible change that occurred in that update which would have caused this issue. As far as I can tell, its this line that is creating that import, but not sure what would have changed in that version since that file has not been updated for 2+ years and v2.14.0 was released in December of 2023. I'm not familiar with the internals of the package so again, i'm hoping this brings something to mind which may be causing this.
Expected Behavior
The build does not include that import and everything works as it did in v2.13.0.
Steps to Reproduce

Environment

URL attempting to play:
Browser:
Operating system:
jsFiddle example: https://jsfiddle.net/sv5x3ug1

Other Information

Quick follow up on this. When I build our project (using Vite) on v2.12.0, this is what the output bundle folder looks like:

When building with v2.16.0, this is the output bundle folder:

So, it looks like all the different player types don't get included in the main bundle JS, which is what I'd expect (along with ALL other npm deps in our project), rather they are being put into their own files alongside our bundle code. Because of the way our build for a Meta Quest works, we have to inline the bundled JS file into the HTML, so these extra player files are not being accounted for.

Dug deeper into this and I solved it by using https://www.npmjs.com/package/vite-plugin-singlefile to inline my files instead of the manual process i was using so closing this. Apologies for the noise.


buildings are being assigned to multiple parcels in different jurisdictions

Buildings can only be assigned to one parcel, but that code only works intra-jurisdiction, so we need a mechanism to make this worth across jurisdictions too.

Fixed https://github.com/oaklandanalytics/cutting_board/commit/70655122b10c4ae62322a5d6b7e816ff886b8f4e


Remove zomby connections

There appears to be an obscure edge case where an endpoint is removed, but the connection stays around. Finding and fixing this bug is one thing, but fixing existing dialogues broken as a result of this is another. This ticket is for fixing existing dialogues by removing these zomby connections.

@SteveBarnett Ready for review.
Ideally, this "fix" should happen before views use the erroneous model data, but we currently don't have the tools we need to do this: we would need a way of searching through all endpoints in a diagram model, and at the moment, we only have the tools for doing this in views.

:+1: for getting a quick fix out, but it would be great to go for a more complete solution, if we have the time.


Improved input system

Some resources

https://developer.android.com/ndk/reference/group/input#ainputevent_getsource
https://developer.android.com/training/game-controllers/controller-input
https://www.glfw.org/docs/latest/input_guide.html#joystick


problem in first step

i am just a beginner so sorry if i am asking a very basic question..
i have my training and test data sets saved in csv format....in your first step it says run preprocess.py on training and test dataset...how to do that? does that mean i have to specify the path of csv files somewhere within the code(preprocess.py)? because i am not able to find that,,please help..thank you:))

It is clearly written in the Readme. Run as python preprocess.py <csv_file_name>.


Replace AccumulationLRFinder with parameter in LRFinder

Since LRFinder was just a special case of AccumulationLRFinder with accumulation_steps=1 this PR replaces the _train_batch method of LRFinder with the _train_batch in AccumulationLRFinder and accumulation_steps is a new parameter of range_test.
@NaleRaphael and @rsomani95, can you guys give me some feedback on this change? I think the usage is still clear and this way there's less code duplication.

It looks good to me!
Though this form of implementation was considered before, I chose to make a new class AccumulationLRFinder to minimize changes on the original implementation. But it seems more convenient to set the argument accumulation_steps in this revision.


Fix dashboard modal buttons

Codecov Report

Merging #1317 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1317   +/-   ##
=======================================
  Coverage   70.37%   70.37%
=======================================
  Files         117      117
  Lines        6158     6158
  Branches      786      786
=======================================
  Hits         4334     4334
  Misses       1661     1661
  Partials      163      163

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86d0f84...3b28b9d. Read the comment docs.

Hi @Satloff, thanks for the contribution!
Could you provide brief description what you've fixed in this PR, or preferably some before/after screenshots, if changing the UI?

The difference is in hover state.

Blue one after changes provided by @Satloff, the right one is current state.
It's related to Dashboard inconsistences  #1310, as in most of the places we are using blue hover version.

I think what this PR does is changing hover state of buttons in modals in the first place. In our modals we have flat buttons that don't change the background color on hover, which is consistent with what MaterializeCSS documentation says. But all of the other buttons (not in modals) do change the background on hover. I'm not sure what is correct, but I think we once have a discussion about it and this difference is intentional.
The screenshot that @Pacu2 posted shows a different problem - in our stylesheets we still have teal color hardcoded, which used to be the secondary color. @dominik-zeglen Could you take care of that in your current PR?

Are we sure that borderless buttons should change their background color on hover? I think this does not happen often in material design applications.

My mistake for not providing screenshots. My intention was to continue the standard styling used throughout the rest of the dashboard with respect to action buttons. Currently, there is no effect on button hover in select modals, which makes the user flow confusing.
Without the change, with mouse over:

With the change, with mouse over:

I think the standard is (all that apply):

for raised buttons raise the Z offset (layer height)
for bordered buttons change background color
for borderless buttons change text color

Shouldn't table buttons (borderless flat) also apply to this standard? This seems to go against 80c03cb

@Satloff Yes, I believe they should.


Error Target @io_bazel_rules_docker//platforms:image_transition was referenced as a platform, but does not provide PlatformInfo

https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3321#018ab594-28c8-4eee-ab66-be1399583a81
Platform : Ubuntu Bazel Remote Cache (:ubuntu: 18.04, 20.04)
Logs:
RROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/c452177aff3ea7c8ea21ee9042ebc31a/external/io_bazel_rules_docker/platforms/BUILD:78:9: in constraint_values attribute of platform rule @io_bazel_rules_docker//platforms:image_transition: '@io_bazel_rules_docker//platforms:image_transition_cpu' does not have mandatory providers: 'ConstraintValueInfo'
(02:32:09) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/c452177aff3ea7c8ea21ee9042ebc31a/external/io_bazel_rules_docker/platforms/BUILD:78:9: in constraint_values attribute of platform rule @io_bazel_rules_docker//platforms:image_transition: '@io_bazel_rules_docker//platforms:image_transition_os' does not have mandatory providers: 'ConstraintValueInfo'
(02:32:09) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/c452177aff3ea7c8ea21ee9042ebc31a/external/io_bazel_rules_docker/platforms/BUILD:78:9: Analysis of target '@io_bazel_rules_docker//platforms:image_transition' failed
(02:32:09) ERROR: /var/lib/buildkite-agent/builds/bk-docker-gdxt/bazel-downstream-projects/bazel-remote/BUILD.bazel:134:16: Target @io_bazel_rules_docker//platforms:image_transition was referenced as a platform, but does not provide PlatformInfo
(02:32:09) ERROR: Analysis of target '//:bazel-remote-image' failed; build aborted

Steps:
git clone -v https://github.com/buchgr/bazel-remote.git
git reset 2bcc2f59e111f71b4de4d84013f8e93a1b981872 --hard
export USE_BAZEL_VERSION=6446607f6eb2ce2b1ff5e5d8d429456dcdfec01f
bazel build //:bazel-remote //:bazel-remote-image

Culprit Found: 87fb4620c6edd0e525d4621ecdca4bd47d69484c
CC Greenteam @comius

cc @katre
The culprit seems likely cause.

This is the same as https://github.com/bazelbuild/bazel-buildfarm/issues/1446. I guess I need to file an issue against rules_docker.

Filed https://github.com/bazelbuild/rules_docker/issues/2275, in the meantime using --@io_bazel_rules_docker//transitions:enable=false to disable the problematic behavior seems to work (but means that the image's architecture attribute is ignored, I don't know if the usage in this project is impacted).

Bazel remote CI is green now. Hence we are closing this issue now.

How to resolve this issue I am unable to find the route map. Can anyone help me what all things I have to add in my project

@jayeshkotia: https://github.com/bazelbuild/rules_docker is archived and unmaintained, they suggest migrating to rules_oci.


Mention NixOS packaging in readme

Up to you to decide if this is readme-worthy, I won't mind either way!
https://github.com/NixOS/nixpkgs/pull/121130

Cool, thanks! Happy to include this in the readme, I've suggested a slightly different wording to make it clearer the libusb requirement isn't related to NixOS.
I'll try and remember to check the Cargo.lock is up to date before the next release... I suppose it's no help doing a new release just for that now?

Thanks for the clarifying change!
Actually a new release now would be good actually, I can drop the lockfile patch (so that automatic updates happen cleanly) and can set it up so that the udev rules are incorporated into NixOS without having to do it manually.

Thanks!

https://github.com/NixOS/nixpkgs/pull/121275
On Fri, Apr 30, 2021 at 8:39 PM Adam Greig @.***> wrote:

I've published 0.1.6 with the new udev file and updated Cargo.lock.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adamgreig/ecpdap/pull/12#issuecomment-830065629, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXHTLTDFHJ526IZGAXDTLKQHLANCNFSM433REHSQ
.


How do I install <sys/ipc.h> and <sys/msg.h>

When asking a question please also include where you looked for an answer (so we can update the documentation if needed).

I have already install vcpkg and intergrated it in my vscode editor , but when i search for those two C libraries I get nothing but this link to report any issues.

Hi @gtsompanoglou
Thanks for posting this issue.
Seems <sys/ipc.h> and <sys/msg.h> are the files in GNU C library, which doesn't exist in vcpkg now. So you cannot install it via vcpkg.
You can open a new issue here to post your request if you want to add this port in vcpkg.


Unable to connect to hardhat, getting RPC Error

Is there an existing issue for this?

 Received:  {code: -32602, messa

ge: "Expected null or array with at least one valid string HTTPS URL 'blockExplorerUrl'. Received: "}

After disconnecting the wallet, its showing this, and the same error in the console.

Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response
Do let me know if this is a replicate.

Thanks for reporting. This issue is temporarily closed due to lack of information. Please provide a minimal reproducible example and reopen this issue. Other information is also helpful, like framework (e.g. Next.js), browser, etc.

Probably not an issue with wagmi, my bad.
rainbowkit is throwing this error.


Fixed #35137 -- Optimized UI of collapsible code line elements in technical 500 template

This PR addresses issue #35137
Introduced changes:

Changed collapsible error code line markup from div to HTML5 details with summary
Changed appearance of those elements by adding a border and prepending a collapse icon (+/-) with CSS
Added javascript to allow having native toggle behavior of details tag without "pushing" the opened summary on top
Made elements fully tabbable by adding tabindex and some javascript to keep focus on opened/closed elements
UI changes only have effect if not in email mode (is_email=False) to keep email layout simple (no toggle indication)
Reduced clickable area of element "Local vars" to it's inner content by adding CSS attribute width: fit-content

Please let me know what you think of these changes. Any help or opinion is very much appreciated.

I checked the regression tests and adjusted them accordingly:
In test_reporting_of_nested_exceptions one more element with the innermost exception message ("final exception") was found. That's because the message is passed as the frame's context_line attribute into ExceptionReporter where it gets rendered within the newly added ol tag with the class "context-summary-placeholder".
In the other failed tests no div tag with the class "context" could be found as it is a details tag now (obviously).


Wrong tab indentation with XML linter

When using the XML linter and tab indentation one gets wrong indentation handling.
Editorconfig:
[*.{xml}]
indent_style = tab
indent_size = tab
tab_width = 4

The result is, that the Editorconfig Maven Plugin demands for each indentation level 4 tabs, for example for 2 indentations then 8 tabs. This is also the case when setting indent_size=4 and omitting tab_width.
What works, but this is not conforming to Editorconfig:
[*.{xml}]
indent_style = tab
indent_size = 1
tab_width = 4

Then the plugin uses 1 tab for indentation. But IDEs like Intellij then set indent size to 1 character and ignore the tab width.
The spec on editorconfig.org states:

indent_style: set to tab or space to use hard tabs or soft tabs respectively.
indent_size: a whole number defining the number of columns used for each indentation level and the width of soft tabs (when supported). When set to tab, the value of tab_width (if specified) will be used.
tab_width: a whole number defining the number of columns used to represent a tab character. This defaults to the value of indent_size and doesn't usually need to be specified

Additionally: the text linter works correctly with the settings above, only the XML linter does not work.

Thanks for the report, @akersch. Would you mind writing a new test case in XmlLinterTest that reproduces this issue?

The fix is merged in the master of the linters project. I'd release the linters and maven plugin unless you have more reports/fixes?

Fixed via https://github.com/ec4j/editorconfig-linters/pull/21

The fix is merged in the master of the linters project. I'd release the linters and maven plugin unless you have more reports/fixes?

Currently, I do not have more reports.
Thank you for the fast fix!

Version 0.1.1 of editorconfig-maven-plugin was released.


Firmware trim motors

vendors of cheap dc motor often produce motors with slightly different performance. this changes allows to enable dynamic trimming. When active the performance is monitored on straight runs to mitigate the issue

Here are some thoughts

The trimming also makes sense when going in reverse. So any time ctrl_left==ctrl_right
To me ctrl_left_trimmed and ctrl_right_trimmed as variable names makes more sense
Probably not necessary to send back the trimmed values or even the trim value. The Android app doesn't really care about the specifics of the car, it just expects it to do the right thing.

Here are some thoughts

The trimming also makes sense when going in reverse. So any time ctrl_left==ctrl_right
To me ctrl_left_trimmed and ctrl_right_trimmed as variable names makes more sense
Probably not necessary to send back the trimmed values or even the trim value. The Android app doesn't really care about the specifics of the car, it just expects it to do the right thing.

In addition:

Currently there can be overflow. If ctrl_left and ctrl_right are already at the max (255), trim/2 is added to one side. This result in an invalid ctrl signal. It is probably better to subtract the absolute trim value from one side if the controls are positive and add it to one side if they are negative.
Right now it will only trim when going straight. How about comparing the ratio between ctrl_left/ctrl_right and speed_left/speed_right. Then trimming can always be active

In addition:

Currently there can be overflow. If ctrl_left and ctrl_right are already at the max (255), trim/2 is added to one side. This result in an invalid ctrl signal. It is probably better to subtract the absolute trim value from one side if the controls are positive and add it to one side if they are negative.
Right now it will only trim when going straight. How about comparing the ratio between ctrl_left/ctrl_right and speed_left/speed_right. Then trimming can always be active

when driving in circles trimming probably is to difficult there it is only active when driving straight. I have to rethink about the overflow. it didn't happen to me but you could be right. I'll probably update the code for it

when driving in circles trimming probably is to difficult there it is only active when driving straight. I have to rethink about the overflow. it didn't happen to me but you could be right. I'll probably update the code for it

pls review

pls review

@vkuehn Sorry for the delay. I did test it and encountered some issues. For me it did not compensate properly when going straight. And when going backwards, the car behaves very strangely for some reason. How well did the new firmware work in your tests?

@vkuehn Sorry for the delay. I did test it and encountered some issues. For me it did not compensate properly when going straight. And when going backwards, the car behaves very strangely for some reason. How well did the new firmware work in your tests?

Strange habits was what I saw with the firmware that is why I started that change.
I have to admit I still did struggle running the OpenBot around as of a lack of a properly connected controller.
Through an USB hub and a cable I did use a ps3 controller. PS4 over Bluetooth but I had to give that one back..
Mainly I did test running forward.
Compensation now is just finding a middle value between the faster and the slower wheel. It is not a complex normalization as it is running on the Arduino.
@thias15 I'll think again how to make that one better. Still difficult to understand why there are sometimes these strange irritations.

Strange habits was what I saw with the firmware that is why I started that change.
I have to admit I still did struggle running the OpenBot around as of a lack of a properly connected controller.
Through an USB hub and a cable I did use a ps3 controller. PS4 over Bluetooth but I had to give that one back..
Mainly I did test running forward.
Compensation now is just finding a middle value between the faster and the slower wheel. It is not a complex normalization as it is running on the Arduino.
@thias15 I'll think again how to make that one better. Still difficult to understand why there are sometimes these strange irritations.

Sorry took me ages to find a solution to test the firmware without a mobile phone as there is no web interface with direct debugging in OpenBot right now. Not sure why python fails to talk reliable to that firmware so did it with node red also. However it turns out that all odd behavior is coming from small problems with the hardware. Like not properly soldered cables or bad tire position on these cheap motors


cache.bolt isn't in config path by default

It looks like this was supposed to be fixed in #359 by @felixbuenemann.
This doesn't seem to be the case however.
I'm currently running plexdrive 5.1.0.r32.g09c8ee8 (09c8ee8) on linux.
When starting up plexdrive with a custom config folder it creates a fresh cache.bolt in ~/.plexdrive.
Parsed config:
user@host:~$ plexdrive -c .plexdrive-foo -v 3 mount .plexdrive
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : verbosity            : DEBUG
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : root-node-id         : root
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : drive-id             :
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : config               : .plexdrive-foo
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : cache-file           : /home/user/.plexdrive/cache.bolt
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : chunk-size           : 10M
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : chunk-load-threads   : 3
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : chunk-check-threads  : 3
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : chunk-load-ahead     : 5
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : max-chunks           : 12
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : refresh-interval     : 1m0s
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : fuse-options         :
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : UID                  : 1000
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : GID                  : 1000
[PLEXDRIVE] [2021-02-15 22:59] DEBUG  : umask                : ----------

I believe the reason for this might be that when argConfigPath is read in https://github.com/plexdrive/plexdrive/blob/09c8ee8f5466d2c65cac395c428389b413b0bd6b/main.go#L51 it still contains the default value as the flags were not parsed yet, which only happens at the end of the flag definitions in https://github.com/plexdrive/plexdrive/blob/09c8ee8f5466d2c65cac395c428389b413b0bd6b/main.go#L64
I'm not sure what would be the best approach here, it doesn't look like you could just parse flags twice as that breaks help.
Trying to parse the flags twice results in the first parse to return --help output and exiting.
Upstream code comments also suggest that this would not be supported, at least here:
https://github.com/ogier/pflag/blob/45c278ab3607870051a2ea9040bb85fcb8557481/flag.go#L582-L583
Ignoring the --help issue, it would however fix the intended configuration:
./plexdrive -c ~/.plexdrive-test -v 3 mount ~/mnt
[PLEXDRIVE] [2021-02-16 00:10] DEBUG  : verbosity            : DEBUG
[PLEXDRIVE] [2021-02-16 00:10] DEBUG  : root-node-id         : root
[PLEXDRIVE] [2021-02-16 00:10] DEBUG  : drive-id             :
[PLEXDRIVE] [2021-02-16 00:10] DEBUG  : config               : /home/user/.plexdrive-test
[PLEXDRIVE] [2021-02-16 00:10] DEBUG  : cache-file           : /home/user/.plexdrive-test/cache.bolt

Looking at the code (though I'm not that familiar with golang) it doesn't seem to easily support parsing flags twice.
One option may be to check after flags parsing if the config value is changed, but this flags lib doesn't appear to support checking if a flag was set or is just default, see also https://github.com/ogier/pflag/blob/73e519546fc0bce0c395610afcf6aa4e5aec88eb/flag.go#L142-L148
Alternatively, https://github.com/spf13/pflag is an actively maintained fork of ogier's pflag, and he already in 2018 suggested to switch to that fork.
In this fork it looks like it can be determined whether the flag was passed by the user by checking for Flag.Changed:
https://github.com/spf13/pflag/blob/85dd5c8bc61cfa382fecd072378089d4e856579d/flag.go#L177
There's also a discussion about this in https://github.com/spf13/pflag/issues/293
The only downside I can see with this approach would be that supplying -c to --help would no longer update the cache.bolt default location, but I think that is negligible, although the help text should be adjusted a bit to reflect that this defaults to sit inside the config directory.

Sounds reasonable. Can you come up with a PR?

hi, yes, until you call flag.Parse() argConfigPath will keep its default value.

OK, fixed in #407.

Released 5.2.1 with the bugfix.


added svelte frontend to the framework list

Svelte performed even better than all Rust frameworks, as it pre-complies the frontend code to javascript at compile time and does not use virtual dom like most of the other frameworks.
Concept of making the compiler to do more than run time code is similar to Rust.

The benchmark code is flawed, I need to redo everything.


[WIP] Address Dictionary query generation

Addresses #459
There are some dramatic changes in this.
Applying fixes for the IDictionary<,>.ContainsKey('tkey) and ICollection<KVP<,>>.Contains(KVP<,>) cases was easy enough because those fit into the existing method-call based plugin architecture. There was a wrinkle in that the operator that I want to use in postgres is ?, which is already used by the WhereFragment expansion, so I also took the opportunity to rewrite the token replacement with a more distinctive and less-likely-to-be-used-already :?: symbol.  This is entirely changeable :)
The drastic thing was adding in a pluggable IBinaryExpressionParser interface.  This was required so that I could easily get at cases where we're indexing into a dictionary on the right or left sides to pull out the keys and values to construct the comparison dictionary.  As you'd expect a ton of things broke right off the bat, so I spent some time tweaking the Matches condition on the SimplePropertyBinaryExpressionParser. Please  please please please please please sanity check me on that.  The tests pass on my local box now but there's no way they're exhaustive in this circumstance.
Should we add a publicly-facing extension point for IBinaryExpressionParser instances like there are for IMethodCallParser instances?
I'd also like to add some more tests actually storing and querying for data based on these dictionaries before I take the [WIP] off of this.
Also, thoughts about generic dictionary access?  I think it's safe to say that the most extreme we could go is IDictionary<string, TValue>, because json maps must have string keys, so is that worth going ahead and doing here?
Also, I want to buff out the binary parsing some more to accept more than dict["key"] == "value".

Oh man, how upset w/ me would you be if I asked you to solve the "?" problem a different way? Leave "?" substitution the way that it was, and maybe use custom IWhereFragment's for the places where you need that operator? The question mark thing is a common usage and I'd prefer to keep it.
And would you also mind rebasing this on master?

I'm actually in the middle of a rebase (kinda scary looking, with csproj changes :)
I could also do a custom WhereFragment, easy enough to revert that commit. No hurt feelings at all, that's why the [WIP]!

@baronfel Actually, @CoreyKaylor is in the process of removing all the csproj files and putting us squarely on project.json. You might have a better time waiting for that.
A way we could maybe do this is have the substitution wildcard not be hardcoded inside of WhereFragment. Keep "?" as the default, but let you override that on an individual WhereFragment?

Sounds like I'll take a breather then and wait for the csproj churn to finish :D
I can do a separate PR for the configurable WhereFragment as a smaller chunk while I'm waiting for all that to settle.

Already in master.

Thanks, rebasing and making the WhereFragment configurable.

Looks like quite a few failing tests on the build server for this branch.
http://build.fubu-project.org/viewLog.html?buildId=47864&tab=buildResultsDiv&buildTypeId=Marten_Master&guest=1

Oh that's expected. I've been having trouble running all the tests successfully on my machine (my poor docker Postgres instance seems to be getting swamped), but I'm still in the process of cleaning things up on my end.

Just making sure we weren't the ones dropping the ball on getting this taken in. :smile:

I'm going to reel this back a bit and skip doing the dict[key] == value pattern right now, because that's a TON of extra work around making sure that we flatten/resolve the left and/or right expressions correctly to try and pull the value out of them to construct the json dictionary correctly.  So just looking at the Contains(KVP) and ContainsKey(K) methods right now.

Ok, I removed the [WIP] on this PR.  We now handle ICollection<KeyValuePair<string,T>>.Contains(KeyValuePair<string,T>> and IDictionary<string,T>.ContainsKey(string) cases generically, and optionally have the ability to set the NpgsqlDbType on a sql parameter, which was necessary when using the @> operator to check for the presence of a key-value pair in a jsonb object.   Separate PRs can address the dictionary index question, because that junk is HAIRY!

Thanks


Convert lab2 to use JS modules

The primary reason for this change is to make it easier for the labs to share code. In a subsequent PR, for example,
I plan to import the request function from lab1 into other labs. A second benefit is that this enables easier unittesting of the modularized code.
An ancillary benefit is that this changes the code to be more idiomatic modern JavaScript, from which readers can benefit.
I plan to convert the other labs as well, this is just the first PR. I'm sending it now to make sure we're in agreement about the
approach.

This is great. The compiler change is small. I imagine eventually rt-module.js will just be the normal version of rt.js, right? My main concern is whether this requires changes to the code that are unnatural in Python.
The socket change—that's because otherwise socket isn't defined? We might be able to get around that by collecting all the imports (they are already collected, actually, in IMPORTS in the compiler) and adding a JS import for them from rt-module.js.
As for turning constants into variables—is it not possible to create module globals that are settable from elsewhere?
I would rather make the compiler a little more complex (readers don't read the compiler!) rather than mangle the Python code.  So for example, we could have the compiler write out a "change_constant" function which changes the value of a given constant, if scoping is a problem.

This is great. The compiler change is small. I imagine eventually rt-module.js will just be the normal version of rt.js, right?

Yes.

The socket change—that's because otherwise socket isn't defined? We might be able to get around that by collecting all the imports (they are already collected, actually, in IMPORTS in the compiler) and adding a JS import for them from rt-module.js.

I fixed it by factoring those objects into a named, external js module source in the latest PR revision. (You can't export symbols from an inline module script.)

As for turning constants into variables—is it not possible to create module globals that are settable from elsewhere?

No. Global variables are always const when exported. IMO the new code is just as readable anyway.

LGTY now?

So here's why I'm concerned about the constants—we grow more of them as the chapters roll on. In chapter 3, SCROLL_STEP is added; I know in chapter 7 we add CHROME_PX. It's going to look crazy to add more and more of these parameters over time, and readers are not going to enjoy having to thread the variables through, either.
What about modifying the compiler to put all global constants inside an object? So instead of HSTEP, you'd refer to constants.HSTEP, and we could mutate that? I don't think this will be too hard.

What about modifying the compiler to put all global constants inside an object? So instead of HSTEP, you'd refer to constants.HSTEP, and we could mutate that? I don't think this will be too hard.

I could do that, or wrap the objects in a new Config object that is passed as a constructor argument to Browser. I don't have a strong opinion, so unless you suggest otherwise I'll do what you suggested.

Let's just do an ugly global object. We can do this entirely in the compiler: it should output an export const constants = {};, and then when a variable is compiled (in compile_expr) it needs to look up whether that variable is bound in the module context. The best way to do that is to add a method to Context objects that recurses. Context objects have a string type field and at the top level it is (I think) "module", so we can check against that.

Done.


Missing ID in VectorStores

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Example code:
import { Chroma } from "@langchain/community/vectorstores/chroma";
import { OpenAIEmbeddings } from "@langchain/openai";

const embeddings = new OpenAIEmbeddings({
  model: "text-embedding-3-small",
});

const vectorStore = new Chroma(embeddings, {
  collectionName: "a-test-collection",
  collectionMetadata: {
    "hnsw:space": "cosine",
  },
});

const document1 = {
  pageContent: "The powerhouse of the cell is the mitochondria",
  metadata: { source: "https://example.com" },
};

const documents = [document1];
await vectorStore.addDocuments(documents, { ids: ["1"] });
const similaritySearchResults = await vectorStore.similaritySearch("pwoerhouse of the cell");

console.log(similaritySearchResults);

Error Message and Stack Trace (if applicable)
[
  Document {
    pageContent: 'The powerhouse of the cell is the mitochondria',
    metadata: { source: 'https://example.com' },
    id: undefined
  }
]

Description
The same issue as shown in Python.
There is already pull request here that fixes one of the vector. But the issue occurs in other vectorstores.
Example code fix in Chroma db
libs/langchain-community/src/vectorstores/chroma.ts line:351:
            ...
            results.push([
                new Document({
                    pageContent: firstDocuments?.[i] ?? "",
                    metadata,
                }),
                firstDistances[i],
            ]);

to
            results.push([
                new Document({
                    pageContent: firstDocuments?.[i] ?? "",
                    metadata,
                    id: firstIds[i],
                }),
                firstDistances[i],
            ]);

If it's possible we would like to perform same solution to other vectorstores.
System Info
dependencies:
@langchain/openai: >=0.1.0 <0.4.0        jsonpointer: ^5.0.1                      uuid: ^10.0.0
@langchain/textsplitters: >=0.0.0 <0.2.0 langsmith: ^0.1.56-rc.1                  yaml: ^2.2.1
js-tiktoken: ^1.0.12                     openapi-types: ^12.1.3                   zod-to-json-schema: ^3.22.3
js-yaml: ^4.1.0                          p-retry: 4                               zod: ^3.22.4

I've been scratching my head trying to figure out why documents all said id: undefined despite following the guide. I need it to be able to delete the document. I hope this gets fixed soon.


[DDW-173] - Button should be disabled when there is nothing to submit

This PR disables button on forms if there is nothing to be submitted (if the input fields are empty)
Screenshots

Testing Checklist

Slack QA thread
[ ] Test forms on: change password dialog, set password dialog, create wallet dialog & generate new address form

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR has default-sized Daedalus window screenshots or animated GIFs of important UI changes:

[ ] In English
[ ] In Japanese

[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

I'd say that button should be active when there is no blocking errors on the screen.
cc @nikolaglumac

same here, but this happened after the first submission. So I'd think that button should be blocked till I change the password to a new one.
BTW is it possible to color first input borders in red in this case? As it would be easier to recognize where error is

same here

@yakovkaravelov @tomothespian please review this PR 🙏

I'd say that button should be active when there is no blocking errors on the screen.
cc @nikolaglumac

Done

same here

Done

same here, but this happened after the first submission. So I'd think that button should be blocked till I change the password to a new one.
BTW is it possible to color first input borders in red in this case? As it would be easier to recognize where error is

Done

Hi @DeeJayElly. For the password change screen the button blocking logic is working correctly but the border is not highlighted red as suggested by @a-rukin "BTW is it possible to color first input borders in red in this case? As it would be easier to recognize where error is". Do you plan on making this enhancement

@DeeJayElly Changes you made are good now but I agree with @nikolaglumac , it is ugly. It would be awesome if you can check the documentation and improve that.

Hi @DeeJayElly. For the password change screen the button blocking logic is working correctly but the border is not highlighted red as suggested by @a-rukin "BTW is it possible to color first input borders in red in this case? As it would be easier to recognize where error is". Do you plan on making this enhancement ?

@ManusMcCole is button disabled there?

For me it's not. But I think it should be

it was fixed previously, but now it's not... strange
it's even more strange... this field is opposite in states:

initially active
start typing disables button
button is not clickable while text is there
only "Enter" submits the field

@DeeJayElly please fix eslint issues

When changing passwords when a user has not yet entered current password the save button has not been disabled. See screenshot below
.

Only after the user clicks the save button which should at that moment be disabled the "incorrect wallet "password" error message is displayed and should have as mentioned previously a red outline to highlight which box is incorrect as mentioned before

Also on the create wallet screen there is an issue where the button becomes active again before the user has entered the repeated spending password

Also important to note that on Change Password screen that one password input only is enough to make the button active again

You are correct @a-rukin i think it should the button should be disabled there.When changing passwords when a user has not yet entered current password the save button has not been disabled. See screenshot below
.

Please recheck it now, @ManusMcCole

Only after the user clicks the save button which should at that moment be disabled the "incorrect wallet "password" error message is displayed and should have as mentioned previously a red outline to highlight which box is invalid

Please recheck now.

@DeeJayElly please fix eslint issues

Fixed

Also on the create wallet screen there is an issue where the button becomes active again before the user has entered the repeated spending password

It's fixed now.

I can't set password now ((

I noticed an error with the error messages for the change password screen.

Here's a summary of all the issues so far

Here's a summary of all the issues so far

Please recheck all issues

@tomothespian please give this PR another look 🙏
@DeeJayElly please make sure all tests are passing 🙏

Is this the correct Error message to display when the user has yet to enter their password ? What do you think  ?@nikolaglumac

Is this the correct Error message to display when the user has yet to enter their password ? What do you think ?@nikolaglumac .Perhaps "Please enter your password" would be better ?

This is definitely not the right error message... @ManusMcCole please check what we have in the current production build.

Please remove the @"Error" Error message @DeeJayElly

@DeeJayElly can you please have this one done today?

should it be still an "Error" message here?

should it be still an "Error" message here?

You're right. I have fixed it now.

it matches :D
@nikolaglumac maybe we just disable second field untill first one is not "good" ?

Please remove the @"Error" Error message @DeeJayElly

Removed

it matches :D @nikolaglumac maybe we just disable second field untill first one is not "good" ?

Try it now @a-rukin

@DeeJayElly Great job! All the previous issues are fixed. I found a couple more that I listed at the end of this document:

Here's a summary of all the issues so far

Great job @DeeJayElly . The only outstanding issue I can still see is the paper wallet message being minorly truncated when Daedalus is not set to full screen

Great job @DeeJayElly . The only outstanding issue I can still see is the paper wallet message being minorly truncated when Daedalus is not set to full screen

@ManusMcCole this is a known issue which has nothing to do with this PR.
We will be fixing it in the scope of a different task.
cc @gnpf @a-rukin

@DeeJayElly on the restore dialog the submit button on 2nd step should remain disabled until user enters all 12/15/27 words:

@DeeJayElly on the restore dialog the submit button on 2nd step should remain disabled until user enters all 12/15/27 words:

Fixed

@DeeJayElly please remove password format validation on the "Current password" field - here we should only check for length > 0...

Fixed


Performance is broken when using libxsmm_aligned_malloc, libxsmm_aligned_scratch

A recent performance study unveiled performance which were root-caused by the use of libxsmm_algined_malloc/libxsmm_algined_scratch for application based allocation. Switching to _mm_malloc improved the performance significantly.
This was observed for cnnlayer and running ResNet50 convolutions.
export OMP_NUM_THREADS=28
export KMP_AFFINITY=granularity=fine,compact,1,0
./run_resnet50.sh 28 100 1 f32 F L 1
on a 8280 Cascade Lake CPU.

It's fixed and even better than _mm_malloc.

With the current master the performance is even slower than before.

The limit is dynamically exploiting the system. I will add verbose output for any such event and document it here.
Do you have a reproducer for a bad case?

Capturing the watermark and dynamically exploiting certain resource is implemented in a simplistic fashion (if not wrong). So, the issue is likely caused by that. Solution is in progress...

Certain allocation events are now shown at high verbosity levels, e.g., LIBXSMM WARNING: huge-page watermark reached at [...] (similarly for locked pages). Let aside huge-page partitioning, the limit for locked pages seems to be not reached on our cluster nodes (at least not by the tests that I checked). Please give it a (re-)try!

that was a machine not part of our cluster. The watermark returned an issue and reboot made the issue disappear.... So let's keep that issue in mind, but close it for now.

With the latest head GxM performance is reduce by 14% due to this issue.
In samples/deeplearning/gxm:
source setup_env.sh
export OMP_NUM_THREADS=56
export KMP_AFFINITY=granularity=fine,compact,1,0
make clean && make -j 16
srun ./build/bin/gxm train model_zoo/resnet/1_resnet50_dummy_56_f32.prototxt model_zoo/resnet/solver.prototxt

I have to check this because we gained perf. from page-locked memory. However, it makes allocations itself much slower. In any case, the new verbose messages should provide watermark information when page-locked memory is exhausted (given it is enabled aka 8aee4b1). Thank you for the reproducer!
First step might be to limit page-locked memory allocation to scratch memory allocations as those can be amortized. I will also check if scratch memory allocations are abused for long-life and more regular memory buffers.

hmm... GxM does lazy allocations, however it excluded the first 2 iterations in the runtime measurement: https://github.com/hfp/libxsmm/blob/master/samples/deeplearning/gxm/src/Engine.cpp#L672

( I am getting certain to be off for 3 weeks; hope the best for the next two days ;-)
The best you can do for this issue is to have a valid reproducer (command line), and target performamce vs. off-performance. With this information, I can drill-down and tune for the use case (if there is no other/general path). With current master we could even re-enable page-locked memory because it now only applies to scratch (and GxM uses just regular, i.e., non-scratch buffers).


Cannot run bert-efa-example example

The example bert-efa-example.yaml refers to a private image<PHONE_NUMBER>33.dkr.ecr.us-east-1.amazonaws.com/bert-efa-hvd-tf1-py3:latest and gets ImagePullBackoff due to lack of permissions.
Here is the line number for reference:
https://github.com/aws-samples/aws-efa-eks/blob/main/examples/bert-efa-example.yaml#L20
If possible, please provide a public version of this image so the example is reproducible.
Thank you!

Hello! I'm also having this issue with almost all of the Pytorch examples: https://github.com/aws-samples/aws-efa-eks/issues/2. It'd be great if these could be pushed to a public repo.


HH simulator

I ported the HH simulator from the delfi package to sbi as a a little exercise to get to know the sbi package. @janfb and I agreed that they would be valuable as part of the overall sbi package as well.

[ ] format w.r.t. to coding conventions
[ ] (?) add entire simulator to notebook (?)

I would suggest to create a separate folder example/hh and in there have hh_utils.py or so with the simulator, stats etc..
Then you can call the simulator and stats in the notebook by loading them from hh_utils.py.

@ojwenzel I suggest to close this PR as we now have a working version of the HH example already?
Many thanks for your effort though! In the end I think it turned out that your vectorization for handling batches changed the simulator in a way that the resulting posterior was different from the one in the delfi version.


Provide & inject not working when injection has default value

Version
3.0.0-rc.10
Reproduction link
https://codesandbox.io/s/vue-provide-inject-mg2oy?file=/src/index.js
Steps to reproduce
https://codesandbox.io/s/vue-provide-inject-mg2oy?file=/src/index.js
What is expected?
It should render without error
Accroding to https://v3.vuejs.org/api/options-composition.html#provide-inject
I think it should work

What is actually happening?
injection is null

It looks like a problem with from being missing:
https://github.com/vuejs/vue-next/blob/b53d45de65239fa4acd9c6bc41ed58fc9b823729/packages/runtime-core/src/componentOptions.ts#L461
I suspect that should be defaulting to key if from isn't set.


There was an issue completing the payment.

Hi there,
Could you please help me check why I get this error message. Upon checking the plugin codes it looks like the plugin is not setting the cko-card-token on card input. Could you please check and advise how to fix it?
Checkout Page: https://codepinoys-gmail.tinytake.com/msc/OTkzMzczM18yMzU5NzcxOQ
Issues: https://codepinoys-gmail.tinytake.com/msc/OTkzMzcwNF8yMzU5NzY5MA
Empty no value: https://codepinoys-gmail.tinytake.com/msc/OTkzMzcxN18yMzU5NzcwMw
Thanks

Hi there,
Upon further investigation it looks like the plugin has an issue on Tokenization. This like of codes is not working https://codepinoys-gmail.tinytake.com/msc/OTk0MzQxOF8yMzYwODA2MQ
Could you please check? Thank you


Consume the component in the readme

Seems like the readme needed some edits.

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           5      5
=====================================
  Hits            5      5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4279e44...b334350. Read the comment docs.


add Zero function to field

I have a few testing functions that check that my struct validation logic errors when certain fields are zeroed, and I wanted to DRY up this process. I'm looking to write a helper that takes a field name, zeroes that field, and ensures that it fails to validate. However, I can't use Set because Field.value is internal, so I can't pass reflect.Zero(f.value.Type()).Interface() to it.
As a result, I wrote Zero, which does just that. Tests are adapted directly from Set.

LGTM. Thanks @mammothbane


[MAP] show qrz confirmation in green

Hi,
propose this PR for show QRZ confirmation with green plot on map (dashboard, logbook and map lba).
(this "multi" confirmation information was in 2 places on code, a unique function (on logbook model) must be better ?)

Hello Joerg,
I don't understand : "The only counting methods are "LotW" and "QSL-Cards"." ;

QRZ is not use for defined if a qso is valid/confirmed ?
eqsl is used on lba, dashboard and logbook, so it should be exclu (if only lotw and qsl card are accepted)

thanks

Hi Aurelien.
For most awards, only QSL and LoTW counts. I agree that this should then be a user option to choose which confirmations should be counted for confirmed in the maps. To implement your solution for custom icons in LBA, I took the easy way, and just hardcoded the same way that was for the markers in the map on the dashboard.

ok, thanks all
i will change "count" (show on map) method for dashboard, logbook and lba.
i change the name on this PR ;)

ok, thanks all i will change "count" (show on map) method for dashboard, logbook and lba. i change the name on this PR ;)

it should be already implemented at dashboard and most of the awards.
The counting methods are living in the user-options. See "Account -> Default-Values -> Default-QSL-Methods"

so, i create a qso_is_confirmed() function, now confirmation plot on map (dashbord, logbook, lba) use the "qsl method" from user option.

Great. i like the new function

Tested working :)


Maybe a bug(wrong slice) in layers.py.

/compressai/layers/layers.py
line 100;     self.mask[:, :, 1:2, 1:2] = 0
Do you mean self.mask[:, :, 1::2, 1::2] = 0  ?
If you use the mask, I think here should be one more ":" here.

There is nothing wrong here. The mask type "c" corresponds to the situation that the current pixel can be predicted by all the surrounding ones within the kernel, as described in detailed in the paper.

I already check the paper. If the  mask matrix is in the fixed shape 3x3, it's right.


Allow histograms to be configured by the user

What does this PR do?
We bind histogram configuration to the environment to allow the agent5
to pass its configuration to dogstatsd6. Since histogram configurations
are complex types we use JSON. This force us to have custom logic to
initialized histogram configuration.
Additional Notes
Due to viper API limitation we have to manually check histogram_percentiles type.

No need to pass through JSON actually.
String slices can be set like export DD_HISTOGRAM_AGGREGATES="max median".
Int slices don't come for free but we could do something like:
type config struct {
    Percentiles []string `mapstructure:"histogram_percentiles"`
}

func (c *config) HistogramPercentiles (int[], err) {
    // try to parse integers out of c.Percentiles strings
}

// ....

var C config
err := config.Unmarshal(&C)
if err != nil {
  percentiles, err := C.HistogramPercentiles()
}

we can discuss whether using a different settings name for histogram_percentiles when passed through env vars, or using a string[] in datadog.yaml too, like:
# Warning: percentiles must be specified as yaml strings
histogram_percentiles: ['95', '98']


[Core] [Mono] Improve and use approximate equality methods

This is split into two three four commits, one which changes the Core math, one which exposes these methods to GDScript, one which changes the C# math, and one that uses it in several places.
The method is_equal_approx has been changed to this (and a corresponding C# method added):
real_t tolerance = CMP_EPSILON * abs(a);
if (tolerance < CMP_EPSILON) {
    tolerance = CMP_EPSILON;
}
return abs(a - b) < tolerance;

Scaling the tolerance for approximate equality means that the approximate equality method is now able to handle large values. The number 100 has less precision than the CMP_EPSILON value, and so previously any difference in the least significant bit would cause this method to return false.
The if statement is necessary because we don't want the tolerance to scale down endlessly. Without it, comparing 0 and 0.00000000000001 for approximate equality would return false since the tolerance would be zero. The if statement means that when comparing values below 1, the method behaves like it used to, where tolerance is CMP_EPSILON.
However, if you know in advance that you are comparing with zero, the new is_zero_approx method should be used, with simpler code that runs faster. Or, if you know in advance what the tolerance will be, you can skip the tolerance calculation by adding a third value to is_equal_approx.
I have also changed Vector3 and several other types to check for approximate equality rather than exact equality, internally and with comparison methods. Previously, the == method for comparing Vector3 etc would almost always return false in normal situations, making == not very useful.
This much more closely aligns with the linked article and the suggested use cases ("such as matrix and vector comparison operators") in the method description comment.
Furthermore, here's a simple example of why approximate comparisons are important (pseudocode):
float n = 0.1;
print(n == 0.1); // Returns false
print(is_equal_approx(n, 0.1)); // Returns true

This would be wonderful to have in core, as it provides a way to avoid problems when comparing vectors.

Moving to 3.2 milestone as we're about to enter the beta stage and release freeze for Godot 3.1. Only bug fixes against issues of the 3.1 milestone (or enhancements to core features of the 3.1 roadmap) will be considered until 3.1-stable is released.
Note: If it's merged after 3.1-stable is released, this change might be considered for cherry-picking into a later 3.1.x release.

@aaronfranke In #26761 I've added IsEqualApprox to MathfEx - you should change your PR accordingly

The idea of this PR is ok, but honestly I would leave the == 0 comparisons as is, there is no need to change them to is_equal_zero_approx

Tested this PR on the master branch (+ custom fix for my above comment), seems to work fine on the TPS demo.

Thanks!

Sorry guys, I dont understand why this got merged, but using approx equality for equality functions is ridiculous. I suggest revert ASAP.

Not only it goes against the intent of the function itself, but it hurts performance and a large part of the existing code requires equality to work the way it worked before.

Actually, from @aaronfranke's answer, i think a mistake happened here

The intent of the function is to check for equality. The purpose of comparing approximately is to prevent tiny floating-point errors from turning an equality false.
I think it makes sense for approximate equality to be the default choice for vectors, especially since a large part of the Godot codebase depends on making such approximate comparisons, in even more places than in this PR (for example https://github.com/godotengine/godot/pull/31395), and also the exposed behavior of == should be "safe".
If there are areas of the codebase where exact comparison is preferred due to performance, and we know that there will never be floating-point error, it might be a good idea to add a separate method to vectors etc for exact equality checking.

@aaronfranke It is the opposite, you use a special function to check a near-equality where it actually matters, else you kill performance.

It is not a good idea to hide this from the user, approximation equality needs to be used explicitly.


Reading empty parquet files causes an exception

Related to #2437
Reading in an empty parquet file generated when to_parquet is used with an empty dataframe results in
Traceback (most recent call last):
  File "/Users/shughes/Programming/anaconda-stats/util_scripts/influx_importer.py", line 264, in <module>
    main(sys.argv)
  File "/Users/shughes/Programming/anaconda-stats/util_scripts/influx_importer.py", line 260, in main
    upload(args)
  File "/Users/shughes/Programming/anaconda-stats/util_scripts/influx_importer.py", line 130, in upload
    upload_parquet(target_files, db_client, args.measurement_n, args.start_dt, args.end_dt)
  File "/Users/shughes/Programming/anaconda-stats/util_scripts/influx_importer.py", line 93, in upload_parquet
    df, f_cols, t_cols = parse_parquet(target_dirs, start_dt, end_dt)
  File "/Users/shughes/Programming/anaconda-stats/util_scripts/influx_importer.py", line 139, in parse_parquet
    dfs.append(dask.dataframe.read_parquet(directory, index='timestamp'))
  File "/Users/shughes/miniconda3/lib/python3.5/site-packages/dask/dataframe/io/parquet.py", line 287, in read_parquet
    categories=categories, index=index)
  File "/Users/shughes/miniconda3/lib/python3.5/site-packages/dask/dataframe/io/parquet.py", line 110, in _read_fastparquet
    minmax = fastparquet.api.sorted_partitioned_columns(pf)
  File "/Users/shughes/miniconda3/lib/python3.5/site-packages/fastparquet/api.py", line 599, in sorted_partitioned_columns
    s = statistics(pf)
  File "/Users/shughes/miniconda3/lib/python3.5/site-packages/fastparquet/api.py", line 567, in statistics
    for col in obj.row_groups[0].columns:
IndexError: list index out of range

I believe the tests didn't catch this because they don't set/expect an index?

You keep catching the corners!

I have a 750gb dataset which feels like it's nothing but corners!


Improve version management

This PR displays a warning at startup if the version used is not a release one.

Non passing tests are due to #47.


Update http4s-client, http4s-dsl, ... to 0.23.1

Updates

org.http4s:http4s-client
org.http4s:http4s-dsl
org.http4s:http4s-server

from 0.23.0 to 0.23.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Superseded by #176.


 don't work when RCTEnableTurboModule is enabled

Description
when enable RCTEnableTurboModule(YES) the  tag stop to display local image from assets-library: or ph:
React Native version:
version 0.63.2
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Enable turbo modules

2 .Update any component in the example project (eg ./Example/src/App.js/MainScreen component and attempt to render an image using assets-library://asset or ph://

Observe runtime error and image not displayed.

Expected Results
Image display as normal

I just created a PR in react-native-cameraroll to add custom Image URL loaders for ph:// and asset-library:// assets. https://github.com/react-native-cameraroll/react-native-cameraroll/pull/632
So if you install react-native-cameraroll, ph:// assets can be loaded again in <Image> components on new arch/Fabric 🎉🥳


Request: module 'SwiftProtobuf' was not compiled with library evolution support; using it means binary compatibility for 'TestModule' can't be guaranteed

Adding Swift-protobuf to our Xcode project causes the following build warning to be produced:
warning: module 'SwiftProtobufPluginLibrary' was not compiled with library evolution support; using it means binary compatibility for 'TestModule' can't be guaranteed
import SwiftProtobufPluginLibrary
^
In the interest of reducing build warnings, I request that the following setting be made on the Protobuf Xcode project build settings:
BUILD_LIBRARY_FOR_DISTRIBUTION = YES;

Build Configuration

macOS 11.6 (20G165)
Xcode version 13.1 (13A1030d)
Swift 5.5
SwiftProtobuf 1.17.0

It may be worth examining #1101 for prior discussion of library evolution mode.

Purely out of curiosity, what are you using the "PluginLibrary" for?  Most people only use the core "SwiftProtobuf" library and I'm interested in learning more about how people use the plugin library so we can do a better job evolving it in the future.

It may be worth examining #1101 for prior discussion of library evolution mode.

Thanks for the reply. I will follow up on the other issue.

Purely out of curiosity, what are you using the "PluginLibrary" for? Most people only use the core "SwiftProtobuf" library and I'm interested in learning more about how people use the plugin library so we can do a better job evolving it in the future.

Hello, thanks so much for your reply.
First off, I'm not the original developer who added protobuf to our app; I'm in charge of taking care of build warnings and these protobuf warnings are some of the last issues I haven't been able to clean up. So, I'm figuring out some of the protobuf issues after the fact.
After some more investigation, we apparently are just a regular client and the import of the SwiftProtobufPluginLibrary module was not needed. I changed to import SwiftProtobuf


Log an error if a BeanDefintion that we don't handle explicitly has an instance supplier

Our default implementation doesn't support instance supplier (as there's no way to know what's behind it) so we should throw an exception rather than silently trying to discover the creator executable.

On a second look this may trigger a number of false positive so I wonder if an error log wouldn't be better for now.

I've found a couple of use cases where the instance supplier is used to call the constructor with dependencies that would be autowired otherwise. That looks like enough to close this for now as we can't reliably know if something will go wrong in practice.


Add mode test

Pull Request Test Coverage Report for Build 122

6 of 8 (75.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 98.958%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

openprocurement/contracting/esco/utils.py
2
3
66.67%

openprocurement/contracting/esco/validation.py
2
3
66.67%

Totals

Change from base Build 121:
-0.5%

Covered Lines:
380

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 122

6 of 8 (75.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 98.958%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

openprocurement/contracting/esco/utils.py
2
3
66.67%

openprocurement/contracting/esco/validation.py
2
3
66.67%

Totals

Change from base Build 121:
-0.5%

Covered Lines:
380

Relevant Lines:
384

💛  - Coveralls


Chapter 1 - ch1_generate_first_image - Loading images

When I attempt to run the line - ds_train, ds_info = tfds.load('celeb_a', split='test', shuffle_files=False, with_info=True)
I get the following error:
"NonMatchingChecksumError                  Traceback (most recent call last)
NonMatchingChecksumError: Artifact https://drive.google.com/uc?export=download&id=0B7EVK8r0v71pZjFTYXZWM3FlRnM, downloaded to C:...\ucexport_download_id_0B7EVK8r0v71pZjFTYXZWM3FlDDaXUAQO8EGH_a7VqGNLRtW52mva1LzDrb-V723OQN8.tmp.521a68dd559d4cd49b06809e3e944c38\uc, has wrong checksum. Expected: UrlInfo(size=1.34 GiB, checksum='46fb89443c578308acf364d7d379fe1b9efb793042c0af734b6112e4fd3a8c74', filename='img_align_celeba.zip'). Got: UrlInfo(size=3.02 KiB, checksum='7871bf45999c9dfc0e6c0ebc60f44e77e6add3cdc9eee3072489754587b2a6f6', filename='uc').To debug, see: https://www.tensorflow.org/datasets/overview#fixing_nonmatchingchecksumerror"

This is due to Google's limiting download from their server. There was instruction in ch2_vae_celeb to download the dataset manually. I have now also copied that to ch1_generate_first_image, please git pull to get that change.

This is due to Google's limiting download from their server. There was instruction in ch2_vae_celeb to download the dataset manually. I have now also copied that to ch1_generate_first_image, please git pull to get that change.

When I run the code in google colab it gives me a FileNotFoundError on the gdown.download line. I don't know what I'm doing wrong.

When I run the code in google colab it gives me a FileNotFoundError on the gdown.download line. I don't know what I'm doing wrong.

@soon-yau


Install via Gemfile?

Is there any specific reason we wish to put the gem installs directly in the Dockerfile or could we use a Gemfile for each permutation?

no specific reason

Gemfile + Gemfile.lock would make the build process deterministic, and give us vulnerability warnings in GitHub https://help.github.com/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository/
I am happy to work on this, unless there are objections?


One of the formulas in the paper seems to have an error

Thanks to the authors for such influential work.
Equation 5 seems to be incorrect, refer to the equation 7 in the paper "DiffusionCLIP: Text-Guided Diffusion Models for Robust Image Manipulation".

These two equations do not seem to be equivalent. Could the author give the derivation of Equation 5.

Also, would you mind further explaining the marked passage, I'm a bit confused.

Hi, thank you for your detailed reading of this work. Regarding Equation 5 (DDIM sampling part), we refer to the representation of the null-text-inversion paper (https://arxiv.org/pdf/2211.09794.pdf)

compared with eq.(5) of RIVAL paper:

We also add a similar explanation in Appendix(A).
For the marked contents, as the inversion process of DDIM is deterministic, it can predict a noise term in each step, then invert the previous-step latent using this noise term and the noisy latent. However, this process does not guarantee that the inverted latent should be formed in a standard Gaussian (N(0, I)). This causes the latents in the inversion chain to potentially have different distributions from the vanilla inverse diffusion process (e.g., generating images from a standard Gaussian). When we try to apply cross-image self-attention (Sec. 3.1), the distribution differences between the two chains (real-inversion & generation) create a distribution gap of KQV terms, which affects the attention calculation and leads to a diverse generation result (Fig. 3)

Thank you very much for your reply, it is very useful for me. @JulianJuaner
For the question of the formula, I have read this paper. It may be a typo and the original paper has been revised in its CVPR camera ready version. Reference can be made to this link: https://github.com/google/prompt-to-prompt/issues/55
For the second question, thank you for your patience to explain.

https://openaccess.thecvf.com/content/CVPR2023/papers/Mokady_NULL-Text_Inversion_for_Editing_Real_Images_Using_Guided_Diffusion_Models_CVPR_2023_paper.pdf“

@houjie8888
Thank you for your correction of the formula. We will check and revise our paper in the later version.
I will temporarily close this issue. If you have any further questions about this paper, please feel free to re-open this issue~

hi @JulianJuaner
I have some questions about adaptive normalization as I'm re-reading this paper today and would appreciate your response.

I would like to know if the noise predicted by DM needs to be normalized. As I understand adaptive normalization, here it may be necessary to first normalize the noise before multiplying by the mean and adding the variance. Is there any underlying theory for Eq. 9 in the paper, and what is it doing?

like this:
$$
\sigma \left( \varepsilon {\theta}\left( X{R}^{t} \right) \right) \left( \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) -\mu \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right) \right) /\sigma \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right) \right) +\mu \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right)
$$

like this:
$$ \sigma \left( \varepsilon {\theta}\left( X{R}^{t} \right) \right) \left( \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) -\mu \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right) \right) /\sigma \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right) \right) +\mu \left( \varepsilon {\theta}^{cfg}\left( X{G}^{t} \right) \right) $$

Thank you very much for your correction. We have urgently checked our implementation and paper, and indeed, you are right. Due to the rush when writing the paper, we did not conduct a thorough review and made this very basic mistake, for which we are deeply sorry. We will revise the parts mentioned in our published paper as soon as possible. Thanks again!

From StyleGAN paper:

Here is the code of the AdaIN implementation used in our work.
def adain(feat, cond_feat, eps=1e-5):
    # eps is a small value added to the variance to avoid divide-by-zero.
    size = feat.size() # [d, c]
    C = size[1]
    feat_var = feat.var(dim=0) + eps
    feat_std = feat_var.sqrt().view(1, C)
    feat_mean = feat.mean(dim=0).view(1, C)

    cond_feat_var = cond_feat.var(dim=0) + eps
    cond_feat_std = cond_feat_var.sqrt().view(1, C)
    cond_feat_mean = cond_feat.mean(dim=0).view(1, C)
    feat = (feat - feat_mean.expand(size)) / feat_std.expand(size)
    return feat * cond_feat_std.expand(size) + cond_feat_mean.expand(size)

Haha, I searched a lot of normalization methods for this.
Very much anticipating future code releases, and still thank you for contributing to the community. (●'◡'●)


erron in request: 404

hello, I always have the mistake erron in request: 404. Everything was working yesterday.

Maybe the spotify api was temporary down.


Warning: LineChart.getDOMNode(...) is deprecated. Please use ReactDOM.findDOMNode(instance) instead

https://github.com/jhudson8/react-chartjs/pull/59


Shifts: Nest under Schedules

Nest shifts under schedules so that the shifts _form doesn't require user to select the schedule they'll be attaching the shift to.  This way when a shift is created from a schedule there's no confusion and they can't mistakenly add the shift to the wrong schedule.
Question:
Should we add a separate form for creating a schedule from any part of the application?  This way managers could go in and create shifts any time anywhere.  These would be un-nested forms where that functioned as they do now.

Should we add a separate form for creating a schedule from any part of the application? This way managers could go in and create shifts any time anywhere. These would be un-nested forms where that functioned as they do now.

You mean a form to create shifts from anywhere or schedules? I think we decided to limit 1 schedule per organization unless they get a "premium" plan. Hah... sounds like EA 😁.
Also, is this related/possible duplicate of #38?

Lol wow I was pretty tired. Yeah it's a duplicate but the question is new.
Do you want to let people make shifts anywhere?  Or is creating it from the
schedule good enough?
On Wed, Oct 18, 2017, 11:14 PM Lakshya Kapoor<EMAIL_ADDRESS>wrote:

Should we add a separate form for creating a schedule from any part of
the application? This way managers could go in and create shifts any time
anywhere. These would be un-nested forms where that functioned as they do
now.
You mean a form to create shifts from anywhere or schedules? I think we
decided to limit 1 schedule per organization unless they get a "premium"
plan. Hah... sounds like EA 😁.
Also, is this related/possible duplicate of #38
https://github.com/zeiter-io/zeiter/issues/38?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeiter-io/zeiter/issues/48#issuecomment-337809889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALidQkKfDKZlSLsfn0U-XMq7XDDw-zjxks5stujKgaJpZM4P-th_
.

Anywhere sounds good. Just like Jira.
Now, in this case we'll have to have a drop-down if the manager is part of multiple schedules. Otherwise default to the only one.

Duplicate.  Adding info to issue #38

Mistakenly closed.  Issue #38 has been closed instead.


[FEATURE] On/Off Button

Is your feature request related to a problem? Please describe.
Sometimes I would love to leave the app open but have no sounds active.
It would be nice if all sound would be going off when toggling that option.
Describe the solution you'd like
n
Describe alternatives you've considered
n
Additional context
n

won't be fixed due to closure of project / archiving of repository


Error: map_fn = tf.python.functional_ops.map_fn AttributeError: module 'tensorflow' has no attribute 'python'

Error on System: py3.5, win7, tf 1.2 cpu version.
map_fn = tf.python.functional_ops.map_fn
AttributeError: module 'tensorflow' has no attribute 'python'

just these two lines:
import tensorflow as tf
map_fn = tf.python.functional_ops.map_fn

anyway looks like old code which might be changed to
map_fn = tf.map_fn ?
I am closing this issue, because it works. Thanks


fix include handle

"const char *file = strchr(yytext, ' ') + 1"  supposes only one space after Include, but the grammar "[ \t]+" mean multiple space and TAB including one space;

Just to flesh out a little background (and correct me if you think I'm mistaken) ...
In v3.0.3, several configuration directives allowed for exactly one space character after the directive name.
v3.0.4 included changes (https://github.com/SpiderLabs/ModSecurity/issues/2006 ) to broaden the whitespace that is allowed for many of these directives, including the two referenced in this pull request.
The last two changes in that commit ( https://github.com/SpiderLabs/ModSecurity/commit/dc78c0e180d09aa1b2f0ffad1a8d6967e69f984f ) changed the whitespace definition from '[ ]' to '[ \t]+' ...
... and you believe that fix was incomplete.

That background stated, can you describe what use case fails to work as expected?
I just tried changing my main.conf file to include additional spaces between 'Include' and the file path and it worked fine.  (Perhaps I've misunderstood something.)

Just to flesh out a little background (and correct me if you think I'm mistaken) ...
In v3.0.3, several configuration directives allowed for exactly one space character after the directive name.
v3.0.4 included changes ( #2006  ) to broaden the whitespace that is allowed for many of these directives, including the two referenced in this pull request.
The last two changes in that commit ( https://github.com/SpiderLabs/ModSecurity/commit/dc78c0e180d09aa1b2f0ffad1a8d6967e69f984f ) changed the whitespace definition from '[ ]' to '[ \t]+' ...
... but that that portion of change appears to be incomplete.
That seem to me to be a correct conclusion.  For one thing, using tabs instead of spaces after the 'Include' keyword is a problem use case.
Turning to this proposed fix:
One thing I'm a little wary of, is including regex.h here.  We haven't previously used that within the parser subcomponent, and, given that Flex has its own regular expression engine, it might be confusing in future if we start mixing that in.

Yes, You are right
If no #2006 included, use one space is correct;
but after #2006 included, [ \t]+ should be supported correctly for  {CONFIG_INCLUDE}[ \t]+["]{CONFIG_VALUE_PATH}[" and {CONFIG_INCLUDE}[ \t]+{CONFIG_VALUE_PATH}.

ignore this PR.


No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file on MacOS

Issue description
Hi, I'm finally able to build and compile my haskell project. But I got the following error:
2017-03-22 21:07:20.683 frontend[79041:2235329] No Info.plist file in application bundle or no NSPrincipalClass in the Info.plist file, exiting
is there any way to know how to add info.plist to my program? is it in default.nix or else?
Steps to reproduce
build using webkitgtk-2.4.11
Technical details

System: (MacOs)
Nix version: (run 1.11.7)
Nixpkgs version: (17.09pre-git)

You're going to have to create an app bundle. The basic structure is:
MyApp.app/
   Contents/
      Info.plist
      MacOS/
        <binary here>
      Resources/

Info.plist is tricky, but you can find some examples looking in /Applications/. Here is the source from Emacs.

@matthewbauer hi, yeah i see it when my app build like this:
Linking dist/build/frontend/frontend ...
Creating application bundle directory dist/build/frontend.app
Copying executable frontend into place from dist/build/frontend/frontend to dist/build/frontend.app/Contents/MacOS/frontend
Copying macos/Info.plist to dist/build/frontend.app/Contents/Info.plist
Running: /Applications/XCode.app/Contents/Developer/Tools/Rez Carbon.r -o dist/build/frontend.app/Contents/MacOS/frontend
Running: /Applications/XCode.app/Contents/Developer/Tools/SetFile -a C dist/build/frontend.app/Contents

After i manage to build it. However, there is no dist/build/frontend, so i recreated it once again, but still I cannot run and got the following report:
Application Specific Information:
abort() called
terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '+[NSUndoManager(NSInternal) _endTopLevelGroupings] is only safe to invoke on the main thread.'

So do I need to create the frontend.app manually every time I finish my compilation ?

Could you provide your current setup? The issue is probably in your build files.

Can we close this due to inactivity?


refactor: changed a named function to be anonymous

Why?

Why not ?
Actually consistency. Maybe I'm too much obsess about consistency but I find harder to understand a piece of code when multiple different conventions are used.
If you consider merging this please wait there are other minor cleanups that I could squash here, if not feel free to close.
Le 26 mars 2015 19:57:32 CET, Brian Ford<EMAIL_ADDRESS>a écrit :

Why?

Reply to this email directly or view it on GitHub:
https://github.com/angular/zone.js/pull/63#issuecomment-86670328

So the only one thing I've got "against" anonymous functions is that debugging gets harder. So if we are after consistency I would rather name all the functions.
(once again, sorry for just chiming in with style issues, still trying to wrap my head around the zone thing)

This fn appears in stacktraces sometimes, so having a name makes it a bit easier when looking at stacktraces.

I haven't thought about it makes sense, closing this PR. Thanks for your help.
@pkozlowski-opensource I appreciate your comments, no problem. May be we can discuss about zones some day, I'm working quite a lot around it these days.


Doubt: What is transaction in the block.

First of all, I would really like to thanks to make me understand the concept of Blockchain...
Now doubt :-
Will the transaction in the block be a list of transactions or a block will have a single transaction.. From your code it seems to be the list...
Thanks
SP

In my first version a block could just contain 1 transaction.
The last version however switched to supporting multiple transactions per block (just like most other blockchain implementations)
I closed this issue because it's a question. Feel free to post follow up questions here.

it is simple , like deferred erea of git;

你可以多次修改文件 add到暂缓区 ,  然后一次性commit


replace loadgen

Problem to be solved
This repo has a number of open issues and we haven't prioritized fixing them because we expect to replace this tool with one or more others.
Draft design
needs work

How will we test multi-node chain?
How will we test state-sync?

The deployment-test of agoric-sdk also has some customization meant to trigger more aggressively any execution divergence: it compiles xsnap with XSNAP_RANDOM_INIT which causes uninitialized memory in xsnap to not be zero filled. That results in diverging heap snapshots if there is any uninitialized memory. It's possible a more dedicated test could be used instead.


map's location is not correct [Other issue]:

Before proceeding, is there an existing issue or discussion for this?

[X] I have done a search for similar issues and discussions.

Description
i have a map, from ros, formate is pgm, now i need to change to building.yaml, i find the robot location is not right

in application, my robot is locate in point7, but now in the website is locate in the left corner
below is my pgm file

map.zip

When you update the position using the RMF API, are you converting the robot coordinates (usually pixel coordinates) to the "canonical" RMF coordinates (which are based on Cartesian meters)?
This is usually done using the nudged Python library to align some known pixel coordinates of the robot with known canonical Cartesian coordinates.

i use free_fleet_client_ros1 to update the corrdinate
i use below source code
https://github.com/CLOBOT-Co-Ltd/clober_rmf
it contain server and client
not do any transform, can you give me some examples how to use the nudged?

Hi @yuduo, you will need to launch the server with the correct transforms filled out here https://github.com/CLOBOT-Co-Ltd/clober_ros2_ff/blob/foxy-devel/launch/clober_ff_server.launch.xml#L26-L29, or any equivalent launch files you are using for the server
to generate these transforms, you can either do it manually by selecting points and passing them to nudged, the documentation of the library provides some examples https://pypi.org/project/nudged/. For example, selecting a few points in the RMF map, and selecting those same corresponding points in the robot laser scan, pass them to nudged to estimate the transform. We have a small portion of such an example documented https://osrf.github.io/ros2multirobotbook/integration_fleets_adapter_tutorial.html?highlight=nudge#b-configure-transformations-between-rmf-and-robot
Or you can use the traffic-editor to overlay your laser scan as a separate layer, create Features on floor plan layer as well as on the robot laser scan. After attaching Constraints to each set of Features, the layers should align and you will obtain the transformation in the .building.yaml output, like so https://github.com/open-rmf/rmf_demos/blob/main/rmf_demos_maps/maps/office/office.building.yaml#L102-L106. The office world in rmf_demos is a good example of how that is done


FeatureManager provide access to a feature iterator.

FeatureManager provide access to a feature iterator without querying for a particular interval.
This must work without the need for an index file present.

This one is done.


Migrating a repository profile from legacy OMIVV to OMEVVP

Requirement Breakdown
Details

Objective
All the repository profiles in the OMIVV appliance should be migrated to OMEVV

Authentication/Authorization
Authenticate using vCenter credentials (Basic Authorization) and "x_omivv-api-vcenter-identifier" (UUID of the vCenter) as a mandatory header.

List of the tasks in the workflow (in   order)
Ensure that the vCenter user credentials and the corresponding vCenter UUID are accepted for both OMIVV and OMEVVComply with any input validation (see below)Main script should collect the vCenter details like IP/Name, Repository details from the OMIVV IP/Name providedExport the vCenter and Repository profiles to csv fileExtract the details required to create the repository profiles in OMEVV

Module type: Library and/or executable
Both library and executable, when used as library, it should send the Repository details objects to the caller. When used as executable to export the details of vcenter and repository profile to csv file.

Input and format
Script1 : Input – OMIVV IP/name , OMIVV creds, VC IP/name, VC creds      Script2 : Input – OMIVV IP/name , OMIVV creds, VC1 IP/name, VC1 creds, OMEVV IP/name, OMEVV creds, VC2 IP/name, VC2 creds

Expected output and format   Export required
Script1: Output – CSV file with all registered VC details and Repository profiles   Script2: Output – Repo profile details extracted from OMIVV , repo profile names with id created in OMEVV

Concurrency requirement.
None

Execution model: synchronous or   asynchronous
Synchronous

Applicable timeouts and retries
Attempt up to 3 times only when the failure is on account of a network timeout to access vcenter details. On any other types of error for instance, providing invalid input parameters, no retry should be attempted.

Expected error handing
Handle all the network and non network related errors and log them in a user friendly way.

Expected domain specific validation
As mentioned above under Input and format

https://github.com/dell/omivv/pull/37

https://github.com/dell/omivv/pull/55


About project license

Hello folks, that’s a really nice project! I would like to use it in one of my projects, but I saw that this repository don’t have any license file. Do you folks intend to add some open source licensing in this project, or should we assume that the code published here can’t be used in other places?
Thank you 😄

Thanks for your interest in our project. This project will adopt Apache License 2.0, and you can use the code under the license.
Thanks!


Add branch coverage for deriveDomainSeparator

This PR adds a test for changing chainId in-flight to add branch coverage for _deriveDomainSeparator

Codecov Report
Base: 88.99% // Head: 89.48% // Increases project coverage by +0.48% :tada:

Coverage data is based on head (29f01e1) compared to base (257390c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##              1.2     #742      +/-   ##
==========================================
+ Coverage   88.99%   89.48%   +0.48%
==========================================
  Files          48       48
  Lines        2554     2625      +71
  Branches      360      360
==========================================
+ Hits         2273     2349      +76
+ Misses        251      250       -1
+ Partials       30       26       -4

Flag
Coverage Δ

production
82.88% <ø> (+1.09%)
:arrow_up:

reference
97.69% <ø> (+0.17%)
:arrow_up:

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

Impacted Files
Coverage Δ

reference/lib/ReferenceFulfillmentApplier.sol
97.97% <0.00%> (+1.01%)
:arrow_up:

contracts/lib/FulfillmentApplier.sol
100.00% <0.00%> (+2.85%)
:arrow_up:

contracts/lib/GettersAndDerivers.sol
100.00% <0.00%> (+5.55%)
:arrow_up:

reference/lib/ReferenceGettersAndDerivers.sol
100.00% <0.00%> (+5.88%)
:arrow_up:

contracts/lib/ConsiderationDecoder.sol
84.43% <0.00%> (+8.54%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Revert "[HUDI-6212] Hudi Spark 3.0.x integration  (#8714)"

This reverts commit 11aee9695ec30d8580758c8c81414ffd3c38f0b5.
Change Logs
revert Hudi Spark 3.0.x integration
Impact
No impact
Risk level (write none, low medium or high below)
Low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Under discussion.


goreleaser: bump release to 0.164.0 and fix config deprecations

Required groundwork for Graviton and darwin arm64 support
Signed-off-by: Antoine Deschênes<EMAIL_ADDRESS>

/cc @nckturner

Still need to add golang 1.16, arm64 platform and multiarch docker images after this, would you rather have it in a single PR?

Sorry for the delay, either is fine but we can do a separate PR to keep it simple.

/lgtm
/approve