I too encountered diminishing returns from brute-forcing encoding variations and parameter adjustments. This is why I left it in the recovery script as a fallback. However, the entropy-driven bitshifting technique, based on observed key correlations, has shown more promising results.
I aim to upload the relevant script in the next 6-12 hours, although I need to be cautious about what data I post.
Bruteforcing encoding didn’t yield tangible results either, but I included it in the recovery process to cover all possible angles.

Thanks for the detailed explanation. I'm particularly interested in the part about "recognizable keys emerging from random noise" through bitshifting - that sounds like a significant finding. Could you share a simple example of this, even with test data? Even a small code snippet showing how you're applying Dijkstra's algorithm to the bitshifting process would help me understand the approach.
Also curious about why you chose Dijkstra's algorithm specifically perhaps I'm really not seeing some connection but what graph structure are you optimizing?

Thanks for the detailed explanation. I'm particularly interested in the part about "recognizable keys emerging from random noise" through bitshifting - that sounds like a significant finding.

Could you share a simple example of this, even with test data?

Even a small code snippet showing how you're applying Dijkstra's algorithm to the bitshifting process would help me understand the approach.

Also curious about why you chose Dijkstra's algorithm specifically perhaps I'm really not seeing some connection but what graph structure are you optimizing?

As I am struggling to find the time to update the repository right now, I will take the time to elaborate further now, prior to updating the repository.
For the sake of staying as close to the original design as possible that yielded valuable insight, the concept of a trigonometric star was used in conjunction with Dijkstra's, although in my research yesterday, a toroidal approach was found to be more appropriate as AES is a cylindrical design when you think about the elliptical aspect of it.
Due to the elaborate nature of this solution, the following is a GPT refined explanation:

The idea of recognizable keys emerging from random noise through bitshifting is rooted in the principle that, with the correct approach, we can reveal hidden structures within what seems like random data. By shifting bits in a specific manner (guided by entropy analysis), some bit patterns will align in a way that mimics valid cryptographic keys. This process can be visualized as manipulating data in a 3D space where each possible bit shift represents a movement along a different axis. These shifts, when observed in a "perspective" (similar to how 3D objects are projected onto a 2D screen), begin to reveal key-like structures amidst the noise.
In this context, trigonometry comes into play when interpreting the angular relationships between the positions of the bits and their shifts. As we shift bits, we're essentially rotating through different "planes" of the key, trying to align certain parts of the key with valid key patterns. This alignment can be seen as a projection from a 3D perspective, where each possible state of the key corresponds to a point in this space, and the key we're trying to recover is a projection of this space.
Dijkstra's algorithm fits into this process conceptually as a pathfinding mechanism to identify the optimal sequence of transformations (bit shifts) that minimize entropy. Imagine each bit shift as a potential "edge" in a graph where the "weight" of the edge represents the entropy deviation from the expected value. The algorithm navigates this graph, finding the shortest path to the configuration that produces a stable, low-entropy output — in this case, a recognizable key structure.
For example, consider the following pseudocode to demonstrate the basic idea:
import numpy as np

def entropy(data):
    """Calculate Shannon entropy of data."""
    _, counts = np.unique(data, return_counts=True)
    probabilities = counts / len(data)
    return -np.sum(probabilities * np.log2(probabilities))

def bitshift(data, shift):
    """Perform bitwise rotation."""
    return [(byte >> shift | byte << (8 - shift)) & 0xFF for byte in data]

def find_optimal_shift(data):
    """Apply Dijkstra's-like logic to minimize entropy."""
    min_entropy = float('inf')
    optimal_shift = 0

    for shift in range(1, 8):  # Test all bit shifts
        shifted_data = bitshift(data, shift)
        current_entropy = entropy(shifted_data)
        if current_entropy < min_entropy:
            min_entropy = current_entropy
            optimal_shift = shift

    return optimal_shift, min_entropy

This example illustrates the process of evaluating each bit shift and calculating the corresponding entropy. The optimal shift is the one that produces the lowest entropy, revealing potential alignment with valid key data.
The trigonometric perspective becomes evident when mapping this process to a toroidal structure. Each bit position and shift can be visualized as points on a 3D torus, where rotations and angular displacements correspond to shifts in the data. By leveraging trigonometry, we can predict and refine the pathfinding process, improving the efficiency of entropy reduction and bit alignment.

I'll work on updating the repository with a more detailed implementation and some actual test data, but this explanation should provide a clearer picture of the theoretical solution in the meantime.

I appreciate the time you've taken to explain your approach, but I feel I need to be direct here, as this thread involves people hoping to recover potentially significant funds.
The trajectory of this discussion has been concerning:

Initial claims about specific entropy patterns and bitshifting successes
When asked for examples, increasingly complex theoretical explanations
Finally, admitting to using GPT to explain an elaborate theory
Yet still no actual demonstration of the claimed successes

The example code provided is just basic bit rotation and entropy calculation - nothing that implements the complex system described or demonstrates the key recovery you initially claimed to achieve.
If you have made genuine progress on this problem, I'm still very interested in seeing it. But if this is mostly theoretical or AI-generated ideas, it would be better to be upfront about that. Many people in this thread are hoping to recover significant funds, and it's important to be clear about what has actually been achieved versus what are just theoretical approaches that could be tried.

I appreciate the time you've taken to explain your approach, but I feel I need to be direct here, as this thread involves people hoping to recover potentially significant funds.
The trajectory of this discussion has been concerning:

Initial claims about specific entropy patterns and bitshifting successes
When asked for examples, increasingly complex theoretical explanations
Finally, admitting to using GPT to explain an elaborate theory
Yet still no actual demonstration of the claimed successes

The example code provided is just basic bit rotation and entropy calculation - nothing that implements the complex system described or demonstrates the key recovery you initially claimed to achieve.

Let's dissect your post (and I will be equally direct)
1: If you think claims of entropy and bitshifting to be irrelevant (or concerning) in this matter, I really do advise you take a step back and think.
You're talking about elliptical curves and advanced encryption standards, if you think entropy has nothing to do with this, then I suggest not to carry this further as It's obvious to me and any other cryptographer.
2: I increased the explanation so that you could get the relevant information necessary, while organising myself. It has been 4 days, this is not a lot of time for someone who is around the clock on other matters.
It seems you have completely skipped over the fact that I explained in depth on how to use Dijkstra's and trigonometry to derive the key.
3: I told you previously, 4 days ago, that I used GPT to revise what I say, it is not theoretical in the slightest, I wasn't "Finally, admitting to using GPT".
Re:

For clarification, I do use GPT from time to time to rephrase my wording as I do have issues with how I word myself and I want zero misunderstandings in a situation like this.

The fact that you have stated this, makes me wonder if you read my last explanations at all.
It also serves as a high deterrence to scold someone about the usage of AI to refactor their wording.
4: If there was no actual demonstrations of claimed successes, what is Recover.py, a claim that I didn't substantiate? I claimed I was able to derive the keys from working keys without issue, the claim was clearly substantiated as the script can derive non-defunct keys. Just like every other claim I have made, will also be substantiated.
Clearly I understand the intricate details of advanced encryption standards and elliptical curves used, or I never would have mentioned a toroidal structured trigonometric guided modified dijkstra’s algorithm as a method of possible recovery.

If you have made genuine progress on this problem, I'm still very interested in seeing it. But if this is mostly theoretical or AI-generated ideas, it would be better to be upfront about that. Many people in this thread are hoping to recover significant funds, and it's important to be clear about what has actually been achieved versus what are just theoretical approaches that could be tried.

If you are genuine and interested to see it, that's fine, but I am starting to wonder if your intentions are in bad faith to be quite honest, to intentionally distort the narrative and press on the matter with extreme passive aggresion, when I have stated my finite time repeatedly, is what is actually concerning here.
With an issue ongoing for over a decade and where you would like immediate data and scripts from someone who is doing this for free and who has stated they work 6/7 days a week, is nothing short of inconsiderate.
I will now take the time necessary that I need and I will update the repository when I am good and ready.
Pressuring others for the sake of good publicity may work for some, but it will not work on me.

I think there may be some misunderstanding here. My concerns aren't about:

The use of entropy analysis (which is absolutely relevant)
Using AI to help with wording
The time needed to properly document work

Rather, I'm trying to understand the gap between what's been claimed (deriving keys through entropy-guided bitshifting) and what's been shown (Recover.py, which implements standard decryption attempts).
If you need more time to document your findings, that's obviously fine. I'm not applying pressure to you I just want to understand what's been actually achieved so far, as this could affect decisions many others make when investigating recovery mechanisms.

I think there may be some misunderstanding here. My concerns aren't about:

The use of entropy analysis (which is absolutely relevant)
Using AI to help with wording
The time needed to properly document work

Rather, I'm trying to understand the gap between what's been claimed (deriving keys through entropy-guided bitshifting) and what's been shown (Recover.py, which implements standard decryption attempts).
If you need more time to document your findings, that's obviously fine. I'm not applying pressure to you I just want to understand what's been actually achieved so far, as this could affect decisions many others make when investigating recovery mechanisms.

It appears to me as if the tone in your previous comment was clear,  however for the sake of everyone's benefit, I am willing to disregard it.
No one deserved to lose their funds to this mistake and while I would be inclined to point the finger and say that it is the creators fault, it's really a combination of multiple people who created this issue.
Moving forward and closing the gap, I'll simply update the repository after the holidays, rather than attempt to explain any further, as I have attempted to do so with little success.
I understand that the methodology I have put forth is rather complex and quite unorthodox, hopefully it makes sense to some in the time being.
It's much easier to just show your work, and so I'll do just that as soon as I can.


Document how to set initial spec

I would like to set the initial spec. The docs says

I do not understand how to use this and cannot find any examples. Please provide.
I would like to be able to use it to finalize the PR https://github.com/panel-extensions/panel-graphic-walker/pull/27.

Solution
My spec was from exporting the current chart. It was a dict in Python. I have to provide it as an Array in React:
<GraphicWalker
...
chart=[spec]
/>

This was not very clear for several reasons

- `chart` is not in the API props docs: https://github.com/Kanaries/graphic-walker#props
- the legacy `spec` confused me. It told me to try to use `storeRef` - which is not documented either.


when using pipe raise AttributeError!

below is my code:

r = redis.Redis(host, port)
p = r.pipeline()
p.set('foo','bar')
Pipeline<ConnectionPool<Connection<host=<IP_ADDRESS>,port=9006,db=0>>>
p.set('bing','bbb')
Pipeline<ConnectionPool<Connection<host=<IP_ADDRESS>,port=9006,db=0>>>
p.execute()
Traceback (most recent call last):
File "", line 1, in
File "/data/news/arioliu/qps_test/env/lib/python2.7/site-packages/redis/client.py", line 2879, in execute
return execute(conn, stack, raise_on_error)
File "/data/news/arioliu/qps_test/env/lib/python2.7/site-packages/redis/client.py", line 2785, in _execute_transaction
response.insert(i, e)
AttributeError: 'str' object has no attribute 'insert'

when i use p = r.pipeline(transaction=False),  it is ok!

What version of redis-py and redis are you using?
I've run your exact code block locally it works as expected.


Hi there is no return in the utils.py file ?

While I was trying to understand the utils.py file but there is no return for the last function, Am I missing something ? Thank You!!

Hi @jhasuman
That function is a generator.  The 'yield' returns values but the function itself does not return/exit.
If you search for 'Python generator' or 'Keras fit_generator', you should be able to find related articles.  For example,

https://jeffknupp.com/blog/2013/04/07/improve-your-python-yield-and-generators-explained/
https://medium.com/@fromtheast/implement-fit-generator-in-keras-61aa2786ce98

@jhasuman - I'm closing this for now.  Let me know if you need any further clarification.


Update khalti SDK to make use of updated APIs

This PR makes changes in how merchants can use Khalti SDK to make payments.

Previously, the SDK provided most of the UI elements that should have been incorporated in their app. This change brings a WebView implementation of Khalti Payment Portal for seamless adaptation and payment making process.
The SDK removes all the deprecated backend APIs with the new APIs.
Removal of khalti package. Now there are only khalti_core and khalti_flutter packages in this repo.
Version Bump in khalti_flutter and khalti_core library.

@Biplab-Dutta What are the changes introduced in this PR?

@Biplab-Dutta What are the changes introduced in this PR?

@Ishwor-Shrestha Updated description

Dart Package for new version

khalti_checkout

Flutter package for new version

khalti_checkout_flutter

Project namespace to be renamed as - "Khalti Checkout"

and first version to be pushed as
1.0.0-preview-release

The changes have been made. The release on pub.dev remains. @acpmasquerade


Verifiably reproducible build artefacts

Description of issue or feature request:
We can give users of our release artefacts (tarballs and wheels) greater confidence in the integrity of the artefacts and our development processes if they can verify that the artefacts we produced correspond to the signed tagged source code for the release.
We can achieve this through implementing reproducible builds.
Current behavior:
Tarball (sdist) and wheels (bdist_wheel) generated for a release are not verifiably reproducible.

$ diff dist-a dist-b
Binary files dist-a/tuf-0.16.0-py2.py3-none-any.whl and dist-b/tuf-0.16.0-py2.py3-none-any.whl differ
Binary files dist-a/tuf-0.16.0.tar.gz and dist-b/tuf-0.16.0.tar.gz differ

Expected behavior:
Tarball (sdist) and wheels (bdist_wheel) generated for a release are verifiably reproducible.

Ensuring SOURCE_DATE_EPOCH is set (i.e. this patch) enables us to create verifiably reproducible wheels, but the tarball (sdist) is still not verifiably reproducible.

$ diff dist-r-a dist-r-b
Binary files dist-r-a/tuf-0.16.0.tar.gz and dist-b-r/tuf-0.16.0.tar.gz differ

Ensuring SOURCE_DATE_EPOCH is set (i.e. this patch) enables us to create verifiably reproducible wheels, but the tarball (sdist) is still not verifiably reproducible.

$ diff dist-r-a dist-r-b
Binary files dist-r-a/tuf-0.16.0.tar.gz and dist-b-r/tuf-0.16.0.tar.gz differ

Note: I tried this on macOS and Fedora 33. I don't think the sdist being non-deterministic is host tool related.

Note: I tried this on macOS and Fedora 33. I don't think the sdist being non-deterministic is host tool related.

tar isn't deterministic by default, do they still differ when generated with --mtime?

tar isn't deterministic by default, do they still differ when generated with --mtime?

Quite right, thanks for the link! Our sdist tarballs are generated by setuptools, which (so far as I could tell in the relatively brief time I spent looking today) has no option to specify mtime.
It's possible we just have to brute force this; unpack and re-pack the tarball with --mtime, use strip-nondeterminism, or similar.
I intend to spend some more time on this in the next couple of weeks, unless someone gets to it first.

Quite right, thanks for the link! Our sdist tarballs are generated by setuptools, which (so far as I could tell in the relatively brief time I spent looking today) has no option to specify mtime.
It's possible we just have to brute force this; unpack and re-pack the tarball with --mtime, use strip-nondeterminism, or similar.
I intend to spend some more time on this in the next couple of weeks, unless someone gets to it first.

Hello! Dropping in to say it'd be nice if these techniques could be made available to the broader Python community somehow.

Hello! Dropping in to say it'd be nice if these techniques could be made available to the broader Python community somehow.

There have been pieces of work done in multiple places to support this:

stalled PR against setuptools to have it respect SOURCE_DATE_EPOCH when creating an sdist: https://github.com/pypa/setuptools/pull/2136
stable ordering of sdist contents for NixOS https://github.com/NixOS/nixpkgs/pull/105680

I think the right next step for having a reproducible sdist for tuf is to try and get the above changes accepted into setuptools.

Updating the state since I started looking where we are with this. Wheel build does seem reproducible and I think this is how we want to set it:
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct) python3 -m build

The source tarball issue still persists. I have a home grown diff solution though:
import hashlib
import sys
import tarfile

chunk_size = 100000
tar = tarfile.open(sys.argv[1])
content_hash = hashlib.sha256()

for member in tar:
    if not member.isfile():
        continue
    member_file = tar.extractfile(member)
    data = member_file.read(chunk_size)
    while data:
        content_hash.update(data)
        data = member_file.read(chunk_size)

print(content_hash.hexdigest())

that prints a hash for tarball file contents (disregarding owner, group, mtime, etc metadata).

Updating the state since I started looking where we are with this. Wheel build does seem reproducible and I think this is how we want to do it:
# Use latest commit date as epoch
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct) python3 -m build

As recommended by the SOURCE_DATE_EPOCH documentation 👍

The source tarball issue still persists. I have a home grown diff solution though:
import hashlib
import sys
import tarfile

chunk_size = 100000
tar = tarfile.open(sys.argv[1])
content_hash = hashlib.sha256()

for member in tar:
    if not member.isfile():
        continue
    member_file = tar.extractfile(member)
    data = member_file.read(chunk_size)
    while data:
        content_hash.update(data)
        data = member_file.read(chunk_size)

print(content_hash.hexdigest())

that prints a hash for tarball file contents (disregarding owner, group, mtime, etc metadata). It does care about file order.

That's neat. We could write/maintain a little tool to diff tarballs based on their content hashes. Would be nice to help fix this for other Python projects too, but not something we should block python-tuf activities on.

The goal of this work IMO should be a tool verify-release that anyone can run. Tool would:

build tarball & wheel locally
download tarball & wheel from github
download tarball & wheel from pypi using pip
verify that that all three are the same or complain loudly

As a first step we could add running the tool to the release instructions.
As a second step, we could run the tool on CI regularly (for each release from 1.0 onwards)
As an added feature the tool could check for signature

Potential solution: https://github.com/theupdateframework/python-tuf/pull/1896#issuecomment-1066034901

So reproducible builds:

ofek has a potential solution for tarball repro in #1896
I've got a branch with a verify script (compares local build result to pypi and github release): https://github.com/jku/python-tuf/blob/verify-release/verify_release -- this should be useful for

any developer to verify the release even when release is done manually
CI to periodically verify releases (a canary check)
after we move to automated CD releases, the release manager can verify the release as it's being made

we should at least consider the build tool pinning issue: currently build dependencies (hatchling at least?) are not pinned.
@ofek do you have opinions about this? I'd like to make sure the build (made from a specific commit) is the same if I run it today or if I run it 6 months from now. I think that suggests we want to pin at least the hatchling version (and plan to bump the pinned version as new hatchling releases are made) but it's possible I'm missing some detail: I'm not very familiar with the python build ecosystem.

ofek has a potential solution for tarball repro in Update package metadata #1896

It works for tarball and wheel repro. Or did you not mention wheels because setting SOURCE_DATE_EPOCH in a deterministic way is all that's needed?  Ofek's wheel builder uses a constant, which IMO is just as fine as the latest git commit.

I've got a branch with a verify script (compares local build result to pypi and github release):

Cool stuff! Maybe at a later point we can generate in-toto metadata for builds and use in-toto also to verify them. I'll add a comment to #529.

we should at least consider the build tool pinning issue: currently build dependencies (hatchling at least?) are not pinned.

Not sure if we need to pin the build dependency. I think it would be enough to keep a record of the build environment. But there doesn't seem to be a canonical way for python projects yet.

did you not mention wheels because setting SOURCE_DATE_EPOCH in a deterministic way is all that's needed

Yes correct, I did not mean to imply 1896 didn't handle this.

Not sure if we need to pin the build dependency. I think it would be enough to keep a record of the build environment.

Yeah that's the other option... I just think it might be easiest to "document" it in pyproject.toml :) This could have some consequences I'm not seeing at the moment though

we should at least consider the build tool pinning issue [...] @ofek do you have opinions about this? I'd like to make sure the build (made from a specific commit) is the same if I run it today or if I run it 6 months from now

Sure, that makes sense to pin

what about transient deps (currently editables, pluggy, packaging, pathspec, tomli)

No need IMO

I think I'll close this: build is reproducible, and there is a script to check that. These are the main items here.
Build environment maybe should be pinned, or at least documented in the build artefacts but I think we can handle that as future work after #1550...


[FEATURE REQUEST] Loop song button

A small button that if tapped will loop the song.
The code that needs to be added to the embed for this to work is loop=1, that's the youtube api code.
@TechStudent11 Please work on this today, if possible otherwise tommrow. Thanks

A small button that if tapped will loop the song.
The code that needs to be added to the embed for this to work is loop=1, that's the youtube api code.
@TechStudent11 Please work on this today, if possible otherwise tommrow. Thanks

The thing is, I don't think I loop a specific segment of a video. Can I?

A small button that if tapped will loop the song.
The code that needs to be added to the embed for this to work is loop=1, that's the youtube api code.
@TechStudent11 Please work on this today, if possible otherwise tommrow. Thanks

The thing is, I don't think I loop a specific segment of a video using the YouTube API.

Yes, little extra work but all the songs are listed in the playlist right? Can you make a func that if the loop button is pressed it knows what song was played on top and using the title of the song it will loop via the youtube video of that individual song? Or, will that mess up things? If possible, this would be great, otherwise, its not really needed, just a idea.

A small button that if tapped will loop the song.
The code that needs to be added to the embed for this to work is loop=1, that's the youtube api code.
@TechStudent11 Please work on this today, if possible otherwise tommrow. Thanks

The thing is, I don't think I loop a specific segment of a video using the YouTube API.

Yes, little extra work but all the songs are listed in the playlist right? Can you make a func that if the loop button is pressed it knows what song was played on top and using the title of the song it will loop via the youtube video of that individual song? Or, will that mess up things? If possible, this would be great, otherwise, its not really needed, this was just a idea coz a loop button would be good in the project, if possible.

When you say a little extra work, you mean a ton of API requesting. Yes, this is possible, and yes I can do it, but it would require a ton of code, debugging and refactoring.
In short, it isn't worth it.

True.
I found that stackoverflow too, but I didn't understand it lol

@TechStudent11 So, can you work on this?

@TechStudent11 Please can you work on this on priority as soon as possible?

@TechStudent11 Please can you work on this on priority as soon as possible?

Waiting for your reply on this @TechStudent11 ... Thanks

Tell me where you want the button to be placed and I'll handle the rest.

Tell me where you want the button to be placed and I'll handle the rest.

After the song has been started playing, a small button can appear above the lyrics button.

Tell me where you want the button to be placed and I'll handle the rest.

After the song has been started playing, a small button can appear above the lyrics button.

okay

Okay so I looked at it a bit more, and this is going to require basically a full rewrite. I think we should hold off on this feature until the React/Next rewrite (#189) is complete.

Okay so I looked at it a bit more, and this is going to require basically a full rewrite. I think we should hold off on this feature until the React/Next rewrite (#189) is complete.

Ok cool

If someone else can work on this in the current way it is, ig we'll proceed. Hope that's fine @TechStudent11

If someone else can work on this in the current way it is, ig we'll proceed. Hope that's fine @TechStudent11

yeah sorry. I've been working on a mobile app, so I haven't been working on anything else, really.

No, you said we should do this after we convert it to React or Next.JS so
that's why I asked this. I kinda knew you were using the mobile app.
On Sat, 12 Feb 2022 at 20:09, TechStudent10 @.***>
wrote:

If someone else can work on this in the current way it is, ig we'll
proceed. Hope that's fine @TechStudent11
https://github.com/TechStudent11
yeah sorry. I've been working on a mobile app, so I haven't been working
on anything else, really.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1037243235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTPIX2B6EKNY4KH72W3U2ZWJNANCNFSM5NERG3WA
.
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 authored the thread.Message ID:
@.***>

No, you said we should do this after we convert it to React or Next.JS so that's why I asked this.

Ohh okay.

I kinda knew you were using the mobile app.

No, as in I am coding a mobile app.

Ok oh, what are you using? Android Studio?

I'm using React Native with the Expo CLI.

interesting
On Sun, 13 Feb 2022 at 01:52, TechStudent10 @.***>
wrote:

Ok oh, what are you using? Android Studio?
I'm using React Native with the Expo CLI.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1037451683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTNIPUVOOGYVTZNZ6VDU226SBANCNFSM5NERG3WA
.
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 authored the thread.Message ID:
@.***>

I aim for this to be done by July 2022, but, as @TechStudent11 said, I'm sure not sure if https://github.com/KendallDoesCoding/mogul-christmas/issues/189 needs to be done before this for this to work.

@TechStudent11 Is this possible in a .mp3 version/offline version... I'm getting to work on that soon.
Example: http://music-in-browser.test.kendalldoescoding.gq/

Hi @KendallDoesCoding i think there should also be a pause button.

Hi @KendallDoesCoding i think there should also be a pause button.

Hi @ArhyaSaha , This would be better if it is part of #105 instead of on this issue, this issue is solely for the purpose of a button to loop the song.

@ArhyaSaha any update?
@CipherKill as you helped with the stop button, would you be able to help with the loop button as well?

To recap, you need a loop button that would play the played/playing song from the beginning ?

Yes!!
On Thu, 22 Sept 2022 at 21:33, Alan Raju @.***> wrote:

To recap, you need a loop button that would play the played/playing song
from the beginning ?
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1255238632,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTO4UMYOR6NIXTSMYMLV7R7NFANCNFSM5NERG3WA
.
You are receiving this because you were mentioned.Message ID:
@.***>

It's possible, but using "loop=1" on the URL isn't the way to go. I'll test out an idea I have and let you know here.

Yes, I know.. Ok, thanks! If it works out, please make a PR.
On Thu, 22 Sept 2022 at 22:26, Alan Raju @.***> wrote:

It's possible, but using "loop=1" on the URL isn't the way to go. I'll
test out an idea I have and let you know here.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1255299849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTIDY4R4PUQC55BQZNLV7SFUPANCNFSM5NERG3WA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sure!

Hey! Good news, got it to work. Making a PR now.

Thanks!
On Fri, 23 Sept 2022 at 15:15, Alan Raju @.***> wrote:

Hey! Good news, got it to work. Making a PR now.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1256003802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTLN5A7PTZNZLZT62C3V7V35LANCNFSM5NERG3WA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Arhya,
That can be a part of #105 as it relates to volume.
On Wed, 24 Aug 2022, 2:34 am ArhyaSaha, @.***> wrote:

Hi @KendallDoesCoding https://github.com/KendallDoesCoding i think
there should also be a pause button.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/187#issuecomment-1224885085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTOEHCEYB5ULVGHYG53V2U4GNANCNFSM5NERG3WA
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix: for failing doc generation

Codecov Report

Merging #728 (47f3de7) into main (103c73a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #728   +/-   ##
=======================================
  Coverage   48.70%   48.70%
=======================================
  Files          68       68
  Lines        2014     2014
  Branches       46       46
=======================================
  Hits          981      981
  Misses       1033     1033

Impacted Files
Coverage Δ

zio-http/src/main/scala/zhttp/html/Dom.scala
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Appstudio update test-component-pac-qclo

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-qclo-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
2 minutes
deprecated-base-image-check

✅ Succeeded
16 seconds
sanity-inspect-image

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
7 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary


fzn-ortools, cumulative, missing solution

What version of OR-Tools and what language are you using?
Version: 9.6
Language: MiniZinc
Linux Ubuntu 22.04
What did you do?
The solution A = 2; D = 3; H = 1; I = 0; is missing.
$ cat /tmp/latest.mzn
include "globals.mzn";
var 1..2: A;
var 2..3: D;
var 1..2: H;
var 0..1: I;
constraint
    A+I=2;
constraint
    H+D=4;
constraint
    cumulative([A,3,H,1],[I,0,D,1],[1,1,1,0],1);
$ minizinc -a --solver ortools /tmp/latest.mzn
A = 1;
D = 2;
H = 2;
I = 1;
----------
A = 2;
D = 2;
H = 2;
I = 0;
----------
==========

name: "cumulative_missing_solution_sat"
variables { name: "A" domain: [1, 2] }
variables { name: "D" domain: [2, 3] }
variables { name: "H" domain: [1, 2] }
variables { name: "I" domain: [0, 1] }
variables { name: "X_INTRODUCED_4_[2]" domain: [0, 0] }
variables { name: "X_INTRODUCED_4_[4]" domain: [1, 1] }
variables { name: "X_INTRODUCED_5_[2]" domain: [3, 3] }
variables { name: "X_INTRODUCED_5_[4]" domain: [1, 1] }
variables { domain: [1, 3] }
variables { domain: [3, 5] }
constraints {
  name: "int_lin_eq"
  linear {
    vars: [0, 3]
    coeffs: [1, 1]
    domain: [2, 2]
  }
}
constraints {
  name: "int_lin_eq"
  linear {
    vars: [2, 1]
    coeffs: [1, 1]
    domain: [4, 4]
  }
}
constraints {
  name: "fzn_cumulative"
  cumulative {
    capacity { offset: 1 }
    intervals: [3, 5, 6, 8]
    demands { offset: 1 }
    demands { offset: 1 }
    demands { offset: 1 }
    demands { }
  }
}
constraints {
  interval {
    start { vars: [0] coeffs: [1] }
    end { vars: [8] coeffs: [1] }
    size { vars: [3] coeffs: [1] }
  }
}
constraints {
  linear {
    vars: [0, 3, 8]
    coeffs: [1, 1, -1]
    domain: [0, 0]
  }
}
constraints {
  interval {
    start { vars: [6] coeffs: [1] }
    end { vars: [6] coeffs: [1] }
    size { }
  }
}
constraints {
  interval {
    start { vars: [2] coeffs: [1] }
    end { vars: [9] coeffs: [1] }
    size { vars: [1] coeffs: [1] }
  }
}
constraints {
  linear {
    vars: [2, 1, 9]
    coeffs: [1, 1, -1]
    domain: [0, 0]
  }
}
constraints {
  interval {
    start { vars: [7] coeffs: [1] }
    end { vars: [7] coeffs: [1] offset: 1 }
    size { offset: 1 }
  }
}


Client Libraries: github.com/ericchiang/k8s  listed but unmaintained since 3-5 years.

github.com/ericchiang/k8s is mentioned as a third party Go library, but has been archived by its author on Nov 19, 2020 (3m years ago as of writing this issue), last published at pkg.go.dev/github.com/ericchiang/k8s on Jul 26, 2018.
So I would suggest to at least list it with an appropriate comment in https://kubernetes.io/docs/reference/using-api/client-libraries/#community-maintained-client-libraries (e.g. "Unmaintained/Archived").
It  might still be useful to know it, as it appears to be imported by ~580 projects according to https://pkg.go.dev/github.com/ericchiang/k8s?tab=importedby but usage in new projects should be discouraged and well maintained active projects should probably move away from it.
De-listing that library might also be possible action to take.
Please note, that I didn't bother to test whether the library still works at all.

There was some discussion in https://github.com/kubernetes/website/issues/21563#issuecomment-660775584

/language en

We're wary of passing judgement on third party code: it might look as if we're tacitly endorsing the rest of the list (which isn't true). However, as https://github.com/ericchiang/k8s is archived, I think it's OK to remove the link.
This does not set a precedent for removing or commenting on third-party links without an obvious mark such as the maintainer setting it as archived

/triage accepted
/priority backlog
/help

The action I recommend: remove the link, on the grounds that the repo we link to is archived. We do also provide an in-project alternative library, https://github.com/kubernetes/client-go/, which is well tested.

i will try to help with this.
/assign


MORNING SESSION: Peer-to-Peer code review

Changes Required ♻
Your code looks good, however, there are some changes I think might make your code look much better.
Below is the list of changes I think you should implement in your code.

[x] Please document your code too. it makes it easier to read.
[x]  We suggest you make the email interactive
[x]  kindly make your commit messages start with imperative verbs.  EXAMPLE "Modified the CSS file for linter errors"
[x]  Please fill in the alt attributes in your images.

Fixed
Hi, thank you for these helpful suggestions. 👍
I made the required changes (Pull Request: Fix Issues #1 and #2):

[x] Documented the code with comments in all the files
[x] Made the email interactive
[x] I will make sure that the next commit messages start with Upper-cases imperative verbs
[x] Fill the alt attribute for alt the img

Don't hesitate to open an issue if you have any other issues, I will be grateful.


feature: Document space framework for users of it

Feature Description
Users of the space framework need a document addressed to them.  I, as a reviewer of PRs changing space functionality consumers to use the space framework, need to understand how the space framework is intended to be used.
While the Go compiler does a certain amount of checking for consistency with the APIs already checked in, an author of code using the space framework needs to know much more than what is written in the Go code and checked by the compiler.
Clues can be found in my comments in my reviews of the PRs currently in flight: #897, #904, and #923.  Also the high level issues such as #905, #906, #913, #914, #928 .
Such a document will address the following issues, among others.

Division of roles and responsibilities; who makes what decisions when, how are those decisions recorded by the decision-maker and conveyed to decision consumers.
What needs to be configured in code that uses the space framework.
How space names correspond to kcp workspaces paths, when the kcp provider is used.
An architectural outline, with clear and distinct identification of process boundaries and library boundaries, boundaries between who owns/authors/maintains what.

Given the current extreme time crunch, I do not expect everything will be done to our complete satisfaction at first.  The needed document will at least be a roadmap.  It might call out forks in the road ahead, where we have decisions still to make.
Proposed Solution
This document gets written.
Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

@effi-ofer
@andreyod
@clubanderson

pushing to backlog, not committed for milestone1 - per @ezrasilvera


Add redirection support to the parser

This PR is quite big, it implements:

The simple_command rule and all its sub-productions (in varying states of completeness)
List node variant, for dealing with generic recursive rules (such as cmd_prefix and cmd_suffix)
Some restructuring of the Command node, to make use of the List node for its arguments.
Redirection node variant, to hold the [n]<redirection_token> <filename> production

It also includes the reserved words PR

Looks great overall.
I think it would be nice to add some docs that explain some of the parsing things like Rule, Option, Terminals and Non-Terminals etc. Maybe that would be nice a separate commit.
Making some parameterized tests for the parser similar to the lexer would also be great. But I also think that should be in a separate PR.


Refactor analytics notebook

This PR introduces a large-scale refactor to the analytics notebook. Noteworthy changes include:

complete removal of the DIBBs Postgres Connector client: its slow querying was a major performance bottleneck when it came to blocking on candidate records
introduction of parallelism through pyspark for both reading the MPI, generating candidate blocks, and evaluating match quality: we still have to parallelize the outer iteration over all records to evaluate (because spark worker nodes can't invoke the spark context to perform their own blocking filters), but all functionality to evaluate each of these records is fully parallelized (these changes are the most major and significant, particularly with conceptually what we can and can't accomplish on each worker node--they are found in the "Open parallel connection," "MPI tabulation," and "Linkage driver function" cells of the notebook)
introduction of robust sub-sampling to ensure that we can get performant but representative samples of patient data loaded at both the labeling and evaluative levels
edge-case catching on display strings: since we're not sub-sampling, there is a risk that we'll create match skews out of sheer change, which could result in divide by 0 errors if we get extremely unlucky and don't sample anyone intended to match; we now catch edge cases like these and they don't crash the file writing

@DanPaseltiner Ya totally fair point. I've got to push up a few tweak changes anyway that I just found during a fresh deploy full run through.


api: Use AsRef instead of &Path

This matches the convention used in std and makes the API simpler
when calling open() as you can just provide a &str or String and
it will be converted into a &Path autmmatically.  This change is
backwards compatible, so a full semver bump should not be required.
You can see this pattern in std in a number of places:

https://doc.rust-lang.org/std/fs/struct.File.html#method.open
https://doc.rust-lang.org/std/fs/fn.read_dir.html
... (basically everything that uses a path) ...

Thanks, merged as ee2ff8a81ab379943000d77eca164cdd853a4545


Add TensorEqualHandler

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

Comparison is base (7019ff0) 100.00% compared to head (ea1f517) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #366   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           53        54    +1
  Lines         1932      1957   +25
  Branches       361       363    +2
=========================================
+ Hits          1932      1957   +25

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


Fix distributed multi cert tests

This change is only to the TestExtractRootCerts function as I needed the multi-cert functionality and wanted it to be testable.
Proposed Changes

🧽  Update TestExtractRootCerts test to include multiple certificates

/okt-to-test

typos... 🤦
/ok-to-test

/approve
/lgtm


Few improvements to make it more customizeable

Description
Few more config options to make it more customizeable, without changing main.cpp. Also added mqtt last will message.
Related issues this fixes
Example entry for HASS configuration.yaml (if applicable):
Checklist:

[X] Change is tested and works on my device.
[X] Linters have been run.
[X] Code is ready for merge (You can set the title to WIP to stop merge early)

:+1: Looks good. Merged


Missing "Pods" folder

Hi,
The app won't build without the pods folder. Installing cocoapods doesn't work anymore it requires the actual pods folder. Please include if you can, thanks for your help!

Hi, @wellkunnected
We have discontinued work on the Talking Bible app. The source code was made available for organizational partners, but we will not be maintaining the project into the future. It was merely a wrapper for our recordings, which are hosted separately—without those, the app is pretty useless except as an example.
I will probably add a note to the README to that effect.


fix status of a few more tests in core-elements

@jakemac53

lgtm, these are passing now?

yeah, they seem to be failing before because of the package-root thing. Here is an example log: http://chromegw.corp.google.com/i/client.dart.packages/builders/packages-linux-core-elements/builds/356/steps/Test dartium under build/logs/stdio

cool! that explains a lot haha :)

not sure why there are still a couple left behind though :(


Add a formatting method that transforms URLs to links

For any cells containing URLs, we should have a fmt_url() method to make them navigable links. We should be careful to employ the method only on column containing URL text (though it is probably the user's responsibility to ensure this and that there are, for example, no URLs as part of a larger block of text).
We could expose options for how the links should be styled. They can be of the conventional style (with underlines and text coloring that sets it apart from other text), or, they can appear to be button-like (with a surrounding box that can be filled with a color).
URLs in data cells could be detected in two ways:

using the simple Markdown notation for URLs of the form: [label](URL)
assumes that the text is simply the URL

For the second case the URL is also used as the label but there is the option to use the label argument to modify that text.

Also include ability to format email addresses as address


iOS + Google FCM

Hi,
I tried to follow the instructions in the following link.
On android works well, but iOS does not receive the token or notifications.
The instructions in that link are still valid?

Same issue here. Notifications are allowed and the callback function isn't reached.

Also in my setup.
pushPlugin.register(iosSettings, (token) => {
   console.log('TOKEN', token);
}

The callback is never called.

Thanks for the feedback.
As far as I can see the article is valid - please note the small comment under the post. More information at this link and #122 .
I hope this helps.

The Capability is not enabled. You can enable them during the build process using the nativescript-custom-entitlements plugin.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>aps-environment</key>
	<string>development</string>
</dict>
</plist>

@nonzod  @simonox the latest version of push-plugin is not reproducing the issue and all notifications are received on iOS (use the demo with own FCM settings for testing purposes).
Closing this one but please let me know if you are still experiencing troubles with FCM on iOS.


Carrier causes main menu lags.

When creating a new world or loading an old one there is a ~30 seconds delay in response to the mouse clicks. I'm playing with 200 other mods but after removing carrier everything is back to normal.

Can you reproduce this with just Carrier? And could you record a video of the issue?

Can you reproduce this with just Carrier? And could you record a video of the issue?

Sorry, I wasn't quite active but I'm back and I still have this issue. I will record a video tomorrow.

Sorry, I wasn't quite active but I'm back and I still have this issue. I will record a video tomorrow.

I'll be closing this due to inactivity. If the issue still persists, please reopen the issue with a demonstration video and whether you can reproduce it with just carrier or not.


Change permissions of files which shouldn't be executable.

Achieved with:
find . -type f -executable ! -path ./gradlew | xargs chmod -x

Why?

If you don't that's fine - it doesn't really affect anybody, just matter of style.

I see, I see. I'll keep it as in since I didn't originally create those files, but thanks for the PR!


CPG Visualization

For now, I'm importing the cpg file to test out the visualization of it.  I'm not sure how some of the resources are meant to connect to each other since I can't seem to generate a file with them included.  Like RequestGroup, for example.  Otherwise, all I need to do is repeat the process shown in the code for the other resources, extracting the toState value from wherever they hold their references to other CPG resources.
Visit /demo/viz to see the visualization.

Testing for careplan done with this resource:
{   "resourceType": "CarePlan",   "contained": [ {     "resourceType": "MedicationRequest",     "id": "fffbe713-0073-4299-a996-cee0905a986e",     "intent": "order",     "medicationCodeableConcept": {       "coding": [ {         "system": "http://www.nlm.nih.gov/research/umls/rxnorm",         "code": "1922509",         "display": "trastuzumab"       } ],       "text": "trastuzumab"     },     "subject": {       "reference": "Patient/example"     }   }, {     "resourceType": "MedicationRequest",     "id": "9bdaa0e1-78f8-454c-bd80-4c9b7bfa8c0b",     "intent": "order",     "medicationCodeableConcept": {       "coding": [ {         "system": "http://www.nlm.nih.gov/research/umls/rxnorm",         "code": "1922509",         "display": "trastuzumab"       } ],       "text": "trastuzumab"     },     "subject": {       "reference": "Patient/example"     }   }, {     "resourceType": "MedicationRequest",     "id": "3cbd747a-a798-422f-93e1-a3b9b01d71fa",     "intent": "order",     "medicationCodeableConcept": {       "coding": [ {         "system": "http://www.nlm.nih.gov/research/umls/rxnorm",         "code": "1922509",         "display": "trastuzumab"       } ],       "text": "trastuzumab"     },     "subject": {       "reference": "Patient/example"     }   }, {     "resourceType": "RequestGroup",     "id": "6540f0c4-55e5-4011-8f68-6e15268ddfc1",     "status": "draft",     "intent": "proposal",     "action": [ {       "relatedAction": [ {         "actionId": "ChemotherapyTCHAC+TH",         "relationship": "after-end"       }, {         "actionId": "-aRb-wkFPr",         "relationship": "before-start"       } ],       "resource": {         "reference": "#fffbe713-0073-4299-a996-cee0905a986e"       }     }, {       "relatedAction": [ {         "actionId": "LQ8xNgyRt",         "relationship": "after-end"       }, {         "actionId": "R7nJd9OOYX",         "relationship": "before-start"       } ],       "resource": {         "reference": "#9bdaa0e1-78f8-454c-bd80-4c9b7bfa8c0b"       }     }, {       "relatedAction": [ {         "actionId": "ChemotherapyTHWeekly",         "relationship": "after-end"       }, {         "actionId": "EndocrineTherapy",         "relationship": "before-start"       } ],       "resource": {         "reference": "#3cbd747a-a798-422f-93e1-a3b9b01d71fa"       }     } ]   }, {     "resourceType": "CarePlan",     "id": "65037caf-dc52-4b74-8394-0bdcd141c54b",     "instantiatesCanonical": [ "90e08eef-33b1-45cc-9842-80f959e4f50e" ],     "status": "draft",     "subject": {       "reference": "Patient/example"     },     "activity": [ {       "reference": {         "reference": "#6540f0c4-55e5-4011-8f68-6e15268ddfc1"       }     } ]   }, {     "resourceType": "RequestGroup",     "id": "d86965df-57f7-4eda-9005-ae99cd103926",     "status": "draft",     "intent": "proposal",     "action": [ {       "resource": {         "reference": "#65037caf-dc52-4b74-8394-0bdcd141c54b"       }     } ]   } ],   "instantiatesCanonical": [ "4a208bf5-b534-4926-82e7-32d2a81c6b85", "90e08eef-33b1-45cc-9842-80f959e4f50e" ],   "status": "draft",   "subject": {     "reference": "Patient/example"   },   "activity": [ {     "reference": {       "reference": "#d86965df-57f7-4eda-9005-ae99cd103926"     }   } ] }

@KeeyanGhoreshi Not sure what happened in the rebase but I can't seem to get to the viz page anymore.
Some thoughts on Ben's suggestions:

I agree the original graph was tiny, that should be larger by default
CarePlans should be in now
onClick would be really nice but probably not worth the time at this stage
I think we should show all the content and not just the IDs. I think the easiest way to do that for now is just stringify&pretty-print the entire resource and put that into the graph. Apologies if that was done already and I just don't see it

The graph is bigger now and zoomable, but showing all the content looks pretty difficult to read.  Besides being huge, the JSON can't really be displayed correctly because of some unknown rules restricting the content of the label of the node.
I had to remove all {, } and " and stringify it twice to escape the other special characters to get it to function.  Adding onClick() effects also appears to be quite a bit more work based on what I've read.

Yeah { } are special characters in DOT syntax so they would have to be escaped. Possibly others too.
Then the base64'ed library CQL is going to be a mess too... Not sure what to do about that.
I don't want to spend too much more time on this so just one more suggestion, instead of JSON might a YML view of the resource look better? https://github.com/nodeca/js-yaml

I think that one super-wide node is the one with base64 CQL data.
YML might look better, but it probably won't solve the issue that the resources are super big and won't align correctly because the label doesn't support leading whitespace


docs: Delta Lake + Polars integration

Description
Add a docs page for the Delta Lake + Polars integration

@ion-elgreco - would you like to grab this one?

@MrPowers Sure! I'll write one after I've done some upstream changes in polars wrt MERGE

@ion-elgreco - awesome, sounds great.  jfyi, these integration pages are designed to be updated as interfaces evolve.  So we can write one now that explains read_delta and scan_delta and then update it with the merge section later.  No rush of course, just adding this detail!

@MrPowers makes sense, those sections I could already do, let me look at that next week :)

This was added: https://delta-io.github.io/delta-rs/integrations/delta-lake-polars/
@ion-elgreco - would you like me to keep this one open or should we close it for now?


Update docker-compose.md

wss -> ws

 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.


Question on from_str complains about lifetime when coping with generics

I would like to read from file/string in a struct with generic, however I face the lifetime error.
The minimal reproduce code:
use ron;
use serde::{Deserialize, Serialize};

pub struct BarBuilder {
}

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct Bar<T: Default> {
    bar: T,
}

impl BarBuilder {
    pub fn build<'de, T: Default + serde::de::Deserialize<'de>>(
        self,
    ) -> Bar<T>{
        let content = "Bar { bar: 1 }".to_string();
        let bar = ron::de::from_str(&content).unwrap();
        Bar { bar }
    }
}

fn main() {
    println!("Hello, world!");
}

The error msg:
$ cargo check
error[E0597]: `content` does not live long enough
  --> src\main.rs:16:37
   |
12 |     pub fn build<'de, T: Default + serde::de::Deserialize<'de>>(
   |                  --- lifetime `'de` defined here
...
16 |         let bar = ron::de::from_str(&content).unwrap();
   |                   ------------------^^^^^^^^-
   |                   |                 |
   |                   |                 borrowed value does not live long enough
   |                   argument requires that `content` is borrowed for `'de`
17 |         Bar { bar }
18 |     }
   |     - `content` dropped here while still borrowed

For more information about this error, try `rustc --explain E0597`.
error: could not compile `demo` due to previous error

My dependencies in Cargo.toml:
[dependencies]
ron = "0.8"
serde = { version = "1.0", features = ["derive"] }

The same error occurs the same with from_reader.
I wonder why this piece of code is not working in ron while there is some way to bypass in toml:
pub struct BarBuilder {
}

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct Bar<T: Default> {
    bar: T,
}

impl BarBuilder {
    pub fn build<'de, T: Default + serde::de::Deserialize<'de> + Clone>(
        self,
    ) -> Bar<T>{
        let content = "bar = 1".to_string();
        let configs: toml::value::Table = match toml::from_str(&content) {
            Ok(t) => t,
            Err(e) => {
                panic!("Error: {}", e);
            }
        };
        let configs: HashMap<String, T> = configs
            .iter()
            .map(|(k, v)| (k.to_owned(), v.to_owned().try_into().unwrap()))
            .collect();
        // let bar = toml::from_str(&content).unwrap();
        Bar { bar: configs["bar"].clone() }
    }
}

So I would like to know if there is one way for me to implement reading from ron within a genereic struct? Thank you!

I think the problem here is that while you define T: Deserialize<'de>, the &str you deserialise from has a different, shorter lifetime. You could either change the bound to T: DeserializeOwned, or if T might borrow data from the content string, pass content: &'de str to the build method itself.
The toml version seems to work because you first deserialise into their Value type and then clone that, erasing the lifetime requirement.
I hope this helps :)

@MomoLangenstein Really thank you for your suggestion! Switching to T: DeserializedOwned works.


fix: truncate long tags in annotation

What this PR does / why we need it:
Truncate tags in annotations konghq.com/tags.
Which issue this PR fixes
Fixes #778
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect significant changes

I added more tests to cover situations when there's too many tags in total.


AppleID keeps getting locked

I keep getting the "your AppleID is locked" error when using Xcodes.
I know there have been a lot of problems with AppleID recently (the great account locking of late April…) but despite that this does seem to be more common in Xcodes and has certainly been happening before the issues AppleID had at the end of April.
For reference (and searchability) the error I get in Xcodes is:
"Unable to install Xcode This Apple ID has been locked for security reasons. Visit Forgot to reset your account (https:///forgot.apple.com)."
And if I try to log in anyways I get a red warning under the login field ("This Apple ID has been locked for security reasons. Visit Forgot to reset your account (https:///forgot.apple.com).")
Is there anything Xcodes can do to mitigate these issues?
I am running Xcodes on 3 machines so I wonder (although I only launch the app when I know there is an Xcode to download) if that is causing the problem. I am unsure if Xcodes installs a persistent helper daemon (nothing in preferences implies it is).
Is it possible to switch from using my appleid and password to using "app specific" passwords?
Thanks
Screenshots attached.

Same here. Happened a few times in the last few weeks. Always when utilizing Xcodes.

Is it possible to switch from using my appleid and password to using "app specific" passwords?

I would love love love if Xcodes could not be dependent on apple passwords and use app passwords, but every time I've tried, the 2 systems don't work with each other. ie The login token I get from X doesn't work with Y.  They way that Xcodes, Fastlane (and others) have always worked is by faking out the login you do at apple.com and fragile(ly) setting tokens and header keys. AppStoreConnect has a very nice api that supports this, but can't use that same api for developer.apple.com.
Previously in the past, users were getting locked out, because Apple changed and added in a hashcash key https://github.com/XcodesOrg/XcodesApp/pull/361 . They may have well done something again, but I haven't seen anything widespread.
Hopefully all your machines @schwa @dfed  are on the latest version? Other than that, I'm not sure what else I can do to help this situation.

Yeah all my machines are on 2.1.2. The first time this happened there was this more widespread incident, and I've been getting my account lock relatively consistently when using Xcodes since. As a casual observer, it feels like Apple may have changed something here? That said, I'm far from in this world and I trust your judgement – just reporting my experience thus far.

Yeah latest version here.
Would extra logging help at least provide any insight into what's causing it?
 The lock out message is very specific - so I'm curious.

(Anecdotally other folks have mentioned this occurred to them this morning too - maybe somewhat widespread?)

In my case it doesn't say apple id is locked, it simply rejects the correct 2FA code I enter. Tried like 5 times, same error: "The code that was entered is incorrect"
macOS 14.5 (23F79), M2; Xcodes 2.1.2(26)

And this morning everything locked again - while rest of account on Mac is just fine.
Are there logs I can check to see what the responses are from Apple?

I haven't seen this in a bit – might have been a blip?

I haven't seen this in a bit – might have been a blip?

For me, It's still an issue, cannot log in.

After trying to log in to the App Store Connect, I've got the same message, and had to unlock the account from my device.

And again today…

It locked my account again today -
Can this work with app-specific passwords ?

Same issue here

I haven't seen this in a long time. I moved from using my personal Apple ID with Xcodes to using my work one.

Suddenly XCodes has an error reading my Account info. Worked yesterday, but this morning...hooped!
Checked my AppleID and all is good.
Looks like XCodes did an update.

This was likely fixed by #602 in 2.4.0

At last 2.4.0 allowed me to log into apple account 🔥

Mine is working too.  Good stuff!  Thanks to Xcodes
On Mon, 28 Oct 2024 at 23:43, Alexey Naumov @.***>
wrote:

At last 2.4.0 allowed me to log into apple account 🔥
—
Reply to this email directly, view it on GitHub
https://github.com/XcodesOrg/xcodes/issues/365#issuecomment-2443339305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4Y655LAZTCQZIM4AOYJJ3Z54VBPAVCNFSM6AAAAABHNJUJTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGMZTSMZQGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


READ_SHARED_STRINGS carries previous value if t element is empty

I have an Excel file which has an empty element  (after 0120) in the shared strings

MANDT/BIC/AGFIR8046/BIC/AGFIR1510/BIC/AGFIR8041FISCPER/BIC/AGFIR8014/BIC/AGFIR8003/BIC/AGFIR8021AMOUNT035YECMEC2014201401208720120M026951M027110
When parsing the file with ZCL_EXCEL_READER_HUGE_FILE the empty value is not recognized and the value 0120 is carried on.  I then have 0120 twice in the shared strings table and cells in the worksheet which are supposed to have no value have 0120 as value.
In an own class which I inherited from ZCL_EXCEL_READER_HUGE_FILE I added an attribute
C_ELEMENT_VALUE Type=IF_SXML_NODE=>NODE_TYPE Value=F_SXML_NODE=>CO_NT_VALUE
and redefined & fixed the method READ_SHARED_STRINGS:
method read_shared_strings.
data lv_value type string .
while io_reader->node_type ne c_end_of_stream.
io_reader->next_node( ).

if io_reader->name eq `t`.
  case io_reader->node_type .

    when c_element_open .
      clear lv_value .

    when c_element_value .
      lv_value = lv_value && io_reader->value .

    when c_element_close .
      append lv_value to et_shared_strings.

  endcase .
endif.

endwhile.
endmethod.
Let me know if I can help fixing this issue. I can also provide a stripped down sample file to test the issue.

Hello Kai,
thanks for pointing out this bug and solution proposal. I could reproduce the problem with the following unit test. I will try to make the fix within the next days.
  method test_shared_string_some_empty.
    data: lo_reader type ref to if_sxml_reader,
          lt_act type stringtab,
          lt_exp type stringtab.
    lo_reader = cl_sxml_string_reader=>create( cl_abap_codepage=>convert_to(
      `<sst><si><t/></si>` &
      `<si><t>Alpha</t></si>` &
      `<si><t/></si>` &
      `<si><t>Bravo</t></si></sst>`
      ) ).
    append :
     `` to lt_exp,
     `Alpha` to lt_exp,
     ``      to lt_exp,
     `Bravo` to lt_exp.

    lt_act = out->read_shared_strings( lo_reader ).

    assert_equals( act = lt_act
                   exp = lt_exp ).

  endmethod.

lt_act contains ('','Alpha','Alpha','Bravo') which is wrong - should be ('','Alpha','','Bravo').
Regards,
Rüdiger

Fixed with
https://github.com/ivanfemia/abap2xlsx/commit/959b02aa1264308025b2aaa659a9111669dfd765
(I followed the fix you suggested).


Rollable tracked resource modifier

Currently tracked resources can't be modified with dice such as /tr -1d.  It would be nice if /tr supported all the same options as /hp and /fp.

Nice idea.  I think the only way to currently do it would be to define a variable in a script, set it based on the roll, and them modify /tr by the variable.  Doing it inline as a straight OtF would be great.


Create Commitment: Set commitment period

User Story / Job to be Done / Problem

As a user creating a new commitment, I want to customize my commitment period so that it fits into my life and goals.
As a user creating a new commitment, I want to know exactly what day/time my commitment is set to start and end so that I can schedule my activity appropriately.

Potential solution ideas

date pickers
Picking today's date to start would set the start time to now, and picking any other day would set the star time to 0:00 for that day. And end time is always 23:59 for the end date selected

"As a user creating a new commitment, I want to customize my commitment period so that it fits into my life and goals."
@ryoungblom mentioned that instead of a datepicker setting amount of days (like in the current app) might make more sense. What did you have in mine when drafting this? Because I can see the value of not letting user do some sort of math and just say "start in 2 days lasting for 5 days"

Yes, my thought was that most people think about setting goals as "I want to do X within Y number of Z"  (e.g., I want to do X within 7 number of days" or "I want to do X within 3 number of months"), as opposed to "I want to do X between Y date and Z date."
I suspect that most users will want to set a start date and then give themselves some number of days or weeks to finish, rather than setting a start date and then figuring out the end date.  Like, I think about myself, and how long it would take me to say, "ok, today is the 25th of May, so 2 weeks from now... that's 14 days... how many days are in May?  So I guess... uh..." and it would be one million times easier to just select "2 weeks."
That said—there may be the odd person who wants to have a specific date!  Maybe we have the day/week/etc selector as the default but a button to switch to a date picker?  Some people might want to set goals before, say, a birthday or a wedding or something, and we don't want to force them to do all that math converting dates, either.
@bitbeckers why can't you guys come up with a metric version of dates, where each day is 10 hours long and there are 10 days in a week and 10 weeks in a month and 10 months in a year??  C'mon.

This helped me to believe it might make more sense to think in amount of days. The population of people using commitpool for a wedding is probably way smaller than all users and in that case, just do the math. We might learn from users that they'd prefer a datepicker, but for now we could use the amount of days.

Let's go with what you guys are suggesting. It's a very cheap decision in that it'll be very easy to change if we discover its not right.

Let's go with what you guys are suggesting. It's a very cheap decision in that it'll be very easy to change if we discover its not right.

What's the suggestion?  I think that both a pure days interface and a pure days interface with the option to switch to a date picker were discusses, and there's very little technical overhead for either.... it's purely a UI decision at this point

there's very little technical overhead for either.... it's purely a UI decision at this point
exactly, so I don't think it matters much which we pick now. So let's go with the pure days interface (no calendar/date picker).

What is important is displaying the dates selected as the user changes the days.

Which can be done easily. So we're going with amount of days as input with a from-to field displaying the date range?


#85 Attach support

This PR is required after the changes in Substrate (see https://github.com/gluonhq/substrate/issues/180)

Yes, we need to do that, but it can be done once Gluon Mobile is also released, and we do a new release of this plugin.

OK, but we should log an issue or document it somewhere so we don't forget :)


First load Sync for google Contact shows only one contact

during initial load on the google data
the app correctly notified me on the right with "628 new contacts" then "500" new contacts until in reached the end of all new contacts to be imported.
The screen then selected one contact, in my case "paulina" and displayed it. The "show all" was not present at the top of the column and there was no indicator or navigation to show all contacts. Reloading the page resolved the issue.
Cannot seem to reproduce it now that my data is imported.

This is semi-expected behavior on import and might be addressed by some upcoming changes to the dashboard, but assigning Jer to take a quick look at it.

this was with the old UI. closing as that has been replaced.


Drag World/Hulk Mode Style Locomotion

Popularised in Sports Bar VR (Pool Nation VR).
The concept where you pull and drag yourself around the world with the controllers.
The concept would be to translate/rotate/scale the play area based on the position of the controllers like so:
Movement (press button on both controllers to activate)

Both Controllers move forward across the Z axis (keeping same z value within threshold)

pushes the world away
i.e. moves play area backward across the Z axis

Both Controllers move backward across the Z axis (keeping same z value within threshold)

pulls the world toward
i.e. moves play area forward across the Z axis

Both Controllers move left across the X axis  (keeping same z value within threshold and same x distance within threshold)

pulls the world to the right
i.e. moves play area right across the X axis

Both Controllers move right across the X axis  (keeping same z value within threshold and same x distance within threshold)

pulls the world to the left
i.e. moves play area left across the X axis

Rotation (press button on both controllers to activate)

Left Controller moves forward on the Z axis, Right Controller moves backward on the Z axis

rotates world to the right
i.e. rotates play area through Y axis to the right (positive rotation).

Right Controller moves forward on the Z axis, LeftController moves backward on the Z axis

rotates world to the left
i.e. rotates play area through Y axis to the left (negative rotation).

Scale (press button on both controllers to activate)

Left Controller moves left on the X axis, Right Controller moves right on the X axis.

Makes world smaller/player bigger
i.e. scales the play area upward (positive scale up)

Left Controller moves right on the X axis, Right Controller moves left on the X axis (until meet in the middle)

Makes world bigger/player smaller
i.e. scales the play area downward (negative scale down)

PR https://github.com/thestonefox/VRTK/pull/1583


bug(md-dialog-actions): It's not at the bottom of the dialog

Bug, feature request, or proposal:
Bug, I think.
What is the expected behavior?
The action buttons to be always at the bottom of the dialog
What is the current behavior?
If you set the height of the dialog, the action buttons stay at the end of the dialog content, instead of at the bottom of the dialog.
What are the steps to reproduce?
Plunker: http://plnkr.co/edit/N1eZhf?p=preview

What is the use-case or motivation for changing an existing behavior?
Follow material design specifications, if I get them right.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Tried it with Material beta.7 and with the latest build (in plunker), using Chrome.
Is there anything else we should know?

Looks like a dupe of https://github.com/angular/material2/issues/4609

Yes, it is. Closing it.


3D-printed case

Could someone share pictures of a 3D-printed case?
I need them for Wife Approval Factor.

Here you go. It is about 21 mm height.

Round holes are mounting points if you want to place your reader in example on the wall. Sure, you can close all the bottom.


response.getHeader("Retry-After") This is not the rate limit return parameter for the v1.1 and v2 interfaces

This is the correct return parameter ↓↓↓↓↓↓↓↓↓↓

Hey, could you submit a pull request with the fix and the associated test ?

Created PR

fixed


fix upload problem

fixup a upload problem

@evanplaice

I've merged this in for now but it would be a good idea to run the test runner to verify functionality.
I vaguely remember adding the creation of multiple sync instances to enable multiple concurrent uploads.
There are also 2 changes in this commit:

The instantiation being commented out
The addition of a newline at the EOF

In the future, try to limit modifications to one change per commit (no matter how minor). Changes should be easy to review from the commit log.

OK , I see


Incorrect data display on the data grid when large data display

Type: Bug
I have a column where I store the message data from Whatsapp in json format. Json length is around 4500 characters. When I query the table in the datagrid in Azure data studio, this column and subsequent columns appear incorrect. When I copy, it copies the correct data to the clipboard, but the display on the grid is incorrect. After navigating between tabs it shows correctly.
Incorrect Display :

Correct Display :

Azure Data Studio version: azuredatastudio 1.46.1 (ba29842b81dec01177415e53948ca2168e69c3f8, 2023-10-02T18:14:22.887Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled
Modes:

@cengiz
Could you please gather logs for the event when you query and incorrect data is loaded?

I also noticed this issue today. I did a simple query to pull a single table row from the database, then as I scrolled through, I noticed that some fields contained HTML where that is not allowed, then realized it was repeating the same data.
But when I select those fields directly, it comes up with the correct data, even when I run the two queries together:

This is a really bad bug that makes ADS nearly unusable. I don't know if I can trust what I see when I use ADS anymore. I can't spend all day double checking if ADS is showing me correct data or decided to lie to me again.
Here is my version info:
Version: 1.46.1
Commit: ba29842b81dec01177415e53948ca2168e69c3f8
Date: 2023-10-02T18:15:27.480Z
VS Code: 1.79.2
Electron: 22.3.25
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0

My coworker is not experiencing this issue and he's on version 1.46.0, so maybe that might help you find the problem?
I followed the instructions you have to @cengiz above, and have attached my console.log and application logs.
console.log
20231106T074836.zip
I looked though the logs and didn't see any sensitive info, but there's a lot of little files in there...
Also important: after restarting the app, the incorrect display of data didn't happen every time as before, but only happened when I only did the single select * statement. So it definitely happened, just not every time (which is why you'll see multiple runs of the same queries in the log).

Hello, I haven't experienced this issue again. I tried again under the same conditions and viewed it without any problems.
That's why I didn't get back to you. The issue might have been resolved.
Thank you for your interest

Closing since it hasn't been encountered again. Please reopen if it happens again and can be reproduced :)


is it possible to playing the specific frame?

I wan to create a function to playing the video as GIFs.
For example, the length of the video is 2 second (fixed). The frame rate is 12/s. Total frame is 24.
When i clicked the button, the scalableVideoView will show no.10 frame.

@waikchiu5
Sorry for late response.
Unfortunately this library does not have its functionality.
Android 6.0 added PlaybackParams for MediaPlayer, so u may be able to use it.


Fillers with different sizes

I don't know if this is the right place to post, i'm new to github!
This script is amazing, but i have a suggestion that i think would be nice. Is there a way or plans to have the option to add fillers with different sizes to the grid? Thanks

hi @Nmaster88 since fillers are used as just that they only size to fill in the gaps - your primary content should get sized how you want using the promoted options with the sizing array.

Ok so that means they will always 1 by 1 in the grid. I was just thinking it would be cool because the content is always reorganized to the left and fillers fill the gaps in the right.

Unfortunately this is how mason works. It needs things to fill the gaps and those gaps are calculated to be a 1x1 based on the ratio.


ImportError: cannot import name 'resourcemanager' from 'google.cloud' (unknown location)

When I tried to run "intro_palm_api.ipynb" with colab, import vertexai failed with following error:
pip install google-cloud-resource-manager did not improve the error, too.
How can we resolve this issue?

ImportError                               Traceback (most recent call last)
 in <cell line: 1>()
----> 1 import vertexai
2
3 PROJECT_ID = "[your-project-id]"  # @param {type:"string"}
4 vertexai.init(project=PROJECT_ID, location="us-central1")
8 frames
/usr/local/lib/python3.10/dist-packages/google/cloud/aiplatform/utils/resource_manager_utils.py in
20
21 from google.auth import credentials as auth_credentials
---> 22 from google.cloud import resourcemanager
23
24 from google.cloud.aiplatform import initializer
ImportError: cannot import name 'resourcemanager' from 'google.cloud' (unknown location)

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.

!pip install google-cloud-aiplatform --upgrade "shapely<2.0.0"
resolved the problem.


release-4.13: GDCM CMP0042 warning

As described on Discourse,
CMake Warning (dev):
  Policy CMP0042 is not set: MACOSX_RPATH is enabled by default.  Run "cmake
  --help-policy CMP0042" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  MACOSX_RPATH is not specified for the following targets:

   gdcmcharls
   gdcmjpeg12
   gdcmjpeg16
   gdcmjpeg8
   gdcmsocketxx
   gdcmuuid

This warning is for project developers.  Use -Wno-dev to suppress it.
-- Generating done

@blowekamp is working on an update to GDCM -- if this does not address the issue, we should set the CMake policy as required.

resolved in GDCM with malaterre/GDCM#83 then in ITK by #485


Update zio, zio-test, zio-test-sbt to 2.1.13

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #3052.


Spell check with SimpleMDE

Since SimpleMDE it looks like there will be no option to use browser based spell check: https://github.com/codemirror/CodeMirror/issues/1017
So... how can I enable the built in one? Is this hard coded atm? Do we need dictionary support or options in the Gitea settings somewhere? Or have I already missed it?
Looks like its still in development upstream? https://github.com/sparksuite/codemirror-spell-checker/issues/16

My upstream link there may have been a bit misleading... even though full config and multi language is still in dev, I think the spell checker for a single language should work just fine? Its listed first on SimpleMDE features!
I see it's been manually disabled in https://github.com/go-gitea/gitea/blob/e88d67b774ae615208b25133c299f2d50b3a018b/web_src/js/index.js#L1439 and 2 other places in that file. Was this due to issues with it? I'll try compiling with it enabled at some point unless someone can shed some light on it?
My speeling is terible and I reely nead this funshonality ;)

Fixed by #19776

#19776

This feature has been deployed on try.gitea.io, feel free to test it and report bugs.


how about "TODO: print error message"?

Hi,
run infer in android project (gradle or ant) get the following message.
jigangdeiMac:adblockui jigang$ infer -- ant debug
TODO: print error message
TODO: print error message
TODO: print error message
TODO: print error message
TODO: print error message
TODO: print error message
There was nothing to analyze, exiting
Can you tell me the cause of this result?

This has been fixed in the 0.1.1 release of Infer as well as in the source code. Please re-open the issue if you see this in the new release.