Example code/docs on interoping with other libraries/frameworks

I have some large sveltejs projects with large components. I'd like to introduce Solidjs to more easily decompose the large components into tsx functions. Are there any good examples of embedding SolidJS into another library? It can be generalized, accounting for the compilation, dom/ssr rendering, reactive event wiring, signals, hydration, cleanup, etc.
Svelte kit, next.js, vuex are all powerful PWA libraries. Until Solidjs has a similar project, it may be useful to wrap Solidjs within one of these projects.

Client only is probably pretty simple and similar in most frameworks. You get a ref and call Solid's render function in the suitable place according to the framework.
But generalizable is hard. SSR has other constraints depending on how the host works. VDOM, strings etc..Building might be ok but like Solid and React both having JSX would be a dance. Have you ever seen examples of docs like this before? I think there are a lot of pitfalls and it would take doing the integrations and writing detailed guides for each.

Yeah I don't know what to do with this one. I could have a better example around using refs to import 3rd parties but the other side is really wide open and not particularly easy if even possible. I will leave this open to gather some feedback but I don't have any plans for the moment.

As discussed in the Help channel on discord, In the case of Sveltejs, it would be useful to have analogs to some of Svelte's concepts such as bind: being something like use:bindAttribute=['value', getter, setter]

Yeah I see separate packages being built for these cases. I think the contributors would need to be intimately familiar with both frameworks to do this and up to date on the latest in each of these frameworks. I'm sure there would be some people in this scenario that could really benefit from this and also be the best people to maintain the effort. I haven't seen libraries like this before as I said earlier so I don't know if there is any precedent but would look forward to supporting anyone willing to prove it out.

I don't really have much in actionable items here. Solid won't integrate with existing meta frameworks directly. And interopt points with libraries depend on each library. I've seen some interesting solutions to the problem like: https://www.npmjs.com/package/react-solid-bridge
And I made these:
https://codesandbox.io/s/solid-react-hoc-8m2yd
https://codesandbox.io/s/react-solid-hoc-5lmt2
But I'm leaving it here. This is just beyond the scope of the core project to maintain I think.


Typo in 1st step of the 4-small-steps-quick-start-tutorial

I am a beginner in Laravel and stumpled over Orchid and it seems exactly what I was looking for. Great work - thank you.
In the first step of the nice 4-small-steps-quick-start at https://orchid.software/en/docs/quickstart/ there seems to be a small problem. I was not able to enter any mail address in the Relation field. There was also no stack trace to figure out whats wrong. Only hint was a message below the input field "The results could not be loaded".
So I changed the line
use App\User;
to
use App\Models\User;
and then it worked.
Regards
Jens

Hey @jensmusleh, thanks. Before Laravel 8, there was no Models directory in the structure.
I brought in the edits by indicating it. You can also do it yourself. Each page has an edit button.


move screen.show_event() into MQTT lib

check if screen.show_event can be moved into boolean OXRS_MQTT::publishStatus(JsonObject json)
This would elimnate a further screen call from the FW

Not sure you can know what the event will be or look like. I think the
event display on screen needs to be controlled by the firmware.
Who knows what someone will want to display...
On Sat, 11 Sep 2021, 06:31 moinmoin-sh, @.***> wrote:

check if screen.show_event can be moved into boolean
OXRS_MQTT::publishStatus(JsonObject json)
This would elimnate a further screen call from the FW
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OXRS-IO/OXRS-IO-MQTT-ESP32-LIB/issues/7, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGTR2VM5JAAUKN7HGR7QQTUBJFJDANCNFSM5DZ3ZBVQ
.

OK, agree
but looked very promissing for our use case


add sub-package rcv

Useful for dealing with SII RCV ("Registro de Compras y Ventas").
Its main feature is the function process_rcv_csv_file.
Test have not been implemented.
Other
Add sub-package contribuyente
For code related to "contribuyente" (tax payer).
Just constants for the moment.
Add sub-package dte
For code related to "dte" (Documento Tributario Electrónico).
Just an enum and constants for the moment.
libs: add module tz_utils
Utils for dealing with timezone-aware datetime objects.
Test have not been implemented.
libs: add module mm_utils
Custom marshmallow field CustomMarshmallowDateField.
Test have not been implemented.

Codecov Report

Merging #8 into develop will decrease coverage by 9.77%.
The diff coverage is 55.08%.

@@             Coverage Diff             @@
##           develop       #8      +/-   ##
===========================================
- Coverage    73.46%   63.69%   -9.78%
===========================================
  Files            5       11       +6
  Lines          147      314     +167
  Branches        14       25      +11
===========================================
+ Hits           108      200      +92
- Misses          39      114      +75

Impacted Files
Coverage Δ

cl_sii/dte/constants.py
100% <100%> (ø)

cl_sii/contribuyente/constants.py
100% <100%> (ø)

cl_sii/rcv/__init__.py
19.23% <19.23%> (ø)

cl_sii/libs/mm_utils.py
35.55% <35.55%> (ø)

cl_sii/rcv/parse.py
65.07% <65.07%> (ø)

cl_sii/libs/tz_utils.py
75% <75%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


Create configuration file for OneClick for fast testbed

for fast testbed, upload cfg files into wiki

angle (rounds 21-24), Dynamic SHA-1 (4-8), Dynamic SHA-2 (1-13), Decim (rounds 1-8), Boolean rng generator

Shall I use 256 categories?

Make 2 versions:

CUDA-enabled, 256 categories
CUDA-disabled, 8 categories


Converting a pdf into mono / greyscale

I need to convert a pdf into mono / greyscale to reduce the price of printing. I started going down the route of converting the pdf to an image, converting it to black and white and then saving that image to a pdf. I then noticed that in the documentation there is a section on color. With functions like setFillColour setDrawColour... So my question is, when I load the pdf is there a way of converting it to greyscale within this package or will I have to carry on with my original logic. Sorry I don't have an example of my code because I'm on my phone but can supply one if it helps.

Your original solution is definitely the way to go for something like this 👍. Those operators are for different purposes than you're describing.


where is the exp/tedlium2_rnn/cmvn.ark from?

hi，I have run the program according to the README. now I want to use another model in ESPnet Model Zoo, but "cmvn.ark" is not included in the zip file. I wonder how can i get the cmvn.ark, and what is it used for? THX.

Its contains the parameters used for Cepstral Mean and Variance Normalization, i.e. normalization of the input audio. It is usually created based on the training data, so its specific to the training procedure of your model.
In espnet it is usually computed like that: https://github.com/espnet/espnet/blob/master/egs/tedlium3/asr1/run.sh#L110

Yes! The cvmn.ark is specific to the model and dataset. For ESPnet 1 models, it is a separate file. The code in this repository was programmed using espnet 1.
However, the ESPnet Model Zoo contains models for espnet 2. Model files for espnet 2 already include the CMVN parameters in the model file.
Using espnet 1 or 2 should give similar results for CTC segmentation, however, I think that espnet 2 is much more user-friendly. There is currently a pending pull request for CTC segmentation in espnet 2, see here: espnet/espnet#3087
If you already want to use espnet2, you can try it out after you downloaded the code, for example with a git checkout from the feature branch. Also, I would be happy if you give feedback, what model you used and how well it works with your setup.

Yes! The cvmn.ark is specific to the model and dataset. For ESPnet 1 models, it is a separate file. The code in this repository was programmed using espnet 1.
However, the ESPnet Model Zoo contains models for espnet 2. Model files for espnet 2 already include the CMVN parameters in the model file.
Using espnet 1 or 2 should give similar results for CTC segmentation, however, I think that espnet 2 is much more user-friendly. There is currently a pending pull request for CTC segmentation in espnet 2, see here: espnet/espnet#3087
If you already want to use espnet2, you can try it out after you downloaded the code, for example with a git checkout from the feature branch. Also, I would be happy if you give feedback, what model you used and how well it works with your setup.

thank you so much! I'll try to use espnet2.

@HalFTeen CTC segmentation for Espnet 2 was merged a while ago. I hope it worked for you!


commits for v3.1.5

Patch release that address various bug/build/doc issues:

Add backwards-compatibilty flags to the core library to match original behavior of the the c++ library. Fixes reading of certain files by the new core.
Fix build failures on MSVC14 and MSVC 2022
Fix build failure on latest 64-bit Ubuntu
Documentation refers to primary branch as "main"
Update the CI workflow matrix to VFX-CY2022
Update auto-fetch Imath version to v3.1.5

Specific OSS-fuzz issues:

OSS-fuzz 44084 Out-of-memory in openexr_exrcheck_fuzzer
OSS-fuzz 45899 Integer-overflow in internal_exr_compute_chunk_offset_size

Merged Pull Requests:

#1247 Update to zlib 1.2.12 and Imath 3.1.5
#1246 move out of bounds check inside loop
#1245 Implement corrupt chunk table reconstruction for Core
#1244 Match cpp header checks
#1239 Add #include for MSVC14
#1238 Update release notes for v2.5.8
#1237 Fix MSVC 2022 build
#1232 Fix logic for detecting _libc_fpstate API
#1230 Add maximumSampleCount limit to CompositeDeepScanLine
#1229 Change references to "master" to "main".
#1227 Update CI for VFX reference platform 2022
#1219 Make local build with Imath

Wait, don't release this yet, it's failing OIIO's CI.

Within the last couple days -- meaning one of the last few commits -- the "core" library seems to have lots its ability to fail individual tile reads for missing tiles, while still succeeding on the tiles that are present in the file. This is crucial for some applications that use missing tiles to signify or infer "checkpointing" or otherwise resume computing an image for the missing tiles.

I accidentally  included a bad commit, I'm backing it out now, waiting for the CI to finish.

I fixed the bad commit, @lgritz can you re-try the OIIO build?
@kdt3rd, could one of your recent fixes be the cause of the missing tile issue?

Your v3.1.5 build currently passes my test, but the top of 'main' fails.

I can report that in the main branch, commit 7ed46204 ("Match cpp header checks") succeeds, while the very next commit 3b0aaaae ("extract some common code, implement corrupt chunk table reconstruction") and beyond causes OIIO test failures for me.
3b0aaaae is not in line for 3.1.5, so it's clear to go from my point of view.

I think that means the ball's in your court, @kdt3rd

It probably should be in v3.1.5, let's hold off on the release until all the known issues are resolved.

yeah, ok, that commit is the chunk table reconstruction logic, glad I did that as a separate commit. So, that change implements the logic that is in ImfMultiPartInputFile, however, there is a distinct difference between multi-part files and single tiled files - if the chunk offset is 0 in a multi-part input file, it triggers the reconstruction logic, but it always errors in a single tiled input image. I didn't add the flag to disable the chunk reconstruction, I'll do that, and change the behavior to not reconstruct when it is only a single part tiled image


Audit and fix all [#next-major-version ] comments in v3alpha

In which we sweep through the v3alpha, after the mechanical v2 -> v3 translation work has landed, and manually address API cleanups.
Since this is the first time through, and this protodoc comment is relatively new, we'll probably also need to do a manual sweep of the comments in the entire API to do fixups. This includes places where we should have oneof but don't due to backward compats concerns, places where refactoring various fields under a message makes sense, etc.

I have audited the remaining occurences of [#next-major-version:..] annotations. They occur in:
api/envoy/config/listener/v2/api_listener.proto:18:  // [#next-major-version: In the v3 API, replace this Any field with a oneof containing the
api/envoy/api/v2/cds.proto:122:    // [#next-major-version: In the v3 API, we should consider deprecating the lb_policy field
api/envoy/api/v2/cds.proto:685:  // [#next-major-version: Reconcile DNS options in a single message.]
api/envoy/api/v2/cds.proto:800:  // [#next-major-version: In the v3 API, we should consider restructuring this somehow,
api/envoy/api/v2/eds.proto:112:    // [#next-major-version: Unify with overprovisioning config as a single message.]
api/envoy/api/v2/lds.proto:227:  // [#next-major-version: In the v3 API, instead of this messy approach where the socket
api/envoy/api/v2/core/config_source.proto:139:    // [#next-major-version: In xDS v3, consider replacing the ads field with this one, since
api/envoy/api/v2/core/base.proto:139:// [#next-major-version: move to type/metadata/v2]
api/envoy/api/v2/rds.proto:117:  // [#next-major-version: In the v3 API, this will default to true.]
api/envoy/api/v2/cluster/outlier_detection.proto:126:  // [#next-major-version: setting this without setting failure_percentage_threshold should be
api/envoy/api/v2/route/route.proto:392:    // [#next-major-version: In the v3 API we should redo how path specification works such
api/envoy/api/v2/route/route.proto:446:  // [#next-major-version: unify with RBAC]
api/envoy/api/v2/route/route.proto:1339://  [#next-major-version: HeaderMatcher should be refactored to use StringMatcher.]

Most of these require structural changes that are not part of the automated cross-version support. Given the timeline of v3, I suggest we punt them to v4. If there are no objections, I will close this out in a few days.

@htuch sgtm to close this.


Separate ldns parsing from clap parsing

This PR adds a separate code path for parsing arguments in a ldns-compatible way. The ldns tools cannot (in general) be parsed with clap, so they need full flexibility over how they parse their arguments. This parsing is only used when the binary is executed with the name of an ldns tool (either via renaming or a symlink). This also allows us to provide different defaults for the ldns and dnst tools.

One possible downside I see of this PR thinking about it a bit late (as I just submitted a review), is that this approach requires all implemented LDNS commands to also be implemented for dnst, as the final value produced by the alternate code is of type Args. I'm not sure that we will want to support the same set of commands for dnst as we implement for backward compatibility with LDNS.

One possible downside I see of this PR thinking about it a bit late (as I just submitted a review), is that this approach requires all implemented LDNS commands to also be implemented for dnst, as the final value produced by the alternate code is of type Args. I'm not sure that we will want to offer dnst equivalents for all implemented LDNS commands.

Good point. I'll check if we can work around that with clap.

Re args_override_self: this PR was not the right place to introduce it anyway. I'll remove it.


community: add PanelCallbackHandler

Description:
Migrates https://panel.holoviz.org/reference/chat/PanelCallbackHandler.html over to langchain-community.
Dependencies: panel
Twitter: IAteAnDrew1

Can you take a look at this PR @vbarda? Thanks!

@ccurme can I have some more time to gather upvotes? Thanks!

hey! lots of CI issues, and I don't think this makes sense to duplicate the code here (in general we're more encouraging of externally-packaged/documented callback handlers like you have already!)
if I added a section to the callbacks list on "external callbacks" that included a link to your linked docs page would that work?

lots of CI issues

I can fix those; seems like it's just long lines

I don't think this makes sense to duplicate the code

We are actually planning to deprecate this in Panel https://github.com/holoviz/panel/issues/7470
I think we'd prefer the callback handler to live in the langchain community.

Can I have this reviewed? Thanks!

oops sorry for the delay! we're actually not taking on new callback integrations (see this doc ) - mostly because of maintenance overhead if people make PRs against a callback like this, which tend to be difficult to review, as callbacks tend to rely much more on the external integration.
Given it's already in our docs, we're happy to accept updates to the docs pointing the integration to how it's best to install! Let me know if that makes sense
If it works for you, you're also welcome to publish a separate langchain-panel package that includes the code such that it doesn't live in either main package


Delete getLegacyInterval method since it only exists to support the deprecated IntervalCollection.delete(start, end)

Remove IntervalCollection.getlegacyInterval() which is only supported by the deprecated IntervalCollection.delete(start, end). The alternative to IntervalCollection.delete() is IntervalCollection.removeIntervalById().
The following files are affected:

packages/dds/sequence/src/intervalCollection.ts
packages/test/test-end-to-end-tests/src/test/deRehydrateContainerTests.spec.ts (removing the else part)

Makes sense to me - @anthony-murphy fyi

@pleath who i think made that change


Standard (native) JS events are no longer emitted in v4

We'd like to see Select2 emit standard events targeting the original <select> element.
Specifically, we needed focus and keydown events for use in our implementation of a field navigation component that helps us define application-specific navigation paths between fields declaratively without using tab indices.
While we realize that Select2 emits custom events, including select2-focus, we don't wish to special-case some code in our field navigation component just for Select2 (we use a few other types of controls). Instead, it'd be great if Select2 would emit the standard events from the original <select> element alongside its custom events, whenever a one-to-one mapping exists and when Select2 doesn't have any counterpart event type.
List of DOM3 Event Types (W3C DOM Level 3)
Standard Events (MDN Web Technology Reference)
Select2 Events (Select2 Documentation)
Note that Select2 doesn't emit any keyboard events targeting the original <select> element, so this makes our use-case impossible to implement in any kind of supported way.
For those who may have the same issue, we've successfully worked around it; although reading this code is not a healthy thing to do. I'll post it below in the hope that:

It helps in understanding the issue and finding an appropriate solution.
Someone can think of a more straightforward workaround in the meantime (or point us toward something that would remove the need for any workaround).
It helps someone else who may have difficulties working around the issue.

There are a few things specific to our codebase (jQuery, AMD) but it should be fairly understandable. We're trying to make a habit of documenting hideous hacks properly, so I include the lengthy comment intended for internal documentation, which should be useful.
Thank you.
define(function (require) {
    var $ = require('jquery');
    var key = require('keymap');
    require('select2');

    /*
     * Here be dragons.
     *
     * As of November 2013, select2 doesn't seem to play nice with the
     * other kids.  More specifically, it doesn't make use of standard
     * events on the select element.
     *
     * Instead, it provides control-specific events prefixed with
     * `select2-' [1].  Since we don't want to special-case the
     * navigation setup code just for select2, we won't assign handlers
     * for these events.  Instead, we'll add handlers for standard
     * events on the select element, and trigger the corresponding
     * actions on the control.
     *
     * This works fine for the focus event.  Since all select2 controls
     * are assigned the select2-container-multi class, we can setup the
     * necessary thunks at once rather easily.
     *
     * Key press events shouldn't be a problem, since we're hooking
     * actions unrelated to select2 (refocusing on the next field).
     * Of course, there's no point in making it that easy.  When
     * converting a select element to select2, the original element
     * gets pushed off-screen using CSS trickery, and select2 uses
     * a mix of div, span, anchor and input elements to build the
     * dropdown.
     *
     * The end-result is that the original select element (to which we
     * assigned a keydown handler using the fieldnav module) isn't
     * emitting any keydown events at all.  The internal auto-generated
     * input element is.
     *
     * Thus, we must assign a handler for the keydown event directly to
     * that input element, and programmatically trigger the same event
     * on the original select so that the navigation handlers can pick
     * it up.  This is kind of the reverse operation from what we had
     * to do with the focus event.
     *
     * The input element is inside a select2-container div, so they are
     * just as easy to query at once.  However, the auto-generated
     * container and the original select element nodes don't have any
     * kind of parent-child relationship in the DOM.  Supposedly, the
     * container always precedes the original element directly, so one
     * solution is to trigger the keydown handler on the next element to
     * the parent of the input that received it (simply by forwarding
     * the event object).
     *
     * We remarked that if the original select element is attributed an
     * ID, select2 will reuse it for the ID of the container itself,
     * simply prefixing it with `s2id_'.  We thus decided to parse that
     * ID to retrieve the original one instead, and trigger the handler
     * that way, which seems a bit more solid.
     *
     * Everything should be fine now, except it isn't.  This works as
     * long as the dropdown is closed, but when it opens, the input
     * mentioned above isn't used anymore.  Instead, another input
     * element is used (this is the search field).
     *
     * This time however, the element doesn't seem to have any kind of
     * relationship to neither the container mentioned above nor the
     * original select element.  No constructed ID from the original
     * ID, no parent-child node relationship -- they're not even close
     * to one another.  Indeed, the search input is under a
     * select2-search div, itself under a select2-drop div that lives
     * under the body element.
     *
     * Worse (for us), these elements are not created or at least are
     * not attached to the DOM until the dropdown is opened for the
     * first time, which means we can't even assign them any handlers
     * when we attach our own view to the DOM.
     *
     * Instead of diving in a complex idea of trying to manage state in
     * parallel to select2 (monitoring open/close events and assigning
     * handlers *only once* when the elements are available), we
     * decided to assign a delegated handler to the body element.
     *
     * Since all select2 controls have their internal elements on the
     * body root, this works fine.  The filtering of events is a little
     * long, but it is usable.
     *
     * Currently, we assign that handler when the select2-nav module
     * is first loaded (which happens only one time, requirejs doesn't
     * unload modules).
     *
     * "Ideally", we would register each view module that uses the
     * select2-nav module and remove that handler when no module uses
     * it anymore (re-adding it subsequently as necessary).  Simple
     * reference counting would do the trick, but for a huge hack like
     * that, this is clearly overkill.  Hence, the handler now lives
     * on the body element indefinitely once it is assigned.
     *
     * The end?  Well, we only managed to assign a handler capable of
     * catching key press events for the controls when they are open,
     * but we still need to rewire these events to the original select
     * element.  As mentioned above, we have no way of doing that,
     * short of keeping state ourselves (idea excluded above) or diving
     * into select2's internals using unsupported interfaces (if it's
     * even possible).
     *
     * The thing is, we saw that pressing the tab key has the native
     * effect of closing the dropdown.  Hence, pressing it twice will
     * work as expected since the handler for the input used when the
     * control is closed can find its corresponding original select
     * element itself (without state) as explained above (using the
     * reconstructed ID).
     *
     * From a UX point of view, it's not that bad, pressing tab to
     * close has an effect of explicitly validating the selection
     * before we go to the next field by pressing tab again, which may
     * even be desirable (who knows what the UX experts would say).
     *
     *
     * Usage:
     *     var rewireSelect2Events = require('integration/select2-nav');
     *     rewireSelect2Events(view);
     *
     * [1] http://ivaynberg.github.io/select2/#events
     * [2] http://ivaynberg.github.io/select2/#programmatic
     */

    $('body').on('keydown',
        'div'
        + '.select2-drop'
        + '.select2-display-none'
        + '.select2-with-searchbox'
        + '.select2-drop-active'
            + '> div.select2-search'
                + '> input.select2-input',
        function (e) {
            if (e.which == key.tab)
                e.preventDefault();
        });

    return function (view) {
        $('.select2-container > input', view).keydown(function (e) {
            $(['#', this.parentElement.id.split('_')[1]].join('')).trigger(e);
        });

        $('.select2-container-multi', view).focus(function () {
            $(this).select2('focus');
        });
    };
});

At this point I'm pushing this off of the 4.0 milestone, so Select2 will not be triggering the native events. Select2 will also not be triggering non-native versions of the events, which is less of an issue as we still have the option to add the native events without breaking compatibility.
If anyone is interested in making this happen, feel free to make a pull request and we'll gladly review it.

so is there no workaround in v4 to support the blur event or will support be coming anytime soon?
I also had something similar where I need to know when select2 loses focus
$("#select2Input").on("select2-blur", onBlur);

Select2 - When I use tab key and go to this field (select), then if i type 0 from the number keypad, it types as ', if I type 1 it types as a. This is only for the first numeric key pressed. I get symbols instead of numbers.

It looks like many developers are having problems with focus events. I really hope we get a solution soon, since using the tab key to navigate through forms is very handy for our users.
I found out that tapping the space bar opens the select2 search, but it would be more user-friendly if that happens automatically, even if it requires some extra configuration.

I gave up on this long ago and moved to selectize. Select2 held the sword up high for a long time though.

A simple fix to relay the blur/focus events is to add them to the relayEvents array like so...
EventRelay.prototype.bind = function (decorated, container, $container) {
  var self = this;
  var relayEvents = [
    'open', 'opening',
    'close', 'closing',
    'select', 'selecting',
    'unselect', 'unselecting',
    'blur', 'focus'
  ];
...

then you can do something like...
$el.on("select2:blur", function (e) {
  e.type = 'blur';
  ...
})

This is fixed? Someone can give me a feedback?

I needed to use the select2:blur event for a tagged select2 I am using.
So I added the blur event to the eventRelay list as described by skryl on my fork and this has fixed my issue.
Should I raise a PR against the upstream with this fix?

@skryl it does trigger the blur event but now the problem is that close and change events also become blur events. i.e., when I select an option (and I am using multiselect), it should trigger 'change' event, but it triggers 'blur' event.

This is not yet solved

$('.select2').select2('focus') seems to be working for me.  It's undocumented though.

Today I ran into the same issue where native "change" event was not being fired and then found this one.
It really pisses me off when some developers do not follow standards and are thinking they are above others and smarter than the rest.  As you may have noticed, there's a lot of issues about this opened (and closed??) where we, developers, are having problems with it, but you're still being ignorant and won't do what we ask for. Is there any specific reason why not? I came to this thread because right here I should be able to read the "discussion" why the native events are not being fired, but have read nothing about that, just another issue of the same.
You did a great job developing this jQuery extension and I do appreciate it and use it quite frequently, but will never understood this ignorance of yours (and others). I would understand if we would be asking for something not standard, but you're cancelling (or not triggering, the same end result) native events.
Would appreciate if you would reconsider you position on this.

Reopening this for another round of the stale bot.

Reopening this for another round of the stale bot.

I'd love for this to be fixed as well. For now I solved it like below with inspiration from https://makandracards.com/makandra/71890-events-triggered-by-jquery-cannot-be-observed-by-native-event-listeners.
jQuery.fn.enableNativeEvent = function(eventNames, convertedPropNames = []) {
  eventNames.forEach(eventName => {
    this.on(eventName, function($event) {
      if (!$event.originalEvent) {
        $event.preventDefault();
        const newName = `$:${eventName}`; // event to listen for is now "$:change.select2"
        const eventData = _.pick($event, convertedPropNames) // Uses lodash.pick
        const event = new CustomEvent(newName,
          { detail: eventData, bubbles: true, cancelable: true  }
        )
        $event.target.dispatchEvent(event)
      }
    })
  })
  return this
}

// Usage
$(".select2able").select2().enableNativeEvent(["change.select2"], ["params"]);

For anyone that finds this thread, and feels disappointed at how far they got, with a ticket ending in stale (twice), well this is what Ive got to work.
It essentially fires out a native duplicate change event that other plugins and addEventListener calls will hear.
This SO answer explains you cant trigger native events via jquery's trigger, you have to fire the event yourself.
https://stackoverflow.com/questions/37113525/how-to-trigger-js-native-even-addeventlistenerchange-function-by-jquery
Although the example there is using initEvent, which is deprecated everywhere except IE (https://developer.mozilla.org/en-US/docs/Web/API/Event/initEvent)
The new way is using new Event('<event-name>'), which of course IE doesnt support, so here's what I'm using to support both;
// note one(...), not on(...), which triggers once and detaches. Otherwise you get stackoverflow as
// this triggers more on(change) events.
$("select").one("change", (e)=>{
    if (window.document.documentMode) {
        // (IE doesnt support Event() constructor)
        //https://caniuse.com/?search=Event()
        var evt = document.createEvent('HTMLEvents');
        evt.initEvent('change', false, true);
    } else {
        const event = new Event('change');
        e.currentTarget.dispatchEvent(event);
    }
});

I only needed to deal with change events, replace that with other events as needed.

Ouch! 10 years on this is still a bug.

I really can't believe this is still an issue in this library.
Can you at least please explain why you don't want to implement it? Is there any real reason?
As of now I can only see many issues closed and you reference them with this issue claiming it is explained here but as far as I can see there is no discussion or reason at all.

I was hours finding a solution and I found it, is as simple as the following:
document.querySelector("#id_of_your_element").onchange = element => {
console.log(element.target.value)
}

Dam how has this not been resolved yet! Looking a solution in 2024....

I ended up here, because the native change event is not triggered on the original select anymore. However, I do not want to use jQuery in new code. Is it possible to catch some kind of change event of select2 without jQuery?

I ended up here, because the native change event is not triggered on the original select anymore. However, I do not want to use jQuery in new code. Is it possible to catch some kind of change event of select2 without jQuery?
...

i have the same problem ... select2 stop event propagation to the original element... and no way to associate or trigger it ...


Page blueprint causes weird first and last line in frontmatter.yaml

Hi,
As I also described in the Discord channel, the following issue occurs recently on my site:
For a page on a friend's band website, I've set up a page blueprint with a custom tab in the Admin panel to insert new tour dates. Those entries were usually written to a frontmatter.yaml file since they need to be the same for each of the languages on the website.
I know that this used to work, but recently there is now the problem that the already existing content of the frontmatter.yaml file is not rendered anymore in the Admin tab, and, if one is creating new entries via the form in the Admin panel, the content in the frontmatter.yaml file is replaced and the file always looks like this:
"\0*\0items":
  gigs:
    -
      date: '2021-06-14 13:07'
      location: 'My Location'
      city: Berlin
      country: Germany
      link: null
      status: confirmed
"\0*\0nestedSeparator": .

I think the problem lies in the first and the last line. But I have no idea why they suddenly occur...
Any hints on what causes this behavior? And how can I solve it?
The blueprint looks like follows:
title: Features
'@extends': default

form:
  fields:
    tabs:
      fields:
        features:
          ordering@: 1
          type: tab
          title: Gigs
          fields:
            header.gigs:
              name: gigs
              type: list
              label: Gigs
              collapsed: true

              fields:
                .date:
                  type: datetime
                  label: Date
                  placeholder: Select a date for the event
                  validate:
                    required: true
                .location:
                  type: text
                  label: Location
                  placeholder: Name of the location
                  validate:
                    required: true
                .city:
                  type: text
                  label: City
                  placeholder: Name of the city
                  validate:
                    required: true
                .country:
                  type: text
                  label: Country
                  placeholder: Name of the country (optional)
                .link:
                  type: url
                  label: Link
                  placeholder: https://www.yourlink.com/
                  help: add the link for the event, including the trailing 'https://'
                .status:
                  type: select
                  size: short
                  classes: fancy
                  label: Status
                  help: Select the status of the event (optional)
                  options:
                    confirmed: confirmed
                    pending: pending
                    canceled: canceled

Thanks a lot in advance! Any help is highly appreciated :-)
Cheers,
Markus

As an addendum: Deactivating the Flex Objects plugin solves the issue temporarily. So, the issue probably lies in there somehow.

Also, the issue is not only related to pages with a shared frontmatter.yaml as I just realized. If I have a page-blueprint form in the Admin view that is supposed to save content to the yaml frontmatter of my markdown files, saving the changes leads to a newly created frontmatter.yaml with the content being removed from its origin (the markdown yaml frontmatter) to the new frontmatter.yaml. Again, the weird first/last lines appear and "destroy" everything.
I would change the title of the issue accordingly.
Deactivating Flex Objects again solves this issue.

@markusritschel I'm not able to reproduce the issue. Maybe you have some plugin that changes the behavior or I am missing something to reproduce the issue. By default, it looks like frontmatter.yaml is only seen by the frontend and it's not used in admin at all.


Fix: missing endif in autoload

I'm using Vim-bootstrap and I tried to add the following line to my vimrc:
autocmd BufRead,BufNewFile jrnl*.txt set fo+=t tw=50
It didn't change anything. So, after disabling the plugins one by one, I found that requirements.txt.vim was causing the problem. I checked the code of ftdetect/requirements.txt and finally I found an unnoticed missing | endif in an autoload.
I hope it will help to other requirements.txt.vim users.

@pwaqo Thanks for your contribution.
I will release the next version v-1.4.2 as soon as I merge this patch.


Spark ETL job failed with no space left on device error

Summary
When sending more than 20 million events in 30 minutes, Spark ETL job will failed with error:

java.io.IOException: No space left on device

Steps to reproduce

create pipeline with workshop configuration
using python script and sending e-commerce events with 10000 user and generate last 30 days events.

What is the current bug behavior?
ETL job fails, no events are successfully loaded into Redshift.
What is the expected correct behavior?
ETL job success, and all event are load to Redshift.

Relevant logs and/or screenshots

Possible fixes

This is :bug: Bug Report

@amliuyong It probably need more resources for spliting raw events to four dimension tables.

The new example shopping data is larger than the notepad example data, which is the cause of it. The default EMR configuration cannot handle as many volumes of events with the notepad data.
You can follow up this doc to increase the cluster capability to process large data volume.

Anyway, we will re-benchmark the data processing program to be as tuned as possible.

It's caused by the default cluster resource, which cannot process the volume of data.
Please follow up on this troubleshooting guide to increase the Spark cluster resource.


Add the resource name to the task action for conversion hosts

Because there's no direct association between conversion hosts and tasks we're relying on the task description to suss them out. This PR merely modifies the task description so that it includes the resource name as well.
This would save the UI team from having to query /api/vms and /api/hosts with the IDs from the tasks just to display a name on those list items.

@mturley Look ok?

Looks perfect, thanks @djberg96! That was fast.

Actually, it's fine either way, but maybe we should add a space after id: to make them all consistent?

@mturley done!

We can probably add this to the conversion host enablement feature BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1622728

Agreed @agrare, let's revisit this when we have time.


Allow user to configure default MotherDuck database in postgresql.conf

Fixes #459
Allow the user to configure a different default MotherDuck database from my_db in postgresql.conf. This affords flexibility because there is currently no user-facing API to change the internal "default" DB in MotherDuck.

Thanks a lot for your work on this. I played a bit with your changes and realized that duckdb tables were not being cleaned up when changing the default database. So I implemented a fix for that. I also updated did some small other tweaks, and updated the docs in some more places.


conflicts with builtin functions

Hi,
I have been using expr for quite some time. Currently, I use version v1.12.1
Today, I tried upgrading to v1.14.0 but my tests show conflicts with my custom functions:

join
repeat

So, what are my options:

i stick to version 1.12 forever
i clone the repo and use a modified version
can I disable built-in functions?
can we refactor this package to have pluggable behavior (so I can not include those conflicting function)?

Hi,
Yes this is what I was afraid of. At begging I was thinking to allow override builtin functions, but fought it may confuse on what function is executed.

can I disable built-in functions

I think this is the best solution. We can introduce a config option to disable a builtin function:
expr.DisableBuiltin(name string)

Will implement it today.

Added next functions:

DisableAllBuiltins()
DisableBuiltin()
EnableBuiltin()

thx, will check it


Use GitHub Actions for CI

Context
travis-ci.org is dead and the current CI pipeline is not working.
Change
To ensure compatibility with various versions of Ruby, I propose using GitHub Actions for CI. The proposed workflow is passing on my fork, and will be added to this repo with the merge of this pull request.

🍃


Undefined port, related to issue #20

In issue #20 @freekmurze fixed undefined $portCommand, which I just realised that it also causes error when port isn't defined in config/tail.php. However, what causes me to open issue #20 is actually the $port variable (last line, in attached image).

Previously it was defined as $port = 22 and the value will change accordingly if there's port key in config/tail.php.
Since we offer ability to use custom ssh port, displaying port that's being used in console info might be helpful. Thus, info() will use the $port variable again to display which port is being used.

Fixed in latest version.

thanks!


Add host architecture to the available features

So that we can XFAIL on these architectures, as done for tests/lto_and_cfi.c

@sylvestre can you try this one on debian / ppc builds before merging?

on s390x:
Expectedly Failed Tests (1):
  LLVM regression suite :: lto_and_cfi.c


Add semicolon as one of delimiter list that CSV guess plugin suggests

Because semicolon is often used as delimiter char.
This assumes https://github.com/embulk/embulk/pull/526.

Will take it on https://github.com/muga/embulk/pull/8


Better Introduction & Explanation of Purpose

When I visit https://endoflife.date/, I get  the following very brief and somewhat uninspiring (sorry) introduction to the project:

endoflife.date is a community-maintained project to document end-of-life dates, and support lifecycles of various products.

I think with the current presentation, a visitor does neither really get the purpose nor the potential of the project.
The project could use the home page to better display what the purpose of the project is and what the possible usages are.
May be an example, a graphic or some use cases could be presented.

Cleaned it up a bit, how does this look:

Want to add a few more lines about purpose, like you suggested.

@captn3m0 looks better, already.
I just came across this page: https://github.com/endoflife-date
I like the explanation and hints there.
The screenshot, though, is not clearly enough as such.

Also, it could borrow from the README.md, too
May be some selected badges? For example "PRs welcome" & "chat on gitter".
The section about the API? Because the tiny "api" in the top right can be overlooked, easily.
The API can be an interesting added value for some, so it should be presented more prominently.

Screenshot:
Preview URL: https://deploy-preview-1703--endoflife-date.netlify.app/
PR: #1703

@captn3m0 beautiful! ❤

Thanks for raising this. I've always wanted to improve this, but never got around to giving it a shot.


In Docs/My profile/ Activity - Contraditory information

In the section Activities or "Pick up where you left off", I have some modules listed, but I have finnished all of them.
It has contraditory information:
example:
Publish and share in Power BI
0% completed • 0 min remaining
Thank you

@Pedrolorenzo Thanks for taking the time to give us feedback.
I've tagged this issue for a member of our Learn infrastructure team to investigate for you.
Appreciate your contribution to our community.


feat: Add support for multiple browser user agents

Description
Added the ability to define a pool of many browser user agents in the environment file.
On each request a random user agent will get used from the defined pool.
The idea is to keep the bot more anonymized and harder to detect by having many user agents instead of just one.
It would be better to have each user agent separated by a line break, but sadly the version of dotenv doesn't support it yet?
Supported in:
https://github.com/bkeepers/dotenv#multi-line-values
But not in:
https://github.com/motdotla/dotenv
Example source for common user agents:
https://developers.whatismybrowser.com/useragents/explore/
NOTICE
Breaking change duo to rename from USER_AGENT to USER_AGENTS in env file!
Maybe this feature could create an additional entry instead of rename or just use old name.

Testing

New dependencies

Breaking change duo to rename from USER_AGENT to USER_AGENTS in env file!
Maybe this feature could create an additional entry instead of rename or just use old name.

Perhaps just revert to USER_AGENT. I don't mind having this come in. Other variables are also non-plural.


⚠ Bofrost.at has degraded performance

In 12ed26d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1489 ms

Resolved: Bofrost.at performance has improved in 73678cd after 9 minutes.


Fix execution of group tasks via invoke()

[x] Bug fix https://github.com/deployphp/deployer/issues/2445
[x] Tests added?

Thanks for quick merge. Can we have new beta release soon? 🙏


Test examples in user guide with travis

#385

Thank you! I've left two comments, otherwise it's a that's a big improvement!

On travis I'm getting weird linking errors like /usr/bin/ld: cannot find -lpython3.6m. Any help would be great.

I don't know the exact problem or the solution, but I can give some context: To run the tests, we need to build binaries, which needs to link libpython in the version specified by the build script. Normally the build script also tells the linker the path of libpyhon through rustc-link-search:
https://github.com/PyO3/pyo3/blob/d63fac8d1cbdc3dcf4eefbbb871b3a6eb031a1b3/build.rs#L444-L448
This seems to fail here, presumably because the we're calling rustdoc here directly (through docmatic) and not cargo.
It's also possible to add directories to the linker path using environment variables, but that should have already been done by the script that travis runs:
https://github.com/PyO3/pyo3/blob/d63fac8d1cbdc3dcf4eefbbb871b3a6eb031a1b3/ci/travis/setup.sh#L16-L20
The logs even tell that this path has been set: https://travis-ci.org/PyO3/pyo3/jobs/502189479#L322
I am not really sure what to do here because debugging travis is a tedious task. The quick and dirty solution would be to make the minimum nightly use python 3.5 (which apparently works) and then only run those test in the minimum nightly builds, just like rustfmt and clippy.

Ok, then I would suggest we activate the tests only for Python 3.5 for now. This way we have at least some mechanism in place which prevents the examples to drift from the current API. We could still leave #385 open and look for a better solution.

I think that eventually, we want to either use a fix version of skeptic/docmatic or (which is more likely) write our own small doc tester. But for now this is a really good solution for moving forward with the docs.


Broken link

Under "See Also", the link for "FAQ for developing in AL" results in HTTP-404

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

ID: 3f0ef3bc-7516-dae7-6cca-d5a9b680364f
Version Independent ID: 288d30ad-0b2d-8c18-63fa-d5555eb7416e
Content: FAQ about developer and IT-Pro experiences - Business Central
Content Source: dev-itpro/faq.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Thanks for catching this! A fix is ready and will be part of our next update later today.


Update get slave request id from heatbeat

This PR allows to find slaverequestid from published state such as slaverequestid-c999_pw0. Today I just wrote gtest.
# Sorry, WIP until priority among slaverequestid-c999_pw0 and slaverequestid-c999_tw0 published slave states are resolved. Making PR anyway to copy the PR number to gtest.

@ziyan told me whichever I can choose if the numeric request ID is the same. I pick the firstly published one. unWIP.

now that GetSlaveRequestIdFromHeartbeat method name is fixed, I can go back to discuss this one~

sure, thanks


Update mixins.md (Vuex version)

Maybe we could specify that the example applies for Vuex version 1.x


empty: support positive len

this pattern is common
var arr []string
assert.True(t, 0 < len(arr))

https://github.com/search?q=language%3Ago+"assert.True(t%2C+0+<+len("&type=code
compares checker will fix it to
var arr []string
assert.Positive(t, len(l))

But that's it, while we should convert it to Empty
assert.NotEmpty(t, l)

It's a new use case
Originally posted by @ccoVeille in https://github.com/Antonboom/testifylint/issues/119#issuecomment-2181545452

Please confirm if the logic is valid for you, then I can code it

Well this one could be added to #119 maybe, not sure if we have to do it at the same time or separately

But this one won't be detected

Do you check it before spam issue?
Duplicate of https://github.com/Antonboom/testifylint/issues/122
Implemented in https://github.com/Antonboom/testifylint/pull/124


Broke page styles when live changing it n Chrome DevTools with webpack template

Steps to reproduce
I have application bootstrapped from vue-cli with a webpack template. I'm running it on Chrome 65.0.3325.146 but it also exists on 64.X.XXX version.
I'm adding here:
package.json: https://gist.github.com/marcinlesek/a7e6076ce4befe2e810743fdbaf81480
webpack.base.conf.js: https://gist.github.com/marcinlesek/80cbf27b6ef4172248709f32c257d0cd
What is expected?
The application works fine with Chrome Browser.
What is actually happening?
When I change style via Chrome dev tools it broke all styles (after changing or disabling one property) that page looks like in pure HTML without any line of style code. Fresh dev tools setup and Chrome reinstall doesn't help. What is a bit tricky, on Firefox 58.0.2 everything works correctly.

My collegues also had this problem, so it convince me that it isn't my local bug but something bigger on Vue side. Also find some questions regarding this bug, like https://stackoverflow.com/questions/48407862/page-styles-break-when-i-change-styles-in-chrome-devtools-with-webpack-hmr
Thanks in advance.
Best regards,
Marcin

For everyone looking for solution:
After a bit I found, that changing cacheBusting: true to false in config/index.js help to solve that and now it's possible to change style in Chrome Dev Tools.
// file: config/index.js

...
// If you have problems debugging vue-files in devtools,
// set this to false - it *may* help
// https://vue-loader.vuejs.org/en/options.html#cachebusting
cacheBusting: false,
...

Another solution here: https://stackoverflow.com/questions/49372717/broke-page-styles-of-vue-js-app-webpack-template-when-live-changing-it-in-chro
Hope this will help anyone! :)
Best,
Marcin

For everyone looking for solution:
After a bit I found, that changing cacheBusting: true to false in config/index.js help to solve that and now it's possible to change style in Chrome Dev Tools.
// file: config/index.js

...
// If you have problems debugging vue-files in devtools,
// set this to false - it *may* help
// https://vue-loader.vuejs.org/en/options.html#cachebusting
cacheBusting: false,
...

Another solution here: https://stackoverflow.com/questions/49372717/broke-page-styles-of-vue-js-app-webpack-template-when-live-changing-it-in-chro
Hope this will help anyone! :)
Best,
Marcin

Thanks Man, it works well with Nuxt!

@filippolcr I am running into the same issue in Nuxt, but I'm fairly new to the setup and am not sure where to change this setting in my project. For Nuxt is it also in config/index.js?

@filippolcr This wont work for me in nuxt. I extended the vueloader config. How did you add this config? Thank you

@filippolcr @filippolcr I fixed it by adding extractCSS: true to the build property in nuxt.config.js https://nuxtjs.org/api/configuration-build/#extractcss

@filippolcr @filippolcr Ok. This created a css flicker error whenn the extracted css wanst loaded. I have no idea then.

i fixed it with disabling the sourceMaps for scss files with the loader property
....
build: {
    loaders: {
      scss: { sourceMap: false }
    },
....

https://nuxtjs.org/api/configuration-build/#loaders

@filippolcr I am running into the same issue in Nuxt, but I'm fairly new to the setup and am not sure where to change this setting in my project. For Nuxt is it also in config/index.js?

// nuxt.config.js

...
build: {
    loaders: {
        vue: {
            cacheBusting: false,
        },
    },
}
...

@filippolcr I am running into the same issue in Nuxt, but I'm fairly new to the setup and am not sure where to change this setting in my project. For Nuxt is it also in config/index.js?

// nuxt.config.js

...
build: {
    loaders: {
        vue: {
            cacheBusting: false,
        },
    },
}
...

@filippolcr I am running into the same issue in Nuxt, but I'm fairly new to the setup and am not sure where to change this setting in my project. For Nuxt is it also in config/index.js?

// nuxt.config.js

...
build: {
    loaders: {
        scss: { sourceMap: false },
        vue: { cacheBusting: false },
    },
}
...

this has seem to work, thank you @homerjam, but know i wonder why is this workaround necessary?and, why those options aren't set by default? also what would be the side effects of disabling cache and source maps

For nuxt.js this was buggy for me :
  loaders: {
        scss: { sourceMap: false },
        vue: { cacheBusting: false },
    },

The solution found to solve this devTools issue:
add this to build in nuxt.config.js:
cssSourceMap: false,

I'm still having the same problem. Someone can explain why ? I'm interested to know if it's a problem from webpack or vue ?


TypeError: this.apickli.add Body Parameters is not a function

The function - add Body Parameters is already exist in the - Apickli-gherkin.js file  but when call in the feature file, it is given error - TypeError: this.apickli.add Body Parameters is not a function

Can any please help to resolve it.

Can you paste your code  here ?

@mrj04
Not clear which code paste here ? Is it package.json
package.json
{
"name": "amock-tests",
"version": "1.0.0",
"devDependencies": {
"cucumber":"^0.5.3",
"apigee-access":"1.3.0"
}
}
I also send a email to you, please check it

I am surprise - when I commented the above addBodyParameter function in my Apickli-gherkin.js file and calling it in feature file , it is still working.
How we know which version of NodeJS support which Apickli-gherkin.js file, any idea? My code was working previously but after install latest version of NodeJS, it is stop working  and given function related errors.
Any one , please help to understand issue?


Improvements for NRF52

Thank you Mateusz, please verify if everything is fine. Every nice improvements! I think now we can run NuttX on PineTime Watch and on other Watches/Bands powered by nRF52

I think we still need support for SPI and GPIO interrupts to do something useful. I'll add them next week.

@acassis FAR is not normally used in ARM code.  It is only required in the common code where it needs to have a value for some architectures.  It is fine in ARM code to assume that FAR is defined to be nothing.   I saw a FAR in a function that he submitted and assumed it should be presented for all functions. My fault!

@acassis Well, it should be used consistently in ARM code.  Either always user FAR or never use it in an ARM file.

At the moment in arch/nrf52 in some places there is FAR in some not. So for now it is far from consistent. But I think it is also true for other ARM chips.
If there is no strict rule (always use FAR vs never use FAR), then there will be not consistency.

Well, it appears at least 15182 inside arch/arm:
alan@dev:~/incubator-nuttx/arch/arm$ grep -r "FAR " | wc -l
15182

Don't be tempted to change that with a simple substitution.  That would mess up the alignment.  It would require lots of manual effort or a very intelligent script.  It looks like Xiao Xiang must have had such an intelligent script when he removed all of the (void).  He also corrected all of the spacing that the that changed because of that.

I don't have the magic script either:(: only single line functions are replaced by the command automatically, other functions spread the multiple lines are done manually.


Add ResolveTaskMutationsBuildOperationType

to capture task parameter resolution which happens as part of resolving mutations. This allows for attributing the resolution of nested input properties to a task.
This is particular interesting for capturing the progress events for Java toolchains, see #21281.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


fix(deps): update terraform ibm to v1.49.0

This PR contains the following updates:

Package
Type
Update
Change

ibm (source)
required_provider
minor
>= 1.48.0 -> >= 1.49.0

ibm (source)
required_provider
minor
=1.48.0 -> =1.49.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.2.3 :tada:
The release is available on:

GitHub release
v5.2.3

Your semantic-release bot :package::rocket:


fix(app): query panel suggestions displays the info of the next row due to an off-by-1 error

Description

Fixes WB-18416
Pass the current index to SuggestionRow so that we set suggestionIndex properly within the component

Testing
Tested via running FE locally.
Before:

After:

I have read the CLA Document and I hereby sign the CLA

recheck


Fix the URL for posting follow-ups

The previous URL returns a 404. This one is pulled from minitel.

👍


Fix Deprecation Warnings for numpy type aliases

Use correct aliases for deprecated numpy types
/home/madhavmk/Desktop/offshore-geodesy/.nox/tests/lib/python3.11/site-packages/nptyping/typing_.py:54: DeprecationWarning: `np.object0` is a deprecated alias for ``np.object0` is a deprecated alias for `np.object_`. `object` can be used instead.  (Deprecated NumPy 1.24)`.  (Deprecated NumPy 1.24)

After further research, this is an open issue on the nptyping library.
Attaching link to Issue


Annoying "where" clauses are required

When writing something generic over <I: Index, J: Index> it is true that (I, J): Index but the type checker doesn't know that. The problem is actually with the Flatten trait (a super-trait of Index). The work-around is to add where clauses (I, J): Flatten, (I::Size, J::Size): Flatten.
This is annoying. It seems to be a limitation of Rust, which might go away in future. We would like to write
trait Flattenable: for<F: Flat> Flatten<F> {}

impl<T: for<F: Flat> Flatten<F>> Flattenable for T {}

and then use Flattenable instead of Flatten as the super-trait of Index. However, that's illegal.

Ooh! I've found another approach: remove the supertrait Flatten from Index and Size. I wasn't relying on those bounds anyway.


deprecated warnings ⚠

As of 2 days ago 'Build filterlists' are not being generated.

@xarantolus Any suggestions?

Hmm yeah, that's not ideal. I upgraded them in the latest commit https://github.com/xarantolus/filtrite/commit/cf1edf06cca967ff477cdc9e80a85f545e232719

Hmm yeah, that's not ideal. I upgraded them in the latest commit cf1edf0. Thank you for pointing it out :)

I'm still unable to build..

I'm still unable to build..

Looking at the output here, it's because a filter list doesn't load:

2024/05/01 15:14:59 Error while generating filter for "lists/Browser.Custom.BL.HighSecurity.txt": downloading filter lists: unexpected status code 503
panic: error while walking: downloading filter lists: unexpected status code 503

This kind of thing probably shouldn't stop the entire generation process

When looking at the code again, I noticed that the generation process errors if the last filter list download fails; so this should be fixed now

When looking at the code again, I noticed that the generation process errors if the last filter list download fails; so this should be fixed now

All seems well now.. Thanks.. 👍

Closed


Improove Hive deployment to fail fast on fatal error, and fix deprovision logic

Fail fast on OCP install Fatal error, instead of waiting for 50 minutes timeout.
This is implemented by watching Hive pods completion status.

Fix deprovision that was running always (in Teardown) if provision failed -
even when provision failed since the cluster name already existed (legitimate failure),
which caused deprovision of existing cluster without intention.

'Wait For Cluster To Be Ready' not only watches for Install to be completed,
but also for Hive cluster deployment to include API endpoint.

This has been tested on PSI, GCP, and AWS.
Output example of the Provision process exiting right after a fatal error (without waiting for the 50 minutes timeout):


Fix lag on lightning strike

I remember you once wrote that you want to get rid of getPersistentChunkIterable hack and run everything from cube iterator.

Conclusion:

Inject and rewrite adjustPosToNearbyEntity()
Inject in updateBlocks() after canDoRainSnowIce() call and add isAreaLoaded check.

Correct?

That probably would be correct, assuming block updates in that loop are disabled.

Updated.

Updated.


Docs: Link directly to PEPs

Summary of changes

Use the Sphinx :pep: role to link to PEPs in docs:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-pep
This means they'll link directly to their new home at https://peps.python.org/ rather than going via redirect at the old https://www.python.org/dev/peps/
And update the non-docs links to the new home.
Pull Request Checklist

[n/a] Changes have tests
[n/a?] News fragment added in changelog.d/.
(See documentation for details)

Is a changelog needed for this?

Thanks, I've dropped the non-docs commit.


RCE: shell globbing

Description
We need a rule (or extend an existing one) to catch shell globbing. There are different ways of globbing that will prevent matching specific words. Examples are:

/etc/pas[s]wd
/etc/[p]asswd
/etc/[!q]asswd
/etc/[m-z]asswd
s=/usr/bin/\[u\]name+-a
/?exec=/bi[n]/bash

This comes from BKPWE8P7, IPQTYJAR. Related issue: https://github.com/coreruleset/coreruleset/pull/2594
This reference might come handy: https://hyperpolyglot.org/unix-shells

This week I merged #2594, the checker for /[e]tc bracket shenanigans. I verified that it catches all the examples in this issue. I converted the examples to FTW tests and committed them.
After fighting with Git I just committed the test additions to the v4.0/dev branch, apologies. They are in commit 3d3eb8faf00e5532ee56398e2abee8df07bccee3.
Do you want to keep this issue open to find more examples? Maybe without brackets? If so, feel free to re-open!


[libgo] Include directory not exposed by targets.

Describe the bug
When I use libgo with vcpkg, compiler complains it can not find the header. I've checked the libgoConfig.cmake and there is no code that exposes the header. Actually, when I specified the header manually, it succeed to find headers, but still failed to generate the simple demo. Undefined reference to jump_fcontext is reported.
Environment

OS: Linux
Compiler: gcc 11.2

To Reproduce
Steps to reproduce the behavior:

./vcpkg install libgo
main.cpp

#include "libgo/coroutine.h"
#include <stdio.h>
#include <thread>

int main()
{
    go []{
        printf("lambda\n");
    };

    co_sched.Start();
    return 0;
}

CMakeLists.txt

cmake_minimum_required(VERSION 3.0.0)
project(demo VERSION 0.1.0)

set(CMAKE_CXX_STANDARD 20)

find_package(libgo CONFIG REQUIRED)

add_executable(demo main.cpp)
target_include_directories(demo PUBLIC vcpkg/packages/libgo_x64-linux/include)
target_link_libraries(demo PUBLIC libgo::libgo)

I use vscode and vcpkg is in the root of workspace. So .vscode/settings.json is

{
    "cmake.configureSettings": {
        "CMAKE_TOOLCHAIN_FILE":"vcpkg/scripts/buildsystems/vcpkg.cmake"
    }
}

Expected behavior
Success to compile and link.
Failure logs
[main] Building folder: kie demo
[build] Starting build
[proc] Executing command: /usr/bin/cmake --build /root/kie/build --config Debug --target demo -j 12 --
[build] Consolidate compiler generated dependencies of target demo
[build] [ 50%] Linking CXX executable demo
[build] /usr/bin/ld: ../vcpkg/installed/x64-linux/debug/lib/liblibgo.a(processer.cpp.o): in function `co::Context::SwapIn()':
[build] /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/scheduler/../task/../context/context.h:39: undefined reference to `jump_fcontext'
[build] /usr/bin/ld: ../vcpkg/installed/x64-linux/debug/lib/liblibgo.a(hook.cpp.o): in function `co::Context::SwapOut()':
[build] /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/netio/unix/../../scheduler/../task/../context/context.h:49: undefined reference to `jump_fcontext'
[build] /usr/bin/ld: /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/netio/unix/../../scheduler/../task/../context/context.h:49: undefined reference to `jump_fcontext'
[build] /usr/bin/ld: /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/netio/unix/../../scheduler/../task/../context/context.h:49: undefined reference to `jump_fcontext'
[build] /usr/bin/ld: /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/netio/unix/../../scheduler/../task/../context/context.h:49: undefined reference to `jump_fcontext'
[build] /usr/bin/ld: ../vcpkg/installed/x64-linux/debug/lib/liblibgo.a(hook.cpp.o):/root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/netio/unix/../../scheduler/../task/../context/context.h:49: more undefined references to `jump_fcontext' follow
[build] /usr/bin/ld: ../vcpkg/installed/x64-linux/debug/lib/liblibgo.a(task.cpp.o): in function `co::Context::Context(void (*)(long), long, unsigned long)':
[build] /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/task/../context/context.h:20: undefined reference to `make_fcontext'
[build] /usr/bin/ld: ../vcpkg/installed/x64-linux/debug/lib/liblibgo.a(co_mutex.cpp.o): in function `co::Context::SwapOut()':
[build] /root/kie/build/vcpkg/buildtrees/libgo/src/c91da23096-15387d4e98.clean/libgo/sync/../scheduler/../task/../context/context.h:49: undefined reference to `jump_fcontext'
[build] collect2: error: ld returned 1 exit status
[build] gmake[3]: *** [CMakeFiles/demo.dir/build.make:98: demo] Error 1
[build] gmake[2]: *** [CMakeFiles/Makefile2:83: CMakeFiles/demo.dir/all] Error 2
[build] gmake[1]: *** [CMakeFiles/Makefile2:90: CMakeFiles/demo.dir/rule] Error 2
[build] gmake: *** [Makefile:124: demo] Error 2
[build] Build finished with exit code 2

Additional context
No

@Kidsunbo  My PR only fix the include directory not exposed by targets.
@yyzybb537 About the issue undefined reference to jump_fcontext'` in linux, I found out that this is due to the fact that there are only function declarations and no definitions in the libgo\context\fcontext.h file:
intptr_t jump_fcontext(fcontext_t * ofc, fcontext_t nfc,
        intptr_t vp, bool preserve_fpu = false);

fcontext_t make_fcontext(void* stack, std::size_t size, fn_t fn);

I saw that the name of this function has been changed on your original repository, but it is still only declared and not defined.
I'm not too familiar with this port, so could you please help fix this or give some suggestions on how to fix it? Thank you!


Revert hard-coded text-scales

Revert "use textScale to automatically size the Category label"
Revert "scale the card label"
Revert "use a custom textScale for the hero heading"
Revert "use textScale to represent the relative size of Header text children"
Revert "set a textScale for the Modal title text"
Revert "apply a text scale to modals"

Scale didn't work as you had hoped?

Scale didn't work as you had hoped?

Actually starting to use it in GodTools Android felt disconnected and wrong for text sizes. I found myself removing a text size constant from several view layouts to allow the model to define those sizes. It just felt wrong.


Multi-image support for Diffusion Policy

I'd like to be able to perform Diffusion policy training and inference on multiple camera streams (e.g. "observation.camera_0" and "observation.camera_1" rather than just "observation.image")
Assuming that I have a real-world Push T dataset with multiple camera streams (e.g. manro99/pusht_5cam on HF), can you provide pointers on how I can update lerobot/common/policies/diffusion/modeling_diffusion.py and lerobot/common/policies/diffusion/configuration_diffusion.py to ingest multiple camera streams for training? Thanks!

Hi @ruijie-he this is on our TODO list, but you are welcome to contribute it. The best example in code is modeling_act.py. The message on this PR also explains the current design: https://github.com/huggingface/lerobot/pull/149.
Can you please take a look at those two resources and let me know if you need any more information?

FYI this is being tackled here https://github.com/huggingface/lerobot/pull/218


Coordinate Conversion does not support the ; and : as coordinate pair separtors when input is DDM and DMS (ArcMap)

The Coordinate Conversion addin supports the colon and and semi-colon characters (this is not supported by Pro/ArcMap). These separator characters work for input in DD format, but not DDM and DMS.
The following DD coordinates which have ; and : work:

45.0N;100.0W
45.0N; 100.0W
45.0N ; 100.0W
45.0N:100.0W
45.0N: 100.0W
45.0N : 100.0W

The following DDM and DMS coordinates which have ; and : do not work:

45 0.0N;100 0.0W
45 0.0N; 100 0.0W
45 0.0N ; 100 0.0W
45 0.0N:100 0.0W
45 0.0N: 100 0.0W
45 0.0N : 100 0.0W

@dfoll @topowright FYI. I have this noted in the Word doc that will serve as content for Xmetal.

@topowright and I believe this should be closed

@dfoll @topowright I just confirmed that the Supported notation formats topic lists : and ; in DD but not for DDM and DMS, so yes it was okay to close.


Bring CLOMonitor score of Prometheus to 100

Proposal
This issue tracks the work that need to be done to bring the CLOMonitor score of Prometheus to 100
CLOMonitor report
Summary
Repository: prometheus
URL: https://github.com/prometheus/prometheus
Checks sets:  COMMUNITY + CODE
Score: 80
Checks passed per category

Category
Score

Documentation
83%

License
75%

Best Practices
80%

Security
75%

Legal
100%

Checks
Documentation [83%]

[ ] Adopters (docs)
[x] Changelog (docs)
[x] Code of conduct (docs)
[x] Contributing (docs)
[ ] Governance (docs)
[x] Maintainers (docs)
[x] Readme (docs)
[ ] Roadmap (docs)
[x] Summary Table (docs)
[x] Website (docs)

License [75%]

[x] Apache-2.0 (docs)
[x] Approved license (docs)
[ ] License scanning (docs)

Best Practices [80%]

[x] Analytics (docs)
[ ] Artifact Hub badge (docs)
[x] Contributor License Agreement (docs) EXEMPT
[ ] Community meeting (docs)
[x] Developer Certificate of Origin (docs)
[x] Github discussions (docs)
[x] OpenSSF badge (docs)
[x] Recent release (docs)
[x] Slack precense (docs) EXEMPT

Security [75%]

[x] Binary artifacts (docs)
[x] Code review (docs)
[x] Dangerous workflow (docs)
[x] Dependency update tool (docs)
[x] Maintained (docs)
[ ] Software bill of materials (SBOM) (docs)
[x] Security policy (docs)
[ ] Signed releases (docs)
[ ] Token permissions (docs)

Legal [100%]

[x] Trademark disclaimer (docs)

For more information about the checks sets available and how each of the checks work, please see the CLOMonitor's documentation.

Hi there! I think we already have one of these issues: https://github.com/prometheus/prometheus/issues/11462, so I'm wondering if a new one is necessary.

Thanks for bringing that to my notice.


A more intuitive nesting order example

I think it's hard to understand with only existing examples.

Rendered

/fast-forward


instructs appveyor to not build branches with an open pull request

Closes #52

I changed my mind. I think that both the feature branch, and pr builds are a good thing. This should not be merged, as no meaningful change exists, and the issue should be closed as will not fix


Run ruff format on cogs

Worth noting it did try and fix the line lengths on the method signatures but i put them back to normal - though we could look at that in more detail if you think it would look better?

I don't agree with many of ruff's opinionated format descisions. Therefore its more hassle than it is worth, to attempt to bend to using their format command for this codebase. I hope to implement many of the format improvements that we do agree with using a custom linter: https://github.com/CarrotManMatt/flake8-carrot.
Please feel free to open any issues on that repository for features that should be checked, after ensuring they haven't already been listed.

I don't agree with many of ruff's opinionated format descisions. Therefore its more hassle than it is worth, to attempt to bend to using their format command for this codebase. I hope to implement many of the format improvements that we do agree with using a custom linter: https://github.com/CarrotManMatt/flake8-carrot.
Please feel free to open any issues on that repository for features that should be checked, after ensuring they haven't already been listed.

Not saying we need to follow everything it suggests - but in this case it does seem to have fixed several things you usually complain about (double space between comment and code, right spacing between methods and imports and shit) but if there's specific bits in this one specifically you don't like I'm happy to change it back

Oh I see. I misunderstood and thought that this PR was implementing the autoformat. I see now that it's just fixing some suggested formatting fixes. The automatic fixes can be made with https://github.com/CarrotManMatt/flake8-carrot 👍🏻

yeah it was literally just me running the formatter - I intend to do the same for other areas of the code as well but didn't wanna make one PR too chonky


Autodump stats

Add the strategy and its parameters to the results could be usefull

This issue was moved to highvelocityspace/zenbot#82


Fixed #28009 -- Document and test Field.empty_value for CharField subclasses

Ticket #28009
This is a partial fix for this ticket. If focuses on the form fields rather (model fields also need to be looked at). I've paused as this point to get some wider input.
The ticket explains that the CharField subclasses should also return empty_value; however, the docs explain that the subclass fields return an empty string.
What is happening in practice is a bit of a mixture. Some fields do return empty_value (email, regex, slug, url). However, GenericIPAddressField always returns an empty string and JSONField and UUIDField always return none. I've added tests for all of these to show the behavior.
So question is - is this inconsistency right (that's how I've written the docs), or is there further work to ensure all of the fields return empty_value.
Appreciate thoughts.

I think we shouldn't change the default empty values, let's test and document them. A change is likely to break something for someone and so that's good enough reason for me not to meddle with this. If someone needs something different there is already the option to do that.

I don't think there was too much change needed on the model side.
I added a few more tests, and the documentation already reads ok for me ('string based field such as...')
While reviewing this I came across a section where 'assertraises was used. I needed to change this to assertraisesmsg as a couple of the tests passed even if kwargs were changed, to understand what was going on here. I've put it as a separate commit, happy to chop it is not appropriate.


add Chungang University

**Chungang University
[Hompage URL]
https://graduate.cau.ac.kr/2018_en/
** Education Level

Bachelor Degree

** Graduate School Course

@jeonginy I am sorry, the domain cau.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Wrong return type hint in parametric get_total_mass

I noticed that the parametric version of get_total_mass has float as return type hint, but it returns a Casadi function instead.
Moreover, there are two consecutive return. See https://github.com/ami-iit/adam/blob/2f18e9e737beeb00a4687a37d10a4822d0e5959b/src/adam/parametric/casadi/computations_parametric.py#L272-L275
cc @CarlottaSartore

In addition, the input order is different. For all the other functions, the length multiplier input comes before the densities. For this function only, it is inverted.

In addition, the input order is different. For all the other functions, the length multiplier input comes before the densities. For this function only, it is inverted.
At this point, I think it is safer to rename that method to get_total_mass_fun so that if some other code was using it, it is clearer that it has changed. In fact, both the two inputs are vectors, and it might be possible to detect easily when they are swapped.

Interestingly, the test in https://github.com/ami-iit/adam/blob/2f18e9e737beeb00a4687a37d10a4822d0e5959b/tests/parametric/test_CasADi_computations_parametric.py#L127C62-L127C78 does not fail. I guess this is because the total mass is bilinear on the density and length, so maybe inverting their order does not change 🤔

I fixed it in https://github.com/ami-iit/adam/pull/72


Feat: Automate greeting using Github bot 🤖

Describe the feature
As the contributor count rises on the repo, it becomes increasingly challenging for maintainers to personally greet and encourage each contributor for their valuable input. Equally important is the reminder for them to review the project's contribution guidelines.
Add ScreenShots
PR greeting message ⬇

ISSUE greeting message ⬇

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Anushkabh I would like to work on this issue, kindly assign me

@Anushkabh Kindly review the PR and merge whenever you are free.

Fixed in #109


uv: 0.4.30 -> 0.5.1

https://github.com/astral-sh/uv/releases/tag/0.5.0
https://github.com/astral-sh/uv/releases/tag/0.5.1
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

[ ] Fits CONTRIBUTING.md.

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

maybe it needs to point staging branch because it's breaking release

Yes, true.

maybe it needs to point staging branch because it's breaking release

Yes, true.

I changed it.

Thanks !

Hey small personal opinion, I don't think anything depends on uv yet in nixpkgs, so sending this to staging doesn't add anything and makes the update land later.
That being said, I could be wrong and I do respect if you have a different opinion.
Thank you both for the contribution!

I think that the rationale was to respect the release calendar for 24.11.
Any "breaking"/major update should be delayed to post-branch-off. This is why we decided to merge this update in staging.

Ah that makes sense !


Thurs branch

Jay,
Thank you for taking the time to point out the parts in my code that need
help. I 'll look into your suggestions and get the edits to you. I am going
over last week's lectures and demos and hopefully I'll catch something I
missed the first time through.
On Sat, Jun 16, 2018 at 1:45 PM, Jay Silvas<EMAIL_ADDRESS>wrote:

@JSilvas commented on this pull request.
Code review
In JS/app.js
https://github.com/MthwBrwn/cookie-stand/pull/5#discussion_r195911581:

\ No newline at end of file
+var alki= new Store('Alki',2,16,4.6);

+renderHeaderRow();
+//  --- need to get this working
+// renderAllCookieRow();
+firstAndPike.renderCookieRow();
+seaTacAirport.renderCookieRow();
+seaCenter.renderCookieRow();
+capHill.renderCookieRow();
+alki.renderCookieRow();
+new Store.renderCookieRow();
This might be a problem spot. It looks like you are trying to create a new
Store object instance & render it's data to the DOM. Alternatively, you
could grab the new instance from your stores array once it is created from
your input form.
In JS/app.js
https://github.com/MthwBrwn/cookie-stand/pull/5#discussion_r195911696:

tableEl.appendChild(tRowEl);

+Store.addNewStore= function(event) {
+//prevent refreshing of page

event.preventDefault();
var newLocation = event.target.storeLocation.value;
var newMinSales = event.target.minimumSales.value;
var newMaxSales = event.target.maximumSales.value;
var newAvgSales = event.target.avgSales.value;

new Store(newLocation, newMinSales, newMaxSales, newAvgSales);

I would try a console.log of the whole line 140 to see if this new object
is being instantiated the way you intend.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MthwBrwn/cookie-stand/pull/5#pullrequestreview-129372370,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlVhBntmidBSzQItlt4fu32QVNAVW4Ylks5t9W5UgaJpZM4UpyKz
.


[i18n-FR] Translated "Integrations" to french (sub PR of 1900)

What is this PR about ?
This is a sub PR, I translated the "Integrations" part of the documentation to french, they require review. I also added the toctcree as I will be creating PRs for other files aswell.

Hey @Wauplin, I understand, I will stop comiting until I find people who can help, thank you for the effort.


add go mod, and fix bug

I think ran should support mod now
and there is a bug

Thanks for the feedback.

Currently "ran" is not compatible with go mod. I'll think about to introduce go mod in the project.

The bug in you fork appears after you add go.mod file. In the go.mod of your fork, there's a line: github.com/m3ng9i/ran v0.1.3. Tag v0.1.3 does not point to the latest code of ran. In v0.1.3, global.LoadConfig() have no arguments, but in the latest code, global.LoadConfig() have one String argument. This is why the bug appears in the fork github.com/ssor/ran. And I didn't use go.mod in my original code, so the bug you talk is not exist in github.com/m3ng9i/ran.


fix: bug issue template

Description
This PR fixes bug issue template that doesn't appear on the issue templates list by fixing indentation.

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Fixes #52

Mobile & Desktop Screenshots/Recordings
N/A

Steps to QA

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Thanks @adiati98!


Need more events regarding user inputs (focus, blur, change)

Without events like focus, blur, and input change (even if invalid) it is challenging to build a full form experience.
So far I had to use a hack to try to work around the lack of events:
useEffect(() => {
    const input = theRef.current?.querySelector('input');

    // HACK: the Datepicker doesn't callback on invalid dates
    const callback = (e: any) => {
      if (!dayjs(e.target.value).isValid()) {
        setValue(e.target.value);
      }
    };
    const blur = (e: any) => {
      setTouched(true);
    };
    if (input) {
      input.addEventListener('change', callback);
      input.addEventListener('blur', blur);
    }
    return () => {
      input?.removeEventListener('change', callback);
      input?.removeEventListener('blur', blur);
    };
  }, [setTouched, setValue]);

this allows me to trigger validation on blur, allows me to set invalid values to run against my validation code, etc.
I feel like this sort of stuff should be cooked into the component.

Could you show all code of this component

Any update on this? Or @dlikhten could you share some more of the code you have, i cant make it work


Property column updated!

Error was causing when using TinyMCE
After adding picture , just crop the image then try to save it.
Error:
“SQL Error 1406 Data too long for column for properties”

Thank you for this.
I'm going to keep text as the default as this will probably will be the right format for most people.

My pleasure
Regards


lxc export of running container breaks when file is missing

Required information

Distribution: Ubuntu
Distribution version: 19.04
The output of "lxc info" or if that fails:

Kernel version: 5.3.0-46-generic
LXC version: 4.0.1
LXD version: 4.0.0
Storage backend in use: dir

Issue description
Export of running container breaks if file disappears (for ex. from .../roundcube/temp/).
Steps to reproduce
Tested on actively used roundcube CT.
It is problem to stop it during export.
It would be nice if in this case the export would give a warning, but not break
Information to attach
lxc export roundcube roundcube.tar.gz
Error: Create backup: Backup create: lstat /var/lib/lxd/storage-pools/default/containers/roundcube/rootfs/.../roundcube/temp/rcmAttmntdDYrtL: no such file or directory

@tomponline another tweak to the tarball writer?

@stgraber yep will take


Added New Features

Added a feature to save the best score from all time in a txt file.
Also added a different variation to the press any key label in the main page as I felt there were too many hands in that page

oh i accidentally removed the copyright label just cause i was working with the placement for the other label
thats my bad, please add that again. I can send in a new pr if nessesary

I like the file save feature, but not the hand and copyright removal.
Feel free to open up a new PR with the saving!


Add Gradle plugin

@buchananwill has a working version of this they can contribute. Need to figure out how to write some tests for it. The Maven plugin should serve as some inspiration for how tests can work: it generates a schema file, and then uses yarn commands to test it against some JS tests

Thanks, I will use the pattern of the maven plugin tests. I'm familiar with
Js/ts testing so that's no problem.
On Sat, 28 Sept 2024, 16:30 Ivan Greene, @.***> wrote:

@buchananwill https://github.com/buchananwill has a working version of
this they can contribute. Need to figure out how to write some tests for
it. The Maven plugin should serve as some inspiration for how tests can
work: it generates a schema file, and then uses yarn commands to test it
against some JS tests
—
Reply to this email directly, view it on GitHub
https://github.com/ivangreene/java-to-zod/issues/53, or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBL2M6K3MBFAZA6CY555QOTZY3DQJAVCNFSM6AAAAABPAW4D62VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TIMZTGU4TIMY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Quick question, all your files are LF, not CRLF - yes?


Modify column width

How can I modify the column's width?

Hello @N214
Yes, you can do it. but you need to edit the structure of the theme. so go to layouts/partials/default.html then you can change the column by following bootstrap 4 column class. thank you

I am going to close this issue, if you need more support you can re-open this issue, or create a new one. thank you


Update chris-sainty.json

Updated by RSS feed as it was pointing to the wrong place. Plus some general improvements to my card.

@chrissainty Hey Chris, thanks for the update. Would you mind updating to the latest format? https://github.com/casals/dotnet-creator-cards/blob/main/creator-cards/_creatorTemplate.json
Thanks and Greetings
Matthias

@matthiasjost I've updated the card to the new format. Let me know if there are any other issues.

Hey @matthiasjost when will the site update with the new info?

It should have happened by two hours after the merge, but it didn't.
I will look at this together with Tim.

Any joy with this?

Any news on this @DeeJayTC?

Yea, have to rebuild the index and have it reload a few of the creators. Hopefully got time to do that tomorrow or monday.


ID switch test parametrisation

Parametrising test for counting ID switches

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

Project coverage is 30.89%. Comparing base (265a5a4) to head (ac09ed3).
 Consider uploading reports for the commit 036bc4c to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #156   +/-   ##
=======================================
  Coverage   30.89%   30.89%
=======================================
  Files          19       19
  Lines        1259     1259
=======================================
  Hits          389      389
  Misses        870      870

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


Mock-server times out for /keys

OS Ubuntu
If going into production mode, everything works fine.

Happens if there are no keys.

Requesting the key once from the cmd line curl http://localhost:8999/keys enables the proxy...

@faboweb Are you still having this issue?

Still the case.


Getting Request failed with status code 409

Describe The Bug:
It was working ok with a week or two with the latest version.  For no reason that I aware of, it stopped working with this error:
[5/5/2023, 8:37:00 PM] [smartthings-tv] [Big Li TV] Registering input source: TV
[5/5/2023, 8:37:00 PM] [smartthings-tv] [Big Li TV] Registering input source: HDMI 2
[5/5/2023, 8:37:04 PM] [smartthings-tv] [Big Li TV] Resetting active identifier to TV because application registration needed to open all applications
[5/5/2023, 8:37:05 PM] [smartthings-tv] [Big Li TV] Error when executing setInputSource of capability samsungvd.mediaInputSource: Request failed with status code 409: {"requestId":"EAB05282-B35E-46DF-81AA-4B9C5BD59EF3","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
If I try to power off the tv with Homekit, I got this error:
[5/5/2023, 8:42:04 PM] [smartthings-tv] [Big Li TV] Error when executing on of capability switch: Request failed with status code 409: {"requestId":"F038B173-2AF5-4E1A-8B74-A9428F25A6AA","error":{"code":"ConflictError","message":"invalid device state","details":[]}}
To Reproduce:
I restarted the hb service, rebooted the server, no difference.   I used the tv remote to "power off" the tv but no difference.  The only thing I plan to try next is to physically power down the TV which is a bit harder since the power plug is behind the tv.

 Could you please try to use the SmartThings Smartphone App and check if everything works correctly there.

Yes, something went south in the tv.  Even the SmartThings app that I had configured to control the tv indicated "offline" state and couldn't turn on the tv.  I looked for some means to revive the state within the tv, and even unplugged the tv did not work.
After powering up the tv, I went to the SmartThing "service" on the tv and click on "Add Device".  I did not expect anything to happen but it did!  Even no new device showed up, the SmartThings app on iphone switched to indicating online, the error went away in HB.  So re-adding device unclogged something with the tv.
thanks.
My personal opinion, the Samsung software is quite poor and non-intuitive.

Glad it's working again.
Yeah I agree with you. The SmartThings stuff has confused me quite some times when developing this plugin. I'm not really happy with how it is behaving. But you have to take what you get. And for my personal use case that I started with (turning TV on/off and changing inputs) it is (mostly) working.


Models 2 - Photo and Album

Added models for the Photos uploaded by a User and the Albums created by the User for the Photos uploaded. Also added tests for the new models.

Coverage remained the same at 100.0% when pulling 13c9d2eadacb2317268e9086b69b43777d1db20a on models-2 into 22cfb317a3ee7a9fe573dd3be86a0640bca6ae9b on master.

Coverage remained the same at 100.0% when pulling 7e302a69ad7c938cb506804ba53fc19b5aa62deb on models-2 into 22cfb317a3ee7a9fe573dd3be86a0640bca6ae9b on master.


Enums in query parameters are not counted

First of all, thank you for sharing this project with us, it's awesome and I find it very useful.
I've found that it doesn't take into account enums in query parameters, for example when I define following method it would generate completely random string as a value for the parameter:
/mymethod:
  get:
    parameters:
      - name: myenum
        in: query
        type: string
        enum: ['a', 'b', 'c']
        required: true

I'm using version 0.99.4

I'll add this to the examples and look into it. Currently a bit busy with another project


Golang fundamental flaw bug - V3.0.0-rc4

Reopening regression issue. Last issue ref: https://github.com/argoproj/argo-workflows/issues/5192
Hey @alexec
The issue still happening on version 3.0.0.-rc4

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

fix(controller): Work-around Golang bug. Fixes #5192 (#5230)

Must have been missed somehow. https://github.com/argoproj/argo-workflows/releases

@simster7 can I ask this goes in rc5 please?

Yes, sorry. I must have inadvertently skipped it in rc4. I can get a new release out today? @alexec

No hurry. Next week is ok.


Hybrid Execution catalog updates for out-of-session updates?

Hey :wave:
I'm wondering if this is expected behavior or not:
Step:

Connect to cloud-url (hybrid exec)
Go to dashboard and follow tutorial to add external postgres my_pg
I can't query my_pg [attempted 3x] in hybrid exec unless I close and re-establish the session.

Not expected, we should be fetching the catalog if there's a chance that we have an out of date one. Currently we do that if execution of a query errors, but I don't believe there's anything in place if query planning errors (where this occurs).