Connection refused

I used the docker run command and get this:

2023-08-30 21:12:36 Level: 4 primes: 16  ok Time: 0.000006
2023-08-30 21:12:36 Level: 5 primes: 32  ok Time: 0.000002
2023-08-30 21:12:36 Level: 6 primes: 64  ok Time: 0.000003
2023-08-30 21:12:36 Level: 7 primes: 128  ok Time: 0.000002
2023-08-30 21:12:36 Level: 8 primes: 256  ok Time: 0.000005
2023-08-30 21:12:36 Level: 9 primes: 512  ok Time: 0.000005
2023-08-30 21:12:36 Level: 10 primes: 1024  ok Time: 0.000004
2023-08-30 21:12:36 Level: 11 primes: 2048  ok Time: 0.000008
2023-08-30 21:12:36 Level: 12 primes: 4096  ok Time: 0.000019
2023-08-30 21:12:36 Level: 13 primes: 8192  ok Time: 0.000038
2023-08-30 21:12:36 Level: 14 primes: 16384  ok Time: 0.000075
2023-08-30 21:12:36 Level: 15 primes: 32768  ok Time: 0.000174
2023-08-30 21:12:36 Level: 16 primes: 65536  ok Time: 0.000438
2023-08-30 21:12:36 Level: 17 primes: 131072  ok Time: 0.001132
2023-08-30 21:12:36 Level: 18 primes: 262144  ok Time: 0.002829
2023-08-30 21:12:36 Level: 19 primes: 524288  ok Time: 0.006860
2023-08-30 21:12:36 Level: 20 primes: 1048576  ok Time: 0.016285
2023-08-30 21:12:36 Level: 21 primes: 2097152  ok Time: 0.037373
2023-08-30 21:12:36 Level: 22 primes: 4194304  ok Time: 0.086988
2023-08-30 21:12:36 Level: 23 primes: 8388608  ok Time: 0.213693
2023-08-30 21:12:37 Level: 24 primes: 16777216  ok Time: 0.482845
2023-08-30 21:12:38 Level: 25 primes: 33554432  ok Time: 1.141875
2023-08-30 21:12:40 Level: 26 primes: 67108864  ok Time: 2.632199
2023-08-30 21:12:46 Level: 27 primes: 134217728  ok Time: 5.845222
2023-08-30 21:12:46 [+] SCRIPTPUBKEY: 0014673b05596068ab95e101b4a8e091cef2b2e411b9
2023-08-30 21:12:46 Traceback (most recent call last):
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 1348, in do_open
2023-08-30 21:12:46     h.request(req.get_method(), req.selector, req.data, headers,
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 1283, in request
2023-08-30 21:12:46     self._send_request(method, url, body, headers, encode_chunked)
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 1329, in _send_request
2023-08-30 21:12:46     self.endheaders(body, encode_chunked=encode_chunked)
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 1278, in endheaders
2023-08-30 21:12:46     self._send_output(message_body, encode_chunked=encode_chunked)
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 1038, in _send_output
2023-08-30 21:12:46     self.send(msg)
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 976, in send
2023-08-30 21:12:46     self.connect()
2023-08-30 21:12:46   File "/usr/lib/python3.10/http/client.py", line 942, in connect
2023-08-30 21:12:46     self.sock = self._create_connection(
2023-08-30 21:12:46   File "/usr/lib/python3.10/socket.py", line 845, in create_connection
2023-08-30 21:12:46     raise err
2023-08-30 21:12:46   File "/usr/lib/python3.10/socket.py", line 833, in create_connection
2023-08-30 21:12:46     sock.connect(sa)
2023-08-30 21:12:46 ConnectionRefusedError: [Errno 111] Connection refused
2023-08-30 21:12:46
2023-08-30 21:12:46 During handling of the above exception, another exception occurred:
2023-08-30 21:12:46
2023-08-30 21:12:46 Traceback (most recent call last):
2023-08-30 21:12:46   File "/tmp/factoring/python/FACTOR.py", line 56, in
2023-08-30 21:12:46     mine()
2023-08-30 21:12:46   File "/tmp/factoring/python/FACTOR.py", line 51, in mine
2023-08-30 21:12:46     if B.mine( mine_latest_block = True, scriptPubKey = SCRIPTPUBKEY ):
2023-08-30 21:12:46   File "/tmp/factoring/python/lib/blockchain.py", line 234, in mine
2023-08-30 21:12:46     block = self.get_next_block_to_work_on()
2023-08-30 21:12:46   File "/tmp/factoring/python/lib/blockchain.py", line 79, in get_next_block_to_work_on
2023-08-30 21:12:46     blocktemplate      = rpc_getblocktemplate()
2023-08-30 21:12:46   File "/tmp/factoring/python/lib/rpc.py", line 50, in rpc_getblocktemplate
2023-08-30 21:12:46     return rpc("getblocktemplate", [{"rules": ["segwit"]}])
2023-08-30 21:12:46   File "/tmp/factoring/python/lib/rpc.py", line 33, in rpc
2023-08-30 21:12:46     with urllib.request.urlopen(request) as f:
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
2023-08-30 21:12:46     return opener.open(url, data, timeout)
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 519, in open
2023-08-30 21:12:46     response = self._open(req, data)
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 536, in _open
2023-08-30 21:12:46     result = self._call_chain(self.handle_open, protocol, protocol +
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain
2023-08-30 21:12:46     result = func(*args)
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 1377, in http_open
2023-08-30 21:12:46     return self.do_open(http.client.HTTPConnection, req)
2023-08-30 21:12:46   File "/usr/lib/python3.10/urllib/request.py", line 1351, in do_open
2023-08-30 21:12:46     raise URLError(err)
2023-08-30 21:12:46 urllib.error.URLError: <urlopen error [Errno 111] Connection refused>

I'm running Docker using WSL and I'm running the node on the same computer in WSL with Ubuntu. I see no option to specify an RPC IP address or port, so I have no idea what it's trying to connect to.

I have similar issue but you seem to get further mine crashes out here:
Level: 4 primes: 16  ok Time: 0.000007 Level: 5 primes: 32  ok Time: 0.000004 Level: 6 primes: 64  ok Time: 0.000002 Level: 7 primes: 128  ok Time: 0.000002 Level: 8 primes: 256  ok Time: 0.000014 Level: 9 primes: 512  ok Time: 0.000003 Level: 10 primes: 1024  ok Time: 0.000005 Level: 11 primes: 2048  ok Time: 0.000010 Level: 12 primes: 4096  ok Time: 0.000019 Level: 13 primes: 8192  ok Time: 0.000036 Level: 14 primes: 16384  ok Time: 0.000086 Level: 15 primes: 32768  ok Time: 0.000236 Level: 16 primes: 65536  ok Time: 0.000587 Level: 17 primes: 131072  ok Time: 0.001570 Level: 18 primes: 262144  ok Time: 0.004230 Level: 19 primes: 524288  ok Time: 0.010466 Level: 20 primes: 1048576  ok Time: 0.035068 Level: 21 primes: 2097152  ok Time: 0.099717 Level: 22 primes: 4194304  ok Time: 0.141856 Level: 23 primes: 8388608  ok Time: 0.318544 Level: 24 primes: 16777216  ok Time: 0.739152 Level: 25 primes: 33554432  ok Time: 1.724480 Level: 26 primes: 67108864  ok Time: 4.047787 Level: 27 primes: 134217728  ok Time: 9.547775 [+] SCRIPTPUBKEY: 00141fa5c697f2e0c9469ccfa288b8dac3867896accf Traceback (most recent call last):   File "/tmp/factoring/python/FACTOR.py", line 56, in <module>     mine()   File "/tmp/factoring/python/FACTOR.py", line 51, in mine     if B.mine( mine_latest_block = True, scriptPubKey = SCRIPTPUBKEY ):   File "/tmp/factoring/python/lib/blockchain.py", line 235, in mine     block = self.get_next_block_to_work_on()   File "/tmp/factoring/python/lib/blockchain.py", line 80, in get_next_block_to_work_on     blocktemplate      = rpc_getblocktemplate()   File "/tmp/factoring/python/lib/rpc.py", line 48, in rpc_getblocktemplate     return rpc("getblocktemplate", [{"rules": ["segwit"]}])   File "/tmp/factoring/python/lib/rpc.py", line 33, in rpc     with urllib.request.urlopen(request) as f:   File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen     return opener.open(url, data, timeout)   File "/usr/lib/python3.10/urllib/request.py", line 525, in open     response = meth(req, response)   File "/usr/lib/python3.10/urllib/request.py", line 634, in http_response     response = self.parent.error(   File "/usr/lib/python3.10/urllib/request.py", line 563, in error     return self._call_chain(*args)   File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain     result = func(*args)   File "/usr/lib/python3.10/urllib/request.py", line 643, in http_error_default     raise HTTPError(req.full_url, code, msg, hdrs, fp) urllib.error.HTTPError: HTTP Error 401: Unauthorized

The first issue is a network issue. I don't use WSL on Windows so I cannot help you there. Folks in the Discord have solved this before though. They can help. The second issue is a credentials problem. Follow the instructions. Create the config file and follow the rest and it will get fixed.


Incomplete migration of Custom view: Few are migrated and others are failing

Hi Team,
We were trying to migrate only custom views related to a particular dashboard. We wrote a filter to filter out only those views in that workbook. Some views got migrated and others did not. We are getting error:
`{
"ClassName": "System.Net.Http.HttpRequestException",
"Exception": {
"Message": "Response status code does not indicate success: 404 (Not Found).",
"Type": "System.Net.Http.HttpRequestException",
"Source": "System.Net.Http",
"StackTrace": "   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()\n   at Tableau.Migration.Net.DefaultHttpResponseMessage.EnsureSuccessStatusCode()\n   at Tableau.Migration.Api.IHttpResponseMessageExtensions.DownloadResultAsync(Task1 getResponseAsync, CancellationToken cancel)",
"HelpLink": null,
"HResult": -2146233088
}
}
]
},
`
It would be great if someone could help me why this error is occurring and how to fix it.

Thank you for this bug report.
We have noticed this internally as well and we're working understanding the issue.

Hey Team, any update on why the issue is happening?

This was a bug in Tableau Server. Upgrading to the latest version will fix this.


Release notes for v3.0.0-alpha

Description
3.0.0-alpha release notes. Prior to merging, the component versions will need to be finalized (currently using strikethrough to denote this).
Todos

[ ] Finalize component versions in _data/versions.yml

Release Note

None required

Yep, 147 chicken-or-egg htmlproofer failures! All for v3.0 urls.


Migration from Teslalogger

Is there a way to import data from Teslalogger?

Afaik there is not enough demand for this feature. But maybe someone is willing to work on it and can contribute it. I'll move this to 💡 Ideas.


msal library breaks angular translations

Hi,
I have an angular 10 application, that uses ng translate, and lately, I have integrated with msal module, and strangely ng translate breaks, and if this known issue and fix is there?
import { BrowserModule } from '@angular/platform-browser';
import { NgModule, CUSTOM_ELEMENTS_SCHEMA, ErrorHandler } from '@angular/core';

import { ReactiveFormsModule } from '@angular/forms';
import {
  HttpClientModule,
  HttpClient,
  HTTP_INTERCEPTORS,
} from '@angular/common/http';
import { HttpConfigInterceptor } from './shared/http-interceptor';

import { TranslateModule, TranslateLoader } from '@ngx-translate/core';
import { TranslateHttpLoader } from '@ngx-translate/http-loader';

import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { ServiceWorkerModule } from '@angular/service-worker';
import { environment } from '../environments/environment';
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
import { MsalApplicationModule } from './msal.module';

export function createTranslateLoader(http: HttpClient) {
  return new TranslateHttpLoader(http, './assets/i18n/', '.json');
}

@NgModule({
  declarations: [AppComponent],
  imports: [
    BrowserModule,
    MaterialModule,
    TranslateModule.forRoot({
      loader: {
        provide: TranslateLoader,
        useFactory: createTranslateLoader,
        deps: [HttpClient]
      }
    }),
    AppRoutingModule,
    ReactiveFormsModule,
    HttpClientModule,
    ServiceWorkerModule.register('ngsw-worker.js', {
      enabled: environment.production,
    }),
    BrowserAnimationsModule,
    MsalApplicationModule,
  ],
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  providers: [],
  bootstrap: [AppComponent],
})
export class AppModule { }

package.json:
"@azure/msal-angular": "^1.1.2",
  "msal": "^1.4.4",

and for MsalApplicationModule i used the same code example
const isIE = window.navigator.userAgent.indexOf('MSIE ') > -1 || window.navigator.userAgent.indexOf('Trident/') > -1;
@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    AppRoutingModule,
    MsalModule.forRoot({
      auth: {
        clientId: 'Enter_the_Application_Id_here', // This is your client ID
        authority: 'Enter_the_Cloud_Instance_Id_Here'/'Enter_the_Tenant_Info_Here', // This is your tenant ID
        redirectUri: 'Enter_the_Redirect_Uri_Here'// This is your redirect URI
      },
      cache: {
        cacheLocation: 'localStorage',
        storeAuthStateInCookie: isIE, // Set to true for Internet Explorer 11
      },
    }, {
      popUp: !isIE,
      consentScopes: [
        'user.read',
        'openid',
        'profile',
      ],
      unprotectedResources: [],
      protectedResourceMap: [
        ['https://graph.microsoft.com/v1.0/me', ['user.read']]
      ],
      extraQueryParameters: {}
    })
  ],
  providers: [],
  bootstrap: [AppComponent]
})

@satyavanu Please see this comment for how to mitigate this issue: #2515 (comment).
Also, in the future, please use one of our pre-configured issue templates, thanks!

@satyavanu Please see this comment for how to mitigate this issue: #2515 (comment).
Also, in the future, please use one of our pre-configured issue templates, thanks!

@jo-arroyo  that's very confusing. you have const protectedResourceMap: [string, string[]][] and you are passing   ["/assets/i18n/*.json", null] on #2515 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/2515#issuecomment-727108424.  the tying is wrong, and next this is still not working, does latest msal support ng translate ?

@jo-arroyo  that's very confusing. you have const protectedResourceMap: [string, string[]][] and you are passing   ["/assets/i18n/*.json", null] on #2515 https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/2515#issuecomment-727108424.  the tying is wrong, and next this is still not working, does latest msal support ng translate ?

@satyavanu Have you tried without the leading slash, i.e. ["assets/i18n/*.json", null] ?
In regards to typing, do you have strict null checks on in your tsconfig?
Please also consider upgrading to @azure/msal-angular@2, where we don't expect this to be an issue anymore.

@satyavanu Have you tried without the leading slash, i.e. ["assets/i18n/*.json", null] ?
In regards to typing, do you have strict null checks on in your tsconfig?
Please also consider upgrading to @azure/msal-angular@2, where we don't expect this to be an issue anymore.


Write a C# program to print pattern 1

Description
Write a C# program to print pattern 1
Input  : 5

Output :
1
1 2
1 2 3
1 2 3 4
1 2 3 4 5

Contributed by - @PraaneshSelvaraj

How to contribute

Save the solution in program/PrintPattern1.cs file
Add PrintPattern1.cs file in print-pattern-1 folder

!assign

I have created a PR #7155 kindly review.


$stateParams and $state.params discrepancy

See the following plunkr: http://plnkr.co/edit/4lNF02CEcwXDOQDPfoMd?p=preview
When navigating to the specified child state (either via $state.go or via ui-sref, both are demonstrated) there is a visible discrepancy between the contents of $stateParams and $state.params.
The $stateParams object lacks some parameters, which are present in $state.params.
This can't be the intended behavior, since the child state is loaded and it should contain the child state specific parameter in $stateParams which is given.

Same as #136

There is a new duplicate of this #2076.

https://gist.github.com/eddiemonge/f6a58169c2846731a1eb

This is still affecting me in the latest 0.2.15 with angular 1.4.3
http://plnkr.co/edit/4lNF02CEcwXDOQDPfoMd?p=preview


BUG: Check for overflow in TimedeltaIndex addition.

Title is self-explanatory.  Closes #14068.

There is a similar bug for adding TimedeltaIndex and similar time delta objects with each other.  I will add this as a separate commit but wanted to make sure my patch for the original issue passes.

There is a similar bug for adding TimedeltaIndex and similar time delta objects with each other.  I will add this as a separate commit but wanted to make sure my patch for the original issue passes.
The slightly tricky part for this patch is how we check for overflow.  For example, if we look at this function here, we replace certain elements with tslib.iNaT.  Should we check for overflow in the locations where they are supposed to be tslib.iNaT?  Or ignore them?

Current coverage is 85.24% (diff: 66.66%)

Merging #14237 into master will increase coverage by <.01%

@@             master     #14237   diff @@
==========================================
  Files           140        140
  Lines         50559      50562     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43099      43102     +3
  Misses         7460       7460
  Partials          0          0

Powered by Codecov. Last update 5e2f9da...2078ca0

Yes, Period, Timedelta and Timestamp are always backed by a int64_t
value.
On Mon, Sep 19, 2016 at 9:43 AM, gfyoung<EMAIL_ADDRESS>wrote:

@gfyoung commented on this pull request.
In pandas/tseries/tdi.py https://github.com/pydata/pandas/pull/14237:

@@ -344,6 +344,17 @@ def _add_datelike(self, other):
other = Timestamp(other)
i8 = self.asi8
result = i8 + other.value

       # gh-14068: there is the possibility of addition overflow,

       # which occurs when we add two very large positive numbers,

       # resulting in a negative number.

       #

       # Since Timestamp objects can never have a negative value,

       # we just need to check that the elements in result are also

       # nonnegative when their corresponding elements in i8 are.

       for x, y in zip(i8, result):

Ah, fair enough. BTW, is it fair to assume that all integers are int64_t
and just check for int64 overflow?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pydata/pandas/pull/14237, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1b_KjV1qiCg6QPdGQt65b3AayiTozxks5qrp-LgaJpZM4J_QBW
.

@chris-b1 : Added the algos implementation for _checked_add, and Travis + Appveyor are happy.

@gfyoung It seems to me that in your test you are only checking Timedelta + Timestamp, but those already error on overflow now. Shouldn't you check for the TimedeltaIndex case ?
Further, can you show a perf comparison?

I don't think cython is needed here
In [11]: arr = pd.to_datetime([0,np.iinfo(np.int64).max-1,pd.lib.iNaT])

In [12]: arr
Out[12]: DatetimeIndex(['1970-01-01 00:00:00', '2262-04-11 23:47:16.854775806', 'NaT'], dtype='datetime64[ns]', freq=None)

In [13]: arr = pd.to_datetime([0,np.iinfo(np.int64).max-1,pd.lib.iNaT]).asi8

In [14]: arr
Out[14]: array([                   0,<PHONE_NUMBER>854775806, -9223372036854775808])

In [15]: arr+10
Out[15]: array([                  10, -9223372036854775800, -9223372036854775798])

In [16]: ((arr+10) < 0) & (arr != pd.lib.iNaT)
Out[16]: array([False,  True, False], dtype=bool)

@jreback IIUC [15] is technically undefined behavior  (sign int overflow in C) - although maybe all the compilers python is built on wrap like that?

@chris-b1 I am not sure.
cc @charris
@shoyer
any idea if this is always true?

This is safe here
In [25]: ((np.iinfo(np.int64).max-arr+10) > 0) & (arr != pd.lib.iNaT)
Out[25]: array([False,  True, False], dtype=bool)

@jorisvandenbossche : Perf comparison of what exactly?

Perf comparison of what exactly?

Before/after of such a TimedeltaIndex addition (as the checking will give a certain overhead)

@jreback : BTW, I think @chris-b1 suggested Cython for perf reasons, not for correctness (that was assumed) IIUC.

I think the check that you do in the cython code (np.iinfo(np.int64).max - b < a) can also be done vectorized in plain numpy? (instead of the looping you had initially) In that case cython is maybe indeed not needed.

@jorisvandenbossche : Writing it in Cython should provide a perf boost (we know the data types).  However, your point about vectorization is well taken and would take care of some of the issues addressed by @chris-b1 .

@jorisvandenbossche :
In [1]: import pandas as pd
In [2]: import numpy as np
In [3]: arr = np.arange(1000000)
In [4]: td = pd.to_timedelta(arr)
In [5]: ts = pd.Timestamp('2000')
In [6]: %timeit -n 1000 ts + td

master: 1000 loops, best of 3: 1.92 ms per loop
PR: 1000 loops, best of 3: 2.09 ms per loop

Cython doesn't really make sense with the current implementation, because you can do this with vectorized NumPy functions already. In the current implementation it's entirely pointless because you're just calling Python methods/functions. If you need the loop, then yes, you should go for Cython.

@shoyer : IIUC, I think your understanding of "current implementation" is a little dated.

@gfyoung Nope, every line in your current Cython code is calling back to Python in order to use NumPy:
def _checked_add_arr_scalar(ndarray[int64_t] arr, int64_t b):
    if (np.iinfo(np.int64).max - b < arr).any():  # vectorized arithmetic, numpy.ndarray.any
         raise OverflowError("Python int too large to "
                            "convert to C long")
     return arr + b  # more vectorized arithmetic

You could do most of this from NumPy's C-API by calling functions like PyArray_Any but that would be pretty pointless.

@shoyer :  Fair enough.  But then again, placing it in algos.pyx seems logical for the time being.  Also, the speed-up from using types couldn't hurt as I said.

Why don't you benchmark the function written in Cython vs pure Python so you can see for yourself?
Using Cython makes code harder to debug/introspect/maintain. We should only use it when it makes a meaningful difference for performance (this is a subjective standard).

@shoyer : Fair enough.  But in the meantime, a suggestion of where to this function would be useful.

@gfyoung as I have said several times, just use the simple numpy construct from above. no reason to code bloat this by doing it in cython. If there is a demonstrated perf gain, then pls show it. but I don't think you can beat numpy here.

@jreback : I would like to abstract the checking into a separate function because there are other places that patching too as I mentioned above.  @chris-b1 suggested I put the code in algos.pyx, so where would you put it then if not there?

@gfyoung sure make a function. But it should doesn't need to be in cython. prob in core/nanops

Sorry, if I sent you down a wrong path, I only meant that to the extent this was impl using an explicit loop that would benefit from cython.
Can you double check your timings (maybe didn't rebuild?) - that overhead seems too small and some local timing suggests so too.
arr = np.arange(1000000)
td = pd.to_timedelta(arr)
ts = pd.Timestamp('2000')

%%timeit
td + ts
100 loops, best of 3: 2.71 ms per loop

%%timeit
(np.iinfo(np.int64).max - ts.value < td.asi8).any()
td + ts
100 loops, best of 3: 3.52 ms per loop

Moved the checked add method to nanops as @jreback suggested.  Travis and Appveyor seem to be happy with this change.

@gfyoung IIRC there was another place in the code where this was needed? (or at least that's what you said)?

@jreback : You are correct.  However, I think I would prefer to submit those changes in a separate PR just because the actual fix for this one hasn't been fully agreed upon and would impact how I fix the other one.

We don't need to do TDI or DTI specifically
why is this ?

In [8]: m = np.iinfo(np.int64).max

In [10]: pd.to_datetime(np.arange(m-5,m-1))
Out[10]: DatetimeIndex(['2262-04-11 23:47:16.854775802', '2262-04-11 23:47:16.854775803', '2262-04-11 23:47:16.854775804', '2262-04-11 23:47:16.854775805'], dtype='datetime64[ns]', freq=None)

In [11]: pd.to_datetime(np.arange(m-5,m-1)) + pd.to_timedelta([10]*4,unit='ns')
Out[11]: DatetimeIndex(['2262-04-10 00:12:43.145224196', '2262-04-10 00:12:43.145224197', '2262-04-10 00:12:43.145224198', '2262-04-10 00:12:43.145224199'], dtype='datetime64[ns]', freq='N')

doesn't seem correct to me

@jreback : The add handling varies from data type to data type as you can see here.  This PR only addresses this branch here.

this needs to be s comprehensive tested fix in a single PR not sure why this is a big deal to do

@jreback : Look at how much debate we had over how we should do the checked adding.  If people are okay with how it is implemented, then sure.  But missing consensus here.

no reason for the debate

thanks @gfyoung
can you open another issue to cover the other cases (e.g. tdi + tdi, dti + tdi)

@jreback : I just realized that there is a bug in the _checked_add_with_arr:
>>> import numpy as np
>>> a = np.array([1])
>>> b = np.array([np.iinfo(np.int64).min])
>>> nanops._checked_add_with_arr(a, b)   # Should not break.
...
OverflowError: Python int too large to convert to C long

And how about the case with mixed overflows:
>>> import numpy as np
>>> a = np.array([1, 1])
>>> b = np.array([np.iinfo(np.int64).min, np.iinfo(np.int64).max])
>>> nanops._checked_add_with_arr(a, b)  # How to pinpoint which one is overflowing?
...
OverflowError: Python int too large to convert to C long

Sidenote - that error message should probably be something more descriptive, as it isn't really an issue converting a Python int to C.  How about instead something like:
OverflowError("{klass} addition would overflow".format(...))?

@chris-b1 : The reason I went for that error message is for API consistency with already existing overflow errors, which you can see in the original issue.

@jreback , @jorisvandenbossche , @chris-b1 : Any ideas about how to patch the bug I mentioned above?

You would add a > 0 guard, like this;
(b > 0) & ((np.iinfo(np.int64).max - b) > a)

http://stackoverflow.com/questions/199333/how-to-detect-integer-overflow-in-c-c

@chris-b1 : Consider the case where b = np.array([1, -1]).  Unless you are suggesting to this element by element?  Then that would make more sense.

> will broadcast, so yes, it is element by element

And as you're looking at this, my opinion is still think the error message should be changed to accurately describe what's happening.  Error messages are more documentation than API, so no need to use the same message as other overflows.

@chris-b1 : Let's table the error message for now.  I'm trying to focus on patching this bug first.  Your answer above about broadcasting doesn't quite answer my question.  I'm trying to point out that your check for > 0 is insufficient unless we decide to explicitly loop through element by element.

I'm not following you on the element-by-element (this is element by element), but I did have a comparison backwards, should be:
(b > 0) & ((np.iinfo(np.int64).max - b) < a)
Note this won't catch underflows, that check would be:
(b < 0) & ((np.iinfo(np.int64).min - b) > a)

@chris-b1 : My point is the following: is a and b in your code scalars ONLY?  Because I'm almost certain that first check will fail if b is an array.

How about you try it?  with broadcasting it will work with any combo of arrays/scalars.

@chris-b1 : I already did.  It doesn't work.  You can't boolean check against a numpy array.

@gfyoung Can you give a reproducible example that does not work?

@jorisvandenbossche :
>>> import pandas.core.nanops as nanops
>>> import numpy as np
>>>
>>> a = np.array([1])
>>> b = np.array([np.iinfo(np.int64).min)])
>>> nanops._checked_add_with(a, b)  # Should not fail.
...
OverflowError: ...

This is one of several ways to break the current implementation.

The suggestion of @chris-b1 of above works fine on this example:
In [19]: (b > 0) & ((np.iinfo(np.int64).max - b) < a)
Out[19]: array([False], dtype=bool)

@jorisvandenbossche : True, but you have to also check for overflow in the opposite direction as well i.e. what happens if you add np.iinfo(np.int64).min to itself?  The current check that you provided by itself will not work.

Yes, but you asked about broadcasting / loop element by element. I am just saying that the example code of @chris-b1 works fine for scalars/arrays. But apart from that, it is indeed true that making the check comprehensive for all cases will include several checks.
And of course that will impact the performance ...

@jorisvandenbossche : Fair enough.  I will put up a PR to separately patch this first.


Version conflicts with hydra-core

  Using cached audiolm_pytorch-1.2.12-py3-none-any.whl (39 kB)
ERROR: Cannot install -r requirements.txt (line 12) and -r requirements.txt (line 27) because these package versions have conflicting dependencies.

The conflict is caused by:
    fairseq 0.12.2 depends on hydra-core<1.1 and >=1.0.7
    audiocraft 0.0.2a2 depends on hydra-core>=1.1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

If I do not use fairseq 0.12.2 it fails due to https://github.com/facebookresearch/fairseq/issues/4501.

Actually I think fairseq is the least maintained here, and there's an old PR for fairseq that suggests a hydra-core<=1.1 compatibility. I install fairseq as if it was 1.1 compatible.
And hydra-core is guilty of having an utterly breaking API between version 1.0 and 1.1 ...

pip uninstall fairseq
git clone https://github.com/pytorch/fairseq
cd fairseq
edit setup.py file
change             "hydra-core>=1.0.7,<1.1",  >>   "hydra-core>=1.1,<1.1",
save file
pip install --editable ./

This did the trick:
pip uninstall fairseq
pip install hydra-core==1.1.0
Change setup.py:
    install_requires=[
        "cffi",
        "cython",
>>   "hydra-core>1.0.7",
>>   "omegaconf>2.0",

pip install --editable ./


Service Request by Monika "The C2 strategy shows all red marks under specification status as if no info was entered???"

[ ] Qualtrics Service Request Form was received from User
[ ] e-mail acknowledging that User's Qualtrics Service Request Form was sent
[ ] Problem NOT RESOLVED
[ ] Problem PARTIALLY RESOLVED
[ ] Problem FULLY RESOLVED and Issue is Closed
[ ] Qualtrics Post-Service Request Survey was sent to User

Use comments feature (below) to document:

A clear and concise description of the solution.

A clear and concise description of any alternative solutions or features you've considered.

Any additional context, such as screenshots about the problem.

From: Donrie Purcell<EMAIL_ADDRESS>Date: Wednesday, September 22, 2021 at 4:08 PM
To<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: FW: The C2 strategy shows all red marks under specification status as if no info was entered???
Hi Monika
Also, remember to click the Save All button, it helps to do this after you’ve selected the completed box.
Regards
Donrie
From: Donrie Purcell<EMAIL_ADDRESS>Date: Wednesday, September 22, 2021 at 4:03 PM
To<EMAIL_ADDRESS><EMAIL_ADDRESS>Cc: david lounsbury<EMAIL_ADDRESS>Subject: The C2 strategy shows all red marks under specification status as if no info was entered???
Hi Monika
Please don’t forget to highlight/tick the completed space.
And everything will be ok, thereafter…

Regards
Donrie Purcell, PhD, MPH
Every generation has the obligation to free men's minds for a look at new worlds,....to look out from a higher plateau than the last generation.
Ellison S. Onizuka
CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and/or privileged information. Any duplication, copying, distribution, dissemination, transmission, disclosure or use in any manner of this email (including any attachments) without the authorization of the sender is strictly prohibited. If you receive this email (including any attachments) in error, please notify the sender and delete this email (including any attachments) from your system. Thank you.


Support custom labels and badge styles. Add License. Upgrade and Remove unused dependencies.

Live Demo
Deployed on render.com free tier.

Proposed Changes

Support custom labels and badge styles, similar to what shields.io offers.

Made possible by replacing badge crate with rsbadges crate (BSD 3-Clause License).
The new crate supports badge logos, but I'd consider it out of scope for now.

Add Apache and MIT Licenses. Addresses #103
Add some files to gitignore based on standard Rust gitignore template.
Upgrade and Remove unused dependencies.

GitHub actions and earthly versions bumped to latest
Rust version upgraded to 2021
Cargo dependencies bumped.
Unused Cargo dependencies removed to reduce compilation time (sidenote: long compiliation time was causing builds to fail on render.com free tier, this may not be an issue on other hosting platforms)

Known issues
Getting 403 errors with ghcr.io
In deploy.yml, sometimes the default ${{ secrets.GITHUB_TOKEN }} may not work well with ghcr.io.
A workaround would be to create and use a GitHub Personal Access Token with write:packages access enabled, no expiry date, and add it to this repository (e.g. ${{ secrets.PERSONAL_ACCESS_TOKEN }}).

Thank you for your PR, and congrats on your first contribution! 🎉


Milestone Report - Evaluation of Deliverables - Mockups

TODOS:

Add an evaluation text for Mockups of the project.

Wrote the evaluation text of mock-ups.

Completed the implementation of mock-ups to milestone report.


How to call one effect multiple times in parallel

Code to reproduce the issue: (请提供可复现的代码或者步骤)
I prepared a simple scenario to describe my issue. Please see the code below:
export default {
    effects: {
        *getFriend({ id }, { call, put }) {
            const response = yield call(api.friendRequest, id)

            yield put({
                type: 'updateFriend',
                payload: { id, friend: response.data }
            });

        },
        *getAllFriends(_, { select, all, put }) {
            const friendIdList = select(({ friendIdList }) => friendIdList);
            yield all( friendIdList.map( friendId =>
                put({'getFriend', {id: friendId})}
            ));

            yield put({
              type: 'allFriendsRequestSuccess',
            });
        }
    }
}

Suppose I call dispatch({type: 'foo/getAllFriends'})
Expected behavior: (预期的正常效果)
I would expect allFriendsRequestSuccess action to be dispatched after all requests inside getFriend are done.
Actual behavior: (实际效果)
However, put is non-blocking, so I will have allFriendsRequestSuccess instantly, not after all tasks end.
Versions of packages used: (哪个库的哪个版本出现的问题)

export default {
    effects: {
        *getFriend({ id }, { call, put }) {
            const response = yield call(api.friendRequest, id)

            yield put({
                type: 'updateFriend',
                payload: { id, friend: response.data }
            });
        },
        *getAllFriends(_, { select, all, put }) {
            const friendIdList = select(({ friendIdList }) => friendIdList);
            const friends = yield all( friendIdList.map( friendId =>
                call(api.friendRequest, friendId)
            ));

            yield put({
                type: 'allFriendsRequestSuccess',
                payload: { friends }
            });
        }
    }
}

Thanks again @nihgwu but this is a bit different what I wanted because sometimes getFriend function can be more complicated. With this way, I'll have a duplicated code. Here is what I came up:

function* getFriend({ id }, { call, put }) {
  const response = yield call(api.friendRequest, id)

  yield put({
    type: 'updateFriend',
    payload: { id, friend: response.data }
  });
}

export default {
    effects: {
        getFriend,
        *getAllFriends(_, { select, all, put }) {
            const friendIdList = select(({ friendIdList }) => friendIdList);
            yield all( friendIdList.map( friendId =>
                call(getFriend, { id: friendId }, {call, put});
            ));

            yield put({
              type: 'allFriendsRequestSuccess',
            });
        }
    }
}

This is still not a good solution but at least I don't repeat myself, I wonder if there is a better way though.

I would write a friendService to make the api request, then call it in effects


Precision Issues With Small Primitives

This issue stems from the following community forum thread: https://community.cesium.com/t/bug-bad-precision-on-0-01-meter-sphere/15050
CesiumJS struggles to render very small primitives. While this behavior can be seen on laptops and desktops, it appears to be more prominent on iOS mobile devices. On an iOS device, we begin to see issues when viewing spheres that have a radius of one meter. I have not tested to see if this issue occurs on android smartphones or tablets of any kind.

Here is a video demo that I put together.
https://youtu.be/UZBvFOZwQ-4
This issue could potentially be related to highp or lowp settings in the glsl shaders. GPU precision could also play a role here. I understand that sandcastle was created as a development tool. Regardless, the sandcastle experience on mobile devices is not great.
Sandcastle example: https://sandcastle.cesium.com/#c=bZBNb8IwDIb/itVTkbqUauzSFTTBuCHtsI9TLqE1LFoSV0laBBP/fWk7BmIokhXb7/NadisstBJ3aGEKBnewQCcbzT76Wsyjss8XZLyQBi2PRo/ccNMGbq0aXCola0eyCvjgw9B46SU6Jqoq/uYGwAiNOfBoHgDAE8GjpGvW5IKcTH4avRDWh58w92xjST/j1iK6+C7LJmycwGTcxYcQRz3/55dDPwzAikrK/HKbs2WcJeENJIAWHq0U6jybFFk2X70ve8UxxOPvwsNyByL9RvHVqoMkSqLC+b3C2eAO8CR1TdZDY1XMWOpR1yqMdOm6Kb/Qs9L1aCct0ku0qGQLspreuD+USjgXOptGqVd5QB7NijTo/6GKwiHM9qVFq8S+k31ms9VQZIwVaUhvk55IrYW9cv4B
Browser: Chrome, Safari
Operating System: iOS, Windows, Linux
@ebogo1

One additional note: If the sphere is created as a glTF model and added to the scene, we get flawless performance and no jitter in the geometry or positioning.


How to enjoy Cosmic Background?

When I go to settings to choose between backgrounds, I do't have default Cosmic bg, I can choose a "color" background or one of my pictures but there is not official cosmic bg available.

I don't believe the official background are packaged, but you can download them from https://github.com/pop-os/cosmic-wallpapers/tree/master/original and
https://github.com/pop-os/wallpapers/tree/master/original.

Some work is needed to get upstream cosmic-bg stuff to work with backgrounds from XDG_DATA_DIRS instead of just hardcoding /usr/share/backgrounds

For now, Settings > Desktop > Wallpaper > Open New Folder click the path edit button, paste `


Old version on screenshot

The screenshot after the language menu says iot-sensor-10.5 instead of the latest one 22.x
https://docs.microsoft.com/en-us/azure/defender-for-iot/organizations/media/tutorial-install-components/sensor-architecture.png

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02235a4d-2df4-9a39-6d37-9dd6f3b68acf
Version Independent ID: be6053d0-6fe5-504d-6a0a-642cefa53d35
Content: Defender for IoT installation - Microsoft Defender for IoT
Content Source: articles/defender-for-iot/organizations/how-to-install-software.md
Service: defender-for-iot
GitHub Login: @batamig
Microsoft Alias: bagol

@guarismo
Thanks for your feedback! We will investigate and update as appropriate.

Hi @guarismo, thanks for sending your feedback into docs!
These screenshots are meant to be examples, and we have work planned in our backlog to bring them all up to date.
To prevent double-tracking, I'm going to close this issue for now, but feel free to continue commenting as needed.
We appreciate your contributions to docs!
#please-close


Sean/feat: pnl margin calculator

Changes:

Add pnl calculators

Type of change

[ ] Bug fix
[x] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

LineHeight of the paragraph text is 24px according to zeplin


Get rid of redundant facet check on app engine local run

This check is not needed because the facet is already confirmed prior to adding it to the target deployable dropdown (if it didn't have this facet, it would not have shown up in the dropdown to begin with):

So in case we don't have this facet, we won't have this (implied) drop down, but just an error message - Artifact isn't specified, correct?

correct

So if I try to add an App Engine Standard target when project is App Engine Flex, it gives me empty drop-down for Artifact and Artifact isn't specified error. Is it clear enough to suggest what I did wrong here? Maybe expand that error a bit to make it easier to understand what is Artifact in this case and how to fix it?

Yeah good idea. The usually is generally steered away from opening a local dev server run config for flex (they are blocked from the tools menu shortcut, and it shows up as hidden by default when manually adding the run config), but some detailed wording here is a good idea. I'll add it.

@ivanporty @patflynn
Added some guiding wording:

On second look. Maybe I'll add something about requiring exploded-war artifacts too.

Updated the wording and added some line breaks. let me know what you think.

screenshot above is updated to reflect all the wording changes

That's awesome, would be really helpful for a confused user!


chore: Remove all Jest snapshotting

Description
Remove all Jest snapshotting.

When we started out building out our e2e testing, we said we would slowly remove all the Jest snapshotting as we go. Whilst our e2e test coverage will continue to grow, its getting to the point where our snapshots are causing more hassle than help. I can't remember when a snapshot test has saved me from doing something wrong, whilst on the other hand every time we update kongponents (probably once a week) we have to update all the snapshots as a separate PR before we can approve and merge the kongponents upgrade. I think possibly "don't test what you don't own" is an apt phrase here.
We should just go through our remaining Jest tests and remove all the remaining snapshot tests all in one go. This issue can track that.

Closed by https://github.com/kumahq/kuma-gui/pull/1489


add scala version to publish command

@benblack86 @jlbelmonte @amotamed

Codecov Report

Merging #601 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #601   +/-   ##
=======================================
  Coverage   84.87%   84.87%
=======================================
  Files          99       99
  Lines        4451     4451
  Branches      379      365   -14
=======================================
  Hits         3778     3778
  Misses        673      673

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 5dabd1d...a51daad. Read the comment docs.

LGTM


Refactor TestDecodingPlugin

For #4510 .

Codecov Report

Merging #4598 into sharding-scaling will increase coverage by 0.05%.
The diff coverage is 40.62%.

@@                  Coverage Diff                   @@
##             sharding-scaling    #4598      +/-   ##
======================================================
+ Coverage                56.1%   56.15%   +0.05%
- Complexity                394      398       +4
======================================================
  Files                    1085     1085
  Lines                   20930    20925       -5
  Branches                 3831     3832       +1
======================================================
+ Hits                    11742    11750       +8
+ Misses                   8444     8427      -17
- Partials                  744      748       +4

Impacted Files
Coverage Δ
Complexity Δ

...ling/postgresql/wal/decode/TestDecodingPlugin.java
71.55% <40.62%> (+9.56%)
31 <3> (+4)
:arrow_up:

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 10018

20 of 32 (62.5%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.07%) to 59.785%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-scaling/sharding-scaling-postgresql/src/main/java/org/apache/shardingsphere/shardingscaling/postgresql/wal/decode/TestDecodingPlugin.java
20
32
62.5%

Files with Coverage Reduction
New Missed Lines
%

sharding-scaling/sharding-scaling-postgresql/src/main/java/org/apache/shardingsphere/shardingscaling/postgresql/wal/decode/TestDecodingPlugin.java
1
82.76%

Totals

Change from base Build 10012:
0.07%

Covered Lines:
12510

Relevant Lines:
20925

💛  - Coveralls


Add Cypress test for lazily loading non refreshable line items

What does this change?
Why?

Closing this for now, will reimplement in the future 👍


Scrollable TabBar

The tabbar should have a way to have scrolling categories. In the scrollable tabbar, there should be a single page showing all the widgets and categories on top as tabbar items, when the user clicks on an item it should scroll to the relevant widget, and if the user is scrolling the screen the tabbar items should change based on his position.
see this as example
https://github.com/EnsembleUI/ensemble/assets/61178058/dd928b21-2ddf-4aa3-a322-c9885a39a6ad

looking at it, apparently if you set tabPosition to stretch it sets the isScrollable to true which is a bit bizzare. It does not expose isScrollable otherwise which is doubly bizarre. @vusters do you know why?


Setting Access-Control-Allow-Origin: * for all resources

Is there a way to set the header Access-Control-Allow-Origin: * for all resources, without going with_header on each and every one of them?

you can use ntex-cors if you need cars support or DefaultHeader middleware

@fafhrd91 It seems that ntex-cors only supports ntex: 0.1, but I also use ntex-files with requires ntex: 0.3. Is there a way to avoid / resolve conflict?

cors from master supports 0.3


missing "del feed["fetch"]" in gpu web server

in python/paddle_serving_server_gpu/web_service.py, at line 109, it seems the following two lines are missing, between "self.preprocess" and "client_list[0].predict":
if "fetch" in feed:
    del feed["fetch"]

https://github.com/PaddlePaddle/Serving/pull/268


Use Netty 5.0.0.Alpha2 as proxyserver failed！

I am developing a proxies manager server with netty 5.0.0.Alpha2-SNAPSHOT named beastkeeper, you can see it as a proxy server. And the server's initChannel method code:
protected void initChannel(Channel ch) throws Exception {

				 ChannelPipeline pipeline = ch.pipeline();

			        pipeline.addLast( new HttpRequestDecoder());

			       pipeline.addLast("aggregator", new HttpObjectAggregator(1048576*1024));
			        pipeline.addLast(new HttpResponseEncoder());
			        pipeline.addLast("redeflater", new HttpContentCompressor());

			       pipeline.addLast(new NettyHttpServerHandler(manager));

			}

And I test with chrome，firefox, htmlunit ,ie, phantomjs, java's url connection.
I send http request as belows:
  GET http://www.sogou.com/ HTTP/1.1
  Host: www.sogou.com
  Proxy-Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)         Chrome/43.0.2357.132 Safari/537.36
Accept-Encoding: gzip, deflate, sdch
Accept-Language: zh-CN,zh;q=0.8

The result is that java's urlconnection, htmlunit , phantomjs is good but chrome, firefox, ie return 200 ok but have an ERR_CONTENT_DECODING_FAILED error. The http response header:
HTTP/1.0 200 OK
Server: nginx
Date: Mon, 20 Jul 2015 01:50:22 GMT
Content-Type: text/html
Vary: Accept-Encoding
Expires: Mon, 20 Jul 2015 01:50:22 GMT
Cache-Control: max-age=0
Connection: close
Content-Encoding: gzip
Transfer-Encoding: chunked

I use wireshark to see chrome's  http response, and it shows chunked encoding is correct, and gzip decoding is correct. But chrome show me ERR_CONTENT_DECODING_FAILED.
I doubt the netty's gzip have some problems because chrome returns 4580 bytes compressed data with beastkeeper and  returns 4574 bytes compressed data with no beastkeeper. Something weird is both of them can be uncompressed by java's GZIPInputStream with no error.
Now I don't know why. Could you help me?

Please try latest version and reopen if you still have issues


Updating homebridge-harmony breaks the remote widget functionality

After updating this plugin, the remote-widget functionality seems to get broken, no 'TV' device in the list of available remotes (everything in homekit-app works fine).
It shows up again if you remove the homebridge-hub accessory and re-add it to homekit. bit of a hassle. Perhaps something worth fixing in the future for reliability.

Hi, I didn’t have this problem as far as I checked . Did you change the name of the hub / or activities ? Did your device in home app reset to default room ?
if they are exposed and working well in home app without any visible change I think it is more a problem of iOS beta than in the plugin (nothing special is done to expose in remote widget ) . Did you try rebooting your iOS device before removing the hub ?
Sent with GitHawk

Hi, I always do a full 'reboot cycle' whenever I start testing stuf. (So I reboot Pi,ATV,iDevices & router).
Upgraded from beta3 to beta4 now so I'll notify you here if this problem persists when I update to a newer version of your plugin. perhaps this is/was also an AppleDev problem rather than one of the plugin.

@Midifreakz Hi, could you check with latest version ? Thanks !

Hi @nicoduj
Installed it straight away! ;) This time the update went very smoothly.

Off Topic but just letting you know: Yesterday and the day before my girlfriend was watching tv and used the Harmony Remote to start the activity. While watching a movie, the TV (only the actual television, not the activity) just powered off out of itself. When I wanted to check the state of the harmony activity in homekit I noticed the remote widget did not show the TV device from homekit. This only happened this one time. Have you ever experienced such an issue in the past? even without using homekit? It's naggin' me hehe...
I guess this has probably something to do with Harmony and not with your plugin.

I am closing, let me know if it appears again.


Test failed and throwing Salesforce Internal Error with no stack trace. Any idea?

@IsTest
private class dlrs_ContentDocumentLinkTest
{
@IsTest
private static void testTrigger()
{
// Force the dlrs_ContentDocumentLinkTrigger to be invoked, fails the test if org config or other Apex code prevents this.
dlrs.RollupService.testHandler(new ContentDocumentLink());
}
}

I am encountering this issue, as well.

Its worth being more expressive when talking about errors, such as giving the error itself. In this case though, salesforce internal errors can only be decoded by Salesforce Support. Meanwhile this might be a useful read through. https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/433. Sorry I am not able to help on this one, even with the salesforce error id.


cmd/ctr: container list should not look up image

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Closes #1176

Codecov Report

Merging #1200 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1200   +/-   ##
=======================================
  Coverage   28.09%   28.09%
=======================================
  Files          28       28
  Lines        2833     2833
=======================================
  Hits          796      796
  Misses       1888     1888
  Partials      149      149

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 52927e5...778b1f1. Read the comment docs.

LGTM


chore: add GitHub workflow for PR audit

Issue #, if available:
Implement #210
Description of changes:
This PR added a GitHub workflow job to execute a cargo audit when a PR is submitted, in order to maintain our code health.
An example execution:
Success: https://github.com/tmyoda/dynein/actions/runs/8846880245
Failed: https://github.com/tmyoda/dynein/actions/runs/8847001630
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I mistakenly created a PR so I will close this.

Thank you for the review. I have pushed the changes based on your comment.
Could you check this? Thanks.


(PDB-4701) Add ast rewriter to default to agent reports in queries

Add maybe-add-agent-report-filter-to-query to take an incoming query
and ast filter and rewrite the filter to include an additional ["="
"type" "agent"] clause at the top level and in every subquery,
whenever the query involves reports, and the existing filter at that
level doesn't already mention the report "type".

CLA signed by all contributors.

Merged in https://github.com/puppetlabs/puppetdb/pull/3255


Buying items without hackstead

You are able to buy items without owning a hackstead.

On account with hackstead, press buy button and send invoice id to account w/o hackstead
Pay for item without hackstead
You just broke the market 👏

Will it actually give the item to the person who paid without the hackstead, or will it still give it to the person who clicked "buy"?

I have to check but I think it goes to the person that paid for the invoice

Looks like the issue is in events/invoice_payment.rs line 193. We should insert into the Sale struct a record of who's actually buying the item so we can use that instead of the invoicee.


add VBA hello world module

What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


closed！Thanks！

Hi @snorp @mneumann @alexcrichton
error: failed to run custom build command for libz-sys v1.1.8 , with CLI command "cargo build --target=wasm32-wasi"
I want to compile this repository,error was happened.i want to fix it with one days, always failed to build on macOS.rendering me unable to use cargo-update.
below detail error info:

warning: error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-wasi"'
error: failed to run custom build command for libz-sys v1.1.8
error: failed to run custom build command for openssl-sys v0.9.74

cargo --version：1.61.0
rustc --version：1.61.0
wasmtime: v0.37.0-x86_64-macos
wasmedge: version 0.10.0
x86_64-apple-darwin (installed)
OSX 12.4 intel-X86
Here is the entire error message:

Hi mindrock how did you fix this?


push live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/AdaptiveCards, working directory: W:\elpj-s, target branch: live, target branch commit: c7dd8cb7bfd045cc559e5bce557483440d8c9a79, source branch: master, source branch commit: .

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/get-started/Bots.md
:white_check_mark:Succeeded

AdaptiveCards/resources/Partners.md
:white_check_mark:Succeeded

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


Feat/roc 9694 hearing for fast track

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/ROC-9694
Change description
Civil Money Claims (CMC)ROC-9694
LR vs LR- Fast Track: Screen to capture Defendant hearing requirements
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x ] No

closing this PR to save some resource on jenkins

closing this PR to save some resource on jenkins

Reopening the request after giving demo to Alana, she is fine with change and I can deploy it to production.


Task 13 & Task 15

SourceCode/2024/May 2024/Rajendra/Task13/project.json
Main.xaml
Log Message not used in workflow Main.
Using Log Message activities is important both during development and after release. They help understanding the flow path which is very useful for maintenance and, when an error occurs, to easily identify the source and the cause.
Variable ExtractDataTable
Variable doesn't have DataTable prefix.
DataTable Variable should start with a dt_ prefix.
Variable FilteredData
Variable doesn't have DataTable prefix.
DataTable Variable should start with a dt_ prefix.
Activity Extract Table Data
Activity has a default name.
Check if it could be easier to understand what the activity does by adding a more descriptive title.
Score: 4/5
Please note that these are just suggestions for improvement, and no specific code is provided as a suggestion.

@rajendrayarlagaddausa333
Task – 13
Code verified.
Task – 15
Code verified.


addition of backports.lzma causes failure of building the buildroot

I built off the latest master and the addition of backports.lzma causes the following issue:
[root@losbs ~]# atomic-reactor create-build-image --reactor-tarball-path /usr/share/atomic-reactor/atomic-reactor.tar.gz /usr/share/atomic-reactor/images/dockerhost-builder buildroot
2015-07-31 16:11:00,300 - atomic_reactor.core - INFO - building image 'buildroot' from path '/tmp/tmp4btfHs/df-09755ff6-4ee5-4008-b47e-b9ab5c404037'
2015-07-31 16:11:00,326 - atomic_reactor.util - INFO - wait_for_command
2015-07-31 16:14:55,273 - atomic_reactor.util - ERROR - {"errorDetail":{"message":"The command [/bin/sh -c cd /tmp/atomic-reactor-*/ \u0026\u0026 python setup.py install] returned a non-zero code: 1"},"error":"The command [/bin/sh -c cd /tmp/atomic-reactor-*/ \u0026\u0026 python setup.py install] returned a non-zero code: 1"}
2015-07-31 16:14:55,273 - atomic_reactor.util - INFO - no more logs

[root@losbs ~]# docker logs compassionate_banach
running install
running bdist_egg
running egg_info
creating atomic_reactor.egg-info
writing requirements to atomic_reactor.egg-info/requires.txt
writing atomic_reactor.egg-info/PKG-INFO
writing top-level names to atomic_reactor.egg-info/top_level.txt
writing dependency_links to atomic_reactor.egg-info/dependency_links.txt
writing entry points to atomic_reactor.egg-info/entry_points.txt
writing manifest file 'atomic_reactor.egg-info/SOURCES.txt'
reading manifest file 'atomic_reactor.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'atomic_reactor.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/atomic_reactor
copying atomic_reactor/inner.py -> build/lib/atomic_reactor
copying atomic_reactor/__init__.py -> build/lib/atomic_reactor
copying atomic_reactor/constants.py -> build/lib/atomic_reactor
copying atomic_reactor/plugin.py -> build/lib/atomic_reactor
copying atomic_reactor/core.py -> build/lib/atomic_reactor
copying atomic_reactor/outer.py -> build/lib/atomic_reactor
copying atomic_reactor/build.py -> build/lib/atomic_reactor
copying atomic_reactor/util.py -> build/lib/atomic_reactor
copying atomic_reactor/buildimage.py -> build/lib/atomic_reactor
copying atomic_reactor/api.py -> build/lib/atomic_reactor
copying atomic_reactor/source.py -> build/lib/atomic_reactor
creating build/lib/tests
creating build/lib/tests/koji
copying tests/koji/__init__.py -> build/lib/tests/koji
creating build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/exit_store_logs_to_file.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_pyrpkg_fetch_artefacts.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/__init__.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/prepub_squash.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_cp_dockerfile.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_tag_and_push.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_add_labels_in_df.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/input_path.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_return_dockerfile.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_add_yum_repo.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_compress.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_pull_base_image.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_tag_by_labels.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/input_env.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_inject_yum_repo.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_import_image.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_rpmqa.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_change_from_in_df.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/prepub_tests_for_image.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_check_rebuild.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/input_osv3.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_koji.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_add_dockerfile.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/exit_remove_built_image.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_push_to_pulp.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/exit_store_metadata_in_osv3.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/post_cp_built_image_to_nfs.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_add_yum_repo_by_url.py -> build/lib/atomic_reactor/plugins
copying atomic_reactor/plugins/pre_assert_labels.py -> build/lib/atomic_reactor/plugins
creating build/lib/atomic_reactor/cli
copying atomic_reactor/cli/__init__.py -> build/lib/atomic_reactor/cli
copying atomic_reactor/cli/secret.py -> build/lib/atomic_reactor/cli
copying atomic_reactor/cli/main.py -> build/lib/atomic_reactor/cli
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/tests
creating build/bdist.linux-x86_64/egg/tests/koji
copying build/lib/tests/koji/__init__.py -> build/bdist.linux-x86_64/egg/tests/koji
creating build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/inner.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/__init__.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/constants.py -> build/bdist.linux-x86_64/egg/atomic_reactor
creating build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/exit_store_logs_to_file.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_pyrpkg_fetch_artefacts.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/__init__.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/prepub_squash.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_cp_dockerfile.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_tag_and_push.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_add_labels_in_df.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/input_path.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_return_dockerfile.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_add_yum_repo.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_compress.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_pull_base_image.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_tag_by_labels.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/input_env.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_inject_yum_repo.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_import_image.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_rpmqa.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_change_from_in_df.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/prepub_tests_for_image.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_check_rebuild.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/input_osv3.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_koji.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_add_dockerfile.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/exit_remove_built_image.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_push_to_pulp.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/exit_store_metadata_in_osv3.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/post_cp_built_image_to_nfs.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_add_yum_repo_by_url.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugins/pre_assert_labels.py -> build/bdist.linux-x86_64/egg/atomic_reactor/plugins
copying build/lib/atomic_reactor/plugin.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/core.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/outer.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/build.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/util.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/buildimage.py -> build/bdist.linux-x86_64/egg/atomic_reactor
copying build/lib/atomic_reactor/api.py -> build/bdist.linux-x86_64/egg/atomic_reactor
creating build/bdist.linux-x86_64/egg/atomic_reactor/cli
copying build/lib/atomic_reactor/cli/__init__.py -> build/bdist.linux-x86_64/egg/atomic_reactor/cli
copying build/lib/atomic_reactor/cli/secret.py -> build/bdist.linux-x86_64/egg/atomic_reactor/cli
copying build/lib/atomic_reactor/cli/main.py -> build/bdist.linux-x86_64/egg/atomic_reactor/cli
copying build/lib/atomic_reactor/source.py -> build/bdist.linux-x86_64/egg/atomic_reactor
byte-compiling build/bdist.linux-x86_64/egg/tests/koji/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/inner.py to inner.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/constants.py to constants.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/exit_store_logs_to_file.py to exit_store_logs_to_file.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_pyrpkg_fetch_artefacts.py to pre_pyrpkg_fetch_artefacts.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/prepub_squash.py to prepub_squash.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_cp_dockerfile.py to pre_cp_dockerfile.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_tag_and_push.py to post_tag_and_push.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_add_labels_in_df.py to pre_add_labels_in_df.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/input_path.py to input_path.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_return_dockerfile.py to pre_return_dockerfile.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_add_yum_repo.py to pre_add_yum_repo.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_compress.py to post_compress.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_pull_base_image.py to pre_pull_base_image.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_tag_by_labels.py to post_tag_by_labels.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/input_env.py to input_env.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_inject_yum_repo.py to pre_inject_yum_repo.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_import_image.py to post_import_image.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_rpmqa.py to post_rpmqa.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_change_from_in_df.py to pre_change_from_in_df.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/prepub_tests_for_image.py to prepub_tests_for_image.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_check_rebuild.py to pre_check_rebuild.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/input_osv3.py to input_osv3.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_koji.py to pre_koji.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_add_dockerfile.py to pre_add_dockerfile.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/exit_remove_built_image.py to exit_remove_built_image.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_push_to_pulp.py to post_push_to_pulp.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/exit_store_metadata_in_osv3.py to exit_store_metadata_in_osv3.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/post_cp_built_image_to_nfs.py to post_cp_built_image_to_nfs.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_add_yum_repo_by_url.py to pre_add_yum_repo_by_url.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugins/pre_assert_labels.py to pre_assert_labels.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/plugin.py to plugin.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/core.py to core.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/outer.py to outer.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/build.py to build.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/util.py to util.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/buildimage.py to buildimage.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/api.py to api.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/cli/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/cli/secret.py to secret.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/cli/main.py to main.pyc
byte-compiling build/bdist.linux-x86_64/egg/atomic_reactor/source.py to source.pyc
installing package data to build/bdist.linux-x86_64/egg
running install_data
creating build/bdist.linux-x86_64/egg/share
creating build/bdist.linux-x86_64/egg/share/atomic-reactor
creating build/bdist.linux-x86_64/egg/share/atomic-reactor/images
creating build/bdist.linux-x86_64/egg/share/atomic-reactor/images/privileged-builder
copying images/privileged-builder/Dockerfile -> build/bdist.linux-x86_64/egg/share/atomic-reactor/images/privileged-builder
copying images/privileged-builder/docker.sh -> build/bdist.linux-x86_64/egg/share/atomic-reactor/images/privileged-builder
creating build/bdist.linux-x86_64/egg/share/atomic-reactor/images/dockerhost-builder
copying images/dockerhost-builder/Dockerfile -> build/bdist.linux-x86_64/egg/share/atomic-reactor/images/dockerhost-builder
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying atomic_reactor.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
atomic_reactor.plugin: module references __file__
creating dist
creating 'dist/atomic_reactor-1.4.0-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing atomic_reactor-1.4.0-py2.7.egg
creating /usr/lib/python2.7/site-packages/atomic_reactor-1.4.0-py2.7.egg
Extracting atomic_reactor-1.4.0-py2.7.egg to /usr/lib/python2.7/site-packages
Adding atomic-reactor 1.4.0 to easy-install.pth file
Installing atomic-reactor script to /usr/bin
Installing pulpsecret-gen script to /usr/bin

Installed /usr/lib/python2.7/site-packages/atomic_reactor-1.4.0-py2.7.egg
Processing dependencies for atomic-reactor==1.4.0
Searching for backports.lzma
Reading https://pypi.python.org/simple/backports.lzma/
Best match: backports.lzma 0.0.3
Downloading https://pypi.python.org/packages/source/b/backports.lzma/backports.lzma-0.0.3.tar.gz#md5=c3d109746aefa86268e500c07d7e8e0f
Processing backports.lzma-0.0.3.tar.gz
Writing /tmp/easy_install-Gk_OGx/backports.lzma-0.0.3/setup.cfg
Running backports.lzma-0.0.3/setup.py -q bdist_egg --dist-dir /tmp/easy_install-Gk_OGx/backports.lzma-0.0.3/egg-dist-tmp-ZZzHYV
unable to execute 'gcc': No such file or directory
This is backports.lzma version 0.0.3
error: Setup script exited with error: command 'gcc' failed with exit status 1

Is this solved by https://github.com/projectatomic/atomic-reactor/pull/246?

It is not, the build failure appears to be happening inside the docker container where it's rebuilding atomic-reactor instead of just using the already built version from the yum repos. GCC is missing from the container, which I don't think it should be necessary unless I'm missing something.

backports.lzma needs gcc to compile, since it ships a C extension module. So yeah, if we use the Python 2 version in the build image, we also need gcc there. (If we use Python 3 version, backports.lzma won't be necessary, since Python 3 already has that builtin)

I think that the main cause of this is that we're not using the Dockerfile from our root (which I'm trying to keep up-to-date), but one of the Dockerfiles in images/ subdir, which has python setup.py install. Could we perhaps delete these and just use the root one, which installs all deps as RPMs?

@bkabrda +1 for installing reactor from fedora repos (we've used setup.py back then when reactor wasn't part of fedora yet)

This fixes https://github.com/projectatomic/atomic-reactor/pull/252

https://github.com/projectatomic/atomic-reactor/pull/252 was merged and resolves this. Closing.


Issues with touch devices (no zooming , tooltip bug)

Hey there,
i have a problem with some touch events on a tablet with windows 8.1 (internet explorer 11) and also on a touch-monitor with windows 7 and the internet-explorer 11.
First of all the bug, i have on both devices:
The tooltips are not shown correctly. If you tap on the charts (wich is a click) it seems, that more events are fired than necessary. the tooltip shortly appear, and afterwards it disappear immediatly. So you can't read it.  (Note: You can't emulate this behavior with Chrome or else)
But its the same on a Windows 8.1 Tablet and IE11
The second bug is only on the tablet ( i think it coud be some kind of MSPointerDown MSPointerUp - thing). I disabled the zooming of the page by

-ms-content-zooming: none;
-ms-touch-action: pan-x pan-y;
-webkit-content-zooming: none;
content-zooming: none;

if not, you would just zoom into the whole page, and not into the diagram. The funny thing is, on the big screen monitor with windows 7, the zoom on the diagram works fine.
On the tablet, it isn't working.

Interesting; this is kind of edge case but also terrifically helpful as I don't have access to any of those devices. Any suggestions how to fix this?

Hi,
so my first input to the "tooltip-bug" is the events which are fired by the windows 8.1 IE 11 from an HP ElitePad.
I really tried to just touch once and the listener for all events was just on the SVG element. This events were fired in this exact order:
On the windows Tablet:
mousemove
pointerover
pointerenter
mouseover
pointerdown
mousedown
focusin
pointerout
mouseout
pointermove
mousemove
pointerover
mouseover
pointerup
mouseup
pointerout
pointerleave
mouseout
focusout

(i think all focux** events were triggered because of the logging with the developer window)
On the windows TV with infrared touch input :
pointermove
mousemove
pointerover
pointerenter
mouseover
pointerdown
mousedown
focusin
pointerout
mouseout
pointermove
mousemove
pointerover
mouseover
pointerout
mouseout
pointerup
mouseup
click
pointerover
mouseover
pointerout
mouseout
pointermove
mousemove
pointerover
mouseover
focusout
pointerout
pointerleave
mouseout

ONE small touch.... damn!
Maybe someone will get some more information from that event-log :(

Hmm... Might be related to #1617, #1658 and #608. Have been running into a lot of issues about tonnes of events being fired...


Update different-id.md

add why the delta method

🚀 Deployed on https://660f4338cb1302163a856c18--cozy-fox-0defec.netlify.app


DuplicateSemicolonFixer - ignore duplicated semicolons inside T_FOR

bug from #992

PR has been merged.

php-cs-fixer --version
PHP CS Fixer version 2.0-DEV by Fabien Potencier

php-cs-fixer fix  Application/
Files that were not fixed due to internal error:
   1) Admin/Controller/AdminController.class.php
   2) Admin/Controller/AttributeController.class.php
   3) Admin/Controller/CategoryController.class.php

This mean some problem occured somewhere inside.
This may or may not be connected with duplicate semicolons. Please provide your files content to replicate the error.

For example: this file is called [FileController.class.php]
<?php

namespace Api\Controller;
use Common\Controller\FileCommonController;

class FileController extends FileCommonController
{

    /**
     * upload file
     * @return [array] [description]
     */
    public function upload_post() {
        parent::upload();
    }

    /**
     * delete file
     * @return [array] [description]
     */
    public function delete_post() {
    	parent::delete();
    }

}

If you change the file name to [FileController.php] can be carried out smoothly.
Run fail:
php-cs-fixer fix FileController.class.php
Fixed all files in 0.289 seconds, 4.500 MB memory used

Files that were not fixed due to internal error:
   1) /home/wwwroot/booking2/FileController.class.php

Run success:
php-cs-fixer fix FileController.php
   1) /home/wwwroot/booking2/FileController.php
Fixed all files in 0.098 seconds, 4.500 MB memory used


Option to disable shadow

Is your feature request related to a problem? Please describe.
There doesn't seem to be an option to turn off the shadow, and I have yabai running with shadows off.
(in yabairc) yabai -m config window_shadow  off
 The shadow can still be seen, and shadows are not present for any other applications.
Current available options:

Describe the solution you'd like
An option to turn off the shadow.
While I'm at it, thanks for making this bar, it is by far the best one I've used for two years now!

Hmm that's weird, I just tested disabling and enabling shadow and simple-bar is normally checking on each refresh if yabai has enabled shadow or not by running this command yabai -m config window_shadow. Depending on the output, It removes automatically its shadow.
Can you try to run this command and see if it returns off?
Otherwise, if you want an easy fix, you can simply add these lines in your custom styles tab (in settings):
.simple-bar {
  box-shadow: none !important;
}

Interesting, it says off when I ran the command...
Also weirdly enough, the css doesn't make the shadow go away:

The shadow is still there. It seems that the box-shadow: none !important; only made the red outline not appear when selecting the bar.
And now I tried updating it to the latest git commit 6abd85084b30fa14673ca189036e6cb8bc1fdf42: the bar doesn't load at all and has this error:

My previous install worked and was commit number 3d38feca9418597ba416f6d6f3a0160f2a1182b9. Not sure what's going on, I've never had any issues like this before! I'm using the latest Ubersicht 1.6.82 on Sonama 14.1.

Oh, I think I know what is happening. It seems that the shadow you see are not .simple-bar shadows because they are rightly removed.
I simply didn't removed all the children shadows and they are projected below the bar.
I just pushed a fix that should make all shadow disappear :)
I also tried to fix the error you saw, please let me know if every thing is working fine again.

Yep - this fixed everything!! Thank you so much for your work and quick response :D


An submit issue in ruby katas

I begin learning ruby. Sometimes  the kata parameter is nil, Output window will be reported to the wrong, but still can do the final submission. (Actually did not complete all the tests)

for example, I can use this code passed some(all?) ruby katas:
$ii=0
def ball_probability(balls)
  $ii+=1
  $ii==1 ? 0.09 : nil.reverse
end

Only need type the right answer of first testcase(0.09), it will passed this kata

Try it now. My theory was that this was a cache busting issue as this was fixed a while ago.

No, you didn't fix the problem.
I can give you an example:
https://www.codewars.com/kata/52191f3c35f5ecba960003f3
Use this code:
$i=0
class Hash
  def get_value( default, *args )
    $i+=1
    $i==1 ? default : nil.reverse
  end
end

Thanks for the example, that made it very easy to test and fix. Should be good now.


First attempt to resolving the github pull request issues

Due to issues on previous pull requests on gut hub tests not passing. I have ran eslint fix, updated the ignore file in an attempt to pass the GitHub tests.
Some other formatting changes may appear appended to my request due to updates made on prettier and it's applications to new file directories. I can make that into a separate commit or PR if needed.
Attached ticket here: https://trello.com/b/lmGzARca/labspt17-cityspire-c

So, on submission I've seen that all the checks have passed. Let me know if you have any questions.

 Fixed the backend tests for GitHub to let other PRs pass

It looks good. I'm glad you found the issue.
The only thing I notice was a type in your comment for PR in the first sentence:
"Due to issues on previous pull requests on gut hub tests not passing."
should be
"Due to issues on previous pull requests on GitHub tests not passing."
The actual PR looks good. I'm glad you caught the first line in the migrations file from the legacy code that needed to be commented out.

Thanks Jason - updated the submission to reflect your comments.


Ollama3 and missing pip package

Hi,
It seems there was a missing package for the app to launch so I have added it.
I have also changed the model to ollama3 as this seems newer though not sure about the impact as I did not get a chance to compare hope this is useful and relevant
Note: happy to separate the proposed chaages into 2 PRs if needed.
Thanks
dan

Great!
Thanks.


Absolutely zero resemblance to the images given

I messed around with quite a few different images (some scribbled, some made with crude Paint skills, and some made with AI), and almost none of them came vaguely close to the input image. I've included the example I find most egregious as screenshots.
Don't get me wrong: I obviously get why that input image would never, ever have worked. The issue isn't the lack of successful duplication—it's the outright lie it outputs. It would be helpful to implement a feature that notifies users when an image can't be accurately processed, rather than generating unrelated websites.

Here are two additional, more conventional examples of "... what?" behaviour.


Text and code revision of P1C1_Sequence1.ipynb

Thanks for the PR. Typo fixes look good but the CI process seems to not like something about this, possibly committing straight to main. I created a branch https://github.com/dcownden/PerennialProblemsOfLifeWithABrain/tree/text-and-code-revisions-P1C1_sequence1/sequences. Maybe the ci process will be happier if you try to merge into that branch first.

Ok, I've just opened a new PR as suggested #16.

Thanks again for those typo fixes, and for your patience. That seems to have worked and your changes look like they are live. We'll need to think through our workflow for incoming PR's and set up some instructions.

You're welcome. Thank you for such a great initiative and for your effort!
Glad to help with the next notebooks, of course.

PS: @dcownden Do you believe it might be a good idea to activate discussions for this repo in order to efficiently communicate in a PR-independent way? Do you prefer other means such as Slack, Zulip, Mail, Twitter or something else?


template stopped working

I'm unsure if it's something on my machine but I can't get the template referenced in the docs to work anymore: https://github.com/Desdaemon/flutter_rust_bridge_template/issues/16 - Also my own flutter playground app which I've based on that template stopped working.
The flutter sample included in this repository still works though, including the code generator call included in the justfile in the root of this repository.
Can you help me to get a standalone flutter+rust app working again please?

/cc @Desdaemon I guess do we miss codegen or import os something?

Don't know how much works on your setup, but I pulled @thomas725's repository and ran codegen (1.48.0). Aside from a few dependency errors, it works fine:

Oh wow! Thanks for trying to run my playground app! So something in my laptops environment must be broken.
I should have included the error messages I get in the first post, sorry:
$ flutter run -d linux
Launching lib/main.dart on Linux in debug mode...
   Compiling native v0.1.0 (/home/thomas/Development/git/flutter-playground/native)
error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:22:39
   |
22 | fn wire_rust_release_mode_impl(port_: MessagePort) {
   |                                       ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:32:38
   |
32 | fn wire_environment_info_impl(port_: MessagePort) {
   |                                      ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:42:26
   |
42 | fn wire_tick_impl(port_: MessagePort) {
   |                          ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:52:34
   |
52 | fn wire_stop_ticking_impl(port_: MessagePort) {
   |                                  ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:62:39
   |
62 | fn wire_create_log_stream_impl(port_: MessagePort) {
   |                                       ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `MessagePort` in this scope
  --> src/bridge_generated.rs:72:33
   |
72 | fn wire_rust_set_up_impl(port_: MessagePort) {
   |                                 ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `DartAbi` in module `support`
   --> src/bridge_generated.rs:105:36
    |
105 |     fn into_dart(self) -> support::DartAbi {
    |                                    ^^^^^^^ not found in `support`

For more information about this error, try `rustc --explain E0412`.
error: could not compile `native` due to 7 previous errors

Suspect you have old cargo lock.
Your Cargo.lock is not in version control.
@Desdaemon download and run it, then it is fine, since auto download latest.
But in your own cargo.lock, maybe it is very old frb_rust lib, e.g. 1.34.2, no wonder there are no such structs :) https://gitlab.com/thomas351/flutter-playground/-/blob/main/native/Cargo.toml

Ohhh!!! Thank you, that was exactly the right guess, after adding an ".old" suffix to both pubspec.lock & cargo.lock files and rerunning flutter pub get and just everything works again :)


Expose metafields and quantity fields on the Shopify Product and Variant models

Asana Task
https://app.asana.com/0/1202051573875308/1204168789439726/f
Summary
This is a dependency of https://github.com/hellojuniper-com/juniper-react/pull/94. After merging, we must publish a new release version of this package, for juniper-react to consume.

The code seems sound, I just have a couple questions about this history of this all before I sign off - will discuss offline.


[Relay][Frontend][Onnx] If Operator Support

This surprisingly small PR adds support for the If operator in the Onnx frontend. This turned out to be a pretty direct conversion to relay!

@mbrookhart @masahi @tmoreau89 @soiferj can you guys take a look at this PR?

@jwfromm  please run CI again

I'm pretty confused why this is failing CI. It looks like on the GPU test, the onnxruntime produces the wrong value (getting a -2 instead of the correct value of 1) while TVM produces the proper result. It seems like on the CPU node, the test passes. I'm not able to replicate the error on my local GPU machine. Does anyone have any ideas (@masahi) why that might happen?

Maybe the old version of onnxruntime had a bug? ORT on CI is fairly old (v1.00) while the latest one is v1.5. You probably have a newer ORT locally.

Good point, I'll try to check out using v1.00. Thanks!

@jwfromm something is wrong with CI

Sorry for the delay. It seems like the only path forward on this for now is to disable GPU tests until onnxruntime is updated to a newer version.

@masahi, I ended up removing onnxruntime from the if test for now. Since the correct result in this case is very clear, there's not much need to generate with onnxruntime. Once we update to a newer ort version I'll switch back.

thanks @jwfromm @mbrookhart @tmoreau89


cross compile error when make install

i have the same problem(cross built on vm,not inside docker) ,see the error log below:
.....
[100%] Linking C shared library libkeystored.so
[100%] Built target keystored
[100%] Built target keystored
Install the project...
-- Install configuration: "Release"
-- Installing: /home/olympus/toolchain/gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi/lib/pkgconfig/keystored.pc
-- Up-to-date: /home/olympus/toolchain/gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi/etc/keystored/keys
/usr/local/bin/sysrepoctl: error while loading shared libraries: libsysrepo.so.0.7: wrong ELF class: ELFCLASS32
-- Installing module ietf-x509-cert-to-name...
/usr/local/bin/sysrepoctl: error while loading shared libraries: libsysrepo.so.0.7: wrong ELF class: ELFCLASS32
/usr/local/bin/sysrepocfg: error while loading shared libraries: libsysrepo.so.0.7: wrong ELF class: ELFCLASS32
-- SSH hostkey found, no need to generate a new one.
-- Importing ietf-keystore stock key configuration...
/usr/local/bin/sysrepocfg: error while loading shared libraries: libsysrepo.so.0.7: wrong ELF class: ELFCLASS32
-- Installing: /usr/local/lib/sysrepo/plugins/libkeystored.so
-- Set runtime path of "/usr/local/lib/sysrepo/plugins/libkeystored.so" to ""
root@ubuntu:/home/olympus/build-root/Netopeer2-0.7-r1/keystored/build# file /usr/local/bin/sysrepoctl
/usr/local/bin/sysrepoctl: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=67d26927d11b2b1222178ea864324628b790151d, not stripped
root@ubuntu:/home/olympus/build-root/Netopeer2-0.7-r1/keystored/build# file /usr/lib/libsysrepo.so.0.7
/usr/lib/libsysrepo.so.0.7: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=8c5b31f9cf8f28d53fc0f83c03890e83dd979a93, not stripped
#403

Cross compiling is tricky, I recommend to use a real tool for this, such as Buildroot or Yocto.
It looks like you're invoking sysrepoctl built for your target architecture while still on the host. Sysrepo's build does this, and therefore you have to build sysrepo twice, once for host and the second time for the target and using an appropriate -DCALL_SYSREPOCTL_BIN=... (and the same for sysrepocfg) should get you going.
See the git log for details.


I want to run the next line after get the QR code.

I'm going to run its next line after get QR code.
However, my code is already run the next line while show the camera view.
Help me, please. Sorry for my bad english.
My code is as follows.
func myFunc(){
  getQRCode()
  if self.myQRCode == nil {  // self.myQRCode always hasn't readed code ...?????
.......
  } else {

  }
}
func getQRCode(){
  reader.delegate = self

  // Or by using the closure pattern
  reader.completionBlock = { (result: String?) in
    self.myQRCode = result
  }

  // Presents the reader as modal form sheet
  reader.modalPresentationStyle = .FormSheet
  presentViewController(reader, animated: true, completion: nil)
}

Hi,
The scan is asynchronous so when you call the getQRCode method it does not wait for a response.
Here an example how to resolve your issue:
func myFunc() {
  // Scan callback
  reader.completionBlock = { (result: String?) in
    if let _result = result {
       println("Scanned code: \(_result)")
    }
    else {
      println("No code found")
    }
  }

  presentViewController(reader, animated: true, completion: nil)
}

I'm sorry.
The Function "myFunc" has to return the boolean value and the value relates to gotten QR Code.
In other words, "myFunc" has to return the result that processed by gotten QR code.
How can I do? Sorry for your trouble.
I'm going to make the function as follows.
func myFunc() -> Bool{
var tmpFlag: Bool = false
reader.completionBlock = { (result: String?) in
if let _result = result {
println("Scanned code: (_result)")
tmpFlag = checkQRCode(result)
}
else {
println("No code found")
}
}
presentViewController(reader, animated: true, completion: nil)
return tmpFlag
}

You can't do that easily because of the async callback.
The QRCodeReader runs into the main thread so if you block it by waiting a result your interface will be frozen and you should not do that.
Why the callback does not suit your needs?

Thank you for your kind reply.


Bug bounty test - PLEASE DO NOT APPROVE. qavbdk

Bug bounty test - PLEASE DO NOT APPROVE. qavbdk

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Context menus

Lo and behold, context menus are coming.

And sorry again for the broken PR, the GitHub is kinda confused about the commits since I didn't merge them properly.

What do these look like?

I'm unsure if I can show the screenshots. But believe me. Amazing.

Due to https://github.com/discord/discord-api-docs/pull/3614 I'm undrafting this. Enjoy!


NullPointerException fix

@LeonKarabchevsky Great fix, thanks!

Hi @stealthcopter!
Do you plan a release with this fix any time soon?
Thanks!


Add relevant articles on Html and CSS to the Html and Css (Beginner's Level) section in the Frontend Track

Task

add relevant articles in this section that discuss a concept or particular topic. For example in the API section, you can add an article to the article list on 'Promises in JavaScript' or 'Knowing the difference between var, let and const' in the JavaScript section article list.

Things to Note

add only articles that are relevant and useful to frontend development.
be as descriptive as possible when naming your links and do not forget to include the author or creator of the content.
Eg. 'Build a food recipe app with fetch API and vanilla JavaScript. ~ GeetProbin'.
confirm that the article has not already been added.
follow the code format or template used.

Resources
View how to contribute to this repository.

Hey @Timonwa I would like to work on this issue.

Hey can you assign me this issue so that I can start working on it

Sure, @Saloni0512, you can go ahead with this. Please give us a star if you haven't already. 😁


Include Alby hosted balance in the UI

Places to add:

Onboarding carousel
Wallet balance

Related UX issue

WDYT? @rolznz @bumi
Wallet here would display custodial balance before it's migrated. Some users were thinking funds are gone when they saw 0 here

CC @reneaaron

I like the onboarding slide. I'm not sure about the wallet page, and this depends on them having a channel with incoming liquidity.

this depends on them having a channel with incoming liquidity.

What do you mean? Doesn't that display before they have any channels?

@stackingsaunter that only works if you have enough to pay to open a channel (but it's step 1 of the onboarding.)
Do you mean if they don't do step 1 and go immediately to the wallet?

Yeah I meant situation before any migration If they enter Wallet page

another user found it hard to find on the node page. This issue probably fixes it.

I like the idea of adding it to the wallet page if the user has a old balance.

"Migrate Funds" button on Wallet page can just go back to the first channel flow.