Update for PM5 Alpha7 and more

Initial support of subchunks on Y axis
Correctly renamed class (BlockFactory) and method (getFullBlock & setFullBlock)
Fix a non thread safe object in an async task (since pthreads 5 objects are not serialized by default so we need to do it ourselves)
Fix the imports of the plugin logger in async tasks (it seems not used, is it still usefull to keep it ?) to a global logger

Main functionnalities seems to works but I'm having issue when pasting schematics on the block conversion, each block becomes a info update block whatever which format I use.

Concerning schematic pasting.
On discord :

VixikHD — 28/04/2023 20:43
You probably need to remap block ids used in schamatics to block ids used in pocketmine

I don't know how I should do that so I don't think it will be on this PR, surely not by me.

Good job!


Consider probing for the appropriate bash completion function so the user doesn't have to modify any code

On import of a command, consider identifying the appropriate bash completion function automatically without any user intervention.

A preview of this is available at https://github.com/mikebattista/PowerShell-WSL-Interop/tree/mikebattista/bash-completion-functions.
For many commands, the operation is noticeably slow which can bog down profile initialization.
Assuming the majority scenario is set it and forget it, there's no need to incur the performance overhead of probing for completion functions at every session. Consider ways to cache the completion function map or a switch the user can run at initial setup to generate the completion map the first time so they can then cache it themselves in their profile.

Added a caching mechanism in the preview branch.


Found another site for the list

https://reintech.io/blog
thanks!

and: https://linuxconfig.org/

Also: https://www.sql-easy.com

Add to block list
https://us.idyllic.app/
https://www.promeai.pro/
https://seapik.com/
https://www.talkie-ai.com/
https://laprompt.com/
https://fluxaistudio.com/

done


Bug 9617 & 6215

instructionText html, processed into valid HTML and displaying as expected
label formatting for only field removed, resulting in all labels and page names displaying correctly now

Separate PR raised


Load PulseAudio/ALSA dynamically (dlopen) on Linux / *BSD

Godot version:
Current master (51a0a381), but could be backported to other stable branches.
OS/device including version:
"X11" platform / any freedesktop.org OS (Linux distros, OpenBSD, FreeBSD).
Issue description:
For the X11 platform, we currently link the PulseAudio library (libpulse.so.0, libpulsecommon-10.0.so) directly in official binaries, which means that our binaries can't be used on systems without PulseAudio (especially relevant for Arch or Gentoo users, as well as any user with a strong aversion for PulseAudio or any Poettering endeavour).
This means that to support such users, game developers need to provide a Linux binary compiled with pulseaudio=no, which causes a fallback to ALSA (libasound.so.2).
[akien@cauldron godot.git (master)]$ ldd ~/tmp/godot/stable/Godot_v3.0.6-stable_x11.64 | grep pulse
        libpulse.so.0 => /lib64/libpulse.so.0 (0x00007f345cdf1000)
        libpulsecommon-10.0.so => /usr/lib64/pulseaudio/libpulsecommon-10.0.so (0x00007f345b6bf000)
[akien@cauldron godot.git (master)]$ ldd ~/tmp/godot/stable/Godot_v3.0.6-stable_x11.64 | grep asound
        libasound.so.2 => /lib64/libasound.so.2 (0x00007fbe43c9f000)

It would be better if we loaded these shared libraries dynamically with dlopen() instead of linking them upfront, allowing to run Godot even if they are missing (eventually defaulting to the Dummy audio driver if both are missing).

This still appears to be a problem with the latest release

The https://github.com/godotengine/godot/pull/22604 implementing dlsym loading for libpulse.so.0 appears to have been closed (not merged) without the alternative solution being discussed by @hpvb ever being implemented.
While projects distributed on steam will run using its runtime, projects distributed on gog or itch will fail without libpulse.so.0 (if the library is not included and rpath origin for binary set in the linker).

I ran into this issue.
But the bottom of this: godot should only be a glibc ELF binary and:

the init code should dynamically load all required libs. one binary can discover the core video games libs: x11 libs/wayland compositor, vulkan/GL, alsa/libpulse. For third party libs, don't expect a distro to have them: all distros are not the size of the huge mainstream ones, they should be distributed with the games.

For third party libs, don't expect a distro to have them: all distros are not the size of the huge mainstream ones, they should be distributed with the games.

Libraries are already statically linked into the binary, unless this is not possible or ill-advised.

Libraries are already statically linked into the binary, unless this is not possible or ill-advised (such as for glibc itself).

I would just like to comment that although this is great for the official binaries, providing an easy option for configuring the build script to NOT use statically linked or bundled libraries is essential, as not doing so makes life very difficult for package maintainers...
I've seen quite a few projects that not only don't provide an easy option to disable it, but actually depend on bundled libraries for their software to work, which makes the software impossible to properly package on systems which depend on custom-compiled libraries, such as Gentoo.

I would just like to comment that although this is great for the official binaries, providing an easy option for configuring the build script to NOT use statically linked or bundled libraries is essential, as not doing so makes life very difficult for package maintainers...

This is already available, and has been the case for a long time :slightly_smiling_face:
Check the [code]builtin_*[/code] SCons options using scons -h.

Libraries are already statically linked into the binary, unless this is not possible or ill-advised (such as for glibc itself).

How about statically linking to musl libc to allow exporting for all distros at once?

How about statically linking to musl libc to allow exporting for all distros at once?

Applications that use OpenGL can't link against musl libc, because the system's libGL is typically linked against glibc. In the NVIDIA proprietary driver's case, this is something no distribution packager can fix :slightly_smiling_face:

Applications that use OpenGL can't link against musl libc, because the system's libGL is typically linked against glibc. In the NVIDIA proprietary driver's case, this is something no distribution packager can fix slightly_smiling_face

but what if you dlopen() libGL? also nowadays linux distros ship libGL as either mesa (because they don't ship nvidia in the first place) or glvnd (gl vendor-neutral dispatch library, created and maintained by nvidia)
gcompat can run glibc binaries on musl without installing shared libraries linked against glibc, so I think it's worth trying dlopen()'ing glibc-linked libGL with musl-linked program

Headless/server binaries could link against musl, but this can cause subtle behavior differences (such as in string formatting or floating-point handling) that can result in difficult-to-track bugs.

you remind me about this article (you'll have much fun if you read it) https://drewdevault.com/2020/09/25/A-story-of-two-libcs.html :smile:
you can read about behavior differences here https://wiki.musl-libc.org/functional-differences-from-glibc.html


Question: Cranelift Self Compilation

For many years now I've been eargerly waiting/searching for a language that can compile it's own compiler to wasm/wasi. I've talked with the guy who made the llvm to wasm demo (sadly that project has quickly been going nowhere). I've talked to some rust groups about compiling a minimal subset of a rust compiler to wasm. I've talked with some people from V-lang, etc.
So my question is, how unrealistic is it for cranelift to compile itself to wasm (a module function with IR input and  wasm-bytes output)? "How unrealistic" as-in; does cranelift have unavoidable multithreading, or raw assembly, etc that would be a show-stopper for compiling it to WASM.
Thanks!

Hi @jeff-hykin -- this use-case would mainly depend on support for generating Wasm bytecode, which we previously discussed a bit in #2566. I think that while it's not totally unrealistic, it's a major undertaking: Wasm as an ISA is very different from our current target architectures in several important ways (stack machine, unlimited "registers" (locals) hence maybe no or only simple regalloc, functions are a first-class machine feature rather than software-managed via stack conventions, structured control flow, etc). I'd encourage you to read over that thread for ideas and background.

Oh I'm actually embarrassed to admit I didn't realize WASM/WASI wasn't a cranelift backend. And I was just reading the internals of the IR last week 😅 Thanks for the pointer to that thread.  That'll certainly resolve this issue for now.
I suppose I just associated wasmtime/bytecode-alliance/cranelift so much I had just always assumed WASM was a cranelift backend.


Push v1.0.1 to Terraform Registry

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Please describe your question here
v1.0.1 is released (thanks for the quick turnaround!). Can this be pushed to the Terraform Registry now?

hmm, that should have been automatic. let me check into that, apologies

ok v1.0.1 is now synced up to the registry - thanks for letting us know!


Square negatives fix

Fix for #157, so the square negatives mode also takes into account
negative credit card spending and negative pacing.

Thank you!


Update CHANGELOG.md

[x] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
Example S3 SSE migration block seems to had been misplaced in another section.
Verification
N/A

DCO signed. Thank you.


Provide onDropFromOutside prop for Dnd Cal

This PR is meant to resolve issue #1090.
Basic callback for outside drops
The change exposes the onDropFromOutside prop on the withDragAndDrop HOC, which takes a callback that fires when an outside draggable item is dropped onto the calendar. The callback receives as a parameter an object with start and end properties that are times based on the drop position and slot size.

It is worth noting that it is entirely up to the user to handle actual event creation based on the callback. All that this API does is allow draggable DOM elements to trigger a callback that receives start and end times for the slot an item was dropped on, and a boolean as to whether it's an all-day event. If the user wants to know which event was dropped, they will have to handle that themselves outside of React-Big-Calendar. An example added to the example App demonstrates how this can be done.
Optional selective dropping
By default, if onDropFromOutside prop is passed, all draggable events are droppable on calendar. If the user wishes to discriminate as to whether draggable events are droppable on the calendar, they can pass an additional onDragOver callback function. The onDragOver callback takes a DragEvent as its sole parameter. If it calls the DragEvent's preventDefault method, then the draggable item in question is droppable. If it does not call preventDefault during the function call, it will not be droppable.

An example was also added to the examples App, this one labelled `Addon: Drag and Drop (from outside calendar). The GIFs show this example in action.
I also added the following comments into the withDragAndDrop HOC by way of documentation.
 * Additionally, this HOC adds the callback props `onDropFromOutside` and `onDragOver`.
 * By default, the calendar will not respond to outside draggable items being dropped
 * onto it. However, if `onDropFromOutside` callback is passed, then when draggable
 * DOM elements are dropped on the calendar, the callback will fire, receiving an
 * object with start and end times, and an allDay boolean.
 *
 * If `onDropFromOutside` is passed, but `onDragOver` is not, any draggable event will be
 * droppable  onto the calendar by default. On the other hand, if an `onDragOver` callback
 * *is* passed, then it can discriminate as to whether a draggable item is droppable on the
 * calendar. To designate a draggable item as droppable, call `event.preventDefault`
 * inside `onDragOver`. If `event.preventDefault` is not called in the `onDragOver`
 * callback, then the draggable item will not be droppable on the calendar.

Hopefully this gives users the flexibility they need, without getting react-big-calendar overly involved with managing outside drag and drop scenarios. Any feedback/discussion/harangues are welcome!

Does it work in version 0.20.4 ?

I'm not sure if I understand. It's a PR into the master branch which is already a few commits ahead of version 0.20.4. So it's not in that version, it would be in a later release assuming it gets merged. But its functionality is compatible with the 0.20.4 codebase from what I can tell; it doesn't rely on anything added in a subsequent commit for its functionality.

this is awesome, thanks for taking the time to do this!

Thank you for your awesome work @kamry-bowman
I just wanted to know... is there any way also make the events be draggable to outside of the calendar?

Is there any documentation or example related to this?

Is there any documentation or example related to this?

https://github.com/jquense/react-big-calendar/blob/master/examples/demos/dndOutsideSource.js


Added Implementation of einsum

This is a PR for einsum in S4TF. Differentiation is yet to be added.

Thank you @Dash2507 for starting this PR, and we are excited to see einsum being implemented!
To make sure the implementation of Swift for TensorFlow has the highest quality, we expect code contributions to closely follow the Swift API Design Guidelines and the Google Swift Style Guide. To proceed, would you mind reviewing the coding guidelines above, refining the implementation against the guidelines and applying the following changes?

Use 4-space indentation everywhere, including all kinds of line breaks.
Use camel case for call function/variable/property names. Avoid snake case and leading underscores in function names.
Use terminology well avoid abbreviations unless it's a well-established term of art.
Use argument labels to optimize API readability at the call site.
Prefer the trailing closure syntax when possible.

Other than coding style, we need to make sure all APIs are well-tested. Could you please add tests to this test file?
We are in preparation for the upcoming 0.4 release for Swift for TensorFlow, and it's likely that we will not be able to finish code reviews for this PR soon. We will get back to it later this month. Sorry for the potential delay in getting this fleshed out and merged!

@Dash2507 You can continue asking the doubts here, I'll help you out as much as I can.

Thanks @Shashi456 , I have added test cases for einsum as well. now only waiting for further reviewing.

@Dash2507 did you build and test it locally? Did they pass?

Yes, tested against four cases and all of them passed.

I haven't been following this closely, but my understanding is that TF recently added an einsum op of some sort.  Would it make sense to use it, rather than performing the expansion in Swift?  cc: @alextp

@lattner I think there is an XLA einsum op but the python API seems to only be using that when executing on TPUs.

I think +Anudhyan Boral<EMAIL_ADDRESS>is still in the process of
using the tf einsum op everywhere.
On Sun, Jun 2, 2019 at 7:19 PM Anthony Platanios<EMAIL_ADDRESS>wrote:

@lattner https://github.com/lattner I think there is an XLA einsum op
but the python API seems to only be using that when executing on TPUs
https://github.com/tensorflow/tensorflow/blob/8f93f5c61cbcba20f90c867c83698285d900dc1a/tensorflow/python/ops/special_math_ops.py#L281
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/swift-apis/pull/164?email_source=notifications&email_token=AAABHRIJCZSYYK5OFLPBJ63PYR5UTA5CNFSM4HR7WEV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYEMRA#issuecomment-498091588,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABHRPRNFX3UXCNY5AZLTTPYR5UTANCNFSM4HR7WEVQ
.

--

Alex

Yes, I have a change in flight which adds a TF classic op (EinsumOp), and a
modified Python wrapper. This would achieve functionality parity with NumPy.
It is temporarily rolled back due to Windows Kokoro issues.
In case of XlaEinsumOp, it is missing a bunch of functionality compared to
the current Python wrapper or NumPy einsum. This is why it is not emitted
in all cases. Perhaps this gap can be closed in the near future.
On Mon, Jun 3, 2019, 9:34 AM Alexandre Passos<EMAIL_ADDRESS>wrote:

I think +Anudhyan Boral<EMAIL_ADDRESS>is still in the process of
using the tf einsum op everywhere.
On Sun, Jun 2, 2019 at 7:19 PM Anthony Platanios<EMAIL_ADDRESS>wrote:

@lattner https://github.com/lattner I think there is an XLA einsum op
but the python API seems to only be using that when executing on TPUs
https://github.com/tensorflow/tensorflow/blob/8f93f5c61cbcba20f90c867c83698285d900dc1a/tensorflow/python/ops/special_math_ops.py#L281
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/swift-apis/pull/164?email_source=notifications&email_token=AAABHRIJCZSYYK5OFLPBJ63PYR5UTA5CNFSM4HR7WEV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYEMRA#issuecomment-498091588,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABHRPRNFX3UXCNY5AZLTTPYR5UTANCNFSM4HR7WEVQ
.

--

Alex

Correction: The above comment is from me, and not Alex. I think GitHub got confused because I replied directly to the email thread.

Then in this case maybe we should wait until the einsum op is ready and use that directly. @rxwei @Dash2507 what do you think?
@alextp @bloops Are you also adding a gradient op for einsum?

Yes, the new einsum op has a python gradient implementation.
On Thu, Jun 6, 2019 at 10:10 AM Anthony Platanios<EMAIL_ADDRESS>wrote:

Then in this case maybe we should wait until the einsum op is ready and
use that directly. @rxwei https://github.com/rxwei @Dash2507
https://github.com/Dash2507 what do you think?
@alextp https://github.com/alextp @bloops https://github.com/bloops
Are you also adding a gradient op for einsum?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/swift-apis/pull/164?email_source=notifications&email_token=AAABHRMEMRED4LU3NS5F2LDPZFAG7A5CNFSM4HR7WEV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDQ5IY#issuecomment-499584675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABHRPQCPLKEDWPZ2VXXJ3PZFAG7ANCNFSM4HR7WEVQ
.

--

Alex

Then in this case maybe we should wait until the einsum op is ready and use that directly. @rxwei @Dash2507 what do you think?

That would be good. Currently swift-apis cannot depend on Foundation (it should be fixed in Swift's build-script), which is another reason this PR is being blocked.


Log Analytics data retention costs

Regarding data ingestion, I think it is clear that Desktop Analytics as its predecessor is "zero-rated" despite of the pricing tier.
However about data retention leaves some open ends in the note that says "If your workspace is on the free plan, then Desktop Analytics retains the last 30 days of "daily snapshots" that are collected in the workspace."
The article refers to "Free" pricing tier, but new subscriptions only have "Per GB (2018)" option (https://docs.microsoft.com/en-us/azure/azure-monitor/platform/manage-cost-storage#legacy-pricing-tiers).
If customer has a "Per GB (2018)" plan (only option for new subscriptions), raising the retention bar beyond 30 days would mean cost for Desktop Analytics?
As per "Data Retention" blade note, "31 days of retention is included with your pricing plan. Longer retention will incur additional charges."
Additionally, according to https://docs.microsoft.com/en-us/azure/azure-monitor/platform/manage-cost-storage#legacy-pricing-tiers, Free plans retention is only 7 days, not 30 days as stated in the note.
Thanks.

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

ID: 2d8d7ece-b19f-1431-a619-e57ce6469c28
Version Independent ID: 86a3d7a5-695b-d3d9-498c-e6b6e03169f8
Content: Desktop Analytics - Configuration Manager
Content Source: sccm/desktop-analytics/overview.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Fixed by a private PR that will publish live tomorrow


fix RPATH behaviour

Commit eaf73b9bd2c2e5ab04f3fc62e3bda2from Feb. 27th 2015 looks wrong.
It added the variable HPX_FULL_RPATH_DEFAULT, but did not make use of it.
This patch probably makes it behave as it was intended to behave, i.e.
different defaults on different platforms.
Alex

Thanks, LGTM!

Can this be merged ?

my first hpx commit :-)

@neundorf that makes you eligible for a STE||AR-GROUP sticker! @aserio would be able to send you one (or two) if you got in contact with him.

@neundorf that makes you eligible for a STE||AR-GROUP sticker! @aserio would be able to send you one (or two) if you got in contact with him.


[WIP] Expand startup integration test

Proposed Changes

Types of Changes

Verification

Testing

Linked Issues

User-Facing Change

Further Comments

Codecov Report

Merging #6030 (1043f80) into master (c3f830e) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #6030   +/-   ##
======================================
  Coverage    9.72%   9.72%
======================================
  Files         138     138
  Lines       10060   10060
======================================
  Hits          978     978
  Misses       8883    8883
  Partials      199     199

Flag
Coverage Δ

unittests
9.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


add package tag to apt::pin

I have seen issues where dsc fails to install
during the package installation phase.
This should resolve the issue by ensuring that
we are correctly pinning pin the package during
that run.

please test this

for some reason, radosgw did not come up correctly. I have never seen this failure state before. it is build number: 1046. I'll leave it up today in case someone wants to look into it.

please test this

let's get this merged


warnet: generate as files

generates ASmap files and COPYs them into the containers

@pinheadmz @josibake
If y'all want ASmap, then we ready for review in here :)

Closing for #217


The output format JSON option changed formats from old versions

Describe the bug
Old versions of sj (1.5.7 in this example) used to break out the output into title, description and results keys like in the below snippet:
$ /tmp/sj_1.5.7 automate -q -i -t 60 -u https://example.com/v2/api-docs?group=abs  -F json --get-accessible-endpoints

{"title":"Access BeeBop","description":"Access BeeBop Services (ABS). ","results":[{"status_code":"200","url":"https://example.com/monitoring/heartbeat","method":"GET","details":"OK"}]}

Now in sj version 1.8.0 this command looks like this:
$ /tmp/sj_1.8.0 automate -q -i -t 60 -u https://example.com/v2/api-docs?group=abs -F json --get-accessible-endpoints --verbose

{"Title:":"Access BeeBop","level":"info","msg":"N/A"}
{"Description:":"Access BeeBop Services (ABS). ","level":"info","msg":"N/A"}
{"Method":"GET","Preview":"alive","Status":200,"Target":"https://example.com/monitoring/heartbeat","level":"info","msg":"Endpoint accessible!"}

I think we want this output (with using the --verbose flag) to look like this:
{"title":"Access BeeBop","description":"Access BeeBop Services (ABS). ", "results":[{"method":"GET","preview":"alive","status":200,"target":"https://example.com/monitoring/heartbeat","level":"info","msg":"Endpoint accessible!"}]}

Note all the key names should be camel-cased (start with a lowercase letter) to confirm to json api standards.

Fixed in 530143b.


Feature/0.1.25

temporary channel timeout configuration
consumer channel reconnect error improvements

ignore that last comment.


Composer installation not working

Hi,
Following your readme:
$ composer require "dnadesign/silverstripe-elemental" "dev-master"

Package not found:
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for dnadesign/silverstripe-elemental dev-master -> satisfiable by dnadesign/silverstripe-elemental[dev-master].
    - dnadesign/silverstripe-elemental dev-master requires undefinedoffset/sortablegridfield ~0.5 -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.

Composer version 1.0-dev however that's not relevant.
Maybe a push to packagist is required?
Cheers,
Robbie

For reference, this is on SilverStripe 3.2.1

Seems fine now, closing.


Disable all drawing, allow only Panning

Is it possible to allow only panning, and disable all drawing?
disableDrawing: true disables everything - which isn't what I'm looking for.

Set the list of default tools to just the pan tool.


Break glass for workload identities recommended?

Hello Team,
Currently it is impossible to apply a user based break glass account to Conditional Access polices applied to workload identities.
Is a break glass Service Princpal required for CA polices applied only to workload identities? not sure if his makes sense to me. If you agree maybe this needs updating.
"at least one emergency access account needs to be excluded from all Conditional Access policies"
Br.
Joshua
[Enter feedback here]

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

ID: fff5de5d-9a97-73ff-4694-79027720b5c3
Version Independent ID: 566a8387-bbdd-8e35-13cc-f2d891bd5608
Content: Manage emergency access admin accounts - Microsoft Entra ID
Content Source: docs/identity/role-based-access-control/security-emergency-access.md
Service: active-directory
Sub-service: roles
GitHub Login: @markwahl-msft
Microsoft Alias: rolyon

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

@JBines
I'm going to assign this to the document author so they can take a look at it accordingly

Stale -eq closed... Insert sad face here


fix: cas login

https://github.com/casdoor/casdoor/issues/2229

https://github.com/casdoor/casdoor/assets/54203997/ffb7e676-b945-4bce-8630-d871c875ea9b


Add lookup to set uniqueVersion.

@TonicArtos your commits merged to https://github.com/Vorlonsoft/GradleMavenPush


The example of "libvox" doesn't work for me.

Expected behavior
I was expecting the program to work (at least for the D version).
Describe the bug
The example doesn't work.
To Reproduce
I'm trying to compile the libvox example but I have no luck. I'm trying to do it both using D (and specifically LDC) and by using C. In the C version, I also had to copy the decorations from the "libvox" module and change some stuff to make it work with a C compiler. For that reason, there may be mistakes that I made here. Having "libvox" work with a C program is very important as pretty much everyone that's gonna make a language frontend will want to bootstrap at some point so it makes sense for me to test it and report back.
In the C version, the program compiles normally but when I try to run it, I get a segmentation fault. In the D version, I'm getting linker errors. More specifically:
/usr/bin/ld: test_libvox_d.o: in function `main':
test_libvox.d:(.text.main+0x4c): undefined reference to `_D6libvox__T5SliceTxaZQk6__ctorMFNaNbNcNiAxaZSQBs__TQBoTxaZQBv'
/usr/bin/ld: test_libvox.d:(.text.main+0x98): undefined reference to `_D6libvox__T5SliceTxaZQk6__ctorMFNaNbNcNiAxaZSQBs__TQBoTxaZQBv'
/usr/bin/ld: test_libvox.d:(.text.main+0xcf): undefined reference to `_D6libvox__T5SliceTxaZQk6__ctorMFNaNbNcNiAxaZSQBs__TQBoTxaZQBv'
collect2: error: ld returned 1 exit status
Error: /usr/bin/cc failed with status: 1

I have uploaded the files in a repo so you can easily test it out yourself and examine the code and see if I made any mistakes (if you prefer to do so). You can see more info in the 'README.md' in the repo. However, of course ask me if you need anything. I'll try to see and answer as fast as I can :)
Additional context

OS: Linux
c73cd86

The compiler says undefined reference to Slice constructor. That is because you didn't include libvox.d into the compilation.
Another thing to note is that prebuilt libvox.so statically links to druntime, which may cause a problem when loaded into non-better-c D program, but check this anyway.
The intended use of libvox from regular D is either using source code or though dub package. I should document all this in the future.

Thank you! It now compiles! However, just like the C version of the program, I now get the same output as the C program. Which is the "segmentation fault". I copy-pasted the files from the "example" directory so I don't see any way I could mess up (but from my history, I would not be surprised 😅).

git clone gives me fatal: unable to access 'https://codeberg.org/rempas/libvox_error.git/': server certificate verification failed. CAfile: none CRLfile: none
Can you run the program under the gdb and print a stacktrace?
I suspect that the problem may be with libc that it was linked with during CI build. It was built on Ubuntu 20.4. What's your OS?

You can try building the .so file yourself with
vox/source> ldc2 -m64 -shared -O3 -mcpu=x86-64-v3 --d-debug -g -boundscheck=off -enable-inlining -flto=full -linkonce-templates --defaultlib=phobos2-ldc-lto,druntime-ldc-lto -fvisibility=hidden -link-defaultlib-shared=false -i c_api.d -of=../bin/libvox.so

In case this issue is the same as #46, and I guessed that the problem is -mcpu flag, you can try compiling without -mcpu=x86-64-v3

And I should probably build a version with lower CPU requirement too

What's you compiler version?

Good morning! I have tested out on my work's laptop without the mcpu=x86-64-v3 flag and it works without problems! I suppose this also fixes #46 (I haven't tested it out tho) so I will close that too! Once again, thank you for your help!


update about me

👷 Deploy Preview for joharehawkinslofthouse processing.

Name
Link

🔨 Latest commit
08bbc094210e82de3d1d0936d94b9fc01f3b225a

🔍 Latest deploy log
https://app.netlify.com/sites/joharehawkinslofthouse/deploys/661d7dad80571d0008a392e7


#861: Implement 'pubsub.client.Client'.

Wraps:

'pubsub.api' functions
'pubsub.topic.Topic' (via a factory / proxy)
'pubsub.subscription.Subscription' (via a factory / proxy)

See:
https://github.com/GoogleCloudPlatform/gcloud-python/issues/861#issuecomment-104353673

Coverage remained the same at 100.0% when pulling 4793f75b3957b1f0a56d34527ed74a62d5bf7cbb on tseaver:pubsub-client_w_proxies into 6bc4e02dcd29f52183f6e879166df54852222fa2 on GoogleCloudPlatform:master.

ISTM there is too much going on here to be considered 1 PR / 1 issue being addressed. In fact, it changes things I didn't know needed changing.
Can you squash the lint picking commit? Picking the lint before sending the PR / making a commit fixes your need to make such commits.

Coverage remained the same at 100.0% when pulling 9b4a15e4f2d27861436dc8974fb3669f73acef8e on tseaver:pubsub-client_w_proxies into 6bc4e02dcd29f52183f6e879166df54852222fa2 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling 42889a5f3cded2e000f2e585fcfc5684a17a8255 on tseaver:pubsub-client_w_proxies into 6cf0852b475c5b0a20c5dcac40bfccd1f2b2301d on GoogleCloudPlatform:master.

FWIW, I've written a couple of example "multi-tenant" scripts, one showing using the Client and one showing the using the API directly.
I honestly can't see much win for the client pattern there, but it should make it clear how it will be used.

@dhermes

ISTM there is too much going on here to be considered 1 PR / 1 issue being addressed. In fact, it changes things I didn't know needed changing.

I'm not sure I understand the objection:  this PR doesn't change any existing code -- it only adds code to implement the Client pattern for pubsub.

The objection is to the the wrapper / proxy approach (and the need to get fancy with __getattr__ for the proxy classes).
Can we design this thing before writing it?
Currently we are introduce code like
>>> topic = client.topic(...)
>>> isinstance(topic, Topic)
False

and that just isn't great.

To maintain the OO approach, we may be able to bind the clients to the objects and just do a better job handling batches/transactions.

I'm still firmly convinced that forcing the client pattern on all users the library is a mistake:  leaving it as a convenience layer "above" the current implementation allows us to experiment with the pattern without committing to it as the One True Way to use the libraries.

Well let's have that discussion before writing 500+ lines of code.

500 lines of code?  The 568 lines in the patch are 90+ lines of docs, 310+ lines of unit tests, ~30 liines of module boilerplate, and 130 lines of "real" code. Those 130 offer a working proof-of-concept that a layered approach is workable.  We can argue about the merits of proxies (DRY, easier mainteinance) vs. explicitly wrapped APIs (better tooling support?), but it is possible to offer the pattern as an option, without imposing it willy-nilly on all uses of the library.
The discussion we were having seemed to me unresolved / ungrounded -- it was all based on comparing tiny snippets, without being able to compare how the new pattern would look in real applications.  I picked pubsub as a sample, because it was the simplest, and wrote this PR to show that we could offer both patterns in a layered approach, including being able to compare real-world examples of both.  For instance, both gists I posted earlier today will work with the code in this PR.

Sorry, I was going off

the LOC thing was not particular helpful of me to point out.
I agree this is the best place to test the client pattern.
I don't think the proxies are a good fix and I do think we will likely need to just ditch the _implicit_environ behavior. People in general are un-easy about defaults that they can't see, so by having the defaults set at client instantiation we alleviate those concerns (and a fair amount of complexity).

Coverage remained the same at 100.0% when pulling cc086b6346ec6c850d82c64d13f776dc954849eb on tseaver:pubsub-client_w_proxies into 6cf0852b475c5b0a20c5dcac40bfccd1f2b2301d on GoogleCloudPlatform:master.

@tseaver I'm closing this given #910 being in. Please re-open if you think necessary.


New WinUI project asks for non-existant .NET SDK

This issue has been moved from a ticket on Developer Community.

[severity:Other] [regression] [worked-in:probem started in 17.11.2]
After upgrading to Visual Studio 17.11.2, when creating a new WinUI project, the following error message appears:

The suggested .NET SDK build numbers are one higher than the actual .NET SDK build numbers, as seen on the .NET downloads page and in the GitHub repository for .NET.
I manually resolved the issue by uninstalling the NuGet packages that were automatically included in the new project...
Microsoft.Windows.SDK.BuildTools
10.0.22621.756
10.0.26100.1
Microsoft.WindowsAppSDK
1.6.240829007
... and replacing them with older versions...
Microsoft.Windows.SDK.BuildTools
10.0.22621.755
10.0.26100.1
Microsoft.WindowsAppSDK
1.4.230913002
1.6.240829007
Note that I had to uninstall and reinstall both packages, and I did not test all the intermediate versions.

Original Comments
Feedback Bot on 9/8/2024, 07:10 PM:
(private comment, text removed)
Alan Tillekeratne on 9/10/2024, 09:14 AM:
(private comment, text removed)
Luke Westendorf [MSFT] on 9/11/2024, 10:12 AM:
(private comment, text removed)

The message is correct and can be fixed by following the instructions in the message. For more info, see microsoft/WindowsAppSDK#4696.


Add math.clamp

Adds math.clamp()

This change is

This is excellent, thank you for the contribution!
One high level comment:

Can we call this clip to mirror numpy and tensorflow?
https://docs.scipy.org/doc/numpy-1.13.0/reference/generated/numpy.clip.html
https://www.tensorflow.org/api_docs/python/tf/clip_by_value

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

src/math/webgl/clamp_gpu.ts, line 28 at r1 (raw file):

  constructor(aShape: number[], min: number, max: number) {
    this.outputShape = aShape;
    this.params = [min, max];

minor suggestion: use the minFixed and maxFixed as params (these are the cache keys to the program)

Comments from Reviewable

Done!
By the way, what's the correct way to run only specific tests with the new math test format? I tried
changing
it('propagates NaNs', math => {
      ...
    });

to
fit('propagates NaNs', math => {
      ...
    });

but that doesn't work.

Oh ha! I didn't know about fit() or fdescribe(), I'll have to add some wiring to punch that through to our custom tester.
One way to only run the tests you care about right now is to run:
./node_modules/karma/bin/karma run -- --grep="math.clip"
in another terminal, while the other npm run test is running. This will focus karma on tests that match this.

Reviewed 7 of 7 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Support for U+201C, U+201D quotes

Really cool gem!
It would be nice if it supports removing the double quotation marks that get created in files such as .xlsx, .ods, .docx etc...
This is what I've tried:
hello = '“String with them funny quotation marks”'
StrSanitizer.has_any_quote?(hello)
nil

The thing is that the " is different from the opening “ and closing quotation mark ”.

thanks a lot for opening the issue, mate.... :)
you can also fork this repo and try to add that function to your forked repo and create a pull request..... ;)
[sorry for the late reply, I was on a vacation]

the issue is fixed... thanks to @bjacquet


fix touchscreen pinch-zoom

Currently, due to a bug in the svg-pan-zoom library, pinch-zoom on touchscreens does not work; it assumes the upper-left corner of the svg viewport is at the upper-left of the screen (or maybe the whole html document).
This could possibly be fixed by switching to a different pan-zoom library.
I tried that library earlier, but it had a more serious bug where the same effect would happen on all zooming (including standard mouse-wheel zooming). However, that bug has since been fixed. So it might work to use that library now.

Is there any way to enable and disable the pinch and zoom? I am trying this for a while but unable to achieve that.

I could include that as part of this feature that I plan to implement next week: https://github.com/UC-Davis-molecular-computing/scadnano/issues/587
Do you mind if I ask what problem you'd want this to solve? Does it sometimes zoom spuriously when you don't want it to?

So here is the functionality I am trying to implement.

I have a svg on the page and a button which is a toggle to enable and disable the pan and zoom.
If I am not using pinch and zoom then it works fine.
When I use the pinch and zoom it does enables the pinch and zoom but I am not able to disable it after that.

I use svg-pan-zoom here. It works on a PC with a touch screen, but the behavior is different on an iPhone. Most of the times the reaction on a pinch-zoom is a very fast zoom-in and zoom-out effect. Sometimes I get the zoom-in action, but never the zoom-out action. I would not say pinch-zoom does now work, but it sure does not work correctly:-)


Up code quality

Hey!
I am not a Go developer :(
But I think We need to define struct name manually without magic

Or it is not possible like this?


[SPARK-29883][SQL] Improve error messages when function name is an alias

What changes were proposed in this pull request?
This PR introduces a public method setFuncName in class Expressions which is used to set the nodeName.

Why are the changes needed?
Error message is wrong when alias is used.

Does this PR introduce any user-facing change?
No

How was this patch tested?
Tested manually.
For query,
select every('true');
Output before this PR,

Error in query: cannot resolve 'bool_and('true')' due to data type mismatch: Input to function 'bool_and' should have been boolean, but it's [string].; line 1 pos 7;

After this PR,

Error in query: cannot resolve 'every('true')' due to data type mismatch: Input to function 'every' should have been boolean, but it's [string].; line 1 pos 7;

Can one of the admins verify this patch?

@gatorsmile I have now handled for BoolAnd and BoolOr. Kindly review the changes.

cc @srowen @cloud-fan

Can one of the admins verify this patch?

@gatorsmile Kindly review this PR.

ok to test

Test build #114761 has started for PR 26712 at commit 3387eef.

Merged build finished. Test PASSed.

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

Test build #114764 has started for PR 26712 at commit 4476e7e.

Merged build finished. Test PASSed.

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

Test build #114761 has finished for PR 26712 at commit 3387eef.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #114764 has finished for PR 26712 at commit 4476e7e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class BoolAnd(funcName: String, arg: Expression) extends UnevaluableBooleanAggBase(arg)
case class BoolOr(funcName: String, arg: Expression) extends UnevaluableBooleanAggBase(arg)

Merged build finished. Test FAILed.

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

Test build #114786 has started for PR 26712 at commit 77ad53f.

Merged build finished. Test PASSed.

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

Test build #114787 has started for PR 26712 at commit 404d829.

Merged build finished. Test PASSed.

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

Test build #114786 has finished for PR 26712 at commit 77ad53f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #114787 has finished for PR 26712 at commit 404d829.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

Test build #114797 has started for PR 26712 at commit 27f1a7f.

Test build #114797 has finished for PR 26712 at commit 27f1a7f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #114828 has started for PR 26712 at commit 2952898.

Merged build finished. Test PASSed.

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

Test build #114828 has finished for PR 26712 at commit 2952898.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #114842 has started for PR 26712 at commit 2952898.

Merged build finished. Test PASSed.

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

Test build #114842 has finished for PR 26712 at commit 2952898.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

Test build #114859 has started for PR 26712 at commit ab2e422.

Test build #114859 has finished for PR 26712 at commit ab2e422.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

Test build #114875 has started for PR 26712 at commit bb665e4.

Test build #114875 has finished for PR 26712 at commit bb665e4.

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

Merged build finished. Test PASSed.

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

There are other function with alias name example VarianceSamp, StddevSamp. I think we should also use expressionWithAlias for registering them?

Should we change them in this PR?

I'm fine either way.

Ok, I will handle them in different PR with new JIRA.

Merged build finished. Test PASSed.

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

Test build #114899 has started for PR 26712 at commit 3c87222.

Test build #114899 has finished for PR 26712 at commit 3c87222.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #114903 has started for PR 26712 at commit 17c91f4.

Merged build finished. Test PASSed.

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

Test build #114903 has finished for PR 26712 at commit 17c91f4.

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

Merged build finished. Test PASSed.

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

cc @cloud-fan

cc @cloud-fan

Test build #114940 has started for PR 26712 at commit d07d261.

Merged build finished. Test PASSed.

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

Test build #114940 has finished for PR 26712 at commit d07d261.

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

Merged build finished. Test PASSed.

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

@srowen Kindly review.

I'm OK with it if @cloud-fan is.

thanks, merging to master!

Thanks @cloud-fan


parameter popup behind dev flag

let's hope it works now :)

@devoncarew @lukechurch  I'm again rewriting this. I try to make the parameter popup so that it is its own class like DartCompleter, do you think that is a good idea ?

see https://github.com/dart-lang/dart-pad/pull/219


wiliwili: init at 1.4.1

Description of changes
The current dependencies on darwin may still be wrong or incomplete, but I cannot test on darwin for the time being.
Tested on Linux, with all functionalities:

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build wiliwili

Result of nixpkgs-review pr 324636 run on aarch64-linux 1

1 package built:

wiliwili


Update bazel toolchains dependency.

PiperOrigin-RevId: 186650360

The failure looks legitimate, have we seen this before?

@gunan I cannot tell since tests didn't even build prior to this. Can I still merge and debug that test after?

I was thinking when we were doing the release.
But sure, let's first merge and then debug. I think this test was passing when we did 1.6, so I would like to avoid disabling the test for 1.6 release.


test(31): validates control headers and routing

Thanks, Bartosz. All PRs merged.
I will test the two new tasks shell scripts on OCP4 and then convert them to go tests later.

You are welcome @yxun. We also do have some go-based tests for our istio-workspace tool, if you are interested - take a look at e2e folder in the repo: https://github.com/aslakknutsen/istio-workspace/


demo page submit 500 error

demo page submit button now got 500 error
https://getrector.org/demo/1ec62bbb-c11a-6c4c-8a6b-15e2ed46e704
@TomasVotruba is it related with remove sensio fw commit https://github.com/rectorphp/getrector.org/commit/1327899978441d8f28a20cc46d93c394c6270701 or update to rector 0.12.9 commit https://github.com/rectorphp/getrector.org/commit/9a75335f3d4dacbe65ad18b93f02bd4141d00b94 ?

@TomasVotruba revert back to retor 0.12.8 seems still error at demo page submit
https://getrector.org/demo/1ec62bdd-d843-6104-b2d1-df501327b691
Let's revert back to remove sensio fw commit.

@TomasVotruba revert the remove sensio fw seems solve the demo page submit error
https://getrector.org/demo/1ec62bf8-bf08-6e1c-85b1-ad1b9028bf0b
🎉

Thank you.
Have you found, what exactly is the bug there?

I didn't try locally yet, is the error not saved or reported via email or some logging service for it?

Not yet. There is some @todo to add monolog, but I could not fine time to implement it


Allow AdditionalN fields to use depends_on

Previously we hadn't come across a framework that needed this.
Fortunately it's not a complicated addition.

🙏


Replace moment with dayjs & base-cms dep upgrades

 Convert remaining monorail theme content body's to use new ad injection component


Allow farmer to set extra fee on its nodes

Specifications

This feature is about allowing a farmer to get extra income from the node by setting an extra fee.
There is no specific objective reason or metric (good hardware quality, extra GPU capacity, ...) for adding this extra fee.
It is just the farmer's freedom to evaluate how much he should get extra from its node.
By setting this extra fee the node will ONLY be eligible for dedicated node use (meaning the full node is rent ie. under a rent contract).
Also while billing, unlike the regular billed amount that is distributed following the traditional schema, the full extra fee directly goes to farmer's account.
The extra fee will be expressed in mUSD/month and will require a convertion in TFT for billing purpose.

Implementation details
To implement this feature we will need to add some new items in TFGrid pallet:

a storage map called DedicatedNodesExtraFee that links a node id to an extra fee (type u64).
The map type will be OptionQuery since default value will be None, which means there will be no extra fee billed in a rent contract context.
No migration will be required by adding this storage.

a set_dedicated_node_extra_fee(node_id, extra_fee_factor) extrinsic that can be called by the node's owner (farmer).
It will not be possible to modify the value by calling this extrinsic while a rent contract is running on the node.

Further considerations

The need of setting limits to extra fee (a max value)?
Can a sudo authority call set_dedicated_node_extra_fee()?
Do we apply the user discounts to the extra fee? dedicated discount = 50% + staking discount = up to 60%

For your extra questions:

No need to set limits
No sudo
No discount

Verified on devnet.
Setting an extra fee for a node is now allowed from the dashboard

and as seen from graphql it is reflected there and also the node is set as dedicated once the extra fee is added.


Adding coin rando to the settings string

Adding coin_rando to Settings.py so it can be stored in setting strings.

This is being handled.


Test Unito app

Testing bi-directional plugin testing.

Test GitHub > Jira

➤ Rebecca Fitzhugh commented:
Test Jira > GitHub


Start with a simple $listeners example

Documentation change only.
It took me a few passes through this documentation to understand the simple/common use case for $listeners, since it rolls right into the more complicated use for supporting v-model. Starting with a simple explicit example will hopefully make it easier for new developers to catch this use case.

@Meekohi thank you for working on this!
@chrisvfritz could you please give your review on this PR?


feat!: add entity names to problem models

Enables us to convert Superset datasets from virtual to physical datasets and pull directly from these models.

Thanks for the pull request, @SoryRawyer!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.


istioctl analyze set warn for no caCertificates in DestinationRule

Part of https://github.com/istio/istio/issues/27960
Based on https://github.com/istio/istio/issues/27960#issuecomment-708655493

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ea0e0f6342a5a6d90cd0148158e31c679b32d231
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

@esnible PTAL.


How to navigate in NativeBase

I looked the NativeBase API.
The question is I didn't find out how to navigate scenes. (using React Navigation ?)
please somebody help me. thanks a lot.

@li-zhenyu you can use react-native-router-flux too for navigation

@deneuv34 any guidance or Docs that you can link to?
Thanks

@deneuv34 react-native-router-flux is great, thanks

@zohaibr you can go here for complete information

@li-zhenyu your welcome :+1:

@deneuv34
There is nothing there about configuring with Native Base, or have I missed something?

I don't think you need docs separately for react-native-router-flux. Here's how we've used it with NativeBase in our KitchenSink App. https://github.com/GeekyAnts/NativeBase-KitchenSink

Nativebase is only a library for UI components and has nothing to do with navigation at the moment. You can use any navigation library (react-navigation, react-native-router-flux etc) available for react-native.

@sankhadeeproy007 great! That works just fine for at least me!
@uxman-sherwani yes I know Native Base is just a library for UI components though for new react native users like me it the whole navigation part of react native is a bit confusing.
The confusing part with combining react-native-router-flux with Native Base for me is that react-native-router-flux has a build-in navbar support which is not the Native Base Header-tag. Therefore it's also a bit confusing how to setup and use the Native Base anatomy tags Container, Header, Content and Footer.

@andidev We can just have hideNavBar set at our initial route. That will hide the RNRF navbar and we can use NativeBase navbar with it.

Thanks! Works like a charm and its really easy to configure.


Page names with "/" in them create unnecessary levels of hierarchy

Originally from Bad3r / Bader on discord.

When a page title has a / in it, it creates an additional split in the page hierarchy, so you get empty intermediary pages. Anything in the page title must be sanitized.

This is a bug with Logseq, and the suggested work-around is not great. https://discuss.logseq.com/t/escaping-hierarchy-behavior-for-page-titles-with-a-forward-slash/9369/6


MacOS: wrong path to dtd file

path to dtd file should be
+<!DOCTYPE keyboard SYSTEM "file:///System/Library/DTDs/KeyboardLayout.dtd">
-<!DOCTYPE keyboard SYSTEM "file://localhost/System/Library/DTDs/KeyboardLayout.dtd">

Double check it though, because I used a file generated by an older version of kalamine

Could it depend on the macOS version?

Could it depend on the macOS version?

Maybe, but I’d find it surprising to have localhost at the root without a / prefix even.
Just in case though, I’m on macOS Sonoma (14.0)

See the reference doc:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE keyboard SYSTEM "file://localhost/System/Library/DTDs/KeyboardLayout.dtd">

The reference doc is marked as obsolete, though no other file is provided. So it might have changed.
Having any way to validate this file would be a great step forward. It can be loaded with lxml but not with the standard Python XML library, nor with any web browser I know, because of the numeric entities e.g.  (pass-through) and many other similar ones that do not correspond to printable characters. If you know a way to work around this, I’m all ears !

So it’s not standard XML?

It is. But it contains numeric character references that do not correspond to printable characters, and most XML parsers block on that.

While the syntax of SGML does not prohibit references to invalid or unassigned code points, such as , SGML-derived markup languages such as HTML and XML can, and often do, restrict numeric character references to only those code points that are assigned to characters.

https://en.wikipedia.org/wiki/Numeric_character_reference#Restrictions

See the reference doc:

Didn’t know that. Not sure whether the issue is that someone didn’t test their docs or if something actually changed


Evaluation Error

I try run the evaluation of this repository
but some issues popped out in the terminal
I want to know how to setup all the CKPT path in the eval.sh
Also, I show my terminal output in the follwing picture
Thanks for helping me

Below is my eval.sh
export EPOCHS= (47)
export CKPT_DIR="/tmp2/danzel/GR-MG/checkpoints/policy"
/// export SD_CKPT="/PATH_TO_GOAL_GEN_MODEL_CKPT/epoch=49-step=51450.ckpt"
export SD_CKPT="/tmp2/danzel/GR-MG/checkpoints/goal/goal_gen.ckpt"
export MESA_GL_VERSION_OVERRIDE=3.3
echo $EPOCHS
echo $CKPT_DIR
/// sudo chmod 777 -R ${CKPT_DIR}
export COUNTER=1
/// Use a for loop to iterate through a list
for epoch in "${EPOCHS[@]}"; do
export COUNTER=$((${COUNTER} + 1))
export CUDA_VISIBLE_DEVICES=${COUNTER}
python3 evaluate/eval.py
--ckpt_dir ${CKPT_DIR}
--epoch ${epoch}
--ip2p_ckpt_path ${SD_CKPT}
--config_path ${@:1} &
done
wait

Hi,
I believe your evaluation script is mostly correct. The main issue seems to stem from the torch.load(ckpt_path) line. Please ensure that my released checkpoint is placed in the correct directory and that the checkpoint filename remains unchanged. This is important because the filename is used to match the epoch variable.

I fixed the filename issue but face the problem above
In goal_gen/evaluate.py
line 30 pretrained_model_dir = "/mnt/bn/lpy-lq/stable_diffusion/instruct-pix2pix"
how to get the config.json

I fix the problem haha
Thanks for helping me
Also, I'm working on some experiment on GR-mg
We try to extend the idea of progress% with LLM or video generate model to generate better token

I'm thrilled to hear about your interest in my project. Come on!


adding custom attribute to message not storing message in Archive table on server

I am working on ionic 3, I want to add some custom attributes while sending message, for that i have followed the steps for creating plugin. my code is as follow...
`sendMsg() {
    console.log("Sending message");

    function customMessage(client, stanzas) {
      const NS = 'http://www.w3.org/2005/Atom';
      var types = stanzas.utils;

      const messageAttribute = stanzas.define({
        name: 'messageAttribute',
        element: 'messageAttribute',
        namespace: NS,
        fields: {
          title: types.textSub(NS, 'title'),
          summary: types.textSub(NS, 'summary'),
          published: types.textSub(NS, 'published'),
          updated: types.textSub(NS, 'updated'),
          cont: types.textSub(NS, 'cont')
        }
      });

      stanzas.withMessage((Message) => {
        stanzas.extend(Message, messageAttribute);
      });
    }

    this.client.use(customMessage);

    this.client.sendMessage({
      to: this.recep,
      body: "",
      messageAttribute: {
        'title': "some title",
        'summary': "message",
        'published': "time stamp here",
        'updated': "time stamp here",
        'cont': "cht"
      }
    });
   console.log("Message sent " + this.sMsg);
  }`

but doing this way message are not being stored in Archive table on server. that will create a problem to get the history from the server. if we use the simple code then that messages being stored on Archive table on server. simple code as follow..
this.client.sendMessage({
      to: this.recep,
      body: this.sMsg
    });

in simple code we can only send message as a string inside body.

Your server is only archiving messages which contain a body element with text, which is a pretty common archiving configuration. One trick would be trying to include a dummy body text to trigger message archiving, but you'd have to check if the server is storing and returning the full stanza or just extracting and saving the body text.
You're doing everything correctly with extending Stanza to include the additional fields, but you'll need to adjust your server to get what you want.

@legastero thank you for clearification.


tests, integration: unmanaged linux bridge keeps unmanaged port

When an unmanaged bridge with strictly unmanaged ports is managed by
NetworkManager, it should keep the strictly unmanaged ports.
Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

This fixture is more like external_managed_bridge_with_unmanaged_ports.
And please the test in tests/nm folder as this is NetworkManager related.

Changes done, thank you!


Replace hexAddress with pubKeyHash

In many examples we use hexAddress as variable name, but it's not very clear and might lead to errors if trying to use the same methods for account/nft ids.
So replace all, also the snake_case variants in Python
Also rename the methods bech32_to_hex() -> bech32_to_pub_key_hash() and hex_to_bech32() -> pub_key_hash_to_bech32() (same with camelCase in JS)

Not needed because of https://github.com/iotaledger/iota-sdk/issues/2079


Test response-middleware in the request_data context tests.

Add an additional step to the request_data context test. This checks if items stored a request.ctx are able to be accessed from a response-middleware after a response is issued.
This is to help debug and reproduce the error described by user verdebirth here: https://community.sanicframework.org/t/issue-with-request-ctx-in-response-middleware/611

Unfortunately even after adding this extra test and running it through our test suite using Tox, I'm still not able to reproduce the error described by verdebirth here: https://community.sanicframework.org/t/issue-with-request-ctx-in-response-middleware/611

Note; linter is failing due to this issue: https://github.com/huge-success/sanic/issues/1889

Placing on hold until #1889 is merged to fix isort

All tests passed now. Can be merged.


just one line fizz-buzz ;)

inspired by list comprehension  ,
this loop prints number and the fizz-buzz word depending on the condition satisfied

Thank you for your PR!
Unfortunately a solution similar to yours has already been submitted :/
The goal is to find creative/abstract new solutions to FizzBuzz.
See The top 5 samples here.
Thanks anyway! :)

Thank you for your PR!
Unfortunately a solution similar to yours has already been submitted :/
The goal is to find creative/abstract new solutions to FizzBuzz.
See The top 5 samples here.
Thanks anyway! :)

no problem , thanks


Localsation:UX issue.

- when we change language from Wallet Settings> Currency and Language.

Some text overlaps.
Some icons are appearing above the text.Some text is coming above the icon.
App version is not showing in app info.

When we change the language, the icon appears above the text.

Verified this issue on dev app v2.0.75(468)


Fix an edge case in GenericCloner which was not generating end_borrows for store_borrow

Generic Cloner creates store_borrow for in_guaranteed args in OSSA. We use PrunedLiveness to compute the boundary of store_borrow for inserting end_borrows. However, if there is an escape boundary cannot be found, and we insert end_borrows at function exits. FunctionExists are populated while cloning. There is an edgecase, where the Generic Cloner is explicitly creating return instructions, these were not inserted in FunctionExits, thereby missing an end_borrow on that path. This PR fixes it.
rdar://99874076

@swift-ci test


Search returns generic error

After following the deployment guide all other functions of the app work except for search. It returns a generic error as below.

No specific errors & app insights does not seem to be configured with the deployment.

I am experiencing the same issue as @Koxzi95 after deploying it on our tenant. Search is not working. Any fix available?

Looks like the application instrumentation key name is mis-matched in ARM deployment templates which is causing the issue. We are working on a fix and will update it ASAP.
As a workaround, can you try adding AppInsightsInstrumentationKey in Configuration settings and provide the value of app insights created during deployment. So for e.g. your base resource name while creating the deployment is "Contoso-Expert-Finder" then application insight resource name would be "Contoso-Expert-Finder" as well.

The issue fixed by @abbodh PR #9 is in PR #10

This issue is still present, experienced the same problem when deploying for a customer yesterday. API app reg permissions have been double-checked and are correct as per the deployment guide.


Track time from upload to version creation

The upload is created even before the validator is called on it, right?
r+wc

Yes, the upload is created right after the form is processed (i.e. the posted file is received). The next step is validation but there is also some task chaining to finally create the version. We already have validation timing so this new metric would allow us to overlay a slightly more complete snapshot of the end to end version creation process.


Liquibase should not fail when change log has only databaseChangeLog tag

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This pr created for the https://github.com/liquibase/liquibase/issues/4223 issue. I have to compare xml and yml behavior for understanding expected behavior.
Xml behavior
$ ./liquibase update
####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ##
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ##
##                                                ##
####################################################
Starting Liquibase at 21:56:52 (version 4.22.0 #9559 built at 2023-05-10 20:45+0000)
Liquibase Version: 4.22.0
Liquibase Open Source 4.22.0 by Liquibase
Database is up to date, no changesets to execute

UPDATE SUMMARY
Run:                          0
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:            0

Liquibase command 'update' was executed successfully.

Json behavior
$ ./liquibase update
####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ##
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ##
##                                                ##
####################################################
Starting Liquibase at 22:00:37 (version 4.22.0 #9559 built at 2023-05-10 20:45+0000)
Liquibase Version: 4.22.0
Liquibase Open Source 4.22.0 by Liquibase

Unexpected error running Liquibase: Could not find databaseChangeLog node

For more information, please use the --log-level flag

After changes all test pass in liquibase.parser.core.yaml.YamlChangeLogParser_RealFile_Test.
Things to worry about
This is my first pr for Liquibase. I can broke things by accident :) Maybe my unit test wont enough for it. I test it with only unit test.

Initial/Pre-Review Thoughts
The changes make sense to me, @macorapci . And thanks for the tests on it.
The json support extends from the yaml class, so funny that doesn't have the same problem, but the structure maybe comes back differently enough to be fine..
Questions I have:

None

Potential risks:

None

What could make the full review difficult:

Nothing

I try to understand reading the code why json works as expected. I have to debug for understand misterio of json. I will debug in my free time. I will share with you when i figure it out. @nvoxland

I'm curious so I couldn't stand it any more for debugging. As @TymofiiKritsak mention in https://github.com/liquibase/liquibase/issues/4223#issuecomment-1552931900, here our empty object format for json and yml.
Json
{
  "databaseChangeLog": []
}

Yml
databaseChangeLog:

Different behavior cause
When we want databaseChangeLog for JSON, we get empty array. When we want databaseChangeLog for XML, we get null. This is why we are getting different behavior JSON and YML. @nvoxland

@nvoxland says that this looks like a reasonable ask. However, we need to validate that the stated YAML above is valid. If it is, then we would like to ensure this works.

You're very welcome  @XDelphiGrl
I respect to any decision what round table decision :) I have only wish about that. Could you explain me, why and how you declare the standard because i am really curious about the topic? @kevin-atx

You're very welcome @XDelphiGrl
I respect to any decision what round table decision :) I have only wish about that. Could you explain me, why and how you declare the standard because i am really curious about the topic? @kevin-atx

Hello, @macorapci!
I might be misunderstanding your question, but are you asking about how Liquibase chooses what to accept as a PR? Or perhaps us to explain how we decide what is standard YAML that is acceptable as a databaseChangeLog ?

I could not explain very well myself. I tried to ask for the second option from the options you provided. (How we decide what is standard YAML that is acceptable as a databaseChangeLog?) Thanks for your try to understand me :) @XDelphiGrl

I could not explain very well myself. I tried to ask for the second option from the options you provided. (How we decide what is standard YAML that is acceptable as a databaseChangeLog?) Thanks for your try to understand me :) @XDelphiGrl

Thank you for the reply! Apologies that I did not understand you at first; if it helps, sometimes I don't even understand myself, let alone anyone else! :)
The official YAML standard is here: https://yaml.org/spec/1.2.2/. A less-overwhelming explanation is here: https://spacelift.io/blog/yaml.  To determine if the YAML changelog is valid, we can use a YAML validator to see if it accepts the syntax of the YAML changelog example. If so, then this is definitely a bug and should be fixed. However, if it turns out this is not valid YAML syntax, then there is a decsion to make:

Fix Liquibase to output a console message that the YAML is not valid. That would be more helpful than the "cannot find databasechangelog node" message.
Add some tolerance to Liquibase to understand that the user intends for this to be an empty (no changesets) changelog and treat it as if it is valid. (It appears this is what your fix does, although I am not a developer so please forgive me if I misunderstand!)

Does that answer your question?

A few functional tests that appear unrelated to this fix are failing; I believe this is due to the code in pro-tests being either ahead or behind liquibase/liquibase. I'm rerunning Oracle and Postgres regressions now to see if the issue is resolved.
https://github.com/liquibase/liquibase-pro-tests/actions/runs/5260166058


[discussion] Add links to packages in README?

The READ me is an exceptionally good project landing page!
A posible tiny improvement is to make each package name in the table a link to the packages source. At least I just wanted to do, even though it's easy to find the package (especially when you realise it's a monrepo layout)

Seemed easy to do, so I just did that. Thanks for suggesting!

Thanks. I quite forgot to do it if I got no negative response :(


Revert unit test coverage changes

Revert my commits from last week, speeding up unit test runs until #4713 is resolved.
cc @filbranden @bgrant0607

Merging the revert so we get back where we were and Travis is responsive again.

Thanks.


Include user upvoted / downvoted

In the user preferences menu, there's a "make my votes public" option. I imagine logging in as the user would be easier than trying to archive them with only public data, but this should be sufficient as-is to allow access to /user/<name>/upvoted and /user/<name>/downvoted.

Sure, this would work similarly to #2. It's straightforward to import them from the archive. Polling them from the live site is trickier, but doable.
I have some other work I want to prioritize first, but I can likely add this as well (especially if other people 👍 it)


Persist store in DB instead of JSON

Problem statement
In order to save the Radio's state between reruns, currently we persist the state in a JSON file. That does the job of seamlessly restarting the Radio, but as Radio traffic, features, message types, collected data, etc, increases we will need a more scaleable approach to data persistence.
Expectation proposal
We should adopt an approach, similar to the one in Listener Radio, which uses sqlx.
By default, it could use sqlite and still keep all the data in a local file, but more advanced users should be able to provide a postgres endpoint and store the Radio's data there.
Open questions
Should we still keep JSON as an option?

Create migration file and embed the migration operations in the binary
Define sqlx schema for publicPOIMessage, attestations, comparisonResult, upgradeIntentMessage
Define query resolver (read and write sql operations to DB)
Currently we track validated messages in a PersistedState struct, and write to the stateful json with a fixed interval. We can consider writing to DB in a similar way with batch write operations
Make sure to swap out the resolvers for the API server
If time allows, we can utilize benchmarks to measure performance improvements


Add Sails web framework

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆
Links to project:

https://sailsjs.com/
https://github.com/balderdashy/sails

21K stars on Github.

I found another PR explaining why it's missing - https://github.com/sindresorhus/awesome-nodejs/pull/998. Next time I will check history before sending PR, sorry for the noise.


box_check_update is incompatible with Vagrant 1.4

When running beaker with Vagrant 1.4, Vagrant cannot start the machines due to an unknown configuration stanza:
vm:
* The following settings shouldn't exist: box_check_update

This needs to be filed internally for tracking.

Filed internally, assigned to @sschneid.

Follow up here:
https://tickets.puppetlabs.com/browse/BKR-15


[BEAM-7388] Reify PTransform for Python SDK

This PR adds useful Reify PTransforms similar to the Java SDK.
It will make code much cleaner. Eg: https://github.com/apache/beam/pull/8589
Related JIRA: https://issues.apache.org/jira/browse/BEAM-7388

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @robinyqiu
This contains the same Map(lambda x: x) hack

Rebased with master to resolve merge conflicts.

Thanks Tanay! These are great. Sorru about the delay.

ReifyTest.test_window fails in DirectRunner due to 'assign_context.window should not be None.', filed https://issues.apache.org/jira/browse/BEAM-7499


List element still has a selectedFg color even when all inputs are disabled.

Maybe I'm just unaware of an option and missed it while scouring the documentation, but I can't seem to figure out how to use a list element in a readonly manner. I can disable the keys, input, and mouse properties which seem to work fine, but I can't ever seem to get rid of the styling on the first item in the list (the default selected item).
I set selectedFg and selectedBg to the same colors as fg and bg, but I'm using ANSI escape codes to color some special characters in my list. For some reason on the selected item only, my escape codes are being overridden.

You can see the first list item's status icon is green where the rest are red. Note however that the ANSI bold escape sequence is still working. Only the color seems to be overridden.
Here is my code for the list:
blessed.list({
  selectedFg: 'green',
  selectedBg: 'black',
  fg: 'green',
  keys: false,
  mouse: false,
  input: false
});

This horrible workaround will probably work for now: list._isList = true;.
I never thought of a non-interactive list to be honest. I can add that as an option.

I believe these lines here are responsible, but I'm not having an easy time understanding what line 3341 is doing or how best to modify blessed so I can remove the selected item styling.

That would be a great option. If I could set something like readonly: true that would be awesome :)

That should be list._isList = false;.*

No worries, I figured it was a typo ;)

That is a gross hack for sure, but it worked :D

Also, try not to use selectedFg/Bg anymore. Those are deprecated. Try: style: { selected: { fg: 'green' } }. I want to eventually remove the old Fg/Bg options.

Good call. I agree with that move. I think a good first step would be to remove them from the docs. That's the only reason I started using them :)


yaml format highlighting for GMEdit.

May be very difficult, I dont know.

Should follow json schema, which would be really difficult.
Maybe better to just recommend they use vscode for it


Icons don't resize with text

WCAG 2.1 requires that user can resize text to at least 200% . When text is resized (see https://github.com/alphagov/govuk-frontend/issues/1519), our icons don't resize with text. We might not wish them to, this issue is partly for reference.
Crown icon when text resized to 32 (16 x 2 = 200%)
(Once https://github.com/alphagov/govuk-frontend/issues/1568 is fixed)

Warning icon when text resized to 200%

Arrow icon when text resized to 200%

We're going to only fix the icons that loose their meaning when scaled up, in the examples shown here that means the warning icon but there may be other components, so we should double check.


Make the @yamada-ui/infinite-scroll-area component headless

script: make-component-headless
package: @yamada-ui/infinite-scroll-area
Description
Currently, the @yamada-ui/infinite-scroll-area component has minimal styles set within the component's source code.
We want to make this style transferable to the theme and make the component headless, enabling more flexible UI customization.
Problem Statement/Justification
By making the @yamada-ui/infinite-scroll-area component headless, we can achieve more flexible styling tailored to the project.
Proposed Solution or API
The styles within the component are mostly defined by css: CSSUIObject and set to a prop named __css. We will transfer these styles to the packages/theme/src/components.
The code below is just an example and not the actual code.
packages/components/input/src/input-group.tsx
const css: CSSUIObject = {
- width: "100%",
- display: "flex",
- position: "relative",
  ...styles.container,
}

packages/theme/src/components/input.ts
baseStyle: {
  container: {
+   width: "100%",
+   display: "flex",
+   position: "relative",
  },
  field: {
    width: "100%",
    minWidth: 0,
    outline: 0,
    position: "relative",
    appearance: "none",
    transitionProperty: "common",
    transitionDuration: "normal",
    _disabled: {
      opacity: 0.4,
      cursor: "not-allowed",
    },
  },
  element: {
    color: ["blackAlpha.600", "whiteAlpha.700"],
  },
},

[!TIP]
In cases where the styles within the component are dynamically changed, there may be instances where it is not possible to transfer the styles to the theme.
In such cases, it needs to be discussed in this issue. Please feel free to send comments to this issue.

Additional Information
The @yamada-ui/infinite-scroll-area component exists in packages/components/infinite-scroll-area/src. You need to check all the components in this folder and if they contain styles internally, you need to modify them.
This change could have a significant impact on projects using Yamada UI, so we will work on it within the scope of v2.0.
Please create the branch for working on this issue from the remote branch v2.0, and direct your pull requests to the v2.0 branch as well.
Please select major for the changeset and create a pull request.

Hi,
Can you asssign me to this issue?

@Hayato1031
Hi, thanks for the comment!
Yes, pls.

I wanna ask you one.
In packages/theme/src/components, there are no file which is named infinite-scroll-area.ts.
Do I have to make the file?

@hirotomoyamada
sorry, I forfot mention to you.
Tell me what do I have to do to this component.

@Hayato1031
Hi, thanks for the comment!
Sorry. The InfiniteScrollArea component isn't themed, right? First of all, we need to theme it, but it doesn't seem like it's at the level of a "good first issue".

Related #2030

@hirotomoyamada
Thanks for your reply.
I got it, I stop working on this issue until you solve the problem.
If there is something what I can do, please tell me.

@Hayato1031
#2031
Once this PR is merged, you can work on it.

@hirotomoyamada
I cant believe that how fast you work on it.
Thanks for your cooperation.

@hirotomoyamada
Hi
Thanks for working on it.
I have a question.
You add theming to the infinite-scroll-area component on the PR, but the change is merged to the main branch right?
For working on this issue, I have to make new branch from v2.0.
But there are no changes on v2.0 branch, therefore still I cant make new working branch.
What can I do for it?

@Hayato1031
Hi, thanks for the comment!
I have now merged main:)

@hirotomoyamada
You mean, I should make new branch from main, and make PR to V2.0?
I thought that I have to make new branch from V2.0, and make PR to V2.0.

@Hayato1031
It has been merged into v2.0, so please create a branch from v2.0.

Fixed #2058


Running rewindui storybook in local throws error with node v17 or greater.

Issue Description:
When running the rewindui storybook locally, an error is encountered when using Node.js version 17 or greater. The command line displays the following error message: Error: error:0308010C:digital envelope routines::unsupported.
Solution:
To resolve this issue, follow the steps below based on your operating system:
For Windows:

Open the command prompt (cmd).
Run the following command:

set NODE_OPTIONS=--openssl-legacy-provider
For Unix, Linux, and macOS:

Open the terminal.
Run the following command:

export NODE_OPTIONS=--openssl-legacy-provider
After setting the NODE_OPTIONS environment variable, navigate to the storybook folder and run the following command:
pnpm dev
This should start the rewindui storybook without encountering the "unsupported" error when using Node.js version 17 or higher.
Please note that these steps are specific to resolving the mentioned error related to the rewindui storybook. If you encounter any other issues or errors, please provide additional details for further assistance.
Contributor Agreement:
I confirm that I have read and agree to the project's contributor guidelines or licensing terms.

Hello @riyajahamedi
Thank you for bringing this up!
Right now rewind-ui is using storybook 6.5.
I am about to upgrade to version 7 soon, but I keep postponing this as it has introduced many breaking changes and it will take some time to do so.
As a workaround to your issue if you don't want to use node v16 you can use nvm to handle multiple node versions.
I will let you know once I upgrade to latest storybook.

@riyajahamedi I have just pushed an update, upgrading to storybook 7, which supports node v18.
Could you give it a test and let me know if everything works fine now for you?

@NickDunas Everything works fine after upgrading to storybook 7 👍


⬆  added back top button

Adding scroll to top button in the website #36

@edilson258 Kindly sign off your commits otherwise I can't merge it into main.
__
  Summary: :hammer_and_wrench: This code needs a fix  |  Tags: Not reusable


Make ChefZero aware of load balancers

We have some complex reasons to hide a ChefZero behind an SSL nginx proxy.
One problem that suddenly arose with this is that URLs returned by
posting to /environment/foo/cookbook_versions use the protocol of the
internal webrick which is always plain http. This causes the chef client
to retrieve these urls on the https port but with an encrypted payload.
Support this situation by using the HTTP_X_FORWARDED_PROTO CGI variable
if it is available.

👍

👍