text:
Update client3:async-http-client-backend-cats, ... to 3.3.17

Updates

com.softwaremill.sttp.client3:async-http-client-backend-cats
com.softwaremill.sttp.client3:circe
com.softwaremill.sttp.client3:core

from 3.3.16 to 3.3.17.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.client3" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #47 (a55f8ff) into master (1fec94e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #47   +/-   ##
=======================================
  Coverage   92.13%   92.13%
=======================================
  Files          35       35
  Lines         267      267
  Branches        2        2
=======================================
  Hits          246      246
  Misses         21       21

Continue to review full report at Codecov.

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

authors: codecov-commenter fgrutsch

repo: fgrutsch/emergence


text:
global search function for project managers

hi,
this is a cool project and tool, thanks!
is it possible to extend the search function to all projects for the role "project manager"?

With the current development version, you can search globally in all projects you are member.

source: gharchive/issue

authors: fguillot sebaohligx

repo: fguillot/kanboard

license: mit

license_type: permissive

license_source: bigquery


text:
feat: Enabling support for EC2 authentication (and others)

By making access key and secret optional, the AWS SDK will default to
looking for credentials in known locations, one of which is EC2
metadata (really useful for EC2/IAM configs).
New order of credential loading:

Loaded from AWS Identity and Access Management (IAM) roles for Amazon EC2 (if running on Amazon EC2)
Loaded from the shared credentials file (~/.aws/credentials)
Loaded from environment variables
Loaded from a JSON file on disk
Loaded from your module's config

More detail here

I'm assuming all the tests will fail because there are no credentials passed during external PR builds.  But this should not have affected any tests.

@stjohnjohnson I know, the change looks good to me. Will merge it tomorrow.

Published as v3.1.0 on npm. Thank you! 🎉

source: gharchive/pull-request

authors: fhemberger stjohnjohnson


text:
fixed URL of popup to point

The URL in the popup should point to https://github.com/fhstp/CoinEater/, not to https://github.com/keraf/NoCoin.

Thanks!

authors: lutzhorn tobiasdam

repo: fhstp/CoinEater

license: MIT

license_source: github-api


text:
Update angle to be mod 2

  # Base function to update angle
  function update_ϕ(ϕ,Sx,Sz)
      return (-1)^Sx*ϕ + π*sum(Sz)
  end

Current phi update angle, correct sum to be mod 2 instead of straight sum.

Dones


text:
Native DatePicker: min and max HTML attribute shouldn't contain time

Description
Setting the minDate()/maxDate() restrictions on a native Date input doesn't restrict the selection in the GUI. Currently, the min/max attribute on the HTML tag contains the time, even when one is just using the DatePicker (not DateTimePicker). According to the HTML docs, a date input should only have the date and ommit the time.
DatePicker::make('Native Date Picker')
  ->minDate(now()->subDays(3))
  ->maxDate(now()->addDays(3))

Produces:
<input [...] max="2024-03-26 18:14:56" min="2024-03-20 18:14:56" type="date" [...]>

But should produce:
<input [...] max="2024-03-26" min="2024-03-20" type="date" [...]>

The native date time input works fine. But according to HTML standard, the space between the date and time should be an T. But Chrome also accepts the space. And the GUI only restricts the date selection, not the time selection. But I guess thats regular chrome behavior.
The JS date and date time picker work fine as expected.
Visual changes

Before (tested with Chrome 123 on Mac/Safari 17.2.1 on Mac/Firefox 124 on Mac):

After:

Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

Hey Dan, thanks for reviewing my PRs. What can I do, that you don't have to rewrite my PRs completely? ;)

There's not some general tip I can write that will improve them. I do this to most PRs. There's just some insights that most people don't have that are a little specific to people who have built so much of the framework. In this case, I didn't like the original implementation since I thought it was fragile - if the type of the max date / min date variable changed in the future away from a string then substr wouldn't really work, and if the date format changed to include extra characters then it also would break as the substr indexes would be out. I just changed it to make it so that it hopefully wouldn't break in these cases, to ease maintenance in the future.
With the other PR, there were other places that also needed the implementation. I also copied the implementation from the text column/entry instead of introducing Collection::wrap() for consistency. I didn't like that a object collection was being created in all cases even though we didn't use any of the collection methods, it felt like an inefficiency.

authors: buddhaCode danharrin

repo: filamentphp/filament


text:
feat: updated site logo

Updated site logo.

Looks good on my end from a design standpoint. Responsive works nicely as well!

authors: svvimming tjsMck

repo: filecoin-project/ecodash


text:
Client Allocation Request for:

Client Allocation Questions
Core Information

Name:
Website / Social Media:
Region: North America
DataCap Requested: 1TiB
Addresses to be Notarized:
Notary Requested: s0nik42

@jessie8o8 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

This user’s identity has been verified through filplus.storage


text:
Head input chain offset

When a participant starts an f3 instance, it needs to determine whether it wants its proposal to contain from baseChain up to the head input chain it locally keeps in EC, or some prefix of it (i.e. offset it by some epochs). Although this may delay latency on the head tipset, it helps reduce latency and reach agreement faster on the EC instance. This is closely related with #173.

In pair with decision on #173 to wait for 2 epochs from the timestamp on the latest finalized epoch, the participant sets as proposal for the new f3 instance the following:

Let $baseChain$ represent the finalized chain up until the latest finalized f3 instance.
Let $ECChain$ represent the current heaviest EC chain according to the participant (that extends $baseChain$ by design)
Let $e'$ be the epoch at which the participant is starting the new f3 instance (following decision on #173 , $e' >= baseChain.head().epoch + 2$).

Then:

If ECChain.head().epoch < e', participant sets its proposal to ECChain
If ECChain.head().epoch = e', participant sets its proposal to ECChain[-1] (remove the head tipset, from the current epoch e')
ECChain.head().epoch cannot be > e' by design (e' is the current epoch)

I think this is done: it is specified in the FIP so the decision is make. @Kubuxu do you need this issue open to track some implentation task?

We don't have the head offset currently. Looking at the FIP pseudocode, it appears "delete the head always", as I'm assuming CurrentEpoch() is the epoch of the chain head and collecting the chain for HeaviestUnfinalizedChain will return that head.

It's difficult to be precise with language here. I had interpreted the FIP's use of CurrentEpoch() to mean the one for which new blocks are currently being transmitted but a tipset could not yet be confirmed by a subsequent block pointing to it. This is why it is always deleted.
What exactly do you mean by the epoch of the chain head? Is it the epoch of the blocks currently being proposed? Or the epoch of the tipset to which the most recent possible block points?

What you wrote here makes sense.

authors: Kubuxu anorth ranchalp


text:
option to turn off animation

What feature or improvement do you think would benefit Files?
There should be an option to disable animation in the application
as you can see when you open the application it takes some time to load because of the animation | preview.
my windows animation is turned off completely | preview.
Requirements

we just need an option for turning out animation completely in the app

Files Version
Version: 2.3.12.0 OS Version: 10.0.19044.2130
Windows Version
Edition	Windows 10 Pro Version	21H2 Installed on	10/9/2022 OS build	19044.2130 Experience	Windows Feature Experience Pack 120.2212.4180.0
Comments
No response

Animations can be turned off from the settings app in Windows.

https://imgur.com/a/5eXhA1l
mine is tuned off but the application still shows the animation!

authors: nzarbayezid yaichenbaum

repo: files-community/Files


text:
random error message

Description
2023-02-17 00:03:34.8979|ERROR|AppUnhandledException|The server threw an exception. (0x80010105 (RPC_E_SERVERFAULT))
System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (0x80010105 (RPC_E_SERVERFAULT))
2023-02-17 00:03:41.4819|INFO|OnLaunched|App launched. Launch args type: ToastNotificationActivatedEventArgs
Steps To Reproduce
randomly
Steps to fix

eg. Fix crash that occurs when...
eg. Correct action happens when clicking...

Files Version
any last dev or stable version, any language pack
Windows Version
Windows 11 Pro 22H2 	22621.1265  Windows Feature Experience Pack 1000.22638.1000.0
Log file
2023-02-17 00:01:47.3772|INFO|IsRunningOnArm|Running on ARM: False
2023-02-17 00:03:34.8979|ERROR|AppUnhandledException|The server threw an exception. (0x80010105 (RPC_E_SERVERFAULT))
System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (0x80010105 (RPC_E_SERVERFAULT))
2023-02-17 00:03:41.4819|INFO|OnLaunched|App launched. Launch args type: ToastNotificationActivatedEventArgs
2023-02-17 00:03:41.7914|INFO|UpdateDrivesAsync|Adding cloud provider "Yandex Disk" mapped to C:\Users\Админис\YandexDisk-izpitera-ru
2023-02-17 00:03:41.8117|INFO|GetDrivesAsync|Drive added: C:, Fixed
2023-02-17 00:03:41.8634|INFO|GetDrivesAsync|Drive added: D:, Fixed
2023-02-17 00:03:41.8852|INFO|GetDrivesAsync|Drive added: E:, Fixed
2023-02-17 00:03:41.9007|INFO|GetDrivesAsync|Drive added: F:, Fixed
2023-02-17 00:03:41.9183|INFO|GetDrivesAsync|Drive added: Z:, Network
2023-02-17 00:03:43.1555|INFO|CheckForUpdates|SIDELOAD: Checking for updates...
2023-02-17 00:03:43.8556|INFO|CheckForUpdates|SIDELOAD: Current Package Name: FilesPreview
2023-02-17 00:03:43.8590|INFO|CheckForUpdates|SIDELOAD: Remote Package Name: FilesPreview
2023-02-17 00:03:43.8612|INFO|CheckForUpdates|SIDELOAD: Current Version: 2.4.36.0
2023-02-17 00:03:43.8635|INFO|CheckForUpdates|SIDELOAD: Remote Version: 2.4.36.0
2023-02-17 00:03:43.8660|WARN|CheckForUpdates|SIDELOAD: Update not found.

Merging with #11149


text:
Feature Request: "Select All" Checkbox next to "Name" column in Details Layout

What feature or improvement do you think would benefit Files?
Add a "Select All" checkbox next to the "Name" column in the Details Layout.
I know there's already a "select all" button in "Selection options", but the space next to the Name column is currently unused and most programs have a similar checkbox there.
The space I'm talking about:

In Windows Explorer:

Requirements

Add a checkbox next to the Name column in the Details Layout

Files Version
3.2.3.0
Windows Version
10.0.26058.1400
Comments
No response

Thank you for your feedback, we're tracking this feature request in #9528. Please add a comment to that issue to be notified when it's resolved.


text:
Experimental Features

Description
once the experimental feature turn on then toggle of that feature couldn't turn off please solve this bugs soon.thank you
Steps To Reproduce
No response
Expected behavior
when i turn off that toggle then one registry warming popup and click on yes or no again by again but notting happen.
Files Version
Version: 2.0.34.0 OS Version: 10.0.22000.376
Windows Version
Edition	Windows 11 Pro Version	21H2 Installed on	2021-11-01 OS build	22000.376 Experience	Windows Feature Experience Pack 1000.22000.376.0
Relevant Assets/Logs
.

You can revert to Explorer by running "UnsetFilesAsDefault.reg" from here.


text:
Middle click actions on navigation bar

What's the Problem?
There is no good solution to clone the current tab right now.
Also there are no middle-click functionalities for actions like back, forward, refresh, layer up.
Solution/Idea
Middle-clicking the layer-up-arrow should do the same as middle clicking the directory one layer above in the file path field.
It should open the directory one layer above the current one in a new tab.
Middle-clicking the back-arrow should open the previous directory in a new tab.
Middle-clicking the forward-arrow should open the next directory in a new tab.
Middle-clicking the refresh-arrow should clone the current tab to a new tab.
This could also be expanded with CTRL + middle-click functionality to do the same stuff but in a new window instead of a tab.
Alternatives
The only thing that I know of is middle-clicking the second last directory in the file path to open it in a new tab so the arrow-up middle-click functionality would be covered.
The rest would be nice quality of life.
Priorities
Could
Files Version
2.1.0.0
Windows Version
Windows 11 Pro 21H2 22000.434
Comments
No response

This world be really useful!

Wasn't really the point of my feature request but that's useful at least.

authors: Conquesttintin DAmNRelentless


text:
Can't Drag & Drop

Description
https://cdn.discordapp.com/attachments/725514946112127057/933000056833998878/Desktop_18-01-2022_15-07-19.mp4
As you can see in the recording, I can't drag & drop a file, whatever the extention is. I can drag and drop out of the explorer, but not into it.
PM if more informations required at MitralyxL#1337
Steps To Reproduce

Take a random file
Open an explorer window
Drag and drop the file INTO the explorer window

Expected behavior
I simply expect the file to transfer to the destination window.
Files Version
Version : 2.1.2.0 OS Version: 10.0.22000.434
Windows Version
Windows 11 21H2 22000.434
Relevant Assets/Logs
debug_fulltrust.log
debug.log
https://cdn.discordapp.com/attachments/725514946112127057/933000056833998878/Desktop_18-01-2022_15-07-19.mp4

Are you able to drop on the folders on the sidebar or the file list or the navigation bar? Is the issue only dropping in the blank space?

Merging with #6941

authors: ArthurMTX gave92 yaichenbaum


text:
Fix : Fixed a bug where no warning would be shown when renaming an item that requires TrustedInstaller

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #8326

Known bugs

There are two cases where Edit permissions doesn't work:

You start to rename an item on one page, and then (somehow) navigate to another before clicking Edit permissions
You open the properties window for that item, navigate to a different page and then rename it

The issue behind these bugs is that the Properties window depends on IShellPage and ListedItem, while RenameAsync doesn't. To get those values, I'm using ContentPageContext, but this doesn't work if you change the working directory while renaming. Do you have any ideas on how I can fix this without messing up the code too much?
Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[x] Did you implement any design changes to an existing feature?

[x] Was this change approved?

[x] Are there any other steps that were used to validate these changes?

Navigate to C:\Windows\Ssytem32
Try to rename any file/folder (such as Utilman.exe)
When the warning is shown try clicking both Ok and Edit permissions

Screenshots

Trusted Installer is just an example, I imagine there can be others cases as well.

Trusted Installer is just an example, I imagine there can be others cases as well.

I guess it can only be either TrustedInstaller or SYSTEM. Is there any other account with greater privileges than admin?
Anyway, I need to find a way to distinguish the two cases since they both return code 0x80270021 (COPYENGINE_E_ACCESS_DENIED_SRC)

I think we should also extended this to other operations such as Delete

Is there any other account with greater privileges than admin?

It could also be a non admin account

It could also be a non admin account that needs access from admin.

In that case there's the UAC modal

I tried to find a way to distinct between TrustedInstaller and SYSTEM, but got nowhere.
Using FileSecurityHelpers.GetAccessControlList() and FileSecurityHelpers.GetOwner(), I can't get anything but generic errors or exceptions (e.g. "Access denied", "NullReference" caused by source.ItemType or by GetOwner()).
I can either use a more general string (e.g. "requires higher permissions") or try again, but in this case I may need some help

I can either use a more general string (e.g. "requires higher permissions")

I think that's fine


text:
Code Quality: Remove ini-parser-netstandard dependency

Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as Ready to build. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.

Closes #15650

Steps used to test these changes
Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.

Open Files app

How come? The same name in different sections seems not to be supported. We might want, but as of now we don't need to go such far.

The same name in different sections seems not to be supported.

That should not be the case. In any case, I think we should define a section to avoid affecting other apps.

Steps used to test these changes

Were these changes tested? I'm trying to test them on my side but it doesn't work.

The same name in different sections seems not to be supported.

That should not be the case. In any case, I think we should define a section to avoid affecting other apps.

@hishitetsu I misunderstood what Wikipedia says and you're right. Now that the PR is ready again.

There seems to be no functional problems. My remaining concern is this. https://github.com/files-community/Files/pull/15654#discussion_r1663302746


text:
componentDisplayMode crashes if only customText is set

If I set none or all 3 properties it works fine. But if I only set 'customText' I get a crash. This was surprising since all three options have defaults.
componentDisplayMode={{
  customText: "Image",
}}

There was a 'static defaultProps' which was checking only if property exists or not.
Fixed since 3.1.0

authors: AndrzejSala mpoisot

repo: filestack/filestack-react


text:
Standard conventions for imports and copyright headers

I've been tending to leave stuff as I find it or make it match its neighbors, but there's some inconsistency here—some files have copyright headers, others don't, some have imports divided into sections, others alphabetize their imports, etc.
My vote would be to remove all copyright headers (the project-level license is plenty) and include authorship information in the Scaladoc when needed. I also prefer plain old alphabetization for imports, but can live with other conventions.

That's an awesome idea!
Authorship information is also available per each source file on Github.

Yeah, I don't think we need it in the file, but if some contributors did want that, the Scaladoc annotation would probably be a better place than a contributors list in the header.

Happy to help with this. Just a quick clarification: do we want to move the contributors to an @author annotation by default? Or just remove the header and contributors for now and add them to the Scaladoc as needed?

One possibility instead of @author is a CONTRIBUTORS file like finagle has (https://github.com/twitter/finagle/blob/master/CONTRIBUTORS).

I think it's not necessary to have CONTRIBUTORS file. Everyone who's contributed is listed on Github.

I'm fine with that. Did we settle on an order for imports? I prefer alphabetization too, but I'm open to other conventions.

I'm on board with simple alphabetical order to imports.

This is not fixed yet. We still have to decide what to do with imports. I just checked and it looks like scalastyle doesn't really have a rule for that.

authors: rpless travisbrown vanyacohen vkostyukov

repo: finagle/finch


text:
Added Jump API to providers

#3 Have'nt had the chance to proper test, as the APIs does'nt seem to have any available bikes at the momemt, let me know if it needs further changes.

Looks good :) I'll merge it in

authors: finncodes zjael

repo: finncodes/openscootermap

license: ISC


text:
DevOps Mutualisation : Whilst building effective group communication, what are people comfortable sharing in public?

Description
This issue has been created to discuss how to provide a mechanism for continuous communication for DevOps Mutualization as Slack is not regulated and might not be the right place for team members to communicate outside the FINOS initiative.
Prior to solutions being explored, the question "What are people comfortable sharing in public?" has been asked to the group for feedback in the comments of this issue.
DevOps Mutualization Meeting Notes
Date and Time : Thursday 30th July @ 1pm ET / 6pm BST - https://github.com/finos/community/issues/52#issuecomment-669343645

The question of how the group communicates will be taken into the next meeting as a topic of discussion with the question "What are people comfortable sharing in public?" asked in advance.

This issue has been resolved through the use of GitHub Team Discussions. Please use the instructions below to engage and join the DevOps Mutualization conversation.
As taken from ...
https://github.com/finos/devops-mutualization/edit/master/docs/Discussions.md
DevOps Mutualization SIG Discussions
The DevOps Mutualization SIG uses GitHub Team Discussions that are only visible to members of the FINOS GitHub Organisation, with optional private discussions available to those who are part of the devops-mutualization-participants team.
GitHub Team Discussions augment the use of GitHub Issues in this repository by allowing both public and private discussions as part of the FINOS GitHub Organisation.
How to Participate in DevOps SIG Discussions

In order to collaborate in FINOS Team Discussions, you must have a GitHub Account and have signed a FINOS Contributor License Agreement (CLA). Please email help@finos.org for help and more information.
If you're are not a member of the FINOS GitHub Organisation, email help@finos.org and request an invitation to join from the FINOS team.
If you are a member of the FINOS GitHub Organisation, please email Amol Shukla or Anders Wallgren so they can add you to the devops-mutualization-participants team.
Once you are a member of the devops-mutualization-participants team you should be able to partake in public and private DevOps Mutualization SIG Discussions.

repo: finos/devops-mutualization


text:
DocumentReference.create() keeps trying to create an already existing document, leading to a hang in functions

[READ] Step 1: Are you in the right place? ✅
[REQUIRED] Step 2: Describe your environment

Operating System version: MacOS 14.5
Firebase Product: functions, firestore
Node.js version: v18.20.3
NPM version: 10.7.0

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:

Create a new demo project via firebase init
Select functions and firestore
Run emulators through: firebase emulators:start --inspect-functions --project demo-me
Visit http://127.0.0.1:5001/demo-me/us-central1/runMeTwice in browser
Refresh

Relevant Code:
{
  "name": "functions",
  "description": "Cloud Functions for Firebase",
  "engines": {
    "node": "18"
  },
  "main": "index.js",
  "dependencies": {
    "firebase-admin": "^12.1.0",
    "firebase-functions": "^5.0.0"
  },
  "private": true
}

//@ts-check
const { onRequest } = require("firebase-functions/v2/https");
const logger = require("firebase-functions/logger");
const { firestore, initializeApp } = require("firebase-admin");
const { initializeFirestore } = require("firebase-admin/firestore");

/** @type {firestore.Firestore} */
let _defaultFirestore;
function defaultFirestore() {
    return _defaultFirestore ??= initializeFirestore(initializeApp(), {
        preferRest: true,
    })
}

exports.runMeTwice = onRequest(async (_, res) => {
    try {
        const doc = defaultFirestore().collection("test").doc("smt");
        await doc.create({});
        logger.log("Created");
    } catch (error) {
        logger.log(error);
    } finally {
        res.end();
    }
});

Expected behavior
The second time the function is ran, it should fail.
Actual behavior
The first time the function is run the document is created. The second time, the function never completes.
Additionally, attaching to the node process, it seems the creation process keeps getting retried even though it should fail.

In addition, performing this in a transaction will eventually fail and terminate the function.
However, attaching the debugger it shows, the transaction is still attempted multiple times.
This seems incorrect.
exports.runMeTwice = onRequest(async (_, res) => {
    try {
        const firestore = defaultFirestore();
        await firestore.runTransaction(async (txn) => {
            txn.create(firestore.collection("test").doc("smt"), {});
        })
        logger.log("Created");
    } catch (error) {
        logger.log(error);
    } finally {
        res.end();
    }
});

Hi @jellynoone ,
I will take a look at this and get back to you.

@jellynoone
While investigating, there are some things can be tried as a workaround:

Use set() instead
DocumentReference.create() calls bulkWriter internally. You can try to use bulkWriter and config the retry option

I'm testing this against the emulator. Did you try with the provided example?
I think the preferRest: true, configuration option might be significant.

@cherylEnkidu Did you perhaps have a chance to reevaluate based on the additional information provided?

Hi @jellynoone ,
I will continue the investigation this week, and I will reply the ticket as soon as I get any updates :)

Hi @cherylEnkidu were you able to take a look?

Hi @jellynoone ,
Thanks for the waiting. I tried the same code you provided, but the process never hangs. Could you please provided a small repo app?

Attaching a small repro app.
export.zip
Additional notes:

The problem reproduces in:

emulated environments
against the live Firestore instance being called locally

The function has to be called two times

The first call will complete normally
The second call will hang

@cherylEnkidu Attaching a video of the bug being reproduced.
https://github.com/firebase/firebase-admin-node/assets/77585130/d4bba6c7-4385-4165-bf79-3c677dce04ed
In the video I'm using firebase emulators:start --project demo-me to start the emulators without needing a real project. However, I tested this with a live Firestore instance and emulated functions and observed the same bug.
In addition, in the video I'm calling curl instead of the browser to make the process more streamlined.

@cherylEnkidu Do you need more information or anything else? Were you able to reproduce the issue?

Hi @jellynoone ,
Thank you for your inputs! I will take a look at the code provided and get back to you.

Hi @jellynoone ,
I have successfully reproduce the issue, while investigating, you may consider removing preferRest: true to always use grpc. I will get back to you once I have more info.

@cherylEnkidu Thank you for getting back to me. Unfortunately disabling preferRest: true is not an option as that would increase the function's cold start. The other alternative I found is to always manually check for the existence of the document before calling create.
While the issue can be circumvented, I can imagine that people who don't do this manually and rely on the firebase-admin package to fail when an existing document is attempted to be created again, and allow user supplied ids, might be exposing themselves to a resources exhaustion attack. So to me this seems like a high priority issue.

When using preferRest, the Firestore endpoint is returning status code 409 when the document already exists. It's also returning 409 when the server aborted the request. The SDK cannot distinguish these two conditions and it is retrying the request, which is appropriate for aborted requests. Unfortunately, I don't have a workaround for this at the moment, other than what you've suggested. We are looking into it.
Googlers see b/352387470

@MarkDuckworth Out of curiosity, couldn't the firebase_admin package use the status code returned in the response to further deduce if the request is retriable?
Attaching the debugger, the raw response received looks something like this:
'{"error":{"code":409,"message":"entity already exists: EntityRef{partitionRef=dev~demo-me, path=test\\/smt}","status":"ALREADY_EXISTS"}}'
This is where the exception is first thrown by the google-gax package at: build/src/fallbackRest.json#decodeResponse.
When this raw response is processed however, the status is dropped from the error object. However, all the information seems to be sent already it is just that the GoogleError.parseHttpError doesn't expose it.

authors: MarkDuckworth cherylEnkidu jellynoone

repo: firebase/firebase-admin-node


text:
Report error when streaming loses connection. #179

After the last commit, do we have a function to detect when streaming losses connection? Or Shall I execute Firebase.stream(path) in the loop ?
Thanks,
@ed7coyne @proppy

I need solution for same issue.

@proppy so if the stream has an error it will restart automatically?

No!!!! Stream will not restart automatically, if any non stream command like "Firebase.setInt(path);" will executed in the program it restart. Also during this command if the internet connection is not found whole program will slow down and it continuously forcing to execute this command only, why program slow down ????????

i was trying to resolve this issue but i failed!!!!!!

Is there a way to detect that the stream connection (socket) has been closed? I am willing to investigate and solve this issue, but any feedback / help / hints are welcome

i am using mills and counting continuously after each 31 sec. whether stream running or not. i get an information about status of stream whether it is running or not. and if any non stream command like "Firebase.setInt(path);" will executed in the program it restart stream.

I think this should be fixed with #356? can you test?

SDK:2.2.1(cfd48f3)/Core:win-2.5.0-dev/lwIP:2.0.3(STABLE-2_0_3_RELEASE/glue:arduino-2.4.1-10-g0c0d8c2)/BearSSL:94e9704
Still having an issue when Stream looses connection when router switches between LTE and 3G described here:
https://github.com/firebase/firebase-arduino/pull/356
As a workaround I'm using an errorCounter and reboot my esp if it gets anormous:
if (Firebase.failed()) {
   Serial.println("streaming error");
   Serial.println(Firebase.error());
   errorCounter++;
 }
if (errorCounter > 10) reset_func();

authors: MrSuhov hixfield maherahmed milinddhanke proppy

repo: firebase/firebase-arduino


text:
10.22.1 not available on Cocoapods

Description
The latest version available on Cocoapods is still 10.22.0
Reproducing the issue
No response
Firebase SDK Version
10.22.1
Xcode Version
15.0.1
Installation Method
CocoaPods
Firebase Product(s)
Crashlytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

10.22.1 was a limited patch release that only changed the FirebaseAnalyticsOnDeviceConversion pod.
Details at https://firebase.google.com/support/release-notes/ios

repo: firebase/firebase-ios-sdk


text:
Missing symbols on Build

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.3.1
Firebase SDK version: 6.18.0
Firebase Component: Analytics
Installation method:Zip file

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:

Manually install firebase from the zip.

Build it.

Output:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_FIRHeartbeatInfo", referenced from:
      objc-class-ref in FirebaseInstallations(FIRInstallationsAPIService.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

As already reported on #4800, we get linking errors since trying to update above 6.14.
I could not reproduce it on a fresh project, and it seemed to work for me once, but it popped up again.
I stripped down the existing project, keeping the build error.

just run sh setup.sh to dl the zippped firebase

@nidegen Could you make sure you remove all old Firebase framework versions and copy the new ones? Also you may clean the build folder and Derived Data folder in case the first doesn't help.
From you particular error it looks like your project picks  an old FirebaseCore.framework version.

That is what i was thinking. I have tried those things, but let me double check. Maybe search paths were wrong.

yep, there was the old version in the carthage build folder 😖 thanks for the trigger:D

I'm glad it was fixed for you!

authors: maksymmalyhin nidegen


text:
Make missing analytics a warning instead of error

To reduce confusion on questions like https://stackoverflow.com/questions/51627290/5-4-1-firebase-corei-cor000022-firebase-analytics-is-not-available/51737237

@baolocdo Does this work?


text:
Move FIRInstanceIDInstanceProvider into the private header file for components to look up an instance of FIRInstanceID

Move FIRInstanceIDInstanceProvider into the private header file for components to look up an instance of FIRInstanceID. This is needed when a components loads with componentsToRegister and depends on instanceID when initializing.

This change is no longer needed with a fix Core initialization (https://github.com/firebase/firebase-ios-sdk/pull/4030)


text:
Only fail a StorageTask once

This should fix an occasional flake I was seeing in testUnauthenticatedSimpleGetDataTooSmall where the expectation was getting fulfilled twice.

LGTM, please wait for @schmidt-sebastian's review

@schmidt-sebastian I changed it to a completed state test and also added it to the other locations in the file. PTAL


text:
This is an open source project for Cloud Firestore.

Link to project (GitHub): https://github.com/1amageek/Ballcap-iOS
Describe the project in 2-3 sentences: Ballcap is a database schema design framework for Cloud Firestore
Why would Firebase developers be interested in this project?: Cloud Firestore is a great schema-less and flexible database that can handle data. However, its flexibility can create many bugs in development. Ballcap can assign schemas to Cloud Firestore to visualize data structures. This plays a very important role when developing as a team.
Have you added a .opensource/project.json file to your site: YES
Examples:

https://github.com/invertase/react-native-firebase/blob/master/.opensource/project.json
https://github.com/sgarciac/fuego/blob/master/.opensource/project.json
https://github.com/firebase/emberfire/blob/master/.opensource/project.json

I believe this has already been addressed in another issue, so closing this.  Thanks for adding your project!


text:
java.lang.NullPointerException: Attempt to read from field 'int com.android.okio.Segment.limit' on a null object reference

Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'int com.android.okio.Segment.limit' on a null object reference
at com.android.okio.OkBuffer.write + 574(OkBuffer.java:574)
at com.android.okio.OkBuffer.read + 610(OkBuffer.java:610)
at com.android.okio.RealBufferedSource.read + 56(RealBufferedSource.java:56)
at com.android.okhttp.internal.http.HttpConnection$FixedLengthSource.read + 469(HttpConnection.java:469)
at com.android.okhttp.internal.Util.skipAll + 227(Util.java:227)
at com.android.okhttp.internal.http.HttpConnection.discard + 239(HttpConnection.java:239)
at com.android.okhttp.internal.http.HttpConnection$FixedLengthSource.close + 491(HttpConnection.java:491)
at com.android.okio.RealBufferedSource.close + 204(RealBufferedSource.java:204)
at com.android.okio.RealBufferedSource$1.close + 187(RealBufferedSource.java:187)
at com.google.android.gms.internal.firebase_messaging.zzk.zza + 4(zzk.java:4)
at com.google.firebase.messaging.zzd.close + 37(zzd.java:37)
at com.google.firebase.messaging.zzc.zzas + 51(zzc.java:51)
at com.google.firebase.messaging.FirebaseMessagingService.zzd + 59(FirebaseMessagingService.java:59)
at com.google.firebase.iid.zzb.run + 2(zzb.java:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker + 1112(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run + 587(ThreadPoolExecutor.java:587)
at com.google.android.gms.common.util.concurrent.zza.run + 6(zza.java:6)
at java.lang.Thread.run + 818(Thread.java:818)

implementation 'com.google.firebase:firebase-core:16.0.9'
implementation 'com.google.firebase:firebase-messaging:18.0.0'

Related: https://github.com/square/okio/issues/79
Still can't reproduce the issue, however our Crashlytics shows 4% crash sessions. All the session are in the background, different Android API and devices.

Some issue with;
implementation 'com.google.firebase:firebase-core:17.1.0'
implementation 'com.google.firebase:firebase-messaging:20.0.0'

Its happen only when you add image in notification

Can you give some more information on how to reproduce this issue?

Seems like any push notification from Firebase throws this. Also after dependencies update.
The strange thing I do not receive fatal crash, notification works fine and received by service properly. So its encountered as crash on Crashlytics, but it does not fatal crash for the app.
Steps to reproduce for me:

Install Firebase Messaging and Firebase Crashlytics.
Send simple messsage or message with payload
Watch crashlytics encounters this as fatal crash.

I filed issue https://github.com/firebase/firebase-android-sdk/issues/709
What's interesting is that I'm getting this error instead of the one I filed after reducing the image size to around 50KB with a width of 480px.
Error:

Fatal Exception: java.lang.NullPointerException
Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
com.android.okhttp.okio.Buffer.write

Here's my stack track:
com.android.okhttp.okio.Buffer.write (Buffer.java:1182)
com.android.okhttp.okio.Buffer.read (Buffer.java:1221)
com.android.okhttp.okio.RealBufferedSource.read (RealBufferedSource.java:55)
com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.read (Http1xStream.java:393)
com.android.okhttp.internal.Util.skipAll (Util.java:159)
com.android.okhttp.internal.Util.discard (Util.java:141)
com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.close (Http1xStream.java:410)
com.android.okhttp.okio.RealBufferedSource.close (RealBufferedSource.java:396)
com.android.okhttp.okio.RealBufferedSource$1.close (RealBufferedSource.java:384)
com.google.android.gms.internal.firebase_messaging.zzk.zza (com.google.firebase:firebase-messaging@@20.0.0:4)
com.google.firebase.messaging.zzj.close (com.google.firebase:firebase-messaging@@20.0.0:38)
com.google.firebase.messaging.zzd.zza (com.google.firebase:firebase-messaging@@20.0.0:51)
com.google.firebase.messaging.FirebaseMessagingService.zzc (com.google.firebase:firebase-messaging@@20.0.0:60)
com.google.firebase.messaging.zze.run (com.google.firebase:firebase-messaging@@20.0.0:2)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
com.google.android.gms.common.util.concurrent.zza.run (Unknown Source:6)
java.lang.Thread.run (Thread.java:764)

What could be the issue?

I removed the image from notification, however still I got crash reports.

Also getting this error using dependencies
implementation 'com.google.firebase:firebase-core:17.2.0' implementation 'com.google.firebase:firebase-messaging:20.0.0

I am facing the same issue. I pin pointed the method that is giving error in firebase messaging library.
public final boolean zzb(Intent var1) {
       if ("com.google.firebase.messaging.NOTIFICATION_OPEN".equals(var1.getAction())) {
           PendingIntent var3;
           if ((var3 = (PendingIntent)var1.getParcelableExtra("pending_intent")) != null) {
               try {
                   var3.send();
               } catch (CanceledException var4) {
                   Log.e("FirebaseMessaging", "Notification pending intent canceled");
               }
           }

           if (MessagingAnalytics.shouldUploadMetrics(var1)) {
               MessagingAnalytics.logNotificationOpen(var1);
           }

           return true;
       } else {
           return false;
       }
   }

What do you think is root cause? any ideas?

Same error for me
implementation 'com.google.firebase:firebase-core:17.2.0'
implementation 'com.google.firebase:firebase-messaging:20.0.0

Why is it closed? The issue isn't resolved!

Same error for me
implementation 'com.google.firebase:firebase-core:17.2.0'
implementation 'com.google.firebase:firebase-messaging:20.0.0

Why is it closed? The issue isn't resolved!

That's because nobody cares. My suggestion don't use images in notifications when you send them from Firebase console, instead send data messages using API and handle image loading by yourself

This is really sad that so many users faced the same issue but still we don’t have a solution. Firebase team should do something in future updates. For time being i will not use the images.

@ashwinraghav we're seeing this issue with customers of the Unity SDK as well https://github.com/firebase/quickstart-unity/issues/508 could you escalate?

Fatal Exception: java.lang.NullPointerException
Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
com.android.okhttp.okio.Buffer.write
Same issue. Couldn' find out what causes the problem.
For my case just one phone (LG Premier Pro with Android 8) encountered with the crash

Facing similar issues in Android app (haveing firebase sdk). Sending  notification in images via firebase console.
Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
at com.android.okhttp.okio.Buffer.write + 1182(Buffer.java:1182)
at com.android.okhttp.okio.Buffer.read + 1221(Buffer.java:1221)
at com.android.okhttp.okio.RealBufferedSource.read + 65(RealBufferedSource.java:65)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.read + 602(Http1xStream.java:602)
at com.android.okhttp.internal.Util.skipAll + 172(Util.java:172)
at com.android.okhttp.internal.Util.discard + 154(Util.java:154)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.close + 619(Http1xStream.java:619)
at com.android.okhttp.okio.RealBufferedSource.close + 421(RealBufferedSource.java:421)
at com.android.okhttp.okio.RealBufferedSource$1.close + 409(RealBufferedSource.java:409)
at com.google.android.gms.internal.firebase_messaging.zzk.a + 4(:4)
at com.google.firebase.messaging.zzd.close + 37(:37)
at com.google.firebase.messaging.zzc.a + 51(:51)
at com.google.firebase.messaging.FirebaseMessagingService.c + 59(:59)
at com.google.firebase.iid.zzb.run + 2(:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker + 1167(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run + 641(ThreadPoolExecutor.java:641)
at com.google.android.gms.common.util.concurrent.zza.run + 6(:6)
at java.lang.Thread.run + 764(Thread.java:764)

Hello, we've been facing similar issues as well. Again, when sending a notification with image which in our case is done by having { notification: { ..., image: "...." } } as payload :
Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
       at com.android.okhttp.okio.Buffer.write(Buffer.java:1182)
       at com.android.okhttp.okio.Buffer.read(Buffer.java:1221)
       at com.android.okhttp.okio.RealBufferedSource.read(RealBufferedSource.java:65)
       at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.read(Http1xStream.java:602)
       at com.android.okhttp.internal.Util.skipAll(Util.java:172)
       at com.android.okhttp.internal.Util.discard(Util.java:154)
       at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.close(Http1xStream.java:619)
       at com.android.okhttp.okio.RealBufferedSource.close(RealBufferedSource.java:421)
       at com.android.okhttp.okio.RealBufferedSource$1.close(RealBufferedSource.java:409)
       at com.google.android.gms.internal.firebase_messaging.zzk.zza(com.google.firebase:firebase-messaging@@20.0.0:4)
       at com.google.firebase.messaging.zzj.close(com.google.firebase:firebase-messaging@@20.0.0:38)
       at com.google.firebase.messaging.zzd.zza(com.google.firebase:firebase-messaging@@20.0.0:51)
       at com.google.firebase.messaging.FirebaseMessagingService.zzc(com.google.firebase:firebase-messaging@@20.0.0:60)
       at com.google.firebase.messaging.zze.run(com.google.firebase:firebase-messaging@@20.0.0:2)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at com.google.android.gms.common.util.concurrent.zza.run(:6)
       at java.lang.Thread.run(Thread.java:764)

I am seeing a similar crashlog when using image in a notification
Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
at com.android.okhttp.okio.Buffer.write(Buffer.java:1182)
at com.android.okhttp.okio.Buffer.read(Buffer.java:1221)
at com.android.okhttp.okio.RealBufferedSource.read(RealBufferedSource.java:55)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.read(Http1xStream.java:393)
at com.android.okhttp.internal.Util.skipAll(Util.java:159)
at com.android.okhttp.internal.Util.discard(Util.java:141)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.close(Http1xStream.java:410)
at com.android.okhttp.okio.RealBufferedSource.close(RealBufferedSource.java:396)
at com.android.okhttp.okio.RealBufferedSource$1.close(RealBufferedSource.java:384)
at com.google.android.gms.internal.firebase_messaging.zzk.zza(zzk.java:4)
at com.google.firebase.messaging.zzj.close(zzj.java:38)
at com.google.firebase.messaging.zzd.zza(zzd.java:51)
at com.google.firebase.messaging.FirebaseMessagingService.zzc(FirebaseMessagingService.java:60)
at com.google.firebase.messaging.zze.run(zze.java:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at com.google.android.gms.common.util.concurrent.zza.run(zza.java:6)
at java.lang.Thread.run(Thread.java:784)

I am seeing the same issue as well.
implementation 'com.google.firebase:firebase-analytics:17.2.0'
implementation 'com.google.firebase:firebase-messaging:20.0.0'

Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'int com.android.okhttp.okio.Segment.limit' on a null object reference
at com.android.okhttp.okio.Buffer.write(Buffer.java:1182)
at com.android.okhttp.okio.Buffer.read(Buffer.java:1221)
at com.android.okhttp.okio.RealBufferedSource.read(RealBufferedSource.java:65)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.read(Http1xStream.java:602)
at com.android.okhttp.internal.Util.skipAll(Util.java:172)
at com.android.okhttp.internal.Util.discard(Util.java:154)
at com.android.okhttp.internal.http.Http1xStream$FixedLengthSource.close(Http1xStream.java:619)
at com.android.okhttp.okio.RealBufferedSource.close(RealBufferedSource.java:421)
at com.android.okhttp.okio.RealBufferedSource$1.close(RealBufferedSource.java:409)
at com.google.android.gms.internal.firebase_messaging.zzk.zza(zzk.java:4)
at com.google.firebase.messaging.zzj.close(zzj.java:38)
at com.google.firebase.messaging.zzd.zza(zzd.java:51)
at com.google.firebase.messaging.FirebaseMessagingService.zzc(FirebaseMessagingService.java:60)
at com.google.firebase.messaging.zze.run(zze.java:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at com.google.android.gms.common.util.concurrent.zza.run(zza.java:6)
at java.lang.Thread.run(Thread.java:764)

authors: AlexeyGorovoy ColumbianGangster DavidWiseGroup Osjack Wallethub Yonghejiunian blessedCode07 mayurik18 pal-tgiannakopoulos searchy2 stewartmiles tfkci turgayulutas waleedsarwar86 zjamshidi

repo: firebase/quickstart-android


text:
docs: installation: clarify when to use method 2

closes #293

@adamprescott91 can you take a peek at the wording and suggest tweaks to make this more clear?

repo: fireeye/capa


text:
Release Docker image to GitHub Container Registry

This PR setups release flow for GitHub Container Registry.

Thank you.

repo: fireworq/fireworqonsole


text:
Remove tag exclusion from exposures

resolves #194

Description
This PR removes the exclusion of tags from the exposure docs. This is now allowed due to a PR to dbt enabling tags and meta on exposures. fishtown-analytics/dbt#3405
Example result is below (jaffle_shop):
exposures:
  - name: user_exposure
    type: dashboard
    depends_on:
      - ref('stg_customers')
    owner:
      email: nope@example.com
    meta:
      foo: bar
      fun: [times]
    tags:
    - funny
    - silly

Checklist

[x] I have signed the CLA
[x] I have generated docs locally, and this change appears to resolve the stated issue
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

I think this is set now @jtcohen6 ... git got a little sloppy though 😭

repo: fishtown-analytics/dbt-docs


text:
Help Switch from Arduino sketch to Node

I'm getting data in the read buffer but it is not the correct data and it is not same data consistently from read to read. I am reading data from an AD4116 https://www.analog.com/en/products/ad4116.html, the chip is on AD's evaluation board https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/EVAL-AD4116.html. I can read data using both an Arduino Uno R3 and AD's Evaluation Controller Board EVAL-SDP-CB1Z.
Here is an Arduino sketch that works:
#include <SPI.h>

#define DATAOUT 11 //COPI
#define DATAIN  12 //CIPO
#define SPICLOCK  13 //sck
#define CHIPSELECT05 5 //cs

void setup() {
    pinMode(DATAOUT, OUTPUT);
    pinMode(DATAIN, INPUT);
    pinMode(SPICLOCK,OUTPUT);
    pinMode(CHIPSELECT05,OUTPUT);
    digitalWrite(CHIPSELECT05,HIGH); //disable device
}

void loop() {
    pinMode(CHIPSELECT05,OUTPUT);

    delay(50);

    SPI.begin();
    SPI.setBitOrder(MSBFIRST);
    SPI.setDataMode(SPI_MODE3);

    digitalWrite(CHIPSELECT05,LOW); //enable device

    SPI.transfer(B01000111);
    unsigned int n1 = SPI.transfer16(0x00);

    digitalWrite(CHIPSELECT05,HIGH); //disable device
}

Here is a JavaScript that dosen't works:
try {

    // declare it
    var spi = global.get("SPI");

    // The AD4116 is on bus 0 and it's device 0
    const ad4116_ID = spi.open(0, 1, err => {

        const options = {
            mode: spi.MODE3,
            // The semantics of chipSelectHigh have changed in kernel 5 and higher
            //chipSelectHigh: false,
            lsbFirst: false, // pi only supports msb first
            threeWire: false,
            loopback: false, // pi doesn't support loopback
            noChipSelect: false,
            ready: false, // pi doesn't support ready
            bitsPerWord: 8, // pi only supports 8 bit words
            maxSpeedHz: 200
        };

        ad4116_ID.setOptions(options, err =>{
            if (err) {
                node.error(err)
                return msg;
            };
        });

        // An SPI message is an array of one or more read+write transfers
        const message = [{
            sendBuffer: Buffer.from([71]), // Sent to read ID
            receiveBuffer: Buffer.alloc(2),  // Raw data read
            byteLength: 1,
            speedHz: 200 // Use a low bus speed to get a good reading
        }];

        if (err) {
            node.error(err)
            return msg;
        };

        ad4116_ID.transfer(message, (err, message) => {
            if (err) {
                node.error(err)
                return msg;
            };
        });
        msg.payload = message
    });

    ad4116_ID.close
}
catch (exception_var) {
    msg.stopped = 4;
    node.error(exception_var);
}

return msg;

I'm sorry, but it looks like nobody was able to help out. There doesn't appear to be an problem with spi-device here so I'll go ahead and close the issue.

authors: FlameMetalsGitHub fivdi

repo: fivdi/spi-device


text:
[Feature] Add PMAX campaigns to url report

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
PMAX campaigns don't have ad groups and ads, but would it be possible to add them to the url report?
Describe alternatives you've considered
For now we have custom logic to add the spend of the PMAX campaigns to the spend of the url report.
Are you interested in contributing this feature?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
No response

Hi there @hansottowirtz thanks for opening this! Could you possibly share some of the logic you use to add PMAX campaigns into the url report? Code or just a high-level explanation would be much appreciated
Also, I don't know much about PMAX campaigns, but why join them into the url report instead of the campaign-level report?

Talked more about this with the team and they noted that in investigating this previous issue, we found that PMAX campaigns are only served at the campaign level and therefore can't be reflected in the URL, ad, or adgroup reports (at least not without muddying the model grain).
So i am thinking that this may not be possible, unless we are missing something or Google has changed things in the past year 😞 @hansottowirtz

going to close this out for now but please feel free to reopen if you'd like to continue discussing!

authors: fivetran-jamie hansottowirtz


text:
Feature/hubspotv3 api update

PR Overview
This PR will address the following Issue/Feature: Issue #111
This PR will result in the following new package version: v0.11.0

This will be a breaking change as it drastically changes how staging models are structured to bring in respecitive fields for downstream analysis. Due to the API v3 changes (see our release notes here from the connector), many tables were impacted on how they sync data. As such, we should make this a breaking change and require customers to ensure they are on the latest version of the HubSpot connector in order to leverage this package.
I do also want to call out that I was able to make these changes compatible with the old version of the connector (pre v3 API update). That being said, when using the old version of the connector with this package, you will see some fields are not documented as they have been removed from the newer API version. Likewise, due to the backwards compatibility, there are some fields that will always be null for users of the new API. These fields have been identified in the yml documentation and notified for deprecation and removal once all connectors are upgraded (next few months).
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
🚨 Breaking Changes 🚨

Following the May 2023 connector update the HubSpot connector now syncs the below parent and child tables from the new v3 API. As a result the dependent fields and field names from the downstream staging models have changed depending on the fields available in your HubSpot data. Now the respective staging models will sync the required fields for the dbt_hubspot downstream transformations and all of your property_hs_* fields. Please be aware that the property_hs_* will be truncated from the field name in the staging and downstream models. The impacted sources (and relevant staging models) are below:

  - `ENGAGEMENT`
    - `ENGAGEMENT_CALL`
    - `ENGAGEMENT_COMPANY`
    - `ENGAGEMENT_CONTACT`
    - `ENGAGEMENT_DEAL`
    - `ENGAGEMENT_EMAIL`
    - `ENGAGEMENT_MEETING`
    - `ENGAGEMENT_NOTE`
    - `ENGAGEMENT_TASK`
  - `TICKET`
    - `TICKET_COMPANY`
    - `TICKET_CONTACT`
    - `TICKET_DEAL`
    - `TICKET_ENGAGEMENT`
    - `TICKET_PROPERTY_HISTORY`

Please note that while these changes are breaking, the package has been updated to ensure backwards compatibility with the pre HubSpot v3 API updates. As a result, you may see some null fields which are artifacts of the pre v3 API HubSpot version. Be sure to inspect the relevant field descriptions for an understanding of which fields remain for backwards compatibility purposes. These fields will be removed once all HubSpot connectors are upgraded to the v3 API.

Documentation Updates

As new fields were added in the v3 API updates, and old fields were removed, the documentation was updated to reflect the v3 API consistent fields. Please take note if you are still using the pre v3 API, you will find the above mentioned source (and respective staging) models no longer have complete field documentation coverage.

PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:

[x] dbt compile
[x] dbt run –full-refresh
[x] dbt run
[x] dbt test
[x] dbt run –vars (if applicable)

I ran various versions of the package with variables enabled and disabled. In particular I tested to ensure the changed models worked when enabled and disabled.
Before marking this PR as "ready for review" the following have been applied:

[x] The appropriate issue has been linked and tagged
[x] You are assigned to the corresponding issue and this PR
[x] BuildKite integration tests are passing

Detailed Validation
Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

[x] You have validated these changes and assure this PR will address the respective Issue/Feature.
[x] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
[X] You have provided details below around the validation steps performed to gain confidence in these changes.

This package update has been validated to ensure it works as expected on the new v3 API update while also working on the older api version. Please see the corresponding Height ticket for the schemas used to validate. Additionally, I was able to gain confidence in these changes due to the customer in the linked Issue claiming the fix resolved upgrade issues they were experiencing.
Please note that these changes had downstream impacts. Please see the respective dbt_hubspot PR for notes on how this was validated.
Standard Updates
Please acknowledge that your PR contains the following standard updates:

Package versioning has been appropriately indexed in the following locations:

[x] indexed within dbt_project.yml
[x] indexed within integration_tests/dbt_project.yml

[x] CHANGELOG has individual entries for each respective change in this PR

[x] README updates have been applied (if applicable)

[n/a] DECISIONLOG updates have been updated (if applicable)
[x] Appropriate yml documentation has been added (if applicable)

dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:

[x] docs were regenerated (unless this PR does not include any code or yml updates)

If you had to summarize this PR in an emoji, which would it be?

🙃

@fivetran-catfritz thanks for the review! I just responded and made appropriate updates based on your above comments. Let me know if you have further questions. Before I move forward I wanted to get your eyes on my new approach to the macros (your initial comment here).
If that looks good to you then I will apply to the other models and regen the docs. If not, let me know!


text:
FEATURE - Include account_id column in models

Are you a Fivetran customer?
Daydream
Describe the solution you'd like
Add account_id column to the following models:

quickbooks__profit_and_loss
quickbooks__balance_sheet

Please indicate the level of urgency and business impact of this request
This is currently blocking our customers from viewing aggregated model data

Thanks for opening this Issue @wasifaleemdd!
Our team will work on assigning this task internally and will communicate here when a member of our team is working to include the account_id field to the profit and loss and balance sheet models.

Hi @wasifaleemdd 👋
I was able to open PR #20 which incorporates the account_id into the balance sheet and profit and loss models. You can follow the progress from there and we will let you know when it is merged and a new version is released.

Just an update on progress here:
The PR has been approved and will be merged into master when Joe returns next week.
In parallel, we are working on these other requests:
https://github.com/fivetran/dbt_quickbooks/issues/18
https://github.com/fivetran/dbt_quickbooks/issues/19
When all of this work is done, we'll create a new release.

FYI the new release v0.2.3 has been cut and should be live on the dbt hub tomorrow morning!
Closing this ticket as this update has been included in the latest release.


text:
SSO Sign In for Client

Is there anyway to authenticate via. SSO? I don't mind taking a crack at this, just need to know if it's been implemented or not.
Thanks!

Hi! No, unfortunately this library doesn't support this yet.
You can create dedicated user in SF, allow auth with password for it and use it for this client.

@fixer-m would you like me to take a crack at SSO or would you prefer that be implemented at a later time?

@lawrence-vo Sure - you can try to implement it, this would be great actually. I have only demo account in SF, so I guess I can't login via SSO and thus can't properly try and test this auth scheme. I would start with analysing how SSO works in official connector, try to recreate it and simplify it if possible.

@fixer-m might take longer as expected since the official client also has issues with SSO.

@lawrence-vo can you link to the issue with the official client?
I just implemented a client credentials flow (OAuth) between DBT and Azure AD for Snowflake.
The project I'm working on requires OAuth-authentication in prod and I'm also utilising this client, therefore I too wouldn't mind taking a stab at as I would love to use this package.
@fixer-m do you have any design ideas for how to implement multiple authentication alternatives?
I'm thinking a IAuthenticator interface... ?
If we can agree on some common patterns then I'd have no problems with creating the AzureOauthAuthenication implementation!

@Tsanton Yes, I guess there should be IAuthenticator interface with multiple implementations. I don't know much about OAuth, so right now I can't suggest any design patterns (I would start from researching official connector code).
I have a few requirements though:

Try to not break existing public contracts
It should be easy to use. Use some common practices and standards
It should be easy to add new auth implementations

@Tsanton , the [issue] is here (https://github.com/snowflakedb/snowflake-connector-net/issues/308)

authors: Tsanton fixer-m lawrence-vo

repo: fixer-m/snowflake-db-net-client


text:
all posts in a pd are flagged if the forum has flagged posts

When viewing flags on normal posts everything's fine. But normal flagged posts also appear inside PDs when viewing flagged content
So the issue is: every flagged post on the forum is displayed when an admin views a flagged PD

now the whole pd is shown if it has a flagged post

repo: flagrow/byobu


text:
Add callback for when collision detection has been completed

Problem to solve
In certain situations one needs to know the order in which collisions happened (during a time step).  For instance if a player collides with both an enemy and the goal within the same time step.  To achieve this, one can assemble a list of objects that are passed to the multiple calls to onCollision.  By creating an additional callback onCollisionsCompleted which is called once all the calls to onCollision are finished, then the player has a full list of all the objects with which it collided within the time step.
Proposal
Add a new callback which is called at the end of the collision resolution step.
More information
I've started working on a branch for this: https://github.com/christian-mindfulness/flame/tree/add_collision_completed

Doesn't onCollisionEnd work for this?

onCollisionEnd is called on the time step when an object stops colliding with another.  This callback will be called at the end of the time step where the collision occurs.  Thus useful if an object is colliding with multiple other objects within a given time step.  There's more detail on the discussion thread that I had with @spydon about a month ago:
https://discord.com/channels/509714518008528896/1157721633109311560

authors: christian-mindfulness ufrshubham

repo: flame-engine/flame


text:
update: go

Name: go
CVEs: CVE-2023-39325
CVSSs: n/a
Action Needed: update to >= 1.20.10
Summary: net/http: rapid stream resets can cause excessive work. A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded to the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.
HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit. New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.
This issue is also fixed in golang.org/x/net/http2 v0.17.0, for users manually configuring HTTP/2.
The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.
This is CVE-2023-39325 and Go issue https://go.dev/issue/63417. This is also tracked by CVE-2023-44487.
See also https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo.
refmap.gentoo: https://bugs.gentoo.org/915555

Fix will be in next alpha release.

authors: dongsupark krnowak

repo: flatcar/Flatcar


text:
Add documentation for CAPI to Flatcar

[x] Add a top-level  intro page for CAPI
Add quickstart guide for the following providers and link to it from the Flatcar website:

[ ] CAPA
[ ] CAPV
[ ] CAPZ
[x] CAPO: https://github.com/flatcar/flatcar-docs/pull/284

AFAICT the page we're linking to for CAPO isn't a quickstart, i.e. a guide you can follow from start to end to get a working cluster. Of course it's better than nothing but I'm not sure I would consider the quickstart part "done" until we have actual quickstarts for all supported providers.

authors: johananl t-lo


text:
Add zh_Hans & zh_Hant languages

Add zh_Hans & zh_Hant languages.
The type family uses Noto Sans.

Oh, I forgot to mention that I'm giving Button to add the Chinese language.

This is not the correct way to do this IMO.
You should just translate the strings in https://hosted.weblate.org/projects/flathub/frontend/ and the backend should automatically render it.

This is not the correct way to do this IMO.
You should just translate the strings in https://hosted.weblate.org/projects/flathub/frontend/ and the backend should automatically render it.

Thanks for your help. But I think my PR is the Chinese version of your Svg download badges. Can this backend be rendered as well?

Yeah, ideally, this should be removed from the repo and maybe add a textfile pointing at https://flathub.org/badges

OK，I see, I will close this PR immediately.

Yeah, ideally, this should be removed from the repo and maybe add a textfile pointing at https://flathub.org/badges

I found out https://flathub.org/badges is no localization of simplified Chinese, but traditional Chinese is localized. How can I upload my local svg that I can contribute my pin to you? because https://hosted.weblate.org/projects/flathub/frontend/ is no character string associated with it.

The string is called get-it-on, there is no SVG, we're creating those on the server on the fly

authors: ArcticFoxPro Songyon razzeee

repo: flathub-infra/assets


text:
Exercise editor allows publication of incomplete questions

migrated from https://github.com/learningequality/kolibri/issues/2407
Summary
Exercises can be published when missing a question, answer, or both. Question is marked as "Incomplete" but does not prevent publishing (is this desired behavior)?
System information
Please specify the Kolibri version you were using and your operating system!

Version: Develop
Operating system: Mac OS X
Browser: Chrome

Screenshots

cc @niustephanie

Need to add proofreader on publish

Incomplete nodes are now excluded from publish, so this should be fixed.

authors: indirectlylit jayoshih rtibbles

repo: fle-internal/content-curation


text:
OSError: [Errno 24] Too many open files

macbook，
when i fit the data, error happen.
error still persist, after i set 'ulimit -n 4096'

Hi,
It's hard to tell with such a generic description, but presumably, this happens because you're using memory mapping with too many cross-validation folds. You can try running with backend='threading' (this is the default) or try reducing the number of CV folds. In particular, you can run into this issue if you're using the subsemble method. An alternative is to set ulimit -n 30000 or something such.

authors: flennerhag joeybaba

repo: flennerhag/mlens


text:
POL-617 - Deprecate authentication type: "rightscale"

Description
This PR brings the required changes to standardize the policy Catalog between US and EU.
Changes required to deprecate EU_Policies branch:

Replaced auth_rs with auth_flexera (bb7d2d87f5b39ab9657b31aa709cea061c1df735)
Modify sys_log definition to prevent rs_cm.audit_entry.create outside Flexera NAM zone (cbfc00ab062717ddf8a0fdf3b7594414491d18bf)
Bumped template version and add CHANGELOG notes (dc1e3a3a835a4314a2a2a832307a3d5e9174de0a, f5b97af3923ce45e52203ede9526ff57b79a8ddc)
Updated Prerequisites section in README.md(b7847fa758c5390ed28c56bb6417f27086e5ae14) with requirements for Flexera Credential

Other changes included in this branch:

Removed sys_log definition where unused (6a86d0b4380976a332558bb8c70616a63c8d6446)
Fixed missing delete_unused_sql_databases definition (c6c351d20bf86f3ab156d93b4eea3783912c1f75)
Replaced references github.com/rightscale/policy_templates and github.com/flexera/policy_templates with github.com/flexera-public/policy_templates (2f2da7af40d4fa43052a272f3ecf57710b316a39)
Disabled publishing AzureAD Group Sync policy (18f1b2aff5b4ffb026af33aa0422a9abd361cdeb)

Issues Resolved

POL-617

Contribution Check List

[x] All tests pass.
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] New functionality has been documented in CHANGELOG.MD
[x] Provider-Specific Credentials page updated to include docs for creating Credential for Flexera [provider=flexera]

After this is approved/merged, pushing changes to production is mostly automated

[ ] Upload to S3 workflow runs after successful Test Policies on master branch. We can/should validate this happens as expected
[ ] Flexera NAM Policy Sync Applied Policy will update and publish new versions.  We can/should validate this happens as expected.
[ ] Update Flexera EU Policy Sync Applied Policy branch parameter from EU_Policies to master branch.  Next policy run, the new versions will get published in Flexera EU. After updating value and running, we can/should validate the updates are as expected and match what was deployed to Flexera NAM

@cdwilhelm, @flexera-public/policy-developers -- I am proposing we release this Monday.  I need at least one formal approval on this PR before we can merge, and once we merge changes that will trigger automation to publish new versions.  Curt will also make a post in the Flexera Community to raise awareness of this change and new requirement.
I used a script to deploy the policy templates which had the type: rightscale change and they all run as expected using auth_flexera credential instead of rightscale credential.

All merge conflicts handled for what's in mater right now.  I am hoping we can hold off on any other major commits to master before we can merge this (currently planned for Monday when @cdwilhelm gets back.
CC: @nia-vf1 @taterdog590 @XOmniverse @lawrethao


text:
自动选择AUST_Student

修补了不选择校园网WIFI的情况下链接命令无效的问题

不过前提是必须连接过一次校园网不然会报没有profile的错


text:
Updated plugin so it can handle empty templates

Hello there, I noticed this plugin doesn't play well with empty files, or files with frontmatter but no content, so here is a small fix :)
Let me know if you want anything changed
Changes

Updated plugin so it can handle empty templates.
Added a new test to cover this case,
added jest as a dev dependancy and updated the test command in package.json so it runs jest.
bumped package version and fixed typo in desc

Hey @fliptopbox is there anything blocking this from being merged?

repo: fliptopbox/eleventy-plugins


text:
Upgrading to Tensorflow Lite 2.5

Right now the backscrub code relies on TF Lite 2.4.1.
When I tested the new code of @Phlash with XNNPACK on ARM architecture (aarch64), there is a bug in the version of XNNPACK packaged with TF 2.4.1 which prevents compiling it:
https://github.com/google/XNNPACK/issues/987
On the latest version of TF Lite 2.5, I could compile backscrub fork with XNNPACK on ARM without issues.

I guess we need a few people to give this a go and report back if it's ok?
@vongillus are you happy to put a PR in for the version change, then testers can pull that PR down to test, I use these incantations:
%> git checkout main
%> git fetch origin pull/<PR number>/head:<local branch name>
%> git checkout <local branch name>
%> cmake --build build/
%> build/deepseg -d -d -c <your camera device> -v <your loopback device>

Looks good in #61, I'll also test against main and put in the PR if it works for me.

authors: phlash vongillus

repo: floe/backscrub


text:
[BUG] New Drakes are not implamented

Describe the bug
If one of the Teams slain an Hextech Drake (maybe Chemtank aswell, atm disabled) and you activated the Objective Pop Ups (Spawn and/or Kill) it won't appear.
After a short View in the Folders its missing in the Path: Frontend\ingame\images\scoreboardPopUps\Dragon
btw nice Tool! Keep going!

They will be in the next version.
Temporary solution: https://github.com/floh22/LeagueBroadcast/issues/89


text:
Dequeue error when adding lots of DrawStates

I'm writing an app the has to render a lot of meshes. In the default Gfx config I can create up to 128 objects in the scene like this:
        DrawState ds;
        ds.Mesh[0] = Oryol::Gfx::CreateResource(*meshDisplayData.meshSetup.get());
        ds.Pipeline = sceneTransient->phongPipeline;

This creates a new DrawState for each object. However, after 128 of these I get an error in Queue.h:
template<class TYPE> TYPE
Queue<TYPE>::Dequeue() {
    o_assert_dbg(this->buffer.size() > 0);
    return std::move(this->buffer.popFront());
}

I can fix this by adjusting the DefaultResourcePoolSize in GfxConfig.h. Is there another way?

You can pass pool sizes for all resource types in the Gfx::Setup() call, for instance see the BlendTest sample, which increases the pool size for Pipeline objects to 512:
https://github.com/floooh/oryol/blob/255de118fc4744b937b40306fd771a33f49ffc62/code/Samples/BlendTest/BlendTest.cc#L29-L31

authors: danhambleton floooh

repo: floooh/oryol


text:
Make the GetMetadata() method public.

It would be great to make a new public method that would return the parameters of the selected video file.
In addition to the Start method, make the method analogous to "getMetadata() (metadata *Metadata, err error)" only public.
With great respect:)

When release ?))

repo: floostack/transcoder


text:
Changement de position

Bonjour,
Serait il possible de personnaliser la position des cadrans ?
(mettre l'affichage du grand numéro en haut et  gauche par exemple)
Merci
Clément

Bonjour,
Actuellement ce n'est possible désolé. (et pour être franc, ce n'est pas prévu)
Merci,

authors: florian-mollin larcox

repo: florian-mollin/loto-associatif-app


text:
Implementation of the ClickShape #11 event

Implementation of the ClickShape #11 event to receive click events on a shape regardless of the state of the ReadOnly property.
The example page has been modified to show the new behavior

Thank you for your commit.
Can you please correct the naming for the Event... that it is like the others...
So, don't name it ClickedShape, instead OnShapeClicked
Thank you!


text:
Add xChangeApi.com service

Service implementation for https://xchangeapi.com

Thanks @xchangeapi 👍

authors: florianv xchangeapi

repo: florianv/exchanger


text:
added raspindi github link

https://github.com/raspberry-pi-camera/raspindi
RaspiNDI is a simple NDI send library for Raspberry Pi.

Send it

repo: florisporro/awesome-ndi


text:
Create Timeseries loader

(Gitlab Issue 103, created by @ChristianWieck)

@ChristianWieck commented:
Currently the timeseries loader can only load time series and no "additional" metadata. Maybe add an option to load scalar values from json/yaml files alongside the time series

Done with #113 and #110.

authors: ChristianWieck stbalduin

repo: flowcean/flowcean


text:
example can not run

https://github.com/flower-corp/lotusdb/blob/main/examples/basic/basic_operation.go
../../../go/pkg/mod/github.com/flower-corp/lotusdb@v1.0.0/index/bptree.go:114:12: assignment mismatch: 2 variables but bucket.Put returns 1 value
../../../go/pkg/mod/github.com/flower-corp/lotusdb@v1.0.0/index/bptree.go:147:19: assignment mismatch: 2 variables but bucket.Put returns 1 value
../../../go/pkg/mod/github.com/flower-corp/lotusdb@v1.0.0/index/bptree.go:185:19: assignment mismatch: 2 variables but bucket.Delete returns 1 value
../../../go/pkg/mod/github.com/flower-corp/lotusdb@v1.0.0/index/bptree.go:205:10: assignment mismatch: 2 variables but tx.Bucket(b.opts.BucketName).Delete returns 1 value

sorry, we fork the bbolt repo and changed, try go get github.com/flower-corp/bbolt@master.

that creates a new issue
go get github.com/flower-corp/bbolt@master
go: downloading github.com/flower-corp/bbolt v1.3.7-0.20220315040627-32fed02add8f
go get: github.com/flower-corp/bbolt@v1.3.7-0.20220315040627-32fed02add8f: parsing go.mod:
module declares its path as: go.etcd.io/bbolt
but was required as: github.com/flower-corp/bbolt

authors: feeops prr123 roseduan

repo: flower-corp/lotusdb


text:
🛑 Metabase is down

In 53cd2d4, Metabase (https://metabase.flowlity.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Metabase is back up in 6f1bf4b after 3 hours, 39 minutes.

repo: flowlity/upptime


text:
Input reference of possibly incorrect type

Hi!
Here it says inputRef gives reference to a FormControl,
https://github.com/flowtype/flow-typed/blob/master/definitions/npm/react-bootstrap_v0.32.x/flow_v0.53.x-/react-bootstrap_v0.32.x.js#L178
But the react-bootstrap docs say it's a reference to an <input> element.
https://github.com/react-bootstrap/react-bootstrap/blob/v0.32.1-docs.0/src/FormControl.js#L29

here you go: https://github.com/flowtype/flow-typed/pull/1919
Nice to see traction towards react-bootstrap libdefs :)

authors: luka-zitnik villesau

repo: flowtype/flow-typed


text:
Linux|Wayland webview does not attach to parent

On Wayland the webview is opening as a separate window

It appears the XEmbed protocol doesn't work on wayland/xwayland unfortunately. The FLTK coredevs are currently working on a native wayland backend, hopefully this would work.

A temporary workaround on wayland is running an app with GDK_BACKEND=x11
GDK_BACKEND=x11 ./myapp

This should force webkitgtk to give an x11 xid which can be embedded in another app.
Embedding in wayland doesn’t seem to be supported currently, even for gtk apps:
https://discourse.gnome.org/t/embedding-external-window-in-gtk-window/2371/9

I think this is the right way of doing it anyway – for whatever reason i didn't thought about that in the first place but this is how many application are doing it. I think we can close the issue and wait for a "better" solution from the fltk core devs. Maybe a note in the readme could help directing people to use GDK_BACKEND=x11

Thank you. ill add that along with install instructions for webkitgtk.

authors: MoAlyousef pythoneer

repo: fltk-rs/webview


text:
deb: tweak tests

Fix inverted tests using !, which has always succeeded.
Add some test cases.

Note: We can't test a fail of a command using ! with set -e.
set -e ignores the commands with !.
We can use sub shell to test a command that should fail.

Fixed inverted tests with !.

Rebased to the latest master to solve conflicts.

Thanks for your review!

repo: fluent/fluent-package-builder


text:
v1.0.0

Signed-off-by: Kenji Okimoto okimoto@clear-code.com

Awesome work @okkez !

authors: gaui okkez

repo: fluent/fluentd-ui


text:
修改./pkg/ddc/base/load_data.go,在文件头部规范License信息

This Pull Request makes the following changes to the  /pkg/ddc/base/load_data.go file in the fluid repository:
Corrected the Copyright year from 2022 to 2021.

/lgtm

repo: fluid-cloudnative/fluid


text:
Seeking doesn't work on mobile devices properly consistently

Fluidplayer has recently developed an issue where if you seek to a different time in a video the picture freezes but the sound continues playing.  Seems to only happen on mobile devices.  I'm using a samsung phone with chrome browser.  Seems to work on desktop and firefox and other browsers.  Issue as far as I can tell is only chrome on mobile.
Example of error.  I start playing video.  I seek ahead to 5:00 in the video by clicking the timeline.  Video continues to play but picture is frozen.  Sounds still keeps playing
Multiple users have reported the same bug.

This issue is mentioned #https://github.com/fluid-player/fluid-player/issues/770, I have created an internal ticket and linked this.

Hi @traffictitan,
This seems to be a problem with the native implementation of HLS on certain browsers on mobile.
To provide some context, I tested this on a standard <video> tag and noticed the issue still occurred. This is likely because Chrome on Android, for example, supports HLS natively, but the implementation isn't great. In Fluid Player, we check for native HLS support, and if it's present, we skip loading HLS.js, instead relying on the browser's native HLS handling.
We found that HLS.js works a bit more consistently, not perfect, but better. The problem with native HLS is that the browser has all the control over stuff like maxMaxBufferLength, you can't change it. With HLS.js you have a lot more control over stuff like that. The more I work with HLS, I notice support is quite bad over the board.
I've added a flag that allows you to override native HLS support when available, and instead force the use of HLS.js. This way you have more control.
<script>
fluidPlayer(
    'hls-video',
    {
        hls: {
            overrideNative: true
        }
    }
);
</script>

NOTE: if you're using the https://cdn.fluidplayer.com/v3/current/fluidplayer.min.js, it takes 24h for the cache to update so the change might not be there if you test it today. You'll have to use https://cdn.fluidplayer.com/3.35.0/fluidplayer.min.js if you want to use it today.

It's been two weeks with no response, hence closing the ticket. We assume this fixed the problem, if not you can open a new ticket.
Thanks for contributing and/or using fluid player!

authors: ZentoDH sergiomcsousa traffictitan

repo: fluid-player/fluid-player


text:
flutter devices output can be confusing when one of many devices is unauthorized

Seen on Gitter from @asaarnak:
$ flutter devices
Device emulator-5556 is not authorized.
You might need to check your device for an authorization dialog.
3 connected devices:

Android SDK built for x86    • emulator-5558 • android-x86 • Android O (API 25) (emulator)
SM N910F                     • fc74d864      • android-arm • Android 6.0.1 (API 23)
Android SDK built for x86 64 • emulator-5554 • android-x64 • Android 7.1.1 (API 25) (emulator)

$ ./adb devices
List of devices attached
emulator-5558    device
fc74d864    device
emulator-5556    unauthorized
emulator-5554    device

I think it's somehow related to "Google Play Store in Android Emulator" https://android-developers.googleblog.com/2017/05/android-studio-3-0-canary1.html
Because the Android O without Google Play is working.

Did anyone find solution

https://stackoverflow.com/questions/26079838/android-studio-adb-error-device-unauthorized-please-check-the-confirmat sounds similar

@KinanKazmi Nope.
Currently tested on everything seems to be ok for me with the Play Store edition emulator:
[✓] Flutter (Channel stable, v1.0.0, on Linux, locale en_US.UTF-8)
    • Flutter version 1.0.0 at /home/asaarnak/A/PROJECTS/GOOGLE/flutter
    • Framework revision 5391447fae (10 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[!] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /home/asaarnak/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /home/asaarnak/A/PROGRAMS/android-studio-ide-182.5160847-linux/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    ✗ Android license status unknown.

[✓] Android Studio (version 3.3)
    • Android Studio at /home/asaarnak/A/PROGRAMS/android-studio-ide-182.5160847-linux/android-studio
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[!] IntelliJ IDEA Ultimate Edition (version 2018.3)
    • IntelliJ at /home/asaarnak/A/PROGRAMS/idea-IU-183.4284.148
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[✓] Connected device (1 available)
    • Android SDK built for x86 64 • emulator-5554 • android-x64 • Android 9 (API 28) (emulator)

! Doctor found issues in 2 categories.

I think it's related to USB debugging. But emulator shouldn't need that access.

It looks like @devoncarew 's change here https://github.com/flutter/flutter/pull/13346 addressed this issue as stated.

authors: asaarnak eseidelGoogle priyajain123 zanderso zoechi

repo: flutter/flutter