Match managing provisioning profiles for DriverKit

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

Issue Description
I'm trying to get Match to manage the Provisioning profile for DriverKit
It seems in Platforms there is not option for DriverKit.
When I create this option in the dev account it actually creates a prov profile for macOS with all device list of iOS and iPadOS.
Is there a way to create a Prov profile for DriverKit with Match?
Thanks
Environment
[✔] 🚀
[18:12:54]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅

### Stack

| Key                         | Value                                                    |
| --------------------------- | -------------------------------------------------------- |
| OS                          | 13.5                                                     |
| Ruby                        | 3.2.2                                                    |
| Bundler?                    | true                                                     |
| Git                         | git version 2.39.3 (Apple Git-145)                       |
| Installation Source         | ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/bin/fastlane |
| Host                        | macOS 13.5 (22G74)                                       |
| Ruby Lib Dir                | ~/.rbenv/versions/3.2.2/lib                              |
| OpenSSL Version             | OpenSSL 3.1.2 1 Aug 2023                                 |
| Is contained                | false                                                    |
| Is homebrew                 | false                                                    |
| Is installed via Fabric.app | false                                                    |
| Xcode Path                  | /Applications/Xcode15_2.app/Contents/Developer/          |
| Xcode Version               | 15.2                                                     |
| Swift Version               | 5.9.2                                                    |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_GB.UTF-8 | ✅ |
| LC_ALL   |             |   |
| LANGUAGE |             |   |

### fastlane gems

| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.220.0 | ✅ Up-To-Date  |

### Loaded fastlane plugins:

**No plugins Loaded**

Loaded gems

| Gem                             | Version      |
| ------------------------------- | ------------ |
| error_highlight                 | 0.5.1        |
| did_you_mean                    | 1.6.3        |
| syntax_suggest                  | 1.0.2        |
| bundler                         | 2.4.19       |
| pathname                        | 0.2.1        |
| rake                            | 13.2.1       |
| base64                          | 0.2.0        |
| nkf                             | 0.2.0        |
| rexml                           | 3.2.6        |
| CFPropertyList                  | 3.0.7        |
| concurrent-ruby                 | 1.2.2        |
| i18n                            | 1.14.1       |
| minitest                        | 5.20.0       |
| thread_safe                     | 0.3.6        |
| tzinfo                          | 1.2.11       |
| activesupport                   | <IP_ADDRESS>      |
| public_suffix                   | 5.0.5        |
| addressable                     | 2.8.6        |
| httpclient                      | 2.8.3        |
| json                            | 2.7.2        |
| algoliasearch                   | 1.27.5       |
| dotenv                          | 2.8.1        |
| rainbow                         | 3.1.1        |
| yaml                            | 0.3.0        |
| arkana                          | 2.0.0        |
| artifactory                     | 3.0.17       |
| atomos                          | 0.1.3        |
| aws-eventstream                 | 1.3.0        |
| aws-partitions                  | 1.913.0      |
| aws-sigv4                       | 1.8.0        |
| jmespath                        | 1.6.2        |
| aws-sdk-core                    | 3.191.6      |
| aws-sdk-kms                     | 1.78.0       |
| aws-sdk-s3                      | 1.146.1      |
| babosa                          | 1.0.4        |
| claide                          | 1.1.0        |
| fuzzy_match                     | 2.0.4        |
| nap                             | 1.1.0        |
| netrc                           | 0.11.0       |
| ffi                             | 1.16.2       |
| ethon                           | 0.16.0       |
| typhoeus                        | 1.4.0        |
| cocoapods-core                  | 1.10.2       |
| cocoapods-deintegrate           | 1.0.5        |
| cocoapods-downloader            | 1.6.3        |
| cocoapods-plugins               | 1.0.0        |
| cocoapods-search                | 1.0.1        |
| cocoapods-trunk                 | 1.6.0        |
| cocoapods-try                   | 1.2.0        |
| colored2                        | 3.1.2        |
| escape                          | 0.0.4        |
| fourflusher                     | 2.3.1        |
| gh_inspector                    | 1.1.3        |
| molinillo                       | 0.6.6        |
| ruby-macho                      | 1.4.0        |
| nanaimo                         | 0.3.0        |
| xcodeproj                       | 1.24.0       |
| cocoapods                       | 1.10.2       |
| colored                         | 1.2          |
| highline                        | 2.0.3        |
| commander                       | 4.6.0        |
| declarative                     | 0.0.20       |
| digest-crc                      | 0.6.5        |
| domain_name                     | 0.6.20240107 |
| emoji_regex                     | 3.2.3        |
| excon                           | 0.110.0      |
| faraday-em_http                 | 1.0.0        |
| faraday-em_synchrony            | 1.0.0        |
| faraday-excon                   | 1.1.0        |
| faraday-httpclient              | 1.0.1        |
| multipart-post                  | 2.4.0        |
| faraday-multipart               | 1.0.4        |
| faraday-net_http                | 1.0.1        |
| faraday-net_http_persistent     | 1.2.0        |
| faraday-patron                  | 1.0.0        |
| faraday-rack                    | 1.0.0        |
| faraday-retry                   | 1.0.3        |
| ruby2_keywords                  | 0.0.5        |
| faraday                         | 1.10.3       |
| http-cookie                     | 1.0.5        |
| faraday-cookie_jar              | 0.0.7        |
| faraday_middleware              | 1.2.0        |
| fastimage                       | 2.3.1        |
| jwt                             | 2.8.1        |
| multi_json                      | 1.15.0       |
| os                              | 1.1.4        |
| signet                          | 0.19.0       |
| googleauth                      | 1.8.1        |
| mini_mime                       | 1.1.5        |
| trailblazer-option              | 0.1.2        |
| uber                            | 0.1.0        |
| representable                   | 3.2.0        |
| retriable                       | 3.1.2        |
| google-apis-core                | 0.11.3       |
| google-apis-androidpublisher_v3 | 0.54.0       |
| google-apis-playcustomapp_v1    | 0.13.0       |
| google-cloud-env                | 1.6.0        |
| google-apis-iamcredentials_v1   | 0.17.0       |
| google-apis-storage_v1          | 0.31.0       |
| google-cloud-errors             | 1.4.0        |
| google-cloud-core               | 1.7.0        |
| google-cloud-storage            | 1.47.0       |
| mini_magick                     | 4.12.0       |
| naturally                       | 2.2.1        |
| optparse                        | 0.4.0        |
| plist                           | 3.7.1        |
| rubyzip                         | 2.3.2        |
| security                        | 0.1.5        |
| simctl                          | 1.6.10       |
| terminal-notifier               | 2.0.0        |
| unicode-display_width           | 2.5.0        |
| terminal-table                  | 3.0.2        |
| tty-screen                      | 0.8.2        |
| tty-cursor                      | 0.7.1        |
| tty-spinner                     | 0.9.3        |
| word_wrap                       | 1.0.0        |
| rouge                           | 2.0.7        |
| xcpretty                        | 0.3.0        |
| xcpretty-travis-formatter       | 1.0.1        |

*generated on:* **2024-04-12**

Hello, @CarlosNano
Creating a provisioning profile for DriverKit using Match can be a bit tricky since Match typically manages provisioning profiles for iOS, macOS, and tvOS. However, it is possible to create a DriverKit development provisioning profile through the Apple Developer account. Here’s how you can do it:
Go to Certificates, Identifiers & Profiles in your Apple Developer account.
Click on Profiles in the sidebar, then click the add button (+) at the top left.
Under Development, select DriverKit development, then click Continue.
Select the App ID you want to use for development, then click Continue. Ensure that your App ID has a DriverKit entitlement enabled.
Select one or more development certificates, then click Continue.
Select one or more devices, then click Continue.
Enter a profile name, then click Generate.
Click Download to get your provisioning profile.
Remember, for release candidate apps, you should continue to use platform-specific provisioning profiles to meet the signing requirements. If you’re using Xcode Automatic Signing, the appropriate provisioning profile type will be selected for the requested distribution type.
My suggestion is helpful for you. If you have any query please tell me.
Best Regard,
angela683h


Want to make navbar more improved

Want to make the dark mode icon more attractive and also want to add some hover effect as all components of navbar have hover effects. @Trisha-tech Please assign this issue to me. I want to make it better and Enhance my skills in open source contribution.

I want to recreate this project navbar . I am UI UX Web designer and also a web developer . So you can assign this task to me  for knowing me better you can reach out my recent project   @naitikhoriya1


userId is undefined when used in publishComposite

We're using this package: https://github.com/englue/meteor-publish-composite. Not sure on which side is the issue.
We have the following publication:
Meteor.publishComposite('candidates', function() {   return {     find() {       return Candidates.find();     },     children: [       {         find(candidate) {           return Jobs.find(candidate.jobId);         }       }     ]   }; });
We have the following hook:
Jobs.before.find(function (userId, selector, options, cursor) {   // userId is undefined when it's called from children publication });

@mvcdev i'm not sure if publishComposite is also hooking on the find method somehow.
I need to check but i can't do it right now.
Can you maybe write a small repro project?

Hi @namirsab! Here is the new repository. Here is the piece of code illustrating the issue: https://github.com/mvcdev/todos/blob/master/imports/api/tasks.js#L7-L36

I'm pretty sure this is related to meteor/meteor#8031 and meteor/meteor/8629 which @mitar and I are working on to get fixed.

People should just start using https://github.com/peerlibrary/meteor-user-extra. ;-)

This issue does not lie in this package. publish-composite runs the children code on the server implicitly in new fibers without binding the environment, which makes the in current invocation being lost and the accompanying userId.
I'll put together a PR some time this week.

I'm closing this as /englue/meteor-publish-composite#105 should resolve this.


OpenStack Infra: Enable node start and stop

Enables starting and stopping nodes through the Ironic API.
Previously, all node operations were disabled for OpenStack. For
now, we are enabling only start and stop.

Start and Stop buttons available from Infrastructure Nodes view:

Only buttons that are valid are shown in single Node view:

:+1: looks reasonable to me!

@miq-bot assign @chessbyte

@miq-bot add_label euwe/yes

Tested against OSP10, found one issue - hardware.provision_state is apparently blank sometimes, even though the correct state is available.  That prevents the user from powering the node on.
Is there any reason to limit 'power on' to depend on provision_state?

@Ladas please review, and assign back to me when ready to merge

@tzumainn provision_state shouldn't be blank. Can you point me to an example and I'll have a look at what may be wrong.
As for power on, the thinking is users should only be able to power on a node when it is in certain states. Like they shouldn't be able to power on a node that is manageable state. If you don't think that make sense or is too limiting, we can remove that restriction.

@rwsu, I don't think we want to limit when 'power on' works past when it works in OpenStack, so limiting it on provision_state may be incorrect.
I suspect that provision_state may be blank immediately after adding a new node directly from CloudForms, as that's the only time it's set (that I can see).

The CI failure appears to be an infrastructure issue:
Phantomjs does not appear to be installed in /home/travis/.phantomjs/2.1.1/x86_64-linux/bin/phantomjs, installing!
bunzip2: phantomjs-2.1.1-linux-x86_64.tar.bz2 is not a bzip2 file.
tar: phantomjs-2.1.1-linux-x86_64.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

@miq-bot assign @romanblanco

@romanblan could you make sure this is good from the UI perspective? Backend should be ok and @durandom is fine doing validate first and support as next PRs (I remember reading that in one response)

@rwsu please rebase

@rwsu Please check the one comment, otherwise looks good to me :+1:, I've tried in UI, found no issues :wink: @Ladas, @tzumainn

@miq-bot assign @tzumainn

I've tested this successfully, looks like we're all good to go then!

Euwe Backport details:
$ git log -1
commit 27cb0d671a77fb440659d3b2784927f19cefdccb
Author: Greg Blomquist<EMAIL_ADDRESS>Date:   Wed Oct 19 13:09:17 2016 -0400

    Merge pull request #11634 from rwsu/openstack_node_start_stop

    OpenStack Infra: Enable node start and stop
    (cherry picked from commit bba1987c272e67a49b8255051163e58c6093a253)


Sorted List binarySearch functions

Based on PR for commons-lang3 https://github.com/apache/commons-lang/pull/1270
There is Collections.binarySearch() in Java core. However, it searches for exact element which is often not usable, as the elements are typically sorted by particular field.
These methods introduce binarySearch() on (sorted) List, with ability to provide sorting key extraction function and key comparator.
The rest of semantics, behavior, parameters and return values remain consistent with Collections.binarySearch() from Java core.

@kvr000
Please only provide only one binarySearch() API in this PR, like ArrayUtils in Commons Lang, no First/Last API.


We Need a Dodge Sound

Now that we are implmenting dodging, we should have a sound for it!

Ffffft Ffffft

swoosh swoosh swooh

Finished via 083a1cc885b83bdffa2572a585cc4619361569dc


Update authentication.md

add missing conjunction

@googlebot I signed it!

Hi @RFMVasconcelos
Can you please give this PR a review

Thank you for the contribution. Closing this in favour of new docs at https://github.com/awslabs/kubeflow-manifests/tree/v1.3-branch/distributions/aws/examples/cognito
/close


security: Enable no-new-privs by default

security: Enable no-new-privs by default

By default, we don't want the containers spawned by our agent to be
able to gain additional privileges.

Fixes #165

Signed-off-by: Sebastien Boeuf<EMAIL_ADDRESS>

cc @mcastelino @sameo

LGTM


NIFI-7127 - Allow injection of SecureHasher into FingerprintFactory

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

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

For documentation related changes:

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

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

@exceptionfactory Let me know what you think of this one.

Closing this PR in favor of https://github.com/apache/nifi/pull/4867 which was rebased on top of NIFI-7668/PR-4809 which introduces the PropertyEncryptor.


Remove Firefox fieldset bug callout

#21262 removed v4's copy of this callout.
The bug the callout covered was fixed in late 2016.

Closing since I wasn't aware that Bootstrap 3 had reached EOL.


BotService Command Review Comments

See here for documentation on extensions:
https://github.com/Azure/azure-cli/tree/master/doc/extensions
Since this issue is already open, feel free to reference it in your PR there.
Blocking

[x] bot create: kind needs enum value (https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#registering-enums)
[x] bot create: Fix casing and help text. Group arguments (arg_group kwarg) and expose other options that the ARM template exposes. Consider adding an example.
[x] Rename bot get command to bot show. (https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md#standard-command-types)
[x] Rename <channel> get commands to channel show. (https://github.com/Azure/azure-cli/blob/dev/doc/command_guidelines.md#standard-command-types)
[x] for channels change --enabled to use three_state_flag and make not required (flag to disable) https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#registering-flags
[x] Remove _ characters from option names.
[x] Add missing help text.  For "groups-mode" and "call-mode", use names that make it clear these are flags and not enums like "use-groups-mode" or "enable-groups-mode". https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#registering-flags

Additive Changes

[ ] Support --ids for the bot service commands. https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#supporting-the-ids-parameter
[ ] Expose bot list command.
[ ] Consider exposing convenience arguments on the update command. https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#generic-update-commands
[ ] * (for me) investigate whether --ids should apply or not for the channel commands.
[ ] generic_update_commands for channel commands. https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#generic-update-commands

Closing as botservice is currently an extension and these issues are tracked under:
https://github.com/Azure/azure-cli-extensions/issues/158
Will reopen if botservice becomes a module.


Inflection failed to pick up class via embeds_many association

I have a class Institution embeds_many :campuses, I also have a inflection initializers to pick up the this singular correctly. Here is the output in the console:
Loading development environment (Rails 4.1.1)
irb(main):001:0> Institution.new.campuses
NameError: uninitialized constant Campus
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:238:in `const_get'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:238:in `block in constantize'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:236:in `each'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:236:in `inject'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/inflector/methods.rb:236:in `constantize'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/activesupport-4.1.1/lib/active_support/core_ext/string/inflections.rb:66:in `constantize'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/metadata.rb:575:in `klass'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/embedded/many.rb:448:in `scope'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/embedded/many.rb:240:in `block in initialize'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/proxy.rb:42:in `init'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/embedded/many.rb:234:in `initialize'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:44:in `new'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:44:in `create_relation'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:26:in `__build__'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:104:in `block (2 levels) in get_relation'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/threaded/lifecycle.rb:125:in `_loading'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:100:in `block in get_relation'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/threaded/lifecycle.rb:84:in `_building'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:99:in `get_relation'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/bundler/gems/mongoid-9646fa21222c/lib/mongoid/relations/accessors.rb:187:in `block in getter'
	from (irb):1
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/railties-4.1.1/lib/rails/commands/console.rb:90:in `start'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/railties-4.1.1/lib/rails/commands/console.rb:9:in `start'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:69:in `console'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
	from /opt/rubies/1.9.3+envato4/lib/ruby/gems/1.9.1/gems/railties-4.1.1/lib/rails/commands.rb:17:in `<top (required)>'
	from bin/rails:8:in `require'
	from bin/rails:8:in `<main>'irb(main):002:0>

I pushed my app for investigation here: https://github.com/joneslee85/demo

Closing for no response. If inflections cannot pick something up, they need to be added to the inflections in your app yourself... See: http://api.rubyonrails.org/classes/ActiveSupport/Inflector/Inflections.html


TST: Interpolate: Parameterise RegularGridInterpolator tests

Reference issue

closes #16582
What does this implement/fix?

Parameterises the remaining test that are easy to do so and weren't done in https://github.com/scipy/scipy/pull/16508.
Additional information

Apologies there is actually a mistake in this pr:
https://github.com/scipy/scipy/blob/1a10f0a2b10a596b154bda199c8497c77ef424e9/scipy/interpolate/tests/test_rgi.py#L112
I forgot to rename this with the test prefix so this test isn't currently be executed. I will make a follow up...

Oh no worries, indeed I missed that too...


Enable Win32 CI by appveyor

Because there are many Win32 users start using this starter.
See: #33

Done


Plan failure when no backend services specified

GCP load balancers can be created solely with backend buckets
instead of backend services.  However, that fails.  Here's an example:
# bind the bucket `lb-bucket` to a GCP backend_bucket
resource "google_compute_backend_bucket" "testlb-backend-bucket" {
  name        = "testlb-backend-bucket"
  bucket_name = "${google_storage_bucket.my_bucket.name}"
  enable_cdn  = false
}

# the URL map points to the backend bucket, not a backend service
resource "google_compute_url_map" "testlb-url-map" {
  name        = "testlb-url-map"
  default_service = "${google_compute_backend_bucket.testlb-backend-bucket.self_link}"
}

module "lbtest-lb" {
  name        = "lbtest-lb"

  source      = "GoogleCloudPlatform/lb-http/google"
  version     = "1.0.5"

  region      = "${var.gcp_region}"

  create_url_map = false
  url_map        = "${google_compute_url_map.testlb-url-map.self_link}"

  # no backend services
  target_tags = []
  backends = {}
  backend_params = []
}

With this setup, terraform plan fails with:
Error: module.lbtest-lb.google_compute_firewall.default-hc: 1 error(s) occurred:

* module.lbtest-lb.google_compute_firewall.default-hc: element: element() may not be used with an empty list in:

${element(split(",", element(var.backend_params, count.index)), 2)}

Since the default-hc will not be created if backend_params is empty,
we just need the expression to parse.  Unfortunately, this requires a
tricky expression to work around a HCL issue:
https://github.com/hashicorp/hil/issues/50#issuecomment-320078816
I used the pipe | character is as delimiter for that trick, because GCP names cannot have pipes.

Fixed with #9


Updated sample app to point to latest release

Updated sample app to v1.0.0-rc1 for trace SDK and API and v0.21.0 for metric SDK and API

@Aneurysm9 can you review this again? I have updated the PR to address your changes.


is this a bug

i can use
when
then
in drools
but i cannot use it in nools, there must be a Constraints at least.
is this a bug in nools?

I"m not sure , you are asking for an empty rule correct ? Cant you just place a constraint that matches on Object  and make the problem go away ?

yes, i do this in this way for now.
but i wish, it could be fixed someday.


Change HostProfileId to be coc.vim

Changes profile from 0_profile.ps1 to coc.vim_profile.ps1

so, coc.vim_profile.ps1 will be loaded instead of Microsoft.Powershell_profile.ps1?

correct

if you type $profile in the integrated console, you will see it


Show Notification when app manager can not connect to app store

When app store is down for updating or server issues or even cartoview can not connect to app store for connectivity issues , app manager loading forever without result.

https://github.com/cartologic/cartoview/pull/119


SDK integration in ios project with Xcode10.1 and swift4.2

I can't be able to integrate this ios sdk into my ios project. Please provide a detailed steps to integrate this sdk into my ios app

I can't be able to integrate this ios sdk into my ios project. Please provide a detailed steps to integrate this sdk into my ios app

did you find any way to integrate in your project??


Implement tokens and use them internally in the parser.

Added token class.
Also some parsing re-implementation due to changes. We can now parse sentences with extra words after a multi-word noun. I.e. 'take toilet paper from chest'. Not that we can handle the extras yet, but the noun is still extracted correctly.

I'm going to go ahead and give you commit access to the repository
And I will probably start working on this project again soon


e2e: Test e2e libvirt failure

To see if main branch pass test_e2e_libvirt
Fixes: https://github.com/confidential-containers/cloud-api-adaptor/issues/1544

Rebased with latest main branch. Only 2 test cases are failed now.
 === RUN   TestLibvirtCreateSimplePod/SimplePeerPod_test/PodVM_is_created
    assessment_runner_test.go:344: Expected to pull with nydus, but that didn't happen
time="2023-11-08T04:21:41Z" level=info msg="Deleting pod nginx..."
time="2023-11-08T04:22:01Z" level=info msg="Pod nginx has been successfully deleted within 60s"
--- FAIL: TestLibvirtCreateSimplePod (191.05s)
    --- FAIL: TestLibvirtCreateSimplePod/SimplePeerPod_test (191.05s)
        --- FAIL: TestLibvirtCreateSimplePod/SimplePeerPod_test/PodVM_is_created (0.38s)

=== RUN   TestLibvirtCreatePodWithSecret/SecretPeerPod_test/Secret_has_been_created_and_contains_data
    assessment_runner_test.go:318: cat: /etc/secret/username: No such file or directory

    assessment_runner_test.go:319: command terminated with exit code 1

do not need any more


Dropping Pins or Markers on the Map

Is your feature request related to a problem? Please describe.
I track storms for friends and family all over the country.  Currently, I have to cross-reference another map to know where they're at so that I can make accurate predictions based on their location.
Describe the solution you'd like
I'd like the ability to drop pins or markers on the map (similar to GR's "home" and "marker").  A hotkey like Alt+Click could place a pin on the map where the cursor currently is.  Further enhancements could include selecting and measuring from the pin.
Describe alternatives you've considered
N/A
Additional context
N/A

I second this! Also maybe adding a feature that allows you to "save" a default map view in a specific place, rather than a station.

This would be a great feature,  but if you want markers now, placefiles can do it. Bellow is a template I put together for this. {title} is the title that Supercell-WX will display, {path_to_icon} is a path or URL to a 16x16 PNG (noting that using a path does not seem to work on Linux).  {lat*}, {lon*}, and {name*} are a latitude, longitude, and name (tool-tip) respectively for a location. You can get the coordinates by hovering your mouse over a location on Supercell-WX, and hitting CTRL-C. You can add as many locations as you want. Just put this into a .txt file someplace on your computer, and add it to Supercell-WX as a placefile, and you are good.
There is a lot more you could do. Here is the placefile specification, if you want to take a look: https://www.grlevelx.com/manuals/gis/files_places.htm.
Title:          {title}
Threshold:      600
RefreshSeconds: 86400
Color:          255, 255, 255
IconFile:       1, 15, 15, 8, 8, {path_to_icon}
Font:           1, 11, 1, "Arial"

Icon: {lat1}, {lon1}, 0, 1, 1, "{name1}"
Icon: {lat2}, {lon2}, 0, 1, 1, "{name2}"
Icon: {lat3}, {lon3}, 0, 1, 1, "{name3}"

Thank you for suggesting placefiles and providing the template. My only (brief) trouble was discovering how to enable the placefile after I added it (clicking the box in the E column). Now I have pins on my map. I am pleased.


Return Image handle instead of window (EFL)

Nice to meet you devs. I'm studying flutter and have a question, so I'm making a sample and writing my opinion here :)
Currently, AddtoApp of flutter-tizen can be implemented by using a window handle. (ecore_wl2, elm_win)
To add the rendered flutter output to the elementary widget, it was not appropriate to use elm_win.
(I tried using other types of windows, but it didn't work as intended. (ELM_WIN_INLINED_IMAGE type of elm_win))
I made a sample by modifying the evas_gl.cc code to use the evas image handle.
The user can get the image handle after set the parent window or parent widget appropriately. And they can add it somewhere.
Below is a sample of this idea.
If a suitable interface and sample code to add parent are presented, users can expect to output FlutterView(?) in EFL-based apps.
(Of course, this is not a nice interface unless multi-instance (maybe FlutterGroup?) is applied.)
sample)

https://github.com/JSUYA/engine/tree/jsuya/flutter-2.8.1-tizen/dev/evas_image

@JSUYA
First of all, It's very interesting proposal. Actually, we have a plan to do something similar!
Currently, Its priority is little behind for other urgent issue...
Thank you very much for all the suggestions and sample code. 👍

Hi. I'm glad that you finally joined my team and thank you for filing a suggestion! (Maybe this issue is related to https://github.com/flutter-tizen/engine/issues/94.)
According to your approach, should the app always pass its window handle (as a parent window) to the embedder regardless of the app's scenario (add to app or normal)?
If so, we might also be able to reduce the launching time overhead by removing the call to elm_win_add in the embedder and reusing the elm window already created by the app. (You don't have to consider this right now.)

Hi. I'm glad that you finally joined my team and thank you for filing a suggestion!

Thank you :)

(Maybe this issue is related to #94.)

I will check it.

According to your approach, should the app always pass its window handle (as a parent window) to the embedder regardless of the app's scenario (add to app or normal)?

In this case, we need the parent's handle, which will contain the evas_image, not the window handle. (Of course, it can be a window)
elementary almost always needs a parent when creating a widget. (elm_XXX_add(parent))

If so, we might also be able to reduce the launching time overhead by removing the call to elm_win_add in the embedder and reusing the elm window already created by the app. (You don't have to consider this right now.)

Yes, we don't have to create unnecessary windows. The container to contain the evas image is created in the app code.

@JSUYA Thanks for the clarification, but what I meant was: Do you plan to make an app pass an Evas object handle to the embedder even if the app does not use the add to app feature?

@JSUYA Just forget everything I said above..  I glanced at your profile and had no idea who you are. 😢
Welcome! & Look forward to working together soon. 😄

@JSUYA Thanks for the clarification, but what I meant was: Do you plan to make an app pass an Evas object handle to the embedder even if the app does not use the add to app feature?

If the application does not use add to app feature, we do not need to pass the parent object.
Now embedder's FlutterApp Interface is one. But I think that if we provide the interface for single flutter screen(elm_win or ecore_wl2_window), Flutter-View(elm/evas_object, NUI/View(component)), we will be able to solve this problem(?).

related issue https://github.com/flutter-tizen/flutter-tizen/issues/351


Introduce convention class

This PR implements the first step towards using the specified convention to assume the style of docstrings and not rely on figuring out whether a docstring uses NumPy or Google style (#459).
This PR introduces a new class Convention that holds the error codes to check. It also keeps the name of the convention to use. I imagine that an instance of this class should be passed to the ConventionChecker. Convention-specific checks like _check_numpy_sections and _check_google_sections can then be executed based on the specified convention. This would eventually solve #459.
I added tests for the code I added and all existing tests still pass.

Is there any interest in moving this forward?

@adamjstewart / @Pierre-Sassoulas would you like to review this?

On vacation this week but will review next week.

Rebased on top of master and addressed feedback

We should add a test case for #459. All of our tests are passing but #459 is still broken.

I'm actually surprised that this PR fixed #459 for you because it is not supposed to, as outlined in the PR description.  I did not touch anything regarding how docstrings are treated or how checks are executed so there must have been something else going on during your tests. This PR only formalizes the concept of conventions a bit.

Gotcha, yeah I have no idea why things were working before the rebase, maybe because the branch was old? I'm fine with formalizing the concept and then fixing #459 in a separate PR. Thanks for your work on this!


Error: Require an oauthToken or token option

I tried to set up a staticman instance on Heroku, but I'm missing something.
The Heroku instance runs at https://staticman-mr.herokuapp.com/. When I open that url, it says "Hello from Staticman version 3.0.0!".
But when I try to submit a comment from my blog, then I get this in the Heroku log:
2021-03-01T17:34:37.714485+00:00 app[web.1]: /app/lib/GitHub.js:33
2021-03-01T17:34:37.714497+00:00 app[web.1]:         throw new Error('Require an oauthToken or token option')
2021-03-01T17:34:37.714498+00:00 app[web.1]:               ^
2021-03-01T17:34:37.714499+00:00 app[web.1]:
2021-03-01T17:34:37.714499+00:00 app[web.1]: Error: Require an oauthToken or token option
2021-03-01T17:34:37.714500+00:00 app[web.1]:     at /app/lib/GitHub.js:33:15
2021-03-01T17:34:37.714500+00:00 app[web.1]:     at new GitHub (/app/lib/GitHub.js:46:7)
2021-03-01T17:34:37.714501+00:00 app[web.1]:     at Object.module.exports.create (/app/lib/GitServiceFactory.js:11:14)
2021-03-01T17:34:37.714501+00:00 app[web.1]:     at /app/lib/Staticman.js:32:35
2021-03-01T17:34:37.714501+00:00 app[web.1]:     at new Staticman (/app/lib/Staticman.js:46:7)
2021-03-01T17:34:37.714502+00:00 app[web.1]:     at module.exports (/app/controllers/process.js:126:27)
2021-03-01T17:34:37.714503+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-01T17:34:37.714503+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-01T17:34:37.714504+00:00 app[web.1]:     at /app/server.js:169:14
2021-03-01T17:34:37.714504+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-01T17:34:37.714504+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-01T17:34:37.714505+00:00 app[web.1]:     at /app/server.js:144:14
2021-03-01T17:34:37.714505+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-01T17:34:37.714506+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-01T17:34:37.714506+00:00 app[web.1]:     at /app/server.js:129:14
2021-03-01T17:34:37.714506+00:00 app[web.1]:     at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-01T17:34:37.714507+00:00 app[web.1]:     at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-01T17:34:37.714507+00:00 app[web.1]:     at module.exports. (/app/node_modules/express-brute/index.js:142:36)
2021-03-01T17:34:37.714508+00:00 app[web.1]:     at module.exports.MemoryStore.set (/app/node_modules/express-brute/lib/MemoryStore.js:28:35)
2021-03-01T17:34:37.714508+00:00 app[web.1]:     at module.exports. (/app/node_modules/express-brute/index.js:127:17)
2021-03-01T17:34:37.714508+00:00 app[web.1]:     at module.exports.MemoryStore.get (/app/node_modules/express-brute/lib/MemoryStore.js:38:35)
2021-03-01T17:34:37.714509+00:00 app[web.1]:     at module.exports. (/app/node_modules/express-brute/index.js:82:15)
2021-03-01T17:34:37.732294+00:00 app[web.1]: npm ERR! code 1
2021-03-01T17:34:37.732902+00:00 app[web.1]: npm ERR! path /app
2021-03-01T17:34:37.739796+00:00 app[web.1]: npm ERR! command failed
2021-03-01T17:34:37.740081+00:00 app[web.1]: npm ERR! command sh -c node index.js
2021-03-01T17:34:37.754082+00:00 app[web.1]:
2021-03-01T17:34:37.754401+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-01T17:34:37.754634+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2021-03-01T17_34_37_741Z-debug.log
2021-03-01T17:34:37.722918+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/v3/entry/github/MichaelRumpler/MichaelRumpler.github.io/master/comments" host=staticman-mr.herokuapp.com request_id=bc3aad82-ac22-434d-90f6-83a855d3fa4c fwd="<IP_ADDRESS>" dyno=web.1 connect=0ms service=45ms status=503 bytes=0 protocol=https
2021-03-01T17:34:37.822591+00:00 heroku[web.1]: Process exited with status 1
2021-03-01T17:34:37.910338+00:00 heroku[web.1]: State changed from up to crashed
I did set the Heroku config variables GITHUB_TOKEN and RSA_PRIVATE_KEY. From the error message I assume that it doesn't find the GITHUB_TOKEN.
When I go to github.com/settings/tokens of my Staticman App user, I see that the Personal Access Token was never used.

I found this blog post and issues #319 and #332.
So it appears that v3 was never fixed to work with a githubToken. Thus I changed my API endpoint to v2. Be sure to remove the "github" part from the endpoint when changing from v3 to v2. This seems to work.
I leave this issue open because

v3 doesn't work with GITHUB_TOKEN (and apparently nobody could get it to work with oAuth)
the docs does not state that

Essentially a dupe of eduardoboucas/staticman.net#15.  The response to my linked issue says that a PR for backward compatibility with GitHub bot in v3 is pending.

Not quite. eduardoboucas/staticman.net#15 is about the connect route. This is about entry.
I accepted the invitation via the GitHub web page. So I didn't run into the problem you mentioned.
But thanks for pointing out that repo for the docs. I didn't see that earlier.

Not quite. eduardoboucas/staticman.net#15 is about the connect route. This is about entry.

Oops my bad, but from the linked issue, we see that there's a PR #405 that's suppose to support the legacy authorization method, even though a GitHub App is preferred.

I tried again to use v3.
I created a GitHub App and then added the vars GITHUB_APP_ID (a 6 digit number) and GITHUB_PRIVATE_KEY to the Config Vars in Heroku (and removed GITHUB_TOKEN).
But it still doesn't work and I get this error in the Heroku log:
2021-03-03T17:15:41.005688+00:00 app[web.1]: node:internal/crypto/sig:124
2021-03-03T17:15:41.005702+00:00 app[web.1]: const ret = this[kHandle].sign(data, format, type, passphrase, rsaPadding,
2021-03-03T17:15:41.005702+00:00 app[web.1]: ^
2021-03-03T17:15:41.005703+00:00 app[web.1]:
2021-03-03T17:15:41.005704+00:00 app[web.1]: Error: error:0909006C:PEM routines:get_name:no start line
2021-03-03T17:15:41.005704+00:00 app[web.1]: at Sign.sign (node:internal/crypto/sig:124:29)
2021-03-03T17:15:41.005704+00:00 app[web.1]: at Object.sign (/app/node_modules/jwa/index.js:152:45)
2021-03-03T17:15:41.005705+00:00 app[web.1]: at Object.jwsSign [as sign] (/app/node_modules/jws/lib/sign-stream.js:32:24)
2021-03-03T17:15:41.005705+00:00 app[web.1]: at Object.module.exports [as sign] (/app/node_modules/jsonwebtoken/sign.js:204:16)
2021-03-03T17:15:41.005706+00:00 app[web.1]: at getSignedJsonWebToken (/app/node_modules/@octokit/app/dist-node/index.js:31:30)
2021-03-03T17:15:41.005706+00:00 app[web.1]: at GitHub._authenticate (/app/lib/GitHub.js:58:21)
2021-03-03T17:15:41.005707+00:00 app[web.1]: at /app/lib/GitHub.js:31:32
2021-03-03T17:15:41.005707+00:00 app[web.1]: at new GitHub (/app/lib/GitHub.js:46:7)
2021-03-03T17:15:41.005708+00:00 app[web.1]: at Object.module.exports.create (/app/lib/GitServiceFactory.js:11:14)
2021-03-03T17:15:41.005708+00:00 app[web.1]: at /app/lib/Staticman.js:32:35
2021-03-03T17:15:41.005709+00:00 app[web.1]: at new Staticman (/app/lib/Staticman.js:46:7)
2021-03-03T17:15:41.005709+00:00 app[web.1]: at module.exports (/app/controllers/process.js:126:27)
2021-03-03T17:15:41.005710+00:00 app[web.1]: at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-03T17:15:41.005710+00:00 app[web.1]: at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-03T17:15:41.005710+00:00 app[web.1]: at /app/server.js:169:14
2021-03-03T17:15:41.005711+00:00 app[web.1]: at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-03T17:15:41.005711+00:00 app[web.1]: at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-03T17:15:41.005712+00:00 app[web.1]: at /app/server.js:129:14
2021-03-03T17:15:41.005712+00:00 app[web.1]: at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2021-03-03T17:15:41.005712+00:00 app[web.1]: at next (/app/node_modules/express/lib/router/route.js:137:13)
2021-03-03T17:15:41.005713+00:00 app[web.1]: at module.exports.<anonymous> (/app/node_modules/express-brute/index.js:142:36)
2021-03-03T17:15:41.005713+00:00 app[web.1]: at module.exports.MemoryStore.set (/app/node_modules/express-brute/lib/MemoryStore.js:28:35) {
2021-03-03T17:15:41.005714+00:00 app[web.1]: library: 'PEM routines',
2021-03-03T17:15:41.005714+00:00 app[web.1]: function: 'get_name',
2021-03-03T17:15:41.005714+00:00 app[web.1]: reason: 'no start line',
2021-03-03T17:15:41.005715+00:00 app[web.1]: code: 'ERR_OSSL_PEM_NO_START_LINE'
2021-03-03T17:15:41.005715+00:00 app[web.1]: }
2021-03-03T17:15:41.011535+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/v2/entry/MichaelRumpler/MichaelRumpler.github.io/master/comments" host=staticman-mr.herokuapp.com request_id=942f9973-31e4-4a27-afab-37bd846dbaab fwd="<IP_ADDRESS>" dyno=web.1 connect=0ms service=42ms status=503 bytes=0 protocol=https

This is exactly the error @hajekj mentioned in his blog. He wrote that you have to add \n before and after the key. I didn't do that in the RSA_PRIVATE_KEY and that one seems to work, but I tried here and still get the same error.
I copied both the RSA_PRIVATE_KEY and the GITHUB_PRIVATE_KEY to a text file and when I had them side by side, I saw that the length of the keys differ. Is that normal? I created the RSA key on Windows with ssh-keygen and the GitHub key was downloaded as .pem file when I created it on the GitHub App page.
GITHUB_PRIVATE_KEY      -----BEGIN RSA PRIVATE KEY-----MIIEpAIBAAKCA.....WEVEFw==-----END RSA PRIVATE KEY-----
RSA_PRIVATE_KEY         -----BEGIN RSA PRIVATE KEY-----MIIEowIBAAKCA.....lW30-----END RSA PRIVATE KEY-----

This is exactly the error @hajekj mentioned in his blog. He wrote that you have to add \n before and after the key. I didn't do that in the RSA_PRIVATE_KEY and that one seems to work, but I tried here and still get the same error

I tried his advice too, but with no success.  Finally I didn't escape the newline, as illustrated in my post in the discussion, and everything works fine.  GITHUB_PRIVATE_KEY is for GitHub App; GITHUB_TOKEN is for the bot.  You only need to choose one of them.  I've switched to the former for a month.

I tried that too.
When I specify the key in multiple lines (copied the .pem file as is), then I got
2021-03-03T15:35:00.270122+00:00 app[web.1]: /app/node_modules/@octokit/request/dist-node/index.js:66
2021-03-03T15:35:00.270180+00:00 app[web.1]: const error = new requestError.RequestError(message, status, {
2021-03-03T15:35:00.270182+00:00 app[web.1]: ^
2021-03-03T15:35:00.270182+00:00 app[web.1]:
2021-03-03T15:35:00.270183+00:00 app[web.1]: RequestError [HttpError]: Not Found
2021-03-03T15:35:00.270183+00:00 app[web.1]: at /app/node_modules/@octokit/request/dist-node/index.js:66:23
2021-03-03T15:35:00.270184+00:00 app[web.1]: at processTicksAndRejections (node:internal/process/task_queues:94:5)
2021-03-03T15:35:00.270185+00:00 app[web.1]: at async GitHub._authenticate (/app/lib/GitHub.js:60:20)
2021-03-03T15:35:00.270185+00:00 app[web.1]: at async /app/lib/GitHub.js:31:21
2021-03-03T15:35:00.270185+00:00 app[web.1]: at async /app/lib/Staticman.js:32:18
2021-03-03T15:35:00.270186+00:00 app[web.1]: at async module.exports (/app/controllers/process.js:126:21) {
2021-03-03T15:35:00.270186+00:00 app[web.1]: status: 404,
2021-03-03T15:35:00.270187+00:00 app[web.1]: headers: {
2021-03-03T15:35:00.270187+00:00 app[web.1]: 'access-control-allow-origin': '*',
2021-03-03T15:35:00.270188+00:00 app[web.1]: 'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset',
2021-03-03T15:35:00.270189+00:00 app[web.1]: connection: 'close',
2021-03-03T15:35:00.270189+00:00 app[web.1]: 'content-encoding': 'gzip',
2021-03-03T15:35:00.270189+00:00 app[web.1]: 'content-security-policy': "default-src 'none'",
2021-03-03T15:35:00.270190+00:00 app[web.1]: 'content-type': 'application/json; charset=utf-8',
2021-03-03T15:35:00.270191+00:00 app[web.1]: date: 'Wed, 03 Mar 2021 15:35:00 GMT',
2021-03-03T15:35:00.270191+00:00 app[web.1]: 'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
2021-03-03T15:35:00.270192+00:00 app[web.1]: server: 'GitHub.com',
2021-03-03T15:35:00.270192+00:00 app[web.1]: 'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
2021-03-03T15:35:00.270193+00:00 app[web.1]: 'transfer-encoding': 'chunked',
2021-03-03T15:35:00.270193+00:00 app[web.1]: vary: 'Accept-Encoding, Accept, X-Requested-With',
2021-03-03T15:35:00.270194+00:00 app[web.1]: 'x-content-type-options': 'nosniff',
2021-03-03T15:35:00.270194+00:00 app[web.1]: 'x-frame-options': 'deny',
2021-03-03T15:35:00.270194+00:00 app[web.1]: 'x-github-media-type': 'github.v3; param=machine-man-preview; format=json',
2021-03-03T15:35:00.270195+00:00 app[web.1]: 'x-github-request-id': '960E:FF96:29CEF1:2C1610:603FACA4',
2021-03-03T15:35:00.270195+00:00 app[web.1]: 'x-xss-protection': '1; mode=block'
2021-03-03T15:35:00.270195+00:00 app[web.1]: },
2021-03-03T15:35:00.270196+00:00 app[web.1]: request: {
2021-03-03T15:35:00.270196+00:00 app[web.1]: method: 'GET',
2021-03-03T15:35:00.270196+00:00 app[web.1]: url: 'https://api.github.com/repos/MichaelRumpler/MichaelRumpler.github.io/installation',
2021-03-03T15:35:00.270197+00:00 app[web.1]: headers: {
2021-03-03T15:35:00.270197+00:00 app[web.1]: accept: 'application/vnd.github.machine-man-preview+json',
2021-03-03T15:35:00.270198+00:00 app[web.1]: 'user-agent': 'octokit-request.js/5.3.1 Node.js/15.10.0 (Linux 4.4; x64)',
2021-03-03T15:35:00.270198+00:00 app[web.1]: authorization: 'Bearer [REDACTED]'
2021-03-03T15:35:00.270198+00:00 app[web.1]: }
2021-03-03T15:35:00.270199+00:00 app[web.1]: },
2021-03-03T15:35:00.270199+00:00 app[web.1]: documentation_url: 'https://docs.github.com/rest/reference/apps#get-a-repository-installation-for-the-authenticated-app'
2021-03-03T15:35:00.270199+00:00 app[web.1]: }

@MichaelRumpler Note that the error ERR_OSSL_PEM_NO_START_LINE is gone, and you're no longer getting Connection closed without response.  You're getting status: 404, which is the server's response.  That indicates that you're correctly set up the *_KEY.
If you follow the documentation_url, the code 404 is related to Resource not found.  You're using the app at the latest commit?  You're installed your app to the GitHub repo for your site?  It seems to be a permissions error:
hashicorp/terraform-provider-tfe#164

I finally figured it out! I created the app, but forgot to install it.
That must be done after the GitHub app was created in the menu Install App. The permissions should already be set before when you created it. You should then be able to see the app in your repositories settings in Integrations.
And Yes, the GITHUB_PRIVATE_KEY must have newlines in Heroku. @hajekj deployed it to Azure, probably this recognizes \n and replaces it with newlines.
I'll close this issue and probably add a PR for the docs at staticman.net.
Thanks for all your help @VincentTam !!

I'll close this issue and probably add a PR for the docs at staticman.net.

That's already in step 1 option 1 #3 in the quick start guide:

Install the app on your GitHub account. You can limit its access to only the repo from which you host your static site

I had been hitting the same errors, so his was helpful. Thanks. To potentially add/clarify:
When using the v3 + Github App + heroku method, I only got it to work when:

In heroku config var, the GITHUB_PRIVATE_KEY had new lines (but not \n)
In heroku config var, the RSA_PRIVATE_KEY does not have any new lines.

Strange that it is inconsistent. But, I tried every combo, and this is the only one that works.
I think the official quick start guide is great, but I think this one line could be fleshed out: If you need the newline literals (for example when using JSON configs since multiline strings are not permitted). I genuinely didn't know if I needed newline literals. And the ultimate answer was that I didn't, but at the same time I needed new lines on one of the keys.

@RyanTG Thank you very much for your reply. This is the only thing that worked for me! Now I gotta fix my template.


Update log4j to 2.17.1 to address CVE-2021-44832.

https://nvd.nist.gov/vuln/detail/CVE-2021-44832

The changes in this PR were already merged, thanks for your interest anyways!


Unnecessary recalculation of state

I use react-sticky along with ReactCSSTransitionGroup for some animations (these animations not inside a sticky element). I noticed the following issue: when I use ReactCSSTransitionGroup on the same page with react-sticky transitions act weird and skip entering animation for elements. I checked the code and found that for every change of properties there is a recalculation for the whole state:
componentWillReceiveProps() {
    this.recomputeState();
  }

I tried to remove these function and all transitions work fine. Probably, because of page reflow (recalculation triggers reflow because it reads properties directly from DOM node).
Is it possible to get rid of these recalculations for each property? Or at least check particular properties? What do you think?

+1 to this. I noticed that this library causes significant slowdowns on pages with much complexity. You see that almost everything in the screen gets rerenders triggered on them, to the point that running this in IE10 on a high-end laptop causes scrolling to get choppy; and using Chrome's experimental CPU throttling replicates the same behavior.
Ideally the only time state should actually change (or shouldComponentUpdate return true) is when there is actually a visual change that needs to occur (i.e. right when sticky state changes).

With react-sticky, redraws everywhere (the stutters in the gif are due to poor performance, not GIF recording):

With same code, except not using react-sticky but instead a custom implementation that only calls setState on sticky state change:

Agreed. On small page it's very laggy.

I totally forgot about this issue, but I'm using a slightly modified version of this package in my project. The only fix, that I made - removed componentWillReceiveProps at all. And performance went back to normal. https://github.com/paraboom/react-sticky/commit/0be78ccb0094af3fda16580678f0b85ddd06b2b8

@osdiab
This is a little bit off-topic, but I want to know how do you generate the gif?
Are you using some chrome extension?
It is very useful to figure out which component has redrawn.

@199911 try https://www.getcloudapp.com/

@dbarbalato btw, I noticed that you removed componentWillReceiveProps from the code, so performance is good right now. I guess, we can close that issue?

@paraboom
Thanks!
I also want to know how the red rectangle in the gif generated.

@199911 https://developer.chrome.com/devtools/docs/rendering-settings

I think this is regarding an old version of the library? I did some poking with the current version, and it doesn't appear to rerender children excessively. It rerenders itself frequently, but since the props don't change React doesn't render the tree. Going to close this in a few days unless somebody can confirm it's still a problem with version 6


Inspector Does Not Set Exported Variables Sometimes

Godot version:
3.1 alpha 2
OS/device including version:
Arch Linux with i3wm, AMD processor, and nVidia graphics
Issue description:
Setting script variables (the stuff from GDscript export commands) with the GUI is often unreliable (often will not work at all, sometimes it works perfectly). Sometimes fiddling around (e.g. messing with what it is initialized to) will help, sometimes not. Often, if the variable has not been set before, there will be a null de-reference error. There appears to be no pattern with what kind of variables have problems. This did not happen with the 3.0 release.
Steps to reproduce:
Make a script that exports a variable. Set the variable with the inspector. Run.
Minimal reproduction project:
I'll get one ready later today.

Would be great to have that reproduction project and more precise reproduction steps if possible


Create Testimonial 10 white

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

Follow figma design and to make the button use Button Design System
After building the component please raise a PR with a screenshot of the component and add the component in Testimonials/src/testimonial-10-white.html & Please do not add hover effect in the main div
If you need to use any icon please use it from Hero Icons
Good luck.

I would like to work on this issue

Please assign this issue to me


Fix duplicate CI runs for both push and pull_request events

Disable CI runs for push event on any branch except master and v*-branch. This means if we want CI runs on branches not from a fork of connectedhomeip, we will need to make pull requests.

@vatsalghelani-csa the previous run said "EFR32" did not run. I updated to master to kick CI to see if this is a real issue or not...


Fix typo in development-time-iis-support.md

The sentence:

... a binding to post 80...

Should read

... a binding to port 80...

@ericmutta  thanks again for your support improving the docs. Keep the PRs coming.

Hi @Rick-Anderson it's been a while, many thanks for following up on the PRs, I'll keep 'em coming :+1:


fix: update Gemfile and valgrant files incorrect definitions

Fixes #510
Updated the definitions of the gemfile and vagrantfile by removing the unused $ sign.
Before fix

After fix

Are really the $ not needed?

They seems to be the issue in matching the files. I also tested by modifying these for my existing config under ~/local/share directory.


Document Secrets Management Options

Need to add additional context for customers with more advanced secrets management requirements.
e.g:

high level diagram of integration /w vault providers
instructions for things that need to change in compose / config files
links to relevent providers

Closed by #37


Add support for * as a markup character and \ for escaping characters

Asterisk support was added in https://github.com/prolificinteractive/Marker/commit/9355362a6b5a93d168bf76cdc721ada03d0ecd53. Closing this and moving escape character support into a separate issue.


Add files via upload

I am a third-year physics and math student at Georgetown University.

@eda1toprak I am sorry, the domain georgetown.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Pack at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Any way to get full resolution?

When I upload an image to be colored, the colored image is always 912 x 512. Is there anyway to get the colored image in the original resolution?

To do that, you would need to download the program and run it locally. Setting it up take a fair share of time, and you need an NVIDIA graphics card that supports CUDA

I did just that. I think I did set it up right. How do I save the large version of processed images if I run the local server?

I haven't figured a way to make it the original size, but I've come very close.
What I did was to:

change the s_size param under "def colorize(self, id_str, step='C', blur=0, s_size=128,colorize_format="jpg"):" at cgi_exe.py to 256
change the s_size param under "def get_example(self, i, minimize=False, blur=0, s_size=128):" at img2imgDataset.py to 256
Not sure if step 1 is necesarry, but Taizan, the dev, was the one to tell me about step 2.
After this, you can just import your picture like normal, right-click the coloured outcome and save it anywhere. The resolution should be higher now. If you want higher res. you can change the s_size param to 512, but I think that'll make it too big as well as funky-looking.

I made the changes to the files and now the processed images are up scaled instead of down scaled. I suppose that is an improvement. Thanks.

Smaller side of the output is 4times of size_s val.
size_s should be multiple of 16

Is it related to #77 ?

Yes.

to enlarge the file, simply input s_size(multiples of 16) in the colorize function and it will propagate to get_example.
"full resolution" is not preferred at this moment because the resolution is bounded by chainer.functions.Convolution2D which forward the array to CUDA cores through chainer
you may not even want to try to turn off gpu mode and passing convolutions to cpu in order to break through the memory boundary, because it can only be on one thread and run literally some days to finish for a bit large s_size.
256 is the max s_size you can have in most cases.

So it's not possible, got it.

we still have waifu2x anywayz ... wwww

I have this installed locally on docker toolbox and kitematic. Is there a way to change the image size on that?

@JamScoBal change s_size from 128 to 256 and you can get a 4x resolution output.

@abbychau By that do you mean going to the settings in Kitematic and adding the "s_size" under the Generals tab and putting in the value of 256?

@abbychau I did that and nothing seems to be changing.

change
painter.colorize(id_str, form["step"][0].decode() if "step" in form else "C", blur=blur) in server.py
to
painter.colorize(id_str, form["step"][0].decode() if "step" in form else "C", blur=blur, s_size=256)

How do I get to server.py in docker and/or kitematic? I am on Windows in case you were wondering.

edit it manually after deployment

Sorry, but I don't understand what you mean. I am a total noob when it comes to this stuff. You will have to put it in layman's terms for me. If you can do step by step instructions that would be great.

Actually we are not supporting the docker version, if you meet further issues by using it, I don't think the issues will be accepted here.
although in this case you just want to edit files in a docker container, it can be basic but tedious to tell these linux(or ssh, in another way to access the files) commands and operations.
Please try to follow:
start the docker

in another bash:

run
apt-get update
apt-get install vim

run vim server.py
go to this line

press d d , the line will disappear
press i
copy painter.colorize(id_str, form["step"][0].decode() if "step" in form else "C", blur=blur, s_size=256)
right click in the shell, and make sure that there are two tabs in front of the line
press esc
press :wq
press enter
go back to the first bash shell and restart the server
(glance https://www.tutorialspoint.com/unix/unix-vi-editor.htm for some basic operations of vi, which is a shell based text editor)

@JamScoBal I maintain the Docker version, I'll see about adding a configuration property for this so you don't have to edit the file inside the container directly. I've logged a ticket for it here: https://github.com/liamjones/PaintsChainer-Docker/issues/3

@JamScoBal I've updated the docker image to allow you to change s_size easily. If you re-pull the 'latest' tag (or pull 'release-1.0.7' specifically) you'll find a new environment variable called PAINTSCHAINER_S_SIZE. Remember it needs to be set to a multiple of 16 to work (128 is the default).

@liamjones Thanks so much!!!!


Adopt more ObsCore Standards for column names?

ObsCore Data Model 1.1 prescribes column names. Maybe we should consider adopting some of these, especially as we're thinking of the template database?  @dr-rodriguez , thoughts?  See Appendix B (p. 40-53) of REC-ObsCore-v1.1-20170509.pdf. (Is this indeed the latest?)
Relevant column names

access_url instead of spectrum and add access_format
target_name instead of source
s_ra and s_dec instead of ra and dec
bib_reference instead of bibcode
add o_calib_status to the spectra table to indicate normalized spectra.

Some quick thoughts:

The ObsCore columns are ONLY needed for an ObsCore table/view; they don't need to be adopted elsewhere. We're not really offering our database through VO protocols, so while these are good, we don't have to adhere to them if it doesn't make sense for us or adds too much overhead. Just as a note, at MAST we have a view that renames columns to the ObsCore standard just for that view, rather than changing the tables themselves.
spectrum is used by astrodbkit to specify which is the column to use for transforming to a Spectrum1D object. It's not too difficult to change or supply new ones, though (see https://github.com/dr-rodriguez/AstrodbKit2/blob/main/astrodbkit2/astrodb.py#L111)
The defaults for astrodbkit2 is to have source be the primary and foreign key; see https://github.com/dr-rodriguez/AstrodbKit2/blob/main/astrodbkit2/init.py I would like to keep those as that is short and more generic than target_name. You can always use a different one, but will need to supply it when you instantiate the Database class.
I don't think the extra s_ for ra/dec really add anything
For bib_reference, does that means the Publications table will have reference and bib_reference?
I don't think we need to add access_format or o_calib_status

I want us to build something that is as interoperable from the start with other relevant tools. And while we don't plan to integrate with other databases, I want it to be super easy for folks to "merge" two different databases made with astrodbtoolkit, which I think is the same goal as ObsCor, isn't it?
I also feel like some people have put a LOT of thought into these column names and why not take advantage of that work if it's "easy" for us to implement?
If there's one field I would be in favor of adding, it would be calib_status for spectra. Right now, there's no good way to indicate if a spectrum is flux calibrated or normalized. And we have a mix.

While I understand that it might require some changes to astrodbkit, using Spectra.c.access_url instead of Spectra.c.spectrum makes good sense to me. We aren't actually providing the spectrum, we're giving a URL. (This would also extend to any similar tables, like Images.)
And yeah, if we adopted bib_reference for the ADS Bibcode, we would indeed have reference as our shortname and also a bib_reference.  I feel meh about this.

Remember that ObsCore is a model to describe observations and data products- our database is primarily for targets, not observations. We do have some data products (Spectra) but again, this is where views come into play since that is the logical place to rename columns after you join underlying tables. Rather than making sweeping database column changes, I would rather effort be spent on working out how to encode views.
That being said, the change for access_url is trivial and I have no problem with it. In fact, the way it's set up you can pass a list of columns so both spectrum and access_url can still be supported. If you wanted to add calib_status (and access_format) that's also not a problem, but note that calib_status is optional in the ObsCore and there are 3 or 4 versions of it.
Our cone search logic (see https://github.com/dr-rodriguez/AstrodbKit2/blob/main/astrodbkit2/astrodb.py#L600) uses ra/dec by default, so changing it to s_ra/s_dec would require users to manually set that. Again- the code supports users specifying custom columns but I think ra is far more common than s_ra. Plus, note that s_ra is meant to be the center of the observation, not necessarily the target location (frequently, but not always, the same).

Huh, I think it's super interesting that you think SIMPLE is primarily about targets and not data products and observations. I absolutely think it's about data and observations...organizing the data is one of my primary motivations and observation planning is an important use case. This might be worth discussing more and making sure we have a coherent description for us and for our users.
So basically what you're saying is that we can always add an ObsCore layer on top. Which is reassuring.
What do you think about the ObsCore names for instrument and facility? Which I want to change anyway? (See issue # - will add when not mobile.)

I think facility_name and instrument_name are fine to change. Is the change just for the Telescopes and Instruments table as you describe in #207? Or are you thinking every time an instrument is mentioned? I'll note that there is no need for foreign keys to match the same name as the column they refer to so we have some options as to how much we change.

After lots of discussion, the only thing I think I only want to change spectrum to access_url in the Spectrum table.
(This change will impact astrodbkit2 - related issue dr-rodriguez/AstrodbKit2#57)


[sca] Prepare SHA3 for pen. tests

Currently, the SCA code for SHA3 uses features to improve SCA that are only available on the FPGA but not on the discrete chip.
This PR, similar to #20772, changes the sha3_sca code such that the code supports measurements on the FPGA and on the chip.
I've made the following experiments:
fpga_mode=true and masks_off=true:

fpga_mode=off (new mode in this PR) and masks_off=true:

As expected, the SCA relevant part is delayed and more noisy but we still can measure leakage. Note that I had to set kIbexLoadHashMessageSleepCycles = 500 to get first order leakage.

Yes, I've conducted these tests on the regular bitstream and not on the one you provided me. The reason for that is that I wanted to be able to compare the power traces when running fpga_mode = false and fpga_mode = true. Running fpga_mode = false on the regular bitstream should be quite similar (minus the extended time period before SHA3 becomes active)?
Running fpga_mode = false on the bitstream you have provided me gives me:


Reflected definitions mismatch the type of method

Opened at Codeplex by toyvo
We have dealt with it in WebSharper in ad-hoc ways but it seems that it comes back to bite us periodically. Would be really much better to fix this in the F# compiler.
Problem:
Type functions (Polymorphic forall 'T.. module-bound properties) get compiled to methods. Quotations using these functions are compiled to method calls. However, reflected definitions of these methods are different from normal methods.
I do not know of a cheap consistent way to detect when this happens, so as to fixup the quotation to the "normal" form expected for a method. Thanks.
DotNetFiddle with repro:  https://dotnetfiddle.net/T2Dgwk
GitHub issue:  https://github.com/fsharp/fsharp/issues/321

comments
toyvo wrote Jul 16, 2014 at 8:15 AM [x]
As discussed with Don Syme, the simplest fix is to simply have the F# compiler mark type functions with some attribute (SourceConstructFlags, or dedicated attribute).

 let empty<'T> = Seq<'T>

 ==>

 [<TypeFunction>]
 static member Empty<'T>() : seq<'T>

This would allow systems like WebSharper to distinguish this case and recover a proper quotation form.

I will close this as by design and we will leave things as they are. I believe WebSharper has worked around the cases where this happens.


Default image type changes based on available types

I'd prefer if there's a specific default image type in the "Create Image" dialog.
Right now, it chooses the first one in the list that lorax-composer returns. This means it changes when that list changes. That's admittedly not very often, but confused me just now :)

Did you have a suggestion in mind? Any objection to having the default option being "Select one" and require the user to choose an option?