text:
[Bug]: fresh install login issue

What happened?
Based on the instructions in the documentation I have started Featbit via docker-compose on MacOS. I had to change the port for API from 5000 to 5001, cause on MacOS port 5000 is taken by AirPlay.
All containers start without a problem, but I am not able to log in to the UI with the default credentials that are in the documentation.
In the console, I am getting the CORS error which I think is the cause of the problem.
Any ideas are more than welcome.

To Reproduce

git clone https://github.com/featbit/featbit
cd featbit
Updated API port from 5000 to 5001 in docker-compose.yml
docker-compose up -d

Expected behavior
Successfully login to the UI
Additional context
I checked the issues and followed the recommendation from this one https://github.com/featbit/featbit/issues/608 to manually initialize MongoDB. But the CORS error persisted.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @myskamartin, can you try

curl http://localhost:5001/health/liveness to make sure the api service is started successfully
check the api service logs, any exceptions?

And to figure out why the preflight request fails, try the following command in bash:
curl -v 'http://localhost:5001/api/v1/user/has-multiple-workspaces' \
  -X 'OPTIONS' \
  -H 'Access-Control-Request-Headers: authorization,content-type,organization,workspace' \
  -H 'Access-Control-Request-Method: POST' \
  -H 'Origin: http://localhost:8081'

Hi @deleteLater, and thanks for your reply.
The API server has started successfully:
[root@ip-10-98-170-245 ~]# curl  http://localhost:5000/health/liveness
Healthy

I don't see any exception in the API logs that would raise my attention, everything looks in order.
But checking why the preflight request fails reveals the 204 No Content (full output below)
[root@ip-10-98-170-245 featbit]# curl -v 'http://localhost:5000/api/v1/user/has-multiple-workspaces' \
> -X 'OPTIONS' \
> -H 'Access-Control-Request-Headers: authorization,content-type,organization,workspace' \
> -H 'Access-Control-Request-Method: POST' \
> -H 'Origin: http://localhost:8081'
*   Trying 127.0.0.1:5000...
* Connected to localhost (127.0.0.1) port 5000> OPTIONS /api/v1/user/has-multiple-workspaces HTTP/1.1
> Host: localhost:5000
> User-Agent: curl/8.3.0
> Accept: */*
> Access-Control-Request-Headers: authorization,content-type,organization,workspace
> Access-Control-Request-Method: POST
> Origin: http://localhost:8081>
< HTTP/1.1 204 No Content
< Date: Fri, 29 Mar 2024 22:04:08 GMT
< Server: Kestrel
< Access-Control-Allow-Headers: authorization,content-type,organization,workspace
< Access-Control-Allow-Methods: POST
< Access-Control-Allow-Origin: *
<
* Connection #0 to host localhost left intact

Any further help is much appreciated.
FYI:  I have started a new installation on Amazon Linux 2023 instance, thus I am no longer using port 5001

Try running the following script in mongodb and see what happens?
https://github.com/featbit/featbit/blob/main/infra/mongodb/docker-entrypoint-initdb.d/init.js

Hi @cosmic-flood,
Running the script will seed the database, but the issue remains and I don't see exceptions in the logs either.

The preflight request returns 204 indicating that there is no CORS issue. Our Api service has request logging enabled by default, so if you refresh your browser, you'll see a browser request log like this one. Can you see these logs?

No, I don't see that in the logs at all.
I am a little bit confused. Given the docker-compose configuration and that I can reach the API container from the UI container, what else do I need to do to reach the API service?
Again, I am not changing the configuration at all to be clear on this one.

Ok, so the question is why requests sent from the browser are not reaching the API service. To be clear, the request was sent from the browser, not the UI service, so you need to make sure that you can access the API service from the machine that is accessing the UI.

Close this issue as there is no further information. Feel free to reopen it if you have any questions. @myskamartin

found it. run this command in the mongo container:
mongosh -u admin -p password < init.js

authors: cosmic-flood ddenev deleteLater myskamartin

repo: featbit/featbit


text:
✨ feat: rollout with custom key

allow user to set the key uppon which to dispatch end users
the default key is keyId

We need to sync this change to our server-side sdks before merge it @cosmos-explorer @dsun0720

source: gharchive/pull-request

authors: cosmos-explorer deleteLater

license: MIT

license_type: permissive

license_source: github-api


text:
[Bug] PreventChanges hook prevents only last defined field

In case of using the preventChanges hook without wanting to throw an error, then it will only remove the last defined field from the context.data.
Example
context.data => {id: '1234', email: 'test@test.com', username: 'testuser'}
preventChanges(false, 'id', 'email')
Actual result:
context.data => {id: '1234', username: 'testuser'}
Expected result:
context.data => {username: 'testuser'}
Root issue
The data variable on line 25 is never changed and on line 33 it is always used to bring context.data to the origin state except the field of the current loop. Therefore, just the field of the last loop is removed from the context.data.
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
"@feathersjs/feathers": "^4.5.15",
"feathers-hooks-common": "^6.1.3",
"lodash": "^4.17.21",
"typescript": "^4.7.4",
NodeJS version:
Node 16

I just saw the "Report a bug" doc and there stands that we need to create issues in the Issue-Tracker of feathersjs/feathers repository. Therefore, I have included it there: https://github.com/feathersjs/feathers/issues/2692

source: gharchive/issue


text:
$joinRelation doesn't work within $or queries

The join relation in the following query is ignored. I'd assume that the same is true for $and.
{
  $or:[
    { $joinRelation: 'child(exists)' },
    { success: true }
  ]
}

What is the raw SQL query that you're trying to run using $or & $joinRelation?
$joinRelation should be used with $eager and only in the query object's root level and without conditioning.

something like:
select * from parent join child on child.parent = parent.id where parent.success or child.id is not null```

It should be possible. Maybe something like this?
query: {
$eager: 'child(exists)',
$joinRelation: 'child(exists)',
$or: {
$not: {
id: null
},
success: true
}
}
בתאריך יום ד׳, 16 באוק׳ 2019, 6:00, מאת RJ Ewing <notifications@github.com

:

something like:
select * from parent join child on child.parent = parent.id where parent.success or child.id is not null```
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/feathersjs-ecosystem/feathers-objection/issues/68?email_source=notifications&email_token=ABB5E3JJAIGQX6QZQA4HGG3QO4GAXA5CNFSM4JBAQTVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBMMKQI#issuecomment-542688577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABB5E3PMB6TNRCQSMK46IS3QO4GAXANCNFSM4JBAQTVA
.

authors: dekelev ewingrj

repo: feathersjs-ecosystem/feathers-objection


text:
added react+typescript chat example & reorganized the examples

Thanks for the great work on Feathers!
I added a TypeScript version of the Feathers Chat React example from my repository.
And requested by no one, but I thought it would be helpful to organize the list of examples as it's pretty long now. If this an unwanted change, but you would like to include the TS React example, I can submit another PR with just it added to the list.

Awesome, thank you for organizing too. Looks much better this way!

authors: codyparker daffl

repo: feathersjs/awesome-feathersjs


text:
Errors when running generate

TLDR - Changing env.lookup() to env.register(require.resolve('generator-feathers')) in generate.js seemed to fix this for me. I do not know enough about yeoman to know if this is machine specific or not. Hopefully this helps.
When running any command (generate shown below) I receive the following:
514 ajones:sandbox$feathers generate
feathers$

events.js:154
      throw er; // Unhandled 'error' event
      ^

Error: You don't seem to have a generator with the name feathers:app installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 0 registered generators run yo with the `--help` option.
    at Environment.create (/Users/ajones/git/forks/feathers-cli/node_modules/yeoman-environment/lib/environment.js:296:7)
    at Environment.run (/Users/ajones/git/forks/feathers-cli/node_modules/yeoman-environment/lib/environment.js:364:24)
    at CommandInstance.<anonymous> (/Users/ajones/git/forks/feathers-cli/lib/commands/generate.js:10:9)
    at EventEmitter.session.execCommandSet (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/session.js:470:20)
    at EventEmitter.vorpal._exec (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/vorpal.js:956:18)
    at EventEmitter.vorpal._execQueueItem (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/vorpal.js:747:17)
    at EventEmitter.vorpal._queueHandler (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/vorpal.js:731:10)
    at EventEmitter.vorpal.exec (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/vorpal.js:678:10)
    at EventEmitter.Vorpal.parse (/Users/ajones/git/forks/feathers-cli/node_modules/vorpal/dist/vorpal.js:163:12)
    at exports.default (/Users/ajones/git/forks/feathers-cli/lib/index.js:14:40)

running yo --help shows that I do have them.
Available Generators:

  feathers
    hook
    middleware
    model
    service

@thejones it's weird, I found the opposite on my machine. When I use env.register on its own, I only get the feathers:app yeoman generator namespace, so I've left the call to env.lookup() in there after it in the PR above.
Would you mind pulling the fix/2 branch and running npm test?
Thanks

authors: derek-watson thejones

repo: feathersjs/feathers-cli

license: mit

license_source: bigquery


text:
Make text searches case insensitive

Don't think there's any good reason to preserve case sensitivity.
Should be easy to implement -- just convert inputs to lowercase, and convert everything you search over at any given moment to lowercase. (I guess we should preserve the case of the taxa listed in the rank file/in the BIOM table, but that is going to make us consistently re-lowercase stuff which will lead to a slight performance decrease.)
idea c/o Lisa

This will require us being able to map feature IDs to their lowercased versions, and then back. Either that or we'll have to literally re-lowercase every feature we're searching against every time we do a search? I think I want to hold off on doing this until more tests re: plot updating have been added, so that it'll be easier to see if the changes I make along the way break everything.

repo: fedarko/rankratioviz


text:
Lightning Gateway backupability

Do we have a common seed for all the clients in the gateway and can we export it/recover from it? If not we should.

dev call: @joschisan reports that every client different seeds. Also, we use 64 bytes which can't be represented as BIP39 seed words.

sounds related: https://github.com/fedimint/fedimint/issues/4170

Also related to https://github.com/fedimint/fedimint/issues/2652. These 3 could probably be one issue.

Working this rn with @m1sterc001guy , moving to bip39 mnemonic and reusing all dpc's fanciness in the fedimint-client with a manual migration: gateway operator moves their ecash out, leaves the federation, rejoins with the automatically created new client derived from the mnemonic

If you do a manual migration you can also move all dbs into one via prefixes.

If you do a manual migration you can also move all client dbs into one via prefixes.

Yep, had the same idea, this is the plan.

authors: Kodylow elsirion joschisan justinmoon kernelkind m1sterc001guy

repo: fedimint/fedimint


text:
🛑 무리 네트워크 is down

In 8393329, 무리 네트워크 (https://muri.network/api/v1/instance/activity) was down:

HTTP code: 403
Response time: 636 ms

Resolved: 무리 네트워크 is back up in 63b3ddf after 15 minutes.

repo: fediverses-kr/upptime-api


text:
nspawn backend followup

Thanks @jscotka for working on this!
Let's create a list of follow-up items:

[ ] update documentation: we should make it clear that conu now supports more than one backend

[ ] an example, or even a simple article/page on documentation with a real example

[ ] marketing: when doing a new release, make it clear that conu now supports two backends
[ ] investigate usage of nsenter to perform exec functionality
[ ] @TomasTomecek to try the code!

@dhodovsk please add more

[ ] Update tests - Create one test suite that runs against all back-ends e.g by moving some docker tests to a more generic place
[ ] Decide and update name of method for container run (run_via_binary vs. run)

maybe one more

[ ] create  issues based on TODO comments or remove them from code if not necessary

authors: TomasTomecek dhodovsk jscotka

repo: fedora-modularity/conu


text:
File System search using Spotter on Windows is broken.

Debug messages appear in the Spotter window when opening Spotter in the FIle System tool on Windows.  No search is possible.

Thanks

It will be integrated in the release after v0.8.2625

authors: carllemp girba

repo: feenkcom/gtoolkit


text:
Restrict NSFW commands to NSFW channels

Please add a function that checks if the Discord channel is an NSFW channel or not.

Thanks for reminding me I'll add it as soon as possible!

Everything has been added now! Check out the README for more information.


text:
支持数据库一键导入导出（先不考虑网页端）

考虑先用nb脚本实现(

#208

所以这里为什么不直接把db_data_seq传进来呢

这样只要这个函数传进来的是Sequence[Subscribe]都能处理，为以后可以选择只需要导出某些用户做铺垫（？

所以这里为什么不直接把db_data_seq传进来呢

这样只要这个函数传进来的是Sequence[Subscribe]都能处理，为以后可以选择只需要导出某些用户做铺垫（？

async def subscribe_export(func):
    data = await func()
    ...

await subscribe_export(load_data)

和
data = await load_data()
await subscribe_export(data)

在功能上是等效的，为什么不写成下面的方式呢


text:
Deployment stuck on 'Setting up source control'

I tried to deploy a blog on Azure but the process seems to be stuck on 'Setting up Source Control'. Am I doing something wrong?

@ch-hristov did you ever figure this out? I am trying to do this now and seeing the same...

Same. Just had to wait a while.

authors: cbartonnh ch-hristov

repo: felixrieseberg/Ghost-Azure


text:
Enhancement request: independet starttype / endtype

Thanks a lot for this great node.
It would be great for my application if I can configure the node to use a fixed time for the start and "sunset" for the end of the timer.
For example: I want to open a blind at 6:30 and close it at sunset.
An additional bonus feature could be to add something like:

starttype is sunrise (+/- offset) but not later than / before 6:30
endtype is sunset (+/- offset) but not later than / before 20:00

Hi Peter,
I am currently not allowing mixed time frames because validation is almost impossible. Say, the user sets a timer that statically starts at 06:30 and ends at sunrise (07:00 as of today). Validation would say ok it runs 30 minutes - save. A few weeks later sunrise might happens before the statically configured start time and you would end up having a timer that runs from 06:30 to 06:25 or so.
There is another mode - the event mode - in event mode you can create an event that does a certain thing at a specific time independently of other events. That would make your blind scenario possible -> Event1: 06:30 open blinds, Event2: sunset close blinds.
Please let me know if this helps!

Hi Fellinga,
thanks a lot for your quick reply and your explanation.
And yes, in event mode I was able to create the necessary scenario.

Solving the problem with the event node is messy. If - to give another example - light on at 6:00 am and off after sunrise. If now the sunrise is BEFORE 6:00 the light should not turn on at all. In the case of the proposed event mode, the light would turn on at 6:00 but not off again (only the next day after sunrise and then immediately on again when 6:00 is reached).
The check could simply ignore the event in case of negative time differences/running times.
Best regards
Hubertus

FYI: It's now possible to mix start and end time but without any check when they overlap.

authors: HubertusH PeterAustria fellinga


text:
validating checksums

This is a pull to implement #46, validating assorted checksums are all hexadecimal digits, and of suitable length.

Good point.  The bug report was for the checksum being too short, and somehow that stuck in my head...

repo: fermitools/metacat


text:
Adding new common area for shared resources

Signed-off-by: tpmccallum tim.mccallum@fermyon.com
Adding new common folder and templates to house resources/pages which are intended to be used across two or more project templates.

The failing CI is normal because the broken URLs are files in this PR (that don't exist yet; but will as soon as this PR is merged)

Thanks @vdice for the approval.
Also huge thanks to @karthik2804 for pacing through all of the other alternatives (which did not turn out in the end i.e. symlinks in GitHub and so forth). A bit of trial and error got us there in the end :)

repo: fermyon/developer


text:
[cli] Spin CLI should print a warning when outdated

The Spin CLI should warn the user when it's outdated and a new release is available.
This would smoothen the experience, especially for developers that use Spin only occasionally.
Considerations

I'm not sure if GitHub enforced rate limiting when asking for the latest release endpoint (https://api.github.com/repos/{owner}/{repo}/releases/latest)

I think there is a rate limit.
A simple way to do this would be a Spin application deployed somewhere that returns a metadata object with the latest release.

This is addressed using the check-for-update plugin now. Alternatively, users can rely on package managers (currently brew is supported) to stay current with their local spin installation

authors: ThorstenHans radu-matei

repo: fermyon/spin


text:
Something is terribly broken with multi-file torrents.

Apart from the bugs I've listed previously, one of my torrent is shown as downloading at 236 MB/s while being at 100%. This happened when I just opened WT and it starting rehashing a incomplete torrent.

Can second this. Files mark as 100% when they definitely aren't.

@ethaniel Please don't post about copyright infringement, we can't help if it's clear that you're using WebTorrent for infringement.

authors: alexisvincent ethaniel feross

repo: feross/webtorrent-desktop


text:
How to launch external media player to play torrent stream?

Is it possible to play the torrent file in an external media player as it is being streamed? How?
var WebTorrent = require('webtorrent')

var client = new WebTorrent()
var magnetUri = '...'

client.add(magnetUri, function (torrent) {
  torrent.files.forEach(function (file) {
       // play file with vlc or mpc-hc
  })
})

Thanks

You can use the command line version for that. https://github.com/feross/webtorrent#as-a-command-line-app

That won't do, unless it is possible to use command line args from inside a node js module?

Why not? If I may ask. And no, at least not for webtorrent.

On Nov 1, 2015, at 4:05 PM, tsoernes notifications@github.com wrote:
That won't do, unless it is possible to use command line args from inside a node js module?
—
Reply to this email directly or view it on GitHub.

I get the magnet link from a web scraper written in nodejs

You can use the torrent.createServer function to create an HTTP server that serves the torrent's contents.
https://github.com/feross/webtorrent#torrentcreateserveropts

Have you looked at https://github.com/mafintosh/playback ? It has WT support

@gillesdemey Thanks, just what I needed.
@DiegoRBaquero Looks cool but it does not support the formats/codecs I need to play
Solved

Awesome – glad your issue was solved.
Thanks @gillesdemey and @DiegoRBaquero!

authors: DiegoRBaquero feross gillesdemey tsoernes

repo: feross/webtorrent


text:
quick setup from flannel to weavenet not working

There are some flannel networking configurations that are not cleared up, during quick provisioning, such as:
#ip addr
10: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN
    link/ether 7a:75:cb:c2:21:66 brd ff:ff:ff:ff:ff:ff
    inet 10.244.0.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::7875:cbff:fec2:2166/64 scope link
       valid_lft forever preferred_lft forever

when moving from calico to flannel we receive this error:
kubectl logs --namespace kube-system kube-flannel-ds-amd64-2d6fz Could not find valid interface matching enp0s8: error looking up interface enp0s8: route ip+net: no such network interface

repo: ferrarimarco/kubernetes-playground


text:
server文件接收服务端地址问题

请问一个文件需要对应一个server地址该如何处理，比如我应用到百度BOS上
PUT /v{version}/bucket/object

已解决

你是如何解决的，可以告知一下吗？

@wjmeverlasting 动态修改server配置项，类似uploader.server = '';这样

repo: fex-team/webuploader


text:
修改异常提示信息

上传文件过大或者其他异常出现时，如何修改弹出框的错误提示信息。

同款疑问！


text:
request.getParameterMap();发现得到的值是{}

request.getParameterMap();发现得到的值是{}

我的也是后端无法拿到前端发送的参数，
前端参数定义<==>formData : { subId : "e1f48d3297c44645867b4a1d07032d50" }，
后端参数获取<==>String subId = request.getParameter("subId")，
结果取出来的值为null。
后端到底应该怎么取参数？


text:
Azure staging certificate isolation

Modified the Azure certificate persistence strategy to separate out certificates generated using the Lets Encrypt Staging API from the Production API to ease testing/switching between the two.

Hmmm. Can you elaborate a bit on this? What's with the -Staging prefix - is that something that Microsoft makes on certificates issued via their managed service? Or?

Sure. So if you set UseStaging to true in LetsEncryptOptions, it will talk to the Staging API. This generates a certificate that is signed by a 'fake' Certificate Authority, so is as valid as a self-signed certificate, and is only useful for testing purposes. However, the library cannot currently distinguish between a certificate generated in this way, or a valid certificate generated by the Production API of LE. So when it searches for an existing certificate before ordering/binding a new one, it can't tell if the certificate is correct for the current value of UseStaging. If you have been working with staging, then switch to production, you'd have to manually unbind the certificate and ensure that it is completely deleted from Azure in order for a new production certificate to be requested, generated and bound - otherwise you'd be stuck using the staging certificate. This PR enables that distinction.

authors: ffMathy killswtch


text:
missing exit option in Small but Perfect Menu

not an issue, but it would be appreciated

Should be fixed now.

Thank you.
Also, I thank you really much for your effort porting this game.

authors: Mr-Poyetas fgsfdsfgs


text:
The Chrome Extension link doesn't work

Hi there,
The url https://chrome.google.com/webstore/detail/github1s/lodjfmkfbfkpdhnhkcdcoonghhghbkhe in readme doesn't work:

https://github.com/fhefh2015/GitHub1s_chrome_extension/blob/0bc209ff35062113027f3957188517d0967d7c14/README.md?plain=1#L19

Hi.
Any Progress?


text:
file-resource custom path does't seem to work

I am trying to add file to the fw bundle using the file-resource option in my fwup.conf file, like so:
file-resource "/release.html" {
    host-path = "${NERVES_ROOT}/../_images/release.html"
}

Then when the firmware bundle is made I get
chris@chrisdev:~/projects/ng1a$ ls _images/fw/
data  meta.conf
chris@chrisdev:~/projects/ng1a$ ls _images/fw/data/
MLO  release.html  rootfs.ext2  u-boot.img  uEnv.txt

From the documentation it seems like this should end up in the root of the bundle.

I'm surprised that doesn't work as well. See test 2:
https://github.com/fhunleth/fwup/blob/master/tests/002_resource_subdir.test
My guess is that you're not using the latest version of fwup. I've been slow to update nerves with the latest, since I haven't used it as much, but I have no reason to believe that it wouldn't work. Sorry - really busy with non-Nerves work. :(

nerves compiled fwup reports version 0.2.0

Yep. That feature is in 0.3.0. I added that along with several other things - most notably firmware signatures. If I weren't so busy with work, I'd update nerves, but I'm just swamped at the moment. The new fwup requires libsodium for the signatures. For whatever reason, my libsodium patch is taking the slow road to be included in buildroot. Here's the patch so that you can manually add it, though: https://patchwork.ozlabs.org/patch/473879/.
Alternately, if you can handle not putting files in the root directory of the archive for a while, that might be the easiest route.

Ok well I really just need the portion of fwup that rewrites the master boot record. So maybe I will look at how to just use that portion....

Closing this issue since support for resources outside of the /data directory was added in 0.3.0.

authors: CaptChrisD fhunleth

repo: fhunleth/fwup


text:
toggle button

A toggle button like the vvvv one could be a 1.0 dflow feature that let have a boolean that can be set on the fly by users.
It requires flow-view to be extended with custom nodes.

Could be created just typing t in the editor.

After one year I started implementing it, and without reading this issue I remembered to create it just typing t in the editor. Well I did not remember it, I am just thinking always in the same way :)
Anyway, the toggle is almost here and it is the first custom node.

repo: fibo/dflow


text:
Fix maxMessageSize validation in StandardMessageDispatcher

maxDeviceMessageSize field accepts random integer values, should only accept 0 or the minimum packet size(300) bytes

closing this and deferring .

authors: KiranSukhavasi adarshan-intel

repo: fido-device-onboard/pri-fidoiot


text:
Parachute click is off

When using TinyClicker, the parachute clicking mechanism is irregular and sometimes does not click the parachute correctly.
https://user-images.githubusercontent.com/70725766/203849363-cfc80e58-ee4c-4484-adc6-94fcb7d687bf.mp4
As you can see in the video, the tap (little grey dot) is always in the top right of the parachute and fails to tap it correctly.
This becomes a major problem when the parachute is above the build floor button and the clicker taps on the build floor button and freezes up.

Attempted to fix the issue in the latest release, should work now correctly

repo: filadog/TinyClicker


text:
Using closure on Table column action does not work

Package
filament/filament
Package Version
v3.2.43
Laravel Version
v10.46
Livewire Version
v3
PHP Version
PHP 8.2
Problem description
This works (shows confirmation):
Tables\Columns\TextColumn::make('name')
    ->action(Tables\Actions\Action::make('test')->requiresConfirmation()),

This does not:
Tables\Columns\TextColumn::make('name')
    ->action(fn () => Tables\Actions\Action::make('test')->requiresConfirmation()),

Expected behavior
Using a closure to, for example, decide the action to trigger, should work.
Steps to reproduce
See problem description.
Add a column with a closure as the ->action() parameter:
Tables\Columns\TextColumn::make('name')
    ->action(fn () => Tables\Actions\Action::make('test')->requiresConfirmation()),

Reproduction repository
https://github.com/tiagof/filament-bugs-report/tree/table-column-action-bug
Relevant log output
No response

Closures in this case are run when the cell is clicked, and are not used to register actions. We cannot use the syntax to do both

Ok...but it seems a bit inconsistent with all the other methods that receive Closures.
Any suggestion on how to have 2+ actions on a table column and decide which one to trigger based on some record property?
Thanks!

What is different about the actions?

Several things. The actual code I'd like to write:
->action(fn (ActionRequest $record) => match ($record->actionType) {
    ActionType::MAIL => EditDestination::makeTableAction(),
    ActionType::DOC => EditTasks::makeTableAction(),
    default => null,
})

There isn't going to be an easy way to do that at the moment

You can access $record in the functions of the action objects themselves so you can attempt to customise the modal content based on that etc

And of course, you can add as many normal actions to each row as you want instead of using a column

And of course, you can add as many normal actions to each row as you want instead of using a column

Yeah...I'll probably revert to that!
Thanks!!

authors: danharrin tiagof

repo: filamentphp/filament


text:
Require doctrine/dbal as development dependency

Because it's only needed for generating the resource classes during development.

I picked the v2 branch for this pull request. If you wish, I can rebase it and pick v3.

Thanks

authors: danharrin maartenpaauw


text:
patch to get the latest zondax code + pendng PR

update package.json to use Zondax's github page
Include MarketCbor.sol and MarketTypes.sol from https://github.com/Zondax/filecoin-solidity/pull/229 in the folder cbor_merge
add npm run cbor which copies MarketCbor.sol and MarketTypes.sol into node_modules and run this before compile
update DealClient.sol to use latest types in filecoin-solidity

Superseded by https://github.com/filecoin-project/fevm-hardhat-kit/pull/88.

authors: raulk snissn

repo: filecoin-project/fevm-hardhat-kit


text:
Add support for selecting items with a selection rectangle

Closes #94
Fixes #1731
This PR adds support for drag selection for both GridViewBrowser and GenericFileBrowser.
I'm sure there are  bugs, please help me find them xD
Issues:

~Items loose focus when trying to rename them~
~Ctrl/Shift + click selection in ListView is broken~
It's difficult to trigger the selection rectangle in GridView unless you click outside an item
~It's difficult to trigger the selection rectangle in ListView unless you click inside an item~
~Selecting multiple items prevents dragging the items to a different directory~

This is really great!

@gave92 I test your changes and they seem to work well! I did notice a small regression when trying to rename files that they would lose focus before I could change the name.

Glad you like this xD
@yaichenbaum this in GridView, ListView or both?
Also I think I broke Cntrl/Shift + click selection in ListView

@gave92 Just in list view.

Some of the issue reported should now be fixed.
@yaichenbaum Why "is it difficult to trigger the selection rectangle in ListView unless you click inside an item"?
Do you refer to the fact that you can't start a selection clicking on the empty space at the bottom of the ListView?

@yaichenbaum Why "is it difficult to trigger the selection rectangle in ListView unless you click inside an item"?
Do you refer to the fact that you can't start a selection clicking on the empty space at the bottom of the ListView?

Yes.

/azp run

authors: Jaiganeshkumaran gave92 yaichenbaum

repo: files-community/Files


text:
fr-FR

fr-FR

@gave92 Is there a possibility to take the work already done by him and finish?

Closing due to inactivity.

authors: boscorelly esibruti yaichenbaum


text:
问题

设为文件打开管理器之后用listary搜索打开文件夹是空的

This is the repo for the website, not the app. Please open the issue again in https://github.com/files-community/files.

authors: TheOnlyTails wangruibao

repo: files-community/Website


text:
Fixed tab title not showing correctly in some cases

Fixes #1548.

Bug still don't fixed.

Bug still don't fixed.

The path displayed on the Tabtitle not the absolute path for the directory??

What do you mean? My screenshot describes the problem still exists.

What do you mean? My screenshot describes the problem still exists.

The fix I have pushed will show the full path of the terminal tab until it is opened, then it switches to the folder title. So can you describe if you can see the full path as title of the tab??

It is better to show screenshots before/after.  Until tab is opened it anyway should display in tab title correct folder name, not full path.

It is better to show screenshots before/after.

Before tab loaded
After tab loaded

Until tab is opened it anyway should display in tab title correct folder name, not full path.

After tab is loaded the title is synonymous with folder name, hence I opted for full folder path so that user can distinguish which tabs has been loaded or not. Now that I think about it, it would be better to use accent color to indicate which tabs hasn't been loaded yet. What do you think about this??

As i mentioned before, it doesn't matter tab has been loaded or not. Tab title should contain only folder name without full path.

As i mentioned before, it doesn't matter tab has been loaded or not. Tab title should contain only folder name without full path.

Made changes to reflect that.

authors: soumyamahunt tsvietOK

repo: files-community/files-uwp


text:
Dotnet Global Tool Install - FileNotFoundException

Ran into an error when installing via dotnet tool install (letting dotnet grab the package from Nuget, nothing downloaded locally)
C:\test> dotnet tool install -g dotnet-script
Format version is missing. This tool may not be supported in this SDK version. Please contact the author of the tool.
You can invoke the tool using the following command: dotnet-script
Tool 'dotnet-script' (version '0.21.0') was successfully installed.
C:\test> dotnet script init

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'C:\Users\xxx\.dotnet\tools\dotnet-script.dll'. The system cannot find the file specified.

Not sure why it is looking for a DLL and not the EXE that is in that directory.
I've tried this from powershell + cmd + restarted my sessions on both etc. with the same result.
System info:
C:\test> dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.1.300-preview2-008530
 Commit:    822ae6d43a

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17133
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.300-preview2-008530\

Host (useful for support):
  Version: 2.1.0-preview2-26406-04
  Commit:  6833f3026b

.NET Core SDKs installed:
  1.1.7 [C:\Program Files\dotnet\sdk]
  1.1.8 [C:\Program Files\dotnet\sdk]
  2.1.4 [C:\Program Files\dotnet\sdk]
  2.1.102 [C:\Program Files\dotnet\sdk]
  2.1.200-preview-007517 [C:\Program Files\dotnet\sdk]
  2.1.300-preview1-008174 [C:\Program Files\dotnet\sdk]
  2.1.300-preview2-008530 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-preview1-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-preview1-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 1.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 1.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 1.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview1-26216-03 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview2-26406-04 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

If you need any more info let me know.

for some reason dotnet tool install -g dotnet-script installs dotnet-script.exe instead of dotnet-script.dll you can use dotnet-script instead of dotnet script.

Works fine on my Ubuntu machine too but on Windows 10 if i use either dotnet script or dotnet-script I get the same error.

This is fixed in the 0.22.0 release.
Please note that it was not our fault, but rather the CLI team that broke backwards compatibility 😄

Thanks for the investigation. Working perfectly now :)

❤to @seesharper for this work on that one

authors: SlowLogicBoy filipw stephenpope

repo: filipw/dotnet-script


text:
Accessing return value from InteractiveRunner.Execute?

Is it possible to access the return value from running an input with the InteractiveRunner.Execute method?

At the moment not, it's only getting printed to the Console.Out, but we can change the return type to Task<object> and expose it.

See #426

authors: cgranade filipw


text:
Udpate cookbook and best-practices

Add parts about streaming and Finagle configuration.

Current coverage is 85.83%

Merging #521 into master will not affect coverage as of 6918a6f

Powered by Codecov. Updated on successful CI builds.

authors: codecov-io vkostyukov

repo: finagle/finch


text:
feat: ability to respond to events with client-side actions

This PR adds ability for the data source to have impact on client-side behavior after responding to the request. It misses some tests and fine tuning, but I wanted to make sure we have directional agreement before commiting more time to it.
On a high-level, from your event handler, you can return either plain object or an instance of Response:
{
  $: 'component',
  component: 'RiseForm',
  props: {
    onSubmit: asyncHandler((values) => {
      // handle on press, then
      return res.json()
        // send action
        .action(['navigate', 'goBack'])
        // or more
        .action(['some-other-action'])
    })
  }
}

Above example will instruct client to perform "goBack" navigation which is specific to Rise mobile application after
succesfully handling action on the server. We should document them at some point, most likely in a follow-up PR, as we currently have just two.

![NOTE] On types: This is not yet supported, but in the future, the return type from within onSubmit would be enforced with TypeScript for better DX. That way, you would know what your components expect in return (if anything) from an event handler. In case of Form, that could be nothing (indicating success) or an array of validation errors.

![NOTE] In the future, we can hide res.json().action(['navigate', 'goBack']) behind something nicer.

On the client, to listen to the events, you register onEvent (name tbd) handler on the Data Source:
useEffect(() => {
  return dataSource.onEvent((dataState) => {
   if (action === 'navigate-back') {
      router.back()
      return
    }
  })
}, [])

It automatically returns unsubscribe function, so it works with useEffect. In the future, if we decide to pass DataSource via Context, components can use a higher-order hook useActionEvent to listen and handle different types of events in specialised components. This API design should be pretty universal and work with JSON RPC as well as In-Memory data sources in the future.
Important change regarding handling actionEvents
The following is no longer needed:
const onEvent = (event: TemplateEvent) => {
  if (isActionEvent(event)) {
    // handle action event
  }
  dataSource.sendEvent(event)
}

<Template onEvent={onEvent} />

We no longer have to "intercept" events in the onEvent prop of <Template /> component in order to perform some client-side actions.
<Template
  onEvent={dataSource.sendEvent}
/>

If Data Source detects an event passed to sendEvent is of type ActionEvent, it will not send it to the server, but will call dataSource.onEvent instead. This makes it easy to do things such as ['navigate-back'] without doing round-trip to the server.
The downside is that we loose the ability to listen to all action events in one place, like we do in the eg server with wsDataSource.onActionEvent. However, going forward, we want to encourage passing functions as props, and I think ActionEvent is best for client-side interactions to avoid confusion.
Instead of:
{
  $: 'component',
  component: 'RiseForm',
  props: {
    onSubmit: 'form-submit'
  }
}

and
wsDataSource.onActionEvent(event => {
  if (event.dataState.action === 'form-submit') {
    // handle form submission
  }
})

you would have to write:
{
  $: 'component',
  component: 'RiseForm',
  props: {
    onSubmit: () => {
      // handle form submission and return something like validation
    }
  }
}

and in the future with JSX:
<RiseForm onSubmit={() => {}} />

You would want to use function as prop anyway in this case, because you can't return response back to the client from onActionEvent (because there can be multiple listeners registered and client expects a single response only).

![WARNING] This is breaking change and is not backwards compatible with eg app due to the way it handles events. We could theoretically leave onActionEvent and still send action events to the server, like before, to avoid expensive refactoring of eg and to have an ability to use it as a preview. On the other hand, it might be better to develop smaller, specialised demo servers and not hold back at a very early stage with core changes due to one application.

Also, going forward, I think we should drop handler (the one that does not allow you to return from the server, client does not await response) and just stick to asyncHandler.
This will solve one major problem: after we switch to JSX, having to decide whether the following:
<Component onSubmit={() => // do something, return new Error("Failed")} />

is a handler (no response supported by the client) or asyncHandler (you can return response, client will wait if component is able to handle this UX).
By making it just one, we reduce complexity and get rid of challenges like the one above.
In practice, you want to return something to the client most of the time to indicate "success". If you still want to perform a side-effect without user feedback, you can make your handler function return nothing.
This does not have any impact on the performance of the client-side, because no handlers are awaited. It is only custom components in Final UI kit that have this capability and users are expected to do that on their own too.
Note: you can still do action: ['navigate-back]' to perform client-side navigation without bothering the server.

I'm really not sure how much of this stuff should be strictly tied to every data source, we should discuss this

It is possible to make it data source specific so that each can define its own shape and style for responses in case there's different needs. What you return from your handler must be supported by currently used data source (and that is up to you). In our case, we have statusCode and ok because we use it to resolve/reject a promise. If you choose a different strategy in your custom data source, you may or may not need one.
I would keep it on the todo list to split/keep separate once we add additional data source. Otherwise, it's very tricky to do in advance.

repo: final-ui/final


text:
Windows10でスタートアップから起動できない場合がある。

ツールから生成したショートカットでは起動されない模様。手動で生成したショートカットだと起動する。
違いを確認してもらったが、名前とサイズくらいとのこと。
ショートカットの生成方法を含めて見直す。
ちなみにふぁいなるが所持しているWin10(x86)だとツールが生成したショートカットでスタートアップから起動できた。
twitterでallfreesoftさまよりご報告いただいた。

1/11にallfreesoftさまより、1.3.91で解消したとご連絡をいただいた。

repo: finalstream/ExplorerWindowCleaner


text:
Where to place logic, Domain vs Service?

Started this post to gather feedback on some content i'm writing to help with the common question of 'Where to place my logic, Domain or Service'
Business Logic in the Domain class vs Service class?
Sometimes it can feel less than obvious where to place code. Lets go back to the Separation of Concerns principle and think about what the Service and Domain layers are concerned with.

Fowlers definitions...
Service Layer, “Defines an application's boundary with a layer of services that establishes a set of available operations and coordinates the application's response in each operation.” Martin Fowler / Randy Stafford, EAA Patterns
Domain Model, “An object model of the domain that incorporates both behavior and data.”, “At its worst business logic can be very complex. Rules and logic describe many different cases and slants of behavior, and it's this complexity that objects were designed to work with...” Martin Fowler, EAA Patterns

I'd like a few views on the concerns i've listed above as well as other concerns we could list to help people understand where placement goes. I suspect sometimes just having some tightly written code in the service layer could be a preference at times to breaking things out into domain layer calcs or updates?

I have challenges with 3 and 4 around the suggestion of implementing cross-object behaviour at the Domain layer, especially when they are invoked by triggers.
At worst, such a design could inadvertently cause a chain reaction of triggers which results to a variety of problems (e.g. SOQL limits, CPU time limit, trigger recursions, etc) that are particularly difficult to troubleshoot and unwind without regression. It does not scale well in an enterprise-level application that is developed iteratively.
Refactoring the design typically involves implementing the behaviour back to Service layer which in SFDC also implies sacrificing SFDC's standard forms (new/edit pages) with custom controller or controller extensions.

Great feedback @jmrjulian thank you, will give this some thought!

@afawcett I am building a complex subscription management system in which bulk of the business logic is invoked through triggers. There are certain scenarios where I don't want subsequent triggers to fire (stop recursion as well as chaining of triggers). Can you please provide me some guidance on that? I don't want all trigger methods to stop but want to control which ones should be skipped. Can we build something in fflib_SObjectDomain class for this?

@afawcett also it would be great if we can build some control through custom settings so admins can turn on/off triggers when they want to perform certain operations like data load without invoking triggers.

I think this is what you're looking for :)
https://andyinthecloud.com/2016/04/13/disabling-trigger-events-in-apex-enterprise-patterns/
Chris Mail

On 10 Jun 2016, at 11:23, mustafaturabali notifications@github.com wrote:
@afawcett also it would be great if we can build some control through custom settings so admins can turn on/off triggers when they want to perform certain operations like data load without invoking triggers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@mustafaturabali does at @Autobat's answer help?
(thanks btw @Autobat )

I'll close this issue for now, its bene open since Feb and really was just a feedback call out. Folks can still add to this issue even though its closed.

authors: Autobat afawcett jmrjulian mustafaturabali

repo: financialforcedev/fflib-apex-common


text:
Remove FUSD.

Atm we have a market that is built into the FIND contract. That forces use of FUSD.
We need to change all transactions so that they allow listing names for sale in the LeaseMarket contract using FiatToken and FlowToken.
We also need to make the method to delist a sale in the old market public so that we can delist everything that is in typesense.
Typesense indexer also needs to be verified that it works for the new listings.
DoD:

we do not use FUSD anymore.
we cannot register in FUSD
we cannot renew in FUSD (but renew in flow and Fiat)
we cannot secondary sell in FUSD.

This task is now expanded to not only remove FUSD but also FiatToken. Instead of FiatToken we should only accept payment for Find names in FlowToken. We need to use the price oracle from increment.fi to lookup the correct amount of flow to accept for a name, and we should allow some slippage
https://docs.increment.fi/protocols/decentralized-price-feed-oracle/using-price-feeds

This has been performed on testnet and new changes staged for mainnet.

repo: findonflow/find


text:
alphabetical Sender

Dears Am not able to send a msg to anyone if the Src was letters instead of numbers
Can you guide me through the solution pleaaase 🥺

you need to set SourceAddrTON: 5 when using tx.Submit

authors: ddaka hamdongunner

repo: fiorix/go-smpp


text:
iPhone 13 Pro Analytics Archive

iPhone 13 Pro Analytics Archive

January 25, 2022

Fire A Cloud, LLC

@Apple Developer Program Member

Assigned to:

@fireacloud
@iamgucci

Link back to here:

Link back to here:

@iamgucci
@fireacloud
@firea-cloud/fireacloud

repo: firea-cloud/firea-cloud


text:
Fix potential account linking sign-in failure due to recursive sign-in attempts

Fixes #1275
AFAIK, this doesn't affect our current codebase.

That's a good catch!

thanks

authors: SUPERCILEX j2emanue samtstern

repo: firebase/FirebaseUI-Android


text:
feat(firestore-bigquery-export): support collectionGroup queries

Created a new parameter which allows the user to decide if the imported Firestore documents are queried via a collection query or a collectionGroup query.
Doesn't fully solve #17 as wildcards aren't allowed in Firestore queries.
Updated recently merged non-interactive option to also accept --query-collection-group parameter. This feature can now be used interactively or non-interactively.

Testing
Tested the import of a collection with 30 documents using a collection query:

Tested the import of a sub-collection with 2 documents using a collectionGroup query:

I've also added the collectionGroup query as an argument to be used during --non-interactive mode: https://github.com/firebase/extensions/pull/354/files#diff-2f74e55e61e11ab08c67d590ea86116bR82

Codecov Report

Merging #354 into next will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next     #354   +/-   ##
=======================================
  Coverage   39.96%   39.96%
=======================================
  Files          19       19
  Lines         633      633
  Branches       84       84
=======================================
  Hits          253      253
  Misses        378      378
  Partials        2        2

@googlebot I consent.

@russellwheatley I've just pushed a commit to make this optional as discussed.

LGTM

Tested the import of a collection with 30 documents using a collection query:

Tested the import of a sub-collection with 2 documents using a collectionGroup query:

I've updated this PR in light of the --non-interactive import PR merging into next (https://github.com/firebase/extensions/pull/328)
I've added the collectionGroup query as an argument to be used during --non-interactive mode: https://github.com/firebase/extensions/pull/354/files#diff-2f74e55e61e11ab08c67d590ea86116bR82

Wanted to mention that I was able to use this branch locally with success for importing by collectionGroup. Thank you!
Hope it can eventually be merged to help others more easily

authors: Ehesp codecov-commenter nwparker russellwheatley

repo: firebase/extensions


text:
Validate credential account

Added validation to check whether it's an external_account or service_account to fix error missing client_email caused by https://github.com/googleapis/google-auth-library-ruby/blob/main/lib/googleauth/json_key_reader.rb#L24 when using Workload Identity Federation

service_account –> Google::Auth::ServiceAccountCredentials
external_account –> Google::Auth::ExternalAccount::Credentials

Fix tests

@tonybaroneee probably can help to review this? 🙏

hi @kaibolay, could you help to publish new version that includes this diff?

@adrianha I have some additional changes queued up for a new release. Could you please test #347 and let me know if it works for you?

hi @kaibolay,
looks fine on my end 👍
[13:18:14]: 🔐 Authenticating with Application Default Credentials
[13:18:14]: ⌛ Uploading the APK.
[13:18:18]: 🕵 Validating upload.
[13:18:26]: ✅ Uploaded APK successfully and created release 1.0.0 (1).
[13:18:26]: 📜 Setting release notes.
[13:18:28]: 📦 Distributing release.
[13:18:29]: 🎉 App Distribution upload finished successfully. Setting Actions.lane_context[SharedValues::FIREBASE_APP_DISTRO_RELEASE] to the uploaded release.

@adrianha Thank you. It's released now.

thank you @kaibolay!

hi @kaibolay, just realized that fastlane-plugin-firebase_app_distribution 0.8.0 depends on google-apis-firebaseappdistribution_v1 and google-apis-firebaseappdistribution_v1alpha, is it expected?
I got Service account impersonation failed with status 403 error after updating to 0.8.0 then it's resolved after updating other dependencies:

aws-partitions: 1.872.0 –> 1.876.0
aws-sdk-s3: 1.141.0 –> 1.142.0
fastlane: 2.217.0 –> 2.218.0

hi @kaibolay, just realized that fastlane-plugin-firebase_app_distribution 0.8.0 depends on google-apis-firebaseappdistribution_v1 and google-apis-firebaseappdistribution_v1alpha, is it expected?

Yes. get_udids uses a v1alpha API.

I got Service account impersonation failed with status 403 error after updating to 0.8.0 then it's resolved after updating other dependencies:

aws-partitions: 1.872.0 –> 1.876.0
aws-sdk-s3: 1.141.0 –> 1.142.0
fastlane: 2.217.0 –> 2.218.0

That's really odd. None of these are direct (or indirect) dependencies of fastlane-plugin-firebase_app_distribution.

I see, maybe it's intermittent then 🤔

authors: adrianha kaibolay


text:
Dynamic Links don't survive app install on iOS 11.3.1

Xcode version: 9.3
Firebase SDK version: 5.0.0
Firebase Component: Dynamic Links
Component version: 3.0.0

Problem:
Dynamic links does not survive app install from app store on iOS 11.3.1
://google/link/?dismiss=1&is_weak_match=1
Note that this works fine on previous iOS versions (11.2 and below)
Steps to reproduce:

Click on Firebase Dynamic Links
Browser redirect to app store
Install from app store
Open the app
Dynamic link not passed

@morganchen12 For sure.
- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
  sourceApplication:(NSString *)sourceApplication
         annotation:(id)annotation {

//the url here returns:
//google/link/?match_type=none&match_message=No pre-install link matched for this device.
or
//google/link/?dismiss=1&is_weak_match=1

    FIRDynamicLink *dynamicLink = [[FIRDynamicLinks dynamicLinks] dynamicLinkFromCustomSchemeURL:url];

//dynamicLink.url is nil here.

}

Note that on iOS 11.2 it still works.

@morganchen12 @dmandar Any update on this? Thanks!

No update yet, but we should be able to get to this this week.

Can you confirm if your links are using the app preview page?

@dmandar yes, we're skipping the app preview page. But this works prior to iOS 11.3.1

Mandar is currently investigating this, but hasn't come back with anything yet.
Internal bug filed at b/79657436.

What about the issue ? If this issue persist in every latest OS version then what is the meaning of using Firebase Dynamic link ? And why they are not providing with any solutions to this when this issue is creating so much noise over the internet.

@kbcodelogicx we are actively investigating this issue and will have an update very soon.

@dmandar @morganchen12 this is fixed on iOS 11.4, but issue still persists on iOS 11.3

@richardliveraise is this iOS 11.3.1, or just iOS 11.3?

@morganchen12 correction, issue is on 11.3.1, I don't have 11.3 device to confirm.

@richardliveraise that's correct - the issue still persists only on that version - we have a bug fix in the works for it. Also, 11.4 or any other version (up to one digit after the decimal) should not exhibit the behavior.

It turns out some of the fixes are still in the process of being implemented. To clarify, this is a server issue, so you won't need an SDK update in order to receive the fix. I'll leave this issue open for the time being until all of the error cases are fixed.

+1

It's working on iOS11.3, but not iOS11.3.1

Hi @morganchen12 , I'm also having this issue and am troubled because iOS 11.3 has currently the majority of iOS userbase. No pressure but do we have any ETA on the server side fix? Thanks in advance...

Is it going to be a server side fix?

Yes.

I am trying to implement Firebase Invites on iOS right now, and after an app install I am also always receiving myAppScheme://google/link/?dismiss=1&is_weak_match=1 instead of the deep link. Therefore FIRInvites cannot parse it and it does not work. Is this related to the issue with Dynamic Links? I have one iPhone 6 on iOS 11.4 and one iPhone 5 on 10.3.3 and it does not work on both of them.
Mind you that it does work on android (with the same firebase project) and on iOS when the app is already installed, so this problem is just occuring when the user is first installing the app after receiving an Invite.

@davidwernhart can you file a new issue and include the versions of the Firebase frameworks you're using?

yes, this is fixed on iOS 11.3.1 . Thank you!!

i have 11.4.1 (iPhone7)

Is this issue still open? Our app launches deep links perfectly when it is already installed, but the deep links never persist after install.
When debugging we can see the deep link in the logs with a message saying "Deep link does not contain valid required params" but it does say "Link is uniquely matched for this device" at the same time...
Any suggestions?

Yes, it is not working in iOS 12.0 also.

The backend issue has been fixed. Can you make sure that the target app has the same bundleID as that contained in your deep link (in case of a shortened link, you can go to the Firebase console to get the long version of the link). Also, do you have the (recommended) app preview page enabled?

Does not work on iOS 12.3
It does work when the preview page is enabled, though.

@dmandar Have the same issue, when preview page is disabled: No pre-install link matched for this device
With preview page enabled all is fine.
iOS version: 12.3

I believe I'm having the same issue with custom domains + preview + deferred links on Firebase v5.20.2. I'm building my links manually. When I do the following with the preview enabled...

Uninstall the app
Open a custom domain dynamic link with preview enabled, and tap "open"
Install the app via Xcode

...openUrl in AppDelegate is correctly called with my link URL. However, adding efr=1 to the link (skipping the preview page) and repeating the process, the openUrl is called with "[my bundle ID]://google/link/?dismiss=1&is_weak_match=1" instead.
Reading the docs, I'm not sure if this is intentional or not — is the app preview required to make deferred deep links work?

@averyvery it's not explicitly mentioned as required since DDL can work without it, but app preview does provide more accurate matching of the app installation to the device that tapped on the link. @dmandar can maybe elaborate more.

@dmandar When can we expect to see dynamic links working without the preview page and with a forced redirect? This disrupts our app's installation flow as it's one of the main ways users install our app.

Same in our app. It's a shame that's not mentioned at all and we have to browse all internet to find this pot to finally have a clue about this bug. As many devs, I think the option to skip the app preview is a must-have, and the success of the dynamic link should not depend on it. Especially when you make this feature SKIPPABLE.
I really encourage you to make this works without app preview cause it disrupts the installation flow  especially with a referral program.

We also face same issues in our iOS apps. All works fine with *.page.link domains, but when we use a custom domain then Dynamic Links don't survive app install.
In that case it is always “appscheme://google/link/?request_ip_version=IP_V4&match_message=No pre-install link matched for this device.” URL that passed to the “application:openURL:sourceApplication:annotation:” method.
So we just can’t use our brand domains for Dynamic Links, and it harms effectiveness of our campaigns.
Is there any progress of fixing this issue? Or a workaround without enabling a Preview page?

@loobnin did you find any solution or made some progress on this issue?

I hate to pile on with a +1 but we're still seeing this issue on iOS 13.x as well. Perhaps this issue should be reopened.

@0x7fs, can you open a new issue and try reproducing the issue with the dynamic links quickstart?

@0x7fs could you check for [UIApplicationDelegate application:openURL:options:] function in your AppDelegate? In my case that was my issue, If you do have openURL delegate y your AppDelegate with nothing in it, somehow this is overriding the same method in FirebaseDynamicLinksPlugin.m so you need to delete that one in your AppDelegate.m, like I explain here https://github.com/FirebaseExtended/flutterfire/issues/100#issuecomment-541204778
So, this is AppDelegate.m

And this is FirebaseDynamicLinksPlugin.m

authors: 0x7fs Appkidd Banck CyrilNb MarsVard Younghun-Jeong averyvery davidwernhart dmandar dmitry-solomadin fmkpro1984 kbcodelogicx loobnin morganchen12 quetool richardliveraise shali3 tamilvelraj toco1001

repo: firebase/firebase-ios-sdk


text:
'FIRPhoneAuthCredential.h' file not found, tvOS/iOS shared pod

[REQUIRED] Step 2: Describe your environment

Xcode version: 9.2
Firebase SDK version: 4.8.1
Firebase Component: Auth
Component version: 4.8.1?

[REQUIRED] Step 3: Describe the problem
The tvOS-target in the Auth podspec excludes files which are needed for the iOS target.
Steps to reproduce:

Install with CocoaPods, targeting tvOS.
Add an iOS target and do another pod install.
Build for your tvOS target (builds fine).
Build for your iOS target, fails on 'FIRPhoneAuthCredential.h' file not found

Relevant Code:
Podfile:
use_frameworks!

def shared_pods
    pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :tag => '4.8.1'
    pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :tag => '4.8.1'
    pod 'FirebaseDatabase', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :tag => '4.8.1'
end

target 'iOS' do
    platform :ios, '9.0'
    shared_pods
    pod 'Hero'
end

target 'tvOS' do
    platform :tvos, '10.0'
    shared_pods
    pod 'ParallaxView'
    pod 'Re-Lax'
end

There's a couple of offending import statements; they were different ones the two times I replicated this.  Second time it was FIRPhoneAuthCredential_Internal.h:
#import "FIRPhoneAuthCredential.h"

Which was imported by FIRUser.m:
#if TARGET_OS_IOS
#import "FIRPhoneAuthProvider.h"
#import "AuthProviders/Phone/FIRPhoneAuthCredential_Internal.h"
#endif

Seems like this issue is caused by the Auth module's podspec excluding these files for a tvOS target.  That's all fine and dandy, but if you have both targets in your project, and the tvOS one was put into CocoaPods first, then those files will be missing when you switch to your iOS target and compile.
As far as I can tell, the podspec should just be edited to include these headers back in because the preprocessor statements exclude the offending files from compiling when you're targeting tvOS.  Have a pull request coming momentarily...

Thanks for the issue and PR.  I don't have too much time to investigate now, but a quick thought   based on the description of adding targets between pod install runs:  I suspect you're running into a CocoaPods issue of needing to do a pod deintegrate before adding a new target to a Xcode workspace.  CocoaPods names targets differently depending upon if the workspace is mono- or multi-targeted.

Thanks, that actually solved it.  No need to merge the PR I assume?

👍 Glad it worked! I'll close the PR - #781.


text:
I get the error log when app run in background long time(3 days)

2020-02-25 12:30:26.609 19145-19145/com.lionparcel.services.driver.stage W/FJD.ExternalReceiver: Error unbinding service: Service not registered: com.firebase.jobdispatcher.JobServiceConnection@4561150
2020-02-25 12:39:31.888 19145-19162/com.lionparcel.services.driver.stage W/es.driver.stag: Reducing the number of considered missed Gc histogram windows from 348 to 100
2020-02-25 12:41:21.263 19145-19145/com.lionparcel.services.driver.stage E/ActivityThread: Service com.firebase.jobdispatcher.GooglePlayReceiver has leaked ServiceConnection com.firebase.jobdispatcher.JobServiceConnection@fd65367 that was originally bound here
android.app.ServiceConnectionLeaked: Service com.firebase.jobdispatcher.GooglePlayReceiver has leaked ServiceConnection com.firebase.jobdispatcher.JobServiceConnection@fd65367 that was originally bound here
at android.app.LoadedApk$ServiceDispatcher.(LoadedApk.java:1805)
at android.app.LoadedApk.getServiceDispatcherCommon(LoadedApk.java:1677)
at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:1656)
at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1721)
at android.app.ContextImpl.bindService(ContextImpl.java:1650)
at android.content.ContextWrapper.bindService(ContextWrapper.java:705)
at com.firebase.jobdispatcher.ExecutionDelegator.executeJob(ExecutionDelegator.java:110)
at com.firebase.jobdispatcher.GooglePlayMessageHandler.handleStartMessage(GooglePlayMessageHandler.java:98)
at com.firebase.jobdispatcher.GooglePlayMessageHandler.handleMessage(GooglePlayMessageHandler.java:67)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
2020-02-25 12:41:21.266 19145-19145/com.lionparcel.services.driver.stage W/FJD.ExternalReceiver: Error unbinding service: Service not registered: com.firebase.jobdispatcher.JobServiceConnection@fd65367
2020-02-25 13:04:36.369 19145-19145/com.lionparcel.services.driver.stage E/ActivityThread: Service com.firebase.jobdispatcher.GooglePlayReceiver has leaked ServiceConnection com.firebase.jobdispatcher.JobServiceConnection@a50170a that was originally bound here
android.app.ServiceConnectionLeaked: Service com.firebase.jobdispatcher.GooglePlayReceiver has leaked ServiceConnection com.firebase.jobdispatcher.JobServiceConnection@a50170a that was originally bound here
at android.app.LoadedApk$ServiceDispatcher.(LoadedApk.java:1805)
at android.app.LoadedApk.getServiceDispatcherCommon(LoadedApk.java:1677)
at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:1656)
at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1721)
at android.app.ContextImpl.bindService(ContextImpl.java:1650)
at android.content.ContextWrapper.bindService(ContextWrapper.java:705)
at com.firebase.jobdispatcher.ExecutionDelegator.executeJob(ExecutionDelegator.java:110)
at com.firebase.jobdispatcher.GooglePlayMessageHandler.handleStartMessage(GooglePlayMessageHandler.java:98)
at com.firebase.jobdispatcher.GooglePlayMessageHandler.handleMessage(GooglePlayMessageHandler.java:67)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
2020-02-25 13:04:36.375 19145-19145/com.lionparcel.services.driver.stage W/FJD.ExternalReceiver: Error unbinding service: Service not registered: com.firebase.jobdispatcher.JobServiceConnection@a50170a

In April 2019 we announced that Firebase Job Dispatcher would be deprecated today, April 7th 2020.  For this reason we are going to close all open issues and archive the repository.  We will also stop supporting FJD for new app installations (such as those targeting sdk versions greater than Android Q).  Existing apps that rely on FJD should continue to function as usual.
While we will no longer work on FJD, we encourage you to migrate to Work Manager which is a superior tool and fully supported by the Android team.
Thank you for taking the time to try the library and provide this feedback.  We sincerely appreciate your effort and we apologize for not addressing it in time.

repo: firebase/firebase-jobdispatcher-android


text:
🐛 [firebase_auth] [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 18002 Invalid PlayIntegrity token; app not Recognized by Play Store.

I am getting an error while fetching the sms code from the verification completed callback. I am getting an SMS on the physical device, but it fails to get set in the text field.
Error:
"E/FirebaseAuth(32222): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 18002 Invalid PlayIntegrity token; app not Recognized by Play Store."

In the screenshot, there's my authentication service class, which I've created, in that the code sent callback is working as expected, but the verification completed callback is never getting called.
Line no. 22 is never getting called.
Flutter Version:
Flutter (Channel stable, 3.7.0, on macOS 13.3 22E252 darwin-arm64, locale en-IN)
Plugin Version:
firebase_app_check: ^0.1.2
firebase_auth: ^4.4.0
firebase_core: ^2.9.0
Important:
I've set up Firebase "Phone Authentication" in Firebase Console & App
I've set up Firebase "App Check" in Firebase Console & App
I've set up SHA Keys (Debug & Release) in Firebase Console

I faced the same issue

@dharambudh1
Can you take a look at plugin example and see if using it, you get same error or not ?

@darshankawar, Yes, I just went through the official example, I've checked their source code & I didn't find any resolution there.
https://github.com/firebase/flutterfire/blob/master/packages/firebase_auth/firebase_auth/example/lib/auth.dart#L490
Look at Line no. 490. That callback is empty.

Please help me, I'm experiencing a similar issue. I have tried several approaches:

Adding SHA-1 and SHA-256 (Debug, Release, and Key from Play Console) in the Firebase project settings.
Adding SHA-256 (Debug, Release, and Key from Play Console) in App Check (Play Integrity).
Connecting to Google Cloud Console in Play Console App Integrity.
Using Authentication SDK v21.2.0+ (Firebase BoM v31.4.0+) as per the documentation at https://firebase.google.com/docs/auth/android/phone-auth

I have spent a lot of time on this issue, and any help would be greatly appreciated.

Thanks for the feedback. Keeping the issue open for team's thoughts on the reported behavior.
/cc @Lyokone

Hello @dharambudh1,
Looking at your code, you are not using the callbacks correctly. Please look at the official example on how to use this function (the callback is meant to see if the verification has been successfully completed, but is not meant to get the credentials):
 await auth.verifyPhoneNumber(
          phoneNumber: phoneController.text,
          verificationCompleted: (_) {},
          verificationFailed: (e) {
            setState(() {
              error = '${e.message}';
            });
          },
          codeSent: (String verificationId, int? resendToken) async {
            final smsCode = await getSmsCodeFromUser(context);

            if (smsCode != null) {
              // Create a PhoneAuthCredential with the code
              final credential = PhoneAuthProvider.credential(
                verificationId: verificationId,
                smsCode: smsCode,
              );

              try {
                // Sign the user in (or link) with the credential
                await auth.signInWithCredential(credential);
              } on FirebaseAuthException catch (e) {
                setState(() {
                  error = e.message ?? '';
                });
              }
            }
          },
          codeAutoRetrievalTimeout: (e) {
            setState(() {
              error = e;
            });
          },
        );

For the 18002 error, did you publish the app on the Play Store already?
@ridwan-aswan
I see that you are mentioning using Using Authentication SDK v21.2.0+, you are following the Android instructions and not the Flutter ones. You should not add BOM manually.

verificationCompleted

I am pretty sure my method is correct because it was working a few weeks ago & I haven't changed anything from there. Verification completed callback is listening for the SMS (we can print SMS Code in the console using "credential.smsCode"). And if we want to perform autofill SMS (without using any 3rd party packages) at that time, that verification completion callback plays a most integral part.
For example, "textEditingController.text = credential.smsCode".
BTW, we haven't published our app yet. It is still under development.

I'm having same issue with an app that has been published to the app store. Was working before and now it isn't. @dharambudh1 did you figure out a fix?

We published a new version of firebase_core that includes some fixes on the Native SDK. Can you try to see if bumping your app to the latest firebase_core and firebase_auth package version solve the issue (don't hesitate to run flutterfire update to ensure that you are using the latest packages)

That fixed it for me!
On Tue, Apr 18, 2023, 5:56 AM Guillaume Bernos @.***>
wrote:

We published a new version of firebase_core
https://pub.dev/packages/firebase_core that includes some fixes on the
Native SDK. Can you try to see if bumping your app to the latest
firebase_core and firebase_auth package version solve the issue (don't
hesitate to run flutterfire update to ensure that you are using the
latest packages)
—
Reply to this email directly, view it on GitHub
https://github.com/firebase/flutterfire/issues/10750#issuecomment-1513077151,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHEF2BEC2DVCIKP65UGPXLXB2FO7ANCNFSM6AAAAAAWX6IMQE
.
You are receiving this because you commented.Message ID:
@.***>

We published a new version of firebase_core that includes some fixes on the Native SDK. Can you try to see if bumping your app to the latest firebase_core and firebase_auth package version solve the issue (don't hesitate to run flutterfire update to ensure that you are using the latest packages)

I'm still getting below-mentioned error:

Guys, to test the app, do you have to put it on the play store?
mine worked normally now it's giving the same problem

I'm getting the same error in logs
SMS verification code request failed: unknown status code: 18002 Invalid PlayIntegrity token; app not Recognized by Play Store.

I did all of the following

setup App Integrity in Google Play Console and linked the correct project number from Google Cloud [same as the Firebase project]
added this dependency to android/app/build.gradle : implementation 'com.google.android.play:integrity:1.1.0'
I have my SHA-1 and SHA-256 correctly added to Firebase console.
I updated the dependencies in pubspec.yaml to firebase_core: ^2.13.0 and firebase_auth: ^4.6.1.

Is there anything else I might be missing?
The app would always open recaptcha for real phone numbers now. For the phone numbers added as test phones in Firebase console, recaptcha is skipped.

Hello,
We're encountering a same problem, and we're actively searching for a solution. if any one sound solution please let me know.

Is it possible to work it out without necessarily publishing it on Play Store?
I have done all the steps in Firebase(SHA keys, google-services.json, Play Integrity in App Check), flutter(updating firebase_core, firebase_auth) and build.grade in android/app(firebase-auth-ktx, firebase-auth, firebase-bom, firebase-app check-play integrity, firebase-appcheck-ktx) but no success.
After all this, reCaptcha screen is skipped only for test phone numbers. I suspect publishing to Play Store would be mandatory but I am not very sure.

It is required to publish your app in the play store for the play integrity provider to work. You can use the internal testing track to test it works before publishing to users. You're likely getting the app signing key from the Play Store which needs inputting into your Firebase console.

https://firebase.google.com/docs/app-check/flutter/default-providers#initialize
Add app check package and give webProvider in main

@dharambudh1 - did you manage to resolve this issue? As mentioned previously, you have to publish to Playstore for play integrity provider to work.

One update, I have published the WinzTrade app on the Play Store in India. The reCaptcha is automatically removed when the app is downloaded from the Play Store.

authors: AK47-23 DimaLiubko GrandeSamarone Lyokone ThakarRajesh darshankawar dharambudh1 elenacrst ericmand priteshkumbhare ridwan-aswan russellwheatley

repo: firebase/flutterfire


text:
Returning value to supress log errors

When nothing is returned, the functions log contains:

Function returned undefined, expected Promise or value

I signed it!

Thanks @weotch :)

authors: nicolasgarnier weotch

repo: firebase/functions-samples


text:
[~WATCH!] Baltasar Ebang Engonga Video Original Video Link Baltasar Ebang Engonga Video Viral On Social Media X Trending Now

26 seconds ago
L𝚎aked Video Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter Telegram
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈1)
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈2)
➤ ►🌍📺📱👉 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺
𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024. 𝖳𝗁𝖾 𝗋𝖾𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗍𝗁𝖾𝗆𝖾 𝗈𝖿 𝖫𝖾𝖺𝚔𝖾𝖽 𝗍𝖺𝗉𝖾𝗌 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗎𝖻𝗌𝖾𝗊𝗎𝖾𝗇𝗍 𝖿𝖺𝗅𝗅𝗈𝗎𝗍 𝗌𝖾𝗋𝗏𝖾𝗌 𝖺𝗌 𝖺 𝗋𝖾𝗆𝗂𝗇𝖽𝖾𝗋 𝗈𝖿 𝗍𝗁𝖾 𝖿𝗋𝖺𝗀𝗂𝗅𝗂𝗍𝗒 𝗈𝖿 𝗋𝖾𝗉𝗎𝗍𝖺𝗍𝗂𝗈𝗇 𝗂𝗇 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖾𝗋𝖺. 𝖠𝗌 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾𝗌 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝖺𝗇𝖽 𝗉𝗎𝖻𝗅𝗂𝖼 𝗅𝗂𝖿𝖾 𝖼𝗈𝗇𝗍𝗂𝗇𝗎𝖾 𝗍𝗈 𝖻𝗅𝗎𝗋, 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗂𝖾𝗌 𝗅𝗂𝗄𝖾 𝖯𝗋𝗂𝗌𝗈𝗇 𝖮𝖿𝖿𝗂𝖼𝖾𝗋𝖿𝗂𝗇𝖽 𝗍𝗁𝖾𝗆𝗌𝖾𝗅𝗏𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝗆𝖾𝗋𝖼𝗒 𝗈𝖿 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖼𝗁𝖺𝗍𝗍𝖾𝗋, 𝗐𝗁𝖾𝗋𝖾 𝖺 𝗋𝗎𝗆𝗈𝗋 𝖼𝖺𝗇 𝗂𝗀𝗇𝗂𝗍𝖾 𝖺 𝖿𝗂𝗋𝖾𝗌𝗍𝗈𝗋𝗆 𝗈𝖿 𝗌𝗉𝖾𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇 𝖺𝗇𝖽 𝗃𝗎𝖽𝗀𝗆𝖾𝗇𝗍.
𝖨𝗇 𝗍𝗁𝖾 𝖾𝗏𝖾𝗋 𝖾𝗏𝗈𝗅𝗏𝗂𝗇𝗀 𝗅𝖺𝗇𝖽𝗌𝖼𝖺𝗉𝖾 𝗈𝖿 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗒 𝖼𝗎𝗅𝗍𝗎𝗋𝖾, 𝗍𝗁𝖾 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗌𝖼𝖺𝗇𝖽𝖺𝗅 𝗎𝗇𝖽𝖾𝗋𝗌𝖼𝗈𝗋𝖾𝗌 𝗍𝗁𝖾 𝗋𝖾𝗅𝖾𝗇𝗍𝗅𝖾𝗌𝗌 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗈𝖿 𝗌𝖾𝗇𝗌𝖺𝗍𝗂𝗈𝗇𝖺𝗅𝗂𝗌𝗆, 𝖺 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗍𝗁𝖺𝗍 𝗈𝖿𝗍𝖾𝗇 𝖼𝗈𝗆𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝖾𝗑𝗉𝖾𝗇𝗌𝖾 𝗈𝖿 𝗍𝗋𝗎𝗍𝗁 𝖺𝗇𝖽 𝖽𝗂𝗀𝗇𝗂𝗍𝗒. 𝖠𝗌 𝗐𝖾 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝖾 𝗍𝗁𝖾 𝖼𝗈𝗆𝗉𝗅𝖾𝗑𝗂𝗍𝗂𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖺𝗀𝖾, 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝖾𝗇𝗍𝖾𝗋𝗍𝖺𝗂𝗇𝗆𝖾𝗇𝗍 𝖺𝗇𝖽 𝖾𝗑𝗉𝗅𝗈𝗂𝗍𝖺𝗍𝗂𝗈𝗇 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗉𝖾𝗋𝗂𝗅𝗈𝗎𝗌𝗅𝗒 𝗍𝗁𝗂𝗇.
𝖠𝗌 𝗍𝗁𝖾 𝗌𝗂𝗍𝗎𝖺𝗍𝗂𝗈𝗇 𝗎𝗇𝖿𝗈𝗅𝖽𝗌, 𝗍𝗁𝖾 𝗍𝗋𝗎𝗍𝗁 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗌𝗁𝗋𝗈𝗎𝖽𝖾𝖽 𝗂𝗇 𝗆𝗒𝗌𝗍𝖾𝗋𝗒, 𝗅𝖾𝖺𝗏𝗂𝗇𝗀 𝗍𝗁𝖾 𝗉𝗎𝖻𝗅𝗂𝖼 𝗍𝗈 𝗉𝗈𝗇𝖽𝖾𝗋 𝗍𝗁𝖾 𝖺𝗎𝗍𝗁𝖾𝗇𝗍𝗂𝖼𝗂𝗍𝗒 𝗈𝖿 𝗍𝗁𝖾 𝗋𝗎𝗆𝗈𝗋𝗌. 𝖨𝗇 𝖺 𝗐𝗈𝗋𝗅𝖽 𝗐𝗁𝖾𝗋𝖾 𝖿𝖺𝗆𝖾 𝖺𝗇𝖽 𝗂𝗇𝖿𝖺𝗆𝗒 𝖺𝗋𝖾 𝗍𝗐𝗈 𝗌𝗂𝖽𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝗌𝖺𝗆𝖾 𝖼𝗈𝗂𝗇, 𝗍𝗁𝖾 𝗌𝖺𝗀𝖺 𝗈𝖿 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗂𝗌 𝖺 𝗍𝖾𝗌𝗍𝖺𝗆𝖾𝗇𝗍 𝗍𝗈 𝗍𝗁𝖾 𝗉𝗈𝗐𝖾𝗋 𝗈𝖿 𝗌𝗈𝖼𝗂𝖺𝗅 𝗆𝖾𝖽𝗂𝖺 𝗍𝗈 𝗌𝗁𝖺𝗉𝖾 𝗇𝖺𝗋𝗋𝖺𝗍𝗂𝗏𝖾𝗌 𝖺𝗇𝖽 𝖼𝗁𝖺𝗅𝗅𝖾𝗇𝗀𝖾 𝗍𝗁𝖾 𝖻𝗈𝗎𝗇𝖽𝖺𝗋𝗂𝖾𝗌 𝗈𝖿 𝗉𝗋𝗂𝗏𝖺𝖼𝗒 𝖺𝗇𝖽 𝖼𝗈𝗇𝗌𝖾𝗇𝗍.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
L𝚎aked Video Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter Telegram
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈1)
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈2)
➤ ►🌍📺📱👉 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺
𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024. 𝖳𝗁𝖾 𝗋𝖾𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗍𝗁𝖾𝗆𝖾 𝗈𝖿 𝖫𝖾𝖺𝚔𝖾𝖽 𝗍𝖺𝗉𝖾𝗌 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗎𝖻𝗌𝖾𝗊𝗎𝖾𝗇𝗍 𝖿𝖺𝗅𝗅𝗈𝗎𝗍 𝗌𝖾𝗋𝗏𝖾𝗌 𝖺𝗌 𝖺 𝗋𝖾𝗆𝗂𝗇𝖽𝖾𝗋 𝗈𝖿 𝗍𝗁𝖾 𝖿𝗋𝖺𝗀𝗂𝗅𝗂𝗍𝗒 𝗈𝖿 𝗋𝖾𝗉𝗎𝗍𝖺𝗍𝗂𝗈𝗇 𝗂𝗇 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖾𝗋𝖺. 𝖠𝗌 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾𝗌 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝖺𝗇𝖽 𝗉𝗎𝖻𝗅𝗂𝖼 𝗅𝗂𝖿𝖾 𝖼𝗈𝗇𝗍𝗂𝗇𝗎𝖾 𝗍𝗈 𝖻𝗅𝗎𝗋, 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗂𝖾𝗌 𝗅𝗂𝗄𝖾 𝖯𝗋𝗂𝗌𝗈𝗇 𝖮𝖿𝖿𝗂𝖼𝖾𝗋𝖿𝗂𝗇𝖽 𝗍𝗁𝖾𝗆𝗌𝖾𝗅𝗏𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝗆𝖾𝗋𝖼𝗒 𝗈𝖿 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖼𝗁𝖺𝗍𝗍𝖾𝗋, 𝗐𝗁𝖾𝗋𝖾 𝖺 𝗋𝗎𝗆𝗈𝗋 𝖼𝖺𝗇 𝗂𝗀𝗇𝗂𝗍𝖾 𝖺 𝖿𝗂𝗋𝖾𝗌𝗍𝗈𝗋𝗆 𝗈𝖿 𝗌𝗉𝖾𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇 𝖺𝗇𝖽 𝗃𝗎𝖽𝗀𝗆𝖾𝗇𝗍.
𝖨𝗇 𝗍𝗁𝖾 𝖾𝗏𝖾𝗋 𝖾𝗏𝗈𝗅𝗏𝗂𝗇𝗀 𝗅𝖺𝗇𝖽𝗌𝖼𝖺𝗉𝖾 𝗈𝖿 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗒 𝖼𝗎𝗅𝗍𝗎𝗋𝖾, 𝗍𝗁𝖾 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗌𝖼𝖺𝗇𝖽𝖺𝗅 𝗎𝗇𝖽𝖾𝗋𝗌𝖼𝗈𝗋𝖾𝗌 𝗍𝗁𝖾 𝗋𝖾𝗅𝖾𝗇𝗍𝗅𝖾𝗌𝗌 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗈𝖿 𝗌𝖾𝗇𝗌𝖺𝗍𝗂𝗈𝗇𝖺𝗅𝗂𝗌𝗆, 𝖺 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗍𝗁𝖺𝗍 𝗈𝖿𝗍𝖾𝗇 𝖼𝗈𝗆𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝖾𝗑𝗉𝖾𝗇𝗌𝖾 𝗈𝖿 𝗍𝗋𝗎𝗍𝗁 𝖺𝗇𝖽 𝖽𝗂𝗀𝗇𝗂𝗍𝗒. 𝖠𝗌 𝗐𝖾 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝖾 𝗍𝗁𝖾 𝖼𝗈𝗆𝗉𝗅𝖾𝗑𝗂𝗍𝗂𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖺𝗀𝖾, 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝖾𝗇𝗍𝖾𝗋𝗍𝖺𝗂𝗇𝗆𝖾𝗇𝗍 𝖺𝗇𝖽 𝖾𝗑𝗉𝗅𝗈𝗂𝗍𝖺𝗍𝗂𝗈𝗇 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗉𝖾𝗋𝗂𝗅𝗈𝗎𝗌𝗅𝗒 𝗍𝗁𝗂𝗇.
𝖠𝗌 𝗍𝗁𝖾 𝗌𝗂𝗍𝗎𝖺𝗍𝗂𝗈𝗇 𝗎𝗇𝖿𝗈𝗅𝖽𝗌, 𝗍𝗁𝖾 𝗍𝗋𝗎𝗍𝗁 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗌𝗁𝗋𝗈𝗎𝖽𝖾𝖽 𝗂𝗇 𝗆𝗒𝗌𝗍𝖾𝗋𝗒, 𝗅𝖾𝖺𝗏𝗂𝗇𝗀 𝗍𝗁𝖾 𝗉𝗎𝖻𝗅𝗂𝖼 𝗍𝗈 𝗉𝗈𝗇𝖽𝖾𝗋 𝗍𝗁𝖾 𝖺𝗎𝗍𝗁𝖾𝗇𝗍𝗂𝖼𝗂𝗍𝗒 𝗈𝖿 𝗍𝗁𝖾 𝗋𝗎𝗆𝗈𝗋𝗌. 𝖨𝗇 𝖺 𝗐𝗈𝗋𝗅𝖽 𝗐𝗁𝖾𝗋𝖾 𝖿𝖺𝗆𝖾 𝖺𝗇𝖽 𝗂𝗇𝖿𝖺𝗆𝗒 𝖺𝗋𝖾 𝗍𝗐𝗈 𝗌𝗂𝖽𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝗌𝖺𝗆𝖾 𝖼𝗈𝗂𝗇, 𝗍𝗁𝖾 𝗌𝖺𝗀𝖺 𝗈𝖿 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗂𝗌 𝖺 𝗍𝖾𝗌𝗍𝖺𝗆𝖾𝗇𝗍 𝗍𝗈 𝗍𝗁𝖾 𝗉𝗈𝗐𝖾𝗋 𝗈𝖿 𝗌𝗈𝖼𝗂𝖺𝗅 𝗆𝖾𝖽𝗂𝖺 𝗍𝗈 𝗌𝗁𝖺𝗉𝖾 𝗇𝖺𝗋𝗋𝖺𝗍𝗂𝗏𝖾𝗌 𝖺𝗇𝖽 𝖼𝗁𝖺𝗅𝗅𝖾𝗇𝗀𝖾 𝗍𝗁𝖾 𝖻𝗈𝗎𝗇𝖽𝖺𝗋𝗂𝖾𝗌 𝗈𝖿 𝗉𝗋𝗂𝗏𝖺𝖼𝗒 𝖺𝗇𝖽 𝖼𝗈𝗇𝗌𝖾𝗇𝗍.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
L𝚎aked Video Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter Telegram
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈1)
🔴📺📱 𝖢𝗅𝚒𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 👉👉 (𝖥𝗎𝗅𝗅 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖵𝗂𝖽𝖾𝗈2)
➤ ►🌍📺📱👉 𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺
𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024.𝖫𝖾𝖺𝚔𝖾𝖽 𝗏𝗂𝗋𝖺𝗅 𝗅𝗂𝗇𝗄 2024 𝖫𝖾𝖺𝚔𝖾𝖽 𝖵𝗂𝖽𝖾𝗈 𝖵𝗂𝗋𝖺𝗅 𝖮𝗇 𝖲𝗈𝖼𝗂𝖺𝗅 𝖬𝖾𝖽𝗂𝖺 2024. 𝖳𝗁𝖾 𝗋𝖾𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗍𝗁𝖾𝗆𝖾 𝗈𝖿 𝖫𝖾𝖺𝚔𝖾𝖽 𝗍𝖺𝗉𝖾𝗌 𝖺𝗇𝖽 𝗍𝗁𝖾 𝗌𝗎𝖻𝗌𝖾𝗊𝗎𝖾𝗇𝗍 𝖿𝖺𝗅𝗅𝗈𝗎𝗍 𝗌𝖾𝗋𝗏𝖾𝗌 𝖺𝗌 𝖺 𝗋𝖾𝗆𝗂𝗇𝖽𝖾𝗋 𝗈𝖿 𝗍𝗁𝖾 𝖿𝗋𝖺𝗀𝗂𝗅𝗂𝗍𝗒 𝗈𝖿 𝗋𝖾𝗉𝗎𝗍𝖺𝗍𝗂𝗈𝗇 𝗂𝗇 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖾𝗋𝖺. 𝖠𝗌 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾𝗌 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗉𝗋𝗂𝗏𝖺𝗍𝖾 𝖺𝗇𝖽 𝗉𝗎𝖻𝗅𝗂𝖼 𝗅𝗂𝖿𝖾 𝖼𝗈𝗇𝗍𝗂𝗇𝗎𝖾 𝗍𝗈 𝖻𝗅𝗎𝗋, 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗂𝖾𝗌 𝗅𝗂𝗄𝖾 𝖯𝗋𝗂𝗌𝗈𝗇 𝖮𝖿𝖿𝗂𝖼𝖾𝗋𝖿𝗂𝗇𝖽 𝗍𝗁𝖾𝗆𝗌𝖾𝗅𝗏𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝗆𝖾𝗋𝖼𝗒 𝗈𝖿 𝗂𝗇𝗍𝖾𝗋𝗇𝖾𝗍 𝖼𝗁𝖺𝗍𝗍𝖾𝗋, 𝗐𝗁𝖾𝗋𝖾 𝖺 𝗋𝗎𝗆𝗈𝗋 𝖼𝖺𝗇 𝗂𝗀𝗇𝗂𝗍𝖾 𝖺 𝖿𝗂𝗋𝖾𝗌𝗍𝗈𝗋𝗆 𝗈𝖿 𝗌𝗉𝖾𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇 𝖺𝗇𝖽 𝗃𝗎𝖽𝗀𝗆𝖾𝗇𝗍.
𝖨𝗇 𝗍𝗁𝖾 𝖾𝗏𝖾𝗋 𝖾𝗏𝗈𝗅𝗏𝗂𝗇𝗀 𝗅𝖺𝗇𝖽𝗌𝖼𝖺𝗉𝖾 𝗈𝖿 𝖼𝖾𝗅𝖾𝖻𝗋𝗂𝗍𝗒 𝖼𝗎𝗅𝗍𝗎𝗋𝖾, 𝗍𝗁𝖾 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗌𝖼𝖺𝗇𝖽𝖺𝗅 𝗎𝗇𝖽𝖾𝗋𝗌𝖼𝗈𝗋𝖾𝗌 𝗍𝗁𝖾 𝗋𝖾𝗅𝖾𝗇𝗍𝗅𝖾𝗌𝗌 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗈𝖿 𝗌𝖾𝗇𝗌𝖺𝗍𝗂𝗈𝗇𝖺𝗅𝗂𝗌𝗆, 𝖺 𝗉𝗎𝗋𝗌𝗎𝗂𝗍 𝗍𝗁𝖺𝗍 𝗈𝖿𝗍𝖾𝗇 𝖼𝗈𝗆𝖾𝗌 𝖺𝗍 𝗍𝗁𝖾 𝖾𝗑𝗉𝖾𝗇𝗌𝖾 𝗈𝖿 𝗍𝗋𝗎𝗍𝗁 𝖺𝗇𝖽 𝖽𝗂𝗀𝗇𝗂𝗍𝗒. 𝖠𝗌 𝗐𝖾 𝗇𝖺𝗏𝗂𝗀𝖺𝗍𝖾 𝗍𝗁𝖾 𝖼𝗈𝗆𝗉𝗅𝖾𝗑𝗂𝗍𝗂𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝖽𝗂𝗀𝗂𝗍𝖺𝗅 𝖺𝗀𝖾, 𝗍𝗁𝖾 𝗅𝗂𝗇𝖾 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝖾𝗇𝗍𝖾𝗋𝗍𝖺𝗂𝗇𝗆𝖾𝗇𝗍 𝖺𝗇𝖽 𝖾𝗑𝗉𝗅𝗈𝗂𝗍𝖺𝗍𝗂𝗈𝗇 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗉𝖾𝗋𝗂𝗅𝗈𝗎𝗌𝗅𝗒 𝗍𝗁𝗂𝗇.
𝖠𝗌 𝗍𝗁𝖾 𝗌𝗂𝗍𝗎𝖺𝗍𝗂𝗈𝗇 𝗎𝗇𝖿𝗈𝗅𝖽𝗌, 𝗍𝗁𝖾 𝗍𝗋𝗎𝗍𝗁 𝗋𝖾𝗆𝖺𝗂𝗇𝗌 𝗌𝗁𝗋𝗈𝗎𝖽𝖾𝖽 𝗂𝗇 𝗆𝗒𝗌𝗍𝖾𝗋𝗒, 𝗅𝖾𝖺𝗏𝗂𝗇𝗀 𝗍𝗁𝖾 𝗉𝗎𝖻𝗅𝗂𝖼 𝗍𝗈 𝗉𝗈𝗇𝖽𝖾𝗋 𝗍𝗁𝖾 𝖺𝗎𝗍𝗁𝖾𝗇𝗍𝗂𝖼𝗂𝗍𝗒 𝗈𝖿 𝗍𝗁𝖾 𝗋𝗎𝗆𝗈𝗋𝗌. 𝖨𝗇 𝖺 𝗐𝗈𝗋𝗅𝖽 𝗐𝗁𝖾𝗋𝖾 𝖿𝖺𝗆𝖾 𝖺𝗇𝖽 𝗂𝗇𝖿𝖺𝗆𝗒 𝖺𝗋𝖾 𝗍𝗐𝗈 𝗌𝗂𝖽𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾 𝗌𝖺𝗆𝖾 𝖼𝗈𝗂𝗇, 𝗍𝗁𝖾 𝗌𝖺𝗀𝖺 𝗈𝖿 𝖨𝗌𝗁𝗈𝗐𝗌𝗉𝖾𝖾𝖽𝗂𝗌 𝖺 𝗍𝖾𝗌𝗍𝖺𝗆𝖾𝗇𝗍 𝗍𝗈 𝗍𝗁𝖾 𝗉𝗈𝗐𝖾𝗋 𝗈𝖿 𝗌𝗈𝖼𝗂𝖺𝗅 𝗆𝖾𝖽𝗂𝖺 𝗍𝗈 𝗌𝗁𝖺𝗉𝖾 𝗇𝖺𝗋𝗋𝖺𝗍𝗂𝗏𝖾𝗌 𝖺𝗇𝖽 𝖼𝗁𝖺𝗅𝗅𝖾𝗇𝗀𝖾 𝗍𝗁𝖾 𝖻𝗈𝗎𝗇𝖽𝖺𝗋𝗂𝖾𝗌 𝗈𝖿 𝗉𝗋𝗂𝗏𝖺𝖼𝗒 𝖺𝗇𝖽 𝖼𝗈𝗇𝗌𝖾𝗇𝗍.

cvc

csde

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

.
.
.
.

.
.
.
.
.

cvbxcdf

@##@#@#

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
@##@#@#

.
.
@##@#@#

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
@##@#@#

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
@##@#@#

.
.
c

authors: fahmidajahan24 iqSqc mathaidim seirokmsei

repo: firebase/quickstart-android


text:
Ownersheip of current directory changes unexpectedly

When creating a job with artifacts, for example:
build:
  image: docker:stable
  script:
    - echo "Hello world" > hello.txt
  artifacts:
    paths: [hello.txt]

You can run sudo gitlab-ci-local to run you job.
Then you will have the file hello.txt under .gitlab-ci-local/artifacts/build/hello.txt which is fine.
But, you will also have hello.txt in you current dir which is strange.
Moreover, the current directory will be suddenly owen by root which will break things since you will no longer be able to create new files in the current directory.
You will not be able to also checkout to some other branch if this branch has new file since git itself will fail to create new files.
The state of my git repo before running sudo gitlab-ci-local:
drwxr-xr-x 1 user user 4096 Jun 11 23:24 ./
drwxr-xr-x 1 user user 4096 May 19 21:33 ../
drwxr-xr-x 1 user user 4096 May 19 21:33 .git/
-rw-r--r-- 1 user user  115 Jun 11 23:16 .gitlab-ci.yml

And after:
drwxr-xr-x 1 root root 4096 May 19 21:34 ./
drwxr-xr-x 1 user user 4096 May 19 21:33 ../
drwxr-xr-x 1 user user 4096 May 19 21:33 .git/
-rw-r--r-- 1 user user  115 Jun 11 23:16 .gitlab-ci.yml
-rw-r--r-- 1 root root   12 May 19 21:34 hello.txt

Running with --shell-isolation does not help.
Expected behavior
Current dir (e.g. .) will not change ownership.
And maybe even that hello.txt will only be created under the artifacts directory.
Host information
Ubuntu 20.04
gitlab-ci-local 4.32.0

gitlab-ci-local should not be run with sudo

I am probably missing something trivial.
But where running gitlab-ci-local as a non-root user I get lots of permission denied error on docker commands.
For example:
Error: command failed with exit code 1: docker image inspect docker:stable
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/images/docker:stable/json: dial unix /var/run/docker.sock: connect: permission denied```

Oh, your linux user needs to be in the docker group.
https://docs.docker.com/engine/install/linux-postinstall/

authors: firecow naweiss

repo: firecow/gitlab-ci-local


text:
Graduate hash-data-using-fnv from the nursery

Corresponding test file: https://github.com/fireeye/capa-testfiles/pull/22

still looking for a good example (this one takes a ton of resources to analyze).

authors: recvfrom williballenthin

repo: fireeye/capa-rules


text:
Fix builds

@firefly-cpp I can see in the Github actions that the 3.9 version of Python is also used. This won't work because the repo depends on 3.10 as mentioned in #16  https://github.com/firefly-cpp/sport-activities-features-gui/actions/runs/5539313014/jobs/10110146140?pr=23
Maybe we could only build for 3.10 and 3.11?

Yes

authors: alenrajsp firefly-cpp


text:
feat(client/macOS): Favorite Resources menu

- [x] Update changelog
- [x] Hook into reset button

I hooked up the reset button and tried to make it a little more idiomatic with how Swift's pub-sub stuff is supposed to work

I tried to account for the button being disabled here - https://github.com/firezone/firezone/pull/6186/files#diff-4002de56a7b4cefb9e756df6b3ace27a5ab72b522fb6117737de35edf04d7965R360
So it'll enable when you have any favorites
I'll ask ChatGPT about not dismissing the menu

I tried to account for the button being disabled here - https://github.com/firezone/firezone/pull/6186/files#diff-4002de56a7b4cefb9e756df6b3ace27a5ab72b522fb6117737de35edf04d7965R360
So it'll enable when you have any favorites

Nice, that works.

Just a little compile issue for the iOS codepath otherwise LGTM

Please merge GitHub

Actually there is a problem in it, I removed some "loading resources..." state which is necessary on iOS

authors: ReactorScram jamilbk

repo: firezone/firezone


text:
More github options (draft and target)

Following on from #8:

It'd also be nice to expose configuring whether the release is a draft, and the "commitish" used when creating a new tag. Perhaps in a future PR...

Welcome to the future :rocket:
Introduce some additional control over the GitHub Release publishing:

Allow configuring whether to keep the release as a draft.
Allow configuring the target_commitish; used if GitHub creates the
release's tag.

Note: I wasn't using my normal machine when working on this, so it's currently in untested-draft status 😃
I'm going to say this fixes #7. That issue is probably too vague to be useful going forward; the available options can always be improved.

Note: I wasn't using my normal machine when working on this, so it's currently in untested-draft status

This is now resolved. Ready for review 😃

Going to look over this PR now. Just want to confirm that this doesn't break backwards compatibility for people using GitHub publishing?
These new features only have any affect when they are explicitly configured?

Just want to confirm that this doesn't break backwards compatibility for people using GitHub publishing?
These new features only have any affect when they are explicitly configured?

For target_committish, we're changing how we use github API, but that shouldn't change behavior. Previously, you were explicitly setting the default value.
For draft, the default is still false. The only change in this scenario is that we won't explicitly set draft=false if the release is already not a draft.
I've tried to make draft promotion a directional thing; you can promote a draft release to a public release, but not the other way round. Of course, the API supports both directions, but I felt it made more sense to hide that with an abstraction.

If you are happy with everything, this should be good to go

If you are happy with everything, this should be good to go

Wonderful :heart:
Do you want the history squashed/cleaned?

If you are happy with everything, this should be good to go

Wonderful ❤
Do you want the history squashed/cleaned?

Thanks for that cleanup. I changed it, but forgot to commit. Fun part of being busy with 3 things at once :sweat_smile:
I'll do a squash and merge, so should be fine :)

I'll do a squash and merge, so should be fine :)

I ended up rebasing anyway whiel fixing up the changelog, so squashing probably isn't needed

authors: MattSturgeon hypherionmc

repo: firstdarkdev/modpublisher


text:
Flutter web support

It would be really nice if Flutter web could be supported by using platform channels and one of the js libraries available.

Great suggestion. Current development effort is at porting flutter_sodium to ffi. A platform channel implementation for the web is probably never going to happen. Once ffi is supported in Flutter Web, we'll make it happen.

authors: cbenhagen kozw


text:
MaAslin2 doesn't support interaction terms from scratch

just noticed, that MaAslin2 interaction terms have to be implemented quite hacky, I was already wondering why the output files looked like y = a + b rather than y = a * b, should be implemented and then just translated from the conditions to test form the user.

we will just expect the user to supply metadata with interaction columns that can be handled as usual

repo: fischer-hub/metagenomics


text:
fish: An error occurred while redirecting file '/Users/koofrank/.rbenv/version'

when I use fisher install plugins, then show:
fish: An error occurred while redirecting file '/Users/koofrank/.rbenv/version'
open: No such file or directory
and I use fisher any command line doesn't work, so I how to uninstall fisher and fix this problem, I use fisher uninstall not work

@phpmaple Thanks, I don't use rbenv so I have never had this problem before, but @daenney, can you share some of your rbenv wisdom with us here?

@phpmaple How do you do the rbenv stuff? With the normal rbenv integration or using the fisherman rbenv plugin?

@daenney When I use fisher install some plugins, Then show this error, and then fisher doesn't work

@phpmaple I think the folder is created when rbenv the utility, not the fisherman plugin, is installed, so if you don't have it installed, then an error will be thrown. In any case, the issue is not fisherman-specific.

@jethrokuan I uninstall  rbenv, then everything is ok

@phpmaple do you confirm that you have https://github.com/rbenv/rbenv installed?

@jethrokuan  I sure

@phpmaple Thanks! Close if your problem is resolved.

It looks like the bobthefish theme is expecting to find the global ruby version in ~/.rbenv/version but it's not there. I had this same problem too (coming from having regular rbenv+fish to fish+fisherman with the rbenv plugin). The relevant lines of fish_prompt.fish are:
   # Don't show global ruby version...
  set -q RBENV_ROOT
    or set -l RBENV_ROOT $HOME/.rbenv

  read -l global_ruby_version <$RBENV_ROOT/version

However, I did not have the version file in my ~/.rbenv folder
For me, the following resolved the issue, though I'm not sure if it's a proper solution:
rbenv version-name > ~/.rbenv/version

@rnorth I have forked, bobthefish here, I don't use it myself, but since it's quite popular I've put it there hoping to fix some of its bugs in the future. If you want to PR me there with that go ahead.

Everyone still having problems:
Replace
# Don't show global ruby version...
set -q RBENV_ROOT
  or set -l RBENV_ROOT $HOME/.rbenv

read -l global_ruby_version <$RBENV_ROOT/version

with
set global_ruby_version (rbenv global)

Per https://github.com/rnorth/bobthefish/commit/ba3b165371ff90ef916ac008a25f60f62f56c84a

The above bgbthefish fix is a package specific fix but to fix your whole RBENV system see the following:
So it looks like after you install RBENV there is no ~/.rbenv/version file. To create it just run rbenv global system . Then that file will be created and everything will work.
To change the version from system just run something like rbenv global 2.4.1 (of course after you've installed version 2.4.1 using rbenv install 2.4.1).

authors: bucaran corysimmons daenney jethrokuan michaeltarleton phpmaple rnorth

repo: fisherman/fisherman


text:
Requires go version > 1.7

Make a note somewhere that the package requires go version 1.7 or above.

related to #9.

repo: fjukstad/walrus


text:
Create a better structure for the resources

I threw this together initially off of some Google doc I mention at the top of the README. That's nice, but I'd like to eventually make it a unique thing that makes more sense. I especially don't like separating out the mobile section, but haven't put the effort into doing it another way yet. I don't know exactly when I'll close this issue, but it will be after I get some input from probably at least... a half dozen people or so? Maybe a dozen? I'm not in a rush on it - just looking for some discussion I guess.

Well, as we can see, there isn't much discussion so far. I'll close this issue and let things just work out organically. Let the record show I'm not super actively maintaining the list, but still think it's a good idea to keep it around.

repo: flamableconcrete/awesome-dnd


text:
Component.removeWhere throwing Concurrent modification during iteration Exception

Current bug behavior

In the onLoad of a component that has just been pushed to the router, I call the removeWhere() function on an unmounted component. It throws this exception:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Concurrent modification during iteration: _Set len:1.

Expected behavior

It worked fine on flame: 1.6.0
Steps to reproduce

Flutter doctor output

Output of: flutter doctor -v

More environment information

Flame version: main
Platform affected: desktop

Log information

#2      Component.removeWhere
component.dart:617
#3      Level1OpeningScene.call.hidePlaygroundAndRunButon
level_1_opening_scene.dart:44
#4      Level1OpeningScene.call
level_1_opening_scene.dart:48
#5      Level1.onLoad
level_1.dart:67
#6      Component._startLoading
component.dart:824
#7      Component._addChild
component.dart:591
#8      Component.addToParent
component.dart:562
#9      Route.didPush
route.dart:137
#10     RouterComponent.pushNamed
router_component.dart:106
#11     new HomePage.<anonymous closure>
home_page.dart:10
#12     ButtonComponent.onTapDown
button_component.dart:6

More information

@st-pasha this is a regression right, and not intentional?

@trunghq3101 I'm failing to reproduce this but I'm probably doing something wrong. Could you post a MRE for this one?

Okay, managed to do a MRE. It's not related to the router.
https://zapp.run/edit/flame-z91s06gva1t0?entry=lib/main.dart&file=lib/main.dart
import 'package:flame/components.dart';
import 'package:flame/game.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(
    GameWidget(
      game: FlameGame(children: [RemoveWhereComponent()]),
    ),
  );
}

class RemoveWhereComponent extends Component {
  @override
  Future<void> onLoad() async {
    add(Component());
    removeWhere((_) => true);
  }
}

After yet another git bisect, #2300 shows to be the culprit.

repo: flame-engine/flame


text:
Components only render after a hot reload

Description
I'm following along with the joystick example here. When I attempt a hot restart of my app, this is what I see:

Only when I trigger a hot reload do I actually see the components being rendered properly:

Development environment
Flame version: ^1.0.0-rc2

Flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 1.22.3, on Microsoft Windows
    [Version 10.0.19041.630], locale en-US)

[√] Android toolchain - develop for Android devices (Android SDK
    version 30.0.2)
[!] Android Studio (version 4.1.0)
    X Flutter plugin not installed; this adds Flutter specific
      functionality.
    X Dart plugin not installed; this adds Dart specific
      functionality.
[!] IntelliJ IDEA Community Edition (version 2019.3)
    X Flutter plugin not installed; this adds Flutter specific
      functionality.
    X Dart plugin not installed; this adds Dart specific
      functionality.
[√] VS Code, 64-bit edition (version 1.51.1)
[√] Connected device (1 available)

! Doctor found issues in 2 categories.

Runtime
This issue is related to running on which platform? (Select all that apply)

[x] Android :android:
[ ] iOS :apple:
[ ] Web :browser:

Minimal reproducible code (Required for bugs)
A minimal reproducible example can be found here.

How are you running it?

In VS Code I hit Ctrl+F5 (Run without debugging).

Do you get the same result if you just run flutter run from the terminal?

Yes. Then if I enter r (hot reload), it works as expected, but if I enter R (hot restart), the issue arises.

It seems when I enter s (take a screenshot), this has the same effect as doing a hot reload.

Changing the square from type Component to flame_forge2d's BodyComponent causes it to render from the start as expected. The problem persists for the joystick, though.

@osharaki Can you confirm is this is still happening on the more recent version of Flame? (v1.0.0-rc4)
Also, I noticed that you are adding your components on the constructor of your game, you could also try to add them on the onLoad method, like
  @override
  Future<void> onLoad() {
    joystick.addObserver(player);
    add(player);
    add(joystick);
  }

When I upgrade to Flame 1.0.0-rc4, runApp(MainGame().widget) now causes an error:

The getter 'widget' isn't defined for the type 'MainGame'

dependencies:
  ...
  flame: ^1.0.0-rc4

@osharaki you have to wrap it in a GameWidget.
runApp(
  GameWidget(
    game: MainGame()
  )
);

@osharaki Can you confirm is this is still happening on the more recent version of Flame? (v1.0.0-rc4)
Also, I noticed that you are adding your components on the constructor of your game, you could also try to add them on the onLoad method, like
  @override
  Future<void> onLoad() {
    joystick.addObserver(player);
    add(player);
    add(joystick);
  }

After upgrading and applying @spydon's comment, the behavior still hasn't changed. However, when I add the components in onLoad() instead, as @erickzanardo suggested, it works fine. I did need to add return super.onLoad();, though. So:
@override
  Future<void> onLoad() {
    joystick.addObserver(player);
    add(player);
    add(joystick);
    return super.onLoad();
  }

In fact, onLoad() also fixes the issue on 1.0.0-rc2. So it seems this was simply a matter of incorrectly adding the components all along?

You shouldn't need to return 'super.onLoad()' that probably was required because you didn't added the 'async' keyword to your method declaration.
Since the use of the onLoad method solved the issue, I am gonna close this, feel free to add more questions here if needed.

authors: erickzanardo osharaki spydon


text:
Fix CH configs

Upgrade clickhouse and add memomy limits

Done in #137

authors: diafour gyrter

repo: flant/loghouse


text:
password for webinterface

Hi,
is there any option to set a username/password for the webinterface?

duplicate of #11

authors: pashcovich skapytek

repo: flant/ovpn-admin