invalid curve name after brew upgrade?

New Issue Checklist

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

Issue Description
After running fastlane for several months on my local machine without any issues, today it suddenly failed with invalid curve name.
Digging into the code, I found that the call to OpenSSL::PKey::EC.new(key) caused the issue. I tried to hard code the value of my key, which fixed the problem. The value of the hardcoded key the string representation of the key, while the original argument seems to be is an instance of OpenSSL::PKey::EC.
Printing the value of the key renders:
<OpenSSL::PKey::EC:0x000000010960b1e8>
I did run a brew upgrade earlier this morning, and the problem seems to start after I did that.
Command executed

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

 [REPLACE THIS WITH YOUR INFORMATION]

Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
12.4

Ruby
3.1.2

Bundler?
false

Git
git version 2.37.2

Installation Source
/opt/homebrew/Cellar/fastlane/2.209.0/libexec/bin/fastlane

Host
macOS 12.4 (21F79)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.1.2/lib

OpenSSL Version
OpenSSL 1.1.1n  15 Mar 2022

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

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

Xcode Version
13.4.1

Swift Version
5.6.1

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
default_platform(:ios)

platform :ios do
  desc "Build and upload dev version of app"
  lane :dev do
    api_key = app_store_connect_api_key(
      key_id: ENV['APP_STORE_KEY_ID'],
      issuer_id: ENV['APP_STORE_ISSUER_ID'],
      key_content: ENV['APP_PRIVATE_KEY']
    )

    bump_version
    build_app(scheme: "XXX-Development")
    upload_to_testflight(app_identifier: "xx.dev")

  end

  desc "Build and upload prod version of app"
  lane :prod do
    api_key = app_store_connect_api_key(
      key_id: ENV['APP_STORE_KEY_ID'],
      issuer_id: ENV['APP_STORE_ISSUER_ID'],
      key_content: ENV['APP_PRIVATE_KEY']
    )

    bump_version
    build_app(scheme: "XXX")
    upload_to_testflight(app_identifier: "xx.app")
  end

  desc "Get certificates"
  lane :certificates do
    sync_code_signing(
      type: "development",
      force_for_new_devices: true,
      readonly: true
    )

    sync_code_signing(
      type: "appstore",
      readonly: true
    )
  end

  lane :bump_version do
    increment_build_number
    commit_version_bump
  end
end

`./fastlane/Appfile`
app_identifier(["xx.app", "xx.dev"])
itc_team_id "999999999"
team_id "7788778877878"

fastlane gems

Gem
Version
Update-Status

fastlane
2.209.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

atomos
0.1.3

rexml
3.2.5

CFPropertyList
3.0.5

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.22.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.7

addressable
2.8.0

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

excon
0.92.4

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

json
2.6.1

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.8.1

bundler
2.3.11

simctl
1.6.8

jwt
2.4.1

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.2.0

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.2.0

httpclient
2.8.3

webrick
1.7.0

google-apis-core
0.7.0

google-apis-playcustomapp_v1
0.10.0

google-apis-androidpublisher_v3
0.25.0

google-cloud-env
1.6.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.13.0

google-apis-storage_v1
0.17.0

rake
13.0.6

digest-crc
0.6.4

google-cloud-storage
1.38.0

emoji_regex
3.2.3

jmespath
1.6.1

aws-partitions
1.617.0

aws-eventstream
1.2.0

aws-sigv4
1.5.1

aws-sdk-core
3.132.0

aws-sdk-kms
1.58.0

aws-sdk-s3
1.114.0

set
1.0.2

forwardable
1.3.2

logger
1.5.0

pathname
0.2.0

shellwords
0.1.0

cgi
0.3.1

date
3.2.2

timeout
0.2.0

stringio
3.0.1

securerandom
0.1.1

uri
0.11.0

openssl
3.0.0

digest
3.1.0

io-nonblock
0.1.0

ipaddr
1.2.4

io-wait
0.2.1

zlib
2.1.1

resolv
0.2.1

time
0.2.0

open-uri
0.2.0

mutex_m
0.1.1

net-protocol
0.1.2

net-http
0.2.0

ostruct
0.5.2

english
0.7.1

erb
2.2.3

strscan
3.0.1

abbrev
0.1.0

io-console
0.5.11

tempfile
0.1.2

delegate
0.2.0

fileutils
1.6.0

tmpdir
0.1.2

base64
0.1.1

singleton
0.1.1

open3
0.1.1

nkf
0.1.1

prettyprint
0.1.1

pp
0.3.0

find
0.1.1

yaml
0.2.0

psych
4.0.3

generated on: 2022-08-12

 [REPLACE THIS WITH YOUR INFORMATION]

Also can confirm that. I'm using the same Using fastlane 2.209.0 version and tried everything but error is still the same

`[12:52:03]: ------------------------------
[12:52:03]: --- Step: default_platform ---
[12:52:03]: ------------------------------
[12:52:03]: Driving the lane 'ios closed_beta' 🚀
[12:52:03]: -----------------------------
[12:52:03]: --- Step: delete_keychain ---
[12:52:03]: -----------------------------
[12:52:03]: -----------------------------
[12:52:03]: --- Step: create_keychain ---
[12:52:03]: -----------------------------
[12:52:03]: $ security list-keychains -d user
[12:52:03]: ▸ "/Users/vitaliikizlov/Library/Keychains/login.keychain-db"
[12:52:03]: ---------------------------------------
[12:52:03]: --- Step: app_store_connect_api_key ---
[12:52:03]: ---------------------------------------
+------------------+----------------------------+
|                 Lane Context                  |
+------------------+----------------------------+
| DEFAULT_PLATFORM | ios                        |
| PLATFORM_NAME    | ios                        |
| LANE_NAME        | ios closed_beta            |
| KEYCHAIN_PATH    | ~/Library/Keychains/Quartr |
+------------------+----------------------------+
[12:52:03]: invalid curve name
+------+---------------------------+-------------+
|                fastlane summary                |
+------+---------------------------+-------------+
| Step | Action                    | Time (in s) |
+------+---------------------------+-------------+
| 1    | default_platform          | 0           |
| 2    | delete_keychain           | 0           |
| 3    | create_keychain           | 0           |
| 💥   | app_store_connect_api_key | 0           |
+------+---------------------------+-------------+
[12:52:03]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡   invalid curve name after brew upgrade?
https://github.com/fastlane/fastlane/issues/20553 [open] 1 💬
a week ago
➡  Pilot fails using environment variables on GitHub
https://github.com/fastlane/fastlane/issues/18655 [closed] 13 💬
09 May 2022
➡  Pilot and deliver fails with "string contains null byte"
https://github.com/fastlane/fastlane/issues/18312 [closed] 7 💬
12 Jul 2021
and 4 more at: https://github.com/fastlane/fastlane/search?q=invalid curve name&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
bundler: failed to load command: fastlane (/usr/local/bin/fastlane)
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/spaceship/lib/spaceship/connect_api/token.rb:71:in initialize': [!] invalid curve name (OpenSSL::PKey::ECError) 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/spaceship/lib/spaceship/connect_api/token.rb:71:in new'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/spaceship/lib/spaceship/connect_api/token.rb:71:in create' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/actions/app_store_connect_api_key.rb:43:in run'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:229:in chdir'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:229:in execute_action' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing' 	from Fastfile:54:in block (2 levels) in parsing_binding'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:45:in chdir' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/runner.rb:45:in execute'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/commands_generator.rb:110:in block (2 levels) in run' 	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!' 	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/commands_generator.rb:354:in run' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/commands_generator.rb:43:in start'
from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in take_off' 	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.209.0/bin/fastlane:23:in <top (required)>'
from /usr/local/bin/fastlane:23:in load' 	from /usr/local/bin/fastlane:23:in <top (required)>'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli/exec.rb:58:in load' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli/exec.rb:58:in kernel_load'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli/exec.rb:23:in run' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli.rb:485:in exec'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli.rb:31:in dispatch'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/cli.rb:25:in start'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/exe/bundle:48:in block in <top (required)>' 	from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/lib/bundler/friendly_errors.rb:120:in with_friendly_errors'
from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.20/exe/bundle:36:in <top (required)>' 	from /usr/local/bin/bundle:23:in load'
from /usr/local/bin/bundle:23:in <main>'

I had the same error.
I did a workaround where i used a filepath to the actual .p8 file instead..

@bonkowski  Did you get any workaround for it? I too was facing the similar issue.

Well, to not get stuck, I edited the token.rb and assigned the value of my private key into the key variable after line 62 🤦🏻♂

You can use is_key_content_base64 from fastlane. app_store_connect_api_key which does not show the same error as the non-base64 version.
app_store_connect_api_key(
  key_id: "D83848D23",
  issuer_id: "227b0bbf-ada8-458c-9d62-3d8022b7d07f",
  key_content: "Base64_encode_of_-----BEGIN EC PRIVATE KEY-----\nfewfawefawfe\n-----END EC PRIVATE KEY-----",
  is_key_content_base64: true
)

Nevertheless it's a workaround, thanks to @blyscuit , I made it work.

Is there any progress with this?
We are having issues with this for a last 2 or 3 weeks.
/usr/local/lib/ruby/gems/3.1.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/token.rb:71:in initialize': \e[31m[!] invalid curve name\e[0m (OpenSSL::PKey::ECError) 	from /usr/local/lib/ruby/gems/3.1.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/token.rb:71:in new'
from /usr/local/lib/ruby/gems/3.1.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/token.rb:71:in `create'

I got the similar error
/Users/me/.gem/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/token.rb:71:in `initialize': \e[31m[!] invalid curve name\e[0m (OpenSSL::PKey::ECError)

In my case, I feed the key using the env variable which has the error:
APP_STORE_CONNECT_API_KEY_KEY=-----BEGIN PRIVATE KEY----\nbalalllaalal\n-----END PRIVATE KEY-----
And it works after adding the double quote:
APP_STORE_CONNECT_API_KEY_KEY="-----BEGIN PRIVATE KEY----\nbalalllaalal\n-----END PRIVATE KEY-----"
Hope this help or is a clue to fix the issue.

I got similar error.
Make sure the APP_STORE_CONNECT_API_KEY_KEY has the trailing \n.
In my case, we store the key in a Password Manager and clicking copy on the field doesn't copy some \n.
This is the ruby code that throw this error. For those who faced this issue, you can try this in your irb until you figure out what is wrong with your key.
OpenSSL::PKey::EC.new(key)

In our project, we've chosen to safeguard the .p8 key file by storing it within Azure KeyVault as a secret. To effectively manage the key while ensuring it remains unaltered, we've adopted a base64 encoding strategy prior to its storage. The steps to reproduce our approach are detailed below:
Storing the .p8 Key File in Azure KeyVault:
Step 1: First, base64 encode the key file:
base64 -i ios/AuthKey_ABCDEFGH.p8 > encoded.txt

Step 2: Manually copy the content from encoded.txt and save it as a secret within Azure KeyVault.
Retrieving and Decoding the Key within a GitHub Actions Workflow:
Step 1: Fetch the base64-encoded key from Azure KeyVault:
az keyvault secret show --name <SECRET_NAME> --vault-name <KEYVAULT_NAME> --query "value" | tr -d '"' > encoded.txt

Step 2: Decode the fetched base64 content to retrieve the original .p8 key:
base64 -D -i encoded.txt > ios/AuthKey_ABCDEFGH.p8

I am Stuck any solution?

In my case, when i user secrect text I have copy value with space value in file.p8 content.
key="-----BEGIN PRIVATE KEY----- MIGTAgEAMBMGByqGSM49A  A3tpef3sl6souQaTH5ChJqxP66g RduSthcXm/tfQW+/Ciln8hhrF5WgDJvV+UligFE4A6MeUmI9l0eb ESY8YIqO -----END PRIVATE KEY-----"
I resolved it by replacing spaces with \n, and it worked perfectly for me.


Disallow batch insert on SQLite

Related to #157. Whether this functionality is eventually added back is
out of scope for 0.5. What is clear is that we need to fix the single
record case on SQLite, and that we cannot safely insert multiple records
in a single query on SQLite.
This does not fix the single record case, and does not resolve the
issue. However, the actual solution to that will be much more complex,
and this is comparatively simple -- and will be a pre-requisite for any
solution to the actual issue.

Review? @mcasper @mfpiccolo @samphippen


Revert "implement per_repo_quota"

Reverts jupyterhub/binderhub#370
This seems to have broken our banning behavior, so
reverting for now.

/cc @minrk @betatim


Change line ending in Rename-Computer.Tests.ps1 to LF

There are CRLF line ending sequences in this file and it shows as modified after a sync on my Linux machine.

Use https://github.com/PowerShell/PowerShell/pull/5314/files?w=1 to view the diff after ignoring the whitespace changes.

Heh, I ran into this very issue last night.


Fixed incorrect error message in Calculate activity

Fixes #798
This error occurs as inside calcEqualClick function only treats f(x) as a graph equation and all other as equations to solve. So when we enter any variable other than x it tries to solve it using the launchCalculation function instead of the launchGraph function and return error when unable to solve it.
In the fix, I have added a check for graph equations in launchCalculation function, if it is a graph equation it will return from the function along with the error in the display.
Preview:

Hmmm. Very specific fix. May be it could be possible to catch error in a more generic way?

@llaske We can use regex /f\(.*\)=[\w]+/ to catch error in more generic way. It will look for f( and )= in the expression.
If this looks good to you, I will update the PR.

Okay but my question was more generic. Is it the only error that could happen during expression evaluation?
I don't want to create a specific code for each possible error type.
Is it possible to do something like a more global try/catch?

I checked the functions for different errors. There is already a try/catch present which is handling the maximum general errors. This error is specific and returns directly from try block with an error in the console.

It only detects x as an argument. So when there is a variable with x  like f(x+y) then it is handled by try/catch itself. This case is specific when no x variable is present inside f() then it takes the number of arguments as 0 inside f() and returns above mentioned error in the console.

@saurabhhere I think it's possible to add a try/catch section around the mustache.render then raise a generic error if something goes wrong.

Yes, I agree we can add a try/catch around the mustache.render, but there are three mustache.render for which we have to use try/catch instead I was thinking to add try/catch block around displayCalculation so if anything goes wrong inside displayCalculation it will raise a generic error.
Preview of try/catch around displayCalculation:

What do you think about this?

Why not? But in that case try/catch could be also be inside the displayCalculation method.
It will avoid to have some calls with try/catch and some calls without try/catch.
We should just ensure that in any case displayCalculation will display a result or an error message.

So should I add try/catch around both displayCalculation and mustache.render to ensure that every time it displays a result or an error message

Hmmm. No, I guess inside the displayCalculation method, it should be enough.


CASSANDRA-14903 fixing nodetool cfstats printing index name twice

Hi @michaelsembwever
I am not sure what output we want here. I just put together what Ian did for CASSANDRA-14903, it looks all consistent to me in sorted output too.
Could you please review that and let me know?
Thanks a lot!

you're correct smiklosovic . i didn't notice that keyspace always gets prepended to the name when in sorted mode.
i will commit the patch as is.


Build out a framework for Go Kafka Client on Mesos

Under development https://github.com/stealthly/go_kafka_client/tree/mesos-framework/mirrormaker

I want to help in contributing to this project. However, I should warn you, I have only (some) theoretical knowledge of mesos, aurora, frameworks. I have used Storm and Kafka, & am a beginner in GoLang.

We could always use more help testing, maybe that is a good place to start to learn more about how it works too

Thanks, Joe.
I am up for that. Can you tell me what all with this involve?
I do not want to do a messed up job.
Are you on IRC to discuss this?
--
κρισhναν
On Wed, Sep 23, 2015 at 1:05 AM, Joe Stein<EMAIL_ADDRESS>wrote:

We could always use more help testing, maybe that is a good place to start
to learn more about how it works too
—
Reply to this email directly or view it on GitHub
https://github.com/stealthly/go_kafka_client/issues/155#issuecomment-142394773
.


Explain context managers in greater detail

Fix #107.

It probably makes some sense to rename read to open here.  Use of open will always require a context manager, since the file needs to remain open to memmap the data.  For that reason, I don't think it makes sense for write_to to not require a context manager, even if we could detect that case, because it creates an asymmetry between open and write_to that will be difficult to remember.
Obviously there's some confusion around this but it's not yet clear to me how to objectively improve the situation.

Closing in favor of #118.


Provide guidance re: twilio Sender ID registration in Hong Kong

Relevant slack thread
Twilio sent an email indicating that attestation services need to either register a Sender ID (takes 3 weeks) or purchase an HK domestic phone number in order to send SMS's there. It's possible that the Verify API is a workaround for this, but we haven't gotten confirmation from twilio that this is the case (they recommend either purchasing a domestic number or registering an alphanumeric Sender ID).
For this ticket we should:

[ ] identify if the Verify API is a workaround here. Analyze the data that we have on this --  how well does twilio verify perform after Jan 1st vs. before?
[ ] if the Verify API is not a valid workaround, come up with instructions for registering Sender ID's (should all validators register their own Sender ID's? Should we instead recommend that they use something generic and unified like "Celo Validator", or does that increase the risk of users getting scam texts and having all validator SMS's blocked?)
[ ] communicate with validators on what steps they need to take
[ ] follow-up on support ticket with twilio

Looked into this briefly and followed up with twilio support to see if they have more data on Verify performance.
From our data, it looks like Verify is performing well (100% completion on the 44 attempts we have, not a large sample), but so is the twilio messaging service (90% of the 20 messages). We should keep an eye on this but don't urgent action on this.

Update: new email communicated effective blocking date as March 1, 2022. Not enough data to tell so far; no messages blocked yet. Continue keeping an eye on this, especially as we get more data later in March.


Destruct ConptyConnection on a background thread

This commit leverages C++/WinRT's final_release extension point to
pull the final destruction of ConptyConnection off onto a background
thread.
We've been seeing some deadlocks during teardown where the output thread
(holding the last owning reference to the connection) was trying to
destruct the threadpool wait while the threadpool wait was
simultaneously running its callback and waiting for the output thread to
terminate. It turns out that trying to release a threadpool wait while
it's running a callback that's blocked on you will absolutely result in
a deadlock.
Fixes #7392.

@msftbot merge this in 1 minute


Optimize service instances SQL query efficiency

Service instances cannot have duplicate values due to the primary key constraint on GUID, so using distinct is not only redundant but also affects query performance.
Co-authored-by: @shahnavaz

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

@sethboyles, thanks for your feedback. At least we improved test coverage. We will keep iterating on this PR to find alternative ways to improve query performance. Our current goals are:

[must] Find possible SQL optimizations for service instances query.
[attractive] Keep it SQL dialect agnostic.

@a-b Perhaps you could close this and if you have suggestions for optimizations create a new PR for them?


MAINT: get rid of some compiler warnings

uninitialized pointer
unused variables
unused function
ISO C prototypes
cimport *
useless cast before snprintf

Thanks for looking into this.
What compiler are you using? I may have a chance to try it out with clang.

GCC 4.7.

can you rebase this?

@jreback done.

can you quantify I guess how many warnings this removed? (as obviously still lots)

I don't know, four? The code has moved on since I wrote this patch and I have no idea how many new warnings were introduced.

this looks ok, but to be sure, can you rebase and push again?

Green!

thanks!


Possibility to view/show all / more aspect models that are connected to a digital twin

As user of trace-xr
I want to view further aspect models that are connected to a digital twin within the trace-x application
so that I have a transparency of which aspects or existing within the digital twin
Link

relates to https://github.com/eclipse-tractusx/traceability-foss/issues/710

Hints / Details
-Use code highlighting for json plain viewer

-https://miro.com/app/board/uXjVO5JVoho=/?moveToWidget=3458764570265682145&cot=14
Outcome

[x] https://github.com/eclipse-tractusx/traceability-foss/issues/710
[x] https://github.com/eclipse-tractusx/traceability-foss/issues/711

Acceptance Criteria

[x] concept ready for implementation
[x] user stories for backend and frontend created
[x] decision on where to visualize it in frontend done incl. mock-up

Requirements:

[x] Semantic models linked to an asset are shown in the detail area
[x] Semantic model is shown in plain JSON plan-text structure viewer with Json code highlighting
[x] Semantic model is shown in plain tree structure (JSON Tree Viewer)
[x] Semantic model is shown in plain graph view structure (https://jsoncrack.com/)
[x] Detail View is extended with section "other semantic models connected to the Twin)

[x] Master (Semantic Model ) / Detail JSON Viewer (JSON Viewer representation could be switched between Plain/Highlighted / Tree and Graph View )

[x] Additional semantic models are shown in the master detail view

Out of Scope

Working directory

https://github.com/catenax-ng/tx-traceability-foss/tree/chore/%23435-concept-show-aspect-models-conntected-to-aas

some tasks on #710 to refactor FE Design

Done -> https://github.com/eclipse-tractusx/traceability-foss/issues/710


Review Extract design

(moved from https://code.google.com/p/solrnet/issues/detail?id=194 https://code.google.com/p/solrnet/issues/detail?id=79 )
The design of ExtractParams isn't completely consistent and needs some review. See https://groups.google.com/d/topic/solrnet/2_zwuMVQJ6o/discussion https://code.google.com/p/solrnet/issues/detail?id=79#c15

Current issue has been closed as part of cleanup process, which is tracked in https://github.com/SolrNet/SolrNet/issues/338.
Please reopen if needed, hopefully helping bringing up to date with current code.


Code lenses with unresolved commands show up as !!MISSING: command!!

Does this issue occur when all extensions are disabled?: Yes
A code lens with no command shows up as !!MISSING: command!!.
This is clearly deliberate, see the implementation and the test for the behaviour.
However, this interacts badly with codeLens/resolve. If the resolve request fails (for example, if the document has been changed such that the old lens is now stale), then the code lens will still appear with !!!MISSING: command!!, even though this is "normal" operation.
The behaviour I would expect is for the code lens not to be displayed in this case. The current behaviour makes a lot of sense for simple code lens providers that don't rely on codeLens/resolve, since in that case not providing a command is questionable and it's useful for it to show up obviously. But in the case where we've resolved the lens and got a failure, I think it would make much more sense to just not display the lens.
This was discovered by a user of the Haskell Language Server after we implemented codeLens/resolve: https://github.com/haskell/haskell-language-server/issues/3827b

VS Code Version: I don't know what the user was using, but the behaviour is clearly present in the source code on master
OS Version: ditto

Steps to Reproduce:

Write a code lens resolve handler that fails
Observe ugly lenses

The behaviour I would expect is for the code lens not to be displayed in this case. The current behaviour makes a lot of sense for simple code lens providers that don't rely on codeLens/resolve, since in that case not providing a command is questionable and it's useful for it to show up obviously. But in the case where we've resolved the lens and got a failure, I think it would make much more sense to just not display the lens.

We don't remove these lenses to not introduce flicker (all lines would shift up by a little). I agree that today's fallback isn't great, a dash might be better, but it should also be clear that the extension should always try to resolve successfully and that failure is pretty bad here (because the UI space for code lense commands is already reserved)

Decided to go with the (existing) "no commands" rendering but we will also start to log extension errors for this

Just one thought: what about simply blank space? So we'd have the space in the UI, which would look a little odd, but we wouldn't be forcing what is ultimately a diagnostic message into the user's face unless they look in the log.

I experimented with that but kinda looks like a rendering glitch and you keep staring at it waiting for an update


Add Support to define INITIAL_TEMPERATURE_SET

📝 Description of the feature
Support initial temperature cards. Especially INITIAL_TEMPERATURE_SET
💡 Steps for implementing the feature
*INITIAL_TEMPERATURE_SET
$#    nsid      temp       loc
0        25         0
🔗 Useful links and references
No response

0.4.0 supports it now


Milestone 7: posts, comments and likes forms.

Pull Request Summary for Milestone 6 Completion

[x] All requirements completed.

Added:
/app/controllers/comments_controller.rb

Created the CommentsController class.
The new action will set the @comment and @user variables.
The create action will handle the creation of a new comment, flash messages, and redirects to the posts#index view in case of success.
Created a private method comment_params to handle the strong parameters for the Comment model.

/app/controllers/likes_controller.rb

Created the LikesController class.
The create action will handle the creation of a new like, flash messages, and redirects to the posts#index view in case of success.

/app/views/posts/new.html.erb

The posts#new view facilitates the creation of a new post.
It incorporates a form structure that makes use of the inputs_group partial to render the form fields for creating a new post.

/app/views/shared/_inputs_group.html.erb

This partial is very convenient for rendering the form fields for creating a new post or for being used in the comments form.

Modified:
/README.md

Marked the forms task as completed.
Added instructions for populating the database with seed data.

/config/routes.rb

Added a route for the posts, comments, and likes resources.

Note: At the moment the user can only comment and like posts at the posts#show view.

/db/seeds.rb

Added seed data for users, posts, and comments using the faker gem.

/app/controllers/application_controller.rb

Added the current_user helper method to be used in the views.

This method is returning the first user in the database for now.

/app/controllers/posts_controller.rb

Modified the show action to include the @user and @like variables.
Modified the new action to include the @post and @user variable.
Modified the create action to handle the creation of a new post, flash messages, and redirects to the posts#index view in case of success or the posts#new view in case of failure.
Created a private method post_params to handle the strong parameters for the Post model.

/app/views/layouts/application.html.erb

Added flash messages to the layout.

/app/views/posts/index.html.erb

I have just added the new button_link partial's local button_type variable set to 'success' to the pagination button.

/app/views/posts/show.html.erb

I have added two forms:

The comments form.
The likes form.

The comments form makes use of the inputs_group partial to render the form fields.

/app/views/users/show.html.erb

I have just added the new button_link partial's local button_type variable set to 'success' to the See all posts button.

Thank you for reviewing this PR. Feel free to reach out on Slack as Arturo (Arthur) Emanuel Guerra Iturres for any queries or further assistance. 🌟

Hi @zieeco!, thank you so much for having reviewed this PR 🤠, wish you a great week and happy programming! 👨🏼💻


Investigate, and if possible remove, need to fetch all management clusters on load

SURE-7040

In cases where there are LOTS of clusters this has a large impact on load of every page (10+ seconds)
We need to understand why we need all mgmt clusters (guessing at least the burger menu) and try to address each

For the burger menu, we should be able to use the new pagination api to filter results to get the required max clusters to show

@richard-cox problem is a good part of that slowness comes from Steve's need to fetch the whole collection from Kubernetes. Even if we could filter the results in Steve, the actual endpoint will likely be slow.
Do you see any option to avoid the fetch altogether? Or is it needed in many other places besides the hamburger menu?


[#557] MSSQL discovery script

Purpose
This PR adds a script to explore the schemas of databases within a MSSQL master instance.
Checklist

[x] Update CHANGELOG.md file

[x] Merge in main so the most recent CHANGELOG.md file is being appended to
[x] Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
[x] Add a link to this PR at the end of the description with the PR number as the text. example: #1

[ ] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
If docs updated (select one):

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[ ] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket
Fixes #557

bunch of tests are failing, but they all look like frontend tests. I don't think they are relevant to your PR?

Those failures are left over from the Github Actions downtime


Train 331

Added following PRs:
#1914: Support adding custom check executables during on-prem installation

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot bump-ee


Translate the demo app to english

Hey it would be cool to have the demo app in english. I think that would help the app and a lot of users of your library.

Yeah, i will soon translate the Demo to English  :)

cool thanks for that
only a quick question and i don't want to bomb you with issues, but i couldn't find a solution till now.
i want to switch to another fragment from my viewmodel. I use databinding mvvm. Can you help me?

In googlesamples, another fragment is switched by View(Fragment):
RepoFragment and NavigationController

🍺🍺   Translate the demo app to english


Model checkpoints uploading

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Devices in manually overridden rings

If I manually reassign a device between groups (say, from first to broad) will it be reassesssed and possibly moved back during the Autopatch ring assement later on? Covering this part either in this page or in FAQ's or in the flow diagrams will help customer understand much clear picture.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e020994f-a009-87f6-6761-097218d01813
Version Independent ID: e020994f-a009-87f6-6761-097218d01813
Content: Software update management - Windows Deployment
Content Source: windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
Product: windows-client
Technology: itpro-updates
GitHub Login: @tiaraquan
Microsoft Alias: tiaraquan

I know this is for a different article, but looks to be essentially the same feedback as #11379, so I'm closing this issue as a duplicate


VIRTual BLocK IOFIOing: 4k-random libaio tests

The fio block device test to run 4k-random read operations through the libaio backend.
The fio block device test to run 4k-random write operations through the libaio backend.
The fio block device test to run compound 4k-random read/write operations through the libaio backend.

:+1: She looks good!


x/tools/gopls: plan for vendoring in multi-module workspaces

As previously discussed, we have not yet accounted for modules that use vendoring in the workspace module design. As of https://golang.org/cl/259623, the workspace module will be enabled for modules that have vendor directories, but the vendor directories will be ignored.
@heschik investigated the possibility of creating a workspace module vendor directory by combining the vendor directories of all of the modules in the workspace, but this doesn't seem to be a feasible approach.
If we choose to simply ignore vendor directories, we must first resolve https://github.com/golang/go/issues/41819. We might also consider using the default mode if we only detect one module in the workspace, as the workspace module will offer no advantage in that case.

This is now subsumed by the go.work proposal: https://github.com/golang/go/issues/45713.


Hevc/x265 freez sometimes in playback

Hi, I have change this commit: 02b3be1 but nothings changed..
when I tried to play a Hevc video sometimes freez and then play again.
here is my video info:
Format                         : Matroska
Format version                 : Version 2
File size                      : 242 MiB
Duration                       : 41mn 40s
Overall bit rate               : 811 Kbps
Encoded date                   : UTC
Writing application            : HandBrake 0.10.2<PHONE_NUMBER>
Writing library                : Lavf55.12.0
Video
ID                             : 1
Format                         : HEVC
Format/Info                    : High Efficiency Video Coding
Format profile<EMAIL_ADDRESS>Codec ID                       : V_MPEGH/ISO/HEVC
Width                          : 1 280 pixels
Height                         : 720 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Variable
Original frame rate            : 23.976 fps
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Default                        : Yes
Forced                         : No
Audio
ID                             : 2
Format                         : AAC
Format/Info                    : Advanced Audio Codec
Format profile                 : HE-AAC / LC
Codec ID                       : A_AAC
Duration                       : 41mn 40s
Channel(s)                     : 2 channels
Channel positions              : Front: L R
Sampling rate                  : 48.0 KHz / 24.0 KHz
Compression mode               : Lossy
Delay relative to video        : -105ms
Title                          : Stereo
Default                        : Yes
Forced                         : No
here is the current video link:
http://dl2.film2movie.biz/serial/The Flash/S02/The.Flash.S02E16.720p.x265.HEVC.Film2Movie_INFO.mkv
Thanks

Hi,
does it freeze at a particular timestamp ?

Hi, thank you for reply
yes, here examples time:(2,6,9,19 sec)
00:00:02 and 00:00:06 and 00:00:09 and 00:00:19
in your MediaPlayerCS is too.
how can I fix this?

Hi,
I wonder if "Sampling rate : 48.0 KHz / 24.0 KHz" can have something to do with the issue you encountered.
I don't know what it means but I hope it is not L/R sample rate !
I experienced differently the playback this sample. It freezed, but only after showing people moving at lighting speed, all of them, and with uncompressed audio sample playback it plays well on my side.
Can you try it again and report about any change ?

Hi again,
I tested with Uncompressed audio sample too, still not working and still it's freezing

I find it strange you don't mention anything being better or worse with compressed vs. uncompressed audio samples playback. No offense, but I have to ask you again if you enabled "Force Decode Audio" during your tests.
I can confirm there is an issue within FFmpegInterop with he-aac audio when playing compressed samples, which is quite easy to fix actually.
On my side, using a windows 10 desktop, the file plays very fast with bad audio until something gives up a few seconds later and freezes. You might have less processing power than me and experienced it differently. What is your platform and how are x265 480p and 1080p playback on your side ?

Hi, sorry I forgot to tell you, when I force decode audio (using uncompressed), audio going to fast on blu-ray video. (so getting worse , but freezing still have!). when I disable this option and play this video, audio works well.
Note: I set sample bitrate to 16 so I don't think it's because of this.
I have Windows 10 Pro x64 build 14342 on PC and Windows 10 Mobile build 10.0.14328.1000 on my phone.
On PC after few seconds will freezes but on phone each frame getting freezes and play. so I think there isn't on my side.
HEVC Blu-ray 1080,720 and 480p freezes
I think the issue is Blu-ray video, I played a WebDL 720p HEVC video, plays very well:
http://onmkv.net/download-alt.php?id=YUhSMGNEb3ZMMVJ5WVdsdVltbDBMbU52YlM5bWFXeGxjeTh6TlRRek1qYzNPRGcwTDBGdVpISnZiaTR5TURFMUxqY3lNSEF1VjBWQ0xVUk1Mbmd5TmpVdVNFVldReTFQVGsxTFZpNXRhM1k=
and I played this video (HDTV 480 HEVC) and plays very well:
General
Format                         : Matroska
Format version                 : Version 4 / Version 2
File size                      : 88.4 MiB
Duration                       : 42mn 30s
Overall bit rate               : 291 Kbps
Movie name                     : PSArips.com | Arrow.S03E22.SD.HDTV.2CH.x265.HEVC-PSA
Encoded date                   : UTC 2015-05-07 04:51:07
Writing application            : mkvmerge v7.8.0 ('River Man') 64bit built on Mar 27 2015 16:31:37
Writing library                : libebml v1.3.1 + libmatroska v1.4.2
DURATION                       : 00:42:25.085000000
NUMBER_OF_FRAMES               : 776
NUMBER_OF_BYTES                : 22819
_STATISTICS_WRITING_APP        : mkvmerge v7.8.0 ('River Man') 64bit built on Mar 27 2015 16:31:37
_STATISTICS_WRITING_DATE_UTC   : 2015-05-07 04:51:07
_STATISTICS_TAGS               : BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Video
ID                             : 1
Format                         : HEVC
Format/Info                    : High Efficiency Video Coding
Format profile<EMAIL_ADDRESS>Codec ID                       : V_MPEGH/ISO/HEVC
Width                          : 720 pixels
Height                         : 408 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Variable
Original frame rate            : 23.976 fps
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Default                        : Yes
Forced                         : No
DURATION                       : 00:42:29.714000000
NUMBER_OF_FRAMES               : 61132
NUMBER_OF_BYTES                : 76799368
_STATISTICS_WRITING_APP        : mkvmerge v7.8.0 ('River Man') 64bit built on Mar 27 2015 16:31:37
_STATISTICS_WRITING_DATE_UTC   : 2015-05-07 04:51:07
_STATISTICS_TAGS               : BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Audio
ID                             : 2
Format                         : AAC
Format/Info                    : Advanced Audio Codec
Format profile                 : HE-AAC / LC
Codec ID                       : A_AAC
Duration                       : 42mn 30s
Channel(s)                     : 2 channels
Channel positions              : Front: L R
Sampling rate                  : 48.0 KHz / 24.0 KHz
Compression mode               : Lossy
Delay relative to video        : -105ms
Title                          : Stereo
Default                        : Yes
Forced                         : No
DURATION                       : 00:42:30.101000000
NUMBER_OF_FRAMES               : 59768
NUMBER_OF_BYTES                : 15300609
_STATISTICS_WRITING_APP        : mkvmerge v7.8.0 ('River Man') 64bit built on Mar 27 2015 16:31:37
_STATISTICS_WRITING_DATE_UTC   : 2015-05-07 04:51:07
_STATISTICS_TAGS               : BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Text
ID                             : 3
Format                         : UTF-8
Codec ID                       : S_TEXT/UTF8
Codec ID/Info                  : UTF-8 Plain Text
Default                        : Yes
Forced                         : No
Here :
http://up.hidiaries1.ir/download/305328/Arrow.S03E22.SD.HDTV.2CH.x265.HEVC.rar

Interesting. Does it mean he-aac decoder changed in build 14342 ?
Back to your video issue, would you have a sample of freezing Bluray 480p video ?

Also, a sample of audio going too fast using uncompressed would be nice as the might be another issue here.

If we ignore the audio issues with he-aac, this is really a CPU issue.
It might be possible to enable compressed h265 playback on preview builds though. I am not sure who would be able to confirm this. Maybe @timotiusmargo ?

I can try this and see if h265 compressed is supported.

I'm finding out how to enable the compressed samples support on preview builds. I'm not seeing the freezing issue with the current preview builds. I'm wondering if this is the same as the seek freezing which has been fixed at the pipeline level.

Do you have details on the availability of the fix you mention ? Are older platforms included as well ?
The freezing and playing issue will occur when buffering is enabled and the cpu can't keep up with decoding samples at a decent rate.
I didn't try 8k h265 but I am pretty sure there will be an issue with any cpu coming from earth, at least with single threaded decoding.


[SPARK-13398][STREAMING] Change FileWriteAheadLogger to not depend on deprecated ThreadPoolTaskSupport

What changes were proposed in this pull request?
Replace deprecated usage of ThreadPoolTaskSupport with ExecutionContextTaskSupport and incidentally update the comment to indicate that the number of concurrent objects is bounded by the threadpool size or 8 whichever is larger (updating the documentation to match code).
How was the this patch tested?
unit tests, streaming/testOnly org.apache.spark.streaming.util.WriteAheadLogUtilsSuite

Test build #51616 has started for PR 11287 at commit f2e6a25.

Test build #51616 has finished for PR 11287 at commit f2e6a25.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

This looks conceptually fine, though the test failed. I am not sure why. I stared at this for a while and don't see what would cause it to not be limited to 8 threads in the test.

I did some digging into why its 32 in jenkins and 4 on my machine - digging into the Scala internals it seems that the (private) FutureTasks doesn't actually look at the provided threadpool when determining parallelism rather it looks at the system. I'll close this for now and look at switching this over to ForkJoinTaskSupport (although it makes it pretty difficult to name the thread pool something meaningful :( ).


Add scale_along_curve node

Adds a node which allows you to scale nodes along a curve. Example:

Thanks for the PR!


Recommendation to use runtimeOnly 'androidx.compose.ui:ui-tooling:1.3.1' fails the build

Build scan link

What's this?
Dependencies which should be removed or changed to runtime-only:
  runtimeOnly 'androidx.compose.ui:ui-tooling:1.3.1' (was implementation)

Plugin version

1.19.0
Gradle version

7.5
(Optional) Android Gradle Plugin (AGP) version

7.4.1
Describe the bug
./gradlew buildHealth produces a report that tells me to use runtimeOnly with androidx.compose.ui:ui-tooling:1.3.1 but using runtimeOnly fails my build, meaning it's a false report.
To Reproduce
I guess have a project with implementation androidx.compose.ui:ui-tooling:1.3.1 and use @Preview somewhere with a composable function.
Expected behavior

A recommendation given by buildHealth should not be false and cause a failing build.

Thanks for the issue. Could you provide a minimal reproducer?

MyApplication.zip
Minimal reproducer attached. Run ./gradlew buildHealth in it.

Also, I can confirm that this is still happening in version 1.20.0.


Gogs support

Any chance to support https://github.com/gogits/gogs PR.
thanks

Hey @bang88, we would absolutely accept a PR to make "git repo" and "git new-pull-request" work with Gogs!
It should be relatively easy: just do a full text search for "bitbucket" and add Gogs to all areas you find.

Sounds doable. 😄

@kevgo but how can i make it work with our domain , are there have any docs i can read, IMO, i can't add gogs like bitbucket. if git town provide a config field that should be good to do this.

Some more detailed steps, now that I'm back from a trip and at my computer:

add a new file gogs.go to https://github.com/Originate/git-town/tree/master/src/drivers that matches how gitlab.go looks like
add a case for gogs to https://github.com/Originate/git-town/blob/master/src/drivers/code_hosting.go#L19-L32

As you can see in the second point, we recognize a server type from the URL. So if your server URL contains gogs, you are good to go. If that's not the case, we might need to implement #743

FYI i would say if we can have custom config for other git services. just something like how to config the main branch and store it in local git repo. so we could fit many use case and no need hard coded everything in git-town.
I think this could be a more friendly for everyone who loves git-town.
As i know maybe many companies  or teams have its own git service. they may use github enterprise version or gitlab and gogs etc. we can't simply check the hostname contains these domains or check the ssh account.
if we provide a configuration then we can do more things with git-town. no limited
Thanks. 😄

We can try adding a config option for the URL with placeholders. For example:

git-town.repo-url = https://github.com/Originate/git-town
git-town.new-pull-request-url = https://github.com/Originate/git-town/compare/<PARENT-BRANCH>...<BRANCH>?expand=1

Setting up these configuration values is a lot of manual work for the users, though. I want that they only have to do this if there is no other way. We should still support many popular hosting services out of the box.
If you don't have the time to build the driver yourself, please just give us the URLs that:

display the homepage of the repo on Gogs. On Github this is https://github.com/Originate/<REPO-NAME>
allow the user to create a new pull request on Gogs. On Github this is https://github.com/Originate/git-town/compare/<PARENT-BRANCH-NAME>...<BRANCH-NAME>?expand=1

We use a private server and the host can access only localhost. 😢

Hmm, why do you need git repo or git new-pull-request in such a scenario?

Just want try these featured. Haha


Opaque errors due to conflicting crate versions

In a dependency chain such that:
Library A is published up to 0.5
Library B depends on A = "=3.0"
Users application C depends on B = "*" and A = "*"
Cargo chooses version 0.5 of A for the downstream crate C which means anything bound on traits from A=0.3 in B are not implemented for the types in use in the interaction between B and C. Which means things fail to compile with errors about trait Foo is not implemented for Bar where they clearly are in the docs. The error messages given by rustc don't help a user realize that a version mismatch is the root cause in this scenario.
To get the downstream crate to build, we need to bound their A dependency to use to the same version as B, or do a lot of re-exports from B. This means that if B updates their dependencies in future, downstream will have to update their Cargo.toml again to B's version of A. (This will require the user probably looking at B's Cargo.toml, or the Cargo.lock)
This feels like it will become a worse problem as we starting seeing more crates semver'ing which will involve locking dependency versions down to their own needs.
Should it be documented as a 'best practice' to do re-exports for everything that downstream crates may interact with?
Or, should we consider some kind of sugar version specification e.g. A = "B" meaning use the same version of A as B does.
Concrete example here

I'm not sure this is super a cargo issue, but it'd be cool if cargo could pass in some metadata that rustc would print for each particular version of a crate. So you'd see stuff like foo(version 1.2.0)::baz::Bar

I agree with @cmr. I am in the middle of a multi-day Cargo debugging session for Servo right now, which mainly comes down to errors of that form (we have many transitive dependencies on libraries like x11-rs, and a small change to it has horrific rippling changes).

+1 to @cmr 's suggestion, it's especially mysterious the first time a user may come across it and some cargo support could go a long way. The extra metadata would only have to appear in situations where multiple versions of the same crate are depended upon in some way.

The error message should indeed be fixed, but that's pretty orthogonal to this bug report I believe. I would consider it under the purview of https://github.com/rust-lang/rust/issues/15142.
@Ryman this use case sounds like it's largely a problem with B for having such a tied down dependency on A and yet relying on so much of its API being exposed. Cargo could try to reduce the number of versions of A in the dependency graph, but that's not always the right answer as often times you want the most up-to-date version of A for everything but one small portion of the graph.

Should it be documented as a 'best practice' to do re-exports for everything that downstream crates may interact with?

I don't think this is going to be a best practice.

Or, should we consider some kind of sugar version specification e.g. A = "B" meaning use the same version of A as B does.

This is also quite difficult to do as it makes the dependencies of B part of the public API of the crate. I would expect B to also have to explicitly opt-in to this behavior if necessary to ensure that it's clearly messaged that dropping a dependency on A is a breaking change.

I don't think this is going to be a best practice.

This is also quite difficult to do as it makes the dependencies of B part of the public API of the crate.

@alexcrichton could you expand on these two points a bit? A question popped up that boiled down to nickel using hyper 0.6 and then hyper 0.7 was included from the Cargo.toml.
My first thought was "I wonder if there's a nickel::hyper re-export of everything". My second thought was "hmm, I have to look at the Cargo.lock file and copy the version; I wish I could just say "use the same".

Ah, the landscape here has changed quite a bit since I last looked at this. We plan to write up an RFC soon about some changes to Cargo to help make errors like this a little more precise and tweak how resolution works, but to answer your specific questions:
I don't think "just reexporting" is going to help much because you still have a problem that nickel is using hyper 0.6 and I'm using hyper 0.7. The only way for the types to agree is for me to link to hyper 0.7 or for me to exclusively use hyper through nickel (which seems unidiomatic). The best thing for cargo to do here actually is to detect this situation and give you an error immediately saying that you can't have multiple versions of hyper like this (as it won't compile).
In terms of making dependencies part of the public API of a crate, that's actually something we do intend to basically do. If you export any dependency's type from your API, then any major version bump in your dependencies must force a major version bump of yourself. This is often forgotten and often leads to problems as well.

for me to exclusively use hyper through nickel (which seems unidiomatic)

Let's pretend there's these two chains of dependencies:
Hyper <- Nickel <- My binary
Hyper <- Cool library <- My binary

If we just follow line one, I'd definitely want the ability to say "use what nickel thinks hyper should be". However, once I bring in the "cool library" that builds atop hyper and knows nothing of nickel, then that wouldn't make much sense.
So I think I agree with your assertion that just re-exporting wouldn't be generally useful.

If you export any dependency's type from your API

This seems like the right trigger, but I'm not sure if erroring would be always appropriate.
Perhaps what could happen is if you export a type that comes from one of your dependencies, then Cargo will also be able to use that version as a version specifier. Something like this:
Hyper <- Nickel <- Binary
Hyper <- CoolLib <- Binary
Hyper <- RestApiLibrary <- Binary

In this example, I am exposing two orthogonal APIs, one hand-rolled and one powered by "RestApiLibrary". I don't care what version of hyper RestApiLibrary uses, even though it exposes some types from hyper. My Cargo.toml could look something like:
[dependencies]
nickel = "*" # Use the newest cause I'm rad like that
cool_lib = "hyper::nickel" # A version of that depends on the same version of hyper that nickel uses
rest_api_library = "*" # Whatever is good

This would give a lot of flexibility, but that flexibility comes with a pretty high complexity. Perhaps it's not worth it?
Maybe it would just be better to allow multiple versions when a crate has a completely "sealed" usage of a dependency? I wonder if you could "seal" a crate after-the-fact? In the example above, could I somehow say
[dependencies,rest_api_library]
sealed = true
version = "*"

And thus prevent using any re-exported types from this crate (or at least acknowledge that I am ok with there being conflicting types).
This is hard stuff to think about! Sorry if I'm just blabbing on! :angel:

Yeah that's actually what we were thinking as well :)
The rest-api-library crate would declare its dependency on hyper as private (e.g. just an internal implementation detail) which would in theory allow that hyper to be duplicated. I'd personally prefer to avoid the case of explicitly telling Cargo "use the version this library is using" and instead just have it automatically deduce that, and I think it should be possible at least.

The rest-api-library crate would declare its dependency on hyper as private

This sounds close, but is a bit different than what I was thinking. We may have to pick somewhere in the middle...
Ideally, I would hope that during compilation of a crate, we could detect if it exposes any types that came from another crate. That would then automatically set the "just an implementation detail" flag. This would have to be on a dependency-by-dependency basis, otherwise the standard library crate will break this scheme for everything!
This could be extended to have a flag in Cargo.toml that states a dependency is internal-only. This would cause a compilation error if the programmer accidentally exposed a type. Perhaps the flag should go the other way though, and you have to opt-in to exposing types.
However, I think that the consumer of a crate should also be able to say that a dependency of a dependency is "just an implementation detail". This would allow me to use a crate that did expose types from its dependency as if it didn't expose them. It would then be up to me to ensure that I don't misuse those types.
I'm looking forward to the RFC or whatever where some of these hard ideas get debated in a broader setting!

Hm yeah that's a good point that any restriction Cargo places should likely be overridable from the top level as well to say "no, I know what I'm doing". I'll try to remember to cc this when that RFC comes into existence though!

cc me

This is coming up again recently as the ecosystem slowly shifts to Serde 1.0 and some dependencies are pinned to 0.8 or 0.9. Sometimes crates have requirements on all three conflicting versions!

I think this issue is addressed with RFC #1977, public/private dependencies. Please reopen if I'm mistaken!


backend: add admin ops (skeleton) support

This patch set adds support for admin ops, but does not add APIs for them.
That shall come in a follow-up patch set.
Signed-off-by: Joao Eduardo Luis<EMAIL_ADDRESS>

It looks good; only this seems to include also more than the support for admin APIs. Maybe I've not understood this properly, but this seems to include also code related to some specific admin APIs :
    AuthUser,
    UserInfo,
    UserKeyOpParams,
    UserKeys,
    UserOpParams,
    UserQuotaOpParams,

To facilitate the review process, could be possible to split this into 2 PRs ? Eg: this one containing only the low-level support code and another one with the parts that are using the underlying layer?

To clarify, you would like,

one PR with commit 30a9fc2ff3c1e53c4133fe1440e7223ebd7ccae0, containing changes to two discrete files;
another PR with all other 6 commits.

Is that it?

It looks good; only this seems to include also more than the support for admin APIs. Maybe I've not understood this properly, but this seems to include also code related to some specific admin APIs :
    AuthUser,
    UserInfo,
    UserKeyOpParams,
    UserKeys,
    UserOpParams,
    UserQuotaOpParams,

To facilitate the review process, could be possible to split this into 2 PRs ? Eg: this one containing only the low-level support code and another one with the parts that are using the underlying layer?

To clarify, you would like,

one PR with commit 30a9fc2ff3c1e53c4133fe1440e7223ebd7ccae0, containing changes to two discrete files;
another PR with all other 6 commits.

Is that it?

I would prefer that way if possible (just for ease the reviewer work); otherwise, please update accordingly the PR description to reflect all that is changed/added here.

It looks good; only this seems to include also more than the support for admin APIs. Maybe I've not understood this properly, but this seems to include also code related to some specific admin APIs :
    AuthUser,
    UserInfo,
    UserKeyOpParams,
    UserKeys,
    UserOpParams,
    UserQuotaOpParams,

To facilitate the review process, could be possible to split this into 2 PRs ? Eg: this one containing only the low-level support code and another one with the parts that are using the underlying layer?

To clarify, you would like,

one PR with commit 30a9fc2ff3c1e53c4133fe1440e7223ebd7ccae0, containing changes to two discrete files;
another PR with all other 6 commits.

Is that it?

I would prefer that way if possible (just for ease the reviewer work); otherwise, please update accordingly the PR description to reflect all that is changed/added here.

I'll be honest: I don't see how that is going to help reviewing the patch set, but if that makes it better for you to review the patch set, who am I to disagree; I will split it into two PRs.
Additionally, I don't think there's missing information in the PR description. There are no API endpoints being added that need to be described, even if there is code added to exercise some admin ops on the RGW side -- again, they are essentially dead code at this point because nothing (besides simple unit tests) are exercising these code paths.

I would prefer that way if possible (just for ease the reviewer work); otherwise, please update accordingly the PR description to reflect all that is changed/added here.

I'll be honest: I don't see how that is going to help reviewing the patch set, but if that makes it better for you to review the patch set, who am I to disagree; I will split it into two PRs.

Let's just say it's not possible, because there are dependencies between patches in the patch set.
Technically, it's possible. Will take me a lot longer than the value obtained from it, and will likely require multiple rewrites of the code to make it play nice the way you want.

It's a lot :-) I caught myself on willing to drop an "lgtm" in the comments and just approve it without deep reading...

for me this is ok; just let me know when this is ready for you and I'll approve.


I2C Bus Speed too fast when set to 'Standard' mode, resulting in data corruption

When using an I2C device with the bus speed set to 'Standard' mode, the bus speed used by the Lightning provider is too fast and exceeds the 100KHz maximum, resulting in data corruption.
I create my I2C settings like this:
    public static I2cConnectionSettings ConnectionSettings(int address = DefaultSlaveAddress)
    {
        return new I2cConnectionSettings(address) {BusSpeed = I2cBusSpeed.StandardMode};
    }

With the default 'inbox' driver, that produces bus activity like so (note the SCL frequency measures dead on 100KHz, which is the maximum allowed speed in Standard mode):

With the lightning provider enabled, the same capture looks like this (note, SCL measures about 165KHz, way too fast!)

I've tried the exact same code (driving an MLX90614 temperature sensor) with both drivers and with the lightning driver enabled, it produces meaningless data which fluctuates wildly. Looking at the protocol analysis, it is clear that things are just not working correctly.

This of course is a SHOWSTOPPER because the I2C bus simply doesn't work, with no possible fix in software.

I can reproduce this

Thanks for finding this issue!
Looks like this is caused by the wrong clock divider value used.
We will look into a fix for this ASAP.

The clock divider was not set correctly. In the Lightning package source '\packages\Microsoft.IoT.Lightning.1.0.2-alpha\build\native\include\BcmI2cController.h' , can you try changing the value of the const ULONG CDIV_100KHZ to 2500 instead of the current 1500, then rebuild the project?

I see you have already published a new NuGet package, 1.0.3-alpha. I've updated my solution to that version and it's spot on 100KHz now, so I'd say that is a fix. Many thanks for that!

P.S. How about pushing the package for the Lightning Provider so I don't have to deal with the C++ source code for that...? There's a NuSoec in the solution but it's not on NuGet anywhere.

Thank you for confirming!
Apologies for the delay in releasing the Nuget providers. We've been planning to publish it on Nuget for some time now, but it's been delayed by some prerequisites for publishing binaries. Hopefully, it's all resolved now and we'll be able to release it shortly, this week or next week.

That will be helpful – thanks!
However, did you notice that I found what appears to be another showstopper in the I2C provider? Basically, with the lightning driver, you can only create one instance of an I2cDevice. Since I2C is meant to be a multi-device bus, that’s a bit of a problem.
Please see https://github.com/ms-iot/BusProviders/issues/32
Best regards,
Tim Long
From: Mahmoud Saleh<EMAIL_ADDRESS>Sent: Monday, March 14, 2016 8:14 PM
To: ms-iot/BusProviders<EMAIL_ADDRESS>Cc: Tim Long<EMAIL_ADDRESS>Subject: Re: [BusProviders] I2C Bus Speed too fast when set to 'Standard' mode, resulting in data corruption (#21)
Thank you for confirming!
Apologies for the delay in releasing the Nuget providers. We've been planning to publish it on Nuget for some time now, but it's been delayed by some prerequisites for publishing binaries. Hopefully, it's all resolved now and we'll be able to release it shortly, this week or next week.
—
Reply to this email directly or view it on GitHubhttps://github.com/ms-iot/BusProviders/issues/21#issuecomment-196501772.

It's been a known issue and the fix has been pulled to the Lightning repository.
Unfortunately,  it didn't make it to the latest Lightning Nuget, 1.0.3-alpha.
However, the fix is straightforward to apply. Either, copy DmapSupport.cpp from the Lightning repository to your Lightning source folder; normally \packages\Microsoft.IoT.Lightning.1.0.3-alpha\build\native\source, or just update this one line in the same file.
If thanks fixes the issue for you, please let me know.
Thanks

Fixed in the latest Lightning SDK, v1.1.0-alpha. If still not fixed, please reopen the issue.


Changing format enables save button

I've got a bunch of data saved in one format that I'm trying to change to the other. This makes it a little easier.
PR to master cause it has a few more commits. I can switch to point at dev if you prefer.

Fixed in one of the changes. Thanks!

0e905160fef6aeb5008519bbd107097ff3eec6ad


Java syntax highlighting does not include "var" as a key word

You're right, it doesn't!

This ticket has been resolved by #3526 c8eeb788cb6618ca3b6dd8fc2d6a130579214289, right?

Right.


uROS-arduino failingto build after update to 2.0.3

I've just tried to update to the 2.0.3 package and it's not building.
 Done
Building dependency tree
Reading state information... Done
163 packages can be upgraded. Run 'apt list --upgradable' to see them.
Creating firmware for generate_lib platform generic
.......
=== ./ament/ament_cmake (git) ===
Cloning into '.'...
=== ./ament/ament_index (git) ===
Cloning into '.'...
=== ./ament/ament_lint (git) ===
Cloning into '.'...
=== ./ament/ament_package (git) ===
Cloning into '.'...
=== ./ament/googletest (git) ===
Cloning into '.'...
=== ./ament/uncrustify_vendor (git) ===
Cloning into '.'...
=== ./ros2/ament_cmake_ros (git) ===
Cloning into '.'...

Resolving deltas: 100% (9836/9836), done.
=== ./control_msgs (git) ===
Cloning into '.'...
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
No changes detected
milner@canterbury:~/Arduino/libraries/micro_ros_arduino-2.0.3-foxy$

This should be fixed with this PR: https://github.com/micro-ROS/micro_ros_arduino/pull/794
Please update the library with the lastest commit, will release the fix if the feedback is positive.

@Acuadros95 Hey, not sure if I am doing it correctly, but I still have an issue, albeit a different one.
I have pulled the latest foxy version from github and added it as a library to Arduino IDE. Next, I tried running the same docker command but now it gives me a different error. Full log below:
sejego@pop-os:~/Arduino/libraries/micro_ros_arduino$ sudo docker run -it --rm -v $(pwd):/project --env MICROROS_LIBRARY_FOLDER=extras microros/micro_ros_static_library_builder:foxy
/entrypoint.sh: line 9: /project/extras/library_generation/library_generation.sh: Permission denied

@sejego you need to modify the permissions of the library_generation.sh file, use:
sudo chmod a+x <Your path>/library_generation.sh

@carmiac @Acuadros95 The issue is fixed, was able to compile everything! Thanks a ton <3


force panel to be even number

When randomly picking the number of individuals to use from discovery for ignore, force the number of individuals in ignore to be even.

wait to do this until I complete https://github.com/agladstein/SimPrily/projects/1#card-4853290


mounter can't utilize full CPU resource

What did you do?
Create a changefeed and run a tpcc workload with warehouse = 200.
What did you expect to see?
No response
What did you see instead?

The CDC instance has 16C. We can see that it can't utilize full CPU quota, and the changefeed spends too much time on waiting mount.
In expect, mounter threads should utilize more CPU and reduce ResolvedTs lag and CheckpointTs lag. I forgot to ptrscreen for the lags, but they were keeping increasing.
Versions of the cluster
master branch.

It's located. The reason is sink manager generating redo tasks without considering schema storage timestamp. So mounter threads are blocked on waiting the timestamp get advanced.

After fixed:


FS-161 Docs for the Akka HTTP integration.

This PR fulfills ticket #161.
We add the docs section for the Akka  HTTP integration.
Along the way, we also simplify the existing test, by removing the unneeded @module.

Codecov Report

Merging #171 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #171   +/-   ##
=======================================
  Coverage   73.81%   73.81%
=======================================
  Files          36       36
  Lines         317      317
  Branches        2        2
=======================================
  Hits          234      234
  Misses         83       83

Continue to review full report at Codecov.

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


Account address generation for factory pattern can lead to storage overwrite of existing accounts

OSX version: 10.11.5
Eris CLI Version: 0.12.0
Docker:
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:44:17 2016
 OS/Arch:      darwin/amd64
Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      linux/amd64
docker-machine version 0.7.0, build a650a40

The following problematic behavior has been observed when creating new contract instances from within other contracts in Solidity:

Calling the new constructor of another contract from a top-level contract account, i.e. the contract that is invoked by an external call from EPM or JS, always creates a new address as expected.
Delegating from the top-level contract to another contract (or further down) to call the new constructor creates a new address only upon first invocation. Any subsequent invocation results in creating the same address and as a result the storage that existed at the address is overwritten!

The attached contracts and EPM scripts (factory-test.zip) can be used to reproduce the behavior in the following sequence:

Create a new chain
cp epm.yaml.1 epm.yaml and run it once to deploy the contracts
Copy the address of the deployed InstructionManager contract (which acts as the mentioned top-level contract) from the console output and paste it in the first job in the epm.yaml.2 file
cp epm.yaml.2 epm.yaml and run it once.
Take note of the new Instruction contract addresses created by the level 1 & 2 factory contracts. Use these addresses to make a copy of their storage, e.g.: http://<IP_ADDRESS>:46657/dump_storage?address="799DF4C5232A8CB99F8A5237B999B8C84DBF7746"
Run the epm.yaml again. This time around it will provoke the creation of already existing addresses by the level 1 & 2 factories and the storage at these addresses will be overwritten.

The following is the console output from the above sequence:
$ cp epm.yaml.1 epm.yaml

jan at MacBook-Pro-6 in ~/Development/git/github.com/eris-ltd/eris-contracts-bundles/src/factory-test on instruction-registry-indexing-48 [!?]
$ eris pkgs do -c test -a 609DE71ECA4548D090757E63E69E62898D2D037F -l https://compilers.eris.industries:10113
Performing action. This can sometimes take a wee while
Executing Job                                 defaultAddr
Executing Job                                 InstructionManagerK
Deploying Contract                       name=Instruction
                                         addr=98287351E4A6FE4C08457D66FE8C336B0CD97402
Deploying Contract                       name=InstructionManager
                                         addr=7B1FC9DD4A5DA4D45FE682FBD5CA0DEE96041239
Deploying Contract                       name=Level1Creator
                                         addr=71DF904F5D69E6E5F1480D7B6F96E6C2371BD3AC
Deploying Contract                       name=Level2Creator
                                         addr=053635F196CCA78337BBB683ACDBB80CECD9EEA0
Deploying Contract                       name=Owned
                                         addr=EFEEFCA8885FF186F7F4C32FFA60A7D3E9902E03
Executing Job                                 Level1K
Return Value                                  D96EAF45A317A8740E984272EAC5AC018186E202
Executing Job                                 Level2K
Return Value                                  AAC0670C944E39FE62EC44659AEB7A02CE989E37

jan at MacBook-Pro-6 in ~/Development/git/github.com/eris-ltd/eris-contracts-bundles/src/factory-test on instruction-registry-indexing-48 [!?]
$ cp epm.yaml.2 epm.yaml

jan at MacBook-Pro-6 in ~/Development/git/github.com/eris-ltd/eris-contracts-bundles/src/factory-test on instruction-registry-indexing-48 [!?]
$ eris pkgs do -c test -a 609DE71ECA4548D090757E63E69E62898D2D037F -l https://compilers.eris.industries:10113
Performing action. This can sometimes take a wee while
Executing Job                                 defaultAddr
Executing Job                                 InstructionManagerK
Executing Job                                 level0-1
Return Value                                  success
Executing Job                                 lastRegisteredAddressPairL0
Return Value<PHONE_NUMBER>000000000000000000000000000000, 614D8884D6117D3838E74C65CEF1F8D2B7D3DE67)
Executing Job                                 duplicateL0
Return Value<PHONE_NUMBER>000000000000000000000000000000
Executing Job                                 level1-1
Return Value                                  success
Executing Job                                 lastRegisteredAddressPairL1
Return Value                                  (614D8884D6117D3838E74C65CEF1F8D2B7D3DE67, 799DF4C5232A8CB99F8A5237B999B8C84DBF7746)
Executing Job                                 duplicateL1
Return Value<PHONE_NUMBER>000000000000000000000000000000
Executing Job                                 level2-1
Return Value                                  success
Executing Job                                 lastRegisteredAddressPairL2
Return Value                                  (799DF4C5232A8CB99F8A5237B999B8C84DBF7746, FF80313C63FC8309796129311A680C3EF62657E4)
Executing Job                                 duplicateL2
Return Value<PHONE_NUMBER>000000000000000000000000000000

jan at MacBook-Pro-6 in ~/Development/git/github.com/eris-ltd/eris-contracts-bundles/src/factory-test on instruction-registry-indexing-48 [!?]
$ eris pkgs do -c test -a 609DE71ECA4548D090757E63E69E62898D2D037F -l https://compilers.eris.industries:10113
Performing action. This can sometimes take a wee while
Executing Job                                 defaultAddr
Executing Job                                 InstructionManagerK
Executing Job                                 level0-1
Return Value                                  success
Executing Job                                 lastRegisteredAddressPairL0
Return Value                                  (FF80313C63FC8309796129311A680C3EF62657E4, 9F26BBD07A757AD7469FA3047F5408731CD3AD31)
Executing Job                                 duplicateL0
Return Value<PHONE_NUMBER>000000000000000000000000000000
Executing Job                                 level1-1
Return Value                                  Address overwrite detected. New address already registered!
Executing Job                                 lastRegisteredAddressPairL1
Return Value                                  (FF80313C63FC8309796129311A680C3EF62657E4, 9F26BBD07A757AD7469FA3047F5408731CD3AD31)
Executing Job                                 duplicateL1
Return Value                                  799DF4C5232A8CB99F8A5237B999B8C84DBF7746
Executing Job                                 level2-1
Return Value                                  Address overwrite detected. New address already registered!
Executing Job                                 lastRegisteredAddressPairL2
Return Value                                  (FF80313C63FC8309796129311A680C3EF62657E4, 9F26BBD07A757AD7469FA3047F5408731CD3AD31)
Executing Job                                 duplicateL2
Return Value                                  FF80313C63FC8309796129311A680C3EF62657E4

The change of storage at the two addresses identified as duplicates was captured in the following files. The rootStorage changed as well as one of the keys for the maturityDate since it uses a timestamp.
799DF4C5232A8CB99F8A5237B999B8C84DBF7746-after.json.txt
799DF4C5232A8CB99F8A5237B999B8C84DBF7746-before.json.txt
FF80313C63FC8309796129311A680C3EF62657E4-after.json.txt
FF80313C63FC8309796129311A680C3EF62657E4-before.json.txt

All in one simplified test @j-h-scheufen @VoR0220
factory-test.zip

factory-test.zip
better


3Hentai: Source Request

Source name
3HENTAI
Source link
https://3hentai.net/
Source language
MULTI
Other details
18+/NSFW=YES
Acknowledgements

[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

@ImAlwaysHorni why did you wipe and close your old issue to create a new one

@ImAlwaysHorni why did you wipe and close your old issue to create a new one

for acknowledgment issues 🐸

for acknowledgment issues 🐸

you closed #485, and made a new one. this won't magically make your request faster

for acknowledgment issues 🐸

you closed #485, and made a new one. this won't magically make your request faster

i renamed it because that case got closed and i couldn't post a new request of same name or duplicate it..so i renamed the closed one and checked this acknowledgment ↓
" I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue."

i renamed it because that case got closed and i couldn't post a new request of same name or duplicate it..so i renamed the closed one and checked this acknowledgment ↓

You aren't supposed to open duplicate issues by wiping/closing the old one.

i renamed it because that case got closed and i couldn't post a new request of same name or duplicate it..so i renamed the closed one and checked this acknowledgment ↓

You aren't supposed to open duplicate issues by wiping/closing the old one.

i would be more careful next time 🙂
thank you

Closing in favor of #485. I will not accept bumping issues like this.


Variant module

Please check the commits, it seems there isn't much in this PR and what is there affects the main package.json which is not desirable.


use authn filter constant every where

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
7061ef8d5625ad7ca34f9cf012f5ff64bd1534e3
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-mc


Revert "[Tests] Disable failing test cases while investigating"

This reverts commit f8e18e515130798ced28e3029965ee8b70fdaf88.
I am finding that the value we print here varies a bit in between platforms. I am just going to remove it.

@swift-ci test

Full test ; )

Build failed
Swift Test OS X Platform
Git Sha - 4cd247f2276a3ab27339ddad8f1b44b3579a685c

Build failed
Swift Test Linux Platform
Git Sha - 4cd247f2276a3ab27339ddad8f1b44b3579a685c


Getting blank images from screencopy

With the latest git master of both wlroots and sway, screencopy is giving me images that are the correct dimensions, but fully transparent. This occurs with both the wlroots screencopy example, and with grim.
First noted at emersion/grim#17
My graphics card is a GeForce GTX 970 and I use nouveau, which I guess could be a significant part of the problem! (Yep, I know it's a bad card to use with Wayland, but I bought it about a year before I started using sway.)

Thanks. Can you try the old screenshot example?

Oh, right, of course, it has been removed from sway. Can you try with rootston?

Well this is odd. On rootston, all three work, screenshot, screencopy and grim. So I guess it's a sway issue…

This makes me think, maybe there's an alpha channel trick involved. Maybe the image data is there but alpha is set to 0. Can you upload your transparent screenshot?


Be in trouble to get kubeconfig information from kubectl to custom proxy api

Currently, I am developing kubernetes api proxy server by golang.
the proxy server is gonna be responsible for my custom authentication.
the flow is as below.
kubectl -> my proxy api(process authentication) -> kubeapiserver
and local kubeconfig is as below.
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: {cert...}
    server: http://localhost:8080
  name: aaa
contexts:
- context:
    cluster: aaa
    user: aaa
  name: aaa
current-context: aaa
kind: Config
preferences: {}
users:
- name: {name}
  user:
    token: {token...}

I wanna get cluster information and users information such as context name or user token,
and I thought there should be in the request header or anywhere from request.
But I can't get data from request and anywhere.

We don't send this information over a request - those are just arbitrary local names.
You could use https://pkg.go.dev/k8s.io/client-go/tools/clientcmd to read the users config and act from that.
/close


Add andromeda theme

Created the Andromeda photojournal/blog theme with a demo available at https://andromeda-theme.netlify.app/ and repo at https://github.com/Pixadus/andromeda-theme, looking to add it to the official Zola themes repo.

To get indexed on the themes gallery you need to have a screenshot.png file, so you will want to convert your jpg to a png.
you should also add a line to your theme.toml for the demo link, eg: https://github.com/Jieiku/abridge/blob/75bb461162f7644a498101bc121faac3cfee7799/theme.toml#L6

Thanks for the comments - just updated the screenshot & added demo link.

Thanks!


Confusing example of DisplayFor.

[Enter feedback here]
I found the unclear code in https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/page?view=aspnetcore-5.0&tabs=visual-studio#the-create-delete-details-and-edit-pages
In the above section, there is a example of Pages/Movies/Index.cshtml :
@Html.DisplayFor(modelItem => item.Title)
Why does modelItem can relate to item?
Do I miss something or it is typo?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 70f6104a-a223-4bb3-4101-f553002b9b26
Version Independent ID: 15e79e80-8d46-7cd5-c883-6cc0f5940a1b
Content: Part 3, scaffolded Razor Pages
Content Source: aspnetcore/tutorials/razor-pages/page.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

See https://github.com/dotnet/aspnetcore/issues/3956


Module 2 - Business Value info needs restructuring

Target intro content at 30 min (by trimming slides)
Add info re Tropo international caveats/pricing to intro content

General comments from the event was that module was too long.  Not enough time on labs.  See Steve's comment:
Need an extra short lab about the Tropo pricing for international call so that devs understand how it will be priced. It is not about selling the product (sales pitch), but to make them understand how the licensing works. They would go to the pricing page, see the price per call, and price per phone number, and price per SMS, and then compute the price to create a Voice Machine in France/US/Italy depending where the lab is delivered.
This could also be explained to a participant, without them having to take the lab.
Concerning the mission, it would have needed more prep about how to run it in real time with proctors. We organized in real time to get the participants feedback. I would extend it by 10 minutes, and ensure there are enough proctors to engage the conversation with the team: 1 proctor = 3 teams maximum. Organize the team as a consequence.

From Phil:
I uploaded a new version of module 2: The Business Value of Cloud Collaboration APIs to the Box directory for Vegas; ended up trimming about 15 slides (set to hidden in the deck). I'll continue to work on the other items.
~Phil

I have reviewed the changes and updates. Very happy with what Phil did. IMO ready to go!

No open concerns with this module
Assigning to @klevenstein for closure


ORM env

ORM env

Hello @maborak! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file ebooksdl/app.py:

Line 18:80: E501 line too long (112 > 79 characters)


fix link to tracy

Objective
#11331 move the tracy dependency, this fix the link to point to the new location

Ok, if we keep it in latest, this should be merge after 0.13

We probably should remove the line number rather than trying to keep it in sync.


Memory leak issues with version 13.6.0

Bug description:
Memory leak issues with version 13.6.0
To Reproduce:
reproduction repo : https://github.com/TheRogue76/rnwwmemoryleak
Steps:

Create a new empty project
Add RNWW
Add a component that shows a web view with a url when state is true and removes it when it is false
Profile the output with something like Xcode instruments

Expected behavior:

Releasing the memory once the view is unmounted
Lower memory usage, (I'm not familiar with WKWebview's normal usage, so i could be wrong, but 500 mb with nothing attached sounds a bit much and feels like it might be related to something else, but if i am wrong, please let me know)

Screenshots/Videos:

Environment:

OS: MacOS
OS version: 13.5.2
react-native version: 0.72.4
react-native-webview version: 13.6.0

Not actively searching, since i am not using React Native very actively anymore, but if anyone sees anything or has ideas, please contribute

Issue persists

Let it get closed. I looked at the code to try to see if i could add some weak self references to the webview in the call back handlers and break the reference cycle, but i can not reason about the 1800 line file that is RNCWebViewImpl.m. If any maintainers see this issue down the line and want to know more about what i think the issue is, feel free to reach out.


Mark both Michael Highstead and Oliver Boyle as agreed to donate contributions to ASF

ref:

https://github.com/apache/cassandra-gocql-driver/issues/1751#issuecomment-2293920730
https://github.com/apache/cassandra-gocql-driver/issues/1751#issuecomment-2299173580

also added Bartosz Burclaf


GP model, Combination of individual responses into a single broadband

Hello, I have a strong question about the Graves and Pitarka model (GP). How made the combination  between  the individual low- and high-frequency responses into a single broadband time series using a set of matched fourth order Butterworth filters having a common corner frequency of 1 Hz? Please can you share the formulations?
Thanks

Hi,
According to Rob Graves, the basic process consists of:

Apply Nth-order, zero-phase butterworth filter with lowpass corner at 1 Hz to the “low frequency” (deterministic) time series.

Apply Nth-order, zero-phase butterworth filter with highpass corner at 1 Hz to the “high frequency” (stochastic) time series.

Sum the two filtered time series together to obtain the broadband result.

The butterworth filters described above are “matched” in the sense that their Fourier amplitude spectra sum to unity for all frequencies.
The GP approach on the Broadband Platform is implemented in the match.py code (using method 2 as specified in match_cfg.py, see also match.py lines 95-104, in order to better account for the mismatch in phase between the deterministic and stochastic motions.)

Thank you...!

Hello, I have a strong question about the Graves and Pitarka model (GP)，too.I want to use GP15.6 model （slip distributions generated using the wavenumber filtering approach with random phasing），However, I couldn't find the specific location of this part of the program in BBP. Could you please help me to pinpoint the exact location of this code? This is very important to me. Thank you very much.


Symbol type is deprecated

The "symbol" type is deprecated in BSON and in Mongo 3.2.
https://docs.mongodb.com/manual/reference/bson-types/
I believe mongoid-enum should be updated to use Strings instead of Symbols for storing the enum value to reduce future data migrations when Symbol is finally removed as a supported type.
Alternatively, mongoid-enum could be made to be indifferent as to whether strings or symbols are stored - including in the auto-generated accessor methods.

+1
We're trying to upgrade mongo, the export utility flat out refuses to handle symbol types.  Any plan to tackle this?

+1
Is there any solution for now?

Some additional insight, apparently the symbol type was deprecated in the BSON driver (masked to string) and specifically undeprecated by the official Ruby mongodb driver.  Mongoid relies on the driver which relies on BSON.  IMO this is beyond the scope of this project but is certainly an issue for anybody using mongoid.  I'm currently unable to post evidence but will do so ASAP unless someone beats me to it.


Typo in Zero-Knowledge TLS image

"termincation" should be termination
https://ngrok.com/docs/cloud-edge/zero-knowledge-tls

Nice catch @refeed ! I'll fix the image.

sorry for the delay! thank you for opening this!


Key components readmes

Currently all readmes are build according to this template:

Component Name
Description
component_type: add here
is_customizable: true/false (choose one, pls)
text for short description here
I/O
text here if i/o specified
Dependencies
Configuration settings specified in the .yaml files at service_configs
Required Python packages specified in requirements.txt.
For more details on inner workings of the component please refer to server.py

Things to correct/improve:

overall readme format for desired points to include there.
I/O info on some components (where not specified)

PR closed bc it was a test one, we'll re-write readmes


Footer text changes only update the apply pages not public pages

Edits in Wagtail admin -> Settings -> System settings only show changes on the apply site, not the public site.

Have to do this for each site (top right corner of the wagtail admin) and the clear cache to see changes. working as intended.


Adding support for service authority parameter

This PR
Adding a new config option that allows flagd clients to override the authority. This is useful when running gRPC sync service behind proxy e.g. envoy, istio etc. For more details, please refer this PR

adds this new feature

Related Issues
https://github.com/open-feature/java-sdk-contrib/pull/949
Notes
Follow-up Tasks
How to test

looks good to me


Efficient calculation of particle densities

The ParticleSet.density() method as currently implemented is very inefficient, in that it recalculates from scratch particle densities in each call
It would be much more efficient if particle densities are kept track of by updating a field on each change of particle.xi and particle.yi.
Note that this would also require the particle.xi and particle.yi Variables to be accessible in SciPy mode, for compatibility between the two modes

Actually a duplicate of issue #40, so closing this one for now


[Enhancement] check db priv after found udf(backport#14870)

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

backport #14870
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.22 out of 23 committers have signed the CLA.:white_check_mark: HangyuanLiu:white_check_mark: amber-create:white_check_mark: waittttting:white_check_mark: trueeyu:white_check_mark: gengjun-git:white_check_mark: packy92:white_check_mark: decster:white_check_mark: EsoragotoSpirit:white_check_mark: femiiii:white_check_mark: Seaven:white_check_mark: liuyehcf:white_check_mark: ABingHuang:white_check_mark: sevev:white_check_mark: ZiheLiu:white_check_mark: nshangyiming:white_check_mark: jiacheng-celonis:white_check_mark: chaoyli:white_check_mark: mofeiatwork:white_check_mark: zaorangyang:white_check_mark: silverbullet233:white_check_mark: miomiocat:white_check_mark: dirtysalt:x: mergify[bot]You have signed the CLA already but the status is still pending?


Issue with tutorials/classify-maizeland-ng/index.md

Issue Description:
when I try run the code, I get this error:
"Training points: Layer error: Collection.loadTable: Collection asset 'projects/earthengine-community/tutorials/classify-maizeland-ng/training-pts' not found."

Thank you for bringing this to our attention. The asset permission settings have been adjusted - you should have access now.