Error #3000

How do you get around the failure to play the video due to error #3000? I can't get twitch to play using TwitchPlayer or even in safari..

Hi,
Please see this page by twitch on how to fix this error: https://streamdiag.com/fix-twitch-error-3000/

All of those errors seem to be related to experiencing that error in a browser, rather than on an embedded stream.

The same resources are used for embedded players and players you see on Twitch, so by clearing your cookies you will likely resolve this issue. You can clear your cookies using the following function:
    /// Call this to clear the cache of WKWebViews.
    ///
    /// - Parameter completionHandler: The completion handler for the completion of wkwebview cache removal.
    public static func clearWKWebViewCache(completionHandler: @escaping () -> Void) {
        if #available(iOS 9.0, *) {
            let websiteDataTypes = NSSet(array: [WKWebsiteDataTypeCookies])
            let date = NSDate(timeIntervalSince1970: 0)
            WKWebsiteDataStore.default().removeData(ofTypes: websiteDataTypes as! Set<String>,
                                                    modifiedSince: date as Date, completionHandler: completionHandler)
        } else {
            var libraryPath = NSSearchPathForDirectoriesInDomains(FileManager.SearchPathDirectory.libraryDirectory, FileManager.SearchPathDomainMask.userDomainMask, false).first!
            libraryPath += "/Cookies"

            do {
                try FileManager.default.removeItem(atPath: libraryPath)
            } catch {
                print("error")
            }
            URLCache.shared.removeAllCachedResponses()
        }
    }

Please try running the function and let it complete its thread before displaying the twitch player; this should resolve the issue.

Great that did it! TYVM!


TwicImg or TwicPicture

Hello,
What's the difference between TwicImg and TwicPicture ?
What do you mean by critical images?
Thanks you

TwicImg renders an img tag and uses Javascript to dynamically lazy-load a "pixel-perfect" image as the source (src).
TwicPicture renders a picture tag with several sources so the browser can choose the best one.
A "critical image" refers to an image that is deemed essential for the initial rendering of a webpage, particularly those that are visible above the fold.
We recommend using TwicPicture for critical images (especially if you use a framework that supports SRR) and TwicImg for off-screen media.
More info in this article.

@florentb was faster than i. But know you have my version too ;-)


Handling with CSS Modules - react-slick in gatsby project

Hey guys!
I'm using react-slick in gatsby project.  I'm trying to customize the "slick-current" but I couldn't because Gatsby use a CSS Module approach.
Do we have some work around to do it? Any suggestion?
Thanks!

What is it that you're doing to customize?

@flavioalves

Create a container for your slider, and position it appropriately.
You may want to take a look at centerMode and centerPadding for some alignments.
You can identify the current item with several methods. the clearest one is to bind a callback on afterChange and update your state from there:

configuration
afterChange: (index) => {
  this.setState({currentSlide: index});
}

slider
<Slider>
  {yourItems.map((item, index) => {
    return <item className={`${index === this.currentSlide ? "activeClass": ""}`}
  })}
</Slider>

afterChange can take care of your animations as well - just create your images with the corresponding indices and animate it  by either adding a class or calling an animation function on it:

render
render() {

return (

       {yourImages.map((img, index) => {
          return
...

        })}

    <Slider>...</Slider>

)
}

I presume the problem is solved, so I'm closing the issue.


Build bump to pick up htslib 1.20

Build bump to pick up htslib 1.20 [sc-50311].

macOS osx_64 build hit:
2024-07-12T21:51:57.5050830Z + bash test-cli.sh
2024-07-12T21:52:05.8319530Z test-cli.sh: line 11: 17464 Illegal instruction: 4  tiledbvcf export --uri s3://tiledb-inc-demo-data/tiledbvcf-arrays/v4/vcf-samples-20 --regions chr1:1-100000 --sample-names v2-usVwJUmo,v2-WpXCYApL --output-format z --output-dir "$OUTDIR"

rerun

macOS osx_64 build hit:

I am confused why we are getting this Illegal instruction error now. We successfully built this feedstock only last week (https://github.com/TileDB-Inc/tiledb-vcf-feedstock/commit/535c08910b810da9efdf43b6541c3306b74e8619), and the osx-64 build passed. Given that this PR hasn't changed the TileDB-VCF source code, I don't see why we would need to suddenly change the OSX_DEPLOYMENT_TARGET.

@jdblischak We bumped up (released) htslib version to 1.20, and since the pin here is >1.15 it got picked up and used here. So perhaps the illegal instruction comes from htslib

I ran the builds on my fork using the latest commit (which used htslib 1.20), and I also tried pinning htslib to 1.19. Both failed with the Illegal instruction error.
This means that something has changed (either a conda dependency or something in the Azure image) since last Tuesday (July 9th) that is causing the error, and it isn't the update of htslib from 1.19 to 1.20.

I am not sure if this is correct but on azure pipelines I can see that the newest jobs run under MacOS 12.7.5 but the last pipeline that passed is also 12.7.5:
https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=40261&view=logs&j=58ac6aab-c4bc-5de2-2894-98e408cc8ec9&t=3001bc22-659c-4b49-91e9-8cb6ed43d4eb

the newest jobs run under MacOS 12.7.5 but the last pipeline that passed is also 12.7.5

Agreed. The versions are the same, but the image has changed:

last passing: Current image version: '20240630.1'
currently failing: Current image version: '20240707.1'

Agreed. The versions are the same, but the image has changed:

This is a good clue. But toolchain versions seem the same, at least:
2024-07-09T13:21:12.4685960Z INFO: activate_clang_osx-64.sh made the following environmental changes:
2024-07-09T13:21:12.5271560Z +AR=x86_64-apple-darwin13.4.0-ar
2024-07-09T13:21:12.5331170Z +AS=x86_64-apple-darwin13.4.0-as
2024-07-09T13:21:12.5379450Z +CC=x86_64-apple-darwin13.4.0-clang

2024-07-13T07:40:56.3260770Z INFO: activate_clang_osx-64.sh made the following environmental changes:
2024-07-13T07:40:56.3790890Z +AR=x86_64-apple-darwin13.4.0-ar
2024-07-13T07:40:56.3791620Z +AS=x86_64-apple-darwin13.4.0-as
2024-07-13T07:40:56.3791960Z +CC=x86_64-apple-darwin13.4.0-clang
2024-07-13T07:40:56.3792440Z +CC_FOR_BUILD=/Users/runner/miniforge3/conda-bld/tiledb-vcf_1720856107208/_build_env/bin/x86_64-apple-darwin13.4.0-clang

last passing: Current image version: '20240630.1'

This one picked up htslib 1.20, so we know definitively that it was fine before even on 1.20.

VCF versions are the same between those two runs and also feedstocks diff is just build number.

The osx-64 build runs on "macOS-12"
https://github.com/TileDB-Inc/tiledb-vcf-feedstock/blob/535c08910b810da9efdf43b6541c3306b74e8619/.azure-pipelines/azure-pipelines-osx.yml#L8
Thus here is the PR that updated the image to version 20240707.1: https://github.com/actions/runner-images/pull/10196
Very few updates were made. Trying to think of potential problems for this error:

CMake and vcpkg were updated
AWS CLI and AWS Session Manager CLI were updated. I only mention these because the line that fails is accessing an array from S3

Very few updates were made. Trying to think of potential problems for this error:

Ack. Reminding myself that this is a feedstock build. None of these updates should matter. All of the dependencies should be provided by conda.

I compared the conda packages installed in the test environment between the  last passing build and a currently failing build.
The conda packages that actually changed versions (as opposed to simply a new build) are: libcxx, c-ares, aws-crt-cpp, aws-c-io
Given that this appears to be a problem with the compilation, I investigated libcxx first. Turns out there was already an Issue open about this Illegal instruction error on osx-64 caused by libcxx 18 https://github.com/conda-forge/libcxx-feedstock/issues/162
Also potentially of interest is this PR that recently updated MACOSX_DEPLOYMENT_TARGET for libcxx https://github.com/conda-forge/libcxx-feedstock/pull/159
Full diff below:
$ grep htslib vcf-*
vcf-failing.txt:htslib:                   1.20-hcfc518d_2             tiledb
vcf-passing.txt:htslib:                   1.20-hcfc518d_2             tiledb

$ diff vcf-passing.txt vcf-failing.txt
1c1
< aws-c-auth:               0.7.22-he52cbe7_7           conda-forge
---
> aws-c-auth:               0.7.22-hdb02296_8           conda-forge
5,9c5,9
< aws-c-event-stream:       0.4.2-ha5205da_14           conda-forge
< aws-c-http:               0.8.2-hf609411_4            conda-forge
< aws-c-io:                 0.14.9-h9f49e27_5           conda-forge
< aws-c-mqtt:               0.10.4-hcc4e2a5_7           conda-forge
< aws-c-s3:                 0.6.0-h8fdb93b_0            conda-forge
---
> aws-c-event-stream:       0.4.2-h2713d70_15           conda-forge
> aws-c-http:               0.8.2-ha849b92_5            conda-forge
> aws-c-io:                 0.14.10-h9f49e27_0          conda-forge
> aws-c-mqtt:               0.10.4-hf6997d9_8           conda-forge
> aws-c-s3:                 0.6.0-hfc8374f_1            conda-forge
12,13c12,13
< aws-crt-cpp:              0.27.2-h7746516_0           conda-forge
< aws-sdk-cpp:              1.11.329-hce9e41e_8         conda-forge
---
> aws-crt-cpp:              0.27.3-hed18db7_1           conda-forge
> aws-sdk-cpp:              1.11.329-h554caeb_9         conda-forge
19c19
< c-ares:                   1.28.1-h10d778d_0           conda-forge
---
> c-ares:                   1.32.1-h51dda26_0           conda-forge
28c28
< libcxx:                   17.0.6-heb59cac_3           conda-forge
---
> libcxx:                   18.1.8-hef8daea_0           conda-forge
40c40
< libtiledbvcf:             0.33.2-hfffce77_0           local
---
> libtiledbvcf:             0.33.2-h4f7dbc7_1           local
42c42
< libxml2:                  2.12.7-h3e169fe_1           conda-forge
---
> libxml2:                  2.12.7-hc603aa4_3           conda-forge
49c49
< tiledb:                   2.24.2-h493d6f2_1           conda-forge
---
> tiledb:                   2.24.2-h86b3714_2           conda-forge

It seems that we only need to pin libcxx<18: https://github.com/TileDB-Inc/tiledb-vcf-feedstock/pull/128
So I will add one last commit removing all other aws and similar pins


fix: SDA-1749: Enable code signing for third party binaries

Description
Due to 3rd party binaries not being signed, notarisation was failing. This PR fixes the issue.
JIRA-ticket
Solution Approach
Sign 3rd party binaries using electron-builder
Related PRs
N/A

Do we need to include this file in git? installer/mac/SymphonySettingsPlugin.bundle/Contents/MacOS/SymphonySettingsPlugin

Yes, it is required while creating .pkg


this project is dead

this project is dead?

😢

@picturepan2 please tell us it is not dead… :pray:

No, it is alive.

I just had the same question.
Got projects like Tailwind snapping at your heels!

@picturepan2 Would you be open to accepting new maintainers? They could help you merge pull request and get things going again.

Same here. If @picturepan2 doesn't accept a new maintainer, I'd go for a fork - any suggestions for a name to avoid confusion?

@Vectrex No need to jump ahead of ourselves. Yan Zhu has put huge amounts of work into Spectre.
Here's some acknowledgement on Twitter that these issues are seen: https://twitter.com/picturepan2/status/1250030107432898560

I'd consider forking as a last resort. Having an (additional) maintainer is definitely a better solution. Thanks for the tweet. (And I'm pretty sure "she" is a "he" :-))

Excellent, then we just have to practice patience :)


minio-client: 2021-03-10T05-59-20Z -> 2021-03-12T03-36-59Z

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/minio/mc/releases.
meta.description for minio-client is: "A replacement for ls, cp, mkdir, diff and rsync commands for filesystems and object storage"
meta.homepage for minio-client is: "https://github.com/minio/mc"
meta.changelog for minio-client is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2021-03-12T03-36-59Z with grep in /nix/store/cjiz9jkvg3z1jx5qyljcgbc8w20qh055-minio-client-2021-03-12T03-36-59Z

directory tree listing: https://gist.github.com/b8b58c16a558d8982ebba19ff77a3eb5

du listing: https://gist.github.com/6ed4204f8b1854d632d249f4a476f051

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
minio-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cjiz9jkvg3z1jx5qyljcgbc8w20qh055-minio-client-2021-03-12T03-36-59Z \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A minio-client https://github.com/r-ryantm/nixpkgs/archive/aee836c655ff12b8b1ba2bd380ba257d715fd8a2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cjiz9jkvg3z1jx5qyljcgbc8w20qh055-minio-client-2021-03-12T03-36-59Z
ls -la /nix/store/cjiz9jkvg3z1jx5qyljcgbc8w20qh055-minio-client-2021-03-12T03-36-59Z/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

minio-client

Maintainer pings
cc @edolstra @bachp @kalbasit for testing.

Result of nixpkgs-review pr 116156 at aee836c6 run on aarch64-linux 1

1 package built successfully:

minio-client

1 suggestion:

warning: patch-phase
patchPhase should not be overridden, use postPatch instead.
Near pkgs/tools/networking/minio-client/default.nix:20:3:
   |
20 |   patchPhase = ''
   |   ^


Issues when up to production

issues "Why I up the project to production it display blank white screen when i access to /admin/login"

Did you run npm run craftable-pro:build after depolyment?

Yes, already

And it ran without any problems? A white page usually indicates that the frontend hasn’t been compiled. Do you see any errors in the console?

I don't see all errors in the console

https://uniclubzone.paragoniu.app/
Here is my website, You can check it

I checked your website and I saw the PHP error unrelated to Craftable PRO:
file_put_contents(/var/www/html/club/storage/framework/views/99eb1ac00707a17563604ccbe43bbb1a.php): Failed to open stream: Permission denied

It looks like you need to change permissions to the storage folder, see this StackOverflow thread: https://stackoverflow.com/a/54070254/23195683 .

I fix already, U can check it again ?

Please try to run npm run craftable-pro:build on your server and paste the output here so that I can check for any errors.

I try a long time but it still blank white screen

I understand. Could you please paste your command-line interface output here after running the command? You can see the example of the output in our tutorial video at the 3:50 timestamp: https://youtu.be/IU3zBf_ioyk?si=HuHj7hAFsEwhBYh2&t=230.

can you clarify this?

After you run the command npm run craftable-pro:build, you should see some output in your command line interface, something like this:

Can you copy & paste the output here or at least send a screenshot?

That seems fine. Would you mind sharing repository access with me so I can check the code?

Here
https://github.com/vividnestor/uniclubzone.git

I checked your repository, and in the file resources/views/craftable-pro.blade.php, you are missing this line after @routes:
@vite(['resources/js/craftable-pro/index.ts', 'resources/css/craftable-pro.css'])

I also updated the packages using npm update. After that, I was able to see the admin panel correctly.

It working thank you so much.


Replace Task.Result With Task.GetAwaiter().GetResult()

There are several places where Task.Result is used. But my suggestion is to use Task.GetAwaiter().GetResult() instead of Task.Result, Please refer quotes from one of the Microsoft's repo

you should avoid using Task.Result and Task.Wait as much as possible as they always encapsulate the inner exception in an AggregateException and replace the message by a generic one (One or more errors occurred), which makes debugging harder. Even if the synchronous version shouldn't be used that often, you should strongly consider using Task.GetAwaiter().GetResult() instead

Thanks for your remark, I'll create a PR for this 👍

@GooRiOn great! Thanks. As you already merged the changes, closing this ticket.


migration to vgo

Just a note, vgo is now called just go modules. BTW @nmiculinic rebase is needed for this PR.

I haven't merged this in since operator-sdk didn't support go modules properly at the time...now it does but I have other priorities and no users that I know caring about this project

Likelihood I'll actually fix this limits towards zero, closing.


[P000592] Ted Poe Options Formatting

Victims Rights under options in Ted Poe's page reads:
Victimâ€™s Rights: WEBVIC
https://github.com/unitedstates/contact-congress/blob/master/members/P000592.yaml
Not sure if that formatting is intentional, but I figured I'd point it out.

Thank you. It's an encoding thing that his developers did wrong. See http://stackoverflow.com/questions/2477452/â€™-showing-on-page-instead-of
The yaml is working so going to close this issue.


Update REDME.md

I have updated the README slightly for better readability.
(I am practicing pull requests so apologies if this doesn't seem right)

thanks for correcting!


make it clear that e&s support starts on v1.12.0, not v1.11.0

Since no one is currently able to use E&S, we allowed a technically breaking change with #410. To help mitigate potential issues, make sure it is clear that E&S is not supported before v1.12.0.

Update changelog
Update release notes on old version
be clear on changelog and release notes on new version
add example of using env name

updated in changelog and release notes.


mod rejections Client need this mod ?

Oh I did not saw this issue. I think this Issue should be fixed since a few months.

Commit: 520dbd9f687ca36507d0bbb08694fa275bab77f9


[Marker.io] (Mobile) cards shown one below the other

Steps to reproduce:

notice cards below the “catalogue”
compare with mobile figma

Actual result: it is not done as per mobile figma
Expected result: please fix

Reported by: Vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://wf-b.stg.prezzee.com/en-us/brands
Issue details: Open in Marker.io
Device typemobileBrowserSafari 18.0.1Screen Size375 x 812OSiOS 18.0.1Viewport Size375 x 710Pixel Ratio@3x

intended | Figma mobile design hasn't been changed


use mysql_config to generate linker args

This adds support for percona-server.

Bump (I just updated and ran into it again).

@sgrif Can this get merged? I ran into it again. Hard to remember how to fix it every time  :)

Can you explain more what this does and why it's needed? The current behavior already uses mysql_config as its fallback case.

I get this error:
% cargo install diesel_cli
...
Compiling diesel_cli v1.3.1
error: linking with `cc` failed: exit code: 1
  |
  = note: "cc" "-m64" " ... "-framework" "Security" "-lsqlite3" "-lpq" "-lmysqlclient" "-lSystem" "-lresolv" "-lpthread" "-lc" "-lm"
  = note: ld: warning: text-based stub file /System/Library/Frameworks//Security.framework/Security.tbd and library file /System/Library/Frameworks//Security.framework/Security are out of sync. Falling back to library file for linking.
          ld: library not found for -lmysqlclient
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

error: aborting due to previous error

It installs ok if with my change. I'm on a mac and use homebrew. I don't have mysql installed, but I do have percona-server installed (https://github.com/Homebrew/homebrew-core/blob/master/Formula/percona-server.rb). It provides the same binaries, but the libraries have different names.
My output:
% mysql_config --libs
-L/usr/local/Cellar/percona-server/5.6.37-82.2/lib  -lperconaserverclient  -lz -lssl -lcrypto

Am I doing something wrong so I don't use mysql_config in the existing release? Do I need a flag / config to use it?

Thoughts on merging this?

@nerdrew I'm facing the same issue, and I've found an easy work-around that seems to do the trick.
brew install mysql-client # keg-only, so it won't conflict with percona binaries
export PKG_CONFIG_PATH="/usr/local/opt/mysql-client/lib/pkgconfig"
cargo install diesel_cli --no-default-features --features=mysql

@sgrif I'm running into this as well. The issue here is that the percona-server package in homebrew does not install a link for libmysqlclient.dylib -> libperconaserverclient.dylib. The percona-server implementation is a complete replacement for the mysqlclient implementation and should be totally safe to merge.

Closed as this is implemented by #40


Comment expansion arrow color should indicate if there are unresolved comment threads

Currently (AFAICT) this is the same regardless of the state of the comments. It should be red or otherwise indicate unresolved comment threads if they are present. Can stay the same if otherwise.

Fixed in PR #127.


docs: Add maintainers guide

Issue #, if available:
#1295
Description of changes:
Adds a maintainers guide to the documentation site, inspired by python's maintainers playbook.

Checklist

[x] Meet tenets criteria
[ ] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jeromevdl should be good now!


Check how to hide unsupported BPMN functions

As a modeler, I would like to be able to model only those diagrams in the BPMN editor that can then also be saved in the SSoT and therefore executed. All useless events, gateways and other setting options of the Camunda modeler should be commented out.

:white_check_mark:   Conditions of satisfaction

[ ] All non-saveable gateways, event types and other setting options should be commented out in the Camunda modeler

This might help https://github.com/camunda-consulting/code/tree/master/snippets/camunda-modeler-plugins/bpmn-js-plugin-reduced-palette


NewIssue testing the use of New Issue using GitHub

lengthy comments go here

closing issue - changed made, merged w/ main, and branch deleted


Calling a function in a component when a query parameter changes

Right now I'm working on moving some of our component state into query parameters so that pages are bookmarkable and other components can cleanly change the values.
It looks like react-router will call .render when a query parameter changes, but it's not clear how to tell which part of the URL / which query parameter changed, and the work I'm doing is outside of .render, in an onChange or componentDidUpdate lifecycle method.
Is there a clean way of implementing this? It seems like I either need to:

Duplicate the query parameters in the component's state so I know when they change
Or pass the query parameters down my view hierarchy from the router as a prop

If I need that info I pass the params/query down my route view hierarchy.
Router.run(routes, (Handler, state) => {
  React.render(<Handler {...state}/>, document.body);
});

// and then everywhere else:
<RouteHandler {...this.props}/>

Now its available here on every component:
  componentWillReceiveProps (nextProps) {
    var old = this.props.query;
    var new = this.props.query;
  }

@ryanflorence I believe you meant:
 componentWillReceiveProps (nextProps) {
    var old = this.props.query;
    var new = nextProps.query;
  }

FWIW, in 0.13.2 this.context.router.getCurrentQuery() always returns the same object reference (which is then updated). This makes passing it down the hierarchy as a prop to compare it with nextProps impossible (this.props is already updated as well). Cloning before passing it down the hierarchy is a possible workaround.

With RRv4, nextProps.location.search works for me, once the component is wrapped with withRouter.

Same with me, I assume this happened when using render on . The return component from this render function (on route) did not get the next props.
<Route match="/any" render={(nextProps) => <ComponentDidNotReceivedTheNextProps />} />

@ryanhomer can you please share the code.
Thank you


Type feedback for 6.0.0.

Hey, I upgraded from node-resque and @types/node-resque to<EMAIL_ADDRESS>but found the follow dissimilarities which I don't know if they are significant or not and should just be removed
Job config is not exported
In @types/node-resque, the second parameter for Worker, jobs, are defined as follows:
export interface Job<TResult> {
    plugins?: string[];
    pluginOptions?: { [pluginName: string]: any };
    perform: (...args: any[]) => Promise<TResult>;
}

export interface JobsHash {
    [jobName: string]: Job<any>;
}

in 6.0.0 it's {} | any. Does the shape of the Job matter? If so, JobHash (maybe renamed to something like JobObject or something) and the Job type config could be exported for use.
Event Emitter event types
There's a long list of event emitter types defined that help out on using the event emitters:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/node-resque/index.d.ts#L52-L84
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/node-resque/index.d.ts#L104-L122
Currently the event parameters just show up as ...args: any[] which makes the actual events bit more cumbersome to use

Thank you @petetnt!
I'm happy to change this library to more closely match the types in the @types repo.  Can you please make a pull request that shares what those changes would look like?

Thank you for your feedback! I think https://github.com/actionhero/node-resque/pull/309 should solve these


Add ability to create cluster with containerd

duplicated of https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/3?
@jsturtevant @jayunit100

/remove-lifecycle rotten


CMake: Add BUILD_STATIC_LIBS option

@zhaozg this is a followup to https://github.com/luvit/luv/pull/459#issuecomment-592446703

This adds on to the changes in https://github.com/luvit/luv/pull/459 to make it possible to build module, static, and shared libraries all at the same time if requested

To build the module, -DBUILD_MODULE=On; the target name for the module is luv
To build a static library, -DBUILD_STATIC_LIBS=On; the target name for the static lib is libluv_a (this matches how libuv names its targets; uv for shared and uv_a for static)
To build a shared library, -DBUILD_SHARED_LIBS=On; the target name for the shared lib is libluv

These are able to be mixed/matched as needed.
This is a breaking change (as was #459) for users of CMake (e.g. luvi) who will now need to specify linking against libluv/libluv_a and turn on BUILD_STATIC_LIBS/BUILD_SHARED_LIBS before calling add_subdirectory

Some notes:

It might be possible to fix this being a breaking change when exactly one build target is specified, using luv as the target name for whatever library type is specified.

For example, luvi sets BUILD_MODULE=Off and then expects luv to be a static library. This could be maintained by setting the static library's target name luv when both BUILD_MODULE=Off and BUILD_SHARED_LIBS=Off (and also infer BUILD_STATIC_LIBS=On from the other two being off)

If anyone has other ideas for how to allow multiple library types to be built at the same time in a less breaking way, let me know


Create push Refspec from a remote branch

Given a local branch ref like refs/heads/master and a remote branch ref refs/remotes/origin/foo I cannot find a way with the current api to produce a valid refspec that git_remote_push accepts.
Just concatenating them like so wont work: refs/heads/master:refs/remotes/origin/foo
I have to manually "rename" the remote branch ref with naive string ops to look like refs/heads/foo to produce a valid refspec for pushing to a remote name with a different name.
Looking like this: refs/heads/master:refs/heads/foo
Did I overlook something or how else do I get from a remote branch name to a refspec name that git_remote_push will accept? Or is there simply no API to convert?

Sorry, posted in wrong repo


Fix index errors

Fixed errors on a specific file (can't share sorry) probably not following the standard but Meshlab can open the file that caused these two errors.
First IndexError, may be caused by a blank line after the last vt
Second IndexError, may be caused by a zero (0) normal index in many faces even though there's a large number of vn lines in that file.

Hi @mlamarre thanks for the PR! Looks good to me.
Can you add a test case to trigger these conditions?

Yes, I'll try to find time to do this in the next couple of weeks.

I added two minimal repro obj files with a text editor and two test cases.

Awesome, thank you!


Reimplement background images

rewrite code for background 'comma' images
make them as background of .page-content in default.html

Thanks for the review!


chained bind and @bind:format

In the docs https://docs.microsoft.com/en-us/aspnet/core/blazor/components?view=aspnetcore-3.0
inside the topic "Chained Bind" was explained the necessity to separate the event handler and the value:
"A chained bind can't be implemented with @bind syntax in the page's element. The event handler and value must be specified separately. A parent component, however, can use @bind syntax with the component's parameter."
But there aren't any example in substitution for @bind:format
For instance, if you try to do some child component ChildComponent.razor as
<input type"=date" value="DateValue"
@onchange="@OnChange" />
@code {
[Parameter] public DateTime DateValue { get; set; }
[Parameter] public EventCallback DateValueChanged { get; set; }
}
and a parent component ParentComponent.razor as
<ChildComponent @bind-DateValue="ParentDateValue"/>
@code {
private DateTime ParentDateValue { get; set; }
}
what happen is that that you can open the datetime snippet form html 5 but, when you select some day , by debug the parameter DateValue ParentDateValue are correctly two-binded, but the input tag at last remain empty (at last because during debugging, at first became correctly setted, but then will become empty and I don't know why).
I suppose this is linked with date formatting (bind:format) because without "chained bind" as
<input type="date" @bind="ValueDate" @bind:format="yyyy-MM-dd" />
@code {
private DateTime ValueDate { get; set; }
}
everything works correctly and, for me, the only difference is a lacking of explanation (or a bug) about how to convert the @bind:format in "chained bind" case.
Somebody can helps about this problem????
Thanks!!!!

@niconico49 thanks for contacting us.
@rynowak Can you explain what the right way to do this is? (If possible).


Feature/unr 1018 reconnect to deployment

Description
When running in editor, if server workers are restarted in short succession, utilise replace-a-worker to prevent load balancer not correctly reissuing authority.
Tests
Restart deployments with single/multiple servers over differing periods.
Primary reviewers
@Vatyx @aleximprobable

do we document replace-a-worker anywhere in the gdk docs?

@ernopp We don't. It's available in the SpatialOS docs though. The usage here isn't user facing, so don't believe we need to update current GDK docs.


iCubGenova11: port it to controlBoard_nws_yarp

I copied the files from iCubGenova10 since they should be identical
To be tested on the robot
cc @xEnVrE

Let me know when you're done with testing.
I'll merge the PR straight away.

Today's test on iCubGenova11 discovered some leftovers and some issues in the detach of cartesiancontrollerserver that caused segmentation fault on closure, now is fine, ready to be merged.


add control for using log mel spectrogram or not

add control for using log mel spectrogram or not

Sorry, but I won't take this.


Pipeline cleanup

This PR combines cleanup tasks to make our development pipelines more pleasant to use and improve:

Rename ./ci to ./dev (to match SDK dev)
Move ./dagger.json to ./dev/dagger.json (to match SDK dev)
Breaking change: repo root is no longer our CI module. '-m dev' is required.
Remove intermediary std/ directory. std/go becomes go, and so on.
dirdiff/ is no longer a weird special case
move linters/markdown to dev/markdown
Shorten argument lengths to make checks more readable
Scrub "CI" from variable and type names

I seem to be hitting a failure because of custom logic in our GHA workflows.

  set -x
  if [[ "dev" == "." ]]; then
    # set some sane defaults for the current module
    if [[ -f $HOME/.docker/config.json ]]; then
      dagger -m . call --source=".:default" --host-docker-config=file:"$HOME/.docker/config.json" docs lint
    else
      dagger -m . call --source=".:default" docs lint
    fi
  else
    dagger -m "dev" call docs lint
  fi

#7647 can't come soon enough...

Breaking change: repo root is no longer our CI module. '-m dev' is required.

Hm, not the biggest fan of moving dagger.json to dev, but I can live with it - I know you feel strongly about this one.
Is anyone currently bundling dagger using our dagger function? If so, we will need to update there - cc @jpadams.

Remove intermediary std/ directory. std/go becomes go, and so on.

Hm. The problem is, now we have some subdirectories of dev that are just util go packages like mage, build and const, while others are dagger modules, which makes it trickier to understand while reading.
I'd prefer to keep these in separate places. Maybe we could have a top-level std and a top-level dev? That also then starts to make this really part of an "official" standard library I guess.
Another alternative is to do more refactoring to get rid of the go subpackages, but that is definitely trickier for build (and we might want to bring them back one day anyways).
Or we could just leave it as-is in main for now.

Just a note for follow-ups - I'd like to make sure we're using our "std" modules, like dirdiff consistently. ATM, we're not good examples of how to do this, since we have mixed use of dirdiff and util.DiffDirectoryF.

Pushed a commit to resolve the go package issues, were you able to run this locally @shykes? It wasn't just failing in CI for me, I was having this issue locally.

Breaking change: repo root is no longer our CI module. '-m dev' is required.

Hm, not the biggest fan of moving dagger.json to dev, but I can live with it - I know you feel strongly about this one.

My reasoning was:

We should be consistent across our repo
Our root module and SDK modules are not consistent (ci + source dir for one; dev + submodule for the others). We should pick one
The SDKs cannot adopt the "ci/ + source dir" pattern, because it doesn't work when you're developing a dagger module - in that case you end up with 2 modules mixed into a single dagger.json
However the root module can adopt the "dev + submodule" pattern

Remove intermediary std/ directory. std/go becomes go, and so on.

Hm. The problem is, now we have some subdirectories of dev that are just util go packages like mage, build and const, while others are dagger modules, which makes it trickier to understand while reading.

I don't think that will be a problem in practice. The way I see it, this is a Dagger module first, and a Go codebase second. Dagger submodules shouldn't be "parked" in a special subdirectory to make space for Go sprawl. If anything I would prefer the other way around: when I navigate the directory tree of my Dagger module, I'm looking for Dagger submodules first and foremost. I find that std/ is a distraction from that.

I'd prefer to keep these in separate places. Maybe we could have a top-level std and a top-level dev? That also then starts to make this really part of an "official" standard library I guess.
Another alternative is to do more refactoring to get rid of the go subpackages, but that is definitely trickier for build (and we might want to bring them back one day anyways).
Or we could just leave it as-is in main for now.

I would like us to try what I propose in this PR for a little bit, and see how it feels, if that's OK.

Just a note for direction of follow-ups in this area - I'd like to make sure we're using our "std" modules, like dirdiff consistently. ATM, we're not good examples of how to do this, since we have mixed use of dirdiff and util.DiffDirectoryF.

Yes, my other linting module removes util altogether, it's just bundled with a bigger change. Coming soon :)

Pushed some commits to resolve the go package issues, were you able to run this locally @shykes? It wasn't just failing in CI for me, I was having this issue locally.

Yeah I was still getting errors... But ran out of time yesterday.

I would like us to try what I propose in this PR for a little bit, and see how it feels, if that's OK.

Could we do the opposite then, and move the go code sub-packages all into the dev/internal package? I understand the logic for what you suggest, but I still think it's important to have some separation here.

@jedevc I moved consts, util and build to dev/internal/. I didn't touch mage though, as I'm not sure how that is used, and I'm afraid to poke the YAML monster...

@jedevc does this look good to you?  I don't know if it's a flake or not. I'm worried that my window for merging this will close, and I won't have time to keep up with merge conflicts before going on vacation... Any help would be appreciated 🙏


WIP: Rework config and options

Rework of config and option management in F3DStarter in order to improve the behavior.

add a "global" category in the config file that as a different behavior as other category
add API to f3d::options to getNames of options and getType of option
rework the option logic

Previous behavior:
When loading a file, the command line and config file are parsed in order to figure out which options to use
New behavior:
F3D has a dynamic option that will changed over time when interacting with F3D.
When loading a file for the first time, F3D keep a hand on:

A dynamic option that will evolve overtime
Used options with the file config applied to it and copied to the engine
The option in use in the engine (hold by engine)

If no file was load previously, dynamic option contains the command line option + global section of config file.
file options is copied from dynamic option and config for the file being loaded is added on it
file is then copied to the engine to be used
If a file was load previously, before doing anything else, F3D will compare each option between the current engine options and the previous file options.
Each different option is stored in the dynamic option.
Then loading continue as before, using the new dynamic option as default for creating the file option to be passed to the engine.
Practical example with the default config (see how it changed a bit in this PR):

f3d foo.vtp bar.step
foo.vtp appears, with axis and all
press X to hide axis
press right to change file
bar.step appears without axis because it was disabled previously, and with SSAO because it is enabled in step config file
press right to change file
foo.vtp appears without axis because it was disabled previously, and without SSAO because it has not been changed
press A to enable SSAO
press right to change file (SSAO changed is added to dynamic options here)
bar.step appears without axis because it was disabled previously, and with SSAO because it is enabled in step config file
press right to change file
foo.vtp appears without axis because it was disabled previously, and with SSAO because it has been changed

I think this behavior is the most natural for multi, while still keeping full retro-compatibility with previous config file when loading a single file.

let me know what you think @Meakk ?


Crash: [SDWebImageDownloaderOperation done] on iOS7 SDWebImage 4.2.3

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
iOS

Platform Version
7.0.x

SDWebImage Version
4.2.3

Integration Method
manually

Xcode Version
Xcode 9.2

Repro rate
sometimes

Repro with our demo prj
not demo

Demo project link
NO

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.
Thread 5 Crashed:
0  Foundation                     0x2fb2f454 ___NSOQSchedule +  340
1  Foundation                     0x2fa8eec6 +[__NSOperationInternal _observeValueForKeyPath:ofObject:changeKind:oldValue:newValue:indexes:context:] +  966
2  Foundation                     0x2fa8ea0a _NSKeyValueNotifyObserver +  90
3  Foundation                     0x2fa8e764 _NSKeyValueDidChange +  344
4  Foundation                     0x2fa7ad64 -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] +  88
5  IPadTQ                         0x00045c7a -[SDWebImageDownloaderOperation done] (SDWebImageDownloaderOperation.m:229)
6  IPadTQ                         0x00047304 -[SDWebImageDownloaderOperation URLSession:task:didCompleteWithError:] (SDWebImageDownloaderOperation.m:431)
7  IPadTQ                         0x0002eefc -[SDWebImageDownloader URLSession:task:didCompleteWithError:] (SDWebImageDownloader.m:378)
8  CFNetwork                      0x2eddd2fc ___55-[__NSCFURLSession delegate_task:didCompleteWithError:]_block_invoke +  52
9  Foundation                     0x2fa9d8a6 -[NSBlockOperation main] +  130
10 Foundation                     0x2fa8daa4 -[__NSOperationInternal _start:] +  772
11 Foundation                     0x2fb3196c ___NSOQSchedule_f +  60
12 libdispatch.dylib              0x39dfce7a __dispatch_queue_drain +  374
13 libdispatch.dylib              0x39df9f92 __dispatch_queue_invoke +  42
14 libdispatch.dylib              0x39dfd744 __dispatch_root_queue_drain +  76
29 libdispatch.dylib              0x39dfd9c4 __dispatch_worker_thread2 +  56
30 libsystem_pthread.dylib        0x39f27dfe _pthread_wqthread + 291
31 libsystem_pthread.dylib        0x39f27cc4 start_wqthread + 4

This seems the same issue as #1816, it seems closed but can not fix this from the root case.
I wonder this is because of NSOperation's finished & executing is KVO by NSOperationQueue, so maybe another thread-safe problem.

There is no such line of code in SDWebImageDownloaderOperation.m:229. Are you sure you're using the correct version of SDWebImage ?
The 4.2.3 version this line should be 220

Sorry , SDWebImage Version is 4.3.0。
This is a very common problem on our app。
Which stable version is recommended？

@dennisxu1014 Each of latest the patch release should be considered stable, unless some serious bug occur (Which we may list in the change log). Such as 4.1.x -> 4.1.2; 4.2.x -> 4.2.3; 4.3.x -> 4.3.3
We follow semver


No easy way to pass a buffer from the browser to the renderer, "remote buffers" are not really useful.

When accessing a buffer remotely, we get a "remote buffer". However a "remote buffer" does not contain any data: accessing any byte triggers a getter that performs IPC behind the scene. That's way too slow! So I can't figure out any use case where one may want to share a buffer between browser and renderer.
What about just copying it, so the renderer gets its own instance, like any non-object variable?
For instance, the only way to achieve that safely is to perform a buffer.toString( 'binary' ) browser-side, then a buffer = new Buffer( buffer , 'binary' ) renderer-side. However the Buffer's documentation specifically says that the binary encoding is deprecated and will be removed in the future.
Am I missing something?

Sending big data through IPC is always slow and would block your app for some time, if we serialize Buffer when sending it the app's whole performance would be decreased as long as there is a Buffer in some objects being sent.
A possible solution is to use shared memory for sending Buffers, but I don't think it deserves the effort, because under most cases when you want to send a Buffer you are doing the wrong thing.

Hi,
I understand your point.
However "Buffer" does not always mean big data, it just means binary data.
In my case for example, the size is usually between 10 and 100 bytes. That's a very small size, still, performing random byte access is slow, so I have to rely on a deprecated feature (.toString('binary')) to achieve that properly.


FeignClient Configuration Properties

This pull request is improvement for #1931, so we can configure feign client using configuration properties

Codecov Report

Merging #1942 into master will decrease coverage by 0.66%.
The diff coverage is 79.48%.

@@            Coverage Diff             @@
##           master    #1942      +/-   ##
==========================================
- Coverage   76.18%   75.52%   -0.67%
==========================================
  Files         209      210       +1
  Lines        6367     6406      +39
  Branches      794      803       +9
==========================================
- Hits         4851     4838      -13
- Misses       1178     1226      +48
- Partials      338      342       +4

Impacted Files
Coverage Δ

...rk/cloud/netflix/feign/FeignAutoConfiguration.java
57.89% <ø> (ø)
:arrow_up:

...rk/cloud/netflix/feign/FeignClientFactoryBean.java
76.41% <79.31%> (+1.09%)
:arrow_up:

...ork/cloud/netflix/feign/FeignClientProperties.java
80% <80%> (ø)

...loud/netflix/hystrix/stream/HystrixStreamTask.java
75.92% <0%> (-19.45%)
:arrow_down:

...a/server/EurekaServerInitializerConfiguration.java
72.41% <0%> (-6.9%)
:arrow_down:

Continue to review full report at Codecov.

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

hi @ryanjbaxter @spencergibb, please review my changes

Targeting the Edgware release this summer, should be merged in the next week or two.

@spencergibb I've already added decode404 to configuration properties

@spencergibb please review the changes


Generate target roll options before extracting EphemeralEffects

This came up while I was testing the combination of a MarkToken with an EphermeralEffect predicated on the mark.
Fully replacing the original roll options with the new options from the clone probably is the safest way to do it.
Test Feat (Mastemind Racket):
{
  "key": "EphemeralEffect",
  "predicate": [
    "target:mark:effect-mastermind"
  ],
  "selectors": [
    "attack",
    "strike-damage"
  ],
  "uuid": "Compendium.pf2e.conditionitems.AJh5ex99aV6VTggg"
}

{
  "key": "MarkToken",
  "slug": "effect-mastermind"
}

What's the "this" that came up?

What's the "this" that came up?

Oh, right. The target predicate doesn't work because the roll option is set after the ephemeral effect is already resolved.


OPCT-177: pre-release v0.4.0 fixes

Fix unbound variables on the CI step when creating release v0.4: https://github.com/redhat-openshift-ecosystem/provider-certification-tool/actions/runs/5047592402/jobs/9054669579
Reorder the Container build to make sure it will succeed before creating the release, otherwise, the workflow should fail
copy and ship binaries with the prefix opct-* (s/openshift-provider-cert/opct/) to deprecate the cert name in future releases
update static files crashing when processing the tool with renamed argument plugins-image
add dev doc expanding the release process with more information about manual tests

Success execution of OPCT v0.4 on OCP 4.13.0:
$ ./opct-linux-amd64 run -w --plugins-image=openshift-tests-provider-cert:v0.4.0-beta2

 $ ./opct-linux-amd64 report opct-v0.4.0_202305221743_sonobuoy_4ea19335-24b4-4964-9942-2f54e14f8971.tar.gz
> OpenShift Provider Certification Summary <

 Kubernetes API Server version		: v1.26.3+b404935
 OpenShift Container Platform version	: 4.13.0
 - Cluster Update Progressing		: False
 - Cluster Target Version		: Cluster version is 4.13.0

 OCP Infrastructure:
 - PlatformType				: None
 - Name					: opct-v040-5fdxz
 - Topology				: HighlyAvailable
 - ControlPlaneTopology			: HighlyAvailable
 - API Server URL			: https://api.opct-v040.devcluster.openshift.com:6443
 - API Server URL (internal)		: https://api-int.opct-v040.devcluster.openshift.com:6443

 Plugins summary by name:		  Status [Total/Passed/Failed/Skipped] (timeout)
 - 10-openshift-kube-conformance	: failed [722/695/27/0] (0)
 - 20-openshift-conformance-validated	: failed [3808/1680/54/2074] (0)

 Health summary:			  [A=True/P=True/D=True]
 - Cluster Operators			: [33/0/0]
 - Node health				: 6/6  (100%)
 - Pods health				: 239/242  (98%)

> Processed Summary <

 Total tests by conformance suites:
 - kubernetes/conformance: 364
 - openshift/conformance: 3443

 Result Summary by conformance plugins:
 - 10-openshift-kube-conformance:
   - Status: failed
   - Total: 722
   - Passed: 695
   - Failed: 27
   - Timeout: 0
   - Skipped: 0
   - Failed (without filters) : 27
   - Failed (Filter SuiteOnly): 0
   - Failed (Filter CI Flakes): 0
   - Status After Filters     : pass
 - 20-openshift-conformance-validated:
   - Status: failed
   - Total: 3808
   - Passed: 1680
   - Failed: 54
   - Timeout: 0
   - Skipped: 2074
   - Failed (without filters) : 54
   - Failed (Filter SuiteOnly): 22
   - Failed (Filter CI Flakes): 4
   - Status After Filters     : failed

It's ready to promote to GA after this PR.
/unhold

/lgtm
/approve


Add optional EBS encryption and protect EBS data from being deleted

Add optional EBS encryption and protect EBS data from being deleted

/assign @JoshVanL
/unassign
/cc @alljames
Hey josh a review should be great. Once EBS volumes are created they are protected from deletion. Esp. once you change from encrypted to unencrypted

/unsassign
/assign @simonswine

/lgtm


Problem using current_user.following?(user)

I am using acts_as_follower with Devise
So I notice something funny with current_user.following?(user)
current_user.following?(user) will always resolve to false, even when it's true, unless I restart my rails server
any thoughts?

Problem is for incompatibility with Rails 5

[ ] First use gem from github. in Gemfile:
gem 'acts_as_follower', github: 'tcocca/acts_as_follower'
It is in version 0.2.1 now

[ ]  In Rails 5 models inherited from ApplicationRecord
Find "follower_lib.rb" and change line 8
if obj.class.superclass != ActiveRecord::Base
To:
if obj.class.superclass != ActiveRecord::Base || obj.class.superclass != ApplicationRecord

[ ] Then clean "follows" table. For example with
rails db:setup

excuse me for my bad english. I can't explain better.
:)

@fdahmadi this is an old solution, this is what the code look like right now
    DEFAULT_PARENTS = [ApplicationRecord, ActiveRecord::Base]

   # Retrieves the parent class name if using STI.
    def parent_class_name(obj)
      unless parent_classes.include?(obj.class.superclass)
        return obj.class.superclass.name
      end
      obj.class.name
    end

@nelsonlho so all what you have to do is listing your parent classes to in the initializer
ActsAsFollower.custom_parent_classes = [Book, Author, Publisher, User]

My first approach is wrong. Sorry.
In my application users can follows each other
After some time server must be restarted because parent_class_name return ApplicationRecord instead of User and table is corrupted and application crash in user.all_following and user.follow(other_user) dos't work correctly
It seems bug is not in acts_as_follows but in somewhere in Puma or Rails. I don't know.
But i do the following approach and after 3 days it is working correctly

First use gem from github.
in Gemfile:
gem 'acts_as_follower', github: 'tcocca/acts_as_follower'
and then
bundle install
It is in version 0.2.1 now

Find follower_lib.rb and comment 3 lines as follow

    def parent_class_name(obj)
      #unless parent_classes.include?(obj.class.superclass)
      #  return obj.class.superclass.name
      #end
      obj.class.name
    end

clean "follows" table.

Restart server

It works in my app. maybe it works on your app too.
excuse me for my bad english.
:)

I also experienced this issue on rails 5 and believe this is solved in PR #56
Use my fork if you like:
gem 'acts_as_follower', github: 'mrjlynch/acts_as_follower'

I think main problem within started Spring process & sometimes it's stuck.

@nelsonlho As @jeremylynch mentioned, I suspect that the merge of #56 should fix this. Does that take care of this issue?


Improve results page styling

Improve results page styling
Fix heading level for "Funds to Votes" at the top of page

Looks good!


Update Unity Version in setup-and-installing.md

Description
I have made this change because, not that 2018.2.0 is out of page we previously linked to, /unity/beta-download no longer contains any download links.
Tests
I'm manually testing 2018.2.0 now.
Documentation
This is documentation.

Our project is based on 2018.2.0b10 right now. Our CI is not testing 2018.2.0

sorry, clicked the wrong button 🤦♂


Consumption warning gives negative or incorrect remaining object counts

Existing behavior
Sometimes, Ninja will warn that Only -57 objects remain for codeunit objects in...
The reason for this is when the back end has object IDs consumption registered for IDs that fall outside ranges defined in app.json. For example, if app.json defines range 50000..50010, and there are 50 objects consumed between 60001 and 60050, then Ninja will say that -49 objects remain to be assigned.
Invalid object ID registrations can happen in two know ways in Ninja:

Ranges in app.json are modified after some object IDs have already been assigned in ranges that previously were defined in app.json but now no longer are.
app.json has different contents in different branches, and merge ID synchronization was used to allow development in that other branch.

Expected behavior
Ninja should always correctly calculate the remaining IDs only for the ranges defined in app.json. Any actual object IDs assigned outside ranges defined in app.json should not influence the calculation of remaining IDs. This will give correct available number of objects to developers in all branches.

This issue is opened only for the purpose of logging it in CHANGELOG.md. The problem is resolved in 2.3.1 that will be published today.


Binary Distribution for Python 3.10

Python 3.10 was released yesterday. However, the command below fails
pip install jaxlib

since jaxlib is linked against specific version of CPython. It would be great to provide jaxlib to end users for the fresh version of Python.

With #8101 merged, JAX builds and the tests pass on Python 3.10.
@yashk2810 would you please take over this bug and look after:
a) adding 3.10 to our release builds and
b) our CI tests?
You may need to wait for scipy to release 3.10 wheels first, which I believe is tracked by https://github.com/scipy/scipy/issues/14567
For the above, I built scipy from git head locally; the released scipy did not work correctly with 3.10, so you can't rely on pip install scipy to do the right thing until there is a scipy release.

@hawkinsp Many thanks!

Sounds good. I'll wait for scipy.

scipy is released now, but jaxlib still doesn't install

scipy is released now, but jaxlib still doesn't install

@NeilGirdhar It's okay. Package jaxlib is binary distributable what means that it is pinned to particular version of Python. Information from SciPy maintainers about release with Python 3.10 support appeared one hour ago so JAX maintainers have no enough time to build jaxlib and upload to PyPI. Just a little more time.

@daskol Yes, sorry, I was just trying to let the Jax developers know that scipy is no longer blocking jaxlib 😄

Hi. Any update on this?

Hi, yes we are releasing today! Stay tuned :)

jaxlib 3.10 wheels have been released: https://pypi.org/project/jaxlib/0.1.75/#files
New jax release too: https://pypi.org/project/jax/0.2.26/#files


open README.md with unicode (to support Hugging Face emoji); fix various typos

(close #217, #66, #67, #69, #91, #126, #127, #145)

Please consider including general attribution for all contributors whose pull requests were closed and incorporated.


Pins published by trial applications shouldn't count

I spot a minor bug in Pinterest's backend. It's not related to the code in this repository, but I haven't found a better place to report it.
Steps to reproduce:

created an app with Trial access
created a board and a section manually
create several pins over API in the board/section using the app
Check, how it looks for another user / anonymous user

Expected result:

No pins in the section and board shown
The number of pins in the section and the board is 0

Actual result

No pins in the section and board shown ✅
The number of pins >0. Even though the user cannot see these pins ⚠

Thanks for the bug report. I'll file it in Pinterest's internal Jira system. In the future, you can report bugs in our Help Center: https://help.pinterest.com/en/contact (I just looked at this page and think that Pinterest API and Developer Tools / API Technical Support / Pinterest API v5 will get you to the right place.)

Closing this issue, because it's not related to this repo.


[R-package] Protection stack imbalance and unprotected objects

The R-package has two protection issues. First, there is a protection stack imbalance when functions are exited by returns from the catch statements in the R_API_END macro. This issue is found when running rchk; see the output below. Second, several objects (results of Rf_asChar(.), e.g. here) which should be protected are currently not protected.
Disclaimer: the main credit for finding the causes of these issues goes to @kalibera.
I will make a pull request / proposal with a suggestion for a solution for this.
Below is output when running rchk on the LightGBM CRAN R-package after this commit
https://github.com/microsoft/LightGBM/commit/42ddff1dec813a868478e698f4fe3883dfde61b6. Note that the missing protections for Rf_asChar(.) are not found by rchk.
Function LGBM_DatasetCreateFromMat_R
  [PB] has possible protection stack imbalance /rchk/packages/build/JczWIO8n/lightgbm/src/lightgbm_R.cpp:126

Function LGBM_DatasetGetFeatureNames_R
  [PB] has possible protection stack imbalance /rchk/packages/build/JczWIO8n/lightgbm/src/lightgbm_R.cpp:210

Function LGBM_DatasetGetSubset_R
  [PB] has possible protection stack imbalance /rchk/packages/build/JczWIO8n/lightgbm/src/lightgbm_R.cpp:150
Analyzed 39640 functions, traversed 108278 states.
Library name (usually package name): lightgbm
Initialization function: R_init_lightgbm
Functions: 41
Checked call to R_registerRoutines: 1

Rchk version: 3d653b7c8f92dac912532856b55f44d2986c6553
R version: 79889/R Under development (unstable) (2021-01-27 r79889)
LLVM version: 10.0.0

Thanks very much for your investigation and write-up! Linking #4282 as there is some overlap between this issue and that one, but this issue adds a lot of good details not contained there.
Could you describe how you ran rchk on {lightgbm}? Ideally a docker run command or something else that would be easy for me to reproduce. I have tried before by following the examples at https://github.com/kalibera/rchk and was not successfully (possibly because of some non-standard things we did in {lightgbm}.
Separate from #4391, I'd like to add a continuous integration job that runs rchk so we can detect and prevent such issues in the future.

Thanks a lot for your feedback.

Could you describe how you ran rchk on {lightgbm}? Ideally a docker run command or something else that would be easy for me to reproduce. I have tried before by following the examples at https://github.com/kalibera/rchk and was not successfully (possibly because of some non-standard things we did in {lightgbm}.

I used docker and followed the steps described here. Note that there is an obvious typo in the corresponding Windows documentation. After creating the CRAN lightgbm_*.tar.gz file with you shell script, I ran the following docker command docker run -v %cd%/packages:/rchk/packages kalibera/rchk:latest /rchk/packages/lightgbm_<IP_ADDRESS>.tar.gz

Excellent, thanks very much! For the sake of others looking to this issue interested in reproducing these problems, this set of commands worked for me.
sh build-cran-package.sh
mkdir packages
cp lightgbm_<IP_ADDRESS>.tar.gz packages
docker run -v `pwd`/packages:/rchk/packages kalibera/rchk:latest /rchk/packages/lightgbm_<IP_ADDRESS>.tar.gz

And that resulted in the following logs
Library name (usually package name): lightgbm
Initialization function: R_init_lightgbm
Functions: 41
Checked call to R_registerRoutines: 1
ERROR: too many states (abstraction error?) in function strptime_internal

Function LGBM_BoosterCreateFromModelfile_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:368

Function LGBM_BoosterCreate_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:355

Function LGBM_BoosterDumpModel_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:718

Function LGBM_BoosterGetEvalNames_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:521

Function LGBM_BoosterLoadModelFromString_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:381

Function LGBM_BoosterSaveModelToString_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:695

Function LGBM_DatasetCreateFromCSC_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:102

Function LGBM_DatasetCreateFromFile_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:70

Function LGBM_DatasetCreateFromMat_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:126

Function LGBM_DatasetGetFeatureNames_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:210

Function LGBM_DatasetGetSubset_R
  [PB] has possible protection stack imbalance /rchk/packages/build/ziRQDfzj/lightgbm/src/lightgbm_R.cpp:150
Analyzed 39640 functions, traversed 108278 states.

Rchk version: 3d653b7c8f92dac912532856b55f44d2986c6553
R version: 79889/R Under development (unstable) (2021-01-27 r79889)
LLVM version: 10.0.0

I've also opened #4400 to track the work for possibly adding a CI job.


[Issue] :

Hey @saloni-15 , plz check whether the project requires contributing.md file for acceptance.
And let me know if I can add it.


Add a default .vscode directory setup on project creation

When creating a new project the extension should create a .vscode directory with the following:

settings.json to tell vscode to ignore certain folders, such as build/ (always), Resources/ (alloy only), platform/ (alloy only)
launch.json with a basic debugger setup

credit to @jquick-axway for this idea (thanks!)

For a Classic app, my .vscode/settings.json looks like this...
{
	"files.exclude": {
		"build/": true
	},
	"search.exclude": {
		"build/": true
	},
	"files.watcherExclude": {
		"build/": true
	},
}

For Alloy, my .vscode/settings.json looks like the below. I've tested with "kitchensink-v2" and it correctly hides the root "i18n", "platform", and "Resources" folders... but still reveals the same folders under the "app" subdirectory.
{
	"files.exclude": {
		"build/": true,
		"i18n/": true,
		"platform/": true,
		"Resources/": true
	},
	"search.exclude": {
		"build/": true,
		"i18n/": true,
		"platform/": true,
		"Resources/": true
	},
	"files.watcherExclude": {
		"build/": true,
		"i18n/": true,
		"platform/": true,
		"Resources/": true
	},
}

Not sure if there is a better way of doing the above without the duplication. I'll leave it to the experts. :)

This is now done in ti create so closing


if user runs npm install in a module folder with no package.json, node_helper folder is erased

if you run npm install in  a module folder with no package.json, a side effect is that the MM shipped modules/node_modules/node_helper/index.js is erased, and now nothing (with node helper.js) will run, and MM goes black screen..
without knowledge of git, github, etc, there is no recovery  of this required module..
happens on 2.8.0
on my odroid its node 8.10.0, npm 6.10.2, unbuntu 18.04.3
on pi its node 10.6.0, npm 6.1.0,  Raspbian 9.4/stretch
on jetson nano, its node 10.16.3, npm 6.9.0, ubuntu 18.04.2
i think we might have to specify this as a dependency, and have a github repo for it..
https://stackoverflow.com/questions/28728665/how-to-use-private-github-repo-as-npm-dependency/28729646#28729646

Can confirm. Leaves my MM all black.
A workaround is to checkout the modules/node_modules/node_helper/index.js file from the git repo after each npm install:
git check modules/node_modules/node_helper/index.js

right.. (should be checkout , not check) but if you don't know git that well, etc.. its a fun time..
i think the node helper module should be a repo on michmich github and then referenced in package.json. then this won't happen
"node_helper": "git://github.com/MichMich/node_helper.git",

why does this even happen? Shouldn't an npm install in a module folder be local and limited to that folder/repo?
Also, this hasn't happened before 2.8.0 has it?

I hadn't seen reports of this until recently, but npm has been updated too..  so I don't know what is causing it.  but even if its npm, we STILL need to DO something to work around the destructive effects.

After I ran "git checkout modules/node_modules/node_helper/index.js" , I received an error message of:
"error: pathspec 'modules/node_modules/node_helper/index.js' did not match any file(s) known to git"
?? how badly does this affect my mirror's functionality, and what actions should I take to resolve this?

this worked for me
from the MagicMirror folder
 git checkout modules/node_modules/node_helper/index.js

how can I submit a pr, which updates the package.json, and creates a new separate repo under your userid?

can i get you @MichMich to create a github repo with just the node_helper module.. then i can submit a pr change to the package.json to depend on  it.  see my comment on Sept 2 above
but the module has to BE someplace..

can i get you @MichMich to create a github repo with just the node_helper module.. then i can submit a pr change to the package.json to depend on it. see my comment on Sept 2 above

added my own repo

pr #1827 submitted

This should be closed. Fix in 2.10

I am still having this issue.  Any help is greatly appreciated.
If I don't add any modules it works beautifully!

@johnnybfireman  please don't post in multiple issues.. one will do..  I replied in the other

Sorry my bad! Thank you for replying
Sent from my iPhone

On Dec 27, 2021, at 12:52 PM, sam detweiler @.***> wrote:

@johnnybfireman please don't post in multiple issues.. one will do.. I replied in the other
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.


chore: add metadata to survey prompt event payload

chore: add metadata to survey prompt event payload
This PR:

adds metadata to inactive user survey prompt event payload that are related to determining the prompt condition.

Pull Request Checklist
If this is your first time submitting a pull request to Dendron, copy and paste the full Dendron Review Checklist into this request and check off each item as necessary.
This template contains the short checklist which is used by the Dendron core team.
Testing

[~] Write Tests
[x] Confirm existing tests pass
[x] Confirm manual testing
[~] If your tests changes an existing snapshot, make sure that snapshots are updated
[~] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), make sure that it is included in the test workspace

Docs

[~] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Analytics

[x] if you are adding analytics related changes, make sure the Telemetry docs are updated

docs: https://github.com/dendronhq/dendron-site/pull/379


Set group invalid(ctypes)

The issue tracker is ONLY used for the python client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:
BUG REPORT

Please describe the issue you observed:
Set group invalid(ctypes branch)

What did you do (The steps to reproduce)?

What did you expect to see?

What did you see instead?

Please tell us about your environment:

What is your OS?

What is your client version?

What is your RocketMQ version?

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

Please describe the feature you are requesting.

Provide any additional detail on your proposed use case for this feature.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

fixed!


grab readme/image

Maybe add one attribute on registry.yml to specify the img and just use this grab method in case it's not defined?

OK, I added a way to explicitly define an image. Ideally, they also live in the npm/GitHub to improve discoverability. If people visit a component page with no image on npm/GitHub, then they're less likely to engage with it because don't know what it looks like.

Sample frontend:

Cool!


Cloneable

I've found Dolt useful and made some changes to make it more usable for some use cases I came across. This might be a little more involved than the direction you're looking for for Dolt. I've updated the README and documented the code for the changes.
The most noticeable change is that attribute and with_* methods return a cloned object. This allows you to re-use Dolt objects. It also eliminates the need to reset the attribute stack. I've also added with_body to make setting the POST body more clear, with_json to specifically send a JSON encoded body, and with_headers to be able to send headers. I also did some cleanup and added more documentation. Because of the addition of with_json and with_body, call always encodes kwargs as query params. This avoids confusion on how sometimes it did form post and sometimes query params. It also allows you to send a form body and have query params.
The one loose end is the mosso api. I wasn't sure about the best way to update that because I'm not familiar with that API or how people are using it with Dolt. In general, instead of using _generate_body, with_json should be used instead. should_contain_values could possibly be a part of with_json, but I also think it's odd that the user doesn't handle wrapping the params with servers since they need to know enough about the API in order to use Dolt.

Wow. This looks amazing. I've just looked at the code on my iPad, but I'll grab a copy on a real computer later today and double check everything and get this merged in and released.
Thanks for such an awesome contribution.

You're welcome. Your post http://www.travisswicegood.com/2011/06/18/50-days/ inspired me to go ahead and put the code I had mangled together for my own use into an actual contribution.


Bug 2176753: Remove dashed line from Configurations subtitle

📝 Description
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2176753
Remove the dashed line from the Configurations subtitle in MigrationPolicies Details page, as there is no any helper text for the title, but the modal is opened instead, when clicking on it.
🎥 Screenshots
Before:
Misleading dashed line under Configurations, as there's no any popover/helper text when clicking on it:

After:
Proper style for the link to edit Configurations (modal is opened after clicking on it):

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

/lgtm

/lgtm


issue close CREDENTIALS modal

https://user-images.githubusercontent.com/56961917/135977438-677210ff-93bf-4392-87e8-227a9a9731a9.mp4

hello, how often does Antares update

Approximately 2 or 3 times per month.
Probably next days I will release an update with fix and translations.
Which distribution are you using?


Corrected Sumbit to Submit

What kind of change does this PR introduce? (Fixed a typo)

Why was this change needed? (Changed Sumbit to Sumbit in the frontend components)

Other information:

When comparing the PR's, it shows a lot of changes but i just changed Sumbit to Submit in all of them

@holopin-bot @Cioraz Thank you!

Hey,
Could you also assign it the hacktoberfest-accepted badge if it suits your needs.
I shall contribute more issues soon


Delight logic for major and above

Implement properly delight major and above properly, requiring a 1N place notation for one of the transitions. Currently it just makes sure the relevant place near the treble isn't made, which works fine for minor but not on higher states..

#43 fixes the inconsistencies. There's further work possible for major and above to see which internal place can be made (4ths, 6ths etc), and then if there's only one remaining option, to apply it.

#43 fixes the inconsistencies. There's further work possible for major and above to see which internal place can be made (4ths, 6ths etc), and then if there's only one remaining option, to apply it.


create matrix_trace.php

Why:

Closes #ISSUE_NUMBER
What's being changed:

Why:
Closes #4602
What's being changed:
created  matrix_trance.php


Support eigen release

This is a common issue.
Seems onnxruntime wants eigen master.
The latest release of eigen, 3.3.7, hasn't include the GPU dir yet.
It only has CUDA, which should be almost equivalent to those files under GPU.
Should we check with __has_include (or other compiler equivalent in pre-17 C++)?
FAILED: CMakeFiles/onnxruntime_providers.dir/tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc.o
ccache /opt/rh/devtoolset-8/root/usr/bin/g++  -DONNX_ML -DONNX_NAMESPACE=onnx -DORT_RUN_EXTERNAL_ONNX_TESTS -DPLATFORM_POSIX -DUSE_FULL_PROTOBUF -DUSE_MKLML=1 -DUSE_MKLML_FOR_BLAS=1 -DUSE_MLAS -DUSE_OPENBLAS=1 -DUSE_OPENMP -I/tmp/scratch/onnxruntime/include/onnxruntime -Imklml/src/project_mklml/include -I/tmp/scratch/onnxruntime/cmake/external/nsync/public -I. -I/tmp/scratch/onnxruntime/cmake/external/gsl -I/tmp/scratch/onnxruntime/cmake/external/gsl/include -I/tmp/scratch/onnxruntime/cmake/external/onnx -I/tmp/scratch/onnxruntime/cmake/external/protobuf/src -Ionnx/.. -I/tmp/scratch/onnxruntime/onnxruntime -I/usr/local/include/eigen3 -I/tmp/scratch/onnxruntime/onnxruntime/../cmake/external/gemmlowp -I/tmp/scratch/onnxruntime/onnxruntime/../cmake/external/re2 -fdebug-prefix-map='/tmp/scratch'='/usr/local/src' -g -fopenmp -DGSL_THROW_ON_CONTRACT_VIOLATION -Wall -Wextra -ffunction-sections -fdata-sections -Wno-error=sign-compare -Wno-parentheses -O3 -DNDEBUG -march=native -mtune=native -DGSL_UNENFORCED_ON_CONTRACT_VIOLATION -flto -fno-fat-lto-objects -fPIC   -std=gnu++14 -MD -MT CMakeFiles/onnxruntime_providers.dir/tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc.o -MF CMakeFiles/onnxruntime_providers.dir/tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc.o.d -o CMakeFiles/onnxruntime_providers.dir/tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc.o -c /tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc
/tmp/scratch/onnxruntime/onnxruntime/core/providers/cpu/tensor/cast_op.cc:10:10: fatal error: Eigen/src/Core/arch/GPU/Half.h: No such file or directory
 #include "Eigen/src/Core/arch/GPU/Half.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

System information

ONNX Runtime version (you are using): master

@snn you upgraded eigen recently. can you take a look?

We never planned to support multiple versions of any of our third-party dependencies.
It's not a bug or issue.

Yes, onnxruntime wants a commit from eigen master. The current onnxruntime master doesn't work with eigen 3.3.7.

@snnn May I ask which feature from master is used, except the path/namespace change?

FYI I don't think this is a bug/regression.
That's why I open it as Feature Request.
But I just wonder, for a library, if it's too aggressive to use master only feature without backward compatibility to any formal release.

May I ask which feature from master is used, except the path/namespace change?

@xkszltl This change is for an upcoming PR. The second PR will be very big, so I split them.  So please allow me answer this question later.

it's too aggressive to use master only feature without backward compatibility to any formal release
This is not specific to eigen. We have the same issue with ONNX. We will consider your concern.  Welcome to write to us with more evidence elaboration.

Thanks for clarification.


How to open a Modal programmatically?

I need to display my modal programmatically, inside a sveltekit Typescript component (i.e. not simply through the data-bs-target attribute on my button). Is this possible?
I've been looking at the commit logs and there seems to be some API documentation coming, but it's not on the tailwind-elements website. And I can't import the library/module into my svelte components. E.g. I can't find a valid import for te:
const myModal = new te.Modal(document.getElementById('save-dialog'), {});

@v79 please check the docs again and update tw-elements in your project to v1.0.0-beta1. We've just released a new version of our UI KIT and now you should be able to use toggle, show or hide methods in your app as we describe in docs:
https://tailwind-elements.com/docs/standard/components/modal/#docsTabsAPI

The problem for SvelteKit with the invalid import seems to still be the case. Just updated to the v1.0.0-beta1 and I can't seem to import te correctly

How did you install our UI KIT in the project? Which type of installation of SvelteKit do you use?

I'm also having trouble getting the modal to work via the API. I'm using:
"@inertiajs/vue3": "^1.0.0",
"tailwindcss": "^3.2.1",
"vue": "^3.2.41",
"tw-elements": "^1.0.0-beta1"

With the following code:
<script setup>
import 'tw-elements';

const uploadModal = new te.Modal(document.getElementById("uploadModal"), {});

function open()
{
    uploadModal.show();
}
</script>

The entire page fails to render and I get the following error on the console:
UploadModal.vue:4 Uncaught (in promise) ReferenceError: te is not defined
    at setup (UploadModal.vue:4:17)
    at callWithErrorHandling (runtime-core.esm-bundler.js:173:22)
    at setupStatefulComponent (runtime-core.esm-bundler.js:7265:29)
    at setupComponent (runtime-core.esm-bundler.js:7220:11)
    at mountComponent (runtime-core.esm-bundler.js:5542:13)
    at processComponent (runtime-core.esm-bundler.js:5517:17)
    at patch (runtime-core.esm-bundler.js:5119:21)
    at mountChildren (runtime-core.esm-bundler.js:5303:13)
    at processFragment (runtime-core.esm-bundler.js:5476:13)
    at patch (runtime-core.esm-bundler.js:5112:17)

If I remove import 'tw-elements'; and instead use the script tag:

Can you check if importing js file like this:
import * as te from 'tw-elements';
instead of:
import 'tw-elements';
fixes the issue?

Can you check if importing js file like this:
import * as te from 'tw-elements';
instead of: import 'tw-elements';
fixes the issue?

Hi Mikolaj!
That's an improvement. I can now ditch the <script> tag and it appears to be importing te - no more error about te being undefined.
I am however having the issue about it failing to read defaultPrevented on null. The stack trace is slightly different, but I assume that's just down to the usage change we've just done.
modal.js:127 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'defaultPrevented')
    at fs.show (modal.js:127:6)
    at Proxy.open (UploadModal.vue:32:21)
    at Index.vue:38:31

Here's the bit it's referring to:
// ...
    const showEvent = EventHandler.trigger(this._element, EVENT_SHOW, {
      relatedTarget,
    });

    if (showEvent.defaultPrevented) {
      return;
    }
// ...

So it seems like showEvent is null. Should I be passing some sort of context when registering the modal or invoking its show() method? At the moment, this is all I've got:
const uploadModal = new te.Modal(document.getElementById("uploadModal"), {});

import * as te from 'tw-elements';

Trying that for me results in another error:
Could not find a declaration file for module 'tw-elements'. 'c:/.../node_modules/tw-elements/dist/js/index.min.js' implicitly has an 'any' type. Try npm i --save-dev @types/tw-elementsif it exists or add a new declaration (.d.ts) file containingdeclare module 'tw-elements';ts(7016)

Actually it's only a warning, not an error. We're working on it, but it should not break the app.

@mralston it looks like the trigger button has wrong code and modal component can't find it. Please check if you have all necessary data-attributes in your html code.

Closing due to lack of response.

Sorry for the slow response. I've created a simple example of the error using code from the documentation.
<script setup>
import * as te from 'tw-elements';

const myModal = new te.Modal(document.getElementById("exampleModal"));

function openModal()
{
    myModal.show();
}
</script>

<template>

    <!-- Button trigger modal via data attributes (this works) -->
    <button
        type="button"
        class="inline-block rounded bg-primary px-6 pt-2.5 pb-2 text-xs font-medium uppercase leading-normal text-white shadow-[0_4px_9px_-4px_#3b71ca] transition duration-150 ease-in-out hover:bg-primary-600 hover:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:bg-primary-600 focus:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:outline-none focus:ring-0 active:bg-primary-700 active:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] m-5"
        data-te-toggle="modal"
        data-te-target="#exampleModal"
        data-te-ripple-init
        data-te-ripple-color="light">
        Launch demo modal (data attrs)
    </button>

    <!-- Button trigger modal using Javascript (this fails) -->
    <button
        type="button"
        class="inline-block rounded bg-primary px-6 pt-2.5 pb-2 text-xs font-medium uppercase leading-normal text-white shadow-[0_4px_9px_-4px_#3b71ca] transition duration-150 ease-in-out hover:bg-primary-600 hover:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:bg-primary-600 focus:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:outline-none focus:ring-0 active:bg-primary-700 active:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)]"
        data-te-ripple-init
        data-te-ripple-color="light"
        @click="openModal">
        Launch demo modal (Javascript)
    </button>

    <!-- Modal -->
    <div
        data-te-modal-init
        class="fixed top-0 left-0 z-[1055] hidden h-full w-full overflow-y-auto overflow-x-hidden outline-none"
        id="exampleModal"
        tabindex="-1"
        aria-labelledby="exampleModalLabel"
        aria-hidden="true">
        <div
            data-te-modal-dialog-ref
            class="pointer-events-none relative w-auto translate-y-[-50px] opacity-0 transition-all duration-300 ease-in-out min-[576px]:mx-auto min-[576px]:mt-7 min-[576px]:max-w-[500px]">
            <div
                class="min-[576px]:shadow-[0_0.5rem_1rem_rgba(#000, 0.15)] pointer-events-auto relative flex w-full flex-col rounded-md border-none bg-white bg-clip-padding text-current shadow-lg outline-none dark:bg-neutral-600">
                <div
                    class="flex flex-shrink-0 items-center justify-between rounded-t-md border-b-2 border-neutral-100 border-opacity-100 p-4 dark:border-opacity-50">
                    <h5
                        class="text-xl font-medium leading-normal text-neutral-800 dark:text-neutral-200"
                        id="exampleModalLabel">
                        Modal title
                    </h5>
                    <button
                        type="button"
                        class="box-content rounded-none border-none hover:no-underline hover:opacity-75 focus:opacity-100 focus:shadow-none focus:outline-none"
                        data-te-modal-dismiss
                        aria-label="Close">
                        <svg
                            xmlns="http://www.w3.org/2000/svg"
                            fill="none"
                            viewBox="0 0 24 24"
                            stroke-width="1.5"
                            stroke="currentColor"
                            class="h-6 w-6">
                            <path
                                stroke-linecap="round"
                                stroke-linejoin="round"
                                d="M6 18L18 6M6 6l12 12" />
                        </svg>
                    </button>
                </div>
                <div class="relative flex-auto p-4" data-te-modal-body-ref>
                    Modal body text goes here.
                </div>
                <div
                    class="flex flex-shrink-0 flex-wrap items-center justify-end rounded-b-md border-t-2 border-neutral-100 border-opacity-100 p-4 dark:border-opacity-50">
                    <button
                        type="button"
                        class="inline-block rounded bg-primary-100 px-6 pt-2.5 pb-2 text-xs font-medium uppercase leading-normal text-primary-700 transition duration-150 ease-in-out hover:bg-primary-accent-100 focus:bg-primary-accent-100 focus:outline-none focus:ring-0 active:bg-primary-accent-200"
                        data-te-modal-dismiss
                        data-te-ripple-init
                        data-te-ripple-color="light">
                        Close
                    </button>
                    <button
                        type="button"
                        class="ml-1 inline-block rounded bg-primary px-6 pt-2.5 pb-2 text-xs font-medium uppercase leading-normal text-white shadow-[0_4px_9px_-4px_#3b71ca] transition duration-150 ease-in-out hover:bg-primary-600 hover:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:bg-primary-600 focus:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)] focus:outline-none focus:ring-0 active:bg-primary-700 active:shadow-[0_8px_9px_-4px_rgba(59,113,202,0.3),0_4px_18px_0_rgba(59,113,202,0.2)]"
                        data-te-ripple-init
                        data-te-ripple-color="light">
                        Save changes
                    </button>
                </div>
            </div>
        </div>
    </div>

</template>

Clicking the Javascript button throws the following:
runtime-core.esm-bundler.js:40
[Vue warn]: Unhandled error during execution of native event handler
  at <ModalTest errors= {} auth= {user: {…}} ziggy= {url: 'http://localhost', port: null, defaults: Array(0), routes: {…}, location: 'http://localhost/modal-test'}  ... >
  at <Inertia initialPage= {component: 'ModalTest', props: {…}, url: '/modal-test', version: '6666cd76f96956469e7be39d750cc7d9', scrollRegions: Array(0), …} initialComponent= {__name: 'ModalTest', __hmrId: '91af0292', __file: '/Users/matt/Sites/welcome-calls/resources/js/Pages/ModalTest.vue', setup: ƒ, render: ƒ, …} resolveComponent=fn<r>  ... >
  at <App>
warn2 @ runtime-core.esm-bundler.js:40
logError @ runtime-core.esm-bundler.js:230
handleError @ runtime-core.esm-bundler.js:222
callWithErrorHandling @ runtime-core.esm-bundler.js:176
callWithAsyncErrorHandling @ runtime-core.esm-bundler.js:182
invoker @ runtime-dom.esm-bundler.js:345

runtime-core.esm-bundler.js:236
Uncaught TypeError: Cannot read properties of null (reading 'defaultPrevented')
    at fs.show (modal.js:127:6)
    at openModal (ModalTest.vue:8:13)
    at callWithErrorHandling (runtime-core.esm-bundler.js:173:22)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:182:21)
    at HTMLButtonElement.invoker (runtime-dom.esm-bundler.js:345:9)

This comes back to the part about importing im not onMount. This library is not fit for SSR and you need to import things onMount to work properly

I'm not sure why someone closed that issue
I still got this error "Uncaught ReferenceError: te is not defined"

I'm not sure why someone closed that issue I still got this error "Uncaught ReferenceError: te is not defined"

Its an issue and only fixable with onMount hack mentioned earlier

"tw-elements": "^2.0.0",
const myModal = new Modal(document.getElementById("myModal"));
Uncaught ReferenceError: Modal is not defined

{{ __('login') }}

        <script>

        const myModalEl = document.getElementById("exampleModalCenter");
        const modal = new Modal(myModalEl);

        function login() {

            modal.show();
        }
    </script>

    Uncaught ReferenceError: Modal is not defined
    What's going on?

facing the same issue in react (pages dir) where the first click triggers a defaultPrevented error but then it works fin (i'm importing it using a useEffect so it imports at the çapp level on first render)


Remove Literal types "true"/"false" from type of Boolean Variants

Is your feature request related to a problem? Please describe.
When using Boolean-Variants the resulting type looks something like this:
const BasicButton = classed('button', { variants: { loading: { true: 'animate-pulse' } } })
// => { loading: boolean | "true" | undefined }

const ButtonContent = classed('div', { variants: { loading: { false: 'invisible' } } })
// => { loading: boolean | "false" | undefined }

const Button = ({ loading, children, ...props}: React.ComponentProps<typeof BasicButton>) => (
<BasicButton loading={loading} {...props}>
  <ButtonContent loading={loading}>{children}</ButtonContent>
  {/* => Type 'boolean | "true" | undefined' is not assignable to type 'boolean | "false" | undefined'. */}
</BasicButton>
)

Describe the solution you'd like
Do not include Literal types "true" and "false" in the type of Boolean-Variants.
Describe alternatives you've considered
  loading = loading === 'true' || loading

Widening the type even more might be a better solution.
I cross checked with Stitches.js, they have the same issue.
Widening it to boolean | "true" | "false" | undefined will fix the issue without breaking anyone using string matching. On it.

Yes, right. That would solve my issue 👍


Indicate who are volunteers on our site

 Issue by bcipolli
Wednesday Mar 05, 2014 at 18:48 GMT
Originally opened as https://github.com/dylanjbarth/fle-site/issues/40

As added recognition, and to focus people's attention on key points of contact, might be nice to mark volunteers clearly.

roles are now indicated


Remove listener used to test if passive listeners are supported

Once you have successfully tested that passive listeners are supported you should remove the test listeners :)

Sweet! Thanks @Mulder90 ❤


SYMBOL_INFO Name value always marshalled as a 1 character string.

Describe the bug
Callbacks that pass in a SYMBOL_INFO as one of it's parameters will always have the Name field be marshelled as a 1 chatacter string. e.g.  PSYM_ENUMERATESYMBOLS_CALLBACK for SymEnumSymbols
What code is involved
var fakeProcess = new IntPtr(1);
DbgHelp.SymInitialize(fakeProcess, null, false);
var pdbBase = DbgHelp.SymLoadModuleEx(fakeProcess, IntPtr.Zero, @"C:\Windows\System32\ntdll.dll", (string)null, 0, (uint)0, IntPtr.Zero, 0);
DbgHelp.SymEnumSymbols(fakeProcess, pdbBase, null, EnumSymbolCallback);

static bool EnumSymbolCallback(in DbgHelp.SYMBOL_INFO symbolInfo, uint symbolSize, IntPtr userContext)
{
    symbolInfo.Name will always be 1 character in length.
    Console.WriteLine("SymbolName: {0}\n", symbolInfo.Name);
    return true;
}

Expected behavior
symbolInfo.Name in the callback should be the correct string.
Workaround
I worked around the issue by changing the SYMBOL_INFO Name to be setup like so:
MarshalAs(UnmanagedType.ByValTStr, SizeConst = 4001)]
public string Name;

4001 was the value returned in the MaxNameLen field on my machine with my setup but I assume this is not the "correct" way to fix this.
I tried adding
[VanaraMarshaler(typeof(SafeAnysizeStringMarshaler<SYMBOL_INFO>), "Ansi")]`

but that doesn't work.
It looks like custom marshelers are not called in this call sequence?

This was a nasty bug. Thanks for reporting it. It is corrected in the latest commit. The callback method only can use native marshaling. I had to add the custom marshaler (per your idea) and then change the callback method syntax to make this work. I added a SymEnumSymbolsEx overload that will return all the SYMBOL_INFO structures in a single call:
using var fakeProcess = new ProcessSymbolHandler(new IntPtr(1), null, false);
var pdbBase = SymLoadModuleEx(fakeProcess, default, @"C:\Windows\System32\ntdll.dll");
foreach (var si in SymEnumSymbolsEx(fakeProcess, pdbBase))
    Console.WriteLine($"SymbolName: {symbolInfo.Name}");


User: Dashboard home - UI

Develop the User Dashboard pages UI appropriately
The user dashboard home contains 5 pages ( you should send a pull request for each of the pages)
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the colour guide and the appropriate colours

Hi. Can I work on this as well?

The admin said one person per issue but you can still check with him if that's okay.

what's the status of this issue? No, pull request yet. It's blocking other Dashboard features. Assign it to me, if possible.

what's the status of this issue? No, pull request yet. It's blocking other Dashboard features. Assign it to me, if possible.
I'm on it.
I'll make a pull request tomorrow.

Hi @PraiseDelia, any update yet?

@PraiseDelia Hi. I'd love to work on the dashboard products popup. Are you done with the issue yet?

Hi @dabsclement.
I am done implementing the dashboard feature, however, I don't think I can make any further progress due to the other contributors not sticking to the contribution guideline.
The file structure is unlike the typical React project. Attached is a screenshot of the current state of the directory structure.

Any update on this issue please?

the issue has been assigned to you @Osilaja78

Alright @ingressive4good

@Osilaja78 what is the progress status of this?

More than halfway through, was delayed due to the new folder structure which caused a lot of import errors.  Will make a PR soon @ingressive4good


Setting address on ServiceInstance

Allowing a developer to specifically set the address of the ServiceInstance for the command/service that they are making discoverable.

@pcross616 @mjwallin1 minor update to the Zookeeper component for discoverable

@Crashfreak Looks good.


add the package name custom validate to take effect

I see the #73 ,The add the validation for package name , it is really nice , but it will be overwritten the user custom validate function , so , I fix it.

Thank you for you PR!
However, I could not understand overwritten the user custom validate function.
Can you tell us about the usecase please?

in the meta.js  , if user define a validate option in the name prompt , the validate option will be overitten , it will not work。
if I config a meta.js the prompts like this:
prompts: {
    name: {
      type: 'string',
      required: true,
      label: 'Project name',
      validate: function (input) {
        return input === 'custom' ? 'can not input `custom`' : true
      }
    }
 }

#73 ,  Add a package name validate,  like this:
function setValidateName (opts) {
  opts.prompts.name.validate = function (name) {
    var its = validateName(name)
    if (!its.validForNewPackages) {
      var errors = (its.errors || []).concat(its.warnings || [])
      return 'Sorry, ' + errors.join(' and ') + '.'
    }
    return true
  }
}

so, the validate function I defined in meta.js  will be overwritten by it

Thanks!
However, I think this essential issue is overwritten the user.
we should be fixed, or warned it.
for example, in options function, check the whether exisit name, if exist it, ignore or warn.

Sometimes , we need a unified format for name ,example vue-router, vue-resource and so on. I think you should keep it

Maybe you can give a configuration item, it's value is a String or RegExp.

we need a unified format for name ,example vue-router, vue-resource and so on.

Indeed, I can now see your use-cases.indeed, I could now see your use-cases.
In that case, Looks good to me.