Beta.4-5 breaking changes & full wagmi support

Hi everyone, we have released beta.4 which under the hood gets rid of our custom react hooks and controllers and instead provides full support for https://wagmi.sh
Wagmi is a great library that we were already using before, but were not able to provide full integration for until now.
React
Please follow updated documentation to see how to set up web3modal with wagmi.
Once integrated, you will need to replace all @web3modal/react hooks with ones from wagmi. See Wagmi Documentation for all available options. In general this should bring you way more stability and allow to use other wagmi compatible libraries like lens-use for example.
HTML / JS
Similar to how react no longer has hooks, vanilla no longer uses controllers. Instead you can import and use core functions like getAccount / watchAccount / getSigner etc. from @wagmi/core package. See updated example for new integration steps.
We are working with wagmi team to document @wagmi/core lib, but meanwhile feel free to ask questions here and use your editors intelisens / typescript autocompletion to see what is available.
Feel free to use this issue for further questions.

modalConnectors() is not working with the connectors argument in createClient for wagmi. When trying to do so it's getting a type error. See below:

Anyway around this?

I've noticed that this can break in subtle ways if the version of @wagmi/core depended on by wagmi is mismatched when compared to the version used by @web3modal/ethereum and can't be deduped by npm.
Wondering if this could be resolved by adding @wagmi/core to peerDependencies instead of it being a direct dependency?

@nhardy will look into this 👍 @M4cs Could you update wagmi to lates version (if you haven't done so already). There were some breaking changes there and we are using their latest wagmi/core lib

Inconsistencies between versions will be solved in upcoming beta.5 ^

@timefordroids (possible exports: Web3ModalEthereum) this looks like you might be still using an older version i.e. you don't have access to new imports, but do have access to older ones.
Make sure all packages are on beta.5 (fastest way to ensure this is to delete your .lock file and node_modules and just re-install everything fresh)

All the packages were installed in a first-time.
That's what I have in yarn.lock
"@web3modal/core@npm:2.0.0-fbf9251":
  version: 2.0.0-fbf9251
  resolution: "@web3modal/core@npm:2.0.0-fbf9251"
  dependencies:
    valtio: 1.7.0
  peerDependencies:
    "@web3modal/ethereum": "*"
  peerDependenciesMeta:
    "@web3modal/ethereum":
      optional: true
  checksum: b23314261129c8d76b26d27805f4658892cf3fbecc0f179a6989dad9bf31a4dd3f4dc51ac007e8b6859fca14499dc70f90ae3a63c7f980fb2ff36e3dc2d8f728
  languageName: node
  linkType: hard

"@web3modal/ethereum@npm:^2.0.0-beta.5":
  version: 2.0.0-fbf9251
  resolution: "@web3modal/ethereum@npm:2.0.0-fbf9251"
  dependencies:
    "@coinbase/wallet-sdk": 3.5.2
    "@walletconnect/ethereum-provider": 1.8.0
  peerDependencies:
    "@wagmi/core": ">=0.5.x"
    "@web3modal/core": "*"
  checksum: 4e76813c390ea9c0c8117f8bdd88621713a1d5df4c57157944a7cf48865715622c31356f32844a60902a9b4c2b14879ac93666fe2b33677a507218e0d657a113
  languageName: node
  linkType: hard

"@web3modal/react@npm:^2.0.0-beta.5":
  version: 2.0.0-fbf9251
  resolution: "@web3modal/react@npm:2.0.0-fbf9251"
  dependencies:
    "@web3modal/core": 2.0.0-fbf9251
    "@web3modal/ui": 2.0.0-fbf9251
  peerDependencies:
    react: ">=17.x"
    react-dom: ">=17.x"
  checksum: 8fee528e925f9e4bfeec39c2ced7c516b4e527557fcc6d1e6256a6e7c48bb436b5713ab6b1ffd048f035d44115596384fe7e233365c0bbfdc4a4cee6868c5e8f
  languageName: node
  linkType: hard

@timefordroids Hmm that core version looks incorrect, should also be beta.5 not 2.0.0-fbf9251

Just added the exact version of core (2.0.0-beta.5) to package.json and it works now. Thank you.

@timefordroids nice, although, you can probably remove it now as core package is part of react one.

Can someone pls give me a hint what's wrong here?
I did a bundle using browserify to use it in vanilla js without modules (can't use modules in my specific use case)
at the "createClien" step, it throws this error:
bundle_beta5.js:12295 Uncaught TypeError: Class constructor Provider cannot be invoked without 'new'
    at StaticJsonRpcProvider.BaseProvider [as constructor]

Here is the code from bundle at the 12295 line

I keep getting this error even before beta 4.
What am I missing?

@nhardy will look into this 👍 @M4cs Could you update wagmi to lates version (if you haven't done so already). There were some breaking changes there and we are using their latest wagmi/core lib

Fwiw using<EMAIL_ADDRESS>fixed my issue with beta 4 but beta 5 with newest wagmi works 👍

Yep, any wagmi 0.8.x version should be working starting with beta 5 👌

Closing this in favour of beta.6 issue
https://github.com/WalletConnect/web3modal/issues/729

FWIW, following the latest docs, i am still not finding the walletConnectProvidor export from @web3modal/ethereum. Neither with beta.5 or beta.7

@archae0pteryx Should definetely be there on beta.7
We use it in all our examples i.e here it is in react
https://github.com/WalletConnect/web3modal/blob/V2/examples/react/src/pages/_app.tsx#L1
Above example deploys here
https://web3modal-dev.pages.dev


[Feature][Transform] Move transform from seatunnel-starter.jar to transform directory

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
Currently, transform is packaged in the seatunnel-starter.jar package. If users need to extend transform, they need to restart the zeta engine. We hope that transform, like connector, exists in a separate folder and is dynamically loaded when a task is submitted. At the same time, users can also dynamically add transform without restarting the engine.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

please assign it to me, thx.


feat: ✨ added tokens for roundings

Pull Request
📖 Description

🎫 Issues

👩💻 Reviewer Notes

📑 Test Plan

✅ DoD

[ ] I have tested my changes manually.
[ ] I have added automatic tests for my changes (unit- and visual regression tests).
[ ] I have updated the project documentation to reflect my changes (e.g. CHANGELOG, Storybook, ...).
[ ] I have made sure to follow the projects coding and contribution guides.
[ ] I have made sure that the bundle size has changed appropriately.
[ ] I have validated that there are no accessibility errors.
[ ] I have used design tokens instead of fix css values

Token are added, but not used in the syn-tag. Added new dev ticket #340

Maye the intent should be made clear when pull requests are created. This was the reason I initially did not approve it: It is not clear what is this for or if it is ready. Could you please create a ticket for this?

Token are added, but not used in the syn-tag. Added new dev ticket #340

Maye the intent should be made clear when pull requests are created. This was the reason I initially did not approve it: It is not clear what is this for or if it is ready. Could you please create a ticket for this?

Yes, I was also wondering that the outcome of this PR is only the tokens ;)
I created #341 to use the token for the syn-tag


Enhancement: Ask Mobile and Ask Require Mobile options within Ask Phone field

Is your feature request related to a problem? Please describe.
Feedback from the May 2022 Sprint, expected a Ask Mobile and Ask Require Mobile options only.  This request is probably focused from a higher ed, younger demographic perspective, but good call out that most people only operate from a Mobile phone perspective and we should simplify the form data gathering.
Describe the solution you'd like
Add additional options, Ask Mobile and Ask Require Mobile, and drive experience on the SEA Registration Page.
Describe alternatives you've considered
The form functions today with the Home and Mobile options, but could require, limit and simplify options if there were Mobile only options.
Are you willing and interested in being engaged during the development and testing process?
Yes and add Robert Wynter.

Included in beta release <IP_ADDRESS>

Included in production release <IP_ADDRESS>


Ensure our buffer allocation allows for the Explicit IV (1.1.1)

Some ciphers/protocol versions have an explicit IV. We need to make sure we
have sufficient room for it in the underlying buffer.
This is a backport of #20085.
This fixes a regression introduced by #19585 and should be merged before any 1.1.1t is released.

How does this relate to #19710 ?

The CI failures here are quite strange and apparently unrelated - but there are a lot of them.

How does this relate to https://github.com/openssl/openssl/pull/19710 ?

Unclear

#19930 would fix the CI failures.

I mean how about reverting https://github.com/openssl/openssl/pull/19585 and using https://github.com/openssl/openssl/pull/19710 instead, maybe add the test case from this PR,

IMO there is nothing fundamentally wrong with the approach in #19585 and #19710 is not a suitable replacement for it. There is no reason to revert it.

I mean how about reverting #19585 and using #19710 instead, maybe add the test case from this PR,

IMO there is nothing fundamentally wrong with the approach in #19585 and #19710 is not a suitable replacement for it. There is no reason to revert it.

But #19585 does not address the similar issue with DTLS,
while this PR increases the allocation size for TLS and DTLS,
although the test case fails to test DTLS.
Moreover explicit IV is a TLS1.3 feature and !ETM is a TLS1.2 feature,
and the only possible stitched ciphers are listed here:
https://github.com/openssl/openssl/blob/d90907dfed17f7075ca48ab1e9a730eab6476e3b/ssl/ssl_ciph.c#L560-L579
so at least as for the 1.1.1 version is concerned, that is RC4-HMAC-MD5, AES-128-CBC-HMAC-SHA1,
AES-256-CBC-HMAC-SHA1, AES-128-CBC-HMAC-SHA256, and AES-256-CBC-HMAC-SHA256,
So I think there was no real issue, at all, at least for 1.1.1 as you can see that #19710 passes
even with your new test case and with #19585 reverted.
On the other hand #19710 addresses TLS and DTLS,
and checks the available memory before the overwrite happens.
So to me this looks like first the reservation size is made larger by #19585, and
now the allocation size has to be increased just to fix the newly added assertion,
so net effect: more memory is needed, and probably never used, otherwise #19710
would fail now, once the test case from this PR has been added.
Well additionally, #19585 has quite some history:
It was first merged to master as 830eae60a61876a5bcd267f47e224269852dcc29
then had to be fixed urgently as ecacbc5e3c48901417e8e05bbf1d29df78610607
and now again caused a regression that will also have to be fixed urgently.
Sorry, but how much more do you guys need to consider a revert?

#19585 and #19710 have different objectives to each other. One is not a replacement for the other.
#19585 is about addressing a bug in the WPACKET accounting logic. The WPACKET_reserve_bytes and WPACKET_allocate_bytes calls are intended to be used in tandem with each other. When performing an operation which will fill a buffer with bytes that you don't know the size of beforehand you call WPACKET_reserve_bytes to set a ceiling on the maximum number of bytes that you will use, and then afterwards you call WPACKET_allocate_bytes to set the number of bytes that you actually used. It should never be the case that the allocate call uses more bytes than were originally reserved. The whole point of the reserve call is to verify that you have sufficient space left in your buffer compared to what you actually want to use. If you allocate more than you reserve then you could inadvertently overflow the buffer.
#19585 addresses a bug where insufficient bytes are reserved and the allocate call uses more than was reserved. #19710 does not address this WPACKET accounting error. Instead it adds checks in the encryption code to ensure that it does not overflow the underlying buffer before it writes out those bytes. Adding overflow checks before writing out the bytes is not a bad idea IMO, but it should do so using the mechanism that we have implemented for this: i.e. WPACKET. By checking the underlying buffer directly you are just avoiding the mechanism we have put in place for this task and so doesn't seem like the right solution to me. If you checked in tls1_enc that the number of bytes didn't exceed the amount reserved in the WPACKET then that would be a much better solution - but then you would immediately find that you would still need #19585 in place to fix the reservation bug. #19710 does not fix a bug, whereas #19585 does. #19710 does add some useful additional hardening (but in the wrong way IMO). I'm not sure that #19710 can be justified in a stable release (and less so in 1.1.1).

But https://github.com/openssl/openssl/pull/19585 does not address the similar issue with DTLS,

The DTLS code does not have the WPACKET accounting error bug that the TLS code has because it does not use WPACKET. This is a bad thing IMO, but not something to be addressed in 1.1.1. It has been addressed in master where the TLS and DTLS code has been harmonised and WPACKET is used for both. Since the DTLS code does not have the bug that #19585 fixes, it is not relevant there. The additional hardening introduced by #19710 could still be useful (but see my comments above) - but it does not address a bug. The hardening in #19710 does not cover TLSv1.3 or SSLv3.

while this PR increases the allocation size for TLS and DTLS,

This PR actually addresses a slightly different problem to #19585. I consider it to be fixing a latent bug that the changes in #19585 highlighted. The underlying buffer is sized based on certain assumptions, i.e. the buffer includes an allowance for:

the payload data itself
growth due to the compression algorithm (if relevant)
the record header
any alignment
any growth due to the encryption algorithm

The last factor includes an allowance for:

growth due to padding
growth due to the MAC/a tag

The bug here is that there is no allowance made for an explicit IV. We've been lucky enough to get away with it by virtue of the fact that the allowance for the MAC/tag is sized at 64 bytes. However the biggest MAC that we ever actually use is SHA-384  - which requires 48 bytes. That gives us 16 spare, which just happens to be the size of an explicit IV. But this is an accident and works by luck.
An alternative fix to that proposed in this PR is to adjust the assumptions that we make and redefine SSL3_RT_SEND_MAX_ENCRYPTED_OVERHEAD so that it only incorporates 48 bytes for the MAC/tag and adds 16 for the explicit IV: ending up at the same value as it has now. We'd then have to modify the WPACKET_reserve_bytes logic to take account of this, and remove the 16 bytes used by the explicit IV. This would have the benefit of meaning that the underlying buffer size does not grow, but IMO complicates things unnecessarily (especially since  SSL3_RT_SEND_MAX_ENCRYPTED_OVERHEAD is a public macro). We could just leave the definition of SSL3_RT_SEND_MAX_ENCRYPTED_OVERHEAD alone and just add some comments explaining that the 64 bytes for the MAC actually only needs 48, and the other 16 are for the explicit IV. We'd still need to adjust the reserve logic in this case.
IMO just adding an additional 16 bytes to the underlying buffer is much simpler and the better solution - even though they are strictly speaking redundant. Having an extra 16 bytes in case of "accidents" is probably not a bad thing anyway.
#19710 does not address this problem at all. It works by virtue of the fact that the underlying buffer just happens to be big enough by chance due to the reasons explained above.

although the test case fails to test DTLS.

This is a good point. It wouldn't be a bad idea to extend the test to DTLS as well.

Moreover explicit IV is a TLS1.3 feature and !ETM is a TLS1.2 feature,

This is not correct. Explicit IV is relevant to TLS 1.1, TLS 1.2 and DTLS, but not TLSv1.3. It was introduced in TLS 1.1 due to a known vulnerability in TLSv1.0/SSLv3 where the IV for each record is the last block of the preceding record (meaning it is predictable). This later gave rise to the BEAST attack.
Explicit IV is only applicable to CBC ciphersuites. Since TLSv1.3 doesn't have any of those it is not relevant there.
However, the buffers (in 1.1.1) are allocated early in the handshake before we know what protocol version/ciphersuites we are going to be using. So allocating a 16 byte allowance for the explicit IV in case we subsequently negotiate something that requires it seems sensible.

although the test case fails to test DTLS.

This is a good point. It wouldn't be a bad idea to extend the test to DTLS as well.

I've added a commit to do that.

although the test case fails to test DTLS.

This is a good point. It wouldn't be a bad idea to extend the test to DTLS as well.

I've added a commit to do that.

Thanks, I've added your test to #19710 and it works there too.

The hardening in https://github.com/openssl/openssl/pull/19710 does not cover TLSv1.3 or SSLv3.

No, that is a complete misunderstanding.
TLSv1.3 and SSLv3 had no issue at all before #19585 broke them,
therefore those enc functions do not use the new parameter, if they turn out to exceed
the minimum reservation that could be addressed easily but currently I only see one place
where there was a real issue: in tls1_enc near EVP_AEAD_TLS1_AAD_LEN.
The idea of #19710 as follows:
All enc functions have the natural right to assume 16 bytes to be available for padding
or adding an AEAD tag value, that is guaranteed by a reservation of SSL_RT_MAX_CIPHER_BLOCK_SIZE,
as it was done before #19585 increased this value.
But in some cases the padding and a HMAC hash is needed, and #19710 adds a side-channel
to check the available memory only in this case.  And this is only TLS1 not SSL3 and not TLS1.3.
It relies on the fact that the subsequent packet allocation is guaranteed to succeed and not
modifiy the already filled in mac value, but that is not a real issue IMHO.
I thought that would be clear since I wrote this in the original commit message:
This adds a new parameter to the enc functions,
that is optional, and if given can be used to prevent
buffer overflows due to excessive padding before they happen.
A minimum space reservation of 16 bytes is assumed to
be available without checking.
Additionally this fixes a bug, that prevented DTLS
to use aes_cbc_hmac_sha1 and aes_cbc_hmac_sha256.

So yes, the memory reservation currently reilies heavily on the fact that CBC ciphers
dont play together with SHA512 and explicit IV.  That wont change ever, but
might deserve a comment.

This pull request is ready to merge

Merged to 1.1.1. Thank you.


🐞[Bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug

selecting time slot div is not properly aligned
make an appointment section is not good as per the UI
Padding not good for the make an appointment
Updating the favicon of rapidoc with logo of Rapidoc
Select time not working properly

Expected behavior

Add ScreenShots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04  Please assign this issue to me under GSSOC with the required levels.
Thanks

I can perfectly allign these assets  so @Anishkagupta04  pls assign me this issue  since it is vey important for me.
Thank you and waiting for your response.

could you do like to make a serate page for this instead on the main page as its seems to look messy

Yes sure @Anishkagupta04  please assigne this issue to me under gssoc with required label, thanks

/assign


chore(build): update clirr config using InternalApi annotation

InternalApi classes are not subject to binary compat guarantees. So we should exclude them. This PR adds a small helper that generates exclusions by scanning the classpath. The intention is to run the tool manually and copy/paste the results. Eventually we should figure out how to exclude annotated classes altogether

I'll close this for now and come back to it when we have a bit more time


feat: Remove kernel version from kmod name, bundle akmods

This PR removes the version name of the kernel from akmods to cleanup changelogs and bundles the akmods used to build the kmods into the resulting image, preventing version drift.
Closes https://github.com/ublue-os/akmods/issues/254 and https://github.com/ublue-os/akmods/issues/255

You didn't do zfs.


Rename data grid to entity grid

Original naming of data grid "data grid" is not very clear on what it is in context of evitaDB. May better name would be entity grid. This way it is clear that it somehow displays entities in some form of grid or table.

Done in #94. Renamed to entity viewer.


thana

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Closing this issue since it has no context. Please feel free to lodge a new one if necessary!


Class cast exception in Replication.java

Hi!
When a new instance of my app connects to the sync_gateway, it logs the class cast exception below.  After restarting the app,   This might not be a bug since it the circumstances are:

created an attachment (which was too large for the server and it chocked on it when updating views)
deleted the attachment object itself (_id = sha1-+BNbV0BRAZNtU/IM8oqWUthvfYc=)
using the REST API (yes, I know it's bad...)
did not delete the _attachment part in the related document

This is the offending object:
{
    "_attachments": {
        "Image 20140801-211302": {
            "content_type": "image/*",
            "digest": "sha1-+BNbV0BRAZNtU/IM8oqWUthvfYc=",
            "length": 2832882,
            "revpos": 2,
            "stub": true
        }
    },
    "_sync": {
        "channels": {
            "6ae70a7a0f7c5994138d93e6852bd7a1": null
        },
        "history": {
            "bodies": [
                "",
                ""
            ],
            "channels": [
                null,
                [
                    "6ae70a7a0f7c5994138d93e6852bd7a1"
                ]
            ],
            "parents": [
                -1,
                0
            ],
            "revs": [
                "1-0b2c9c863a16af28e62032dd94362258",
                "2-4fbe9d22ac16477d0ccb67f639870397"
            ]
        },
        "rev": "2-4fbe9d22ac16477d0ccb67f639870397",
        "sequence": 1473,
        "time_saved": "2014-08-01T21:13:50.970308714+02:00"
    },
    "actionId": "40eb02f7-e470-46b9-9be8-3b8c5c604ec9",
    "filename": "Image 20140801-211302",
    "mimetype": "image/*",
    "owner": "6ae70a7a0f7c5994138d93e6852bd7a1",
    "size": 2832882.0,
    "title": "Image 20140801-211302",
    "type": "Attachment"
}

I am using the latest git versions:
couchbase-lite-android: f4d96e40a24ffafa16c04df21b0f73aa81d335bf
couchbase-lite-java-core: 4bf559f0151d58e0bfb77248f3d90f64bc096a91
Exception from logcat:
08-06 11:30:03.530    1446-1488/MYPACKAGE.debug E/CBLite﹕ Exception getting status from {error=not_found, id=e7b327ca-6d89-4cf7-98c5-60479688aa54, reason=missing, rev=2-4fbe9d22ac16477d0ccb67f639870397, status=404}
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
at com.couchbase.lite.replicator.Replication.statusFromBulkDocsResponseItem(Replication.java:1613)
at com.couchbase.lite.replicator.Puller$5.onDocument(Puller.java:594)
at com.couchbase.lite.replicator.BulkDownloader.finishedPart(BulkDownloader.java:235)
at com.couchbase.lite.support.MultipartReader.appendData(MultipartReader.java:171)
at com.couchbase.lite.replicator.BulkDownloader.executeRequest(BulkDownloader.java:148)
at com.couchbase.lite.replicator.BulkDownloader.run(BulkDownloader.java:85)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)

Seems it was fixed in https://github.com/couchbase/couchbase-lite-java-core/commit/9c8b295b57d4dca0d8ffe277e65db5799ddb0390

closing based on last update.


/bin/sh: line 4: zip: command not found

The included make_base file uses the zip command to compress the output files into one archive. However, MINGW32 doesn't include the zip command by default.

In addition, running make puts the files into the archive in an odd format:

GameYob.zip

home\steven\Desktop\programming\3DS\Apps\GameYob\output\

GameYob.3ds
GameYob.cia
GameYob.elf

3ds\GameYob\

GameYob.3dsx
GameYob.smdh
I doubt this was intentional, as the download for the 3DSHomebrewTemplate repo has the 3ds, cia, and elf files in the main folder of the ZIP archive. That file tree above is even from all your recent GameYob distributions.

ZIP structure should be fixed now, and I've updated my latest releases as well.
As for zip, all I can say is get the zip command. I can't help it if your environment doesn't include it by default.

Well, you could at least leave a note somewhere saying you'll have to download zip if you're using MINGW32. It can be downloaded here.

With that logic, I'd have to include a note for every possible OS and setup that might not have zip.

True that...


Consider switching rig daq validation implementation

It appears that daqs are being validated here: https://github.com/AllenNeuralDynamics/aind-data-schema/blob/c593512d06d7e76a25cb94735d1989ce226dc5e1/src/aind_data_schema/core/rig.py#L85
I'm not sure if this was intended but a field validator doesn't have predictable access to all fields in the info object according to documentation. Could we potentially switch to using a model_validator instead? This also appears to be breaking the validation of my serialized rig data which I was kinda hoping to rely on.
Would happily implement this change to move this along.

Resolved in #805


Custom crop presets

Version
3.14.2
Development Environment
Browser: Chrome (89.0.4389.90)
OS: Windows 10 (Version 10.0.19041 Build 19041)
Current Behavior
Currently, the crop functionality inside the image editor has the following presets: Square, 3:2, 4:3, 5:4, 7:5, and 16:9. The current API does not allow changing these presets.
Expected Behavior
An ability to change the presets on the UI options object.
Making the change
We are using the Toast UI Image Editor in our app and it is fantastic! Thank you for all the work you have done.
If we create a PR with the ability to change the crop presets, would you consider merging it into the project? Do you think the feature is something other users would find useful?
Thank you!

@ziga-miklic
Sorry for the late reply. This proposal looks similar to #125 and #350. This option is currently being prepared and will be updated to complete. Thank you!

Thank you for responding @lja1018 That is great news!
I look forward to checking out the changes once they are available. Keep up the great work!

Any updates？

@wenjing-pure
Sorry. There's no update.


Upgrading esbuild to support s390x architercture

npm install fails on s390x system architecture due to outdated esbuild. This PR upgrades esbuild to its latest version and with that way the npm install works properly on s390x systems.

Thanks!

that was fast. Thank you :)


Environment problem

May I ask what version of PyTorch you are using? I found that my torch version became 2.0 after following these steps to configure the environment, and as a result, I am unable to successfully import tinycudann.
pip install torch==1.12.1+cu113 torchvision==0.13.1+cu113 -f https://download.pytorch.org/whl/torch_stable.html pip install ninja git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch pip install nerfstudio
It will report an error if I want to train the second stage (edit part), i.e.:
ImportError: libtorch_cuda_cu.so: cannot open shared object file: No such file or directory

Can you try installing with pytorch 1.13? Use the commands on the tab that says Torch 1.13.1 with CUDA 11.7 here: https://docs.nerf.studio/en/latest/quickstart/installation.html#dependencies

Ah also, the instructions are a bit confusing. From the installation page, you should only follow the commands up to tinycudann. Then, come back to our readme and go to step 2


add link to Updates to client feature states

:white_check_mark: Organization membership check passed
Requester is not a member of the MicrosoftDocs organization.


feat: Auto clear expired bids

Prerequisites

[X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request
I would love a new feature that automatically clears expired bids, just like clearing sold items.
Describe the Use Case
It is pretty often in the bidding process. Also, once expired bids reach 100, and the bot continues bidding repeatedly, it will likely cause a softban.
Describe Preferred Solution
Simply adding a "Clear Expired Bids", which is trigged, say, once expired bids reach 50. Just like auto clearing sold items.
Describe Alternatives
No response
Additional Information
No response

This setting is available under Common Settings Tab


Upgrade core-js dependency to fix firefox issue

You can review the issue here: https://github.com/zloirock/core-js/issues/24
This bug affects multiple older versions of firefox that are still commonly supported.

Thanks!

@sebmck - any idea when you will publish to npm?

@jhorwit2 Later today hopefully.

Awesome man, thanks! I wish ever repo was as quick as you :D.

Update it in 3.0 branch.

@zloirock Weird, it got lost in a merge somewhere. I've upgraded core-js and it now uses a caret so patches will be automatically updated. Released as of 3.0.7.


Proposal: Browser lock or screen turn-off for iOS connect/disconnect should be handled automatically

There is currently a little nasty situation happen in iOS platform with connection drop when user switch app or just locking his phone and no reconnect happen on page become active again. Surely there is some workaround to deal with it, but I think it will be much better if this will be implemented on a framework level.

I am using SignalR in Asp.Net Core 2.0 with typescript. I am also facing this issue in IOS operating system, but its works fine in other operating systems. Is there any workaround to work with this in typescript meanwhile?

This is something we discussed and we think is better handled by application code.


Initial version of jsbuilder tool

This introduces a jsbuilder tool which creates a .wasm file from js.
The rust portion simply passes on data to js, where it should then be decoded/encoded as per the signature encoding.
The javascript should have the following exported.
runFunction(data number[]): number[]
(global as any).Exports = {
main: mainFunction,
run: runFunction,
}
The rust portion also exports a function to call back to next(), which again accepts bytes and returns bytes.
newData = (global as any).scale_fn_next(data)

Have removed buffers from the rust portion. These are now in js.
New function exposed to js - getaddr which returns the address of an ArrayBuffer.
The Resize function now routes through to js.
Next now takes [ptr, len] and returns packed.


Issue fixed on pokemon-stats play

There was no back button on the pokemon-stats play. The only way was to refresh the page. This issue is fixed.

Hello Sir, "Authorization required to deploy." is showing on Vercel. Can you resolve it and complete the process :)

Yeah, it is the same as #646 but I gave the separate button from the card and it will be visible by useState hook.

@JayPokale please resolve conflicts


Upgrade to Android V2 embedding to not rely on deprecated API

V2 is out there for a good while now and the time is ticking: Android Studio presents a warning

The plugins bluetooth_enable, share_files_and_screenshot_widgets use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

https://media.giphy.com/media/qUIm5wu6LAAog/giphy.gif

Is this still not merged???


Docker-compose is not working

we have tried to get Yawik to run with docker-compose but unfortunately a number of errors are displayed. These are caused as far as we can see in docker-entrypoint.sh references files and commands that are not available inside the container built from the provided Dockerfile.
Besides the docker-compose file we copied the .env file and the whole folder etc from the repo.
version: "3"
services:
    nginx:
        image: nginx:alpine
        container_name: yawik-nginx
        volumes:
            - ./etc/docker/nginx/nginx.conf:/etc/nginx/conf.d/default.conf
            - /opt/docker/yawik/public:/var/www/yawik
        ports:
            - "8080:80"
        links:
            - php
            - mongo
        environment:
            - UMASK="0000"
            - VIRTUAL_HOST= domain.tld
            - LETSENCRYPT_HOST= domain.tld
            - LETSENCRYPT_EMAIL=<EMAIL_ADDRESS>        networks:
            - default
            - proxy-tier

    php:
        container_name: yawik-php
        env_file:
          - .env
        build:
            context: etc/docker/php
            args:
                TIMEZONE: ${TIMEZONE}
        volumes:
            - /opt/docker/yawik/public:/var/www/yawik
        links:
            - mongo
        environment:
            - UMASK=0000
        networks:
            - proxy-tier
            - default

    mongo:
        image: mongo:3.4.10
        container_name: yawik-mongo
        environment:
            - MONGO_DATA_DIR=/data/db
            - MONGO_LOG_DIR=/dev/null
        volumes:
            - /opt/docker/yawik/mongodb/data:/data/db
        ports:
            - "27017:27017"
        command: mongod --smallfiles --logpath=/dev/null # --quiet

networks:

  proxy-tier:
    external:
      name: nginx-proxy

As error message we get the following displayed:
Attaching to yawik-mongo, yawik-php, yawik-nginx
yawik-php | /var/www/yawik
yawik-nginx | 2019/03/19 14:35:16 [emerg] 1#1: host not found in upstream "php" in /etc/nginx/conf.d/default.conf:11
yawik-nginx | nginx: [emerg] host not found in upstream "php" in /etc/nginx/conf.d/default.conf:11
yawik-php exited with code 1
yawik-nginx exited with code 1

To track down the mistake. We cloned the repo and did docker-compose. The following error occurred while building:
Step 14/25 : RUN rm /etc/localtime &&     ln -s /usr/share/zoneinfo/UTC /etc/localtime &&     "date"
 ---> Running in 7c221ee6b5f0
rm: cannot remove '/etc/localtime': No such file or directory
ERROR: Service 'php' failed to build: The command '/bin/sh -c rm /etc/localtime &&     ln -s /usr/share/zoneinfo/UTC /etc/localtime &&     "date"' returned a non-zero code: 1

Hi @aiveras, this issue should be fixed in my #541 pull

Hi @kilip Thank you for your commit. Now the docker image is created without errors. However, we still get this error message at the end:
Creating yawik-mongo ... done
Creating yawik-php   ... done
Creating yawik-nginx ... done
Attaching to yawik-mongo, yawik-php, yawik-nginx
yawik-php | /var/www/yawik
yawik-php | cp: cannot stat 'etc/docker/php/php-ini-overrides.ini.dist': No such file or directory
yawik-nginx | 2019/04/23 22:20:08 [emerg] 1#1: host not found in upstream "php" in /etc/nginx/conf.d/default.conf:11
yawik-nginx | nginx: [emerg] host not found in upstream "php" in /etc/nginx/conf.d/default.conf:11
yawik-php exited with code 1

@aiveras Were you able to sort this out. Facing the same problem while building docker-compose up

no the problem still occurs..

We're using this docker to run CI/CD on gitlab.
Let's close this issue

We're using this docker to run CI/CD on gitlab.
Let's close this issue


Fix link error about package.

Fix link error about package.

Hi, @saragluna , please help to review this PR.


when the center of a geohash's bounding box is 0,0 dataLaer fails -- 0,0 is a valid lat/lng

In leaflet.dvf.datalayer.js GEOHASH function.
The following condition fails if the center of the bounding box evaluates to 0,0 witch is a valid lat/lng location.  Specifically, this is the location that the Equator and the Prime Meridian intersect.
if (locationInfo.latitude[2] && locationInfo.longitude[2]) {
    bounds = new L.LatLngBounds(new L.LatLng(locationInfo.latitude[0], locationInfo.longitude[0]), new L.LatLng(locationInfo.latitude[1], locationInfo.longitude[1]));
}

a little farther down, since the bounds is undefined this line fails
center: bounds.getCenter()

This will cause an entire dataLayer to fail if a single center point is 0,0.

Actually, this will fail anytime the center of a geohash falls on the Equator or the Prime Meridian.

@tlhampton13 good catch.  Should be fixed soon.

Giving this some more thought, I don't believe this scenario will ever happen, or is it actually happening for you?  The geohash of 0, 0 is s0, s00, s000, s0000, and so on.  If you calculate the center of any of those geohashes, it's never 0, 0. In order for it to actually be 0, 0, you'd have to have a super long geohash string.  In general, that code could probably use some refactoring/cleanup, but I don't believe it will fail with geohashes of realistic length.  @tlhampton13 What do you think?

@sfairgrieve
You are correct.  No geohashes actually span the Equator or Prime Meridian.  These lines would fall along a bounding edge of the adjacent geohashes.
I am getting a failure in the GEOHASH function though because the bounds is undefined.  But the reason is not as I originally described.
In some of my records the geohash fields is empty string.
{
  "geohashField": ""
}

When this happens the GeoHash.decodeGeoHash() method actually returns location information for the empty string.  Notice that the third element in the arrays (center point) is missing.
{
  "latitude": [-90.0, 90.0],
  "longitude": [-180.0, 180.0]
}

then the if condition fails because the center point is not present.
if (locationInfo.latitude[2] && locationInfo.longitude[2])

I can change the data so that the geohashField is not present if it is "", but then records without a field fail.  So I add a filter to the dataLayer, but that fails because the _loadRecords method lookups the geocode before checking includeLayer value.

@tlhampton13 apologies for the delayed response.  Did you make any progress with this?  For now, my suggestion would be to either remove records that have a blank geohashField before passing the data to the DataLayer (e.g. using lodash or your own JavaScript) or implementing your own LocationMode function (you can use the GEOHASH one as a starting point).  I agree that the existing code in Leaflet DVF needs to be updated to be more resilient to cases like this or provide more ways of preventing it.


Error rendering report: render command error:file in C:\XXXX\XXXX doesn't have a valid JSON contenttype

Hey guys I'm encountering this error when trying to generate reports with your jsreport-dotnet development solution.
I'm getting this exact error when the process go through this code block:
var reqFile = Path.Combine(_tempPath, $"req{Guid.NewGuid().ToString()}.json");
File.WriteAllText(reqFile, requestString);

var outFile = Path.Combine(_tempPath, $"out{Guid.NewGuid().ToString()}");
var metaFile = Path.Combine(_tempPath, $"meta{Guid.NewGuid().ToString()}");
var output = await _binaryProcess.ExecuteExe($"render --keepAlive --request={reqFile} --out={outFile} --meta={metaFile}").ConfigureAwait(false);

The output result is:
output.Command = C:\Users\XXXX\AppData\Local\Temp\.jsreport\binary-default-<IP_ADDRESS>\jsreport.exerender --keepAlive --request=C:\Users\XXXX\AppData\Local\Temp\jsreport-temp\req00d4a350-4a94-4f2d-af76-fae057bbce50.json --out=C:\Users\XXXX\AppData\Local\Temp\jsreport-temp\out9030077f-aa55-42ef-b710-8f04afcee5f0 --meta=C:\Users\XXXX\AppData\Local\Temp\jsreport-temp\meta9f61dd49-9dde-4ea9-bc44-d713924af1ec
output.IsError = True
output.Logs = 'render command error:file in C:\Users\XXXX doesn't have a valid JSON contenttype jsreport render -h to get help about usage and available options'
Any help would be really appreciate it, thanks!

I tried running CoolM1234 sample project on issue 4
But I'm getting the same error:

Thank you for the bug report. I'm looking into it. Could you post here the file
C:\Users\XXXX\AppData\Local\Temp\jsreport-temp\req00d4a350-4a94-4f2d-af76-fae057bbce50.json ?

@pofider thanks for the quick response, sure here it is:
req00d4a350-4a94-4f2d-af76-fae057bbce50.json.txt

Thank you. There is nothing wrong with it.
I have a suspicion that the problem is the space in your username and in the path c:\users\foo foo\.,,. I've the space in my username as well and it works. However I have a feeling that it is somehow symlinked in my windows 10. Looking into it.

Ok, I can replicate the issue. Working on a fix.

Please update<EMAIL_ADDRESS>and let me know if it works for you afterwards. Thank you.

@pofider thanks a lot, it's working now.
You may closed this issue, the problem was solved.

Thank you for confirmation. Closing this now.


[PE-D][Tester C] No errors when adding a new person to link to an already occupied internship

Trying to link two contact persons to the same internship would display that it is not possible to do so.
But if I were to create a new Person, and link it to the same already occupied internship, no errors are thrown.
Though the newly created Person would not have any linked company/internships. You could potentially throw a warning over here to tell the user that the internship is already occupied.

Labels: type.FunctionalityBug severity.Low
original: nealetham/ped#8

Clarify in documentation that link index is ignored if invalid


[SPARK-6080] [PySpark] correct LogisticRegressionWithLBFGS regType parameter for pyspark

Currently LogisticRegressionWithLBFGS in python/pyspark/mllib/classification.py will invoke callMLlibFunc with a wrong "regType" parameter.
It was assigned to "str(regType)" which translate None(Python) to "None"(Java/Scala). The right way should be translate None(Python) to null(Java/Scala) just as what we did at LogisticRegressionWithSGD.

Can one of the admins verify this patch?

add to whitelist

ok to test

Test build #28150 has started for   PR 4831 at commit 12db65a.

This patch merges cleanly.

Test build #28150 has finished for   PR 4831 at commit 12db65a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28150/
Test PASSed.

LGTM. Merged into master and branch-1.3. Thanks!


Tiles are not connecting on Intel integrated GPUs

This issue has already been opened and closed once before however I am still facing the same problem.
Relates to issue #6519 - I did post a comment there but assume that as the issue was closed no one has visibility on it.
Specs below, let me know if any further info is needed or if I'm just being stupid and missed the fix somehow..
OS Name	Microsoft Windows 10 Enterprise
Version	10.0.14393 Build 14393
Other OS Description Not Available
OS Manufacturer	Microsoft Corporation
System Name	GB-HQ0FXP2
System Manufacturer	Dell Inc.
System Model	OptiPlex 3050
System Type	x64-based PC
System SKU	07A3
Processor	Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz, 3192 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date	Dell Inc. 1.8.3, 23/03/2018
SMBIOS Version	3.0
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Dell Inc.
Graphics are Intel integrated also, HD 530 if that helps.
Let me know if you need any more info.
Cheers,

Its fixed on master, not in release.. wait for thursday's release or build the client yourself

Apologies, I'm new here, didn't realise that was how it worked...


is there work in progress or is this abandoned?

Hi, I was planning using this for one small app i have to write but as i dont see new commits in more than 2 months or work in progress just wanted to check if there is a new version coming for blazor 0.6 and if new features and bugs are being worked on?
Thanks!

Hello,
I had difficult time so I did not have much time for this project. I will start to developing new features new features & upgrading for Blazor 0.6 next week so this project is not abandoned.

thanks! hope to see new update soon!

@Mewriick there is gitter channel for blazor extensions https://gitter.im/BlazorExtensions/Lobby and https://github.com/BlazorExtensions for people working on components/extensions to follow same patterns and namespaces and put them together for easy discoverability.
Would be great to see your component under BlazorExtensions.


When column config says quote, use quotes in SQL to add comments

resolves #2539
Description
When 'persist_docs' was turned on, an error occurred if a column had config 'quote: true' because the DDL to add the comment did not quote the column name. This fix passes the column quote config on to the ColumnInfo object and checks that config when constructing the SQL to add a comment.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

@cla-bot check

it does seem like a macro or adapter method that we could write, doesn't it?
{% macro quoted_column(column_dict, column_name) %}
  {% set result = column_name %}
  {% if column_dict[column_name]['quote'] %}
    {% set result = adapter.quote(column_name) %}
  {% endif %}
  {% do return(result) %}
{% endmacro %}


Difference in depth value when calculated using get_distance() vs multiplying depth pixel value with depth scale

Required Info

Camera Model
D435i

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
5.4.0-58-generic

Platform
core i7

SDK Version
Real Sense SDK 2.0

Language
C++

Segment
Vision

Issue Description
PFA below code snippet:
    // Ingest depth frame
    rs2::frameset data = pipe.wait_for_frames();
    rs2::depth_frame depth = data.get_depth_frame();

    // Query frame size (width and height)
    const int w = depth.get_width();
    const int h = depth.get_height();

    // Query depth distance using get_distance()
    float depth_distance = depth.get_distance(100, 100);

    // Query depth scale
    float depth_scale = depth.get_units();

    std::cout << "depth distance: " << depth_distance << "\n";
    std::cout << "depth_scale: " << depth_scale << "\n";

    // Create OpenCV matrix of size (w,h) from the depth data for some processing
    Mat image(Size(w, h), CV_16U, (void*)depth.get_data(), Mat::AUTO_STEP);

    // Use the OpenCV matrix to get the depth information
    uint16_t* fr_data = (uint16_t*)image.data;
    uint16_t pixel = fr_data[100,100];
    float meters = pixel * depth_scale;
    std::cout << "depth distance from converted cv Mat frame:  " << meters << "\n";

I had obtained depth distance from the depth frame for pixel co-ordinates (100,100). And then I am creating a cv Mat frame out of the depth frames's bytes data. Now I am trying to get the depth distance by multiplying the depth scale value with the depth pixel value of the converted cv Mat depth frame.
I am noticing a diff in the calculated depth distances. Why is this so ?
PFA o/p logs:
depth distance: 3.056
depth_scale: 0.001
depth distance from converted cv Mat frame: 2.35
depth distance: 3.07
depth_scale: 0.001
depth distance from converted cv Mat frame: 2.318
depth distance: 3.14
depth_scale: 0.001
depth distance from converted cv Mat frame: 2.279
depth distance: 3.14
depth_scale: 0.001
depth distance from converted cv Mat frame: 2.358
depth distance: 3.042
depth_scale: 0.001
depth distance from converted cv Mat frame: 2.264

I see even if one doesn't convert the depth frame to cv Mat and directly calculate the distance by multiplying depth scale and the pixel value of depth frame there is a variation in the distance measurement.
code snip :
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100,100];
    float dp_meters = dp_pixel * depth_scale;
    std::cout << "depth distance from depth frame: " << dp_meters << "\n";

o/p snip :
depth distance: 3.155
depth_scale: 0.001
depth distance from depth frame: 2.295
depth distance from converted cv Mat frame: 2.295

I see even if one doesn't convert the depth frame to cv Mat and directly calculate the distance by multiplying depth scale and the pixel value of depth frame there is a variation in the distance measurement.
code snip :
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100,100];
    float dp_meters = dp_pixel * depth_scale;
    std::cout << "depth distance from depth frame: " << dp_meters << "\n";

o/p snip :
depth distance: 3.155
depth_scale: 0.001
depth distance from depth frame: 2.295
depth distance from converted cv Mat frame: 2.295

@sandeshk1 , the issue is within this lines:
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100,100];

When you cast depth.get_data() you get a pointer to a one-dimensional buffer but then you treat it as it were a two-dimensional array....
The length of line is not specified so the result of  dp_data[100,100]; is undefined and imo can lead to segfault.
You should probably use
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100 *  w + 100];

With OpenCV the matrix dimensions are specified explicitly, but since the outcome is similar to results obtained in C++ then I'd suggest to check it again.

@sandeshk1 , the issue is within this lines:
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100,100];

When you cast depth.get_data() you get a pointer to a one-dimensional buffer but then you treat it as it were a two-dimensional array....
The length of line is not specified so the result of  dp_data[100,100]; is undefined and imo can lead to segfault.
You should probably use
    uint16_t* dp_data = (uint16_t*)depth.get_data();
    uint16_t dp_pixel = dp_data[100 *  w + 100];

With OpenCV the matrix dimensions are specified explicitly, but since the outcome is similar to results obtained in C++ then I'd suggest to check it again.

@ev-mp, thanks a lot for the quick reply.
My bad treating the 1-D buffer as though it was a 2-D array.
With your recommendation I was able to get the correct distance value.
So basically the index for the 1-D array should be "pixels's y-coordinate * width + pixel's x-coordinate" is it ? Could you explain a bit more on this solution for my understanding.

@ev-mp, thanks a lot for the quick reply.
My bad treating the 1-D buffer as though it was a 2-D array.
With your recommendation I was able to get the correct distance value.
So basically the index for the 1-D array should be "pixels's y-coordinate * width + pixel's x-coordinate" is it ? Could you explain a bit more on this solution for my understanding.

@sandeshk1 , it is correct.
In float depth_distance = depth.get_distance(x,y);  (x,y) stand for (col,row).
So finding the corresponding pixel with 1D buffer is  y * width + x

@sandeshk1 , it is correct.
In float depth_distance = depth.get_distance(x,y);  (x,y) stand for (col,row).
So finding the corresponding pixel with 1D buffer is  y * width + x

@ev-mp Thanks for the explanation.
Closing this thread as the solution was provided

@ev-mp Thanks for the explanation.
Closing this thread as the solution was provided


Weird disconnect issue which shows in console

Hi,
When someone leaves my server I seem to get this message:
issue server.txt
Any Ideas?

Have you tried to reset your map's barricades file, or use a backup of the file, if you have one?

 I'll keep you updated.

Not a rocket bug


Documentation is unclear how to use different layouts

The documentation at http://ned.im/noty/ is unclear how to use the different layouts. I guessed the following should work:
noty({
	layout: 'topleft',
	text: 'Test'
});

But I get "Uncaught TypeError: Cannot read property 'options' of undefined" in the console, related to this line: this.options = $.extend({}, this.options, this.options.layout.options);.

Also stuck on this. Regards

Use camelCase to fix this. Change topleft to topLeft


The package doesn't work with django 4.0.*

when trying to install the recent version of django-rest-auth with Django 4 since it uses the deprecated function ugettext_lazy from django.utils.translation the error :
  File "/path/to/views/views.py", line 8, in <module>
    from rest_auth.registration.serializers import SocialLoginSerializer
  File "/path/to/python3.8/site-packages/rest_auth/registration/serializers.py", line 2, in <module>
    from django.utils.translation import ugettext_lazy as _
ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/path/to/venv/lib/python3.8/site-packages/django/utils/translation/__init__.py)

I modified it to fit Django 4.0 while waiting pull request you can use this repo  https://github.com/Omaraitbenhaddi/django-rest-auth


Additional code comment on separate line?

When using the option "Leave a code comment with your reason for fixing", the comment is placed on the same line as the eslint-disable-next-line comment:
            <FadeInUp amount={4}>
              {/* eslint-disable-next-line @typescript-eslint/no-explicit-any -- FIXME http://bit.ly/some-url-here */}
              <Icon icon={MaterialCheckCircle as any} color="$gray40" />
            </FadeInUp>

This leads to these lines getting really long and I was wondering if you would consider allowing the comment to be added on the previous line?
            <FadeInUp amount={4}>
              {/* FIXME http://bit.ly/some-url-here /*}
              {/* eslint-disable-next-line @typescript-eslint/no-explicit-any */}
              <Icon icon={MaterialCheckCircle as any} color="$gray40" />
            </FadeInUp>

I'm happy to submit a PR for this if you can point me in the right direction.

@stevenmusumeche That sounds good! Welcome to submitting the PR.
Basically, it would be easy to implement by mimicking the implementation of the function that allows a description to be added to a comment. Currently eslint-interactive uses the promptToInputDescription function to ask the user for a description of the comment. Similarly, it would be nice to implement a promptToInputDescriptionPosition function that asks the user where to insert the comment. The obtained answer should be passed to Core#disablePerLine or Core#disablePerFile.
Inserting a comment is performed on the following line:
https://github.com/mizdra/eslint-interactive/blob/ffb557fae2ee94164167e3ccc1e5a23a00e9c26f/src/plugin/fix/disable-per-line.ts#L55-L61
https://github.com/mizdra/eslint-interactive/blob/ffb557fae2ee94164167e3ccc1e5a23a00e9c26f/src/plugin/fix/disable-per-file.ts#L28-L44
Perhaps the implementation of toCommentText needs to be changed as follows.
-export function toCommentText({ type, scope, ruleIds, description }: Omit<DisableComment, 'range'>): string {
+export function toCommentText({ type, scope, ruleIds, description, descriptionPosition }: Omit<DisableComment, 'range'>): string {
   const header = scope === 'next-line' ? 'eslint-disable-next-line' : 'eslint-disable';
   const ruleList = unique(ruleIds).join(', ');
   if (type === 'Line') {
     if (description === undefined) {
       return `// ${header} ${ruleList}`;
     } else {
-      return `// ${header} ${ruleList} -- ${description}`;
+      if (descriptionPosition === 'separate') {
+        return `// ${description}\n// ${header} ${ruleList}`;
+      } else {
+        return `// ${header} ${ruleList} -- ${description}`;
+      }
     }
   } else {
     if (description === undefined) {
       return `/* ${header} ${ruleList} */`;
     } else {
-      return `/* ${header} ${ruleList} -- ${description} */`;
+      if (descriptionPosition === 'separate') {
+        return `/* ${description} */\n/* ${header} ${ruleList} */`;
+      } else {
+        return `/* ${header} ${ruleList} -- ${description} */`;
+      }
     }
   }
 }

@mizdra - how can I run the CLI locally to test my changes?

Thanks! I've just opened a PR @mizdra

This feature is shipped by v10.8.0!


Add experimental support for .safetensors models in LCM pipeline

Similar to what was done in 62e2058e65c4 for lcm-lora.

@wbruna Thanks, which models you tested?

Comparing fluently/Fluently-v4-LCM with a pruned safetensors file:

I also tested Dreamshaper 8, ICBINP and a few other models.


Updating modulo multiplicative inverse to logarithmic complexity instead of linear.

Presently the code for modulo multiplicative inverse is written in linear complexity on mod. But it can be calculated using extended eucledian algorithm in logarithmic complexity.
Please assign this task to me.

Hello, Can you please assign this issue to me?
Thanks in advance :)

I have sent a pull request already for this issue. Kindly merge it

I have sent a pull request already for this issue. Kindly merge it

Reference this issue in your PR.


"Failed setup, will retry" with "Updated failed: 'time'"

Describe the bug
I recently have an error for my integration saying "Failed setup, will retry" with a mouse-over showing "Updated failed: 'time'".
In the logs it only says:
2024-03-25 18:00:14.008 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.332 seconds (success: False)
2024-03-25 18:00:54.756 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.319 seconds (success: False)
2024-03-25 18:02:15.173 DEBUG (MainThread) [custom_components.weatherflow_forecast] Finished fetching weatherflow_forecast data in 0.353 seconds (success: False)

I have enabled debug logging and it doesn't appear to make a difference.
To Reproduce
Steps to reproduce the behavior:

Go to the installed WeatherFlow Forecast integration
See "Needs Attention" for the installed integration

I cannot reproduce this right now. It can happen, when the Weatherflow Servers are not sending data, or you Internet temporary is down.

Interesting. Would it be possible to improve the error message to make it more clear?

Sure. I just need to capture the exact error that comes in from the API Request, so that I can raise the issue when it happens. I have already a few of them there, but obviously not them all.

Just saw this for the very first time tonight.

Same issue today.  Started after a host system shutdown by my UPS.

Additional information:
It appears the API has either changed or is malfunctioning.
Getting raw data for all my stations by my token ID works at
https://swd.weatherflow.com/swd/rest/stations?token=[your_access_token]
However, trying to access an individual station at
https://swd.weatherflow.com/swd/rest/observations/station/[your_station_id]?token=[your_access_token]
returns
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

	<title>Payara Server 6.2023.2 #badassfish - Error report</title>

HTTP Status 404 - Not Found

type Status report

messageNot Found

descriptionThe requested resource is not available.

Payara Server 6.2023.2 #badassfish

The above URL's both work fine for me with my Token and Station ID. Are you sure you have set your Station to Public Access? That is required for this to work.

I'm getting this error right now and nothing has changed. Must be an API issue on Tempest's end even though my station is online and reachable via app and website.

I'm getting this error right now and nothing has changed.  My ‘normal’ Weatherflow integration is working seamlessly. In the mean time, I changed everywhere possible the usage of the Weatherflow forecast sensors to the Weatherflow sensors.

Little addendum: it seems to work again for me. No more errors.

Confirmed my issue at least was a Tempest api issue.


About the ComboBox can't Fuzzy search

Issue type
enhancement
Which version of the app?
WinUI 3 Gallery
Description
Why can't I use fuzzy search for its items in the ComboBox, this seems to be a common problem for apps in the Windows platform
But now that it's WinUi3, why not support key-word fuzzy search initially? At least this is a headache for Asian countries (China, Japan, South Korea) and other scenarios that need to use input methods to type keywords
It would be great if it could be supported!
Screenshots
No response
Windows version
Windows 11 23H2 (22631)
Additional context
No response

Dup of #9936


Define which scc and role to apply on openshift

Hi,
As seen in #202 I'm trying to apply installation to an openshift cluster.
At this time, I can use daemonset from provisionner but an error says me (in logs) that local-volume-admin is not auhorized to list (and so, later, I guess, to create) persistent volumes.
This is how I'm creating my serviceaccount:
oc create serviceaccount local-storage-admin
oc adm policy add-scc-to-user privileged -z local-storage-admin
oc adm policy add-cluster-role-to-user system:node -z local-storage-admin

Note that system:persistent-volume-provisioner dosen't exists on openshift.
Thanks for your help.
PS: If I can use it on OpenShift, I will try to provide a documentation on how to deploy on that cluster system

Does everything work once you bind service account to system:node?

No it doesn't, I've finally found wich are the roles to apply:

system:node
system:pv-attach-detach-controller
system:pv-binder-controller
system:pv-provisioner-controller
system:pv-recycler-controller

I know have a new problem, each pods says:
Found new volume at host path "/mnt/disks/d10" with capacity<PHONE_NUMBER>, creating Local PV "local-pv-31b5888"
E0628 09:58:02.875045       1 discovery.go:153] Error creating PV "local-pv-31b5888" for volume at "/mnt/disks/d10": PersistentVolume "local-pv-31b5888" is invalid: spec: Required value: must specify a volume type

New issue ? or I should just rename this one to "integrate inside openshift" ?

Note: bootstrapper is unusable because rolebindings are not the same for openshift.
My last problem is https://github.com/kubernetes-incubator/external-storage/issues/204#issuecomment-311614839

OpenShift doesn't have the kube-side local volume API yet so it won't recognize local PVs. I'm not sure it will be made available in 3.6 either since it's still alpha in upstream. So even though the local volume provisioner is external we're still reliant on things existing on the kube/openshift side.

Yeah, you'll need to have local volume API for it to work, as @wongma7 said, it is not strictly external.

It's a pitty for me... I'm using openshift 1.5.1 so this is not usable. Our Galera works on GlusterFS right now, but as we are using statefulsets I thought that I will be able to write data on hostPath.
Without any provisionner, I really don't know how to create PVs and to be sure that PVC will bind PV on current host.
Bad news so...

@ddysher yes right, but local-volume api should work on k8s 1.7 while openshift (right now) uses 1.5.

there will be support on openshift side for local volume soon (1yr later)
/area local-volume


Add missing argument in ParquetRewriter logging

The logging statement misses one argument

LOG.info("Start rewriting {} input files {} to {}", inputFiles.size(), outPath);

Reporter: Ethan Guo
Note: This issue was originally created as PARQUET-2301. Please see the migration documentation for further details.

Ethan Guo:
The PR is merged: https://github.com/apache/parquet-mr/pull/1096


Dynamic Base URL Configuration for API Endpoints at branch feature/webiu-2024

Is your feature request related to a problem? Please describe.
I got frustrated when some system services were running on my Mac at port 5000, making it difficult to work with hardcoded API endpoints like http://localhost:5000. This situation can lead to confusion and interruptions in development. Additionally, switching environments requires manual changes to the code, increasing the likelihood of errors and complicating the development workflow.
Describe the solution you'd like
I would like to implement a feature that allows the base URL for API requests to be configured dynamically using environment files. This would involve creating an environment.ts file that holds the base URL (e.g., serverUrl) and allows components to reference this variable instead of hardcoding the URL in multiple places.
Describe alternatives you've considered
I have considered using a configuration service that fetches the appropriate API base URL from a central source, but that approach seems more complicated than simply using environment variables. Another alternative was to use a build tool to replace the URLs at build time, but this would add complexity to the build process. Using environment files is a cleaner and more manageable solution.

Feature added in PR https://github.com/c2siorg/Webiu/pull/85


After update, getting OC schema issues

Hi, firstly thanks for your updates. the issue is, I am getting new schema issue when the NUC boots from the opencore EFI. Please find the attached pictures.

EFI.zip
Just updated to OC7.1 with latest kexts. The system is booting normal and everything seems good. Please have a look at the EFI folder and do let me know if we need to change any thing. Regards

I have booted with debug version of OC and found out that ProvideCustomSlide quirk is not needed:
OCABC: All slides are usable! You can disable ProvideCustomSlide!

I have booted with debug version of OC and found out that ProvideCustomSlide quirk is not needed:
OCABC: All slides are usable! You can disable ProvideCustomSlide!

Thanks.. will do and check again..

Unable to verify it. It's critical for me to keep this system running. My son's using it for his school.


Telegram message loop

There seems to be an issue with the telegram notification platform. While working on the robustness I encountered loops in the sending of messages from time to time. This leads to sending a endless stream of messages to the given chat id.

It's wired...doesn't happen with a new bot. Can somebody confirm that there is a problem?

No problems with a new bot.


Simultaneously animate multiple points with .plot

just wondering if I am missing something, or maybe it's not currently possible. But is there a way that I can:
var points [  [ [x,y], [x,y], [x,y] ],  [ [x,y], [x,y], [x,y] ],  [ [x,y], [x,y], [x,y] ]... ];

var polygon [ poly1, poly2, poly3...];

polygon.forEach(function (v, i) {

v.animate(3000).plot( points[ i ] ); // Simultaneously animate?

});

Great work! and thanks!

Well I would think it would work exactly that way :D.
This will be animated nearly (if not almost) simultaneously.
The only other way would be animating one polygon and updating all other with the during method.
poly2.array().morph(points[1])
poly3.array().morph(points[2])

poly1.animate(3000).plot(points...).during(function(pos){
  poly2.plot(poly2.array().at(pos))
})

Well - Iam not completely sure about that. Maybe you have to clone the point array before you can use them correctly...

Thanks for the fast reply!
It changes the polygon shape, but no animation. I am not adding any additional points just re arranging the x, y numbers in a triangle. I tried the morph anyway but didn't make a difference. By cloning the array do you mean:  array2 = array1.slice(0);
I also tried just animating one item in the array with the same out come. I can past some code if you care.
cheers!

The code you posted first should work since 3.2.0


Getting datatype error though the values passed is of string

Report
Getting the error spec.triggers.metadata.queueLength in body must be of type string: "integer" though the values passed is integer string.
I am trying to create ScaledObject via helm chart and passing the value for queueLength as following:
queueLength: "5"
Expected Behavior
successfully created helm release with Triggerauthentication and Scaledobject created with the values passed from values.yaml
Actual Behavior
successfully creating a helm release with ScaledObject Created.
Steps to Reproduce the Problem

install keda verion 2.1.0 with helm
create a local helm chart
Create a template for TriggerAuthenticaton and ScaledObject.
Set values
Run local helm helm upgrade --install keda-scaler .  -f values.yaml

Logs from KEDA operator
Error: UPGRADE FAILED: failed to create resource: ScaledObject.keda.sh "aws-sqs-queue-scaledobject" is invalid: spec.triggers.metadata.queueLength: Invalid value: "integer": spec.triggers.metadata.queueLength in body must be of type string: "integer"
helm.go:84: [debug] ScaledObject.keda.sh "aws-sqs-queue-scaledobject" is invalid: spec.triggers.metadata.queueLength: Invalid value: "integer": spec.triggers.metadata.queueLength in body must be of type string: "integer"

KEDA Version
2.1.0
Kubernetes Version
1.20
Platform
Amazon Web Services
Scaler Details
No response
Anything else?
No response

What was the fix? Facing the same issue

Fixed by adding quotes in scaledobject value field

I had a similar issue.
Was fixed by a change:
Myvalue: {{ .Values.cpuValue  }}
to
Myvalue: {{ .Values.cpuValue | quote }}


Add crate: Emu: a language for GPGPU from Rust

Please add crate to category: GPU Computing
crate
repo
docs

Have you had a chance to look at this?

@calebwin  These requests are often treated faster if you make the pull request yourself.

@Enet4 I just submitted a PR to add the crate https://github.com/anowell/are-we-learning-yet/pull/49

Merged. Sry I didn't get to adding it quicker, but yeah, definitely faster with a PR.


Disable magnet wrecks

Until we can manage these code-wise better and not rely upon people who aren't even around anymore to balance them.
:cl:

tweak: Disable magnet wrecks TEMPORARILY pending further re-balancing.

ill balance them after this weekend and do ruins soon


DE417740 Preprocessing bundles prior to gw7 packaging

Fixes #DE417740
Proposed Changes

Reading all dependency bundles prior to packaging to ensure that encapsulated assertions that were previously decoupled and are now available in the final build gets attached by ID.

Looks good to me.


[WIP] Use GH Actions for ARM

So this will trigger Travis for x64/32 builds and GH for ARM builds?

So this will trigger Travis for x64/32 builds and GH for ARM builds?

That's the plan. We will see whether we should carry intel builds to GH actions in the future

GH actions does not currently support ARM for non-self-hosted runners.


TODO though being here would be very strange, at least log the error

I'm bouncing this bug between the various oauth modules because no one thinks this issue is from their module.
I'm seeing this error every few minutes:
Stacktrace (most recent call last):

  File "django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "newrelic/hooks/framework_django.py", line 499, in wrapper
    return wrapped(*args, **kwargs)
  File "django/views/generic/base.py", line 71, in view
    return self.dispatch(request, *args, **kwargs)
  File "django/utils/decorators.py", line 34, in _wrapper
    return bound_func(*args, **kwargs)
  File "django/views/decorators/csrf.py", line 58, in wrapped_view
    return view_func(*args, **kwargs)
  File "django/utils/decorators.py", line 30, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "braces/views.py", line 91, in dispatch
    return super(CsrfExemptMixin, self).dispatch(*args, **kwargs)
  File "newrelic/hooks/framework_django.py", line 837, in wrapper
    return wrapped(*args, **kwargs)
  File "django/views/generic/base.py", line 89, in dispatch
    return handler(request, *args, **kwargs)
  File "django/utils/decorators.py", line 34, in _wrapper
    return bound_func(*args, **kwargs)
  File "django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper
    return view(request, *args, **kwargs)
  File "django/utils/decorators.py", line 30, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "oauth2_provider/views/base.py", line 170, in post
    url, headers, body, status = self.create_token_response(request)
  File "oauth2_provider/views/mixins.py", line 124, in create_token_response
    return core.create_token_response(request)
  File "oauth2_provider/oauth2_backends.py", line 106, in create_token_response
    headers)
  File "oauthlib/oauth2/rfc6749/endpoints/base.py", line 64, in wrapper
    return f(endpoint, uri, *args, **kwargs)
  File "oauthlib/oauth2/rfc6749/endpoints/token.py", line 100, in create_token_response
    request, self.default_token_type)
  File "oauthlib/oauth2/rfc6749/grant_types/refresh_token.py", line 63, in create_token_response
    refresh_token=self.issue_new_refresh_tokens)
  File "oauthlib/oauth2/rfc6749/tokens.py", line 270, in create_token
    self.request_validator.save_bearer_token(token, request)
  File "oauth2_provider/oauth2_validators.py", line 291, in save_bearer_token
    assert()  # TODO though being here would be very strange, at least log the error

This is what I have installed:
django-oauth-toolkit==0.8.1
djangorestframework-oauth==1.0.1
oauth2client==1.4.11
oauthlib==0.7.2
requests-oauthlib==0.5.0

See also https://github.com/evonove/django-oauth-toolkit/issues/206


Preprocessing error on ghc HEAD (8.1)

Hey, I'm not certain this is an actual bug or a function of me doing weird stuff. I'm profiling current ghc HEAD when building some common libraries and generic-deriving fails with:
Mar 09 11:13:40 ghcperf ghcperf-start[16800]: Linking Setup ...
Mar 09 11:13:41 ghcperf ghcperf-start[16800]: Preprocessing library generic-deriving-1.10.0...
Mar 09 11:13:42 ghcperf ghcperf-start[16800]: src/Generics/Deriving/TH.hs:24:1: error:
Mar 09 11:13:42 ghcperf ghcperf-start[16800]: parse error on input ‘-- $('deriveAll0'     ''Example) -- Derives Generic instance’

Removing those deriveAll* examples makes the library compile again. I suspect it's a CPP issue but I can't understand what syntactic construct it picks up to make it fail.

What OS and C preprocessor are you using?

Running nixos 16.03-beta.  cpp is from gcc 4.9.3 AFAICT.

Hm, odd. I can't reproduce the issue on Linux x86_64 using GHC HEAD with gcc 4.9.3.
Out of curiosity, if you make the following change, does it build successfully?
diff --git a/src/Generics/Deriving/TH.hs b/src/Generics/Deriving/TH.hs
index 8268257..082d85f 100644
--- a/src/Generics/Deriving/TH.hs
+++ b/src/Generics/Deriving/TH.hs
@@ -1,46 +1,45 @@
 {-# LANGUAGE BangPatterns #-}
 {-# LANGUAGE CPP #-}

------------------------------------------------------------------------------
--- |
--- Module      :  Generics.Deriving.TH
--- Copyright   :  (c) 2008--2009 Universiteit Utrecht
--- License     :  BSD3
---
--- Maintainer<EMAIL_ADDRESS>--- Stability   :  experimental
--- Portability :  non-portable
---
--- This module contains Template Haskell code that can be used to
--- automatically generate the boilerplate code for the generic deriving
--- library.
---
--- To use these functions, pass the name of a data type as an argument:
---
--- @
--- {-# LANGUAGE TemplateHaskell #-}
---
--- data Example a = Example Int Char a
--- $('deriveAll0'     ''Example) -- Derives Generic instance
--- $('deriveAll1'     ''Example) -- Derives Generic1 instance
--- $('deriveAll0And1' ''Example) -- Derives Generic and Generic1 instances
--- @
---
--- On GHC 7.4 or later, this code can also be used with data families. To derive
--- for a data family instance, pass the name of one of the instance's constructors:
---
--- @
--- {-# LANGUAGE FlexibleInstances, TemplateHaskell, TypeFamilies #-}
---
--- data family Family a b
--- newtype instance Family Char x = FamilyChar Char
--- data    instance Family Bool x = FamilyTrue | FamilyFalse
---
--- $('deriveAll0' 'FamilyChar) -- instance Generic (Family Char b) where ...
--- $('deriveAll1' 'FamilyTrue) -- instance Generic1 (Family Bool) where ...
--- -- Alternatively, one could type $(deriveAll1 'FamilyFalse)
--- @
------------------------------------------------------------------------------
+{- |
+Module      :  Generics.Deriving.TH
+Copyright   :  (c) 2008--2009 Universiteit Utrecht
+License     :  BSD3
+
+Maintainer<EMAIL_ADDRESS>+Stability   :  experimental
+Portability :  non-portable
+
+This module contains Template Haskell code that can be used to
+automatically generate the boilerplate code for the generic deriving
+library.
+
+To use these functions, pass the name of a data type as an argument:
+
+@
+{-# LANGUAGE TemplateHaskell #-}
+
+data Example a = Example Int Char a
+$('deriveAll0'     ''Example) -- Derives Generic instance
+$('deriveAll1'     ''Example) -- Derives Generic1 instance
+$('deriveAll0And1' ''Example) -- Derives Generic and Generic1 instances
+@
+
+On GHC 7.4 or later, this code can also be used with data families. To derive
+for a data family instance, pass the name of one of the instance's constructors:
+
+@
+{-# LANGUAGE FlexibleInstances, TemplateHaskell, TypeFamilies #-}
+
+data family Family a b
+newtype instance Family Char x = FamilyChar Char
+data    instance Family Bool x = FamilyTrue | FamilyFalse
+
+$('deriveAll0' 'FamilyChar) -- instance Generic (Family Char b) where ...
+$('deriveAll1' 'FamilyTrue) -- instance Generic1 (Family Bool) where ...
+-- Alternatively, one could type $(deriveAll1 'FamilyFalse)
+@
+-}

 -- Adapted from Generics.Regular.TH
 module Generics.Deriving.TH (

Yea, that worked. Again not sure why. Maybe close this bug for now and when someone else hits this apply your patch?


Exception

debugMode is useless. Need to throw exception with good description

Just done this (i think). Now, if there is an error, the rest of the process won't crash. Also, if debugMode is set to TRUE , an error message will be shown (PDOException)


مرحبا اخواني لي طلب من فظلك في تهكير ارجو تساعدوني

I'm banggali

how r u
On Sat, Feb 26, 2022, 12:49 AM Amir khan @.***> wrote:

I'm banggali
—
Reply to this email directly, view it on GitHub
https://github.com/lovehacker404/World/issues/17#issuecomment-1051173524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWHU4BDXBFAKHNXSIED7IYTU47MMPANCNFSM43KFDXAA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi need help to hack a insta account and I can pay .

Yeah Shure
On Sat, Apr 16, 2022, 1:56 PM Zaki1408 @.***> wrote:

Hi need help to hack a insta account and I can pay .
—
Reply to this email directly, view it on GitHub
https://github.com/lovehacker404/World/issues/17#issuecomment-1100612406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWHU4BC7ICLYB2N3663VJF3VFJ6DPANCNFSM43KFDXAA
.
You are receiving this because you commented.Message ID:
@.***>


feature/saga branch import cycles need to be breaked

What happened:
feature/saga
There are two import cycles under engine package that need to be breaked. Unlike Java, this behaviour is not allowed in Golang.
How to reproduce it (as minimally and precisely as possible):
Write a unit test under engine package, e.g., statemachine_engine_test.go. Try to run it but it gives the following errors.

Closed by #647

Closed by #647


Short Login Time

Hello, this is sort of an issue but how can I increase the cookie expiration time because it only stays logged in for 30 minutes which I need to be longer. Also, the token_validity does not seem to help, nor the cookie_expire_secconds because I have it set to "2592000" seconds or 30 days. All help is appreciated.

It should be longer than 30 minutes by default, you can change the
expiration in the Edit Site Config page. If it's still not working, I'd
like to take a look at it at some point to see if I have a bug
[image: Screen Shot 2019-06-02 at 12.42.28 PM.png]
On Sat, Jun 1, 2019 at 4:45 PM MrLava13<EMAIL_ADDRESS>wrote:

Hello, this is sort of an issue but how can I increase the cookie
expiration time because it only stays logged in for 30 minutes which I need
to be longer. Also, the token_validity does not seem to help, nor the
cookie_expire_secconds because I have it set to "2592000" seconds or 30
days. All help is appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/therecluse26/PHP-Login/issues/232?email_source=notifications&email_token=AB63QATXCGUYFV32JASPTPLPYLNVNA5CNFSM4HSBIPD2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXDS3MQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB63QAQLMB7LNWXC5RV5OA3PYLNVNANCNFSM4HSBIPDQ
.

Hello, sorry for the late reply, I tried in many ways what you said but nothing seemed to work.


Randomization not working

I have the following prompt (and corresponding wildcard files for f_sentient and f_animal):
${animal=!{__f_animal__}}  ${sentient=!{__f_sentient__}} [${animal}|${sentient}|${animal}] AND ${sentient} in an ancient forest. Dramatic lighting. dappled lighting. deeps shadows.
Every time I run with a "batch count" > 1, each resulting image uses exactly the same wildcard values. The same is true if I set batch-size > 1 and batch_count = 1.  The values seem to repeat no matter what.
However, if I hit "Generate" again, the values are different.
Dynamic Prompts version
45b21373 | Sat Jun 3 10:48:47 2023
version: v1.3.2  •  python: 3.10.7  •  torch: 2.0.1+cu118  •  xformers: N/A  •  gradio: 3.32.0  •  checkpoint:<PHONE_NUMBER>45b21373	Sat Jun 3 10:48:47 2023

@tscott65
Instead of using batch count and batch size, under  dynamic prompts, enable "Combinatorial generation" and leverage "Max generations" and "Combinatorial batches".
You may still have issues,  A few of us are having issues using Immediate evaluation of variables like you are:
https://github.com/adieyal/sd-dynamic-prompts/issues/421

I encountered the same problem after upgrade today.
Reinstalling dosen't help.

@akx what are your thoughts on this? It isn't a bug per se in that the sampler is designed to fix the value of the variable once it has been evaluated but the expectation of randomised values within a batch is reasonable. This problem would be resolved if we created a new sampler for every batch but then other session-based state like cyclical samplers wouldn't work. Perhaps we should reset variables each time we sample?

same bug for me

@adieyal Hm, don't we reset (or at least overwrite) them in the context for each generation? 🤔

I'm not 100% sure. The variable assignment is takes place in
https://github.com/adieyal/dynamicprompts/blob/main/src/dynamicprompts/samplers/base.py#L71-L75
    def _get_sequence(
        self,
        command: SequenceCommand,
        context: SamplingContext,
    ) -> StringGen:
        tokens, context = context.process_variable_assignments(command.tokens)
        sub_generators = [context.generator_from_command(c) for c in tokens]

        while True:
            yield rotate_and_join(sub_generators, separator=command.separator)

the variables are processed outside of the loop on line 71 but the generators are sampled inside of the loop and yielded to the caller. From my reading, I think that variables are only ever processed once.
Here is a unit test that fails
def test_random_variables_across_prompts(wildcard_manager: WildcardManager):
    cmd = parse("${ball=!{red|blue}} ${ball} ${ball} ${ball}")
    scon = SamplingContext(
        default_sampling_method=SamplingMethod.RANDOM,
        wildcard_manager=wildcard_manager
    )
    gen = scon.sample_prompts(cmd)
    seen = set(islice(gen, 40))
    assert len(seen) == 2

Not sure if I understand this topic correctly but I'm wondering whether #668 is related?


Energy Use Trends - New Buildings Issue

Can call this a nice to have.
There is a flaw in the original design of the ENERGY USE TRENDS graph. Buildings that are built after the first year of data (2015) show up as an error Not enough data available even when they have data for every year they've existed. See id = 50254 as an example. This building has four years of site_eui_wn data but since it wasn't built or reporting data back to 2015 it throws an error.

┆Issue is synchronized with this Asana task

I've applied a fix here that gets available years from a given buildings data instead of from seattle.json, but I'm leaving this open for additional testing.
I do leave the original variable avail_years in place, in case it is used elsewhere. I only get previousYear from from the building data, right before passing to the shift template. Existing check to see that selected_year !== previousYear is left as is, as is the no_year flag

@tomay I did a bunch of testing on this. It seems to be performing quite well. The only odd behavior is sometimes the error message doesn't make sense. See id = 50662 as an example.
The building has 2020 data but shows this error:

And since 2020 is the first year of data for this building, selecting a different year isn't possible.
We might just need a different error message that is more generic.

There was already an error message for an invalid range of data. I extended this to include the case where there is only a single year of data

Note: previously, they were trapping errors for buildings which were missing data at the beginning of the range (with an error like above - "No data available for the year 2015".
This is no longer applicable, since we are taking whatever range of data is available. I haven't removed that completely, but instead worked around it

Thanks for the update. This looks good to me.


[Meru] [New Pricing] Grandfathering of existing users

Make sure that all workspaces created before a specific date will be free forever, with the current free plan limits imposed on them.
Technical implementation TBD.

The main question here is whether we have a free plan object in DB or not and whether the free plan has a special role or not.

The problem is that we don't have a subscription (link between plans and workspaces) for existing free users, logic happens here: https://github.com/dust-tt/dust/blob/main/front/lib/auth.ts#L517-L559

Add logic to create a Subscription object for all workspaces as they get created, that put them in the current FREE_TEST_PLAN

Ok, so this should be removed when we remove the free test plan.
Plan looks good to me.

Given that other pieces depend on this PR, I'm wondering if we could not be more aggressive 🤔. If we were to start by doing:

Add logic to create a Subscription object for all workspaces as they get created, that put them in the current FREE_TEST_PLAN

We could probably infer in the Authenticator that if there is no subscription, then it's a FREE_TEST_PLAN . We can always backfill later.

This is the role of lib/auth.ts not the middleware. The idea here is to prepare the FREE_NO_PLAN and be ready to start using it. This reduces the risk of the final switch as we will have derisked the use of a grand-fathered FREE_TEST_PLAN entirely IMHO.
We could keep lib/auth.ts as is (return FREE_TEST_PLAN) but that adds more risk down the road so I'd rather spray it as much as possible.


Update dns related processes

Current dependencies on/for this PR:

main

PR #3329   (this PR)

This comment was auto-generated by Graphite.


Support for Firefox mobile

When viewing the example using Firefox Mobile for Android it seems the native media controls are used, making it impossible to navigate etc.

Video screenshot:

Live mode:

Normal mode:

fixed in 1.0.6


TypeError: Cannot read property '1' of null     at IncomingMessage. (/root/.node-red/node_modules/smartfritz/lib/smartfritz.js:36:74)

it happed by accident....what to do now?
8 Jul 09:32:50 - [red] Uncaught Exception:
8 Jul 09:32:50 - TypeError: Cannot read property '1' of null
    at IncomingMessage.<anonymous> (/root/.node-red/node_modules/smartfritz/lib/smartfritz.js:36:74)
    at IncomingMessage.emit (events.js:194:15)
    at IncomingMessage.EventEmitter.emit (domain.js:441:20)
    at endReadableNT (_stream_readable.js:1129:12)
    at process.internalTickCallback (internal/process/next_tick.js:72:19)
root@deb8mpd-virt:~/.node-red#

no, wait..i changed the fritzbox-ip ....
but node-red does not start anymore...
where is the place to change it by hand?


Add content/es/docs/reference/glossary/pod-priority

created file content/es/docs/reference/glossary/pod-priority.md to translate Pod Priority to Spanish

Hey @krlooss, thanks for the PR. Do you mind updating the PR title and providing a description of this PR? Thanks!

Hey @krlooss, thanks for the PR. Do you mind updating the PR title and providing a description of this PR? Thanks!

Done!

/lgtm

/lgtm

Muchas gracias!
/approve


include/nuttx/sched.h:  Move prototype for sched_releasetcb()

Move the prototype for the internal OS from from sched/sched/sched.h to include/nuttx/sched.h.  This was done because binfmt/binfmt/excecmodule.c requires the prototype for sched_releasetcb() and was illegally including sched/sched/sched.h.  That is a blatant violation of the OS modular design and the person that did this should be hung up by their thumbs.  Oh... I did that back in a bad moment in 2014.  Now that is made right.

Incidentially, I think this change would fix the build broken by PR  #625  with the single configuration that I tested:  stm32f4discovery:nsh.  But this PR is not a fix for the problems with PR  #625  is not a fix to the problem.  It would fail on other builds because it has a logic error in the ordering.