text:
Cannot update languages - could not find an editable info

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Cannot update release notes with deliver
Command executed
deliver(
        app_version: "2.3.69",
        skip_binary_upload: true,
        skip_screenshots: true,
        skip_app_version_update: false,
        platform: "ios"
    )

Complete output when running fastlane, including the stack trace and command used
bundle exec fastlane upload_ios_release_notes

[✔] 🚀
+-----------------------+---------+--------+
|               Used plugins               |
+-----------------------+---------+--------+
| Plugin                | Version | Action |
+-----------------------+---------+--------+
| fastlane-plugin-waldo | 3.2.0   | waldo  |
+-----------------------+---------+--------+

[15:48:22]: ----------------------------------------
[15:48:22]: --- Step: Verifying fastlane version ---
[15:48:22]: ----------------------------------------
[15:48:22]: Your fastlane version 2.210.1 matches the minimum requirement of 1.81.0  ✅
[15:48:22]: ------------------------------
[15:48:22]: --- Step: default_platform ---
[15:48:22]: ------------------------------
[15:48:22]: Driving the lane 'ios upload_ios_release_notes' 🚀
[15:48:22]: --------------------------
[15:48:22]: --- Step: setup_travis ---
[15:48:22]: --------------------------
[15:48:22]: Not running on CI, skipping CI setup
[15:48:22]: ---------------------
[15:48:22]: --- Step: deliver ---
[15:48:22]: ---------------------
[15:48:22]: Your Deliverfile has had smart quotes sanitised. To avoid issues in the future, you should not use TextEdit for editing it. If you are not using TextEdit, you should turn off smart quotes in your editor of choice.
[15:48:22]: Successfully loaded '.../Deliverfile' 📄

+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                Detected Values from './fastlane/Deliverfile'                                                                                |
+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| app_identifier         | xx                                                                                |
| username               | xx                                                                                |
| force                  | true                                                                                |
| submit_for_review      | false                                                                                |
| skip_binary_upload     | false                                                                                |
| skip_screenshots       | true                                                                                |
| skip_metadata          | false                                                                                |
| app_review_information | {}                                                                                |
| languages              | ["en-AU", "en-CA", "en-GB", "en-US", "es-ES", "es-MX", "zh-Hans", "zh-Hant", "da", "nl-NL", "fi", "fr-CA",                                                                                |
|                        | "fr-FR", "de-DE", "el", "it", "ja", "no", "pt-BR", "pt-PT", "ru", "sv", "tr", "hi", "he", "hu", "ro",                                                                                |
|                        | "pl", "hr", "sk", "cs", "uk", "ms", "th", "vi", "id", "ca", "ko", "ar-SA"]                                                                                |
| release_notes          | {"default"=>"xx"}                                                                                |
| copyright              | xx                                                                                |
+------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

[15:48:22]: Login to App Store Connect xx
[15:48:25]: Login successful

+--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                deliver 2.210.1 Summary                                                                                |
+--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| app_version                          | 2.3.69                                                                                |
| force                                | true                                                                                |
| skip_binary_upload                   | true                                                                                |
| skip_screenshots                     | true                                                                                |
| skip_app_version_update              | false                                                                                |
| platform                             | ios                                                                                |
| screenshots_path                     | ./fastlane/screenshots                                                                                |
| metadata_path                        | ./fastlane/metadata                                                                                |
| username                             | xx                                                                                |
| app_identifier                       | xx                                                                                |
| edit_live                            | false                                                                                |
| use_live_version                     | false                                                                                |
| skip_metadata                        | false                                                                                |
| overwrite_screenshots                | false                                                                                |
| sync_screenshots                     | false                                                                                |
| submit_for_review                    | false                                                                                |
| verify_only                          | false                                                                                |
| reject_if_possible                   | false                                                                                |
| phased_release                       | false                                                                                |
| reset_ratings                        | false                                                                                |
| dev_portal_team_id                   | xx                                                                                |
| run_precheck_before_submit           | true                                                                                |
| precheck_default_rule_level          | warn                                                                                |
| copyright                            | xx                                                                                |
| app_review_information.first_name    | xx                                                                                |
| app_review_information.last_name     | xx                                                                                |
| app_review_information.phone_number  | xx                                                                                |
| app_review_information.email_address | xx                                                                                |
| app_review_information.demo_user     | xx                                                                                |
| app_review_information.demo_password | xx                                                                                |
| app_review_information.notes         | xx                                                                                |
| release_notes.default                | xx                                                                                |
| languages                            | ["en-AU", "en-CA", "en-GB", "en-US", "es-ES", "es-MX", "zh-Hans", "zh-Hant", "da", "nl-NL", "fi", "fr-CA",                                                                                |
|                                      | "fr-FR", "de-DE", "el", "it", "ja", "no", "pt-BR", "pt-PT", "ru", "sv", "tr", "hi", "he", "hu", "ro",                                                                                |
|                                      | "pl", "hr", "sk", "cs", "uk", "ms", "th", "vi", "id", "ca", "ko", "ar-SA"]                                                                                |
| ignore_language_directory_validation | false                                                                                |
| precheck_include_in_app_purchases    | true                                                                                |
+--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

[15:48:29]: Making sure the latest version on App Store Connect matches '2.3.69'...
[15:48:30]: '2.3.69' is the latest version on App Store Connect
[15:48:30]: Detected languages: ["en-AU", "en-CA", "en-GB", "en-US", "es-ES", "es-MX", "zh-Hans", "zh-Hant", "da", "nl-NL", "fi", "fr-CA", "fr-FR", "de-DE", "el", "it", "ja", "no", "pt-BR", "pt-PT", "ru", "sv", "tr", "hi", "he", "hu", "ro", "pl", "hr", "sk", "cs", "uk", "ms", "th", "vi", "id", "ca", "ko", "ar-SA", "default"]
[15:48:33]: Cannot find edit app info... Retrying after 10 seconds (remaining: 4)
[15:48:44]: Cannot find edit app info... Retrying after 10 seconds (remaining: 3)
[15:48:56]: Cannot find edit app info... Retrying after 10 seconds (remaining: 2)
[15:49:07]: Cannot find edit app info... Retrying after 10 seconds (remaining: 1)
[15:49:18]: Cannot find edit app info... Retrying after 10 seconds (remaining: 0)
+------------------+------------------------------+
|                  Lane Context                   |
+------------------+------------------------------+
| DEFAULT_PLATFORM | ios                          |
| PLATFORM_NAME    | ios                          |
| LANE_NAME        | ios upload_ios_release_notes |
+------------------+------------------------------+
[15:49:28]: Cannot update languages - could not find an editable info

+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 3    | setup_travis               | 0           |
| 💥   | deliver                    | 66          |
+------+----------------------------+-------------+

[15:49:28]: fastlane finished with errors

[!] Cannot update languages - could not find an editable info

Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
12.6.1

Ruby
3.0.2

Bundler?
true

Git
git version 2.37.0 (Apple Git-136)

Installation Source
/opt/homebrew/lib/ruby/gems/3.0.0/bin/fastlane

Host
macOS 12.6.1 (21G211)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.0.2_1/lib

OpenSSL Version
OpenSSL 1.1.1l  24 Aug 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
14.0.1

Swift Version
5.7

System Locale

Error

No Locale with UTF8 found 🚫

fastlane gems

Gem
Version
Update-Status

fastlane
2.210.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-waldo
3.2.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.5.0

bundler
2.2.29

tsort
0.1.0

uri
0.10.1

pathname
0.1.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.5

concurrent-ruby
1.1.10

i18n
1.12.0

minitest
5.16.3

tzinfo
2.0.5

zeitwerk
2.6.1

activesupport
6.1.7

public_suffix
4.0.7

addressable
2.8.1

httpclient
2.8.3

json
2.6.2

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.643.0

aws-sigv4
1.5.2

jmespath
1.6.1

aws-sdk-core
3.158.1

aws-sdk-kms
1.58.0

aws-sdk-s3
1.114.0

babosa
1.0.4

claide
1.1.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.15.5

ethon
0.15.0

typhoeus
1.4.0

cocoapods-core
1.11.3

cocoapods-deintegrate
1.0.5

cocoapods-downloader
1.6.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.1

cocoapods-trunk
1.6.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.8.0

ruby-macho
2.5.1

nanaimo
0.3.0

xcodeproj
1.22.0

cocoapods
1.11.3

redcarpet
3.5.1

cocoapods-acknowledgements
1.3.0

colored
1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
0.0.8.2

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.93.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.0.0

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.2

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

jwt
2.5.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.2.0

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.7.0

google-apis-core
0.9.0

google-apis-androidpublisher_v3
0.29.0

google-apis-playcustomapp_v1
0.11.0

google-apis-iamcredentials_v1
0.15.0

google-apis-storage_v1
0.19.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.0

google-cloud-core
1.6.0

google-cloud-storage
1.43.0

mini_magick
4.11.0

naturally
2.2.1

optparse
0.1.1

plist
3.6.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

fastlane-plugin-waldo
3.2.0

generated on: 2022-10-07

I have the same issue

Same here, pretty much exact same log.

The same happens for me too :(

Try using '--use_live_version true' not helping?
https://stackoverflow.com/questions/66277828/could-not-find-an-edit-version-on-app-store-connect-try-using-use-live-versi

Is there a workaround here? We have been stuck on this error for a while

To be more specific, here is our command executed that continues to fail: ```
deliver(
submit_for_review: true,
app_identifier: 'com.hidden.hidden',
api_key_path: 'omitted',
automatic_release: true,
skip_screenshots: true,
skip_binary_upload: true,
submission_information: {
add_id_info_uses_idfa: false
},
precheck_include_in_app_purchases: false,
force: true,
release_notes: {
'en-US' => 'our release notes',
}
)
I've tried `use_live_version: true` and also splitting the deliver command to first submit the app for review and then set the release notes. Both failed with the same error `Cannot update languages - could not find an editable info`

source: gharchive/issue

authors: BarnaKaracsony TDMNS elanor883 ktraunmueller mrcperello tomrom-pomelo

license: MIT

license_type: permissive

license_source: github-api


text:
incompatible character encoding error when using cocoapods 1.0.0

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used
> Compiling RealmSwift-dummy.m
> Linking RealmSwift
> Copying RealmSwift-umbrella.h
> Touching RealmSwift.framework
> Building Pods/Pods-Wildcard [Debug]
> Check Dependencies
> Processing Info.plist
> Compiling Pods-Wildcard-dummy.m
> Copying Pods-Wildcard-umbrella.h
> Touching Pods_Wildcard.framework
> Building Wildcard/Wildcard [Debug]
> Check Dependencies
> Running script '📦 Check Pods Manifest.lock'
incompatible character encodings: ASCII-8BIT and UTF-8
[11:56:38]: Variable Dump:
[11:56:38]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios test"}
[11:56:38]: Error building/testing the application - see the log above

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | cocoapods                           | 4           |
| 4    | scan                                | 41          |
+------+-------------------------------------+-------------+

[11:56:38]: fastlane finished with errors
/usr/local/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/error_handler.rb:32:in `handle_build_error': [!] Error building/testing the application - see the log above (RuntimeError)
	from /usr/local/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/runner.rb:31:in `block in test_app'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.0/lib/fastlane_core/command_executor.rb:72:in `rescue in execute'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.0/lib/fastlane_core/command_executor.rb:45:in `execute'
	from /usr/local/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/runner.rb:23:in `test_app'
	from /usr/local/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/runner.rb:9:in `run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/scan-0.5.2/lib/scan/manager.rb:10:in `work'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/actions/scan.rb:10:in `run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:143:in `block (2 levels) in execute_action'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:129:in `block in execute_action'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:128:in `chdir'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:128:in `execute_action'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/fast_file.rb:149:in `method_missing'
	from Fastfile:19:in `block (2 levels) in parsing_binding'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/lane.rb:36:in `call'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:52:in `block in execute'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:46:in `chdir'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/runner.rb:46:in `execute'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/bin/fastlane:38:in `block (2 levels) in run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane_core-0.41.0/lib/fastlane_core/ui/fastlane_runner.rb:23:in `run!'
	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/bin/fastlane:156:in `run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-1.68.0/bin/fastlane:162:in `<top (required)>'
	from /usr/local/bin/fastlane:22:in `load'
	from /usr/local/bin/fastlane:22:in `<main>'

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
fastlane_version "1.68.0"

default_platform :ios

platform :ios do
  before_all do
    cocoapods
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    ensure_git_status_clean
    increment_build_number
    git_commit(path: "./", message: "changed build nr")
    gym(scheme: "Wildcard", use_legacy_build_api: true) # Build your app - more options available
    pilot
  end

  desc "Deploy a new version to the App Store"
  lane :appstore do
    gym(scheme: "Wildcard") # Build your app - more options available
    deliver(force: true)
  end

  after_all do |lane|
  end

  error do |lane, exception|
  end
end

Environment
fastlane version (fastlane -v): 1.68.0
bundler
Description
When using cocoapods version 1.0.0-beta*, the pods gem adds build phases starting with a '📦' character.:
📦 Check Pods Manifest.lock
📦 Embed Pods Frameworks
📦 Copy Pods Resources
This results in the following error when running fastlane:

Running script '📦 Check Pods Manifest.lock'
incompatible character encodings: ASCII-8BIT and UTF-8

If I remove the first character of the three different build phases that cocoapods adds, the script works fine.

Hi @mborsten! Hope you are doing well! Can you let me know exactly what commands you are running? Please reformat using this template: https://github.com/fastlane/fastlane/blob/master/ISSUE_TEMPLATE.md
We really want to look into this! :+1:

I've updated the issue

@mborsten Thanks for following up. We are going to look into this :+1:

I think this a been corrected by CP in 1.0.1

Great to hear 👍

I can confirm this is no longer a problem with CP 1.0.1

authors: KrauseFx TKBurner mborsten nicolasbraun

repo: fastlane/fastlane


text:
Import helper module using import_from_git

Hey,
We have two apps and our Fastlane usage is pretty much identical. I'm attempting to extract all of our actions into a separate repository to share with both apps. Some of the extracted actions can transparently identify the app and make adjustments accordingly. I've created a helper module helper/app_helper.rb to hold various utility functions for identifying the app, etc.
However, now that I've come to use import_from_git, I'm discovering there isn't a nice way to reference the helper module from the external repository.

import_from_git will only import the actions and Fastfile.
I tried to move the helper file into the actions folder, however when importing external actions, Fastline   asserts that the file defines a 'FooAction' constant.

My current options appear to be:

Use .env files to specify the values my helper methods would usually compute. I don't like this option though, convention over configuration.
Make all of my helper methods actions.
Trick Fastlane into requiring my helper file by adding a dummy action, e.g:

module Fastlane
  module Actions
    class AppHelperAction < Action
    end
  end
end

module Fastlane
  module Helper
    module AppHelper
      class << self
...

I'm using option 3 right now, but I'm sure I don't need to point out how much a gross hack it is :smile:
Any suggestions?

Yeah, there is nothing for that yet. Easiest way is to add it to your Actions file :wink:

Hey @ileitch, thanks for bringing this up! I am going to mark this as a feature request and close it for now, but will be sure to reopen it again when we get a chance to bite this off for a future release. If you would like to get set up to contribute, we would LOVE that! :smile: :octopus: :palm_tree:

authors: KrauseFx ileitch ohwutup


text:
Initial work on devserver

An attempt to implement #92
This is some initial work on getting a native dev-server into fastpack. The module is in reason right now but I can convert it to OCaml as the rest of the codebase is in OCaml.
For some reason the cohttp server doesn't seem to close down when fastpack is stoped, not sure why but investigating.
There is code borrowed from/inspired by https://github.com/anmonteiro/reason-graphql-fullstack and https://github.com/actionshrimp/ocaml-livereload.

#115 supersedes this

source: gharchive/pull-request

repo: fastpack/fastpack


text:
Replace Google Analytics for Plausible on old docs

Related to https://github.com/fatiando/community/issues/46
Reminders:

[ ] Run make format and make check to make sure the code follows the style guide.
[ ] Add tests for new features or tests that would have caught the bug that you're fixing.
[ ] Add new public functions/methods/classes to doc/api/index.rst and the base __init__.py file for the package.
[ ] Write detailed docstrings for all functions/classes/methods. It often helps to design better code if you write the docstrings first.
[ ] If adding new functionality, add an example to the docstring, gallery, and/or tutorials.
[ ] Add your full name, affiliation, and ORCID (optional) to the AUTHORS.md file (if you haven't already) in case you'd like to be listed as an author on the Zenodo archive of the next release.

🥂

authors: leouieda santisoler

repo: fatiando/ensaio


text:
feat: Added redis support for proxy-cache plugin

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

failure

repo: fatihbm/apisix


text:
Control Sense Guard switch

I don't know if it's by design but you can't build and automation to turn off the main water automatically if a leakage is detected.
In order to do this the Guard switch needs to be separated from the other sensors so it can be toggle on/off as an own switch otherwise you can only control the main water inlet manually.

I think this is due to a recent change in homekit, where devices with multiple sensors are grouped by default. But i see how this is a problem if you have non-grohe leak sensors. Will investigate if there is something I can do.

Solving this will require quite some refactoring, but I will put it on my todo list. Its quite stupid that Homekit has this limitation, but I think I know what needs to be done.

If you would like to try out this feature, I have pushed a new feature branch which splits the sense guard switch from the sensors: https://github.com/faune/homebridge-grohe-sense/tree/feature/split-water-control
This is work in progress, but would be nice to hear if this solves your problem before spending more time on this.

Great! Of course but how do I install a new feature branch?

git clone https://github.com/faune/homebridge-grohe-sense
cd homebridge-grohe-sense
git checkout feature/split-water-control
npm install
npm run build
npm link
homebridge -I -D

Hi faune,
tested and Grohe Sense Guard (close/open valve) switch works in Homebridge and Home.app, but somehow the switch is not able to use as switch in Home.app automation, as it says that the Guard in not a switch, but a sensor.
Is there a plan to fix this?
Many thanks

I did a workaround via Node-Red 👍

authors: faune jimmykarlsson mrazon87

repo: faune/homebridge-grohe-sense


text:
Fixed: Unhandled Exception: type 'FlutterError' is not a subtype of t…

Solves #57

Sorry that's not the solution


text:
Race condition when loading keras config JSON file.

These lines read the keras JSON config file, if it exists.
Then they unconditionally write back the same keras JSON config file.
https://github.com/fchollet/keras/blob/master/keras/backend/__init__.py#L27-L50
If there are multiple python kernels reading/writing the same config file at once, a race condition is created, and some jobs will throw an exception. This can happen in a cluster environment where the keras.json file is shared via NFS, or on shared memory machines starting multiple processes at once.
My suggestion is to make writing the file keras.json conditional on that file's non-existence. This will at least mean that the race condition only happens the first time keras is used in an installation. A more complicated idea would write to a temporary file and then use shutil to move that temporary file, gaining a certain kind of atomic writing. However, just making the writing code conditional will eliminate most instances of this problem.

File "/home/my_username/.local/lib/python2.7/site-packages/keras/init.py", line 2, in
from . import backend
File "/home/my_username/.local/lib/python2.7/site-packages/keras/backend/init.py", line 26, in
_config = json.load(open(_config_path))
File "/my/python/installation/python/lib/python2.7/json/init.py", line 290, in load
**kw)
File "/my/python/installation/python/lib/python2.7/json/init.py", line 338, in loads
return _default_decoder.decode(s)
File "/my/python/installation/python/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/my/python/installation/python/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

Additionally... I know that I should have read the backtrace more carefully from the beginning, but it seems like people might confuse this with an error in loading the JSON that defines a model. Perhaps some exception handling in the part that reads the config file could make it clear that that is where the failure lies.

I resolved this.

For reference, the fix is this commit https://github.com/fchollet/keras/commit/a4d191d4f97a8100a561b87802fdd6ab5db0ed26

authors: bryan-lunt fchollet ksze

repo: fchollet/keras


text:
Vae loss negative

I'm running the vae and vae_deconv (in keras examples) with the loss function as provided (no changes done to code logic, but different data). However, I sometimes get both training and validation loss to be negative, which means the variable kl_loss is negative. As I understand, we are minimizing log (p(x))-D_kl(p(x)||q(x)), we know the D_kl is non-negative, it means D_kl(p(x)||q(x))> log(p(x)), or the information in p(x) is less than the distance between the  two distributions. Is this statement correct? I'm basically trying to understand what the function vae_loss is exactly computing, and why it would be negative.

I also get negative loss sometimes.

authors: appierys samsinai


text:
Sparse sample_weight causes crashes

When sample_weight is a sparse vector, the following simple example code crashes (I'm running on Anaconda python, with a GeForce GTX 980, on Ubuntu 12.04):
import numpy as np
from keras.models import Sequential
from keras.layers.core import Dense, Dropout, Activation
from keras.optimizers import SGD

# Generate data
X = np.zeros((100, 100))
y = np.zeros((100, 2))
## The training always fails with
#W = np.zeros((100,))
## The training fails roughly half the time with
W = np.random.binomial(1, .05, size=(100,))
## The training always succeeds with
# W = np.ones((100,))

model = Sequential()
model.add(Dense(100, 50, init='uniform', activation="relu"))
model.add(Dense(50, 2, init='uniform', activation="softmax"))
sgd = SGD(lr=.01, decay=1e-6, momentum=0.9, nesterov=True)
model.compile(optimizer=sgd, loss="binary_crossentropy")
model.fit(X, y, nb_epoch=20, batch_size=50,
          sample_weight=W)

The code crashes halfway through training with output:
rbharath@not0rious:~/torch-models$ python simple_multitask_seq.py
Using gpu device 0: GeForce GTX 980
Epoch 0
100/100 [==============================] - 0s - loss: 0.6931
Epoch 1
Traceback (most recent call last):
  File "simple_multitask_seq.py", line 22, in <module>
    sample_weight=W)
  File "build/bdist.linux-x86_64/egg/keras/models.py", line 477, in fit
  File "build/bdist.linux-x86_64/egg/keras/models.py", line 215, in _fit
  File "/home/rbharath/anaconda/lib/python2.7/site-packages/theano/compile/function_module.py", line 606, in __call__
    storage_map=self.fn.storage_map)
  File "/home/rbharath/anaconda/lib/python2.7/site-packages/theano/compile/function_module.py", line 595, in __call__
    outputs = self.fn()
  File "/home/rbharath/anaconda/lib/python2.7/site-packages/theano/gof/op.py", line 768, in rval
    r = p(n, [x[0] for x in i], o)
  File "/home/rbharath/anaconda/lib/python2.7/site-packages/theano/sandbox/cuda/basic_ops.py", line 2384, in perform
    out[0] = x.reshape(tuple(shp))
ValueError: Reshape has invalid dimension 0 (must be >0)
Apply node that caused the error: GpuReshape{1}(GpuElemwise{TrueDiv}[(0, 0)].0, MakeVector.0)
Inputs types: [CudaNdarrayType(float32, vector), TensorType(int64, vector)]
Inputs shapes: [(0,), (1,)]
Inputs strides: [(1,), (8,)]
Inputs values: [<CudaNdarray object at 0x7f3909e31d70>, array([0])]

Debugprint of the apply node:
GpuReshape{1} [@A] <CudaNdarrayType(float32, vector)> ''
 |GpuElemwise{TrueDiv}[(0, 0)] [@B] <CudaNdarrayType(float32, vector)> ''
 | |GpuFlatten{1} [@C] <CudaNdarrayType(float32, vector)> ''
 | | |GpuFromHost [@D] <CudaNdarrayType(float32, vector)> ''
 | |   |AdvancedSubtensor [@E] <TensorType(float32, vector)> ''
 | |     |<TensorType(float32, matrix)> [@F] <TensorType(float32, matrix)>
 | |     |Subtensor{int64} [@G] <TensorType(int64, vector)> ''
 | |     | |Nonzero [@H] <TensorType(int64, matrix)> ''
 | |     | | |<TensorType(float32, matrix)> [@F] <TensorType(float32, matrix)>
 | |     | |Constant{0} [@I] <int64>
 | |     |Subtensor{int64} [@J] <TensorType(int64, vector)> ''
 | |       |Nonzero [@H] <TensorType(int64, matrix)> ''
 | |       |Constant{1} [@K] <int64>
 | |GpuDimShuffle{x} [@L] <CudaNdarrayType(float32, (True,))> ''
 |   |GpuFromHost [@M] <CudaNdarrayType(float32, scalar)> ''
 |     |Elemwise{Cast{float32}} [@N] <TensorType(float32, scalar)> ''
 |       |Shape_i{1} [@O] <TensorType(int64, scalar)> ''
 |         |Nonzero [@H] <TensorType(int64, matrix)> ''
 |MakeVector [@P] <TensorType(int64, vector)> ''
   |Shape_i{1} [@O] <TensorType(int64, scalar)> ''

The crashing behavior is nondeterministic and appears to depend on the sparsity of the sample_weight. If sample_weight is uniformly 0, then it always crashes, with a sparse sample_weight, it crashes about half the time, and if it is uniformly one, then the code never crashes. On CPU, the code doesn't crash, but the loss function goes to NaN instead. This behavior isn't limited to Sequential models. Here's a Graph model with the same behavior:
import numpy as np
from keras.models import Graph
from keras.layers.core import Dense, Dropout, Activation
from keras.optimizers import SGD

# Generate data
X = np.zeros((100, 100))
y = np.zeros((100, 2))
## The training always fails with
#W = np.zeros((100,))
## The training fails roughly half the time with
W = np.random.binomial(1, .05, size=(100,))
## The training always succeeds with
# W = np.ones((100,))

model = Graph()
model.add_input(name="input", ndim=100)
model.add_node(
    Dense(100, 50, init='uniform', activation="relu"),
    name="dense", input="input")
model.add_node(
    Dense(50, 2, init='uniform', activation="softmax"),
    name="head", input="dense")
model.add_output(name="task", input="head")
sgd = SGD(lr=.01, decay=1e-6, momentum=0.9, nesterov=True)
model.compile(optimizer=sgd, loss={"task": "binary_crossentropy"})
model.fit({"input": X, "task": y}, nb_epoch=20, batch_size=50,
          sample_weight={"task": W})

Any suggestions for debugging/fixing this issue would be greatly appreciated. I've been banging my head against it for a day or so.

On CPU, the code doesn't crash, but the loss function goes to NaN instead

I can see why that would happen (we're taking the loss function applied to empty arrays). One easy fix for you would be to replace your 0s with epsilons small enough not to sensibly affect your loss function (but large enough not to cause overflows).
We definitely need a workaround when there is no sample with weight != 0 in a batch.

The question, of course, is what to return when there is no sample to compute the loss on. Returning 0 would mess up the training process badly.

Conclusion: the problem is conceptually ill-defined and thus cannot be considered to be a Keras bug. Returning NaN or crashing is in fact acceptable behavior given that there is no sensible value that can be returned.
Your fix: either make sure that every batch has at least one valid sample (preferably more, if you want you training process to go smoothly), or use epsilons instead of 0s (but keep in mind that for batches where there is no valid sample, it will probably mess up your training process, i.e. the loss of the batch would be meaningless).

Can we print a warning on this?
I spent quite some time trying to figure out what the problem was. In my case I was using sample_weight_mode='temporal' and at some of the time-steps with sample_weight 1 I had 0s in the output.

I'm currently encountering something like this bug (model is fairly complex, so will take time to confirm that it's the same, and some apparently unrelated changes cause the nans to vanish)
But I'm doing a stateful recurrent time series classification with a GRU that output classification at the FINAL timestep, so I think I have a valid case for weighting the loss function at 0 for the first timestep(s) before the classifier can possibly know what to classify and yet still accumulating gradients across those timesteps; nonetheless this causes nans. The workaround, of using epsilon weights, works for now, but it took a loooooong time to work out which parameters were messing with my updates, so at least documentation would be nice.

authors: danmackinlay fchollet kracwarlock rbharath


text:
Reduce latency of DbSearchIndexImpl.addUpdateIndex

Add table indexes for DB queries used in the 'addUpdateIndex' method
Move repeatedly used SimpleJdbcInsert objects up as class members

Resolves: https://jira.lyrasis.org/browse/FCREPO-3455
How should this be tested?
This is an optimization, no functional changes.
Interested parties
@fcrepo/committers

@awoods what is your feeling on this PR now?

@whikloj : it can probably be closed, no?

authors: awoods whikloj

repo: fcrepo/fcrepo


text:
acl:Append DELETE and PATCH authorization

Resolves:
https://jira.duraspace.org/browse/FCREPO-2715
https://jira.duraspace.org/browse/FCREPO-2716
What does this Pull Request do?

Adds Unit & IT Tests to verify acl:Append permission is not sufficient to make http DELETE requests.
Implements acl:Append PATCH logic to specifically deny patches that include Sparql DELETE statements and allow only specific requests. Also, adds Unit and IT tests to verify acl:Append PATCH logic.

What's new?
Created a new CachedSparqlRequest class to support reading the InputStream from the request object multiple times (First time in the filter to verify that there are no delete statements and secondly in the FedoraLDP). The spring provided ContentCachingRequestWrapper could not be used as the MessageBodyReader in Fedora only has access to the request's InputStream, but not to the getContentAsByteArray method of the ContentCachingRequestWrapper.
How should this be tested?
Maven build tests and manual interaction with the webapp to verify the acl:Append http DELETE & PATCH authorization.
Additional Notes:
We would need FCREPO-2783 for the createdBy and lastModifiedBy user to work correctly.
Interested parties
@fcrepo4/committers, @peichman-umd

@mohideen : Looks like there is a checkstyle error: https://github.com/fcrepo4/fcrepo4/commit/c3ebfdb3c49a295646ceb1d7d7c082efd138057f

authors: awoods mohideen


text:
Custom disappears when click custom cortical area in CB

https://github.com/user-attachments/assets/351c85d2-86fa-4f68-9479-b8048cd1dec6

I cant repo this.
I am guessing this has something to do with regions, but I need your genome you are using here to check

steps:

import a different gneome (any different genome) into this essential genome
open cb/bm split
click edit on custom cortical area

Confirmed, you need to import any genome to make this happen.
Each cortical will jump to region even if it doesn't have the cortical in first place

Check the logs of BV. I am 99% sure this is FEAGI sending inconsistent data

Sorry.

you load essential genome
Delete ALL vision
Download the genome
Load essential genome again
Import the genome you downloaded
Refresh (FEAGI needs to fix that part)
You open CB and click any vision region to edit

@m-nadji-tehrani I am betting the endpoint giving funni results is "/v1/region/regions_members"

Fixed in a local branch and will be pushed to public repo shortly

authors: Amir-Rasteg Kakcalu13 m-nadji-tehrani

repo: feagi/brain-visualizer


text:
don't bring to front when application auto-locks

when Feather auto-locks in the background, the window pops to the front, stealing the desktop environment's focus.
this is quite annoying, please change this behavior such that Feather remains in the background during the process.

Yep. I agree this is annoying behavior, will change.

Fixed in e5a61c6e2fb3e79092a7c40334c05635e2fc4a95

authors: chaserene tobtoht

repo: feather-wallet/feather


text:
MVP Tor support in the client

Part of #2610, but without stream separation by operation. @oleonardolima already did most of the work for an MVP version, so let's get it in. The full version can follow later.

As I've mentioned in today's dev call, I still need to test and debug the connection to hidden services peers thoroughly, and  I think it's best to split the work done into two/three PRs:
I did update the description of #2610, extracting it from there, the current work in progress (step/milestone 2):

feat: add initial Tor support, without OperationId stream isolation: https://github.com/fedimint/fedimint/issues/4752

[ ] feat: add initial Tor support, connection to hostname https://github.com/fedimint/fedimint/pull/5053
[ ] feat: add initial Tor support, connection to onion addresses (hidden services)
[ ] feat: add initial Tor support, support for onion addresses into InviteCode

cc @elsirion (@benthecarman I'll focus the updates in this issue for now :))

update: FWIW, I've used harbor for testing alongside the fedimint-cli, building on top of the #5443,  here is harbor's branch/PR if anyone is curious about it https://github.com/MutinyWallet/harbor/pull/89

update: I think this initial mvp is almost there, I was able to do a test federation setup with hidden services, using the non-tls script / setup approach.
It only required to set up the hidden service beforehand, using the onion address during federation setup (the SafeUrl/Url handles it pretty well), and the onion addresses will be part of the config and returned in the api_endpoints responses, encoded in the federationId, and so on.
If some guardian wants to expose both through an onion address, it seems possible with some traefik settings, but the domain will still be exposed as it's part of the response in api_endpoints 🤔
FYI @elsirion @benthecarman

yaaaaaaaay

authors: Kodylow elsirion oleonardolima

repo: fedimint/fedimint


text:
replit: bump nix channel

Using the latest nix channel on replit gives a newer version of the rust compiler, which makes it further along in the build process past the error mentioned in https://github.com/fedimint/fedimint/pull/1112. Unfortunately, it runs out of disk space even after this change.

I think the solution for that will ultimately be throwing hardware/money at the problem. https://twitter.com/amasad/status/1602748179438411776

authors: elsirion ryantm


text:
python 2.5 doesn't allow relative imports with *

using python 2.5 feincms 1.5 wasn't even installable, this commit should fix this and hopefully not break something else.

Thanks!
(why do we have star imports at all?)

repo: feincms/feincms

license_source: bigquery


text:
Make date field required

Is this possible ?

@blaindy Surely this should be handled by your app, not the plugin. What language are you using?

Hi, I have the same issue,it is because the script add readonly attribute to the field so the field didn't get validate correctly.

authors: blaindy lenamtl pacMakaveli

repo: felicegattuso/datedropper

license: mit


text:
Is it possible to run the board on different server that the actual server that runs MQ?

I don't want to host the board on the same api server that runs MQ.
Is it possible to do it using the connection string and the queue name only?

@DvirH Did my answer solved it for you?

@felixmosh Thank you Felix, It did solve my problem

authors: DvirH felixmosh

repo: felixmosh/bull-board


text:
Successful deploy, but the site keeps returning a 500 error

I've just deployed through the marketplace and deploy to azure button on the repo a number of times. The deploy always succeeds, but after trying to go to the site I keep getting a 500 error.
This is the only thing being written to the log.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<title>IIS Detailed Error - 500.1002 - Internal Server Error</title>

HTTP Error 500.1002 - Internal Server Error

The page cannot be displayed because an internal server error has occurred.

<fieldset>
Most likely causes:

IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.

IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.

IIS was not able to process configuration for the Web site or application.

The authenticated user does not have permission to use this DLL.

The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

</fieldset>

<fieldset>
Things you can try:

Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.

Check the event logs to see if any additional information was logged.

Verify the permissions for the DLL.

Install the .NET Extensibility feature if the request is mapped to a managed handler.

Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

</fieldset>

<fieldset>
Detailed Error Information:

Module	   iisnode

Notification	   ExecuteRequestHandler

Handler	   iisnode

Error Code	   0x00000002

Requested URL	   http://hackingonhacks-blog:80/index.js

Physical Path	   D:\home\site\wwwroot\index.js

Logon Method	   Anonymous

Logon User	   Anonymous

</fieldset>

<fieldset>
More Information:

This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

View more information »

Microsoft Knowledge Base Articles:

</fieldset>

I just deployed from the button again and the first time it failed (shared tier), though there was no error message aside from saying it failed. Then I tried again using a medium basic tier and that worked. First page load was a 500 error, but trying again a few minutes later resulted in the site loading.

repo: felixrieseberg/Ghost-Azure


text:
🛑 JNews is down

In 9922011, JNews (https://jnews.io/default/) was down:

HTTP code: 403
Response time: 47 ms

Resolved: JNews is back up in ac1b6fd.

repo: ferdysopian/jegmontol


text:
how to set multiple pattern of a input

I want to set multiple pattern of a input, and give multiple error tips for every pattern, how can I do?
code snippet:
<form v-form name="report" @submit.prevent="onSubmit">

     <input type="text" name="width" placeholder="输入宽" v-form-ctrl v-model="model.width" pattern="[0-9]{1,}">
         x
    <input type="text" name="height" placeholder="输入高" v-form-ctrl v-model="model.height" pattern="[0-9]{1,}">

     必须输入高宽值
     输入必须为数字

</form>

if I have another pattern for validation, and then give the third error-tips for users, what can I do?

@baooooogx Just add a custom validator? What did you end up doing?

@ianwalter    I want to have another pattern to show my custom error-tips, like this:

     <input type="text" name="width" placeholder="输入宽" v-form-ctrl v-model="model.width" pattern1="[0-9]{1,}" pattern2="" pattern3="">
         x
    <input type="text" name="height" placeholder="输入高" v-form-ctrl v-model="model.height" pattern="[0-9]{1,}" pattern2="" pattern3="">

     必须输入高宽值
     输入必须为数字
    my custom error-tips here
    my custom error-tips here

But at last, I add a method to valid the input before submit, and control error-tips show or hide. Obviously, this is not a good idea.

Custom validator that sets error flags per validation error?  As far as I remember it's not possilbe to have multiple patterns on a single input

Closing Vue 1 compatible version issues.

authors: baooooogx fergaldoyle ianwalter

repo: fergaldoyle/vue-form


text:
error occured when using vuejs in production

maybe the reason is
//  vue/dist/vue.js
 7569      // store directives on node in dev mode
 7570      if ('development' !== 'production' && this.el) {
 7571:       this.el._vue_directives = this.el._vue_directives || [];
 7572:       this.el._vue_directives.push(this);
 7573      }
 7574    }

Fixed for now, although we can't use v-bind object syntax to set multiple validation attributes in production for now.

authors: ablipan fergaldoyle


text:
Serverless AI Tutorial: npm install may not be applicable

I was following the Serverless AI Tutorial and chose the Rust path.  However, the docs show npm install as a command to run before spin build --up.  I wonder if we should add a note to mention this is only needed if the app is TS/JS?

Thanks @vdice fixed in https://github.com/fermyon/developer/pull/900

authors: tpmccallum vdice

repo: fermyon/developer


text:
Question on testing/mocking internals

I wrote myself a simple do-nothing sample and added basic unit tests that run outside WASM:
https://github.com/christophwille/SpinHello/blob/main/src/Tests/SampleUnitTests.cs
Going one step further would be taking https://github.com/fermyon/spin-dotnet-sdk/blob/c12d70e36a274396c7b1ded7a06ec913748bdb3d/samples/hello-world/Handler.cs#L43 And here the question comes up of how to properly mock that guy - do you envision me to wrap it in a service that I replace (IOutboundHttp with one real implemenation and one Mock) or is this an area that is "undefined" as of now?

I wrote myself a small wrapper in my sample app for HttpOutbound.Send.
Aside: It is super-confusing that between HttpRequest and HttpResponse the StatusCode props are different underlying types. I probably would like it better not seeing System.Net anywhere to make sure there are no mishaps in copy/paste (worded that way because it is only hunch).

Thanks for the feedback!
Re mocking outbound HTTP, you're right, the static member is impractical to mock.  Longer term, I'm hoping we can align more with the Microsoft HTTP API, using the WASI interface only as the low-level transport handler, but there are challenges to doing that.  But for now, your approach of to writing a small wrapper is the right way to go.
Re status codes, that's a good point and we'll have a think about what to unify on.
Thanks again for kicking the tyres and for taking the time to let us know what issues you're running into!

authors: christophwille itowlson

repo: fermyon/spin-dotnet-sdk


text:
remove workarounds for quickjs-wasm-rs case conversion

Now that quickjs-wasm-rs no longer does object key case conversion when serializing and deserializing, there's no need for complicated workarounds.
Signed-off-by: Joel Dice joel.dice@fermyon.com

@karthik2804 Please let me know if there are any files that need to be re-generated based on these changes.

@dicej this one looks good to merge to me after the first commit is signed.

repo: fermyon/spin-js-sdk


text:
Better large file handling

Large files fail with RangeError (in Chrome)

Haven't seen RangeError in a while, but large downloads seem to stall part-way through (around when the tab hits 2GB ram?)

You should check to see if you are hitting your machine's paging limit.

For a 105MB file, the page uses 540MB of memory. By commenting out bits of the code at a time, I found this breakdown:

90MB just for loading instant.io in chrome (incl. my browser extensions)
210MB from drag-drop/buffer
105MB from create-torrent in webtorrent.seed
105MB from file.getBlobURL in onTorrent on instant.io

We're creating lots of buffers that don't get released, it seems. Ideally, we only need to hang onto one copy of the buffer.

There are still some leaks, but it doesn't look like we're losing any full copies of the file anymore! Progress! There's only one copy of the file in memory.
For a 360MB file:

90 MB for base instant.io page
360 MB for file
160 MB for webtorrent.seed (and leaks?)

cc @jhiesey

We're now running into a bug in Chrome where blobs can't be larger than 500MB. https://code.google.com/p/chromium/issues/detail?id=375297 This looks like it's really close to being fixed though!
I was able to seed a 1GB file in Firefox and stream to Chrome!

This issue was moved to https://github.com/feross/webtorrent/issues/319.

authors: FesterCluck feross


text:
JSON errors in Syntastic

Syntastic is showing errors from Standard in various valid JSON files. When the same files are checked using the standard executable no errors are returned.
For example, this repository's package.json file is returning the following:
{
  "name": "standard",
  // …
}
// package.json|2 col 9 warning| Unexpected token : (undefined)

With arrays, double quotes are flagged:
[
  "string"
]
// ./array.json|2 col 4 warning| Strings must use singlequote. (quotes)

Any ideas?

Got it. JSON files were being detected as JavaScript files.
If anyone comes across this you can check by opening a JSON file and running :set filetype?. The response should be filetype=json.

repo: feross/standard


text:
Allow, or ignore, @ decorators

I have JS Standard running nicely on my project, with one annoying issue. My project is running in React and Webpack, with Babel, so I'm using shiny features such as decorators with frameworks like MobX (the framework I use to manage state).
The problem here is that JS Standard doesn't like, or shall we say recognise, what these decorators are. It will throw an error like: -
src/components/Avatar/Avatar.js:6:1: Parsing error: Unexpected character '@'
My React component might look something like this, as a really simple example: -
@CSSModules(styles, { allowMultiple: true })
class Avatar extends Component {
  render() {
    const { whatever } = this.props
    return <MyHtmlStuff whatever={whatever} styleName='example' />
  }
}

export default Avatar

It doesn't get the @CSSModules declaration in the above example. Is there something we can do to easily support this in a future release?
Cheers,
Owen

@owenayres does this solve your problem? https://github.com/feross/standard#how-do-i-use-experimental-javascript-es-next-features

@timoxley Yep, that fixed my issue. Thanks for linking me up, feel stupid for missing this...!

HI @owenayres , @timoxley
I am working on angular 5 application, I have a similar problem with decorator
import { Injectable } from '@angular/core'
@Injectable()
export class WindowService {
}

'Injectable' is defined but never used.

authors: owenayres progtarek timoxley


text:
allow hyper-rustls as an alternative for hyper-tls, set the default to neither

(Another attempt at @akru's #39.)

What's the reasoning behind removing the default? I think it might confuse people who are upgrading

What's the reasoning behind removing the default? I think it might confuse people who are upgrading

No particular reason, I probably misread your comment on the previous PR. I reverted that part.
Though there is one thing that does bother me a bit: There is no easy way to say "I want rust-ipfs-api with hyper, but without any TLS implementation". It's also not entirely clear which of the optional dependencies are supposed to be used as features, and how they depend on each other.
If you want me to, I can make another PR, reordering that a bit, maybe like this:
[features]
default           = ["with-hyper-tls", "with-builder"]
with-hyper-tls    = ["with-hyper", "hyper-tls"]
with-hyper-rustls = ["with-hyper", "hyper-rustls"]
with-hyper        = ["hyper", "hyper-multipart-rfc7578", "failure"]
with-actix        = ["actix-http", "actix-multipart-rfc7578", "awc", "derive_more"]
with-builder      = ["typed-builder"]

That should make it clear how the features are supposed to be used.

No particular reason, I probably misread your comment on the previous PR. I reverted that part.
Though there is one thing that does bother me a bit: There is no easy way to say "I want rust-ipfs-api with hyper, but without any TLS implementation". It's also not entirely clear which of the optional dependencies are supposed to be used as features, and how they depend on each other.
If you want me to, I can make another PR, reordering that a bit, maybe like this:
[features]
default           = ["with-hyper-tls", "with-builder"]
with-hyper-tls    = ["with-hyper", "hyper-tls"]
with-hyper-rustls = ["with-hyper", "hyper-rustls"]
with-hyper        = ["hyper", "hyper-multipart-rfc7578", "failure"]
with-actix        = ["actix-http", "actix-multipart-rfc7578", "awc", "derive_more"]
with-builder      = ["typed-builder"]

That should make it clear how the features are supposed to be used.

If you want me to, I can make another PR, reordering that a bit, maybe like this:

Yeah, I think this works. I'm fine with the with- prefix since it's consistent.
Thank you!

If you want me to, I can make another PR, reordering that a bit, maybe like this:

Yeah, I think this works. I'm fine with the with- prefix since it's consistent.
Thank you!

Here we go. I figured it'd be easier to handle if I just append it to this PR.

Here we go. I figured it'd be easier to handle if I just append it to this PR.

Nice, this looks good. I'll update the docs before publishing a new build

Nice, this looks good. I'll update the docs before publishing a new build

Hm, just noticed that this maybe isn't too optional: features should be strictly additive, so adding more features to a compiling crate should not make it not compile.
I think the solution would be to default to one if both are active. The sad part is that there doesn't seem to be a nice way to emit a warning in this case, and it will also make the cfg situation even more complicated, which you lament in #70. (Though I think there are ways to mitigate that.)

Yeah, I'm working on just having separate crates for each backend implementation which should simplify things a bit, but it's still pretty far off. It also won't fully solve the "mutually exclusive feature flag" issue, but it should make it way easier to understand

It wouldn't? If you have a trait IpfsClient and then an impl IpfsClient for IpfsClientHyper, either in a subcrate or behind a feature flag...?

Yeah because the TLS crates would still be mutually exclusive I think

IpfsClientHyperRusTLS? Mmmh. I suppose HyperConnector could also be a (struct) type argument (questionable whether to have three separate news, or one with a <T: Connect> parameter...)

authors: ferristseng jcaesar

repo: ferristseng/rust-ipfs-api


text:
French patch

Hi,
Some info about the patch :
Missing the API doc, Splatfest, Some gear stats, and some strings in a couple of files (i'm not very fluent in english).
There some string that i did, but missing the context, it may be incorrect.

Thank you.
I'll check the patch roughly and then merge it.

Could you create a new commit to update them and push it?

It's done.

Squash-merged your patch as 2995e0b68a75a745e585edf9feacd8642688be22 .
Merci beaucoup!

authors: fetus-hina ultrasonicytb


text:
[#81] Alterar ordem dos Campos em Criar Projeto

Descrição
Altera a ordem dos campos para a ordem TITULO, PROBLEMA ENFRENTADO, RESULTADOS DESEJADOS.

Issue
Refer: https://github.com/fga-eps-mds/2022-1-PUMA-Doc/issues/81

Principais Implementações
Altera a ordem dos campos no html da pagina.

Tipos de Mudanças

[ ] Bug fix (alteração que corrige uma issue e não altera funcionalidades já existentes);
[x] Nova feature (alteração que adiciona uma funcionalidade e não altera funcionalidades já existentes);
[ ] Alteração disruptiva (Breaking change) (Correção ou funcionalidade que causa alteração nas funcionalidades existentes);
[ ] Documentação

Percebi que o código está com um problema de que quando clicamos em criar projeto, redireciona para a página de listar disciplinas. Vou fazer um hotfix nisso.

authors: enzoggqs freitasc


text:
Constant page refresh after install

After installing Kanboard on Ubuntu 14.04.4 using docker, and connecting it to my Gitlab server I find myself unable to use it because after sign in any page I go to will constantly refresh. I noticed a few other people have flagged this issue, but no response so far.
I use the chrome plugin "redirect path" and it is showing a perpetual loop of javascript redirects.
I'm accessing my installation through chrome, however IE produces the same problem

I cannot really reproduce this issue at least with the last Docker image.
Can you describe how you are running the Docker image and how you access it?

authors: fguillot oszelaar

repo: fguillot/kanboard


text:
Warnings are being displayed as errors

Hi,
I have a rule as a warning and yet, it triggers a blocking popup box, that seems to be an error rather than a warning. Is there a way to avoid displaying warnings?
Thanks.

Yes it would be great to have this feature!

authors: GabriFila iKnowMagic


text:
🛑 Distribuidora RN is down

In 59ffe9c, Distribuidora RN (https://www.distribuidorarn.com.ar) was down:

HTTP code: 500
Response time: 17638 ms

Resolved: Distribuidora RN is back up in a4e5346.

repo: fideo/statusSites


text:
Add label for Input wrapper Blade components

Description
This pull request introduces labels for the Input Wrapper Blade component, as this is currently not supported. By clearly associating text labels with input fields, we enhance user experience, making forms more intuitive and easier to navigate.

Code style
Simply add the new label attribute to the <x-filament::input-wrapper> component.

[x] composer cs command has been run.

Testing

[x] Changes have been tested.

Documentation

[x] Documentation is up-to-date.

The label isn't the responsibility of the input wrapper component.
Instead, it's part of the field wrapper.
I'm not sure if it's currently possible to use the field wrapper as a Blade component instead of using Filament Forms, but you could give it a try.
If it doesn't work, I'm happy to review a PR that adds support for using it standalone. 🙂

In that case, wouldn't it make more sense to have the Field wrapper available as core component?

authors: mischasigtermans zepfietje

repo: filamentphp/filament


text:
Add troubleshooting to 'Adding a form to a Livewire component'

Description
This PR adds a troubleshooting section to 'Adding a form to a Livewire component' with a problem I faced recently. When installing Filament in Laravel, you usually don't have to add the @filemanetStyle and @filamentScripts to your layout, unless you add forms to your front-end application. Therefore I think it would be good to point users to the instructions once again.

[x] Visual changes (if any) are shown using screenshots/recordings of before and after.

Code style

[x] composer cs command has been run.

Testing

[x] Changes have been tested.

Documentation

[x] Documentation is up-to-date.

I understand you don't need to do this for the admin panel, but there are many other instructions to follow other than adding these directives to your layout - such as setting up Tailwind with the preset. I hope most people will read the installation instructions of the package they use before they read pages in that package documentation

authors: danharrin vjanssens


text:
add ability

in  normal mode can search in db with
$db->where('name','==','sam')->first();
with this commit changes can search  in other way easy and shorter :
$db->whereName('sam')->first(); // equals with ('name','==','sam')
also can set oparator
$db->whereName('like','sam')->first(); // equals with ('name','like','sam')

where* can be use for all custom names like whereEmail, whereHGFJH , ...

.
.
.

Pull Request Test Coverage Report for Build 150

24 of 25 (96.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 94.801%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Query.php
15
16
93.75%

Files with Coverage Reduction
New Missed Lines
%

src/Database.php
1
74.1%

Totals

Change from base Build 148:
-0.1%

Covered Lines:
547

Relevant Lines:
577

💛  - Coveralls

on my mistake some commits are duplicate :/

I like the simplicity. To confirm, using whereUserProfile() would be user_profile as the column/field? Off-topic, but eventually I do want to include more of a Laravel-style collection on these results. I know we have the Document class, but we do need more functionality with that. Most likely will be a V2 or a 1.1. Also, are you on Slack? Should be a join link in the readme. Would love to connect.

hi, for your example,  should look like this
whereUser_profile
But with a little change it can be similar to laravel_query_builder.
Thanks about slack I joined

hi, for your example, look like this
whereUser_profile
But with a little change it can be similar to laravel_query_builder.

I would recommend we make it so
whereUserProfile('Tim') = the same as WHERE user_profile = 'Tim'
This way it's more universal to understand (and we don't mismatch, always using camel-case in methods)

now can select "user_profile_is_with_some_query" with
$db->query()->whereUserProfileIsWithSomeQuery('data')->first(); also  $db->query()->whereuser_profile_is_with_some_query('data')->first();
to select "User"
whereUser or whereuser
to select "UserOwner"
whereUserowner or whereuserowner

authors: coveralls faryar76 timothymarois

repo: filebase/Filebase


text:
Client Allocation Request for: Plant Research South China Base of China Agricultural University

Client Allocation Questions
Core Information

Name: Plant Research South China Base of China Agricultural University
Website / Social Media: http://vetetable.com/
Region: Greater China
DataCap Requested: 10TiB
Addresses to be Notarized: f15d5pxriekd6rcxx2t5xlebbubc5qlqtcuyewxfy
Notary Requested: dannyob

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

Hi! Could you request this through a notary in your region? A list is available here: https://plus.fil.org/verifiers


text:
PDF file preview in Files and add Tags

What feature or improvement do you think would benefit Files?
Hello,
I'm currently testing if Files (3) is the solution for my file management requirements.
For now (after 10 minutes of testing) I have two improvements I'd like to request:

I don't see a preview for a (selected) pdf file. Could that be added?
When I want to add a not-yet-existing tag to a file, I should be able to make the new tag on the fly and find it added to the Tags list afterwards. Could you make that possible?

GrZ Bart Hoeksel, Nedcom
Requirements

Adding PDF preview will make it possible to preview PDF files in Files
Adding new Tags to files from contextual menu will make it possible to add new tags quicker

Files Version
3.2.3.0
Windows Version
Edition	Windows 11 Home Version	23H2 Installed on	28-9-2022 OS build	22631.3235 Experience	Windows Feature Experience Pack 1000.22687.1000.0
Comments
No response

Thanks for the feedback, You can open the info pane (Ctrl + Alt + i) and click preview and were tracking your second request in #12146. You can check there or click subscribe in the right sidebar for updates.

repo: files-community/Files


text:
Tag still cause crash after the update, and the same thing happens in the preview version.

Description
This is a continuation of the question I asked last time.
I compared the preview version with the official version and recorded.
https://github.com/files-community/Files/issues/15413

The video shows the Preview Version without my old tag datas(in official version path), it doesn't crash.
https://github.com/files-community/Files/assets/81501083/0a767446-8c45-4f2c-b12f-24206d2627ea
When I copy the old Tag data into the Preview version path,
The Tags in perview Version  are  the same as the Tags in official  Version .
https://github.com/files-community/Files/assets/81501083/883dc85f-2be5-4a26-892b-752101cae7b2
Steps To Reproduce
Steps To Reproduce

Right-click on the file to edit the tags.
Files APP crash.
(manually, not automatically) Reopen the files app.
Check this path: C:\Users"myUserName"\AppData\Local\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState
Reopen the Files APP after it has crashed, and this path will add an new file.
"filestags-temp-1.db","filestags-temp-1-log.db",and 2,3,4,......

Requirements

e.g. Fix crash that occurs when...

Files Version
3.4.1.0
Windows Version
11
Log File
debug.log

We no longer use the LiteDB for tags storage anymore.
When you copy those files under LocalState, can you try skipping the filetags.db?

Delete the old .db  files, The problem is solved..


text:
When press any letter on keyboard doesnt go to file which start with that letter

Description
On default explorer when I press key P for example it's go-to first file which starts with P, on files this doenst occur.
Steps To Reproduce

press any letter on a large folder who has a lot of files
Files stay on the top of folder, doenst go to file with that letter

Expected behavior
When any key pressed, go to first file with that letter
Files Version
Versão: 2.0.13.0 OS Version: 10.0.22471.1000
Windows Version
Windows 11 Pro Insider Preview 22471.1000
Relevant Assets
No response

Merging with #6322


text:
Fix: Fixed an issue where right clicking empty space didn't clear selection

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 #12402

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?

Open app
Selected some items
Right click on white space

I think that would be the expected behaviour by most users

I tested column layout again, it's not working if a single folder is selected but it does work if multiple folders are selected.

Ok, I'll look into this as soon as I can


text:
Feature: Added support for Infomaniak kDrive

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 #15475

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.

kDrive is displayed in Files and copying of files etc. is possible

Note: The Sync Status column is not displayed, but this does not work in Windows File Explorer either. I think kDrive does not set the property “System.FilePlaceholderStatus” correctly, which Files (and probably also Windows File Explorer) uses to find out the status.

@mafra99 does this still work if the user changes the location from kDrive settings?

I have just reinstalled kDrive and now the entry in the registry no longer contains an application name, but only an ID. As a result, kDrive is no longer recognized on my device.

I can think of two other ways to recognize kDrive anyway:

Using the DefaultIcon under Computer\HKEY_CLASSES_ROOT\CLSID<>\DefaultIcon to check whether the path contains kDrive

Via the entry in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SyncRootManager

To use the entry from SyncRootManager seems safer to me, I have pushed a commit that contains the changes for this.
In the second commit I cleaned up the code a bit and fixed a few warnings.
The method GetDriveType is new and returns the drive type, e.g. iCloudDrive or kDrive. This should make the method DetectGenericCloudDrive a little simpler.
Compared to before, the DriveType is now returned directly as soon as one is detected and the checks for the other DriveTypes are no longer executed.

@mafra99 does this still work if the user changes the location from kDrive settings?

@yaira2 thanks, that actually didn't work. should also be fixed


text:
ScriptRunner.Execute overload should delegate to virtual version

Commit e4106437912b648efd2f759789a25d0cd3de5afd introduced a new virtual Execute overload on ScriptRunner and broke debugging. There should really only be one virtual of Execute and all other (present & future) overloads should delegate to it, which is what this PR does. It removes duplicate code between the overloads, and more importantly, fixes the debug scenario. You see, DebugScriptRunner inherits from ScriptRunner and overrides Execute. While e4106437912b648efd2f759789a25d0cd3de5afd introduced two virtuals, DebugScriptRunner overriddes just one of them but not the one the entry-points calls.

Thanks :+1:

authors: atifaziz filipw

repo: filipw/dotnet-script


text:
Add Google-Maps directions link to the address in map-bubble/listings

Seems like an easy addition that might help conversion to connect donors with recipients.
Downside: May encourage people to go direct to the address without contacting recipient ahead of time.

Duplicate of https://github.com/findthemasks/findthemasks/issues/126

repo: findthemasks/findthemasks


text:
Disable Vertical Scroll Bar

The Vertical Scrollbar kind of makes the UI harder to use, I suppose removing the scrollbar is better. It can be done by fixing footer

I'd like to work on this issue if you could assign me.

hey i am interest to solve this issue can u assign me this

authors: SankalpaFernando lakshangan

repo: fineanmol/Annoying-submit-button


text:
Suggestion: Move PR build pipelines to GitHub actions for visibility

Feature Request
Description of Problem:
Currently the status and result of the PR build pipelines are opaque to the community contributors since they run in a closed environment.
Potential Solutions:
Suggestion to move the PR build pipelines to GitHub actions making the results visible for all.

Yes, I thought about that too. I need to deploy docker images to a public repo first. I have that on my to do list.

@marcusspangenberg, @olofkallander, I finally moved PR checks to gitactions. PR was already merged #381

authors: RicardoMDomingues marcusspangenberg

repo: finos/SymphonyMediaBridge


text:
fix storetype typo

What type of PR is this?

What does this PR do / why is it needed ?

Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

O so

repo: finos/legend-engine


text:
bigquery-export: Add document.id to BigQuery tables

[REQUIRED] Step 2: Extension name
This feature request is for extension: firestore-bigquery-export
What feature would you like to see?
For this feature to be useful to me, I really need the firestore document's id exposed as a single field in the generated tables. Currently, the fully qualified document_name is provided, but this includes a bunch of additional prefixes that makes it really difficult/cumbersome to join across tables.
How would you use it?
I want to use the big query tables to power DataStudio as well as for running one-off queries to better understand my app's usage.
I often store data semi-normalized using document identifiers, such as memberId (which is like a userId), and then need to join to the memebers collection, using memberId as the join key.
Currently, I would have to concact a string together to join on document_name in this format
projects/XX-project-nameXX/databases/(default)/documents/members/<my member document id>

Hi, it looks like now import has the document id column, however the extension which sync the firestore with bigquery table does not include document id column so the table now has imported rows with document id, created rows without

Hi, may I know about the current state of this feature? It looks like IMPORTS generates the document_id filled-id with the document ID however CREATE/UPDATE leave this column blank, which creates inconsistencies

@mustafaekim May I ask what version of the firestore-bigquery-export extension you're using? You should be able to see it in your Firebase console dashboard in the extension's tab.

Hi, it is Version 0.1.5
Thanks for getting back

If you head to your firestore-bigquery-export extension in the extension's tab on the Firebase console, you ought to be able to update to version 0.1.6 which has the document_id update.

Great, thanks. Do you have any recommentation to fix the previous records? Should I delete the table and import again?

That would be my recommendation 😄 .

authors: Neilpoulin mustafaekim russellwheatley

repo: firebase/extensions


text:
fix(firestore-send-email): downgrade error to warn

should fix https://github.com/firebase/extensions/issues/1516

closed as duplicate


text:
[FR] Add API for validating FCM tokens

Is your feature request related to a problem? Please describe.
There are often situations when you need to verify from which platform IOS or Android a specific registration token was received on server.
Describe the solution you'd like
There is a  google api for this, but is not included in either firebase-admin-node or googleapis SDK.
Describe alternatives you've considered
An alternative solution would be to call the API directly via HTTP.

Thanks for the request. There was a similar request for the Python Admin SDK: https://github.com/firebase/firebase-admin-python/issues/204 The response posted there is still up-to-date.
If no objections, I'll leave this FR open to avoid duplicated FRs being created.

Thank you for your quick response!
Do you maybe already have the information when this Identity ID API will be replaced with the new API (Firebase Installation Service and Firebase Registration Service)?

I don't have a specific timeline to share at this moment. Please stay tuned.

authors: chong-shao kzupan

repo: firebase/firebase-admin-node


text:
firebase-auth updateUser with providerToLink using "password" as providerId

Hey I'm trying to link providerData with providerId = "password" using firebase admin SDK
environment :

Firebase SDK version:  10.0.2
Firebase Product: auth
Node.js version: 16.13.0
NPM version: 8.1.0

The problem
I'm trying to link providerData using firebase admin SDK in order to link providerData with providerId = "password" .
I'm using updateUser method and pass providerToLink object in order to link providerData.
updateUser method will return this error :

code : auth/invalid-provider-id
message : The providerId must be a valid supported provider identifier string.

Relevant Code:
await admin
            .auth()
            .updateUser(user.uid, {
                providerToLink: {
                    uid: user.email,
                    email: user.email,
                    displayName: user.displayName,
                    providerId: 'password',
                },
            })
            .catch((error: any) => {
                console.error(`${error}`);
            });

If I understand correctly providerToLink is used when you want to link a user to a specific provider, such as google.com. If you want to set a password to a user you should be able to set it in the updateUser payload. I may have misunderstood your requirement here. Adding @prameshj for more context.

The list of valid provider ids can be found by invoking this API call - https://cloud.google.com/identity-platform/docs/reference/rest/v2/defaultSupportedIdps/list
In this case, is a password change being attempted?

Have you found the answer?

I don't think you can link a password provider directly. You could just call updateUser with the email you want (and the password when you know it).
That's odd because you can unlink a password provider.

If you're trying to update user password and add password as the new provider, you can just unlink other provider & set new password in updateUser, then sign in with new password and email with signInWithEmailAndPassword and pass the new password & email to it.

what if i'm trying to have multiple emails for one user?  setting email on the UpdateRequest replaces the email.

I ran into this yesterday, and adding to what @MichaelBorde mentions, in 2024 and on firebase ~ 10.7.2 you MUST set a password for providerData to be populated, OR it will be linked after the user logs in with passwordless login (email link).
(+, In the case where a user's email is changed, either by himself or by an admin, the auth user is correctly updated with providerData[] but he's immediately logged out and must re-login with his [new] email. Haven't found a way to change emails on a user without the user being kicked out)
If not setting a password, or until the user has logged in with his new email:

After setting a password/ logging in:

authors: AminAtwi-ITXI MichaelBorde arnotixe jayenashar lahirumaramba prameshj sberkaye tahmassraheem1


text:
Internal Updates

Description
Adds AdListener support for NativeAd.

Testing
N/A

Type of Change
Place an x the applicable box:

[ ] Bug fix. Add the issue # below if applicable.
[x] New feature. A non-breaking change which adds functionality.
[ ] Other, such as a build process or documentation change.

Notes
Internal Updates only.

Will any of this break with the iOS 11.0.1 release? (I'm in the process of updating to it now.)

Will any of this break with the iOS 11.0.1 release? (I'm in the process of updating to it now.)

Doesn't look like workflows related to adlistener are changed in the recent release. So this update should be compatible.

Approved with one small issue

Addressed the comment. Thank you for the quick review Jon!

authors: jonsimantov nakirekommula

repo: firebase/firebase-cpp-sdk


text:
Failed Submission Checks with Error ITMS-91065: Missing Signature

Description
What We Use Firebase For

Analytics

How We Use Firebase
At my company, we have an analytics framework (dynamic), which defines protocols and wrappers to allow integration of more than one analytics service. This is where our implementation of Fireworks lives. We recently updated our framework to target 10.25.0 for Firebase.
One thing to note here is that our CI/CD pipeline uses older version of Xcode, 15.0.1, as opposed to Xcode 15.2 like the release notes says this version requires. We saw the requirement at the time, but after testing it internally, everything seemed to be in order. Therefore, we proceeded with 10.25.0 still.
Failed Submission Checks
Yesterday, when we submitted one of our apps for review for the purpose of distributing TestFlight builds on App Store Connect, we got the error: ITMS-91065: Missing signature.

At this point, we realized our integration of Firebase is likely incorrect. After some research, I realized we're supposed to embed and sign static xcframeworks. I made the appropriate changes in addition to add PrivacyInfo.xcprivacy in our own framework, and exported the xcframework and made a test build.
After uploading using Transporter, I got this error:
Asset validation failed (90085)
No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. (ID: ecb746c1-c4aa-4750-94a6-3598cbe7a0ce)

After some research, the issue seems to be the Info.plist in the embedded frameworks from Firebase now. Using FirebaseCore.framework as example, its Info.plist specifies that CFBundleExecutable is FirebaseCore. Yet the executable is nowhere to be found within FirebaseCore.framework because it's a static library.

Questions
It's very likely that the issue lies in our project configuration and setup instead of anything on the Firebase side. However, I'd like some assistance confirming it.
Is using lower version of Xcode (15.0.1 instead of 15.2) a factor here?
According to the integration instructions included in Firebase.zip and Apple's own instructions, we're supposed to choose the Embed & Sign option for static frameworks since Xcode 15. However, the change is giving me the above Asset validation failed (90085): No architectures in the binary issue. Do these steps change if we're using Firebase in our library project instead of app project?
Expected Outcome
App integrated with Firebase can go through Apple review without issue.
Reproducing the issue

Create a dynamic framework project in Xcode
Follow integration steps in Firebase.zip in the releases
Build and export xcframework
Create an app project in Xcode
Include the xcframework from step 3
Build and export the IPA
Upload via Transporter
Observe error: Asset validation failed (90085) No architectures in the binary

Firebase SDK Version
10.25.0
Xcode Version
15.0.1
Installation Method
Carthage
Firebase Product(s)
Analytics
Targeted Platforms
iOS
Relevant Log Output
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!

See the code signature file in the file hierarchy. With the new code signing requirements, the FirebaseCore xcframework must be linked as is:

There may also be issues using an Xcode version before Xcode 15.2, since Apple's linker do not guarantee support of linking objects from future versions.

@paulb777 Thanks for the quick reply. I am going to try to compile and export the xcframework manually with newer Xcode to see if that does the trick.

To give an update, unfortunately, using Xcode 15.2+ didn't fix the issue. I still got the same error when uploading via Transporter, which complained about no architecture in the binary that doesn't exist.
Failing that, I tried to switch to Swift Package Manager from Carthage to rule out Carthage being the problem. At the end, I ran into more issues with our CI/CD, which I didn't see when building locally. I took the xcframework that I built locally and put it into the app project and got errors about Firebase framework not found.
At this point, I think the issue is one of the following:

There's unknown issue with our project setup that removes the binary itself along with the codesign folder.
Including a static framework within a dynamic framework while the former needs to be signed simply isn't supported by Apple.

I then pivoted and started removing our Firebase integration and implementation in the library, and moved it to the app project itself. No issues were observed when uploading through Transporter. The build was processed, then I submitted it for review to distribute to external group on TestFlight. I will report back after it's reviewed.

@lancefu-eventbase
Have any progress？

@lancefu-eventbase Have any progress？

@zhaojb9 After removing Firebase from our library and moving it to the app itself, everything looks fine. Apple has reviewed the app for test build distribution and we're able to use it to verify things are in order as well on the Firebase integration side. Ideally, we'd prefer leaving the integration code in our library. However, we're rushing to get it "fixed" so that app submissions won't be blocked. I will circle back if I learn more.
I also posted on Apple Forum, but it didn't get any traction unfortunately. See https://forums.developer.apple.com/forums/thread/751766.

Thanks for sharing @lancefu-eventbase! I'll close for now and we can reopen with new information.

@lancefu-eventbase
Sorry, I also want to confirm some information. Have you tried including Firebase in your own library, then signing your own library, and then submitting it for review. After my investigation, I found that the Signatures folder in the archive directory after the app is packaged contains the signature information files of all frameworks. These files should be uploaded to the appstore for review and confirmation by reviewers.
After we manually signed our library, this folder contains the signature information, but I am not sure whether the firebase inside the library will also pass the review because of the signature of our library. I think Apple’s intention is to make the SDK signature tamper-proof, so the SDK signature after secondary packaging should also meet Apple’s requirements. I think Apple will not record the SDK signature, but only check whether it is valid.

After my continued investigation, I will share the following information with you
Whether a signature is required varies depending on how the SDK is introduced.

If the SDK is imported from source code, no signature is required, because you have to bear the responsibility of trusting the source code yourself (such as pod introduction)
If you download the Xcode project file of this SDK and compile it yourself, and then introduce it through xcframework (officially said binary), this xcframework needs to be signed. The signatures mentioned here can be signed by yourself. Because the open source is the source code, and the signature should be done by the person who generated xcframework. If you don't want to sign, you can introduce it through pod (source code).

I hope to be helpful.

@lancefu-eventbase Sorry, I also want to confirm some information. Have you tried including Firebase in your own library, then signing your own library, and then submitting it for review. After my investigation, I found that the Signatures folder in the archive directory after the app is packaged contains the signature information files of all frameworks. These files should be uploaded to the appstore for review and confirmation by reviewers. After we manually signed our library, this folder contains the signature information, but I am not sure whether the firebase inside the library will also pass the review because of the signature of our library. I think Apple’s intention is to make the SDK signature tamper-proof, so the SDK signature after secondary packaging should also meet Apple’s requirements. I think Apple will not record the SDK signature, but only check whether it is valid.

Yes, I have tried.
If I embed the Firebase xcframeworks in our library, then the IPA file will have modified contents within those xcframeworks and the actual executable and code signature folder removed. The xcframeworks all get signed by our distribution certificate, but not Google's. Uploading this IPA via Transporter will result in an error as mentioned previously:
Asset validation failed (90085)
No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. (ID: ecb746c1-c4aa-4750-94a6-3598cbe7a0ce)

If you get a different result, I'd love to hear what your setup is like. We are using a rather old Xcode version at 15.0.1. I don't know if Carthage or Fastlane does something funny to cause this either.

@lancefu-eventbase
After I signed it myself, no errors occurred when I uploaded it through xcode.
Let me briefly share my operation process.

Use Xcode15.1 to sign our internally packaged SDK, using the company's developer plan, and the signing process uses a python script written by GPT instead of xcode
The signed xcframework will be displayed as verified in xcode, and the unsigned framework will be displayed as unsigned.
The signing process is carried out before the app is archived, because I found that the signature information is not saved in the .app folder, but in an external archive folder, and will be uploaded to the apple server when xcode is uploaded.

I have never used Transporter and I don’t know if the problem you are talking about is a compatibility issue that causes the upload to fail. I always upload directly through Xcode.

@lancefu-eventbase
Latest results.
Apple has successfully passed the review.
So I need to summarize.

The SDK developer of the binary distribution cannot confirm the source code, so the packager needs to sign it to confirm whether the SDK has been tampered with.
Since Firebase pod is a source code reference, when performing secondary distribution of the SDK, the person who ultimately distributes the SDK needs to sign his or her own SDK.

repo: firebase/firebase-ios-sdk


text:
Occasional fatal crash with connectivity constraint on job

The stack trace:
Exception java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in com.google.firebase.iid.zzae@e69a4c8
android.app.LoadedApk$ReceiverDispatcher$Args.run (LoadedApk.java:1214)
android.os.Handler.handleCallback (Handler.java:751)
android.os.Handler.dispatchMessage (Handler.java:95)
android.os.Looper.loop (Looper.java:154)
android.app.ActivityThread.main (ActivityThread.java:6316)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:872)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:762)

Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.net.NetworkInfo.isConnected()' on a null object reference
com.google.firebase.iid.zzad.zzchp ()
com.google.firebase.iid.zzae.onReceive ()
android.app.LoadedApk$ReceiverDispatcher$Args.run (LoadedApk.java:1196)
android.os.Handler.handleCallback (Handler.java:751)
android.os.Handler.dispatchMessage (Handler.java:95)
android.os.Looper.loop (Looper.java:154)
android.app.ActivityThread.main (ActivityThread.java:6316)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:872)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:762)

The phone details:
Model: LG-K550
Android API: 24
Connection State: Disconnected

This crash was reported to Firebase, so I haven't been able to reproduce it on my devices.

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.

authors: magneticflux- samtstern

repo: firebase/firebase-jobdispatcher-android


text:
🐛 [firebase_auth] authStateChanges is not called after linkWithCredential

Bug report
Describe the bug
authStateChanges gets not notified about a user changed from anonymous to authenticated by calling linkWithCredential.
Steps to reproduce
Steps to reproduce the behavior:

Add a listener to FirebaseAuth.instance.authStateChanges()
Call FirebaseAuth.instance.signInAnonymously()
Call FirebaseAuth.instance.linkWithCredential()
See that FirebaseAuth.instance.currentUser?.isAnonymous has changed, but the listener was not called

Expected behavior
FirebaseAuth.instance.authStateChanges() should emit an event when the user is linked to credentials.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.5, on macOS 13.2 22D49 darwin-arm64 (Rosetta), locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc3)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.75.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues **found!**

Thanks for the report @guenth39
I tried the plugin example by including the steps to replicate you mentioned, but was unable to replicate the reported behavior. Can you provide us complete code sample that we can use to verify this ?

In case someone is looking for the answer to the same problem. authStateChanges doesn't fire when this events happend:
reload()
linkWithCredential()
unlink()
updateEmail()
updatePassword()
updatePhoneNumber()
updateProfile()

But the event that will fire is userChanges(). It works the same as authStateChanges.
Hope it helps. Already made a suggestion to change it in the docs.

In case someone is looking for the answer to the same problem. authStateChanges doesn't fire when this events happened:
reload()
linkWithCredential()
unlink()
updateEmail()
updatePassword()
updatePhoneNumber()
updateProfile()

But the event that will fire is userChanges(). It works the same as authStateChanges.
Hope it helps. Already made a suggestion to change it in the docs.

authors: Flucadetena darshankawar guenth39

repo: firebase/flutterfire