Using Proxmox API: https://<IP_ADDRESS>:8006/api2/json

The problem
During start of the adapter the following warning is shown in the log
proxmox.0
	2024-05-22 13:03:16.105	warn	Using Proxmox API: https://<IP_ADDRESS>:8006/api2/json
proxmox.0
	2024-05-22 13:03:15.988	info	starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v18.20.3, js-controller: 5.0.19

Debug Log
2024-05-22 13:10:48.942 - info: host.ioBrokerTestsystem instance system.adapter.proxmox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-05-22 13:10:51.636 - info: host.ioBrokerTestsystem instance system.adapter.proxmox.0 started with pid 12226
2024-05-22 13:10:54.218 - debug: proxmox.0 (12226) Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
2024-05-22 13:10:54.331 - debug: proxmox.0 (12226) Objects client ready ... initialize now
2024-05-22 13:10:54.340 - debug: proxmox.0 (12226) Objects create System PubSub Client
2024-05-22 13:10:54.345 - debug: proxmox.0 (12226) Objects create User PubSub Client
2024-05-22 13:10:54.527 - debug: proxmox.0 (12226) Objects client initialize lua scripts
2024-05-22 13:10:54.592 - debug: proxmox.0 (12226) Objects connected to redis: <IP_ADDRESS>:9001
2024-05-22 13:10:54.727 - debug: proxmox.0 (12226) Redis States: Use Redis connection: <IP_ADDRESS>:9000
2024-05-22 13:10:54.823 - debug: proxmox.0 (12226) States create System PubSub Client
2024-05-22 13:10:54.829 - debug: proxmox.0 (12226) States create User PubSub Client
2024-05-22 13:10:54.928 - debug: proxmox.0 (12226) States connected to redis: <IP_ADDRESS>:9000
2024-05-22 13:10:55.313 - info: proxmox.0 (12226) starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v18.20.3, js-controller: 5.0.19
2024-05-22 13:10:55.354 - warn: proxmox.0 (12226) Using Proxmox API: https://<IP_ADDRESS>:8006/api2/json
2024-05-22 13:10:55.722 - debug: proxmox.0 (12226) received 200 response from proxmox with content: {"data":{"ticket":"PVE:root@pam:664DD2BF::MBLhZHu0YG6aoXI4kuTQB0bwBH1fYoeBASGyZLNzb3jc/F0STxArRRg7kHfGSAlo6L6PZkI5le5tSqRKDfVJu4fG810Y66dSBaPWcDTtOcwN7uj3Dl8IKvc1B9z9FUc7sn5R3lHZV+xP4uLZLFfSQPQTt/2doF3xY9s/4QwxpBN2McR5qnym0RfbUFP0SEgg/HtnN5NgKjmuMiFBHl2gr5vUZ/Y/D0flPPYwdPIK7AuX/wEccpfuSQwBC6QL9jcvgCnyLbDsVoZIxq+oZbLiVor1toJSP1FaDLWe7nhVjDij+6p1ZYKWsoVTxj6m0rWis0+kXeZr5rHORbCUynfPzA==","CSRFPreventionToken":"664DD2BF:A8Ay2O9SVDHN5A+Qu4Rkb/6TJYQ4gyxWSzbAJR+pUmk","username":"root@pam","cap":{"nodes":{"Sys.AccessNetwork":1,"Sys.Syslog":1,"Sys.Audit":1,"Sys.Incoming":1,"Sys.PowerMgmt":1,"Sys.Modify":1,"Permissions.Modify":1,"Sys.Console":1},"dc":{"SDN.Use":1,"SDN.Audit":1,"Sys.Modify":1,"Sys.Audit":1,"SDN.Allocate":1},"mapping":{"Mapping.Audit":1,"Mapping.Use":1,"Mapping.Modify":1,"Permissions.Modify":1},"access":{"Group.Allocate":1,"Permissions.Modify":1,"User.Modify":1},"vms":{"VM.Config.Network":1,"VM.Allocate":1,"Permissions.Modify":1,"VM.Config.CDROM":1,"VM.Clone":1,"VM.Audit":1,"VM.Config.CPU":1,"VM.Config.Memory":1,"VM.Snapshot":1,"VM.Config.Disk":1,"VM.Monitor":1,"VM.Config.Options":1,"VM.Snapshot.Rollback":1,"VM.Config.Cloudinit":1,"VM.Migrate":1,"VM.Config.HWType":1,"VM.Console":1,"VM.PowerMgmt":1,"VM.Backup":1},"storage":{"Datastore.Audit":1,"Datastore.Allocate":1,"Datastore.AllocateSpace":1,"Datastore.AllocateTemplate":1,"Permissions.Modify":1},"sdn":{"Permissions.Modify":1,"SDN.Use":1,"SDN.Audit":1,"SDN.Allocate":1}}}}
2024-05-22 13:10:55.724 - debug: proxmox.0 (12226) dataticket: {"data":{"ticket":"PVE:root@pam:664DD2BF::MBLhZHu0YG6aoXI4kuTQB0bwBH1fYoeBASGyZLNzb3jc/F0STxArRRg7kHfGSAlo6L6PZkI5le5tSqRKDfVJu4fG810Y66dSBaPWcDTtOcwN7uj3Dl8IKvc1B9z9FUc7sn5R3lHZV+xP4uLZLFfSQPQTt/2doF3xY9s/4QwxpBN2McR5qnym0RfbUFP0SEgg/HtnN5NgKjmuMiFBHl2gr5vUZ/Y/D0flPPYwdPIK7AuX/wEccpfuSQwBC6QL9jcvgCnyLbDsVoZIxq+oZbLiVor1toJSP1FaDLWe7nhVjDij+6p1ZYKWsoVTxj6m0rWis0+kXeZr5rHORbCUynfPzA==","CSRFPreventionToken":"664DD2BF:A8Ay2O9SVDHN5A+Qu4Rkb/6TJYQ4gyxWSzbAJR+pUmk","username":"root@pam","cap":{"nodes":{"Sys.AccessNetwork":1,"Sys.Syslog":1,"Sys.Audit":1,"Sys.Incoming":1,"Sys.PowerMgmt":1,"Sys.Modify":1,"Permissions.Modify":1,"Sys.Console":1},"dc":{"SDN.Use":1,"SDN.Audit":1,"Sys.Modify":1,"Sys.Audit":1,"SDN.Allocate":1},"mapping":{"Mapping.Audit":1,"Mapping.Use":1,"Mapping.Modify":1,"Permissions.Modify":1},"access":{"Group.Allocate":1,"Permissions.Modify":1,"User.Modify":1},"vms":{"VM.Config.Network":1,"VM.Allocate":1,"Permissions.Modify":1,"VM.Config.CDROM":1,"VM.Clone":1,"VM.Audit":1,"VM.Config.CPU":1,"VM.Config.Memory":1,"VM.Snapshot":1,"VM.Config.Disk":1,"VM.Monitor":1,"VM.Config.Options":1,"VM.Snapshot.Rollback":1,"VM.Config.Cloudinit":1,"VM.Migrate":1,"VM.Config.HWType":1,"VM.Console":1,"VM.PowerMgmt":1,"VM.Backup":1},"storage":{"Datastore.Audit":1,"Datastore.Allocate":1,"Datastore.AllocateSpace":1,"Datastore.AllocateTemplate":1,"Permissions.Modify":1},"sdn":{"Permissions.Modify":1,"SDN.Use":1,"SDN.Audit":1,"SDN.Allocate":1}}}}

Version of nodejs
18.20.3
Version of ioBroker js-controller
5.0.19
Version of Adapter
2.3.0
Version of Proxmox
8.1.4
Operating system running ioBroker
Ubuntu 22.04.4 LTS (GNU/Linux 6.5.13-1-pve x86_64)
Checklist of files to include below

[X] iobroker.current.log (Please share the logs in debug mode)
[ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads
No response

this is correct.. if you have more node, so you can see which one to start with


feat: Create and verify JWS when creating new presentation

closes #862
Signed-off-by: Dima<EMAIL_ADDRESS>

This is correct, you need fetcher/resolver. We implemented similar in did-exchange (it is called keyresolver

Yeah, but we need first to resolve DID of the entity which signed the JWT (issuerID parameter) and then find appropriate public key (keyID parameter) as it's done in keyResolver.resolve().


remove rbd-mirror metrics already exported by ceph

The PR removes the metrics
ocs_rbd_mirror_image_primary_snapshot_timestamp
ocs_rbd_mirror_image_secondary_snapshot_timestamp
ocs_rbd_mirror_image_image_bytes
ocs_rbd_mirror_image_image_snapshot_bytes

as corresponding metrics already exist in ceph
ceph_rbd_mirror_snapshot_image_local_timestamp
ceph_rbd_mirror_snapshot_image_remote_timestamp
ceph_rbd_mirror_snapshot_image_last_sync_bytes

image_bytes and snapshot bytes can be calculated by sync_time and sync_bytes metrics exported by ceph
ocs_rbd_mirror_image_image_bytes :  ceph_rbd_mirror_snapshot_image_last_sync_bytes / ceph_rbd_mirror_snapshot_image_last_sync_time

ptal @umangachapagain

We also need to replace the usage of these metrics in alerts.
all the alerts are based on image state,  that metric is not removed from the exporter

/cherrypick 4.15

@weirdwiz DCO check is failing. Please address it.

need to squash the commits, on it

/cherry-pick release-4.15

/cherry-pick release-4.14

/lgtm


请问有VAB-Mobile和WebArena-Lite这两个数据集生成的代码吗

@wangjinghan666 Sorry for the missing of mentions. I am afraid currently we are busy working on organizing our code and data and have not decided related plans.


Setup Deployment to Artifactory

Done 🎉

Snapshots: https://repo.dustplanet.de/artifactory/libs-snapshot-local/net/gravitydevelopment/updater/updater/
Releases: https://repo.dustplanet.de/artifactory/libs-release-local/


Update build support to Julia 1.3 and later.

Fixes #30
As per discussion with @juliohm, this PR will make the builds run only for Julia 1.3 and later versions.
Test Reports from My Fork:

Fixes #30

cc: @juliohm

Amazing @LakshyaKhatri , thanks for the improvement.


Fix a small bug with the use of setComponentByPosition in pyasn1

I was using this great tool for a CTF, I wanted to generate the private key PEM file, given the RSA modulus and both public and private exponents. I ran the command and there was an error during the generation of the file, in the function setComponentByPosition. I checked the documentation and made a little modification that made the program work as expected for me.
I don't know what it's worth but I prefer to send it to you.
Thanks for the tool !

Looks like this was fixed as part of another PR in 720c2e44.


Sources can be removed from this repo, right?

There are many source files that can be removed, correct?

but run and upload-symbols binaries are needed

@lazar-otasevic-cif Are you referring to the dummy files? Those are there because SPM will complain (compile error) if a target's resource folder is empty.

ah all good


List outdated

Thanks for writing this package manager... quite nifty.
Is there a way to list installed packages which are outdated and need upgrading? Thanks.
Cheers,
James

$ wget 'https://cygwin.com/setup-x86_64.exe'
$ install setup-x86_64.exe /bin
$ rm setup-x86_64.exe
Put this to .bashrc or .bash_profile
alias upgradeCygwin="setup-x86_64.exe --no-desktop --no-shortcuts --no-startmenu --quiet-mode --upgrade-also --delete-orphans"
run
$ upgradeCygwin

Someone made an Ansible module wrapping apt-cyg and used some trickery to get the installed version: https://github.com/naokirin/ansible-apt-cyg-module/blob/master/library/apt-cyg#L82-100
I am using a slightly modified version of this python script and it works well, but I am still looking for a better way to list outdated packages :)


WIP Handle NumericUpDown percentage StringFormat correctly

Describe the changes you have made to improve this project
The current behavior for e.g. percentage text input with StringFotmat like P0 or {0:0.00%} converts the input one-to-one to the value:
100% = 100
This is not what the user expects, because the .Net default works different:
100% = 1
So this PR changes this behavior to the .Net default one.
Unit test

[x] ShouldConvertTextInputWithPercentStringFormat
[ ] more tests

Additional context

Closed Issues
Closes #3376
/cc @mgnslndh @timunie

Hi @punker76
some more thoughts on your PR:

Should we derivide from TextBox instead of control? That way some Properties would be implemented by default
If the stringformat is HEX the control has to accept [a..f] as Input as well.
Is a double- value precise enough? That way you cannot use decimal or ulong - values.
The DemoApp crashes on an invalid Stringformat. Is there a way to handle this? Should we handle this?

Happy coding and a 💯 times thanks.
Tim

Good morning @punker76 ,

Is a double- value precise enough? That way you cannot use decimal or ulong - values.

one addition: if we change the basetype to decimal we will also solve #2923 (it was closed in the past with a note that this would be a breaking change, we have a breaking change right now :smile:  ) and #3673 .
Happy coding
Tim


chore: node ci patch

Description
Temporary workaround to for https://github.com/nodejs/node/issues/53902. Replaces latest with 22.4.1. There is a RC for v0.33.0 using npx peppr and this image. The team is short right now so we plan on releasing on Tuesday
Related Issue
Fixes #

Relates to #https://github.com/nodejs/node/issues/53902
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

latest node is passing, v22.5.1


cocoapods  didn't find LGSemiModalNavController

[!] Unable to find a pod with name matching `LGSemiModalNavController'

Hey @RobinChao not sure what this could be. I created a sample project and tried to replicate but I cant. It seems to be working just fine for me. Make sure you have the following
pod "LGSemiModalNavController"

Here is the pod on cocoapods.org https://cocoapods.org/?q=lgsemimodal

Closing for now, feel free to re open if you need more help.


Add feature flag for Kinesis lag metric

This PR adds a new enableTimeLagMetrics property to the Kinesis supervisor tuningConfig that controls whether the millisBehindLatest-based metrics are emitted, and also whether such information is included in the supervisor status report.
This PR has:

[x] been self-reviewed.
[x] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

#9819 might make this not necessary, but even still it feels lopsided to me that this setting only can only provide control over time lag and not both time and record count lag. Thoughts?

I'll close this for now as I agree with #9819 making this not needed


[service-bus] UX study branch

(not yet mergeable or tested across a larger swath of scenarios).

/azp run js - servicebus - tests

/azp run js - servicebus - tests

UX study has concluded and we went a different way. Can close this now (and it's massively conflicted anyways!)


How did this go for you?

Hey - this library looks very cool - I am looking at doing something similar, trying to convert maybe 5-10k lines of coffeescript to es2015.  I see the last commit here is a few months old - I am just wondering how your transition went using these transforms.  Have you completed it?  Would you consider it a success?  How much time do you think you saved vs converting by hand?
thanks!

Hey!
Thanks :-) We still haven't converted our codebase, although we just had our first PR succeed on Jenkins in which all files were converted, so I guess it won't be long now.
The problem with these transforms is that they make a lot of assumptions on code style, so I can imagine that some of these won't work as well for your codebase. If you could give me a idea of what type of codebase you're working with, I could maybe explain which transforms will work and which won't (e.g. backbone-classes assumes that all classes are extending objects that have a .extend method).
If you're working on a CJSX codebase I have some changes locally to recast that might be interesting too.
All in all I'm confident that this approach will actually save us a lot of time/hassle, but like I said, we're not done yet!

Hey there,
It's now been two weeks since we converted our codebase to ES2015! I'm really happy with the performance of the transforms, but there was still quite some "manual" labor left. After the transform we had 30k ESLint warnings in our codebase, with the help of some ESLint/JSCS autofixers and some stylistic codemods we reduced it to <5k, the rest is being manually fixed as we see them at the moment.
All in all I'm really happy with the outcome, but I can't stress it enough that this will probably never work as a "single-click" coffee-to-es2015 transform, there will always be manual labour left over.
If you have any questions, please let me know and I'd be happy to answer!


[@thumbtack/thumbprint-react] Add ability to constrain <ModalDefault> height

In some modal flows, I'm finding the need to constrain the modal height on desktop so that it's consistent even across modal content (whose length varies) changes.
(https://www.figma.com/file/IcbYHDSlj6A1gXJTpvM1UQF5/🗓-Calendar-%2B-Availability?node-id=4188%3A1097)
I've found this to be a relatively use case (i.e. it's a bit jarring when the modal height suddenly expands/constrains as we switch from loading state or when some collapsed content within modal gets revealed, etc.)
Currently, there doesn't seem to be a good way for consumer to apply a fixed height to modal.
It's possible to render a child of <ModalDefault> as
 with some fixed height, but it's deficient because
(1) We'd want the entire modal (i.e. including sticky footer and close button row) height to be consistent, not just the children
(2) When children are long, this wrapper
 overflows; however, there already is a container that actually controls the overflow (
) and leads to weird styling issues (i.e. overflowing children will bleed into the bottom padding of
)
I also attempted using <ModalDefaultAnimatedWrapper> but <ModalFooter isSticky> throws a ref error (TypeError: Cannot read property 'current' of null) and it's just a lot of reinventing <ModalDefault> mechanics when the only thing I want more is height constraint.
I would prefer if <ModalDefault> can accept an additional height prop (like width) that simply constrains height of the entire modal (whether it's pixel, percentage, or discrete values) and I would be happy to contribute to the change. What are your thoughts?

@jichan-thumbtack Are you not able to constrain the height of the content inside of the modal? Eg. (excuse the pseudo code):
<Modal>
  <ModalDefaultContent>
     <my-content-wrap height="500px">
        <my-content>i'm the content that has overflow, flexes</my-content>
        <my-footer>button, no flex</my-footer>
     </my-content-wrap>
  </ModalDefaultContent>
<Modal>

Yeah those issues are not present with the particular example, but
(1) is a problem when you use <ModalDefaultFooter isSticky>. When the footer is sticky, it is placed outside of the contents node.
(2) is a problem when contents are longer than the specified height. If I apply overflow to
 with height: 300px;, then we would have double scrollbars. If we let it overflow that
, it bleeds into padding of the contents node.

The above example essentially renders:

 // modal container node

 // modal contents node

Content overflows beyond the immediate wrapper

    // modal sticky footer and close button

I'd think applying height to the root container seems like it would result in the most predictable layout, but I'm open to suggestions

@danoc I talked with @jichan-thumbtack and it looks being able to add a fixed height to https://github.com/thumbtack/thumbprint/blob/master/packages/thumbprint-react/components/ModalDefault/index.jsx#L389 would produce the behavior needed.
It may be possible to get the effect without it but it involves rebuilding the layout structures that already exist. We like to discuss with you since you have better context on this component.

Ok, sweet! Thanks for digging into it. Would chatting on Monday work?
On Thu, Aug 22, 2019, 6:02 PM Tom Genoni<EMAIL_ADDRESS>wrote:

@danoc https://github.com/danoc I talked with @jichan-thumbtack
https://github.com/jichan-thumbtack and it looks being able to add a
fixed height to
https://github.com/thumbtack/thumbprint/blob/master/packages/thumbprint-react/components/ModalDefault/index.jsx#L389
would produce the behavior needed.
It may be possible to get the effect without it but it involves rebuilding
the layout structures that already exist. We like to discuss with you since
you have better context on this component.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thumbtack/thumbprint/issues/433?email_source=notifications&email_token=AAG7URRTKMRSHHSQPDP3SPTQF4SI3A5CNFSM4IOZGIVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD46XSGA#issuecomment-524122392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG7URR4UA6ALCUIGVG2I4TQF4SI3ANCNFSM4IOZGIVA
.

This was done in #444.


Traceback Error on Latest Build

Description
Using the latest build. everything runs fine, but after awhile, the program crashes with a traceback error, forcing me to restart. This is causing me to miss out on drops because I let the program AFK, and I'm not finding it until later.
I've tried both the EXE and source code, both crash in the same way after awhile.
To Reproduce
As far as I know, run the program.
Expected behavior
The program should run.
Observed behavior
The program is crashing.. possibly a twitch update? The error suggests that this is a problem with claiming the drop? Looks like it crashes after it claims one.
Screenshots

Logs
No response
OS
Windows 11
Build
.exe and source code
Version/Commit
v15.10.0
Additional context
I am using Starlink Internet, but I highly doubt this is the issue, as nothing else in my network is experiencing problems.

Trying the latest dev build from @DevilXD I got to see it in real time. As soon as the timer hit 0 and it was time to claim a drop, the program crashed, so it is absolutely related to claiming drops.


Feat: To add feedback review section inside the feedback

Describe the feature
Inside the feedback section, having a feedback review option would look good.
@Suchitra-Sahoo
So please assign this to me under gssoc'24.
Add ScreenShots
SS-

Record

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

This is not required

I think it is not much helpful.


Feat/smape regression error

Before submitting

[ X] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ X] Did you read the contributor guideline, Pull Request section?
[X ] Did you make sure to update the docs?
[X ] Did you write any new necessary tests?

What does this PR do?
This PR adds SMAPE regression metric: https://github.com/PyTorchLightning/metrics/issues/372.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @hugoperrin! Thanks for opening this PR.

In the file tests/helpers/non_sklearn_metrics.py:

Line 9:36: E128 continuation line under-indented for visual indent
Line 10:36: E128 continuation line under-indented for visual indent

In the file tests/regression/test_mean_error.py:

Line 17:121: E501 line too long (128 > 120 characters)
Line 28:121: E501 line too long (122 > 120 characters)
Line 101:121: E501 line too long (127 > 120 characters)

In the file torchmetrics/regression/symmetric_mean_absolute_percentage_error.py:

Line 28:121: E501 line too long (138 > 120 characters)

Do see the Hitchhiker's guide to code style

@hugoperrin mind check last comments from @SkafteNicki, mainly related to references

@Borda I updated the needed docs, I think this should be good, I'll wait on the CI to finish and fix things if things are needed to be fixed then :) Thank you for your quick feedback :)

PS: should I squash the commits by the way?

no need, well do it with all PR by default: squash + merge


bump dcos-ui package for 1.8.5 release.

These changes shouldn't go into master branch.
This is only for 1.8.5 release. cc/@cmaloney

merged in 1.8.5


Updated requirements for pygrib and its setup

Currently pygrib cannot be installed with pip unless you have numpy previously installed since the setup.py depend on it without declaring this dependency. This PR makes that install dependency explicit so that pip knows it is needed and thereby succeeds in installing even if numpy wasn't installed.
I verified that pygrib installs correctly by building a wheel and then inside a Docker image running pip install for my pygrib-wheel without having installed numpy and it correctly pulls numpy.
I also include a requirements-file so that it is clear that the running of pygrib depends on numpy being installed too.
I didn't include a requirement for pyproj since this was optional, but maybe it wouldn't hurt to just add it if the two ways of getting pyproj actually point to the same code?

Thanks for all the pull requests @local-minimum !


lib.rs:85-87: Pass fakehub to all required endpoints to...

The puzzle 124-85a7849c from #124 has to be resolved:
https://github.com/h1alexbel/fakehub/blob/60d120a50afe67d81b57f1b64804cd87f8b1adc5/server/src/lib.rs#L85-L87
The puzzle was created by @rultor on 02-Sep-24.
Estimate: 35 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd Main quality problem: Lack of clear bug description. Suggestion: Provide a concise des...

I see you're talking to me, but I can't reply since I'm not a chat bot.

The puzzle 124-85a7849c has disappeared from the source code, that's why I closed this issue.


Marathi Translations are started

This commit is to indicate that Marathi translations are started, Thanks to Hacktoberfest.

25% of translations been done

@TheLastProject do we have to keep the app_name as it is? Like Catima can is written in Marathi as कटिमा (Read as Kateemaa in Marathi)

Do whatever is most normal in your language. Some languages tend to write brand names in their letters, some don't. I don't speak Marathi so I don't know what's normal there :) Just be consistent :)

Hi, Hacktoberfest is over. Do you still want to finish up this MR to be listed in the README? :)

@TheLastProject I will finish up by this weekend.

I am closing this pull request since the Hacktoberfest is over, done about 33% of translations, since i have a day job, can't focus/give 100% of time, It is so much joy, since i rarely get to interact with my native language. I will continue the translation task side by side at slow pace.


feat: Add custom save path

What
This PR adds a feature allowing users to define the output path when taking a photo/snapshot or recording a video.
The idea was presented in https://github.com/mrousavy/react-native-vision-camera/issues/893.
Additionally, this PR fixes an issue on Android where the quality parameter for takeSnapshot was mandatory, resulting in an error [EUNSPECIFIED: quality] if not provided. (https://github.com/mrousavy/react-native-vision-camera/issues/2804)
Changes
Added a new parameter "path" to specify the output directory for photos, snapshots, and recorded videos.
Updated the relevant functions to handle the custom save path.
Tested on
iPhone 12, iOS 17.4.1
Huawei ELE-L29, Android 12
Related issues

https://github.com/mrousavy/react-native-vision-camera/issues/893
https://github.com/mrousavy/react-native-vision-camera/issues/2804

Hi! Thank you so much for this contribution, this is good stuff.
I have a few code-organization/style concerns which I will think about and get back to you soon.
To share what's going on inside my head;

I am not a big fan of having one function for getting a path or creating a temp file.
I think maybe we can get the path at high-level using a sync native function, and basically always assume the path is non-null and writable on native side. In the JS func for startRecording/takePhoto/takeSnapshot we get a temp path from native if the current path is null (or not writable). This also reduces the amount of logic/branching on the native side and moves it to JS, where code is more flexible in general
message is a bit weird for the error parameter, I'd call it cause or something and pass an error I guess? Just a minor nitpick

Don't worry about changes right now, I'll get back to you in a few days about this. But I definitely think this should go into main, this is good nice work 👍

Thank you for taking the time to review my PR and for your positive feedback.
I agree that it could be a good idea to have a function for getting a temporary path and managing the path logic directly in the JS code. This would indeed simplify the native side and make the code more flexible overall.
I'll wait for your detailed feedback before making any changes. Looking forward to refining this feature based on your suggestions :)


Selection-on-observables Simulation Goals

Hey y'all, I'm starting a thread so we can collect our discussion as we clarify the explicit goals of the selection-on-observables simulation that Amine is working on.
As far as I see it, there is one goal of this simulation that we're already in agreement on:

Demonstrating the workflow for causal inference described in section 5.2 of Brathwaite & Walker (2018).

I think this will not be of much interest to audience members of the conference, by itself, because it does not show how the workflow

solves some problem that the audience members care about, or
leads to some new insight / knowledge / perspective that is practically useful.

I think that we can include the following additional goal for the simulation in order to make it very interesting for the audience:

show how causal graphs allow one to determine which estimated regression coefficients can be given interpretations in terms of causal effects.

This should be represent a large change from current practice as it means that to interpret an estimated model, one needs:

a causal graph
a hypothesized intervention that is being conceived of (if only implicitly) in one's causal question
a causal question (what's the effect of ___?)

What do you all think?

In particular, we should emphasize that researchers should “draw their assumptions before they draw their conclusions.” (See the following online MOOC of the same name). The reason for this emphasis is that causal graphs enable easy determination of when a given causal effect is identified. This information is invaluable when interpreting an. estimated model.
As an illustration of this point, consider the following scenario from my time when working in transportation consulting at Cambridge Systematics.
Imagine one is a large technology company that is looking to expand its corporate campus. However, the city that one’s campus is located in will not allow the expansion to occur unless the company meets certain requirements. In particular, the company must show that despite its expansion, it is taking preventative steps to keep its drive-alone-mode share beneath X%, after the expansion.
As a result of these requirements, the company wonders “if I could move each of my employees, after the expansion, X% or Y miles closer to the campus, what would the drive alone mode share of the company be?”
This is a causal inference question that would be addressed with a mode choice model similar to the one used in my asymmetric models paper. That model featured a bike utility based on travel distance, and car and transit utilities based on travel time and travel cost. If travel distance -> travel cost and travel distance -> travel time (which it def does in the Bay Area), then one cannot interpret the travel distance coefficient causally because we control for the intermediate variables of travel cost and travel time.
We should use simulation to show that one never recovers true coefficient values, asymptotically, when in a situation where intermediate variables of a cause must be controlled for. We can contrast with a simulation where travel cost and travel time are not intermediate variables between travel distance and the mode choice. The idea would be to look at the percentage of time that the data-generating parameters fall within one’s confidence / credible interval as the training set size increases. In both cases, the model for the mode choice will be correct. What will differ is the data generating process for the explanatory variables. We will show that this difference is enough to render one’s estimates asymptotically biased in the case where the true model entails controlling for "intermediate" variables. This is analogous to the issue with multicollinearity and not being able to distinguish or allocate responsibility for an outcome.
We can base the simulations on the models in my asymmetric paper, and we can base the causal question on my work work with Cambridge Systematics.

@bouzaghrane @hassanobeid1994

@timothyb0912 My understanding is that demonstrating the workflow from section 5.2 of your paper with Joan entails in itself communicating that we have to be being upfront about our causal assumptions in our causal graphs. Right?

We can base the simulations on the models in my asymmetric paper, and we can base the causal question on my work work with Cambridge Systematics.
Do you think it would be easier since I am assuming that some defensible causal graph has already been identified?

Updating this with conclusions from video call:
We'll have 1 to 2 simulations being done for the project and 1 analysis with real data.
All simulations and real data analysis will be based off the scenario from my 2018 asymmetric models paper with Joan.

Simulation #1 will present a selection on observables scenario.

The idea is to have 2 causal graphs.
The model for Y is the same in both graphs.
There is no unobserved confounding in any graph.
The model for the Xs differs.

In the first causal graph, the Xs are generated in dependently.
In the second causal graph, the Xs are generated from a realistic causal graph where some Xs cause other Xs.

The contribution is to demonstrate that true causal effects (er, model coefficients? difference in predicted probabilities at changed X values?) are not recovered in the second scenario even though the model for Y is "well-specified." We need causal graph to accurately interpret an estimated statistical model.

Simulation #2 will present a scenario with unobserved confounding and the use fo the de-confounder to address it.

Should take the realistic causal graph from simulation #1 and remove one or more observed variables.
The contribution is that we show how to deal with unobserved confounding in transportation context.
We'll contrast results from standard setting with results using the deconfounder.

Real data analysis

Use the same causal graph from simulations, apply the deconfounder.
Show how results differ from traditional results as shown in the 2018 paper.

Just to close the loop on your comment above, no defensible causal graph for this scenario has been created yet!


[BEAM-79] Add Gearpump runner profile to Java8 Archetype POM

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @manuzhang

retest this please

Changes Unknown when pulling 31810c459ea95cb7816261087a7e73dc0e0338c3 on huafengw:example into ** on apache:master**.

LGTM


Added support for DOM elements that are positioned using css-transforms.

This pull-requests add support for DOM elements that are positioned using css-transforms rather than left, top, etc... This is necessary for web-technologies such as famo.us, which exclusively depend on css-transforms to do their positioning.

Ah thanks for pointing that out. I will fix it in the forked repo.
Cheers

Hi, I've pushed the fix onto the forked repo:
https://github.com/IjzerenHein/cordova-plugin-opentok
cheers


[FLINK-32374][table-planner] Fix the issue that ExecNodeGraphInternalPlan#writeToFile should support TRUNCATE_EXISTING for overwriting

What is the purpose of the change
This PR fixes the issue that COMPILED PLAN statement may generate invalid JSON when overwriting the existing JSON with a shorter version.
Brief change log

Add TRUNCATE_EXISTING to ExecNodeGraphInternalPlan#writeToFile

Verifying this change
This change is already covered by existing tests, such as CompilePlanITCase#testCompilePlanOverwrite.

Roll back the changes made on src and run this case will reproduce the error. Apply the changes made on src and re-run the case to verify the fix.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): No
The public API, i.e., is any changed class annotated with @Public(Evolving): No
The serializers: No
The runtime per-record code paths (performance sensitive): No
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: No
The S3 file system connector: No

Documentation

Does this pull request introduce a new feature? No
If yes, how is the feature documented? N.A.

@LadyForest Could you please backport to 1.17 & 1.16. Thx.


Prod build crashes after today's changes

It compiles just fine, but throws a lot of exceptions when trying to run it.
https://github.com/AngularClass/angular2-webpack-starter/commit/fe37a03b6e86fa7ceeb9c76e0cc59db3eb2b8d83 broke it

+1

e00aac92d112a56fc57e08717f9451107265c8f6 fixed the issue for me

can you pull latest and see if it's still broken

The latest works for me. Cloned, installed, built and served.

thanks, closing now. update to latest and reopen if there is an issue


Add react-draft-wysiwyg to Rich text editor

This is really good text editor.
https://github.com/jpuri/react-draft-wysiwyg

Thanks for the head's up! Is there a reason you didn't use devarchy to add it?

It has been added to the catalog.


Status, Time and Size of Response

Verify if status, time and size of response is being passed. If not, pass it so that it can be displayed in on UI in the 3rd column, under 'Response' section after a request has been run.

Time displayed. Need to fetch Size of response.

Assigned to @rka12


Sorting summary table

As mentioned already in your fitplotter repo, I am adapting your wonderful projects (fitalyser and fitplotter) to my needs. I am almost done, but one thing drives me nuts, and I hope to get some help from you.
I simply want to have the summary table sorted by date in descending order. Therefore I delete the table every time there is a new activity and changed the code in utilities/summaryTable.js as follows. The idea is to read the files in activitiesFolder and sort them by creation date in the desired order before parsing them:
fs.readdir(activitiesFolder, (err, files) => {
  if (err) {
    console.log("\nDoes not exist: \"" + activitiesFolder + "\n\nCheck path to FIT files\n");
    return;
  } else {
    //START NEW CODE
    files.sort(function(a, b) {
      return fs.statSync(activitiesFolder + "/" + b).birthtime.getTime() - fs.statSync(activitiesFolder + "/" + a).birthtime.getTime();
    });
    // END NEW CODE
    files.forEach(file => {
      if (file.slice(-4) === fileExt) {

But the table is still not sorted by date in descending order. The funny thing is, that if I am starting summaryTable.bat again and agan after deleting the table, the newly generated table is always sorted in a different way, which I do not understand at all.
Can you give me a hint what I am doing wrong here?
node.js and javascript is not my homeground, so maybe my question is silly, but I am always eager to learn. Thank you!

Just to add one more thing: If I console.log the array "files" before and after the sort function, there is a difference, and the array after the sort function is in the correct order. But the csv file is always different, and there seems to be no pattern for the order.

I think the problem is  that the node.js  is tricky by working asynchroniously. It probably explains why "the table is still not sorted by date in descending order. The funny thing is, that if I am starting summaryTable.bat again and agan after deleting the table, the newly generated table is always sorted in a different way". That is, in the asynchronuios mode, one should non expect that the commands are executed in the strict sequence, the command can start earlier than a command before, it's a nightmare for programmers. It is my suggestiom, and honestly, I have no idea about sorting with the node.js promises
https://wanago.io/2018/04/09/explaining-promises-and-callbacks-while-implementing-a-sorting-algorithm/

Just investigating further: Until this line (126) in utilities/summaryTable.js the "file" is correct:
fs.readFile(activitiesFolder + "/" + file, function (err, content) {

But if I console.log "file" after this line, "file" is suddenly different. How come?

Ended up with a very awkward "solution": At the end of summaryTable.js I added some code to open the CSV file, sort the entries and write the CSV file again. If I find the time I will probably think about a better solution ...

s I added some code to open the CSV file, sort the entries and write the CSV file again

if it's so, the reason is certainly because of asynchronuios  features. Anyway, whatever working is better than anything not.


Invalid HTML output for empty attributes

Got a spec where  is being spit out as  which is invalid. Please don't do that. Thanks~

 and  are equally valid or invalid... I think both invalid because both have an empty string href attribute which is not a valid URL.


Better readme?

Would be fantastic to have a better readme in this repo to showcase the benefits of the format
cc @whyrusleeping @diasdavid @lgeirth @richardlitt

I had this conversation with @diasdavid, trying to build up from first principles why multiaddresses are useful && justified. I like the way it starts at the state of the world today and addresses each obvious response, leading to the domain that multiaddr expresses that we cannot otherwise achieve today. (or: show the lock before the key)
Imagine trying to describe, a way that you can connect to a peer, without having a canonical way to present its address
I could have custom formats by transport

we have IP addresses and ports

but ip+port might be valid for a uTP connection, but not for a TCP connection
if I tell you
reach out to me on <IP_ADDRESS>:9090
which transport will you use?

*nod* Right. So we have utp://<IP_ADDRESS>:9090
(I'm building from first principles; humour me)

right, now what I want to describe a webrtc-noffle addr that has to pack an id + a signalling server I can use?

SDP?

SDP would not fulfil it completely, but I get your point, there has been historically a panoply of addr formats, why add a new one
the problem that it solves is a way to have a canonical way to represent addrs that is also extensible
meaning that it is flexible enough for the transports that there will still come
and can also represent any of the current ones


Update room version to 2.3.0

Describe the Issue
https://developer.android.com/jetpack/androidx/releases/room#version_230_3
Would you like to work on the issue?
:)

Yes Sure :)

I was seeking the code to find what i was referring to but just found another issue, these Transaction annotations are no op:
https://github.com/google/android-fhir/blob/1992c7a03e13f71a88bff72177901bc048237729/engine/src/main/java/com/google/android/fhir/db/impl/DatabaseImpl.kt#L64
Because that is not a class Room parses. Transaction annotation only works on Room DAO's so this code needs to use a real transaction (db.withTransaction {} )
The main reason i asked for an update was because I thought we had some TypeConverteer's that needs other values injected but seems like we don't have that case. Regardless, it is still good to update.


getting-started: install-fioctl: Fixing and improve token creation

Signed-off-by: Raul Muñoz<EMAIL_ADDRESS>

Docs for 6732d6c5c7cc1d2a2cf258f67c85079a2d88e1b1 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1067/docs/artifacts/html/index.html

Docs for c59298cb4ffddcafba13f0b253aa1f0592033247 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1068/docs/artifacts/html/index.html

Docs for 28e1f521d3ffdf5b5b8aead54f1aab075d229627 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1069/docs/artifacts/html/index.html


create urls.py for app_template

This has been proposed before and the decision was to keep the app template minimal.


Clear data log when main.py is opened for write

https://github.com/microbit-foundation/micropython-microbit-v2/commit/6ade36b3cb26f6b945606a61763422ed630155f5 introduced a change that clears the data log on opening main.py for write. We have our own main.py and our own file system so don't get that in the simulator for free.
However, we already clear the log on flash, so I think this would just catch self-rewriting programs in the simulator context.  For that reason I don't think it's worth doing right now as part of #47 as we're pressed for time.

I agree, if every time the "play" button is pressed it clears the log there is no need to do much else right now.
After launch we can look into adding the hook for self-modifying programmes, but it's safe to assume the impact will be almost insignificant.


Add ability to reject chapters that are external links

kojirou.exe -l en --autocrop --rank views-total a2febd3e-6252-46eb-bd63-01d51deaaec5 --dry-run
Here is an example of a manga with problematic output. The links chosen for chapter 1-3 aren't hosted on MD and so don't make it into the final 0001.azw3 file - instead it simply starts at chapter 4.
I can work around this by specifying --rank most but I'd like either more fine-grain chapter selection or an automagic way to reject external links for chapters.
I don't think attempting to follow the links and download from there is a viable solution given that I can't even follow the link in my Firefox browser :/

I've had a fix for this issue locally for quite some time, I just forgot to push it. The fix is now on master. I'll also create a new release with these fixes in the next few minutes. :)
As you've said, the only realistic fix here is just rejecting these "external" chapters, so that's what we now do.

New release with prebuilt binaries is available, this should fix your issue. Thanks for reporting!


Update fetch.mdx

Appreciate was spelled wrong

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


Support a closeTimeout prop for useTooltip

Summary
Alex suggested that:

a closeTimeout that defaults to 0 but can be increased to leave the tooltip visible for a bit longer for these cases where there's something we want to click

This is very helpful when the tooltip contains a link.

Main Story: ch67249
:vertical_traffic_light: Acceptance criteria

[x] There is a story showcasing how to have the tooltip close 5 seconds after the mouse leaves

Implementation Tasks

Deployment
Before merge to master
Note: Code merged to master should be safe to automatically deploy to production as-is.

[ ] [QA] User-testing/quality assurance done

After merge to master

@alexanderchan @wesleycole i just ran lerna publish 😂 i think i'm supposed to wait for approval before that command

@alexanderchan @wesleycole i just ran lerna publish 😂 i think i'm supposed to wait for approval before that command

ahh no worries, we should probably try to automate the package deployment side of things to simplify this all maybe with gh actions.
We might also consider moving from lerna to just yarn workspaces + changesets.  This is emotion's pr for the changeset side of things: https://github.com/emotion-js/emotion/pull/1343/files


arch/intel64/irq.h: rename rdtsc macros

Summary

arch/intel64/irq.h: rename rdtsc macros
rename _rdtsc macro to rdtsc to avoid conflict with external code rename rdtsc macro to rdtscp to be the same as asm instruction used

Impact
Testing
CI

let's ignore the unrelated riscv ci error.


"Go to file" truncates paths and is non-resizable

Version: 1.45.1 (system setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:35.169Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:

Create a deep directory hierarchy
Create several files with the same name in different directories
Press Ctrl+P and type in the name of the file

There is no way to uniquely identify the files if they differ in the deepest directory level.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

This issue has been reported already in either this or a similar form. Please check the label that was assigned to this issue to find it.

To save others the eyeball-grep: https://github.com/microsoft/vscode/issues/85374


vere: init at 1.20

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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.

cc @laMudri maintainer of previous urbit package

@matthew-levan Can you replace this PR with my commit at https://github.com/NixOS/nixpkgs/compare/master...ryantm:nixpkgs:vere ? I did some various small polishing steps based on this linter https://github.com/jtojnar/nixpkgs-hammering and I renamed all instances of "vere" (except the src repo) to "urbit". This seems more consistent with how the AUR is packaging it https://aur.archlinux.org/packages/urbit

@matthew-levan Can you replace this PR with my commit at master...ryantm:nixpkgs:vere ? I did some various small polishing steps based on this linter https://github.com/jtojnar/nixpkgs-hammering and I renamed all instances of "vere" (except the src repo) to "urbit". This seems more consistent with how the AUR is packaging it https://aur.archlinux.org/packages/urbit

Done.


Add own viewer project

I have developed my own label render logic, which is currently only a prototype but actually works quite well.

This is impressive. So BinaryKits.Zpl.Viewer generates the label without calling Labelary.

This is impressive. So BinaryKits.Zpl.Viewer generates the label without calling Labelary?

yes

I can't even think how to handle the strange multi line behavior...

My goal is not to build a perfect renderer but to generate a rough preview. The more accurate it becomes the better. There are some zpl files in the TestUi that I have tested with. You can try them with the WebApi. When you start it there is a small test application in the root.

I would suggest to include the viewer in the main project. The basic functions are implemented. Now the finishing touches need to be made. Maybe you could optimize my web interface for testing. I have built it very minimalistic. The Labelary Client we could
publish from my point of view also as nuget package.

Just alight few doubts

include the viewer in the main project
Do you mean "Zpl.Label" project? How will it be linked/used?

optimize my web interface for testing
Any suggested direction?

The Labelary Client nuget
"BinaryKits.Zpl.Labelary" ?

Just alight few doubts

include the viewer in the main project

No, the viewer has his own nuget package

Do you mean "Zpl.Label" project? How will it be linked/used?

optimize my web interface for testing

Any suggested direction?

Maybe this project has his own  docker container to publish in the future.

The Labelary Client nuget

"BinaryKits.Zpl.Labelary" ?

Yes

Btw, I believe permission is given so you no longer need to fork (if you prefer).

"I would suggest to include the viewer in the main project."
Still confused about this part. Do you mean include viewer in the main solution? But that's already the case:

yes in the solution 😄

I just wanted to say that the viewer project is ready

https://www.nuget.org/packages/BinaryKits.Zpl.Labelary/
NuGet is there, not enough description?

@YipingRuan i'm not a great writer. but if you can think of something useful, feel free to expand it.


Unresolved reference: ReactNativeBlobUtil since 0.21.1

Using Self-Signed SSL Server doesn't seem to be working anymore after updating to 0.21.1. Been using 0.19.4 before and it was running just fine.
React Native: 0.75.4
React-Native-Blob-Util: 0.21.1
When trying to run Android debug, following errors occur.
Errors:
Unresolved reference: ReactNativeBlobUtil
Unresolved reference: ReactNativeBlobUtilUtils

Reverting to 0.19.4 builds the App just fine again.
MainApplication.kt
package de.xxx.xxx

import android.app.Application
import com.facebook.react.PackageList
import com.facebook.react.ReactApplication
import com.facebook.react.ReactHost
import com.facebook.react.ReactNativeHost
import com.facebook.react.ReactPackage
import com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.load
import com.facebook.react.defaults.DefaultReactHost.getDefaultReactHost
import com.facebook.react.defaults.DefaultReactNativeHost
import com.facebook.soloader.SoLoader
import java.security.cert.CertificateException
import java.security.cert.X509Certificate
import javax.net.ssl.X509TrustManager
import com.ReactNativeBlobUtil.ReactNativeBlobUtilUtils

class MainApplication : Application(), ReactApplication {

  override val reactNativeHost: ReactNativeHost =
      object : DefaultReactNativeHost(this) {
        override fun getPackages(): List<ReactPackage> =
            PackageList(this).packages.apply {
              // Packages that cannot be autolinked yet can be added manually here, for example:
              // add(MyReactNativePackage())
            }

        override fun getJSMainModuleName(): String = "index"

        override fun getUseDeveloperSupport(): Boolean = BuildConfig.DEBUG

        override val isNewArchEnabled: Boolean = BuildConfig.IS_NEW_ARCHITECTURE_ENABLED
        override val isHermesEnabled: Boolean = BuildConfig.IS_HERMES_ENABLED
      }

  override val reactHost: ReactHost
    get() = getDefaultReactHost(applicationContext, reactNativeHost)

  override fun onCreate() {
    super.onCreate()
    SoLoader.init(this, false)
    ReactNativeBlobUtilUtils.sharedTrustManager = object : X509TrustManager {
        override fun checkClientTrusted(chain: Array<java.security.cert.X509Certificate>, authType: String) {
        }

        override fun checkServerTrusted(chain: Array<java.security.cert.X509Certificate>, authType: String) {
        }

        override fun getAcceptedIssuers(): Array<java.security.cert.X509Certificate> {
            return arrayOf()
        }
    }
    if (BuildConfig.IS_NEW_ARCHITECTURE_ENABLED) {
      // If you opted-in for the New Architecture, we load the native entry point for this app.
      load()
    }
  }
}

@javache are you aware of any problems here with the new extended Baseclass?
Thsat's the only change I can imagine that broke something here.

BaseReactPackage was introduced in RN 0.74 and hasn't changed significantly since - you'll want to bump your min version, but that doesn't seem to be the problem here.

Have to try it in a base project then - sounds strange.
is it working normally without th custom trustManager?

Is it working normally without th custom trustManager?

It successfully builds then, yes

I am working on reproducing it and seeing what's wrong

However, there is a crash on startup with "Cannot read property 'getConstants' of null" here

Experiencing the same issue on Expo 52 with React Native 76. Can confirm downgrading works for me too

Seems like the autolinking broke...
But still not sure why exactly

That's the cause of it:
https://github.com/react-native-community/cli/pull/2563
So nothing on my side, but still nasty...
So there are basically 3 solutions:

See if you manage to update the cli to the patched version
Fix the cli manually by editing the file: @react-native-community\cli-platform-android\build\config\findPackageClassName.js as shown in the linked merge. Basically you just have to adjsut the regex at the end of the file. And afterwards you must clear android/build
downgrade this library until a fixed version of RN is available and you can upgrade

Thank you for investigating @RonRadtke! Lets wait for RN to fix it.

Thank you for investigating @RonRadtke! Lets wait for RN to fix it.

I am in contact with RN devs there

@Relax594 I just found a work-around to trick autolinking. It's released as a new version


ViewContainerRef in parent

I have a root component AppComponent which all other components derive from. Now, because ViewContrinerRef needs to be injected in the constructor, the AppComponent ends up with the last child's ViewContainerRef.
There is a modal in AppComponent which I want to show. But, its reference though @ViewChild is always undefined. That is because the viewContainerRef in AppComponent is of a child, and not of the parent.
Can you suggest me what should be done in this case?

Same problem here

In latest versions I have removed requirement of viewContainerRef, it is needed only for ngUpgrade apps

So

remove viewContainerRef
clean install latest or latest @beta version
if did not helped please use plunkr from readme and create a plunkr to reproduce your issue

if above did not fixed your issue, please refer to https://github.com/valor-software/ng2-bootstrap/blob/development/components/utils/components-helper.service.ts#L25-L43


Fix broken links

Motivation and Context

The links of tutorials is broken, and I fixed it according to the PyTorchVideo website.
How Has This Been Tested

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Looks great, thanks for the PR!


chore(main): release 0.7.0

:robot: I have created a release beep boop
0.7.0 (2023-12-14)
Features

day14 completed (7ffa584)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fretboarder/aoc23/releases/tag/v0.7.0 :sunflower:


FIX: Inform SynthStrip about the desired intraop threads

Necessary too for Nipype to execute resource management. This PR alleviates the problems of memory with SynthStrip by (1) setting a reasonable number of CPUs when operating in that mode [memory fingerprint drops as numpy is not so overeager]; and (2) permits nipype to execute resource management, ensuring there are not too many synthstrip instances operating at once.
As long as SynthStrip's model continues to be as large, and as long as pytorch does not implement all the layers in the model with half-precision, this is the best we can do at the moment.
Resolves #1004.

Tested locally. Please reopen if you look at the code and some concern emerges.


Bookstore: styling

In this Pull Request I:

Add the missing JSX elements to the project (without adding extra functionality).
Add styling to the Application

@Zuhaib042 Thank you for the review


Exercise Suggestion: Pi-syntax

Hi. I like this book a lot, but I think it could have more exercises. In the quantifiers chapter, there's an example on the use of the syntax keyword that introduces the existential quantifier. As an extra exercise, I defined a datatype that captures dependent functions and declared a syntax similar to the Sigma syntax. The Pi type turned out to be almost the same as Sigma type, only with different associativity in the type of the value constructor. I think that making this discovery might be useful for newcomers like myself. It helps to appreciate the difference between dependent sum and product types.

I think this is a great idea! What about you, @wadler?

@jllang Just to mention this, though, I'm pretty sure you can do this just fine without defining a datatype for it. Just a bit of syntax should be enough.

Wow, I even managed to define an infix arrow syntax similar to lambda abstraction for constructing values of my Pi type!

It is remarkable how even function types aren't truly special in Agda

They're pretty special, in the sense that you can't pattern match on their structure.

OK, that's true. Still, I'm quite surprised that I could define my own lambda abstraction equivalent.

If you want to propose a new exercise for the book, please submit it in a pull request and I will be happy to review it. From the description above, it wasn't clear to me exactly what you had in mind.


async support?

Hi, cool project. Since the underlying Moka project describes itself like:

Thread-safe, highly concurrent in-memory cache implementations:

Synchronous caches that can be shared across OS threads.
An asynchronous (futures aware) cache.

I was wondering if you're planning on adding an async/await version of the API.

Hi, this will work for your async functions.
import asyncio
import time

from moka_py import cached

@cached(maxsize=1024, ttl=10.0, tti=1.0)
async def f(x, y):
    print("hard computations")
    await asyncio.sleep(5)
    return x + y

if __name__ == "__main__":
    start = time.time()
    print(asyncio.run(f(1, 2)))
    print(asyncio.run(f(1, 2)))
    print(time.time() - start)

# hard computations
# 3
# 3
# 5.002709865570068

Awesome, good to know.
Does it make sense for cache.get() and cache.set() to have async partners?

Hi!

Does it make sense for cache.get() and cache.set() to have async partners?

I doubt it. cache.get() takes ~230ns (nanoseconds) on average (4.42 millions calls per second) and cache.set() takes ~740ns on average (1.35 millions calls per second) for a cache of size 10000 that's fully occupied. Therefore, adding async machinery would be unnecessary overhead.
In future, I plan to add an async partner for Moka.get_with which seems reasonable (since it will need to receive a Python async function and run it somewhere in Rust runtime). But for now, exporting async functions is experimental in pyo3 (this is why with_concurrent=True is not supported for async functions in moka_py.cached() decorator)

Thanks for the extra per info. Makes sense. I plan on covering this project on the next https://pythonbytes.fm/ so having a little more inside info is helpful.


Support shared library build with g++/clang

See https://github.com/abdes/cryptopp-cmake/issues/1#issuecomment-1228782765
See https://github.com/abdes/cryptopp-cmake/issues/1#issuecomment-1228791939
We need to find the proper way to set cmake for a shared library build with all symbols exported when using g++/clang. With such build, cryptest need to be linked against the shared library and all tests need to pass.

Will not be implemented.


Logs to debug remote write issues

I created an aws timestream db named prometheus-database and a table named prometheus-table.
I modified the region on main.go to match my region.
Build and pushed the docker image to ecr.
I have prometheus running in a kubernetes cluster. I patched the prometheus container,
  ...
  containers: # container for your adapter
    - name: timestream-adapter
      image: xxx.dkr.ecr.us-east-1.amazonaws.com/timestream-adapter
  remote_write:
    url: "http://localhost:9201/write"

The pod is named prometheus-prometheus-0. I see the timescream-adapter running on the pod,
k describe pod prometheus-prometheus-0 -n prometheus
Name:         prometheus-prometheus-0
...
Containers:
...
  timestream-adapter:
    Container ID:   docker://a7ec874984a973bf588acb8810fc9bc20357a8014ba0aa9ca0d3eeae7ca50296
    Image:<PHONE_NUMBER>85.dkr.ecr.us-east-1.amazonaws.com/timestream-adapter
    Image ID:       docker-pullable://285651481985.dkr.ecr.us-east-1.amazonaws.com/timestream-adapter@sha256:4f73e6a3b127685924056497b6650f76043353a5637a1883dfcfea9d27a9b2cc
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Thu, 27 Jan 2022 14:14:36 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zm6mb (ro)
...

I can't see any data in the database. Is there a way to print some logs to checl for some connectivity issues?
k logs prometheus-prometheus-0 -n prometheus -c timestream-adapter
does not print anything

I solved this by correctly patching prometheus with,
  ...
  containers: # container for your adapter
    - name: timestream-adapter
      image: xxx.dkr.ecr.us-east-1.amazonaws.com/timestream-adapter
  remoteWrite:
    - url: "http://localhost:9201/write"


Show warning message if BigInt64Array is not available

Closes #183. @Keavon is this roughly what you imagined? I'm a bit of a vuejs novice so I'm sorry if I approached this wrong.

This change is

This looks great! Let me make a few adjustments to the text if you don't mind.
Your browser currently doesn't support Graphite

Unfortunately, some features won't work properly in your browser. Please use a modern browser other than Safari, such as Firefox, Chrome, or Edge. Rest assured, Safari compatibility is planned.

Your browser is missing support for the BigInt64Array JavaScript API which is required for using the editor. You can still explore the user interface.

I understand, let's just see the interface

(you'll want to style the link to use the accent color)

Tiny nitpicks in the code:

Let's use a 4px border-radius instead of 5px
Instead of 100vw and 100vh, it might be safer to use right: 0 and bottom: 0 (disregard if this doesn't work, I haven't tested it)
For the padding, we don't use the rem unit anywhere else in Graphite, but we try to use multiples of 4px everywhere
Use two  tags for the two paragraphs in the altered text above
Remove the units from your 0-valued CSS properties like 0px and 0rem, so it just says 0 instead for those


int64_t support

Looks like there is no full support for int64_t with sqlite3. since, sqlite3 datatype SQLITE_INTEGER is mapped to soci::dt_integer in soci. I guess it needs to be mapped to soci::dt_long_long. But it is a breaking change.
Also, the common api : soci::get_last_insert_id gives int32_t which may also need to be changed.

There is chance for a breaking change to be accepted into SOCI 4.
If you'd be willing to provide a PR, so it can be CI tested. Then, we will be able to review and decide.
/cc @vadz

Getting below error while compiling in travis.
In file included from /usr/include/c++/4.6/cstdint:35:0,
                 from /home/travis/build/SOCI/soci/include/soci/soci-backend.h:15,
                 from /home/travis/build/SOCI/soci/include/soci/backend-loader.h:11,
                 from /home/travis/build/SOCI/soci/src/core/backend-loader.cpp:10:
/usr/include/c++/4.6/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the upcoming ISO C++ standard, C++0x. This support is currently experimental, and must be enabled with the -std=c++0x or -std=gnu++0x compiler options.```

shall i change the flags with -std=c++0x?

See https://github.com/SOCI/soci/pull/720#issuecomment-475188038

@mloskot , Thanks for merging the get_last_insert_id changes to support 64 bit value.
Getting back to the first isssue,

SQLITE_INTEGER is mapped to soci::dt_integer in soci. I guess it needs to be mapped to soci::dt_long_long as an option/default to read 64 bit value.

need some comments. because, reading 64bit value from sqlite3 is a must for me.

The 64-bit integer support is there, but you mean https://github.com/SOCI/soci/pull/721#issuecomment-475324131
If there is no clear way to detect those as BIGINT, I have no any immediate recommendations how to work around this.
By the way, AUTOINCREMENT is best avoided:

The AUTOINCREMENT keyword imposes extra CPU, memory, disk space, and disk I/O overhead and should be avoided if not strictly needed. It is usually not needed.

https://www.sqlite.org/autoinc.html

I'm afraid that not only I don't have the solution to the problem, but I don't even really understand what exactly the problem is. You seem to imply that it's related to dt_integer interpretation, but where exactly is this problematic?
I must also admit that I'm somewhat confused by data_type enum in general as it's not really clear what exactly is it supposed to represent and where is it used. In particular, it seems pretty weird that it has just dt_integer (and not dt_short, dt_unsigned and all the other combinations) but both dt_long_long and dt_unsigned_long_long...

I have changed my column types from INTEGER to BIGINT and even the foreign keys referring to AUTOINCREMENT INTEGER. Things working as expected.

@vadz Yes, that is confusing and an improvement would be to simply cover all C++ fundamental types. Long time ago I started sketching the idea https://github.com/SOCI/soci/wiki/RFC1 but I never had time to go around. Something for 5.0.0.


LND cant start anymore 'runtime: out of memory' Raspberry Pi 3

Background
By 'RaspiBollt' tutorial get worked 0.4.0 LND on testnet.
Possible after not correctly shutdown (weak/bad power supply on RaspPi or external HDD or both) LND can't start after wallet unlock.
Upgrade to 0.4.1 beta didn't help.
Bitcoind fully synced.
Memory usage:
              total        used        free      shared  buff/cache   available
Mem:           976M        101M        818M        1.0M         56M        826M
Swap:          2.0G        380M        1.6G

After LN unlock:
Apr 04 23:42:41 SkyCry lnd[6528]: 2018-04-04 23:42:41.766 [INF] LNWL: The wallet has been unlocked without a time limit
Apr 04 23:42:41 SkyCry lnd[6528]: 2018-04-04 23:42:41.766 [INF] LTND: LightningWallet opened
Apr 04 23:44:20 SkyCry lnd[6528]: runtime: out of memory: cannot allocate 374341632-byte block<PHONE_NUMBER> in use)
Apr 04 23:44:20 SkyCry lnd[6528]: fatal error: out of memory
Apr 04 23:44:20 SkyCry lnd[6528]: runtime stack:
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.throw(0x8c7f9c, 0xd)
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/panic.go:619 +0x60
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.largeAlloc(0x16500000, 0x60101, 0x76f39000)
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/malloc.go:828 +0xdc
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.mallocgc.func1()
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/malloc.go:721 +0x38
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.systemstack(0x0)
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/asm_arm.s:349 +0x80
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.mstart()
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/proc.go:1170
Apr 04 23:44:20 SkyCry lnd[6528]: goroutine 84 [running]:
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.systemstack_switch()
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/asm_arm.s:294 +0x4 fp=0x12f4ac54 sp=0x12f4ac50 pc=0x68c0c
Apr 04 23:44:20 SkyCry lnd[6528]: runtime.mallocgc(0x16500000, 0x81f080, 0x4282a601, 0x179f4)
Apr 04 23:44:20 SkyCry lnd[6528]:         /usr/local/go/src/runtime/malloc.go:720 +0x86c fp=0x12f4acb4 sp=0x12f4ac54 pc=0x21130
Apr 04 23:44:21 SkyCry systemd[1]: lnd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 04 23:44:21 SkyCry systemd[1]: lnd.service: Unit entered failed state.
Apr 04 23:44:21 SkyCry systemd[1]: lnd.service: Failed with result 'exit-code'.

Memory usage at time around error:
              total        used        free      shared  buff/cache   available
Mem:           976M        916M         39M        672K         20M         25M
Swap:          2.0G        596M        1.4G

Environment

lnd version 0.4.1-beta commit=
Linux SkyCry 4.14.30-v7+ #1102 SMP Mon Mar 26 16:45:49 BST 2018 armv7l GNU/Linux
Bitcoin Core Daemon version v0.16.0

bitcoin.conf:
# RaspiBolt LND Mainnet: bitcoind configuration
# /home/bitcoin/.bitcoin/bitcoin.conf

# remove the following line to enable Bitcoin mainnet
testnet=1

# Bitcoind options
server=1
daemon=1
txindex=1
disablewallet=1

# Connection settings
rpcuser=*
rpcpassword=*
zmqpubrawblock=tcp://<IP_ADDRESS>:29000
zmqpubrawtx=tcp://<IP_ADDRESS>:29000

# Raspberry Pi optimizations
dbcache=100
maxorphantx=10
maxmempool=50
maxconnections=40
maxuploadtarget=5000

lnd.conf:
# RaspiBolt LND Mainnet: lnd configuration
# /home/bitcoin/.lnd/lnd.conf

[Application Options]
debuglevel=trace
debughtlc=true
maxpendingchannels=5
alias=Lightning-Moon
color=#640d89

[Bitcoin]
bitcoin.active=1

# enable either testnet or mainnet
bitcoin.testnet=1
#bitcoin.mainnet=1

bitcoin.node=bitcoind

[autopilot]
autopilot.active=1
autopilot.maxchannels=5
autopilot.allocation=0.6

If I need to provide you more information, please keep in mind I'm not very good with Linux.

Apr 04 23:44:20 SkyCry lnd[6528]: runtime: out of memory: cannot allocate 374341632-byte block<PHONE_NUMBER> in use)

Looks like you might need to allocate some swap to the system. The initial scrypt on start up can be a bit memory intensive, but the memory will quickly be released once key derivation is finished.

Which version of Go are you running?
Actually looking at the mem report, you shoud definitely have enough:
              total        used        free      shared  buff/cache   available
Mem:           976M        916M         39M        672K         20M         25M
Swap:          2.0G        596M        1.4G

At that time I did not have Go, but now I have go version go1.10.1 linux/arm

If you manually compile from master, and re-attempt are results different?

lnd version 0.4.1-beta commit=e30881a14cdd5d9f17132acc99dd46d331f6f61f
The same sesults:
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.484 [INF] LTND: Version 0.4.1-beta commit=e30881a14cdd5d9f17132acc99dd46d331f6f61f
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.485 [INF] LTND: Active chain: Bitcoin (network=testnet)
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.608 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.661 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:10009
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.661 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080
Apr 06 23:34:22 SkyCry lnd[21619]: 2018-04-06 23:34:22.662 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create wallet, or `lncli unlock` to unlock already created wallet.
Apr 06 23:42:40 SkyCry lnd[21619]: 2018-04-06 23:42:40.121 [INF] LNWL: Opened wallet
Apr 06 23:42:40 SkyCry lnd[21619]: 2018-04-06 23:42:40.550 [INF] LTND: Primary chain is set to: bitcoin
Apr 06 23:42:40 SkyCry lnd[21619]: 2018-04-06 23:42:40.550 [INF] LTND: Initializing bitcoind backed fee estimator
Apr 06 23:42:46 SkyCry lnd[21619]: 2018-04-06 23:42:46.807 [INF] LNWL: Opened wallet
Apr 06 23:42:47 SkyCry lnd[21619]: 2018-04-06 23:42:46.864 [INF] LNWL: Started listening for blocks via ZMQ on tcp://<IP_ADDRESS>:29000
Apr 06 23:42:53 SkyCry lnd[21619]: 2018-04-06 23:42:53.040 [INF] LNWL: The wallet has been unlocked without a time limit
Apr 06 23:42:53 SkyCry lnd[21619]: 2018-04-06 23:42:53.040 [INF] LTND: LightningWallet opened
Apr 06 23:43:52 SkyCry lnd[21619]: runtime: out of memory: cannot allocate 374341632-byte block (968163328 in use)
Apr 06 23:43:52 SkyCry lnd[21619]: fatal error: out of memory
Apr 06 23:43:52 SkyCry lnd[21619]: runtime stack:
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.throw(0x8c94f7, 0xd)
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/panic.go:616 +0x60
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.largeAlloc(0x16500000, 0x60101, 0x76dc06c8)
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/malloc.go:828 +0xdc
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.mallocgc.func1()
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/malloc.go:721 +0x38
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.systemstack(0x0)
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/asm_arm.s:349 +0x80
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.mstart()
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/proc.go:1175
Apr 06 23:43:52 SkyCry lnd[21619]: goroutine 33 [running]:
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.systemstack_switch()
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/asm_arm.s:294 +0x4 fp=0x12c5fc54 sp=0x12c5fc50 pc=0x6a1ac
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.mallocgc(0x16500000, 0x8200f0, 0x19101, 0x193c8)
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/malloc.go:720 +0x89c fp=0x12c5fcb4 sp=0x12c5fc54 pc=0x22b68
Apr 06 23:43:52 SkyCry lnd[21619]: runtime.newarray(0x8200f0, 0x440000, 0x2613dbc0)
Apr 06 23:43:52 SkyCry lnd[21619]:         /usr/local/go/src/runtime/malloc.go:855 +0x5c fp=0x12c5fcc8 sp=0x12c5fcb4 pc=0x22e64
Apr 06 23:43:55 SkyCry systemd[1]: lnd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 06 23:43:55 SkyCry systemd[1]: lnd.service: Unit entered failed state.
Apr 06 23:43:55 SkyCry systemd[1]: lnd.service: Failed with result 'exit-code'.

Also make check returned some FAILs
make_check.txt

If you increase your swap to say, 4G are the result any different?
This is odd as I run an lnd node a btcd node, and several other services on a box with only 1GB of RAM, yet have no issues.

4G swap do not help.
Looks like wallet.db is somehow broken. What is its normal size? My is 146MB..
Got lnd + bitcoind on windows desktop and fed it that wallet.db. Unlock wallet and lnd very fast get all memory it can (up to 30Gb including swap). wallet.db very fast grew to 256MB. System gets huge lags, lnd "worked" about 10 min and finally crashed.
2018-04-07 17:43:55.963 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create wallet, or `lncli unlock` to unlock already created wallet.
2018-04-07 17:44:12.330 [INF] LNWL: Opened wallet
2018-04-07 17:44:12.391 [INF] LTND: Primary chain is set to: bitcoin
2018-04-07 17:44:12.392 [INF] LTND: Initializing bitcoind backed fee estimator
2018-04-07 17:44:13.153 [INF] LNWL: Opened wallet
2018-04-07 17:44:14.157 [INF] LNWL: Started listening for blocks via ZMQ on tcp://<IP_ADDRESS>:18501
2018-04-07 17:44:14.897 [INF] LNWL: The wallet has been unlocked without a time limit
2018-04-07 17:44:14.897 [INF] LTND: LightningWallet opened
2018-04-07 17:55:00.582 [DBG] LNWL: Filtering block 1291878<PHONE_NUMBER>000490dd50c3bdce8746e00213d1cc5940a4d841060791ee3be549) with 47 transactions

Unlock wallet and lnd very fast get all memory it can (up to 30GB including swap). wallet.db very fast grew to 256MB. System gets huge lags, lnd "worked" about 10 min and finally crashed:

There must be something peculiar with your set up, I run lnd on machines that have much less RAM and don't run into any issues during start up or operation. Note that wallet.db isn't the only database that lnd uses, if you swap that one out, but don't also move the others, then you may run into issues during startup.

Note that wallet.db isn't the only database that lnd uses, if you swap that one out, but don't also move the others, then you may run into issues during startup.

Well actually before I copy wallet.db to my windows machine I created new wallet there, so I though all necessary files were there. Never mind, when copied all files from raspi lnd dir to the windows one nothing is changed: unlock wallet -> lnd eats all memory -> system lags -> lnd die.

Can you reproduce this with a fresh installation?

If you activate profiling, then attempt with the original wallet.db, what shows up in the CPU trace?

I ran out of memory on my Raspberry Pi a while back, and had this same issue, even after adding swap. The way I cleared it was to kill all lnd created files (in my case in the ~/.lnd directory), and then it runs fine with 2GB of swap. Here is my current memory with lnd and bitcoind running.
          total        used        free      shared  buff/cache   available

Mem:         949580      524596       26868       35492      398116      335764
Swap:       2047996       44604     2003392

Can you reproduce this with a fresh installation?

I made a new RasPi installation on a separate SD card. I created a new wallet, and everything still works. Tried to use an old wallet here and receive exectly the same error as in the opened message.
On Windows10 desktop I have the same thing, a new wallet from RaspPi works and the old one does not.

If you activate profiling, then attempt with the original wallet.db, what shows up in the CPU trace?

Yes I know some words)) Actually I do not know what I do but here is screen..

I think we're just wasting time here. I can provide this file if someone is interested (it's testnet with a random password).

I see a very similar signature running on iOS. Not sure if I should open a different issue over this. I also suspect this has something to do with improper shutdowns. I occasionally hit 'out of memory' upon unlocking the wallet after an improper LND shutdown. But if I restart LND then I might be able to recover again. The probability of hitting this is much higher on iPhone 5S (1GB memory) vs iPhone X (3GB memory). This is master commit 4ab2bba5c7bad9f1b1b7d7c9855e0e82194cab6a (dated April 27th)
2018-05-05 09:10:33.649 [WRN] LTND: open /var/mobile/Containers/Data/Application/CDA6EA8C-F993-4A99-B82B-DD2B94636787/Library/Application Support/lnd/lnd.conf: no such file or directory 2018-05-05 09:10:33.650 [INF] LTND: Version 0.4.1-beta commit= 2018-05-05 09:10:33.651 [INF] LTND: Active chain: Bitcoin (network=testnet) 2018-05-05 09:10:33.972 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2018-05-05 09:10:34.843 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:10009 2018-05-05 09:10:34.846 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080 2018-05-05 09:10:34.846 [INF] LTND: Waiting for wallet encryption password. Use lncli createto create wallet, orlncli unlock` to unlock already created wallet.
2018-05-05 09:10:39.989 [INF] LNWL: Opened wallet
2018-05-05 09:10:40.354 [INF] LTND: Primary chain is set to: bitcoin
2018-05-05 09:10:40.547 [INF] BTCN: Loaded 1052 addresses from file '/var/mobile/Containers/Data/Application/CDA6EA8C-F993-4A99-B82B-DD2B94636787/Library/Application Support/lnd/data/chain/bitcoin/testnet/peers.json'
2018-05-05 09:10:40.551 [INF] CMGR: 3 addresses found from DNS seed testnet-seed.bluematt.me
2018-05-05 09:10:40.551 [INF] CMGR: DNS discovery failed on seed x49.testnet-seed.bitcoin.jonasschnelli.ch: lookup x49.testnet-seed.bitcoin.jonasschnelli.ch: no such host
2018-05-05 09:10:40.552 [INF] CMGR: 50 addresses found from DNS seed testnet-seed.bitcoin.schildbach.de
2018-05-05 09:10:40.769 [INF] BTCN: New valid peer <IP_ADDRESS>:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/)
2018-05-05 09:10:40.779 [INF] BTCN: Syncing to block height 1296416 from peer <IP_ADDRESS>:18333
2018-05-05 09:10:47.754 [INF] LNWL: Opened wallet
runtime: out of memory: cannot allocate 268435456-byte block (274825216 in use)
fatal error: out of memory
runtime stack:
runtime.throw(0x101447e42, 0xd)
/usr/local/Cellar/go/1.10/libexec/src/runtime/panic.go:619 +0x5c
runtime.largeAlloc(0x10000000, 0x100a50101, 0x105158000)
/usr/local/Cellar/go/1.10/libexec/src/runtime/malloc.go:828 +0xec
runtime.mallocgc.func1()
/usr/local/Cellar/go/1.10/libexec/src/runtime/malloc.go:721 +0x3c
runtime.systemstack(0x100000000)
/usr/local/Cellar/go/1.10/libexec/src/runtime/asm_arm64.s:229 +0x8c
runtime.mstart()
/usr/local/Cellar/go/1.10/libexec/src/runtime/proc.go:1170
goroutine 90 [running]:
runtime.systemstack_switch()
/usr/local/Cellar/go/1.10/libexec/src/runtime/asm_arm64.s:178 +0x8 fp=0x10e358f60 sp=0x10e358f50 pc=0x100a591c0
runtime.mallocgc(0x10000000, 0x1012d1400, 0x1, 0x10e82c000)
/usr/local/Cellar/go/1.10/libexec/src/runtime/malloc.go:720 +0x760 fp=0x10e359010 sp=0x10e358f60 pc=0x100a17098
runtime.makeslice(0x1012d1400, 0x4000000, 0x4000000, 0x10e82c000, 0x200, 0x200)
/usr/local/Cellar/go/1.10/libexec/src/runtime/slice.go:61 +0x74 fp=0x10e359040 sp=0x10e359010 pc=0x100a45f0c
github.com/biscottigelato/SwiftLightning/vendor/github.com/btcsuite/golangcrypto/scrypt.Key(0x10e45e078, 0x8, 0x8, 0x10e740fc8, 0x20, 0x20, 0x40000, 0x8, 0x1, 0x20, ...)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/btcsuite/golangcrypto/scrypt/scrypt.go:235 +0xd0 fp=0x10e359100 sp=0x10e359040 pc=0x100c2cde8
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/snacl.(*SecretKey).deriveKey(0x10e740fc0, 0x10e359970, 0x10e48c2a0, 0x100c3fa70)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/snacl/snacl.go:114 +0x6c fp=0x10e3591a0 sp=0x10e359100 pc=0x100c2d504
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/snacl.(*SecretKey).DeriveKey(0x10e740fc0, 0x10e359970, 0x10e506000, 0x10e359230)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/snacl/snacl.go:201 +0x28 fp=0x10e359200 sp=0x10e3591a0 pc=0x100c2db30
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/waddrmgr.(*Manager).Unlock(0x10e506000, 0x1091dc6c8, 0x10e2bc200, 0x10e45e078, 0x8, 0x8, 0x0, 0x0)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/waddrmgr/manager.go:1040 +0x284 fp=0x10e359950 sp=0x10e359200 pc=0x100c3fc9c
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet.(*Wallet).walletLocker.func1(0x10168e8e0, 0x10e426010, 0x10e426010, 0x0)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet/wallet.go:1141 +0x90 fp=0x10e3599b0 sp=0x10e359950 pc=0x100dd2168
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/walletdb.View(0x101696160, 0x10e720780, 0x10e74ebc8, 0x0, 0x22706d617453656d)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/walletdb/interface.go:196 +0x58 fp=0x10e359a00 sp=0x10e3599b0 pc=0x100c286e0
github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet.(*Wallet).walletLocker(0x10e45c000)
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet/wallet.go:1139 +0x734 fp=0x10e359fd0 sp=0x10e359a00 pc=0x100dc9f1c
runtime.goexit()
/usr/local/Cellar/go/1.10/libexec/src/runtime/asm_arm64.s:1037 +0x4 fp=0x10e359fd0 sp=0x10e359fd0 pc=0x100a5b87c
created by github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet.(*Wallet).Start
/Users/biscottigelato/gocode/src/github.com/biscottigelato/SwiftLightning/vendor/github.com/roasbeef/btcwallet/wallet/wallet.go:142 +0xc4
goroutine 39 [select]:`

Before running on mobile phones, there're optimizations that need to be done. We don't recommend doing so until that point. If you wish to run on mobile phons, then the best way would be to help with the required optimizations.

Is there an issue that details what exactly is being talked about here?

Closing for now as there've been a few goroutine leaks recently that should have addressed this. If this still arises (upon upgrading to the current master), then I'll re-open this issue.

hi, i have the same issue of memory.
lnd version 0.5.2, running on a raspberry pi3, with 2 gb of swap , with a swap file on external hard drive
runtime: out of memory: cannot allocate 2097152-byte block<PHONE_NUMBER> in use)
fatal error: out of memory
runtime stack:
runtime.throw(0x9dff80, 0xd)
/usr/local/go/src/runtime/panic.go:608 +0x5c
runtime.largeAlloc(0x1ffe00, 0x60101, 0x7e584000)
/usr/local/go/src/runtime/malloc.go:1021 +0x120
runtime.mallocgc.func1()
/usr/local/go/src/runtime/malloc.go:914 +0x38
runtime.systemstack(0x35f0000)
/usr/local/go/src/runtime/asm_arm.s:354 +0x84
runtime.mstart()
/usr/local/go/src/runtime/proc.go:1229
goroutine 14 [running]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_arm.s:298 +0x4 fp=0x3647db4 sp=0x3647db0 pc=0x68530
runtime.mallocgc(0x1ffe00, 0x8c0238, 0x80001, 0x3647e34)
/usr/local/go/src/runtime/malloc.go:913 +0x86c fp=0x3647e18 sp=0x3647db4 pc=0x1af38
runtime.makeslice(0x8c0238, 0x1ffe00, 0x1ffe00, 0x7b38c, 0x7e2bccc0, 0x7e603e00)
/usr/local/go/src/runtime/slice.go:70 +0x68 fp=0x3647e2c sp=0x3647e18 pc=0x53138
bytes.makeSlice(0x1ffe00, 0x0, 0x0, 0x0)
/usr/local/go/src/bytes/buffer.go:231 +0x58 fp=0x3647e48 sp=0x3647e2c pc=0x7b528


Update Storage Version to use v1beta1

Changes
Update SHP Controllers to operate on v1beta1 API resources
Move storage version to v1beta1, instead of v1alpha1
Update webhook conversion functions to come from v1alpha1 instead of v1beta
Fixes #1107
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Set the storage version to v1beta1 and update Shipwright controllers to operate on the same.

@qu1queee I was testing the changes, and my buildah build failed because I missed out on specifying  source.type as Git in the yaml. I believe, we have kept it "optional" intentionally, but, with the introduced changes, we might either need to make it as required, or probably add some logic to specify the type considering the source.git. Please let me know if I am missing something.


Error when trying to add an export policy to a NetappFiles Volume - AttributeError: 'NoneType' object has no attribute 'rules'

When I first try the command, I was using this version of az-cli
{
  "azure-cli": "2.14.1",
  "azure-cli-core": "2.14.1",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {}
}

Then I have upgraded to the last version
{
  "azure-cli": "2.31.0",
  "azure-cli-core": "2.31.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {}
}

but nothing has changed
Describe the bug
Command Name
az netappfiles volume export-policy add
Errors:
The command failed with an unexpected error. Here is the traceback:
'NoneType' object has no attribute 'rules'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 658, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 713, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/command_modules/netappfiles/_exception_handler.py", line 18, in netappfiles_exception_handler
    raise ex
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 692, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 200, in handler
    instance = custom_function(instance=instance, **custom_func_args)
  File "/usr/lib64/az/lib/python3.6/site-packages/azure/cli/command_modules/netappfiles/custom.py", line 301, in add_export_policy_rule
    for rule in instance.export_policy.rules:
AttributeError: 'NoneType' object has no attribute 'rules'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
I want to add an export policy to allow all clients to connect to this volume using the NFSv3 protocol (the same used when I created the volume)

az netappfiles volume export-policy add -g resourcegroup --account-name accountname --pool-name poolname --name volumename --allowed-clients <IP_ADDRESS> --rule-index 1 --unix-read-only false --unix-read-write true --cifs false --nfsv3 true --nfsv41 false

I also tried with --allowed-clients "<IP_ADDRESS>" and --allowed-clients "<IP_ADDRESS>/0" but no lucky
Expected Behavior
Environment Summary
Linux-4.18.0-305.17.1.el8_4.x86_64-x86_64-with-redhat-8.3-Ootpa, Red Hat Enterprise Linux 8.3 (Ootpa)
Python 3.6.8
Installer: RPM

azure-cli 2.31.0

Additional Context

#20818 #20809 #20796 #20815 #20796

route to service team

@pjnroll Apologies for the late reply. Could you please use the most recent version of AzCLI and let us know if you are still running into the same issue ? Awaiting your reply.