Error when submitting store metadata

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.5

Ruby
2.6.3

Bundler?
false

Git
git version 2.21.0 (Apple Git-122)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.5 (19F101)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
11.1

System Locale

Variable
Value

LANG
zh_CN.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Push a new release build to the App Store"
  lane :release do
    build_app(scheme: "xxx")
    upload_to_app_store
  end
end

`./fastlane/Appfile`
app_identifier("xxx") # The bundle identifier of your app
apple_id("xxx") # Your Apple email address

itc_team_id("xxx") # App Store Connect Team ID
team_id("xxx") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.153.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.16.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.73.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday
1.0.1

faraday_middleware
1.0.0

fastimage
2.1.7

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
1.17.2

naturally
2.2.0

simctl
1.6.8

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.14.0

memoist
0.16.2

os
1.1.0

googleauth
0.12.0

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.1

google-cloud-errors
1.0.0

google-cloud-core
1.5.0

digest-crc
0.5.1

google-cloud-storage
1.26.1

emoji_regex
1.0.1

jmespath
1.4.0

aws-partitions
1.313.0

aws-eventstream
1.1.0

aws-sigv4
1.1.3

aws-sdk-core
3.95.0

aws-sdk-kms
1.31.0

aws-sdk-s3
1.64.0

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

webrick
1.4.2

generated on: 2020-07-24

Deliverfile
app_review_information({
demo_account_required:false,
contact_first_name: "xxx",
contact_last_name: "xxx",
contact_phone: "+xxx",
contact_email: "xxxx.com",
demo_account_name: "",
demo_account_password: "",
notes: ""
})

@joshdholtz
pi/client.rb:163:in `handle_response': [!] The provided entity includes an unknown attribute - 'demo_account_required' is not an attribute on the resource 'appStoreReviewDetails' (Spaceship::UnexpectedResponse)

@shizu2014 Thank you for creating a new issue! Are you able to post your entire fastlane output (from beginning to end)? It gives me a lot more info to diagnose the issue.

[23:43:33]: Successfully exported and compressed dSYM file
[23:43:33]: Successfully exported and signed the ipa file:
[23:43:33]: /Users/xxx/Documents/xxx/0724/xxx/xx.ipa
[23:43:33]: ---------------------------------
[23:43:33]: --- Step: upload_to_app_store ---
[23:43:33]: ---------------------------------
[23:43:33]: Successfully loaded '/Users/xx/xx/xx/xx/xx/fastlane/Deliverfile' 📄
+----------------------------+--------------------------------------+
|           Detected Values from './fastlane/Deliverfile'           |
+----------------------------+--------------------------------------+
| price_tier                 | 0                                    |
| app_review_information     | {:demo_account_required=>false,      |
|                            | :contact_first_name=>"xxx",           |
|                            | :contact_last_name=>"xxx",       |
|                            | :contact_phone=>"+xxx",    |
|                            |<EMAIL_ADDRESS>|
|                            | m", :demo_account_name=>"",          |
|                            | :demo_account_password=>"",          |
|                            | :notes=>""}                          |
| submission_information     | {:add_id_info_uses_idfa=>false,      |
|                            | :export_compliance_uses_encryption=  |
|                            | >false,                              |
|                            | :export_compliance_encryption_updat  |
|                            | ed=>false,                           |
|                            | :content_rights_contains_third_part  |
|                            | y_content=>false}                    |
| primary_category           | Entertainment                        |
| skip_screenshots           | false                                |
| skip_metadata              | false                                |
| force                      | true                                 |
| run_precheck_before_submit | false                                |
| copyright                  | Copyright 2020 xxx    |
| automatic_release          | true                                 |
| submit_for_review          | true                                 |
| app_rating_config_path     | ./rating.json                        |
+----------------------------+--------------------------------------+
[23:43:33]: Login to App Store Connect<EMAIL_ADDRESS>[23:43:39]: Login successful
+--------------------------------------+--------------------------------------+
|                           deliver 2.153.0 Summary                           |
+--------------------------------------+--------------------------------------+
| ipa                                  | /Users/xxx/Documents/workSpace/  |
|                                      | xxxxx/xxxx/xxxx.ipa       |
| screenshots_path                     | ./fastlane/screenshots               |
| metadata_path                        | ./fastlane/metadata                  |
| app_version                          | 1.0                                  |
| username                             |<EMAIL_ADDRESS>                     |
| app_identifier                       |xxxx                |
| platform                             | ios                                  |
| edit_live                            | false                                |
| use_live_version                     | false                                |
| skip_binary_upload                   | false                                |
| skip_screenshots                     | false                                |
| skip_metadata                        | false                                |
| skip_app_version_update              | false                                |
| force                                | true                                 |
| overwrite_screenshots                | false                                |
| submit_for_review                    | true                                 |
| reject_if_possible                   | false                                |
| automatic_release                    | true                                 |
| phased_release                       | false                                |
| reset_ratings                        | false                                |
| price_tier                           | 0                                    |
| app_rating_config_path               | ./rating.json                        |
| submission_information.add_id_info_  | false                                |
| uses_idfa                            |                                      |
| submission_information.export_compl  | false                                |
| iance_uses_encryption                |                                      |
| submission_information.export_compl  | false                                |
| iance_encryption_updated             |                                      |
| submission_information.content_righ  | false                                |
| ts_contains_third_party_content      |                                      |
| team_id                              | xxx                            |
| dev_portal_team_id                   | xxx                           |
| run_precheck_before_submit           | false                                |
| precheck_default_rule_level          | warn                                 |
| copyright                            | Copyright 2020 xxxx    |
| primary_category                     | Entertainment                        |
| app_review_information.demo_account  | false                                |
| _required                            |                                      |
| app_review_information.contact_firs  | bi                                   |
| t_name                               |                                      |
| app_review_information.contact_last  | xxx                              |
| _name                                |                                      |
| app_review_information.contact_phon  | +xxxx                       |
| e                                    |                                      |
| app_review_information.contact_emai  |<EMAIL_ADDRESS>                |
| l                                    |                                      |
| ignore_language_directory_validatio  | false                                |
| n                                    |                                      |
| precheck_include_in_app_purchases    | true                                 |
+--------------------------------------+--------------------------------------+
[23:43:41]: Making sure the latest version on App Store Connect matches '1.0'...
[23:43:43]: '1.0' is the latest version on App Store Connect
[23:43:46]: Loading './fastlane/metadata/zh-Hans/description.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/keywords.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/release_notes.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/support_url.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/marketing_url.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/promotional_text.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/name.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/subtitle.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/privacy_url.txt'...
[23:43:46]: Loading './fastlane/metadata/zh-Hans/apple_tv_privacy_policy.txt'...
[23:43:46]: Loading './fastlane/metadata/copyright.txt'...
[23:43:46]: Loading './fastlane/metadata/primary_category.txt'...
[23:43:46]: Loading './fastlane/metadata/secondary_category.txt'...
[23:43:46]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[23:43:46]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[23:43:46]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[23:43:46]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[23:43:56]: Will begin uploading metadata for '1.0' on App Store Connect
[23:43:56]: Skipping 'release_notes'... this is the first version of the app
[23:43:56]: Uploading metadata to App Store Connect for version
[23:43:57]: Uploading metadata to App Store Connect for localized version 'zh-Hans'
[23:43:58]: Uploading metadata to App Store Connect for localized info 'zh-Hans'
[23:44:02]: Category 'Entertainment' from iTunesConnect has been deprecated. Please replace with 'ENTERTAINMENT'
[23:44:02]: You can find more info at https://docs.fastlane.tools/actions/deliver/#reference
[23:44:09]: Uploading app review information to App Store Connect
[23:44:10]: Error fetching app store review detail - The specified resource does not exist - There is no resource of type 'appStoreReviewDetails' with id 'null'
+--------------------+--------------------------------------+
|                       Lane Context                        |
+--------------------+--------------------------------------+
| DEFAULT_PLATFORM   | ios                                  |
| PLATFORM_NAME      | ios                                  |
| LANE_NAME          | ios release                          |
| IPA_OUTPUT_PATH    | /Users/Mac2020/Documents/workSpace/  |
|                    | 0724/soccerBall/soccerBall.ipa       |
| XCODEBUILD_ARCHIVE | /Users/Mac2020/Library/Developer/Xc  |
|                    | ode/Archives/2020-07-24/soccerBall   |
|                    | 2020-07-24 23.43.09.xcarchive        |
| DSYM_OUTPUT_PATH   | /Users/Mac2020/Documents/workSpace/  |
|                    | 0724/soccerBall/soccerBall.app.dSYM  |
|                    | .zip                                 |
+--------------------+--------------------------------------+
[23:44:10]: The provided entity includes an unknown attribute - 'demo_account_required' is not an attribute on the resource 'appStoreReviewDetails'
+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | default_platform    | 0           |
| 2    | build_app           | 26          |
| 💥   | upload_to_app_store | 37          |
+------+---------------------+-------------+
[23:44:10]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Traceback (most recent call last):
34: from /usr/local/bin/fastlane:23:in <main>' 	33: from /usr/local/bin/fastlane:23:in load'
32: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/bin/fastlane:23:in <top (required)>' 	31: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
30: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	29: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
28: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	27: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
26: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	25: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
24: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	23: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/lane.rb:33:in call'
16: from Fastfile:22:in block (2 levels) in parsing_binding' 	15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 	13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action' 	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:17:in run' 	 7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/deliver/lib/deliver/runner.rb:42:in run'
6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/deliver/lib/deliver/runner.rb:122:in upload_metadata' 	 5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/deliver/lib/deliver/upload_metadata.rb:324:in upload'
4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/deliver/lib/deliver/upload_metadata.rb:565:in set_review_information' 	 3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:122:in create_app_store_review_detail'
2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:607:in post_app_store_review_detail' 	 1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/spaceship/lib/spaceship/connect_api/client.rb:99:in post'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.153.0/spaceship/lib/spaceship/connect_api/client.rb:163:in `handle_response': [!] The provided entity includes an unknown attribute - 'demo_account_required' is not an attribute on the resource 'appStoreReviewDetails' (Spaceship::UnexpectedResponse)

The previous app_review_information should be filled out like this:
app_review_information({
first_name: " xxx",
last_name: "xxx",
phone_number: "+xxxx",
email_address<EMAIL_ADDRESS>demo_user: "",
demo_password: "",
notes: ""
})
But if you fill in this way and report more errors.

I'm getting the same error after updating to 2.153.0.

upload_to_testflight hangs as well once build has been uploaded and when setting changelog metadata

@shizu2014 @markmuniz Which version were you both coming from?

@alex-benoit upload_to_testflight didn’t have any changes in this latest version 🤔 Would you be able to open an issue with what you are seeing? I think yours might be something different

@shizu2014 @markmuniz Which version were you both coming from?

2.152.0

Ahhh, I see the issue! I will have a new version (2.153.1) out in about an hour or so.

This is fixed in 2.153.1 now!

@joshdholtz Indeed - this was my issue https://github.com/fastlane/fastlane/issues/16932
Also related to metadata uploading but completely unrelated...


Move Repositories Across Org to Main

Overview
Github moved the repository naming convention from master to main months ago and it is time for us to migrate all projects to the standard repo-naming convention.
The process requires three steps.
1. Manually create the main branch from master and push it up.
2. Make sure all outstanding PRs are merged or notified to re-open their pull-requests against main.
3. Inside of settings on the repository change the default repository to main.
Repositories on main
Fortunately, there are a handful of repositories already on main that can be excluded from this round up.

[x] website-hugo -- already on main
[x] .github -- already on main
[x] request-for-comment -- already on main

Actions
Below are the repositories that need to be migrated to main.  As noted, it is a 3-step process.
1. Create the main branch

[x] templates
[x] governance
[x] incubator
[x] brand-assets
[x] chronologue
[x] glossaries

2. Open Pull-Requests Notified

[x] templates
[x] governance
[x] incubator
[x] brand-assets
[x] chronologue
[x] glossaries

3. Repository default Updated

[x] templates
[x] governance
[x] incubator
[x] brand-assets
[x] chronologue
[x] glossaries

Completed the work.  I ended up being able to rebase the prs via the UI in github to a new branch.  The one deviation was I put templates onto dev as the default.  And figured we'd release from main.  Does look like there is some divergence in the branches we need to account for.


Delete Nodes and Transitions

Implement delete nodes and delete transitions. Modal pops up to confirm and then snackbar appears in lower right corner to confirm. Since we cannot connect nodes yet all of the transition deletions will be disabled. To test it correctly removes the transition replace the calls to willOrphanChild in SidebarHeader with false.
Tooltip for disabled button:

Delete modal:

Snackbar confirmation:

Great job Ben, the functionality is great! Some things to consider might be moving the text from the tooltip to become part of the delete modal. I think the tooltip text is a lot to read / understand for how small the text is and where it appears on the screen. It might be more user-friendly if it pops up as part of the delete modal for nodes that can't yet be deleted. That would also mean adjusting the modal to not always have the delete button, to have different text, a different icon, etc. Also, it might be redundant to have a cancel button on the modal, an X in the top right corner, and clickAway functionality - maybe get rid of the X if possible?

Updated the expanded node for observations and show transitions for action nodes. Implementing UNDO needs some research first (PATHWAYS-253

Looks good! Issues 1 and 2 have been resolved and we have tasks for 2 and 3. One last request that I missed the first time. Can we also add a snackbar notification when we delete a transition? Otherwise this looks good to go.


Neodigm Tulip | Ghost Marquee text on the Light (ampm) gray (negative) shadow is difficult to read

Hopefully this is just a CSS issue. Test both WHITE, and GHOST themes (light / dark AMPM).

This is fixed in v3.0.


when parase datas(from net) error, how could i find the error? could print error automatic

I'm not 100% sure what you're asking, but I think you might be asking how to print the reason for decoding failures? If so, you can get to this info by decoding to Decoded instead of Optional and then printing the result. I'd have to see more of your code to be able to give you more direction than that, unfortunately.

thank you! i get the  error now


predict problem tf not defined ??

i have this problem when i try to predict using h5 file
_______________________________________________________________ Traceback (most recent call last):   File "predict.py", line 146, in <module>     _main_(_args)   File "predict.py", line 75, in _main_     yolo.load_weights(weights_path)   File "/content/keras_yolo2/keras_yolov2/frontend.py", line 83, in load_weights     self._model = load_model(weight_path, custom_objects={"yolo_loss": keras.losses.mse})   File "/usr/local/lib/python3.6/dist-packages/keras/engine/saving.py", line 419, in load_model     model = _deserialize_model(f, custom_objects, compile)   File "/usr/local/lib/python3.6/dist-packages/keras/engine/saving.py", line 225, in _deserialize_model     model = model_from_config(model_config, custom_objects=custom_objects)   File "/usr/local/lib/python3.6/dist-packages/keras/engine/saving.py", line 458, in model_from_config     return deserialize(config, custom_objects=custom_objects)   File "/usr/local/lib/python3.6/dist-packages/keras/layers/__init__.py", line 55, in deserialize     printable_module_name='layer')   File "/usr/local/lib/python3.6/dist-packages/keras/utils/generic_utils.py", line 145, in deserialize_keras_object     list(custom_objects.items())))   File "/usr/local/lib/python3.6/dist-packages/keras/engine/network.py", line 1022, in from_config     process_layer(layer_data)   File "/usr/local/lib/python3.6/dist-packages/keras/engine/network.py", line 1008, in process_layer     custom_objects=custom_objects)   File "/usr/local/lib/python3.6/dist-packages/keras/layers/__init__.py", line 55, in deserialize     printable_module_name='layer')   File "/usr/local/lib/python3.6/dist-packages/keras/utils/generic_utils.py", line 145, in deserialize_keras_object     list(custom_objects.items())))   File "/usr/local/lib/python3.6/dist-packages/keras/engine/network.py", line 1032, in from_config     process_node(layer, node_data)   File "/usr/local/lib/python3.6/dist-packages/keras/engine/network.py", line 991, in process_node     layer(unpack_singleton(input_tensors), **kwargs)   File "/usr/local/lib/python3.6/dist-packages/keras/engine/base_layer.py", line 457, in __call__     output = self.call(inputs, **kwargs)   File "/usr/local/lib/python3.6/dist-packages/keras/layers/core.py", line 687, in call     return self.function(inputs, **arguments)   File "/content/keras_yolo2/keras_yolov2/backend.py", line 46, in space_to_depth_x2     import tensorflow as tf NameError: name 'tf' is not defined

The problem was fixed, please update your fork

thanx very much
i have already fix it
any advice to improve learning score with out overfitting and early stoping

usually a custom backend for simple problems has better precision, also I don't like to use early stop, some times its stops too early


HTTP/2 in express for node v10

hi,
since now node v10 supports HTTP/2.
it would be feasible option to implement the same in express for routes ,render, session management for intern releases.
https://nodejs.org/api/http2.html

In progress in PR #3390


Any plans to test the models on smaller datasets like cifar10?

@myopengit nope, not something I plan to do.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/446 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit db86c68:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Enabling URL from open-edx server for android

how to enable PROGRAM_URL and PROGRAM_DETAIL_URL_TEMPLATE flags fot open-edx-android from open-edx server? I am unable to find any documentation on that.

This discussion has moved to our Slack channel for the Open edX community:
https://openedx.slack.com/archives/C0F0NA2F5/p1545116583026200


Resolving small API changes

Summary
Closes #29
Issue recap
Recreating list for record keeping purposes - so things can be crossed out.

(partial) Argument naming conventions

Change drift kwarg to static_hamiltonian or static_operator where applicable

Somewhat related to the above:

Add static dissipator for lindblad?
All model classes should be able to be instantiated with/without various operator types. E.g. currently operators is required for HamiltonianModel, but we should be able to instantiate with just a drift. Similarly, a LindbladModel should be able to be instantiated with just dissipators (no Hamiltonian part).

It should be "simple" to change this but may be somewhat non-trivial as the current structure implicitly makes these assumptions in a bunch of places.

(partial) Add validation to Lindblad signal setter

None currently exists.

(partial) Add validation to Hamiltonian operators in Lindblad

None currently exists.

(partial) For some reason Lindblad constructor needs Hamiltonian signals.

This should not be necessary.

While trying to resolve some of the above I realized there is another issue we should address with this:

Duplication of operator and static_operator information in the models and operator collections. This isn't such a big deal but it does make tracking down behaviour somewhat confusing. It would be good to eliminate this duplication, which should eliminate some of the circularity in the way the property setters are utilized in the constructor.

Details and comments
Current status:

Changed drift kwarg -> static_operator or static_hamiltonian depending on context. Tests are passing.

Remaining open issue: Due to the divergence between the static_operator and static_hamiltonian names, some inheritance structure has been messed up across the models and operator collections. I'm going to leave this unresolved at the moment, as decisions about handling this are going to be affected by adding a static dissipator to LindbladModel and the corresponding operator collections.
No need to add new tests for this as a the "drift" handling is already heavily tested.

Added validation to LindbladModel signal setter.

More or less already existed in the constructor, so just moved it to the signals setter.
Need to add tests for this, but will wait as the automatic setting of dissipator signals to value 1. should be revisited when static dissipator is added.

Added validation to Hamiltonian operators in LindbladModel

Refactored the validation step in HamiltonianModel to use an is_hermitian function which verifies if a 2d array is Hermitian or if a 3d array represents a list of Hermitian operators.
Added validation of hamiltonian terms in LindbladModel
Added tests for both HamiltonianModel and LindbladModel that this validation step is actually working, as well as verifying that it can be overridden by setting validate=False.
Left this part marked as (partial) as this validation will ultimately need to handle csr_matrix types as well, and whether that will be handled in this PR depends on which of this and #28 is completed first.

Allow hamiltonian_signals to be optional in LindbladModel constructor.

Made this optional but need to test.

Eliminate duplication of operator storage in models and Operator collections

Just did this for GeneratorModel and HamiltonianModel, and for their corresponding operator collections
Created two helper functions: one to update the internally stored static operators and operator list from one frame to another, and one to setup the operator collection for a given evaluation mode. These are now called by the constructor and property setters where required. (Originally this code was solely in property setters, so it required setting properties in certain orders, and required accessing data in weird ways, which is why the duplication of the operator data was necessary.)
Added tests for setup_operators_in_frame but need to add tests for construct_operator_collection
Need to clarify the interfaces for BaseOperatorCollection and BaseGeneratorModel, and the DenseOperatorCollection and SparseOperatorCollection.

Mainly, with other proposed changes to argument/property names, need to re-evaluate some of the abstract property names

Need to do the same for LindbladModel and its corresponding operator collections

Another general note:

Need to make sure the model constructors make correct use of to_array v.s. to_numeric_matrix_type, though depending on merge order this responsibility may be with this PR or with #28 .

This PR is getting somewhat sprawling but it should hopefully simplify/clarify things. From a user perspective very little has changed (renaming drift to static_operator or static_hamiltonian), but this (and other things) are modifying/simplifying the whole model and operator collection structure, so it's impacting a lot of lines of code and getting a bit hard to think about in the simple terms of each of the isolated points in the main comment.
Plan going forward:

Finish simplifying BaseGeneratorModel, GeneratorModel, HamiltonianModel, BaseOperatorCollection, DenseOperatorCollection, and SparseOperatorCollection

Knowing the naming structure we want now, remove any abstract properties from the base classes that no longer apply to the Lindblad case
Set the new helper functions as static class methods of GeneratorModel, and set HamiltonianModel to use them where appropriate instead of importing
Document and test them (in particular, configurations in which some args are None.) Some of these tests may need to wait until the type handling PR is in, but I can at least write what I expect they should be and temporarily skip them until I can rebase on that.

Do the same to LindbladModel and its corresponding operator collections

Once the above two points are in:

Modify the model classes and operator collections so that operators/hamiltonian_operators can be supplied as None

Perhaps this should be done in conjunction with the top two?

Add the type handling/testing for the points in the main comment

Additionally:

I think I may delete CallableGenerator. It's no longer used anywhere and just adds more confusion with the model interfaces
Going to scrap the plan to add a static_dissipator in this PR. This should be easy-ish to do after this PR and can be a standalone PR if we decide we really need it.

Note:

Getting GeneratorModel.transfer_operators_between_frames to work for csr matrices required modifying RotatingFrame._conjugate_and_add to work for CSR matrices (if input is csr then it will convert the op_to_add_in_fb to a csr). This is a little bit of a hack, but the type handling at the moment is still a little bit unclear. It's definitely getting better, but still needs some work. That being said, my main concern at the moment is: if the user starts with sparse, wants to work with sparse, and only builds/transforms models using standard functions, the matrices should never be turned into dense arrays. This at least achieves that.

Just added option for Dense/SparseOperatorCollection to be defined with None for operators, and evaluate with only a static operator. Added tests for this case as well as tests for error modes if collections are evaluated with neither of operators and static_operators.

Finished up with allowing GeneratorModel and HamiltonianModel to have only a static component.

Added tests to verify evaluation works.
Added validation check and corresponding test: these classes require at least one of static_operator and operators to be non-empty.
Modified signal setting validation to handle case that operators is None. If operators is None it now raises an error if signals is set to anything other than None. Added test case for this.

I think the last thing that needs to be done with these classes is to make the Hamiltonian operator validation step work for both arrays and CSR (right now it auto-converts to array).

Current status:

All required changes have been made to GeneratorModel and HamiltonianModel, and the corresponding operator collections.
Need to do the same for LindbladModel and associated operator collections:

Eliminate redundant operator storage (follow setup for GeneratorModel)
Make interface for lindblad associated operator collections cleaner, similar to the others (maybe a new abstract base class?)
Add ability for lindblad collections to function by specifying only one of all the possible operator types.

Add static dissipators at this point?

Update LindbladModel to accept only one of all possible operator types.
Change signal setter/getter for LindbladModel into two, one for hamiltonian_signals and one for dissipator_signals.

Current status:

LindbladModel has been setup and tested to work in various configurations of having different types of operators specified.
LindbladModel.signal setter has been updated to align with the signal setter of GeneratorModel in terms of validation. It still sets the dissipator coefficients to a list of ones if they are specified as None, but this will be changed once the static dissipators are added.
Linblad-associated operator collections have been revamped. These could still use improvement, but I think they are starting to converge.

The vectorized versions have been setup now to inherit essentially all of their functionality from other classes. The MRO is a bit weird for these so I don't think this is yet the "right" version, but whether or not this should be improved upon in this PR or in subsequent work will be a matter of discussion in review.
There are not a lot of conditional checks in RHS evaluation - a potential thing to modify for speed in the future.

To do:

Add static dissipators + testing
Could always add more tests generally with all of these changes, but i'm starting to feel fairly satisfied with where the tests are at.

Note: I've decided to not update rotating_wave_approximation to work directly with sparse matrices. This is a standalone task that deserves some thought. For now I've modified rotating_wave_approximation to explicitly convert everything into dense arrays. Note that it still work son sparse models, it just uses dense arrays intermediately while doing the approximation.

I believe I've addressed all comments. Aside from small changes which I've commented on above, substantial changes are:

Made in_frame_basis a property of the models, along with static_operator, operators, and the corresponding LindbladModel equivalents.

The original get_static_operator, etc... have been made private, and the properties call this, using the in_frame_basis property.

Added in_frame_basis kwarg to constructors for the models and Solver, and added handling of this kwarg to solve_lmde, solve_ode, and rotating_wave_approximation (all of these functions do computations in the frame basis, and now they need to check whether to transform things into/out of the frame basis at the beginning/end)
I've made all of the class methods into standalone helper functions.
Not related to any comments, but something I realized was missed in the Solver class: added the validate kwarg to Solver construction, so that a Solver can be constructed with validation of hamiltonian operators being skipped.

Added a test to check that a Solver can be constructed within a function to be jitted.

Still to do:
Started to fix up the notebooks, but there seems to be an error now in the RWA for the lindblad model in general_demo.ipynb. Will need to fix this, and add a test to catch whatever is happening.

To explain in_frame_basis:

Setting it to True makes the model evaluation functions evaluate in the basis in which the frame is diagonal (as per the decomposition given by np.linalg.eigh).

If the rotating_frame is None, or was supplied in already diagonal form as a 1d array, this kwarg/property has no effect.

I thought the default False was natural as "entering a rotating frame" is perfectly well defined irrespective of what basis things are written in, so setting in_frame_basis=True feels like an additional action that the user should have to manually specify.
In terms of which basis to solve in: I do believe that it's always better to solve in the basis in which the frame is diagonal.

It is strictly cheaper than in a basis in which the frame is non-diagonal (for this package everythign is internally stored in the frame basis, so if you compute things in a different basis there is the additional step of mapping the generator/state out of the frame basis).
I've written solve_ode and solve_lmde to always solve in the frame basis, whether model.in_frame_basis is True or False. Before solving, if model.in_frame_basis=False, it will temporarily set it to True, map the state into this basis, solve, then map the output back to the original basis and set model.in_frame_basis back to False.

As explained in the second point it seems to me to default it to True, and due to the last point it shouldn't have any effect on the efficiency of solving one way or the other.


Add FSharPlus.Data types

I was wondering, since F#+ is anyway a dependency of this project, is there any drawback in adding F#+ Data types like NonEmptyList and so on, to the overload list ?
At the moment I can't think of any downside.

This would be a great addition. I had to write one for NonEmptyList and although easy to write it would be great to get out of the box here.

This was completed in 0.10.0


Allow a subset of Markdown

With code block support, I think it would make sense to allow a real markdown (subset).
The most common things I would use (and you can sometimes see in use on Twitter) are bold, italic, lists and inline code.
The "document"-oriented markup like headings could get abused and don't really make sense in a tweet, as well as links and images, which Twitter already handles differently.

If anyone wants to work on this, you can continue where https://github.com/sindresorhus/refined-twitter/pull/113 left off.

Closing as this extension is now deprecated: https://github.com/sindresorhus/refined-twitter/commit/8dd9df749d3a4e82c95b2bd6628c8d65f0f72e6c


Feature/fixing unit tests

fixing part of the unit tests that fails to compile. ./client/transaction-pool  and ./client/basic-authorhisp tests still fails to compile so i disabled them temporarly and created proper ticket

@gleb-urvanov https://trello.com/c/9BYtUew0/144-fix-transaction-pool-basic-authorship-unit-test


alexa discovery not working (NOT USING Home Assistant)

SUMMARY
I have an alexa echo dot 4th Gen connected to my wifi, I have a linux box with 2 ips, one for my own stuff with apache (<IP_ADDRESS> only) and one  for node-red (listening on <IP_ADDRESS> only). node-red-contrib-amazon-echo is on port 80 on <IP_ADDRESS>.
Running as root.
I'm NOT USING home assistant
ECHO DEVICES

Echo Dot 1st generation
Echo Plus 2nd generation

MODULE VERSION

0.1.10

CONFIGURATION

[
    {
        "id": "39f31d24c7dfae5d",
        "type": "amazon-echo-hub",
        "z": "6cc8f080d76fe305",
        "port": "80",
        "processinput": "3",
        "discovery": false,
        "x": 270,
        "y": 280,
        "wires": [
            [
                "c4eaa9dc9fb1c0af"
            ]
        ]
    },
    {
        "id": "c4eaa9dc9fb1c0af",
        "type": "amazon-echo-device",
        "z": "6cc8f080d76fe305",
        "name": "Persianas Salon",
        "topic": "switch2 false",
        "x": 540,
        "y": 280,
        "wires": [
            [
                "79e0f932c3d19140"
            ]
        ]
    }
]

CONSOLE OUTPUT

30 May 14:21:07 - [info] Node-RED version: v2.2.2
30 May 14:21:07 - [info] Node.js  version: v18.0.0
30 May 14:21:07 - [info] Linux 5.15.0-33-generic x64 LE
30 May 14:21:07 - [info] Loading palette nodes
30 May 14:21:08 - [info] Dashboard version 3.1.7 started at /ui
30 May 14:21:08 - [info] Settings file  : /root/.node-red/settings.js
30 May 14:21:08 - [info] Context store  : 'default' [module=memory]
30 May 14:21:08 - [info] User directory : /root/.node-red
30 May 14:21:08 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 May 14:21:08 - [info] Flows file     : /root/.node-red/flows.json
30 May 14:21:08 - [info] Server now running at http://<IP_ADDRESS>:1880/
30 May 14:21:08 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

30 May 14:21:08 - [info] Starting flows
30 May 14:21:08 - [info] Started flows
30 May 14:21:08 - [info] [tasmota-mqtt-broker:ca68e347c2565417] Connected to broker: mqtt://<IP_ADDRESS>:1883

STEPS TO REPRODUCE

Echo dot 4th gen on wifi, node-red on wired computer.
EXPECTED RESULTS

You must be able to find devices, i supposed. I tried with mobile alexa app and echo dot
ACTUAL RESULTS

Maybe it is a problem with packets between wifi and wired computer.


Using enum inside export value gives error in 3.0.1.

OS: Ubuntu Linux 17.10
Godot version: Godot_v3.0.1-stable_x11.64
I use my own enum inside a script that gets loaded into a bunch other scripts. So I use this file as my source for global values. However in the latest version of Godot this doesn't seem to work anymore. I don't know if this is me using it wrong or this is a bug, please tell me. :smile:

Example project:
BugReport.zip

Hi! Thanks for the bugreport and sorry about this. This is exactly the sort of breakage I'm trying to avoid in the stable series. I'll figure out why this is happening and make sure this gets fixed in 3.0.2 or at least documented if this is somehow unavoidable.

So the good news is that it appears to be cosmetic. The functionality still works so it's a problem with the editor. It won't actually break your game. So this can be fixed in 3.0.2. If this is too annoying to work with please revert to 3.0 for the moment :-/

Caused by b7faa76485be1cfe368d24e4fe30adf252beedbe

Oh, I'll see if I have time to have a look at what my commit broke when I get home.
My guess right now would be that due to GDScript no longer forgetting if it was called for autocompletion/validation some bug elsewhere was exposed but I can't say for sure without doing some debugging.

@x1212 Instead of calling clear() in _parse_bytecode() and parse() duplicating all of clear() except clearing the already data seems to solve this issue.
	completion_type = COMPLETION_NONE;
	completion_node = NULL;
	completion_class = NULL;
	completion_function = NULL;
	completion_block = NULL;
	current_block = NULL;
	current_class = NULL;

	completion_found = false;
	rpc_mode = ScriptInstance::RPC_MODE_DISABLED;

	current_function = NULL;

	validating = false;
	for_completion = false;
	error_set = false;
	tab_level.clear();
	tab_level.push_back(0);
	error_line = 0;
	error_column = 0;
	pending_newline = -1;
	parenthesis = 0;
	current_export.type = Variant::NIL;
	error = "";

instead of clear() I also put the clear() back in _parse() as I couldn't quite figure out why it had to be removed.

You can also fix this by replacing the !validating with true in line 456 of modules/gdscript/gdscript_parser.cpp ... so I guess the problem is that now that the validating member works, some optimization in the parser supposed to make validating faster breaks validating?
The part that isn't executed now is supposed to load preloaded scripts ... and the errormessage is caused by the parser not understanding that target_types is a const member of the preloaded const script.

Just saw that 3.0.2 already got it's first rc ...
I wanted to look for a better solution but I guess I'll create a pullrequest today that removes that !validating condition for parsing preloaded scripts.

Tested it in 3.0.2 and it seems to be fixed! Thanks!

It's still valid in the master branch though.

Why is this merged into the 3.1 master branch? I'm waiting for so many new features and bug fixes in 3.1.


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit 6c6d4cf:
:clock10: Pending: waiting for processors (26 builds ahead of you)
:warning: Docs Build is busy, currently there are 26 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6c6d4cf:
:clock10: Full build: the average full build time is 7 min(s) 49 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 6c6d4cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Intergate streaming plugin with annotation plugin.

Hi, your plugin is very neat and useful. Thanks for the effort!
As I'm trying to create a real time data control chart. I'm using your plugin for streaming data and annotation plugin to draw UCL & LCL (Upper Control Limit & Lower Control Limit) lines. The problem is that when the chart is moved to the left, the annotation lines, which must be static, are moved as well. Screenshot attached below.

Is it possible to make the annotation lines static just like the axises? Thanks in advance!

Thanks for trying the plugin!
As chartjs-plugin-streaming moves every element in a chart, the annotation lines and labels are also moved. A workaround at this moment is:

Include chartjs-plugin-streaming.js before chartjs-plugin-annotation.js

<script src="chartjs-plugin-streaming.js"></script>
<script src="chartjs-plugin-annotation.js"></script>

And, use 'afterDraw' for annotation.drawTime and annotation.annotations[*].drawTime

This will solve your problem. I will investigate how to fix in the other cases.

Work perfectly! Thank you again!


Original date stamp (March 7)

Content to be added or changed:
There needs to be a date at the top of the page, perhaps with the original March 7 date

The title now displays the last update timestamp (see screenshot). Is that what you meant? Would you confirm so I close this issue?


merged dom-expressions into the repo

This PR looks big, but there's lots of CRLF/LF conversions. The main changes are:

move dom-expressions into the solid repo
update package.json depdendencies (remove dom-expressions dependencies, add them to local package's package.json as needed) so that they are linked into each dependent by Lerna
gitignore build artefacts that are currently copied into the source src folder
rollup.config now copies files from the local packages instead of the ones in node_modules.

Other than that, it's only new files from those packages, and all the line ending changes (respecting editorconfig).

Added a new commit. It is easier to check out any new commits individually rather than looking at the Files changed tab.

@ryansolid Oh goodness, master conflicts with this PR everywhere due to the line endings.

I wasn't expecting you to keep adding more stuff. I am not particularly in favor of the first commit. And in parallel started working on the other stuff you mentioned.

Actually, nevemind, I was being hasty, the conflicts are the deleted files only

I am not particularly in favor of the first commit.

Something that kept throwing me off is looking for code in Solid's repo that's actually coming from dom-expressions.
I think it can easier to understand if they're in the same repo. After all, they're all made by solid (you and contributors).

I suppose but the intent is to support multiple libraries. Yes there are only 6 currently to my knowledge and I wrote them all. But I really was intending it to be its own thing. There are many things that I do intentionally not to tie it specifically to Solid etc... Maybe it's time for the experiment to be over but that was idea anyway.

merged master to here, no conflicts.

I suppose but the intent is to support multiple libraries

Having the packages here in this repo doesn't prevent you from supporting those libs (yours or not).
I think it is really nice stuff actually. Do you think you could (or do you?) support SSR with arbitrary reactive libs plugging into the templates (f.e. mobx-jsx)?

I'm still planning to make lume-jsx (or some name) at some point, hooking into the system like mobx-jsx, etc.

Btw, if there's something you like about someone's PR and want to take only that part into master, it can be nice if you let the author know, then they can get their name onto the commits (vs having them sniped and getting no credit).

Yeah it takes a bit more setup so I haven't bothered but everything is done in a generic way so no reason any of those other libraries couldn't have the same SSR capability. I've done more with Solid like create a static non-reactive runtime for scenarios that don't need it. But ignoring those kind of things it's definitely doable. The reason I stopped was Solid's SSR is hinged on Suspense and I didn't bother implementing it in the other libraries. Although to be fair ignoring Transitions (Concurrent Mode type stuff) we could implement Suspense in the other libraries.

Although to be fair ignoring Transitions (Concurrent Mode type stuff) we could implement Suspense in the other libraries.

That's awesome. :+1:


Web identity proof failure

I'm not seeing the web identity proof succeed for http://trevor.caira.com/keybase.txt (my username is toc).

OK Proof for trevor.caira.com failed: No server-given hint for sig=ac405d5580edfdc7f81c994a4c1303e160715489344f7f2be8fcb3a0314fd3d20f (code=306)

same.
Do you finalfy fix the problem ? and how to ?


Volume script does not work properly with Retropie 4.7, not muting.

I downloaded the latest RP image, 4.7, ran the script, and instead of it being mute/quiet/loud, it was quiet/loud/super loud.
It won't mute. Thanks.

Fixed it myself, I had to edit /boot/cmdline.txt and add:
snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_compat_alsa=1
This reverts the audio settings back to the previous configuration before they broke it in the newer releases.


Fuuraiki 3 [PCSG00493]

App summary

App name: Fuuraiki 3
App serial: PCSG00493
App version: 1.01

Vita3K summary

Version: v0.1.5
Build number: 2663
Commit hash: https://github.com/vita3k/vita3k/commit/e8151664
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game runs at full speed and is fully playable, though config menu and diary texts are missing.
Screenshots

Text missing:

Log
vita3k.log
Recommended labels

Playable
text missing

With the missing text issue gone, the game is fully playable now.
App summary

App name: Fuuraiki 3
App serial: PCSG00493
App version: 1.01

Vita3K summary

Version: v0.1.5
Build number: 2683
Commit hash: https://github.com/vita3k/vita3k/commit/b3a44b5
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game plays at full speed without any issue.
Screenshots

Log
vita3k.log
Recommended labels

Playable
graphics bug

hi, my game doesn't render background image on build 0.1.5 2796, it only show text, do you have any idea?


New Crowdin translations

For https://github.com/getferdi/ferdi/issues/340.

Regex to find unexpectedly translated variables when searching in i18n/**/*.json:
\{(?!version|seconds|currency|price|name|amount|count|limit|default|plan|duration|time|service|field|license|size|length|interval)(.*)\}

@vantezzen I'm not sure why some files are out of sync; could it be mismatching locale names for the files? I don't see many configuration options in https://crowdin.com/project/getferdi/settings#integration:
I thought about locale file names mismatch because we have 3 files for Chinese but in Crowdin there's only 2 (Traditional/Simplified).

@vantezzen I am not sure why some files are out of sync. The configuration dashboard at https://crowdin.com/project/getferdi/settings#integration doesn't give much indications:

Maybe the locale file names need an update/triage? I noticed there is three translations files related to the Chinese language when there should be two. I will double check.

@vantezzen Example with f6630d0 above, while Crowdin is in that state for that string:

I apparently missed to update a Serbian string before overriding the ones I thought out-of-sync; it got reverted by the bot via f6630d0. I updated it in Crowdin but now the update doesn't seem to be picked up. @vantezzen is that something I should report to Crowdin you think?

I got my answer 😄

[ ] nb-NO.json should be nb.json
[ ] ua.json should be ru-UA.json
[ ] zh.json should be zh-CN.json

Not sure what should be made of zh-HANT.json
Source: Crowdin Language Codes

@kytwb We should squash merge future CrowdIn PRs as these commits really clutter the commit history.

@vantezzen noted! 👌 I've also fine-tuned AppVeyor builds to skip commits containing edits on src/i18n/locales/*.json files only via 8a6c744f.


Added course description to model/seeds. Added displaying courses students are enrolled in.

Set force flag to true to update the db.


Experimental support for running dbt-duckdb against a Buena Vista-based proxy server

One of my fun hobby projects is a pure-Python Postgres proxy server called Buena Vista (BV) that I have written a DuckDB-based impl for: https://github.com/jwills/buenavista/blob/main/examples/duckdb_server.py
I started working on it because a) I have always wanted something like it as a way to play with SQL query rewriting in ways that a regular database won't let you do and b) because I realized in doing dbt-duckdb development work that it's actually really convenient to be able to simultaneously query your database from one place (using e.g. DBeaver or pgcli or whatever your tool of choice is) while also running dbt models against your database in another terminal/shell. Since DuckDB (currently) has a rule that if one process has write privileges to a DuckDB file, then no other process is allowed to talk to that file, I needed a way for both dbt and my query tool of choice to connect to the same DuckDB database file and do work against it-- ya know, like, the way a database usually works.
This PR creates a way to specify in the credentials for the dbt-duckdb target that the adapter should connect to a BV server instead of opening the DuckDB file on the path directly. My thinking here is that for the dev target, someone could use a BV server to do their development work, but a prod (or whatever) target would just write the DB file directly (so no proxy server, just run as normal against the DuckDB file in process.)
Note that I am using psycopg2 as the driver here; I tested out a lot of them but I chose psycopg2 b/c of its popularity, the fact that dbt uses it for dbt-postgres already, and the fact that it does all of the parameter bindings for prepared statements locally which helps a lot with the performance and simplicity of the BV implementation.
There are a few questions that I've been thinking about that I would like some feedback on:

Right now, specifying the host and port arguments in the target config means that we will completely ignore the path argument and just talk to the BV server directly (which right now, is configured to load a DuckDB file of its own when it is initialized)-- is that the right thing to do? Or should we keep the path arg in play and somehow communicate the path to the BV server so that it opens the DuckDB file at that path as its primary database (if it hasn't done so already?) That might involve refactoring the BV server a bit so that it could support having connections to multiple DuckDB files at once, which doesn't seem so bad and might actually be good?

The BV server does not currently support Python models, but since it's a Python service itself, I think it would be relatively straightforward to do so; the main question is how we would communicate to the BV server that the "query" it's getting is a python script that it needs to execute instead of a SQL query? Should it be a separate/dedicated endpoint on the BV server itself? Should it be a "mode" that you can put the Postgres connection into so that it interprets the query payload it receives as Python instead of SQL?

Is there other stuff I should have thought about but haven't yet?

Closing this up as I figured out a better way to solve this problem that I'm pretty excited about. 😄


New weight classes are not instantly shown the league overview

Adding a new weight class does not refresh the parent league overview.

Can you reevaluate if this issue still persists after the changes?
https://wrestling-scoreboard.oberhauser.dev/
I didn't experience that any more.
But I noticed if editing a weight class, the weight class info is not updated.

I can reproduce neither, both seem fixed. A new weight class does show up in the parent league. Changing any details of the class will update immediately  in the parent league.


Reword/reconsider recommended drive size warnings

Based on a comment chain in #2014: the recommended drive size warning message is a bit ambiguous at the moment with "Not Recommended" – it's not clear to the user what isn't recommended, in this case it being the size of the drive in relation the the image. Also brought up is whether the recommended size field is actually used in practice.

We could change "not recommended" to "image recommends nGB"


Create issue templates

Provides a bug report and a feature request template.

Thanks, @aevesdocker! I've pushed your suggestions 😄


sqlite3_statement_backend::loadOne: database is locked

Dears,
This might be related more to sqlite than SOCI itself, but I havn't found much information about this issue on the web, so I'm just asking here!
I'm using a connection pool and my sqlite is build with SQLITE_THREADSAFE, and while Read operations (select) don't seem to be an issue, Write ones (Update, Replace, Insert) keep poping the same issue:
sqlite3_statement_backend::loadOne: database is locked

Thanks in advance!

Closing as related to SQLite and client-side workaround. SOCI can't really help, unless there's update in SQLite API, I guess.


How to use concat with IProperty

How can I concat a few fields ?
I don't find any way to do this.
Thank you

going to be in develop branch soon :) this will need to be added to IProperty. thanks for reminder.

in develop


Thank you for the great app

Did a lot of templates in the past and was always a pain in the a…
Now found MJML and was surprised how simple and clever it is built.
i use the mac app. its sufficient for me. but api looks interesting as well.
And best of all its free?? Really? Why? I would even pay for it (one time payment of course).
found mjml today through google and now we have the best email template ever since.
checked it in litmus – looks well everywhere.
THANK YOU!

👍


Installation issue

I'm trying to install a copy of cgat locally for myself on a shared computing cluster ie:
pip install -install-option="--prefix=~/PythonPackages" cgat
However I get the following error (the same occurs if I follow the instructions for manual installation) :
"Downloading/unpacking cgat
Running setup.py egg_info for package cgat
Traceback (most recent call last):
File "< string >", line 14, in
File "/nfs/users/nfs_t/ta6/PythonPackages/cgat-python/build/cgat/setup.py", line 250, in < module >
pysam.get_libraries()]
AttributeError: 'module' object has no attribute 'get_libraries'
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "< string >", line 14, in
File "/nfs/users/nfs_t/ta6/PythonPackages/cgat-python/build/cgat/setup.py", line 250, in < module >
pysam.get_libraries()]
AttributeError: 'module' object has no attribute 'get_libraries'
I've updated Pysam but that did not resolve the issue.
Tallulah

Hi Tallulah,
What's the output of these commands:
which python
echo $PYTHONPATH
which pip
pip list | grep pysam
python -c "import pysam; print pysam.__version__"
python -c "import pysam; print pysam.__file__"

Best regards,
Sebastian.

which python
/nfs/users/nfs_t/ta6/PythonPackages/cgat-python/bin/python
echo $PYTHONPATH
/nfs/users/nfs_t/ta6/.local/lib/python2.7/site-packages/:/nfs/users/nfs_t/ta6/PythonPackages:/nfs/users/nfs_t/ta6/RNASeqPipeline/software:/nfs/users/nfs_t/ta6/RNASeqPipeline/software/usr/local/lib/python2.7/dist-packages/:/usr/local/lib/python2.7/dist-packages/:/nfs/users/nfs_t/ta6/PythonPackages/lib/python2.7/site-packages/:/nfs/users/nfs_t/ta6/.local/lib/python2.7/site-packages/:/nfs/users/nfs_t/ta6/PythonPackages:/nfs/users/nfs_t/ta6/RNASeqPipeline/software:/nfs/users/nfs_t/ta6/RNASeqPipeline/software/usr/local/lib/python2.7/dist-packages/:/usr/local/lib/python2.7/dist-packages/:/nfs/users/nfs_t/ta6/PythonPackages/lib/python2.7/site-packages/:/nfs/users/nfs_t/ta6/PythonPackages:/nfs/users/nfs_t/ta6/RNASeqPipeline/software:/nfs/users/nfs_t/ta6/RNASeqPipeline/software/usr/local/lib/python2.7/dist-packages/:/usr/local/lib/python2.7/dist-packages/:/nfs/users/nfs_t/ta6/PythonPackages/lib/python2.7/site-packages/:
which pip
/nfs/users/nfs_t/ta6/PythonPackages/cgat-python/bin/pip
pip list | grep pysam
Usage: pip COMMAND [OPTIONS]

pip: error: No command by the name pip list
(maybe you meant "pip install list")

python -c "import pysam; print pysam.version"
0.7.5
python -c "import pysam; print pysam.file"
/nfs/users/nfs_t/ta6/RNASeqPipeline/software/usr/local/lib/python2.7/dist-packages/pysam/init.pyc

Hi,
I would try upgrading pysam first:
pip install pysam==0.8.4

and check that you are running that version (0.8.4):
python -c "import pysam; print pysam.__version__"

Then, try reinstalling the cgat code.
If that option does not work either, I would try:
wget https://raw.github.com/CGATOxford/cgat/master/install-CGAT-tools.sh
bash install-CGAT-tools.sh --cgat-scripts --location /nfs/users/nfs_t/ta6/PythonPackages/cgat-conda

Best regards,
Sebastian.


Enable $env:PAGER to work correctly if arguments are used

PR Summary
If $env:PAGER is a command with args, it doesn't work correctly as the current code tries to find a command matching $env:PAGER which fails due to the args.  Fix is to split $env:PAGER into the command and the args, find the first occurrence of the command and pass back the args.
No tests as this is interactive only.  Manually validated with less -w which highlights the first lien of a new page.
Fix https://github.com/PowerShell/PowerShell/issues/6142
PR Checklist
Note: Please mark anything not applicable to this PR NA.

[X] PR has a meaningful title

[X] Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[NA] User facing Documentation needed

[ ] Issue filed - Issue link:

[X] Change is not breaking
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

@anmenaga @daxian-dbw Have you any thoughts or change requests?


[es] Update translations

Text changes:

h1: Accessibility Myths
Myth 6: Web accessibility is just a developer's responsibility
Myth 9: Accessibility can be fixed by the accessibility overlay
Myth 11: Accessibility is only for blind users
Myth 18: Accessibility is like a feature - you do it once and then you have it

Hi @pazguille, I updated some text, would you find time to translate it?

#47


Fix deprecation warning

Get rid of deprecation warning - all callbacks should be called with (error, result) format.

The Travis build failed with node 0.12. This is caused by the style-loader's 0.13.2 release, which upgraded the loader-utils to 1.0.2. And loader-utils 1.0.2 only supports node engines +4.


filter taxa by abundance threshold or clade

E.g., set threshold for mean abundance, minimum abundance, max abundance from within the visualization (as opposed to filtering taxa programmatically prior to creating the .qzv file). Also filter by taxonomy (e.g., only show Gammaproteobacteria). Generally better to do programmatically, yes, but what if a user wants to feel out the perfect settings for showing a comprehensible list of taxa? Can add as a tab in an emperor-style sidebar.
Also, removed taxa should appear in a dock within the filtering menu, as suggested for samples here. Allow dragging/dropping taxa from plot to dock and vice versa to manually select what appears. E.g., a user might want to show all taxa above a certain threshold, plus rare taxa of interest, which can be dragged back out of the dock into the plot. The current function, whereby taxa are removed/added by clicking on them, is great but the advantage of the "dock" is that only visible taxa appear in the legend, which is nice for making publication-ready figures.

:+1:
Im also a big proponent of capping the number of bars that are shown the in the bar chart. I'd like to be able to just collapse on the fly.


⚠ Secret Website 3 has degraded performance

In 5eeb3f8, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2912 ms

Resolved: Secret Website 3 performance has improved in 9b4b9dc.


Support for React 17

LGTM, everything seems to be working fine

LGTM! Can't use it in new projects!

any update?

There is no restriction for using react 17.x.x with this package. Currently a warning will be displayed when using this package under a package with a react greater version than 16.8.6.
I just need to verify mui-rte can work correctly with react 17 and will update the peer dependencies version range. For now you can just simply use the react version you need.

@niuware I cannot install the mui-rte package in a create-react-app / material-ui environment due to the React version:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@material-ui/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS><5" from<EMAIL_ADDRESS>npm ERR!     node_modules/mui-rte
npm ERR!       mui-rte@"*" from the root project
npm ERR!     1 more (@material-ui/icons)
npm ERR!   2 more (react-dom, @material-ui/icons)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/mui-rte
npm ERR!   mui-rte@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Do you recommend installing using the --force or --legacy-peer-deps flags?

Version 1.29.0 allows the use of React 17.0.x.


Support for React Native 0.68+

Describe the solution you'd like
React Native from 0.68 is now using Java 11. A version selector similar to the Node version selector should be added to handle this. Currently, I don't think there is a way for me to build my app, so for Android, I have to push it manually to the store.
Describe alternatives you've considered
There is no alternative for future versions of RN.
Additional context
From the RN docs at https://reactnative.dev/docs/environment-setup
If you have already installed Node on your system, make sure it is Node 14 or newer. If you already have a JDK on your system, make sure it is version 11 or newer.

Hi @lostchopstik thank you for getting in touch with us!
You can't build your React Native project on the portal?

Hey there. No, I currently get this error when running a build on Android:
* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.android.internal.application'.
   > Android Gradle plugin requires Java 11 to run. You are currently using Java 1.8.
     You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.

Hey @lostchopstik you can set the JAVA_HOME variable in AppCenter to 11 to overcome this.
In App Center, under your Build Configuration you can set the JAVA_HOME to $(JAVA_HOME_11_X64)

Save and Build, and you're good to go.
You can ignore the other names I have in the build configuration, those are specific to my project.
I recently moved my projects' compileSdkVersion  to 31 and basically anything 31 and above for Android requires Java 11, so I ran into what you're facing too. The above did the trick, hope it helps

Thanks for the workaround @sabun123!

setting JAVA_HOME as $(JAVA_HOME_11_X64) is not working anymore. It is throwing unknown error. Any suggestion ?


add section to change year

Hi could you please provide more description on this

only shows 2023 data. i need a way to show previous years as well


recognize git-for-windows as windows

This seems to fix https://github.com/scrooloose/syntastic/issues/1613 for me

Please refrain from making changes without fully understanding what the code you're changing is supposed to do.  Your patch (1) removes the check without solving the problem, and (2) breaks other things.  Sorry, but no.

I made this change, to my local version, and saw it silenced all the errors I was seeing (reported in #1613 ).  I knew there was a chance this might not be the right fix though


Unexpected token

Hi
I am trying to use this in my ng2 app but when I add "PerfectScrollbarModule.forRoot(PERFECT_SCROLLBAR_CONFIG)" into my NgModule imports it throws below exception. If i remove this from import app works fine.
(index):72 Error: (SystemJS) Unexpected token <
SyntaxError: Unexpected token <
at eval ()
at Object.eval (localhost:52432/app/app.module.js:23:36)
at eval (localhost:52432/app/app.module.js:49:4)
at eval (localhost:52432/app/app.module.js:50:3)
Evaluating localhost:52432/angular2-perfect-scrollbar
Evaluating localhost:52432/app/app.module.js
Evaluating localhost:52432/app/main.js
Error loading localhost:52432/app/main.js
at eval ()
at Object.eval localhost:52432/app/app.module.js:23:36)
at eval (localhost:52432/app/app.module.js:49:4)
at eval (localhost:52432/app/app.module.js:50:3)
Evaluating localhost:52432/angular2-perfect-scrollbar
Evaluating localhost:52432/app/app.module.js
Evaluating localhost:52432/app/main.js
Error loading localhost:52432/app/main.js
Could you please help me identifying the issue.
Thanks

It's more looks like your system.config.js wrong (or any other bundler config, which you using).
That error, usually appears, when you try load library, but server don't find it and return just html with first symbol "<". That's why you see Unexpected token <.
So you need to check your config file, which import library.
Also, if you want to specify, which library can't loading, try to return 404 error, instead of 404 page from server (only when loading library).

But when remove  "PerfectScrollbarModule.forRoot(PERFECT_SCROLLBAR_CONFIG)" from import list app works fine. so doesn't that mean something is going wrong when importing this module/library?
Below is my system.config.js
`
(function (global) {
System.config({
paths: {
// paths serve as alias
'npm:': 'node_modules/'
    },
    // map tells the System loader where to look for things
    map: {
        // our app is within the app folder
        app: 'app',
        // angular bundles
        '@angular/core': <EMAIL_ADDRESS>        '@angular/common': <EMAIL_ADDRESS>        '@angular/compiler': <EMAIL_ADDRESS>        '@angular/platform-browser': <EMAIL_ADDRESS>        '@angular/platform-browser-dynamic': <EMAIL_ADDRESS>        '@angular/http': <EMAIL_ADDRESS>        '@angular/router': <EMAIL_ADDRESS>        '@angular/forms': <EMAIL_ADDRESS>        // other libraries
        'rxjs': 'npm:rxjs',
        'angular-in-memory-web-api': 'npm:angular-in-memory-web-api',
        '@angular/material': <EMAIL_ADDRESS>        'angular2-perfect-scrollbar': 'npm:angular2-perfect-scrollbar'

    },
    // packages tells the System loader how to load when no filename and/or no extension
    packages: {
        app: {
            main: './main.js',
            defaultExtension: 'js'
        },
        rxjs: {
            defaultExtension: 'js'
        },
        'angular-in-memory-web-api': {
            main: './index.js',
            defaultExtension: 'js'
        }
    }
});

})(this);`

Main file index.js is in the folder lib. So, with your map block, you need to specify path to index.js in the packages block.
At least for me, it's looks like:
 map: {
        // Other libs
        'angular2-perfect-scrollbar': 'npm:angular2-perfect-scrollbar'
    },
packages: {
        // Other libs
        'angular2-perfect-scrollbar':   { main: 'lib/index.js', defaultExtension: 'js' }
    }

And the reason, why everything works, when you remove PerfectScrollbarModule.forRoot(PERFECT_SCROLLBAR_CONFIG) is because application don't try to load library and as result everything works fine

yes, needs to set main to 'lib/index.js'
Thanks


Add katex support in documentation.

This commit adds latex support within rustdoc for arkworks algebra.
In order to add latex code in textmode, use delimiters $ and $.
In order to add latex code in displaymode, use delimiters $$ and $$.
To compile the documentation, use cargo rustdoc.
This is achieved via the option --html-in-header set via

the environment variable RUSTDOCFLAGS, or
the variable build.rustdocflags of .cargo/config.toml
I opted for the latter making it a default compilation flag to use with
rustdoc.

IMPORTANT: for some reason (independent from us) cargo rustdoc fails
on rust nightly and this is due to a failure concerning cfg-if and
rand-chacha. I did not investigate the reason why this happened.

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (master)
[ ] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the GitHub PR explorer

Great, right now doctests (cargo test) fail because the documentation path is incorrect:
instead of doc/katex-header.html it expects ../doc/katex-header.html.
However, cargo rustdoc expects doc/katex-header.html instead of ../doc/katex-header.html.
We have two options:

we YOLO it, and let the user set the option --html-in-header or the env variable RUSTDOCFLAGS manually.
we create a makefile inside each package with the following content:

doc:
	cargo rustdoc -- --html-in-header doc/katex-header.html

The latter is what's being used in curve25519-dalek, but would pollute the build environment :(
This affects only local compilation and shouldn't concern upload to docs.rs, which is already dealt with.

@mmaker would using the solution in this issue work? https://github.com/rust-lang/cargo/issues/9427
We would have to switch to running doctests on nightly only, but that's fine IMO

Ok after some investigation:
rustdocflags = "-Zdoctest-in-workspace --html-in-header doc/katex-header.html"
clearly does not work because it's not a rustdoc option. After some hacking around, the following option is what we want:
doctest-in-workspace = true```

Now `.cargo/config.html` looks like the following:

Add support for katex, and work around rust-lang issue #8097.
https://github.com/rust-lang/cargo/issues/8097
[target.'cfg(nightly)']
rustdocflags = "--html-in-header doc/katex-header.html"
Without this line, one among cargo test --doc and cargo rustdoc
will fail due to the relative path in the --html-in-header option for rustdoc.
[unstable]
doctest-in-workspace = true```
Note the target.cfg(nightly): without it, on rust stable we'd have cargo test --doc fail because of the relative path issue...
However, now we have nother problem: target.<cfg> sections only define rustflags and not rustdocflags... therefore we're back to square one.

Force-pushing this pull request with a makefile-based workaround (similarly to what's done in curve25519-dalek...


(SERVER-2320) Allow generation of an authorized cert offline

The cert used by the CA CLI needs to have a special auth extension that
is disallowed by the Puppet Server CA, to prevent any node from
requesting a cert with the special permissions. Previously, this cert
was always created along with the rest of the CA files.
This commit adds a way to generate an authorized cert with the special
extension, from an existing CA. The special cert is signed offline, not
through the main Puppet CA. It can be generated with values for the
master, or with values for other nodes. In the latter case the cert and
keys will need to be distributed manually.
This also updates generate to not use the subject_alt_names
setting. This setting is supposed to be specific to the master node, but
generate can be used to create certs for any node, and those shouldn't
necessarily have the master's alt names. When using generate, the user
needs to specify both certname and any alt names manually.

Some questions here:

Do we only want to allow creating CA client certs when the server isn't running?
Should it overwrite existing files?
Do we like this UX, or should this be its own command/a different flag?
Do we want to call out that we're not going through the CA API in logging?

Manually verified that this works. Created a CA using pupeptserver ca setup, deleted the master cert, ran puppetserver ca generate ... --ca-client, it overwrote all the other files that were still hanging around (signed dir, keys), then I could successfully talk to the server again. Didn't even have to HUP it.

If we like this approach I'll add a couple more tests to generate.

Updated with extra/better tests.

Sorry, missed those comments:

Some questions here:

Do we only want to allow creating CA client certs when the server isn't running?

Yeah, I think we want to be able to assume that when the CA is running it is canonical and doesn't need to coordinate with other processes (for updating the serial number for instance).

Should it overwrite existing files?

I'd rather not, we don't do that elsewhere so it seems good to not start now. This matches the the-master-must-be-offline-when-regenerating-its-cert that is assumed above. Don't know how @jpartlow feels about that though?

Do we like this UX, or should this be its own command/a different flag?

The help around the flag assuages my concerns about it only being a flag.

Do we want to call out that we're not going through the CA API in logging?

I don't know? Nothing jumped out at me wrt logging.

I think this close, most of my comments are wrt issues that might arise with multiple certnames passed in, I don't know how valuable that functionality is, but it might be good to have tests around it.

Should it overwrite existing files?

I'd rather not, we don't do that elsewhere so it seems good to not start now. This matches the the-master-must-be-offline-when-regenerating-its-cert that is assumed above. Don't know how jpartlow feels about that though?

So, I'm not sure how we got the current implementation of save_file in the generate action as it goes against the behavior I thought we had elsewhere (probably my own capriciousness). I could see not changing it since it's the existing behavior :shrug:

I think the question is should the puppetserver ca generate ... --ca-client overwrite an existing set of cert/keys?
I'm not sure? What's the behavior of puppetserver ca setup? Probably we should match that?

Yeah I've updated this so that it no longer overwrites certs and keys.

Updated the docs to emphasize that the flag should not be used while the server is running. I'm going to file a ticket for making that mandatory, so we can figure out how to do it right, and maybe figure out a way to error more gracefully in general when the server isn't running.
Manually tested this with single and multiple certnames, things look good.


postcss-custom-properties warnings when overriding css variables

Bug Report
From Issue #7514
Related to PR #7712
Versions.
Angular CLI: 1.5.0-rc.0
Node: 8.1.2
OS: win32 x64
Angular: 5.0.0-rc.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.5.0-rc.0
@angular-devkit/build-optimizer: 0.0.25
@angular-devkit/core: 0.0.17
@angular-devkit/schematics: 0.0.30
@ngtools/json-schema: 1.1.0
@schematics/angular: 0.0.41
typescript: 2.5.3
webpack: 3.7.1

The log given by the failure.
A lot of warnings are being shown to me since #7712 :
WARNING in ./path/to/component/some-component.component.scss
(Emitted value instead of an instance of Error) postcss-custom-properties: path\to\component\some-component.component.scss: Custom property ignored: not scoped to the top-level :root element (some-css-selector { ... --custom-property: ... })
    at Object.emitWarning (path-to-my-project\node_modules\webpack\lib\NormalModule.js:117:16)
    at path-to-my-project\node_modules\postcss-loader\index.js:131:24
    at Array.forEach (native)
    at path-to-my-project\public\node_modules\postcss-loader\index.js:130:31
    at <anonymous>

Repro steps.
when I set:
:root {
  --custom-property: 200;
}

on styles.scss,
and I override it in a component, some-component.scss
some-css-selector {
  --custom-property: 100;
}

It's working perfectly fine but it's very annoying seeing a warning for each css variable I override.
May that be related to a postcss-custom-properties limitation?

postcss-custom-properties doesn't support variable declarations on CSS selectors other than :root. Only :root is allowed. That's why you get the warning. Mostly this only means that your variable will not be transpiled back for older browsers. So when you want  this to work with older browsers, you have to use :root all the time, so postcss-custom-properties knows what to do with it.

Is there a way to silence this warning or noting to the tool that I don't care about transpiling this feature back to older browsers? Thanks.

I don't know about the angular-cli and how it can be configured with it (you have to check by yourself), but the setting of the postcss-custom-properties package you'll find here:
https://github.com/postcss/postcss-custom-properties#warnings

We need a way to add custom PostCSS config to Angular CLI projects.
This issue is related: Using the Bulma CSS library current causes lots of warnings:
https://github.com/jgthms/bulma/issues/1190

Hi,
In my project, by design, we have a lot of css variables.
How should I get rid of these warnings?
Thank you for your support 👍

Not using Bulma, but running into the same issue since our project doesn't care about older browsers. We really don't want to eject the webpack configuration at this point, so can we can an extra configuration setting or expose the postcss configuration to get rid of these warnings?

I think fix explained here https://github.com/MoOx/postcss-cssnext/issues/186 but we need a way to deliver to Angular.

Thank you @zoonman for the update! :)
How to put this part of angular-cli? That  is the question.

@jycouet I believe it has to be a part of .angular-cli.json file, but I don't know how to declare config and pass that declaration inside.
I'm newbie in the modern Angular world (I mean 2.+). I noticed there is an eject.d.ts file inside @angular/cli/tasks which exports postcssArgs. So we need someone like @Brocco, who knows Angular implementation really well.
In my case error look like this:
WARNING in ./node_modules/css-loader?{"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader?{"ident":"postcss"}!./node_modules/stylus-loader?{"sourceMap":false,"paths":[]}!./src/styles.styl
(Emitted value instead of an instance of Error) postcss-custom-properties: /Users/zoonman/Projects/www/liverecord/client/src/styles.styl:115:3: Custom property ignored: not scoped to the top-level :root element (.default :root { ... --body-color: ... })
NonErrorEmittedError: (Emitted value instead of an instance of Error) postcss-custom-properties: /Users/zoonman/Projects/www/liverecord/client/src/styles.styl:115:3: Custom property ignored: not scoped to the top-level :root element (.default :root { ... --body-color: ... })
    at Object.emitWarning (/Users/zoonman/Projects/www/liverecord/client/node_modules/webpack/lib/NormalModule.js:117:16)
    at /Users/zoonman/Projects/www/liverecord/client/node_modules/postcss-loader/index.js:131:24
    at Array.forEach (<anonymous>)
    at /Users/zoonman/Projects/www/liverecord/client/node_modules/postcss-loader/index.js:130:31
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
 @ ./src/styles.styl 4:14-186
 @ multi ./src/styles.styl ./node_modules/font-awesome/css/font-awesome.css

I found that error is coming from postcss but there in no way to change its config.
Looks like this was planned https://github.com/angular/angular-cli/issues/5701 but it I don't know anything more. I can't say more, I'm newbie, I just started with this new version of Angular.

Found a hackable solution.
As there is no "official" way to provide Angular CLI a postcss-custom-properties config - yet.
Open index.js from your projects node_modules\postcss-custom-properties\dist folder
Find this line:
warnings: options.warnings === undefined ? true : options.warnings,
We're going to change warnings property from true to false.
warnings: options.warnings === undefined ? false : options.warnings,
Save and run ng serve

@trimox thx it works, until there will be a fix or a way to pass options to postcss-custom-properties I add hacked  postcss-custom-properties to my project and used it as local package.

If you don't want to eject from ng and you can afford not having postcss-custom-properties postprocessor at all (e.g. because you don't support older browsers anyway), you can remove it completely with a little command like the one below.
I add it to my package.json scripts entry and run as a postinstall script, so it runs always after you do any changes in installed packages. It removes each line where customProperties occurs in the above webpack config. Tested with angular-cli 1.5.
"scripts": {
  "remove-postcss-custom-properties": "sed -i -E '/customProperties/s/^.*$//g'<EMAIL_ADDRESS>}

Hack-ish, I know... but might do as a temp solution, while we decide what do we want to do with these custom properties and backward support.

@ryzy   After put this line on script and run it manually, the warnings does nos desapear. May you explain how to entirely implement it?

Closing as #8289 has a more up to date discussion on the issue.

What is the workaround for adding postcss-custom-properties support now? We needed this and had it working, albeit in a hacky way, for our IE support, and now it is gone with no official alternative besides rolling back to before this pr was merged.


fix init xa panic bug

What this PR does:
Which issue(s) this PR fixes:

Fixes #537
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report

Merging #539 (beb08e7) into master (d6750d5) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #539      +/-   ##
==========================================
- Coverage   36.55%   36.54%   -0.01%
==========================================
  Files         162      162
  Lines       11163    11166       +3
==========================================
  Hits         4081     4081
- Misses       6735     6738       +3
  Partials      347      347

Impacted Files
Coverage Δ

pkg/datasource/sql/xa_resource_manager.go
4.37% <0.00%> (-0.10%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Wallet label display fixes

Fix the following issues regarding wallet label display :

When we set / update a label on a wallet, it does not update directly the label in the page title (we have to go back to the wallet list to see that it was updated).

If we register a contact with the same address as an existing wallet, then the contact name overrides the wallet label or address in the wallet list and detail.

Fixed this already in #115

Thanks for your effort @air1one, but I will close this as @luciorubeens is already looking into @Nasicus's PR (#115)


[REQUEST] Nikolite block

Description:

The ability to craft a nikolite block from nikolite dust, in the same way redstone dust works.

Reason:

Once a player has fortune long mining trips present an inventory space issue, compressing the nikolite into blocks would allow relief for some of that issue.
This is similar to all the raw ore blocks as well.

Duplicate for #133