[!] iTunes Connect error: undefined method `key?' for nil:NilClass (RuntimeError)

New Issue Checklist

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

Issue Description
getting error:
[!] iTunes Connect error: undefined method `key?' for nil:NilClass (RuntimeError)
when using command:
fastlane deliver --skip_binary_upload true --skip_metadata true --submit_for_review false --overwrite_screenshots true
Complete output when running fastlane, including the stack trace and command used

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

fastlane deliver --skip_binary_upload true --skip_metadata true --submit_for_review false --overwrite_screenshots true
Successfully loaded '/Volumes/My Passport/Xcode projects/zviratka-ios/fastlane/Deliverfile' 📄
+---------------------+-------------------------+
| Detected Values from './fastlane/Deliverfile' |
+---------------------+-------------------------+
| app_identifier      | com.circusatos.zviratka |
| username            |<EMAIL_ADDRESS> |
+---------------------+-------------------------+
[19:31:01]: Login to iTunes Connect<EMAIL_ADDRESS>[19:31:05]: Login successful
+-----------------------+-------------------------+
|             deliver 2.14.2 Summary              |
+-----------------------+-------------------------+
| skip_binary_upload    | true                    |
| skip_metadata         | true                    |
| submit_for_review     | false                   |
| overwrite_screenshots | true                    |
| app_identifier        | com.circusatos.zviratka |
| username              |<EMAIL_ADDRESS> |
| screenshots_path      | ./fastlane/screenshots  |
| metadata_path         | ./fastlane/metadata     |
| app_version           | 0.3.0                   |
| edit_live             | false                   |
| ipa                   | zviratka.ipa            |
| platform              | ios                     |
| skip_screenshots      | false                   |
| force                 | false                   |
| automatic_release     | false                   |
| dev_portal_team_id    | PTAQTTL7HU              |
+-----------------------+-------------------------+
[19:31:06]: Making sure the latest version on iTunes Connect matches '0.3.0' from the ipa file...
[19:31:08]: '0.3.0' is the latest version on iTunes Connect
[19:31:10]: Verifying the upload via the HTML file can be disabled by either adding
[19:31:10]: force true to your Deliverfile or using fastlane deliver --force
Does the Preview on path './Preview.html' look okay for you? (y/n)
z
Please enter "yes" or "no".
Does the Preview on path './Preview.html' look okay for you? (y/n)
y
[19:31:18]: HTML file confirmed...
[19:31:19]: Starting with the upload of screenshots...
[19:31:19]: Removing all previously uploaded screenshots...
[19:31:19]: Activating language en-US...
[19:31:23]: Uploading 7 screenshots for language en-US
[19:31:23]: Uploading './fastlane/screenshots/en-US/UnderLeaves10_2880x1800.png'...
Looking for related GitHub issues on fastlane/fastlane...
➡  [!] Undefined method `description' for nil:NilClass (NoMethodError)
https://github.com/fastlane/fastlane/issues/7686 [closed] 9 💬
5 weeks ago
➡  Pilot doesn't set requiring metadata for external testing
https://github.com/fastlane/fastlane/issues/7085 [open] 19 💬
3 days ago
➡  pilot upload failure undefined method `builds' for nil:NilClass
https://github.com/fastlane/fastlane/issues/6267 [closed] 9 💬
6 weeks ago
and 12 more at: https://github.com/fastlane/fastlane/search?q=iTunes Connect error: undefined method `key?'%20for%20nil&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
/Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/spaceship/lib/spaceship/tunes/app_version.rb:590:in rescue in container_data_for_language_and_device': [!] iTunes Connect error: undefined method key?' for nil:NilClass (RuntimeError)
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/spaceship/lib/spaceship/tunes/app_version.rb:579:in container_data_for_language_and_device' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/spaceship/lib/spaceship/tunes/app_version.rb:571:in screenshots_data_for_language_and_device'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/spaceship/lib/spaceship/tunes/app_version.rb:393:in upload_screenshot!' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/upload_screenshots.rb:55:in block (2 levels) in upload'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/upload_screenshots.rb:42:in each' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/upload_screenshots.rb:42:in block in upload'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/upload_screenshots.rb:40:in each' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/upload_screenshots.rb:40:in upload'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/runner.rb:63:in upload_metadata' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/runner.rb:21:in run'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/commands_generator.rb:62:in block (2 levels) in run' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:178:in call'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:178:in call' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:153:in run'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-4.4.3/lib/commander/runner.rb:446:in run_active_command' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in run!'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-4.4.3/lib/commander/delegates.rb:15:in run!' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/commands_generator.rb:148:in run'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/deliver/lib/deliver/commands_generator.rb:12:in start' 	from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/fastlane/lib/fastlane/cli_tools_distributor.rb:45:in take_off'
from /Users/abuki/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.14.2/bin/fastlane:15:in <top (required)>' 	from /Users/abuki/.fastlane/bin/bundle/bin/fastlane:22:in load'
from /Users/abuki/.fastlane/bin/bundle/bin/fastlane:22:in `'
logout
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.2.4

Bundler?
false

Git
git version 2.9.3 (Apple Git-75)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Is homebrew
false

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

Xcode Version
8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

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

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

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

default_platform :ios

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

  end

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

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

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

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

  # You can define as many lanes as you want

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

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

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

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

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

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

team_id "PTAQTTL7HU"  # Developer Portal Team ID

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.14.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

activesupport
<IP_ADDRESS>

addressable
2.5.0

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.14.3

claide
1.0.1

colored
1.2

commander
4.4.3

domain_name
0.5.20161129

dotenv
2.2.0

excon
0.54.0

faraday
0.11.0

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.0.1

gh_inspector
1.0.3

google-api-client
0.9.26

googleauth
0.5.1

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

i18n
0.7.0

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
2.9.0

little-plugger
1.1.4

logging
2.1.0

memoist
0.15.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.4.3

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.3

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.5

rake
10.4.2

rdoc
4.2.0

representable
2.3.0

retriable
2.1.0

rouge
1.11.1

rubygems-update
2.5.2

rubyzip
1.2.0

security
0.1.3

signet
0.7.3

slack-notifier
1.5.1

sqlite3
1.3.13

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

thread_safe
0.3.5

tzinfo
1.2.2

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.3

word_wrap
1.0.0

xcodeproj
1.4.2

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

generated on: 2017-02-12

uploading screenshot should not be related to code signing

My fault. I was trying to upload a screenshot with 2880x1800px, which is for mac, not for iOS.
Anyway, it would be better to have there a warning: "You are uploading a wrong resolution". Or maybe do not upload the images with no matching dimensions.

Agreed, the error message is not clear, fix incoming 👍

I just pushed https://github.com/fastlane/fastlane/pull/8205 which will be available with the next release 👍


Standard_name check

Description
Make sure that standard_name for our output is on the official list.

Just a word of warning but there are a lot of indices that don't have a CF-compliant standard_name. For the full list see: http://cfconventions.org/Data/cf-standard-names/60/build/cf-standard-name-table.html
In the past I've opted for "CF-ish" variable names where an equivalent didn't exist. Not the end of the world.

Correct, this is going to be a problem. Closing.


Move weight computation from propose to traced_evaluate

Closing and reopening because git email does not match email associated with my CLA.


fix(model-server): useRoleIds is a boolean parameter

:tada: This PR is included in version 7.1.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Minor: Add documentation for cot

Which issue does this PR close?
Part of #12740
Rationale for this change
I noticed that the cot function does not have documentation by running the script in https://github.com/apache/datafusion/issues/12872
(venv) andrewlamb@Andrews-MacBook-Pro-2:~/Software/datafusion$ ./dev/update_function_docs.sh
...
Running CLI and inserting scalar function docs table
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.25s
     Running `target/debug/print_functions_docs scalar`
INFO: The following functions do not have documentation:
  - map_extract
  - map
  - cot
  - map_keys
  - map_values

Note that @ jonathanc-n  is working on the map functions in https://github.com/apache/datafusion/pull/13047
In fact it appears to be completely undocumented in the old docs too: https://datafusion.apache.org/user-guide/sql/scalar_functions.html so this is a win for the automated script
What changes are included in this PR?
Add docs to cot
Are these changes tested?
Yes by CI
Are there any user-facing changes?
More docs!

I reran the doc generator locally to make sure there are no logical conflicts and things looked good


Disjoint Unions Refinements don't work

So I was looking at the Disjoint unions in the docs and it gives this example:
// @flow
type Success = { success: true, value: boolean };
type Failed  = { success: false, error: string };

type Response = Success | Failed;

function handleResponse(response: Response) {
  if (response.success) {
    var value: boolean = response.value; // Works!
  } else {
    var error: string = response.error; // Works!
  }
}

so I extended it to do this:
// @flow
type Success = { success: true, value: boolean };
type Failed  = { success: false, error: string };

type Response = Success | Failed;

function handleResponse(response: Response) {
  if (response.success) {
    // var value: boolean = response.value; // Works!
    var successResponse:Success = response;
  } else {
    // var error: string = response.error; // Works!
    var failedResponse:Failed = response;
  }
}

And no errors, so, so far so good. But then I applied my own code to my own example, which is quite similar:
type singlePerson = {
  married: false,
  dreamSpouse: string,
}
type marriedPerson = {
  married: true,
  spouse: string,
}

type person = singlePerson | marriedPerson;
function parsePerson(guy: person) {
  if(guy.married){
    var spouse: string = guy.spouse;
    var marriedDude:marriedPerson = guy;
  } else {
    var dreamSpouse:string = guy.dreamSpouse;
    var marriedDude:singlePerson = guy;
  }
}

parsePerson({married: true, spouse: "Jess Crowe"});

And low and behold, errors like:
3:   married: false,
              ^ boolean literal `false`. Expected boolean literal `true`, got `false` instead
7:   married: true,
              ^ boolean literal `true`
7:   married: true,
              ^ boolean literal `true`. Expected boolean literal `false`, got `true` instead
3:   married: false,
              ^ boolean literal `false`
15:     var marriedDude:marriedPerson = guy;
                        ^ property `spouse`. Property not found in
18:     var marriedDude:singlePerson = guy;
                        ^ object type
15:     var marriedDude:marriedPerson = guy;
                        ^ property `spouse`. Property not found in
18:     var marriedDude:singlePerson = guy;
                                       ^ object type
18:     var marriedDude:singlePerson = guy;
                        ^ property `dreamSpouse`. Property not found in
15:     var marriedDude:marriedPerson = guy;
                        ^ object type

I don't understand why am I getting these errors for this? Feel free to try this yourself at:
https://flow.org/try/#0FAFwngDgpgBAzgSwHYHMA2UAKUBOcD2SMAvDAN7AwwC2AhjjglACYBcMAZrWnFADSUYzHFFrUAyhHwBXXuzghGqAQF9QkWHQZNm2PIRLlBWxi3aLp-QXCmyo8xchSrg66DGj6ipRKgx6CIgAfGnpTXVxAgG5gDmkkAGMQBAMIel4AwgAKFGkwdk9AgEojKgQOHLyAOhMdIooqKgA3enhbOXhHVENcsCqbGV4YxpgWnFDtFgARaWZ7WpZM7xhe4ZgVGCgeWAbGsaERMUlB+wUlFB7q4VEJdqg15taF5hm51l90LEiDUlXBNTUwDSeC+XiyZGe5hwlj4bRO7AARAApKBwOAwADCOHwAHcoAiVEUYq5wO5xNIEglUejSGR4BSqWioTDRtxLOwAEb4fAYWhEFQxUmwABitAQGGYVFp9Mp1PYXG2sNw2JwDnO62JQpgACVUVIkLxDOTZWiYCFReKWMS4olkgYABZ85gYXUDA1QLIiN0dV363glXblGCevWEXj9BnUgOCKgAeljrPGLTQ7JgXJ5omWXr9UCqycsURg8ZgAHV8DgANZwACEMcTMsZcF9YfsxsbhmzLbWGy2ht2cYT+2V5bVTg7ofdVWHOELxbLlZrdf2XEtzGb7tYFol4+993+wEBQA

@Mohamed-Abo-El-Soud var is function-scoped, you cannot declare marriedDude once as marriedPerson and then as singlePerson. use const or let instead. see this post for more details

I think I figured out the problem.
I used the same variable marriedDude:marriedPerson and marriedDude:singlePerson in both cases of the control flow.


Linter issue

Just moving the import after the docstring, the linter was complaining.

Thanks! Merged to testing branch and then to stable so closing w/o merge.


The MOTP metrics is showing a low score.

Hi, I am using this reference code to do simultaneous detection and tracking on small objects.  The average precision and average recall of the detection model shows a good perfromance but when it comes to tracking the MOTP score is very low? Any suggestions on how I can improve the performance ? Also, the MOTA and other metrics are high, so I can't figure out where the prblem actually lies ? @timmeinhardt
IoU metric: bbox
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.660
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.946
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.808
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.660
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = -1.000
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = -1.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.692
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.705
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.705
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.705
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = -1.000
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = -1.000

INFO - root - mergeOverall: 0.022 seconds.
IDF1    IDP   IDR  Rcll   Prcn GT MT PT ML FP FN IDs  FM  MOTA  MOTP IDt IDa IDm
Train_Moffat 99.0% 100.0% 98.0% 98.0% 100.0%  1  1  0  0  0 10   0   0 98.0% 0.086   0   0   0
OVERALL      99.0% 100.0% 98.0% 98.0% 100.0%  1  1  0  0  0 10   0   0 98.0% 0.086   0   0   0

Currently, I am only using a single object per image but I will change it to multiple objects when I get improvement on a single object tracking.

Have you tried optimizing the tracking thresholds, for example, detection_obj_score_thresh and track_obj_score_thresh. Or visualizing the output? This should give you a good idea of what is wrong.

I will do that and check if there is any improvement. Is there any other way to find the optimal tracking thresholds besides manually changing it with presumption?

You could write a script to find the optimal hyperparameters. But there is no analytic way to find them. At first, I would visualize your outputs to understand whats happening. This could give you an idea what parameters and how to change them.

Hi, I tried to use Visdom to visualize the training and evaluation metrics as suggested in the documents, but the Visdom server is showing a blank blue screen.

I started the Visdom server at port 8097 by running "visdom" in the terminal. I then changed the port number in the config file as well.

To verify the code is connected to the Visdom server, the "Webscoket connected" information is available.

But when I look at the logs at logs/visdom, the folder is empty.

I tried to visualize the bounding box location during validation, and the prediction worked quite well. But for the test data, the prediction is random.
During the training phase, I only used validation data for tracking and didn't use any test data. The validation data itself is in a sequential format. I wanted the test data to be unseen during training.

The -1.23 values are obtained for the test data.

for the validation data, the predictions are quite good.
@timmeinhardt any idea what's causing these issues ?

I managed to load results from visdom. BUt I still can't figure out why the tracking woks on validation data but not the test data.
@timmeinhardt


Implement a proper Debug for Map / TileLayer

So we don't get bombarded with this when testing:

Right, I guess a LayerTileData could debug print to something like 123:vhd, for a tile with gid 123 that is flipped on all axis. Or did you have something else in mind?

Whatever it is, it should be less than 1000 characters long. :p

Maybe default debug formatting = Only show width/height, alternate = Show all tiles

Hello @aleokdev and @bjorn. Can I take this on?

Of course, feel free to! You can open a PR against current since this shouldn't be considered a breaking change.


[docs] Fix missing import in auto-dark theme palette example

While going through the example on how to configure dark theme automatically for the MUI theme, I found a slight issue in the provided example.  A required import for createMuiTheme was excluded.  This PR quickly fixes this issue by adding the import.

[X] I have followed (at least) the PR section of the contributing guide.

Thanks


PageKit > Cross-site scripting (DOM-based)

Problem
We have run BurpSuit(Security Scan tool) on our PageKit project and it was providing high-risk bugs in codemirror.js which is internally used in editor.js in Pagekit.
Report Details

Cross-site scripting (DOM-based)
/admin/site/page/edit
Issue detail:

The application may be vulnerable to DOM-based cross-site scripting. Data is read from textarea.value and passed to jQuery.html.

Issue background

DOM-based vulnerabilities arise when a client-side script reads data from a controllable part of the DOM (for example, the URL) and processes this data in an unsafe way.
DOM-based cross-site scripting arises when a script  writes controllable data into the HTML document in an unsafe way. An attacker may be able to use the vulnerability to construct a URL that, if visited by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to visit the attacker's crafted URL in various ways, similar to the usual attack delivery vectors for reflected cross-site scripting vulnerabilities.
Burp Suite automatically identifies this issue using static code analysis, which may lead to false positives that are not actually exploitable. The relevant code and execution paths should be reviewed to determine whether this vulnerability is indeed present, or whether mitigations are in place that would prevent exploitation.

Issue remediation

The most effective way to avoid DOM-based cross-site scripting vulnerabilities is not to dynamically write data from any untrusted source into the HTML document. If the desired functionality of the application means that this behavior is unavoidable, then defenses must be implemented within the client-side code to prevent malicious data from introducing script code into the document. In many cases, the relevant data can be validated on a whitelist basis, to allow only content that is known to be safe. In other cases, it will be necessary to sanitize or encode the data. This can be a complex task, and depending on the context that the data is to be inserted may need to involve a combination of JavaScript escaping, HTML encoding, and URL encoding, in the appropriate sequence.

References

Cross-site scripting
DOM-based cross-site scripting

Vulnerability classifications

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
CWE-116: Improper Encoding or Escaping of Output
CWE-159: Failure to Sanitize Special Element

Request:
GET /admin/site/page/edit?id=page&menu=administrator HTTP/1.1
Host: pagekit.com
Cookie: pagekit_session=in8ah866le3ra2krdp04ttvtd9; pagekit_auth=BBheftEBY9AqeDiqdBmcdBGdVBR8XiQ8.LjejPpWLZo%2FeZyydLRM%2FFfPX84MBq6v; current_role=MQ%3D%3D; remember_ses=in8ah866le3ra2krdp04ttvtd9
Upgrade-Insecure-Requests: 1
Referer: https://pagekit.com/admin/site/page
Accept: */*
Accept-Language: en-US,en-GB;q=0.9,en;q=0.8
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
Connection: close
Cache-Control: max-age=0
Accept-Encoding: gzip, deflate

Response:
HTTP/1.1 200 OK
Date: Thu, 04 Feb 2021 15:46:55 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 19195
Connection: close
Server: Apache
Vary: X-Forwarded-Proto,Accept-Encoding
Set-Cookie: remember_ses=in8ah866le3ra2krdp04ttvtd9; expires=Sat, 06-Feb-2021 15:46:55 GMT; Max-Age=172800; path=/; secure; HttpOnly
Cache-Control: private, max-age=0, no-store, max-age=0
Set-Cookie: current_role=MQ%3D%3D; expires=Fri, 04-Feb-2022 15:46:55 GMT; Max-Age=31536000; path=/; secure; HttpOnly
Set-Cookie: remember_ses=in8ah866le3ra2krdp04ttvtd9; expires=Sat, 06-Feb-2021 15:46:55 GMT; Max-Age=172800; path=/; secure; HttpOnly
Cache-Control: no-cache
Expires: Thu, 04 Feb 2021 15:46:55 GMT
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, iSnip
Dynamic analysis:

Data is read from textarea.value and passed to jQuery.html.

The following value was injected into the source:
m6437stmf5%2527%2522`'"/m6437stmf5/><m6437stmf5/\>orxqqixu24&

The previous value reached the sink:
uhmx5hf1ek%2527%2522`'"/uhmx5hf1ek/><uhmx5hf1ek/\>dynvems276&

The stack trace at source was:
at HTMLTextAreaElement.get [as value] (<anonymous>:1:765266)
at Function.v.fromTextArea (https://pagekit.com/app/assets/codemirror/codemirror.js:43:1640)
at o.init (https://pagekit.com/app/assets/uikit/js/components/htmleditor.min.js:2:1472)
at new o (https://pagekit.com/app/assets/uikit/js/uikit.min.js?v=19e2:2:6776)
at Object.<computed> [as htmleditor] (https://pagekit.com/app/assets/uikit/js/uikit.min.js?v=19e2:2:8068)
at VueComponent.<anonymous> (https://pagekit.com/app/system/modules/editor/app/bundle/editor.js?v=19e2:170:55)

The stack trace at the sink was:
at Object.apply (<anonymous>:1:940882)
at o.render (https://pagekit.com/app/assets/uikit/js/components/htmleditor.min.js:2:6362)
at o.disableMarkdown (https://pagekit.com/app/assets/uikit/js/components/htmleditor.min.js:2:13245)
at HTMLTextAreaElement.disableMarkdown (https://pagekit.com/app/assets/uikit/js/components/htmleditor.min.js:2:13338)
at HTMLTextAreaElement.dispatch (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:3:6466)
at HTMLTextAreaElement.r.handle (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:3:3241)
at Object.trigger (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:3:5574)
at HTMLTextAreaElement.<anonymous> (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:3:11542)
at Function.each (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:2:2882)
at Object.each (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:2:847)
at Object.trigger (https://pagekit.com/app/assets/jquery/dist/jquery.min.js?v=19e2:3:11518)
at o.trigger (https://pagekit.com/app/assets/uikit/js/uikit.min.js?v=19e2:2:7321)
at VueComponent.$watch.immediate (https://pagekit.com/app/system/modules/editor/app/bundle/editor.js?v=19e2:195:25)
at VueComponent.t.$watch (https://pagekit.com/app/assets/vue/dist/vue.min.js?v=19e2:7:2786)
at VueComponent.<anonymous> (https://pagekit.com/app/system/modules/editor/app/bundle/editor.js?v=19e2:194:19)

This was triggered by a load event.

Is there any way to fix this issue? Thanks in advance!!
Technical Details

Pagekit version: 1.0.13
Webserver: Apache
Database: 5.6.10
PHP Version: 7.3.19

And no one even replied to this? Amazing.

Pagekit is (almost) dead. I suggest to head over to biskuit cms (Pagekit fork)

DOM-based cross-site scripting arises when a script writes controllable data into the HTML document in an unsafe way. An attacker may be able to use the vulnerability to construct a URL that, if visited by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

I don't see how this is possible. The field is filled with either content comming from the database or with content coming from the page user currently visiting the page. Nothing is used from the URL.
Additionally, dupe of #815

DOM-based cross-site scripting arises when a script writes controllable data into the HTML document in an unsafe way. An attacker may be able to use the vulnerability to construct a URL that, if visited by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

I don't see how this is possible. The field is filled with either content comming from the database or with content coming from the page user currently visiting the page. Nothing is used from the URL.
Additionally, dupe of #815

Well, it is literally explained in the OP how it works. If a logged in user  navigates to a purposely crafted url their session might get stollen. For example by clicking the link in the comments. This is not something new.

Well, it is literally explained in the OP how it works. If a logged in user navigates to a purposely crafted url their session might get stollen.

There is a generic explanation on how such attacks could work. However, it is not stated that this is always possible. In this specific scenario I don't see a possible attack here. Nothing from the URL is passed to the textarea, the textarea is only filled by the user or from server side. The user has to be logged in and have access to the admin panel (which should be granted to trusted users, only).
However, I am open to be convinced by the opposite by a working example.

For example by clicking the link in the comments.

User entered content in the comments is not using this editor component and additionally is sanitized.

This is not something new.

The attack vector is not something new. But, to be a threat it is also require that it can be exploited. And in this particular scenario, I don't see a possibility to exploit.

Have you inspected an example provided by OP? He managed to  inject a code into into DOM via CrossSite request.
P.S. PageKit development is dead anyway so yeah.

I just see a statement that if a textare on the page is filled with a specific value, then this value is printed to the page. This is correct as this is the design of an HTML editor. However, I don't see steps to reproduce this issue. So, there is nothing I could check. I just see a code analysis of a tool from where I don't get what I have to do to reproduce the issue.


Test framework

Add test framework that allows running a yaml based test configuration.  The yaml allows defining queries and JS based test expression on the results of the queries.
Refactor tools out of the zulia-server project into zulia-tools which now includes the zuliatest tool.
bump common compress to 1.26.1 (from 1.25.0) for security fix
bump flapdoodle mongo to 4.12.2 (from 4.11.1)
bump jansi to 2.4.1 (from 2.4.0)

To run:
zuliatest --testConfig /path/to/sample_testing.yaml --testOutput /path/to/test_output.csv

Looks like we might be able to give a JSON schema to the YAML file for autocomplete.  I need to dig a little.
I was considering the multiple indexes but I was torn.


Town Color Picking

It would be ideal if players could pick their own town colors instead of it being picked for them.

/town color command - choose town color. Some of my players are getting dark/hard to see colors and keep complaining about it.

Added in 2.0


Can't delete training types that are used by trainings with cancellations

Deleting a training type should set the type of every training with that type to null.


Need tests for writing multiple irregular time series

Preliminary code changes were made in cdss-lib-common-java and cdss-lib-processor-ts-java to write multiple irregular time series to files and need tests.

Now is not a good time to finalize the code so attached are files need to be added to the repo when there is time.  Also, the following was deleted test/regression/commands/general/WriteDelimitedFile/Test_WriteDelimitedFile_Irregular_2TS.TSTool.
Attach files here for WriteDateValue/ExpectedResults.
Test_WriteDateValue_Irregular15min2Nonaligned_out.dv.txt
Test_WriteDateValue_Irregular15min2Aligned_out.dv.txt
Attach files here for WriteDateValue.
Test_WriteDateValue_Irregular15Min2Nonaligned.TSTool.txt
Test_WriteDateValue_Irregular15Min2Aligned.TSTool.txt
Attach files here for WriteDelimitedFile.
Test_WriteDelimitedFile_Irregular_2TSAligned.TSTool.txt


Add teuthology git version query/logging

Signed-off-by: Dan Mick<EMAIL_ADDRESS>

k.  1) changed to 1.0.0- or 1.0.0 if failure 2) better exception handling and a message if failure

Awesome, thanks!

This broke everything:
https://paste.fedoraproject.org/388672/14679031/

A more readable traceback:
2016-07-07 09:02:11,897.897 INFO:teuthology:teuthology version: 1.0.0-6514f9e
Traceback (most recent call last):
  File "/Users/zack/inkdev/teuthology/virtualenv/bin/teuthology", line 9, in <module>
    load_entry_point('teuthology', 'console_scripts', 'teuthology')()
  File "/Users/zack/inkdev/teuthology/scripts/run.py", line 34, in main
    teuthology.run.main(args)
  File "/Users/zack/inkdev/teuthology/teuthology/run.py", line 306, in main
    set_up_logging(verbose, archive)
  File "/Users/zack/inkdev/teuthology/teuthology/run.py", line 30, in set_up_logging
    teuthology.setup_log_file(os.path.join(archive, 'teuthology.log'))
  File "/Users/zack/inkdev/teuthology/teuthology/__init__.py", line 69, in setup_log_file
    root_logger.log.info('teuthology version: %s', __version__)
AttributeError: 'function' object has no attribute 'info'

How the....I ran this code!...  sigh.


Merge to live.

OPS Build status updates of commit 77ef67c:
:clock10: Preparing: average preparing time is 39 sec(s)

OPS Build status updates of commit 77ef67c:
:clock10: Incremental building: average incremental building time is 21 sec(s)

OPS Build status updates of commit 77ef67c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Prerelease-Packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Symbol-Packages-snupkg.md
:white_check_mark:Succeeded
View

docs/reference/errors-and-warnings/NU5030.md
:white_check_mark:Succeeded
View

docs/reference/msbuild-targets.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix the bug about parsing dragonwell version (#642)

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] Mark if documentation changes are required.
[ ] Mark if tests were added or updated to cover the changes.

@IvanZosimov Hello, all tests passed. Please review this pull request. Thank you very much

@IvanZosimov Hello, all tests passed. Please review this pull request. Thank you very much

@IvanZosimov Hello, please review this pull request. Thank you very much!

is there a way to mark this project as abandonware?

is there a way to mark this project as abandonware?

Why is it listed as abandoned software?

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] > - [ ] Mark if documentation changes are required.
[ ] > - [ ] Mark if tests were added or updated to cover the changes.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] > - [ ] Mark if documentation changes are required.
[ ] > - [ ] Mark if tests were added or updated to cover the changes.
a3c03fb3323ce0ee60478afafd05807a25800def

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ]  > - [ ] Mark if documentation changes are required.
[ ]  > - [ ] Mark if tests were added or updated to cover the changes.
a3c03fb

Hello, I think this does not need to be changed according to the original content in the usage document

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] > - [ ] Mark if documentation changes are required.
[ ] > - [ ] Mark if tests were added or updated to cover the changes.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] > - [ ] Mark if documentation changes are required.
[ ] > - [ ] Mark if tests were added or updated to cover the changes.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ]  > - [ ] Mark if documentation changes are required.
[ ]  > - [ ] Mark if tests were added or updated to cover the changes.

Sorry, I have added the test case and updated test data. The original test case is indeed a bit insufficient.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ]  ] Mark if documentation changes are required.
[ ]  > - [ ] Mark if tests were added or updated to cover the changes.

Sorry, I have added the test case and updated test data. The original test case is indeed a bit insufficient. Please review, thank you very much!

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ x] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[ ] > - [ ] Mark if documentation changes are required.

[x] Mark if tests were added or updated to cover the changes.

Description:
Fix the bug about parsing dragonwell version
Related issue:
#642
Check list:

[x] Mark if documentation changes are required.

[x] Mark if tests were added or updated to cover the changes.

2f3fa4737e9caf495a52363adc5c4321077c508d


[Feature / CSS tweak] Make the comment collapse button easier to tap/click

Is your feature request related to a problem? Please describe.
Yes. My problem is that the touch target for collapsing comments is hard to hit.
I still hit the username often.
Describe the solution you'd like
Just adjust the CSS slightly so that the comment collapse button is wider/bigger.
Also increase the margin between the collapse button and username.
Describe alternatives you've considered
x
Additional context
x

Is Expando the term I'm supposed to call the collapse buttons?

Duplicate of #110
I hope I will fix it soon enough, but I dont really have much free time


Add support for several elasticsearch auth options, TLS and more options

Pull request
Description
New options for elastic connector:

headers
timeout
auth
tls

Related
Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance

it is not working yet anyways. For some reason on CI the elasticsearch docker image is not coming up properly with http ssl settings :( Still investigating with some heavy printf debugging


Implement Output struct which be used to serialize to an output file

remember to add tests for serializing to make sure each field will be successfully serialized into string.

@genedna claim

closed by: #22


Register in curated list of awesome lists

I've created a pull request to awesome list: https://github.com/sindresorhus/awesome/pull/706
Before it can be merged, following changes to the README.md are required:

add a description of what service workers are,
linkify service worker to a good resource about it,
change # Table of Contents to ## Contents.

https://github.com/sindresorhus/awesome/pull/706#issuecomment-231085519

Superstar 🎆 !


Use StringIO instead of string concatenation.

This may bring a huge performance benefit while loading a large .ics file for platforms where the creation of a new string object is costly. Inside Termux installation a read_lines function call dropped from 10 seconds to approx. 125 ms while parsing a 680 kB ics file.

Thank you, that looks awesome!


Format code

@kant2002 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Any news on this?

Sorry for the delayed response. Thank you for your contribution.


Update deprecation warning filter in QiskitTestCase

Summary
No longer filter Aer warnings that have been fixed in Aer's 0.13. release.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 87.556%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
59470

Relevant Lines:
67922

💛  - Coveralls

Test failures look to be related to the on-going GitHub service incident.


Team3-Sprint2-v1

(Note: we worked on this together on the same computer today/tonight)
Frontend:

Added page: EditApplication.tsx
Added updateApplication, deleteApplication, and fetchApplication to the auth file.
Backend:
Added post route to update a TA Application in taApplication.routes
Added delete route to delete a TA Application in taApplication.routes

Fixed issues with http://localhost:3000/view-applications route rendering and other minor issues

Please move the function you add to auth.ts to other file under service. auth.ts should only contain authentication related function.

Should be moved to apply.ts in the second commit


Add default value for REF of premerge jenkinsfile to avoid bad overwritten [skip ci]

fix #10964
Currently, premerge should only be triggered from a Pull request, but there could be some unexpected manual trigger from the internal pipeline directly. And people could forget to put the required REF for the pipeline to fetch the corresponding jenkinsfile, this could cause the default param got overwritten by an old jenkinsfile (currently the oldest tag in repo which has no REF param), the pipeline lose the REF param for upstream router to pass the jenkinsfile commit and then fail all following runs.
Solution:
Add a default value as main for the REF, to make sure that even unexpected manual ops would not remove the REF param for the pipeline itself.
this will be applied to JNI and ML repos later

build

Verified working. change to [skip ci] to save resource

build

build


Can I replace PointGroup's backbone with PTv2 instead of SpUnet?

Can I replace PointGroup's backbone with PTv2 instead of SpUnet?

Yes, of course. But I have not test it and it would be helpful if you can share your config.

I was because our framework adopts eval_epoch as the actual epoch num. If eval_epoch is 100 and epoch is 3000, then the dataset will loop 30 times. The error seems to be because of another reason.

Aha, recently I updated S3DIS preprocessing which can produce additional normal vectors for the dataset. You can re-preprocess S3DIS or directly download the processed one shared by us. Further please refer here. (Also, you can modify the config, and do not apply normal as a part of feat.)

Pointcept is in a phase of rapid evolution, please feel free to ask me any questions encountered.

Hi, I haven't written a test process for instance segmentation, and the test dataset config is None currently,  https://github.com/Pointcept/Pointcept/blob/main/configs/s3dis/insseg-pointgroup-v1m1-0-spunet-base.py#L120. You can directly use the evaluated result during training, and it is precise.

You can modify code here (pointcept.engine.hook.evaluator.InsSegEvaluator).

Hi, I mainly refer to the CSC code: https://github.com/facebookresearch/ContrastiveSceneContexts/blob/83515bef4754b3d90fc3b3a437fa939e0e861af8/downstream/insseg/lib/test.py#L113. The performance looked good and I didn't make a comparison of the two settings.

I tried the setting on normal ScanNet20 and S3DIS benchmarks and the performance was pretty good. I will run again and check the performance, please wait for my response. And could you share your custom config with me?

I checked the data and config you sent to me, I think it was because of data imbalance and difficulty imbalance. 1. You can first try to ignore branch class instance and check the performance of boll class; 2. Then, try to set different loss weights for the two classes.

Try this, change boll index to 1, and change branch index to 1, then ignore segment index 0. If it works, it means some hard code that ignores segment 0 exists in the evaluation code (The evaluation code is modified from ScanNet official, some hard code exists).

Yes, and I am not familiar with PointGroup, some hyperparameters,s and fitting mechanism might also lead to the result.


Split long lines in domain.txt

I have some sub-domains aliases preceded with an uuid and I'd like to split and indent them.
draft.example.com \
  1bd70e60-2c43-416b-aaff-c2429ea5a0d0.draft.example.com \
  1eab8b9b-5b6e-4dd9-988d-18e7af1b31e8.draft.example.com \
  2f1b79e7-8d85-4c74-a481-9775350c7c35.draft.example.com \
  40a8d208-188d-45b7-b4e8-763d42cedea3.draft.example.com \
  464497eb-de18-44e9-9783-5e53f2d7d679.draft.example.com \
  # comments and empty lines possible

  60ff37f4-4d9a-46f1-86c6-f38cd6bcd639.draft.example.com \
  62e14bbe-a924-4118-bcf6-13f5154ad38f.draft.example.com \
  6530cefa-c08c-4130-b372-567d5276c6ae.draft.example.com \
  67fe21dc-7177-4d2e-b2d7-374adbff6d50.draft.example.com \
  748597fe-2354-4976-8397-5047f91c9570.draft.example.com \
  887b453d-c628-4ed7-a916-542317879361.draft.example.com \
  a062f957-993d-48b4-838b-9c46ea0739e2.draft.example.com \
  a4f06559-3170-44fc-ad83-efb331d28a07.draft.example.com \
  ab4a037a-129e-49f4-87f2-06c70cecdaf5.draft.example.com \
  bb157bb9-c2a0-43dd-ba98-d8597d05e3d8.draft.example.com \
  e238f54c-9ade-41c2-b86a-38ab3bc6782d.draft.example.com \
  e2f9545f-6e5b-466a-bcd7-de1fa2388570.draft.example.com \
  f69d425a-82cc-421a-86a1-4bfbe6ce0c05.draft.example.com \
  f7e539ad-e384-430e-915e-b605e3d68a5d.draft.example.com \
  fde9056f-d280-45ca-938a-1f29cdc3e711.draft.example.com

I think if i'd be going to implement this it should follow some known behaviour like e.g. bash handles it. Empty lines would basically be the end of the previous block. But tbh I don't really want to over-complicate parsing of that file... it's ugly enough as is and I think for a use case like yours an external script to call dehydrated would be way better suited for the job, so I'm closing this ticket.


toolchain: arcmwdt: linker: fix placeholders for arcmwdt toolchain

syntax ". += length;" not work with arcmwdt toolchain, let's using
". = . + length;", which both work with gnu and arcmwdt toolchain.
Signed-off-by: Watson Zeng<EMAIL_ADDRESS>Fix: #35479

Ideally, this patch should be accompanied by an automated check that prevents use of symbol f= expression, where f is any supported operator, in the linker scripts.

@stephanosio Is there any similar design that I can take a reference?  And I think your ideal should be an enhancement, maybe we can add it in v2.7.0.

Is there any similar design that I can take a reference? And I think your ideal should be an enhancement, maybe we can add it in v2.7.0.

@IRISZZW Possibly, we can update checkpatch.pl to do just that in the future; or alternatively, make arcmwdt generate errors when an unsupported statement is encountered; or, even better, make arcmwdt support +=.


Bugfix: #1903

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[x] Entries added to ./unreleased/ for any new functionality

closes #1903

Codecov Report

Merging #1906 (0c0faa6) into unstable (4bba030) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           unstable    #1906      +/-   ##
============================================
- Coverage     76.96%   76.95%   -0.01%
============================================
  Files           405      405
  Lines         12531    12532       +1
  Branches        556      556
============================================
  Hits           9644     9644
- Misses         2887     2888       +1

Impacted Files
Coverage Δ

...transformations/standard/IncrementalRenaming.scala
87.59% <100.00%> (+0.09%)
:arrow_up:

...he/io/annotations/parser/CommentPreprocessor.scala
96.70% <0.00%> (-1.10%)
:arrow_down:

Continue to review full report at Codecov.

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


Files Information In File Explorer

Files Information (properties) In File Explorer
If File Explorer shows some basic information about the current file then that would be nice
like file size.

Also can be done via extension.

Yah, i totally understand. thank you.


Fix link

It was redirecting to https://github.com/PolymerLabs/lit-element-starter-js/blob/master/11ty.dev

I would appreciate if someone can merge this. Danke ❤

Thanks for the comment and contribution. Really sorry about this! The repo is not monitored very closely as the source of truth for the starter kits are in the Lit monorepo: https://github.com/lit/lit/tree/main/packages/lit-starter-js
This repo acts as a "release" branch for the starter kit so your change would get overwritten if we merge it in here without merging it into the Lit monorepo.
If you make the change against the Lit monorepo and assign me as a reviewer I can review.
Also filed https://github.com/lit/lit-element-starter-js/issues/27 to improve contributor communiation for the starter kits.
Thank you.


Make maintainers explicit with CODEOWNERS

Hello!
We're making maintainers explicit. I've guessed the maintainers here, let me know if this is not right. Thanks!

I think the CODEOWNERS structure should look something like this (not sure if @VZout wants to be included as an examples/ owner or not, and you could probably put @khyperia as one of the owners on every one of these categories if she wants :P)
* @khyperia

crates/* @khyperia @eddyb

examples/* @khyperia @termhn @VZout(?)

docs/* @XAMPPRocky
*.md @XAMPPRocky

Wonderful, thank you so much @termhn ! I've updated this PR with your suggestion.

Linking https://github.com/EmbarkStudios/rust-gpu/issues/161 because this will close that issue

@khyperia Erin is off for a month so we won’t be able to get a review from her. Is there anything else to do here or can we merge?

rrright, yes, sorry, completely forgot about that!

Thank you everyone!! 💜


scheduler in rdm training

I noticed that when training RDM, we need to set args.cosine_lr=True to initialize the scheduler in engine_rdm.py. However, the instructions given in the readme defaults to args.cosine_lr=False. I am new in deep learning. I wonder is it correct to keep the learning rate of adamw as a constant during training? Why can it still converge? Looking forward to your reply!

You don't need to set args.cosine_lr=True. A constant learning rate should be ok and can still converge -- the convergence of a model does not mean that the learning rate is 0, but instead, the loss stops decreasing.


HBASE-25088 CatalogFamilyFormat/MetaTableAccessor.parseRegionInfoFrom…

…

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 34s
the patch passed

+1 :green_heart:
compile
0m 31s
the patch passed

+1 :green_heart:
javac
0m 31s
the patch passed

+1 :green_heart:
shadedjars
7m 17s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 24s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 18s
hbase-client in the patch passed.

29m 20s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f5677c303389 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / dca0b593cf

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/1/testReport/

Max. process+thread count
200 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 50s
Docker mode activated.

@Joseph295 Can you please add a test for this one as Duo mentioned that it is used at some critical places?

@Joseph295 Can you please add a test for this one as Duo mentioned that it is used at some critical places?

done, thanks for your reminder

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 21s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 54s
master passed

+1 :green_heart:
compile
0m 32s
master passed

+1 :green_heart:
shadedjars
8m 11s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 29s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 36s
the patch passed

+1 :green_heart:
compile
0m 35s
the patch passed

+1 :green_heart:
javac
0m 35s
the patch passed

+1 :green_heart:
shadedjars
8m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 30s
hbase-client in the patch passed.

31m 36s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 55d6d716de17 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 687e53b7e4

Default Java
1.8.0_232

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/testReport/

Max. process+thread count
230 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 48s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m 37s
master passed

+1 :green_heart:
compile
0m 46s
master passed

+1 :green_heart:
shadedjars
10m 34s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 38s
hbase-client in master failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 19s
the patch passed

+1 :green_heart:
compile
0m 39s
the patch passed

+1 :green_heart:
javac
0m 39s
the patch passed

+1 :green_heart:
shadedjars
11m 18s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 35s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 38s
hbase-client in the patch passed.

41m 10s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux eff3f357357f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 687e53b7e4

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/testReport/

Max. process+thread count
285 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  4s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  5s
the patch passed

+1 :green_heart:
compile
0m 29s
the patch passed

+1 :green_heart:
javac
0m 29s
the patch passed

+1 :green_heart:
shadedjars
6m 56s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 30s
hbase-client in the patch failed.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 22s
master passed

+1 :green_heart:
checkstyle
0m 41s
master passed

+1 :green_heart:
spotbugs
1m 34s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 17s
the patch passed

-0 :warning:
checkstyle
0m 37s
hbase-client: The patch generated 1 new + 1 unchanged - 0 fixed = 2 total (was 1)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m 44s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m  2s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 18s
The patch does not generate ASF License warnings.

46m 40s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 6c389170ddc5 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 687e53b7e4

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

And please fix the checkstyle issue?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m  0s
the patch passed

+1 :green_heart:
compile
0m 41s
the patch passed

+1 :green_heart:
javac
0m 41s
the patch passed

+1 :green_heart:
shadedjars
9m 51s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 34s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 35s
hbase-client in the patch passed.

36m 51s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1a7132b6ccd8 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4e59014bed

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/testReport/

Max. process+thread count
271 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 45s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
8m 44s
master passed

+1 :green_heart:
compile
1m  0s
master passed

+1 :green_heart:
shadedjars
11m 43s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  5s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
12m 11s
the patch passed

+1 :green_heart:
compile
0m 53s
the patch passed

+1 :green_heart:
javac
0m 53s
the patch passed

+1 :green_heart:
shadedjars
12m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 23s
hbase-client in the patch passed.

55m 22s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2448

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2402ea459f20 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4e59014bed

Default Java
1.8.0_232

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/testReport/

Max. process+thread count
220 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2448/5/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


VeeHD Extractor Broken

pi@raspberrypi ~ $ youtube-dl http://veehd.com/video/4665804_Tell-No-One-Ne-le-dis-a-personne-2006-French-EngSoftSubs-Re-Up --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://veehd.com/video/4665804_Tell-No-One-Ne-le-dis-a-personne-2006-French-EngSoftSubs-Re-Up', '--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.3 - Linux-3.12.35+-armv6l-with-debian-7.6
[debug] exe versions: avconv 9.14-6, avprobe 9.14-6, ffmpeg 0.8.13-6, rtmpdump 2.4
[debug] Proxy map: {}
[VeeHD] 4665804: Requesting webpage
[VeeHD] 4665804: Downloading webpage
[VeeHD] 4665804: Requesting player page
[VeeHD] 4665804: Downloading player page
ERROR: Unable to extract iframe url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 633, in extract_info
ie_result = ie.extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 270, in extract
return self._real_extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/veehd.py", line 59, in _real_extract
r'<iframe[^>]+src="/?([^"]+)"', player_page, 'iframe url')
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 532, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract iframe url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
pi@raspberrypi ~ $ youtube-dl --version
2<IP_ADDRESS>

Hi, this seems to use a different Veehd player, which is not yet supported by youtube-dl and I would like to add a test case for it, however, I can't do that, because the video on your provided URL contains copyrighted material. Could you provide another URL (with freely available content) where the same error happens?

VeeHD extractor is fixed so that avi/divx videos can be downloaded in the next version.
@naglis Sorry I accidently commited the video with copyright issues into test cases but I've already replaced it with a publicly availble tralier in 482a1258de6af0a15b6e7859d244f9125cadef47


TypeError with convolutional layer: init() takes at least 3 arguments

Hello, guys!
Everything worked really well with Lasagne and Nolearn,
until I reinstalled my Ubuntu. I've configured everything and ran some tests like lasagne tutorials and everything was okay,
so I wanted to use my old code with network like:
net2 = NeuralNet(
    layers=[
        ('input', layers.InputLayer),
        ('conv1', layers.Conv2DLayer),
        ('pool1', layers.MaxPool2DLayer),
        ('conv2', layers.Conv2DLayer),
        ('pool2', layers.MaxPool2DLayer),
        ('conv3', layers.Conv2DLayer),
        ('pool3', layers.MaxPool2DLayer),
        ('hidden4', layers.DenseLayer),
        ('hidden5', layers.DenseLayer),
        ('output', layers.DenseLayer),
        ],
    input_shape=(None, 3, PIXELS, PIXELS),
    conv1_num_filters=32, conv1_filter_size=(3, 3), pool1_ds=(2, 2),
    conv2_num_filters=64, conv2_filter_size=(2, 2), pool2_ds=(2, 2),
    conv3_num_filters=128, conv3_filter_size=(2, 2), pool3_ds=(2, 2),
    hidden4_num_units=500, hidden5_num_units=500,
    output_num_units=50, output_nonlinearity=nonlinearities.softmax,
    update_learning_rate=0.01,
    update_momentum=0.9,
    regression=False,
    max_epochs=1000,
    verbose=1,
        # Training test-set split
    eval_size = 0.2
    )

In fact it was a bit larger, but whatever. And it gives me such error:
 Start training...
/usr/local/lib/python2.7/dist-packages/Lasagne-0.1dev-py2.7.egg/lasagne/init.py:86: UserWarning: The uniform initializer no longer uses Glorot et al.'s approach to determine the bounds, but defaults to the range (-0.01, 0.01) instead. Please use the new GlorotUniform initializer to get the old behavior. GlorotUniform is now the default for all layers.
  warnings.warn("The uniform initializer no longer uses Glorot et al.'s "
Traceback (most recent call last):
  File "las_mnist.py", line 200, in <module>
    net2.fit(X, y)
  File "/usr/local/lib/python2.7/dist-packages/nolearn/lasagne.py", line 138, in fit
    out = self._output_layer = self.initialize_layers()
  File "/usr/local/lib/python2.7/dist-packages/nolearn/lasagne.py", line 369, in initialize_layers
    layer = layer_factory(layer, **layer_params)
TypeError: __init__() takes at least 3 arguments (2 given)

Why I think, it's something with convolutions,
because network with DenseLayers and Dropouts only runs well:
net1 = NeuralNet(
    layers=[
        ('input', layers.InputLayer),
        ('hidden1', layers.DenseLayer),
        ('dropout1', layers.DropoutLayer),  # !
        ('hidden2', layers.DenseLayer),
        ('dropout2', layers.DropoutLayer),  # !
        ('hidden3', layers.DenseLayer),
        ('dropout3', layers.DropoutLayer),  # !
        ('output', layers.DenseLayer),
        ],
    input_shape=(None, 3, PIXELS, PIXELS), #None in the first axis indicates that the batch size can be set later
    dropout1_p=0.5,  # !
    hidden1_num_units=2000,
    dropout2_p=0.5,  # !
    hidden2_num_units=1000,
    dropout3_p=0.5,  # !
    hidden3_num_units=500,

    output_num_units=50, output_nonlinearity=nonlinearities.softmax,
    # learning rate parameters
    update_learning_rate=0.01,
    update_momentum=0.9,
    regression=False,
    # We only train for 10 epochs
    max_epochs=100,
    verbose=1,
    # Training test-set split
    eval_size = 0.2
        )

Please help me, if you have some ideas how to handle it.
Thank you very much!

It looks like you've updated your version of Lasagne inbetween.  Some of the conv and pool layer parameters have been renamed and you'll have to adjust your code.
But yeah, make also sure you're running versions of nolearn and Lasagne that are known to work together.  So if you're getting the latest nolearn from Git master, make sure you're using its requirements.txt to install Lasagne:
pip uninstall Lasagne && \
pip install -r https://raw.githubusercontent.com/dnouri/nolearn/master/requirements.txt


difficult-amethyst: add keyboard, new, and mouse emoji

#413
This adds the keyboard, new, and mouse emoji, which are used on ~community in the collections reordering instructions.
EDIT Also added backhandIndex for onboarding banner

:rocket: PR was released in v0.19.0 :rocket:


Validation / testing dataset preparation

Hello, thank you for this awesome-looking repo! Would it be possible for you to provide instructions on how to obtain and prepare the validation and testing data?
Thanks so much!

Hey @greeneggsandyaml, you need to put your data into the ms coco format like it's written here. Afterward you can use the coco dataset reader. As an alternative you can also implement an additional datareader for your required format(e.g. pascal voc).

Thanks for the quick response! I suppose I was mainly asking about the datasets you used specifically (THEODORE, CEPDOF, FES). Did you preprocess these in any way? Also, do I have to download 139.4 GB for THEODORE? That seems like a ton.

For THEODORE you can download the 25k tfrecord and convert this to mscoco using e.g. datumaro. For FES you need to request permission to download the data. But after this was successful you can download and convert the tfrecord as well.  CEPDOF requires also permission/an account and a manual conversion from that used format to mscoco. But I can send you the coco annotation file if you have the images.


-- minify CSS  removes quotation from strings with blanks

What version of Hugo are you using (hugo version)?

$ hugo 0.69.2

Does this issue reproduce with the latest release?
YES
-- minify removes quotation
feed {
	font-family: "Source Sans Pro", Helvetica, "sans-serif";
}

goes to
feed {
	font-family:  Source Sans Pro, Helvetica, sans-serif;
}

IF strings contains blanks, the quotes MUST stay here.

I verified under https://go.tacodewolff.nl/minify that the current version of the minifier library still shows this behavior. IMHO this behavior is correct however given CSS syntax. To quote https://developer.mozilla.org/en-US/docs/Web/CSS/font-family:

Font family names must either be given quoted as strings, or unquoted as a sequence of one or more identifiers. This means that punctuation characters and digits at the start of each token must be escaped in unquoted font family names.

So "Source Sans Pro" doesn't need to be quoted, "Source Sans 12" or "Source Sans .NET" on the other hand do. That seems to match the library's implementation.

Similar issue: #6621

@palant is correct that removing quotes here is completely valid. If this causes a bug, please file a bug report at https://github.com/tdewolff/minify


Grayscale support in gdew042t2Grays is no longer working

Hi, Martin,
I noticed that the latest gdew042t2Grays.cpp breaks the grayscale support for the display. The following block that forces mono mode (also the default mode) displays the "Starting..." text.
    display.init(false);
    display.setMonoMode(true);
    display.fillScreen(EPD_BLACK);
    display.setTextColor(EPD_WHITE);
    display.drawString(130, 200, "Starting...");
    display.update();

But when I disable the mono mode (i.e., enable grayscale) then it doesn't display anything. Note that I didn't even change the colors in this case to keep it simple.
    display.init(false);
    display.setMonoMode(false);
    display.fillScreen(EPD_BLACK);
    display.setTextColor(EPD_WHITE);
    display.drawString(130, 200, "Starting...");
    display.update();

Note that in the above code display is a very simple wrapper for Gdew042t2Grays that only adds additional functions.
Any ideas on what might be going on here? Here is the datasheet for reference.

Hello @thebitguru
this time you will have to debug it yourself since I do not own anymore (And won't buy anymore SPI epapers)
since I'm focused on helping another projects for a few years.
But last times I tested:
https://github.com/PaperMETAR/FirmwareTinker/blob/master/src/main.cpp
It was working in the demos.
Debug the buffers, check start up commands, I don't think that class has changed anything since last times we checked.

Try to print text in one of the Grays
Try playing around removing Background
Try also making a small mono-mode update and then make the gray-mode update to see if there is any initial initialization wakeUp command that is needed

Thanks for those tips. I will experiment over the next few days and report back. I will submit a PR if I am able to propose a fix.

Great!
Thanks for your contribution. Now this will be fixed by anyone using this display and you also have your code in the contributors list.
Please close it after checking again that it works as expected.

Confirmed against master branch. Thanks!

The @thebitguru I will like to see some pictures/ videos once you finish your creation!
Thanks a lot for choosing our component.

Will do. Thanks for all your work on this library!


Additional features: SLO, auth_response assertion encryption, configurable enc and digest algs, Agreement Screen, better NameID management and minor bug fixes

In this PR we found the following:

https://github.com/OTA-Insight/djangosaml2idp/issues/38 -> fixed
https://github.com/OTA-Insight/djangosaml2idp/issues/36 -> implemented
https://github.com/OTA-Insight/djangosaml2idp/issues/35 -> implemented
https://github.com/OTA-Insight/djangosaml2idp/issues/32 -> implemented
https://github.com/OTA-Insight/djangosaml2idp/issues/31 -> implemented
https://github.com/OTA-Insight/djangosaml2idp/issues/28 -> fixed
https://github.com/OTA-Insight/djangosaml2idp/issues/26 -> some little changes
https://github.com/OTA-Insight/djangosaml2idp/issues/23 -> implemented
added decorators to fill SAML attributes in requests.session

Still need unit tests and a better documentation.

Changes are consolidated in https://github.com/OTA-Insight/djangosaml2idp/pull/49, so closing this one


Add pending transaction for HUSD and SEEDS redemption

Issue: After submitting a request for redemption of HUSD or buying SEEDS there is no indicator of a pending transaction.
Solution: Add transaction to transaction table view with a pending state, followed by a completed state once done.

In the old version, you could only redeem in the wallet page and the transaction would show up there immediately -- maybe just need to redirect there when a redemption is done in the profile page?


layer2 mode will use NodePort?

Is this a bug report or a feature request?:
bug
What happened:
when i install the  metalb, and then specify the service type to LoadBalancer,
then it will give me a exteranl_ip correctly, and it works.
but I find that the service will automactilly allocated a nodePort, why this happened?
What you expected to happen:
nodePort should not be allocated and used.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

MetalLB version: latest
Kubernetes version: 1.11.1
BGP router type/version: layer2
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a): ubuntu16.04 standard 4.4 kernel

Kubernetes does this automatically, there is no choice. The three service types (ClusterIP, NodePort, LoadBalancer) are supersets of each other. A NodePort service also has an internal cluster IP. A LoadBalancer service also has a NodePort and an internal cluster IP.
This is part of the core k8s service logic, MetalLB can't change it even though it doesn't care about the NodePort.

@danderson how about that if i use the bgp mode, if LoadBalancer must have nodePort, oh that's awful,
cluster all node will use the same nodePort, is that means that the lodabalancer service number if limited by the nodePort numbers. it's awful, is other lb do the same things?

Yes, all k8s LoadBalancer services do this. All MetalLB modes, and all cloud implementations, etc. It's built into the core k8s logic for services, no way to turn it off. Yes, it means the number of LBs is limited by the number of available NodePorts, by default 2767.
Sorry, there's nothing I can do to improve this. If this is a problem for you, you should report a bug in upstream Kubernetes and explain why this breaks your use case. Hopefully that will encourage k8s devs to remove the requirement that LoadBalancer has a NodePort.

@danderson  thanks to explain that , i will try to report this in the upstream. thanks a lot .


TEST: separate out NIST ECC tests from non-NIST

ECC keys with non-NIST group names aren't supported when running with
the FIPS provider.
Keys with such groups that are included in evp_test stanza files
aren't even possible to decode if provider side decoders are used,
since those depend on available EVP_KEYMGMT implementations and what
they support.
Those keys could only be decoded because the legacy decoders were
used.
To make these tests future proof, we separate out the stanzas having
keys with NIST approved group names into separate files, and adjust
the file lists in test/recipes/30-test_evp.t aaccordingly.

#12587 will depend on this

This pull request is ready to merge

Merged
e6ed04a9dcc2ead94e35c4a7400b9c998b5ad9ac TEST: separate out NIST ECC tests from non-NIST


ci: testplan: do not run tests on all platforms when a test changes

With many tests having 10s or scenarios and variants, anytime we make a
change to a test right now, we end up building all scenarios on all
platforms which ends up in multiple 10s of the thousands of instances
that need to run on 30 or 40 runners blocking CI for hours. We do not
really need that, a test needs to be smart about its coverage and not
rely on boiling the ocean to catch, mostly build errors that are
platform specific.
Change this to do the normal coverage we get on push events.
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>

example https://github.com/zephyrproject-rtos/zephyr/actions/runs/9515757778 (sorry @ycsin , I had to cancel that job), try a bit later when this PR is merged.


ERROR(cortex-m-rt): The interrupt vectors are missing.

Trying out your tutorial but gettings stuck compiling when adding microbit to the .toml
ERROR(cortex-m-rt): The interrupt vectors are missing.

Finally got it to build after adding extern crate microbit; to main.rs
What gives? 😄

I encountered the same issue just now using the latest version of both microbit and cortex-m-rt. Adding the extern crate statement mentioned above worked for me as well.

This also happens if you don't specify the  chip in Embed.toml.
[default.general]
# chip = "nrf52833_xxAA" # uncomment this line for micro:bit V2
# chip = "nrf51822_xxAA" # uncomment this line for micro:bit V1


Erroneous/Inconsistent value for context.source.id

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.18.2
Amplify CLI Version
8.3.1
What operating system are you using?
Windows 11
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, function, api
Amplify Commands
Not applicable
Describe the bug
I have a model Project that has (at least) two subfields tasks and siteLocations.
Whenever I execute a GetProject query and select .tasks.items.* my query returns the two entries as expected. However, the query returns null for both subfields if I also include .siteLocations.items.* in the selection set.
Upon examining the cloudwatch logs I can see that when I do not select the extra subfield the context.source.id and the resulting DDB query template are correct. However, when I include the other subfield I can see that context.source.id has an erroneous value halfway through the execution of the pipeline and the resulting DDB query template reflects this erroneous value.
I elaborate on this in Additional Information.
Expected behavior

Adding a subfield to the selection set should not cause another subfield to fail.
The context.source.id field (and everything else in the source) should remain consistent througout the invocation of the pipeline at that same level of nesting.

Reproduction steps

query MyQuery1_succeeds {
  getProject(id: "d90758f8-e2f2-4f58-ac39-bdec31e36e44") {
    tasks {
      items {
        id
        name
      }
    }
  }
}

query MyQuery2_fails {
  getProject(id: "d90758f8-e2f2-4f58-ac39-bdec31e36e44") {
    tasks {
      items {
        id
        name
      }
    }
    siteLocations {
      items {
        id
        name
      }
    }
  }
}

MyQuery1_succeeds returns the two values as expected for in tasks.items.
MyQuery2_fails returns null for tasks.items (and for siteLocations)
GraphQL schema(s)

# Put schemas below this line
type Project
  @model(
    subscriptions: null,
    timestamps: {createdAt: "createdAt", updatedAt: "updatedAt"})
  @auth(rules: [
    { allow: groups, groupsField: "id", groupClaim: "customGroupClaim", operations: [create, read, update, delete] }
  ])
{
  id: ID!

  tasks: [Task] @hasMany(indexName: "byProjectIdBySortOrder", fields: ["id"])

  siteLocations: [SiteLocation] @hasMany(indexName: "byProjectIdBySortOrder", fields: ["id"])
}

type Task
  @model(
    subscriptions: null,
    timestamps: {createdAt: "createdAt", updatedAt: "updatedAt"}
  )
  @auth(
    rules: [
      { allow: groups, groupsField: "projectId", groupClaim: "customGroupClaim", operations: [create, read, update, delete] }
    ])
{

  id: ID! @primaryKey(sortKeyFields: ["projectId"])
  projectId: ID! @index(name: "byProjectIdBySortOrder", sortKeyFields: ["sortOrder"])

  name: String
  description: String
  sortOrder: Int
}

type SiteLocation
  @model(
    subscriptions: null,
    timestamps: {createdAt: "createdAt", updatedAt: "updatedAt"}
  )
  @auth(rules: [
    { allow: groups, groupsField: "projectId", groupClaim: "customGroupClaim", operations: [create, read, update, delete] }
  ])
{
  id: String! @primaryKey(sortKeyFields: ["projectId"])
  projectId: ID! @index(name: "byProjectIdBySortOrder", sortKeyFields: ["sortOrder"])

  name: String
  address: String
  sortOrder: Int
}

Log output

# Put your logs below this line

Additional information
I have checked the cloudwatch logs for the query and made the following observations:

all fields resolve with "fieldInError": false
The context.source.id contains string value "e0cb39cb-3685-4dd6-b7b8-8d5fc093c64e" (as expected) at the earlier entries in the log but when the resolver function corresponding to Project.siteResolver.auth.1.req (referenced as ProjectsiteLocationsauth0Function) executes its entry shows that context.source.id now contains "[\"e0cb39cb-3685-4dd6-b7b8-8d5fc093c64e\", \"5fb82c2b-a371-4a15-a41d-81ee6a991469\"]",

I know the source of the extraneous guid "5fb82c2b-a371-4a15-a41d-81ee6a991469" seen above. It corresponds to another Project that the user has access to as indicated by a custom group claim (which I describe below). I just don't know why it is added into the source object.
Special Modifications:
I have added a custom cognito claim that returns a list of ProjectIds that the user has access to. I reference this as the customGroupClaim (as seen in the schema provided). I have therefore overriden the Query.getProject.auth.1.req.vtl to ensure this value is treated as a list (#featurerequest :) ). This results in the authFilter like this:

  "context": {
      "stash": {
           "authFilter": {
                "or": [
                    {
                        "id": {
                            "in": [
                                "e0cb39cb-3685-4dd6-b7b8-8d5fc093c64e",
                                "5fb82c2b-a371-4a15-a41d-81ee6a991469"
                            ]
                        }
                    }
                ]
            }
       }
  }

My Hypothesis:
While it seems farfetched it feels like context.source.id has been set to whatever value was provided as the id to filter on. In my case this is a list. When I modify my system to return a list of only one item the erroneous context.source.id in the logs shows a stringified list containing one string. I modified the filter to use eq: string instead of in: [string] but still end up with the stringified list containing one string.
Other:
I upgraded from amplify cli 8.2.0 to 8.3.1 to see if that would solve the problem but it didn't.

Hey @naedx, Thank you for reaching out. Could you please test the following in the AppSync console and let us know if you are observing an empty array in the result.

Create and run a createproject mutation.
Create and run a createSiteLocation mutation with the sort field, for example:

Run a getProject query with the SiteLocation items. For example:

On replicating this I was able to see the following output.

Hey @ykethan and @josefaidt. Thank you for looking into this.
@ykethan, I'm going to retry as you've suggested and let you know by next Tuesday (7/06). I'll further add more aspects from my setup if it doesn't manifest with this alone. (My true and complete setup where the problem is manifesting contains about 13 models and 50 types at the moment as well as some lambda functions.)
Based on what you have proposed, my setup should return the results as you see. But, but it would return null for .siteLocations and .tasks only after .tasks is added.

Hey @naedx 👋 to add on to @ykethan 's comment above, what is the motivation behind setting the groupClaim on the ID field rather another field? Or what is the use case you're looking to accomplish?

The use case is that I want to be able to authorize, and deauthorize users from the a Project and all it's children in a multi-tenant setup.
If I were to use Owner Authorization I would have to add the owner: [String!] to the project and every child type, and object and update each one when then users are added/removed.
I have used the ID field since this uniquely identifies the Project and all the children bear this as an index. That way, no object can be accessed without the user possessing a claim on the project.
Is there a better approach to achieve this?

Hey @naedx, I would suggest looking into custom attributes for Amazon Cognito user pools where we can set the record’s ID as a value in a custom Cognito attribute. Please refer to the following issues providing additional information and examples.
https://github.com/aws-amplify/amplify-category-api/issues/28#issuecomment-1132978133
https://github.com/aws-amplify/amplify-category-api/issues/64
Please do let us know if this helps with your use case.

I think the issue of the erroneous $ctx.source.id is caused by what is described here in the comment on Issue #64:

Hopped onto a call with @lseemann, after digging deeper, we found that the offending code in the resolver was because there is a line of code that updates the $ctx.source.<fieldname> to $primaryRoleX.
Have created a PR aws-amplify/amplify-cli#10197.

I can see the offending code in my the default generated templates:
#if( $util.authType() == "User Pool Authorization" )
  #if( !$isAuthorized )
    #set( $primaryRole0 = $util.defaultIfNull($ctx.identity.claims.get("customGroupClaim"), "___xamznone____") )
    #set( $ownerClaimsList0 = [] )
    #if( (!$util.isNull($ctx.source.id)) && (($ctx.source.id == $primaryRole0) || $ownerClaimsList0.contains($ctx.source.id)) )
      #set( $isAuthorized = true )
      $util.qr($ctx.stash.put("authFilter", null))
    #else
      #if( !$isAuthorized && $util.isNull($ctx.stash.authFilter) )
        $util.qr($ctx.source.put("id", $primaryRole0))
        #set( $isAuthorized = true )
      #end
    #end
  #end
#end

Specifically, at $util.qr($ctx.source.put("id", $primaryRole0)).
In overriding my templates to handle the list of strings I had replaced this code but it seems I have other subfields that I hadn't overriden yet that still contained it.

Hey @naedx, Thank you for the information. On reaching out to the team and discussing your use case, the team suggests separating the groups as a separate field as combining Multi tenant and groups on a ID may cause unintended behaviour in your application.
For example:
type Todo @model @auth(rules: [{ allow: groups, groupsField: "groups" }]){
  id: ID! @primaryKey
  name: String! @index(name: "byName", queryField: "todoByName")
  description: String
  groups: [String]
}

here we separate the groups and the ID field allowing us to logically separate the items that can be retrieved byname and if present in a specific group

Hey @ykethan, thanks to you and the team for the reply! Indeed, changing from using the key field to another field generates the authZ rules that I need.
That addresses my use case sufficiently. I only now need to set this tenantId on all existing records and all new going forward.

Changing my schema to follow this model:

type Todo
  @model
  @auth(rules: [{ allow: groups, groupsField: "tenantId", groupClaim: "customGroupClaim" }])
{
  id: ID! @primaryKey
  tenantId: String!
  name: String! @index(name: "byName", queryField: "todoByName")
  description: String
}

Generates the following:

#if( $util.authType() == "User Pool Authorization" )
  #if( !$isAuthorized )
    #set( $authFilter = [] )
    #set( $role0 = $util.defaultIfNull($ctx.identity.claims.get("customGroupClaim"), []) )
    #if( $util.isString($role0) )
      #if( $util.isList($util.parseJson($role0)) )
        #set( $role0 = $util.parseJson($role0) )
      #else
        #set( $role0 = [$role0] )
      #end
    #end
    #if( !$role0.isEmpty() )
      $util.qr($authFilter.add({ "tenantId": { "in": $role0 } }))
    #end
    #if( !$authFilter.isEmpty() )
      $util.qr($ctx.stash.put("authFilter", { "or": $authFilter }))
    #end
  #end
#end

Hey @naedx, Glad to hear that you are back up and running. Please do let us know if we can go on ahead and close the issue.

Thanks for the follow up, @ykethan . The original issue no longer manifests if I set auth to use a non-key field. You may close this on that basis.
(Overwriting the source.id based on the selection set still seems like an odd behavior though.)


"asgi_redis is too old"

Current master cannot be executed.
RuntimeError: Your version of asgi_redis is too old - it must be at least 1.2.0
To fix I need to run:
pip install -r requirements_big_mode.txt
To install the necessary version of asgi_redis
We might consider to put this into
requirements_production.txt

Current master in non big mode works without problems. Also a fresh install of big mode works. asgi-redis is installed in version 1.3.0. So this might be only an update problem.

So this might be only an update problem.

doubt it.
did the npm install and pip install -r routine as usuall.
You might want to checkout current master in a new directory to reproduce this issue.
requrements-productive.txt now seems dependant on asgi_redis.

$ rm -r .virtualenv/
$ rm -r personal_data/
$ python3 -m venv .virtualenv
$ source .virtualenv/bin/activate
$ pip install -U setuptools pip
$ pip install -r requirements.txt
$ python manage.py start

This works without any problems. asgi-redis must not be required if use_redis is False in settings.

Tested a fresh git clone with the described setup: Works for me. asgi_redis shouldn't be installed, if you just install the requirements.txt?

Hmmm. Seems I just took time older requirements into new setup or something. Thanks for clarification.


Bug:  Forge build  failed to parse unrecognised token, /**

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (44f3a4b 2022-07-18T00:09:10.206569Z)
What command(s) is the bug in?
forge build
Operating System
macOS (Intel)
Describe the bug
Running  forge build with debug output I noticed this:
 failed to parse "~/workspace/contracts/lib/Comptroller.sol" ast:
"[Diagnostic { loc: File(0, 116, 174), level: Error, ty:
ParserError, message: "unrecognised token
 '/**\n     * @notice Whether or not this market is listed\n     \n*/',
expected \"(\", \"[\", \"address\", \"bool\", \"byte\", \"bytes\", \"case\", \"default\", \"error\", \"false\", \"function\", \"leave\", \"mapping\", \"payable\", \"string\", \"switch\", \"this\", \"true\", \"type\", \"}\", Bytes, Int, Uint, address, hexnumber, hexstring, identifier, number, rational, string", notes: [] }]".

Falling back to regex to extract data

It successfully compiles, just making note of this error

I believe this was just fixed here https://github.com/hyperledger-labs/solang/pull/925

I believe this was just fixed here hyperledger-labs/solang#925

yup, fixed as of forge 0.2.0 (cce3a44 2022-07-20T00:14:55.494548Z)

I'm still getting a parse error, using latest forge 0.2.0 and solidity 0.8.20
> forge fmt --check && pnpm solhint "{script,src,test}/**/*.sol"

Error: ParserError
     ╭─[ERC1155LazyMintable.sol:101:48]
     │
 101 │             uint256 i = _voucher.commissionBps.length;
     │                                                ┬
     │                                                ╰── unrecognised token '(', expected "!=", "%", "%=", "&", "&&", "&=", ")", "*", "**", "*=", "+", "+=", ",", "-", "-=", "/", "/=", ":", ";", "<", "<<", "<<=", "<=", "=", "==", ">", ">=", ">>", ">>=", "?", "]", "^", "^=", "|", "|=", "||", "}"

This is not related at all, please open a new issue with the full file and forge version. @codemedici


IG Builder warnings ignored

No changes but to ignore the new warnings.

https://build.fhir.org/ig/IHE/ITI.MHD/branches/Moehrke_builder_updates/index.html

I have an info warning that might be ignorable, but I am not sure if that is the right action
https://chat.fhir.org/#narrow/stream/179166-implementers/topic/searchParameter.20codeableConcept


Add link to Github repo

There are some places in the app where we need to link back to this repository.

FAQ Page

There are about 2 sections here where we can direct people here to open issues (indicated in the screenshot)

The other part will be just on the home page, maybe in the footer somewhere

I have opened a PR adding this functionality.  https://github.com/OlivierJM/powercut/pull/27


[New Port Request] libnfc

Library name: libnfc
Library description:libnfc is a library which allows userspace application access to NFC devices.
Source repository URL: https://github.com/nfc-tools/libnfc
Project homepage (if different from the source repository): http://www.nfc-tools.org/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.