Precip Accumulation decimal place error

Describe the bug
Hello,
TL;DR: Precip Accumulation in HA appears to be off by a factor of 10 compared to the API. I am using US units (Inches).
In the API, I am seeing this:
"daily": {
        "summary": "Cloudy",
        "icon": "cloudy",
        "data": [
            {
                "time":<PHONE_NUMBER>,
                "icon": "rain",
                "summary": "Rain",
                "sunriseTime":<PHONE_NUMBER>,
                "sunsetTime":<PHONE_NUMBER>,
                "moonPhase": 0.6,
                "precipIntensity": 0.0062,
                "precipIntensityMax": 0.05,
                "precipIntensityMaxTime":<PHONE_NUMBER>,
                "precipProbability": 0.95,
                "precipAccumulation": 0.15,
                "precipType": "rain",
                "temperatureHigh": 57.38,
                "temperatureHighTime":<PHONE_NUMBER>,
                "temperatureLow": 55.47,
                "temperatureLowTime":<PHONE_NUMBER>,
                "apparentTemperatureHigh": 53.25,
                "apparentTemperatureHighTime":<PHONE_NUMBER>,
                "apparentTemperatureLow": 46.85,
                "apparentTemperatureLowTime":<PHONE_NUMBER>,
                "dewPoint": 51.29,
                "humidity": 0.95,
                "pressure": 1012.35,
                "windSpeed": 6.33,
                "windGust": 12.76,
                "windGustTime":<PHONE_NUMBER>,
                "windBearing": 147.08,
                "cloudCover": 0.8,
                "uvIndex": 1.37,
                "uvIndexTime":<PHONE_NUMBER>,
                "visibility": 3.19,
                "temperatureMin": 47.37,
                "temperatureMinTime":<PHONE_NUMBER>,
                "temperatureMax": 57.38,
                "temperatureMaxTime":<PHONE_NUMBER>,
                "apparentTemperatureMin": 46.64,
                "apparentTemperatureMinTime":<PHONE_NUMBER>,
                "apparentTemperatureMax": 53.25,
                "apparentTemperatureMaxTime":<PHONE_NUMBER>
            },
            {
                "time":<PHONE_NUMBER>,
                "icon": "rain",
                "summary": "Rain",
                "sunriseTime":<PHONE_NUMBER>,
                "sunsetTime":<PHONE_NUMBER>,
                "moonPhase": 0.63,
                "precipIntensity": 0.0167,
                "precipIntensityMax": 0.1401,
                "precipIntensityMaxTime":<PHONE_NUMBER>,
                "precipProbability": 0.75,
                "precipAccumulation": 0.4003,
                "precipType": "rain",
                "temperatureHigh": 60.76,
                "temperatureHighTime":<PHONE_NUMBER>,
                "temperatureLow": 44.45,
                "temperatureLowTime":<PHONE_NUMBER>,
                "apparentTemperatureHigh": 53.62,
                "apparentTemperatureHighTime":<PHONE_NUMBER>,
                "apparentTemperatureLow": 39.59,
                "apparentTemperatureLowTime":<PHONE_NUMBER>,
                "dewPoint": 53.42,
                "humidity": 0.89,
                "pressure": 1002.72,
                "windSpeed": 14.11,
                "windGust": 24.59,
                "windGustTime":<PHONE_NUMBER>,
                "windBearing": 193.63,
                "cloudCover": 0.74,
                "uvIndex": 2.63,
                "uvIndexTime":<PHONE_NUMBER>,
                "visibility": 7.62,
                "temperatureMin": 50.42,
                "temperatureMinTime":<PHONE_NUMBER>,
                "temperatureMax": 60.76,
                "temperatureMaxTime":<PHONE_NUMBER>,
                "apparentTemperatureMin": 46.84,
                "apparentTemperatureMinTime":<PHONE_NUMBER>,
                "apparentTemperatureMax": 53.62,
                "apparentTemperatureMaxTime":<PHONE_NUMBER>

However, In Home Assistant, I am seeing this:

Expected behavior
Precip Accumulation 0d should be 0.15 in
Precip Accumulation 1d should be 0.4003 in
Actual behavior
Precip Accumulation 0d is 0.0150 in
Precip Accumulation 1d is 0.0400 in
Home Assistant version
2024.11.2
Integration version
v<IP_ADDRESS>
Other details
No response
Troubleshooting steps

[X] I have updated my Home Assistant installation to the latest version.
[X] I have updated the Pirate Weather Integration to the latest version.
[X] I have gone through the documentation before opening this issue.
[X] I have searched this repository and API Repository to see if the issue has already been reported.
[X] I have restarted my Home Assistant installation.
[X] I have queried the API in my browser to confirm the issue is not with the API.
[X] I have not included my API key anywhere in my issue.
[X] I have written an informative title.

According to this post here, the API comes in cm not mm. So when the conversion is done to inches, that would explain why it is off by a factor of 10.


[STORM-3494] use HdfsLoginUtil singleton to login to hdfs

Please refer to https://issues.apache.org/jira/browse/STORM-3494
Use HdfsLoginUtil singleton to login to hdfs exactly once for a process.
This will break backwards-compatibility. I didn't find a better way to resolve this. Suggestions are very welcome.

Could we assume if the deprecated blobstore configs are set, STORM_HDFS_LOGIN_PLUGIN should use this default implementation?  Not sure I like this, but would prevent breaking things?
Generally looks good to me.

We don't want to add hadoop as a dependency to storm itself. So the loginPlugin is in a separate module.  Hence to use this loginPlugin, users need to explicitly copy jar files to external-daemon otherwise there would be ClassNotFoundException.  So we can't use it as the default.


Add camel-quartz wrapper

Add camel-quartz wrapper

@ozgurkisir-qlik warning there is still a conflict to resolve


Do not build rr/valgrind/gdb if usable packages are available

In our debugging dockerfiles, we build valgrind, gdb, and rr ourselves.
However, rr provides deb and rpm pacakges on their releases page, and centos 7 has new-enough versions of valgrind and gdb in the SCL repos.
We should avoid building these ourselves if we don't have to.

Has this been done for all platforms?


Azure adapter[do-not-merge/only-for-review]

Initial attempt at addressing #125
This PR is only for getting feedback and not ready for merging.

I made a change here: https://github.com/dsyer/spring-cloud-function/tree/sobychacko-azure-adapter. I couldn't make it into a PR because I rebased onto master as well, so you might like to just grab that branch and force push it into this branch to take advantage of the static cache.

Great to see this Azure adapter underway! I was about to write something myself, but you've saved me some time :-) I've just joined Microsoft as a Cloud Developer Advocate (specifically for Azure + Java), so I'm keen to work with you guys to publicise your efforts and detail how this can benefit the Azure ecosystem. Please feel free to ping me at<EMAIL_ADDRESS>- and good luck getting this complete and merged!


Override parameters using SetParameters.xml (&quot changing as ")

I am using Override parameter to override my connection strings.Task is working fine but it is changing &quot to &quot .
For example : This is the connection string
connection string="data source=source;initial catalog=test;...
And I am changing it to as below using Override parameter.
connection string="data source=Othersource;initial catalog=test;...
In this case I am getting as below :
connection string="data source=Othersource;initial catalog=test;...
It is working correctly when I run MSdeploy through command line.

Can you share full logs with system.debug

Somewhat similar issue. When I try to use the override parameters I get the error System.Exception: Error: Unrecognized argument 'Web'. All arguments must begin with "-". I am entering them into the release configuration as name="settingName",value="settingValue" I've also tried settingName=settingValue both result in the same error. Any ideas?

Closing the issue, as there is no response.
Please feel free to reopen / open a new thread, if the issue still persists.


Upgrade http4s 0.20 and doobie 0.6.0

Upgraded http4s partially via https://http4s.org/v0.20/upgrading/, using scalafix.  A number of other issues spring up, most notably that doobie 0.6.0 and http4s 0.20 must be upgraded together due to evicted dependency issues.
This depends on / includes #102 .
A few adjustments were made in the scala client tests. Using the Http4sClientDsl[F[_]], we get much better syntax on creating requests.

Oops, sorry about out of date local branch. will revise


Mentorship Initiative

The mentorship program is now part of the nodeJS organization on github 🎉 .
It would be awesome to add this issue to the next commcomm meeting (tomorrow i assume) To discuss the following:

New issues related to the mentorship program should be opened in the new repo from now on.

CommComm members and people interested in the program should watch the repo.
A new team should be created for this initiative under node

Kicking off the mentorship program:

Open an issue to iterate over the program structure and process so it is visible to everyone before starting (need explicit agreement from members of the commcomm and the TSC). Check https://github.com/nodejs/mentorship/issues/2
Create a slack channel for the mentorship channel under nodejs (or do we have an already existing slack channel ready to be used)
Coordinate with the nodejs/node project about the program to announce mentorship under their project etc.
Open an issue / reach directly to the monetors list in the node-forward mentors program for node.
Reachout to node evangelists and other active members to publicize the mentorship program to gain momentum (i believe @ZibbyKeaton can help out here).

I don't have the full background about Initiatives etc, and we do not have (yet) a document for the process or general details, so i would like some input about how things are usually carried on after this point forward.

I think we can take this issue off the cc-agenda, as it can/should be reported in the Initiatives report before we discuss agenda items 👍


Command line functionality failure

I believe there is an issue when attempting to write the analytical output from the command line. Here is an example:
python millipede_bar.py --incident data/gaussian_T1.csv --parameters parameters.toml --write

Output
(venv) C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork>python millipede_bar.py --incident data/gaussian_T1.csv --parameters parameters.toml --write
Traceback (most recent call last):
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\millipede_bar.py", line 142, in <module>
    main()
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\venv\lib\site-packages\click\core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\venv\lib\site-packages\click\core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\venv\lib\site-packages\click\core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\venv\lib\site-packages\click\core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "C:\Users\gmbra\Downloads\CAVS\Millipede Bar Fork\millipede_bar.py", line 133, in main
    filename = incident.stem
AttributeError: 'str' object has no attribute 'stem'

It appears that y'all's intent is that incident needs to be a path object, but it is instead the untouched string that the user passes in. Inserting incident = Path(incident) above line 132 appears to fix this.

That makes sense. I changed incident to be a Path object in line 35, but forgot to do so at line 135. Thanks for catching this.


feat apilinks.json generator

Closes #152
Opening this as a draft currently to get feedback on the approach since it's a bit non-trivial relative to the other generators. The apilinks.json file maps things exported by modules to their source locations on Github.
Example:
{
  "SomeClass.prototype.var": "github.com/nodejs/node/tree/<hash>/lib/file.js#L100"
}

This means we need to parse the module's javascript source in addition to its markdown.
What the current approach does is doing:

Adds another loading & parsing step for the js source files

acorn is used for parsing the source files
This is dependent on the Markdown source parsing since it uses the source_link metadata in the docs

Exposes the parsed js ast to other generators by adding the ast-js generator
api-links generator is based off of the ast-js result

With the current approach, the generator is almost there. Some todos remain though:

[ ] I think some exported functions aren't making it
[ ] Git methods are kinda broken
[ ] Some cleanup & docs
[ ] Add tests (when we agree on an approach)

@flakey5 do you need review here? I think I forgot to review this PR!

do you need review here

As far as the approach yes please


Fix the widening operator of the Map functor

This commit avoids using the join operator for the widening
of the Map functor in abstractDomain.ml
and ensures termination when ValueDomain is infinite
by using ValueDomain.widen.

Thanks, good catch!
Could you please rebase on Infer master and use phys_equal instead of ==? As of 7834c95bc831a41858e5088bb0795c8d2ebdb189 we no longer use ==.

Hi @sblackshear ,
I rebased on Infer master and change == to phys_equal. Please check it.
By the way, I still cannot fully understand why do you use phys_equal instead of ==.
Could you give me a reference for that?

== is syntactically very light-weight, and given that it has a tricky specification, should only be used in very specific cases.  Emphasizing the difference with = by using phys_equal instead is just a little mechanism to try to avoid incorrect use by making people thing twice before using it.


Smoke test

EDIT by @Rick-Anderson follows
Internal review URL

@v-alje  I don't see https://source.dot.net/#Microsoft.AspNetCore.Http.RequestDelegateGenerator/DiagnosticDescriptors.cs,44128aef6daa9b5e

@Rick-Anderson Correct, internal and private types are excluded from documentation. They are not available to be called by end users without reflection.


Add_additional_info_to_slideshow37: Controlled Bio info

Placed the click handler on the corr el

Added additional info to Project Container collage.


Optionally skip time reporting

With my current jira setup, whenever I try to create a sub-task it fails with an error caused by the originalEstimate not being able to be set for the task.
I've fixed / hacked it locally by doing
      if (!issue.fields.timetracking) {
        return;
      }

in the setOriginalEstimate method in breakdown-util.js
It would be very cool to have a feature flag ? allowing to avoid this error - i.e. don't set originalEstimate for new tasks.

I´m wondering if your adjustment could be a general rule?

Ah no, it cannot be a general rule. Is the issue somehow dependent on the Sub-task setup of your Jira? Is it allowed to give an estimate for sub-tasks within your Jira UI?

I can only create a sub-task from the User Story screen and doing so doesn't allow to provide any information beside the name.
I can add the details later on in the Sub-task details view, but it's impossible to do it when creating the Sub-task.
I'm using Jira Cloud.

I´ve made an adjustment to not touch the timetracking in case

there is no original estimate defined for the issue; and
you are creating an issue.
Through that you should be able to work with sub-tasks in your environment when you avoid defining the original estimate for new sub-tasks.

Thanks, just checked the new release and it works great.
Closing this one.


Suggestion: Ability to exclude building type from PP ranking

Could be helpful to be able to exclude a certain type of building from PP ranking. For example, though a farm may have the shortest PP, I may not necessarily want to buy another farm and would rather see a ranking based on building types allowed.

I think this is a duplicate of another issue.

Looks like it is, an 11/29/2017 thread.

You didn't need to close it, I would just marked it as dup, oh well.


Global-Buffer-Overflow in function dwarf::line_table::line_table at dwarf/line.cc:107

Tested in Ubuntu 16.04, 64bit.
The tested program is the example program dump_line.
The testcase is dump_line_global_buffer_overflow.
I use the following command:
/path-to-libelfin/examples/dump-lines dump_line_global_buffer_overflow

and get:
terminate called after throwing an instance of 'dwarf::format_error'
  what():  expected 858944595 arguments for line number opcode 16, got 2
--- <0>
Aborted (core dumped)

I use valgrind to analysis the bug and get the below information (absolute path information omitted):
valgrind /path-to-libelfin/examples/dump-lines dump_line_global_buffer_overflow
==9235== Memcheck, a memory error detector
==9235== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9235== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==9235== Command: /path-to-libelfin/examples/dump-lines dump_line_global_buffer_overflow
==9235==
terminate called after throwing an instance of 'dwarf::format_error'
  what():  expected 858944595 arguments for line number opcode 16, got 2
--- <0>
==9235==
==9235== Process terminating with default action of signal 6 (SIGABRT)
==9235==    at 0x546A428: raise (raise.c:54)
==9235==    by 0x546C029: abort (abort.c:89)
==9235==    by 0x4ED3DDD: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==9235==    by 0x4EDF895: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==9235==    by 0x4EDF900: std::terminate() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==9235==    by 0x4EDFB54: __cxa_throw (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
==9235==    by 0x48226F: dwarf::line_table::line_table(std::shared_ptr<dwarf::section> const&, unsigned long, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) (line.cc:116)
==9235==    by 0x413558: dwarf::compilation_unit::get_line_table() const (dwarf.cc:304)
==9235==    by 0x402CB7: main (dump-lines.cc:41)
==9235==
==9235== HEAP SUMMARY:
==9235==     in use at exit: 81,960 bytes in 75 blocks
==9235==   total heap usage: 139 allocs, 64 frees, 90,129 bytes allocated
==9235==
==9235== LEAK SUMMARY:
==9235==    definitely lost: 0 bytes in 0 blocks
==9235==    indirectly lost: 0 bytes in 0 blocks
==9235==      possibly lost: 144 bytes in 1 blocks
==9235==    still reachable: 81,816 bytes in 74 blocks
==9235==                       of which reachable via heuristic:
==9235==                         stdstring          : 86 bytes in 1 blocks
==9235==         suppressed: 0 bytes in 0 blocks
==9235== Rerun with --leak-check=full to see details of leaked memory
==9235==
==9235== For counts of detected and suppressed errors, rerun with: -v
==9235== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Aborted (core dumped)

I use AddressSanitizer to build ffjpeg and running it with the following command:
/path-to-libelfin/examples/dump-lines dump_line_global_buffer_overflow

This is the ASAN information (absolute path information omitted):
/path-to-libelfin-address/examples/dump-lines dump_line_global_buffer_overflow
=================================================================
==9296==ERROR: AddressSanitizer: global-buffer-overflow on address 0x00000045f374 at pc 0x00000043db90 bp 0x7fff57889ea0 sp 0x7fff57889e90
READ of size 4 at 0x00000045f374 thread T0
    #0 0x43db8f in dwarf::line_table::line_table(std::shared_ptr<dwarf::section> const&, unsigned long, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) /path-to-libelfin-address/dwarf/line.cc:107
    #1 0x40f67b in dwarf::compilation_unit::get_line_table() const /path-to-libelfin-address/dwarf/dwarf.cc:304
    #2 0x403356 in main /path-to-libelfin-address/examples/dump-lines.cc:41
    #3 0x7f0bb309682f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
    #4 0x403888 in _start (/path-to-libelfin-address/examples/dump-lines+0x403888)

0x00000045f374 is located 0 bytes to the right of global variable 'opcode_lengths' defined in 'line.cc:15:18' (0x45f340) of size 52
SUMMARY: AddressSanitizer: global-buffer-overflow /path-to-libelfin-address/dwarf/line.cc:107 dwarf::line_table::line_table(std::shared_ptr<dwarf::section> const&, unsigned long, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
Shadow bytes around the buggy address:
  0x000080083e10: f9 f9 f9 f9 00 00 00 00 03 f9 f9 f9 f9 f9 f9 f9
  0x000080083e20: 00 00 00 00 00 00 00 00 04 f9 f9 f9 f9 f9 f9 f9
  0x000080083e30: 00 00 00 00 00 04 f9 f9 f9 f9 f9 f9 00 02 f9 f9
  0x000080083e40: f9 f9 f9 f9 00 00 00 00 03 f9 f9 f9 f9 f9 f9 f9
  0x000080083e50: 07 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00 00 00
=>0x000080083e60: 04 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00[04]f9
  0x000080083e70: f9 f9 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00
  0x000080083e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x000080083e90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x000080083ea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x000080083eb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07
  Heap left redzone:       fa
  Heap right redzone:      fb
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack partial redzone:   f4
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
==9296==ABORTING

An attacker can exploit this vulnerability by submitting a malicious elf file that exploits this bug which will result in a Denial of Service (DoS) even buffer overflow.

CVE-2020-24824 has been assigned for this issue.


My doc build is picking up methods not in the advertised API

Description of issue (what needs changing):
This is a bit of a difficult issue to pin down. I have a class that extends tf.Module, and I'm trying to build the documentation for that class using sphinx (with a couple of extensions). When I build it, I'm seeing a large number of methods in my doc build that aren't advertised in the tf.Module docs. (These are mostly inherited from the superclasses of tf.Module: Autotrackable and Trackable, but that might not be too important here.)
I'd like to be able to show those parts of the tf.Module API that are intended for use by client code (including those with leading underscores that are intended for use in subclasses, i.e. 'protected' methods), and to omit those that aren't. It's not clear to me what parts of these tensorflow classes are indeed part of the public/protected API. It's also not clear to me, if the public API only includes what is shown on the website, how I can omit the rest from my doc build.
The simplest suggestion for me would be for tensorflow to remove the docstrings for all fully private functionality, but that's a lot of work, and I assume you use those docstrings.
You may be wondering why I'm raising this as an issue with tensorflow. The reason is that with the current structure of docstrings in tensorflow, I'm finding it difficult to manage my downstream doc build. Does the tensorflow team have a clear and consistent way of delineating fully private functionality, and if not, is there anything that can be done to improve docstring usability in this regard?

what parts of these tensorflow classes are indeed part of the public/protected API.

The rule is, if it's on tensorflow.org it's public. otherwise it's not.
The code that hides many of those methods is here:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/docs/generate2.py#L177


Deploying NodeJS app fails

Does this occur consistently?
Repro steps:

Have Angular app
Deploy to Azure app service, any app

Action: appService.Deploy
Error type: ECONNRESET
Error Message: request to https://MYURL.scm.azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20Code failed, reason: read ECONNRESET
Version: 0.20.0
OS: win32
OS Release: 10.0.19042
Product: Visual Studio Code
Product Version: 1.51.1
Language: en

Call Stack
ClientRequest.<anonymous> extension.bundle.js:166:16389
ClientRequest.emit events.js:228:7
ClientRequest.EventEmitter.emit domain.js:475:20
TLSSocket.socketErrorListener _http_client.js:406:9
TLSSocket.emit events.js:223:5
TLSSocket.EventEmitter.emit domain.js:475:20
emitErrorNT destroy.js:92:8
emitErrorAndCloseNT destroy.js:60:3
processTicksAndRejections task_queues.js:81:21

This seems like an intermitted issue with Azure.  Could you please restart your app and try to deploy again later?  If this keeps occurring, please provide detailed repro steps.
You could also consider using Azure Static Web Apps.  It's built to handle SPA better than App Service.


Ability to monitor elapsedTime

I'm not sure if this is the preferred way, but we needed a way to detect when an animation was complete, and comparing the elapsed time to the duration accomplished this for us. The only change is to make Animation's elapsedTime property publicly readable.
If you would prefer a different approach, please make a suggestion and I'd be happy to work it up.

@ckentgeorge I don't think there's any harm in making the Animation's elapsed time public. There is already a way of being notified when an action finishes though:
If you create an ActionSequence and pass in your action, followed by a RunBlockAction, you can use the RunBlockActions closure as a callback for when your action finishes. Something like this:
let yourAction = // make your action

let callbackAction = RunBlockAction(handler: {
    // Animation finish callback
})

let sequence = ActionSequence(actions: [yourAction, callbackAction])

The advantage that this has over checking the elapsed duration is that this will always be called, even in the event of a frame rate drop resulting in the update method of the action being completely skipped over, or was not called towards the end of the action. (eg. you might test if the elapsed time is within 0.02 seconds of the duration, but in the event of a frame rate drop at that point, update may never be called with that value).
There is also another mechanism that you may be able to use, depending on your use case. Each action has a willBecomeActive and didBecomeActive closure that you can set:
public var onBecomeActive: () -> () = {}
public var onBecomeInactive: () -> () = {}

The subtle difference here is that these closures are just called to inform you of the active/inactive state of the action. If you run the action in reverse, for instance, onBecomeActive will still be called first, and onBecomeInactive after the action has finished.
In the first example, using the RunBlockAction, if you run the action in reverse, the ActionSequence will call the RunBlockAction first, and then your action second, because it maintains the order of its inner actions, which are now reversed.
Can you let me know if that solves your issue? I'm inclined to keep the duration private for now, but if you have a use case that isn't satisfied, then it would be good to find a solution.
I should also try to spend a bit more time on documentation too!

@ckentgeorge Did you manage to solve your issue using the current TweenKit api?

Steve:
We haven’t circled back around on this issue yet, but I think the method you mentioned will be adequate for our needs. Thanks!
Christopher
From: Steve Barnegren<EMAIL_ADDRESS>Reply-To: SteveBarnegren/TweenKit<EMAIL_ADDRESS>Date: Wednesday, October 25, 2017 at 4:17 AM
To: SteveBarnegren/TweenKit<EMAIL_ADDRESS>Cc: Christopher George<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SteveBarnegren/TweenKit] Ability to monitor elapsedTime (#4)
@ckentgeorge Did you manage to solve your issue using the current TweenKit api?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


scraping web https

i want scraping data website with https type is possible? i try scraping always return empty data.

@komarudin2211 It's definitely possible. Once thing I would check for is if the site expects particular headers or other parameters in the request. For instance I've run into a case where a site won't accept requests without a User-Agent header.


Ensure that the distTar artifact name is available without an afterEvaluate block

@henryptung

Semantically, it might make sense to override setBaseName to throw in this case, but in any case my build will work. :+1:

Link #52


Contribution

Hi!
I have found your "organisation" while I was rebuilding my own version of ZfcUser.
As you have already some other projects converted to Laminas and because I'm not a fan of several user modules which are only maintained by the creators themself I have deleted my "organisation"
and if you want I can contribute to yours.
You can have a look at https://github.com/LMTemp/LMFriends-mvc-user
there is everything I have changed to the ZfcUser.
Basically there are a few things which would be good to integrate into this project which I already have in my fork:

convert arrays to new style
use strict types
change factories so they are compatible with servicemanager 3.0
add csrf tokens again ()
switch from tabs to spaces (and maybe vom /r/n to /n)
use ::class where possible
use null coalescing operator
add parameter type declarations where possible

I would also suggest to add the ZfcUserDoctrineORM to this organisation - I have used it a lot and would like (need) to port it to laminas
What do you think about it?
Regards Alex

@alexz707,
The intent of LM-Commons is for the community to help maintain these libraries.  Your help is welcomed.
@matwright has been maintaining LmcUser and I suggest that you create one or more pull requests so we can look at it.
As far as ZfcUserDoctrineORM, I believe you are not the first one to mention that it should be ported to Laminas as well.  If you are willing to take that work, we can import the repo from ZF-Commons and make you one of the maintainers.

Hi!
ok, so I will try to break the changes into small pieces so it's easier to review them.
Some questions before I start:
I'm used to have the factories next to the classes - would you mind if I would change that?
Can we changed the PSR-0 to PSR-4 ? PSR-0 is deprecated and PSR-4 would allow to get rid off the LmcUser Folder under the src dir.
Yes sure I'm willing to take the work!
I need it for some projects and I it's better to have one place where the packages are maintained instead of several "own" projects which are not really maintained.
Regards
Alex

@alexz707,
Just to make sure, you want to take on the work of migrating ZfcUserDoctrineORM to Laminas?  If so, I will create the repo under LM-Commons for it and give you the rights to the repo.  Let's call it LmcUserDoctrineORM.

@alexz707,
On the other topics, we have to keep in mind that we have many people using this library before we make changes to it.
On the factories issues, I also like to keep factories in the same folder as the class.  At this point, there is no added value to changing that since.  I would wait for a major release to make that change as it introduces breaking change in namespaces forcing everyone to go through their code.  Honestly, I don't know when or what would trigger a major release.
On the PSR-0 issue, I agree that we should upgrade to PSR-4.  @matwright, Any thoughts?

@alexz707,
Just to make sure, you want to take on the work of migrating ZfcUserDoctrineORM to Laminas? If so, I will create the repo under LM-Commons for it and give you the rights to the repo. Let's call it LmcUserDoctrineORM.

Yes I want to do that migration :)

@alexz707,
On the other topics, we have to keep in mind that we have many people using this library before we make changes to it.
On the factories issues, I also like to keep factories in the same folder as the class. At this point, there is no added value to changing that. I would wait for a major release to make that change as it introduces breaking change in namespaces forcing everyone to go through their code. Honestly, I don't know when or what would trigger a major release.
On the PSR-0 issue, I agree that we should upgrade to PSR-4. @matwright, Any thoughts?

You are right. Is this module already in use by many people? When I look at the other homegrown forks of it I would say there is a lot of work to do to make it "famous" again ;)
Of course their shouldn't be breaking changes in minor releases... but is moving a factory a breaking change? Because the module config would also implement that change so the change wouldn't be recognized.
But that's only cosmetical - there is no improvement except readability.
Regards Alex

@alexz707,
Just to make sure, you want to take on the work of migrating ZfcUserDoctrineORM to Laminas? If so, I will create the repo under LM-Commons for it and give you the rights to the repo. Let's call it LmcUserDoctrineORM.

Yes I want to do that migration :)

I created the repo for LmcUserDoctrineORM with an import of ZfcUserDoctrineORM so that is has the entire history, branches, etc.  and assigned you to the Dev team for it.
I have no set opinion on whether to keep all the tags and branches since I do not use it.
We have not set a clear scheme on how to release the library once it is migrated.  I did a major release for LmcRbacMVC.  Others did a minor release.  The important thing is to document the BC in namespaces and any configuration.  For config, we use lmc_xxx as a key where xxx is the library name like lmc_user or lmc_rbac.
I would suggest to add test scripts if you can and some CI like Travis as well to CI-test any future pull requests.
When you are ready to publish to Packagist, let me know as I will have to create the package the first time and make you a maintainer.

Of course their shouldn't be breaking changes in minor releases... but is moving a factory a breaking change? Because the module config would also implement that change so the change wouldn't be recognized.
But that's only cosmetical - there is no improvement except readability.

Refactoring a factory is a BC to me as I have no idea how people use the factories.  I would not assume that everyone uses the Service Manager to create services.  Probably not a good practice to call factories directly but then again, I can see reasons why to do it like create their own private instance of a class or service.  In that case, their code would break.
So I would leave factories where they are for now.

@alexz707,
Just to make sure, you want to take on the work of migrating ZfcUserDoctrineORM to Laminas? If so, I will create the repo under LM-Commons for it and give you the rights to the repo. Let's call it LmcUserDoctrineORM.

Yes I want to do that migration :)

I created the repo for LmcUserDoctrineORM with an import of ZfcUserDoctrineORM so that is has the entire history, branches, etc. and assigned you to the Dev team for it.
I have no set opinion on whether to keep all the tags and branches since I do not use it.
We have not set a clear scheme on how to release the library once it is migrated. I did a major release for LmcRbacMVC. Others did a minor release. The important thing is to document the BC in namespaces and any configuration. For config, we use lmc_xxx as a key where xxx is the library name like lmc_user or lmc_rbac.
I would suggest to add test scripts if you can and some CI like Travis as well to CI-test any future pull requests.
When you are ready to publish to Packagist, let me know as I will have to create the package the first time and make you a maintainer.

Perfect, thank you I will inform you when I'm ready.
As there are so many changes I think if someone wants to use the "old" tags and versions, they will stick to the old repos with the old name. I guess the old tags/history doesn't make sense...
I'll have a look at the LmcRbacMVC and will document the BCs.
I have worked with Travis and so on a while ago but of course I'll implement the tests :)

@alexz707,
On the other topics, we have to keep in mind that we have many people using this library before we make changes to it.
On the factories issues, I also like to keep factories in the same folder as the class. At this point, there is no added value to changing that. I would wait for a major release to make that change as it introduces breaking change in namespaces forcing everyone to go through their code. Honestly, I don't know when or what would trigger a major release.
On the PSR-0 issue, I agree that we should upgrade to PSR-4. @matwright, Any thoughts?

Yes, I think that's a good idea. I'll can set up a new version dev branch for PSR-4 work and we can keep current version dev for any patches BC breaking updates. Would that work for you?

@visto9259
could you please set the default branch to master for the LmcUserDoctrineORM?
I have already pushed the changes to the master but can't set the default branch.
Thanks :)

@alexz707
Done.

@alexz707
Done.

Thanks - I think the Repos is ready for Packagist. :)

@alexz707,
On the other topics, we have to keep in mind that we have many people using this library before we make changes to it.
On the factories issues, I also like to keep factories in the same folder as the class. At this point, there is no added value to changing that. I would wait for a major release to make that change as it introduces breaking change in namespaces forcing everyone to go through their code. Honestly, I don't know when or what would trigger a major release.
On the PSR-0 issue, I agree that we should upgrade to PSR-4. @matwright, Any thoughts?

Yes, I think that's a good idea. I'll can set up a new version dev branch for PSR-4 work and we can keep current version dev for any patches BC breaking updates. Would that work for you?

@matwright that's a good idea. The PSR-4 change shouldn't break anything because it's just behind the namespaces...
If you are fine with it, I could just make a branch at my fork and push it when ready?

@alexz707
Packagist is set.  Added you as a maintainer.
Would not be a bad idea to remove older tags.

@alexz707
Packagist is set. Added you as a maintainer.
Would not be a bad idea to remove older tags.

@visto9259  Thanks a lot, already deleted the tags.

The latest PR's have been reviewed and merged into Master branch.
A pre-release v3.4.0 is ready for further testing.
This contains the module refactoring, php8 compat. and the Captcha functionality.


How do we increase the code font size

Hi! Try this one.

i didn't understand can you more elaborate on that.Where i need to pass the fontSize

By updating options, you can set it this way:
myOptions.withFormat(Format.Compact.copy(fontSize = 15f))

And don't forget to check your markup to be sure that isn't broken, because larger font size requires larger space between lines. Just play with other params in Format. Hope it helps!

codeView.setOptions(Options.Default.get(this)
.withLanguage("python")
.withCode(R.string.code5)
.withTheme(ColorTheme.MONOKAI)
.withFormat(Format.Compact.copy(fontSize=15f)));
after adding this m getting error
Error:(24, 35) error: Compact has private access in Format
Error:(24, 49) error: cannot find symbol variable fontSize

If you use it from Java, you should create the instance of Format class and provide several params:
codeView.setOptions(Options.Default.get(this)
    .withLanguage("python")
    .withCode(R.string.code5)
    .withTheme(ColorTheme.MONOKAI)
    .withFormat(new Format(
        1,    // scale factor
        18,   // line height
        3,    // border height
        15    // font size
    ));

It's a good catch! At this moment it is not so simple and convenient to create format this way in cause of interoperability with Kotlin data classes which represents Format. I will improve Java support in next release.
P.S. The preceding constants was taken from Format.Compact.

@MShamshuddeen @Rizwansyed9 That helped? Can I close the issue?

Yes, Thanks for your Time and support

So, i have added a button to zoom in,
but here is what happens on zooming in :
zoomIn.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                zoom++; //a variable to keep track of current zoom level
                mCodeView.setOptions(Options.Default.get(HomeActivity.this)
                        .withLanguage("c")
                        .withCode(currentCode)
                        .withFont(Font.Consolas)
                        .withFormat(new Format(
                                1,    // scale factor
                                (zoom+(int)(zoom*0.30)),   // line height
                                3,    // border height
                                zoom    // font size
                        ))
                        .withTheme(ColorTheme.MONOKAI));
            }
        });

but this refreshes the code, can't i just change the format without re-initializing the whole code in the code view ? is that possible ?


Undo-redo for images isn't guaranteed

Paste an image (clipboard, or upload from input in latest commit) and do undo-redo. After some number of iterations (usually first), image will not appear. Continue to do it; eventually it will reappear.
Issue is at least as old as 816493ca441995986651f2596678f606a9a061ab and occurs on CJ's demo too.
(@cjquines please put the commit hash as a comment in the hosted html file)

no idea what the demo's commit is, but i think it's later than the commit you mention.
i've never experienced this issue despite undoing and redoing several times, nor could i reproduce it? my first guess would be that the image's file url is being invalidated, but i'm not sure if that's why?

okay, can reproduce. my guess is that it's not rendering all after redoing. am investigating.


🍒 Cherry pick PR #11188 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/11188 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.2.4-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @luacmartins in version: 1.2.4-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.


cannot find the integration home-assistant

This might be a stupid question, but how can I find the integration in homeassistant? Tried Configuration -> Integrations -> Add -> Alpha ESS but it is not there. I tried to find it in hacs as well, no luck.

@CharlesGillanders Will you be progrssing with this.  I have a client that will be installing a Alpha ESS system later this year and would be willing to work with you on this once the install is running.

I am also interested in this. Do you need any help testing? I am trying to get details about the API, but no luck yet.

I haven't been able to find time to work on this for quite some time.  I too was unable to find any documentation on the API, however I was able to monitor the API calls made by a web browser accessing the Alpha ESS site and at least partially reverse engineer what the AlphaESS API does.
I've uploaded the work in progress which I have on the reverse engineered API.
There are methods to connect to AlphaESS, obtain a list of units registered to your credentials, and retrieve statistics from their web app for your unit(s)
My test script works enough at a command line to read those statistics for my Alpha unit but I obviously haven't been able to try this with anyone else.  Nor have I yet figured out how to make this integrate correctly with HomeAssistant so there's a considerable amount of work needed to be done to make this ready for use.

Thanks. It works. Only Load not getting a value, but I will check what the problem is. Im thinking of just making this a mqtt sensor to get the info into home assistant

I fixed the load problem, if you want to grab the latest version of the test harness.

@charlj22 MQTT works - then we can create a sensor for the energy dashboard

@johnjoemorgan I have forked this to add a MQTT component. It works and I can see the energy in Home Assistant. There is quite a few problems though. HA wants energy, not power, so I had to create a energy sensor for HA do get the data. HA also only do Home, Grid and Solar. No battery yet. The python program also stops and dont restart. Im not sure how to fix that. Maybe add logging to find the reason.

AlphaESS Web API V2.120210512004203.pdf
I found this documentation if its useful. I too would be interested in using this integration to track solar/battery data in home assistant.

Home Assistant has now updated to support the battery component, I am having a smile 5 in the next few weeks and keen to get this working to complete with the solar integration i have done already

If anyone is interested in trying this out in home assistant I have updated all of the code so it should now work as a custom component.  This is alpha quality code - I am running it myself in my own home assistant but I've only been able to test with my own system.

My system is booked to be installed on the 13th I will report back once it's connected and online

My system is booked to be installed on the 13th I will report back once it's connected and online

Excellent - thanks for this.

MY system won't be installed until the New Year.  Sorry can't be much help till then

Thank you very much for this excellent work. I have installed the component and it seems to be working well. The only slight oddity I've noticed so far is that Battery to Load (data["Ebat"]) doesn't seem to actually report the total battery discharge - unless I have misunderstood what this value is supposed to represent. I have the Smile B3 and it might be an issue with this system's reporting. As you can see, I have had some grid import overnight between 0100 and 0400 and the rest of the night was on stored energy. This is what is shown:

I have a request, would you please add the battery state of charge (data["Soc"]) as an additional sensor so that we can run automations based on Soc and the weather/solar forecast?

@dry Thank you so much for providing such useful feedback.  I will look to add the state of charge - the figure is in the API call that I am using but I took a shortcut with the current sensors by only gathering those that reported kWh so to gather SOC I'll need to fix that shortcut.  It will be better for the longer term to do this so best just to go ahead now!
As for the Ebat figure - that's what I thought that figure was meant to be but as we don't have any actual documentation for the Alpha ESS API it's a bit of a guess - If it's not reporting what I thought then I'll have to look elsewhere for that figure.

It may be that different system types report their settings differently. Do you have a Smile B3? I just realised that I can look back at the history of individual sensors and this graphic is the Battery to Load isolated. It was reporting a value when I first installed the component but, oddly, it was a decreasing value. I'm very new to HA so it may be that I don't have this setup correctly.

And I've just noticed this log entry:

And I've just noticed this log entry:

I've made some further updates - it now tracks three additional battery measurements - state of charge, charge, and discharge.
I've removed the previous battery to load sensor - it should be replaced with the new discharge sensor.
I am still not sure what is happening with solar to load - more investigation needed there.
Updating should be as simple as stopping home assistant, copying in the updated code and re-starting home assistant. Once started you will need to remove the old Battery to Load sensor from the entities page.

Thank you. I've updated and will report back when it's run for a few hours.

Hi.
I would like to say this integration is very useful to me so thank you for developing it.
Reviewing my setup with this integration I have noticed that the Solar to load appears to be the charge of the battery with a huge exception.
It can be seen that the value increases while the battery is being charged and decreases when the battery is used to supply power to the load.
However once you hit a new day it drops down to 0 and even when the battery starts to charge the value does not go up until it has charged a few kWh first.
This kind of looks like when a new day is hit the number becomes a negative of what ever is remaining and it shows anything as a negative as a 0.
I do not know enough about the programming to check if this is correct but that’s what the numbers look like.

I've run the latest version (0.0.2) for a full 24 hours now and it works really well in terms of the HA Energy tab. No issues that I can see. And thank you adding the Battery SoC, that works properly and should enable some great automations.

My Battery install has now been pushed out to early November due to stock issues. I will report back once i have it installed.
I did get the custom integration up and running(though not connected to anything) but noticed that it uses the cloud service. Any way to make this communicate directly communicate to the battery locally? Don't get me wrong i am super happy that you have developed this so feel free to tell me to go away!

@Ralphy140 - Sorry not at this time.  I did see that someone had figured out how to setup a fake local server which tricked the Alpha unit into uploading the figures to a local system instead of the cloud but that also disabled all updates from Alpha and of course breaks the vendor app etcetera.  I wanted a solution which allowed home assistant to run alongside the existing app rather than replace it so I focused on using the cloud API rather than the more problematic local server approach.

@CharlesGillanders, thank you for this great contribution.  Just to let you know, it seems to work fine for my Alpha ESS Smile 13.3 (at least over the last 24 hours since I got it running).   I will monitor it for a while and compare the readings to the UI and App to see if there are any issues.   I do note in the HA UI, that the Battery SOC does not show up in the default Lovelace config in the same “Location” as the rest of the energy sensors, but that isn’t a significant issue.   In looking to fix this, I found that if I open any of the sensors on the integration page the UI reports something like:
This entity ('sensor.al8001620080041_state_of_charge') does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.
Not sure if that is of concern or not.
Again, thank you so much for this :-)

sorry for pikcing up this old topic. I´m new to Home Assistant and want to connect the information of the Alpha Ess. I have made the folder in de custom_components. copied all the files into it. But at configuration - integrations - add integration I can´t find anything. What am I doing wrong ?

 Tried Configuration -> Integrations -> Add -> Alpha ESS but it is not there. I tried to find it in hacs as well, no luck.

did you got this working ?

you should have the files in a directory inside custom_components. If you then restart Homeassistant you should find alpha ess in configuration - >integrations.

you should have the files in a directory inside custom_components. If you then restart Homeassistant you should find alpha ess in configuration - >integrations. it worked for me.

I have created a folder alphaess in /root/config/custom_components
after I have copied all the folders and files into this directory
restarted Home Assistant
but when I go to configuration - devices|&services - integrations - add integration  I can´t find it

Sorry I am not more help then. Here's the files I have loaded on my homeassistant, and this was sufficient (after restart) to make the integration available. Sorry if it is an abvious suggestion, but you might want to check you have all these? Only other suggestion I have is to look at homeassistant log to see if an error is visible.

Sorry I am not more help then. Here's the files I have loaded on my homeassistant, and this was sufficient (after restart) to make the integration available. Sorry if it is an abvious suggestion, but you might want to check you have all these? Only other suggestion I have is to look at homeassistant log to see if an error is visible.

Ok, I´m missing some folders, they are not in the zip file

The pycache folder is created automatically by HomeAssistant when the integration is loaded and the .git folder is only there if you have pulled the integration through git rather than using the zip download.  You do need the translations folder though and that should be there when you unzip the master.zip file from github.

The pycache folder is created automatically by HomeAssistant when the integration is loaded and the .git folder is only there if you have pulled the integration through git rather than using the zip download. You do need the translations folder though and that should be there when you unzip the master.zip file from github.

thanks, then I have all teh correct files, but after restart i can´t find the integrations.  sorry for my noob questions. just started Ha yesterday, so a lot to figure out

anything appearing in the error log after you restart ?

just a warning
2022-01-06 13:19:33 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alphaess which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

I figured it out. the integration is now there and working :) coming from a knx this is something different but nice to figure out
thanks for all your help
now just find out to get all the information :)

Just in case it ends up helping someone else is there anything useful you can share about what you did to get it working?

HI All - Same problem as above.  Cant see to find the integration.  All the folders are correct and in the right place.  Appreciate the assist.  I do get a waring in the logfile:
2022-02-25 15:40:55 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alphaess which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

I also have the same error as Karl-Johns above
2022-07-04 22:26:36 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration alphaess which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
All folders are in the correct place, but cant find the integration :(


How can start in specific Progress Tab?

I want to start in a specific progress tab..
I try to call skip() method in for loop but it doesn't work..

@jjimenez0611
update to new version 3.0.0!
You can use startStories(int)

Thanks! I will use it.


driveshare-gui 0.4.2 not working on OS X

Installation of the OS X binary works but i can't start it. I get the following exception:
Uncaught Exception:
Error: Cannot find module 'electron-safe-ipc/host'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at EventEmitter. (/Users/skunk/Documents/driveshare-gui/build/main.js:13:13)
at emitOne (events.js:82:20)
at EventEmitter.emit (events.js:169:7)
Same problem if i run "npm start".

You are missing a dependency, try:
rm -r node_modules app/node_modules
npm install

I have the same problem.

@littleskunk when you built the release for OSX, I am guessing that a npm install was missed.

I reinstalled nodejs and build a new binary. This time the binary is fine. I don't know what the problem was but it should work now. I replaced the broken binary. Download it and try again.

Found the reason for the currupted binary. The curl upload is not working.


[WIP] chore: Refactor from Android Support Lib to Android X

Fixes #945
Changes:

Migrated from Android Support Lib to Android X

Not ready for review yet.
Screenshots for the change:

@Masquerade0097 Build will fail because Glide doesn't support the refactor. Let's leave the refactor for now. Move towards navigation component integration
Also create an issue for replacing Android Job with Work Manager


The App Name you entered has already been used.

New Issue Checklist

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

Issue Description
I am trying to deliver a new version of an existing app. The app is already created in iTunes Connect.
The error output is:
opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/spaceship/lib/spaceship/tunes/tunes_client.rb:223:in `handle_itc_response': [!] The request could not be completed because: (Spaceship::TunesClient::ITunesConnectError)
	The App Name you entered has already been used. The App Name you entered has already been used.

But there's no mention of what name it's trying to use? Why isn't it matching to to my existing app and trying to deliver a new version?
Complete output when running fastlane, including the stack trace and command used
bundle exec fastlane deliver --force true --verbose
Successfully loaded Appfile at path '/Users/me/Developer/app/app-ios/fastlane/Appfile'
- apple_id<EMAIL_ADDRESS>- team_id: 'XXXX'
- team_name: 'XXXX'
-------
INFO [2017-02-01 12:47:58.54]: Successfully loaded '/Users/me/Developer/app/app-ios/fastlane/Deliverfile' 📄
WARN [2017-02-01 12:47:58.54]: No values defined in './fastlane/Deliverfile'
INFO [2017-02-01 12:47:58.54]: Login to iTunes Connect<EMAIL_ADDRESS>Looking for iTunes Connect Team with ID XXXX
INFO [2017-02-01 12:48:00.86]: Login successful

+-----------------------+--------------------------------+
|                 deliver 2.13.0 Summary                 |
+-----------------------+--------------------------------+
| app_identifier        | com.XXXX.XXXX                  |
| app_version           | 1.0                            |
| team_id               | XXXX                           |
| force                 | true                           |
| screenshots_path      | ./fastlane/screenshots         |
| metadata_path         | ./fastlane/metadata            |
| username              |<EMAIL_ADDRESS>               |
| edit_live             | false                          |
| ipa                   | app.ipa                        |
| platform              | ios                            |
| skip_binary_upload    | false                          |
| skip_screenshots      | false                          |
| skip_metadata         | false                          |
| submit_for_review     | false                          |
| automatic_release     | false                          |
| dev_portal_team_id    | XXXX                           |
| dev_portal_team_name  | XXXX                           |
| overwrite_screenshots | false                          |
+-----------------------+--------------------------------+

INFO [2017-02-01 12:48:01.42]: Making sure the latest version on iTunes Connect matches '1.0' from the ipa file...
INFO [2017-02-01 12:48:02.44]: '1.0' is the latest version on iTunes Connect
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/description.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/keywords.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/release_notes.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/support_url.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/name.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/copyright.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/primary_category.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/secondary_category.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
INFO [2017-02-01 12:48:02.44]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
INFO [2017-02-01 12:48:03.19]: Activating language en-US...
INFO [2017-02-01 12:48:05.72]: Uploading metadata to iTunes Connect

Looking for related GitHub issues on fastlane/fastlane...
Search query: The request could not be completed because:
	The App Name you entered has already been used. The App Name you entered has already been used.

URL: https://api.github.com/search/issues?q=The%20request%20could%20not%20be%20completed%20because:%0A%09The%20App%20Name%20you%20entered%20has%20already%20been%20used.%20The%20App%20Name%20you%20entered%20has%20already%20been%20used.+repo:fastlane/fastlane
➡  Unable to create an app on itunes connect via spaceship or produce.  Error: The App Name you entered has already been used
   https://github.com/fastlane/fastlane/issues/5102 [closed] 10 💬
   4 weeks ago

➡  Error finding relevant GitHub issues: undefined method `map' for nil:NilClass
   https://github.com/fastlane/fastlane/issues/7274 [closed] 4 💬
   02 Dec 2016

➡  Produce failing to create app in iTunesConnect
   https://github.com/fastlane/fastlane/issues/5728 [closed] 11 💬
   01 Dec 2016

and 2 more at: https://github.com/fastlane/fastlane/search?q=The%20request%20could%20not%20be%20completed%20because:%0A%09The%20App%20Name%20you%20entered%20has%20already%20been%20used.%20The%20App%20Name%20you%20entered%20has%20already%20been%20used.&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.
/opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/spaceship/lib/spaceship/tunes/tunes_client.rb:223:in `handle_itc_response': [!] The request could not be completed because: (Spaceship::TunesClient::ITunesConnectError)
	The App Name you entered has already been used. The App Name you entered has already been used.
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/spaceship/lib/spaceship/tunes/tunes_client.rb:255:in `update_app_details!'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/spaceship/lib/spaceship/tunes/app_details.rb:75:in `save!'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/upload_metadata.rb:86:in `upload'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/runner.rb:62:in `upload_metadata'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/runner.rb:21:in `run'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/commands_generator.rb:62:in `block (2 levels) in run'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/commander-4.4.3/lib/commander/command.rb:153:in `run'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/commander-4.4.3/lib/commander/runner.rb:446:in `run_active_command'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/commander-4.4.3/lib/commander/delegates.rb:15:in `run!'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/commands_generator.rb:148:in `run'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/deliver/lib/deliver/commands_generator.rb:12:in `start'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/fastlane/lib/fastlane/cli_tools_distributor.rb:45:in `take_off'
	from /opt/local/lib/ruby2.2/gems/2.2.0/gems/fastlane-2.13.0/bin/fastlane:15:in `<top (required)>'
	from /opt/local/bin/fastlane:23:in `load'
	from /opt/local/bin/fastlane:23:in `<main>'

Environment
Captured Output
Command Used: env
Output/Log

Successfully loaded Appfile at path '/Users/me/Developer/XXXX/XXXX-ios/fastlane/Appfile'
- apple_id<EMAIL_ADDRESS>- team_id: 'XXXX'
- team_name: 'XXXX'
-------
INFO [2017-02-01 13:04:13.24]: Successfully loaded custom action '/Users/me/Developer/XXXX/XXXX-ios/fastlane/actions/app_name.rb'.
INFO [2017-02-01 13:04:13.24]: Successfully loaded custom action '/Users/me/Developer/XXXX/XXXX-ios/fastlane/actions/build_number_icon.rb'.
INFO [2017-02-01 13:04:13.24]: Successfully loaded custom action '/Users/me/Developer/XXXX/XXXX-ios/fastlane/actions/color_icon.rb'.
WARN [2017-02-01 13:04:13.25]: Generating fastlane environment output, this might take a few seconds...
DEBUG [2017-02-01 13:04:14.18]: Checking if there are any plugins that should be loaded...

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.2.6

Bundler?
true

Git
git version 2.11.0

Installation Source
/opt/local/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/opt/local/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

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

Xcode Version
8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

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

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

# By default, fastlane will send which actions are used
# No personal data is shared, more information on https://github.com/fastlane/enhancer
# Uncomment the following line to opt out
# opt_out_usage

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

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

default_platform :ios

platform :ios do

  before_all do
    # Environemnt variables are set using gem dotenv and .env.default. If multiple environments are
    # needed, you can run fastlane with the --env environment_name to load .env.environment_name
    # instead of .env.default.

    # In addition to the .env.* method of loading environment variables, we also load a local 'keys'
    # file, if it exists. This is a standard ruby file and can be used to keep passwords outside of
    # the git repo. See fastlane/keys.template for an example.
    load_keys
  end

  # After all steps have completed successfully, run this
  after_all do |lane|
    # This block is called, only if the executed lane was successful
    # slack(
    #   message: "Successfully deployed new App Update."
    # )
    if ENV["SLACK_URL"]
      slack(
        message: "lane executed successfully",
        success: true,
        default_payloads: [:test_result, :git_branch]
      )
    else
      notify("Lane #{lane} completed successfully!")
    end
    #clean_build_artifacts
  end

  # If there was an error, run this
  error do |lane, exception|
    if ENV["SLACK_URL"]
      slack(
        message: exception.to_s,
        success: false
      )
    else
      notify("Lane #{lane} failed to complete.")
    end
    #clean_build_artifacts
  end

  desc "Install pod dependencies"
  lane :install_pods do
    cocoapods
  end

  # https://github.com/FixIssue/FixCode
  # Xcode 8+ no longer loads unsigned plugins; therefore this project is deprecated.
  #/*
  # # Run this lane on your development machine once
  # desc "Installs FixCode which disables the \"Fix Issue\" button in Xcode"
  # lane :xcode do
  #   install_xcode_plugin(
  #     url: "https://github.com/fastlane/FixCode/releases/download/0.2.0/FixCode.xcplugin.zip"
  #   )
  # end
  #*/

  #### Apple Member Center ####

  desc "Produces all used App IDs and provision services"
  lane :prod do
    produce(app_identifier: 'com.XXXX.XXXX.debug', app_name: 'XXXX Debug', skip_itc: true)
    produce(app_identifier: 'com.XXXX.XXXX.alpha', app_name: 'XXXX Alpha', skip_itc: true)
    produce(app_identifier: 'com.XXXX.XXXX.beta', app_name: 'XXXX Beta', skip_itc: true)
	produce(app_identifier: 'com.XXXX.XXXX', app_name: 'XXXX', skip_itc: true)
    sh "produce group -g group.com.XXXX.XXXX"
    sh "produce enable_services -a com.XXXX.XXXX --app-group"
    sh "produce associate_group -a com.XXXX.XXXX group.com.XXXX.XXXX"
    sh "produce enable_services -a com.XXXX.XXXX.debug --app-group"
    sh "produce associate_group -a com.XXXX.XXXX.debug group.com.XXXX.XXXX"
    sh "produce enable_services -a com.XXXX.XXXX.alpha --app-group"
    sh "produce associate_group -a com.XXXX.XXXX.alpha group.com.XXXX.XXXX"
    sh "produce enable_services -a com.XXXX.XXXX.beta --app-group"
    sh "produce associate_group -a com.XXXX.XXXX.beta group.com.XXXX.XXXX"
  end

  # Run this lane on your development machine once.
  desc "Fetches certificates and provisioning profiles so you can build locally and deploy to your device"
  lane :certs do
    match(app_identifier: "com.XXXX.XXXX.debug", type: "development")
    match(app_identifier: "com.XXXX.XXXX.alpha", type: "adhoc")
    match(app_identifier: "com.XXXX.XXXX.beta", type: "adhoc")
    match(app_identifier: "com.XXXX.XXXX", type: "appstore")
  end

  desc "Runs all the tests"
  lane :test do
    return if test_disabled?
    scan
  end

  desc "Create new screenshots for the App Store in all languages and device types; additionally, this will add device frames around the screenshots and add the correct titles"
  lane :screenshots do
    match(app_identifier: "com.XXXX.XXXX", type: "development")
    snapshot(reinstall_app: true)
    frameit(white: true, path: './fastlane/screenshots')
  end

  desc "Uploads metadata only - no ipa file will be uploaded - You'll get a summary of the collected metadata before it's uploaded"
  lane :upload_metadata do
    deliver(metadata_only: true)
  end

  private_lane :build_app do |options|

    # This part is done only when the app is not for the "production" environment
    if not options[:release]
      # Modulate the color of the icons
      color_icon(
        modulation: "#{options[:modulation]}"
      )
      # Add the build number to the icon
      build_number_icon
    end

    # Update the app name
    app_name(
      plist_path: "#{options[:project_name]}/Info.plist",
      app_name: options[:app_name]
    )

    # Update the app identifier
    update_app_identifier(
      xcodeproj: "#{options[:project_name]}.xcodeproj",
      plist_path: "#{options[:project_name]}/Info.plist",
      app_identifier: CredentialsManager::AppfileConfig.try_fetch_value(:app_identifier)
    )

    # Update app group identifiers
    # update_app_group_identifiers(
    #   entitlements_file: "#{options[:project_name]}/XXXX.entitlements",
    #   app_group_identifiers: ["group.com.XXXX.XXXX#{options[:app_identifier_suffix]}"]
    # )

    # Install the certificate and provisioning profiles
    match(
      app_identifier: CredentialsManager::AppfileConfig.try_fetch_value(:app_identifier),
      force_for_new_devices: true,
      type: options[:match_type]
    )

    # Version bump
    increment_build_number(
      build_number: options[:build_number],
      xcodeproj: "#{options[:project_name]}.xcodeproj"
    )

    # Build the app
    gym(
      scheme: "#{options[:scheme]}",
      configuration: options[:configuration],
      #provisioning_profile_path: options[:profile],
      codesigning_identity: options[:codesigning_identity],
      export_method: options[:export_method],
    )

  end

  # Publish to Testflight
  private_lane :publish_testflight do |options|

    # Generate a changelog with GIT since the last successful build in Jenkins
    changelog = sh("git log --graph --pretty=format:'%h -%d %s <%an>' --abbrev-commit #{ENV['GIT_PREVIOUS_SUCCESSFUL_COMMIT'] || 'HEAD^^^^^'}..HEAD")

    # Send the app to Testflight
    pilot(
      changelog: "#{changelog.to_s}",
      skip_submission: false,
      distribute_external: true,
      beta_app_feedback_email<EMAIL_ADDRESS>      beta_app_description: "This is the beta release of the XXXX iOS App",
    )
  end

  # Publish to Crashlytics
  private_lane :publish_fabric do |options|

    changelog = options[:changelog]
    if changelog.to_s == ''
      # Generate a changelog with GIT since the last successful build in Jenkins
      changelog = sh("git log --graph --pretty=format:'%h -%d %s <%an>' --abbrev-commit #{ENV['GIT_PREVIOUS_SUCCESSFUL_COMMIT'] || 'HEAD^^^^^'}..HEAD")
    end
    # Send the app to Crashlytics
    crashlytics(
      api_token: ENV["CRASHLYTICS_API_TOKEN"],
      build_secret: ENV["CRASHLYTICS_BUILD_SECRET"],
      notes: "#{changelog.to_s}",
      groups: "#{options[:groups]}",
      notifications: true,
      debug: options[:debug]
    )
  end

  # Publish to the AppStore
  private_lane :publish_appstore do |options|
    deliver(force: true)
  end

  desc "Build and publish an Alpha version to Fabric."
  lane :alpha_fabric do
    build_app(
      release:false,
      modulation:66.6,
      app_name:"XXXX α",
      app_identifier_suffix:".alpha",
      match_type:"adhoc",
      configuration:"Alpha",
      codesigning_identity:"iPhone Distribution: XXXX",
      export_method:"ad-hoc",
      project_name:"XXXX",
      scheme:"XXXX",
      build_number: ENV["BUILD_NUMBER"]
    )
    publish_fabric(
      debug:true,
      groups:"alphagroup",
    )
  end

  desc "Build and publish the Beta version to Fabric"
  lane :beta_fabric do
    build_app(
      release:false,
      modulation:166.6,
      app_name:"XXXX β",
      app_identifier_suffix:".beta",
      match_type:"adhoc",
      configuration:"Beta",
      codesigning_identity:"iPhone Distribution: XXXX",
      export_method:"ad-hoc",
      project_name:"XXXX",
      scheme:"XXXX",
      build_number: ENV["BUILD_NUMBER"]
    )
    publish_fabric(
      debug:true,
      groups:"betagroup",
      changelog: changelog_from_git_commits(commits_count: 1, pretty: '%h - %d %s')
    )
  end

  desc "Build and publish the Release version to the AppStore"
  lane :release_appstore do
    build_app(
      release:true,
      app_name:"XXXX",
      app_identifier_suffix:"",
      match_type:"appstore",
      configuration:"Release",
      codesigning_identity:"iPhone Distribution: XXXX",
      export_method:"app-store",
      project_name:"XXXX",
      scheme:"XXXX Release",
      build_number: ENV["BUILD_NUMBER"]
    )
    publish_fabric(
      debug:false,
      groups:"releasegroup"
    )
    publish_appstore
  end

end

def compare_url
  last_bump_hash = sh("cd ../;git log --pretty=format:'%s %h' | grep -i '^version bump [0-9]\\{12\\}\\b' | awk '{print $NF}' | head -n1").strip
  current_hash = sh("git rev-parse HEAD").strip
  "http://gitlab.XXXX.com/XXXX/XXXX-ios/compare?from=#{last_bump_hash}&to=#{current_hash}"
end

def change_log_since_last_tag
  # http://git-scm.com/docs/pretty-formats
  # <short hash> <commit title>
  return changelog_from_git_commits(pretty: '%h %s')
end

def version_string(version_number, build_number)
  "#{version_number} (#{build_number})"
end

def tag_name(build_type, version_number, build_number)
  "#{build_type}/#{version_number}/#{build_number}"
end

def load_keys
  begin
    import("keys")
  rescue => exception
    UI.important("fastlane/keys file not found. To use this Fastfile, copy fastlane/keys.template into fastlane/keys and fill in the values")
    #raise exception
  end
end

`./fastlane/Appfile`
# More information: https://github.com/fastlane/fastlane/blob/master/docs/Appfile.md

apple_id<EMAIL_ADDRESS>team_id "XXXX"  # Developer Portal Team ID
team_name "XXXX"
for_platform :ios do
	app_identifier "com.XXXX.XXXX"
	for_lane :alpha_fabric do
	  app_identifier "com.XXXX.XXXX.alpha"
	end
	for_lane :beta_fabric do
	  app_identifier "com.XXXX.XXXX.beta"
	end
	for_lane :release_appstore do
	  app_identifier "com.XXXX.XXXX"
	end
end

fastlane gems

Gem
Version
Update-Status

fastlane
2.13.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

i18n
0.8.0

json
1.8.6

minitest
5.10.1

thread_safe
0.3.5

tzinfo
1.2.2

activesupport
<IP_ADDRESS>

public_suffix
2.0.5

addressable
2.5.0

babosa
1.0.2

bundler
1.13.6

claide
1.0.1

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.2.0

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.7.8

cocoapods-trunk
1.1.2

cocoapods-try
1.1.0

colored
1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.5

ruby-macho
0.2.6

nanaimo
0.2.3

xcodeproj
1.4.2

cocoapods
1.2.0

highline
1.7.8

commander
4.4.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

dotenv
2.2.0

excon
0.54.0

multipart-post
2.0.0

faraday
0.11.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.0.1

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

hurley
0.2

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.0.15

representable
2.3.0

retriable
2.1.0

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.2.0

rubyzip
1.2.0

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

word_wrap
1.0.0

rouge
1.11.1

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

Delivering the ipa via Application Loader worked just fine. Not sure why fastlane deliver isn't working.

@parleer application loader does not update metadata, fastlane/deliver does.
can you check your name.txt inside your metadata folder (in each language) - to see if it might have changed to a name, that is already taken.
alternatively you could download the current metadata, to ensure you are in sync with your store entry.
fastlane deliver download_metadata

please backup all stuff, as it will overwrite things in fastlane/metadata

@hjanuschka that worked...almost...now getting the following Transporter Error, but it's no longer complaining about the app name:

[15:23:13]: Making sure the latest version on iTunes Connect matches '1.0' from the ipa file...
[15:23:14]: '1.0' is the latest version on iTunes Connect
[15:23:14]: Loading './fastlane/metadata/en-US/description.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/keywords.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/release_notes.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/support_url.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/name.txt'...
[15:23:14]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
[15:23:14]: Loading './fastlane/metadata/copyright.txt'...
[15:23:14]: Loading './fastlane/metadata/primary_category.txt'...
[15:23:14]: Loading './fastlane/metadata/secondary_category.txt'...
[15:23:14]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[15:23:14]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[15:23:14]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[15:23:14]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[15:23:15]: Activating language en-US...
[15:23:18]: Uploading metadata to iTunes Connect
[15:23:20]: Successfully uploaded set of metadata to iTunes Connect
[15:23:21]: Starting with the upload of screenshots...
[15:23:21]: Successfully uploaded screenshots to iTunes Connect
[15:23:23]: Uploading binary to iTunes Connect
[15:23:23]: Going to upload updated app to iTunes Connect
[15:23:23]: This might take a few minutes. Please don't interrupt the script.
[15:24:40]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:25:24]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:26:12]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:27:14]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:28:28]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:29:42]: [Transporter Error Output]: An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
[15:29:42]: [Transporter Error Output]: An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
[15:29:42]: [Transporter Error Output]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
[15:29:42]: [Transporter Error Output]: The max number of retries was performed. The package will not be uploaded.
[15:29:43]: Transporter transfer failed.
[15:29:43]:
[15:29:43]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The max number of retries was performed. The package will not be uploaded.
[15:29:43]: The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
An exception has occurred: Warning: The same packet was resent too many times without acknowledgement.
The file, 9c6ad7a314053838fda15665f237b04f.ipa, did not complete its upload.
The max number of retries was performed. The package will not be uploaded.
\nThe max number of retries was performed. The package will not be uploaded.d.s without acknowledgement.ete its upload.
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

I seem to remember dealing with this Transporter error on the last app I created, but can't remember how to resolve it; I think it may have just went away on it's own... strange that publishing to Crashlytics never has these type of transport issues...

This looks like a different error, can you submit a separate issue for this? Are you behind a proxy?

I'll mark this as closed and open another issue if the Transporter error continues.


[main] Upgrade to latest dependencies

Release 1.4 deps upgrade -ikvmw
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing 1b90ef3...39eef14:
  > 39eef14 upgrade to latest dependencies (# 6341)
  > 073af74 Ensure the clean up will remove installed elements (# 6338)
  > ff55a45 Fix for pod overcommit by one in HA Scheduler (# 6322)
  > 5bb50cb Allow adapter/v2 based components to use ConfigMapWatcher (# 6086)
  > d14dc09 upgrade to latest dependencies (# 6327)
  > 6d61534 Update actions (# 6328)
  > 76ce7e4 Cleanup Zipkin tracing only once in upgrade test suite (# 6331)

/lgtm
/approve


Update etcd.md

try to fix this

This is not the correct fix.
Please remove the {{< glossary ... shortcode from line 21 in content/zh/docs/tasks/administer-cluster/configure-upgrade-etcd.md. That shortcode still works even if inside a HTML comment.
/hold


update samples for vega support

closing this since PR #108 fixes by modifying hipcc.

Agree the hipcc mod is a better fix.
From: Maneesh Gupta<EMAIL_ADDRESS>Sent: Monday, July 24, 2017 4:25 AM
To: ROCm-Developer-Tools/HIP<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [ROCm-Developer-Tools/HIP] update samples for vega support (#104)
closing this since PR #108https://github.com/ROCm-Developer-Tools/HIP/pull/108 fixes by modifying hipcc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ROCm-Developer-Tools/HIP/pull/104#issuecomment-317367633, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACYSAibxWgzeF_7_tRNLDnwK6wiPbtjLks5sRGLbgaJpZM4ObJrB.

As these samples are used as "the way to be use hip", I think we should merge these changes.

@adityaatluri: I don't think making all HIP samples build fat binaries is the right way. We could change one samples to build as fatbin to demonstrate how to do it.

Agree
From: Maneesh Gupta<EMAIL_ADDRESS>Reply-To: ROCm-Developer-Tools/HIP<EMAIL_ADDRESS>Date: Monday, July 31, 2017 at 10:18 PM
To: ROCm-Developer-Tools/HIP<EMAIL_ADDRESS>Cc: Benjamin Sander<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [ROCm-Developer-Tools/HIP] update samples for vega support (#104)
@adityaatlurihttps://github.com/adityaatluri: I don't think making all HIP samples build fat binaries is the right way. We could change one samples to build as fatbin to demonstrate how to do it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/ROCm-Developer-Tools/HIP/pull/104#issuecomment-319256579, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACYSAnuzuZ7xGh_6ngdvxQvssXM2KA4Zks5sTpkhgaJpZM4ObJrB.


Should we allow publishing a null price feed?

The question is whether we should ever allow publishing a null price feed.  I think the answer is "no" and will add checks to explicitly enforce this as part of the hardfork for #357.

No


chore: fix circleCI conf

Latest semantic-release upgrade requires the release branches to be listed in an array.
Currently builds fail with
[1:08:27 PM] [semantic-release] › ✖  ERELEASEBRANCHES The release branches are invalid in the `branches` configuration.
A minimum of 1 and a maximum of 3 release branches are required in the branches configuration (https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#branches).

This may occur if your repository does not have a release branch, such as master.

Your configuration for the problematic branches is [].

This PR should fix it.
Signed-off-by: Maria Paktiti<EMAIL_ADDRESS>

:tada: This PR is included in version 1.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


keyFile Location

Hi,
I'm running my server on a Mac, so the pi directory in the config doesn't exist.  Is it possible to make that log file location adjustable so for other platforms?
Thanks,
Eric

Hi,
you can just set the keyFile directory to whatever you want. The directory in the in the README is just an example.

Got it - thanks.  I didn’t try it because of the “Don't specify a directory or you'll get an EISDIR error.” line in the end me.


Look for index.html in subfolders as well

If not found in subfolder -> 404 not found

Not going to fix. Accessing a subfolder returns 'Not Allowed'


[AIRFLOW-1203] Pin Google API client version to fix OAuth issue

Removing tests since they're broken. They're attempting to connect to Google BigQuery, but aren't properly mocking.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #2296   +/-   ##
=========================================
  Coverage          ?   69.12%
=========================================
  Files             ?      144
  Lines             ?    11023
  Branches          ?        0
=========================================
  Hits              ?     7620
  Misses            ?     3403
  Partials          ?        0

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 0da540b...41d0ecb. Read the comment docs.

Lgtm


Language Server Client should not be created for specific language

It's nonsense.
FYI: https://langserver.org/

Why LSP?
LSP creates the opportunity to reduce the m-times-n complexity problem of providing a high level of support for any programming language in any editor, IDE, or client endpoint to a simpler m-plus-n problem.

We should focus on making generic clients and language servers better.
Our resources are not infinite.

Hi @kyoh86 - what are you specifically commenting on?
Command github.com/myitcv/govim/cmd/govim (referred to simply as govim) is a Go development plugin for Vim8. It is backed by gopls, the Language Server Protocol server for Go.
Package github.com/myitcv/govim provides an API for plugin developers to interface with Vim8 in Go.
As such, I don't (currently) have it as a specific goal to provide a generic LSP client in the github.com/myitcv/govim/... modules/packages.
https://godoc.org/golang.org/x/tools/internal/lsp might become such a client when it possibly is "released" from being internal. That is being tracked by https://github.com/golang/go/issues/31080

@myitcv
I'm sorry I didn't make it clear enough.
I'm thinking in the following way.

We can use generic LSC (Language Server Client) plugins like vim-lsp, vim-lsc, etc.
And plugins for each languages should leave functions as a LSC to them.

Conversely, they should have functions which make up for LSC

Otherwise, we cannot reduce the m-times-n complexity problem.
I'm given to understand that Language Server Protocol is solution for the problem.
Langserver.org says:

The problem: "The Matrix"

Go
Java
TypeScript
...

Emacs

Vim

VSCode

...

The solution: lang servers and clients

Language
Server

Go

Java

TypeScript

...

Editor
Client

Emacs

Vim

VSCode

...

@kyoh86 thanks for providing more detail. I think it depends what you are trying to solve for.
What are you trying to do right now that:

can't be done in Vim?
can't be done with a plugin written in VimScript?
can't be done with a github.com/myitcv/govim-based plugin written in Go?
can't be done with the github.com/myitcv/govim/cmd/govim Go development plugin?

My guess, given that we're having this discussion in the context of a Go-based plugin, is that you're actually looking for something between 3 and 4, say 3.5. Specifically, an LSP client, written against github.com/myitcv/govim that provides some sort of API to a Vim user.
To be honest, I don't know what that API should look like, hence I've effectively started by solving this in reverse by creating github.com/myitcv/govim/cmd/govim as a Go development plugin.
Now it's entirely possible that something generic and useful is produced in the process of continued development of github.com/myitcv/govim/cmd/govim.
So, long story short: I'm not entirely clear what goal you're trying to solve, but equally I'm not averse to a generic LSP client plugin "something" for Vim; it's just that I don't know what that looks like yet. So I'm starting with a specific goal of github.com/myitcv/govim/cmd/govim and seeing where that takes me.

I'm going to close this issue on the basis I think it is well addressed in the FAQ (and its various links). Please say if you disagree.


[5.1 06-12-2019][CodeCompleiton] Don't hide members for unresolved base types

Cherry-pick of #25574 into swift-5.1-branch-06-12-2019

Explanation: Previously, if the type has constrained generic parameters, initializer call pattern completion (e.g. TypeName(#HERE#) used to not work without explicit generic arguments TypeName<Int>(#HERE# because the generic parameters are unresolved. This patch fixes the issue by not hiding members for type with unresolved types.
Scope: Code completion for initializer call pattern.  And qualified member list
Issue: rdar://problem/49480808
Risk: Low
Testing: Added regression tests
Reviewer: Ben Langmuir (@benlangmuir)

@swift-ci Please test

@swift-ci Please nominate

Build failed
Swift Test Linux Platform
Git Sha - 891eba7e31016a04aefdb0ba109e900e713538c8

@swift-ci Please test Linux platform


[hmac, rtl] Minor HMAC fixes

This PR includes two changes:

Add endianness option to KEY register. Current implementation is hardcoded for big endian which does not match Ibex's endianness. https://github.com/lowRISC/opentitan/issues/23158#issuecomment-2120138498
I encountered a bug that specifically prevents reloading context for 384 and 512-bit variants. Namely, SW cannot correctly set DIGEST registers during context reloading, because both 32-bit words of 64-bit sha_word is reloaded with the same copy. I tested this fix with my driver implementation.

Thanks @ballifatih for the fixes, glad to have the digest reloading for SHA-2 384/512 tested and ironed out, this LGTM! As for the key endianness swap change, I also think we hold back on this for now, as I mention here https://github.com/lowRISC/opentitan/issues/23158 and Martin as well. The DV to test the new features is yet to stabilize and this would break DV and require a lot more adaptations. We can introduce a dedicated swap and choose to test it later.

Thanks @martin-velay and @gdessouky. I dropped the endianness change commit so that it can be further discussed and decided in the main issue #https://github.com/lowRISC/opentitan/issues/23158. I also made the nit changes for the other changes (mostly visual alignment around assignments).

Thx @ballifatih, I agree that the digest reloading fix is more urgent than supporting key endianness swapping, which we can do in a later PR. I took the liberty to edit the title and description of this PR. I'll review it

Closing as relevant changes are added in https://github.com/lowRISC/opentitan/pull/23236.
I was able to run drivers on top of this change, but I will try with #23236.


autogenerate enum validation methods

What do you want to change?
The codegen for enums generates a list of constants containing valid values:
type EnumType string

const (
	EnumTypeA EnumType = "A"
	EnumTypeB EnumType = "B"
)

When writing developer tools, it can be helpful to convert from a string value to an enum type. However, there is no exhaustive list of valid enum values, so we have to wait until a query fails to discover that an invalid enum value has been provided.
I'd like the codegen to also emit something like:
func (e EnumType) Valid() bool {
  switch e {
  case EnumTypeA, EnumTypeB:
    return true
  default:
    return false
  }
}

Then I can convert from string to enum type and check valid early on.
I know that this applies to PostgreSQL and Go. I'm not sure about MySQL and the other languages.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go

On a related note, I find myself wanting to be able to list all available enum values.

I have definitely opened a ticket for this previously, probably at least a
year ago, agree it would be a good feature
On Wed, May 11, 2022 at 11:19 Josh Bleecher Snyder @.***>
wrote:

On a related note, I find myself wanting to be able to list all available
enum values.
—
Reply to this email directly, view it on GitHub
https://github.com/kyleconroy/sqlc/issues/1607#issuecomment-1124143479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AML53FNE33JXEDCEZBJZC5DVJP22BANCNFSM5VST2BLA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Kevin Burke
phone:<PHONE_NUMBER> | kevin.burke.dev

The fix was easy: https://github.com/kyleconroy/sqlc/pull/1613. Feedback welcome.
I hope we can get it reviewed.

Ah, previously here: https://github.com/kyleconroy/sqlc/issues/447
I still think this is a good idea.


about the CSS selector：ChildText

func (*HTMLElement) ChildText
func (h *HTMLElement) ChildText(goquerySelector string) string
ChildText returns the concatenated and stripped text content of the matching elements.
how can i  get the first  elements
eg:

testonetesttwo

if i use the ChildText, i will get the  "testone testtwo ",but i only want to get the first the elements "testone", now i use the strings.Split to get it.
but, is there others way to solve it?
thx.

Hmm can you use .foo > span as a selector?

@vosmith  , i had use it, but i can't get only the testone,  .foo > span  will get the  "testonetesttwo ", the ChildText will get the all ,not the first

use .foo > span:first-child if you only want testone.  Let me know if it works!

@vosmith ， Wow，cool.
.foo > span:first-child  this way is ok.
thank you so much! 👍

testonetesttwo

What about this example?
Sorry to barge in here after so much time has passed on from this issue.