Question - Advance Installation Options

Hello, I have a question regarding the following statement in the Advance Usage.md
Option 1: default:
Zap installs lnd for you as part of the installation process. Zap will automatically start the internal lnd daemon for you when you select the default connection type during the on-boarding process. In this mode we run lnd as a light client called neutrino (BIP 157 & BIP 158) which allows us to run lnd without requiring a Bitcoin full node on your system - Instead, Zap will connect to one Zap's hosted BTC full nodes.
Question: After creating the wallet, is it possible to access the LND implementation that Zap just installed through LND's REST interface, invoice macaroon and tls.cert?
I want to use Zap to control the wallet and LND and Bitcoin backend through Neutrino, but I want to be able to create invoices through a website connection to LNDs using Zap's wallet.
Thanks.
M.

It is possible.
See https://twitter.com/btcsocialist/status/1167861605721227264?s=21
I’ll do a more detailed write up and add to our documentation.

I put together a brief tutorial here https://docs.zaphq.io/docs-desktop-neutrino-connect


fix: Remove more @rules_synology in case it causes the 8.0.0rc4 failure

The BCR test at https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/72#019367bc-a363-4bce-87a5-6370bd11332b seems to be failing on a missing @rules_synology even though the module under-test is exactly that one.  This is really the same fix started in 87bbeda2cd07275e49200dec527034b03da32acf (but seems I found some post-merges)
I'm assuming that the import is being done with an alias so that the module doesn't exist to specifically catch this absolute reference behaviour.  I can't repo and I'm unsure.

#173 shipped but with a templating error corrected in #175, published in #176


Fix Workflow

The song just won't end!

The song just won't end!

pretty sure thats just unrelated to the pr tho

The song just won't end!

Fixed


Import container/helm vulnerabilities from ArtifactHub.io

Is your feature request related to a problem? Please describe.
Currently, osv.dev doesn't have much information about container image vulnerabilities.
At the same time Artifacthub.io runs trivy to scan container images^1, would be great to be able to see vulnerability information collected by Artifacthub in osv.dev.
Describe the solution you'd like
Integrate Artifacthub as datasource for vulnerabilities using Security Report API^2
Describe alternatives you've considered
Fetching vulnerability information directly form ArtifactHub API^2
Additional context

https://github.com/artifacthub/hub/issues/4052

Thanks for the endorsement and for raising this with Artifacthub.io as well. We're largely dependent on them choosing to publish OSV records before we can move this forward...


Problems with installation

Hello,
I read with interest your article and your script seems to me very useful in testing some preliminary in silica digestions for my project.
By the way I have some problems with installation and I got this error message:
(base) bruno@Pleroma:~/Desktop$ make -C egads/src
make: Entering directory '/home/bruno/Desktop/egads/src'
gcc -o ../egads -Wall -O3  -lm -ggdb -lz main.o restrict.o enzyme.o sequence.o counts.o html.o d3.bin.o css.bin.o html.bin.o gel.bin.o ridge.bin.o table.bin.o msbuffmin.bin.o args.o
/usr/bin/ld: warning: msbuffmin.bin.o: missing .note.GNU-stack section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
/usr/bin/ld: main.o: in function ks_getuntil2': /home/bruno/Desktop/egads/src/main.c:14: undefined reference to gzread'
/usr/bin/ld: main.o: in function main': /home/bruno/Desktop/egads/src/main.c:49: undefined reference to gzopen'
/usr/bin/ld: main.o: in function ks_getc': /home/bruno/Desktop/egads/src/main.c:14: undefined reference to gzread'
/usr/bin/ld: main.o: in function ks_getuntil2': /home/bruno/Desktop/egads/src/main.c:14: undefined reference to gzread'
/usr/bin/ld: main.o: in function main': /home/bruno/Desktop/egads/src/main.c:131: undefined reference to gzclose'
/usr/bin/ld: main.o: in function ks_getc': /home/bruno/Desktop/egads/src/main.c:14: undefined reference to gzread'
/usr/bin/ld: /home/bruno/Desktop/egads/src/main.c:14: undefined reference to gzread' /usr/bin/ld: main.o: in function main':
/home/bruno/Desktop/egads/src/main.c:58: undefined reference to log10' /usr/bin/ld: /home/bruno/Desktop/egads/src/main.c:58: undefined reference to round'
collect2: error: ld returned 1 exit status
make: *** [makefile:45: ../egads] Error 1
make: Leaving directory '/home/bruno/Desktop/egads/src'
I currently have Ubuntu 23.04 version installed.
Do you have any suggest? Thanks in advance.
Bruno

Can you run the following as a test? It should finish the build process and produce the executable /home/bruno/Desktop/egads/egads.
cd /home/bruno/Desktop/egads/src
gcc -o ../egads -Wall -O3 main.o restrict.o enzyme.o sequence.o counts.o html.o d3.bin.o css.bin.o html.bin.o gel.bin.o ridge.bin.o table.bin.o msbuffmin.bin.o args.o -lm -lz

I believe the issue is the newer version of gcc is more pedantic regarding library include positions. Please let me know if it works and I'll update the makefile accordingly.
Tony

Hello Tony,
Thanks a lot for your very quick answer! I performed the test but it seems not to be effective:
(base) bruno@Pleroma:~/Desktop/egads/src$ gcc -o ../egads -Wall -O3 main.o restrict.o enzyme.o sequence.o counts.o html.o d3.bin.o css.bin.o html.bin.o gel.bin.o ridge.bin.o table.bin.o msbuffmin.bin.o args.o -lm -lz
/usr/bin/ld: warning: msbuffmin.bin.o: missing .note.GNU-stack section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker

If that's the the only output, then it was probably successful.
Do you have the executable /home/bruno/Desktop/egads/egads?

Hello Tony,
I found the executable so installation was successful.
How to start to use the program? I understood the syntax, but should I add my reference genome in a specific folder of the installation, or is possible use the absolute path? Is there a pre defined list of RE from which can I choose? Data in /test/data seem to be already elaborated: is there any row data anywhere in order to perform a quick test?
Thanks.
Bruno

I've update the readme to include a full example (recreates the report used in the paper).
Any path (absolute or relative) to a file should work for both the input fasta file and the output html and/or bed file
The REs are defined in REBASE. I've now included links in the readme.
The test folder are unit test to validate some of the code, not to test if the program compiled correctly. To do that run the example in the updated readme. Sorry for the confusion.

Hello Tony,
I've tried with the example and all went smooth.
Thanks again for your kind help and explanations.
Bruno


EDL cmx 9600 tries to add the same clip to multiple tracks

Hello,
I tried to used OTIO with some sample EDLs we use to test our editorial tools and one them raised the following error during EDL parsing:

ValueError: Composable named 'mad.men.714.hdtv-lol.mp4' is already in a composition named 'A1', remove from previous parent before adding to new one. Composable: Clip("mad.men.714.hdtv-lol.mp4", MissingReference(None, None, {}), TimeRange(RationalTime(0, 24.0), RationalTime(81982, 24.0)), {}), Composition: Track(A1, [otio.schema.Clip(name='mad.men.714.hdtv-lol.mp4', media_reference=otio.schema.MissingReference(name=None, available_range=None, metadata={}), source_range=otio.opentime.TimeRange(start_time=otio.opentime.RationalTime(value=0, rate=24.0), duration=otio.opentime.RationalTime(value=81982, rate=24.0)), metadata={})], TimeRange(RationalTime(0, 24.0), RationalTime(81982, 24.0)), {})

Caused by an edit event like:

003  AX       AA    C        00:00:00:00 00:56:55:22 00:00:00:00 00:56:55:22

FROM CLIP NAME: mad.men.714.hdtv-lol.mp4

It seems that the adapter tries to add the same clip to A1 and A2 tracks, following rules defined here: https://github.com/PixarAnimationStudios/OpenTimelineIO/blob/master/src/py-opentimelineio/opentimelineio/adapters/cmx_3600.py#L77, but this is not allowed.
EDLs being some kind of wild west, may be the adapter should have a permissive mode where only critical problems would cause errors, and others would just issue warnings ? Some extension of the ignore_timecode_mismatch mode? I had some problems with some ill formed asc_sop values, which in some cases could be ignored?
Thanks.

Without having tried a fix, could it be that one of these lines are redundant? https://github.com/PixarAnimationStudios/OpenTimelineIO/blob/master/src/py-opentimelineio/opentimelineio/adapters/cmx_3600.py#L255-256

Hi @gplsteph thanks for letting us know. I just submit PR #644 to fix this.
Do you happen to have an example of some of the asc_sop issues?
As we characterize recoverable issue in EDLs, I think starting to phase in some less strict parsing behavior may make sense. I think some of the cases are still a little unclear to us so we want to keep catching them to make sure we keep improving the adapter and don't risk pushing bad data into productions.
If you have other specific cases where lest strict parsing behavior would be helpful, I'd love to take a look and see what we can do.

Hello, thanks!
The asc_sop issue was caused by a bad string being set as the value. Not a real production example, just something we had in our tests suite to check we were able to retrieve this from EDLs. Our tools don't parse it, we just keep track of the string. Parsing it and using it is left to tools which really need it.
Given that this is retrieved from a comment which could (and will) be anything, that this is not stricly needed for a cut, I think that should be considered as a "bonus" and shouldn't cause parsing to fail. It might be a good idea as well to keep all comments in the clip meta data, even if they were parsed and produced something.
cheers.

@reinecke your PR looks good. @gplsteph can you verify that #644 addresses the audio track problem you found?

I looked at the code, and it seems it will. However I’m not sure if the writer will do the right thing. I think it will write two A tracks ?

In a quick test I see it writing out a single A track, however this is using a somewhat contrived edl I created from your example above.
Would you be able to check against a more real-world case? I unfortunately haven't encountered this issue in the flavor of EDLs I've been working with. Would you be able to give us some more context on how these EDLs are used in your workflow and where the OTIO adapters fall short in supporting that? Also if you have any example EDLs you could share it would help us in improving our test suite.

Hello,
here are the EDL files we use for our own EDL parser unit tests. Some of them are real production EDLs, some others are examples we put together.
Please note that some of these files have binary data at the end. I never knew from where this data came from, but, in doubt we have this in the code which loops over the EDL lines:
                    # Not sure why we have to do that ...
                    # Some crappy Windows thing ?
                    line = line.replace("\x1a", "").strip(" \n")
                    if not line:
                        continue

So, not sure if all these examples are real valid cases, we wrote our parser a couple of years ago, and added samples over the years.
Hope it helps.
multiple_tests.zip

@gplsteph Thanks for sharing these, this is a great test set.
The 0x1A thing comes from the SMPTE specification 258M (descendent of the CMX3600 EDL spec published in the 80s). In part 5.1, it states:

The end of an edit decision list is indicated by either:
– the end of the storage medium;
– a CONTROL-Z (SUB) character.

So technically those files adhere closer to the SMPTE spec, but realistically I think most people have abandoned that. There are some others I've seen with similarly weird characters at the beginning, but I still haven't figured those out.
Would you mind if we added some of your example files to the OpenTimelineIO repo so we can include them in our unittesting?

hello, no problem to add our files to the otio test suite. And thanks for the 0x1A explanation!


chore: fix all tests

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

chore: fix all tests

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[ ] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 3 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 44.094%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/cmd/cmd_add.go
0
1
0.0%

pkg/cmd/cmd_graph.go
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2475

Relevant Lines:
5613

💛  - Coveralls


feat: custom domains in HTTP API

Issue #, if available:
Description of changes:
Description of how you validated changes:
End to end tested
Checklist:

[x] Write/update tests
[x] make pr passes
[x] Update documentation
[x] Verify transformed template deploys and application functions as expected
[x] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1472 into develop will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1472      +/-   ##
===========================================
- Coverage    94.39%   94.35%   -0.05%
===========================================
  Files           78       78
  Lines         4714     4819     +105
  Branches       948      969      +21
===========================================
+ Hits          4450     4547      +97
- Misses         121      125       +4
- Partials       143      147       +4

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 4a991a0...6fcacc4. Read the comment docs.

Overall looks good to me. Is Domain supported in globlas?

yes. updated a test to use globals instead

Overall looks good to me. Is Domain supported in globlas?

yes. updated a test to use globals instead

Can we add Domain here https://github.com/awslabs/serverless-application-model/blob/develop/docs/globals.rst for HttpApi?

Codecov Report

Merging #1472 into develop will decrease coverage by 0.03%.
The diff coverage is 92.66%.

@@             Coverage Diff             @@
##           develop    #1472      +/-   ##
===========================================
- Coverage    94.15%   94.11%   -0.04%
===========================================
  Files           78       78
  Lines         4789     4894     +105
  Branches       967      988      +21
===========================================
+ Hits          4509     4606      +97
- Misses         130      134       +4
- Partials       150      154       +4

Impacted Files
Coverage Δ

samtranslator/plugins/globals/globals.py
99.05% <ø> (ø)
:arrow_up:

samtranslator/model/sam_resources.py
94.29% <100%> (+0.09%)
:arrow_up:

samtranslator/model/apigatewayv2.py
94.73% <100%> (+0.98%)
:arrow_up:

samtranslator/model/api/http_api_generator.py
92.43% <91.48%> (-0.77%)
:arrow_down:

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 c5221fc...e28f4a4. Read the comment docs.

Codecov Report

Merging #1472 into develop will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1472      +/-   ##
===========================================
- Coverage    94.15%   94.11%   -0.04%
===========================================
  Files           78       78
  Lines         4789     4897     +108
  Branches       967      988      +21
===========================================
+ Hits          4509     4609     +100
- Misses         130      134       +4
- Partials       150      154       +4

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 c5221fc...fbd3f80. Read the comment docs.


3.0 Cookie Consent updates

Cookie consent has been removed from the templates in ASP.NET Core 3.0
Fixes #12720

@Rick-Anderson can you please review and merge?

@isaac2004 Rick's on vacation. I have this on my to-do list for today.


RSS Feed: XML namespaces are missing

No they are not, got fooled by Firefox XML preview :trollface:


fix: npm audit fix

Codecov Report

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

@@          Coverage Diff           @@
##           master     #52   +/-   ##
======================================
  Coverage    1.98%   1.98%
======================================
  Files          32      32
  Lines         707     707
  Branches      178     178
======================================
  Hits           14      14
  Misses        693     693

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 710a0e0...a901acd. Read the comment docs.

:tada: This PR is included in version 1.3.6 :tada:
The release is available on:

1.3.6
GitHub release
1.3.6

Your semantic-release bot :package::rocket:


[SelectField] Add min-height to MenuItem

This PR adds a min-height to <MenuItem /> component. It especially allows to add an empty <MenuItem /> in <SelectField /> for nullable value. For instance:
<SelectField floatingLabelText="Frequency" value={this.state.value} onChange={this.handleChange}>
          <MenuItem value={null} primaryText="" />
          <MenuItem value={1} primaryText="Never" />
          <MenuItem value={1} primaryText="Always" />
</SelectField>

It is still not a perfect solution, as if we put some primaryText prop, text would still overlap with floating label (as explained in #4275).

Yet, I can't see any easy solution here. We should discuss about it in the issue directly. Meanwhile, this PR allows to bypass the problem.
Here is the updated sample preview:

Note: some tests are failing on both this branch and master on my dev machine. Hence, I suppose this is fine.

Note: some tests are failing on both this branch and master on my dev machine. Hence, I suppose this is fine.

Looks like an issue with eslint. I'm fixing them.

The direction taking looks good to me. Would it makes sens to create a new example for this use case intead of changing the existing one?

New example done.


cannot burn the bootloader to ATTiny

Hi,
we have purchased the NOKOLino at Maker Fair Berlin.
The issue is - we cannot burn the bootloader to the ATTiny.
We Use UNO Board, and all the wirings are made as shown.  The UNO board is working fine.
But when we try to burn the bootloader to AATiny45, which was in the package, we only get this errors:
avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
     System wide configuration file is "C:\Users\anstayk\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf"

     Using Port                    : COM4
     Using Programmer              : stk500v1
     Overriding Baud Rate          : 19200

avrdude: Send: 0 [30]   [20]
avrdude: Send: 0 [30]   [20]
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x03
avrdude: Send: 0 [30]   [20]
avrdude: ser_recv(): programmer is not responding
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x03
avrdude done.  Thank you.
Error while burning bootloader.
all the wiring between Arduino and ATTiny is double and triple checked (also with multimeter to confirm there is a connection)

Fixed it.
The IPS sketch was not successfully uploaded to the UNO

Well... i'm glad i could help ;-)
Have fun!


Person card needs click handler

Description

When PersonCard was made, it didn't have a click handler. On the persons page, when a PersonCard is clicked, it must navigate to that person's profile. Hence, a click handler needs to be added
Acceptance Criteria

[ ] PersonCard receives click
[ ] PersonCard navigates to the right person

Implementation details

n/a
Testing notes

n/a

LGTM


Fix unused/missing conditions of Heat CR

I've tested this PR in my local and confirmed all conditions become ready.


Add new page for Help

Describe the feature
In this we will add the FAQs part provide option for Need more help and also feedback form
Add ScreenShots
.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

hey @mahek0620 thank you for creating the issue.
As of now, we do not need it. We will let you know in the future if there is a need. Please search for another issue and raise it, which I'm happy to assign to you.


Parser fixes

Fixed a small thing

I mean, I'm not strictly opposed to the syntax, but it still think it is not a good idea.


Can we add legends ?

With a donut widget, can we add legends automatically ?
Thanks a lot !

It's possible that I could make it simple for you to inspect a chart's data from which you could build a legend - in this case automatic would mean do it yourself...

But if i do it myself, how can i match colors with the legends ?

That's what I'd have to make it simple for you to do :smile:


feat: add more test cases for my teams panel

@kurokn under integrations tab, the table has a status column and it shows the status of the integration. Please add a test to validate it. Different icon is displayed depending upon the integration status


Where to put .map files?

Hi,
I am experimenting with your Docker for Mapserver on a new Linux Centos 7 box. I am getting an error as follows:
msLoadMap(): Unable to access file. (/usr/local/mapserver/test.map)
Any advice on where the map files should be located?
Thanks!

Actually just fixed it! Using this "sudo docker exec -i -t mapserver bash" gets me in to the correct file system.


setup yarn caching

Closes #22
What?
This action allows caching dependencies and build outputs to improve workflow execution time.

added for unit-test and static analysis workflow

Why?
Saves time waiting for CI to pass on PRs

If we want to benchmark this I'll add a manual trigger with workflow_dispatch


Generational parser does not seem to handle GC Cause included in young event.

Describe the bug
When processing a line like:
5.374: [GC (Allocation Failure) [PSYoungGen: 262144K->28340K(305664K)] 262144K->28364K(1005056K), 0.0146665 secs] [Times: user=0.08 sys=0.00, real=0.01 secs]
GenerationalHeapParser.psYoungGen(GCLogTrace, String) is called and the offset (5) appears to not take into account the cause, resulting in:
May 01, 2024 10:03:19 AM com.microsoft.gctoolkit.parser.GCLogTrace getOccupancyBeforeAfterWithMemoryPoolSizeSummary
WARNING: Unable to calculate generational memory pool summary.
vert.x-eventloop-thread-0, not implemented: 5.374: [GC (Allocation Failure) [PSYoungGen: 262144K->28340K(305664K)] 262144K->28364K(1005056K), 0.0146665 secs]2024-05-01 10:03:19,806 [vert.x-eventloop-thread-0] INFO STDOUT: vert.x-eventloop-thread-0, not implemented: 5.374: [GC (Allocation Failure) [PSYoungGen: 262144K->28340K(305664K)] 262144K->28364K(1005056K), 0.0146665 secs]

with the following groups:
1: 5.374
2: null
3: null
4: 5.374
5: null
6: (Allocation Failure)
7: PSYoungGen
8: 262144
9: K
10: 28340
11: K
12: 305664
13: K
14: 262144
15: K
16: 28364
17: K
18: 1005056
19: K
20: 0.0146665

getOccupancyBeforeAfterWithMemoryPoolSizeSummary tries to convert null (5), "PSYoungGen" (7), and "K" to KByte values, which generates a NumberFormatException, and causing the notYetImplemented() logging.
To Reproduce
Steps to reproduce the behavior:

Attempt to load the attached file
sample.zip

Expected behavior
GCToolkit is able to properly parse the GC event.
Desktop (please complete the following information):

OS: Windows 11
Java 11 (Amazon Corretto)
GCToolkit tip (April 30, 2024)

Additional context
This is an older log file from Java 8/CMS that likely won't come up as frequently anymore, so it may be a lower priority.  It's not clear if this should be a feature request instead due to the fact this triggers "Not yet implemented" logging.

Similar issues with another file, slightly different in format.
218982.552: [GC [PSYoungGen: 463514K->98518K(531328K)] 2167820K->1805185K(2239360K), 0.0933556 secs]

parallel_simple_nostamps.zip
Sample file attached.

Before I get into some details, the log line you've posted is a PSYoung which is a parallel young gen collector. It is paired with the PSOld, the parallel old gen collector The ParNew collector is a young gen collector that is paired with the CMS collector. The concurrent mode failure is a single threaded Full GC
This is an odd error. We do have tests for this so I'm not sure how this was missed. Certainly @5 would give you an NPE. While that shouldn't  prevent the file from being parsed but it will mess up the event being generated.
How this works: The regex should precisely match the target line and it should not match any other line.The test for the rules make use of an array of an array of log lines. Each group of log lines in the inner arrays should match 1 rule and 1 rule only. Each individual rule is run over the entire array of arrays to ensure that it capture it's set of log lines (maybe a set of size 1) and that it doesn't capture any other set of log lines. I suspect that the log that you've pushed contains log lines that are missing from that test.
There is another set of tests that will take a GC log segment and ensure that the generated event contains the expected values. I would say that these log lines are missing from this test also. So a test failure that also should be corrected. I'll file an issue.

Thanks Kirk. (Switching to my work account, as this is where I'll be making the changes)
I've run the tests in GenerationalHeapParserTest, but it appears that this specific case is missing.  All test cases pass with or without my changes.  Because of this, I've added a test case for some lines from the files I'm using, which can be seen in the difference here: https://github.com/microsoft/gctoolkit/compare/main...jlittle-ptc:gctoolkit:gctoolkit-352
Also, I did some before/after runs (with debug on) for some of the files in the gclogs under preunified\ps\details and noticed the same sort of messages occurring there.  The following files generate "not implemented" messages, which are not exposed by the current test suite (all tests pass):

1047_2.log: 85970.989: [GC [PSYoungGen: 96879K->5527K(100480K)] 236639K->156157K(1032576K)
memoryleak2.log: 2011-08-07T18:30:17.711+0100: 15.973: [GC [PSYoungGen: 524160K->0K(524224K)] 2649456K->2133504K(20971456K), 0.0742930 secs]
932_def.par.wd.nt.log: 0.880: [GC [PSYoungGen: 12288K->1648K(14336K)] 12288K->1648K(47104K), 0.0093244 secs]

While I haven't tested every file, I have confirmed that the not implemented lines no longer occur for the above 3 files with my changes.
I did notice that the way the tests are checking for parsed lines, there doesn't seem to be a way to check the changes for the GC Failure.  The event doesn't get added to the event list, though it does get parsed successfully (NotImplemented error on Debug before, no error after)  I have some questions about detecting errors that I'll post in a discussion post so the knowledge isn't buried in a bugfix.
This is the first time I've contributed back to an OSS program, so hopefully you and your team don't mind a bit of hand-holding along the way.  I can put together a PR for my changes above, but wanted to make sure everything meets your expectations before I do so.

@karianna Should this bug be closed as fixed as the PR was accepted?


modifying admin-web.xml for atlas-ranger-plugin

Committer: zhangqiang2<EMAIL_ADDRESS>Overview
The source code of our contribution “Pull-Request” aims to solve the problem of manually copying ranger-atlas-plugin.jar, that is a prerequisite for using the ranger-atlas plugin, under the existing code.
For those who are new to ranger-atlas, one will always find difficult that the ranger's Web UI has no plugin connection after successfully installing the plugin. This problem always occurs, because there is no corresponding Atlas folder in the specified path of ranger-admin, and there is no ranger-atlas-plugin.jar in that Atlas folder. Meanwhile, ranger's official document does not provide any guidance to beginners, to tell them to copy the jar package to the specified path, leading to many developers can not use some parts of the ranger functionalities.
Our open source contribution that only modifies a small part of source code can directly generate the corresponding Atlas folder and jar package. It means that by using our contribution, developers no need to manually create a folder and import the relevant jar package. In this way, this can bring good convenience to the developers and users.
Implementation Details
Existing Problem (Motivation of this Contribution):
After installing the ranger-atlas plugin, the connection failure will be displayed on the ranger's Web UI view the installation log and found an error:
atlas failed to find service class org.apache.ranger.services.atlas.RangerServiceAtlas. Resource lookup will not be available. Please make sure plugin jar is in the correct place.
Later one cannot fine the Atlas file in the following directory :
ranger-0.6.2-SNAPSHOT-admin/ews/webapp/WEB-INF/classes/ranger-plugins
To solve this problem, one can only manually create the atlas folder and import the ranger-atlas-plugin.jar package, which is not convenient for the end user.
Our Solution/Contribution:
Download incubator-ranger code directly from gitHub，Open it with compiler in src-main-assembly file path of admin-web.xml, as follows:

The code of admin-web.xml is related with Ranger, and compiled automatically to generate the component folder. For example, the following figure is related to Yarn.

We then add the following Atlas-related code:

The code set the output path, the permissions of some file, the contents of folder contains, etc.
Verification:
Re-compile the code, reinstall the ranger, atlas and ranger-atlas-plugin and start. First, the specified path has been automatically generated as Atlas folder, and the folder already has ranger-atlas-plugin.jar：

Second, the Ranger Web UI shows a successful connection, which shows that our implementation is correct.

@zhangqiang2 Thanks for submitting the patch and for the detailed description.

Apache Ranger is currently NOT setup to use pull requests to take in the changes for commit.
Please use the apache review board to submit your code changes for review and commit.
Also create a jira to go along with the review and mention it in the review board review.


[SourceKit] Guard the ASTBuildOperation’s state with a mutex

The OperationState is accessed from multiple threads and TSAN was reporting race conditions. Let’s guard it using a mutex.

@swift-ci Please smoke test


fsc netcore crash (stackoverflow), .net full works

Trying to build with .net core sdk 2.0 fsc, crash with stackoverflow
as a note, using .net full build correctly
Repro steps
dotnet new console -lang F#
dotnet add package FSharp.Data

now
dotnet build

Expected behavior
Build (hopefully), but for sure not a SO crash
Actual behavior
SO crash
         Process is terminating due to StackOverflowException.
     1>C:\Program Files\dotnet\sdk\2.0.0\FSharp\Microsoft.FSharp.Targets(224,9): error MSB6006: "RunFsc.cmd" exited with code -1073741571. [e:\temp\reproso\reproso.fsproj]

Known workarounds
instead, doing
msbuild /t:Build

works.
Related information
> dotnet --info

.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0

  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

> msbuild /version

Microsoft (R) Build Engine version 15.3.409.57025 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

15.3.409.57025

I think this is a duplicate of #3303 ?

Fixed:  https://github.com/Microsoft/visualfsharp/pull/3658

@KevinRansom this is the fix which was merged into the CLI's 15.5 branch, correct?

No ... we should do a new merge though

Thanks!


Allow dockerfile on deploy

What should we add or change to make your life better?
I need to use a custom image when deploying
Here:
https://github.com/dotnet/tye/blob/master/docs/reference/schema.md#dockerfile-string
States that dockerfile is only for run.
Need it for deploy as well.
Why is this important to you?
My containers need to be custom.  Custom dependencies installed, etc.
azsdke2e
azsdke2e2

I need this as well, thanks.


Multi controls

This PR adds the ability to specify multiple controls on a plugin.
This solves two problems:

better organization of cell controls if there are a lot of properties
Make it possible to add functionality to all plugins (see https://github.com/react-page/react-page/issues/904)

E.g. its possible to add padding controls to all plugins:

I decided to use vertical tabs, because vertical space is rare in the bottom toolbar. Having the tabs on the left saves us some space.
This PR additional fixes some styling problems on mobile and adds documentation about the new feature (+ some undocumented stuff)

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on:

v2.0.0-beta.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


Amazing Project

Hi
A huge well done on training this model, It works really well and is incredibly useful
I work at a recording studio and I've used drumsep to supercharge my recording workflow - I use it on every drum recording or drum mixing session in some way.
I mainly use it to de-bleed drum stems and it does an awesome job, but it works really well as a reference tool for songs that don't have multitracks available. I use it alongside HTDemucs to really break down reference mixes!
Are you done with this project? I'm really interested in building a similar model or perhaps fine tuning yours, but I'm struggling to set up demucs for training and could use some help! I have access to a massive bank of training data and I'm good with programming concepts, but I don't really understand that demucs training documentation, or maybe I'm missing something.
If you're able to give me a rough guide of how you used demucs to train the model, I would really appreciate that!
Also, since there is now a 6 source Demucs model, as you managed to train this model, do you think it would be possible theoretically to further break down drum sources potentially with more specific training data? I.e kick, snare, toms, hihat, cymbals, percussion (tambourine/shaker)?
Again, thanks for this, it's become a really valuable tool!

Thank you very very much! I'm glad that you found drumsep useful. I would like to know a bit more about how you use it to de-bleed drum stems!
Setting up and training Demucs can be a bit of a headache, especially if you don't have a powerful GPU. I trained the Hybrid Demucs version, to do it I followed the recommendations in these two Issues: Issue 1 and Issue 2. Also, you might find this doc useful.
In response to the question regarding the separation of more sources, you can set any amount of sources (if you have the corresponding data), but the more you try to separate, the less difference there is between the audio signals, and so the harder it is for the model to discriminate between them. In my experience, hi-hats and cymbals can be very difficult to discriminate against. But I think that a well-trained model with the correct dataset should achieve great results.
If you have more specific questions, you can ask me anything. You can also e-mail me at<EMAIL_ADDRESS>And yes, I'm currently working on this project, and I want to train a second model with more data and for more epochs!

Hi, thank you so much for getting back to me! Very much appreciated, I will have a look at those links!
I have sent you an email, just letting you know in case it goes to your junk folder :)
Cheers!

Whoa!!! Great work!!! What is the licensing on these models? My perhaps poor understanding is that right now the models that Facebook's hybrid Demucs uses is for educational purposes, which I imagine is why there isn't a single iOS app out there powered by Demucs. However if you created your own models and are now putting it out there for anyone to download, there could be a situation where people are monetizing on your hard work.


cis-operator doesn't support Kubernetes cluster managed by Scaleway

Hi,
cis-operator works only with providers declared here : https://github.com/rancher/kubernetes-provider-detector/tree/master/providers
Having a Kubernetes cluster managed by Scaleway, my cluster can't launch cis-operator. When executing, getting this error :
time="2021-07-23T09:33:28Z" level=info msg="Starting CIS-Operator"
time="2021-07-23T09:33:29Z" level=fatal msg="Error building controller: unknown provider"

Shouldn't the start be allowed even if the detection of the provider fails ?
Thank's.

Same here using OVHCloud managed Kubernetes cluster. Thanks for the trick @xom4ek !

Same here using OVHCloud managed Kubernetes cluster. Thanks for the trick @xom4ek !

@manicole What did you do to resolve? I don't understand the fix. Can you share how you did it? Thank you.

Hi @manicole !
What label did you put on OVH nodes ?
Thanks !

I'm getting this problem on a self hosted cluster (kubespray)

I'm getting this problem on a self hosted cluster (kubespray)

Hi @belaw! just applying @xom4ek  fix solved the issue

k label node MYNODE kubernetes.azure.com/cluster=""

I'm getting this problem on a self hosted cluster (kubespray)

Hi @belaw! just applying @xom4ek fix solved the issue

k label node MYNODE kubernetes.azure.com/cluster=""

Hi @C-Romeo, thanks, I should have mentioned that I already figured that out 😁 and I just wanted to push this issue because the node label makes the cluster look like a cloud based cluster when you view it in Rancher.

The question on this one is, "do we want to implement a programatic version of the work around so that the operator doesn't fail when provider is unknown?"
this issue was release noted (i'm verifying the veracity of that statement ;) ), and the workaround noted resolves the issue. https://github.com/rancher/cis-operator/issues/103#issuecomment-1222771391


darwin.adv_cmds: restore locale data

This is a follow up to https://github.com/NixOS/nixpkgs/pull/346043 to add the missing locale data. It’s not exactly the same as the data used on macOS, but it’s close. This is being done separately in case the PR is rejected.
Replacement for https://github.com/NixOS/nixpkgs/pull/347642.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I will merge this in a bit (trying to avoid a stdenv rebootstrap right now).


Add Flex/AnyFlex pin drivers

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[x] My changes were added to the CHANGELOG.md in the proper section.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
This adds a Flex/AnyFlex pin driver to fix #740
Testing
The GPIO HIL-test exercises the new driver. Doesn't seem to deserve a dedicated example

I think we need much more documentation in this module. Looking at the docs with this branch included:

I can't even imagine trying to figure out which pin type I need as a user who is not familiar with the HAL. I don't even really know what half of these types do, honestly.

I can't even imagine trying to figure out which pin type I need as a user who is not familiar with the HAL. I don't even really know what half of these types do, honestly.

I have a few ideas for improving the docs here and also on the "landing page" to help new users to have a smooth(er) start. But well - not in this PR (and we should generally wait for the doc-test PR to land before shuffling around docs I guess)
But it's definitely already much easier than the into_XXX API we had before

I think the docs topic touches #742

I opened https://github.com/esp-rs/esp-hal/issues/1660 to track the module level doc improvements


ActiveMQ failover correct parameters in connection URI

Not all parameters are for failover and some of them must be set on server basis. As was discussed in #4430

Merged/cleaned up locally. thanks!


2024-10-11_01-35-35_master-next_amazon-kvs-producer-sdk-cpp

Automatically created.

Successfully created backport PR for kirkstone-next:

#9916

Successfully created backport PR for scarthgap-next:

#9917

Successfully created backport PR for styhead-next:

#9918


Project: Restaurant page

Remember to run npm install.

Hello,
Having in mind the DRY rule, I didn't create a <div> element for each tab. What I did was to create one <div> and then emptying it, and afterward appending the corresponding components to it, to later add that element into the container. I think in this way, I wouldn't have to create a <div> item for each module. I did the change to create one file for each module and kept the main file (index.js) as clean as possible.
Thanks!

Thanks, @MauricioRobayo !
I made the necessary changes to the project, hence:

Inject the tabs.
Create a div for each injected content generated in each tab.

and also made the optional changes:

Use of append instead of appendChild (in most cases).
Use of textContent instead of innerHTML (except where it was needed before I included some  in the contact information).
Erased the comments for the style.scss file.

💯


Completed lists task

Hey MLCC guys check out the lists assignment i completed

Numpy Exercise Q4. Your output is different than expected output see for hint


Default avatar would be better as auto generated gravatar

Default avatar would be better as auto generated gravatar rather than the default image. It would add vibrancy to the forum.

Done ... if you enable the default avatar you can also then use the gravatar generated one in place of the shadow bust image.  You can choose the gravatar generation set as well.

That was quick 👀
I used the gravatar setting for the first time, and thought wow - this would make it seem so much more alive. :D

I agree !  I should get the site updated this weekend, that change will be reflected then.
Going to close this one as complete.


Put current input into history instead of current selected candicates.

When a candicate is selected, add the current input to history
instead of the current candicate.
This will behave like ivy/helm, and is more reasonable and convenient.
For example, press C-h f and then input selectrum-, then you can select
selectrum-read and read about it. Later, you can pass C-h f again and
followed M-p to continue selecting and reading other functions starting
with selectrum- quickly.

The current behaviour is intentional but I understand that there are reasons to favour restoring previous searches in some cases. One problem is that search results can change over time because a dynamic completion table can return different results. With M-p, M-n and M-r you should be able to always select the exact candidate you submitted previously (this behaviour is also consistent with the default interface).
We can think about adding this feature separate from regular history navigation. Maybe we could have a global list of previous search patterns instead which could be navigated using similar commands like for history navigation.

I originally wanted to change the way of adding history to input,
because the default behavior is basically useless during dynamic completion.
For example, for many commands in the WIKI, sometimes the
dynamic completion's candidates are very redundant, making it very
difficult to select through M-n. This kind of experience is very
unfriendly, so I miss the ivy/helm way a bit.
Maybe we can add a custom variable like selectrum-history-style to allow users
to choose howto through configuration. Although not perfect, but practical enough.
In addition, in this way, when others use selectrum-read to create their own
commands, they can let-bind selectrum-history-style to determine the style of history
insertion.

I originally wanted to change the way of adding history to input, mostlly
because the default behavior is basically useless during dynamic completion.

I don't think they are useless, I often use them.

For example, for many commands in the WIKI, sometimes the
dynamic completion's candidates are very redundant, making it very
difficult to select through M-n. This kind of experience is very
unfriendly, so I miss the ivy/helm way a bit.

Only helm does this, I tested with a recent version of ivy and it seems it behaves like selectrum now, although I remember they didn't in the past. What do you meant by redundant here? If you want to avoid duplicates you can use history-delete-duplicates.

Maybe we can add a custom variable like selectrum-history-style to allow users
to choose howto through configuration. Although not perfect, but practical enough.

I would prefer to have both options I think (history navigation and search pattern navigation). A global search pattern history would also be useful to search for the same things in another context.

Oh, I think I get why you think they are useless now. For some commands the selected candidate is indeed useless like for swiper like ones.

Maybe there is a problem with my description, sorry.
Regarding ivy, it has always been to insert input into the history. I
have always used it before. Of course, it may have changed recently.
Because I have been using selectrum these days, it is very good, but
in some places I am not very used to it, so I hope it will be better
and better.

I understand it better now and I checked swiper which does save the input, too. So ivy still behaves like this for commands like swiper which makes sense. In the light of commands like this I think having a variable to control the history behaviour is a good idea.

I think we could reduce the option to a boolean variable called selectrum-use-input-as-history-p. It should be intended to be let bound by interactive search commands for which the regular behaviour doesn't make sense.

At the very beginning, I also wanted to set it to boolean type. Changed to choiced symbol just for possible future other styles (although they don't seem to be).
Of course, the Boolean type will make the code and settings concise. I respect your
opinion.
Can you please continue to modify and merge the code? The local lint does not work very well here, so submitting the code is a bit troublesome for me.

I can do that no problem. But I would like to wait for input from @raxod502 on this. I also had another idea: We could always save the input as a text property of the history item. After a quick test this seems to work, well. Then we could add three commands to get the prev/next input or to complete against the history of inputs (maybe mapped to C-M-n, C-M-p and C-M-r). WDYT? This would avoid the need for the caller to think of this variable and if you always prefer to get the input history you could just remap M-p, M-n and M-r to those commands.

I don't really agree with this idea. First of all, I think there is really noneed to introduce so many new commands for this, which may cause the
code to become more and more bloated. Secondly, I feel that using text property too much to pass properties is not a good way.
Finally, this will make those who use selectrum-read to write their commands and want to use input as history, have to bind commands one by one each time, which is very troublesome.
In the previous method, only one selectrum-history-style variable needs to be paid attention to.

First of all, I think there is really noneed to introduce so many new commands for this, which may cause the code to become more and more bloated.

New functionality doesn't make code bloated in my opinion but there could also be just one command to toggle the behaviour.

Secondly, I feel that using text property too much to pass properties is not a good way.

I can't think of a technical argument against using text properties here.

this will make those who use selectrum-read to write their commands and want to use input as history, have to bind commands one by one each time, which is very troublesome

You wouldn't have to bind anything, the user would have full control to use input history or history of chosen values.

I actually find the "what you actually typed" history far more useful, because prescient.el already shows my history of selected candidates at the top, but compliance with the default completing-read is a reasonable argument against that behavior. If there were a convenient variable to swap which of the two modes is the default, then that would be ideal I think.

I also see that is more useful in many circumstances. I think having both options in selectrum but keep the default format is a good solution. For example if you deactivate selectrum or use another completion engine, history based on input would be broken.

we could perhaps have some mechanism by which the standard bindings will delegate to either of the two available history rings depending on a variable that could be configured per-command

Maybe we could combine that with your idea of a variable to swap which of the two modes is the default so we would have only one variable like selectrum-history-use-input. Users can set it to their desired default and commands can also enforce a specific history usage by binding it to a different value. The only problem is with recursive minibuffers again so to really only set this for the very next session one would need to set the variable in minibuffer-with-setup-hook like with selectrum-should-sort-p.

I can't think of a technical argument against using text properties here.

My opinion, too many text properties may trigger more gc, not everyone's machine
is high-performance.
Others, I also agree with @raxod502.

Users can set it to their desired default and commands can also enforce a specific history usage by binding it to a different value

Seems like a reasonable start. Hopefully, we will not find any situations where a command wants to enforce a specific usage and then the user wants to do it the other way. If we don't find any, then we've solved the problem!

so to really only set this for the very next session one would need to set the variable locally in minibuffer-with-setup-hook

Mayhaps this situation is getting a bit ridiculous. Maybe we should introduce a macro for binding Selectrum variables, which would take care of the minibuffer-with-setup-hook automatically, and say that's the only supported way of setting them?

My opinion, too many text properties may trigger more gc, not everyone's machine is high-performance

The GC caused by sorting and filtering (~ 10,000) is not just one but several orders of magnitude more than the GC caused by propertizing each history candidate (~10). This change will have no impact on performance.


Best practices for grapqhl requests

Http client throws exceptions in general (e.g: not found) but an error on grapqhl is returning 200 without a data but with a GraphQLError type.
Would it not be better to pass an exception with errors list in it, so it could pass by the error handler of the http client as others ? Otherwise for every grapqhl a manual null checks will be required if you don't implement in the first place it will look like a simple NPE 🤔
In general, I could not find any documentation for usage of grapqhl and handling errors of it, what do you think best way to handle ? Also some utilities like to chunk or paginated grapqhl requests might be really helpful. Is there a plan to provide those as part of the SDK ?
I've done a POC here for the aforementioned cases.

There are some possible ways to go here.
One is to create a specific middleware that checks if in the response body the error field is not empty and raises an exception. But as the data field could still be filled this may be not wanted.
Another one is using a thenApply and first check for the errors field and raise an exception. You could even put this inside a method to be referenced as lambda.
The third option is to directly deserialize to a class structure representing the queried data.
And last but not least use one of the many GraphQL client libraries for Java which help in either creating the response classes or writing the queries based on the models. E.g.: Netflix DGS or Apollo Java client


Add CLI commands for schema registry

@jerrypeng @srkukarni please help review this

retest this please

@srkukarni @merlimat can you review this PR again?

retest this please

@mgodave can you add the missing headers to the files

@mgodave Example of CLI params:
https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdTopics.java#L268
and for Java API: https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-admin/src/main/java/org/apache/pulsar/client/admin/Topics.java#L523

@jerrypeng : I pushed a commit to fix the license headers.
@merlimat : I think the CLI is following the pattern in functions CLI. I guess the big question here will be how to make those CLI commands consistent with @jerrypeng @srkukarni . I think we can move forward with this PR and have a separate PR on addressing this.
thoughts?

I think the schema is not confined to be used from functions. We should have a common convention to for CLI and Java APIs. For schema I'd rather stick with the topic convention. That also ensures the short naming form can be respected as well.

@srkukarni @jerrypeng @merlimat please review the latest PR.
I changed the schema admin interfaces followed @merlimat 's review comments with some bug fixes.
added an integration tests on schema CLI to make sure basic create/get/delete/get work

all CI jobs passed.

@merlimat please review the latest change.


Fix dependency erros and simplify code.

Fix golint and gosec dependencies.
Simplify code as suggested by gosimple.
Fix comments.

Excellent.


save hoomd_xml files

In the ethane.py example it is possible to save .top and .gro files. It would be nice to save hoomd_xml, gsd and lammpsdata files as it is done in mbuild.

In mBuild when saving as .hoomdxml, .gsd, and .lammpsdata the save function is calling internal save_hoomdxml, save_gsd, and save_lammpsdata writers that actually take a ParmEd structure as an argument rather than an mBuild Compound (this conversion is performed within mBuild prior to calling the individual writers).  So it should be easy to support saving ParmEd structures in these formats.  However, in the long term what we would like to do is to add the save_hoomdxml, save_gsd, and save_lammpsdata functions to ParmEd, so that ParmEd is handling all of the saving.  These are only incorporated into mBuild right now because ParmEd does not have writers for these file formats.  I'm sure @ctk3b has a vision for how we should handle this in the short term, but it might be time for us to work on actually adding these writers into ParmEd

I think adding the writers into ParmEd makes the most sense long term but short term would it be easier to copy writing code from mbuild or import the mbuild save_hoomdxml function?

My mistake, the functions are write_hoomdxml, write_gsd, and write_lammpsdata.
As @mikemhenry suggested, these can be imported by using:
from mbuild.formats.hoomdxml import write_hoomdxml
from mbuild.formats.gsdwriter import write_gsd
from mbuild.formats.lammpsdata import write_lammpsdata
These functions are not currently included in the mBuild documentation, but we have actually been working on updating the documentation today, so I can make sure that soon information is available for those functions so you will know what arguments to pass.

Thanks! @evanmiller326 and I are presenting mbuild and foyer to our lab today and hoomd is pretty critical to our workflow.

Okay for now then (since we won't have the docs updated for a bit) it would probably be best to look at the source code for mBuild (in the formats directory).  The writers are pretty well documented there, so that should give you an idea of what arguments you will need to pass to them.

I'm gonna close this now but for the record the straightforward way to access these writers is with Compound.save
E.g.
ethane.save('ethane.hoomdxml', forcefield_name='oplsaa')
ethane.save('ethane.hoomdxml', forcefield_files='my_ff.xml')


#70 add workaround description for Spring Boot >= 1.5.x

Codecov Report

Merging #72 into master will not change coverage.

@@            Coverage Diff            @@
##             master     #72    +/-   ##
=========================================
  Coverage      40.6%   40.6%
- Complexity        0     336   +336
=========================================
  Files            64      64
  Lines          1751    1751
  Branches        414     341    -73
=========================================
  Hits            711     711
  Misses          935     935
  Partials        105     105

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 36640a2...c26cfc3. Read the comment docs.

@derjust will be a release for Ingalls ?


Adding support for NTLM hashes during ingestion

Description

Adding support for NTLM hashes during ingestion
Code Cleanups

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1097b85). Click here to learn what that means.
The diff coverage is 15.49%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #177   +/-   ##
=======================================
  Coverage        ?   36.05%
=======================================
  Files           ?       27
  Lines           ?      796
  Branches        ?        0
=======================================
  Hits            ?      287
  Misses          ?      509
  Partials        ?        0

Files Changed
Coverage Δ

...s/Functions/Ingestion/ProcessPwnedPasswordEntry.cs
0.00% <0.00%> (ø)

...unctions/Functions/Ingestion/ProcessTransaction.cs
0.00% <0.00%> (ø)

Functions/Implementations/Azure/BlobStorage.cs
14.28% <0.00%> (ø)

Functions/Implementations/Azure/QueueStorage.cs
0.00% <0.00%> (ø)

Functions/Implementations/Azure/TableStorage.cs
0.00% <ø> (ø)

Functions/Models/QueuePasswordEntry.cs
0.00% <0.00%> (ø)

Functions/Functions/Range.cs
38.46% <33.33%> (ø)

.../HaveIBeenPwned.PwnedPasswords.Shared/HashEntry.cs
79.76% <100.00%> (ø)


Appearance.setColorScheme not workin in RN Web

Edit: I wrote the wrong RN version. I have edited the right one! I'm currently using the newest one since I stared the project few days ago!
Description
Appearance.setColorScheme("dark") works perfectly fine for iOS and Android but raises the following Error when used for RN web even thought its written in the documentation that it works for web.
_Appearance.default.setColorScheme is not a function. (In '_Appearance.default.setColorScheme("dark")', '_Appearance.default.setColorScheme' is undefined)
Steps to reproduce

Create a Pressable
onPress={Appearance.setColorScheme("dark")}
Observe error in RN web

React Native Version
0.74.3
Affected Platforms
Runtime - Web
Output of npx react-native info
System:
  OS: macOS 14.0
  CPU: (8) arm64 Apple M2
  Memory: 83.52 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.4.1
    path: /opt/homebrew/bin/node
  Yarn: Not Found
  npm:
    version: 10.8.2
    path: ~/.npm-global/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10811636
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 19.0.2
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs
Uncaught Error
_Appearance.default.setColorScheme is not a function. (In '_Appearance.default.setColorScheme("dark")', '_Appearance.default.setColorScheme' is undefined)
Call Stack

Source Map
This call stack is not symbolicated. Some features are unavailable such as viewing the function name or tapping to open files.
index
http://localhost:8081/node_modules/expo-router/entry.bundle:153573:52
renderWithHooks
http://localhost:8081/node_modules/expo-router/entry.bundle:25695:33
mountIndeterminateComponent
http://localhost:8081/node_modules/expo-router/entry.bundle:28984:34
beginWork$1
http://localhost:8081/node_modules/expo-router/entry.bundle:35239:29
performUnitOfWork
http://localhost:8081/node_modules/expo-router/entry.bundle:34509:29
workLoopSync
http://localhost:8081/node_modules/expo-router/entry.bundle:34432:28
renderRootSync
http://localhost:8081/node_modules/expo-router/entry.bundle:34405:25
recoverFromConcurrentError
http://localhost:8081/node_modules/expo-router/entry.bundle:33897:40
performConcurrentWorkOnRoot
http://localhost:8081/node_modules/expo-router/entry.bundle:33810:54
workLoop
http://localhost:8081/node_modules/expo-router/entry.bundle:37546:48
flushWork
http://localhost:8081/node_modules/expo-router/entry.bundle:37524:28
performWorkUntilDeadline
http://localhost:8081/node_modules/expo-router/entry.bundle:37761:48
Showing all frames
Component Stack

Source Map
This call stack is not symbolicated. Some features are unavailable such as viewing the function name or tapping to open files.
index
http://localhost:8081/node_modules/expo-router/entry.bundle:153566:43
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:65953:44
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:66319:41
StaticContainer
http://localhost:8081/node_modules/expo-router/entry.bundle:165743:17
EnsureSingleNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:163244:34
SceneView
http://localhost:8081/node_modules/expo-router/entry.bundle:165668:13
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
Background
http://localhost:8081/node_modules/expo-router/entry.bundle:167963:43
Screen
http://localhost:8081/node_modules/expo-router/entry.bundle:169069:73
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
<unknown>
ResourceSavingScene@http://localhost:8081/node_modules/expo-router/entry.bundle:168879:43
MaybeScreen
http://localhost:8081/node_modules/expo-router/entry.bundle:194647:43
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
MaybeScreenContainer
http://localhost:8081/node_modules/expo-router/entry.bundle:194632:43
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
AnimatedComponent
http://localhost:8081/node_modules/expo-router/entry.bundle:137743:14
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
AnimatedComponent
http://localhost:8081/node_modules/expo-router/entry.bundle:137743:14
Dummy
http://localhost:8081/node_modules/expo-router/entry.bundle:194577:30
Drawer
http://localhost:8081/node_modules/expo-router/entry.bundle:195353:13
DrawerViewBase
http://localhost:8081/node_modules/expo-router/entry.bundle:193870:12
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
SafeAreaProviderCompat
http://localhost:8081/node_modules/expo-router/entry.bundle:168965:25
DrawerView
http://localhost:8081/node_modules/expo-router/entry.bundle:194056:43
PreventRemoveProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:164734:14
NavigationContent
http://localhost:8081/node_modules/expo-router/entry.bundle:165449:18
<unknown>
http://localhost:8081/node_modules/expo-router/entry.bundle:165465:31
DrawerNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:193742:57
<unknown>
http://localhost:8081/node_modules/expo-router/entry.bundle:65839:41
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
GestureHandlerRootView
http://localhost:8081/node_modules/expo-router/entry.bundle:188967:43
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:65953:44
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:66319:41
StaticContainer
http://localhost:8081/node_modules/expo-router/entry.bundle:165743:17
EnsureSingleNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:163244:34
SceneView
http://localhost:8081/node_modules/expo-router/entry.bundle:165668:13
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
Background
http://localhost:8081/node_modules/expo-router/entry.bundle:167963:43
Screen
http://localhost:8081/node_modules/expo-router/entry.bundle:169069:73
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
SafeAreaProviderCompat
http://localhost:8081/node_modules/expo-router/entry.bundle:168965:25
NativeStackView
http://localhost:8081/node_modules/expo-router/entry.bundle:167645:13
PreventRemoveProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:164734:14
NavigationContent
http://localhost:8081/node_modules/expo-router/entry.bundle:165449:18
<unknown>
http://localhost:8081/node_modules/expo-router/entry.bundle:165465:31
NativeStackNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:161280:43
<unknown>
http://localhost:8081/node_modules/expo-router/entry.bundle:65839:41
ThemeProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:166733:30
RootLayout
http://localhost:8081/node_modules/expo-router/entry.bundle:159820:45
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:65953:44
Route
http://localhost:8081/node_modules/expo-router/entry.bundle:66319:41
View
http://localhost:8081/node_modules/expo-router/entry.bundle:39052:26
NativeSafeAreaProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:160992:19
SafeAreaProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:160865:45
wrapper
http://localhost:8081/node_modules/expo-router/entry.bundle:73992:46
EnsureSingleNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:163244:34
BaseNavigationContainer
http://localhost:8081/node_modules/expo-router/entry.bundle:161911:13
ThemeProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:166733:30
NavigationContainerInner
http://localhost:8081/node_modules/expo-router/entry.bundle:74246:25
ContextNavigator
http://localhost:8081/node_modules/expo-router/entry.bundle:74026:43
ExpoRoot
http://localhost:8081/node_modules/expo-router/entry.bundle:73981:41
_HelmetProvider
http://localhost:8081/node_modules/expo-router/entry.bundle:201567:12
AppContainer
http://localhost:8081/node_modules/expo-router/entry.bundle:51978:24
Showing all frames

Screenshots and Videos
No response

Appearance.setColorScheme("dark") works perfectly fine for iOS and Android but raises the following Error when used for RN web even thought its written in the documentation that it works for web.

Hi,
Thanks for reporting this issue.
It seems like this issue is actually unrelated to React Native core but related to React Native Web. Please open this issue against this other repository:
https://github.com/necolas/react-native-web/issues
I'll be closing this but feel free to comment if the other repo points back to us as a issue in the core of React Native.

Thank you!
Out of curiosity: Is someone checking the RN Web issues? Seems like no one is answering there since a few weeks!


Add a link to amonguscapture-gtk to the readme plz

Belongs in the amonguscapture repo; happy to review a PR over there, but I'll close this issue

Belongs in the amonguscapture repo; happy to review a PR over there, but I'll close this issue


Mac OS's icon files in flutter project causes exception and breaks flutter --run

Mac OS's "Icon\r" file in flutter project causes exception when running an app with flutter --run. "r" and "R" to refresh doesn't work when this happens.
Exception from flutter run: FormatException: Invalid HTTP header field value: "lib/res/images/Icon\r"

I'm not entirely sure what this mean.  Maybe @danrubel knows?

If you create an Icon\r file on Mac in the lib/res/images/ directory, then flutter run fails.
Running lib/main.dart on iPhone SE...
Application running.
Type "h" or F1 for this help message; type "q", F10, or ctrl-c to quit.
Type "r" or F5 to perform a hot reload of the app, and "R" to restart the app.
Type "w" to print the widget hierarchy of the app, and "t" for the render tree.
Syncing files to device...
 I believe that they are an artifact of the Mac Finder and should not be considered part of the application, but wanted to check before I filter them out from the device.

Looks like a kind of file we should ignore:
http://apple.stackexchange.com/questions/31867/what-is-icon-r-file-and-how-do-i-delete-them
There may be other file types we should be ignoring for the dev file server, or maybe we just need to be http encoding their names (since in this case looks like an http error due to lack of encoding).

Support for encoded paths in the server code is up. After that lands I'll fix flutter_tools to send the path encoded.


Multiline string with JSON() results in invalid Json if the string contains an extra line

Bicep version
Bicep CLI version 0.3.126 (a5e4c2e567)
Describe the bug
If you use a multline string that contains json then use the ARM json() function to convert it to an object, the object is different depending on the last line.
//Good Array
var jsonStringGood  = '''
[
  "one",
  "two",
  "three"
]'''

//Bad Array
var jsonStringBad  = '''
[
  "one",
  "two",
  "three"
]
'''

To Reproduce
//"flat" string
var jsonStringFlat  = '["one","two","three" ]'

//Good Array
var jsonStringGood  = '''
[
  "one",
  "two",
  "three"
]'''

//Bad Array
var jsonStringBad  = '''
[
  "one",
  "two",
  "three"
]
'''
var jsonArrayFlat = json(jsonStringFlat)
var jsonArrayGood = json(jsonStringGood)
var jsonArrayBad = json(jsonStringBad)

output flatArray array = [for (name, i) in jsonArrayFlat: {
  element: name
}]

output goodArray array = [for (name, i) in jsonArrayGood: {
  element: name
}]

output badArray array = [for (name, i) in jsonArrayBad : {
  element: name
}]

Bicep build this, then deploy:
DeploymentName          : testDeploy
ResourceGroupName       : BicepTesting
ProvisioningState       : Succeeded
Timestamp               : 3/24/2021 4:04:45 AM
Mode                    : Incremental
TemplateLink            :
Parameters              :
Outputs                 :
                          Name             Type                       Value
                          ===============  =========================  ==========
                          flatArray        Array                      [
                            {
                              "element": "one"
                            },
                            {
                              "element": "two"
                            },
                            {
                              "element": "three"
                            }
                          ]
                          goodArray        Array                      [
                            {
                              "element": "one"
                            },
                            {
                              "element": "two"
                            },
                            {
                              "element": "three"
                            }
                          ]
                          badArray         Array                      [
                            {
                              "element": [
                                "one",
                                "two",
                                "three"
                              ]
                            }
                          ]

DeploymentDebugLogLevel :

Additional context
This might purely be an issue with the json() function but I also believe is a confusing aspect of the Multiline syntax.
As primarily a PowerShell user, multiline strings don't include an extra \n on the end of the line
PowerShell
PS C:\> $a = @"
>> test1
>> test2
>> "@

PS C:\> $a + "|"

test1
test2|

Bash is a little more obvious
bash
$ cat test.sh
line="Test1
Test2"
echo "$line|"
$ ./test.sh
Test1
Test2|
$ cat test2.sh
line="Test1
Test2
"
echo "$line|"
$ ./test2.sh
Test1
Test2
|

vs bicep
Bicep
//Array in JSON String
var pipe = '|'
var myVar  = '''
test
'''
var myVar2  = '''
test'''
output out1 string = '${myVar}${pipe}'
output out2 string = '${myVar2}${pipe}'

Outputs                 :
                          Name             Type                       Value
                          ===============  =========================  ==========
                          out1             String                     test
                          |
                          out2             String                     test|

Great catch, and thanks for providing all the detailed information from your testing! As far as I can tell this happens when:

Variables are being used
The JSON array contains some whitespace (spaces or new lines) after the closing ].

The multiline syntax obviously makes this much easier to run into, because it usually includes a terminating newline.
Here's another minimal repro:
var whatIsMyValue  = '[""one"",""two"",""three""] '
output whatIsMyValue array = json(whatIsMyValue)

This needs a fix in the ARM expression library that Bicep uses to generate string expressions. I've submitted a fix for it there, and will update + add a test in this repo when merged.


Database Seeding

I was a bit stunned while using the permissions, which are seeded with the package.
It should be always the same direction and follow the same rule like:
{{model}}-{{action}}
Like this it follows more the convention of first the model and then the action.
Status
$roles = [
            'admin' => ['create-post', 'post-edit', 'post-delete', 'post-update'],
            'user' => ['create-user', 'user-edit', 'user-delete', 'user-update'],
        ];

Proposition
$roles = [
            'admin' => ['post-create', 'post-edit', 'post-delete', 'post-update'],
            'user' => ['user-create', 'user-edit', 'user-delete', 'user-update'],
        ];

If Accepted
If accepted I would make the needed changes and send in a Pull Request.
Additional Thoughts on seeding.
The Seeding Table shouldn't be a mandator part of php artisan erag:publish-permission, this should be made optional with a --seed option or published as a DatabaseSeeding file.

Thank you for your input! Your changes are accepted. Please go ahead with the modifications and submit a Pull Request.
Additional Thoughts on seeding.
Thank you for your suggestions! I completely agree with your proposition regarding the seeding table. It shouldn’t be a mandatory part of the php artisan erag:publish-permission command. Instead, we should make it optional by adding a --seed option or allowing it to be published as a separate DatabaseSeeding file.
This way, users can choose to publish the seeder if they want to include it in their setup.
Looking forward to your modifications and the Pull Request!

Thank you both for your valuable input and collaboration!
@Houbsi, I appreciate your proposal on standardizing the permission names to follow the format {{model}}-{{action}}. This definitely makes sense, as it enhances the consistency and clarity of the permissions. Let's proceed with this change.
Regarding the seeder, I agree with the idea of making it optional. Allowing users to include the seeder with a --seed option or publishing it separately ensures flexibility and better customization. I will review the changes as soon as you submit the Pull Request.
Thanks again for your contributions. Looking forward to working with you to improve the package!

@Houbsi
{{model}}-{{action}} Are you working on this feature?

Yes, sorry I'm on nightshift duty atm. I had the weekend planned for it.

Hi mate @Houbsi,
Can you fix? The closing single quote is missing in 'user-create'.

done after the PR was merged


Evaluation for reproducing the paper's result

I am currently conducting research on structure-based drug design using proteins.
I find the concept of fragmentation linking to be a valuable approach in drug design, and I am particularly impressed with your work's ability to consider the conditioning on the protein pocket. Thank you for hard working on it!
I have a few questions regarding your research:

First, I attempted to reproduce the results from your paper using the Sampling section (https://github.com/igashov/DiffLinker#sampling). However, I noticed that the results for the ZINC and GEOM datasets differ significantly from the paper's reported results, especially concerning the SA score. While the paper's SA score is approximately 3.x, my results yielded a score of 6.x. I'm unsure why these results are different. Is there an additional step required to accurately reproduce the paper's findings?

Unfortunately, as mentioned in the readme, there is no pocket linker prediction model available. Therefore, I was unable to conduct experiments with the Pocket dataset. Could you provide some suggestions on how I can reproduce the paper's results without this model? Additionally, I am curious about the linker prediction model used in the Table 5 pocket section.

I came across Figure 2 in the paper, which showcases examples of linkers sampled by DiffLinker conditioned on pocket atoms. I attempted to replicate these results using the same molecule fragments from the MOAD dataset and the awesome hugging face. However, I couldn't achieve the same results as presented in the paper, even when utilizing the same protein anchors. Could you please guide me on how to accurately reproduce the results shown in Figure 2?

I am interested in reproducing the results shown in Figure 4 and 5 from the paper. However, I encountered a challenge as there is no index provided in the paper, which prevents me from attempting the test. Could you kindly provide me with the necessary information about the fragments used in the Figure 4 and 5 datasets? This would be immensely helpful in my efforts to replicate the results accurately

If you require any specific information or have any additional questions to aid in reproducing my experiments, please let me know, and I will promptly provide the requested details.
Thank you for your time and consideration.
@igashov

Thank you so much for dedicating your time and attention to my question.

I have followed the README's sampling and evaluation section and made the necessary modifications to suit the specific dataset requirements. Consequently, I conducted tests on three datasets (GEOM, ZINC, MOAD).
However, I noticed that there is no checkpoint available for "[Pockets] Size GNN" used to predict the linker size. Also, In Table 5 and 6 of the paper, there is no notation about the sampled size. I am curious about how you conducted the experiments based on protein pockets and managed to predict the linker size without this information.

Thank you for sharing the information about these things. If possible, could you provide an example of the generated results for these experiments? It would be helpful for my current research.

Thank you so much for providing this information. I am currently searching for the molecule in the geom_multifrag_test_frag.sdf file, and having access to this will save me a considerable amount of time.

I have also conducted sampling using Hugging Face. By examining the fragments in 3D, I sampled 231 samples from the GEOM test set. Following this, I converted this sdf files to smiles file and data pickle file using this scrip(reformat_smi.py). Despite computing the modified script(compute_metrics_hf.py)

python -W ignore compute_metrics_hf.py \
                 GEOM \
		 [path]/geom_multifrag_output/hf_geom_final_test.smi \
                 datasets/geom_multifrag_train_linkers.smi \
                 5 1 None \
                 resources/wehi_pains.csv \
                 diffusion

The result differs from the one presented in the paper's Table. I have attached the output files for your reference.
5.huggingface_scipt_summary.zip
I would appreciate any guidance on how to achieve better results and obtain more favorable metric values. Alternatively, I wonder if I might have overlooked any steps in the evaluation process.
If there's anything else you'd like to share or if you need further assistance, please let me know.
Sincerly,
Minju

I checked samples for [zinc, difflinker] and apparently you have a different version of OpenBabel. Basically, I first used your data (incl OpenBabel output), reran evaluation, and got the same numbers as you. Then I reran OpenBabel using your .xyz files and then again reran the evaluation script and got different numbers that are very close to what we report in the paper (recovery and uniqueness are of course different as you sampled only one linker per input). Please find my files attached. If you compare .sdf files produced by your and my OpenBabel, you will see some differences that cause the further changes in numbers. Therefore, please check that your OpenBabel version in 3.0.0.
Samples and results with my OpenBabel version:

samples.tar.gz
formatted.tar.gz

Experiments with Pockets dataset were conducted with the ground-truth linker sizes, not sampled ones.

The uuid of the input set of fragments from this Pockets test set table used in Figure 2 is 34038. I am attaching the tables of all samples made by DiffLinker (conditioned and unconditioned) on the Pockets test set. Unfortunately, these tables do not contain uuid, but you can find the relevant samples by searching for the right smiles of input fragments: C1CCCCC1.CC(O)N[C@H]1CCC2OCNC2C1.
Tables with samples:  samples_used_for_Figure_2.tar.gz

Happy to help!

In order to reproduce the paper results on a specific dataset I would recommend to use command line and the code provided in this repository.

Best regards
Ilia

I am pleased to share that I finally achieved the desired result. I truly appreciate your kind and detailed assistance. (It was not important, I did encounter a small issue where the "formatted.tar.gz" file turned out to be empty, but I managed to create the formatted data using the samples you provided.)

,3 4. 5. I understand now. Thank you for responding to my questions and for consistently providing the results.

When I first discovered your work, I was surprised by the excellent implementation using Hugging Face and the well-organized repository. However, I encountered some issues with reproducibility.
Before reaching out to you, I had lost my way in conducting the experiments.
Thankfully, with the exact and detailed answer you provided, I was able to resolve this problem.
Thank you once again for your invaluable help. I am looking forward to your future works.
Best regards
MinJu

Oh indeed it's empty. Here it is – should be with tables: formatted.tar.gz
Thank you for your nice feedback. I am glad to hear that you liked our work and that you managed to solve the issues!
Best regards
Ilia


Charger Wattage Calculator Feature

Description
This calculator will allow users to input the voltage (V) and current (A) of their chargers and calculate the wattage (W). This feature will be helpful for users to determine the power output of their chargers.
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 please assign me this issue

We already have Electric Power Calculator, pls work on new issues @divyansh-2005