text:
Supply: Error 404 (Not Found) Google Api Error: Invalid request

I am having the below error while uploading the APK to PlayStore by using the supply command.
Google Api Error: Invalid request - <!DOCTYPE html>

  <meta charset=utf-8>
  <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
  <title>Error 404 (Not Found)!!1</title>

  **

404. That’s an error.

The requested URL /androidpublisher/v2/applications/{packageName}/edits? was not found on this** server.  That’s all we know.

Here is my setup for the supply command
+-------------------------+----------------------------------------------------------------------------------------+
|                                            Summary for supply 2.123.0                                            |
+-------------------------+----------------------------------------------------------------------------------------+
| track                   | alpha                                                                                |
| skip_upload_metadata    | true                                                                                |
| skip_upload_images      | true                                                                                |
| skip_upload_screenshots | true                                                                                |
| validate_only           | false                                                                                |
| apk                     | {pathToApk}                                                                            |
| package_name            | {packageName}                                                                          |
| metadata_path           | ./fastlane/metadata/android                                                            |
| json_key                | ./google-key.json                                                                      |
| skip_upload_apk         | false                                                                                |
| skip_upload_aab         | false                                                                                |
| check_superseded_tracks | false                                                                                |
| timeout                 | 300                                                                                |
| deactivate_on_promote   | true                                                                                |
+-------------------------+----------------------------------------------------------------------------------------+

Stack

Key
Value

OS
10.15.7

Ruby
2.6.5

Bundler?
false

Git
git version 2.29.2

Installation Source
~/.rbenv/versions/2.6.5/bin/fastlane

Host
Mac OS X 10.15.7 (19H2)

Ruby Lib Dir
~/.rbenv/versions/2.6.5/lib

OpenSSL Version
OpenSSL 1.1.1h  22 Sep 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
12.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
```ruby
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command
# If you want to automatically update fastlane if a new version is available:
#update_fastlane
fastlane_version "2.38.1"
default_platform :android
platform :android do
    desc "Deploy a new version to the Google Play"
    lane :release do
    gradle(task: "")
    gradle(task: "") // build APK
    supply(
        track: "alpha",
        #rollout: 0.5,
        skip_upload_metadata: true,
        skip_upload_images: true,
        skip_upload_screenshots: true,
        validate_only: false
    )
    post_to_slack_no_payload(
        message: getPvtSlackMessage("App Center"),
        channel: "mobilesquad_bots"
    )
    end
end
```

`./fastlane/Appfile`
```ruby
# Path to the jason secret file, by using a relative path it means fastlane can only be run from the project root directory
json_key_file ""
package_name ""
```

### fastlane gems
| Gem      | Version | Update-Status      |
| -------- | ------- | ------------------ |
| fastlane | 2.166.0 | 🚫 Update available |
### Loaded fastlane plugins:
| Plugin                           | Version | Update-Status |
| -------------------------------- | ------- | ------------- |
| fastlane-plugin-get_version_code | 0.2.0   | ✅ Up-To-Date  |
| fastlane-plugin-appcenter        | 1.11.1  | ✅ Up-To-Date  |
| fastlane-plugin-badge            | 1.5.0   | ✅ Up-To-Date  |
Loaded gems
| Gem                              | Version      |
| -------------------------------- | ------------ |
| did_you_mean                     | 1.3.0        |
| slack-notifier                   | 2.3.2        |
| atomos                           | 0.1.3        |
| CFPropertyList                   | 3.0.3        |
| claide                           | 1.0.3        |
| colored2                         | 3.1.2        |
| nanaimo                          | 0.3.0        |
| xcodeproj                        | 1.19.0       |
| rouge                            | 2.0.7        |
| xcpretty                         | 0.3.0        |
| terminal-notifier                | 2.0.0        |
| unicode-display_width            | 1.7.0        |
| terminal-table                   | 1.8.0        |
| plist                            | 3.5.0        |
| public_suffix                    | 4.0.6        |
| addressable                      | 2.7.0        |
| multipart-post                   | 2.0.0        |
| word_wrap                        | 1.0.0        |
| tty-screen                       | 0.8.1        |
| tty-cursor                       | 0.7.1        |
| tty-spinner                      | 0.9.3        |
| babosa                           | 1.0.4        |
| colored                          | 1.2          |
| highline                         | 1.7.10       |
| commander-fastlane               | 4.4.6        |
| excon                            | 0.78.1       |
| ruby2_keywords                   | 0.0.2        |
| faraday                          | 1.1.0        |
| unf_ext                          | 0.0.7.7      |
| unf                              | 0.1.4        |
| domain_name                      | 0.5.20190701 |
| http-cookie                      | 1.0.3        |
| faraday-cookie_jar               | 0.0.7        |
| faraday_middleware               | 1.0.0        |
| fastimage                        | 2.2.0        |
| gh_inspector                     | 1.1.3        |
| json                             | 2.1.0        |
| mini_magick                      | 4.11.0       |
| rubyzip                          | 2.3.0        |
| security                         | 0.1.3        |
| xcpretty-travis-formatter        | 1.0.0        |
| dotenv                           | 2.7.6        |
| bundler                          | 1.17.2       |
| naturally                        | 2.2.0        |
| simctl                           | 1.6.8        |
| jwt                              | 2.2.2        |
| uber                             | 0.1.0        |
| declarative                      | 0.0.20       |
| declarative-option               | 0.1.0        |
| representable                    | 3.0.4        |
| retriable                        | 3.1.2        |
| mini_mime                        | 1.0.2        |
| multi_json                       | 1.15.0       |
| signet                           | 0.14.0       |
| memoist                          | 0.16.2       |
| os                               | 1.1.1        |
| googleauth                       | 0.14.0       |
| httpclient                       | 2.8.3        |
| google-api-client                | 0.38.0       |
| google-cloud-env                 | 1.4.0        |
| google-cloud-errors              | 1.0.1        |
| google-cloud-core                | 1.5.0        |
| rake                             | 12.3.2       |
| digest-crc                       | 0.6.2        |
| google-cloud-storage             | 1.29.1       |
| emoji_regex                      | 3.2.1        |
| jmespath                         | 1.4.0        |
| aws-partitions                   | 1.404.0      |
| aws-eventstream                  | 1.1.0        |
| aws-sigv4                        | 1.2.2        |
| aws-sdk-core                     | 3.110.0      |
| aws-sdk-kms                      | 1.39.0       |
| aws-sdk-s3                       | 1.86.0       |
| forwardable                      | 1.2.0        |
| logger                           | 1.3.0        |
| stringio                         | 0.0.2        |
| ipaddr                           | 1.2.2        |
| openssl                          | 2.1.2        |
| ostruct                          | 0.1.0        |
| strscan                          | 1.0.0        |
| date                             | 2.0.0        |
| fileutils                        | 1.1.0        |
| etc                              | 1.0.1        |
| zlib                             | 1.0.0        |
| racc                             | 1.5.2        |
| nokogiri                         | 1.11.1       |
| rexml                            | 3.1.9        |
| psych                            | 3.1.0        |
| mutex_m                          | 0.1.0        |
| webrick                          | 1.4.2        |
| fastlane-plugin-get_version_code | 0.2.0        |
| fastlane-plugin-appcenter        | 1.11.1       |
| csv                              | 3.0.9        |
| badge                            | 0.13.0       |
| fastlane-plugin-badge            | 1.5.0        |

Hi @zekapp, it seems that you try to use very old version of supply tool (Android Publisher v2 API is not supported anymore).
Please update to the newest fastlane version.
You can read more in https://github.com/fastlane/fastlane/issues/14573

Yes. Please try the latest one.
We've migrated the SDK of Google's APIs in #18656 lately, which should work for you.

authors: ainame lucgrabowski zekapp


text:
match exposes Git repository credentials

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
When match fails to clone the Git repository, it prints the entire Git command executed to the console. This includes the Authorization header that it's using, which in the case of basic HTTP auth means that it contains the password for the repo (which, in the case of GitHub, is a personal access token).
This is dangerous as it could lead to this credential being exposed in continuous integration logs. There is no option to disable this behaviour (furthermore, it feels like it should be opt-in if anything).
The relevant part of my fastlane output below is this line:
git clone https://github.com/lawrence-forooghian/macdown-match.git /var/folders/q2/88t_3skx1rn0gn9znm57tc3c0000gn/T/d20221223-12740-q7tb2h -c http.extraheader='Authorization: Basic ZmFrZS11c2VybmFtZTpmYWtlLWFjY2Vzcy10b2tlbg=='

We see that the raw password is exposed (I've used some dummy values):
> $ echo "ZmFrZS11c2VybmFtZTpmYWtlLWFjY2Vzcy10b2tlbg==" | base64 -d
> fake-username:fake-access-token

Command executed
bundle exec fastlane certificates (see my Matchfile; it just wraps match)
Complete output when running fastlane, including the stack trace and command used

[08:32:51]: Driving the lane 'certificates' 🚀
[08:32:51]: -------------------
[08:32:51]: --- Step: match ---
[08:32:51]: -------------------
[08:32:51]: Successfully loaded '/Users/lawrence/code/forks/macdown/fastlane/Matchfile' 📄
+--------------+--------------------------------------+
|     Detected Values from './fastlane/Matchfile'     |
+--------------+--------------------------------------+
| git_url      | git@github.com:lawrence-forooghian/  |
|              | macdown-match.git                    |
| platform     | macos                                |
| storage_mode | git                                  |
| username     |                 |
+--------------+--------------------------------------+
+--------------------------------------+--------------------------------------+
|                          Summary for match 2.211.0                          |
+--------------------------------------+--------------------------------------+
| app_identifier                       | ["com.example.myAppName"]            |
| git_url                              | https://github.com/lawrence-foroogh  |
|                                      | ian/macdown-match.git                |
| git_basic_authorization              | ********                             |
| type                                 | development                          |
| readonly                             | false                                |
| generate_apple_certs                 | true                                 |
| skip_provisioning_profiles           | false                                |
| username                             |               |
| storage_mode                         | git                                  |
| git_branch                           | master                               |
| shallow_clone                        | false                                |
| clone_branch_directly                | false                                |
| skip_google_cloud_account_confirmat  | false                                |
| ion                                  |                                      |
| keychain_name                        | login.keychain                       |
| force                                | false                                |
| force_for_new_devices                | false                                |
| include_mac_in_profiles              | false                                |
| include_all_certificates             | false                                |
| force_for_new_certificates           | false                                |
| skip_confirmation                    | false                                |
| safe_remove_certs                    | false                                |
| skip_docs                            | false                                |
| platform                             | macos                                |
| derive_catalyst_app_identifier       | false                                |
| fail_on_name_taken                   | false                                |
| skip_certificate_matching            | false                                |
| skip_set_partition_list              | false                                |
| verbose                              | false                                |
+--------------------------------------+--------------------------------------+
[08:32:51]: Cloning remote git repo...
[08:32:51]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
Cloning into '/var/folders/q2/88t_3skx1rn0gn9znm57tc3c0000gn/T/d20221223-12740-q7tb2h'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
[08:32:51]: Exit status: 128
[08:32:51]: Error cloning certificates repo, please make sure you have read access to the repository you want to use
[08:32:51]: Run the following command manually to make sure you're properly authenticated:
[08:32:51]: $ git clone https://github.com/lawrence-forooghian/macdown-match.git /var/folders/q2/88t_3skx1rn0gn9znm57tc3c0000gn/T/d20221223-12740-q7tb2h -c http.extraheader='Authorization: Basic ZmFrZS11c2VybmFtZTpmYWtlLWFjY2Vzcy10b2tlbg=='
+---------------+--------------+
|         Lane Context         |
+---------------+--------------+
| PLATFORM_NAME |              |
| LANE_NAME     | certificates |
+---------------+--------------+
[08:32:51]: Error cloning certificates git repo, please make sure you have access to the repository - see instructions above
+------+--------+-------------+
|      fastlane summary       |
+------+--------+-------------+
| Step | Action | Time (in s) |
+------+--------+-------------+
| 💥   | match  | 0           |
+------+--------+-------------+
[08:32:51]: fastlane finished with errors

[!] Error cloning certificates git repo, please make sure you have access to the repository - see instructions above

Environment

[08:41:00]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Stack

Key
Value

OS
13.1

Ruby
3.1.0

Bundler?
true

Git
git version 2.39.0

Installation Source
~/.rbenv/versions/3.1.0/bin/fastlane

Host
macOS 13.1 (22C65)

Ruby Lib Dir
~/.rbenv/versions/3.1.0/lib

OpenSSL Version
OpenSSL 3.0.5 5 Jul 2022

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
14.2

Swift Version
5.7.2

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
require 'base64'

lane :certificates do
  git_url = "https://github.com/lawrence-forooghian/macdown-match.git"
  git_basic_authorization = Base64.strict_encode64("fake-username:fake-access-token")

  match(app_identifier: "com.example.myAppName",
        git_url: git_url,
        git_basic_authorization: git_basic_authorization
       )
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.211.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

bundler
2.3.26

pathname
0.2.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

thread_safe
0.3.6

tzinfo
1.2.10

activesupport
5.2.8.1

public_suffix
4.0.7

addressable
2.8.1

httpclient
2.8.3

json
2.6.3

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.680.0

aws-sigv4
1.5.2

jmespath
1.6.2

aws-sdk-core
3.168.4

aws-sdk-kms
1.61.0

aws-sdk-s3
1.117.2

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.16.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

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.95.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.3.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.2

google-apis-androidpublisher_v3
0.32.0

google-apis-playcustomapp_v1
0.12.0

google-apis-iamcredentials_v1
0.16.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.44.0

mini_magick
4.12.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

generated on: 2022-12-23

[08:41:01]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
[08:41:01]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅

same problem

Matchfile
git_url(ENV["GIT_URL"])
storage_mode("git")
type("appstore")
git_basic_authorization(Base64.strict_encode64(ENV["GIT_TOKEN"]))
username(ENV["FASTLANE_APPLE_ID"])

GIT_URL=https://github.com/username/repo
GIT_TOKEN= ghp_Ox9PbIsxxxxxxxxxxxxx
FASTLANE_APPLE_ID=xxxx@xxx.com/email address
my working

@productdevbook What email for the FASTLANE_APPLE_ID you used? Is your GitHub email or a different email?

@productdevbook What email for the FASTLANE_APPLE_ID you used? Is your GitHub email or a different email?

apple developer email adress

you can use match repo with ssh, check it out how to setup here https://medium.com/@muhammedqazi/mastering-fastlane-the-ultimate-guide-to-effortless-android-and-ios-deployments-with-github-e0878c3f9529

source: gharchive/issue

authors: Doetheman lawrence-forooghian muhammadqazi productdevbook

repo: fastlane/fastlane

license: MIT

license_type: permissive

license_source: github-api


text:
Show the default value when running fastlane action [tool_name]

New Issue Checklist

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

Issue Description
Some actions have required parameters marked with the * but they also have the default value.
Would be nice to know the default value of the parameters when executing  fastlane action [tool_name].
i.e.
Match has the force_for_new_devices parameter that is required and by default is false as we can see here but fastlane action match doesn't say it.
fastlane action match

| * force_for_new_devices | Renew the provisioning profiles if the device count on the developer portal has changed | MATCH_FORCE_FOR_NEW_DEVICES |

Environment
fastlane version:  1.81.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? no

Hi @serluca Great to hear from you. We are going to evaluate this as a feature request and will follow up on this thread as relevant. Thanks for working with us! 👍

Hi @TKBurner thanks to get back to me, I know that when the command runs I can see the parameters but doesn't help when writing the fastfile.

Accepted in #4331 🚀

authors: TKBurner mfurtak serluca


text:
Proposal to remove and/or from conditionals with Mr. Rubocop 🚨

Why
Ruby style guide explains how &&, ||, and, and or should be used - https://github.com/bbatsov/ruby-style-guide#no-and-or-or

The and and or keywords are banned. The minimal added readability is just not worth the high probability of introducing subtle bugs. For boolean expressions, always use && and || instead. For flow control, use if and unless; && and || are also acceptable but less clear.

What
rubocop changed about 160ish instances of and and or used for boolean expressions. This change does touch many places of the codebase but shouldn't have any side effects (unless there were side effects from and and or that we were somehow depending on)

@KrauseFx Rubocop did all the work. I just enjoyed its success 😊

source: gharchive/pull-request


text:
Support .gradle.kts project

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Currently, we can write Gradle file with Kotlin that file name with .gradle.kts.
But the current version of Fastlane does not support this file type.
To detect the project platform, require the setup.rb should know .gradle.kts is also an Android project.
https://github.com/gradle/kotlin-dsl
Description
I add the line that .kts is also an Android project.
And I test with my .gradle.kts project.

CLA signed!

@janpio
It  write with Kotlin.
The normal gradle file write with groovy.

Thanks @wakwak3125! Sorry it took so long to merge.


text:
Version bump

Changes since release 0.43.2:

Improve ToolCollector to differentiate crashes and user_errors
[fastlane_core] Updated changelog loader to follow redirects (#4582)

👍  💎

authors: asfalcone mfurtak


text:
Disable output buffering for sh

Disable output buffering for Actions.sh

Looks great :+1:

authors: KrauseFx xfreebird


text:
Add "--new-comment" / "--base" / "--head" support to Danger action

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Description

I added Danger parameters that are not  supported yet.
Motivation and Context

I want to use --new-comment option on fastlane Danger action :D

I signed it!

Oh! @duck8823 Im so sorry! I think I missed the point of why you had the head and base variables, and you were right the first time! 😳. Would you mind reverting that last commit? Sorry for the back and forth!! 🐙

@ohayon It's Okay. I reset last commit.
Thank you for your review :D

Thanks @duck8823 this is great! 🚀


text:
Set info plist output

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
From the same plist file as template, I want to generate different plist files with different configurations without doing any change at all in the template.
Description
Add a new output parameter to set_info_plist to allow setting a different output for the resultant plist file.
The changes are backward compatible. The new parameter is optional and the current behaviour is kept in case of not providing it.

I signed it!

Documentation added to fastlane/docs in this pull request:
https://github.com/fastlane/docs/pull/371

@KrauseFx Thanks a lot for your feedback and your time reviewing this PR. The requested changes were applied to the code.


text:
将pytorch模型转换为fastNLP可用的模型

你好，我在尝试使用fastNLP构建自己的模型的时候遇到了问题。
pytorch教程[https://pytorch.apachecn.org/]中有一个字符级的文本生成模型
class RNN(nn.Module):
    def __init__(self,input_size,hidden_size,output_size):
        super().__init__()
        self.input_size=input_size
        self.hidden_size=hidden_size
        self.output_size=output_size

        self.i2h=nn.Linear(input_size+hidden_size,hidden_size)
        self.i2o=nn.Linear(input_size+hidden_size,output_size)
        self.softmax=nn.LogSoftmax()

    def forward(self,input ,hidden):
        combined=torch.cat((input,hidden),1)
        hidden=self.i2h(combined)
        output=self.i2o(combined)
        output=self.softmax(output)
        return output,hidden
    def init_hidden(self):
        return V(torch.zeros(1,self.hidden_size))

我想用fastNLP重写一次，但是在写的时候遇到一个问题，fastNLP要求返回数据为一个字典类型{'pred':outputs}，那对于这个模型应该如何改写呢？
谢谢~

就把forward中的返回值改成字典

repo: fastnlp/fastNLP


text:
move nb testing module to withins source tree

Making a fastplotlib.testing module would allow the test utilities to be used by dependent packages, ex. whatever algorithm package I end up with by the end of my phd.
For example in the example nbs they could just:
from fastplotlib.testing import test_plot, notebook_finished
...

I think this is a good idea!

repo: fastplotlib/fastplotlib


text:
Subtitle Under A Button

It would be useful if we could add a subtitle under each button (optional).
Thanks

Hi, thanks for the suggestion! I'm not planning on adding this feature to AHKActionSheet, though, as it's quite complicated as it is.
Since this project is open source, I encourage you to fork it and make your own version of it :smiley:!

repo: fastred/AHKActionSheet


text:
remove_column triggers check even when wrapped in safety_assured

Hello,
First of all, thank you very much for the excellent library.
Gem version: 0.19.1
Rails version: 7.0.4
class User < ApplicationRecord
  self.ignored_columns += ['name', 'email_address']
end

class RemoveOldColumns < ActiveRecord::Migration[7.0]
  def change
    safety_assured { remove_columns :users, :name, :email_address }
  end
end

Triggers:
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

=== Dangerous operation detected #strong_migrations ===

Active Record caches database columns at runtime, so if you drop a column, it can cause exceptions until your app reboots.
A safer approach is to:

1. Ignore the column:

  class User < ApplicationRecord
     self.ignored_columns += ["name", "email_address"]
  end

2. Deploy
3. Wrap column removing in a safety_assured { ... } block

  class RemoveUnusedColumns < ActiveRecord::Migration[7.0]
    def change
      safety_assured { remove_columns :users, :name, :email_address }
    end
  end

4. Remove column ignoring from step 1
5. Deploy

For more details, see https://github.com/fatkodima/online_migrations#removing-a-column

I have already completed steps (1-3), but when I try to run the migration, this errors keeps stopping me.

Dangerous operation detected #strong_migrations

Not the right gem I think 😅

Do you use both gems?

@fatkodima oh my, you're quite right. Somehow they both got added to the Gemfile! Sorry for the trouble, and thanks again for the excellent work 👍

Thank you for kind words and using it! ❤

authors: brevio-nicolay fatkodima


text:
accept TOS ?

seems like new account need to accept tos to make request ? get thsi error with new account (mail validated)
2016-08-09 03:02:22,125 [     pgoapi] [   INFO] Status code 3 returned. Performing get_player request.
2016-08-09 03:02:22,126 [       scan] [  ERROR] 'map_cells'
2016-08-09 03:02:22,126 [       scan] [  ERROR] Unexpected error while parsing response.
2016-08-09 03:02:22,127 [       scan] [  ERROR] Response dict: {'responses': {'GET_MAP_OBJECTS': {}}, 'status_code': 3, 'auth_ticket': {'expire_timestamp_ms': 1470706331672L, 'start': 'SOMEVALUE=', 'end': 'SOMEVALUE'}, 'request_id': SOMEVALUE}

seems like its the issue, solved by using this tool :
https://github.com/TachyonRSA/PoGoTos

Please close, it's not related to this project

Technically, I would say it is an issue considering the one of the devs has stated that the app should accept ToS if necessary
https://github.com/favll/pogom/issues/90#issuecomment-238339602

Yeah, there is a bug in one of our api request loops. I'm currently running a hotfix that should fix this.

fixed in 43f4da80cbf142a1953b8de3e76076c0d039cfdc

authors: Jordan-TE favll lax20attack nborrmann niayh

repo: favll/pogom

license: mit

license_source: bigquery


text:
Adding UTF8 encoding in the JVM parameter

Lines 62, 65 and 70, added JVM parameter -Dfile.encoding=UTF8 to make sure mock responses are encoded in UTF8 by default.

Thanks for the PR.

authors: fbascheper sooron


text:
Propagating batch shape from Embedding layer to stateful LSTM

Hello,
I'm having troubles using a stateful LSTM after an Embedding layer. If I use it directly or have a dense layer before (but no Embedding layer), it works fine. I wrote a simple demo to illustrate the problem:
vocab_size = 20
max_len = 10
n_labels = 5

n_samples = 500

embedding_size = 100
batch_size = 16

# generate fake data
X_train = np.random.randint(0, vocab_size, size=[n_samples, max_len])
y_train = np.random.randint(0, 2, size=[n_samples, n_labels]) #multiclass, multilabel

model = Sequential()

#have to give full batch size to first layer for using stateful LSTMs later on
model.add(Embedding(vocab_size, embedding_size, input_length=max_len, batch_input_shape=(batch_size, max_len)))
#stateful LSTM (everything works great with normal LSTM)
model.add(LSTM(output_dim=300, stateful=True))
model.add(Dropout(0.5))
model.add(Dense(n_labels))
model.add(Activation('sigmoid'))

model.compile(loss='binary_crossentropy', optimizer='adam', class_mode="binary")
model.fit(X_train, y_train, batch_size=batch_size, nb_epoch=10)

the model runs successfully until the end of the epoch, when it fails:
Epoch 1/10
496/500 [============================>.] - ETA: 0s - loss: 0.6959
Traceback (most recent call last):
  File "./stateful_lstm_embedding_test.py", line 34, in <module>
    model.fit(X_train, y_train, batch_size=batch_size, nb_epoch=10)
  File "build/bdist.macosx-10.10-x86_64/egg/keras/models.py", line 678, in fit
  File "build/bdist.macosx-10.10-x86_64/egg/keras/models.py", line 314, in _fit
ValueError: Shape mismatch: x has 16 rows but z has 4 rows
Apply node that caused the error: Gemm{no_inplace}(Subtensor{::, int64::}.0, TensorConstant{0.20000000298}, <TensorType(float32, matrix)>, lstm_U_o_copy0, TensorConstant{0.20000000298})

The same happens with both tensorflow and theano backends. Maybe I'm confused on how to give batch_input_shape to an Embedding layer, but I'm providing it batches of sizes batch_size x max_len so I cannot think of what else to provide.

As far as I'm concerned, all batches have to have the same size for stateful RNNs, for instance batch_size = 10 worked for me.

Indeed, the issue you have is that the last batch in your data does not have size 16, but instead has side 4. You should make sure that all your batches are the same size in order to use stateful networks (since e.g. the sample of index i in the batch n is the follow-up to the sample of index i in the batch n-1). This is explained in the documentation.

authors: fchollet santi-pdp v-v

repo: fchollet/keras


text:
Real time face recognition with keras

I'am doing project on real time face recognition, I found a code on github which uses Yale dataset and I got accuracy of 89%, I've changed the dataset and save the weight. Now I want to make it real time, So now I load an Image and convert it to numpy array then reshape it and pass it though classes = loaded_model.predict_classes(img)
Now here I am getting an error which says : Exception: Error when checking : expected dense_input_1 to have shape (None, 22500) but got array with shape (22500, 1)
I just want to know that in predict_classes function what type of data feed required a numpy array 1d or 2d ?

Hi,
I think the shape of the variable img is incorrect. You may check the expand_dims method and add an additional axis at the beginning.
By the way, do you plan to pass single image to the model at each time? This might be inefficient. You may try different batch size and verify the relationship between computational speed and batch size.
BR.

Hi, nixingyang,
Thank for you reply. I've tried to do, but facing the same problem...below I've written my last lines of codes. please help me out ...

img = cv2.imread('image.jpg',0)
img = cv2.resize(img,(150,150))
img = np.expand_dims(img, axis=0)
img = np.array(img).flatten()

classes = loaded_model.predict_classes(img)

@aquibjaved Could you please post the code which defines the structure of your model? If possible, the output of model.summary() would also be helpful.

@nixingyang  below is the code to load the model and an Image for test.
`import cv2
import numpy as np
import os
from skimage import io
from sklearn.cross_validation import train_test_split
#importing kers
from keras.utils import np_utils
from keras.models import *
from keras.layers import Dense, Dropout, Activation
load json and create model
json_file = open('model.json', 'r')
loaded_model_json = json_file.read()
json_file.close()
loaded_model = model_from_json(loaded_model_json)
load weights into new model
loaded_model.load_weights("yaleface.h5")
print("Loaded model from disk")
evaluate loaded model on test data
loaded_model.compile(loss='binary_crossentropy', optimizer='rmsprop', metrics=['accuracy'])
#score = loaded_model.evaluate(X_test,Y_test, verbose=0)
print loaded_model.summary()
img = cv2.imread('image.jpg',0)
img = cv2.resize(img,(150,150))
img = np.expand_dims(img, axis=0)
img = np.array(img).flatten()
#img = np.expand_dims(np.expand_dims(img, axis=0), axis=0)/255
print img
classes = loaded_model.predict_classes(img)
`

@aquibjaved The structure of your model was not revealed in your code as you initiated the model from a json file. Could you please try the code shown below?
img = cv2.imread('image.jpg', 0).astype(np.float32) / 255
img = cv2.resize(img, (150, 150))
img = img.flatten()
img = np.expand_dims(img, axis=0)

The shape of the input would be (1, 22500) which should work in your case. The weird thing is that, you intended to apply flatten operation on your input. It smashed the spatial dimensions of the image.

@nixingyang
Thank you so much, It works but for every different image it says
classes predict is [4].
it's weird, How can I overcome this problem

@aquibjaved This depends on how good is your model. I noticed a bug in your code. You should call compile before load_weights. The pre-trained weights were lost when you called compile.

@nixingyang I did, I keep the compile  before ** load_weights**, same issue
`import cv2
import numpy as np
import os
from skimage import io
from sklearn.cross_validation import train_test_split
#importing kers
from keras.utils import np_utils
from keras.models import *
from keras.layers import Dense, Dropout, Activation
load json and create model
json_file = open('model.json', 'r')
loaded_model_json = json_file.read()
json_file.close()
loaded_model = model_from_json(loaded_model_json)
loaded_model.compile(loss='binary_crossentropy', optimizer='rmsprop', metrics=['accuracy'])
load weights into new model
loaded_model.load_weights("yaleface.h5")
print("Loaded model from disk")
#print loaded_model.summary()
img = cv2.imread('test2.jpg', 0).astype(np.float32) / 255
img = cv2.resize(img, (150, 150))
img = img.flatten()
img = np.expand_dims(img, axis=0)
classes = loaded_model.predict_classes(img)
print classes`

@aquibjaved Comment the load_weights line and try again. The predictions should be random for each input image. Then, the issue is related to the pre-trained weights.

@nixingyang  I did comment the load_weight and the predictions are random, on a same image every time the prediction is different. So now there's an issue related to the pre-trained weights.

@nixingyang
My accuracy on test data is 98.4% then why it is not working ?

@aquibjaved Make sure that you are using the same version packages as the pre-trained model. Check how the weights are saved/loaded to/from disk. It should be a bug in your code.

@aquibjaved have you tried exporting your whole model with weights?
I am using save_model and load_model for me and it is working correctly - i.e. the loaded model has expected metric value.
2nd question: am I right that you are flattening your image before passing it to the net? If so - is it flattening it the same way it was when training. And why not to keep it a 2D network input? Are the values during training somehow preprocessed - do you do the same when calling predict ?

@kretes   I'll try this surely... load_model

@kretes  can show you'r code how you've loaded the model and made the predictions.

authors: aquibjaved kretes nixingyang


text:
Fix shapes should be tuples.

It seems that refactoring for multiple backends introduced some typos and some input or output shapes (especially one-dimensional) were not tuples anymore. In some circumstances, like using a LSTM layer with forget_bias_init='he_normal', Keras crashed:
    model.add_node(LSTM(embedding_dim, return_sequences=True, forget_bias_init='he_normal'), name='lstm', input='shared_1')
  File "/home/xxx/venv/src/keras/keras/layers/containers.py", line 262, in add_node
    layer.set_previous(self.nodes[input])
  File "/home/xxx/venv/src/keras/keras/layers/core.py", line 53, in set_previous
    self.build()
  File "/home/xxx/venv/src/keras/keras/layers/recurrent.py", line 328, in build
    self.b_f = self.forget_bias_init((self.output_dim))
  File "/home/xxx/venv/src/keras/keras/initializations.py", line 46, in he_normal
    fan_in, fan_out = get_fans(shape)
  File "/home/xxx/venv/src/keras/keras/initializations.py", line 7, in get_fans
    fan_in = shape[0] if len(shape) == 2 else np.prod(shape[1:])
TypeError: object of type 'int' has no len()

Right, thanks!


text:
Added helper class to use data in HDF5 datasets

This class enables one to use slices of datasets in an HDF5 file as matrices for training/testing algorithms in keras.
Usage example:
X_train = HDF5Matrix(datapath, 'features', train_start, train_start+n_training_examples, normalizer=normalize_data)
y_train = HDF5Matrix(datapath, 'targets', train_start, train_start+n_training_examples)

The arguments are:
datapath: path to HDF5 file
dataset: name of the dataset in the HDF5 from which to take the data
start and end: indices to slice the given dataset
normalizer: function to be applied to the data coming from the dataset on-the-fly. Can be used for centering/standardizing/scaling data, but cannot change the dimensions of the data in any way.

Looks good. I'll move some other utils to io_utils.

authors: fchollet jfsantos


text:
training.py _standardize_input_data() cleanup input tensor corner cases

This cleans up some corner cases where crashes would previously occur for certain input data values. In particular, when unexpected data types are passed in, the error is much clearer than the current behavior (crash) if an unsupported type is passed in. This PR also permits input tensors to be specified, and they are ignored here because they are to be processed separately from numpy arrays when they are provided. If they are provided in a manner that is incorrect, a reasonable error should be produced.
See https://github.com/fchollet/keras/pull/7072#issuecomment-311174255 for other related PRs.
This is merged in #6928.
note that the tensors parameter appears unused elsewhere, but PRs #7072 and #6928 depend on this. It is useful for edge case checks.

You say this PR covers some corner cases but you add an extra parameter (and every change is related to it).

Which are the corner cases that are covered?
If this is connected to another PR, you should mention here how they are connected.
What is the point of the new parameter? I'm not sure how it should work, could you be more specific when you describe the parameter (in the docstring)? Why would you pass None values in skip_standardizing?

I understand you want to mention three cases:

if skip_standardizing is None then standardize everything
list has None values => remove them from the list (they won't be skipped)
otherwise standardize len(skip_standardizing) items.

Is this correct?
Also it doesn't seem to matter which items are in skip_standardizing, you only take into account
the length of skip_standardizing anyway. No?

Everything you said sounds correct, I updated the top post with a more detailed description of the changes which (1) provides a clearer error when users provide incorrect input and (2) does it in a way that is forwards compatible with input tensors.
I think I had also mentioned at the top that this is part of https://github.com/fchollet/keras/pull/7072#issuecomment-311174255 and the merged version is #6928.

Unless I'm missing something, providing the function with the length of the list, instead of the actual list, produces the same result. In that case, the function skips an unnecessary step, so you might want to change the skip_standardizing parameter into num_skip_standardizing or something like that and just specify the length of the list (like len([p]) ).
However, that seems counter-intuitive. I don't get why the number of elements is more important than the actual elements. If this change is dependent on another PR, then in my opinion it isn't atomic enough and constitutes bad design. Am I wrong? Please elaborate.

Oh, is this used to cover the case of fit(None, None,...) that is discussed in other PRs?

Yes, this PR is necessary to account for fit(None,None,...) and fit(None,Tensor,...).
I could switch it to a simple length or the skip list could be renamed input_tensors, which could then be updated with additional tensor specific checks in the future. Either is ok with me.

@ahundt If it is certain that there will be checks specifically on parts of the input, then out of those two I'm in favor of the second solution.
Otherwise, it seems like _standardize_input_data should be able to automatically infer if the input is correct and print the relevant message.
Is there a use case that should allow the user to specify the wrong amount of inputs to skip and crash the program? If not, then the user should not be a part of the decision process, otherwise please elaborate (the why definitely needs to be specified).

Okay I did the rename. Am I missing an obvious way to write this without the parameter entirely?
If not, I think the length calculations are appropriate considering the function title is to standardize the input data which is done according to the type of those inputs. These are all internal APIs anyway, so no keas users should be calling this function.

I still don't get it, sorry. The actual tensors are never used and len(input_tensors) should always be equal to len(names) - len(data), so instead of introducing an external source of error (the developer that defines input_tensors), why not just set expected_names to len(names) - len(data)? That is, replace line 63 with expected_names = len(data), remove the input_tensors parameter and the code will work every time. Why should it fail? Why should the developer be allowed the mistake of passing the wrong number of input_tensors?
Can you provide an example use case that is not supported by keras master, along with the reason it should work that illustrates the importance of the extra parameter here? The unit test shows that keras/master won't work (because it doesn't have the extra parameter) but it doesn't explain why the parameter makes sense. There is no code that takes advantage of the extra parameter in this PR and _standardize_input_data is used four times in the keras codebase. This PR doesn't seem related to any of them, therefore it doesn't seem to be atomic enough like I said.
If it's meant to be added later, I believe you should provide a placeholder example because I honestly don't understand the PR...
Also: sanity checks and programming flaws that should not reach runtime should be dealt with with assertions, whereas exceptions should be used to handle runtime faults.
Is the use case for this PR something that could happen during runtime or should it be solved immediately by the developer? If it's the latter, consider having an assert len(names) - len(input_tensors) == len(data) somewhere in there.

Oh sorry! This is required to support input tensors as described in #6928, split into atomic PRs as François requested.
Each item in the PR chain at https://github.com/fchollet/keras/pull/7072#issuecomment-311174255 is a prerequisite of a later one in that list, which merged together form #6928 . Here is what happens:

is_placeholder checks to differentiate numpy data inputs from input tensors
If a model input is an input tensor it is added to Model._input_yield_op_tensors
At the point where _standardize_input_data() is called anything convertible to a numpy array would work, but a crash will occur if you call a numpy function on an input tensor such as a TFRecord. This PR lets those items be skipped without error.

Here is exactly where it is required:
https://github.com/fchollet/keras/pull/6928/files#diff-299cfd5886683a4b012f286403769fc1R1273
Is that more clear?

At the point where _standardize_input_data() is called anything convertible to a numpy array would work, but a crash will occur if you call a numpy function on an input tensor such as a TFRecord. This PR lets those items be skipped without error.

Ok then, in the case, instead of introducing a new parameter, every input should be checked with is_placeholder.
Keep those that return true in a list, e.g. input_tensors and check that len(names) - len(input_tensors) == len(data). However this would probably mean that the names parameter would have to change into a list of tensors (self._feed_input_names -> self._feed_inputs and self._feed_output_names -> self._feed_outputs).
I really don't like that instead of actual input_tensors you could have an arbitrary list and it would still work. It's not intuitive and I really believe it's not the best design.
What do you think?

@PavlosMelissinos

Ok then, in that case, instead of introducing a new parameter, every input should be checked with is_placeholder.

I tried to implement this and I realized why a new parameter of some sort is necessary. This is checking actual input data, such as when model.fit(x,...) is called. The input data is the contents of x and only contains inputs convertible to numpy arrays, input tensor data, or None. There needs to be another parameter to count the number of actual input placeholders expected to ensure the actual provided data matches up.
In other words:

checking if the input is a numpy array is not good enough because it might be converted to a numpy array later
checking if data is a placeholder will always return False because it is the actual input data, not the layer representing such data.

Considering that #7066 is no longer necessary and has been merged here, I now added the parameter feed_data which includes the list of data that should be fed to the backend, each of which should be a placeholder. This hopefully makes the overall change here in #7067 completely atomic and much more sensible.
What do you think?

I was mistaken, the way I previously implemented it is the most feasible way that functions correctly. The count of expected inputs can only be modified based on the number of input tensors, not the number of feed dict entries or numpy arrays. This is because of the external loss case, where you don't know how many input numpy arrays you're going to need.
Here is the unit test of 29efd9f that demonstrates exactly why this is the case:
https://gist.github.com/ahundt/ba00b4f2a185ddce6f122b2ec592c3d9
I'm working on a fix...

I was mistaken, the way I previously implemented it is the most feasible way that functions correctly. The count of expected inputs can only be modified based on the number of input tensors, not the number of feed dict entries or numpy arrays. This is because of the external loss case, where you don't know how many input numpy arrays you're going to need.
Here is the unit test of 65a5bce that demonstrates exactly why this is the case:
https://gist.github.com/ahundt/ba00b4f2a185ddce6f122b2ec592c3d9
I'm working on a fix...

Assuming this latest merge passes the unit tests, this PR should now actually be an atomic commit where the parameters for _standardize_input_data() make sense.

@souptc I'm trying to add an is_placeholder attribute to the output of K.is_placeholder() in CNTK, however it does not appear to support runtime attributes (or perhaps just public ones?). Could you please advise?

Consider using the property decorator for is_placeholder. If the class inherits from object, which it does, then the decorator forces the class instance to treat the exposed attribute as read-only, so you can make sure it's not modified after the creation of the object (it throws an AttributeError). In other words it emulates the final keyword found in other languages.
At the same time, you keep _is_placeholder as a private attribute (by convention but still better than nothing imho).
It's a few extra lines but they make the code a little bit more robust.

@PavlosMelissinos I also switched to a public is_placeholder member based on my meeting with François today.

Yeah, I noticed your post on the other thread, that's why I mentioned the property decorator, as a workaround, but simple is better than complex, so my suggestion is probably unnecessary for this use case.
After your explanation, the PR overall seems ok to me, maybe you should add parts of it as comments/docstring.

That does sound like it would be nicer, but as you mentioned it probably can't be done with existing objects, and this behavior should remain backwards compatible.

@ahundt , the reason is it is conflict with the "is_placeholder" attribute defined in cntk variable:
https://github.com/Microsoft/CNTK/blob/master/bindings/python/cntk/variables.py
`@property
def is_placeholder(self):

    '''

    Whether this variable is a placeholder.

    '''

    return super(VariableMixin, self).is_placeholder()`

The "placeholder" in cntk is another concept, maybe we can use another name, like _is_keras_placeholder?

@souptc thanks for the heads up, that's unfortunate! I see that's why _is_placeholder had been working but is_placeholder does not.
@fchollet should we:

switch back to an is_placeholder() backend function
rename is_placeholder to _is_placeholder
rename is_placeholder to is_keras_placeholder
some combination of (1+2) or (1+3)
something else

I've gone with option 3 for now, replacing is_placeholder with is_keras_placeholder.

I no longer have time to maintain this. If someone is interested, feel free to take it over.

authors: PavlosMelissinos ahundt souptc


text:
WIP: Update modeshape authentication code for Shiro compatibility

https://jira.duraspace.org/browse/FCREPO-2783
What does this Pull Request do?
Changes to allow recording the logged in user as the createdBy and lastModifiedBy user. It works, but many tests are failing. (Marked them as Ignored)
How should this be tested?
Build and manually test the fcrepo-webapp to ensure that Modeshape is recording the logged in user in the Fedora resources' createdBy and lastModifiedBy.
Interested parties
@fcrepo4/committers, @peichman-umd

This PR has been superseded by https://github.com/fcrepo4/fcrepo4/pull/1352 if I am not mistaken.  Closing this PR for now.  @mohideen, @peichman-umd  :  If  I am mistaken, please let me know and I'll reopen.

authors: dbernstein mohideen


text:
[AppMan] Added support for AIR and FP 22...

@Meychi, please update zip for:

http://www.flashdevelop.org/appman/frameworks_flexsdk_9-22.zip

playerglobal.swc download page

Done, thanks.

authors: Meychi SlavaRa

repo: fdorg/flashdevelop


text:
How can I verify a user by local strategy on client without real authentication?

How can I verify a user by username/password(like local strategy) on client without call authenticate() to really login?

@daffl I'm using vuex on client and I can't get service('authentication') directly, I tried this:
...mapActions('authentication', {  createAuthentication: 'create'}),

but failed with error: [vuex] module namespace not found in mapActions(): authentication/

I found in feathers-vuex a class which can help me get service:
import feathersClient from '@/api/feathers-client'

const authService = feathersClient.service('/authentication')
  let res = await authService.create({
    strategy: 'local',
    email,
    password
  })

@daffl But then another question is even if I pass in a wrong email or password, the create() will always return an accessToken, that can't help me verify an invalid user.

I have to logout first, then use authentication.create() or auth/authenticate() to verify a user

Yes. This is a known issue and tracked in https://github.com/feathersjs/feathers/issues/1017. Closing this one since this repository will be moved.

repo: feathersjs/authentication


text:
Cannot read property 'service' of undefined

There is my code:
https://github.com/kozzztya/share-debt/tree/36cf4897219d4ac218a9a6210ab279de53269445
After test running ./node_modules/.bin/ava test/debt-add.test.js I have an error on login:
Cannot read property \'service\' of undefined

Can you look what's wrong?

Usually this happens when app.setup isn't called. This normally happens when the server is started through something other then app.listen.

I called it without any success https://github.com/kozzztya/share-debt/blob/36cf4897219d4ac218a9a6210ab279de53269445/src/index.js#L6
Also I didn't use sub app like in previous issues with the same error.

And I didn't see in examples of feathers-auth using app.configure(services()). Am I calling all stuff in the right order?

It looks like you are configuring authentication twice, once in https://github.com/kozzztya/share-debt/blob/36cf4897219d4ac218a9a6210ab279de53269445/src/app.js#L19 and another time in https://github.com/kozzztya/share-debt/blob/36cf4897219d4ac218a9a6210ab279de53269445/src/services/auth/index.js. If you remove https://github.com/kozzztya/share-debt/blob/36cf4897219d4ac218a9a6210ab279de53269445/src/app.js#L19 everything will probably work.

I tried to configure auth in different places. That what I forget to delete.
Still have the same issue with app.configure(authentication()) only in app.js.

app.setup wasn't called in test env. thanks for help.

authors: daffl kozzztya

repo: feathersjs/feathers-authentication


text:
Removed overly complex promisify function wrappers

Function signatures were parsed to get the #params in a function
and to see if the func was likely a callback func. There were
some manageable issues with signatures whose params had default
values. However the parser used does not work for params using
deconstruction, and those are common. We would have to switch to
a parser that parses signatures into an Abstract SyntaxTree to
solve this problem. That is really going too far for the small
benefits any parsing provides.

Removed all the promisify func except fnPromisfyCallback
Renamed fnPromisifyCall to the more descriptive callbackToPromise
Removed tests related to promisfy funcs
Updated test for callbackToPromise
Updated README.
Closed issue reminding us to remove hacks to get around Node 4.

Looks good @eddyystop! I think this is a good call. Simpler = better.
Likely will need to be a major release I guess.
:shipit:

authors: eddyystop ekryski

repo: feathersjs/feathers-hooks-common


text:
docs are out of date

Could this get updated docs?
Or is primus deprecated?
The docs here also are not consistent: https://docs.feathersjs.com/clients/primus.html

We haven't updated Primus to 6.0 yet (see #25). What exactly is outdated?

I just got it working lol.
The docs are not clear on how to use it on the front-end.
There are 2 different ways listed on the link I posted above, but one doesn't even work.
I got it working like this:
import feathers from 'feathers/client';
import hooks from 'feathers-hooks';
import authentication from 'feathers-authentication/client';

import feathersPrimus from 'feathers-primus/client';
const primus = new Primus('/')

const app = feathers()
    .configure(hooks())
    .configure(feathersPrimus(primus))
    .configure(rx(RxJS))
    // Use localStorage to store our login token
    .configure(authentication({
        storage: window.localStorage
    }))

It's as simple as this but the docs aren't that clear lol

This is what is documented in the browser usage section at https://docs.feathersjs.com/clients/primus.html#browser-usage right?
That section should probably also include how to use it with a module loader.

It says: .configure(feathers.primus(primus));
feathers.primus doesn't even exist lol
I took this const primus = require('feathers-primus/client'); from the server side usage on the same page and used that on client side lol, but I don't think that server side would need this client

It does exist and work if you are using the feathers-client as it is documented in the browser usage section (meaning including the script tags like <script type="text/javascript" src="//unpkg.com/feathers-client@^1.0.0/dist/feathers.js"></script>).
It does not if you are using it with a module loader like Webpack, Steal or Browserify. Then you have to do what you pointed out. What I was saying is to include that example for using a module loader in the browser usage section.
The server usage should still be correct. There is no reason why another Node server couldn't talk to an existing Feathers server but it requires more Primus setup work because the global Primus isn't available like it is in the browser.

So what's the deal here? Are we going to add a module loader bit to the docs? Or are we all good and can now close this?

I was confused too, but for another reason.
What threw me off is actually that primus/primus.js is automatically enabled as a route on the server when configuring feathers-primus, and that file needs to be included through a regular <script> tag before new Primus() is available on the client.
I had assumed feathers-primus/client would be all the client instantiation needed, and I could forego external <script> tags. Like @ryuken, I'm also using Webpack (in multiple places; via a webpack-dev-server and a production build served from a live web server, which changes how I'm able to pull in external scripts).
In my setup, the API server and the front-end are two distinct endpoints, so calling primus/primus.js actually needs to be done against my other endpoint.
It might be useful to make it clear in the docs that primus/primus.js is automatically generated on the server, and it needs including outside of webpack at the HTML level to instantiate properly.

This has been updated in the latest Primus documentation. We can open new issues if some of the usage is still unclear.

authors: daffl ekryski leebenson ryuken

repo: feathersjs/feathers-primus


text:
Boolean values

Hey,
I was trying to filter TODO list by proving a boolean value (/serviceEndPoint?completed=true), but that didn't work because the value was actually 'true', which results with zero records.
This worked for me:
      if (hook.params.query.completed === 'true') {
        hook.params.query.completed = true;
      } else if (hook.params.query.completed === 'false') {
        hook.params.query.completed = false;
      }

Am I doing something wrong?

Have you tried using completed=1 or completed=0?  I'm just curious if it works.  I think it really depends on how the query parser handles the query.  Since it appears to be leaving it as a string,  your solution is probably the way to go.
if (typeof hook.params.query.completed === 'string') {
  hook.params.query.completed = (hook.params.query.completed === 'true');
}

That's the way to do it. It also might be possible to use different query parsers that try to convert this automatically but hooks are still the most straightforward way. We can't do this automatically since we have no information about the data format that we might want to convert to.

authors: daffl evgenyboxer marshallswain

repo: feathersjs/feathers-rethinkdb


text:
Non-ascii characters corrupt the range data

(Originally reported at solidity-coverage 418)
("corrupt" might be overdramatizing this a little.)
It looks like ranges are calculated by character count rather than string length, and non-ascii characters are 'wider' than length 1. This can introduce unexpected drift if you're using the parser to identify string injection points when modifying source files.
Ascii: length 36
contract A {
    /// S
    uint x;
}

Non Ascii: length 37
contract A {
    /// 𝕊
    uint x;
}

These two contracts produce the same range data.  Not sure this can (or should?) be fixed here. A simple work-around for my case is to sanitize files before parsing.
The issue raising this at SC involved scientific notation in a natspec comment.

What you are saying is that I am giving out a unicode character range instead of a byte range? Or vice-versa?

@federicobond

giving out a unicode character range
Yes,  I think that's right. You're counting unicode while JS string methods count bytes.

In the examples above, the range for uint  is:
"range": [
  27,
  30
]

And running...

ascii.slice(0,31) ends on t;
nonAscii.slice(0,31) ends on n;

Interesting catch. I am only copying the character ranges returned by the ANTLR parser. I just found out that there was a deprecation due to the treatment of UTF-8 in the ANTLR JS target. Can you try making this same change in src/index.js and see if it fixes it?

@federicobond Yes! That looks good.
This is the diff from test asserting the ascii/non-ascii ASTs are deep equal.
"typeName": {
  "name": "uint"
  "range": [
-    27
-    30
+    28
+    31
  ]
``

authors: cgewecke federicobond

repo: federicobond/solidity-parser-antlr


text:
Websocket subscriptions

All federation APIs use websockets, but we don't support websocket subscriptions (the whole reason we chose to use websockets for our APIs!)

I don't think this is useful for one subscription-one response type of notification. Because that looks same on the network level.
It is useful for one subscription-multiple responses type of notification. I can't think of instances of this.
If you know of any examples where this will be useful, please tell.

Because that looks same on the network level.

It might look the same on the wire, but is it handled the same by jsonrpsee? One problem we had was running into timeouts for RPC requests. Another was having a client side limit on parallel requests. I wonder if subscriptions would be the better fit just because their anticipated usage pattern matches more closely to how we'd use them.

The decrypted preimage status call is one example prone to subscriptions:
https://github.com/fedimint/fedimint/pull/3939/files
We have Pending -> Some | Invalid (plus a potential Timeout status).

authors: Maan2003 douglaz elsirion justinmoon

repo: fedimint/fedimint


text:
Vm crashes on the CI

This issue will keep track of VM crashes on the CI. This is for the VM that we compile ourselves loading GT on Pharo 9.

Crash on MacOS M1 in #fullGC
Segmentation fault Fri Jul 23 16:59:57 2021

./workspace/feenkcom_gtoolkit9_main/glamoroustoolkit/GlamorousToolkit.app/Contents/MacOS/GlamorousToolkit-cli
PharoVM version:5.0-Pharo 9.0.0 built on Jul 23 2021 04:17:58 Compiler: Apple LLVM 12.0.5 (clang-1205.0.22.11) Apple LLVM 12.0.5 (clang-1205.0.22.11) [Production Spur 64-bit VM]
Built from: CoInterpreter * VMMaker-tonel.1 uuid: cece64c1-2784-0d00-8ce0-9d41031e5830 Jul 23 2021
 With:StackToRegisterMappingCogit * VMMaker-tonel.1 uuid: cece64c1-2784-0d00-8ce0-9d41031e5830 Jul 23 2021
 Revision: v8.1.0-alpha-1748-g36efc12bb - Commit: 36efc12bb - Date: 2021-07-23 10:14:18 +0200

C stack backtrace & registers:
	 x00 0x00000001796087f0 x01 0x0000000142b860f0 x02 0x0000000142b85f90 x03 0x0000000120077fc0
	 x04 0x0000000120060080 x05 0x0000000000000000 x06 0x0000000000001000 x07 0x0000000000000000
	 x08 0x0000000142b860e8 x09 0xffffffffffefa5ac x10 0x0000000000041695 x11 0x0000000000000034
	 x12 0x000000000000005c x13 0x0000000003000024 x14 0x000000016d201668 x15 0x000000016d201668
	 x16 0x000000019db49cc4 x17 0x0000000203518150 x18 0x0000000000000000 x19 0x0000000142b85f90
	 x20 0x00000001796087f0 x21 0x0000000142b860f0 x22 0x0000000103098040 x23 0x0000000103098100
	 x24 0x0000000102ffd000 x25 0x0000000000000007 x26 0x0000000102ffd000 x27 0x0000000102ffd000
	 x28 0x0000000142b86117  FP 0x000000016d1c1480  LR 0x0000000102f379bc  SP 0x000000016d1c1460
	  PC 0x0000000102f379f0  STATE 0x0000000000000000
*0   libPharoVMCore.dylib                0x0000000102f379f0 markLiteralspcmethod + 140
1   libPharoVMCore.dylib                0x0000000102fe1710 reportStackState + 308
2   libPharoVMCore.dylib                0x0000000102fe1a78 sigsegv + 232
3   libsystem_platform.dylib            0x000000019db90c44 _sigtramp + 56
4   libPharoVMCore.dylib                0x0000000102f379bc markLiteralspcmethod + 88
5   libPharoVMCore.dylib                0x0000000102f37414 markAndTraceMachineCodeOfMarkedMethods + 632
6   libPharoVMCore.dylib                0x0000000102fa1fd4 markObjects + 2016
7   libPharoVMCore.dylib                0x0000000102fa12a4 fullGC + 264
8   libPharoVMCore.dylib                0x0000000102fc1368 primitiveFullGC + 44
9   libPharoVMCore.dylib                0x0000000102f78af8 interpret + 22644
10  libPharoVMCore.dylib                0x0000000102f8085c enterSmalltalkExecutiveImplementation + 184
11  libPharoVMCore.dylib                0x0000000102f73850 interpret + 1484
12  libPharoVMCore.dylib                0x0000000102f2297c vm_main_with_parameters + 648
13  GlamorousToolkit-cli                0x0000000102c435b8 _ZN11vm_bindings2vm2VM5start17h09af580d215e1613E + 16
14  ???                                 0x0000000000000000 0x0 + 0

Can't dump Smalltalk stack(s). Not in VM thread

Most recent primitives
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
setPosition:to:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
asFloat
-
exponent
timesTwoPower:
truncated
exponent
exponent
truncated
<=
*
**PrimitiveFailure**
digitMultiply:neg:
nextPutAll:
findFirstInString:inSet:startingAt:
**StackOverflow**
write:from:startingAt:count:
**StackOverflow**
write:from:startingAt:count:
**StackOverflow**
write:from:startingAt:count:
//
\\
write:from:startingAt:count:
*
**PrimitiveFailure**
digitMultiply:neg:
//
\\
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
sizeOrNil:
close:
wait
**StackOverflow**
basicIdentityHash
signal
class
species
basicNew
basicNew
indexOfAscii:inString:startingAt:
basicNew
initialize
class
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
nextPutAll:
findFirstInString:inSet:startingAt:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
write:from:startingAt:count:
sizeOrNil:
close:
wait
**StackOverflow**
close
signal
class
value:
at:
at:
at:
at:
at:
primitiveGarbageCollect
**FullGC**

stack page bytes 8192 available headroom 5576 minimum unused headroom 5808

	(Segmentation fault)

Is this still an issue?

I will close this as we do not seem to see this problem anymore.

authors: chisandrei girba

repo: feenkcom/gtoolkit


text:
🛑 PasImpCh is down

In c15fa49, PasImpCh ($SITE_PASIMPCH) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PasImpCh is back up in eae51d8 after 13 minutes.

repo: felipesbs/bitrate-uptime


text:
🛑 PasImpCh is down

In 0e7bef0, PasImpCh ($SITE_PASIMPCH) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PasImpCh is back up in 7af586f after 17 minutes.


text:
Extension issue

Issue Type: Bug
Extension Name: php-intellisense
Extension Version: 2.3.14
OS Version: Windows_NT x64 10.0.21364
VS Code version: 1.55.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

report issue

repo: felixfbecker/vscode-php-intellisense


text:
Performance improvements for formatting in SqlString

Improve performance by:

Returning early if there are no values to use for formatting
Not copying the values argument if it is already an Array
Parsing the SQL string using the technique from #1390

Benchmark Results

Query
Before (ops/sec)
This PR (ops/sec)
Speedup (PR/before)

no values
1,733,030
48,704,838
28

1) simple query
759,563
1,925,109
2.5

2) more values
582,647
1,098,441
1.9

3) a lot of values
366,547
507,246
1.4

4) long query string, few values
647,084
1,772,840
2.7

See this gist for the code.

Thanks, again, @nwoltman! I added you to the package.json over the weekend as well :) LGTM besides the two comments I have.

Updated, waiting on AppVeyor (@dougwilson do you have the power to cancel those intermediary commits I pushed that got queue up for testing on AppVeyor?)

@dougwilson do you have the power to cancel those intermediary commits I pushed that got queue up for testing on AppVeyor?

Yep! Canceled them.

authors: dougwilson nwoltman

repo: felixge/node-mysql


text:
'ml' is not recognized as an internal or external command

I get an error stating
  'ml' is not recognized as an internal or external command,
  operable program or batch file.
C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\deps\libffi\ffi.targets(28,5): error MSB3721: The command "call ml "/nologo" "/safeseh" "/c" "/FoRelease\obj\ffi\win32.obj" "..\..\..\deps\libffi\src\x8
6\win32.asm"" exited with code 1. [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\deps\libffi\ffi.vcxproj]
I had entered a separate issue in the win-ca repository. However it seems to center around the windows-build-tools and the having VS installed at C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin rather than C:\Program Files\Microsoft Visual Studio 14.0\VC\bin
To Reproduce:

Create an empty folder
Run npm init -y
Run npm install --global windows-build-tools and below is my output

user@machine MINGW64 /c/Users/user/Source/Repos/windows-build-tools-issue
$ npm install --global windows-build-tools

> windows-build-tools@3.0.0 postinstall C:\Users\user\AppData\Roaming\npm\node_modules\windows-build-tools
> node ./dist/index.js

Downloading BuildTools_Full.exe
[>                                            ] 0.0% (0 B/s)
Downloaded BuildTools_Full.exe. Saved to C:\Users\user\.windows-build-tools\BuildTools_Full.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
Successfully installed Visual Studio Build Tools.
------------------- Python --------------------
Python 2.7.14 is already installed, not installing again.

All done!

+ windows-build-tools@3.0.0
added 1 package from 1 contributor and updated 2 packages in 71.689s

Run npm i --save win-ca

RyanGat-CA@L04283RYANGAT MINGW64 /c/Users/RyanGat/Source/Repos/windows-build-tools-issue
$ npm i --save win-ca

> ref-napi@1.4.0 install C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi
> node-gyp rebuild

C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi>if not defined npm_config_node_gyp (node "C:\Users\RyanGat-CA\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Users\RyanGat-CA\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  win_delay_load_hook.cc
  Generating code
  Finished generating code
  nothing.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\\nothing.node
  nothing.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\nothing.pdb (Full PDB)
  binding.cc
  win_delay_load_hook.cc
..\src\binding.cc(177): warning C4244: 'argument': conversion from 'int64_t' to 'std::size_t', possible loss of data [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\binding.vcxproj]
..\src\binding.cc(229): warning C4244: 'argument': conversion from 'int64_t' to 'double', possible loss of data [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\binding.vcxproj]
..\src\binding.cc(298): warning C4244: 'argument': conversion from 'uint64_t' to 'double', possible loss of data [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\binding.vcxproj]
..\src\binding.cc(384): warning C4244: 'argument': conversion from 'int64_t' to 'std::size_t', possible loss of data [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\binding.vcxproj]
     Creating library C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\binding.lib and object C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\binding
  .exp
  Generating code
  Finished generating code
  binding.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\\binding.node
  binding.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ref-napi\build\Release\binding.pdb (Full PDB)

> ffi-napi@2.4.3 install C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi
> node-gyp rebuild

C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi>if not defined npm_config_node_gyp (node "C:\Users\RyanGat-CA\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Users\RyanGat-CA\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  Building assembly file ..\..\..\deps\libffi\src\x86\win32.asm
  'ml' is not recognized as an internal or external command,
  operable program or batch file.
C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\deps\libffi\ffi.targets(28,5): error MSB3721: The command "call ml "/nologo" "/safeseh" "/c" "/FoRelease\obj\ffi\win32.obj" "..\..\..\deps\libffi\src\x8
6\win32.asm"" exited with code 1. [C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\deps\libffi\ffi.vcxproj]
  win_delay_load_hook.cc
  Generating code
  Finished generating code
  nothing.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\Release\\nothing.node
  nothing.vcxproj -> C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi\build\Release\nothing.pdb (Full PDB)
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\RyanGat-CA\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\RyanGat-CA\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\RyanGat\Source\Repos\windows-build-tools-issue\node_modules\ffi-napi
gyp ERR! node -v v8.11.2
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN windows-build-tools-issue@1.0.0 No description
npm WARN windows-build-tools-issue@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ffi-napi@2.4.3 (node_modules\ffi-napi):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ffi-napi@2.4.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ win-ca@1.1.0
added 2 packages from 5 contributors in 41.281s

Please let me know if you need any additional information.

I resolved this issue by adding C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin to my PATH. That resolved the issue.

repo: felixrieseberg/windows-build-tools


text:
Chrome 48: cropper('getCroppedCanvas').toDataURL is not a function

I'm receiving an error with Chrome 48.0.2564 only and its saying toDataURL is not a function. I'm assuming this is an issue with the getCroppedCanvas although I'm not able to recreate this locally. Are others getting this kind of issue?

It is all fine in my Chrome 48, just check your own code to fix it.

@wcatron working fine for me. Make sure that when you call $("#my_selector").cropper("getCroppedCanvas") the return value is a Canvas Element
It should look like, <canvas width="1024" height="576">
If it really is your browser just do a test.
Open up your console and type document.createElement("canvas").toDataURL, the return value should be the specified function, or will throw an error as you say.

Had the same problem.
Changed "autoCrop" to true and it returns the canvas instead of an image.

I finally figured out the underlying issue. getCroppedCanvas only works if you are actually cropping, which explains why setting "autoCrop" to true would fix the issue for some. However I wanted the user to be able to not crop their image if they wanted and used the "clear"/"crop" method to toggle the crop feature. Unfortunately that means you can't save the image if you're not cropping it.

I also encountered this problem, because the object is not to find the object Jquery

authors: ChillerPerser fengyuanchen tingfeng-key vinnymac wcatron

repo: fengyuanchen/cropper


text:
Update chart home-assistant to 0.2.66

This PR contains the following updates:

Package
Update
Change

home-assistant
patch
0.2.65 -> 0.2.66

Release Notes

pajikos/home-assistant-helm-chart (home-assistant)
v0.2.66
Compare Source
📦 Uncategorized

Added support for configuring all possible probes
Merge pull request #65 from pajikos/feature/probes
Released version 0.2.66 of the helm chart

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

repo: fenio/homelab


text:
🛑 Debugger is down

In 1f1e297, Debugger (https://debug.ferdium.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Debugger is back up in 7522519 after 58 minutes.

repo: ferdium/ferdium-status


text:
remove bindle flags from spin deploy

--buildinfo, --no-buildinfo , -d/-staging-dir and -e/--deploy-existing-bindle

--staging-dir and --deploy-existing-bindle are gone.  Do we also want to remove --buildinfo and --no-buildinfo?  Currently it seems like the buildinfo is appended to the version part of the OCI tag (e.g. cloud.fermyon.com:myspiffyapp:0.0.1-buildinfo) but I am not sure if that's useful given that OCI tags are mutable?
If we think buildinfo is not useful, should we also remove the random buildinfo?  Again I am not sure if it is significant e.g. for application URLs.

Well --no-buildinfo crashes the deployment process after uploading the app so that one can get in the sea

😬 Yes, let's remove both.

Should we still create the random suffix or can I exterminate that too?

Should we still create the random suffix or can I exterminate that too?

Again, I'm pretty sure it isn't used in any of our app check/ready logic, so should be good to remove.  I can help verify/test when PR is up.

authors: itowlson michelleN vdice

repo: fermyon/cloud-plugin


text:
feat: accept a values file for spin new

Makes spin new accept a file which sets parameters defined in the template.
The file can be provided via --values-file.

If a parameter is set in both the file and as CLI option, the value provided
as option takes precedence.
If a value is not specified (neither in the file nor as CLI option), the user
will be asked to enter the missing value in a prompt. I.e. not every
parameter must be set in the file.

Example usage
# ./values.toml
project-description = "This is a project."
http-base = "/"
http-path = "/foo"

After building spin with these changes, the following command scaffolds a new
app with parameters read from the file:
spin new --values-file values.toml http-rust foo

Fixes #492
cc @fibonacci1729
Signed-off-by: Moritz moritz.zielke@gmail.com

Thanks @mooori ! This is excellent

repo: fermyon/spin


text:
Use getters for auth-related properties in Service Options

not just string, should be string | () => string

closing as we haven't gotten a request for this

authors: dannysheridan zachkirsch

repo: fern-api/fern-typescript


text:
Wrap lines option in request and response examples

Feature Description
A checkbox to wrap lines in code blocks and request+response examples. I saw this feature here(https://docs.cdp.coinbase.com/cdp-sdk/reference/getasset) and thought it was pretty cool.
Use Case
When responses return long strings or many nested properties that are difficult to read.

@nateKlaux love the idea of bringing the best-in-class ideas from other docs sites into Fern Docs.  Is there a specific code block you have where you'd want this? Will allow us to test when we build it!

authors: dannysheridan nateKlaux

repo: fern-api/fern


text:
c#, improvement: set instead of init field accessors in types

Types are now generated with set accessors rather than init accessors to improve flexibility of object construction.

@dsinghvi no -- all required fields must still be provided at initial object initialization, so users must explicitly choose to put null or some other temp value if they wish to set it later user set. This feels ideal


text:
Don't focus tree when tracking active file.

This is a really small change but is essential for people who uses vim keybindings. When going to definitions of functions, it changes the focus to the solution explorer which breaks the mouseless experience.

hi @fernandoescolar
Please review the PR and if there is something wrong please let me know.


text:
Fix typo in renderer/views/player.js

Previously, the following error was thrown on player open:
rendering error: Cannot read property 'false' of undefined
	TypeError: Cannot read property 'false' of undefined
    at D:\Workspace\webtorrent-desktop\renderer\views\player.js:439:43
    at Array.forEach (native)
    at renderPlayerControls (D:\Workspace\webtorrent-desktop\renderer\views\player.js:418:13)
    at Object.Player (D:\Workspace\webtorrent-desktop\renderer\views\player.js:22:9)
    at getView (D:\Workspace\webtorrent-desktop\renderer\views\app.js:81:20)
    at App (D:\Workspace\webtorrent-desktop\renderer\views\app.js:44:30)
    at render (file:///D:/Workspace/webtorrent-desktop/renderer/main.js:126:12)
    at redraw (D:\Workspace\webtorrent-desktop\node_modules\main-loop\index.js:65:23)
    at D:\Workspace\webtorrent-desktop\node_modules\main-loop\node_modules\raf\index.js:72:10

It is fixed now.

Do you intend to provide integration tests in somewhat near future? It should help to prevent things like that on the master branch.
I could work on that once I'm done with #642 if you want to, but I'll need some guidelines (or at least a green light).

@dcposch

@feross @dcposch This should be merged and released ASAP, since successful dlna discovery basically crashes the program.

LGTM. This sucks a lot and is entirely my bad. I'll look at the new telemetry and try to find out how many users were affected

authors: Goldob dcposch mathiasvr

repo: feross/webtorrent-desktop


text:
WebTorrent Desktop 0.17.0

Checklist

[x] Test on Mac
[x] Test on Windows
[x] Test on Linux
[x] Test auto updaters

https://github.com/feross/webtorrent/pull/928

@grunjol @feross would be cool if someone tried installing the .deb file and tested this release on Linux
because we recently added 32- and 64-bit versions, feross might want to test the auto updater

https://github.com/feross/webtorrent-desktop/releases/tag/v0.17.0

Tested on Ubuntu 16.04 64bits. Working fine (and with a very fast startup time!)

Thanks @grunjol  !
I think @feross has a two Windows VMs (32- and 64-bit) the app at v0.16 on them. Let's run them and make sure they auto update correctly.

I'll test this out shortly.

It's not easy to test the autoupdater on an unreleased version

We should fix that

Server is out of space. Looking into it.

webtorrent.io is currently down
How much downtime is there each time we update this repo?
Do we have something like Uptime Robot for webtorrent.io ? I use it for scramble.io and dcpos.ch, it's free and works pretty well

Server is out of space. Looking into it.

How much downtime is there each time we update this repo?

No more than a second or two. The server is turned off, a couple mv commands run (those are instant), then it is started again.
https://github.com/feross/webtorrent-www/blob/master/bin/deploy.sh#L17-L22

Do we have something like Uptime Robot for webtorrent.io ?

Just signed up. @dcposch I'll add your email to the notification list.

Okay -- added more storage capacity to the server, the disk resizing I did during the migration a few weeks ago had failed. But it's all good now!
Now -- testing the autoupdater.

@dcposch Please accept the email invitation so I can add you to the alerts.

done

@dcposch @feross uptimerobot only checks externally if the server is up. I recommend you NewRelic, I have 100+ servers under the free account (only show the last 24hs stats) but you can setup interval server alerts (disk space, I/O, CPU usage) to avoid.

@dcposch Added you

@grunjol @feross Linode also offers that type of server monitoring (disk space alerts, I/O, CPU). I think you want both. Server monitoring is good but you also want to check that the service is actually up, and Uptime Robot has the advantage of simplicity
I tested the auto updaters on Windows. Installed 0.16 64-bit. Correctly updated to 0.17 64-bit.
Installed 0.15, which only came in 32-bit. Updated to 0.17 32-bit, which then updated to 0.17 64-bit.
Looks good.

@dcposch Nice. I'm still struggling to get it downloaded over here. GitHub is silly slow. I bet they're throttling us, since we're using around 600GB of bandwidth per month at the moment.

Issue opened: https://github.com/feross/webtorrent-www/issues/108

authors: dcposch feross grunjol

repo: feross/webtorrent-www


text:
MIME Type not supported for mkv files

Hi,
I was experimenting with webrtc and not able to solve how to stream MKV files. All I see is MIME Type not supported.
The last time I was working on media encoding I came to know that MKV should be explicitly defined as DOM type.
Thanks in advance.

Next time please search before opening a new issue: https://github.com/feross/webtorrent/issues?q=is%3Aissue+mkv+is%3Aclosed
See: https://github.com/jhiesey/videostream/issues/29

repo: feross/webtorrent


text:
Remove unused Cargo.lock`s

Seems these got lost after some refactoring, the root lock is the one updated.

Thank you for the PR! You're right, these crates are intended to be used as libraries and are not binaries, so Cargo.lock shouldn't be committed to the repository in the first place.

repo: ferrumfix/ferrumfix


text:
No error message when login with posting key and submit story

Step to reproduce:

Login in advanced mode using posting key
Select Submit a story

Tested at iOS device.

Did submit story fail? Generally, posting key and main password is check before broadcasting transaction and if transaction is successfully signed then broadcast goes through.

Probably, thought for a second and nothing happened.

Did login screen closed? if not, then there is an issue with devicetoken, which I am testing now...

Login ok, after login with posting key then I click Submit a story menu - it's thought for a second and nothing happened.

Oh right, sorry! Yes it has been reported and fixed, should work with upcoming release v1.3.3 https://github.com/feruzm/esteem/commit/1906018af0439f36a172b9cd9d05332b102ba90a

authors: feruzm testzcrypto

repo: feruzm/esteem


text:
1.4.3 jsp版本，本地配置没有问题，部署在服务器上显示后端配置不正确加载配置文件错误

1.4.3 jsp版本，本地配置没有问题，部署在服务器上显示后端配置不正确加载配置文件错误

看看是不是路径的问题，java的那段代码对 windows 和 linux 的路径处理分割有点问题，没有处理 windows 的 '' 路径分割。

authors: Phinome zoud

repo: fex-team/ueditor


text:
在angular的一些指令里如ng-show则无法生效

下面是Jade代码：
如果把webuploader封装成指令，放在ng-show指令下，则webuploader则点击没反应：
div(ng-show="9>data.photos.length")
    p.form-control-static.text-info 添加照片(支持jpg/png/bmp)
    web-uploader-simple(onqueued, onsuccess, onerror, onprogress)

这是指令代码：
//- webuploader html directive
.g-webuploaderSimple
  div(ng-hide="uploading")
    #filePicker 选择图片
  div(ng-show="uploading")
    span.l-uploadingTip 上传中...
    a.btn.btn-warning(ng-click="uploadCancel()") 取消上传

coffee:
.directive("webUploaderSimple", [
  "$timeout", "WebApi", "Paths"
  ($timeout, WebApi, Paths)->
    return {
      restrict: "E"
      scope: {
        onqueued: "="
        onsuccess: "="
        onerror: "="
        onprogress: "="
        oncomplete: "="
      }
      templateUrl: Paths.get("go", "webUploaderSimple")
      link: (scope, elem, attrs)->
        currentUploadFile = null

        #WebUploader
        uploader = new WebUploader.Uploader({
          swf: __uri("../lib/webuploader/Uploader.swf")
          formData: {
            header: JSON.stringify(WebApi.getApiHeader())
            body: null
          }
          server: WebApi.url("webUploader")
          pick: {
            id: "#filePicker"
            label: "点击选择图片"
          }
          fileNumLimit: 1
          method: "post"
          accept: {
            title: "Images"
            extensions: "gif,jpg,jpeg,bmp,png"
            mimeTypes: "image/*"
          }
        })

        log("webUploaderSimple")

        scope.uploadCancel = ()->
          uploader.stop()
          uploader.cancelFile(currentUploadFile)
          reset()

        setUploading = (b)->
          $timeout(()->
            scope.uploading = b
          )

        reset = ()->
          uploader.reset()
          setUploading(false)

        uploader.on("fileQueued", (file)->
          setUploading(true)
          uploader.upload()
          currentUploadFile = file
          if scope.onqueued
            scope.onqueued(file)
        )

        uploader.on("uploadSuccess", (file, response)->
          reset()
          if scope.onsuccess
            scope.onsuccess(file, response)
        )

        uploader.on("uploadError", (file, response)->
          reset()
          if scope.onerror
            scope.onerror(file, response)
        )

        uploader.on("uploadProgress", (file, percentage)->
          if scope.onprogress
            scope.onprogress(file, percentage)
        )

        uploader.on("uploadComplete", (file)->
          if scope.oncomplete
            scope.oncomplete(file)
        )
    }
])

如果把上述ng-show去掉后，控件才生效。是否与angularjs这方面代码不兼容？
希望能尽快解决！

个人封装的angular指令 ，没问题
https://github.com/giscafer/angular-webuploader

authors: giscafer luozt

repo: fex-team/webuploader