text:
Parsing JSON with multiple representation in same attribute

I'm relatively new to Rust, and even more so to serde, so I'm having trouble finding out if this is even doable.
I have a JSON file which has two different representations in this form:
"coordinates": [           [             [               121.423364,               24.9913596             ],             [               121.4233327,               24.9912977             ],           ]         ]
and this:
"coordinates": [           [             121.4472492,             25.0052053           ],           [             121.4466457,             25.0028547           ]         ]
It shows that  it has two dimensions array and three dimensions arrays representing ways in the same attribute.
This makes the file is hard to serialize.
Below is the code that I implement
#[derive(Serialize, Deserialize, Debug)]
struct Geometry {
    #[serde(deserialize_with = "string_or_number", rename = "type")]
    geometry_type: Value,
    #[serde(default, skip_serializing_if = "Vec::is_empty", rename = "coordinates")]
    geometry_coor: Vec<Coordinates>,
    #[serde(default, skip_serializing_if = "Vec::is_empty", rename = "coordinates")]
    geometry_coor2: Vec<Vec<Coordinates>>
}

#[derive(Serialize, Deserialize, Debug)]
struct Coordinates {
    #[serde(deserialize_with = "string_or_number")]
    longitude: Value,
    #[serde(deserialize_with = "string_or_number")]
    latitude: Value,
}

fn string_or_number<'de, D>(de: D) -> Result<Value, D::Error>
    where D: serde::Deserializer<'de>
{
    let helper: Value = Deserialize::deserialize(de)?;

    match helper {
        Value::Number(n) => {
            println!("{:#?}", n.as_f64().unwrap().to_string());
            Ok(Value::Number(n))
        },
        Value::String(s) => Ok(json!(s)),
        _ => Ok(json!(null))
    }
}

And  I have trouble in struct Geometry which serialize the file of coordinates.
So does there have any ways that I can deal with this kind of form?

I would recommend using an untagged enum to represent a coordinate array that can be 2d or 3d.
Playground link

Nice!

authors: Tverous dtolnay

repo: serde-rs/json


text:
Serializer and Deserializer should be pure interface

For now the Serializer and Deserializer traits contain many functions, but many of them have default implementations. A problem is, the default implementations make too many assumption about the serializing protocol, probably based on json. Though them may be convenient for implementing a json serializer, or other text protocols, but most of them do not suit for a binary protocol. The point is, Serializer and Deserializer are so big, that when implementing a concrete serializer/deserializer it is quite possible to accidentally miss some functions. So it is better to remove the default implementations,    and make the Serializer and Deserializer traits a 'checklist', the compiler can help checking the implemention. In addition, the current default implementations can be moved to some JsonlikeSerializer or CommonTextSerializer sub-traits.

I agree. This "magic" has caused me some headache debugging, so I ended up replacing all of them manually.

+1. I think magic layers are more appropriate for Deserialize/Serialize sugar, which are types that many serde users need to interact with. The -er types are relatively rarely implemented, and harder for an author to get complete ambient test coverage of via their own client code, so sacrificing sugar for correctness feels appropriate.

I can get behind this. One downside though with making this always pure is that any new hint we add would trigger a major release, or we just add a default implementation for that method. Would everyone be okay with this?

@erickt adding a default implementation when adding a hint seems preferable to a major release. It's entirely backwards compatible this way, and formats which need the hinting can start using it immediately. Since this is all about getting rid of default impls, issues should be added to remove the default impl come the next major version.

source: gharchive/issue

authors: JohnHeitmann erickt jwilm lcy03406 oli-obk

repo: serde-rs/serde

license_type: permissive

license_source: bigquery


text:
Fix extract faces grayscale

What has been done
When activating to return the face in grayscale, an error occurs because it tries to convert from BGR to RGB, but the image is in grayscale.

How to test
Fixed to allow returning the face image in grayscale, to test you can use the following command:
faces = DeepFace.extract_faces(
    img_path = 'image.jpg',
    grayscale = True
)

LGTM

source: gharchive/pull-request

authors: ProgramadorArtificial serengil

repo: serengil/deepface

license: MIT

license_source: github-api


text:
Project pictures don't scale properly in smartphone mode

Hi Serg,
First of all, many thanks for your last commit, now the project images are perfectly inline if you add additional projects. But I realized another thing, when I updated the commits from 16 Nov 2020. It looks like the images don't scale in panorama mode anymore when you narrow the browser window or open it on a smartphone. I also tried a fresh install with the last yourfolio download with the standard pictures. It's the same.  Maybe you missed something when yo restructured the styles?
Kind regards,
Mark

Hello Mark,
Nice to meet you and I am glad to help!
Also, thank you for your attention to this theme! It's very helpful for improving it.
Not sure if I understand you correctly.
Could you please send me a screenshot that describes this bug?
Also please add info about size of viewport on which you explore this issue. It will help me to reproduce this on my side.
You could get size of your viewport by using this tool.
Thank you in advance!

Did you mean the case like this when you rotate a screen?

No, I meant if you make the browser window smaller for example. In previous versions the pictures changed in landscape mode. Since the update from 16.11.2020 they don’t resize properly.

Am 29.04.2021 um 13:07 schrieb Mark Walter @.***>:
No, I meant if you make the browser window smaller for example. In previous versions the pictures changed in landscape mode. Since the update from 16.11.2020 they don’t resize properly.

Am 29.04.2021 um 12:48 schrieb Sergey Furtak @.***>:
Did you mean the case like this when you rotate a screen?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Image0.png is the normal Browser view
Image1.png is before the update from 16.11.20 and
Image 2.png is from after the update from 16.11.20 where the pictures are not rendered in landscape mode anymore.
Von meinem iPhone gesendet

Am 29.04.2021 um 13:12 schrieb Mark Walter @.***>:
No, I meant if you make the browser window smaller for example. In previous versions the pictures changed in landscape mode. Since the update from 16.11.2020 they don’t resize properly.

Am 29.04.2021 um 13:07 schrieb Mark Walter @.***>:
No, I meant if you make the browser window smaller for example. In previous versions the pictures changed in landscape mode. Since the update from 16.11.2020 they don’t resize properly.

Am 29.04.2021 um 12:48 schrieb Sergey Furtak @.***>:
Did you mean the case like this when you rotate a screen?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

<image0.png>
<image1.png>
<image2.png>

@Serg I am sorry, I hope it works now:
This is the view with the normal browser width in both version of yourfolio, before the update from 16.11.2020 and after:
Before the update from 16.11.2020, the pictures are rendered in landscape mode when you make the browser window smaller or watch it on a smartphone:
And this is how the pictures look like after the update from 16.11.2020 in the same browser size:
All the best,
Mark

Am 30.04.2021 um 18:06 schrieb Sergey Furtak @.***>:

@MUWalter, seems like your images weren't uploaded.
Could you please upload this again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@serg I update my last post, I hope you can see my screenshots now and understand what I mean.

@MUWalter thank you for details!
It will help me with reproducing on my side
I will think about it and get back with results

Thank you very much, I am glad I could help!

Am 01.05.2021 um 12:42 schrieb Sergey Furtak @.***>:

@MUWalter thank you for details!
It will help me with reproducing on my side
I will think about it and get back with results
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello Mark,
It was weird issue available only in Safari browser.
Now it fixed in this commit and pushed to master branch.
Please check and confirm if it works on your side.
Thanks!

Cool, so far it looks like it worked. Cheers!

Am 13.05.2021 um 21:41 schrieb Sergey Furtak @.***>:
Hello Mark,
It was weird issue available only in Safari browser.
Now it fixed in this commit https://github.com/serg/yourfolio/commit/acaa8f1957e12fbd2ad872c2fcf0eaac3ed5c016 and pushed to master branch.
Please check and confirm if it works on your side.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/serg/yourfolio/issues/10#issuecomment-840788637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHEVHTYILS2GIV4ETBTMYF3TNQTPZANCNFSM43ZM3WFA.

authors: MUWalter serg

repo: serg/yourfolio


text:
Can shift+enter on a binary field open an external hex editor?

Like WinSCP, I can open a remote file in a local external text editor. After editing, the changes goes to a temp file and the temp file is uploaded to remote.
I would like to have dbeaver launching HxD or any other configurable editor, the changes should be written back to the database.
#2159  and #2138 can be superseded by this ticket.

I like this

authors: serge-rider yanOnGithub

repo: serge-rider/dbeaver


text:
JSX support in Sublime Text 3?

Hi,
Just saw the tweet about .jsx support, tried it in Sublime Text 3 and tags aren't expanding when I try it within a React render method. I'm using the JavaScript (Babel) syntax, could that be the reason it's not working? Do we have to write the render method in a specific way with a specific syntax to make it work?
Thanks!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10344355-jsx-support-in-sublime-text-3?utm_campaign=plugin&utm_content=tracker%2F35867&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F35867&utm_medium=issues&utm_source=github).

+1

I assume you’re trying to use Tab key: https://github.com/sergeche/emmet-sublime#tab-key-handler

+1

+2

@sergeche Indeed that was the problem, using ctrl+e works fine and changes span.bar as  for example.
Just to make sure, there is really no way of having the tab completion?
Thanks again for the amazing work on Emmet, can't live without it :wink:

You can enable it as described in link above, but you’ll loose your native JS snippets

Alright, well using ctrl-e is good enough, thanks for the help!

+1

authors: e2goon falzhobel harrisgeo jeroveoo rashthedude sergeche

repo: sergeche/emmet-sublime

license: mit


text:
agilie/AGInterfaceInteraction

AGInterfaceInteraction - library performs interaction with UI interface
Language - Swift

https://github.com/vsouza/awesome-ios/pull/2324

repo: serhii-londar/awesome-ios


text:
Ignore end of line prettier errors

Override the default lint rule for End of Line introduced in Prettier v2.0.0 (i.e. revert to "auto" rather than forcing "LF")
While there are other options to address this, this change simply suppresses the "error" rather than touching every single line within 70+ files
See prettier options for more info
Perhaps we could find a good suitable time to switch most/all of the linting rules over to the default, but I fear it will make it quite messy to trace the history of commits if a lint change touches every line in every file...
Signed-off-by: Gareth Hancock gazhank@gmail.com

npm run lint generates a lot of noise.  For example:
C:\Git\node-serialport\test\initializers\test-config.js
   1:53  error  Delete `␍`  prettier/prettier
   2:1   error  Delete `␍`  prettier/prettier
   3:61  error  Delete `␍`  prettier/prettier
   4:63  error  Delete `␍`  prettier/prettier
   5:64  error  Delete `␍`  prettier/prettier
   6:37  error  Delete `␍`  prettier/prettier
   7:85  error  Delete `␍`  prettier/prettier
   8:6   error  Delete `␍`  prettier/prettier
   9:30  error  Delete `␍`  prettier/prettier
  10:4   error  Delete `␍`  prettier/prettier
  11:2   error  Delete `␍`  prettier/prettier

✖ 6990 problems (6990 errors, 0 warnings)
  6990 errors and 0 warnings potentially fixable with the `--fix` option.

I'm pretty sure this isnt down to the way I've cloned the repository on Windows as I don't get these errors for other reps I use.  But if this i just a problem for me then I'll see if I can change my local config

I wonder if my windows machine defaulted to some old school setting when I did a complete rebuild a few weeks ago :-(
I hadn't checked the linting on this repo before so maybe hadn't noticed.  Hopefully this is just a local config problem :-)

Sorry it looks like a local config issue from the rebuild
fixed with:
git config --global core.autocrlf false
git add --renormalize .

I'll close this, and see if the Lerna update needs to be reworked

repo: serialport/node-serialport


text:
Opt-in to TraceId enrichment for ASP.NET Core 5.0 logs - support in Serilog.Sinks.MSSqlServer

Please add TraceId support into the SQL Server sink.
This is related to the following issue:
https://github.com/serilog/serilog-aspnetcore/issues/207
The TraceId was changed in .Net Core 5 and the TraceId is no longer included in the logs. Issue #207 was fixed, but each sink must implement the change. It looks like several sinks have been updated already, but Serilog.Sinks.MSSqlServer still doesn't have support. This is important to us, since we user the TraceId extensively.

List the names and versions of all Serilog packages used in the project:

Serilog:
Serilog.Sinks.MSSqlServer
Serilog.Enrichers.AspnetcoreHttpcontext
Serilog.Exceptions

Target framework and operating system:
[ ] .NET 6

Thanks you!

There is now a preview version 6.5.0-dev-00060 of the MSSQL sink up on nuget.org (https://www.nuget.org/packages/Serilog.Sinks.MSSqlServer/6.5.0-dev-00060) containing support for TraceId and SpanId.
We would appreciate everyone who tries it out and gives us some feedback.

repo: serilog-mssql/serilog-sinks-mssqlserver


text:
cppflow2: declare inline for header only implementation

As #73 suggested, non-template function definition in header needs to be declared as inline to avoid ODR violation. This requires changes in both the auto-generated header and the manually written headers.
This may not be important if we are going to separate the implementation into cpp files, but we need to address them if we want to keep the library header only.

This has caused me issues as well. For the time being, I just manually added the inline keyword to all the necessary methods in my local copy, but this should probably be implemented.

Yes, it's true, we should do something about.
I don't know if we should continue with a header only structure or move the implementations into a cpp files. At the beginning I started the code as a header-only library as I though I would require lot of templated functions, but now is not that the case.
I don't know, perhaps we should switch...

I am working on a large project with the constraint of using c ++ 14. Most companies have old Ubuntu 16 in production that are not natively compatible with c ++ 17.
Inline variables are implemented from c ++ 17, I chose to switch to the cpp implementation with a static lib compilation to avoid adding cpp to the project files.

@serizba There are too many people complaining this. Maybe I will add the missing inline declaration to temporarily solve this for now. It seems it is the easiest way to do.

Yes, we have to address this.
But I am not sure on whether to stick with the header-only implementation or switch definitions to cpp files.

I am not sure either.... In my opinion, it is more like a lib design choice. Both have their own pros and cons. The PR #81 chose to keep header only structure simply because it took the minimum effort to solve this problem. In other words, it is not recommending header-only is better.

I think that for the moment I will stick with the header-only implementation and I will accept PR #81.

I already made the effort to convert from header to .Cpp/. H implementation.
Switching to inline implementation will not break c++ 14 compatibility?

@khaled-besrour To be honest, I am against moving back to C++ 14 (sorry) because we are considering conditionally importing C++20 features (std::span).

As the proverb say:

There is nothing more permanent than a temporary solution.

authors: khaled-besrour ljn917 rustom-ichhaporia serizba

repo: serizba/cppflow


text:
Alias improvements

Changelog
Changed

Users get alias /user/:id/:username to be consistent with the rest (and to possibly allow to change username).
Attachments get alias /attachment/:id.
Discussions get alias /:prefix/:id where :prefix is determined by the object the discussion is tied to.
Blog posts get alias /blog/:id
Revisions get the same prefix as their repository

Internal

Clean up Normalizer module

Open TODOs

[ ] We still have some entities that don't have a good title (e.g. revisions, exercises, discussions...). If I find a simple way to map the content to some keywords, I do that. If not, they probably just receive a default title (e.g. translated "article revision") to improve the aliases a little bit.

Draft because of open TODO and failing CI

Draft because of open TODO and failing CI

Failing CI due to prettier failed... :smile:

authors: inyono kulla


text:
🛑 sgm2.serverssh.net is down

In 0d463d8, sgm2.serverssh.net (sgm2.serverssh.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sgm2.serverssh.net is back up in 4a4fab0.

repo: serversshnet/server-status


text:
⚠ degrpc.serverssh.us has degraded performance

In 1ba31f3, degrpc.serverssh.us (http://degrpc.serverssh.us/) experienced degraded performance:

HTTP code: 200
Response time: 16236 ms

Resolved: degrpc.serverssh.us performance has improved in c6d8679.


text:
🛑 sg1socks.ipservers.xyz is down

In 9aa45f6, sg1socks.ipservers.xyz (sg1socks.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sg1socks.ipservers.xyz is back up in c565adb after 35 minutes.

repo: serversshnet/uptime


text:
🛑 us-ray.ipservers.xyz is down

In e764463, us-ray.ipservers.xyz (us-ray.ipservers.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: us-ray.ipservers.xyz is back up in b0439ae after 56 minutes.


text:
Customize navbar at Runtime.

Summary
Toggle navbar and footer from dark to light mode at runtime.
Details
Toggle between dark/light navigation bar and footer at runtime using the Toggle radio button located at the navigation bar Dropdown menu.
To achieve this task, there are two technical approaches, an easy one and a more complicated one:

Instead of using the class: navbar-themed, use the classes: navbar-dark bg-dark (or navbar-light bg-light) and just toggle the values of the Bootstrap CSS variables: --bs-dark and --bs-light, accordingly. The change of these variables should have the desired effect. Also, modify the link colors of the navbar and footer by using an appropriate Bootstrap CSS variable.
Override the navbar-themed mixin so that it uses the value of a Bootstrap CSS variable (e.g. the --bs-dark and --bs-light) instead of a Sass variable. It must be tested if it is possible to realize the second approach.

Acceptance criteria

[ ] If there are issues with chosen approach (for example some Bootstrap CSS variables are not supported), then document it a Word file "Support of Bootstrap CSS variables" for future reference.
[ ] Manual tests.
[ ] UI Customizability is preserved

Additional context
Add any other context or screenshots about the task.

Relevant for the Backend: for a light navigation bar, set the following CSS variables:
--oscm-navbar-color:   rgba(--oscm-white, 0.8);
--oscm-navbar-links-color: rgb(var(--oscm-primary));

Close till replacement of rgb with hsl values. Customize navbar as described in above comment.

repo: servicecatalog/oscm


text:
arm64 build failure: could not find system library 'openssl' required by the 'openssl-sys' crate

https://github.com/servicer-labs/servicer/actions/runs/6064765510/job/16453515976#step:4:724
A package update introduced a dependency on openssl-sys. This fails to build on the Github action for an arm64 release.
   Compiling openssl-sys v0.9.92
   Compiling futures-util v0.3.28
error: failed to run custom build command for `openssl-sys v0.9.92`

Caused by:
  process didn't exit successfully: `/target/release/build/openssl-sys-39820fd7b4b38d98/build-script-main` (exit status: 101)

--- stderr
  Package openssl was not found in the pkg-config search path.
  Perhaps you should add the directory containing `openssl.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'openssl' found

  --- stderr
  thread 'main' panicked at '

  Could not find directory of OpenSSL installation, and this `-sys` crate cannot
  proceed without this knowledge. If OpenSSL is installed and this crate had
  trouble finding it,  you can set the `OPENSSL_DIR` environment variable for the
  compilation process.

  Make sure you also have the development packages of openssl installed.
  For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.

  If you're in a situation where you think the directory *should* be found
  automatically, please open a bug at https://github.com/sfackler/rust-openssl
  and include information about your system as well as this message.

  $HOST = x86_64-unknown-linux-gnu
  $TARGET = aarch64-unknown-linux-gnu
  openssl-sys = 0.9.92

Fixed by uninstalling checker crate. This one was mistakenly installed.

repo: servicer-labs/servicer


text:
Winit 0.24

Hi.
This is pretty much the same as https://github.com/servo/surfman/pull/179 but just upgrading to v0.24.0
Regards,
PECastro

I pushed some more fixes to make CI pass.

@bors-servo r+

:pushpin: Commit ed34735 has been approved by jdm

:hourglass: Testing commit ed34735084b278b48f72460bd7961e407ee4e914 with merge 82c1790cef79ba869ac1c88f72236aa4ab6dfac3...

:sunny: Test successful - checks-travis
Approved by: jdm
Pushing 82c1790cef79ba869ac1c88f72236aa4ab6dfac3 to master...

authors: bors-servo jdm pecastro

repo: servo/surfman


text:
capgen error in /static/uploads/ when running the index database

`static/uploads$ python index_database.py
Traceback (most recent call last):
File "index_database.py", line 3, in
from capgen import CaptionGenerator
ModuleNotFoundError: No module named 'capgen'
`

@LinuxBeaver  maybe this folder don't have this file .check your path

authors: LinuxBeaver NeekHua

repo: sethuiyer/Image-to-Image-Search


text:
Feature Request: Ability to set minimum required battery percentage

Since SYM is intended for end users to setup, it'd great if we can incorporate a battery check feature into SYM process. This addition would help users avoid interruptions due to low battery levels, contributing to a smoother user experience. Whether the computer was shipped with low battery, organizations need to deploy multiple apps, or FileVault processes are time-consuming, this feature could save users from potential interruptions
Is your feature request related to a problem? Please describe.
Nope.
Describe the solution you'd like
An option for us to set minimum required battery percentage. By not meeting that required percentage, user will be prompted a message (with icon?) to connect their mac to a power source. Preferably at the very beginning of the SYM process, where the timer is counting down for 60 seconds right now.
pmset -g batt | grep -Eo "\d+%" | cut -d% -f1 can provide the percentage.
system_profiler SPPowerDataType | grep "Connected" | awk '{print $2}' can provide the status if computer is connected to power source or not.
Describe alternatives you've considered
Add a custom script to run before SYM script starts. OR add a function within SYM script to check power connection before starting the script.
Additional context

Happy New Year, @arnoldtaw!
Excellent idea! (I'm confident Graham has some code we could copy-pasta.)

What about ensuring AC power is connected?
https://github.com/grahampugh/erase-install/blob/main/erase-install.sh#L574-L654

That logic seems right. Not sure if it's a better idea to spin up a new dialog process before the SYM process starts or integrated as part of the SYM, where the count down is. Do you plan to add this in the future version of SYM? If so, would love to request the ability to set minimum % too 😅

Updated lines:
https://github.com/grahampugh/erase-install/blob/main/erase-install.sh#L632-L712

@arnoldtaw:
Please test 1.15.0-b11.

Thanks @dan-snelson
I wasn't sure if this will be added so I added myself something similar.
The following will
(1) use swiftDialog
(2) allow admin to set preferred %
(3) allow user to connect to power source and continue (instead of ending the process)
function acPowerCheck () {
    required_battery_percentage=60
    current_battery_percentage=$(pmset -g batt | grep -Eo "\d+%" | cut -d% -f1)
    current_power=null

    check_ac_status () {
        if /usr/bin/pmset -g ps | /usr/bin/grep "AC Power" > /dev/null ; then
            current_power="Yes"
        fi
    }

    # Initial Check (mostly for desktop type device)
    check_ac_status

    if [[ $current_power == "Yes" ]]; then
        updateScriptLog "PRE-FLIGHT CHECK: Device connected to AC power."
    else
        updateScriptLog "PRE-FLIGHT CHECK: Device is not connected to AC power."
        # IF low battery, display message and loop
        if [[ $current_battery_percentage -lt $required_battery_percentage ]]; then
            # Does not meet required %
            updateScriptLog "PRE-FLIGHT CHECK: Current battery ($current_battery_percentage %) is lower than required battery ($required_battery_percentage %). Prompting to connect to AC power."

            /usr/local/bin/dialog --title "Waiting for AC Power Connection" \
                --icon "SF=powerplug.fill,colour=red,bgcolor=none" \
                --message "Please connect your Mac to an AC power adapter. \n\nAC power is required to continue." \
                --button1text "Continue" \
                --button1disabled \
                --ontop \
                --quitkey d \
                --blurscreen \
                --position center \
                --commandfile "/var/tmp/deployment_power_check.log" & dialogPID=$!

            until [ "$current_power" = "Yes" ]; do
                # Run AC power checks
                sleep 1
                check_ac_status
                updateScriptLog "PRE-FLIGHT CHECK: Waiting for AC power connection"
                sleep 1
            done
            updateScriptLog "PRE-FLIGHT CHECK: AC power connected!"
            /bin/echo "icon: SF=powerplug.fill,colour=green,bgcolor=none" >> /var/tmp/deployment_power_check.log
            sleep 2
            /bin/echo "quit: " >> /var/tmp/deployment_power_check.log
        else
            # Meet required %
            updateScriptLog "PRE-FLIGHT CHECK: Current battery ($current_battery_percentage %) is equal or more than required battery ($required_battery_percentage %)."
        fi
    fi
}

Thanks, @arnoldtaw.
You’re invited to submit a PR; have you had a chance to test your code with the latest 1.15.0 ?
(Just skimming while AFK, dialog has yet to be installed.)

@arnoldtaw:
Your Item No. 3 above inspired me; please take a look at 1.15.0-b16:

Addressed in SYM 1.15.0.

authors: arnoldtaw dan-snelson

repo: setup-your-mac/Setup-Your-Mac


text:
Concurrent map write in ssh agent code

herd run app=xxx role=yyy -- uptime
Waiting (0s/1m0s)... 0/8 done, 8 in progress, 0 ok, 0 fail, 0 errorfatal error: concurrent map writes

goroutine 26 [running]:
github.com/seveas/herd/ssh.(*agent).SignersForPath(0x1400004c960, {0x1401b5f3a70, 0x26})
        /private/tmp/herd-20241210-74971-uoime0/herd-0.13.1/ssh/agent.go:271 +0x314
github.com/seveas/herd/ssh.(*Executor).connect.(*agent).SignersForPathCallback.func3()
        /private/tmp/herd-20241210-74971-uoime0/herd-0.13.1/ssh/agent.go:237 +0x30
golang.org/x/crypto/ssh.publicKeyCallback.auth(0x0?, {0x1401bd882e0, 0x20, 0x20}, {0x1400052212e, 0x7}, {0x10208abc0, 0x14000a48000}, {0x102082080, 0x140001704c0}, ...)
        /Users/oliikit/Library/Caches/Homebrew/go_mod_cache/pkg/mod/golang.org/x/crypto@v0.28.0/ssh/client_auth.go:308 +0x54
golang.org/x/crypto/ssh.(*connection).clientAuthenticate(0x1400af7ed00, 0x14000b80270)
        /Users/oliikit/Library/Caches/Homebrew/go_mod_cache/pkg/mod/golang.org/x/crypto@v0.28.0/ssh/client_auth.go:72 +0x2c8
golang.org/x/crypto/ssh.(*connection).clientHandshake(0x1400af7ed00, {0x1401bc86000, 0xe}, 0x14000b80270)
        /Users/oliikit/Library/Caches/Homebrew/go_mod_cache/pkg/mod/golang.org/x/crypto@v0.28.0/ssh/client.go:113 +0x274
golang.org/x/crypto/ssh.NewClientConn({0x102092ed8, 0x14000bb4010}, {0x1401bc86000, 0xe}, 0x14000130820)
        /Users/oliikit/Library/Caches/Homebrew/go_mod_cache/pkg/mod/golang.org/x/crypto@v0.28.0/ssh/client.go:83 +0x110
golang.org/x/crypto/ssh.Dial({0x10198475c?, 0x0?}, {0x1401bc86000, 0xe}, 0x14000130820)
        /Users/oliikit/Library/Caches/Homebrew/go_mod_cache/pkg/mod/golang.org/x/crypto@v0.28.0/ssh/client.go:181 +0x48
github.com/seveas/herd/ssh.(*Executor).connect.func2()
        /private/tmp/herd-20241210-74971-uoime0/herd-0.13.1/ssh/executor.go:135 +0x48
created by github.com/seveas/herd/ssh.(*Executor).connect in goroutine 40
        /private/tmp/herd-20241210-74971-uoime0/herd-0.13.1/ssh/executor.go:133 +0x4e0

This happens because any thread can write to the signersByPath map. When rewriting the agent code this must be fixed.

Fixed indirectly in #74

repo: seveas/herd


text:
🛑 Severn Bronies website is down

In 05b02d6, Severn Bronies website (https://severnbronies.co.uk) was down:

HTTP code: 502
Response time: 779 ms

Resolved: Severn Bronies website is back up in cac3fed.

repo: severnbronies/status


text:
dshUI: Implement flag for colorize.sh

Implement the following flag so colorize.sh can be run from dshUI
dshUI --colorize | -c <FILE_PATH> <COLOR_CODE> <REGEX>...
This will run
dshUI/colorize.sh <FILE_PATH> <COLOR_CODE> <REGEX>...

Resolved in commit a64ee3ff6d081801f9fcd0a70d30f28b2d9fc434

repo: sevidmusic/DarlingDataManagementSystem


text:
Реализация очередей и мелкие изменения

Важные изменения

Переименован вспомогательный модуль: Карта -> Карты
Переименован вспомогательный модуль: Множество -> Множества
Переименован вспомогательный модуль: Список -> Списки

Изменения:

ИтераторМассив теперь СписокИтераторМассив, новый  ИтераторМассив теперь обёртка над СписокИтераторМассив, но реализующий только контракт Итератора, а не СписокИтератора
Списки теперь возращают СписокИтераторМассив
Синхронизированные вьюхи коллекций теперь пробрасывают оригинальные исключения наверх

Добавлено:

Интерфейсы для новых типов коллекций Очереди
Коллекция ОчередьМассив - Простая FIFO очередь
Коллекция ПриоритетнаяОчередь - Очередь с компаратором вверху которой всегда находится самый приоритетный элемент
Коллекция ОчередьОтложенных - Частный случай приоритетной очереди, элементы которой должны реализовывать интерфейс "Отложенный", и возвращаются только когда наступает их время
Добавлен хелпер "Массивы.ИзЭлементов()" для быстрого создания массивов
Добавлен хелпер "Соответствия.ИзЭлементов()" для быстрого создания соответствий
Добавлен хелпер "Соответствия.Скопировать()" для быстрого копирования соответствий

Документация:

В README оставлено только общее описание и диаграмма классов
Диагарммы классов разделены по родительским интерфейсам
Описание программного интерфейса разбито для каждого интерфейса отдельно и разложено в разделе /doc

@coderabbitai review

@coderabbitai говори по русски

repo: sfaqer/collectionos


text:
Data movement workload

Put description here...
Code-Reviewer Section
The general guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.

[ ] The PR has a description, explaining both the problem and the solution.
[ ] The description mentions which forms of testing were done and the testing seems reasonable.
[ ] Every function/class/actor that was touched is reasonably well documented.

For Release-Branches
If this PR is made against a release-branch, please also check the following:

[ ] This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or master if this is the youngest branch)
[ ] There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

I've committed this through a different path.

authors: sfc-gh-ajbeamon sfc-gh-chliu

repo: sfc-gh-ajbeamon/foundationdb


text:
🛑 CatamarcaCapital is down

In 6ee9071, CatamarcaCapital (https://www.catamarcaciudad.gob.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CatamarcaCapital is back up in 6e5ff1d.

repo: sfvc/upptime


text:
Extra .exe suffix on windows, possible regression in 0.11.x

I'm updating Bazel's use of rules_graalvm from 0.10.3 to 0.11.1, and from GraalVM 20.0.2 to 21.0.2, and am seeing a failure where it looks like the handling of executable_name had changed on windows:
ERROR: C:/b/ufipaqxb/execroot/_main/_tmp/c7869347f3b0f58b8b3d901d6cb2632e/root/fqvxxemw/external/bazel_tools/tools/java/runfiles/BUILD:12:13: Compiling Java headers external/bazel_tools/tools/java/runfiles/libauto_bazel_repository-hjar.jar (1 source file) failed: missing input file '@@rules_java~~toolchains~remote_java_tools_windows//:java_tools/turbine_direct_graal.exe'

The build logs contain
========================================================================================================================
GraalVM Native Image: Generating 'turbine_direct_graal.exe' (executable)...
========================================================================================================================
...
 - '-H:Name' (alternative API option(s): -o turbine_direct_graal.exe; origin(s): command line)
...
Produced artifacts:
 C:\b\ykmfm4bk\execroot\_main\bazel-out\x64_windows-fastbuild\bin\src\java_tools\buildjar\java\com\google\devtools\build\java\turbine\turbine_direct_graal.exe.exe (executable)

The usage of native_image is configuring a windows-specific path with the .exe suffix. It's overriding the defaults to drop the -bin suffix that's added:
https://github.com/bazelbuild/bazel/blob/4420fffb00794405a334d55c9c5c53669a217f05/src/java_tools/buildjar/java/com/google/devtools/build/java/turbine/BUILD#L29-L34
native_image(
    name = "turbine_direct_graal",
    executable_name = select({
        "@bazel_tools//src/conditions:windows": "%target%.exe",
        "//conditions:default": "%target%",
    }),

It looks like an extra suffix is being added somewhere, so it's resulting in .exe.exe on windows.
I wondered if this is related to https://github.com/sgammon/rules_graalvm/pull/217, but from the build logs it looks like native-image is being invoked with -o turbine_direct_graal.exe.

I think I have worked around the windows-only failures I was seeing with
    executable_name = select({
-        "@bazel_tools//src/conditions:windows": "%target%.exe",
+        "@bazel_tools//src/conditions:windows": "%target%",
        "//conditions:default": "%target%",
    }),

I think the default value of the attribute has a similar select, so it still seems like there's an underlying issue here that could affect other users of rules_graalvm:
https://github.com/sgammon/rules_graalvm/blob/d6bde1f91fb5c59faa46ef18d54b7a187e6295a5/graal/graal.bzl#L48-L51

@cushon Thanks for reporting. I intend to look into this today, a bit swamped but I should be able to get to it quickly

Hey @cushon,
Firstly, thanks for your patience and workaround. "Today" turned into two weeks before I even noticed.
The current behavior in the rules is to treat executable_name as the name of the bin only, so that the rules can account for the exe extension (as you've noticed). This is something we've inherited from the older rules_graal.
In the original behavior, the binary name was set unconditionally to %target%-bin, which made it difficult to customize. As a backward-compatible change, I added the executable_name attribute and defaulted it to that same pattern.
The original rules_graal never supported Windows, so when I added Windows support, to preserve the behavior of that attribute, I elected to manage the .exe extension for the user. It is at this point the select was added.
The rule you have cited above (under graal/graal.bzl), is the "compat" entrypoint, which tries to maintain compatibility with the older rules_graal. The newer entrypoint is at graalvm/graalvm.bzl. Subtle, I know, and in the next major version I may consider cleaning that up and merging into just the modern entrypoint.
That being said, the modern entrypoint does this same thing:
https://github.com/sgammon/rules_graalvm/blob/024d4e38e9a656a70f4b5f6f696d8582f6213de7/graalvm/nativeimage/rules.bzl#L28-L31
https://github.com/sgammon/rules_graalvm/blob/024d4e38e9a656a70f4b5f6f696d8582f6213de7/graalvm/nativeimage/rules.bzl#L66-L68
I suppose we could:

Check for an existing .exe postfix and avoid adding one if it is doubled up
This would be a change in behavior that is technically backwards incompatible, but I don't think anyone wants two .exe extension in their filename, so it's probably fine.

Stop managing the extension altogether
We could leave it up to callers, but that would require callsites to be updated and it would break expectations on Windows as they exist currently.

Personally I think approach 1 is fine, but I wanted to get your take first in case I might be missing something. @fmeum if you have any thoughts they are welcome.

Thanks for digging in to this! The approach 1 you described sounds fine to me too.
For what it's worth I'm still slightly confused about where the duplicate .exe is coming from. I would have thought the user-provided executable_name here overrode the default, and for there to be one select(). Is the duplicate .exe definitely happening in rules_graal, and not as a result of the native-image CLI automatically adding the .exe suffix on windows?

Oh, I see what you mean now. That's a good question, I'll double check.

authors: cushon sgammon


text:
Update scala-library, scala-reflect to 2.12.14

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.12.13 to 2.12.14.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-patch

Superseded by #221.

repo: shadaj/scalapy


text:
chore: Update to Next14

Updates this repo to use Nextjs 14
Removes workaround for prisma as it is fixed now - https://github.com/prisma/prisma/issues/16117
Adds workaround for Image component in mdx files for next after 13.5 as suggested in https://github.com/hashicorp/next-mdx-remote/issues/405
Bumps all dependancies except a few content layer /mdx ones
Replaces deprecated domains in next.config.js and with remote domains
Moves themeColour in viewport rather than metadata ( change in next14)

Closes: https://github.com/shadcn-ui/taxonomy/issues/251 https://github.com/shadcn-ui/taxonomy/issues/192

Thank you

authors: IsaacCDHall VaniaPopovic

repo: shadcn-ui/taxonomy


text:
[Bug] ComboBox breaks inside Dialogue

When using ComboBox inside Dialog component with the modal: true (default value), clicking on element inside PopoverTrigger causes the whole dialog to rerender, closing PopoverContent in the process. With modal:false it works as expected. Because Popover renders outside the dialog tree, it's considered an outside interaction.
I wonder if this is the expected behaviour. It would be nice to make ComboBox work inside modal:true Dialog as well.
Example code:
    <Dialog>
      <DialogTrigger>

test

      </DialogTrigger>
      <DialogContent className="">
        <ComboBox placeholder="" onChange={() => null} />
      </DialogContent>
    </Dialog>
  );

@seenyat have you found any solution?

@vimtor
I fixed it by wrapping my PopoverContent (which is being used by ComboBox) in its own FocusScope and DismissableLayer (suggested in this issue https://github.com/radix-ui/primitives/issues/922#issuecomment-948366132). That fixed my problem with unexpected rerender.
 React.ElementRef<typeof PopoverPrimitive.Content>,
 React.ComponentPropsWithoutRef<typeof PopoverPrimitive.Content>
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
 <PopoverPrimitive.Portal>
   <FocusScope asChild loop trapped>
     <DismissableLayer>
       <PopoverPrimitive.Content
         ref={ref}
         align={align}
         sideOffset={sideOffset}
         className={cn(
           "...",
           className
         )}
         {...props}
       />
     </DismissableLayer>
   </FocusScope>
 </PopoverPrimitive.Portal>
));```

@vimtor I fixed it by wrapping my PopoverContent (which is being used by ComboBox) in its own FocusScope and DismissableLayer (suggested in this issue radix-ui/primitives#922 (comment)). That fixed my problem with unexpected rerender.
const PopoverContent = React.forwardRef<
 React.ElementRef<typeof PopoverPrimitive.Content>,
 React.ComponentPropsWithoutRef<typeof PopoverPrimitive.Content>
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
 <PopoverPrimitive.Portal>
   <FocusScope asChild loop trapped>
     <DismissableLayer>
       <PopoverPrimitive.Content
         ref={ref}
         align={align}
         sideOffset={sideOffset}
         className={cn(
           "...",
           className
         )}
         {...props}
       />
     </DismissableLayer>
   </FocusScope>
 </PopoverPrimitive.Portal>
));

I've tried this but unfortunately not working! Do you have any other suggestions for me to resolve this issue? Thank you

Hi @hafijAsadMVN, to be honest, I don't know what did the trick for me, as I tried different things I saw in various GitHub issues. Let me copy the dialog.tsx components here to see if it works for you.
"use client";

import * as React from "react";
import * as DialogPrimitive from "@radix-ui/react-dialog";
import { X } from "lucide-react";

import { cn } from "@/lib/utils";

const Dialog = ({ open, ...props }: DialogPrimitive.DialogProps) => {
  return <DialogPrimitive.Root open={open} {...props} />;
};
Dialog.displayName = DialogPrimitive.Dialog.displayName;

const DialogTrigger = DialogPrimitive.Trigger;

const DialogPortal = ({ className, children, ...props }: DialogPrimitive.DialogPortalProps) => (
  <DialogPrimitive.Portal className={cn(className)} {...props}>

{children}

  </DialogPrimitive.Portal>
);
DialogPortal.displayName = DialogPrimitive.Portal.displayName;

const DialogOverlay = React.forwardRef<
  React.ElementRef<typeof DialogPrimitive.Overlay>,
  React.ComponentPropsWithoutRef<typeof DialogPrimitive.Overlay>
>(({ className, ...props }, ref) => (
  <DialogPrimitive.Overlay
    ref={ref}
    className={cn(
      "fixed inset-0 z-50 overflow-y-scroll max-h-screen scrollbar-hide sm:py-8 grid place-items-center bg-black/20 backdrop-blur-sm transition-all duration-100 data-[state=closed]:animate-out data-[state=closed]:fade-out data-[state=open]:fade-in",
      className
    )}
    {...props}
  />
));
DialogOverlay.displayName = DialogPrimitive.Overlay.displayName;

const DialogContent = React.forwardRef<
  React.ElementRef<typeof DialogPrimitive.Content>,
  React.ComponentPropsWithoutRef<typeof DialogPrimitive.Content>
>(({ className, children, ...props }, ref) => (
  <DialogPortal>
    <DialogOverlay>
      <DialogPrimitive.Content
        ref={ref}
        onPointerDownOutside={(event) => event.preventDefault()}
        onInteractOutside={(event) => event.preventDefault()}
        className={cn(
          "relative z-50 gap-4 rounded-b-lg border bg-background p-6 shadow-lg animate-in data-[state=open]:fade-in-90 data-[state=open]:slide-in-from-bottom-10 sm:max-w-lg sm:rounded-lg sm:zoom-in-90 data-[state=open]:sm:slide-in-from-bottom-0",
          className
        )}
        {...props}
      >
        {children}
        <DialogPrimitive.Close className="absolute right-4 top-4 rounded-sm opacity-70 ring-offset-background transition-opacity hover:opacity-100 focus:outline-none focus:ring-2 focus:ring-ring focus:ring-offset-2 disabled:pointer-events-none data-[state=open]:bg-accent data-[state=open]:text-muted-foreground">
          <X className="h-5 w-5" />
          Close
        </DialogPrimitive.Close>
      </DialogPrimitive.Content>
    </DialogOverlay>
  </DialogPortal>
));
DialogContent.displayName = DialogPrimitive.Content.displayName;

const DialogHeader = ({ className, ...props }: React.HTMLAttributes<HTMLDivElement>) => (

);
DialogHeader.displayName = "DialogHeader";

const DialogFooter = ({ className, ...props }: React.HTMLAttributes<HTMLDivElement>) => (

);
DialogFooter.displayName = "DialogFooter";

const DialogTitle = React.forwardRef<
  React.ElementRef<typeof DialogPrimitive.Title>,
  React.ComponentPropsWithoutRef<typeof DialogPrimitive.Title>
>(({ className, ...props }, ref) => (
  <DialogPrimitive.Title
    ref={ref}
    className={cn("text-lg font-semibold leading-none tracking-tight", className)}
    {...props}
  />
));
DialogTitle.displayName = DialogPrimitive.Title.displayName;

const DialogDescription = React.forwardRef<
  React.ElementRef<typeof DialogPrimitive.Description>,
  React.ComponentPropsWithoutRef<typeof DialogPrimitive.Description>
>(({ className, ...props }, ref) => (
  <DialogPrimitive.Description ref={ref} className={cn("text-sm text-muted-foreground", className)} {...props} />
));
DialogDescription.displayName = DialogPrimitive.Description.displayName;

export { Dialog, DialogTrigger, DialogContent, DialogHeader, DialogFooter, DialogTitle, DialogDescription };

@vimtor I fixed it by wrapping my PopoverContent (which is being used by ComboBox) in its own FocusScope and DismissableLayer (suggested in this issue radix-ui/primitives#922 (comment)). That fixed my problem with unexpected rerender.
const PopoverContent = React.forwardRef<
 React.ElementRef<typeof PopoverPrimitive.Content>,
 React.ComponentPropsWithoutRef<typeof PopoverPrimitive.Content>
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
 <PopoverPrimitive.Portal>
   <FocusScope asChild loop trapped>
     <DismissableLayer>
       <PopoverPrimitive.Content
         ref={ref}
         align={align}
         sideOffset={sideOffset}
         className={cn(
           "...",
           className
         )}
         {...props}
       />
     </DismissableLayer>
   </FocusScope>
 </PopoverPrimitive.Portal>
));

I've tried this but unfortunately not working! Do you have any other suggestions for me to resolve this issue? Thank you

I'm facing the same issue but that solution didn't worked. Did you solved it?

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

@vimtor I fixed it by wrapping my PopoverContent (which is being used by ComboBox) in its own FocusScope and DismissableLayer (suggested in this issue radix-ui/primitives#922 (comment)). That fixed my problem with unexpected rerender.
const PopoverContent = React.forwardRef<
 React.ElementRef<typeof PopoverPrimitive.Content>,
 React.ComponentPropsWithoutRef<typeof PopoverPrimitive.Content>
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
 <PopoverPrimitive.Portal>
   <FocusScope asChild loop trapped>
     <DismissableLayer>
       <PopoverPrimitive.Content
         ref={ref}
         align={align}
         sideOffset={sideOffset}
         className={cn(
           "...",
           className
         )}
         {...props}
       />
     </DismissableLayer>
   </FocusScope>
 </PopoverPrimitive.Portal>
));

This worked for me, I didn't need to wrap the PopoverContent with DismissableLayer, just FocusScope  (You can import it from @radix-ui/react-focus-scope package) was enough to make the CommandInput focusable.

I just got into the same problem and after i almost gave up, i removed button tag in popovertrigger and it worked without any other changes.

@vimtor I fixed it by wrapping my PopoverContent (which is being used by ComboBox) in its own FocusScope and DismissableLayer (suggested in this issue radix-ui/primitives#922 (comment)). That fixed my problem with unexpected rerender.
const PopoverContent = React.forwardRef<
 React.ElementRef<typeof PopoverPrimitive.Content>,
 React.ComponentPropsWithoutRef<typeof PopoverPrimitive.Content>
>(({ className, align = "center", sideOffset = 4, ...props }, ref) => (
 <PopoverPrimitive.Portal>
   <FocusScope asChild loop trapped>
     <DismissableLayer>
       <PopoverPrimitive.Content
         ref={ref}
         align={align}
         sideOffset={sideOffset}
         className={cn(
           "...",
           className
         )}
         {...props}
       />
     </DismissableLayer>
   </FocusScope>
 </PopoverPrimitive.Portal>
));

I've tried this but unfortunately not working! Do you have any other suggestions for me to resolve this issue? Thank you

I'm facing the same issue, but that solution didn't work neither for me. Did you solve it? For me, the issue is this: I have a shadcn <Select > component inside a dialogue but the hover on the items doesn't trigger the focus because it is trapped (the click works)
Update: found a solution here: #1647 (comment)

The solution in the link also worked to me, thanks man.

authors: EL-MEHDI-ESSAADI ManuDoni hafijAsadMVN ishaqyusuf maik-emanoel seenyat shadcn vimtor

repo: shadcn-ui/ui


text:
*&![Full-Video]™ Breckie Hill Leaked Original Video Trending On Social Media

Describe the bug
27 second ago - Lea𝚔ed viral link 2024 video Lea𝚔ed Viral the internet by storm and amazed viewers on various social media platforms. Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media.Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media.Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media.
🔴📺📱 Cl𝚒ck Here To link 👉👉 (Full Lea𝚔ed viral link 2024 Video1)
🔴📺📱 Cl𝚒ck Here To link 👉👉 (Full Lea𝚔ed viral link 2024 Video2)
➤ ►🌍📺📱👉 Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media
Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media 2024.Lea𝚔ed viral link 2024 Lea𝚔ed Video Viral On Social Media 2024.
The recurrent theme of Lea𝚔ed tapes and the subsequent fallout serves as a reminder of the fragility of reputation in the digital era. As the lines between private and public life continue to blur, celebrities like Prison Officerfind themselves at the mercy of internet chatter, where a rumor can ignite a firestorm of speculation and judgment.
In the ever evolving landscape of celebrity culture, the Ishowspeedscandal underscores the relentless pursuit of sensationalism, a pursuit that often comes at the expense of truth and dignity. As we navigate the complexities of the digital age, the line between entertainment and exploitation remains perilously thin.
As the situation unfolds, the truth remains shrouded in mystery, leaving the public to ponder the authenticity of the rumors. In a world where fame and infamy are two sides of the same coin, the saga of Ishowspeedis a testament to the power of social media to shape narratives and challenge the boundaries of privacy and consent.
The viral video of Lea𝚔ed viral link 2024 Nude Lea𝚔 emerging online has amassed tremendous views across fan accounts and social media sites with one video clip. The viral video circulating recently shows Lea𝚔ed viral link 2024 Nude Lea𝚔 in an unexpected and hilarious moment while in public running errands.
Numerous fans have rushed to watch the viral video and share the clip amongst followers featuring Lea𝚔ed viral link 2024 Nude Lea𝚔 caught in an amusing and awkward situation. While surprising, the authentic and candid video showing Lea𝚔ed viral link 2024 Nude Lea𝚔 handling a real life blooper so genuinely has earned praise from viewers. Nonetheless, fans watch the current viral video of Lea𝚔ed viral link 2024 Nude Lea𝚔 that emerged online with delight and clamor for what the celebrity icon s reaction to the widely spread viral video will be.
The fan video showing Lea𝚔ed viral link 2024 Nude Lea𝚔 first emerged on Twitter on Monday, posted by an amused fan who claimed to have captured the silly incident on their phone camera while out and about. The viral Clip of Lea𝚔ed viral link 2024 Nude Lea𝚔 had garnered over 2 million views by Tuesday morning as more users on Instagram, Facebook and YouTube began uploading and sharing the embarrassing yet entertaining video.
Lea𝚔ed viral link 2024 Nude Lea𝚔 Only Fans Lea𝚔 video
Lea𝚔ed viral link 2024 Nude Lea𝚔 Lea𝚔ed pictures
Lea𝚔ed viral link 2024 Nude Lea𝚔 explicit content Lea𝚔
Only Fans account breach
Only Fans data hack
Lea𝚔ed viral link 2024 Nude Lea𝚔 personal information exposed
Desi Xvideos Pakistani Sexy
Campinos Xxx 2014 Kajal
Jerk Videos Ass Xxnx
Only Fans 2024 Lea𝚔ed Video
XnX VIRAL Gloria Bugie Noodles Viral Video L𝚎aked on X Twitter
latest Lea𝚔ed Video Viral On Social Media
Kompoz Me Lea𝚔ed Com
Scoop Big Xnxx Celebrity
Latest News, Photos, Videos on Lea𝚔ed Video
Outdoor Desi Village The
Latest Videos of Lea𝚔ed Videos
Xnx VIRAL Gloria Bugie Noodles Lea𝚔ed Video Trending
Viral Lea𝚔ed Video, Aakhir Woh Larki Kon Thi
Blue Flims 2024 Lea𝚔ed
Trending Lea𝚔ed Videos Viral
Kendall Washington
Viral Ice Spice Lea𝚔ed Video Trending ON X Twitter
18+ viral mms Lea𝚔ed video telegram links
XXX Telegram LINK!! Erin Bugis Lea𝚔ed Video Viral Trending ON Twitter
Here's x.n.x Lea𝚔ed viral link 2024 Nude Lea𝚔ed 2024 Video Viral On Soc𝚒al Med𝚒a Tw𝚒tter
Lea𝚔ed viral link download
Lea𝚔ed viral link twitter
Viral video link website
Telegram viral video link 2024
Telegram viral link download
Viral video link download
Affected component/components
Button
How to reproduce
fghdfghdfgh
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
gfhdfghdfgh

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

xcvxcv


text:
How to reduce the compiled file size

In the release page, file size for linux-arm and linux-mips is too big.
Is there any method to reduce the size?
eg. I'm using a router with armv7 CPU, how to build to make the file size smaller?

upx

https://upx.github.io
upx --best /path/to/v2ray-plugin

@cokebar Did you managed to get file size smaller ? I saw there is commit 1d239bc already, but latest release 1.2.0 binaries are still around 3.4 MB

authors: Love4Taylor cokebar oglops rampageX


text:
windows support column?

I feel like it's a little strange we have the "Win EOL" column when a lot (maybe most) of these tools don't actually work on windows. Should we have an extra column for non-wsl Windows support? It looks like we have the data already in the text

The Compatibility Testing table is the research data behind the Suggested Compatible Format section. It is to help decide what to put in the .node-version file and work with a wider group of people. Or for a particular format, see what products will support it.
Say I work on a Mac using node version manager X which does not work on Windows. But I work with people on Windows, using node version manager Y. What file formats will work for everyone in my team?

authors: jdxcode shadowspawn

repo: shadowspawn/node-version-usage


text:
🛑 Shakedown Social - Uploads is down

In fafe869, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 272 ms

Resolved: Shakedown Social - Uploads is back up in 0739a21.

repo: shakedown-social/upptime


text:
🛑 Shakedown Social - Uploads is down

In 4bec9b4, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 185 ms

Resolved: Shakedown Social - Uploads is back up in 23723a2.


text:
🛑 Shakedown Social - Uploads is down

In 73331a9, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 644 ms

Resolved: Shakedown Social - Uploads is back up in be9fe4c.


text:
🛑 Shakedown Social - Uploads is down

In 6edef98, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/c83dff7e175cde04.png) was down:

HTTP code: 404
Response time: 316 ms

Resolved: Shakedown Social - Uploads is back up in 54e0bdb after .


text:
🛑 Shakedown Social - Uploads is down

In 781f95b, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 314 ms

Resolved: Shakedown Social - Uploads is back up in dbf06ab.


text:
45816967 ADNI Vision Transformer

Hi,
This is 45816967's pull request to add a vision transformer to topic-recognition for the classification of ADNI dataset achieving a test accuracy of 64.43%.
The pull request contains:

modules.py: The code for the models used for the vision transformer
dataset.py: The code used to load the data from a folder
train.py: The code used to run the training loop for the vision transformer
predict.py: Code used to run predictions from a chosen model
driver.py: Script to quickly train and predict using the model
README.md: Project Documentation

Thanks,
Jun Khai Chooi
45816967

This is an initial inspection, no action is required at this point
Difficulty: Hard
Readme:

Good work
Contents explained well
Plenty of hyperparameter tuning

Commit messages: Exellent
Code:

Uses Vision transformer
Well commented
Good design

Functionality/Performance:

Did patient-level split
Test acc is 64.43%

General comments:

Solves the problem well although performance is poor
Good work

Marking
Good Practice (Design/Commenting, TF/Torch Usage)
Adequate design and implementation
Good spacing and comments
Header blocks missing -1
Recognition Problem
Solves problem
Driver Script present
File structure present
Shows Usage & Demo & Visualisation & Data usage
Module present
Commenting
No Data leakage
Difficulty: Hard
Commit Log
Meaningful commit messages
Progressive commits used
Documentation
ReadMe good
Model/technical explanation
Good Description and Comments
Markdown used and PDF submitted
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch)
No Feedback required
Request Description good

Merging not possible until the gitignore file is removed, please fix. Does not affect grade only merge.

Feedback attempt and no feedback marks lost.


text:
PD Toolkit: Object nodes should have all the cold inlets except the first one

http://en.flossmanuals.net/pure-data/ch039_order-of-operations/

I've tried to replace this line, with the code below, but then I realised WebPD controls hot/cold issues by itself, so it's not the problem
savedInlets.push(node.addInlet(getInletType(pdInlet), idx.toString(), idx.toString(),                 /*default*/null, /*hidden*/false, /*readonly*/false, /*cold*/(idx > 0) ? true : false));

repo: shamansir/rpd


text:
Need for pullup resistors on SDA and SCL pins

Last year I had no problem making an I2C_1602_LCD display work with your MicroPython driver. But when I tried it again just yesterday, I found that the software no longer worked. I kept getting an error message like "Line 25 OSError I2C write error -1010". Looking at your code, I decided it must be the wrong I2C address, so I found a couple of I2C_1602_LCD displays with known IC2 Addresses (0x27 and 0x3f) which I then tried to make work with the software changing the line which read "LCD_I2C_ADDR=63" to the appropriate decimal value (63 for 0x3F boards and 39 for 0x27 boards) and still could not make the software work. Anyways, I started over from scratch, with all new hardware, and still no luck. Then I remembered I had another Micro:bit breakout board (a Chinese made ElecFreaks Micro:bit Breakout board called "OCTOPUS Bit v 1.6". When I replaced the SparkFun Micro:bit breakout board with the ElecFreaks board, your MicroPython I2C_1602_LCD driver magically worked. So, I guess last year I was using the ElecFreaks Micro:bit breakout board.
So, then I wondered what the difference might be. After a bit more research on the Internet, I came across an article that says a pull-up resistor of from 5K ohms to 20K ohms is sometimes needed, especially when multiple I2C devices are attached to the same bus. So, I tried two 12K ohm pull-up resistors on the SDA and SCL pins of the SparkFun Micro:bit breakout board, and found it would now work with your I2C_1602_LCD driver. I first tried pulling it up to +3V and later tried pulling the 2 pins up to +5V.  In both cases, that was enough pull-up to make the 1602_LCD work.
So, if you have other folks having problems running your MicroPython I2C_1602_LCD drivers on their
Micro-bit board, advise them to try a pull-up resistor between SDA and +5V and SCL and +5V.  Anything in the range of 5K ohm and 20K ohm should work.

micro:bit use a 4.7K resistor in the board, it is suit for most case. If you meet I2C pullup resistor problem, the resistor in board may not work. Internal weak pullup has no effect for micro:bit hardware I2C, and micropython for micro:bit does not support software I2C now.
And which version of micro:bit do you using? Old version 1.3B or new version 1.5?

Thanks for your feedback.
I don't know how to tell which version of the Micro:bit boards I have. I checked my invoice, the box they came in, and on the board itself, but I saw no indication of a version number. The invoice shows that I ordered and received them six months ago (not one year ago as I had thought).
I did locate a Micro:bit schematic on Version 1.3B and it does show two 4.7K ohm pull-up resistors on SDA and SCL as you said. I imagine the newer version of the board has the same, or better. But, the schematic also shows two other devices on the Micro:bit that share this same I2C bus: the FreeScale MAG3110 magnetometer chip and the FreeScale MMA8653FC accelerometer chip. So, the limit of the Micro:bit's internal pull-up might be easier to reach when you factor these two devices in, and the fact that I was using a SparkFun Micro:bit Break-out board and a foot long 4-wire ribbon of jumper wire between the MB-102 solder-less breadboard and the I2C_1602_LCD display. Given this longer wiring route, the added circuit capacitance could exceed the amount the engineers were assuming when they came up with when they calculated the 4.7K ohm values.
All I know is that with multiple Micro:bit boards (likely same lot), with multiple SparkFun Micro:bit breakout board I consistently get a MicroPython error, but with my single Elec-Freak Micro:bit breakout board, the same software (still burned into FLASH memory on the Micro:bit boards) magically work.
I can only conclude that the potential exists where by Micro:bit experimenters can run into problems with the Micro:bit's I2C interface that can be easily resolved by adding a couple 10K pull-up resistors. This information should be general knowledge to the Micro:bit user community.
This problem was never with your software, which I am happy you have made available thru GetHub. Thank you for this and your other Python modules which makes it possible to teach kids more advanced topics than is covered in the basic "Read-the-Docs" MicroPython tutorials.
Have a Happy New Year,
-William Moore
On Thursday, December 27, 2018, 6:13:52 PM PST, shaoziyang notifications@github.com wrote:
micro:bit use a 4.7K resistor in the board, it is suit for most case. If you meet I2C pullup resistor problem, the resistor in board may not work. Internal weak pullup has no effect for micro:bit hardware I2C, and micropython for micro:bit does not support software I2C now.
And which version of micro:bit do you using? Old version 1.3B or new version 1.5?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I think you still use old version micro:bit, because new version has only ship three month ago. The most different is sensor chip, but function is same.
New version micro:bit with small label in the back, and has only one sensor chip:

The problem may cause by LCD1602 module, My LCD1602 is work fine without external res, maybe 4.7K res in micro:bit is too large for some LCD1602 module.

authors: randmor shaoziyang

repo: shaoziyang/microbit-lib


text:
OOM on 8mb file

I tried to unminify an 8 MB file, but got an OOM error after a while. I had about 24 GB of RAM free when I started.
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x7fbc63a0146c node::Abort() [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 2: 0x7fbc63a014b5  [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 3: 0x7fbc63c2de6a v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 4: 0x7fbc63c2e0e1 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 5: 0x7fbc63fc8c66  [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 6: 0x7fbc63fda043 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 7: 0x7fbc63fda930 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 8: 0x7fbc63fdc91d v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
 9: 0x7fbc63fdc975 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
10: 0x7fbc63fa8dda v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
11: 0x7fbc6423431e v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/lib/x86_64-linux-gnu/libnode.so.64]
12: 0x212d24c5452b

Can you share the file?
I believe Node caps the amount of memory it is willing use at about a gigabyte by default, so you might also try passing --max-old-space-size=8192 (or another large amount).

Thanks, that seemed like it helped!
$time node --max-old-space-size=8192 node_modules/.bin/unminify $i > $i.clean

real    14m10.835s
user    15m59.688s
sys     0m16.022s

authors: bakkot nfultz

repo: shapesecurity/unminify


text:
Game broken

When attempting to access this at https://shaw-dev-workshop.github.io/github-games-bhaveshshah21-home, I am getting a 404. This could be caused by a couple of things:

GitHub Pages needs to be enabled on the  branch. You can fix this in the repository settings.
The index.html file is incorrectly named inde.html. We will fix this together in class.

Can you fix the first bullet, please?

Fixed and reverted index.html


text:
P0769R2 Add shift to

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0769r2.pdf

実装済み

repo: shibainuudon/HamonCore


text:
🛑 Österreichischer Blasmusikverband is down

In 68bdab5, Österreichischer Blasmusikverband (https://www.blasmusik.at/) was down:

HTTP code: 500
Response time: 857 ms

Resolved: Österreichischer Blasmusikverband is back up in 03b6609 after 26 minutes.

repo: shiermann/upptime


text:
🛑 Österreichischer Blasmusikverband is down

In ffebd96, Österreichischer Blasmusikverband (https://www.blasmusik.at/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Österreichischer Blasmusikverband is back up in ee5c631.


text:
[WIP] --audio-only コマンドラインオプションの追加

--audio-only 付きで実行された場合に, 合成した音声のみをコンテナにつめるようにしました.
--out-filename が指定されない場合, 拡張子は .weba ないし .m4a となります.
mux() の枠組みは変更せずに NoVideoProducer というなにも生成しない映像用の VideoProducer を用意する方法で実現しています.
プログレスバーの処理を mux() 内に移動しようとしたのですが,
mux() でのループは映像の準備ができていない場合に sleep するようにしているので,
映像ありの場合は mux() 内でプログレスバーの処理をすると sleep の影響を受けて
スムーズに処理されませんでした.
このため 音声のみの場合にのみ mux() 内で処理し,
映像のある場合は VideoProducer::produce() での処理のままとしています.
音声のみの場合は AudioProducer::produce() での処理のほうがいいかもしれないので, まだここは変えるかもしれません.

#26 に引き継ぎます

repo: shiguredo/hisui


text:
Beta tags not parsable when following mockito guidelines

To reproduce:

Change version.properties to include a beta tag and tag version wildcard (e.g. version=1.0.0-beta.*, per mockito's versioning guidelines / learnings on tags)
Run any gradle command
Observe the build error below

Might be an issue with the downstream library used for parsing, but still worth noting here?
Caused by: org.shipkit.auto.version.VersionSpec$IncorrectVersionFormat: Problems deducting the version automatically. Expected correct 'version' property in file: /Users/jplaiste/opensource/datahub-gma/version.properties
Correct examples: 'version=1.0.*', 'version=2.10.100'
        at org.shipkit.auto.version.VersionSpec.readVersionSpec(VersionSpec.java:39)
        at org.shipkit.auto.version.AutoVersion.deductVersion(AutoVersion.java:42)
        at org.shipkit.auto.version.AutoVersion.deductVersion(AutoVersion.java:33)
        at org.shipkit.auto.version.AutoVersionPlugin.apply(AutoVersionPlugin.java:12)
        at org.shipkit.auto.version.AutoVersionPlugin.apply(AutoVersionPlugin.java:9)
        at org.gradle.api.internal.plugins.ImperativeOnlyPluginTarget.applyImperative(ImperativeOnlyPluginTarget.java:43)
        at org.gradle.api.internal.plugins.RuleBasedPluginTarget.applyImperative(RuleBasedPluginTarget.java:51)
        at org.gradle.api.internal.plugins.DefaultPluginManager.addPlugin(DefaultPluginManager.java:181)
        at org.gradle.api.internal.plugins.DefaultPluginManager.access$300(DefaultPluginManager.java:51)
        at org.gradle.api.internal.plugins.DefaultPluginManager$AddPluginBuildOperation.run(DefaultPluginManager.java:276)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.api.internal.plugins.DefaultPluginManager$2.execute(DefaultPluginManager.java:159)
        at org.gradle.api.internal.plugins.DefaultPluginManager$2.execute(DefaultPluginManager.java:156)
        at org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:49)
        at org.gradle.api.internal.plugins.DefaultPluginManager.doApply(DefaultPluginManager.java:156)
        ... 161 more
Caused by: Unexpected character 'ILLEGAL(*)' at position '11', expecting '[DIGIT]'
        at com.github.zafarkhaja.semver.VersionParser.consumeNextCharacter(VersionParser.java:516)
        at com.github.zafarkhaja.semver.VersionParser.digits(VersionParser.java:448)
        at com.github.zafarkhaja.semver.VersionParser.numericIdentifier(VersionParser.java:408)
        at com.github.zafarkhaja.semver.VersionParser.preReleaseIdentifier(VersionParser.java:339)
        at com.github.zafarkhaja.semver.VersionParser.parsePreRelease(VersionParser.java:311)
        at com.github.zafarkhaja.semver.VersionParser.parseValidSemVer(VersionParser.java:261)
        at com.github.zafarkhaja.semver.VersionParser.parseValidSemVer(VersionParser.java:195)
        at com.github.zafarkhaja.semver.Version.valueOf(Version.java:265)
        at org.shipkit.auto.version.VersionSpec.readVersionSpec(VersionSpec.java:37)
        ... 181 more

Hey, we don't support "-beta.*" at the moment. Do you need this for your use case?

Not immediately, or potentially ever. I'm still working out how we want to do release (and branches). New project, no clear standards here :)
I was just testing stuff out.

Ok. We'll table this feature for now.
BTW. I improved the error message: https://github.com/shipkit/shipkit-auto-version/pull/29

authors: jplaisted mockitoguy

repo: shipkit/shipkit-auto-version


text:
Docker CLI commands run as user root still

In two cases:

The "I don't have php7 caveat" when using Linux
CLI  (instead of php-fpm) commands when using Linux

Gonna have to get fancy with this issue similar to how MySQL does, using gosu.
Example installation here: https://github.com/docker-library/mysql/blob/86431f073b3d2f963d21e33cb8943f0bdcdf143d/8.0/Dockerfile#L6-L17
Additionally:

ENTRYPOINT script should run as root to correctly create symlinks
exec call to composer, phpunit, artisan should use gosu to run command as $WWWUSER
app container should have a /.composer directory created & chmod -R ugo+rw'ed

This will be done in PR #21

Fixed in #21

repo: shipping-docker/vessel


text:
Why was modalContainer attribute removed since version 4?

According to this issue the attribute modalContainer was added to the tour service. In fact it can be seen in this PR. I also see it was released in version 3.3.0. However, it's been removed in version 4 and is currently not available. I can't see any notes on this in the Changelog file. Is there a reason why you removed this? Can it be re-added?

@vjgonzalez I'm not sure what you mean. It's still there https://github.com/shipshapecode/ember-shepherd/blob/master/addon/services/tour.js#L423

Yes, it's in the master branch, but not in the releases: check out tag for version 11.0.0:

Ah sorry, just released a new version. Didn't realize it had not been released.

repo: shipshapecode/ember-shepherd


text:
Update to latest version of rails

Can somebody help to update to latest version of rails :)
Thanks

#37


text:
Helix optimization with openmm energies

Description
Adds new functionality to the helix modeling code, where openmm energies and nonbonded exclusions are used when optimizing the radius and pitch. RIght now there are 3 different scenarios for optimizing helices:

Simple case: Given LJ sigma and epsilon (same for backbone and sidechain), optimize radius, pitch, and particle spacing along the helix by evaluating energy internally. Nonbonded 1-2 and 1-3 interactions are used instead of any bonded terms, so the result can be used to determine the bond length and angles which will stabilize the helix.
Openmm energy evaluation with no bond constraints: Given LJ sigma and epsilon (can be different for backbone and sidechain), optimize radius, pitch, and particle spacing along the helix by evaluating openmm energy. Bonded force constants are all set to zero (we assume that at each iteration the bonds and angles are at equilibrium values), so there is no need to update the force field parameters within the openmm simulation object. Nonbonded 1-2 and 1-3 interactions are excluded, so there can be some unphysical results without constraints on the angles (such as backbone bonds going across the center of the helix).
Openmm energy evaluation with bond constraints: Given LJ sigma and epsilon (can be different for backbone and sidechain particles) and equilibrium bond distances for bb-bb and bb-sc bonds (can be different), optimize radius and pitch. Here, we have to determine which helical spacing (delta_t) corresponds to the specified bb-bb bond distance at each iteration. Nonbonded 1-2 and 1-3 interactions are excluded, so there can be some unphysical results without constraints on the angles (such as backbone bonds going across the center of the helix).

All 3 of these seem to be working now.
**Update:
I also added the functionality to do the reverse optimization: specifying the radius, pitch, and optionally bond lengths, and determining which LJ sigma parameters of backbone and sidechain give the lowest openmm energy. To summarize these new cases:

Optimize sigmas without bond constraints: Given a fixed radius and pitch, determine the bond length (assumes equal for bb-bb and bb-sc bonds) and sigma_bb and sigma_sc parameters which result in the lowest openmm energy. Epsilon LJ parameter is assumed equal for bb and sc, in which case we can pick any value for epsilon.
Optimize sigmas with bond constraints: Given a fixed radius and pitch, and fixed bond lengths (can be different for bb-bb and bb-sc), determine the optimal sigma_bb and sigma_sc parameters which result in the lowest openmm energy. Epsilon LJ parameter is assumed equal for bb and sc, in which case we can pick any value for epsilon.

Status

[x] Ready to go

I went through this again and everything looks good to go.


text:
Update php@8.1

Build php@8.1

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
composer-unused Could not setup composer-unused

Describe the bug
composer-unused Could not setup composer-unused
https://github.com/Slamdunk/php-p7m-reader/actions/runs/4175072546/jobs/7229492984#step:3:20
Version

[x] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[x] v2

Runners

[x] GitHub Hosted

Operating systems
ubuntu-latest
PHP versions
8.1
To Reproduce
https://github.com/Slamdunk/php-p7m-reader/blob/98790e85fd22a7888063c3ca3895f35c8a0bb3b5/.github/workflows/ci.yaml#L23-L28

The latest release of composer-unused has the phar file, so it should install correctly now.

authors: Slamdunk shivammathur

repo: shivammathur/setup-php


text:
Added check_prime to cpp

To check whether a number is prime or not.

Can u label it hacktoberfest-accepted.

Can u label it hacktoberfest-accepted.

It is same, any merged PR will also be considered for the contest!

Can u label it hacktoberfest-accepted.

It is same, any merged PR will also be considered for the contest!

Other PR is labelled as accepted , So I thought it is not considered for contest. So, can u make it.

authors: amnjain shivangdubey


text:
feat: emit WAMessageStubType.GROUP_CHANGE_DESCRIPTION Ecent

this PR implements the WAMessageStubType.GROUP_CHANGE_DESCRIPTION event which is triggered by a description update of a group. it also works for community descriptions.
🌟 Created by @arthursimas1

Thanks for your contribution 🥰.
The next step is to wait for review and approval to merge it to main repository
The community can help reacting with a thumb up (👍🏻) for approval and rocket (🚀) for who has tested it.
To test this PR you can run the following command below:
# NPM
npm install @shizodevs/shizoweb@shizothetechie/shizoweb#!!-New-Feats-!!
# YARN v2
yarn add @shizodevs/shizoweb@shizothetechie/shizoweb#!!-New-Feats-!!

Regards & Loves from
shizoweb 🤭

authors: shizo-devs shizothetechie

repo: shizo-devs/shizoweb


text:
Graceful handling of missing document keyword

Added to support angular universal. Same problem originally solved by https://github.com/shlomiassaf/angular2-modal/pull/144, but updated to reflect recent changes.

Thank you for your contribution.
Due to a huge refactor I could not use the commit but I believe the issue is now fixed with version 3.0.0
If not, please feel free to open a new issue.
Version 3 comes with a better build (FESM) and the following changes:
* handle document for angular universal
* refactor: use ng-template instead of template
* refactor: remove defaultOverlayTarget directive
* refactor: replace custom swpCmp with ngComponentOutlet

### BREAKING CHANGES

  - Moving to use <ng-template> will break applications running on < 4
  - Applications using defaultOverlayTarget (all of them) will have to omit it

(2f98e75)

authors: davidthor shlomiassaf


text:
Review: Navbars

Overview
For this review, we're going to take a look at the Navbar Home and Navbar Landing components.
Review Branch
review-#5
Files to review

NavBarHome.jsx
NavBarLanding.jsx

Checklists
(Please edit the following list if necessary to indicate the actual checklists to be used.)

Architecture
Design
JS

Due date
Tuesday, February 16
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

NavBarLanding.jsx:
Design-05: Ensure comments are appropriate
This navbar is only used on the landing page but the comment says that it appears on top of every page. Also is not rendered by the App component.
NavBarHome.jsx:
JS-01: Name constructs appropriately
Consider changing the file name since this navbar is not only used on the home page.
Design-05: Ensure comments are appropriate
This navbar is not rendered by the App component.
Design-07: Ensure code is readable
Some in-line styling are defined as consts at the top while others are defined in the component. Might want to make them all consts so components are easier to read.

NavBarHome.jsx
Design-05: Ensure comments are appropriate.
Design-07: Ensure code is readable.
There are certain areas where the code could be reorganized to be read better
JS-01: Name constructs appropriately.
Maybe rename it so that the it is used
NavBarLanding.jsx
Design-05: Ensure comments are appropriate.
Some areas could have comments
Design-07: Ensure code is readable.

NavBarHome.jsx
Design-05: Ensure comments are appropriate.
More comments should be used throughout the code.
JS-01: Name constructs appropriately.
This navbar is not only used for the home page. Name should be changed to something more applicable.
NavBarLanding.jsx
Design-05: Ensure comments are appropriate.
More comments should be used throughout the code.
Arch-01: Obey file name conventions.
Landing directory that NavBarLanding.jsx is in should be lowercase L, so it should be landing.

NavBarHome.jsx:
Design-05: Ensure comments are appropriate
I'd recommend adding additional comments throughout the code whenever possible.
JS-01: Name constructs appropriately
Rename it to appropriately fit it's usage.
NavBarLanding.jsx
Design-05: Ensure comments are appropriate.
Ditto from the NavBarHome

NavBarHome.jsx:
Design-07: Ensure code is readable
Design-05: Ensure comments are appropriate - Comment how functions/classes work in the file
NavBarLanding.jsx:
Design-07,Design-05: similar to NavBarHome.jsx

NavBarLanding.jsx
Arch-01: obey filename conventions

the directory "Landing" should be renamed to "landing"

Design-05: Ensure comments are appropriate.

Some comments that do not match with the file, should change some of them to be appropriate.

NavBarHome.jsx
Design-08: Ensure code is DRY.

The dropdown code style is repeated should make it a const style.

JS-01: Name constructs appropriately.

rename the file to be more appropriately

Design-05: Ensure comments are appropriate.

Some comments that do not match with the file, should change some of them to be appropriate.

NavBarHome.jsx
Design-05: Ensure comments are appropriate.
Design-07: Ensure code is readable.
NavBarLanding.jsx
Design-05: Ensure comments are appropriate.
Design-07: Ensure code is readable.

authors: CalianaFortin alohajerome awongway kyraikeda mkirts saitoshi trey-sumida


text:
fix: fetch associations in bulk edit

1. Why is this change necessary?
Fetching associations in bulk edit leads into an infinite loop if the repository search result is more then 500. In this case the methods self execute to paginate through the results. Unfortunately the condition wether the method should self execute or not, is always true. At this point you are stuck in an infinite loop.
2. What does this change do, exactly?
Fix the condition.
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-23814
Please use this issue to track the state of your pull request.

Thanks for your contribution, your PR got merged! :tada: :blue_heart:

authors: keulinho shopwareBot stefanpoensgen

repo: shopware/platform


text:
PayPal plugin not compatible with other languages

PHP Version: 8.3   | Shopware Version: 6.4.20.2  | Affected area / extension: Extension:PayPal-Integration

Expected behaviour:
When switching the language in the shop frontend to English oder French I expect ALL PayPal buttons and texts and overlays to be in Enlish or French, too.
Actual behaviour:
When switching the language in the shop frontend to English oder French all the PayPal buttons or texts and overlays stay in german. Only the PayPal Checkout button changes it's language. The rest stays in German.
Even in the official Shopware documentation, which is in English, there are not correctly translated PayPal texts in the screenshots.
https://docs.shopware.com/en/shopware-6-en/extensions/paypal
How to reproduce:
simply change the language and you see the German texts.

[public] Shopware automated response: This issue is linked to the internal issue: PPI-1005
[created from PPI-1005, comment 503255]

[public] Are you talking about the Pay later button and the messaging regarding this? Or anything else?
Regarding the pay later messaging, unfortunately, this is how PayPal behaves and not something we as plugin developers can alter at the moment. It renders in the langauge of the merchant. There is a possibility to activate “Cross border messaging”, please contact your PayPal representative regarding this.
[created from PPI-1005, comment 506045]

I am talking about nearly everything what is shown via PayPal plugin.

the message for rate pay which says "Bezahlen Sie in 3-24 monatlichen Raten. Mehr erfahren"
the link "Mehr erfahren" in the message above which opens a popup in the wrong language
the PayPal button "Später bezahlen" / pay later

repo: shopware/shopware


text:
"AI-generated summary of ratings" are not displayed in storefront

PHP Version: php8.3-fpm   | Shopware Version: 6.6.8.2  | Affected area / extension: Platform(Default)

Expected behaviour:
If I set up the "AI-generated summary of ratings" as described in our docs, I would expect the summary to be displayed in the store front.
Actual behaviour:
The "AI-generated summary of ratings" are not shown in the storefront.
How to reproduce:
Create a review for a product, make it visible in the storefront and activate the "AI-generated summary of ratings" as described in our docs.
I have tested this with different test environments with different Shopware versions. All versions 6.6.6.0 and higher show this issue.
In the version 6.5.8.15 it works as expected for example.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39712
[created from NEXT-39712, comment 514625]

authors: MaxBaeumer shopwareBot


text:
In variant articles, the display in the frontend does not fit if there are several images

In variant articles, the display in the frontend does not fit if there are several images.
The more images the product has, the smaller the preview will be.

[public] Shopware automated response: This issue is linked to the internal issue: TSP-390
[created from TSP-390, comment 516161]


text:
Added external redirect to blog controller

1. Why is this change necessary?
When a blog category has a external link, it does not redirect. This feature is missing in the Blog Controller 😄
2. What does this change do, exactly?
Redirects to that page if external link is defined in the current category
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21488
Please use this issue to track the state of your pull request.

Thx @shyim 💙

authors: shopwareBot shyim soebbing


text:
Set font display for googles pagespeed

1. Why is this change necessary?
See https://issues.shopware.com/issues/SW-23654
2. What does this change do, exactly?
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-23671
Please use this issue to track the state of your pull request.

Please not for pagespeed but for your customers ;)

Please not for pagespeed but for your customers ;)

Moin @hlohaus, thank you for your contribution! 💙


text:
Characters " " inside Code Block instead of space

I'm a new Showdown user, experimenting the CLI tool to convert my markdown pages into static html files for my blog. I'm very happy with it so far.
However, I just stumbled upon a Gotcha while copy/pasting my directory structure inside a block of code (using the triple backticks).
Does someone knows why the rendering with Showdown is like this:
tree
├── folder1
│   └── a.txt
└── folder2
    └── b.txt

While it is like this in other markdown to html converter (and also here on Github):
tree
├── folder1
│   └── a.txt
└── folder2
    └── b.txt

It looks like Showdown is putting &nbsp; inside the
 tag instead of   to render the space character.
I'm really not sure if I'm misusing it or if it's a bug. Does anyone one has an idea about it?

Bug confirmed.
The input text has non-breaking spaces inside the code block which get converted to the correspondent html entity  . However, then the code block is encoded again, changing & to & resulting in that weird behavior.

i met the same problem

Same here, I got this: ¨NBSP;

Same here, => { becomes => { in
 and  blocks. Inspecting reveals =&gt {.

we are working on a fix for this (and other related issues).

should be fixed. Will be merged in develop soon.

authors: Stonks3141 djlxiaoshi gengue tivie yoric-m

repo: showdownjs/showdown


text:
读取文件时不支持中文

打开时如果路径有中文就不发生错误。

MiniExcel.QueryAsDataTableAsync(@"F:\MyDeskTop\测试\b.xlsx");
这样的会出错误，如果是用openFileDialog打开却正常。

我这边测试没有问题，麻烦需要提供完整exception message


text:
Kbd and bullets

Get rid of the uneeded JS alerts and also fix the id for the bullet button to get that working.
Fixes issue #19 and re-fixes issue #13

(develop version of #22 -- for future reference!)
Thanks @SnoringFrog!

I'll have to look into this a bit more, it seems SE has changed this. This is what I see:

So... no merge yet! :(

Aren't those just their standard unordered/ordered list buttons and not the one from the script? I was referring to the extra bullet/unordered list button.

Although I do see that they have their button ids on the lis instead of the spans. Shouldn't matter for the function of the button (doesn't seem to for my locally modified script), but might be good to change for consistency.

You're right... don't know what I was thinking at that time! :/ Merged! :) Thanks for fixing it!


text:
Launcher doesn't exit cleanly on Linux

On Manjaro Linux, the launcher doesn't seem to exit cleanly. I have to manually kill the left over process.
It works fine, installs fine and so on but it does give this:

[liam@liam-manjaro ~]$ /home/liam/Downloads/Linux.Not.Paradox.Launcher.v1.2.0.x64/launcher
An unhandled exception occurred at $00007F9CC756942C:
EAccessViolation:
$00007F9CC756942C

If you need more info, let me know.

Thanks for the report. Please let me know what edition and version of Manjaro you're using.
I'll set up a VM with Manjaro sometime this week to test it out and see what I can do to fix it.

Wow, thanks! This is just KDE Manjaro.

Just installed a copy of Manjaro KDE and can confirm the reported bug.
From initial investigation, it would appear to be a problem between the compiled code and the KDE shell.
Looking for solutions

I've released version 1.2.2 that although doesn't fix the actual bug (as the root cause appears to be in KDE (kio core), the launcher will invoke the kill command on it's own process id to fully close.
The access violation will still appear but the launcher process will be properly terminated.
As an extra I also changed the options window info text color (so now you can actually read them)


text:
Add detail to postgres/docker AWS RDS setup

I had some trouble getting setup with postgres and docker (I'd never used them before) so this PR contains some postgres-for-dummies style information which would have clarified things for me.

Lemme know what you think! I don't know Maria/MySQL that well but it looks like Maria's a fork of MySQL so they've got the same URI format? At least the only things I could find about Maria's URI format were this SO question (which referred to the MySQL docs) or these MariaDB docs (which didn't actually include URI and told the user to use the mysql binary)

repo: shuttle-hq/shuttle-docs


text:
dbStructures merge issue

There is a merge conflict spot at commit (https://github.com/shuzhao-li/JMS/commit/297dea56801dfc97719d3ea03ccedda58fe96cd1). Needs to remove the problematic one.
I looked into it and I think it is more likely should keep the HEAD one and discard the one from 88a17cb7d9f78fc4b563e031e55f219a2df0b35f. But it is probably better to have you checked and correct it directly. @shuzhao-li

Okay, fixed.

authors: gmhhope shuzhao-li

repo: shuzhao-li/JMS


text:
c codes

bora codar

.


text:
Ensure line feed file end

What do you think about introducing the "file should end with a newline" rule?
Here's the Checkstyle rule for this.

Hi @egor-n
You can enable it by adding this to your .editorconfig
[*.{kt,kts}]
insert_final_newline=true

I should have thought of that. Thank you!

No worries. Documentation wasn't very clear. If you don't mind I'll keep this ticket open until insert_final_newline is set to true by default.

Right now it would not fail if there are two new lines at the end of a file. I guess that could be optimized, right?

@vanniktech 2 or more blank lines should trigger "Needless blank line(s)" error. If you don't please submit a bug report.

There you go #108

Instead of enabling this option by default I went with improving ktlint's .editorconfig support by automatically falling back to "[*]" for property resolution. This way people who have .editoconfig with insert_final_newline = true under [*] won't have to do anything else to enable it and others won't be surprised by the change.
"not enabled unless .editorconfig says otherwise" behavior is currently due to the fact that neither Jetbrains's nor Google's styleguide says anything about newline at the end of file. I'll try to clarify it before making insert_final_newline on by default.
insert_final_newline = true under [*] support included in ktlint@0.13.0.

Would love to see this enabled by default, especially because git diff warns about this. (A lot of tooling warns about it, actually!)

authors: egor-n shyiko thauk-copperleaf vanniktech

repo: shyiko/ktlint


text:
behavior

https://dwc.tdwg.org/terms/#dwc:behavior
Vocabulário controlado recomendado.
Definição: o comportamento apresentado pelo sujeito no momento em que a ocorrência foi registrada.

Aqui temos um ponto muito importante de discussão. O domínio e exemplos sugeridos apontam para um problema de qualidade chamado "esquizofrenia de domínio"

“Domain schizophrenia – Fields may be used for different purposes depending on a specific requirement or purpose.” (English, 1999)

Mistura-se forma de vida com hábito e outras características que ficariam melhor em seus próprios termos e classes.
Além disso, seria melhor usar para o Brasil um padrão que incorporasse termos e classes do DwC e Plinian Core. Isso porque, para forma de vida, temos a classe "NaturalHistory" e o termo "LifeForm" que abrigaria perfeitamente (sem esquizofrenia) a forma de vida.
Adotar um padrão mais flexível, que não fique preso as limitações do DwC, seria um caminho, a meu ver, muito mais apropriado para resolver nossos problemas e engajar as diferentes instituições brasileiras.

authors: edalcin yohanaditzel

repo: sibbr/DarwinCoreBrasil


text:
I want to upload image base64..!!!!!

Pls

The editor doesn't support uploading images of any type. You can create a custom menu with upload options, once uploaded you can insert the image into the editor.
Refer https://sibiraj-s.github.io/ngx-editor/#/menu?id=custom-menu for creating a custom menu. and https://sibiraj-s.github.io/ngx-editor/#/commands for the commands.

repo: sibiraj-s/ngx-editor


text:
Vaadin support.

We should add Vaadin support at some point.
Ideally, that would happen with an integrated server which can be started just as easily as the "desktop" ones.

Embedded tomcat is an option. This shouldn't be a problem.

authors: RobertZenz rjahn