Potentially incorrect parsing for u-photo

Describe the bug
Hi Aimee, thanks for this wonderful library! I'm using it in an IndieWeb Micropub client I'm working on. I may have found a potentially incorrect parsing.
The documentaton for img parsing can be found on the wiki: microformats2 parsing - parsing a u-* property and a more detailed explanation specifically for an img element
To Reproduce
For the h-entry on my staging site, given the following HTML:
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAYAAABWdVznAAACBUlEQVR4AU3Bz0uTcRwH8Pfn+zzP5rPaFszNbc4S3UzEViMqguhkskOHrEt0WZdOdhOCIJA8hn9AeYhOGjuMQrNDyohIkn4cIqRpkLXNbT6b85n7/fg8356Bh14vwn/GR/ttbbJOHxo0AZPIeEIiPvPu+2YdRwQcmTgboIohL+qcYgBcROTSOa7ooMhFn21+o6CiQ4DpWeKTqP1pPs/ubd+CKdTXjdvjESj7NZQPGqFzg9f77z16svQq8YIzmPj8+5l8djPGRQmjpwO4emkYGmM4f6YfXJJAJfVu8/X6Y5ho9v6c2/4rm95St6xjd3rgdXahoDbBGMFttyK338DqgoKQM9isR4J9opwrXYPBrYbBkcnuwiEHcMrjgG5wqLUW8vkiDN0ADN4lpdJjjDXavTA5JDs2vh4g1OvCdq6IdGEPIb8LPz4fwCN70MHaekCkY7ICtQqfzQsPeRFfKuNG1I+O+JsyBlkYgpXQIcgWhekDvSsg0g0C1qQCFpUdWCQRFknEorKDNXEXBgFgdKgHA6vC8sdEJRqJepMsc+Evr0C2HUe6VMP67wryNUKupaJo0XCyq/vp5NzkSwbTirs6VbTob5kgIjwyhGSqjGSqjPDIEJggQpG05aS/NQWTANPPLx8OL9+MLWjNesbncXszO/luItIdzhPfqm1jumdg+EF89qEG0z/TU9ArSzunAgAAAABJRU5ErkJggg==" alt="Ru's avatar" class="u-photo mx-auto w-auto h-full lazyload" loading="lazy" data-src="/assets/img/authors/rusingh.png" width="250" height="250">

...the parser seems to output:
photo: [
  {
    type: [ 'h-full' ],
    properties: {
      name: [ "Ru's avatar" ],
      photo: [
      {
        alt: "Ru's avatar",
        value: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAYAAABWdVznAAACBUlEQVR4AU3Bz0uTcRwH8Pfn+zzP5rPaFszNbc4S3UzEViMqguhkskOHrEt0WZdOdhOCIJA8hn9AeYhOGjuMQrNDyohIkn4cIqRpkLXNbT6b85n7/fg8356Bh14vwn/GR/ttbbJOHxo0AZPIeEIiPvPu+2YdRwQcmTgboIohL+qcYgBcROTSOa7ooMhFn21+o6CiQ4DpWeKTqP1pPs/ubd+CKdTXjdvjESj7NZQPGqFzg9f77z16svQq8YIzmPj8+5l8djPGRQmjpwO4emkYGmM4f6YfXJJAJfVu8/X6Y5ho9v6c2/4rm95St6xjd3rgdXahoDbBGMFttyK338DqgoKQM9isR4J9opwrXYPBrYbBkcnuwiEHcMrjgG5wqLUW8vkiDN0ADN4lpdJjjDXavTA5JDs2vh4g1OvCdq6IdGEPIb8LPz4fwCN70MHaekCkY7ICtQqfzQsPeRFfKuNG1I+O+JsyBlkYgpXQIcgWhekDvSsg0g0C1qQCFpUdWCQRFknEorKDNXEXBgFgdKgHA6vC8sdEJRqJepMsc+Evr0C2HUe6VMP67wryNUKupaJo0XCyq/vp5NzkSwbTirs6VbTob5kgIjwyhGSqjGSqjPDIEJggQpG05aS/NQWTANPPLx8OL9+MLWjNesbncXszO/luItIdzhPfqm1jumdg+EF89qEG0z/TU9ArSzunAgAAAABJRU5ErkJggg=='
        }
      ]
    },
    value: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAYAAABWdVznAAACBUlEQVR4AU3Bz0uTcRwH8Pfn+zzP5rPaFszNbc4S3UzEViMqguhkskOHrEt0WZdOdhOCIJA8hn9AeYhOGjuMQrNDyohIkn4cIqRpkLXNbT6b85n7/fg8356Bh14vwn/GR/ttbbJOHxo0AZPIeEIiPvPu+2YdRwQcmTgboIohL+qcYgBcROTSOa7ooMhFn21+o6CiQ4DpWeKTqP1pPs/ubd+CKdTXjdvjESj7NZQPGqFzg9f77z16svQq8YIzmPj8+5l8djPGRQmjpwO4emkYGmM4f6YfXJJAJfVu8/X6Y5ho9v6c2/4rm95St6xjd3rgdXahoDbBGMFttyK338DqgoKQM9isR4J9opwrXYPBrYbBkcnuwiEHcMrjgG5wqLUW8vkiDN0ADN4lpdJjjDXavTA5JDs2vh4g1OvCdq6IdGEPIb8LPz4fwCN70MHaekCkY7ICtQqfzQsPeRFfKuNG1I+O+JsyBlkYgpXQIcgWhekDvSsg0g0C1qQCFpUdWCQRFknEorKDNXEXBgFgdKgHA6vC8sdEJRqJepMsc+Evr0C2HUe6VMP67wryNUKupaJo0XCyq/vp5NzkSwbTirs6VbTob5kgIjwyhGSqjGSqjPDIEJggQpG05aS/NQWTANPPLx8OL9+MLWjNesbncXszO/luItIdzhPfqm1jumdg+EF89qEG0z/TU9ArSzunAgAAAABJRU5ErkJggg=='
  }
],

Expected behavior
Correct JSON output:
photo: [
  {
    alt: "Ru's avatar",
    value: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAMCAYAAABWdVznAAACBUlEQVR4AU3Bz0uTcRwH8Pfn+zzP5rPaFszNbc4S3UzEViMqguhkskOHrEt0WZdOdhOCIJA8hn9AeYhOGjuMQrNDyohIkn4cIqRpkLXNbT6b85n7/fg8356Bh14vwn/GR/ttbbJOHxo0AZPIeEIiPvPu+2YdRwQcmTgboIohL+qcYgBcROTSOa7ooMhFn21+o6CiQ4DpWeKTqP1pPs/ubd+CKdTXjdvjESj7NZQPGqFzg9f77z16svQq8YIzmPj8+5l8djPGRQmjpwO4emkYGmM4f6YfXJJAJfVu8/X6Y5ho9v6c2/4rm95St6xjd3rgdXahoDbBGMFttyK338DqgoKQM9isR4J9opwrXYPBrYbBkcnuwiEHcMrjgG5wqLUW8vkiDN0ADN4lpdJjjDXavTA5JDs2vh4g1OvCdq6IdGEPIb8LPz4fwCN70MHaekCkY7ICtQqfzQsPeRFfKuNG1I+O+JsyBlkYgpXQIcgWhekDvSsg0g0C1qQCFpUdWCQRFknEorKDNXEXBgFgdKgHA6vC8sdEJRqJepMsc+Evr0C2HUe6VMP67wryNUKupaJo0XCyq/vp5NzkSwbTirs6VbTob5kgIjwyhGSqjGSqjPDIEJggQpG05aS/NQWTANPPLx8OL9+MLWjNesbncXszO/luItIdzhPfqm1jumdg+EF89qEG0z/TU9ArSzunAgAAAABJRU5ErkJggg=='
  }
],

Additional context
The type definitions appear to be correct:
export declare type MicroformatProperties = Record<string, MicroformatProperty[]>;
export declare type MicroformatProperty = MicroformatRoot | Image | Html | string;
export interface Image {
    alt: string;
    value?: string;
}

However, when accessing the first index in the photo (MicroformatProperty[]) array, TypeScript complains it cannot find value on the type string:
photo[0].value
        ^^^^^^
Property 'value' does not exist on type 'MicroformatProperty'.
  Property 'value' does not exist on type 'string'.ts(2339)

Hi @hirusi thanks for creating the issue.
I've investigated how your site parses with other parsers - both PHP and Python.
THe PHP parser doesn't look to parse your photo property: https://php.microformats.io/?url=https%3A%2F%2Fweb-git-indiekit.hirusi.vercel.app%2F
Whereas the Python parser does:https://python.microformats.io/?url=https%3A%2F%2Fweb-git-indiekit.hirusi.vercel.app%2F
The Python parser shows the same behaviour (but without parsing the image's alt tag)
I believe you are expecting the parser to not parse the h-full class you have attached to your image? Is this correct? The parsers will interpret any h-* classname as a root microformat.
For the TypeScript error, you'll need to implement a Type Guard

Sorry @hirusi I accidentally closed the issue 🤦♀

@aimee-gm My apologies. I just realized that h-full was getting parsed as an h-* property. I am using TailwindCSS and it's a class that it comes with. Didn't click to me that this is what could be causing the error - I was too focused on u-photo. 😅
I have tested a fix on my staging site and it seems to work well now. Neither the PHP nor the Python parser pick up the alt information anymore - but that's an issue for me to deal with elsewhere. 🙂


Feature Request: Save draft

Another useful feature for Quick Capture would be to save a draft in localStorage every x seconds.
And load from localStorage when you quit the app without sending it.

I would pick 5 seconds as it's around the time one thought that you put into words.

I would also overwrite the old draft when saving a new.
And show a "Draft" notification (same as "Edit" and "Saved").

Decision to not implement.
After nearly 3 months of usage, I never ran into a case where I wish I had "save draft".
As long as the window is open, the current text is saved.
I could add to docs that you have to submit before closing or your text is lost.

Save and update text from textarea every 5s
Use LocalStorage, just have one key/value and reuse
Update status to "Draft" in the same way that "Saved" is used (i.e. show for some seconds)
When starting the app, check for content from LocalStorage and prefill
If textarea is empty, make text in LocalStorage empty as well

For testing it:
Write something, wait for 5s, quit without saving, open again. Assertion: Text shows up again and can be saved

This approach worked but did not feel snappy for the user as they have to wait for x seconds.
Instead, I now went for "Save on 500ms pause", so when the user stops writing for 500ms, the update will happen.

For testing it:

Case 1: Write something, pause writing, quit without saving, open again. Assertion: Text shows up again and can be saved
Case 2: Write something, pause writing, delete text, pause, quite, open again. Assertion: No text shows up

Both cases work, but the constant status update is annoying.
I decided to remove this status as saving draft is now an instant thing.

Closing as the issue is solved, just the binaries are not created yet.


Segfault when connecting to MacOS host with SSL

As the title mentions, here is the output of the command, please let me know if there is further information I should provide.
Thank you!
$ waynergy --host <IP_ADDRESS> --enable-crypto
wl-clipboard 2.0.0
Copyright (C) 2019 Sergey Bugaev
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
wl-clipboard 2.0.0
Copyright (C) 2019 Sergey Bugaev
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
0.000000109: [WARN] Could not kill lingering wlpaste instances: -1

0.019515004: [ERROR] No certificate hash available
Segmentation fault (core dumped)

I was able to get it working passing in a name and also --enable-tofu, however my keys are completely wrong on the client (Arch Linux).


Slider tooltip not showing/buggy behaviour on mobile

The slider doesnt show any tooltip. Sometime it does work tho, but with buggy behaviour. Spam clicking works on real mobile while in browser it rarely does.
The range slider works better than the others but still buggy. This behaviour has also been tested on another android device from a friend who tried my app, no tooltips as well.
Happens only on mobile, desktop works fine.
Tested browsers: Google chrome (Desktop), Chrome (Mobile), Vivaldi(Desktop) and Samsung Browser(Mobile)
Mobile device: Samsung Galaxy S24
sliders-2024-05-11_23.01.22.webm
EDIT: Firefox on desktop in mobile mode seems to work just fine, mobile still a bit buggy only when trying to move the pointer element

Done in https://github.com/beercss/beercss/releases/tag/v3.5.6 and feel free to reopen this issue.


Update the readme

migrate over the old readme
add license
add contribution guidelines

The readme will need a follow-on update once the rest of the code-base is in place. There are some remaining things that can't be done before then (i.e. badges, etc).
This PR provides the bulk of the effort and covers as much as can be done at the current time.

FYI, @kcpevey Nebari can be used with Github-Actions OR Gitlab's version (I think they are called Gitlab Runners)


[WFLY-19768] MicroProfile Reactive Streams Operators 3.0.1

https://issues.redhat.com/browse/WFLY-19768

Thanks @kabir


Used postgres version

Hello!
I am trying to convert the database to SQLite to get a better understanding on how it works and to try to embed it. What Postgres version do you use exactly?

Yeah, the locale name can be completely different. I imported the pg dump into Windows based postgres where the locale is called something else. The important thing is to create the database with the locale that is supported by your system, and then pg_restore into it. The locale name stored in the dump shouldn't matter.

Oh, I didn't know that! I'll try that out later on! Thanks for the help!


Question: Support for 4 button -P01 Pico?

Describe Your Problem:
I'm interested in knowing if the current 4 button support in the plugin also supports the 4 button PJ2-4B-GWH-P01 'scene' Pico, which is natively supported by Caseta AFAICT. I'm interested in picking one up but would only want to use it through HK to control groups of both Lutron and non-Lutron devices. I've gathered from #26 that some form of the 4 buttons is currently supported by the plugin, and in #33 that the scene flavored 4 button -P01 might also be supported. However, the readme does state only the -L01 4 button pico currently supported. I'm curious what the current state is? If the readme is outdated, I'm happy to file an update to it if there's a full list of supported picos for the plugin.
If useful, it seem Lutron now have a KB article on which Picos are fully supported within the Caseta system.
Thanks, and appreciate your work on unlocking these capabilities for the community! 🙌
Logs:
N/A
Plugin Config:
N/A
Screenshots:
N/A
Environment:
N/A

hmmm I'm honestly not sure. the way the Picos identify themselves to the hub is not necessarily congruent to how Lutron markets them, so it very well might Just Work. if you have one, can you give it a try and see how it appears in the startup log?

I don't have one at the moment, but was about to pull the trigger on it anyway to give it a try. Happy to provide logs and debug info if that's enough to get things going. Worst case - would you be up for me shipping the remote to you if you need it physically? I'm in the Bay Area so shipping would be pretty fast I think.
Let me know if you'd prefer to keep this issue open, or I can open a new issue once I try it and get some logs. Thanks!

debug logs should be enough to add support if it's needed, plus maybe a bit of guesswork. let's keep this open so long as the feature request is "live" :)

Looks like the remote 'just works'! Was able to confirm single, double, and long press customization behavior. No setup or configuration necessary. Here's the device entry on startup:
    {
      Name: 'Keypad',
      DeviceType: 'Pico4ButtonScene',
      AssociatedArea: { href: '/area/2' },
      href: '/device/56',
      SerialNumber: 93292965,
      FullyQualifiedName: [ 'Family Room', 'Keypad' ],
      Parent: { href: '/project' },
      ModelNumber: 'PJ2-4B-GXX-P01',
      ButtonGroups: [ { href: '/buttongroup/16' } ],
      EngravingKit: 'LivingRoom',
      LinkNodes: [ { href: '/device/56/linknode/55' } ],
      DeviceRules: [ { href: '/devicerule/82' } ],
      AddressedState: 'Addressed',
      AssociatedLink: { href: '/link/1' }
    }

Anything else you'd like me to pull/capture from the logs to confirm?

Great news! I’d love a doc update PR if you could be convinced :)

PR opened. I'll close out this issue, thanks!


Dark Mode not controllable

Hello,
first of all great project but I got 1 small problem.
I want to have  a  theme toggle but since you have "darkMode": "media" in your tailwind.config.js this isn't posible.
I wanted to ask if u could mby change it to some kind of env variable, since u obvioulsy can't access any kind of other app state and it won't make that much of a difference but for someone like me it would definitily help

I can unfortunately only choose between auto dark mode or manual dark mode, so I will settle for auto dark mode for now.

@albingroen Is there a way to override it or pass the mode. As I am not using tailwindcss. I am using mui and there is toggleSwitch for switching between dark and light mode. Light mode looks fine but dark mode doesn't  work.
Thanks.


How to handle rotation

I am wondering how to best handle device rotation with the Panoramic View.
At the moment, I am able to adjust the frames of the scrollView and imageView after a rotation and also adjusted the gyro methods so that the x-axis is used when the device is used in landscape and y-axis when in portrait.
What I do have problems with however, is the PanaromicIndicator? Is there a good way to have that moved and resized when the device is rotated?

want my app to be able to show/hide the indicator based on a tap on the image (as a toggle). If I have the scroll indicator enabled in the view and then disable it, it hides, but then enabling it again, the app crashes.
As this is likely related to the rotation issue, I am adding it in this issue thread.


Unresolvable dependencies in the POM

Hi,
I'd really like to try this out in a new project but there are some custom dependencies in the POM (snapshot and also a custom version of the graphql library) that I don't have access to.
    <dependency>
        <groupId>io.leangen.geantyref</groupId>
        <artifactId>geantyref</artifactId>
        <version>1.1.1-SNAPSHOT</version>
    </dependency>
    <dependency>
        <groupId>com.graphql-java</groupId>
        <artifactId>graphql-java</artifactId>
        <version>LEANGEN</version>
    </dependency>

Would it be possible to resolve those or offer a published binary? :0)
Many thanks!
Adam

Hi TiGz,
We're glad that you're interested in giving SPQR a go.
This is still not a release so we didn't switch to maintaining stable dependencies only yet. Probably in the next month when we release we'll switch to maintaining a stable master for releases.
As for the dependencies it should be safe to use released:

io.leangen.geantyref
geantyref
1.1.1

which is on the central now.
But the graphql-java fork artifact is still not published anywhere, fastest solution would be to build it yourself and install it in your local repo, and we were also planing to put it on bintray in the next couple of days, maven central is a bit more complicated matter.
Hope this helps for now and we'll try to keep you updated.
Maybe Bojan (kaqqao) has more to add tomorrow.
Cheers,
Milos

This project is no longer depending on the forked version of graphql-java so the build issue should be solved. Currently, it depends on their nightly because we need some of the unreleased fixes. Once the next stable version of graphql-java is released, we will finally stabilize the dependencies.
@TiGz Can you confirm the build is now working for you?


[BUG] tag

ver 4.2.1
Bug that occurs to the person who joined the team.
no overhead team name tag when player sign up.
The overhead tag is not working.
reconnect to the server to get a tag
or
the reload command to get the overhead tag.

This is caused by conflicts with other plugins, not just betterteams by itself. What is your scoreboard manager plugin?

This issue is being closed for inactivity. If you are still having problems feel free to open a new issue linking this one, make sure you answer any questions asked in the new issue.


Minema crashes when I try to record : Can't Export Frame 2

Hi, I use Minema v3.6.2-TickSync but when I try to record it crashes
FFmpeg version is: 5.0 full_build
When I try to record with minema it tells me the following error:
java.util.concurrent.ExecutionException
java.lang.RuntimeException: Can't export frame 2
Cause:
java.io.IOException
Invalid attempt to access the memory address
See log for full stacktrace
This is the log:
https://pastebin.com/UEZEeBDe
Please, help me.

I tried help someone with the same problem, but I had no luck with it. Any additional information would be nice like the operating system and its version.

@mchorse Windows 10.

Anything else?

Anything else?

I have no idea, however, try creating a clean installation of modded Minecraft in a new game directory. Copy over mods there, and setup ffmpeg again. The person who had the same issue seems to have this fixed after creating a clean installation.

Recommend the ffmpeg version?

@mchorse Hi, the problem has been solved, but after recording the video through Minema, the video will come out accelerated, how can I remove it?

@mchorse Hi, the problem has been solved, but after recording the video through Minema, the video will come out accelerated, how can I remove it?

Try enabling limit frame rate option in Mod options > Minema > Capturing.

@mchorse
But when I turn on the limit, I get the same error "Can't Export Frame 2"

same thing happened with me except it said frame three?

still have the error

Clearing the Movies directory fixed it for me.


placeholder and React event bug fixes

@browniefed I made these changes based on your suggestions in #29 and #30
Now your test passes. Let me know if you have any thoughts on this!

I'll take a look later tonight when I'm back on my computer

Reviewed on my phone, small enough changes. Looks good

Thank you Jason. Really appreciate it!


Unable to increase the exipry time of aws keys to 12 hours.

Hi There,
I was informed that aws keys will expire after 12 hours of creation. I tried different options: 1. use default value, 2. add "aws_default_duration = 43200" in .okta_aws_login_config.
My aws keys are expiring every hour. Can you please help me what configuration do I have to change to make sure keys are active for 12 hours from the time of creation.
Thanks,
Gaurav

You also need to change the MaxSessionDuration for each role you want to access.  If the value you've selected for aws_default_duration is greater than the session duration for the current role, gimme-aws-creds will display a warning and fallback to 3600 seconds.  There's more info on extended session expiration here.

Hi Eric,
I already set Maximum CLI/API session duration to 12 hours (43,200 seconds) for the role and after that I set aws_default_duration to 43200 in my local. But my keys are still expiring after an hour.

Hi Eric,
Every role is set up for 12hours session.


escape does not work when way is self-intersecting

When adding nodes to a way, you can hit escape to stop a click from adding a new node to the way. When you are making a self-intersecting way, you can't create a new node. You can then hit escape to avoid messing things up. However, in some cases this does not work. I've tested in Chrome and Firefox, and have this little issue only if it's a highway=residential.

@joostschouppe Can you give more detail about this or a screencapture? I'm not sure what the exact issue is or how to reproduce it. What is escape supposed to be doing that it's not doing?

I have tried to reproduce, and it seems to have gone away already

@joostschouppe Great!

I can still reproduce this..

It probably will happen whenever that the line you are drawing causes the self-intersection.

@bhousel So when you connect to the endpoint and make a self-intersection and then press escape it doesn't exit the draw mode? Still cannot reproduce in Firefox or Chrome…


Adds support for Realm DB to the monkeycache project

This solution includes all of the components needed to use the MonkeyCache solution with a RealmDB backend. This has been tested on iOS, Android and Windows via unit tests.

No plans to add another package on here. Thanks for the PR though.


[FEATURE] onboard customer's bank details using /payment_methods CREATE

Feature Description
Add capability to onboard customers and their bank details prior to making a txn.
Current State
Only card payment method can be persisted using /payment_methods endpoint. A txn has to be completed for persisting bank details.
Use case
Use payment_tokens for initiating a bank txn.
Possible Implementation
Add capability in /payment_methods CREATE API to persist bank details.
Have you spent some time checking if this feature request has been raised before?

[X] I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to submit a PR?
Yes, I am willing to submit a PR!

This is merged and deployed in sandbox.


add ohmyzsh plugin file

hi,
i added a small script to include the z.sh when exists in ohmyzsh custom / plugin folder.

sorry i don't wan't to maintain ohmyzsh stuff in this repo.


Texture furnace / workbench

Hello, i use a texture pack in my server and the texture Furnace / workbench does not appear
Exemple screen :
No texture pack : https://image.noelshack.com/fichiers/2019/05/6/1549113550-2019-02-02-14-18-25.png
Texture pack : https://image.noelshack.com/fichiers/2019/05/6/1549113786-2019-02-02-14-23-00.png
Same FastWorkbench
thanks

Are you using LiteLoader?

Yes same problem

Yeah the bug is caused by liteloader, and liteloader appears to be out of active development.

Even without the problem appears


Add() a single file is very slow

Worktree.Add(file) calls Status(), which goes over the entire worktree. In addition, Add() takes a single file.
So adding multiple files in a large repo therefore becomes an O(N2) operation (excruciatingly slow).

This is crushing me as well.  I have a repo with thousands of files.  I've done a lot of work to make my workflow entirely in memory, using libasciidoc to get really fast document processing, but then this Add() performance basically steals back all the gains I achieved.

Hey, we encountered that issue as well in Kubernetes release engineering. We're trying to add a single file to kubernetes/kubernetes which takes round about 5 minutes to succeed. Do you have any idea how to overcome this obstalce?


[State Sync] Add a new Storage Service implementation (server-side)

Motivation
This PR adds a new server-side implementation for the Storage Service. The Storage Service is an inter-node service allowing Diem nodes to request storage data (e.g., transactions and proofs) directly from other nodes over the Diem network. This PR sets up the framework (template) for this service by implementing the plumbing between request/response processing from the server-side, as well as outlines the required interface between the server and local Diem DB.
To achieve this, the PR offers 2 commits:

Add the new server implementation (as a library to later be exposed over the network)
Add several (simple) tests for the server implementation. These will need to be improved and expanded in the future.

Notes:

The implementation offered here is by no means complete (and you'll notice many TODOs). Instead, this PR is meant to set up the framework so that we can start building on the server-side implementation and make the Storage Service a living thing 😄

Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
A set of simple unit tests have been added for this functionality.
Related PRs
None, but this PR relates to: https://github.com/diem/diem/issues/8906

Thanks, all! 😄
/land


Help wanted

We could use some help with issues in related modules:

[x] Support fullwidth characters: https://github.com/chalk/slice-ansi/issues/4
[x] Support for unicode surrogate pairs: https://github.com/chalk/slice-ansi/issues/5
[x] Adds moot escape codes: https://github.com/chalk/slice-ansi/issues/6
[x] Use AVA test macros in the tests: https://github.com/chalk/chalk-cli/issues/5

Many thanks to @kevva for the work on this :)

I think https://github.com/chalk/slice-ansi/pull/10 needs to land before this is truly fixed :).

Oh I just saw 'merged' and figured it was done. I think it's sufficient for this ticket though.


Test and import HMPPS Intranet snapshots

User Story
Snapshots have been shared with the long-term-storage account, we need to:

[x] copy shared snapshots to the long-term-storage-account
[x] create volumes and EC2s from the snapshots and check the data is accessible
[x] delete the EC2s and import the volumes and snapshots into terraform.

User Type(s)

Value

Questions / Assumptions / Hypothesis

Definition of done

[x] readme has been updated
[x] user docs have been updated
[x] another team member has reviewed
[x] tests are green

Reference
How to write good user stories

https://github.com/ministryofjustice/modernisation-platform-environments/pull/1294
https://github.com/ministryofjustice/modernisation-platform-environments/pull/1286
https://github.com/ministryofjustice/modernisation-platform-environments/pull/1282
Code here - https://github.com/ministryofjustice/modernisation-platform-environments/blob/main/terraform/environments/long-term-storage/hmpps-intranet.tf


[BUG] link to version 1.3 is showing 2.0.0 documentation.

What is the bug?
The 1.3.x docs  page https://opensearch.org/docs/1.3/security-plugin/configuration/security-admin/ is showing the below config which is 2.0.0 specific configuration and does not work on 1.3.x.
./securityadmin.sh -f ../../../config/opensearch-security/internal_users.yml
-t internalusers
-icl
-nhnv
-cacert ../../../config/root-ca.pem
-cert ../../../config/kirk.pem
-key ../../../config/kirk-key.pem
How can one reproduce the bug?
Steps to reproduce the behavior.

Hi @peterzhuamazon - Can you please tell me if this is still an issue and how we can fix it? Here is the page: https://opensearch.org/docs/1.3/security/configuration/security-admin/.

@scrawfor99 - what is the correct script to add here?

Hi @hdhalter,
The security admin script is supported for all version of OpenSearch so this should be fine. @neuralsearch-opensearch could you provide the error you are encountering so that I can try to take a look at reproducing your issue or debugging the problem?
Thank you!

Closing this issue since we cannot reproduce it.


Allow passing boto3 session directly to MSKAuthTokenProvider.generate_auth_token_from ...

aws-msk-iam-sasl-signer-python version: 1.0.0
Python version: 3.11
Operating System: Linux
Method of installation: pip
Kafka library name: n/a
Kafka library version: n/a

Description
We have a lot of code that passes a boto3 session around. Underneath this session is credentials that are either auto-refreshing, profile-based, or instance based. The instantiation of a Kafka client shouldn't need to know.
Currently, a way to make this happen is via an ugly wrapper class:
session = boto3.session.Session(...)

...

class WrappedSessionCredentialProvider(CredentialProvider):
    METHOD="wrapped"

    def __init__(self, delegate_session):
        self.delegate_session = delegate_session

    def load(self):
        return self.delegate_session.get_credentials()

credentials_provider = WrappedSessionCredentialProvider(session)

def oauth_cb(oauth_config):
    auth_token, expiry_ms = MSKAuthTokenProvider.generate_auth_token_from_credentials_provider("us-east-1", credentials_provider)
    return auth_token, expiry_ms/1000

As sessions are such a core concept in boto3, it would be nice for the MSK lib to work with them natively.

We also facing this case, we want configure Credential directly from ak sk in code. Not through environment file. Any updates?

I think this is a fair ask. @lucasmo @hengjiUSTC but I am not sure if adding this feature should deprecate the old way of passing custom credentials provider. I will seek guidance from other SDK owners in AWS and get back to you on this.
Would one of you be interested in contributing to this feature?

Working with a customer on this, the way of passing the credential provider in is very complex and we probably shouldn't ask customers to muck around botocore to accomplish this. This removes the entire magic functionality of the default credentials providers chain.
We should prioritize this as a feature for all MSK signers.

Doubly so when other MSK clients already implement the default credentials provider chain:
https://github.com/aws/aws-msk-iam-auth/tree/main


Two column style

Hello,
Thanks again for the great template! I've been using it for a while and I modified it to my taste so that it has two column format, and thus you can pack more things on a single page. Here is an example.
Would you care for a pull-request for an option to use two column style? If you prefer to make it single column only, I would understand the decision.
Cheers,
Onur

That's great! I'll consider your changes, please make your pull-request :)
Thanks for your improvement.
Best regards,
Claud D. Park

오후 4:55에 Onur Ferhat 이(가) 쓴 글:

Hello,
Thanks again for the great template! I've been using it for a while
and I modified it to my taste so that it has two column format, and
thus you can pack more things on a single page. Here
http://onurferhat.com/resume/onurferhat.pdf is an example.
Would you care for a pull-request for an option to use two column
style? If you prefer to make it single column only, I would understand
the decision.
Cheers,
Onur
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/posquit0/Awesome-CV/issues/56, or mute the thread
https://github.com/notifications/unsubscribe/ABak4kABqbXEfj2yW-eow1ZfqowHVkliks5qS1-DgaJpZM4JF1if.

Already sent the pull request (#58). As I noted there, I commented out two sections of the sample resume to make it fit a single page, you can uncomment them & generate the example outputs again if you prefer.
Thanks for the opportunity and the great project!
Onur

Hello @tiendan . Do you have the full code for your cv pdf. It is perfect for me. It has correct fonts and location icon. Thanks.

Hi @tgeorgiop,
Sorry for replying late, here you have the source code for 2 columns: https://dl.dropboxusercontent.com/u/41916970/awesome-cv_two_columns.zip
Cheers,
Onur

Hi @tiendan,
The dropbox file isn't accessible anymore. Are you able to renew the link? Best.

Hi @strboul & @timozattol
Sorry for that, I switched from Dropbox to Sync and the link was broken 😅  Here is the new link:
https://cp.sync.com/dl/51a82e2e0#6jkbi4rx-m9r9xh4c-xh8uqykm-ue56xyvj
Cheers,
Onur

It there a way to change the width of these column ?

Hi @jdcpower1994 ,
Sorry for the late reply, but here it is:
In the CV style file, you can find the page layout parts: https://github.com/posquit0/Awesome-CV/blob/master/awesome-cv.cls#L106, which should appear a little bit different in the 2-column style:
\RequirePackage[left=1.7cm, top=1.4cm, right=1.7cm, bottom=1.9cm, footskip=.5cm,twocolumn,columnsep=0.5cm]{geometry}
Here you should touch the margins and columnsep parameter to make the perfect fit for your purposes.
Cheers,
Onur

@tiendan what you've done there looks great, would you be able to provide a refreshed link for the source code? Neither one seems to be working... I've been trying to do something similar with my own resume and I've only worked with LaTeX for a couple months now, this would be exactly what I need

@tiendan The above link also seems to be broken.

One final note: as the PR is abandoned, I've forked the repo again and applied my (very dirty) updates. You can check it out here:
https://github.com/tiendan/Awesome-CV/
The changes are:

Two column style
Logo placement for experience and education sections (beware: very dirty spacing fixes)
Some other spacing changes to make it fit nicely just for my resume. You'll need to touch some parameters to make it work for your case, if you want to fit it in 1-2 pages exactly.

Cheers,
Onur


Add file-metadata.csv file

Add scalaCsv dependencies
Add checksum calculation class and tests
Add additional files class
Add a method to write the metadata to the bag.
Update existing tests and add new one.
Add method and tests to get the file metadata.
Add wiremock stub for file metadata call
Write the files to the bag in the Main class

This is only draft because the generated-graphql dependency is still a snapshot version. Once the API and generated graphql PRs are merged, I can update the version and the build should pass.

I'm going to refactor this a lot to make it use a single graphql call. I'll mark this as ready when I'm done.


Functions missing from REST api docs

http://pulsar.apache.org/en/admin-rest-api/
There's no mention of the functions endpoints.

Swagger was failing because the function endpoint was returning some protobuf. This protobuf needs to be refactored out of the API, and then swagger should work.

The docs of functions, sinks and sources are all added.

The docs of functions, sinks and sources are all added.


Proposal: Statically typed fromEvent

TLDR: I have implemented a fromEvent alternative that is type-safe and has some additional features. And I want to know if I can open a PR. :)

So, as you people might know fromEvent's types are not really great which is fair considering when they were written it wasn't possible to statically type it. But now we can have better types for fromEvent.
So in this light, I implemented rxjs-from-emitter. I recommend checking out the readme to see all it's features, but in short these are it's two major features -

Correct Observable inferences corresponding to listener's arguments.
Static checking if an event exists or not.

If this implementation is in alignment with RxJS's goals and interests, I would be more than happy to send a PR :) I have answers to all your questions. Also don't get distracted with the change in API, it's the types that are important. To put it in the perspective runtime code is ~100 LOC where as type-level code is ~600 LOC.
Also additional to the type-safety, according to me there are some (respectfully) design-level flaws of fromEvent that rxjs-from-emitter solves which I have documented here.
PS: In case this comes across a publicity stunt to promote my package or whatever, it's not. I love RxJS and I genuinely want to make it better :)
Also I will take this opportunity to thank everyone that constantly works on RxJS to make it better!

@benlesh Is this any good? 🤔😅

I think this is really cool. I'm not sure I agree with all of the design choices, but I like the spirit of it. If we did have a design we agreed on, we'd need to have a migration plan. How do we get millions of users there gracefully over a series of major releases? What does the deprecation track look like? Are there code transformations we can do? Etc. RxJS is unfortunately way too popular to make a big breaking changes to API design without careful considerations like that.

I'm so happy that you find it cool! :D And I really appreciate that you asked these questions instead of just dismissing the proposal.
I think we can at least agree upon the fact that if we want type-safety fromEvent needs to go because it's just too dynamic. I mean consider this –
Let's say we have an emitter emitter1 that is node style and the allowed events are "a" and "b" both will have observable of types Observable<number>. We also have another emitter emitter2 that is dom style and the allowed events are "b" and "c" both both will have observable of types Observable<string> and since they are dom style they also have extra options after passing the listener.
Now imagine someone wrote fromEvent([emitter1, emitter2], ...). Now the second parameter should be of type "b" only because that is common in both. It should return Observable<number | string>. And I don't know what to do about the third argument.
The point I want to make is fromEvent is quite a mess. I'm not saying it's impossible to make it type-safe it's quite possible (I haven't fully tried) but the entropy is too much. And solving the problems that I mention about fromEvent is also quite difficult without changing the API. Also Problem #1 is definitely a bug that should be fixed.
As a matter of fact I started working on type-safety keeping the API same but when I realised fromEvent also takes array of emitters then things became a little too much. That is when I thought let me roll my own fromEvent-like thing.
And beyond all this what I like about fromEmitter that it's principally correct – unbiased, doesn't make assumptions and has types that just strict enough to make the code work not cause runtime error.
Regarding other design disagreements if you can be specific we can come to a common ground.
Regarding migration, fromEvent can be replaced by fromEmitter in the following way depending on the usage.
// 01 ---

// before:
fromEvent(emitter, name);

// after:
fromEmitter(emitter).event(name);

// 02 ---

// before:
fromEvent<T>(emitter, name);

// after:
fromEmitter(emitter).event(name) as Observable<T>;

// 03 ---

// before:
fromEvent(emitter, name, options);

// after:
fromEmitter(emitter).event(name, options);

// 04 ---

// before:
fromEvent<T>(emitter, name, options);

// after:
fromEmitter(emitter).event(name, options) as Observable<T>;

// 05 ---

// before:
fromEvent(arrayOfEmitters, name);

// after:
merge(...
    arrayOfEmitters
    .map(e => fromEmitter(e).event(name))
);

// 06 ---

// before:
fromEvent<T>(arrayOfEmitters, name);

// after:
merge(...
    arrayOfEmitters
    .map(e => fromEmitter(e).event(name))
) as Observable<T>;

// 07 ---

// before:
fromEvent(arrayOfEmitters, name, options);

// after:
merge(...
    arrayOfEmitters
    .map(e => fromEmitter(e).event(name, options))
);

// 08 ---

// before:
fromEvent<T>(arrayOfEmitters, name, options);

// after:
merge(...
    arrayOfEmitters
    .map(e => fromEmitter(e).event(name, options))
) as Observable<T>;

This assumes that users are using fromEvent in such a way that fromEmitter doesn't give error like not listening to bogus events, etc. Even if refactoring to fromEmitter gives them errors it's an opportunity to fix the code.
In most cases users can and should remove as Observable<T>. We can't have that by default because it can break the code. Also instead of writing as Observable<T> I guess we should also offer an identity operator that users can use (not code transformers) like following if the runtime overhead is not too much.
const assertType =
    <T>() =>
        ($: Observable<unknown>) =>
            $ as Observable<T>

I don't know how difficult it will be to make code transformers but I have a feeling it shouldn't be much hard in case of TypeScript. In case of JavaScript I guess we can't really tell if it's a single emitter or array of emitters with 100% accuracy.
Also this refactoring will require spread version of merge which is now available in v8. So I guess we should deprecate fromEvent in v9? and I think we should keep fromEventPattern but have a lint rule that can detect if the code can be refactored to withMethods.
So first step now to agree upon the design and API. If the current design is good, I can explore writing code transformers.


Is there your second post about it?

@dvf
Hi!
I saw your post on Medium and liked to much your basic concept about blockchain, understanding it by making it.
Is there your second post talking about verifying transactions, preventing double spents, etc?

Also, I consider porting it to Eventlr (using visual conditions/actions that are compiled to JavaScript).


fix: fix langchain error handling to avoid crash on openai>1.0.0

Related Issues/PRs
N/A
What changes are proposed in this pull request?
The code referencing openai<1.0 classes can't run when you have openai>1.0.
How is this patch tested?
Manual tested
Does this PR change any dependencies?

[x] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[x] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

/azp run

/azp run

/azp run

/azp run

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

Project coverage is 25.31%. Comparing base (d9149d1) to head (da95b6d).

:exclamation:  There is a different number of reports uploaded between BASE (d9149d1) and HEAD (da95b6d). Click for more details.
HEAD has 144 uploads less than BASE

Flag
BASE (d9149d1)
HEAD (da95b6d)

151
7

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #2307       +/-   ##
===========================================
- Coverage   83.72%   25.31%   -58.42%
===========================================
  Files         326      326
  Lines       16769    16769
  Branches     1480     1480
===========================================
- Hits        14040     4245     -9795
- Misses       2729    12524     +9795

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

/azp run


support generic lambda expressions

From @jmesserly on April 25, 2016 22:19
Initial implementation of #301 may not cover this.
See #526 for an example
These don't come up all that often in practice, as you can't write down their type yet (see #526). We implemented them in Analyzer for completeness.
Copied from original issue: dart-lang/dev_compiler#527

Hmmm. I actually think this will work but we should add a test to double check.

Just double checked, this does indeed work already in DDC. Closing out.


File Server for FSLogix (not FSLogic) is not modern

I would approach with the usage of Azure Blog Storage when building into Azure Cloud, and not use a traditional File Server with Compute overhead, whilst utilizing FSLogix Containers.
Just saying :)
//Karsten

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 26f8c27e-77a0-1ca8-4749-d0d3f075fba3
Version Independent ID: fca6a9b5-2b70-52fe-1e5f-0aa4c432f3e4
Content: Strategic benefits of Azure Virtual Desktop - Cloud Adoption Framework
Content Source: docs/scenarios/wvd/strategy.md
Service: caf
Sub-service: caf-scenario-virtual-desktop
GitHub Login: @martinekuan
Microsoft Alias: martinek

Thank you for your feedback.  We have created internal ticket 177462 to track and investigate this issue.

#please-close


Cannot build - boost_chrono not found

Hi
I desperately tried to build the caffe-android-lib for arm64-v8a architecture but always get this error (I tried with both master and dev branch). I build on OSX El Capitan, ndk-r10e.
`CMake Error at /usr/local/Cellar/cmake/3.5.0/share/cmake/Modules/FindBoost.cmake:1647 (message):
Unable to find the requested Boost libraries.
Boost version: 1.56.0
Boost include path:
/Users/sladomic/caffe-android-lib/android_lib/boost/include
Could not find the following Boost libraries:
      boost_chrono

Some (but not all) of the required Boost libraries were found.  You may
need to install these additional Boost libraries.  Alternatively, set
BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT
to the location of Boost.
Call Stack (most recent call first):
cmake/Dependencies.cmake:5 (find_package)
CMakeLists.txt:63 (include)
-- Found GFlags: /Users/sladomic/caffe-android-lib/android_lib/gflags/include
-- Found gflags  (include: /Users/sladomic/caffe-android-lib/android_lib/gflags/include, library: /Users/sladomic/caffe-android-lib/android_lib/gflags/lib/libgflags.a)
-- Found PROTOBUF: /Users/sladomic/caffe-android-lib/android_lib/protobuf/lib/libprotobuf.a
-- Found PROTOBUF Compiler: /Users/sladomic/caffe-android-lib/android_lib/protobuf_host/bin/protoc
-- Found LMDB: /Users/sladomic/caffe-android-lib/android_lib/lmdb/include
-- Found lmdb    (include: /Users/sladomic/caffe-android-lib/android_lib/lmdb/include, library: /Users/sladomic/caffe-android-lib/android_lib/lmdb/lib/liblmdb.a)
-- -- CUDA is disabled. Building without it...
-- OpenCV found (/Users/sladomic/caffe-android-lib/android_lib/opencv/sdk/native/jni)
-- Found EIGEN include: /Users/sladomic/caffe-android-lib/android_lib/eigen3
-- Python interface is disabled or not all required dependencies found. Building without it...

See also "/Users/sladomic/caffe-android-lib/caffe/build/CMakeFiles/CMakeOutput.log".`
Can I somehow copy the boost_chrono from somewhere else or do I need to change something in the build script?
Thanks,
Michael

I just had a test build of dev branch on my macbook (OS X El Capitan) using cmake 3.5.2 and ndk-r10e, and everything seemed fine. Please make sure your settings are correct, e.g.,
export ANDROID_ABI="arm64-v8a"
export USE_OPENBLAS=1

Thanks.

Thanks. It worked now. I updated my cmake from 3.5.0 to 3.5.2 and used OpenBLAS now. But nevertheless the issue https://github.com/sh1r0/caffe-android-demo/issues/20 remains. This one can be closed though.


fix: resubmission incorrectly marking transactions as failed

Explanation
When resubmitting a pending transaction – if an 'already seen' error is caught (which indicates that the tx is still pending in the mempool), we should ignore the error instead of failing the transaction.
Here is how the bug was happening:

The user submits a transaction with a low gas price, which is then added to the TransactionController and marked as 'submitted'.
The PendingTransactionTracker starts monitoring the transaction status.
If the transaction is not mined within a certain number of blocks (determined by the #isResubmitDue method), the PendingTransactionTracker attempts to resubmit the transaction.
Inside the #resubmitTransaction method, the PendingTransactionTracker calls the #approveTransaction method from the TransactionController to approve the transaction again.
The TransactionController's #approveTransaction method attempts publish the transaction again. However, since the original transaction is still pending, the node responds with an "already known" error.
The #approveTransaction method in the TransactionController catches this error in the catch block, but it treats it as a general error and calls the failTransaction method.

References

Fixes https://github.com/MetaMask/metamask-extension/issues/24183

Changelog
@metamask/transaction-controller

FIXED: When resubmitting a pending transaction – if an 'already seen' error is caught (which indicates that the tx is still pending in the mempool), we should ignore the error instead of failing the transaction.

Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@metamaskbot publish-preview

Superseded by https://github.com/MetaMask/core/pull/4255


[Power Source] Mandatory attribute has to be implemented in sample-app and chip-tool

Feature Area
Other
Test Case
TC-PS-1.1 and 2.1
Reproduction steps
All-clusters-app and Chip-tool has to be enabled with below mentioned attribute as it is mandatory:

BatChargePermissions

Specification Reference:

Bug prevalence
Whenever I do
GitHub hash of the SDK that was being used
1a6bd3b28743a2b2494157190061eeabaf4eb9c3
Platform
raspi
Anything else?
No response

Please see spec issue - https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/8158. There is no way this attribute is correctly marked in the spec. None the less, it needs to be fixed before this cluster is launched.

Battery management things has been removed from spec in PowerSourceCluster


Suggestion: Class Cast

For example, in Java:
int a = 1;
Long b = (Long) a;
Can the provider be implemented in skript-reflect?
Thanks a lot.

skript-reflect does this automatically. Can you show where you'd need this?

set {_p} to "just_a_example" parsed as player
set {_w} to {_p}.getLocation().getWorld().getHandler()
{_w} is a WorldServer now.But I need NMS World
They are same acturally

A WorldServer is an NMS World tho:

Yeah, they are same, but when I try to put {_w} into a Java function, not of the same type

They are of the same type, you're probably doing something wrong there.

It told me that WorldServer is not World, but they are same

Anyway, this place is for suggestions/bug reports, if you want help with your scripts, I recommend you join the skript-reflect Discord or skUnity discord


Add symlink_host_gcc: Symlink the host's compiler for Linuxbrew

Codecov Report

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

@@            Coverage Diff             @@
##           master     #358      +/-   ##
==========================================
- Coverage   61.39%   61.35%   -0.04%
==========================================
  Files         375      375
  Lines       20355    20367      +12
==========================================
  Hits        12497    12497
- Misses       7858     7870      +12

Impacted Files
Coverage Δ

cmd/install.rb
68.04% <0%> (-5.21%)
:arrow_down:

Continue to review full report at Codecov.

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


Implement the full CollapsibleHeaderLayout

For PXBLUE-XXXX

Changes proposed in this Pull Request:

Enhance the Header component to manage 'dynamic' or 'static' variants
Implement the CollapsibleHeaderLayout component which manages the spacing and scrolling of the main screen contents
Update the docs / storybook
Did some linting cleanup on hooks/dependencies

Screenshots:

To Test:

Swap the outer View component in the Showcase App.tsx with CollapsibleHeaderLayout
Take the props from the existing Header and pass them into the HeaderProps prop of the CollapsibleHeaderLayout
Remove the existing Header component
Explore

I have not checked this on Android yet, so that would be as good a place to start as any.

Alternatively, you can use the version of App.tsx I will share on Teams which does the above for you.

The two menu buttons in the actionItems will swap the variant (first) and update the expanded/collapsed heights (second) if you want to test those out.

Make sure to poke around with all of the different combinations of things you can do (scrolled down, scrolled up, expanding and collapsing on click, opening and closing search in different locations, changing the sizes, changing the variant, etc.).

noticed some difference between android/iOS using the expanded prop. On android when expanded is set it scrolls to collapse and on iOS it does not. iOS stays extended...

Are you talking about the startExpanded prop?
That only comes into play the very first time the app is loaded to initialize some state variables. If you simply hot reload the app (e.g., by changing a property in App.tsx) it will (should?) have no effect unless you reload the app on the device.
startExpanded also works independently of the variant prop. You can have a 'dynamic' header that starts expanded or you can have a static header that starts expanded.
I suspect you may have been playing with the variant on one of your simulators (and ended up where one is dynamic and one is expanded) and then you set the startExpanded prop and refreshed the apps.

Are you talking about the startExpanded prop?
That only comes into play the very first time the app is loaded to initialize some state variables. If you simply hot reload the app (e.g., by changing a property in App.tsx) it will (should?) have no effect unless you reload the app on the device.
startExpanded also works independently of the variant prop. You can have a 'dynamic' header that starts expanded or you can have a 'static' header that starts expanded.
I suspect you may have been playing with the variant on one of your simulators (and ended up where one is dynamic and one is expanded) and then you set the startExpanded prop and refreshed the apps.

yes ok all good, it works


resolve GHSA-67hx-6x53-jw92

https://github.com/babel/babel/security/advisories/GHSA-67hx-6x53-jw92

@mergifyio backport release/4.2.x

@mergifyio backport release/3.7.x


[HTTP] Proxy implementation

Description:
This is similar to behaving like squid proxy server. Can do after May.

I am closing this issue as the need is longer there. We can have a new issue when we the need is there.


Den strigo feat/landing page

Please read and mark the following check list before creating a pull request (check one with "x"):

[ ] I read and followed the CONTRIBUTING.md guide.
[ ] I read and followed the New Feature Checklist guide.

Short description of what this resolves:

Hi @nnixaa ,
How can i see landing page?? is there any link/route to that page in dashboard or somewhere else??


bug

The following code realizes the picture sliding left and right and the background picture has Gaussian blur. How to solve the problem when the picture sliding left and right appears white lines on both sides of the picture

Code:
PageView.builder(
  itemCount: widget.works == null ? 0 : widget.works!.apPhotoEntityList!.length,
  itemBuilder: (context, index) {
    return Stack(
      children: [
        //背景图片
        Image.network(
          widget.works!.apPhotoEntityList![index].imgUrl!,
          fit: BoxFit.cover,
          width: double.infinity,
          height: double.infinity,
        ),
        Align(
          alignment: Alignment.center,
          child: Image.network(
            widget.works!.apPhotoEntityList![index].imgUrl!,
            fit: BoxFit.fitWidth,
          ),
        ).blurry(
          shadowColor: Colors.transparent,
          borderRadius: BorderRadius.zero,
          padding: EdgeInsets.zero,
          blur: 5,
          elevation: 0,
          color: Colors.transparent,
        ),
      ],
    );
  },
)

Screenshot

Thanks for filing this issue @xaiocaiji7653.
Can you please provide reproducible steps and code for this so I can directly start fixing relevant bugs instead of recreation the issue on my side?

@xaiocaiji7653 Can you provide reproducible steps, so I can start fixing.


is note about reminer do not fire after failover is correct? I read timer will not fire based on state but reminder always fire ?

is note about reminer do not fire after failover is correct? I read timer will not fire based on state but reminder always fire ?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 70a492fe-4ea3-2972-e4bd-e25f95b210bf
Version Independent ID: 31b848a4-c9ce-bf05-d3c3-c171d7696741
Content: Reliable Actors timers and reminders - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-reliable-actors-timers-reminders.md
Service: service-fabric
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@snaolekar
Thanks for your feedback! We will investigate and update as appropriate.

@snaolekar
The article you referenced is correct that reminders will not fire after a failover in Azure Service Fabric. This is because reminders are based on a specific time interval and are not tied to the state of the actor. When a failover occurs, the state of the actor is lost and the reminder is not rescheduled.
However, timers are different from reminders in that they are tied to the state of the actor. When a failover occurs, the state of the actor is preserved and the timer is rescheduled based on the new primary replica. This ensures that the timer will continue to fire as expected.
So, to summarize, reminders will not fire after a failover in Azure Service Fabric, but timers will continue to fire based on the state of the actor.


feat: enhance metrics defs

This PR adds a script which parses the implemented metric definitions and saves them as a machine readable file. To allow downstream consumers automatic updates on new Arroyo versions, it was integrated into the package build process and will ship with future versions.
Closes #360

Awesome, thanks!


problematic use a fundingsource directly

https://github.com/lnbits/lndhub/blob/main/views_api.py#L13

I think I ran into something that is related to this issue and am leaving some notes to try to diagnose the problem.
Wallets don't implement invoice_status, they only have a get_invoice_status method:
The lndhub plugin tries to call invoice_status
this in turn tries to call invoice_status from the lnbits/wallets/x.py.
Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/anyio/streams/memory.py", line 98, in receive
    return self.receive_nowait()
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/anyio/streams/memory.py", line 93, in receive_nowait
    raise WouldBlock
anyio.WouldBlock
2024-05-15 14:23:09.94 | ERROR | lnbits.app:exception_handler:439 | Exception: 'CLNRestWallet' object has no attribute 'invoice_status'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 159, in call_next
    message = await recv_stream.receive()
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/anyio/streams/memory.py", line 118, in receive
    raise EndOfStream
anyio.EndOfStream

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/slowapi/middleware.py", line 136, in dispatch
    response = await call_next(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
  File "/app/lnbits/middleware.py", line 215, in block_allow_ip_middleware
    return await call_next(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
  File "/app/lnbits/middleware.py", line 215, in block_allow_ip_middleware
    return await call_next(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
  File "/app/lnbits/middleware.py", line 230, in first_install_middleware
    return await call_next(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 191, in __call__
    response = await self.dispatch_func(request, call_next)
  File "/app/lnbits/middleware.py", line 230, in first_install_middleware
    return await call_next(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 165, in call_next
    raise app_exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/base.py", line 151, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/app/lnbits/middleware.py", line 125, in __call__
    await self.app(scope, receive, send)
  File "/app/lnbits/middleware.py", line 61, in __call__
    await self.app(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/sessions.py", line 83, in __call__
    await self.app(scope, receive, send_wrapper)
  File "/app/lnbits/middleware.py", line 104, in __call__
    await super().__call__(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/gzip.py", line 24, in __call__
    await responder(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/gzip.py", line 44, in __call__
    await self.app(scope, receive, self.send_with_gzip)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/cors.py", line 83, in __call__
    await self.app(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 758, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 778, in app
    await route.handle(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 299, in handle
    await self.app(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 79, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/starlette/routing.py", line 74, in app
    response = await func(request)
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/fastapi/routing.py", line 299, in app
    raise e
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/fastapi/routing.py", line 294, in app
    raw_response = await run_endpoint_function(
  File "/root/.cache/pypoetry/virtualenvs/lnbits-9TtSrW0h-py3.10/lib/python3.10/site-packages/fastapi/routing.py", line 191, in run_endpoint_function
    return await dependant.call(**values)
  File "/app/lnbits/extensions/lndhub/views_api.py", line 180, in lndhub_getuserinvoices
    (await funding_source.invoice_status(invoice.checking_id)).pending
AttributeError: 'CLNRestWallet' object has no attribute 'invoice_status'. Did you mean: 'get_invoice_status'?

These lines are probably relevant:
https://github.com/lnbits/lnbits/blob/5114bd4a47f3bb6aaaf95b4c9b8722734ec9c5dc/lnbits/settings.py#L558
https://github.com/lnbits/lndhub/commit/75c2b0b7f1d081dca39fa63a473b0d3427245a52

fix and released in v0.5.0
https://github.com/lnbits/lndhub/pull/32


pulsar.ebay.com

back on the list again please see #119
Match found in https://hosts.ubuntu101.co.za/hosts:
pulsar.ebay.com

@xxcriticxx  i just reported it to the right place.I'm guessing it will be whitelisted shortly.


documentation/wiki

It would be nice to have a wiki or something to learn how to use it
or some kind of documentation

I just realized that that is not needed


fix #396: (windows) fullscreen/unfullscreen events, disable minimize on fullscreen

Fix #396: a critical bug where the newest implementation of fullscreen/unfullscreen broke the window listener events.
Disables minimize when window is fullscreen. This mimics the behavior of Chromium.

LGTM


⚠ Bofrost.fr has degraded performance

In 4c55470, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 3806 ms

Resolved: Bofrost.fr performance has improved in a60e828.


support live preview

if It works in  live preview mode , i close Obsidian and open it again,it cannot remember

The same here

Same here.


Typescript support

Please generate Typescript types, per https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
I'm currently including your component in my project via const { ReactGhLikeDiff } = require("react-gh-like-diff"), but would much rather leverage Typescript to get full type-checking/parameter support.
Thanks!

Me too!


Use stdlib to for C/C++ backend definitions

The stdlib has definitions that can for example turn an HLSL intrinsic into the suitable call in glsl.
The mechanism for describing these transformations is somewhat ad hoc - but it does allow a lot of flexibility and the ability to describe succinctly intent.
With the C++ backend, this was dealt with in two different ways

For simple scalar built in functions there implementation was pushed out to the 'prelude'
Built in intrinsics that were type dependent the implementation was generated on demand in when it is used

For example take
Matrix<float, 4, 4> mat = ...;
Matrix<float, 4, 4> sinMat = sin(mat);

That the sin scalar function will be turned into a call into a function in the prelude. In this case F32_sin. That the sin(mat) will cause a function Matrix<float, 4, 4> sin(Matrix<float, 4, 4>)  to be generated, and then at the call site just 'sin' can be output.
The defining of the functions within the prelude has some definite pros to it, in that a client can decide what implementation they wish to use for these functions. If the only implementation is defined in the stdlib, either it would be beneficial to be able to change the stdlib defintion or clients will be stuck with whatever implementation is defined in stdlib. It's also unfortunately true, that all of the functions that would need to be defined may not be available on all compilers. That the prelude can either ignore this (as client can always just use their own prelude) and/or it's typically pretty easy (if ugly) to test such cases with preprocessor in prelude. If it's defined in stdlib and not replaceable - then potentially it won't work at all for some compilers.
Having definitions as part of the stdlib is more in keeping with other targets, and allows for definitions to be located in a single place. Also if such definitions were replacable then perhaps you'd have the best of both worlds. Where the ones defined in the stdlib are perhaps the 'default' definition.
For the second case, the 'sin' generation could perhaps be side stepped with templating pre generated specializations (and so a very big prelude file). One of the reasons the implementation was made to generate the functions as needed, is it allows for supporting a C backend in the future.
That being said - there are some functions where having a simple implementation in the stdlib would be a perfectly good solution. Take cross for example. If that was given a default definition, that was then converted to C/C++, as part of the regular emit, it would remove a lot of code and complexity from the CPP code generation.
Other simple examples would be 'length', 'normalize', 'reflect', 'any', 'all' and vector/matrix multiplication. You could also imagine other operations (such as a swizzle converting to a construct) might be suitable.

The C++ backend is now refactored to follow the same pattern for other backends.


Resume: 2020 - 2021 Worked for a known conman to bring to life his pump and dump scheme.

https://tinyurl.com/3xaej452

Spam or truth? There is only one way to find out. Look into the sources yourself.

tari-project/tari#3052

tari-project/tari#3051

tari-project/tari#3035

tari-project/tari#2997

tari-project/tari#3062

tari-project/tari#3061

tari-project/tari#3060

tari-project/tari#3059


Move tile path string to level index width methods from mysql to layout package

It's a better home for those path parsing related methods.

Codecov Report
Attention: Patch coverage is 94.28571% with 2 lines in your changes missing coverage. Please review.

Project coverage is 35.03%. Comparing base (46ec9c2) to head (c57ab12).
Report is 49 commits behind head on main.

Files
Patch %
Lines

cmd/example-mysql/main.go
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   35.80%   35.03%   -0.77%
==========================================
  Files          16       33      +17
  Lines        1363     2777    +1414
==========================================
+ Hits          488      973     +485
- Misses        801     1696     +895
- Partials       74      108      +34

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


Async select

This PR fixes #12427.

Found with @nobuti that:

search is not working properly (just tested in DO region editor).
when timespan is selected, it is not rendered displaying the selected item.

Both issues are fixed. Also, the slider component doesn't trigger change until the user releases the dragger. This is enqueued to deploy due Jenkins is going to shut down™.

Working like a charm now, should I test the rest of the places where the select component is being used?
I've found one minor thing with the boundaries slider, when there is only one value:

Reviewing all available analysis + places where select is being used.

Analyses reviewed:

DO: 👌  (several custom selects included).
Filter by layer: 👌  (source select, standard selects).
Subsample: 👌 , no selects :joy:.
Georeference: 👌 , tested in most "complicated" one, street-by-address, where there are standard and custom selects.
Intersection: 👌 .
AOI: 👌 , no selects.
Merge: 👌 , custom selects included.
Centroid: 👌 , with enabler-selector with select, pretty nice.
Convex hull: 👌 , with operation and enabled-selector, 💃 .
Filter by column: value: 👌 .
Filter points in polygons: 👌 .
Connect with lines: 👌 .
Cluster: 👌 , no selects.
Markov: 👌 .
Find nearest: 👌 .

Frontend tests passing, merging 💋 .


Indentation level in code section

Describe the bug
Given a schema object type, some of its fields have additional arguments. In the generated code section, the additional arguments are printed in new lines missing some white spaces.
To Reproduce

Prepare a schema with sample object type.
Run plugin cli to generate graphql MDX
Run docusaurus to preview generated graphql document, navigate to the page for sample object type. In the code section, see result below:

GraphQL schema

If applicable, add an extract of the GraphQL schema.
type DepartmentInformation implements Record {
  id: ID!
  email: EmailAddress
  number: PhoneNumber
  departmentOpenTime: Time
  departmentCloseTime: Time
  website: URL
  employees(skip: Int): [String!]!
}

Docusaurus configuration

I am using the default plugin settings.
Expected behavior
In repro step 3, expect to see code section as below:

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@ljiang-ti - Another good catch! :pray:
Apparently an edge case, ie it only occurs if this is the last field of the type. But, I see that you did figure it our and submitted PR.
This is will be release today :rocket:

Fix released in 1.18.1 :magic_wand:


Proposal: Allow for Input filtering in NumberBox

Proposal: Allow for Input filtering in NumberBox

Summary

For now, using a NumberBox to handle Number-only inputs is sometimes less preferable to using a TextBox, since the TextBox can be tweaked to have an input filter that disallows adding any characters that are not digits for example.
With a TextBox this can be done with the BeforeTextChanging-Event (like this), which does not exist for the NumberBox. Thus, currently it's not possible to straight up block or otherwise handle invalid NumberBox input. The best option is the current Validation that just resets the value on invalid input when pressing enter. Either being able to manually limit the possible inputs specifically or just being able to handle BeforeChanging Event in any way the developer desires would be helpful here I think.
Rationale

NumberBox should make restriction to digit-only or arithmetic-only Inputs possible
This is a specialized tool sometimes less useful for its actual purpose than a more general tool (TextBox)

Scope

Capability
Priority

Add a possibility to block undesired input characters/text
Must

Add a way to work with input data in any way desired, eg. like TextBox.BeforeTextChanging
Should

Add an option to simply limit the NumberBox to predefined character sets (eg. Digits only, digits+'.'+',', arithmetic, etc.)
Could

Offer a way to notify the user of his invalid Input (eg. Tooltip popup on invalid character?)
Could

Important Notes

Please just tell me if I didn't see the obvious way that would already allow me to do this.
Open Questions

None yet.

This is something that the Terminal would also like added. For the Settings UI, we're using NumberBox's for things that can only be numbers, but being able to type non-numeric input into them definitely seems weird.

This is something that the Terminal would also like added. For the Settings UI, we're using NumberBox's for things that can only be numbers, but being able to type non-numeric input into them definitely seems weird.


Linux build requires libXScrnSaver

You may want to note in your How to Build From Source documentation that the Linux build requires the libXScrnSaver package.
https://github.com/Microsoft/BotFramework-Emulator/blob/v4/CONTRIBUTING.md#how-to-build-from-source
If this package is not present, the following error is received upon launching the emulator with npm run start:electron:dev:
/home/stephen.panicho/Downloads/BotFramework-Emulator/node_modules/electron/dist/electron: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start:electron: `electron --inspect=7777 .`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start:electron script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start:electron:dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/stephen.panicho/.npm/_logs/2018-08-08T16_25_50_010Z-debug.log

Thank you for the submission. We are in the process of auditing our readme which includes build/run instructions. I'll be sure to incorporate this.

Doc a pre-preq for Linux

@spanicho-bnet Can I ask what version / distro of Linux you were running? I just tried to build the source locally on Ubuntu 16.0.5 LTS and didn't run into this issue. Maybe that version comes with the package already installed natively?

Addressed in #1028


chore(ci): Adding tests for CAF scripts

Test flow:

Install dependencies (minikube for linux, asdf, plugins)
run caf_create_local_k8s.sh to setup K8s cluster (minikube or orbstack)
install ingress-nginx via helm to nginx-ingress namespace which is needed by caf_route_to_local_k8s.sh
Run caf_route_to_local_k8s.sh and attempt to CURL the metrics endpoint of kube-dns using the full service name kube-dns.kube-system.svc.cluster.local

I didn't bother making a docker image for the following reasons

Tests are pretty fast
Storing the image in the adaptive ECR repo adds complexity and exposes it since this is a public repository
Only useful for the linux test since we're using the mac runner directly

We can consider adding these 2 workflows, or the jobs as part of the ci.yaml workflow as well.


Wrong internal dependency tree for beta versions

Version
4.0.0-beta.7 (or any 4.x version lower than the current @next)
Steps to reproduce

in package.json of an actual project, use an exact-version dependency, e.g. "react-router-dom": "4.0.0-beta.7"
wait until a newer version is released, beta.8, before installing (e.g. when continuous integration runs npm install without recycling node_modules)
run npm install

Expected Behavior
├─┬<EMAIL_ADDRESS>│ ├─┬ ...
│ └──<EMAIL_ADDRESS>
No runtime errors.
Actual Behavior
Wrong dependency to beta.8:
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>
Random runtime errors, nothing is rendered, e.g.:
Uncaught TypeError: Cannot read property 'path' of undefined
    at Switch.js:53
    at forEachSingleChild (ReactChildren.js:51)
    at traverseAllChildrenImpl (traverseAllChildren.js:77)
    at traverseAllChildrenImpl (traverseAllChildren.js:93)
    at traverseAllChildren (traverseAllChildren.js:172)
    at Object.forEachChildren [as forEach] (ReactChildren.js:71)
    at Switch.render (Switch.js:51)
    at ReactCompositeComponent.js:796
    at measureLifeCyclePerf (ReactCompositeComponent.js:75)
    at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (ReactCompositeComponent.js:795)

workaround:
  "dependencies": {
    "react-router": "4.0.0-beta.7",
    "react-router-dom": "4.0.0-beta.7",
  },

will install correctly:
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Dupe of #4656


PROGRESS is not properly displayed in 1.29.1 cluster

What steps did you take and what happened:
Steps:
$ ~/sonobuoy version
Sonobuoy Version: v0.57.1

~/sonobuoy  run  --e2e-repo-config <omitted>
~/sonobuoy  status

Conformance test has passed 40 mins. Many cases have been executed but the output of  ~/sonobuoy  status sticks in Passed:  0, Failed:  0.
         PLUGIN     STATUS   RESULT   COUNT                                PROGRESS
            e2e    running                1   Passed:  0, Failed:  0, Remaining:386
   systemd-logs   complete                4

Sonobuoy is still running. Runs can take 60 minutes or more depending on cluster and plugin configuration.

Finally when the test complets, the status is as below:
 $  ~/sonobuoy   status
         PLUGIN     STATUS   RESULT   COUNT                                PROGRESS
            e2e   complete   passed       1   Passed:  0, Failed:  0, Remaining:386
   systemd-logs   complete   passed       4

What did you expect to happen:
Status report show the actual progress.
Anything else you would like to add:
Same Sonobuoy and same command lines (steps)  works well in 1.28 and 1.27 clusters.
Have searched the open issues and not found similar one. I am not sure it is a Sonobuoy  bug, or only happens in my cluster.
Environment:

Sonobuoy version: 0.56.17; 0.57.1
Kubernetes version: (use kubectl version): 1.29.1
Kubernetes installer & version: kubeadm 1.29.1
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):  Ubuntu in CP and SUSE in node
Sonobuoy tarball (which contains * below)

I'm observing similar issue.
For me its not reporting progress at all, the output stays like:
./sonobuoy status
         PLUGIN    STATUS   RESULT   COUNT   PROGRESS
            e2e   running                1
   systemd-logs   running                6

Sonobuoy is still running. Runs can take 60 minutes or more depending on cluster and plugin configuration.

and I have the following in the e2e pod logs:
Will run 386 of 7407 specs

Environment:
Sonobuoy version: v0.57.1
Kubernetes version: 1.29.3
Kubernetes installer & version: Cluster API 1.7.0; kubeadm version v1.29.3
Hardware configuration: Openstack
OS: Alpine Linux v3.19

Good day. Is anyone looking into this?

I faced the same issue.
And, It seems to be working well in v1.28.
Environment:
Sonobuoy version: v0.57.1
Kubernetes version: v1.29.5
Kubernetes installer & version: Kubespray v2.25.0; kubeadm version v1.29.5
OS: Ubuntu Server 22.04 LTS

I also faced the same issue, reproductible with a simple kind cluster
kind create cluster
sonobuoy run
sonobuoy status # nothing changes, although we can see the creation of pods/namespaces in the cluster
sonobuoy logs   # no logs are sent

Environment:

Sonobuoy version: Sonobuoy Version: v0.57.2
Kubernetes version:

Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0

Kind version: kind v0.23.0 go1.21.10 linux/amd64


nextcloud26: init at 26.0.0

Description of changes
:tada:
See this slide for relevant changelog: https://youtu.be/docYiLbGSxI?t=5058
https://nextcloud.com/blog/hub-4-pioneers-ethical-ai-integration-for-a-more-productive-and-collaborative-future/
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

closes https://github.com/NixOS/nixpkgs/pull/219929

the "remove custom dbuser creation" patch isn't required anymore for 26, you can now disable that behavior by setting NC_setup_create_db_user=false during setup or add "setup_create_db_user" => false to config.php before setup.

the "remove custom dbuser creation" patch isn't required anymore for 26, you can now disable that behavior by setting NC_setup_create_db_user=false during setup or add "setup_create_db_user" => false to config.php before setup.

Done.

@Ma27 do you think we should remove NC24?

Shouldn't it be added here as well ?
https://github.com/NixOS/nixpkgs/blob/60c1d71f2ba4c80178ec84523c2ca0801522e0a6/nixos/modules/services/web-apps/nextcloud.nix#L207

I'll try to take a look later today, but no guarantees because exam phase.

@Ma27 do you think we should remove NC24?

Let's await the final patch release. Reason is quite simple: we can automatically backport all updates on the next updates and we don't have to fix up the backport.
Btw, I'd resolve the review comments and drop the nextcloud23 references (this makes the module simpler on some occasions) and deploy the changes to my setup. Would it be OK if I push the changes after that to your branch? :)

@Ma27 do you think we should remove NC24?

Let's await the final patch release. Reason is quite simple: we can automatically backport all updates on the next updates and we don't have to fix up the backport.

Got it.

Btw, I'd resolve the review comments and drop the nextcloud23 references (this makes the module simpler on some occasions) and deploy the changes to my setup. Would it be OK if I push the changes after that to your branch? :)

Please do so! It's running on my setup since the opening of this PR, no trouble so far.

FWIW I got bitten by https://github.com/nextcloud/user_saml/issues/709, but considering that we don't ship SAML by default and the workaround is trivial I don't consider this a blocker.

@RaitoBezarius btw, why does 881efdb state that the stateVersion logic is broken? The change seems OK to me :)

Fixed, excessive amount of carefulness. :)


🌱 Stop using github.com/pkg/errors

What this PR does / why we need it:
This project is deprecated and not maintained anymore: https://github.com/pkg/errors
We can use standard golang primitives for that.

@neolit123 thanks for the information. We will deprecate pkg/errors and see how well it works for us, good to know that people are still using it.


Test Istio release "Istio 1.9.6"

Istio recently (2021-06-24 19:16:50 +0000 UTC) released "Istio 1.9.6". Let's test it :rocket:.

https://github.com/knative-sandbox/net-istio/pull/699 updated.


(node:11856) [DEP0016] DeprecationWarning: 'root' is deprecated, use 'global'

If i use this - const jsons = require('./environment');
When running the node server, I am getting warning - (node:11856) [DEP0016] DeprecationWarning: 'root' is deprecated, use 'global'. Still now. Any solution ?

Fixed on 0.3.0


Router v1 v2 setup

Fixes/Closes/References #1616
Type
✨ Feature
Value
This will split basic traffic to the different parts of our apps (v1, v2).

Merging as it affects no-one, happy to run through it with anyone interested.


Improve JS build system - Google Closure

I would like to compile down the JavaScript in this project by compiling down the JavaScript using Google Closure.  This would have several benefits:

Makes it easier to know which browsers (and versions) we support.
Makes the client faster for players to download and use.
Frees me from worrying about the data size of all my comments and variable names.
Would help me find JS bugs before they happen.

Here is a handy link to the Closure JS Compliler:
https://github.com/google/closure-compiler

While working on compiling the JS code in this project I stumbled upon a design detail I hadn't seen before... the JavaScript builds "require" statements on the fly, using local file paths that are built from config strings.
So... I need to nuke all that before the build system possible / reasonable.


Golang rune type not colored like others

VSCode Version: 1.26.1 (1.26.1) 493869ee8e8a846b0855873886fc79d480d342de
OS Version: macOS High Sierra 10.13.6 (17G65)

Please see https://github.com/Microsoft/vscode-go/issues/1894.
Does this issue occur when all extensions are disabled?: Yes

@willfaught Which theme are you using? I tried all the themes that ship out of the box, and I don't see the issue

The default theme.
On Sun, Sep 2, 2018 at 2:15 AM Ramya Rao<EMAIL_ADDRESS>wrote:

@willfaught https://github.com/willfaught Which theme are you using? I
tried all the themes that ship out of the box, and I don't see the issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/57725#issuecomment-417916153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD5VnxnHc1LqK5qmUzA9hINqwYEVxuCks5uW6GjgaJpZM4WV_7H
.

uh... looks like that was fixed in 98d3a0b3f238682131a448f33fd580d090f8e8e8 for #56515, but it's not available yet in vscode stable.

And it was me who fixed it! I can't believe I couldn't recall that.
Thanks again @db47h
@willfaught Please try our Insiders or wait for an update to the stable bits which should be out sometime this week


Source links for models

Thingiverse, Cults3d, CGTrader, MyMiniFactory

All have APIs, so we should store proper identifiers, not just URLs.


[Examples] Add Typescript and Typescript ESM examples

Description

Simple examples to show that Typescript and Typescript ESM can be used with the SDK with no issue.
Test Plan

Each works by running pnpm test in each.  Next step would be to add these examples into the CI system once there is not as much churn.
Related Links

Hm, I'm getting dependency errors:
transfer.ts:15:8 - error TS2307: Cannot find module 'aptos' or its corresponding type declarations.
my directory is there, but just not working for me, I'm running it from the simple_transfer directory in both cases, am I just doing it wrong ? can never tell when it's a package manager error

Hm, I'm getting dependency errors:
transfer.ts:15:8 - error TS2307: Cannot find module 'aptos' or its corresponding type declarations.
my directory is there, but just not working for me, I'm running it from the simple_transfer directory in both cases, am I just doing it wrong ? can never tell when it's a package manager error

It uses a link dependency (I'm no expert of typescript build systems).
So, because it uses a link dependency you have to run pnpm build in the main repo, then run that one.
I suspect it can be cleaned up need to do a little research into pnpm


Fix bug in funnel shift dataflow analysis

Fixes #629

@manasij7479

Looks great but please add a regression test

ping

lgtm, thanks!


contribute expanx feature and its testing activity

[x] expand another list into the bullet item
[x] enable custom animation on the bullet item
[x] enable custom layout and touch ripple layout interactions on the touch list
[x] enable custom notification items in the list

@cymcsg merge first

Thank you for the great work!


ConsoleDataWriter write interval configurable

Sorry for the commit mess, tried to amend message with your conventions... :sweat_smile:

Thanks. Would you mind squashing your commits into a single one, please?

Please regarding commit message, we follow Netty's convention: https://netty.io/wiki/writing-a-commit-message.html

cherry-picked on master as 5f4d0be9585a472ad4343f99ef3c8dbf9fffaa54
Thanks!


Can I order pizza here?

I hope you give the best.
I ordered on sindresorhus, but he give me creepy.
https://github.com/sindresorhus/awesome/issues/544

nooooooo!!!!!!!

Treefiddy for one.


Unknown build rule 'command' while build language server binary on macOS

Describe the bug
A clear and concise description of what the bug is.
Basic information
Mac OS (Catalina V 10.15.7)
gcc --version
Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)

ninja --version
1.10.0.git.kitware.jobserver-1

Build lua-language-server from scratch following instructions got the error:
ninja: error: /Users/xiao/development/lua-language-server/build/macos/make.ninja:169: unknown build rule 'command'
build $builddir/_/copy_script: command
                               ^ near here

To Reproduce
Steps to reproduce the behavior:
https://github.com/sumneko/lua-language-server/wiki/Build-and-Run-(Standalone)
Follow the steps listed here for macOS to build language-server binary
git clone https://github.com/sumneko/lua-language-server
cd lua-language-server
git submodule update --init --recursive
cd 3rd/luamake
ninja -f ninja/macos.ninja
cd ../..
./3rd/luamake/luamake rebuild

Expected behavior
A clear and concise description of what you expected to happen.
I should have this one running fine and get binary under
./bin/macOS/lua-language-server

Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: macOS [e.g. Windows, macOS, Ubuntu]
Is WSL remote?
Client: [e.g. VSCode, neovim]

Additional context
Add any other context about the problem here.

This also happens on Linux

This also happens on Linux

I can confirm that ...

Update luamake, and try again.

Should fixed by 3e072133aafe9467cd13499f8c33d6d5f7c8bdff

Thanks for the swift response and that very quick fix!

Confirm latest master works, thank you @sumneko


Feature/add drop

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


fix: break words in TOC titles for proper wrapping

Fixed wrapping issue in TOC section for long single-word headers (e.g. env variables)
Before:
https://user-images.githubusercontent.com/827338/230904093-f9de9564-9b73-4c63-9224-46ceb2c3ee07.mp4
After:
https://user-images.githubusercontent.com/827338/230904132-55bcacfa-c3e8-4795-9e14-cfedc4b636d2.mp4

Sure, done 👍

Thanks for fixing this!


Nvme detected but no disk

Hi,
I don't know what i'm doing wrong.
after running script my nvme installed on pci card is detected and added to compatibility list. However disk is not shown in dsm 7 under hdd/ssd and can't create pool or cache.
Can it be that i'm using some simple pci converter to nvme ? Not approved by Synology.
RS1221+
DSM 7.1.1 u4
Script - latest
M2 drive ssd 960 pro samsung
Also when running script: i have error on line 500 /run/synostorage/disk/$(basename -- "$d")/m2_pool_support: No such file or directory
Script also reporting:
No M.2 cards found
No Expansion Units found

That error is interesting because to get that far your Synology must have a /sys/block/nvme device but no /run/synostorage/disks/nvme active disk.
I would assume it is definitely because the PCIe card is not a Synology PCIe card. I do have another script that may trick DSM into thinking your PCIe card is a Synology card. https://github.com/007revad/Synology_enable_M2_volume

OP not responding


Some async method in Client implementation didn't need to be async at all

The binary, text, and call methods are just calling a synchronous function and returns immediately, so there's no apparent reason to make them async function as it is. (unless you have plans for the future and want your API to be like this already to match your future plans)

Thanks for the contribution, it looks like I've missed this one.
I've also fixed methods on the server handle, converting them into synchronous functions.


404

@mcxtlong commented on Sun Jun 02 2019
[在此处输入反馈]
http://www.contoso.com/default.html
404 not found

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 6d0d3c05-6a37-ccb6-d897-a4c35beb2597
Version Independent ID: a826593c-e1e0-2caa-c764-3e3f63322892
Content: 如何：使用 WebRequest 类请求数据
Content Source: docs/framework/network-programming/how-to-request-data-using-the-webrequest-class.md
Product: dotnet-framework
Technology: dotnet-networking
GitHub Login: @karelz
Microsoft Alias: ncldev

Hi team,
the user is reporting a 404 link which is present in the original example
best

Can we please get translation to English, we do not support bug reports in other languages ...

Hi @karelz
the reported segment is not localized, because is in the code box.

The chinese text in the comment is just a placeholder from the automatic template to logging issues (It just says "Feedback")
best

Adding this feedback item to our community project and our backlog.
Example could be changed to use a different URL.
Locations that have to be changed:

https://github.com/dotnet/docs/blob/master/docs/framework/network-programming/how-to-request-data-using-the-webrequest-class.md
https://github.com/dotnet/samples/blob/master/snippets/csharp/VS_Snippets_Network/RequestDataUsingWebRequest/cs/WebRequestGetExample.cs
https://github.com/dotnet/samples/blob/master/snippets/visualbasic/VS_Snippets_Network/RequestDataUsingWebRequest/vb/WebRequestGetExample.vb


Support JavaScript?

This project is awesome. I like it and recommend to many friends.
And will you support javascript?
Thank you.

What exactly is the goal?
Supporting ES2015 Imports/Exports?

Yes. Support ES2015 Imports/Exports.

Feel free to create a pull request, i currently don't have the time to implement.


⚠ TROJAN 🇺🇸 United States USF 1 has degraded performance

In 5967ad7, TROJAN 🇺🇸 United States USF 1 (https://ust-1.optnl.com/) experienced degraded performance:

HTTP code: 200
Response time: 6857 ms

Resolved: TROJAN 🇺🇸 United States USF 1 performance has improved in 42aa90c.


Fix legacy flexbox inheritance issue

Fixes #61.
In iOS 5 and 6, when the Arrange component is used at any nesting level within any flexbox that has flex-direction set to row-reverse the Arrange component inherits the reversed direction. This shouldn’t happen.
Status: Ready to merge
Reviewers: @jeffkamo @mlworks
Changes

Declares flex-direction: row on the Arrange root selector

Todo

[x] Review tests

+1. Reviewed and tested.