fix: remove discord link

Description of the Changes
remove discord link from UI and faq
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.8.0-dev.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update Dsn, update dev dependencies and pipelines.

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

[x] Update github actions.
[x] Clean config.
[x] Fixed tests.
[x] Update README.md.

👍


Crashes on iOS

the package looks for a global var that maybe an expo thing? It crashes for me instantly on iOS did not check android yet. Does this lib assume you are using expo?

hey! yes, it is only used in expo projects because it relies on expo-modules.

@alantoa any guide on how to install in an existing expo project?

it should work as-is if you use npx expo run:ios

it should work as-is if you use npx expo run:ios
Please, is there a way to use this package on an existing expo project yet?


Reviewed Three Ruby Snippets

I saw your open issue #28 and reviewed the first three Ruby snippets. The majority was spelling and grammar issues but I did add some code and documentation to two snippets just to bolster them. No code errors that I could find!

Hi @meg-gutshall, thanks for the great work. Snippets look fine, just one small linting change and we are good from my side.

Yes, @florianjosefreheis that's fine with me! Glad to help!

@meg-gutshall @florianjosefreheis Is this PR ready to be merged? Or do you plan on adding some other changes? If not I'll merge it once you agree.

@petrovicstefanrs ok from my side.

@florianjosefreheis @petrovicstefanrs Ready to merge. I will check other Ruby snippets as I have time and send them through. I'm hoping to do them in chunks of 3-4 at a time and then start creating snippets of my own once all are checked over.

@meg-gutshall @florianjosefreheis , Nice! Merging this and thank you both! 🚀


Mike | table will now sort if you pass in a sorting function. Follow …

…the examples in teh playerMatchTable.container file as well as the playerMatchesColumns.js file. Using a memoized selector to sort (sortPlayerMatches.js in the selectors folder). Also changed the reducer (/gotPlayer/matches.js) to have some sorting state which is used by the selector to sort the table

looks okay to me.  ready to merge?  anyone else want to review?

I'm going to refactoring the table component to be more componentized as right now it's sort of a monolith. Once I push that and it passes review we can merge


[suggestion] naked roll

Hello there Ethck! Many thanks for your great module, I just wanted to request something, do you think it would be possible to roll a naked d20?

Greetings! A naked roll is certainly possible, but I'm struggling with where to put it. I can't exactly just throw it into the existing categories, but I'm also not sure if it deserves it's own roll. Any suggestions? Currently I'm thinking of adding a row titled "Special" and include a couple of other types of rolls in there (perhaps like hit die?), but I'm not sure what all to include.


Add data-table to list of available custom modules

data-table component is not available in custom module list. This PR adds it.

Thanks


Add types for dispatch prop

This PR adds types for the dispatch prop. This includes a standard action dispatch and a thunkful action dispatch variant.
Inspired by: https://github.com/reduxjs/react-redux/blob/master/src/types.ts

Coverage remained the same at 100.0% when pulling ad568e0bc8be5c3baad9e084516e9d66a7e887e6 on jkelaty-rbx:action-thunk-prop-types into 60ce019cc53a78b1917c1cc4880879e6a3d0c34c on Roblox:master.

I think this mostly looks good, but I can see that one of your previous analysis "failures" still got marked as green:  Can we introduce an analyze error in a commit, validate that CI fails, and the revert it before merge? I've had odd behaviors with tools exiting with an error and still passing CI steps, so I'm perhaps a bit paranoid 😅

Yeah, I'm guessing (likely mistakingly) luau-lsp doesn't factor a missing directory for its exit code. My test commit successfully failed CI, so we should be good!

@ZoteTheMighty Thanks for the quick review! Feel free to merge whenever

Looking good, but I'm curious: Are these types enough to catch bugs?

@matthargett  This is a great question. These types might catch bugs where we try to pass something other than an action or a thunk into dispatch, but their main utility is unfortunately to work around some of Luau's constraints. The issue that I ran into was when I was dispatching non-homogenous types within the same dispatch scope. Luau would try to narrow the dispatch arg on the first invocation and then complain about subsequent calls, thus type checking fails.
However, I just did some quick testing to verify what I said, and I stumbled onto another issue with void returning thunks that I will need to follow up on, so we should put this PR on pause until then anyway.


fix: Remix IDE imports for guides

It turns out changing the @openzeppelin/contracts version to v4.9.5 works just fine. Updated the imports for both API3 Ecosystem repo and contracts within the guides.
Closes #693.

What about these other guides that have Ownable?
* https://docs.api3.org/guides/dapis/index.html#how-to-use-dapis-in-a-smart-contract

* https://docs.api3.org/guides/dapis/funding-multiple-dapis-gelato/index.html

* https://docs.api3.org/guides/qrng/quantumon/index.html#_1-defining-the-imports

So these contracts were not included in the api3-ecosystem/remix-contracts repo. I just added them with their updated imports. This way it would make it easier to update and manage contracts for these types of guides in the future.


Windows compat after recent changes

Fixes str vs bytes with subprocess and re as well as symlinks.  Regression for
direct command line test (skip it).  Drop Python 3.3 and 3.4 from AppVeyor CI.
refs #28

The AppVeyor builds work on 3.5 and 3.6, for 2.7 the symlink loop test fails.  IMHO, this is still an improvement for the situation on Windows, even without full version coverage.
WDYT?

Looks good for now — thanks!

What's the link to the Appveyor project, by the way?

The URL I am using is https://ci.appveyor.com/project/fleimgruber/uncommitted.

Thanks! I'll know to refer to it when questions about Windows come up in the future.

Feel free to ping me as well in that case and in case I miss it, happy to chime in!


Failed when installing API

Hello,
I'm trying to install the API, but got an error and not conclude it:
$ composer require kunalvarma05/dropbox-php-sdk
Using version ^0.1.5 for kunalvarma05/dropbox-php-sdk
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)

Installing kunalvarma05/dropbox-php-sdk (v0.1.5)
Loading from cache

Writing lock file
Generating autoload files

Illuminate\Foundation\ComposerScripts::postUpdate
php artisan optimize

[BadMethodCallException]
**  Method accessible does not exist.
Script php artisan optimize handling the post-update-cmd event returned with error code 1
Installation failed, reverting ./composer.json to its original content.**
After this, my composer broke and I should restore everything to can work again.
Can you help me? What's wrong?

@matheusmaximo Can you share some more info/output regarding the error you got?
However, I'll test it with Laravel.

@matheusmaximo The installer seems to be working fine. I tried it on a fresh installation of laravel 5.3. Works smoothly.
$ composer require kunalvarma05/dropbox-php-sdk
Using version ^0.1.5 for kunalvarma05/dropbox-php-sdk
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
    Finished: success: 0, skipped: 0, failure: 3, total: 3
  - Installing guzzlehttp/promises (v1.3.1)
    Downloading: 100%

  - Installing psr/http-message (1.0.1)
    Loading from cache

  - Installing guzzlehttp/psr7 (1.3.1)
    Loading from cache

  - Installing guzzlehttp/guzzle (6.2.2)
    Downloading: 100%

  - Installing kunalvarma05/dropbox-php-sdk (v0.1.5)
    Downloading: 100%

Writing lock file
Generating autoload files
> Illuminate\Foundation\ComposerScripts::postUpdate
> php artisan optimize
Generating optimized class loader
The compiled class file has been removed.

Doesn't seems to be a problem with the package.
However, can you clear the composer cache and give it a try?
Thanks.

@matheusmaximo I had the same issue on Laravel 4.2 so I assume you are using an older version of laravel.  I had to work my way around the tightenco/collect library using a zip install because that required library was the problem.  The tightenco/collect ends up overloading part of the Illuminate core which then breaks a lot of stuff due to changes in later versions of the core framework .  It appears it should be fine in  Laravel > 5.2 but I have not tested it until we migrate off of 4.2 and slowly work that direction.


Enable secrets encryption

https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/

Should we make it encrypted by default? If we do, should we at this point also make automatic move from un-uncrypted secrets, a.k.a migration?
How about the key(s)? How should we take those in? Having them in cluster.yml might leak them easily. I see two options:
a) provide them as options/envs to  up command
b) generate them on the fly and dump out after cluster setup with a note that these are supposed to be kept somewhere safe. :)

Encryption should be enabled by default (is there any reason not to encrypt?).
Option b) sounds good to me.

is there any reason not to encrypt?

Not really, just wanted to double check we don't want to have that configurable :)

Not really, just wanted to double check we don't want to have that configurable :)

I might change my mind after I see the first implementation 😄


Introduce /itchysats/order protocol

The key test taker_takes_order_and_maker_accepts_and_contract_setup passes. Adapting the rest of the actor tests should be trivial.

I am not sold at all on using an internal channel over handling the decision at the actor level on the maker. The current design was motivated by the possibility of testing the protocol in isolation, but it's basically impossible given all the coupling with actors in
daemon.

The file taker_cfd.rs is not very clean. Conversely, maker_cfd.rs gets more complicated because we have to support the
legacy connection for a while longer. The logic there is to first try to accept/reject using the new protocol and if it fails attempt it
over the legacy connection.

You can see that the new design follows the proposal in https://github.com/itchysats/itchysats/issues/1770. This means that
the taker now generates an OrderId when placing the order. We currently reuse the same type for the offer (legacy) and the taker's order, which is a bit confusing (but hard to avoid, because our model wants an OrderId). With the new protocol the taker ignores the OrderId associated with the offer, but we have to keep it around for legacy connections.

I assumed we were trying to first migrate our network stack, and only then change the protocols if possible (as we agreed). If we change two things at the same time, we risk much longer debugging time and misattributing the problems to the network stack, not the protocol changes - we have seen that so far in other protocols that were migrated and changed along the way.
As it is fundamentally easier to iterate on a protocol with libp2p, I'll see to rework this changeset to just move the network stack.

I assumed we were trying to first migrate our network stack, and only then change the protocols if possible (as we agreed). If we change two things at the same time, we risk much longer debugging time and misattributing the problems to the network stack, not the protocol changes - we have seen that so far in other protocols that were migrated and changed along the way.
As it is fundamentally easier to iterate on a protocol with libp2p, I'll see to rework this changeset to just move the network stack.

I tried to only do contract setup over the new network layer, but I could not come up with anything acceptable. That's why I went down this route. Feel free to give it a go though!

fair enough! I suspected there might be some blocker :) I'll timebox it, in the worst case, I'll just move forward with this one as a fallback!

Closing in favour of #2292 (which is heavily based on this PR).


⚠ Bofrost.lu has degraded performance

In 4f0eae8, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2408 ms

Resolved: Bofrost.lu performance has improved in aa344ef after 6 minutes.


LibWeb/CSS: Treat counters() function with 1 argument as invalid

Fixes #887.

Couldn't the size check just be changed to size() == 2 ?

No, size of 3 is also valid.


Added detailed scaling

Added Transform.scaleXY constructor to adjust the scale by Offset
Description
Transform.scale constructor allows scaling by multiplying x and y with one value. I added Transform.scaleXY constructor to gain more control over scaling.

@googlebot I signed it!

This PR is also missing tests and the analyzer is complaining about it.
Also: When opening a PR please fill out the full template that's shown in the PR description.

@goderbauer  as my first pr, I have no idea how to do test and deal with analyzer.

I am going to close this PR for now. Please feel free to re-open when you can address the open comments.


create multiple thumbnail sizes

hi
i'm using laravel-filemanager:~1.8
how i can create multiple thumbnail sizes of uploaded image ?

This can be accomplished by creating a custom event listener, which listens to FileWasUploaded event, and create additional thumbnails there.


Option to emit string union instead of enum

In emitEnum on line 310, we'd like this to output string union instead of enum type. Is there an option which supports this?
Could we create a pr to update this behavior?
Thanks in advance!
cc @schani, @mamantoha , @jnpdx , @uhop , @proppy

Nobody.

@daniel-ro-github
I think it isn't not recommended to create a commit with a suggested feature

In emitEnum on line 310, we'd like this to output string union instead of enum type. Is there an option which supports this?

No, string union type for typescript enum structure isn't supported

Could we create a pr to update this behavior?

Yeah, you can create code and PR with implemented behavior you want, that will be tested by CI inicially

@clystian

No, string union type for typescript enum structure isn't supported

But why? It is possible, I'm using a workaround to get them even inline. Inline enums look much more better. Always wanted to have this!: https://github.com/zardoy/vscode-framework/blob/3ac2146c53831fccfe20f9f6f7a85c2e17153d96/integration-tests/fixture-snapshots/vscode-gitlens/src-generated-bare.ts#L464-L468
btw I'm surprised how well my workaround works.

#1824 1789

Great idea! Please try to implement it but this PR only contains comments.


Handle .docx, .xlsx, and .pptx with extra magic

The freedesktop magic doesn't work for the Office 2007+ files, it
detects them all as application/zip. I have magic which detects them,
but it requires looking at 2,000 byte ranges, too much for their
project (which has to support things like file browsers). Since you
already warn that by_magic is slow, it'd be nice to support it here
at least.
This would allow the paperclip project to use mimemagic and stop
relying on the file binary:

https://github.com/thoughtbot/paperclip/issues/1530#issuecomment-43375497

Support is enabled through an overlay, required with
require 'mimemagic/overlay'

Documentation is in the README

@minad new PR for your suggestions in #19.

thx! are you fine if we drop 1.8.7 support?

@minad definitely fine with not supporting 1.8.7. I don't use that version personally, and the paperclip project doesn't support it.

ok, dropped it :)


Update dependency: image_picker and file_picker_pro

Hi,
When i try install "flutter pub add file_picker_pro", i got this message:
Because file_picker_pro >=1.3.0 <1.4.0 depends on image_picker ^0.8.7+5 and file_picker_pro <1.3.0 depends on image_picker ^0.8.7+3, file_picker_pro <1.4.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.4.0 <1.5.0 depends on image_picker ^0.8.9, file_picker_pro <1.5.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.5.0 depends on file_picker ^5.3.3 and XXXXXXX depends on file_picker ^6.1.1, every version of file_picker_pro requires image_picker ^0.8.7+3.
So,
I can't install file_picker_pro, because my project use "image_picker: ^1.0.7" and "  file_picker: ^6.1.1"
Could you please update
Could you, please , update the "image_picker: ^1.0.7" and "  file_picker: ^6.1.1" dependencies?
Thanks in advance

okay, I will try to update
On Sat, Feb 10, 2024 at 4:13 AM VersaDesenvolvimento <
@.***> wrote:

Hi,
When i try install "flutter pub add file_picker_pro", i got this message:
Because file_picker_pro >=1.3.0 <1.4.0 depends on image_picker ^0.8.7+5
and file_picker_pro <1.3.0 depends on image_picker ^0.8.7+3,
file_picker_pro <1.4.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.4.0 <1.5.0 depends on image_picker ^0.8.9,
file_picker_pro <1.5.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.5.0 depends on file_picker ^5.3.3 and
XXXXXXX depends on file_picker ^6.1.1, every version of file_picker_pro
requires image_picker ^0.8.7+3.
So,
I can't install file_picker_pro, because my project use "image_picker:
^1.0.7" and " file_picker: ^6.1.1"
Could you please update
Could you, please , update the "image_picker: ^1.0.7" and " file_picker:
^6.1.1" dependencies?
Thanks in advance
—
Reply to this email directly, view it on GitHub
https://github.com/datadirr/file_picker_pro/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7DEBUW7AAJTBIKODRM2N7TYS2RBRAVCNFSM6AAAAABDCFR7VSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDOOJUGI4TQOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

file_picker_pro: ^1.6.0
Okay done, now use this version
On Wed, Feb 14, 2024 at 10:12 AM datadirr datadirr @.***>
wrote:

okay, I will try to update
On Sat, Feb 10, 2024 at 4:13 AM VersaDesenvolvimento <
@.***> wrote:

Hi,
When i try install "flutter pub add file_picker_pro", i got this message:
Because file_picker_pro >=1.3.0 <1.4.0 depends on image_picker ^0.8.7+5
and file_picker_pro <1.3.0 depends on image_picker ^0.8.7+3,
file_picker_pro <1.4.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.4.0 <1.5.0 depends on image_picker
^0.8.9, file_picker_pro <1.5.0 requires image_picker ^0.8.7+3.
And because file_picker_pro >=1.5.0 depends on file_picker ^5.3.3 and
XXXXXXX depends on file_picker ^6.1.1, every version of file_picker_pro
requires image_picker ^0.8.7+3.
So,
I can't install file_picker_pro, because my project use "image_picker:
^1.0.7" and " file_picker: ^6.1.1"
Could you please update
Could you, please , update the "image_picker: ^1.0.7" and " file_picker:
^6.1.1" dependencies?
Thanks in advance
—
Reply to this email directly, view it on GitHub
https://github.com/datadirr/file_picker_pro/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7DEBUW7AAJTBIKODRM2N7TYS2RBRAVCNFSM6AAAAABDCFR7VSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDOOJUGI4TQOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Update util.go

Fixed domain with non unicode symbols

I will happily accept this but fix the Travis test first 👍 I can take a look at it later on.

Probably just add go get golang.org/x/net/idna line (as first line) under install section in travis yaml file