clang-tidy fixes

ran through several clang-tidy fixes.
I tried to keep C++98 compatibility. Locally, it builds fine with -DCMAKE_CXX_STANDARD=98
edit: also, every commit was ran with git clang-format.

See https://github.com/splinter-build/splinter for a set of patches that overlap with these. Though the intention and direction of that fork is very different than the PR, some of the same parts of the code are changed in the same way as this PR.

All of my changes are clang-tidy cleanups, most automated. I can cleanup the code in separate commits if desired.
As far as that fork is concerned, is that going to be merged here? This uses C++98 AFAIK (no idea why).

I like https://github.com/splinter-build/splinter/commit/89d25314b54b9427686adbc2f232d8f908038cf5
clang-tidy warns against this as well.

I like splinter-build@89d2531
clang-tidy warns against this as well.

Part one of the commit you referenced is submitted as a PR to ninja here: https://github.com/ninja-build/ninja/pull/1614

That's unfortunate. This PR despite being smaller, might suffer the same fate.

It's almost certainly what will happen, yes. Sorry.
There are three maintainers for the Ninja project. Of them, only one has been active for many years but is not able to keep up with the influx of pull requests.

As far as that fork is concerned, is that going to be merged here? This uses C++98 AFAIK (no idea why).

I missed this question before. Sorry.
It's my intention that every one of the commits that are currently in the Splinter-Build repository will be merged into the Ninja repository. Assuming that Ninja's maintainers are willing to merge them.
I have made no architectural changes. The Splinter project is intended to be a place for C++ language feature enhancements to the Ninja codebase.
There is some recent discussion in one of the Splinter issues about working on some architectural / feature divergence. But if that's done, it would be handled such that the language-feature enhancement commits are kept separate from the feature changes to make upstreaming easier.

This uses C++98 AFAIK (no idea why).

See here for discussion about that: https://github.com/ninja-build/ninja/issues/1403

That's also unfortunate.
On the bright side, CentOS 6 is EOL on November 30, 2020. CentOS 7 supports C++11 just fine.
https://github.com/ninja-build/ninja/issues/1403#issuecomment-378789918
is hilarious. Some of those cast changes that you pointed to are actual bugs and can prevent the compiler from properly optimizing the code. Especially in for loops.

Looks good, but it will result in lots of conflicts with all the other PRs. Maybe we can tackle this one warning at a time?
Also have a look at #1768 where I introduce a .clang-tidy config and let CI check it.

So split up each commit as a separate PR?

Yes. And please expect that some of those PRs will be opened for quite a long time. There's no one paid to work on Ninja (Google even still uses v1.8.2 for Chromium and doesn't care that much about master) and changes like these do result in merge conflicts, ergo more work. There are lot of PRs for features people have been waiting YEARS to get merged. The milestones can give you an idea of which things are next on the priority list.

Placed the small commits in separate PRs.

Thanks, I'll close this one than.

Well, the big ones are still here. I guess I'll keep them local.

Ups, sorry!

:). I’ll send at a later time.


Adds missing test for positive behaviour on Speakers#getTalk.

Missed writing a test for the new method on Speakers to get a specific talk. Added here.

Thanks @mdwheele


Ok

Ok

Need help fixing cache in iOS systems to make things faster and run more smoothly your program is nice but with the help of me you and other  like minded individuals we could make something big where the whole world will notice when we finish fixing the cache problem in every system from the earliest versions on every iOS systems right from the beginning of time


Trigger Condition/Priority do not evaluate against the generator

Version
4.9.3
Describe the bug
When evaluating triggers condition and priority go directly against adaptive expressions rather than through the generator.  This means they cannot use functions defined in the generator templates to simplify condition/priority.  The same issue may be found other places.
[bug]

@tomlm says he worked through this with you offline.


Make a node without popup menu

Hi. Is it possible to make a node in a different way than using a popup menu, for example by an outside menu. If it is possible I want to now what a function/functions should be called to make a node.

Hi!
https://github.com/Ni55aN/d3-node-editor/issues/38

Thank you! I should have studied the history of the issues. Sorry :-)


feat: upgrade to JSDOM 19

Resolves #12023
Summary
Bumps JSDOM to 19. See #12023 for details.
As this is a breaking change this should go into Jest 28, not before.
Test plan
Green CI?

Node 10 failures are expected as JSDOM dropped support for it (and 15) because they are EOL.
Won't be a factor as Jest 28 will also drop Node 10/15 support anyway, see https://github.com/facebook/jest/pull/12220

Hi @SimenB no problem! I rebased it and resolved all conflicts, should pass now.

Codecov Report

Merging #12290 (5693212) into main (a651b65) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #12290   +/-   ##
=======================================
  Coverage   66.94%   66.94%
=======================================
  Files         329      329
  Lines       17345    17345
  Branches     5059     5059
=======================================
  Hits        11612    11612
  Misses       5701     5701
  Partials       32       32

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 a651b65...5693212. Read the comment docs.


Local API support

Introduce support for the Risco local API (no reliance on cloud).
The APIs are somewhat similar, but are not identical. A few differences:

The cloud version uses zero-based indexes for partitions and zones, while the local one is one-based.
The local version does not currently support events.
The local version lets you register for immediate status updates.
The cloud version is stateless - a new Alarm object is returned on every call. The local version keeps the zone and partition objects up to date.
The local version doesn't have support for bypassing or unbypassing a zone, just a toggle. A race condition with two simultaneous calls to bypass can leave the zone not bypassed, for example.

@vanackej would love to get your input here, thanks!

This fixes #6


[FEATURE] Client send sparkConf through registerApplicationInfo rpc to Coordinator

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
We can let client send sparkConf to coordinator to show more context information about this application.
Motivation
Insight and know what application are running and being served by RSS cluster.
Describe the solution

Create a util method like this.

  public static Map<String, String> sparkConfToMap(SparkConf sparkConf) {
    Map<String, String> map = new HashMap<>();
    Tuple2<String, String>[] scalaMap = sparkConf.getAll();

    java.util.Iterator<Tuple2<String, String>> it =
        Arrays.stream(scalaMap).iterator();
    while (it.hasNext()) {
      Tuple2<String, String> tuple = it.next();
      map.put(tuple._1(), tuple._2());
    }

    return map;
  }

Extends the ApplicationInfoRequest

message ApplicationInfoRequest {
  string appId = 1;
  string user = 2;
  // new added
  map<string, string> properties = 3;
}

Other efforts related, finally display a column conf within application page.

Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[x]  I agree to follow this project's Code of Conduct

Search before asking

[x]  I have searched in the issues and found no similar issues.

Describe the feature
We can let client send sparkConf to coordinator to show more context information about this application.
Motivation
Insight and know what application are running and being served by RSS cluster.
Describe the solution

Create a util method like this.

  public static Map<String, String> sparkConfToMap(SparkConf sparkConf) {
    Map<String, String> map = new HashMap<>();
    Tuple2<String, String>[] scalaMap = sparkConf.getAll();

    java.util.Iterator<Tuple2<String, String>> it =
        Arrays.stream(scalaMap).iterator();
    while (it.hasNext()) {
      Tuple2<String, String> tuple = it.next();
      map.put(tuple._1(), tuple._2());
    }

    return map;
  }

Extends the ApplicationInfoRequest

message ApplicationInfoRequest {
  string appId = 1;
  string user = 2;
  // new added
  map<string, string> properties = 3;
}

Other efforts related, finally display a column conf within application page.

Additional context
No response
Are you willing to submit PR?

[x]  Yes I am willing to submit a PR!
Application information should be displayed in the Spark history server.

@jerqi Sorry for that I do not explain more about the motivation.

Motivation
I want to get the application relevant upstream trigger, in our scenacrio, it is livy, the upstream of livy is supersql and then is us.

If I have sparkConf, I can get these information by
usp.param=20240315170727772_20240726000000
spark.app.name=livy-session-23219-decb9ee5-a499-469a-b8ed-e23605e8efbf
spark.livy.supersql.session_id=decb9ee5-a499-469a-b8ed-e23605e8efbf
spark.org.apache.hadoop.yarn.server.webproxy.amfilter.AmIpFilter.param.PROXY_URI_BASES=http://xxxx/xxx

Base on these, we can get more context and know well about this job, we could dig the reason of failure or under performance.
Besides, we can get more useful information to help us for issue defeat.

spark.sql.warehouse.dir to check the cluster performance.
java version to check whether the java version is expected.
spark.internal.preload.jars to check whether the client jar is expected.
classpath  to check whether the client jar is correct.
user.name to get the actually user name
spark.rss.* to check the effected config about uniffle.
spark.app.attempt.id to know the attempt time


Refactor the app, fix bugs and add tests.

Note

The Ledger App project started several years ago, and some things may seem outdated at the moment, so I refactored the app based on app-boilerplate.
This is a large PR, so it may take more effort to review it, thank you for your efforts. 🙏
While this update contains breaking changes, but it does not affect Ledger Live, StellarX, StellarTerm and Stellar Account Viewer, they still work well together.

Changelog
Updated

Added a Sequence Number setting: Displayed or NOT Displayed, default to NOT Displayed. (resolves #40)
Optimized the display of amount. (ex. 10000000 XLM -> 10,000,000 XLM) (resolves #39)
Optimized the display of offer price.
Optimize the display of Memo Text and Manage Data Value, if they are printable ASCII characters, they will be printed directly, otherwise display the base64 encoded summary.
In some common operations, the prompt for the operation type was removed.
Other UX improvements.
Other bugfixes.
Refactored this app based on app-boilerplate.
Refactored unit tests and added full e2e tests.
Added APDU documentation.

Breaking changes

Removed keypair validation in GET_PUBLIC_KEY command. If necessary, we recommend that you ask the user to confirm the address on the device.
Removed support for the KEEP_ALIVE command at the app layer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@0edc5c9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #43   +/-   ##
==========================================
  Coverage           ?   77.89%
==========================================
  Files              ?       12
  Lines              ?     2298
  Branches           ?        0
==========================================
  Hits               ?     1790
  Misses             ?      508
  Partials           ?        0

Flag
Coverage Δ

unittests
77.89% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@lpascal-ledger Looks like the swap-ci-workflow.yml is outdated, I'll make a separate PR to fix this, please wait a moment.

@overcat I'm on it, don't worry. Bitcoin application cutoff some legacy last week so it's expected.
Also refreshing branch protection rules in the same time.
Nice CI though.

@lpascal-ledger I made a duplicate PR#45  since I didn't notice that you made a PR


Draft: schedule's args serdes should adhere to this SDKs protocol

Args typically are serialized and deserialized using objarray-> and args-> (defined in temporal.internal.utils) so that data-conversion can transparently work with arbitrary data.  Schedule should adhere to this protocol and apply objarray-> on arguments so as to satisfy the args-> call when workflow is executed.
TODO: enhance UT to actually launch a workflow when base java library adds proper schedule support to its "testing" framework.

@mintybayleaf first of all thank you for the contribution. Came handy just in time for me.
One thing though... I followed the doc https://cljdoc.org/d/io.github.manetu/temporal-sdk/0.20.1/doc/clients?q=schedule#scheduled-workflow-executions but got an exception when the workflow was launched. The workflow launched by temporal scheduler was trying to deserialize arguments using ->args (around line 74 in internal/workflow.clj) and raised an exception as the serialization was not done using ->objarray.  This PR attempts to use ->objarrary for serialization as the symmetrical use of ->objarray and ->args for serdes seems to be the pattern.
However I wonder if I'm missing something and may not be using the schedule api as intended. Can you take a peek and give feedback please? In particular, how are you using it?

@mintybayleaf first of all thank you for the contribution. Came handy just in time for me.
One thing though... I followed the doc https://cljdoc.org/d/io.github.manetu/temporal-sdk/0.20.1/doc/clients?q=schedule#scheduled-workflow-executions but got an exception when the workflow was launched. The workflow launched by temporal scheduler was trying to deserialize arguments using ->args (around line 74 in internal/workflow.clj) and raised an exception as the serialization was not done using ->objarray. This PR attempts to use ->objarrary for serialization as the symmetrical use of ->objarray and ->args for serdes seems to be the pattern.
However I wonder if I'm missing something and may not be using the schedule api as intended. Can you take a peek and give feedback please? In particular, how are you using it?

Thank you for using the code! I think this might have been an oversight on my part when I copied a bulk of the code over.
The symmetry here makes sense, and I just simply missed it because we wrote this code internally and did not use the internal ->objarray function at that time. I pulled down your change and tested it with our scheduled workflows.
We use a custom JSON converter for the payloads and everything seemed to work just fine!
So good catch! This seems to be backwards compatible as well.

@mintybayleaf first of all thank you for the contribution. Came handy just in time for me.
One thing though... I followed the doc https://cljdoc.org/d/io.github.manetu/temporal-sdk/0.20.1/doc/clients?q=schedule#scheduled-workflow-executions but got an exception when the workflow was launched. The workflow launched by temporal scheduler was trying to deserialize arguments using ->args (around line 74 in internal/workflow.clj) and raised an exception as the serialization was not done using ->objarray. This PR attempts to use ->objarrary for serialization as the symmetrical use of ->objarray and ->args for serdes seems to be the pattern.
However I wonder if I'm missing something and may not be using the schedule api as intended. Can you take a peek and give feedback please? In particular, how are you using it?

@muralisrini
Thank you for using the code! I think this might have been an oversight on my part when I copied a bulk of the code over.
The symmetry here makes sense, and I just simply missed it because we wrote this code internally and did not use the internal ->objarray function at that time. I pulled down your change and tested it with our scheduled workflows.
To answer your actual question we are converting the bytes -> json and vice versa so we could use the cli and the ui
So good catch! This seems to be backwards compatible as well.

perfect, ty for the quick response!
I've removed Draft now.


undefined method `[]' for nil:NilClass during Match

New Issue Checklist

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

Issue Description
Over the weekend, interacting with the dev center using match errors out. After drilling down, it looks like the providers for the supplied developer account are nil/null and the terms aren't accepted. I vaguely remember there was a warning in fastlane that new terms were needed to be accepted on the Developer Center. However, on the Dev Center there's no new terms update, and I can do all normal functions on the dev center with this account (regen/create provisioning profiles, add/remove team members, make new bundle ID's).
The JSON Blob printed out in the output is the body of the request to https://olympus.itunes.apple.com/v1/session made in fetch_olympus_session
(please excuse the mess of output, it's taken from Bamboo who maims fastlane's output)
Complete output when running fastlane, including the stack trace and command used
INFO [2017-11-20 14:26:15.65]: -------------------
INFO [2017-11-20 14:26:15.65]: --- Step: match ---
INFO [2017-11-20 14:26:15.65]: -------------------
INFO [2017-11-20 14:26:15.65]: Successfully loaded '/Users/buildserver/Documents/bamboo-home/bamboo_agent_<IP_ADDRESS>/xml-data/build-dir/HHUS-CIQE315-JOB1/ios/Fastlane/Matchfile' ?
+---------+----------------------------------------------------------------------------------------+
|                           Detected Values from './Fastlane/Matchfile'                            |
+---------+----------------------------------------------------------------------------------------+
| git_url | [[redacted]]                                                                           |
| type    | enterprise                                                                             |
+---------+----------------------------------------------------------------------------------------+
+-----------------------+----------------------------------------------------------------------------------------+
|                                            Summary for match 2.65.0                                            |
+-----------------------+----------------------------------------------------------------------------------------+
| type                  | enterprise                                                                             |
| force                 | true                                                                                |
| git_url               | [[redacted]]                                                                           |
| git_branch            | master                                                                                |
| template_name         | [[Redacted]]                                                                           |
| verbose               | true                                                                                |
| app_identifier        | [[redacted]]                                                                           |
| username              | [[redacted]]                                                                           |
| keychain_name         | login.keychain                                                                         |
| readonly              | false                                                                                |
| team_id               | [[redacted]]                                                                           |
| skip_confirmation     | false                                                                                |
| shallow_clone         | false                                                                                |
| clone_branch_directly | false                                                                                |
| force_for_new_devices | false                                                                                |
| skip_docs             | false                                                                                |
| platform              | ios                                                                                |
+-----------------------+----------------------------------------------------------------------------------------+
INFO [2017-11-20 14:26:15.66]: Cloning remote git repo...
INFO [2017-11-20 14:26:15.66]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
INFO [2017-11-20 14:26:15.66]: $ GIT_TERMINAL_PROMPT=0 git clone '[[redacted]]' '/var/folders/vh/1_pfckjs5sv8h58swn9v2_pm0000gn/T/d20171120-93078-9ir0fx'
INFO [2017-11-20 14:26:15.67]: ? Cloning into '/var/folders/vh/1_pfckjs5sv8h58swn9v2_pm0000gn/T/d20171120-93078-9ir0fx'...
INFO [2017-11-20 14:26:16.98]: ? remote: Counting objects: 27587, done.
INFO [2017-11-20 14:26:17.05]: ? remote: Compressing objects: 100% (25325/25325), done.
INFO [2017-11-20 14:26:25.62]: ? remote: Total 27587 (delta 2257), reused 27477 (delta 2203)
INFO [2017-11-20 14:26:25.62]: ? Receiving objects: 100% (27587/27587), 128.55 MiB | 15.01 MiB/s, done.
INFO [2017-11-20 14:26:25.70]: ? Resolving deltas: 100% (2257/2257), done.
INFO [2017-11-20 14:26:25.90]: ?  Decrypted '[[Redacted]].cer'
INFO [2017-11-20 14:26:26.31]: ?  [[Decrypts all profiles in repo]]
INFO [2017-11-20 14:26:26.31]: ?  Successfully decrypted certificates repo
INFO [2017-11-20 14:26:26.31]: Verifying that the certificate and profile are still valid on the Dev Portal...
{"user"=>{"fullName"=>"[[Redacted]]", "emailAddress"=>"[[Redacted]]", "prsId"=>"[[Redacted]]"}, "provider"=>nil, "availableProviders"=>[], "backingType"=>"NONE", "roles"=>[], "unverifiedRoles"=>[], "featureFlags"=>[], "agreeToTerms"=>false, "modules"=>[{"key"=>"Resources", "name"=>"ITC.HomePage.Resources.IconText", "localizedName"=>"Resources and Help", "url"=>"https://itunespartner.apple.com/", "iconUrl"=>"https://itunesconnect.apple.com/itc/img/ico_homepage/resourcesAndhelp.png", "down"=>false, "visible"=>true, "hasNotifications"=>false}], "helpLinks"=>[{"key"=>"All", "url"=>"https://itunespartner.apple.com", "localizedText"=>"All Resources and Help"}, {"key"=>"News", "url"=>"https://itunespartner.apple.com/news/", "localizedText"=>"News"}, {"key"=>"Videos", "url"=>"https://itunespartner.apple.com/videos/", "localizedText"=>"Videos"}, {"key"=>"Guides", "url"=>"https://itunespartner.apple.com/guides/", "localizedText"=>"Guides"}, {"key"=>"FAQ", "url"=>"https://itunespartner.apple.com/faq/", "localizedText"=>"FAQ"}, {"key"=>"ContactUs", "url"=>"https://www.apple.com/itunes/go/itunesconnect/contactus", "localizedText"=>"Contact Us"}], "localizations"=>{"signIn"=>"Sign In", "personalDetails"=>"Personal Details", "signOut"=>"Sign Out"}, "pccDto"=>nil}
WARN [2017-11-20 14:26:28.72]: Lane Context:
INFO [2017-11-20 14:26:28.72]: {:DEFAULT_PLATFORM=>:ios, :ENVIRONMENT=>"mhqaenterprise", :PLATFORM_NAME=>nil, :LANE_NAME=>"build", :SIGH_PROFILE_TYPE=>"enterprise", :MATCH_PROVISIONING_PROFILE_MAPPING=>{"[[redacted]]"=>"match InHouse [[redacted]]"}}
ERROR [2017-11-20 14:26:28.72]: undefined method `[]' for nil:NilClass
INFO [2017-11-20 14:26:28.72]: Successfully generated documentation at path '/Users/buildserver/Documents/bamboo-home/bamboo_agent_<IP_ADDRESS>/xml-data/build-dir/HHUS-CIQE315-JOB1/ios/fastlane/README.md'
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | mkdir -p ../build-post              | 0           |
| 4    | Switch to update_build_number lane  | 0           |
| 5    | set_info_plist_value                | 0           |
| 6    | set_info_plist_value                | 0           |
| 7    | set_info_plist_value                | 0           |
| 8    | xcversion                           | 10          |
| 9    | automatic_code_signing              | 1           |
| 10   | update_info_plist                   | 0           |
| 11   | update_app_identifier               | 0           |
| 12   | update_project_team                 | 0           |
| 13   | match                               | 15          |
| ?   | match                               | 12          |
+------+-------------------------------------+-------------+
DEBUG [2017-11-20 14:26:28.73]: All plugins are up to date
ERROR [2017-11-20 14:26:28.73]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Search query: undefined method `[]' for nil
URL: https://api.github.com/search/issues?q=undefined method `[]'%20for%20nil+repo:fastlane/fastlane
??  `app_store_build_number` fails with `undefined method `current_build_number' for nil:NilClass (NoMethodError)`
https://github.com/fastlane/fastlane/issues/10447 [open] 3 ?
3 hours ago
??  undefined method `to_sym' for nil:NilClass when running gym
https://github.com/fastlane/fastlane/issues/10717 [closed] 11 ?
3 weeks ago
??  Gym Errors Out with: [!] undefined method `each_with_object' for nil:NilClass
https://github.com/fastlane/fastlane/issues/10780 [closed] 8 ?
2 hours ago
and 292 more at: https://github.com/fastlane/fastlane/search?q=undefined method `[]' for nil&type=Issues&utf8=?
?  You can ? + double-click on links to open them directly in your browser.
DEBUG [2017-11-20 14:26:29.24]: All plugins are up to date
/Users/buildserver/fastlaneSource/spaceship/lib/spaceship/provider.rb:8:in initialize': [!] undefined method []' for nil:NilClass (NoMethodError)
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:507:in `new'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:507:in `fetch_olympus_session'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:472:in `send_shared_login_request'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/portal/portal_client.rb:13:in `send_login_request'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:671:in `do_login'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:405:in `login'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/client.rb:121:in `login'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/portal/spaceship.rb:22:in `login'
from /Users/buildserver/fastlaneSource/spaceship/lib/spaceship/portal/spaceship.rb:92:in `login'
from /Users/buildserver/fastlaneSource/match/lib/match/spaceship_ensure.rb:19:in `initialize'
from /Users/buildserver/fastlaneSource/match/lib/match/runner.rb:22:in `new'
from /Users/buildserver/fastlaneSource/match/lib/match/runner.rb:22:in `run'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/actions/match.rb:12:in `run'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:231:in `block in execute_action'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:227:in `chdir'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:148:in `trigger_action_by_name'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
from ../fastlane/Fastfile:186:in `block in parsing_binding'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/lane.rb:33:in `call'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:45:in `chdir'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/runner.rb:45:in `execute'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/lane_manager.rb:54:in `cruise_lane'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/commands_generator.rb:104:in `block (2 levels) in run'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
from /Users/buildserver/fastlaneSource/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:66:in `run!'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/commands_generator.rb:303:in `run'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
from /Users/buildserver/fastlaneSource/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in `take_off'
from /Users/buildserver/fastlaneSource/bin/fastlane:20:in `<top (required)>'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/bin/fastlane:23:in `load'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/bin/fastlane:23:in `'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `eval'
from /Users/buildserver/.rvm/gems/ruby-2.3.3/bin/ruby_executable_hooks:15:in `'
Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.1

Ruby
2.3.3

Bundler?
true

Git
git version 2.13.6 (Apple Git-96)

Installation Source
~/.rvm/gems/ruby-2.3.3/bin/fastlane

Host
Mac OS X 10.13.1 (17B48)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.3.3/lib

OpenSSL Version
OpenSSL 1.0.2l  25 May 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
9.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.65.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-unzip
1.0.1
✅ Up-To-Date

fastlane-plugin-update_project_codesigning
0.2.0
✅ Up-To-Date

fastlane-plugin-appicon
0.10.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.0.0

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.16.0

io-console
0.4.5

rake
11.3.0

CFPropertyList
2.3.5

concurrent-ruby
1.0.5

i18n
0.9.1

minitest
5.10.3

thread_safe
0.3.6

tzinfo
1.2.4

activesupport
4.2.10

public_suffix
2.0.5

addressable
2.5.2

ast
2.3.0

babosa
1.0.2

debug_inspector
0.0.3

binding_of_caller
0.7.3

builder
3.2.3

byebug
9.1.0

claide
1.0.2

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.3.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.11.0

cocoapods-trunk
1.3.0

cocoapods-try
1.1.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.7

ruby-macho
1.1.0

nanaimo
0.2.3

xcodeproj
1.5.3

cocoapods
1.3.1

coderay
1.1.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

json
2.1.0

docile
1.1.5

simplecov-html
0.10.2

simplecov
0.14.1

tins
1.15.1

term-ansicolor
1.6.0

thor
0.19.4

coveralls
0.8.21

safe_yaml
1.0.4

crack
0.4.3

declarative
0.0.10

declarative-option
0.1.0

diff-lcs
1.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

dotenv
2.2.1

excon
0.59.0

fakefs
0.8.1

multipart-post
2.0.0

faraday
0.13.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.0

jwt
2.1.0

little-plugger
1.1.4

multi_json
1.12.2

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.13.6

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.3.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

tty-screen
0.6.2

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
1.0.0

fastlane-plugin-appicon
0.10.0

fastlane-plugin-unzip
1.0.1

fastlane-plugin-update_project_codesigning
0.2.0

hashdiff
0.3.7

interception
0.5

method_source
0.9.0

parallel
1.12.0

parser
<IP_ADDRESS>

powerpack
0.1.1

pry
0.11.3

pry-byebug
3.5.0

pry-rescue
1.4.5

pry-stack_explorer
<IP_ADDRESS>

rack
1.6.8

rack-protection
1.5.3

rainbow
2.2.2

rb-readline
0.5.5

rest-client
2.0.2

rspec-support
3.5.0

rspec-core
3.5.4

rspec-expectations
3.5.0

rspec-mocks
3.5.0

rspec
3.5.0

rspec_junit_formatter
0.2.3

ruby-progressbar
1.9.0

rubocop
0.49.1

tilt
2.0.8

sinatra
1.4.8

webmock
2.3.2

xcode-install
2.3.1

yard
<IP_ADDRESS>

generated on: 2017-11-20

Same errors here.

Fastlane 2.65.0
XCode 9.1 (9B55)
Same here, with any fastlane function interfacing with the developer account (register_devices, match, etc.)

Same here. Issue appeared after upgrading from 2.64.0 to 2.65.0

Still present on 2.66.0

Same here.

Same error message with sigh.

Same here... on 2.66.0
ruby -v 2.4.0

I'm experiencing the same issues. I'm using fastlane version 2.66.0

Same here. Didn't occur in 2.64.

I faced the same issue , temporarily solution is roll back to version 2.64.0. Below code works for me now.
gem uninstall fastlane --all --executables
gem install fastlane --version 2.64.0 --no-document

2.64.1 works for us, too.
If you're running a CI, you will probably have to force uninstall, since there are some dependent gems:
gem uninstall --force fastlane --all --executables

Hello everyone, sorry you're having issues with this. I believe I've already found the culprit in our code so hang tight a little bit longer and we'll try to fix it!

If you are using bundler to install fastlane, you can try my branch using the following code:
gem 'fastlane', github: "milch/fastlane", branch: "fix-provider-crash"

After running bundle install that version should be picked up. Let me know if that fixes your crashes!

@milch, This fixed it for us as well.

Version 2.66.1 was just released, so once you upgrade everything should be working again!
Thanks for all your reports everyone. I'm going to close this for now, but let me know if something like this pops up for any of you again

Hi @milch
I've updated to 2.66.1. But still get an error like below
2.66.1/fastlane/lib/fastlane/fast_file.rb:360:in 'version_range_info': [!] undefined method 'split' for nil:NilClass (NoMethodError)
Is this the same issue like this one?

@swarchen Huh, sorry about that. I lust looked into it but it seems that this is a separate issue. You are using import_from_git, right?
Could you open a separate issue with full fastlane env output (etc.) for me please?

Hi @milch . Thanks for the reply.
I've opened a new issue #10977 with fastlane env output.


Why is ipv6 disabled in boot2docker 17.04?

I'm trying to run unbound in a container (docker run -it --entrypoint=/bin/bash spotify/helios-solo:latest to be exact). One of the ports it listens to is ::1 8953. unbound starts fine with boot2docker 17.03 and below, but it fails on 17.04.
root@b830b961e530:/# unbound
[1493753376] unbound[107:0] debug: creating udp4 socket <IP_ADDRESS> 53
[1493753376] unbound[107:0] debug: creating tcp4 socket <IP_ADDRESS> 53
[1493753376] unbound[107:0] debug: creating udp6 socket :: 53
[1493753376] unbound[107:0] debug: creating tcp6 socket :: 53
[1493753376] unbound[107:0] debug: creating tcp6 socket ::1 8953
[1493753376] unbound[107:0] error: can't bind socket: Cannot assign requested address
[1493753376] unbound[107:0] debug: failed address ip6 ::1 port 8953 (len 28)
[1493753376] unbound[107:0] error: cannot open control interface ::1 8953
[1493753376] unbound[107:0] fatal error: could not open ports

This is because ipv6 is disabled for some reason.
root@b830b961e530:/# sysctl -a | grep disable_ipv6

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

Compare 17.03.
root@98c78f0fd9ce:/# sysctl -a | grep disable_ipv6

net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.eth0.disable_ipv6 = 0
net.ipv6.conf.lo.disable_ipv6 = 0

Why the change? Was this intentional? Could we re-enable ipv6 by updating sysctl.conf?

This is not a change within boot2docker, but, as far as I can tell, a ~"feature"~ regression of the 17.04.0-ce docker release (release notes).  I can only guess that it seems to be related to https://github.com/moby/moby/pull/30807, since it is the only one to mention ipv6, but I can't seem to figure out how to use link-local-ip to have it just generate one.

If you're running containers with --network=host, this is most likely due to a bug in docker 17.04; https://github.com/moby/moby/issues/32433, which will be fixed in 17.05 which is scheduled to be released soon

@thaJeztah Thanks for clarifying.

Feel free to close.

 Oh, I don't have permissions on this repository to close issues, but you should be able to do so yourself 👍


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In a1d266b, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 7419 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in b463db6 after 10 minutes.


No function clause when the record does not exist

I noticed that if a query fails to return any records, I get the following error:
** (FunctionClauseError) no function clause matching in Memento.Query.coerce_records/1
(memento) lib/memento/query/query.ex:663: Memento.Query.coerce_records(:"$end_of_table")
However calling Mnesia directly, I get the standard message of:
{:atomic, []} that I can easily pattern match on.

Nevermind. I looks like I can turn coercion off and handle the end_of_table result myself.

Hey @Korbin73, this might still be a potential bug. Can you please post details about your table structure and the query you executed?

Sure, it's quite simple actually.  I have a simple table:
defmodule Request.Record do
use Memento.Table,
attributes: [:url, :response]
end
All I did was do a select that where I knew that the it would not return anything from Mnesia:
Memento.transaction! fn ->
Memento.Query.select(Request.Record, {:==, url, "gibberish"}, [limit: 1])
end
After looking at the source, I noticed that I could turn off coercion so the coerce_records function isn't called. I was expecting on getting an empty record when it was on instead of an exception, but turning off coercion and matching the result myself is pretty easy.

Yep this was in fact a bug in the code. It should've returned an empty list when no records match.
I just published a new release (v0.3.1) to hex.pm with the bugfix.


Debug drawing extension to allow drawing primitives on HUD layer

Description

This PR adds the ability to draw the DebugHelper primitives on the HUD layer as well. This allows drawing debug primitives which do not show up in sensor data. New PythonAPI functions are implemented with the naming DebugHelper.draw_hud_<shape>() alongside existing draw functions DebugHelper.draw_<shape>(). The python function signatures are otherwise equivalent to their existing non-HUD counterparts.
Here is an example. I am drawing the old primitives (red) and new primitives (blue) side by side. The first image shows the server-side window where all the primitives are visible, and the second image shows an sensor.camera.rgb sensor output. The new primitives do not show up in the sensor output, which means they can be used for server-side visualization without polluting sensor data. Old primitives are drawn with default properties, and the HUD primitives are drawn with thickness=10 to match the old primitives. A thickness of 1 equates to 1 pixel wide on the new HUD primitives.

This PR is a proposed solution to the issue #6705.
Where has this been tested?

Platform(s): Ubuntu 20.04
Python version(s): 3.7
Unreal Engine version(s): 4.26 (Carla fork)

Possible Drawbacks
Very simple feature, so there isn't much that could go wrong.

Hello saipua, could you merge dev branch into yours so I can use our jenkins to test everything works fine?

Hi, I've updated my branch to dev


Folder fails to lookup in tmdb because of - and :

I'm retroactively scanning for missing trailers, but when a movie has a - instead of : in the folder name, the lookup in TMDB seems to fail. In many OS filesystems, a colon : cannot be used so - is added instead.
Example:

Folder: Chicken Run - Dawn of the Nugget (2023) parses into:

Title: Chicken Run - Dawn of the Nugget
Year: 2023

TMDB title: Chicken Run: Dawn of the Nugget

The TMDB API gets checked using the following snippet. A quick test to replace the special characters, makes it work with a lot of movies.
# https://github.com/jsaddiction/TrailerTech/blob/main/providers/tmdb.py#L198
        for result in response['results']:
-            if str(year) in result['release_date'] and result['title'].lower() == title.lower():
+            if str(year) in result['release_date'] and result['title'].lower().replace(":", "") == title.lower().replace(" -", ""):
                return result['id']

Ideally, we strip out special characters in this string matcher?

I like where you mind is on this.  Honestly, this script has taken a back seat for now.  I am rewriting several scripts to manage kodi library based on several events triggered by the *arr apps in a smart converged library way.  After I have filled that gap, I will eventually get to rewriting this script.  I think better integration with Radarr and a local database within the script will prove to be much more efficient.  This script scans your entire library every time it's called unless a specific path is given.  To me we should already know what we have.  Additionally, I'd like to cache result from TMDB and look for updates weekly and act on TMDB's changes rather than searching over and over.  Moreover, I am a quality nerd so accurate analysis of resolution and bit rate of all available trailers should be determined and stored (TMDB sometimes lies).  Potential upgrades should be downloaded, evaluated, stored in the db and replace the original if better.  Just some thoughts.
As for your current issue, you are welcome to fork this repo, make the edits and use to your liking.  For me, this script is fairly stale and desperately needs some upgrades.


Unknown Runtime: 'electron '

Issue Summary
Hi 👋
I'm trying to rebuild the module with sqlcipher support for electron 21.1.0, and I'm getting the error Unknown Runtime: 'electron '.
I'm not sure where the problem is. Most likely I'm not doing something properly.
I'd much appreciate if someone could take a look at this logs.
Thanks!
[17:02:13] 'build-sqlcipher' errored after 2.49 s
[17:02:13] Error: Command failed: set npm_config_target=21.1.0 && set npm_config_arch=x64 && set npm_config_target_arch=x64 && set npm_config_disturl=https://atom.io/download/electron && set npm_config_runtime=electron && set npm_config_build_from_source=true && npm rebuild sqlite3 --build-from-source --sqlite_libname=sqlite3 --sqlite=C:\Users\paco\acme\my-electron-app\sqlcipher --verbose
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm verb cli C:\Program Files (x86)\nodejs\node.exe C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 1ms
npm timing config:load:defaults Completed in 4ms
npm timing config:load:file:C:\Users\paco\AppData\Roaming\nvm\v16.16.0\node_modules\npm\npmrc Completed in 1ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 4ms
npm timing config:load:env Completed in 2ms
npm timing config:load:file:C:\Users\paco\acme\my-electron-app\build-temp\.npmrc Completed in 0ms
npm timing config:load:project Completed in 5ms
npm timing config:load:file:C:\Users\paco\.npmrc Completed in 1ms
npm timing config:load:user Completed in 2ms
npm timing config:load:file:C:\Program Files (x86)\nodejs\etc\npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 1ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 2ms
npm timing config:load Completed in 27ms
npm timing npm:load:configload Completed in 28ms
npm timing npm:load:mkdirpcache Completed in 1ms
npm timing npm:load:mkdirplogs Completed in 1ms
npm verb title npm rebuild sqlite3
npm verb argv "rebuild" "sqlite3" "--build-from-source" "--sqlite_libname" "sqlite3" "--sqlite" "C:\\Users\\paco\\acme\\my-electron-app\\sqlcipher" "--loglevel" "verbose"
npm timing npm:load:setTitle Completed in 5ms
npm timing config:load:flatten Completed in 6ms
npm timing npm:load:display Completed in 12ms
npm verb logfile logs-max:10 dir:C:\Users\paco\AppData\Local\npm-cache\_logs
npm verb logfile C:\Users\paco\AppData\Local\npm-cache\_logs\2022-10-13T15_02_12_690Z-debug-0.log
npm timing npm:load:logFile Completed in 13ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 62ms
npm timing arborist:ctor Completed in 0ms
npm timing build:queue Completed in 0ms
npm info run<EMAIL_ADDRESS>install node_modules/sqlite3 node-pre-gyp install --fallback-to-build
npm info run<EMAIL_ADDRESS>install { code: 7, signal: null }
npm timing command:rebuild Completed in 1062ms
npm verb stack Error: command failed
npm verb stack     at ChildProcess.<anonymous> (C:\Users\paco\AppData\Roaming\nvm\v16.16.0\node_modules\npm\node_modules\@npmcli\promise-spawn\lib\index.js:63:27)
npm verb stack     at ChildProcess.emit (node:events:527:28)
npm verb stack     at maybeClose (node:internal/child_process:1092:16)
npm verb stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd C:\Users\paco\acme\my-electron-app\build-temp
npm verb Windows_NT 10.0.22000
npm verb node v16.16.0
npm verb npm  v8.11.0
npm ERR! code 7
npm ERR! path C:\Users\paco\acme\my-electron-app\build-temp\node_modules\sqlite3
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-pre-gyp install --fallback-to-build
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp verb cli [
npm ERR! node-pre-gyp verb cli   'C:\\Program Files (x86)\\nodejs\\node.exe',
npm ERR! node-pre-gyp verb cli   'C:\\Users\\paco\\acme\\my-electron-app\\node_modules\\@mapbox\\node-pre-gyp\\bin\\node-pre-gyp',
npm ERR! node-pre-gyp verb cli   'install',
npm ERR! node-pre-gyp verb cli   '--fallback-to-build'
npm ERR! node-pre-gyp verb cli ]
npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>| win32 | x64
npm ERR! node-pre-gyp verb command install [ 'napi_build_version=6' ]
npm ERR! node-pre-gyp info build requesting source compile
npm ERR! node-pre-gyp verb command build [ 'rebuild', 'napi_build_version=6' ]
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli   'C:\\Program Files (x86)\\nodejs\\node.exe',
npm ERR! gyp verb cli   'C:\\Users\\paco\\AppData\\Roaming\\nvm\\v16.16.0\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js',
npm ERR! gyp verb cli   'clean'
npm ERR! gyp verb cli ]
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| win32 | x64
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp info ok
npm ERR! node-pre-gyp ERR! UNCAUGHT EXCEPTION
npm ERR! node-pre-gyp ERR! stack Error: Unknown Runtime: 'electron '
npm ERR! node-pre-gyp ERR! stack     at get_runtime_abi (C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\util\versioning.js:86:13)
npm ERR! node-pre-gyp ERR! stack     at Object.module.exports.evaluate (C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\util\versioning.js:295:15)
npm ERR! node-pre-gyp ERR! stack     at handle_gyp_opts (C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\util\handle_gyp_opts.js:59:27)
npm ERR! node-pre-gyp ERR! stack     at configure (C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\configure.js:12:3)
npm ERR! node-pre-gyp ERR! stack     at C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\build.js:43:7
npm ERR! node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\Users\paco\acme\my-electron-app\node_modules\@mapbox\node-pre-gyp\lib\util\compile.js:91:5)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
npm ERR! node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1092:16)
npm ERR! node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! node-pre-gyp ERR! System Windows_NT 10.0.22000
npm ERR! node-pre-gyp ERR! command "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\paco\\acme\\my-electron-app\\node_modules\\@mapbox\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
npm ERR! node-pre-gyp ERR! cwd C:\Users\paco\acme\my-electron-app\build-temp\node_modules\sqlite3
npm ERR! node-pre-gyp ERR! node -v v16.16.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.10
npm verb exit 7
npm timing npm Completed in 1212ms
npm verb unfinished npm timer build<PHONE_NUMBER>311
npm verb unfinished npm timer build:deps<PHONE_NUMBER>312
npm verb unfinished npm timer build:run:install<PHONE_NUMBER>316
npm verb unfinished npm timer build:run:install:node_modules/sqlite3<PHONE_NUMBER>316
npm verb code 7

npm ERR!      C:\Users\paco\AppData\Local\npm-cache\_logs\2022-10-13T15_02_12_690Z-debug-0.log

    at ChildProcess.exithandler (node:child_process:398:12)
    at ChildProcess.emit (node:events:527:28)
    at ChildProcess.emit (node:domain:537:15)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)

C:\Users\paco\acme\my-electron-app>

Steps to Reproduce

Rebuild the module with sqlcipher for electron 21.1.0 using the following command:
set npm_config_target=21.1.0 && set npm_config_arch=x64 && set npm_config_target_arch=x64 && set npm_config_disturl=https://atom.io/download/electron && set npm_config_runtime=electron && set npm_config_build_from_source=true && npm rebuild sqlite3 --build-from-source --sqlite_libname=sqlite3 --sqlite=C:\Users\paco\acme\my-electron-app\sqlcipher --verbose

Version
5.1.2
Node.js Version
16.16.0
How did you install the library?
Windows 10 ARM 64 bit

My bad, I have read the docs better and now I'm setting proper flags. Now I'm stuck on a 403 while downloading headers :)


Round corners on rootView

I would like to add round corners to the root view ONLY when the LeftViewController is showing (see attachment 1). I've been advised to use :
sideMenuController.rootViewContainer.layer.cornerRadius = 8.0 which didn't do anything.
I tried using the following code instead and the result was half way of what was desired (see attachments 2 & 3) :
rootViewContainer?.cornerRadius = 8.0
Issues :

The round corners appear on the root view even when no side-menu is showing
When we expand the side-menu, we see a black BG behind the rounded corners

If this could be fixed, it would be great.
Thank you!

I tried to implement this feature. But it has really bad performance.
You can check it out by yourself in this branch:
test_rounded_corners
If you will have any ideas, pull requests are welcome.


add the function to check if the user has identified

Hi!
I want to know that user has identified.
and I want to know  user's property like email, name.
Can you create this function in flutter package?

Hey! I think this package may not be right place for this: this feature would involve querying PostHog's API as a logged in user (using a full-access personal API key instead of the write-only project API key). For now we don't plan to support this here. In the meantime I'd suggest you write your own ad hoc function in your app to query the person PostHog endpoint the way you need.

@Twixes Ohh Thanks!


how to get mesh vertices?

Hello, I am quite new in this area. I have a .stl file. I want to get vertices of this object. The vertices should be in shape of (Mx3). How to do that?

Hi @odgiv ,  a .stl-file is basically  a list of triangles.
your_mesh.vectors gives you all triangles defined by their vertices.
You can also access the vertices by using:
your_mesh.v0, your_mesh.v1and  your_mesh.v2
Note that for example your_mesh.v0[0],your_mesh.v1[0],your_mesh.v2[0] are the vertices of the first triangle (position 0) .
If you only want all vertices of your mesh in one array you could maybe do this:
import numpy as np
from stl import mesh

# Using an existing stl file:
your_mesh = mesh.Mesh.from_file('some_file.stl')

# Creating an array with all vertices of all triangles:
allvertices = np.array([your_mesh.v0,your_mesh.v1,your_mesh.v2])

# Numpy-Concatenate to connect the three arrays with each other
allvertices = np.concatenate(allvertices)

# Removing duplicate vectors
allvertices = np.unique(allvertices,axis=0)
print(allvertices)

maybe this can also help you:
https://pythonhosted.org/numpy-stl/usage.html#quickstart
I hope i could help

@biga123 thank you.


Factsheet 'maxArrayLens' naming convention deviation?

In the object 'maxArrayLens' inside the factsheet, the naming convention for the object are suddenly different, with names including dots ('.'), like 'order.node'
Is this supposed to be a separate JSON object (Like as a JSON object accessing it like 'factsheet.protocolLimits.maxArrayLens.order.node') ?
Looking at the schema, this is intentionally a name with a dot (so in it needs to be accessed like 'factsheet.protocolLimits.maxArrayLens.['order.node']') which is just deviating from the overall neat convention that has been used everywhere else. Also I would think are implementations of JSON with having a dot in the key will be problematic..
Suggestion 1:
Change it to the same naming convention as everywhere else, for example:
factsheet.protocolLimits.maxArrayLens.orderNode
Suggetstion 2:
Change it to a JSON object so it can be accessed properly as a JSON, for example:
factsheet.protocolLimits.maxArrayLens.order.node
where order is a JSON that has the property node.

@Tirine Thank you for pointing that out and suggesting solutions. By using these names, we tried to show the data structure to which this limit is referring to. But you are right, this is a deviation from the naming convention.
Since this would be breaking changes, we must postpone a decision on that until the release of Version 3 is coming up. For the use of Version 2, we will stick to these names.

In the object 'maxArrayLens' inside the factsheet, the naming convention for the object are suddenly different, with names including dots ('.'), like 'order.node'
Is this supposed to be a separate JSON object (Like as a JSON object accessing it like 'factsheet.protocolLimits.maxArrayLens.order.node') ? Looking at the schema, this is intentionally a name with a dot (so in it needs to be accessed like 'factsheet.protocolLimits.maxArrayLens.['order.node']') which is just deviating from the overall neat convention that has been used everywhere else. Also I would think are implementations of JSON with having a dot in the key will be problematic..

Technically I don't see a need of change. As far as I understand the json-spec and the charts on https://www.json.org/json-en.html don't forbid keys containing dots. I agree with you that some json-implementations could have troubles with that, but I don't think, that specifications should be set up in a way, that ready-implemented software with weak parts can still be used in future. e.g. I doubt that html5 was specified in a way that considered limitations of IE.

Technically was not my argument either, convention and in the end code style for end users is my argument :)


Unable to extract CSS (vite: true)

Environment

Operating System: Darwin
Node Version:     v22.6.0
Nuxt Version:     2.18.1
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      bridge, vite, nitro, alias, css, modules, experimental, build, head, plugins, components, buildModules, moment, axios, vue, router, serverHandlers, devServerHandlers, devServer, typescript
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>
Reproduction
Any Nuxt 2 project of Nuxt Bridge cannot extract css
Describe the bug
When the Nuxt 2 project was gradually upgraded using the bridge, it was found that after enabling Vite, all styles were style tags dynamically generated by JS and could not be extracted into separate css files. This caused the page to not display properly when loaded for the first time.
Additional context
No response
Logs
No response

Have you tried vite.legacy: false?
ref: https://github.com/nuxt/bridge/pull/1164

@wattanx vite.legacy: false succeeded, but compared with the webpack package, the page still flickers and displays no style first. This problem will not occur after webpack packaging. Nuxt 3 will not have this problem either.

So I think the vite issue still exists.

It seems to work in a production build.
(npm run build && npm run start)
https://stackblitz.com/edit/github-yueotr
There may be a problem in the case of dev

It seems to work in a production build. (npm run build && npm run start) https://stackblitz.com/edit/github-yueotr
There may be a problem in the case of dev

@wattanx
I think you should have noticed that although the style is successfully extracted, the application style still flickers.
You can try to use webpack to extract the style in the same way, and there will be no flickering.

Rather than flickering, it should be a lag in enabling styles

There was also likely to be flickering in the case of production builds.
(I didn't notice it because it was fast).
We'll look into it, but it will take time.

@wattanx I think we should reopen it and revise the title.
Yes, you solve the problem of style flashing in #1308, but it has not solved the problem of flashing after Pord Build packaging.
My configuration:
export default defineNuxtConfig({
  ssr: true,
  sourcemap: true,
  bridge: {
    capi: true,
    vite: { legacy: true },
    nitro: true,
    meta: true,
    macros: { pageMeta: true },
  },
  vite: {
    css: {
      postcss: {
        plugins: [tailwindcss(), autoprefixer()],
      },
    },
  },
});

At present, this is the biggest reason that hinders me to continue to upgrade to Nuxt 3. Because there are a lot of dependence that needs to be upgraded. But this problem forced me to continue to use the webpack@v4, so I couldn't continue to gradually upgrade other contents.

@wattanx
I only made a minimum replica: https://stackblitz.com/edit/github-yueotr-bdkcg4?file=pages%2Findex.vue

In addition, this seems to be the return of #561

<template>

test

</template>

For this purpose, I also created a minimal implementation for Nuxt 3. The behavior is essentially different. There is only one reason why Nuxt 3 is not present:
Nuxt 3 writes the style of pages or components to the html head, and Nuxt bridge does not do this.
This is why the page flickers after Nuxt bridge enables vite.
example: https://stackblitz.com/~/github.com/medz/github-8bvs9l

This is the output after Nuxt bridge enables vite. There is no h1{color:red} style, and the style is applied in JS only after index.xxx.js is loaded.
This causes the flickering.

Could you create a new issue? (I might miss it otherwise)

Could you create a new issue? (I might miss it otherwise)

Yes 👉 https://github.com/nuxt/bridge/issues/1334


Link to GitHub website and other version controls are missing.

Add website/download/documentation link.
On the frontend development career page, there is a section called Version Control. For each list, the links to their website, documentation and download link if applicable are missing.
List

[ ] Git
[ ] Git Desktop
[ ] GitHub
[ ] GitLab
[ ] Bitbucket

Task
For the above list,

add link to the website of the service with the name of the link saved as "Website".

add link to the documentations page of the service with the name of the link saved as "Documentation".

add link to the download page of the service if applicable with the name of the link saved as "Download here".

include a badge for each link, with the label of the badge set to 'Link'. (view examples of the badge on the links in this section.)

Things to Note

the website link must come first,

the download link must come second,

and the documentations page link must come third on the list.

please follow the code format/template on the html page.

Resources
View how to contribute to this repository.

can i work on this problem

Yes @aryancharan. You can work on it.

I am willing to work on it

I am willing to work on it Can I work on it ?
@mohit1607 you can go ahead with this.

Just a one problem I made the  changes in my computer and the local repo is  up to date but when I type command
"git push origin " I get this :  remote: Permission to Timonwa/techroadmap.git denied to mohit1607.
fatal: unable to access 'https://github.com/Timonwa/techroadmap.git/': The requested URL returned error: 403

I think you are trying to push directly to the main repo instead of you own repo. It's not possible to do that since you don't have access to the main repo.
Try doing that first. Or just do git push, it should show you  something like git push --set-upstream origin branch.. Then you copy and paste it.


Game-Breaking Bug: Non-host players get softlocked on join

Describe the bug
Upon joining a lobby, the player will get stuck on a black screen. Every UI element will be present and centered on the middle of the screen. Now the player is softlocked, unable to use anything, and the only way to quit the game is to Alt+F4. If the host closes the lobby, the player will still be stuck on this screen.
On the host's side, the player is never visible, both inside the ship and in the "Esc" menu screen. The game console also does not throw any errors.
Disabling AC solves this issue entirely
To Reproduce
Steps to reproduce the behavior:

Have both players use the same profile&configs shared below.
Have one player host a game.
Have the second player join the host.
See error on the non-host player.

Expected behavior
The non-host player joins the lobby without any issue.
Screenshots
Non-Host screen after joining the lobby:

Additional context
All disabled mods were disabled during an effort to try and figure out the source of this bug, but I wasn't successful. Everything works perfectly for the host, with every single mod enabled. The issue only happens when another player joins.
Logfiles
R2_Modman_Log_Host.txt
R2_Modman_Log_Player.txt
(Host)Player.log
Add a list of all of your mods
Dependency_String.txt
Profile_Code: 018d5237-55ed-67c9-56f7-616ccf68dc85

i'm having the same issue

Similar issue, I quit out of my game and came back and it worked fine. However, for some reason I had 10 inventory slots available despite the host (and myself) setting it to only 4. The host only had 4 slots to work with while I had 10. (Should be noted our setup does NOT include perks, and AC should be the only mod affecting inventory in some way.)
My log is as follows:
log.txt
And Dependency String as follows:
BepInEx-BepInExPack-5.4.2100
NotAtomicBomb-TerminalApi-1.5.1
AlexCodesGames-AdditionalContentFramework-1.0.3
Rune580-LethalCompany_InputUtils-0.6.1
sfDesat-ExpansionAssets-1.0.0
jockie-LethalExpansionCore-1.3.15
Evaisa-HookGenPatcher-0.0.5
Evaisa-LethalLib-0.14.0
IAmBatby-LethalLevelLoader-1.0.7
sunnobunno-YippeeMod-1.2.3
RugbugRedfern-Skinwalkers-4.0.1
Pooble-LCBetterSaves-1.7.3
Monkeytype-HideChat-1.0.0
BlueAmulet-NameFix-1.0.1
AlexCodesGames-AdditionalSuits-2.0.0
notnotnotswipez-MoreCompany-1.7.6
FlipMods-TooManyEmotes-1.8.3
FlipMods-LetMeLookDown-1.0.1
echoman-Uninvertible_Jetpack-0.0.1
Piggy-ShowCapacity-1.0.7
Suskitech-AlwaysHearActiveWalkies-1.4.4
AgeCo-AgeSignals-1.0.1
boring-CustomTranslatorCharLimit-1.0.2
ThePotato-scanForItemsFix-1.0.4
TheDeadSnake-Touchscreen-1.0.8
Zaggy1024-OpenBodyCams-1.0.20
Jamil-Corporate_Restructure-1.0.6
akechii-DiscountAlert-2.3.0
Dreamweave-CompanyBuildingEnhancements-2.6.0
LethalOrg-ProgressiveDeadline-2.0.0
Nozz-Lethal_Missions-1.1.6
Evaisa-LethalThings-0.9.4
Justice69-ImmersiveScraps-1.1.5
PotatoePet-AdvancedCompany-1.0.140
sfDesat-Aquatis-1.1.0
TeamBridget-Peaches_Castle-1.0.41
Boniato-Ganimedes-1.6.0
Ceelery-Kast-1.0.3
With the code to match configs as such:
018d52c0-7f20-0c4d-43b0-243fbb7d4c0f

The attached log files are not the Player.log files and are lacking crucial information.

The attached log files are not the Player.log files and are lacking crucial information.

My bad, got mixed up in the moment and sent the regular R2Modman logs. I've updated the issue with the Host's Player.Log file for now, and tomorrow i'll get the Non-Host's one (he's asleep right now).

Apologies for the wrong log file, does this potentially help out with the issue at hand?
Player.log

I also updated my logs accordingly, I was a non-host in my run that experienced this exact same issue too.

found why it was happening for me, lethal level loader.

scratch that x2, only breaks with advanced company

I will also note that in a smaller modpack of my own, BetterSprayPaint caused this issue. Disabled just it, the second player joined fine. Re-enabled it, back to the black screen bug.
If anyone is still having this issue and has that mod, try toggling it.
Figured I'd mention this since disabling mods one by one to find out which one is conflicting can be quite tedious. And of course, your mileage may vary from mine.

scratch that, more interiors. and it seems more interiors does it alone, advanced comp or not.

can confirm

I'm using MoreInteriors with no issue.


FollowJointTrajecotry Test Configuration

Description

PR depends on https://github.com/eholum/ros2_controllers/pull/1 which also needs to be moved to the main repo
PR introduces launch and configuration files for testing action interface for JTC

I don't understand what exactly this depends on - is there a corresponding ros2_controllers PR upstream? The test also needs to be registered in the CMakeLists.txt and start its own ursim, is that part still missing?


Add intrinsic for clock2x32ARB

Close issue #4564.
This change adds the glsl intrinsic clock2x32ARB support.
Also define a cap: GL_ARB_shader_clock.

Thanks, I will provide a follow-up change for the 64bit version.


Unable to use customize deviceshifu

Is your feature request related to a problem? Please describe.
My Instruction Name is a num, for it's my device id, but it is unable to be a python func name.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
xx
Describe the solution you'd like
modify shifu crd that i can set the python func name
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

fixed in #369 , closing this issue


Transform constructor to data

Codecov Report

Merging #11 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   99.43%   99.45%   +0.02%
==========================================
  Files           1        1
  Lines         178      185       +7
==========================================
+ Hits          177      184       +7
  Misses          1        1

Impacted Files
Coverage Δ

index.js
99.45% <100%> (+0.02%)
:arrow_up:

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 651f1c0...b757e45. Read the comment docs.


Possibly fix #28?

I haven't exhaustively tested, but it fixes the particular regex I was experiencing wrong results for, and a couple others I tried at random.

Going to have to reject this pull request, sorry! Although this fixes the specific case you mentioned, it introduces a few other test case failures, starting with test_star_advanced in fsm_test.py. You can run the whole suite using python -m pytest in the base directory of the project.
Also, if you are supplying a bug fix, please also add a test case which demonstrates the bug, like this:
def test_bug_28():
	# Defect in lego.to_fsm()
	assert not parse("(ab*)*").to_fsm().accepts("bb")


bug: Running my T3 app takes up way too much RAM

Provide environment information
System information:
  System:
    OS: Windows 10 10.0.19044
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
    Memory: 2.35 GB / 7.88 GB
  Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.12.1 - C:\Program Files\nodejs\npm.CMD```

Version in the package.json:
  "ct3aMetadata": {
    "initVersion": "7.10.3"
  }

Describe the bug
When I run my create-t3-app project, it uses a large amount of CPU and RAM, making my system unresponsive.
See a video of what is going on in my VScode terminal
Reproduction repo
https://github.com/Beefy-py/chat-app.git
To reproduce

Clone the create-t3-app production repo project which I made public from GitHub.
Install all dependencies using npm install.
Start the application using npm run dev.
Navigate to localhost in your browser and interact with the application for a few minutes.
Check task manager

Additional information
Expected behavior:
The application should run smoothly with minimal resource usage.
Actual behavior:
The application causes my system to become unresponsive, and when I check my task manager, it's using more than 70% of my device RAM and more than 80% CPU. It's crazy.
System Info
npx envinfo --system --binaries:
  System:
    OS: Windows 10 10.0.19044
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
    Memory: 2.35 GB / 7.88 GB
  Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.12.1 - C:\Program Files\nodejs\npm.CMD

Screenshot performance
Running in VSCode terminal

Running in Windows Powershell

Errors
I got this after some time in the VScode terminal before it continued wreaking havoc again:
warn  - The server is running out of memory, restarting to free up memory.
error - Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -4077,
  code: 'ECONNRESET',
  syscall: 'read'
}```

Remove:
console.log(ctx.prisma);
from
/src/server/api/routers/chat.ts:11
It's gonna keep eating all your available memory when that tRPC method gets called.

Should it be considered resolved ?

Yup,
Solved.


Update the new US based locations.

New US location URLs related to CloudSigma are updated.
Description
The new locations are wdc.alpha3cloud.com and sjc.alpha3cloud.com

Thanks for the contribution. The change looks good to me, but it would be good to also add / update test cases.
Having said that - should this driver also be renamed from CloudSigma to Alpha2Cloud? Or should the driver name be left as is and we perhaps add an alias for Alpha2Cloud -> Cloud Sigma (or vice versa).

Codecov Report

Merging #1781 (3ccff87) into trunk (a4f4f90) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            trunk    #1781   +/-   ##
=======================================
  Coverage   83.41%   83.41%
=======================================
  Files         394      394
  Lines       87680    87680
  Branches     9261     9261
=======================================
  Hits        73135    73135
  Misses      11386    11386
  Partials     3159     3159

Impacted Files
Coverage Δ

libcloud/common/cloudsigma.py
100.00% <ø> (ø)

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 a4f4f90...3ccff87. Read the comment docs.

Thanks @Kami
The driver should not be renamed. It should be left as CloudSigma.
We have just changed the URLs for two locations but the driver and the functionality should be the same.

@mohsen-hassani-cs Thanks for confirming and sorry for the delay (I've missed your comment). I will go ahead and merge you PR.
Thanks again for your contribution.


Fixup the generic node structure for Java [phab:D1129]

Created by salguarnieri at 2016-10-28 20:19:56:
According to the schema and other langauges, there should be no source
range that represents the class node. The class name source range should
be used for the abs node. See the updated tests for examples.

zarko accepted this revision at 2016-10-31 17:16:08

salguarnieri closed via commit 1b74ffa98b1c9edc285008eded4fb2b44a519e7d at 2016-10-31 17:18:44


TimeSpan updates incorrectly

I am updating a row using DataTable and the TimeSpan column is not updated correctly.
The value set in the code is 1 day 9 hours but it is persisted as "1 day 02:09:36" in db.

I have tested this using Npgsql and that work correctly.

Can someone tell me how to debug the code so that I can see what is going wrong?

Can someone please help us with this? Our project is stuck because of this issue, we are getting incorrect numbers because of this issue.

Rebuild the FSharp.Data.Npgsql.sln, then open the Tests.sln (close Tests.sln and repeat this step if you make any changes in the type provider)
Comment out NpgsqlCmdTests.fs and NpgsqlConnectionTests.fs if you just want to diagnose the issue against your database.
In Program.fs paste the code that's causing you problems.
From the FSharp.Data.Npgsql.sln VS instance attach the debugger to devenv.exe of the other instance.
If you now modify the connection string static parameter, you'll be able to hit breakpoints in InformationSchema.fs
If you modify any command, you'll be able to hit breakpoints in NpgsqlCommandProvider and NpgsqConnectionProvider.
===
All of the above is debugging the design-time part of the provider.
To debug the runtime bit (ISqlCommand.fs in particular), change Tests.fsproj to an executable and type Console.ReadKey () just above the line where you execute the problematic command.
Keeping in mind the step that you need to rebuild and close solutions with any modification, launch the Tests program without pressing anything.
From the FSharp.Data.Npgsql.sln VS instance attach to Tests.exe, place breakpoints in Runtime.fsproj and only then press a key in the Tests progam's window to continue execution, hopefully hitting your breakpoints.

Folder FSharp.TypeProviders.SDK is empty.

It's https://github.com/demetrixbio/FSharp.Data.Npgsql/blob/master/src/Runtime/CommandBuilder.fs#L37 causing the issue.
If the issue occurs then IMO it needs to be fixed further up - in DbCommandBuilder, not  at this level.
IMHO this change needs t0 be reverted.
@melanore could you please have a look and share your thoughts?

Apologies for delta replying.  Managing our local response to virus outbreak :(.   Would really help me to see a piece of test code that reproduces. Most of the issues we have seen with timezones are related to subtle misunderstanding of the Postgres semantics.  To make sure it is a bug I love to reproduce it exactly as a failing test ideally.  I can take a look tomorrow. Sorry this is holding you up
Darren

Am 21.03.2020 um 7:26 PM schrieb Sandeep Chandra<EMAIL_ADDRESS>
It's https://github.com/demetrixbio/FSharp.Data.Npgsql/blob/master/src/Runtime/CommandBuilder.fs#L37 causing the issue.
If the issue occurs then IMO it needs to be fixed further up - in DbCommandBuilder, not at this level.
IMHO this change needs t0 be reverted.
@melanore could you please have a look and share your thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Attached is a test app. It has DDL and sql to insert test data.
TestApp.zip
Take your time, response to coronavirus has higher priority than this.

Thanks for the app - just to confirm I can reproduce the bug which is a good start.  Debugging to try and understand what is happening.  Your theory might be right about the resetdbtype.  It looks like it's getting cast badly at some point

Hey just an update on this - have been wading through it slowly.  I haven't set up testing for a long time on this so had some cleanup to do but have ported your example into a failing unit test,  updated and documented the test setup and cleaned a bunch of failing unit tests.  There's a branch https://github.com/demetrixbio/FSharp.Data.Npgsql/tree/20/03/BUG-interval_updates_corrupting  you can follow if you want to help with the actual debugging but I kind of understand now how it's coming up with that strange time interval (converting 33 hours into 1 day 2 hours 9 minutes 36 seconds).  That happens to be 1.09 (1.089999 actually) days (decimal days),  so something is doing a horrible cast of 1,09  from 1 day 09 hours to 1.09 days.

@melanore  suggested we might need to also set DbType in  here - am going to try that.  Have had a bit of trouble getting debugger to step into this code since it's an override - rider seems to only let me breakpoint the underlying method but will resort to print statements if necessary till I kill this.  Thanks for your patience.

Fixed in https://www.nuget.org/packages/FSharp.Data.Npgsql/0.2.4-beta
Thanks @daz10000 for figuring out the root cause and @sandeepc24 for reporting an issue.

Quick postscript on this one - thanks @sandeepc24  as well,   this flushed out some awkwardness in enum handling we had been seeing so fixed two problems for price of one bug fix.  Always nice.

Thanks guys for fixing this issue.

Just updated to latest version and I get following error
FSC : error FS3031: The type provider
'\.nuget\packages\fsharp.data.npgsql\0.2.4-beta\lib\netstandard2.0\FSharp.Data.Npgsql.dll'
reported an error: Assembly attribute 'TypeProviderAssemblyAttribute' refers to a designer
assembly 'FSharp.Data.Npgsql.DesignTime' which cannot be loaded or doesn't exist.
Could not load file or assembly
'\.nuget\packages\fsharp.data.npgsql\0.2.4-beta\lib\netstandard2.0\FSharp.Data.Npgsql.DesignTime.dll'.
The system cannot find the file specified.

That's the known compile time issue with the .net type provider. Could you try to switch FSAC to net/mono in Ionide (or any other IDE you are using)?

I installed version 16.5 of Visual Studio and that is causing this issue.

Same problem now with .NET 5 Preview. Both 0.2.3 and 0.2.4 :(

Error seems to be caused by this issue - https://github.com/demetrixbio/FSharp.Data.Npgsql/issues/78. Hopefully fix suggested by @cartermp will work.


Issue/1933 Create "Migrating" section and move content from Guides

Create "Migrating" section and move content from Guides.
Fixes #1933

Thank you, it is now master based @TheLarkInn

@TheLarkInn can you re-approve this one been hanging for some time now

Hi @montogeek ,
Can u merge this if i rebase and resolve the conflict?

@EugeneHlushko sure

Failure is known: API rate limit exceeded for <IP_ADDRESS>
Pls finish this one @montogeek

@montogeek yes, makes any sense for the finished PRs? thought to create new ones under main repository but merge older ones as is to reduce mess on my side of things

Was trying to make the build pass, it already did. Already pinged @TheLarkInn to approve it

Thank you!

Approved. Let's get conflicts resolved and good to go!

Cool, waiting for build and can merge cc @montogeek

Thanks


Patch 5

Description
Extending PR https://github.com/rethinkdb/docs/pull/802.
This PR is adding the 3 missing examples.

FYI: @srh , I'll merge this PR just letting you know that is was here 😄


Use with ES6

Hey, how can I use this plugin using ES6 import syntax instead of common js require?

The plugin is published with an es6 bundle that your runtime should pick up automatically. You can import it either as a default import or using the exported function, e.g.
import dtsPlugin from "esbuild-plugin-d.ts";
// or
import { dtsPlugin } from "esbuild-plugin-d.ts";

Okay, thanks for the information! Maybe you could update the readme so that others can see this 👍


Input Playback Service is missing in RecordArticulatedHandPoseInputSystemProfile

Describe the bug
The RecordArticulatedHandPoseInputSystemProfile used by the HandInteractionRecordArticulatedHandPose scene does not include the Input Playback Service, which causes errors when one tries to record/playback input.
To reproduce
Steps to reproduce the behavior:

Go to the HandInteractionRecordArticulatedHandPose scene
Open the input simulation window from Mixed Reality Toolkit > Utilities > Input Simulation
Run the scene in editor play mode
Bring up a simulated hand by pressing t
Start recording
Move the hand around by holding left shift
End recording
See error

Expected behavior
Error should not appear.
Your setup (please complete the following information)
Unity 2019.4.8f1
MRTK v2.4

fixed in the forthcoming 2.5.0 release


some minor changes to your script, see commit history for details

some minor changes to your script, see commit history for details

Thanks again for these improvements! I just tagged 2.1.0 with them included :)


bindToController does not transfer form and model controller objects from scope to controller

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
feature
What is the current behavior?
The bindToContoller option when using a directive does not bind any of the formControllers or modelControllers.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
http://plnkr.co/edit/uT8nbdMuUE8dpSjBytfj
What is the expected behavior?
When using bindToController the form and model controllers should be transferred to the controller just like the bound properties. See comments in the js code.
What is the motivation / use case for changing the behavior?
The whole point of bindToController is to remove the complexities of dealing with the scopes. By not transferring over the form and model controllers when using the bindToController the developer is forced to reintroduce the scope object in order to do any javascript form validation.
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
This appears to affect all versions that have bindToController implemented.
Other information (e.g. stacktraces, related issues, suggestions how to fix)

There is no reason to not bind your form to the controller. Doing <form name="vm.testForm"> is perfectly valid.
The reason why this.testForm is undefined during the controller instantiation, is that the controller is instantiated before child directives (including form) have been linked. BTW, injecting $scope in your controller won't help you at all (it will run into the same problems).
--
If you want to access the form controller from within your controller, you need wo wait until the post-linking phase, when the form controller will have been bound to your controller.
In previous versions, you would rely on hacks like $timeout, or being forced to have link function anyway, but since v1.5.3 directive controllers have lifecycle hooks, so you can use $postLink.
Updated plnkr
--
Closing since what you requested is already possible.


Forced to update to latest Gradle plugin for Android Studio 2.1 stable

Not sure if you want this yet, but AS 2.1 stable will not allow the project to build without it.

Hmm, I guess I'll have to merge this. Strangely, I've never encountered this issue with any other library before. For instance, I use the library with this build.gradle in a project, and even though build tools uses an older version, it stilll works fine with the latest android studio.
Maybe this is a problem with using the release candidate build tools?

Yeah, I don't know either. I updated this morning and it prompted me to update it both for this and for my app. It wouldn't let me do a build or a Gradle sync without it.

Strange. If this crops up with future version of the plugin, I'll investigate further.


Add support for Hibernate Validator @CPF annotation

Feature description
Checks that the annotated character sequence represents a Brazilian individual taxpayer registry number (Cadastro de Pessoa Física).

Supported data types: CharSequence
Country:  Brazil

Docs: https://docs.jboss.org/hibernate/stable/validator/reference/en-US/html_single/#_country_specific_constraints
@REGON implementation can be used for reference (RegonGeneratorSpec and RegonSpec).

I want to work on this issue!

@brunodmartins thank you for taking this on!
A couple of links that might help you get started:

https://www.instancio.org/building/
https://github.com/instancio/instancio/blob/main/CONTRIBUTING.md

Thanks! I am working on a PR right now!

I opened the PR. I used the SSN generator as a guide to implement the CPF generation, and after that, I added the Bean validation. I can work on the other two BR issues too! #1007 #1005


Finatra sends the wrong HTTP status code when it receives a request for an unsupported method

Register multiple methods for the same route. E.g.
get("/foo") { rq => ... }
post("/foo") { rq => ... }

Then send request to the route with a different method (e.g. a PUT to /foo).
Finatra responds with 404 (Not Found).  It should respond with 405 (Method Not Allowed).

Are there labels for lhf (low hanging fruit) for Scala newbies to get started with? I took a quick look at Finagle, TwitterServer, and Finatra but am not sure if this is a simple task or not.

hi @akanshmurthy, this is a bit off topic but we love help.
for finagle we've been using "good first issue". same for util and twitterserver.
doesn't look like any of the current finatra tickets are tagged with that.

Ok, thanks! I was thinking about working on this ticket which is why I posted here :) Sorry for the spam!

I really don't know how to use GitHub >.<, just an update that @jyanJing is working on this.

Finatra is now supporting returning a 405 in its latest release: 19.9.0!
For release notes, please check: https://finagle.github.io/blog/2019/09/10/release-notes/


Issue #3228 Add Multipath TCP (MPTCP) support

#3228 solved.

I have not done the testing.

Thanks! Looking forward to seeing MPTCP being supported in this Duckduck Go app!

@awaan05 Hey - thanks for opening this! I'm going to close it as Not Planned for now since additional work is needed for this change to work. Specifically:

The Multipath entitlement is required
The approach taken in this PR adds a new session property that isn't directly used, and cannot be used from other parts of the codebase
multipathServiceType is only being set on a single URLSessionConfiguration instance; any other instances that are created (even from .default) will use the default value, not handover

However, I've raised this suggestion as a ticket internally so that we can discuss and prioritize the change. Thanks!


SRP Swagger Updates for Jan23 [2023-05-01] Api Version GA

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Could you please add a bit more information about the suppressions you are adding. The reason for those are not really clear to me.

Removed unnecessary suppressions

Please comment on the other unanswered questions - #28461 (comment)

This comment was addressed - https://github.com/Azure/azure-rest-api-specs/pull/28461#issuecomment-2070931564

Could you please add a bit more information about the suppressions you are adding. The reason for those are not really clear to me.

This was done https://github.com/Azure/azure-rest-api-specs/pull/28461#issuecomment-2070931564

      "description": "The SAS Expiration Action defines the action to be performed when sasPolicy.sasExpirationPeriod is violated. The 'Log' action can be used for audit purposes and the 'Block' action can be used to block and deny the usage of SAS tokens that do not adhere to the sas policy expiration period."

would those also be logged?

Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:2723 in 10a3bff. [](commit_id = 10a3bffebd607e63dfb03e10187c79dd3115fdb2, deletion_comment = False)

    },

Is it true by default?

Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:5284 in 10a3bff. [](commit_id = 10a3bffebd607e63dfb03e10187c79dd3115fdb2, deletion_comment = False)

      "description": "The SAS Expiration Action defines the action to be performed when sasPolicy.sasExpirationPeriod is violated. The 'Log' action can be used for audit purposes and the 'Block' action can be used to block and deny the usage of SAS tokens that do not adhere to the sas policy expiration period."

would those also be logged?
Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:2723 in 10a3bff. [](commit_id = 10a3bff, deletion_comment = False)

No, the Block Action will not be Logged

    },

Is it true by default?
Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:5284 in 10a3bff. [](commit_id = 10a3bff, deletion_comment = False)

The default is false

Just want to check:
The lintdiff stage errors
'PatchPropertiesCorrespondToPutProperties'
do seem like they _might _ be highlighting an issue that needs fixing -- do you support updating these properties with patch?

Just want to check: The lintdiff stage errors 'PatchPropertiesCorrespondToPutProperties' do seem like they _might _ be highlighting an issue that needs fixing -- do you support updating these properties with patch? Is this a real issue or false positive?

Some of these are false positives since PUT and PATCH do have the same properties:

startOn/endBy/intervalUnit/interval/startFrom
PUT: https://github.com/triciarosario/azure-rest-api-specs/blob/a3a45cc7083de45d6842585fd6f02f67675fdba4/specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storageTaskAssignments.json#L564
PATCH: https://github.com/triciarosario/azure-rest-api-specs/blob/a3a45cc7083de45d6842585fd6f02f67675fdba4/specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storageTaskAssignments.json#L730

prefix
PUT: https://github.com/triciarosario/azure-rest-api-specs/blob/a3a45cc7083de45d6842585fd6f02f67675fdba4/specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storageTaskAssignments.json#L518
PATCH: https://github.com/triciarosario/azure-rest-api-specs/blob/a3a45cc7083de45d6842585fd6f02f67675fdba4/specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storageTaskAssignments.json#L518

Only taskId is not something the user can update, so it is not in PATCH

    },

Is it true by default?
Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:5284 in 10a3bff. [](commit_id = 10a3bff, deletion_comment = False)

The default is false

Documenting that could avoid FAQs.

      "description": "The SAS Expiration Action defines the action to be performed when sasPolicy.sasExpirationPeriod is violated. The 'Log' action can be used for audit purposes and the 'Block' action can be used to block and deny the usage of SAS tokens that do not adhere to the sas policy expiration period."

would those also be logged?
Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:2723 in 10a3bff. [](commit_id = 10a3bff, deletion_comment = False)

No, the Block Action will not be Logged

Documenting that could avoid FAQs.

pr/ RequestMerge

/pr RequestMerge

      "description": "The SAS Expiration Action defines the action to be performed when sasPolicy.sasExpirationPeriod is violated. The 'Log' action can be used for audit purposes and the 'Block' action can be used to block and deny the usage of SAS tokens that do not adhere to the sas policy expiration period."

I mean that it could be nice to clarify in the comment

In reply to:<PHONE_NUMBER>

Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-05-01/storage.json:2723 in 10a3bff. [](commit_id = 10a3bffebd607e63dfb03e10187c79dd3115fdb2, deletion_comment = False)

/pr RequestMerge

Blocked on GO SDK issues. Please address that, then request merge again

/pr RequestMerge

Blocked on GO SDK issues. Please address that, then request merge again

What is the process to get breaking changes approved?

/pr RequestMerge


[11.x] Remove getDefaultNamespace function in EnumMakeCommand

There is no need to have this method in the EnumMakeCommand (Parent class)

Would it be better to place it in the Enums folder instead of the App folder, aligning with the structure where Models are in the Models folder and Casts are in the Casts folder?
protected function getDefaultNamespace($rootNamespace)
{
    return $rootNamespace.'\Enums';
}

@eura-app agreed: https://github.com/laravel/framework/pull/50396