[SPARK-22375][TEST] Test script can fail if eggs are installed by set…

…up.py during test process
What changes were proposed in this pull request?
Ignore the python/.eggs folder when running lint-python
How was this patch tested?

put a bad python file in python/.eggs and ran the original script.  results were:

xins-MBP:spark xinlu$ dev/lint-python
PEP8 checks failed.
./python/.eggs/worker.py:33:4: E121 continuation line under-indented for hanging indent
./python/.eggs/worker.py:34:5: E131 continuation line unaligned for hanging indent

test same situation with change:

xins-MBP:spark xinlu$ dev/lint-python
PEP8 checks passed.
The sphinx-build command was not found. Skipping pydoc checks for now

Can one of the admins verify this patch?

ok to test

I think you can add it here instead https://github.com/apache/spark/blob/0e31e28d483918c1de26f78068e78c2ca3cf7f3c/dev/tox.ini#L19

Test build #83171 has started for PR 19597 at commit 9568906.

Test build #83172 has started for PR 19597 at commit 59efcb8.

Test build #83171 has finished for PR 19597 at commit 9568906.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83171/
Test PASSed.

Test build #83172 has finished for PR 19597 at commit 59efcb8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83172/
Test PASSed.

Merged to master.

@xynny, mind if I ask your JIRA id?


[BUG] Localized scripts not showing up correctly on website

When scripts take advantage of the new localization features, the metadata extractor is not able to grab things correctly for use on the website.
Although #689 refers specifically to the bundler, it may be that solving this current issue requires rewriting the metadata extractor in Lua, since it's no longer a matter of simply parsing out strings from the .lua file.
cc: @rpatters1

Oof. Not an easy fix I can think of. If we let our meta-data extraction dictate what scripts can do, it feels a bit like tail wagging dog.
The safest and more future-proof solution would probably be to do what RGP Lua and (seemingly) JW Lua do. That is, extract the plugindef from the script and execute it in a minimal Lua environment, then extract the results. That way there would be no need to parse it directly.
I can tell you that embedding Lua in a program is trivially simple. If need be I could write a standalone program to do it. But it may be possible to simply run Lua from the command line and get what we need.

Yes, I think I can configure our action runner with Lua and execute plugindef(). This will take some experimentation and probably won't happen in the next couple of days, but hopefully within the week.

MinJWLuaVersion and MaxJWLuaVersion are defined as numbers. The current get-metadata action reads these as strings, but the new Lua-based one sees it, correctly, as a number -- but turns it into a string for compatibility with what the website expects.
This means that finaleplugin.MinJWLuaVersion = 0.70 will result in a string value of 0.7.
I can think of three ways to handle this:

Leave it as-is.
After Lua returns all the finaleplugin values to JS, use JS to override this property by grabbing the string out of the original plugindef() text.
Change these properties to strings in plugindef().

I'm hoping that if we do 3, JW/RGPLua will still be able to use the value correctly. I imagine that this is fine, since Lua will coerce strings to numbers when doing arithmetic or mathematical comparisions. @rpatters1 Can you confirm?
I'd really rather not do # 2, because it would be the only value that JS reads directly from the code, and I'm concerned that # 1 would look strange on the website. It feels like version numbers should be strings anyway, for reasons like this.

I suppose there's a fourth approach, which is for JS to look at the returned string (e.g., 0.7) and work magic on it to make sure there are at least 2 decimal places. Conceptually, this is okay with me because I'm already doing some manipulation of returned values in JS, but it doesn't feel great. Better than # 2, perhaps, but still not as clean as # 4.

Could you use string.format to guarantee 2 decimal places?

To answer your question, I don't know what either plugin would do with it. It might work, but I'd rather not do it if there's another way.
This Lua code should produde "0.70":
local formattedString = string.format("%.2f", 0.7)

Sure, I can get 2 decimals in Lua or JS. But then what about version 0.100? Or 1.2?
I'll play with some options, see if I can get consistent results.

I don't know what JW Lua does, but  RGP Lua takes those numbers and multiplies them by 1000 and then converts them to integers. So 0.70 becomes 700. Then it does numerical comparisons.
As long as I'm working on RGP Lua, I will commit to the minor version number never being fewer than 2 digits or more than 3.

Actually I realize my approach really doesn't work with 3 digits, so if we ever get to v0.99, it may be time to take the plunge to 1.00.

(I think it should be v1 already--hard to call this still a beta!)
If RGP multiplies by 1000, then it would actually be fine with a string value, because the multiplication coerces it to a number. But if we don't know what JW does....
The problem, of course, is that version numbers really are strings, not numbers.

I would have to debug into the bowels of LuaBridge to find out if it would automatically convert a string to a float on the c++ side. It might or it might not.
My recommendation is for now to assume 2 decimal places and if the day ever comes when that's not the case, we'll cross the bridge them.


in initialize: execution expired (Faraday::ConnectionFailed)

I run my latest fastlane and get failed. No error happened for built-in action like gym, but when I run any custom lane in Fastfile, I got this output:
[20:52:44]: -------------------------------------------------
[20:52:44]: --- Step: Verifying required fastlane version ---
[20:52:44]: -------------------------------------------------
[20:52:44]: Your fastlane version 2.30.2 matches the minimum requirement of 2.28.7  ✅
[20:52:44]: ------------------------------
[20:52:44]: --- Step: default_platform ---
[20:52:44]: ------------------------------
/usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:904:in `initialize': execution expired (Faraday::ConnectionFailed)
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:904:in `open'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:904:in `block in connect'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/timeout.rb:103:in `timeout'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:902:in `connect'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:887:in `do_start'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:876:in `start'
	from /usr/local/Cellar/ruby/2.4.1_1/lib/ruby/2.4.0/net/http.rb:1407:in `request'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/adapter/net_http.rb:80:in `perform_request'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/adapter/net_http.rb:38:in `block in call'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/adapter/net_http.rb:85:in `with_net_http_connection'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/adapter/net_http.rb:33:in `call'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/request/url_encoded.rb:15:in `call'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/rack_builder.rb:139:in `build_response'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/connection.rb:386:in `run_request'
	from /usr/local/lib/ruby/gems/2.4.0/gems/faraday-0.12.1/lib/faraday/connection.rb:186:in `post'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane_core/lib/fastlane_core/crash_reporter/crash_reporter.rb:77:in `send_report'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane_core/lib/fastlane_core/crash_reporter/crash_reporter.rb:29:in `report_crash'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:80:in `rescue in run!'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:106:in `run!'
	from /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.4/lib/commander/delegates.rb:15:in `run!'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane/lib/fastlane/commands_generator.rb:303:in `run'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in `take_off'
	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.30.2/bin/fastlane:20:in `<top (required)>'
	from /usr/local/bin/fastlane:22:in `load'
	from /usr/local/bin/fastlane:22:in `<main>'

I installed ruby by homebrew in /usr/local/bin/ and version information is ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16] and fastlane is installed from gem and version is 2.30.2
Any help?

Here is the result of fastlane env
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.12.4

Ruby
2.4.1

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.4 (16E195)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.1_1/lib

OpenSSL Version
OpenSSL 1.0.2k  26 Jan 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.3.2

System Locale

Variable
Value

LANG
zh_CN.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# 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

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.28.7"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    puts "before lane"
  end

  desc "demo"
  lane :demo do
    puts "hello world"
  end

  desc "Creating a code signing certificate and provisioning profile"
  lane :signing do
    cert
    sigh(force: true)
  end

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

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

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

  desc "Take screenshots"
  lane :screenshot do
    snapshot
  end

  desc "Create IPA"
  lane :build do
    increment_build_number
    gym
  end

  desc "Upload to iTunes Connect"
  lane :upload do
    deliver
  end

  desc "Create app icon"
  lane :genicon do
    appicon(
      appicon_image_file: './fastlane/metadata/AppIcon.png',
      appicon_devices: [:iphone, :ipad],
      appicon_path: 'TaoYanZuoYe/Assets.xcassets'
    )
  end

  desc "lane test"
  lane :demo do
    puts "hello world"
  end

  desc "生成 Framework ，并引用对应的 Framework"
  lane :pod_generate_frameworks do |options|
    ENV['PODFILE_TYPE'] = 'generate_frameworks'
    ENV["BUILD_PODS"] = options[:build]
    ENV["FRAMEWORK_PODS"] = ''
    cocoapods(use_bundle_exec: false)
    ENV['PODFILE_TYPE'] = ''
    ENV["BUILD_PODS"] = ''
    ENV["FRAMEWORK_PODS"] = options[:build]
    if !(ENV["FRAMEWORK_PODS"] && ENV["FRAMEWORK_PODS"].length > 0) # 如果 build 为空，说明是 build all ，设置成 development
      ENV['PODFILE_TYPE'] = 'development'
    end
    cocoapods(use_bundle_exec: false)
  end

  desc "直接引用 Framework"
  lane :pod_frameworks do |options|
    ENV['PODFILE_TYPE'] = ''
    ENV["FRAMEWORK_PODS"] = options[:frameworks]
    if !(options[:frameworks] && options[:frameworks] != 'all')
      ENV['PODFILE_TYPE'] = 'development'
    end
    cocoapods(use_bundle_exec: false)
  end

  desc "全部使用源码"
  lane :pod_source do |options|
    ENV['PODFILE_TYPE'] = ''
    ENV["FRAMEWORK_PODS"] = ''
    cocoapods(use_bundle_exec: false)
  end

  after_all do |lane|
    # This block is called, only if the executed lane was successful
    puts "lane success!"
    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "com.lejent.TaoYanZuoYe" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "CD76TM5QAC" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.30.2
🚫 Update available

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-appicon
0.6.0
✅ Up-To-Date

fastlane-plugin-pgyer
0.2.1
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.1.2

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
2.0.7

xcpretty
0.2.7

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.3.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

json
2.1.0

io-console
0.4.6

openssl
2.0.3

fastlane-plugin-appicon
0.6.0

fastlane-plugin-pgyer
0.2.1

generated on: 2017-05-18

I have the same issue and here is my env
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.5

Ruby
2.4.0

Bundler?
false

Git
git version 2.6.4

Installation Source
~/.rvm/gems/ruby-2.4.0/bin/fastlane

Host
Mac OS X 10.12.5 (16F73)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.4.0/lib

OpenSSL Version
OpenSSL 1.1.0e  16 Feb 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.3.2

System Locale

Variable
Value

LANG
zh_CN.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# 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

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.19.3"

default_platform :ios

platform :ios do

  lane :beta do
    increment_build_number(
      xcodeproj: "./ios/jimi.xcodeproj",
      build_number: latest_testflight_build_number(version: get_version_number(xcodeproj: "./ios/jimi.xcodeproj")) + 1
    )
    gym(
      workspace: "./ios/jimi.xcworkspace",
      scheme: "jimi"
    )
    testflight(skip_submission: true, app_identifier: "com.zaodao.jimi", ipa: "jimi.ipa")
    send_to_dingtalk(:text => "请前往testflight下载",:title => "iOS测试版本已更新",:url => "https://itunesconnect.apple.com")
  end

  lane :release do
    increment_build_number(
      xcodeproj: "./ios/jimi.xcodeproj",
      build_number: latest_testflight_build_number(version: get_version_number(xcodeproj: "./ios/jimi.xcodeproj")) + 1
    )
    gym(
      scheme: "jimi",
      project: "./ios/jimi.xcodeproj"
    )
    testflight(skip_submission: true, app_identifier: "com.zaodao.jimi", ipa: "jimi_release.ipa")
    send_to_dingtalk(:text => "请前往testflight下载，如果不需更新到正式版请勿下载",:title => "iOS正式版本已更新",:url => "https://itunesconnect.apple.com")
  end

end

`./fastlane/Appfile`
app_identifier "com.zaodao.jimi" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "84EMB66X65" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.32.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.14.6

io-console
0.4.6

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

excon
0.55.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

hurley
0.2

jwt
1.5.6

memoist
0.15.0

multi_json
1.12.1

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

faraday_middleware
<IP_ADDRESS>

json
2.1.0

openssl
2.0.2

plist
3.3.0

faraday
0.12.1

unf
0.1.4

domain_name
0.5.20170404

terminal-table
1.8.0

unicode-display_width
1.2.1

netrc
0.11.0

rest-client
1.8.0

aliyun-sdk
0.5.0

mini_portile2
2.1.0

nokogiri
1.7.2

mime-types
2.99.3

generated on: 2017-05-22

@huang-kun do you have any solution to this?

@gaoneng1989 not yet. Even with the latest version!

Could you update to the most recent release and try again? 👍

Same issue, waiting for solution...
Here is my env:
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.12.5

Ruby
2.4.1

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.5 (16F73)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.1_1/lib

OpenSSL Version
OpenSSL 1.0.2k  26 Jan 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.3.2

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.33.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.2.1

terminal-table
1.8.0

plist
3.1.0

addressable
2.4.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types
2.99.2

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.4

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

json
2.0.2

mini_magick
4.5.1

multi_xml
0.5.5

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

io-console
0.4.6

openssl
2.0.3

generated on: 2017-05-24

Hey everyone, thanks for reporting this. Are you based in China? On the first look it seems like you can't reach the crash reporting server, which is hosted by Google, and parts of Google are blocked in China. We'll work on a fix to not crash like this.
In the mean-time, could you connect to a VPN outside of China and see if that fixes the issue for you? Thanks

We did try some actions like cert under VPN environment, but it didn't anyway...

Same issue, waiting for solution too ...
Here is my env:
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.4

Ruby
2.4.1

Bundler?
false

Git
git version 2.9.3 (Apple Git-75)

Installation Source
~/.rvm/gems/ruby-2.4.1/bin/fastlane

Host
Mac OS X 10.12.4 (16E195)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.4.1/lib

OpenSSL Version
OpenSSL 1.1.0e  16 Feb 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.1

System Locale

Variable
Value

LANG
zh_CN.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# 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

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.33.0"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."

  end

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

  lane :tofirdebug do
    gym(scheme:"EloancnBorrower",
      workspace:"EloancnBorrower.xcworkspace",
      export_method:'ad-hoc',
      clean:true,
      configuration:"Debug",
      output_name:"EloancnBorrowerDebug.ipa",
      output_directory:'/Users/donghuixiang/Desktop/eloanBorrowIpa')
    fir publish "/Users/donghuixiang/Desktop/eloanBorrowIpa/EloancnBorrowerDebug.ipa" -T fir_token -c "测试环境"
  end
  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: "EloancnBorrower") # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

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

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics

`./fastlane/Appfile`
app_identifier "com.eloancn.EloancnBorrower" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "685MD7243L" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.33.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.15.0

io-console
0.4.6

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.2.1

terminal-table
1.8.0

plist
3.3.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

json
2.0.2

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

faraday_middleware
<IP_ADDRESS>

openssl
2.0.3

generated on: 2017-05-24

Thanks @ohayon, this will be fixed in the next release 👍


feat(frontend): include maskable icons

Motivation
We add maskable icons that are best practice nowadays for modern Android devices and Google products.
Ref: MDN docs.

For what is explained around, the background will be automatically taken from the background_color prop of the manifest. So theoretically, it needs a transparent background no? or shall we already make it round with the background we want?

Agree with yout but, the documentation also ends with following:

Finally, give your maskable icon an opaque background color to fill the entire icon area.

This editor - https://progressier.com/maskable-icons-editor - or article -https://intercom.help/progressier/en/articles/6208771-can-a-pwa-icon-have-a-transparent-background - also mention "a solid background"
That's why I'm not sure but, we can try.

This editor - https://progressier.com/maskable-icons-editor - or article -https://intercom.help/progressier/en/articles/6208771-can-a-pwa-icon-have-a-transparent-background - also mention "a solid background"

After having read that, if I am not mistaken, we can actually reuse the same exact images for the maskable icons, but just marking them as maskable. I tested it in the website you provided and the icon we have would work for purpose "maskable"

and in this article it says that the default purpose is "any" that allows the icon to be used in any context (maskable, and non-maskable).
@peterpeterparker if you agree, I would close this PR without merging, since it would not add particular difference for now, unless we decide to have different icons for the different purposes.

if you agree

Not really. In my opinion, the best practice for creating icons is to use square images that are maskable. This means providing icons with a plain background and a square shape, which ensures compatibility across different devices and platforms. Although other formats might work, as you tested, they can be unreliable because we won't be testing on each individual device. Using square, maskable images is a safe and consistent approach which does not require much effort.
Of course, it's your call—this is only my recommendation.

Talked with Misha (covering Artem) and he said to use the same background of the favicon


Clean up argument checking and default value imputation for schedulers

Issue #, if available:
Description of changes:
Extends something I did for GP searchers to schedulers. Arguments are losely type-checked, and default values are maintained consistently (e.g., do not have to copy&paste default values from superclass).
Also, whenever a default value is imputed, this is written into the log, so you later on know what argument values were used.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-540-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-540/2/index.html

Job PR-540-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-540/3/index.html

Job PR-540-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-540/4/index.html


[REQUEST]: Save the pre-processed brain image that is actually used for training and/or evaluation.

Hello!
This is not an issue but rather a request for help!
I would like to modify or intervene the pipeline in the correct spot (somewhere inside predict.py probably !?) in order to be able to save a case's preproccessed brain.nii.gz without the lesions masks.
So pretty much the original .nii.gz with ROBEX and N4BIasFieldCorrection applied (If i'm not wrong, I am assuming these two processes are what you are using for the overall preproccessing)
Could you provide me with any insights of how I could achieve that?
The reason of this need is that I want to compute some statistics based on intensities and I want to remain consistent with your approach, instead of computing robex and n4BiasFieldCorrection from start. It seems like robex has some stochasticity too...
I sincerely apologize delving into your work after such a long time but since I have made questions in the past and observed your welcoming and willing spirit, I thought of giving it a try :)!
Thank you,
Theodore Tranos

Hi @thtranos,
Actually, all the preprocessed images are cached in a folder named 001_Preprocessed_Images/ (you can ignore the "_0000" suffix in the filenames). This folder is located in the root output directory that you specified. You don't need to modify any code for this. :smiley:

Hi @thtranos, Actually, all the preprocessed images are cached in a folder named 001_Preprocessed_Images/ (you can ignore the "_0000" suffix in the filenames). This folder is located in the root output directory that you specified. You don't need to modify any code for this. 😃

Additionally, please note that ROBEX introduces some randomness in its algorithm (controlled by a random seed), so even the same image may yield slightly different results across different runs. If you want the skull stripping results to be deterministic, please refer to this link.

Thanks for the reply. I was aware of this repository but they seem to not have been ROBEXed, those scans are the originals with applied N4BiasFieldCorrection right?
Also thanks for the link.

:smiley: Hi @thtranos,
Neither the ROBEX nor ANTs toolkits are included in this repository because they are too complex to fully integrate into the automatic installation process. If you haven't installed ROBEX or ANTs, the images will simply be copied without any modifications, so they will be identical to the originals.

@thtranos Yes, they are supposed to be applied to those images.


feat: add DA light node support

Overview
This PR adds support for a Celestia DA light client/node. Replaces #29
Resolves #25
Resolves #31

[x] Will be rebased on #28
[x] add ARCH check for DA light node image type https://github.com/celestiaorg/optimism/pull/29/commits/500517928fde63a194057c9be2dbf7e64dc6a300
[x] ensure that uptime is consistent using a light node vs. local-devnet https://github.com/celestiaorg/optimism/issues/31 https://github.com/celestiaorg/optimism/pull/29/commits/6962ec0357e4950a19899ab3b5581f41554535f7
[x] look into whether these issues are because the node was not fully synced (update: it was): https://github.com/celestiaorg/celestia-node/issues/2151
this is separate issue https://github.com/celestiaorg/celestia-node/issues/2152
[x] change DA node to use $home/.path-to-node-store to allow user to use their own node store (keys, data, config) 9ac02bc65e9a221653a07e3650a1e975d8be4bc5
[x] edit tutorial to reflect the above
[x] rewrite health check for DA node https://github.com/celestiaorg/optimism/issues/30 (this may not be necessary if the user should run their node locally to sync it before starting celopstia)
[x] add light node PWD
[x] update .gitignore
[x] add key that is funded with TIA

this will be a squash & merge PR

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

No reorgs after 10k blocks, except the one above. Bridge to L2 was also successful

https://github.com/celestiaorg/celestia-node/issues/2145

Needs rebase. Also changes to patches / yarn.lock don't feel relevant.
these were required to run on a mac, so can remove as ubuntu is default cc @tuxcanfly

i don't understand how this needs rebase. there are no merge conflicts.

need to look into starting on different platforms after seeing this again after removing the architecture check

Planning to remove the light node from the docker setup, to reduce complexity and improve DX/UX

hm, same behavior still for me running on 5239c9e161a6379c7b048400e2715bf640f41e7a

here are the full logs: https://gist.github.com/jcstein/7c75815310a8b680bd16578bfbe19256

ok so i changed the IP on celestia light start [...] to the one that is in the logs above ^ (<IP_ADDRESS>:26659) and it’s posting fine. i suppose it’s something to do with the networking on the box as @Ferret-san suggested
it’s posting data, but still getting errors from celestia-node (as expected)
here are logs https://gist.github.com/jcstein/666b75cd8611626ea6391bcb6e56e869


Add FMC support to STM32F429i_disc1 board

Use the H7 driver and add device tree node for STM32F429. Other F4 chips not tested.

Duplicate of #30438


Compatibility with UNIGUI

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

For Unigui
You need add FDGUIxWaitCursor to your serverModule and in your serverModule checked the property AutoCoInitialize

I need to test on IIS


fix shape based validation

This change breaks the excessively long chain of sh:node statements in the shape leading to recursion issues in pyshacl.
In essence most of the sh:node statements in the shapes could be removed, since this is also covered by sh:targetObjectsOf of the object.
So, if we have:
:x
 sh:path :y ;
 sh:node :z .

:z sh:targetObjectsOf :y .

we can omit :x sh:node :z.
I now only made a minimal change by removing one sh:node statement. But IMO we could remove all of them that match the above.
@DylanVanAssche what is your opinion on this?

If the removals are not punching holes in the coverage I'm all for it!
Basically, we must be able to validate via 2 ways:

Property paths
RDF type classes

Ok, then I will remove those sh:node statements that aren't necessary for this.


Added Moralis to Data tools page

Added Moralis as an API provider to the list of data tools in the Polygon documentation

Hi @filipmartinsson thanks so much for your contribution. Please accept my suggested edits.
In order to add this page to the site, you need to create a menu entry in mkdocs.yaml at the correct place.
Once you've done that, and tested it renders correctly, push the changes and I can merge.
Thank you :)

Hi @filipmartinsson thanks so much for your contribution. Please accept my suggested edits.
In order to add this page to the site, you need to create a menu entry in mkdocs.yaml at the correct place.
Once you've done that, and tested it renders correctly, please push the changes and I can merge.
Thank you :)

Thanks @kmurphypolygon . I've added it to the menu now. Appreciate the help :)


Adding embedd view extension

adding extension of embedd video....

tested on pkc-dev, will test the deployment using script


Sync: Optimize bookmarks JSON provision

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3241   👈

This comment was auto-generated by Graphite.


Fix ambiguous timestamps

Ambiguous timestamps are fixed now; tested with a generated unit test (various scenario's were tested).
After this; unit tests were disabled (they can be re-eabled by uncommenting the line with -DCONFIG_PERFORM_UNIT_TESTS in platformio.ini and recompiling).
A succesfull regression test was done on a DSMR5 smart meter.
Possible future improvements (of minor importance now; perhaps turn these into Trello cards on the backlog?):

remove redundant IS08601 formatting functions (simuilar functions now in src\dsmr_timestamp.cpp and src\dsmr_timestampTest.cpp)
improve test sequence start time definition (allow for specifying a more human-readable start time)
refactor TZ definition; perhaps even move to twomes-generic-esp-firmware. Things to sonsider/refactor:
-- twomes-p1-reader-firmware needs TZ to be at variuos places to Europe/Amsterdam for proper DSMR timestamp parsing. This is now done via #define TIMEZONE_DEFINITION "CET-1CEST,M3.5.0/2,M10.5.0/3" and calls to setenv("TZ", ...) and tzset() functions at various places.
-- The generic firmware has a function InitializeTimezone() in its src\generic_esp_32\generic_esp_32.cpp, which sets UTC.
-- The twomes-p1-reader-firmware uses a deviceTime() function which essentially returns time(NULL); (it should probably be simplified)
-- in summary, it seems as if the generic firmware concerns itself to setting the TZ envirnment variable to UTC, in order to make sure that the timestamps of the ESP device clock would be proper. However, the setting of the TZ environment variable does not influence the time(NULL) result, neither does it interfere with NTP properly setting the device clock. Only when considering setting the RTC on a M5CoreInk, we may need to pay attention to the influence timezones may have (the RTC seems to use a rather complex set of registers for year, month, day, hour, minute, second, in stead of an internal unix-time-style counter; we should be mindful when translating NTP results and device clock results (unix time) to the RTC registers and vice versa ans make sure we are consistent (use UTC for all transformations?)

When starting up the p1-reader while not on connected to the p1 port it successfully found out that baudrate and isdsmr5 should not be set. When this was done I connected the p1-reader to the p1 port and it set baudrate to 115200 and isdmr5 to 0 as expected. The following readings it used the nvs values and didn't need to recalculate anything.
Then I left on for 5,5 hours and the heartbeat stands at 33 right now, so it didn't reset. All other values are correct too, like timestamps and other meter readings.


Consider replacing requests

Requests has been the default suggestion for a python http client library, however it is starting to show its age.
I suggest replacing it in this guide with one of the alternatives, httpx
It is a drop-in replacement for requests, and it also adds async support among other things.

Agreed :) I'm working on the next version of the blog, and it does feature httpx instead of requests.

Out of curiosity, what do we get by using httpx over requests?

The ability to make async requests.
Requests is synchronous by default, to make async requests you can either wrap it or use a requests plugin.


Bug fix

Fix the bug when used in 2016.3, click path choosing caused NPE.
Your original code set tool frame invisible when choosing path, which  make it fail to create dialog (the logic of DialogWrapperPeerImpl.java require its father component, i.e. too frame, to be visible). So there exists two ways to solve it:

make tool frame visible;
choose another parent component for dialog to use;

I chose the second one to make it consistent with your original behavior.
I only tested on latest version of intellij (2016.1, 2016.3). Is there easy way to test on multiple versions?

Is all IDE contains the class WindowManagerEx ?

Tested on Android Studio 1.5.1 and it works well.
By the way, replace WindowManagerEx with WindowManager could be better?

I have not maintained this plugin for a long time, maybe you can add some of the long-awaited features for the user, such as generate getter and setter, custom field names, and more……

I am not sure whether replacing WindowManagerEx with WindowManager could be better, I just saw other part of idea source using WindowManagerEx to generate dialog so I mimic that code.
I may consider adding some of them if I have time.

May I refactor your repo structure? like removing those versions of zip?

Method findVisibleFrame () is defined in classWindowManager, the WindowManagerEx has extended WindowManager

Sure, you can do anything you want in your repo and pull request to here

link to #7


Showcase Submission for 85-the-game-of-life

Thank you Jayce Pearson for your contribution! A member of the Coding Train team will review it shortly.

The Colorful Game of Life
Jayce Pearson

Great work!!


Window title not automatically updating to active folder or filename text

VSCode Version: 1.21.1
OS Version: Win7 Enterprise SP1

Does this issue occur when all extensions are disabled?: Yes
Summary: The window title bar details are not consistent with the folder or filename that is open and active. Resizing the window causes the title to refresh and display properly.
Steps to Reproduce:

Open VS Code
Close "Untitled-1" that automatically opens in editor
Click on Explorer Icon in the Activity Bar
Click on "Open Folder" button
Select folder of files. (In this instance I am using a folder named  'Test' containing 2 files.)
Folder opens as expected, but widow title does not display the folder name:

Resize the window manually or use the windows maximize button, note that folder name now displays properly in the window title:

Double click the file 'index.html' to open in edit mode in the editor, note that there is not indication to the file in the window title bar:

Resize the window manually or use the windows maximize button, note that the file name now displays properly in the widow title:

This issue will also occur when tab focus is on a file. The previous filename will be displayed and not the current one. Resizing the window fixes the window title.

"styles.css" is the active tab, but "index.html" is being displayed in the window title bar:

Thanks
-Chris
//END

This issue appears to be related to #33506, so I will close it.


Take camera snapshot using VisionIPC

Probably no point in fixing up the RGB padding if we're going to merge https://github.com/commaai/openpilot/pull/22905 soon.


Some properties are parsed but never assigned to the properties dict

I just noticed colors get parsed but get never assigned to the dict. It looks like this is also the case for some other properties as well. If you agree this is legit I can investigate and possible append more commits.

Didn't see this PR, sorry about that. Fixed this bug and a few other property assignment bugs involving the vector integer properties under f05e0aa . Thanks for the help though!


Project Organization & Submodules

Project Organization & Submodules
Recently, we have been discussing the current organization of the project on Slack.
Basis for the Discussion:

IBAnimatable is a large codebase and will continue to grow as we add more features.

We want to limit the amount of unused imported code and decrease the size of the dependency.
e.g) Using IBAnimatable solely for Transitions yet still having to import all ActivityIndicators

Proposed Solution:

One possible approach would be to split the project using CocoaPods subspecs.
For example:
IBAnimatable would import the entire framework.
IBAnimatable/Core would import core protocols/components required by other subspecs.
IBAnimatable/Transitions imports transitions and IBAnimatable/Core
IBAnimatable/ActivityIndicators imports activity indicators and IBAnimatable/Core

I won't continue listing possible subspecs because they're a rough draft and likely to change.

I do think the inheritance hierarchy for UIKit could be a good guideline for this:
e.g) IBAnimatable/UIControls or IBAnimatable/Controllers

Pros:

Decreases the size of the dependency for IBAnimatable users and reduces unused imported code.

A more modular project is easier to debug, test, maintain, and optimize performance.

Working with more modular components would let us take each individual component further without bloating the code base and opens up the possibility for IBAnimatable plugins.

It could make supporting other platforms such as tvOS even easier.

Cons:

The change in imports could be an API breaking change for many users of IBAnimatable.

This could be limited by still having IBAnimatable import all subspecs.

It would most likely require decoupling some of the framework's components which could also lead to API breaking changes.

I agree with the needs here, a few questions:

How will it works for Carthage, Submodules... ? If one subspecs is a dedicated framework, then it will be straightforward
How will we name them? If you named it UIControls, does that mean I will have to do import UIControls? It's not quite clear what it represents, but if you named it AnimatableUIControls, it's starting to be long to write.
Should we have one repository by dedicated "subproject" or keep them all in the same? It's quite the same as IBAnimatableMaterial

Beside a few unclear points, I'm totally ok for introducing API breaking change since it will really improve the usage. We will have a big work on installation / migration documentation.
Also, it would be great to list all the modules we need to create to make this real.

Let me address the 4 points you brought up:

I have very limited knowledge of Carthage so that's why I didn't mention this. I would love to hear anyone's suggestions on this subject.

I think UIControls is a clear name choice. It would never be possible to import something like UIControls directly, it would have the prefix IBAnimatable/UIControls. This import would then import all the other IBAnimatable dependencies that it needs to function.

eg) Firebase currently uses a structure like this:
  - `import Firebase` <- imports all of Firebase

  - `import Firebase/Database` <- imports only Database tools

  - `import Firebase/Auth` <- imports only Auth tools

** If for some reason Auth depended on Database it would be imported by default.
(I think most of point 3 was covered in this)

I would prefer we don't split the project into subprojects but rather use this subspec/submodule approach. The reason I'm against creating multiple projects is I think that it can diminish support from the community and make components harder to find. I would like to keep everything in a centralized place.

I globally agree with you, I think we can go ahead and make adjustments with the PRs review!
About Carthage: it will simply compiles every shared frameworks schemes found in a xcworkspace / xcodeproj to generate a dedicated framework. Once that done, the user can choose which frameworks to add in its projects.

Second though: I'm wondering if we shouldn't do a feature release before starting this. Otherwise, let's keep make a temporary branch feature/modules where we can merge all the PRs and then releasing it in master when everything is ready to go.

I agree that would probably be the best approach 👍


Update schunk package name.

Need to check

[x] Multiple ros controller managers running (for WAM and neck) is ok
[x] Joint states are merged(?) correctly

Also need to update neck script.

Things seem to work now! Here's a quick summary of the decisions I made:

ROS doesn't like multiple /controller_managers (they listen to the root /controller_manager topic). My workaround is to push all the neck things into their own /schunk_robot namespace in launch/schunk_neck.launch. (It looks like I had to do different things to different nodes to make that change happen, and I'm not sure why. I'll investigate later.)
Since everything was pushed into the /schunk_robot namespace, the joint states are now published to /schunk_robot/joint_states. This doesn't work because ROS state publishers will only read from the root /joint_states topic. My workaround is to relay all messages from /schunk_robot/joint_states to /joint_states. This means that each message on /joint_states doesn't contain the whole joint state of the robot, but it looks like a thing that other people do.

@aditya-vk please review and let me know what you think!


Return the NBN locID for the provided address, following the addressSplitDetails if required.

This resolves 61% of the outstanding LocID in Somerville, VIC:

5967 total addresses
5019 resolved by first lookup (leaving 948)
578 resolved by second lookup (leaving 370)

YMMV

Are there a few dots on top of each other??

Some of the unknowns in this address are caused by "Blacks Camp Rd" being renamed to "Warwong Avenue" a couple of years ago

I think this is a reasonable compromise that makes a significant improvement


OpDecorateStringGOOGLE can only be used with decorations that take string arguments

To fix: #2253

Hey @sarahM0 this PR is left dangling. Please revisit it.


Create CONTRIBUTING.md

Description

Related Issue

Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[ ] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[ ] I've read the CODE_OF_CONDUCT.md document.
[ ] I've read the CONTRIBUTING.md guide.
[ ] I've updated the code style using make codestyle.
[ ] I've written tests for all new methods and classes that I created.
[ ] I've written the docstring in Google format for all the methods and classes that I used.

Awesome, thanks @jmsquare ! I let you merge 👍
For the topic on what issue tracker we should use to facilitate contribution, do you want to start a Github discussion?


plotting of ND wheel axis does not have expected output

The above should show a scan from 0 to 200 degrees, but instead only shows the first ~20 and also shows negative values which were not scanned.

oh, the labels for the ND wheels are both 0 and not indexed correctly, too.

Looks to me like it's plotting motor position in absolute, rather than corrected for zero position/factor


📚 Documentation: Clicking a button inside input refreshes the page

💭 Description
On elements/input-fields page, clicking a button inside the input field (i.e. to show/hide password, or copy text) causes a whole page refresh.
This happens because most of the input field examples are inside a form, so a button click submits the form by default. The issue would be resolved by setting type="button" on all of these buttons.
<form class="form u-width-full-line u-max-width-500">

      Label

        <input type="password" class="input-text" placeholder="Placeholder" />
        <button
          class="show-password-button"
          aria-label="show password"
          type="button"
        >

        </button>

    ...

</form>

I have a PR ready if all this sounds alright 😄
As for the Code of Conduct below, I'm getting a 404. This seems to be the correct link.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@mat2ja nice catch, thank you :+1:


Add cobertura goal back

Not sure if you explicitly need it?
Perhaps investgate further at a later date.

Change the spelling of "NucleusConfigurarion" - see comments
Add references to issues this fixes (Unless I am blind and they are here somewhere)

@kbristow you're blind 👀


Fix failing HadoopFS tests

Some of the Hadoop FileSystem contract tests are not passing and have been commented out.
Analyze the reason for the failures, and decide whether or not a fix in lakeFS HadoopFS is needed.
It's possible that some tests are not applicable to lakeFS, or that the tests needs to be adapted to lakeFS.
The list of failing tests:

In TestLakeFSFileSystemContract:

[ ] testWorkingDirectory
[x] testRenameFileMoveToNonExistentDirectory
[x] testListStatus
[x] testRenameDirectoryMoveToNonExistentDirectory
[x] testRenameFileAsExistingDirectory
[x] testListStatusThrowsExceptionForNonExistentFile
[x] testOverwrite
[x] testMkdirs
[x] testRenameFileAsExistingFile
[x] testRenameDirectoryAsExistingFile
[x] testRenameNonExistentPath

In TestLakeFSContractRename:

[x] testRenameNonexistentFile
[x] testRenameFileNonexistentDir

In TestLakeFSContractDelete:

[x] testDeleteDeepEmptyDir

In TestLakeFSContractCreate:

[x] testCreateFileOverExistingFileNoOverwrite

Fixing the contract was done by aligning the lakeFS file system with s3a v2.7 implementation for the above tests.


feature: add footer

add footer
click on Hasadna logo should go to hasadna home page

Use Anyway site as a reference. no need to add facebook / twitter buttons / icons

already merged


ERROR: failed to load locked problem!

Even I paid, it still shows ERROR: failed to load locked problem!

should be fixed in b08c4dfce10b586dae19402c1219cee20c912b55


Error while installing dependencies with esy

I got the following error when I run esy with the hello example:
 ~/gits/dream/example/1-hello | master !1 | esy                                                                                 1 ✘  16:19:43
info esy 0.6.12-dev (using esy.json)
info building @opam/easy-format@opam:1.3.3@f5b11eb6
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: @opam/easy-format@opam:1.3.3
    # esy-build-package: pwd: /home/davi/.esy/3/b/opam__s__easy_format-opam__c__1.3.3-97ae9c63
    # esy-build-package: running: 'dune' 'build' '-p' 'easy-format' '-j' '4' '--promote-install-files=false' '@install'
    # esy-build-package: running: 'dune' 'install' '-p' 'easy-format' '--create-install-files' 'easy-format'
    /usr/bin/opam var prefix > /tmp/dune_0dfee4_output
    [ERROR] Opam has not been initialised, please run `opam init'
    error: command failed: 'dune' 'install' '-p' 'easy-format' '--create-install-files' 'easy-format' (exited with 1)
    esy-build-package: exiting with errors above...

  building @opam/easy-format@opam:1.3.3
esy: exiting due to errors above

What is master !1 ?

Oh, it's from my zsh config. Just ignore 😅

I am unable to reproduce this locally right now. It looks like some kind of upstream error, probably in esy's repos, and it might have been fixed upstream. Have you observed this since?

I'm going to close this for lack of information/ability to reproduce it. I've also converted the OCaml-syntax examples to use opam as the recommended package manager.


The source release tar.gz configures vendored deps, but not .cargo/config

For example cargo-vendor-src-0.1.13.tar.gz from the releases page.
Inside the tar, we have all the source to cargo-vendor itself as well as vendored dependencies. However, if you fetch this tar and do a cargo build, it does not appear to use the vendored deps because .cargo/config is not set in that directory.
Looking at the .travis.yml, I think the pre-deploy step needs to set the .cargo/config.

This crate is now included natively in Cargo as of https://github.com/rust-lang/cargo/pull/6869 and today's nightly Rust. I'm closing all issues in this repository before I archive the repository, but if you're still interested in seeing this issue fixed then please feel free to file an issue with Cargo itself!


Custom log_configuration

Without having to overwrite the container definition, it would be nice to be able to use a custom log_configuration such as firelens to use fluentbit as a log distributor which is useful when moving logs to datadog.

hi @nitrocode - this functionality is available now with v2.21.0 per #144


Redirect to openwhisk.incubator.apache.org

After launch, we need to make this happen.

There are probably a few steps we need to consider, and will rely on @mrutkows and Felix from Adobe to guide us. Such as:

Procuring hosting resources/VM from Apache Foundation
Configuring those resources to host our static (or dynamic) files
Ensuring that openwhisk.org is a redirect rather than the explicit domain

Infrastructure already exists at Apache for this static hosting. It is a matter of just putting the files there. Currently there are two ways how to do this as documented on the project-site page at Apache.
I suggest in the immediate short term, once this new site is finalized, we do a manual upload of the site's content to the appropriate SVN location - just to have something up there.
We then work with Apache infra to see how

we can automate the site update directly out of GitHub and
infra can setup the redirects

Makes sense ?

This can be marked complete. @csantanapr?


Debugger:  Attach doesn't work correctly on Windows 8.1 x64 when the BP is set before debugging

Environment data
dotnet --info output:
VS Code version: 1.7.2
C# Extension version: v.1.6.0-beat3
.NET Core version: 1.0.0-preview2 -1 - 003177
OS: Windows 8.1 x64
Steps to reproduce

Open VSCode
Install C# Extension v.1.6.0-beta3
Delete all files in C:\Users.vscode\extensions\ms-vscode.csharp-.debugger except “install.complete”
Unzip the contents of the matching zip file into the C:\Users.vscode\extensions\ms-vscode.csharp-.debugger
Download hwapp folder in attachments directly and open with VSCode
hwapp.zip
Launch the project in Command Prompt using the command "dotnet run"
Select the debug type “.Net core Attach”
Set a BP at line of 13
Press F5 to start debugging
Select process ID on UI

Expected  behavior
This bp should be hit
Actual behavior
The bp can't be hit and show error message in debug console as following:
"ERROR: Unable to start debugging. Unexpected CLRDBG output from command "-interpreter-exec console "info sharedlibrary"". Undefined MI command: interpreter-exec
"
##Investigation:
This issue doesn't appear every time, but if steps 9 and 10 are executed first, then executed step 8, the bp can always be hit.

Sounds like an issue with the MI Engine...

May be... And this issue also happened on my machine with openSUSE 42.2 installed.

Similar issue on Rhel 7.

Similar issue on win7 x64 and win10 x64

This issue can repro on my Debian and CentOS.


fix: properly end goroutine in benchmark

PR Description
For loop used in the benchmark to discard messages was not properly terminated.
for {
	<-mbx.ReceiveC()
}
// <---- this is unreachable code

This loop will keep iterating because result from ReceiveC() was never checked.
Also, main benchmarks goroutine waits for receiver goroutine to finish.
Which issue(s) this PR fixes

Notes to the Reviewer
PR Checklist

[ ] CHANGELOG.md updated
[ ] Documentation added
[ ] Tests updated
[ ] Config converters updated

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ptodev hey, somebody needs to merge this because I am not contributor :)
thanks for review

Hi @vladopajic, thank you for the contribution and apologies for the late response! I forgot to merge it back when the CI completed :)


Unable to write into user settings because the file has unsaved changes. Please save the user settings file first and then try again.

Error: Unable to write into user settings because the file has unsaved changes. Please save the user settings file first and then try again.
at C.y in src/vs/workbench/services/configuration/common/configurationEditing.ts:347:10
at C.E in src/vs/workbench/services/configuration/common/configurationEditing.ts:554:15
at C.n in src/vs/workbench/services/configuration/common/configurationEditing.ts:177:14
at Object.factory in src/vs/workbench/services/configuration/common/configurationEditing.ts:166:16
at A.h in src/vs/base/common/async.ts:635:33
at <anonymous> in src/vs/base/common/async.ts:626:9
at new Promise (<anonymous>)
at A.queue in src/vs/base/common/async.ts:624:10
at C.writeConfiguration in src/vs/workbench/services/configuration/common/configurationEditing.ts:164:21
at z.Hb in src/vs/workbench/services/configuration/browser/configurationService.ts:1010:35
at async Promise.all (index 0)
at async Object.G [as settled] in src/vs/base/common/async.ts:1478:18
at async z.updateValue in src/vs/workbench/services/configuration/browser/configurationService.ts:358:3

Go to Errors Site

Needed the real caller of updateValue to know if it is really a bug or. not. I would not like to change it into No Telemetry error because it is a valid error and the caller has to handle it.

@sandy081 just to clarify, I am not suggesting to not have this error, just to not send it to our error telemetry so that we do not report these errors all the time as build champ. That means to extend ErrorNoTelemetry for example.

@bpasero Yeah, I understood that to use ErrorNoTelemetry, but doing so, this might cause not to catch valid issues for eg., if a feature (say settings editor) in core does not catch this and does not work because of this error. I would expect the callers to catch the error and handle it appropriately just like handling fs read/write errors.

We need more stacktrace that who called updateValue on configurationService, then we can know which feature/component is updating configuration and take an action accordingly.
I do not understand why there is no stack trace beyond updateValue

Maybe some async involved, I am not sure if stacktraces would continue over async automatically because there is probably perf overhead. I know in devtools when you have it open and debug, you get full support for them.
Maybe @connor4312 knows?

Yea, unless async stacks are enabled in the runtime (which comes with a notable performance penalty) then the stack will not include anything outside the current task's stack.


devServer proxy does not work as advertised

Version
3.0.0-beta.5
Reproduction link
https://github.com/Rayraegah/cli-error-axios
Steps to reproduce

Configure a proxy under devServer in vue.config.js (e.g. '/gists' : 'https://api.github.com')
Use Axios to send a POST (.e.g. axios.post('/gists/...'))
Use Axios to send a GET (.e.g. axios.get('/gists/...'))
Repeat using fetch instead of Axios (same errors)

What is expected?
The axios post request should be proxied to https://api.github.com like GET requests do. Sometimes the GET requests are not proxied.
What is actually happening?
The axios request goes to https://localhost:8080/gists/... instead of https://api.github.com/gists

The issue is the same as the one in create-react-app that was resolved recently.
refer: https://github.com/facebook/create-react-app/pull/3726 and https://github.com/facebook/create-react-app/issues/3311
On my main repo, GET requests were successful, only POST failed. But in the test repo - both GET and POST end in errors.

@yyx990803 Why close this issue? You haven't resolved this problem yet. I think a bug tag is better than closing this issue.

Just to clarify this was partially resolved in Beta-6 release. PUT and POST requests made via Axios are working but with fetch it is not.

@liyuanqiu https://help.github.com/articles/closing-issues-using-keywords/

@Rayraegah Has this problem been solved?


Camera rotation settings (RPiHQ)

Does the rotation setting in settings_RPiHQ.json only accept 0, 90, 180, 270? or do other values need to be in a specific format?
Example: when I mounted the camera on my roof it turns out it is 10 degrees off the meridian.  If I tell the camera to use rotation 180 it rotates the produced images to around as expected.  I changed the setting for rotation last night to rotation=190 and the images being produced are only showing a 10 degree rotation.

Reread the code for capture and it only accepts 0, 90, 180, 270
Closed


Simulation cannot run

Hi! I tried to run this model with my dataset, I have processed the price and news data as according to the structure given in the README file. I passed the files through 04_clean_data.ipynb, and then generate_all_data.py to get the env_data.pkl. Because I did not know how data/06_input/all_symbols.pkl is generated, I passed the env_data.pkl in the generate_test_data file to get data/06_input/subset_symbols.pkl which is later used in run.py.
However after these processing, I encountered some issues when running simulations.
Issue1:
Some issues are related to the config file: for example: from 'symbol=config["general"]["trading_symbol"]' -> throws error: KeyError: 'general'. I think the config file do not have some keys that were later used.
Issue2:
Regarding the eco files used, I can only find 5 of them online(AMTMNO,AWHAEMAN,CCI,M2SL,T10YFF), may I ask if the rest(ANDENO,ICSA,ISMNMDI,PERMIT) are also public information and how I could retrieve?
Issue3:
Regarding the ark_records_df, may I clarify that if the data is retrieved from the ark invest api: stock trades?
Issue4:
May I ask how the file 06_input/all_symbols.pkl is generated? Because I did not manage to locate the reference in the project.
Could you please advise on these issues? If possible, may I ask if you could release a version that can be run directly?
Thank you so much for addressing the issues.

For the issue 1:
Sorry about the confusion. We have two versions of the code that are supposed to run on single-stock trading and multiple-stock trading setups. Due to the API speed and budget limitation, we gave up the multiple stock cases, and that configuration file you saw previously was for that purpose. Please see the recent pull request for the updated config file(config.toml), as that is the correct format; we will soon refactor the others.
For the issue 2:
In general, you do not need those eco variables now. Our experiments found that the symbols often moved in the contributed direction with the market. However, the eco variables suggest a deteriorated condition(possibly due to inflation?). So, we stopped using them in our final paper, and those variables are deprecated. But in case you are curious, they are available at

ANDENO: https://fred.stlouisfed.org/series/ANDENO
PERMIT: https://fred.stlouisfed.org/series/PERMIT
ICSA: https://fred.stlouisfed.org/series/ICSA
ISMNMDI: https://ycharts.com/indicators/us_ism_non_manufacturing_suppliers_deliveries_index#:~:text=US ISM Services Supplier Deliveries Index is at a current,16.78%25 from one year ago.

For Issue 3:
Again, this is a deprecated feature. We tried to let the system align with the traders' opinions. But as we start from a zero position, and the institution may have already established a position before, the trading targets do not necessarily align. The initial records are retrieved from a Chinese website that records all history trading records: https://ark.alien-tomato.com/

For the issue 4, there was a mistake on file naming, in file 'process_raw_data/generate_all_data_sub2.py',
the file name in line 24 has been corrected to './data/06_input/all_symbols.pkl'.
Through the python files of  'process_raw_data/generate_all_data.py' and  'process_raw_data/generate_all_data_sub2.py', you can get data file 'all_symbols.pkl'

No activity.
Feel Free to reopen if needed.


server time out error

not able to login to server time out error

@JuanOrellana Do you connect to the server fine using another ftp client like Filezilla?

never mind it is working now fine
On Wed, Sep 28, 2016 at 3:46 PM, jimmaaay<EMAIL_ADDRESS>wrote:

@JuanOrellana https://github.com/JuanOrellana Do you connect to the
server fine using another ftp client like Filezilla?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mgrenier/remote-ftp/issues/483#issuecomment-250278705,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqRO4fiITcPh4lZ18IRDDYaxg0u9zzKks5qusQKgaJpZM4KJBqm
.


fix(LLC/BTC): Cardinality error new text

📝 Description
Didn’t manage to add translation to this error. It’s generated in code which is outside our scope.
Temporary fix : replaced the string with the provided one. No links possible if a custom error is not properly created.
❓ Context

JIRA or GitHub link:  LIVE-10325 LIVE-10326

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@mle-gall Do you think we could reopen this PR ?


Handle exception in helpers

If any exception occurred , nothing returns by setting function. With this changes, the setting function returns default value if any exception occurred.

That's not the purpose of the helper so can't accept it.


remove empty package lock in root

What does this change?
Removing the empty package lock from root since it's causing snyk to fail

Hey! I got there first 🤣 https://github.com/guardian/giant/pull/140

Hey! I got there first 🤣 #140

hahaa, yours has already finish building, lets merge that one 🤣


Screensharing

This PR implements the following:

/screenshare
/close
/freeze
/unfreeze

Closes: #25
Edit: if this is merge I am going to close linked issue, since I'm going to work down the list, then merge this and close it

Why did you merge master? I cannot push my stuff right now. I'm resetting it, changing what you told me to do, then we can start testing and merge.

I think I broke something

Oops

It's fine. I'm rebasing. Then we can easily fast-forward everything.

ok ty

I think my API key for Hypixel is invalid. That way the test failed.

Ah I see

probably shouldn't just have the api key there like that


Failed extraction from blogger post

gg = goose.Goose()
gg.extract(url='http://elelibro.blogspot.com/2017/01/il-potere-morbido-della-lingua-italiana.html').cleaned_text

Result is empty unicode string. Expected is the body of that blog post. Since it's hosted on blogger, I suspect other blogger blogs may be affected. Setting the language manually doesn't change the output, or fetching the raw html first  via requests.

You can accomplish that by doing something like the following:
goose = Goose()
goose.config.known_context_patterns.append({'attr': 'class', 'value': 'post-outer'})
article = goose.extract('http://elelibro.blogspot.com/2017/01/il-potere-morbido-della-lingua-italiana.html')
print(article.cleaned_text)

Goose uses a few default tags to find the content of the article. If it doesn't pull the article, it is likely that the id/class needed is not a standard class or id. I found this by inspecting the site and finding that the main article was wrapped in a div with class=post-outer. I hope this is helpful!


⚠ Bofrost.at has degraded performance

In 3671200, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1407 ms

Resolved: Bofrost.at performance has improved in ee4ed7e.


Workspaces: All crates below the root folder must be members of the workspace

The workspace documentation says the following:

The package.workspace manifest key (described above) is used in member crates to point at a workspace's root crate. If this key is omitted then it is inferred to be the first crate whose manifest contains [workspace] upwards in the filesystem.

(emphasis mine)
This implies that all crates below the workspace root must be part of the workspace, even if there are no dependencies on them.
For example, imagine the following workspace layout.
…
├── Cargo.toml
├── src
├── sub1
│   ├── Cargo.toml
│   └── src
└── sub2
    ├── Cargo.toml
    └── src

The root Cargo.toml defines a workpace with member sub1:
[package]
# …

[workspace]
members = ["sub1"]

# no dependencies

Now we can build the root project and sub1 without problems. But when we try to build sub2, the following error occurs:
> cargo build
error: current package believes it's in a workspace when it's not:
current:   /home/…/test/sub2/Cargo.toml
workspace: /home/…/test/Cargo.toml

this may be fixable by adding `sub2` to the `workspace.members` array of the manifest located at: /home/…/test/Cargo.toml

So sub2 blindly assumes that it's part of the workspace, even though it's not part of workspace.members.

Real World Example: Imagine working with git worktree. This command allows you to temporary check out a branch in a subfolder. For example, you might want to do a quick bugfix on master while working on a feature branch (let's say that you want to introduce cargo workspaces in your project).
So you check out the master branch in a bugfix subfolder. The you cd into it and try to build it. But it fails with the same error as above because your crate now thinks that it's part of the root workspace.

This is indeed correct! Unfortunately I'm not sure there's a lot we can do about this... We can perhaps add workspace = false in addition to workspace = "..." to allow an explicit opt-out of a workspace, but I figure that if you have to modify Cargo.toml you may as well hook it up to the workspace.
cc @rust-lang/tools

@alexcrichton I think that the explicit opt-out should be in the "root" crate, instead of the Cargo.toml of a dependency. Perhaps have a workspace key for each dependency that defaults to true?  This would make testing crates locally, as seems to be the main issue, require no change in the crate itself which would simplify things greatly.

@4e554c4c hm yeah that sounds reasonable, some form of configuration in the workspace root indicating "please don't include this area"

To clarify: This problem even occurs when there is no dependency on sub2 at all. The root crate doesn't even know about sub2. But sub2 thinks that it's part of the workspace because there is a [workspace] section in a crate upwards the file system.
An opt-out in the root crate wouldn't really solve this problem, since sub2 is not even mentioned in the Cargo.toml of the root crate. A better solution would be: Not only look for a workspace root upwards in the file system, but for a workspace root that contains the current crate.
Alternatively, the proposed workspace = false would make sense to me. Then at least we could fix it without modifying other (completely unrelated) crates.

@phil-opp isn't the workspace root here though aware of the filesystem layout? Enough to know to reject the directory with sub2?

A better solution would be: Not only look for a workspace root upwards in the file system, but for a workspace root that contains the current crate.

Unfortunately this can wreak havoc with lock files. One of the crucial properties of a workspace is that all members agree on the set of crates in a workspace. If disagreement were allowed then this could cause Cargo.lock files to oscillate depending on which crate you compile as Cargo wouldn't always know what to resolve.

isn't the workspace root here though aware of the filesystem layout? Enough to know to reject the directory with sub2?

I don't know how it's implemented. I thought that the root crate only scans its members and (transitive) path dependencies. The sub2 crate is neither.

One of the crucial properties of a workspace is that all members agree on the set of crates in a workspace.

All members agree that sub2 isn't part of the workspace.
The problem is that we can't compile sub2:
error: current package believes it's in a workspace when it's not:
…

This error message is strange. The sub2 crate “believes it's in a workspace”, but at the same time it knows that “it's not”. Couldn't we just compile the crate without throwing this error (since we're sure that the crate is not part of the workspace)?

Ah so the problem here is that sub2 does indeed think it's in a workspace. The logic for finding your workspace is to either look at package.workspace or walk up the filesystem looking for [workspace]. Because sub2 lacks a package.workspace it's walking up the filesystem and finding another crate. In that sense, not all members agree because sub2 thinks it's a member.
The change I'm thinking of here is that the workspace itself says "this path is excluded" so if the "walk up" logic walks along that path then it just aborts and says there's no workspace.

I've got an idea for a motification to workspaces which I believe fixes this. If you're interested in this issue and that doesn't work for you though please let me know!

I believe with the exclude key this is no longer an issue, so closing.


Add GitHub Actions

What's the intent? To replace azure-pipelines with GH actions? We could use Cirrus instead, because all 4 OSes can run on it.

I'm fine with either, I did this in response to https://github.com/tokio-rs/mio/issues/1444#issuecomment-1189212858. Azure pipelines isn't used as much I think (based on personal experience alone).

I'd prefer GitHub actions for now, as it's much easier to maintain and deal with.

@Thomasdezeeuw I'll much about with this.


Update sql-database-upgrade-new-service-tiers.md

Adding the link to pricing tier recommendations in the beginning of the article.

Hi @VeljkoVasic, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Fix clean make command

Closes https://github.com/plone/volto/pull/6403

[ ] I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
[ ] I verified there aren't other open pull requests for the same change.
[ ] I followed the guidelines in Contributing to Volto.
[ ] I succesfully ran code linting checks on my changes locally.
[ ] I succesfully ran unit tests on my changes locally.
[ ] I succesfully ran acceptance tests on my changes locally.
[ ] If needed, I added new tests for my changes.
[ ] If needed, I added documentation for my changes, either in the Storybook or narrative documentation.
[ ] I included a change log entry in my commits.

copied from PR:
Tested locally with the branch: the files are now kept.
When running make, it still shows warnings that it cannot find node_modules with the find, which is strange and exits with an error code . Running make clean a second time and the clean finishes ok.
Another thing  while testing the issue with make clean. When I do a clean checkout from the the plone/volto repo and do a make install, is it normal that the pnpm-lock.yaml be changed right away compared to git?  I updated to the latest pnpm .  AFAIK  KGS is KGS, or can this happen anytime with pnpm that is finds newer minor versions within the ranges specified for packages?
Studio1:volto fred$ make clean
find: ./packages/blocks/node_modules: No such file or directory
find: ./packages/generator-volto/node_modules: No such file or directory
find: ./packages/types/node_modules: No such file or directory
find: ./packages/volto-slate/node_modules: No such file or directory
find: ./packages/coresandbox/node_modules: No such file or directory
find: ./packages/providers/node_modules: No such file or directory
find: ./packages/volto-testing/node_modules: No such file or directory
find: ./packages/volto/node_modules: No such file or directory
find: ./packages/components/node_modules: No such file or directory
find: ./packages/scripts/node_modules: No such file or directory
find: ./packages/registry/node_modules: No such file or directory
find: ./packages/slots/node_modules: No such file or directory
find: ./packages/client/node_modules: No such file or directory
find: ./packages/helpers/node_modules: No such file or directory
make: *** [clean] Error 1
Studio1:volto fred$ make clean

pnpm-lock.yaml changes:
git-diff-output.log

@fredvd I haven't tried the command, but I tried the find and it did work, no clue why it's complaining.
Regarding the pnpm changes, sometimes if someone changes the metadata of a package during a minor, etc, the lock changes. However, it's only metadata too.
Remember to install pnpm always using corepack, no local manual installation.


Assistant message generation error

Hi, which model are you using?

I have the same error when i integrate model with litellm: https://litellm.ai/

I think this error might have occurred due to selecting the wrong type when choosing a custom host model. Because currently, some LLMs use the 'tool_calls' mode for utility invocation, while others use 'function_call'. Did you select the correct type when creating your custom host model?


Helmfile doesnt error if helm-secrets fail

Operating system
Ubuntu 24.04
Helmfile Version
0.165.0
Helm Version
v3.14.4
Bug description
Its an rather old issue (see link) but still open.
I use helm secrets Plugin and vals with hashicorp vault urls.
If the URL is incorrect and the secret isn't found, helmfile however renders ok or fails when the yaml is invalid and the yaml to json conversion fails.
All tools (helm / vals / helm secrets)  report invalid secrets as an error and I also checked the correct returncode (0: ok / 1: not found)
Example helmfile.yaml
just use a secret url in a values file, eg:
value: ref+vault://an/invalid/vault/secret
Error message you've seen (if any)
No error. The missing secret renders to an empty string.
An error is expected though.
Steps to reproduce
just template -- will try to build a static demo project
Working Helmfile Version
no working
Relevant discussion
https://github.com/roboll/helmfile/issues/1163

While I was trying to reproduce this issue in a small static environment (helmfile, static values.yaml) it was working as expected.
It is however still not working in my complex environment, will try to dig for the root cause.

@reimerp thanks so much. great to have an demo to debug that. I will fix this try my best.

any debug logs?

Sorry took me a while to debug / demo this, since its just occurring when you use vault fragments. I don't know if other secret providers offer this feature buts its very convenient to group related secrets in one location, eg:
a user "admin" has a "token" and a "password", or a tls cert has a key, a root pem and a pem file which can only exist together.
In the demo I used the prometheus-community/prometheus chart as in the demo and added a imagePull secret.
The referenced working secret is "ref+vault://some/path/prom#imagepull"
The Readme in that demo shows the usage.
https://github.com/reimerp/vault-fragment-issue

closed by mistake


Questions about JOS 3 development

Hello,
Thanks a lot for your previous help.
As I mentioned in an e-mail, I want to use the JOS 3 model and for that I try to understand it. So, I have several questions about the construction of the model:

The set point temperature is the "the body temperature of the model that does not have a thermoregulation system". What about the AVA blood flow in this passive model? Is Oava equal to 0.9126 as the equation (49) at the thermal equilibrium let it suppose or to 0? In the python code, it seems equal to 0 but I'm not sure to understand why?
How did you choose the number of iterations for the initialization?
I see some value differences between your article and the python code. Especially, the thermal capacity of the pelvis core is equal to 13.834 Wh/K in the python code and to 16.119kJ/K = 4.478Wh/K. Which value is correct ? How did you determine these capacity values?
Same question for the conductance ms-fat in the pelvis : is it 0.3738 W/K or 10.37 W/K?
The parameter "posture" have an effect on the convective and radiative coefficients. Does it take into account the contact with a chair for the sitting posture or with a bed or the floor for the lying posture?

Can you help me with that ?
Thank you very much again,

Thanks a lot for your update. I'm looking forward to having your answers to my questions. It will be really useful for me and my PhD project.
Célia Sondaz

Hello,
Sorry to bother you again. Do you have time to help me and to answer my questions?
Thank you for your help.
Célia Sondaz

The value differences that you pointed out are currently under investigation. Please wait for a while. Sorry for this inconvenience...

Dear Celia Sondaz
I'm so sorry for the late reply.

The set point temperature is the "the body temperature of the model that does not have a thermoregulation system". What about the AVA blood flow in this passive model? Is Oava equal to 0.9126 as the equation (49) at the thermal equilibrium let it suppose or to 0? In the python code, it seems equal to 0 but I'm not sure to understand why?

In this passive model, the AVA blood flow rate is set to 0. As you indicated, it is not 0 in thermo-neutral. I will think about validity of it in the future model.

How did you choose the number of iterations for the initialization?

By confirming the parameters have become stable.

I see some value differences between your article and the python code. Especially, the thermal capacity of the pelvis core is equal to 13.834 Wh/K in the python code and to 16.119kJ/K = 4.478Wh/K. Which value is correct ? How did you determine these capacity values?
Same question for the conductance ms-fat in the pelvis : is it 0.3738 W/K or 10.37 W/K?

Thank you for finding my mistakes. I revised the code in ver.0.3.2.

The parameter "posture" have an effect on the convective and radiative coefficients. Does it take into account the contact with a chair for the sitting posture or with a bed or the floor for the lying posture?

No it doesn't. The elder model had it. Adding the effect of the contact surface is a future work.

Dear Yoshito,
Thank you very much for your answer, the checking and the version 0.3.2.
I'm really interested by the AVA issue, so please let me know if you have any update about it. I will probably do some research on this topic on my side. I will keep you posted.
Thanks a lot

Has anyone got the answer? I agree with CeliaSondaz's suggestion. It seems that "err_bcr" and "err_msk" are reversed, and "0.97" is incorrect. In addition, if "cap_bcr" refers to the capacity ratio for weighting, then I think the values [37.071, 33.817, 16.119] should be transformed to [10.2975, 9.3935, 4.477].
Has the person responsible or the supervisor checked the content? Were the same codes used for the results in the paper of Energy & Buildings?
Is he an author in below?
https://jp.linkedin.com/in/yoshito-takahashi-b77312161
Another paper for JOS-3 mentions only 83 nodes (Plevis doesn't have muscle and fat).

Sorry for the late reply.
I have been very busy at work.
I fixed the function calculating AVA blood flow.
Could you check the branch jos3-dev-0.4.1 ?
Your modifications at line 370 and 371 is also correct, but I think these core temperature values are low, so, I leave them as original.
The same codes used for the paper are here.
https://github.com/TanabeLab/JOS-3/releases/tag/v0.3.1
It is correct that the nodes of JOS-3 have 85 nodes.
I'm sorry to have you confused.

Dear Yoshito Takahashi and Akihisa Nomoto,
I've noticed a potential issue in your paper.
In equations (40) and (41), you've used symbols "Â" and "Mnshiv"
which do not appear in the "Symbols" section of your paper.
I believe "Â" might be a garbled character, and "Mnshiv" might be intended to be "Mnst."
Could you kindly clarify and confirm this?
Additionally, it seems that "Mnst" is not utilized in the provided Python code.
for i, bn in enumerate(BODY_NAMES):
# If the segment has a muscle layer, muscle blood flow increases.
if not IDICT[bn]["muscle"] is None:
bf_ms[i] += (mwork[i] + mshiv[i])/1.163
# In other segments, core blood flow increase, instead of muscle blood flow.
else:
bf_cr[i] += (mwork[i] + mshiv[i])/1.163
return bf_cr, bf_ms, bf_fat
Thank you for your attention to this matter.
Sincerely,

Hi.
Thank you for pointing it out.
I will check it out.
Regards
(@AkihisaNomoto

@suteacsute
Hi.
Sorry for the delay in replying. As you pointed out, the letters are garbled, and the character dot, meaning "multiply," is correct. It seems to have been converted during the proofreading stage.
Also, for the BF formula, it is difficult to answer it. This is because non-shivering thermogenesis does not involve activity and may not lead to an increase in blood flow. Since I cannot conclude this matter at this time, I leave the python code as it is. I added the comment about it in read.me.

Thank you very much for checking and pointing this out.

@CeliaSondaz
It is difficult to conclude it is correct.
However, some studies reported that changes in activity level and thermal environment cause transient fluctuations in core temperature.
Sorry I could not find the English paper and the below is written in Japanese.
https://www.jstage.jst.go.jp/article/aije/71/609/71_KJ00004391587/_pdf/-char/ja

時間 means time
深部温度 means rectal temperature
椅座安静 means sitting
踏み台昇降 means repeat step up and down
The following study reports a temporary decrease in rectal temperature upon moving to a hot environment and initiating exercise.
It is thought that this is brought about by a sudden change in activity level or environment.
To prevent this phenomeno
The following study reports a temporary decrease in rectal temperature upon moving to a hot environment and initiating exercise.
It is thought that this is brought about by a sudden change in activity level or environment.
To prevent this phenomenon, it would be better to change PAR gradually.
Thank you.


I was told to talk about this 500 error

I had been logged in automatically from a cookie and then I changed my language to python and clicked train and got this message.
Good luck!
No route matches kata/577a98a6ae28071780000989/train/train

Closing as duplicate of #596


Added Tests for Json Serialization and Deserialization

Added Tests #6 around StringToIntJsonConverter and StringToLongJsonConverter used in Integrations.IdentityServices.AzureActiveDirectory

Hey @renato-marciano, thanks for contributing!
All code files in this project must contain a standard header. For .cs files, this is:
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT license.

Can you please re-commit your new file with this header? Thanks!

Yep, Added.


[Feature Request] Full SSR support

Right now the only proper way of using this lib with SSR is to wrap it in  tag. But is it possible to implement a full SSR support so images would also properly render to SSR? The issue that exists right now is that if  is omitted sometimes intersection observer is not triggered after initial load and images appear hidden although they are already within a viewport

Do you think it would be fixed by #78? Or there would be other things take into consideration?


Remove dependency on github.com/calyptia/go-bubble-table by creating a custom table model

The changes in #61 are causing some weirdness in the table headers and relying on a third-party table model is probably not the best idea here - especially as it seems to be lightly maintained. Creating a custom, generic table model for buoy's use case is likely a better path and more maintainable in the long run.

Another potential option is replacing with https://github.com/Evertras/bubble-table - seems to be more maintained


Set IME's window position on TextInput

Before

After

I've created a very early implementation for setting IME's window position on TextInput which works only on Windows.
Currently, I extended the Clipboard struct also handles the Input Method to avoid large diff. And set IME's window position in the on_event method.
TODO

[ ] Rename Clipboard and make also have responsibility of Input Method, or Separate struct and pass Clipboard and InputMethod to on_event arguments. Do you think which is better?
[x] Separate codes related to Input Method to another crate, like window_clipboard . I've found that winit has the method for this situation.
[x] Support MacOS
[x] Support Linux

To follow the master branch, I've decided to create a new crate window_ime that handles IME features like window_clipboard to avoid borrow-checker error.
You can check the status of my progress on https://github.com/hatoo/iced/tree/integrate_window_ime and it works only in Windows now.
Any support for window_ime is appreciated.

Finally, I've successfully merged the master branch with a minimum interface change.

for winit windows to handle xim input method, i think this PR can be referenced
https://github.com/alacritty/alacritty/pull/691


Error after install react-navigation package with npm

Current Behavior
I created a new project in create-react-native-app. Next, I was install react-navigation: npm install --save react-navigation.
When I run: yarn start in the terminal, appear this error:
yarn start v0.24.5
$ react-native-scripts start
sh: 1: react-native-scripts: not found
error Command failed with exit code 127.
I created again another app and next I was install react-navigation with yarn and next yarn start and the error not appear. I believe error appear when react-navigation is installed with npm.
Your Environment

software
version

react-navigation
1.0.0-beta.11

react-native
0.44.0

node
7.10.0

npm or yarn
npm 5.0.3 - yarn 0.24.5

linux
Linux Mint 18.1 64bits

run 'npm install -g react-native-sripts'  and then try again.

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!

am also stuck at this point, some one help me out!


Update docs for working with Hadoop dependencies.

Attempt to make things clearer in general
Point out that HDFS deep storage and MR jobs don't use the same loading mechanism
Recommend using mapreduce.job.classloader = true when possible

Related to discussion in #3222.

👍

👍


Change typeface

Is there any way to change the typeface and set a custom font type?

Technically it is possible using SpannableStringBuilder. Check this for more details.


Nested Ember Engines

Hi Ember masters.
Now I am using Ember-engines, which seem to be really powerful and amazing.
There is one question I want to ask. Is there an Ember generator to generate nested engines?
For examples I have ‘sportsbook-engine’ in my app and now I want to create sub-engines ‘sportsbook-live’ and ‘sportsbook-prematch’.
Please suggest me the right way to do that.
Thanks

Here is an example of nested engines. But I'm not sure is this right way.
https://github.com/Vazgen7788/ember-nested-engines-experiment

Have you gone through the guides? http://ember-engines.com/guide
There are instructions for creating engines as addons (standalone or in-repo).
Routable engines can be nested inside apps or other routable engines.
Route-less engines can be nested inside templates in apps or engines.
Please review the guides and raise issues if you have specific problems. Please ask questions in the #ember-engines channel of community slack.


Add spanish translation for-The-b-foundation

Thank you, I have moved to the archive.

Hello @adamjonas, Is the file in the wrong place?
Thanks!!

Looks like the right place but has the wrong title still

Hello, The _index.en.md file is in the baltic-honeybadger directory.