Wrong inverse intrinsics from O3D305 with ifm3d 1.4.1, C++

Hi,
with the following code I get strage inverse intrinsics from O3D305 camera
const auto& buffer = img->GetBuffer(ifm3d::buffer_id::INVERSE_INTRINSIC_CALIBRATION);
int width = buffer.width();
int height = buffer.height();
std::vector<double> intr(width*height/sizeof(double), 0.0);
std::memcpy(intr.data(), buffer.ptr(0), width*height);

result:
[0]: 3.9123517191159456e+17
[1]:<PHONE_NUMBER>49330.25
[2]: -2.7037003746954724e-06
[3]: -8.7463578209951619e-14
[4]: 0
[5]: 0
[6]: 1.6049665430689486e-314
[7]: -3.058777675590818e-10
did you change something compared to older versions < 1.0 of ifm3d or am I doing something wrong?
Thanks

Hi @REB427,
What firmware version are you using on your O3D305?

Hi @REB427,
with the new version all intrinsic values are exposed instead of just the translations and rotations.
You should be able to access the values using the deserialize module like this:
#include <ifm3d/deserialize/deserialize_o3d_buffers.hpp>

auto inv_intrinsics = ifm3d::O3DInstrinsicCalibration::Deserialize(buffer);

float trans_x = inv_intrinsics[ifm3d::intrinsic_param::TRANS_X];
float trans_y = inv_intrinsics[ifm3d::intrinsic_param::TRANS_Y];
float trans_z = inv_intrinsics[ifm3d::intrinsic_param::TRANS_Z];
float rot_x = inv_intrinsics[ifm3d::intrinsic_param::ROT_X];
float rot_y = inv_intrinsics[ifm3d::intrinsic_param::ROT_Y];
float rot_z = inv_intrinsics[ifm3d::intrinsic_param::ROT_Z];

That solved the problem, thanks.
Also figured out that my code from above is working when changing double to float.
In older ifm3d versions the intrinsics were double


Cannot access root path anymore with directoryBrowser

I used to be able to browse the root path of directoryBrowser, but now I can't.
If I access "http://localhost:8080:/files/images" it works, but if I try to access "http://localhost:8080:/files" it doesn't work anymore.
I don't remember what version of Swifter I was using when it worked, but now it is the 1.4.7.
This is what I had:
server["/files/:path"] = directoryBrowser(FileUtils.documentsDirectory.path)

Now I have to declare another route "/files" and create a 2nd version of directoryBrowser without the guard at the beginning.
server["/files/:path"] = directoryBrowser(FileUtils.documentsDirectory.path)
server["/files"] = directoryBrowserFixed(FileUtils.documentsDirectory.path)

public func directoryBrowserFixed(_ dir: String) -> ((HttpRequest) -> HttpResponse) {
        return { request in
            // workaround
            let (_, value) = request.params.first ?? ("", "")

//            guard let (_, value) = request.params.first else {
//                return HttpResponse.notFound
//            }
            let filePath = dir + String.pathSeparator + value
...

Hey, @pakerwreah Thanks for reporting this. Unfortunately this behavior has changed as definition of routes like /files/:path was returning incorrect results treating :path as a wildcard and causing more problems in the resolution of several routes, see the discussion in #405 for more information.
But if what are you looking for is list a directory you can do it easily but in another way. For example, if you go to the DemoServer.swift the file you will see we are using the following line of code:
server["/files/:path"] = directoryBrowser("/")

If you replace it instead with the following line:
server["/files/:path"] = directoryBrowser(publicDir)

Note:
publicDir is equal to String.File.currentWorkingDirectory()

And then you use the . to enter the directory like this route http://localhost:9080/files/. it should list the directory successfully:
.
..
logo.png
Swifter.framework
SwifterSampleOSX
SwifterSampleOSX.swiftmodule

Please note the browsers use a cache, etc so to test the routes you should make the request using Postman, Paw, curl in terminal or another tool you want.

It works if I type:
curl -v --path-as-is http://localhost:8080/files/.
But unfortunately it's not very useful that way.

@pakerwreah Can you more specific please about the how are you using the directoryBrowser specifically? Why is not very useful using the . sequence?

I use directoryBrowser to explore and download files from my iOS app documents folder. My database file for example is at the root folder.
This functionality is also used by my test team. It's not very productive to tell them to open a terminal and use curl.
If you type .../files/. on the web browser it automatically normalizes the path to .../files, the same way as curl, but using curl we can pass this flag --path-as-is so it won't change the path and it works.
ps.: files without extension are also not downloading anymore.

Swifter is still very useful for me because I've built a SQL console with it to query my app's database directly. I've also made a network interceptor using websocket. But as for browsing files, maybe I should search for a FTP server.

@pakerwreah I understand your use now, thanks for sharing it. I think the topic of the wildcard to match all the routes in #405  would help you and solve your problem. Unfortunately, I cannot promise a deadline for when it would come. I would do my best to try to integrate it soon, maybe somebody else can come with a solution, let's see...


NiFI-3064 convert to Avro fails when a MySQL query returns two columns…

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
… with the same name even with different aliases

I can't change it, but your PR title should be NIFI-3064 instead of NIFI-3604.

+1 LGTM, Ran the unit tests and tested with MySQL, Postgres, Oracle, verified the issue occurs without aliases and does not occur when column aliases are used.


Fastlane Deliver Unexpected error

New Issue Checklist

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

Issue Description
Unexpected Error when uploading metadata to ITC.
Had the same error 12 hours ago. (playing the waiting game did not solve the problem)
ITC is/was online according to apple
Uploading for testflight works completely fine.
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

[INSERT OUTPUT HERE]
---iMac:-- --$ bundle exec fastlane deliver --force
[15:01:17]: Successfully loaded '/Users/--/Documents/--/fastlane/Deliverfile' 📄
+-----------------------+-----------------------+
| Detected Values from './fastlane/Deliverfile' |
+-----------------------+-----------------------+
| app_identifier        | --.--            |
| username              |<EMAIL_ADDRESS>      |
+-----------------------+-----------------------+
[15:01:17]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false
[15:01:17]: Login to iTunes Connect<EMAIL_ADDRESS>[15:01:19]: Login successful
+--------------------------------------+------------------------+
|                    deliver 2.59.0 Summary                     |
+--------------------------------------+------------------------+
| force                                | true                   |
| app_identifier                       | --.--             |
| username                             |<EMAIL_ADDRESS>       |
| screenshots_path                     | ./fastlane/screenshots |
| metadata_path                        | ./fastlane/metadata    |
| app_version                          | 1.0.0                  |
| edit_live                            | false                  |
| ipa                                  | --.ipa             |
| platform                             | ios                    |
| skip_binary_upload                   | false                  |
| skip_screenshots                     | false                  |
| skip_metadata                        | false                  |
| skip_app_version_update              | false                  |
| submit_for_review                    | false                  |
| automatic_release                    | false                  |
| dev_portal_team_id                   | --             |
| overwrite_screenshots                | false                  |
| run_precheck_before_submit           | true                   |
| precheck_default_rule_level          | warn                   |
| ignore_language_directory_validation | false                  |
+--------------------------------------+------------------------+
[15:01:20]: Making sure the latest version on iTunes Connect matches '1.0.0' from the ipa file...
[15:01:21]: '1.0.0' is the latest version on iTunes Connect
[15:01:21]: Framed screenshots are detected! 🖼 Non-framed screenshot files may be skipped. 🏃
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-1_Agenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-2_DetailAgenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-3_NewHour.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-4_TaskView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-5_ClientView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 5-6_SettingsView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-1_Agenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-2_DetailAgenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-3_NewHour.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-4_TaskView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-5_ClientView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6 Plus-6_SettingsView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-1_Agenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-2_DetailAgenda.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-3_NewHour.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-4_TaskView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-5_ClientView.png
[15:01:21]: 🏃 Skipping screenshot file: ./fastlane/screenshots/nl-NL/iPhone 6-6_SettingsView.png
[15:01:21]: Loading './fastlane/metadata/nl-NL/description.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/keywords.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/release_notes.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/support_url.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/marketing_url.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/promotional_text.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/name.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/subtitle.txt'...
[15:01:21]: Loading './fastlane/metadata/nl-NL/privacy_url.txt'...
[15:01:21]: Loading './fastlane/metadata/copyright.txt'...
[15:01:21]: Loading './fastlane/metadata/primary_category.txt'...
[15:01:21]: Loading './fastlane/metadata/secondary_category.txt'...
[15:01:21]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[15:01:21]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[15:01:21]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[15:01:21]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/trade_name.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/address_line1.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/city_name.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/country.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/postal_code.txt'...
[15:01:21]: Loading './fastlane/metadata/trade_representative_contact_information/is_displayed_on_app_store.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/first_name.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/last_name.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/phone_number.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/email_address.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/demo_user.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/demo_password.txt'...
[15:01:21]: Loading './fastlane/metadata/review_information/notes.txt'...
[15:01:23]: Activating language nl-NL...
[15:01:25]: Uploading metadata to iTunes Connect
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 5)...
Potential server error received: 'Unexpected Error'. Retrying after 10 seconds (remaining: 5)...
Looking for related GitHub issues on fastlane/fastlane...
➡  Unexpected Error when submitting the app for review
https://github.com/fastlane/fastlane/issues/8819 [closed] 4 💬
5 weeks ago
➡  pilot without skip_waiting:true appears to be broken(?)
https://github.com/fastlane/fastlane/issues/8867 [closed] 13 💬
4 weeks ago
➡  Deliver: Unexpected Error when selecting build
https://github.com/fastlane/fastlane/issues/7757 [closed] 3 💬
06 Apr 2017
and 10 more at: https://github.com/fastlane/fastlane/search?q=The request could not be completed because:
	Unexpected Error&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
[!] The request could not be completed because:
Unexpected Error
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
[INSERT OUTPUT HERE]
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.4.1

Bundler?
true

Git
git version 2.13.5 (Apple Git-94)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

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
9.0

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

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.47.0"

default_platform :ios

platform :ios do
  before_all do
    ENV["SLACK_URL"] = "--"
    cocoapods

    FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD="--"

  end

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

  # 1
  desc "Creating a code signing certificate and provisioning profile"
  # 2
  lane :provision do
    # 3
    produce(
      app_name: '--',
      language: '--',
      app_version: '--',
      sku: '--'
    )
    # 4
    cert
    # 5
    sigh(force: true)
  end

  desc "Take screenshots"
  lane :snapshot_f do
    snapshot
    frameit(white: true)
  end

  desc "increment build"
  lane :inc_build do
    increment_build_number
  end

  desc "increment patch"
  lane :inc_patch do
    increment_version_number(
      bump_type: "patch"
    )
  end

  desc "increment minor"
  lane :inc_minor do
    increment_version_number(
      bump_type: "minor"
    )
  end

  desc "increment major"
  lane :inc_major do
    increment_version_number(
      bump_type: "major"
    )
  end

  desc "Create ipa"
  lane :build do
    gym(scheme: "--",
      workspace: "--.xcworkspace",
      include_bitcode: true)
  end

  desc "Upload to App Store"
  lane :upload_appstore do
    deliver
  end

  desc "Upload to TestFlight"
  lane :upload_testflight do
    pilot
  end

  desc "Upload metadata"
  lane :upload_metadata do
    deliver(metadata_only: true)
  end

  desc "Upload sentry"
  lane :upload_symbols do
  download_dsyms
  sentry_upload_dsym(
    auth_token: '--',
    org_slug: '--',
    project_slug: '--'
  )
  end

  desc "Provision, take screenshots, build and upload to testflight"
  lane :all_testflight do
    provision
    # screenshot
    inc_build
    build
    upload_testflight
    upload_symbols
    clean_build_artifacts

    slack(
      message: "Successfully deployed testflight!"
    )

  end

  desc "Provision, take screenshots, build and upload to App Store"
  lane :all_appstore do
    provision
    # screenshot
    build
    upload_appstore
    upload_symbols
    clean_build_artifacts

    slack(
      message: "Successfully deployed new app update to the App Store!"
    )

  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 "--" # The bundle identifier of your app
apple_id "--" # Your Apple email address

team_id "--" # 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.59.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-sentry
1.4.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.1.2

bundler
1.15.4

io-console
0.4.6

CFPropertyList
2.3.5

i18n
0.8.6

minitest
5.10.3

thread_safe
0.3.6

tzinfo
1.2.3

activesupport
4.2.9

public_suffix
2.0.5

addressable
2.5.2

babosa
1.0.2

claide
1.0.2

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.3.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.7.8

cocoapods-trunk
1.2.0

cocoapods-try
1.1.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.7

ruby-macho
1.1.0

nanaimo
0.2.3

xcodeproj
1.5.2

cocoapods
1.3.1

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

declarative
0.0.10

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

dotenv
2.2.1

excon
0.59.0

multipart-post
2.0.0

faraday
0.13.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.0

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.2

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.7.3

googleauth
0.5.3

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.13.6

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.3.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

tty-screen
0.5.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
0.0.4

fastlane-plugin-sentry
1.4.0

generated on: 2017-10-02

15:24:42: --- Step: cert ---
15:24:42: ------------------
+---------------+----------------------------------------------------+
|                      Summary for cert 2.59.0                       |
+---------------+----------------------------------------------------+
| development   | false                                              |
| force         | false                                              |
| username      |<EMAIL_ADDRESS>                                  |
| team_id       | --                                        |
| keychain_path | /Users/--/Library/Keychains/login.keyc  |
|               | hain-db                                            |
| platform      | ios                                                |
+---------------+----------------------------------------------------+
15:24:42: Starting login with user<EMAIL_ADDRESS>[15:24:43]: Successfully logged in
[15:24:44]: Found the certificate -- (iOS Distribution) which is installed on the local machine. Using this one.
[15:24:44]: Verifying the certificate is properly installed locally...
[15:24:44]: Successfully installed certificate --
[15:24:44]: Use signing certificate '--' from now on!
[15:24:44]: ------------------
[15:24:44]: --- Step: sigh ---
[15:24:44]: ------------------
+-------------------------------------+----------------+
|               Summary for sigh 2.59.0                |
+-------------------------------------+----------------+
| force                               | true           |
| adhoc                               | false          |
| development                         | false          |
| skip_install                        | false          |
| app_identifier                      | --.--     |
| username                            |<EMAIL_ADDRESS>|
| team_id                             | --     |
| ignore_profiles_with_different_name | false          |
| cert_id                             | --     |
| skip_fetch_profiles                 | false          |
| skip_certificate_verification       | false          |
| platform                            | ios            |
+-------------------------------------+----------------+
[15:24:44]: Starting login with user<EMAIL_ADDRESS>[15:24:47]: Successfully logged in
[15:24:47]: Fetching profiles...
[15:24:48]: Verifying certificates...
[15:24:49]: Found 1 matching profile(s)
[15:24:49]: Recreating the profile
[15:24:51]: Creating new provisioning profile for '--.--' with name '--.-- AppStore' for 'ios' platform
[15:24:52]: Downloading provisioning profile...
[15:24:53]: Successfully downloaded provisioning profile...
[15:24:53]: Installing provisioning profile...
/Users/--/Documents/--/AppStore_net.--.mobileprovision
[15:24:53]: Setting Provisioning Profile type to 'app-store'
[15:24:53]: Cruising back to lane 'ios all_appstore' 🚘
[15:24:53]: --------------------------------------
[15:24:53]: --- Step: Switch to ios build lane ---
[15:24:53]: --------------------------------------
[15:24:53]: Cruising over to lane 'ios build' 🚖
@fastlane-bot the cert/sign steps are working completely fine

Is it just me that is having this problem? or are there more people?
(still having this problem)

@frrijn where you able to figure this out?

@waltermvp sadly not. Still having the same problem. Already spent quite some time trying to figure it out, but the error is just too general that I have no idea what it could be. But if you are able to find a solution. please let me know!:P

@frrijn same here manually uploaded metadata. However take a look here,
https://github.com/fastlane/fastlane/issues/8819#issuecomment-338058782

I had a similar error. Turned out I was uploading en-GB metadata into an app that only had English (U.S.) active in iTunes connect. Renaming the en-GB to en-US fixed it for me.


Added missing Questions and fixed Back to Top

Added missing Questions and fixed Back to Top

@uchiha-suraj  There are conflicts. Can you resolve them?

yeah, sure ;)

Thanks @uchiha-suraj for PR


[IMPROVEMENT] Make gRPC service timeout configurable

Is your improvement request related to a feature? Please describe (👍 if you like this request)
We are using longhorn 1.5.x in various environments.
One of them has PVC getting close to 1TB. It also has slower network than others.
From time to time we have network issues that will cause replica issues and cause longhorn to salvage a volume. Then longhorn will try to rebuild a replica from remaining sane ones: with the slower network and that amount of data, this operation takes hours and at some point timeouts when reaching 24h which might be frustrating if you've spent those hours looking at rebuild percentage going up slowly to 90+% before going back to 0%.
Describe the solution you'd like
As making the rebuild operation faster might be challenging and limited by network speed vs data size, the alternative would be to be able to give it more time i.e., from my understanding, be able to configure the gRPC service long timeout

Describe alternatives you've considered
Alternatives:

Reduce amount of data for rebuild operation (not always possible)

move data to other system
trim
rebuild replica with low data size
copy data back

Recreate PVC, move data to new one and switch from old to new one (blue/green kindof)

Related to the ticket https://github.com/longhorn/longhorn/issues/2765

Btw, if it takes longer than 24h to rebuild the replica, it is singling that the current infrastructure is not quite suitable for this big size volume. The cluster would busy doing rebuilding for a long time here. Would it be better to?

Reduce the size of the volume
Increase the network bandwidth in this cluster

@fab-sgnct
Can you briefly introduce how you use the volume, e.g. if the volume data is overwritten very frequently? Do you have any snapshots of the big volume? v1.5.x has introduced the fast replica rebuilding, but it sounds not working in your case.


Suggestion

Hello, i have a suggestion for Multi-mode gateway.
Could you make it like 5 presses on button triggers the permit_join on Zigbee2MQTT?
i think it would be useful for quick pairing
Please review my suggestion

No. This integration not related to ZHA or z2m projects.


"Unable to clone" error when following your INSTALL-linux.md instruction

When I let the machine to run the third line "git submodule update --init --recursive", it runs for a few minutes and eventually report an error

(base) root@653dab7338f7:~/waifu2x-caffe# git submodule update --init --recursive
Cloning into '/root/waifu2x-caffe/rapidjson/thirdparty/gtest'...
fatal: unable to access 'https://chromium.googlesource.com/external/googletest.git/': Failed to connect to chromium.googlesource.com port 443: Connection timed out
fatal: clone of 'https://chromium.googlesource.com/external/googletest.git' into submodule path '/root/waifu2x-caffe/rapidjson/thirdparty/gtest' failed
Failed to clone 'thirdparty/gtest'. Retry scheduled
Cloning into '/root/waifu2x-caffe/rapidjson/thirdparty/gtest'...
fatal: unable to access 'https://chromium.googlesource.com/external/googletest.git/': Failed to connect to chromium.googlesource.com port 443: Connection timed out
fatal: clone of 'https://chromium.googlesource.com/external/googletest.git' into submodule path '/root/waifu2x-caffe/rapidjson/thirdparty/gtest' failed
Failed to clone 'thirdparty/gtest' a second time, aborting
Failed to recurse into submodule path 'rapidjson'
(base) root@653dab7338f7:~/waifu2x-caffe#

what should I do about it?

It took a while, but it worked for me.
If you're inside a firewall that blocks google's domain, that might be the cause.

ok thanks.


chore: plural naming

provider -> providers

@jrieken Can you give me a look

Thanks for you PR but we aren't taking purely cosmetic changes

Thanks for you PR but we aren't taking purely cosmetic changes

But it is semantically wrong, shouldn't it be plural here?


Trying the quickstart, but getting an error.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\
node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v6.9.2
npm ERR! npm  v3.5.2
npm ERR! code E404
npm ERR! 404 no such package available : @angular/common
npm ERR! 404
npm ERR! 404  '@angular/common' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'angular-quickstart'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Downloads\quickstart\npm-debug.log

Install a newer npm

This is the absolute latest.  Goto nodejs.org and 6.9.2 is the latest you can get for windows unless you want to try the experimental stuff.  I actually figured it out by doing the following.
npm set registry http://registry.npmjs.org

Newer npm, not node

Ok, agreed, but npm is bundled with nodejs.  3.5.2 is the latest AFAIK.  But either way, I am all good with the registry.

Latest is 4, but with a 3.10.x it is happy

@jbarber2016 had the same issue, your solution to set the registry first worked for me 👍

Setting the registry and having the latest npm and node still doesn't work or me. I am on windows 10:
npm ERR! code EJSONPARSE
npm ERR! Failed to parse json
npm ERR! Unexpected token '\u0000' at 1:1
...
npmERR! Failed to parse package.json data
npmERR! package.json must be actual JSON not just JavaScript
npmERR!
npmERR! This is not a bug in npm.
I am using node v6.9.2, npm v3.10.10

I would guess something is wrong with your package.json, maybe the encoding isn't correct but hard to know without seeing it.

I cloned the repository. Here is the file:
package.json:
{
"name": "angular-quickstart",
"version": "1.0.0",
"description": "QuickStart package.json from the documentation, supplemented with testing support",
"scripts": {
"start": "tsc && concurrently "tsc -w" "lite-server" ",
"e2e": "tsc && concurrently "http-server -s" "protractor protractor.config.js" --kill-others --success first",
"lint": "tslint ./app/**/*.ts -t verbose",
"lite": "lite-server",
"pree2e": "webdriver-manager update",
"test": "tsc && concurrently "tsc -w" "karma start karma.conf.js"",
"test-once": "tsc && karma start karma.conf.js --single-run",
"tsc": "tsc",
"tsc:w": "tsc -w"
},
"keywords": [],
"author": "",
"license": "MIT",
"dependencies": {
"@angular/common": "~2.4.0",
"@angular/compiler": "~2.4.0",
"@angular/core": "~2.4.0",
"@angular/forms": "~2.4.0",
"@angular/http": "~2.4.0",
"@angular/platform-browser": "~2.4.0",
"@angular/platform-browser-dynamic": "~2.4.0",
"@angular/router": "~3.4.0",
"angular-in-memory-web-api": "~0.2.2",
"systemjs": "0.19.40",
"core-js": "^2.4.1",
"reflect-metadata": "^0.1.8",
"rxjs": "5.0.1",
"zone.js": "^0.7.4"

},
"devDependencies": {
"concurrently": "^3.1.0",
"lite-server": "^2.2.2",
"typescript": "~2.0.10",
"canonical-path": "0.0.2",
"http-server": "^0.9.0",
"tslint": "^3.15.1",
"lodash": "^4.16.4",
"jasmine-core": "~2.4.1",
"karma": "^1.3.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~4.0.14",
"rimraf": "^2.5.4",

"@types/node": "^6.0.46",
"@types/jasmine": "^2.5.36"

},
"repository": {}
}

I have similar problem, attaching npm log.
npm-debug.log.txt

Apparently problem was related to zone.js: https://github.com/angular/zone.js/issues/554
I've fixed it by updating package.json dependencies to newest one and doing npm install.


Add go.mod and a basic .gitignore

Add a basic go.mod and .gitignore to get started.

/lgtm

@evallesp It's the basic one GH creates, even the operators are using this one that has references to Windows executables.


Bump plugin version in the next release

https://github.com/mybbgroup/Isango/blob/263fc9140178efda3438266df54d1eb1ee9a04e6/upload/inc/plugins/isango.php#L22
As title says we have to bump version number in next release (for now let it be).

Oopz...

Closed by #57

Need to bump to 2.0.0

Need to bump to 2.0.0


Initial FAQs page

:white_check_mark: Checklist

[ ] This pull request has a meaningful title.
[ ] If your changes are not yet ready to merge, you have marked this pull request as a draft pull request.

:ballot_box_with_check: Maintainers' checklist

[x] This pull request has had the appropriate labels assigned
[x] This pull request has been added to the SATRE backlog project board
[ ] This pull request has been assigned to one or more maintainers

:arrow_heading_up: Summary

Adds FAQs page

:closed_umbrella: Related issues

Closes #236

:raising_hand: Acknowledging contributors

[x] All contributors to this pull request are already named in the table of contributors in the README file.
[ ] The following people should be added to the table of contributors in the README file:

Would be great to know if others can think of FAQs - maybe another good option for collab cage @harisood

What is the relationship between SATRE, DEA, DSPT, SDE, ...... etc
....

Who governs the SATRE specification?
....

Does SATRE support federation?
SATRE does not currently support federation, but is a building block to support interoperability and future federated standards

What is the relationship between SATRE, DEA, DSPT, SDE, ...... etc

I'm not sure of the answer here

Who governs the SATRE specification?

For now at least - is this the same as "Who are the maintainers?" and not the same as "Who are the contributors?"

Does SATRE support federation?
SATRE does not currently support federation, but is a building block to support interoperability and future federated standards

I think we'll need to add a glossary definition for both "interoperability" and "federation" to add this

I think a table layout looks too cramped. What do you think of using headings and paragraphs instead? This has the added benefit that you can link directly to a question in future.
## Is SATRE an ISO technical standard?

No. The SATRE specification aims to provide a helpful guide for TRE Operators, Developers and Builders....

I think a table layout looks too cramped. What do you think of using headings and paragraphs instead?

Agreed, looks better

Will merge this now - should be easy to add/edit subsequent FAQs from here


Gzip encoding: steps

Hi,
Could you provide specific steps on how to enable compression for rest endpoint?
Maybe a tutorial / example how to do it step by step for light-4j v2.x...
I have read this FAQ: https://doc.networknt.com/faq/gzip-response/#how-to-compress-the-response-with-gzip
but I don't understand how to apply this in my test app:

what config files to change?
need to create some provider & how to register it?

@chivas-bambook It is a good idea to create a tutorial to show how to use the encoder and decoder between two services. I will write up something soon. Thanks a lot for raising it up.

@chivas-bambook Meanwhile, you can take a look at the test cases for the usage. It will take a while for us to create another tutorial.

@stevehu Ok, thank you


Block breaking delay issue?

Having issues where using this addon with some specific scripts causes a delay in breaking blocks as seen in this video. https://youtu.be/zpoGuKKXKvE
Even this basic test causes it. Disabling all scripts and restarting fixes it. Then enabling one with just this test starts it again.

Using:
Minecraft 1.21.1 - Paper
Skript 2.9.1

Changing from "packet event" to "sync packet event" fixed this issue, not sure if that's the intended fix but it doesn't delay block breaking now.

Yes, it's the fix.
The default event listener use async thread to process some code then switch to the main Thread. This is to ensure low TPS impact but takes more times. This is how ProtocolLib works and that's why I have added the option for full sync / async.
You should use on sync packet only when it's really needed.


fix: update examples to 3.12.0

coverage: 99.245%. remained the same
when pulling 0a94fdd743971049c293cf8601225b226bdf176c on rc-fix-examples-3.12
into 698661062f93d9bee61c5d78ad787d85547f6ea0 on master.


Remove need for useEffect in Product Overview page

This also prevents a potential bug if the view parameter is not the first parameter in the searchParams.

Oh yeah, I just used GitHub's editor to do this. Let me see if I can make another PR off develop.


Allow importing assets from parent folder

The app we are building with create-react-app is a part of a larger application, and resides in a subfolder of the repository. We wanted to load some JSON files from the parent folder, so we don't need to copy these configurations (used also by other parts of the app) to the subfolder.
Currently this results in an error, because files from the parent folder are not loaded with json-loader:
You may need an appropriate loader to handle this file type.

Would it make sense to loosen the include setting for certain loaders? We probably still want to exclude node_modules from the modules processed with babel-loader, but wouldn't it make sense to drop the include setting altogether from those loaders that already have include: [paths.appSrc, paths.appNodeModules]?

Would it make sense to loosen the include setting for certain loaders? We probably still want to exclude node_modules from modules processed with babel-loader, but wouldn't it make sense to drop the include setting altogether from those loaders that already have
include: [paths.appSrc, paths.appNodeModules],

?

wouldn't it make sense to drop the include setting altogether from those loaders that already have include: [paths.appSrc, paths.appNodeModules]?

Let's do it. Want to send a PR?

@gaearon I'll send a PR.

@fson @gaearon what about importing js modules from a parent shared folder, is that possible?


Move @types/hoist-non-react-statics to devDependencies"

This pull request moves the "@types/hoist-non-react-statics" package from the dependencies section to the devDependencies section in the package.json file. This change is appropriate because type declaration files are typically used during development and compilation but are not required at runtime.
The modification ensures that the type definitions for "hoist-non-react-statics" are available during development and TypeScript compilation, but won't be included in the production build of projects using this package. This change helps to reduce the size of the production bundle and follows best practices for managing dependencies in TypeScript projects.
To implement this change, I used the following npm command:
npm install @types/hoist-non-react-statics --save-dev
This command installs the package as a dev dependency and automatically updates the package.json file, moving it from the "dependencies" section to the "devDependencies" section.

thank you, it's included in v15.4.1


Issues with kernel 4.19.115-v7+ rpi-update on ubuntu-mate 16.04.2

Having issues with rpi-update on kernel 4.19.115-v7+ on ubuntu-mate 16.04.2, after upgrade the new firmware update it cannot reboot and hdmi gives no signal. Now ubuntu-mate 16.04.2 cannot boot up at all. Having upgrading issues with reboot problems since kernel 4.19.115.

Which device(s) are you testing?

Raspberry pi 3

Can you identify the exact update which caused this. See:
https://github.com/Hexxeh/rpi-firmware/commits/master
If you click on each commit the end of the url contains a git hash. Run
sudo rpi-update <hash>
to revert back to that version. Report the first version with this error.

The problem is now my raspbery pi 3 cannot even boot up ubuntu-mate 16.04.2 on my SD Card.
It is total. Brick.

And that is why we advise people not to run rpi-update without good reason.

anyway to recover the boot issues on ubuntu-mate 16.04.2???

Do you have a spare SD card and a USB card reader? If so, download a fresh image - the Lite build will do - and write it to the new card, then come back for instructions.

pelwell i install another image of ubuntu-mate 16.04.2 on another SD card and have USB card reader. I try to copy the boot.bak to boot. Still it would not boot up. No Signal on HDMI. Please let me know the step to do. Thank you.

pelwell, i have check, the /lib/modules.bak and lib/modules are the same. The only different is that the /lib/modules files have the latest rpi-update kernels. The PI_BOOT files are there. But the PI_ROOT boot files are not there. Even though I copy the boot.bak to boot. There is no HDMI Signal. There is no boot to the SD Card.

OK, we can try a reinstall with an older version, but note:
There is no guarantee this will work, and if this fails then I'm out of suggestions - you'll just have to try and salvage the data as best you can.

With the broken card in the card read plugged into the Pi you should end up with two mount points - something like /media/pi/boot and /media/pi/root. I'm going to use those paths in the these instructions, but you may need to change them to match reality.
On the https://github.com/Hexxeh/rpi-firmware/commits/master page you'll find a list of releases. Because you are on a Pi 3 I'm going to guess that there might have been a problem with the switch to the common firmware on Apr 16th, so the last commit before that is https://github.com/Hexxeh/rpi-firmware/commit/10f878d6798d22599e50c6e4eb0e619924ee0d68 on Apr 15th, which shortens to 10f878d.
Run the following command:

$ sudo BOOT_PATH=/media/pi/boot ROOT_PATH=/media/pi/root rpi-update 10f878d

When that completes, shutdown the Pi, move the patched card from the card reader into the normal slot and apply the power. Finger crossing is optional.

Hi pelwell,
It work like a charm! I managed to get it to work on single attempt. Your methods really works.
I have my other SD Card with the similar Ubuntu-Mate 16.04.2 distro. And run the command
that you mentioned.
$ sudo BOOT_PATH=/media/pi/boot ROOT_PATH=/media/pi/root rpi-update 10f878d
Make some modification to the path while access to my other SD Card.
$ sudo BOOTH_PATH=/media/rusli/PI_BOOT ROOT_PATH=/media/rusli/PI_ROOT rpi-update 10f878d
And shutdown the Pi down and reboot the patch card reader in to the PI. And it is working! Woohoo!
Thank you pelwell.
I wonder why the latest kernel was not supported with the Rapsberry pi 3????
There were issues too with 4.19.115 and the 4.19.115-V7+ with the Raspberry pi 3.
Once again Thank you. Very much appreciate your help pelwell.

rpi-update is a testing ground for new kernels and firmware. Since the launch of Pi 4 we have been building its firmwares from a separate version of the code, but this is a maintenance headache because most changes have to be made to both side. The master branch of the releases has just switched to building all firmware from the same source code to give it some more testing, and some people have reported problems - not as extreme as yours, usually - and they are being investigated.
It looks as though you were unlucky with the timing of your update, or perhaps the update just went wrong in some way, but it underlines the fact that rpi-update and its firmware releases should be used with caution, preferably after a backup, and ideally not at all.

You may want to follow https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=267576 for more
information about what is being tested.
We aren't currently aware of an issue that would explain what you have seen.
If you have a spare sdcard and some free time it may be useful to install raspbian, run rpi-update and see if you also see the same issue.
If not, then install ubuntu-mate 16.04.2 and run rpi-update see if you see the same issue.

There are bugs with kernel 4.19.115 and 4.19.115-v7+ with the raspberry pi 3. As after doing the rpi-updates, I cannot do any reboot and the power is totally down. No Signal on my HDMI output. I done it with my new SD Card. I had the same problems. I got no choice but to register and sign up myself to the github and ask for help. That is my only hope. LoL! I just hope they fix those bugs before it release to the public. Once again thanks for your help. pelwell.

I just hope they fix those bugs before it release to the public.

FYI, "they" is us (@pelwell, @popcornmix and others), so "they" are aware of your problem and won't make a full OS release until they think it is ready.

Oh thanks for the infos popcornmix.
I sure am. Doing those testing. Thanks for the help guys. Very much appreciate it.

LoL! Ah... programming errors eh? Hee hee hee....

Please close the issue if you are satisfied with the answers.


Partial and Unlabeled Predictions

After fine tuning on on a small set of classes.  For example, I have a class called ''mvr" and it is displayed as "mv". I have attached an image of the output below.

dunno about the partial labels, but boxes without labels happens because of your threshholds.
if something has acc of 0.25 it will draw a box but dont write a label


"Optimization Opportunities" panel hints Gmail address although it shouldn't be provided

A company e-mail is required but a Gmail address is hinted:

However, as expected, it is not accepted:

Hi Dan, you're right... that's somewhat confusing. I'll have the backend team update it.

Should this be handled in the front end?


feat(): show old version of hunks via virtual lines

Use virtual lines to show the old version of hunks inline in the buffer.

Added config.show_deleted
Added toggle_deleted()

E.g:

Oh wow! That's a neat idea!

Is highlight group configurable?

Not yet, currently uses GitSignDeleteLn.

A, I saw TermCursor and assumed it's only that, but if it is a custom group then colorschemes can just style it accordingly, doesn't need to be configurable as can just be linked if needed.

Yep, I sorting out highlights more with #395

I was looking for exactly this, thanks! :beer:


🆕 Software Suggestion | Remotely

Basic Information
Name: Remotely
Category: Productivity Tools
URL: https://remotely.one/
Description
Remote desktop software accessible via web browsers. No network configuration is necessary as it uses a reverse connection scheme (UDP hole punching?). Supports GPU acceleration and WebRTC for fast streaming. Fully open-source. Supports Windows and Linux (but can be accessed from any device with a web browser). Can be self-hosted, although a public instance is offered. 2FA is supported.
Why I am making the suggestion
Same reason as #2312. This one is much faster, it uses a more modern and efficient compression protocol, but the team is much smaller and younger.
My connection with the software
None, just a user.

[x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.

How It Works
The Remotely client has two parts: the service and the remote control. The service is responsible for maintaining a persistent connection to the server and executing remote commands. The remote control is launched as needed for remote control sessions.
Both applications make outgoing websocket connections over secure SSL/TLS protocol. Because the connections are outgoing, you don't need to open any ports in your firewall, and the service won't accept any incoming connections.
The Remotely service will register with your Remotely organization ID, which is generated when you create your account or join an existing organization. On the first connection, the service generates a separate unique ID and sends it to the server. Upon each subsequent connection, the server must send back that ID before anything else, or else the service will uninstall itself immediately. This is an additional layer of security that ensures the service is communicating with the original server.
Users and computers are grouped into an organization, and they can't interact with resources outside their organization. Microsoft's Identity framework is used for all login and authentication to verify users.

Source: https://remotely.one/About


on first startup, "no dashboard :("

This happens when starting a locker prior to the dashboard installing from the registry.

I've never had this happen - do you have a screen shot? I'm working on site polish stuff.

We're already solving this.

simon fixed it :)


[Bug Report] Bad performance with add key command

Server laggy when the command is used on a large number of players.
Versions (please complete the following information):

Minecraft Server Version: 1.18.2
Plugin Version:  1.11.6-SNAPSHOT

Issue
Bad performance with add key command
Screenshots

The open crate also needs some optimization too.


DONTMERGE: Debug Windows path

Thank you for a step-by-step debugging session. This documents it quite well. I was trying to run same steps on my local machine itself because the behaviour of the subprocess was similar there too.

Debugged and results are incorporated here.


Website is inaccessible because of Cloudfare error.

Attempting to access https://stencil.fuller.li to view the documentation is currently broken. A Cloudfare error page is shown instead.

Same issue here. Seems like a lot of people have this problem. https://twitter.com/stefanprodan/status/834872543790174209 may help? Not sure if there is anything we can do on the Cloudflare side.

Same trouble nowadays. @kylef @ilyapuchka @djbe you could resolve this issue, i guess.

Same problem as https://github.com/kylef/swiftenv/issues/162#issuecomment-518191162. Issued the same fix, it may take a little bit of time due to the nature of DNS TTL.

Thanks a lot, @kylef 🙏
Now it's works!


Change Write([]byte) to log full message to message field

[This is in part a continuation of a discussion started in PR #9 where we were also worried about message length.]
The message field (sent as short_message in GELF) and the full_message field are stored in the exact same way in Elasticsearch, so presumably they support the same sizes. I've actually tested message only up to 80 KB (via a null-delimited "RAW/Plaintext" interface) and 2500 lines or so, however. :-) It works fine, and the Graylog UI seems to do a reasonable job of dealing with it. (I have seen a complaint that long fields don't work, but that appears to be because they changed the default configuration to do term analysis on the message field, which isn't done by default.)
Having looked into this a bit, I find:

full_message is optional to send in GELF, unlike message.

full_message is not parsed for things like sources and timestamps.

On its syslog inputs, Graylog has a store_full_message: true option which stores the raw syslog protocol message (usually RFC 5424 in the full_message field. This seems useful for debugging and handling situations where bad messages come in that the parser can't handle. We turned this on when we set up Graylog because it seemed like a good idea at the time, and it still doesn't strike me as a bad thing to do.

Graylog search functionality seems to be oriented mainly towards message and it seems to take a bit of extra work to search full_message instead.

From all this, I get the sense that full_message is considered something that can be safely ignored by clients retrieving and processing messages from Graylog. Given that, I think it's a bad idea, when given a message via the io.Writer interface, not to put the entire message into the message field.
As background, let me tell you about my use of Graylog at work. We have dozens of servers generating log messages into the Systemd Journal that we forward to a central Graylog installation so we can easily query across servers, do centralized analysis (such as with OSSEC LIDS log analysis), keep historical records, and so on.
In order to keep things as simple as possible, I'm aiming to get all our non-journal logging also going into the journal, including logs from programs that write directly to /var/log such as auditd, output of jobs run by cron, and so on. (For example, I'm intending to replace /usr/sbin/sendmail on those servers with a program that eats the message and logs it to the journal.)
One of the questions I had to ask myself is whether I should be using the full_message field, and what with various programs partially duplicating information across message and full_message, that seems like a bad idea. How would the OSSEC log scanner, for example, know that for some log entries full_message is all the information in message and a few other fields in unparsed form, yet for other messages message could be an incomplete log message and full_message contains the complete message but without other log entry information such as the timestamp? That way lies a lot of pain, especially if I end up having to assemble new versions of log entries for log-scanning software that expects things to be re-assembled in a syslog-ish format with the timestamp, source etc. all in one big string.
So for these reasons, I'm suggesting we change the io.Writer API, Write([]byte),  of go-gelf to record the entire bytestring it's handed in the message field and not send a full_message field. I think it's reasonable for it to continue adding things like the extra fields for file and line number of the caller.
Note that if anybody does want to use the full_message field for something, or any other fields for that matter, we have the Write(*Message) interface for that which allows (or should allow) full control over the GELF message being sent, within the limitations of the protocol. (We should not allow, e.g., a GELF message to be sent without a message field since that field is required by the protocol.)
If we're agreed on this, I'm happy to submit a PR for changes to the code and update the documentation appropriately, including this rationale in an appropriate place (probably the commit message).

Makes sense to me! The short_message field is mandatory while full_message is optional.
So the best solution would be to allow the user to decide which part of the message should go into which field. But because of the nature of this library of implementing io.Writer we can't provide additional flexibility easily. We could think of some way of providing a split function to the writer. But in the end using only the message field should be what most people expect.

Oh, I wasn't clear in the original post; we also have the Write(*Message) interface that allows clients to set up whatever arbitrary GELF messages they like, so there's no problem if they want to do something in particular. (We should check it to make sure it gives maximum flexibility, of course; I'll try to compare it with the spec. tomorrow.) Write([]byte) is just a convenience method, really, for those who want to just log some sort of message and not be bothered with the details of all the different ways they could do it.
I'll update the issue above with this information.

I would suggest at the same time updating the documentation of the GELF payload to reflect this understanding that the short_message field really means message. It would be helpful if it was made clear that the short_message  field in GELF maps to the message field in Graylog.

Please use the branch v2 as base for upcoming API changes!

I take it you've decided not to bring in this change for v2, but delay it until v3?
I'm not clear on how using v2 as the base works. If you accept an API change and merge it on to master, and someone else has another change for the new version, if they base it off of v2 they won't be testing the other changes already on master.
My suggestion is this:

Have master and v2 point to the same commit for the moment.
Delay, for a little bit, bringing in any API-breaking changes.
Bring in non-API-breaking changes (e.g., some README fixes I have lined up) on both master and v2 by having both refs move forward on the same commits together.
When we have API-breaking changes to bring in, bring them in on master and live with having to do each change we want to bring into v2 as well a second time on v2.

v2 is master currently, so if there is no other work going on it stays the same. When there are API changes and refactorings we will branch v3 of of it. Just that you take the merged TCP feature into account when you do something there.

So for non-API-changing commits, I should be submitting PRs to v2 and you'll put them on master as well? You want commits that change the API also submitted for v2 and you'll take care of redirecting them appropriately?
That's fine, but I'd suggest you document this somewhere obvious from the main page for this repo, because people are unlikely to notice it buried deep in this issue.

So I'd like to submit a pull request that solves this problem, but I'm not sure how to best go about it.
Would you consider it an API change if the current behavior was changed to simply writing the whole message to both the Full and Short fields of the message type? If not, then I would submit that...
If it is an API change, then we might as well go all the way and abandon the Full field - with the above behavior it's just duplicated info.


[File locksmith] Adding context menu icon

Description of the new feature / enhancement
Please add a context menu icon to the entry of FLS.

Scenario when this would be used?
Helps to find the entry in the context menu faster.
Supporting information
No response

Released/fixed with v0.69.0!


Upgrade deps

Upgrade dependencies.
Test Plan

[X] acceptance tests

maybe will fix the make deps situation


MPI Build Fix for newer GNU Fortran compiler versions

@sriram-LANL
Add -fallow-argument-mismatch to GNU fortran compiler flags to allow MPI calls to build with warnings on newer GNU compilers
https://stackoverflow.com/questions/63892055/fortran-error-type-mismatch-between-two-unrelated-subroutine-calls

Changes absorbed into release/1.0.1


Add http body

I have an endPoint:
var endpointClosure = { (target: MyCustomApi) -> Endpoint<MyCustomApi> in
    let endpoint: Endpoint<MyCustomApi> = Endpoint<MyCustomApi>(
        URL: url(target),
        sampleResponseClosure: {.NetworkResponse(200, target.sampleData)},
        method: target.method,
        parameters: target.parameters
    )
    switch target {
    case .Person(let json):
        //How to add HTTPBody here?  endpoint.urlRequest is not mutable, so i can't change the request.
    default:
        return endpoint
    }
}

enum NextVisitApi {
    case Person(someJSON: JSON)
}

Typically HTTP bodies come from parameters, looks like you have one that's specified in JSON. So to set the HTTP body to the json, you just need to tell Moya which parameter encoding to use.
var endpointClosure = { (target: MyCustomApi) -> Endpoint<MyCustomApi> in
    let endpoint: Endpoint<MyCustomApi> = Endpoint<MyCustomApi>(
        URL: url(target),
        sampleResponseClosure: {.NetworkResponse(200, target.sampleData)},
        method: target.method,
        parameters: target.parameters
    )
    switch target {
    case .Person(let json):
        return endpoint.endpointByAddingParameterEncoding(.JSON)
    default:
        return endpoint
    }
}

And that should work. You can check out the different options for parameter encoding here.
Let me know if that helps :+1:

Also i'd like to add this link
Hope it will be helpful

Yeah, good point! The request-mapping is later-stage stuff in the pipeline, but it's there that I'll often play around with stuff I can't get working at higher levels.

This is correct?
var endpointClosure = { (target: NextVisitApi) -> Endpoint in
let endpoint: Endpoint = Endpoint(
URL: url(target),
sampleResponseClosure: {.NetworkResponse(200, target.sampleData)},
method: target.method,
parameters: target.parameters
)
switch target {
case .VisitsPUT:
return endpoint.endpointByAddingParameterEncoding(.URL).endpointByAddingHTTPHeaderFields(["Content-Type":"application/x-www-form-urlencoded; charset=UTF-8"])
default:
return endPointWithAuthHeader(endpoint)
}
}

That would URL encode it, which might be what you want, I'm not sure of your server setup.
In general, yes, this is exactly how you customize attributes of requests, through the endpoints closure.

I think we can close this one for now, if anything pops out, let us know! 🐼

@sunshinejr @ashfurrow @ivanruizscm I have encountered this issue too. But there is no endpointByAddingParameterEncoding method in Moya 10.0.0 anymore. Could you guide me how to do this?


[Minor] Raise exception for wrong import

Hi, just wondering if this is still correct in README?
docker run --gpus all \
    -p 30000:30000 \
    -v ~/.cache/huggingface:/root/.cache/huggingface \
    --env "HF_TOKEN=<secret>" \
    --ipc=host \
    lmsysorg/sglang:latest \
    python3 -m sglang.launch_server --model-path meta-llama/Meta-Llama-3.1-8B-Instruct --host <IP_ADDRESS> --port 30000

I am building an alternative version of the image defined in Dockerfile and now getting the error added in this PR when I run python3 -m sglang.launch_server...

Hi, just wondering if this is still correct in README?
docker run --gpus all \
    -p 30000:30000 \
    -v ~/.cache/huggingface:/root/.cache/huggingface \
    --env "HF_TOKEN=<secret>" \
    --ipc=host \
    lmsysorg/sglang:latest \
    python3 -m sglang.launch_server --model-path meta-llama/Meta-Llama-3.1-8B-Instruct --host <IP_ADDRESS> --port 30000

I am building an alternative version of the image defined in Dockerfile and now getting the error added in this PR when I run python3 -m sglang.launch_server...

Yes it is still correct since it works for the lmsysorg/sglang:latest image in Docker Hub. I need to fix something in my Dockerfile - it worked before the latest updates. Anyway, my bad, apologies for disturbance!


extend the support from csv to all excel file formats(xls, xlsx and ods)

The fundamental change is that unicodecsv was replaced with pyexcel. This PR has updated many aspects. I wondered if this could be accepted back in or not.

I am afraid I can't accept this diff since its going to change the package name itself. I feel this can be a separate project itself in different repo and can be distributed in different name.

Alright, I would release it separate as a variant to csvtotable and keep its downstream compatibility.


chmo IRI is invalid

Hi,
The IRI/URL of Chemical Methods Ontology is no longer available (http://purl.obolibrary.org/obo/chmo). Could you please help to fix it?
Thank you.

Yes of course.

The correct PURL for the ontology is http://purl.obolibrary.org/obo/chmo.owl
Class PURLs are of the form http://purl.obolibrary.org/obo/CHMO_0000161
I think this issue can be closed?


Training with 96x96 input

Hello,
I am trying to adapt the code to run 96x96 inputs, more specifically the BigGAN.py script, by adding arch[96] into the functions def G_arch and def D_arch. However, I get the following error when compiling D_input = torch.cat([img for img in [G_z, x] if img is not None], 0) line in the def G_D function:
RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 0. Got 96 and 64 in dimension 2 at /pytorch/aten/src/THC/generic/THCTensorMath.cu:71
What I could investigate so far are the G_z and x tensors. They have different dimensions, torch.Size([50, 3, 64, 64]) and torch.Size([50, 3, 96, 96]), respectively. Therefore, concatenation cannot be done. I think that G_z tensor should also be in the form of x tensor. I would appreciate any help.
arch[96] = {'in_channels':  [int(ch * item) for item in [16, 16, 8, 4]],
            'out_channels': [int(ch * item) for item in [16,  8, 4, 2]],
            'upsample': [True] * 4,
            'resolution': [12, 24, 48, 96],
            'attention': {2**i + 2**(i-1): (2**i + 2**(i-1) in [int(item) for item in attention.split('_')]) for i in range(3, 7)}}
.
.
.
arch[96] = {'in_channels':  [3] + [int(ch*item) for item in [1, 2, 4, 8]],
            'out_channels': [int(item * ch) for item in [1, 2, 4, 8, 16]],
            'downsample': [True] * 4 + [False],
            'resolution': [48, 24, 12, 6, 6],
            'attention': {2**i + 2**(i-1): 2**i + 2**(i-1) in [int(item) for item in attention.split('_')] for i in range(2, 7)}}

I solved the problem by changing the bottom_width variable's default to 6 in the Generator class.


cross_section and probability interface exports

Currently, QEDbase.jl exports the functions

unsafe_differential_cross_section
differential_cross_section
total_cross_section
unsafe_differential_probability
differential_probability
total_probability

However, it does not define them in any way. This is definitely an issue because they cannot be overridden (because they are undefined) but re-exporting them in a different package still creates a collision requiring a namespace qualifier to use them. The question is where to keep the implementations in the future. Right now they are in QEDprocesses.jl. The functions seem basic enough to be part of either QEDbase or QEDcore, and since they are in a way convenience functions based on top of an interface, I suggest moving them to QEDcore.

Oh, this should be added here because defining them anywhere else, would end up being type piracy in one way or another.
I will open a PR later today.

Solved with #87


Setup secure access through SSH with /dev/ pipes.

See if there's a way that CSHers can use their shell access to ssh and then pipe data to a file in a similar manner as the /dev/ profiles work.

We're working on this right now! expect to see something very soon,
Thanks!


Better dogstream format

@dannyroberts this is a better dogstream format. wasn't as trivial as i had first thought, luckily the conf allows for trailing commas
@proteusvacuum

already ran on prod

:pray: very nice of them on the trailing commas. Looks good to me, thanks!


Add support for qs options via qsOptions key

Closes https://github.com/request/request/issues/1473
The qsOptions key can be used to pass options to both the parse and the stringify methods of the qs and querystring modules.
The arrayFormat options was missing from the qs readme https://github.com/hapijs/qs/pull/72

A few thoughts on this:

Can we link directly to the relevant options from the readme?

qs.parse
qs.stringify
querystring.parse (seems better to link directly to a specific Node.js version here, rather than the latest)
querystring.stringify
Not our issue, but it's hard to tell from a glance what options the qs methods support.
Since this does a lot of different things, may be better to split it into two: qsParseOptions and qsStringifyOptions?
Some text like this might be good, too:

qsOptions - object containing options to pass to the qs or querystring module*, for example, to change the way arrays are converted to query strings*

Agreed, I was thinking about the same problem - different options for parse and stringify Also adding links there would be good.

Improved the docs a bit, and introduced the qsParseOptions and the qsStringifyOptions keys.


Untrusted certificate error is reported when image signing is enabled.

This issue only happens when the internal image registry is used.
--dest-tls-verify=true flag needs to be removed in order to honor the value of insecure registry setting for the internal image registry.

PR is #353

Merged fix.  Will be in RC2

verified with RC.2


Fix: Example - missing dependency #90

Description

When I tried to copy and install it independently, I found that it created dependency issues.
Related Issue

#90

Summary by CodeRabbit

New Features

Integrated Vanilla Extract CSS-in-JS library with Vite for improved styling management and performance.
Enhanced type safety and theming options within the project.

Additional context

Checklist

/fast-forward


[engsys][monitor-query] upgrade typescript version to ~4.8.0

to be consistent with most packages in the repository.

Fix compiler errors. Use Extract<Thing, Record<PropertyName, unknown>> instead of Thing & Record<PropertyName, unknown>

probaly also need to update core-util

API change check
API changes are not detected in this pull request.


Template string multiline does not work on test input

Hi,
let me say thank you for this package first. I'm really enjoying it.
I found one issue with test input when using template literals. It looks like it adds some wierd whitespace or uses something als instead of \n when using multiline strings.
Had this issue on day03 part1.
part1: {
    tests: [
      {
       // works:
        input: `00100\n11110\n10110\n10111\n10101\n01111\n00111\n11100\n10000\n11001\n00010\n01010`,

        // does not work: (multiline string)
        input: `00100
        11110
        10110
        10111
        10101
        01111
        00111
        11100
        10000
        11001
        00010
        01010`,
        expected: 198,
      },
    ],
    solution: part1,
  },

Hi!
The test input worked for me on that day. It seems you have a lot of spaces or tabs in your test data, is that there in your actual code as well? Because that will be part of the string literal and add "weird whitespace". Try removing all spaces before the lines after the first.

It has to do with how trimTestInput option works - it will trim empty lines at the beginning and the end of the input and will remove the indents only if the indents are the same, so you can nicely format the input, while not messing deliberate differences in indentation. In your example, the first line of the test input is not indented as far as JS template string is concerned.
In JS template string all the white spaces are a part of the string, so without trimTestInput option the input would have to look like this:
run({
  part1: {
    tests: [
      {
        input: `forward 5
down 5
forward 8
up 3
down 8
forward 2`,
        expected: 150,
      },
    ],
    solution: part1,
  },
  part2: {
    tests: [
      // { input: ``, expected: "" },
    ],
    solution: part2,
  },
  trimTestInputs: false,
})

/*
Produces input:

forward 5
down 5
forward 8
up 3
down 8
forward 2
*/

With trimTestInput: true it can look like this:
run({
  part1: {
    tests: [
      {
        input: `
          forward 5
          down 5
          forward 8
          up 3
          down 8
          forward 2
        `,
        expected: 150,
      },
    ],
    solution: part1,
  },
  part2: {
    tests: [
      // { input: ``, expected: "" },
    ],
    solution: part2,
  },
  trimTestInputs: true,
})

/*
Produces input:

forward 5
down 5
forward 8
up 3
down 8
forward 2
*/

But not like this:
run({
  part1: {
    tests: [
      {
        input: `forward 5
          down 5
          forward 8
          up 3
          down 8
          forward 2
        `,
        expected: 150,
      },
    ],
    solution: part1,
  },
  part2: {
    tests: [
      // { input: ``, expected: "" },
    ],
    solution: part2,
  },
  trimTestInputs: true,
})

/*
Produces input:

forward 5
          down 5
          forward 8
          up 3
          down 8
          forward 2
*/

I added a relevant section to the README: https://github.com/caderek/aocrunner#trimtestinputs
Closing, let me know if something is not clear.


Global File system: path direct error in readfile and writefile function

The writefile and readfile function only support for the operation in the root folder, once I want to specify a subdirectory like apps, it feels to navigate inside to do the read or write operation. For example
GFS.readFile('./code/test.json', function(err,data){
console.log(data);
})
should read te file inside the code folder, but it throw me an error as not found.
for write GFS.writeFile('./code/test.json', testdata,function(err,data){
console.log(data);
}), it failed to write data inside code folder and only write it to root folder.

I am merging this issue with the previous one which was open.

Currently you cannot use unix-style relative paths because what the cwd (current working directory) is for a ThingsJS worker is unclear. Once we establish what the cwd would be, we can start supporting relative paths. For now, let's just stick to absolute paths.

It is able to read from the folders. We tested. The problem currently is it
can only write to nested folders if there already exists a file. If the
file does not exist, it is unable to create the file in the nested folder.
So a separate create function should do the task?
Also second thing is will the users be running the benchmarks? The reason I
ask is for testing and running the benchmarks right now we have a small
hack that works but it might not work for the users.
On Mon, 8 Oct, 2018, 11:10 AM Xuejie(Alicia) Tang<EMAIL_ADDRESS>wrote:

The writefile and readfile function only support for the operation in the
root folder, once I want to specify a subdirectory like apps, it feels to
navigate inside to do the read or write operation. For example
GFS.readFile('./code/test.json', function(err,data){
console.log(data);
})
should read te file inside the code folder, but it throw me an error as
not found.
for write GFS.writeFile('./code/test.json', testdata,function(err,data){
console.log(data);
}), it failed to write data inside code folder and only write it to root
folder.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DependableSystemsLab/ThingsJS/issues/40, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJtt-GpCJ9Wmy8d-tXkKIg89FeogBAZGks5ui5T1gaJpZM4XNbK_
.


pre-commit: PR118458

Link: https://github.com/llvm/llvm-project/pull/118458
Requested by: @dtcxzyw

/add-label regression


chore(main): release 0.19.1

:robot: I have created a release beep boop
0.19.1 (2023-08-02)
Bug Fixes

quadxwaypointscost: fix quadxwaypointscost observation space shape bug (#282) (0bf6ebd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rickstaa/stable-gym/releases/tag/v0.19.1 :sunflower:


Docs: Plugins Overhaul

This is an overhaul of the plugins section for the Amplication documentation. The old version had pages spread between the Getting Started, How To, and Plugin Development sections. The fact that so many pages were spread out made it harder to navigate.
This new version combines all Plugin-related content under a single new section "Plugins". This should make it much easier for developers to navigate. Sections are re-written and the appropriate links to sections like the Custom Plugin Architecture section, and the Event Reference are more clear.
All URLs remain the same so all existing links to the docs will be OK.
This PR takes care of #368

LGTM

Hi @GreenMachine01, call of your feedback has been implemented in this commit. Can I move the associated issue to Waiting For Dev Review or Waiting For Merge?

@dericksozo please resolve conflicts here


Understanding this library

Hi.
I'm playing with node-red-contrib-blynk-websockets and a Arduino MKR. I have a question.
If I inject for example a number to a virtual pin from node-red, this value will be send to app, to arduino or to the two at same time?
I need switch on-off a output directly from node-red, without app.
Regards,
Jaume Nogues
rPrim Tech School
Barcelona

hi,
this is meant to replace the arduino device in the chain so you can t trigger directly another device
use http requsts or mqtt to communicate from node red to the device, and the contrib between node red and blynk server/app
i hope this helps

Thanks tzapu!! Help me a lot!!


Travis integration

It builds the library and pass the tests.
It also deploys automatically to bintray on every new tag.

I've tested it on a fork and works fine.
@cristiangarciascmspain it's only missing the credentials for bintray as environment variables: BINTRAY_USER and BINTRAY_KEY. Can you add them? Either in the travis file as encrypted variables, or through the web interface settings.


Replace all from ... export all with explicit exports

Follow-up of #10274. Partially fixes #10258, https://github.com/enso-org/enso/issues/6729, #9236
Pull Request Description
Replaces all from ... export all with explicit by-name exports.
Important Notes

Remove isAll and hiding fields from Export IR
Static or extension method can be imported by name
Simplify exports resolution algorithm
A new ConflictingResolutionsError compiler error is thrown when there are conflicting resolutions in a module.
For exmple, a conflicting resolution is a type defined in the module that has the same name as a different submodule.
Previously, this was reported as a warning, but it would now cause issues for the export resolution, so an error is thrown earlier.
Add a lot of tests for BindingsMap.
Add tests for various steps of ExportsResolution.

We used to have 0 unit tests for this, as well as for BindingsMap.

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[x] Unit tests have been written where possible.

Failing tests:

forgotten closed file prevents delete of directory on windows
SuggestionBuilderTest fails on all platforms
RuntimeSuggestionUpdateTest fails on all platforms
I am not sure what No_Such_Method error means?

Close, so close...

There is not enough time to run proper benchmarks before integration. But I have at least run some benchmarks locally (lower score is better - ms/op):

Benchmark name
Old score
New score

ImportStandardLibrariesBenchmark
219
58

ManyErrorsBenchmark
77
74

ManyLocalVarsBenchmark
32
25

ManyNestedBlocksBenchmark
51
46

ManySmallMethodsBenchmark
114
106

Moreover, local experiments with running
enso --no-compile-dependencies --no-global-cache --no-ir-caches --no-read-ir-caches --compile Base

revealed that compilation of Standard.Base now takes 6 seconds, versus the old 31 seconds.