[Feature] Adding a new Chat Assistant

Problem
If a user is stuck in something on the website or if the user wants to know something about the organization and other details about the website at a single place.
Description
This is a chatbot created in HTML, CSS and JavaScript to help the user if it wants to get some information or want to an assistant of CC organization. It will generate automated replies on behalf of the organization to give help to the user.
Alternatives
In contrast to other paid software that is available online but only has a limited capacity, such as providing users with thousands of texts for free and then organization has to pay to use them, but this chat assistant was entirely constructed from scratch and will produce responses to user questions. As a result, it has the benefit of being original.
Implementation
I already wrote its HTML, CSS and JavaScript and it only needs some questions to be edited according to organization before fully deployed, and as I am a new to Docker, so, I tried to implement it but could not do so because it was not getting shown on the browser while using docker. So, if you select me in the project "Modernize CC Resource Archive", after doing all the modernization of the website provided in the project, I would also be interested in implementing this feature in your guidance. @possumbilities @TimidRobot
Thank you!
I also provided some screenshots by implementing it in a single webpage that How it will look on the website.
1.

[

Hey @aayushchauhan10,
It's a great idea to use a chatbot for answering questions, but currently it falls out of scope for this project. It will just add more complexity to the project. About answering questions for users, I think a better approach would be to put some FAQs just like cc-chooser.
However, I think a better option would to pitch this idea for the main CC website. Let's see what maintainers have to say about this.

Hey @Xaid-vfx,
Yes, you are right in a way that we could choose FAQs to help users but in other way, my opinion of choosing chat assistant is that if a user is stuck in some other thing that is not mentioned in the FAQs, then, there should be an option to talk with the company executive about the same, and there will be the chat assistant will work its part, but if it not there, then, it will not give the positive impression of the organization and as you said about the complexity of the project, whole of the website is just the same, we are only adding a new feature to it, so, It will not be so much complex, according to me.

Hi @aayushchauhan10 Thank you for this idea, but I think its complexity is far more from a feature standpoint than the resource archive needs. Closing.


Updates for PWA release 12.0.0

Description
Docs content for PWA Studio Release 12.0.0 and 12.1.0. The changes are mostly from the auto-generated docs from pwa-studio repo.
The remaining additions that I will add in the next PRs are:

Port over the commerce feature support table.
Add new metapackages section with Readme text from the metapackage repos.
Add new GraphQL docs for Contact Us and Newsletter to metapackages section

Related Issue
Jira Ticket: PWA-2376
How Has This Been Tested?
Built gh-pages site to review the changes: https://developer-stage.adobe.com/commerce/pwa-studio/integrations/adobe-commerce/version-compatibility/

@jcalcaben, if you can spare some time this morning to review this, that would be most helpful. Most changes are from the auto-generated files I copied from the most recent build in pwa-studio. Thanks.

@jcalcaben Just pushed the Venia sample data changes from PWA-2151/3473


fix: correct scripts linting template name

Current dependencies on/for this PR:

main

PR #34   👈

PR #35

PR #36

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: Lq6fAFaN1fLnSbVbBggu


I would like to mention Random Forest Algorithm

Hy Team!
I would like to mention about Random Forest Algorithm. Please assign me this issue

Go ahead. And please ⭐ the repo.

Thank You very much


Call to undefined method Illuminate\Database\Query\Builder::restored()

This problem happens in the current state of master branch.
Here is the stack trace:
    1. in Builder.php line 2448
    2. at Builder->__call('restored', array(object(Closure)))
    3. at call_user_func_array(array(object(Builder), 'restored'), array(object(Closure))) in Builder.php line 1465
    4. at Builder->__call('restored', array(object(Closure)))
    5. at call_user_func_array(array(object(Builder), 'restored'), array(object(Closure))) in Model.php line 3551
    6. at Model->__call('restored', array(object(Closure)))
    7. at call_user_func_array(array(object(User), 'restored'), array(object(Closure))) in Model.php line 3565
    8. at Model::__callStatic('restored', array(object(Closure))) in NtrustUserTrait.php line 81
    9. at User::bootObservers() in NtrustUserTrait.php line 45
    10. at User::boot() in Model.php line 296
    11. at Model->bootIfNotBooted() in Model.php line 277
    12. at Model->__construct() in EloquentUserProvider.php line 130
    13. at EloquentUserProvider->createModel() in EloquentUserProvider.php line 47
    14. at EloquentUserProvider->retrieveById('1') in SessionGuard.php line 132
    15. at SessionGuard->user() in GuardHelpers.php line 35
    16. at SessionGuard->authenticate() in AuthManager.php line 294
    17. at AuthManager->__call('authenticate', array()) in Authenticate.php line 57
    18. at Authenticate->authenticate(array()) in Authenticate.php line 41
    19. at Authenticate->handle(object(Request), object(Closure)) in Pipeline.php line 137
    20. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    21. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in VerifyCsrfToken.php line 65
    22. at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 137
    23. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    24. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in ShareErrorsFromSession.php line 49
    25. at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
    26. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    27. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in StartSession.php line 64
    28. at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
    29. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    30. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
    31. at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 137
    32. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    33. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in EncryptCookies.php line 59
    34. at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 137
    35. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    36. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
    37. at Pipeline->then(object(Closure)) in Router.php line 644
    38. at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 618
    39. at Router->dispatchToRoute(object(Request)) in Router.php line 596
    40. at Router->dispatch(object(Request)) in Kernel.php line 267
    41. at Kernel->Illuminate\Foundation\Http\{closure}(object(Request)) in Pipeline.php line 53
    42. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Debugbar.php line 51
    43. at Debugbar->handle(object(Request), object(Closure)) in Pipeline.php line 137
    44. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    45. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
    46. at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 137
    47. at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
    48. at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
    49. at Pipeline->then(object(Closure)) in Kernel.php line 149
    50. at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 116
    51. at Kernel->handle(object(Request)) in index.php line 53
    52. at require_once('/home/aterbonus/prueba/public/index.php') in server.php line 21

The problem is caused by this when the user model doesn't have the SoftDeletes trait.
Is a requirement to use ntrust to have the SoftDeletes trait in the user model?

@Aterbonus
Thanks for finding issue.
I have fixed on last commit. Can you please verify now with master branch?

Everything seems good now :). Thanks for the quick fix.

I will release new version after few more tests.


Tiny bug fix

@ptelad Stumbled upon this misconfiguration, please take a look and merge if it looks good. Thanks!
Use correct WKWebViewConfiguration properties/values for disabling requiring user action for media playback.
See API:
https://developer.apple.com/documentation/webkit/wkwebviewconfiguration

@ptelad bump...


Revert "[TT-188] disable the login db (#1188)"

This reverts commit 885580663f81b30e547da4ae87990650fd43a5f8.

There's a lot of red, but it seems like there's always a lot of red these days?


Is it possible to segment the definition of the function to be taken the gradient?

Dear friend,
Is it possible to segment the definition of the function to be taken the gradient?
For example:
if x < SomeValue then f(x) = someThing
if x > SomeValue then f(x) = someOtherThing

Thanks,
David

Conditionals are allowed in non-optimized mode (which is the default)
On Mon, May 9, 2016 at 5:20 PM David Lopes Macedo<EMAIL_ADDRESS>wrote:

Dear friend,
Is it possible to segment the definition of the function to be taken the
gradient?
For examplo,
if x < SomeValue then f(x) = someThing
if x < SomeValue then f(x) = someThing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/twitter/torch-autograd/issues/118

Sadly, It didn't work...
I am using cudnn and I have got the following error:

/home/dlm/torch/install/bin/luajit: /home/dlm/torch/install/share/lua/5.1/nn/Container.lua:67:  0ms | Step: 0ms
In 3 module of nn.Sequential:
In 3 module of nn.Sequential:
models/vgg_bn_drop_autograd_selu.lua:23: both torch.CudaTensor and (null) have no less-than operator

The code is below:
local SeLU  = function(input, weight, bias)
--local y = weight * input + bias
  local output
  if input < -0.5 then
    output = 0.5 * y
  elseif (input >= -0.5) and (input <= 0.5) then
    output = 1.0 * y
  else
    output = 0.5 * y
  end
  return output + 0 * torch.sum(weight) + 0 * torch.sum(bias)
end

local autogradSeLU = autograd.nn.AutoModule('AutoSeLU')(SeLU)
--local autogradSeLU = autograd.nn.AutoModule('AutoSeLU')(SeLU, tensor(1, 1),tensor(1, 1))

Sadly, It didn't work...
I am using cudnn and I have got the following error:

/home/dlm/torch/install/bin/luajit: /home/dlm/torch/install/share/lua/5.1/nn/Container.lua:67:  0ms | Step: 0ms
In 3 module of nn.Sequential:
In 3 module of nn.Sequential:
models/vgg_bn_drop_autograd_selu.lua:23: both torch.CudaTensor and (null) have no less-than operator

The code is below:
local SeLU  = function(input, weight, bias)
--local y = weight * input + bias
  local output
  if input < -0.5 then
    output = 0.5 * y
  elseif (input >= -0.5) and (input <= 0.5) then
    output = 1.0 * y
  else
    output = 0.5 * y
  end
  return output + 0 * torch.sum(weight) + 0 * torch.sum(bias)
end

local autogradSeLU = autograd.nn.AutoModule('AutoSeLU')(SeLU)
--local autogradSeLU = autograd.nn.AutoModule('AutoSeLU')(SeLU, tensor(1, 1),tensor(1, 1))

Dear friends,
Could someone tells me what is the error bellow:
local SeLU  = function(input)
  local output
  if torch.le(input, 0) then
    output = 0
  else
    output = input
  end
  return output
end

I am using cudnn and getting this error:

/home/dlm/torch/install/bin/luajit: /home/dlm/torch/install/share/lua/5.1/nn/Container.lua:67:  0ms | Step: 0ms
In 3 module of nn.Sequential:
In 4 module of nn.Sequential:
/home/dlm/torch/install/share/lua/5.1/nn/Dropout.lua:20: bad argument #1 to 'resizeAs' (torch.CudaTensor expected, got userdata)
stack traceback:
[C]: in function 'resizeAs'
/home/dlm/torch/install/share/lua/5.1/nn/Dropout.lua:20: in function </home/dlm/torch/install/share/lua/5.1/nn/Dropout.lua:16>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function </home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:41>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:44: in function 'forward'
train.lua:151: in function 'opfunc'
/home/dlm/torch/install/share/lua/5.1/optim/sgd.lua:44: in function 'sgd'
train.lua:160: in function 'train'
train.lua:236: in main chunk
[C]: in function 'dofile'
.../dlm/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670

When I use the following code, it works great:
local SeLU  = function(input)
  local output = 0.5 * (torch.abs(input) + input)
  return output
end

Is input always a torch tensor or scalar? You're returning a scalar, which might cause weirdness.

Try torch.le(input, 0).value instead of torch.le(input, 0)

I am using cuddn...
Input and output are tensors...
The following code is ok:
local seluFunc = function(input)
  local output, aux, aux2, aux3
  aux = (seluc/selua+1)/2
  aux2 = ((1-aux)*torch.abs( input+selub)+aux*( input+selub))-selub
  aux3 = -((1-aux)*torch.abs(-aux2+selub)+aux*(-aux2+selub))+selub
  output = selua*aux3
  return output
end

But I still don't understand what is wrong with the code bellow:
local seluFunc2 = function(input)
  local output, lessX, equalX, graterX, aux1, aux2, aux3
  lessX = torch.lt(input, -selub)
  aux1 = torch.gt(input, -selub)
  aux2 = torch.lt(input, selub)
  equalX = torch.cmul(aux1, aux2)
  graterX = torch.gt(input, selub)
  aux3 = torch.add(lessX,equalX)
  output = torch.add(aux3,graterX)
  return output
end

Full logs:
In 3 module of nn.Sequential:
In 54 module of nn.Sequential:
In 3 module of nn.Sequential:
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:77: attempt to index local 'input' (a nil value)
stack traceback:
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:77: in function 'checkInputDim'
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:130: in function <...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:128>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function </home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:78>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function </home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:78>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function 'backward'
train.lua:152: in function 'opfunc'
/home/dlm/torch/install/share/lua/5.1/optim/sgd.lua:44: in function 'sgd'
train.lua:158: in function 'train'
train.lua:234: in main chunk
[C]: in function 'dofile'
.../dlm/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670
WARNING: If you see a stack trace below, it doesn't point to the place where this error occured. Please use only the one above.
stack traceback:
[C]: in function 'error'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:67: in function 'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function 'backward'
train.lua:152: in function 'opfunc'
/home/dlm/torch/install/share/lua/5.1/optim/sgd.lua:44: in function 'sgd'
train.lua:158: in function 'train'
train.lua:234: in main chunk
[C]: in function 'dofile'
.../dlm/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670

Does it work on plain NN, on the CPU?
On Sun, Jun 19, 2016 at 7:10 AM David Macêdo<EMAIL_ADDRESS>wrote:

I am using cuddn...
Input and output are tensors...
The following code is ok:
local seluFunc = function(input)
local output, aux, aux2, aux3
aux = (seluc/selua+1)/2
aux2 = ((1-aux)torch.abs( input+selub)+aux( input+selub))-selub
aux3 = -((1-aux)torch.abs(-aux2+selub)+aux(-aux2+selub))+selub
output = selua*aux3
return output
end
But I still don't understand what is wrong with the code bellow:
local seluFunc2 = function(input)
local output, lessX, equalX, graterX, aux1, aux2, aux3
lessX = torch.lt(input, -selub)
aux1 = torch.gt(input, -selub)
aux2 = torch.lt(input, selub)
equalX = torch.cmul(aux1, aux2)
graterX = torch.gt(input, selub)
aux3 = torch.add(lessX,equalX)
output = torch.add(aux3,graterX)
return output
end
Full logs:
In 3 module of nn.Sequential:
In 54 module of nn.Sequential:
In 3 module of nn.Sequential:
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:77: attempt to
index local 'input' (a nil value)
stack traceback:
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:77: in
function 'checkInputDim'
...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:130: in
function <...lm/torch/install/share/lua/5.1/nn/BatchNormalization.lua:128>
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function
'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function
'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function
[C]: in function 'xpcall'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:63: in function
'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function
'backward'
train.lua:152: in function 'opfunc'
/home/dlm/torch/install/share/lua/5.1/optim/sgd.lua:44: in function 'sgd'
train.lua:158: in function 'train'
train.lua:234: in main chunk
[C]: in function 'dofile'
.../dlm/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main
chunk
[C]: at 0x00406670
WARNING: If you see a stack trace below, it doesn't point to the place
where this error occured. Please use only the one above.
stack traceback:
[C]: in function 'error'
/home/dlm/torch/install/share/lua/5.1/nn/Container.lua:67: in function
'rethrowErrors'
/home/dlm/torch/install/share/lua/5.1/nn/Sequential.lua:84: in function
'backward'
train.lua:152: in function 'opfunc'
/home/dlm/torch/install/share/lua/5.1/optim/sgd.lua:44: in function 'sgd'
train.lua:158: in function 'train'
train.lua:234: in main chunk
[C]: in function 'dofile'
.../dlm/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main
chunk
[C]: at 0x00406670
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/twitter/torch-autograd/issues/118#issuecomment-226991597,
or mute the thread
https://github.com/notifications/unsubscribe/AAJ4j6iVC_i76tfAijynMxiBkjTK-qMyks5qNSOJgaJpZM4IalSN
.


Sticky scroll on first line sticks around

Testing #156175

Enable stick scrolling
In a TS file:

class Foo {
}

Scroll down to trigger sticky scrolling then scroll back up to the top of the file

bug
The sticky scrolling on the first line remains, preventing me from selecting text on that line

Maybe #156566

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Major revisions

Fixes a bunch of issues, listed in the change log. The biggest change is that the alt/az calculation is fixed such that it matches the astropy calculation to a respectable precision. Altitudes (or, rather, zenith angles) match to 1e-5, and did before these changes. The azimuths, however, were off due to an erroneous assumption about the North pole position in ICRS (not accounting for the drift of the Earth's north pole with respect to the north celestial pole). They are now correct to within an arcminute, when previous they were off by a half degree in some cases.
For this big a change, I've raised the version number, since data generated before and after this may differ slightly.
Closes #27

I've tagged @steven-murray to review because this addresses an issue he raised.

Hi Steven. Thanks for the feedback! I've tried to address most of your comments. I should note that this PR is focused on fixing specific issues with the az/za calculation and passing frequency interpolation settings. Most style and documentation issues will be left for future work.

Looks like you need a review from @nkern as well, since I don't have write access.


ADD ISSUE_TEMPLATE

Hello there,
I would like to add an issue template for your repository. This template would have four issues namely bug, documentation, feature, proposal. Kindly assign me this issue as a part of DWOC.
THANK YOU

Not Required

Not Required


Fix (Exist): File.exists method is deprecated and no longer exist

Hello :)
We currently have an issue with upgrading our Monolith to Ruby 3.2.0, the problem is coming from the exists method which has been deprecated before Ruby 2.5 (https://ruby-doc.org/core-2.5.0/File.html#method-c-exists-3F
) and no longer exist (the irony ahah) in Ruby 3.2.0
Do you think these changes are relevant to you ? :)
Thank you for taking the time to review my PR.
Best regards,
Thornolf

No problem, thank you for merging :)


PostNL integration broken.

Home Assistant release with the issue:

0.103.0
Last working Home Assistant release (if known):
I think 0.101
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on pi4 (32 bit)
Integration:

https://www.home-assistant.io/integrations/postnl/
Description of problem:
postnl sensor not created
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: postnl
  username: !secret POSTNL_USERNAME
  password: !secret POSTNL_PASSWORD

Traceback (if applicable):
Mon Dec 16 2019 15:02:37 GMT+0100 (Central European Standard Time)
Can't connect to the PostNL webservice
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/postnl_api/postnl_api.py", line 179, in _request_login
    data = response.json()
  File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/simplejson/__init__.py", line 525, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.7/site-packages/simplejson/decoder.py", line 370, in decode
    obj, end = self.raw_decode(s)
  File "/usr/local/lib/python3.7/site-packages/simplejson/decoder.py", line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/postnl/sensor.py", line 46, in setup_platform
    api = PostNL_API(username, password)
  File "/usr/local/lib/python3.7/site-packages/postnl_api/postnl_api.py", line 57, in __init__
    self._request_login()
  File "/usr/local/lib/python3.7/site-packages/postnl_api/postnl_api.py", line 182, in _request_login
    raise (UnauthorizedException())
postnl_api.postnl_api.UnauthorizedException

Additional information:

Duplicate of #20696, therefore please close this issue and comment on the linked issue.

Duplicate of #20696, closed here.


Output Terraform

For Terraform users, it would be handy if the CLI could export a TF config

We could possibly modify an existing terraform declaration... I don't think it would be worthwhile to generate new.
@adjohn I'd like confirmation that there's a user-request here.


Doesn't release memory until job queue is empty?

I have an application using Thread Pool that will often result in job queues of more than 25,000 jobs. This is expected and the delay in processing the jobs isn't a problem. However, the memory consumed by the queue doesn't seem to be released once the job is executed. At peak the resident memory of the application might reach 1GB when the job queue is peaking. However, when the job_queue reaches zero the resident memory is largely cleared.
I've run everything through valgrind multiple times and it's not indicating any memory leaks when the application shuts down gracefully. When I put in a dummy call back that keeps the queue at a minimum size the memory consumption is pretty low. The only thing that seems related to the total memory consumption is the job queue length. That the resident memory clears once the queue is empty is odd to me. Do you have any suggestions?
Thanks

I guess you are referring to the 'jobqueue_destroy' function
This function is only used in 'thpool_destroy', and the release queue should only be called when the thread pool is released.
Here is the author's explanation


F service platform UI

Depends on new localization keys.

also remove the ':' after Dienstname

the space between the name nad the config can be smaller, also please include a screenshot with an opened configuration

still the space between the name and the body can be reduced

Textbox is now set on stretch, the space was minimal reduced. It has to be like that because of localization the text box has to adjust to the label before the text box.


Tracking issue for the Redis JSON support

Motivation
After #1803, we have basic support of RedisJSON, but massive amount of commands remain unsupported:

[x] #1806
[ ] #1807
[ ] #1808
[x] #1809
[x] #1810
[ ] #1811
[x] #1812
[ ] #1813
[ ] #1814
[ ] #1815
[ ] #1816
[ ] #1817
[ ] #1818
[ ] #1819
[x] #1820
[ ] #1821
[ ] #1822
[ ] #1823
[ ] #1824
[ ] #1825
[x] #1826

We need to support all of these commands to make our JSON support more complete and powerful.
Other pull requests related to JSON:

[x] #1803
[x] #1828
[x] #1840
[ ] #1829
[x] #1843

Call for Contribution
Feel free to pick up any issue and finish it!
You can request to be assigned with any issue from this list and try to implement it.
How to implement

Check the RedisJSON document and the document for the specific command (e.g. JSON.SET)
Check the document of Kvrocks data structures design and #1803 to understand how Kvrocks implements Redis data types upon RocksDB. (and also the document of jsoncons which is used in kvrocks to parse/serialize JSON.)
Add corresponding methods to types/json.h, types.redis_json.h/cc, and command interface (Parse and Execute function) to commands/cmd_json.cc. (Note: types/json.h is just wrapper functions of jsoncons library which is not related to storage, while types/redis_json.h is about how to encode/decode JSON from storage (IO operations))
Add corresponding C++ unit test cases and Golang unit test cases for your newly implemented command.
Open your pull requests and we will review them promptly!

I found that some of the command was marked as deprecated in the Redis document, do you guys still want to support it?
For example:
JSON.RESP

@Kelvinyu1117 I think we can complete the active commands first and the deprecated commands are also good to support if users did have solid reasons. cc @PragmaTwice

Can the JSON feature of KVRocks be officially used in a production environment?

@PragmaTwice All JSON commands are done and we can close this tracking issue now.


[ENH] Adding CNTC network for classification from sktime-dl

Reference Issues/PRs

Fixes #3153.
What should a reviewer concentrate their feedback on?

One thing I was trying was to make the code a bit more readable (compared to what it was on sktime-dl). So let me know any changes I can make towards that goal.
PR checklist

For all contributions

[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.

I have a basic design question which I wanted to confirm if I am doing correctly / what can be done:

For cntc, the input X needs to be modified into [X2, X, X].
X2 is determined by a function prepare_input in CNTCClassifer
It works correctly for fit, since I am able to modify the input before sending it to the model.
For predictions, if I were to write _predict_proba (get X2 here) in CNTCClassifier (and then call super()._predict_proba()), the issue is that it has a line X = X.transpose(0, 2, 1), which needs to be done before calculation ofX2`

Is there a way to take care of this? My current approach would be to completely overwrite both _predict and _predict_proba in CNTCClassifier and not call the functions in the super class at all, but was wondering if there is a better solution to this?

This particular estimator requires adding a soft dependancy (keras_self_attention)

@miraep8 wrote it up here:
https://github.com/alan-turing-institute/sktime/pull/3416
(also in the latest doc now)

@fkiraly
Done, please check and let me know if this is correct?


[AWS UPI] OKD 4.4 console fails to start with connection refused

OKD: 4.4.0-0.okd-2020-04-21-163702-beta4 (and older betas/releases)
Initial image: stable 31.20200407.3.0 (AWS AMI ami-07159149bd9fd748f)
100% reproducible: have tried a number of other OKD 4.4 releases, all results in the same issue
oc adm must-gather archive: https://keybase.pub/andygeorge/openshift/must-gather.local.8590515517328253782.tar.gz
Using the AWS UPI instructions, we're able to get a 3 master/3 worker cluster up, but install-complete eventually fails due to the console (and its pods) never coming up successfully:
[core@ip-10-127-12-110 ~]$ oc get pods -n openshift-console
NAME                         READY   STATUS    RESTARTS   AGE
console-5f7566d6b6-cfxsj     0/1     Running   3          11m
console-74ddfdc585-vzgp6     0/1     Running   3          11m
console-7c777c67c6-ts64q     0/1     Running   1          4m52s
downloads-7db88fb486-l77m9   1/1     Running   0          14m
downloads-7db88fb486-rsvgg   1/1     Running   0          14m

The behavior is similar to what was seen in #141, but instead of EOFs returned by oauth-openshift, we see refused connections - I assume nothing is binding to tcp/443:
[core@ip-10-127-12-110 ~]$ oc describe -n openshift-console pod/console-5f7566d6b6-cfxsj
Name:                 console-5f7566d6b6-cfxsj
Namespace:            openshift-console
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 ip-10-127-11-58.us-east-2.compute.internal/<IP_ADDRESS>
Start Time:           Fri, 24 Apr 2020 15:58:58 +0000
Labels:               app=console
                      component=ui
                      pod-template-hash=5f7566d6b6
Annotations:          console.openshift.io/console-config-version: 16007
                      console.openshift.io/default-ingress-cert-config-version: 12754
                      console.openshift.io/image: quay.io/openshift/okd-content@sha256:ae96918edcbe07424f38f9976132c8ebe694050ffb46cf526df3a0da68be7b8d
                      console.openshift.io/oauth-secret-version: 16027
                      console.openshift.io/proxy-config-version: 443
                      console.openshift.io/service-ca-config-version: 16014
                      console.openshift.io/trusted-ca-config-version: 16016
                      k8s.v1.cni.cncf.io/networks-status:
                        [{
                            "name": "openshift-sdn",
                            "interface": "eth0",
                            "ips": [
                                "<IP_ADDRESS>"
                            ],
                            "dns": {},
                            "default-route": [
                                "<IP_ADDRESS>"
                            ]
                        }]
                      openshift.io/scc: restricted
                      operator.openshift.io/pull-spec: quay.io/openshift/okd-content@sha256:ae96918edcbe07424f38f9976132c8ebe694050ffb46cf526df3a0da68be7b8d
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/console-5f7566d6b6
Containers:
  console:
    Container ID:  cri-o://e070f86e644677eaf9313d36e58aa4a95a7f1b90f568f5ae6a272c0e992df861
    Image:         quay.io/openshift/okd-content@sha256:ae96918edcbe07424f38f9976132c8ebe694050ffb46cf526df3a0da68be7b8d
    Image ID:      quay.io/openshift/okd-content@sha256:ae96918edcbe07424f38f9976132c8ebe694050ffb46cf526df3a0da68be7b8d
    Port:          443/TCP
    Host Port:     0/TCP
    Command:
      /opt/bridge/bin/bridge
      --public-dir=/opt/bridge/static
      --config=/var/console-config/console-config.yaml
      --service-ca-file=/var/service-ca/service-ca.crt
    State:       Running
      Started:   Fri, 24 Apr 2020 16:09:07 +0000
    Last State:  Terminated
      Reason:    Error
      Message:   ec.com/oauth/token failed: Head https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-04-24T16:08:07Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com/oauth/token failed: Head https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-04-24T16:08:22Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com/oauth/token failed: Head https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-04-24T16:08:37Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com/oauth/token failed: Head https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-04-24T16:08:47Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com/oauth/token failed: Head https://oauth-openshift.apps.os-test.test.us-east-2.aws.int.kennasec.com: dial tcp <IP_ADDRESS>:443: connect: connection refused

We also wish to run our master nodes as infra nodes, so I followed some instructions in #141, and got those to come up correctly, but that doesn't affect the openshift-console pods.
Not sure if this is actually a bug, and feels like we're just missing something simple in our configuration - any thoughts or ideas of what to try next?

@andygeorge
Hey, I think I gave some incorrect advice in #141.  If your masters were schedulable before, and you followed the instructions that I gave for making them into infra pods, I have since discovered that they still need to be schedulable...  I killed one of the ingress pods to see if it would move to another master node.  It did not... It was stuck pending for a node that was schedulable.  my bad.
Do this to make the masters schedulable again if your Ingress pods are stuck pending.
oc patch scheduler cluster --patch '{"spec":{"mastersSchedulable":true}}' --type=merge

There is probably a "right" way to put the ingress pods on the master nodes using taints and tolerations, yet not label them as worker nodes.  I see if I can figure it out and post here.
@vrutkovs Vadim, do you know how to do that?  Should one do that?  (philosophical question.)

The right way to place ingress pods is via configuration: https://docs.okd.io/latest/networking/ingress-operator.html#nw-installation-ingress-config-asset_configuring-ingress.
Router pods have been created, but LB failed to be created:
Error syncing load balancer: failed to ensure load balancer: could not     find any suitable subnets for creating the ELB in events of openshift-ingress namespace.
I'm not entirely sure why is that happening - missing permissions / some AWS error? Could you have a look on AWS console?

@vrutkovs Is it possible that error is because we only have an internal load balancer (we don't want the cluster to have an external ingress), and our default ingresscontroller is External?
I did try an oc replace --force to change the default ingresscontroller to Internal, but that command hung all weekend and did nothing, so I'm going to try setting it to Internal on cluster build right now.

Ingesting an IngressController CR to point to Internal does seem to get the service to see the internal LB (yay!). I'm now getting new errors that I'm troubleshooting:
6m          Warning   SyncLoadBalancerFailed     service/router-default                 Error syncing load balancer: failed to ensure load balancer: Multiple untagged security groups found for instance i-0f8e28a48c461d2d7; ensure the k8s security group is tagged
4m49s       Warning   SyncLoadBalancerFailed     service/router-default                 Error syncing load balancer: failed to ensure load balancer: Multiple untagged security groups found for instance i-07697825b303ff6bd; ensure the k8s security group is tagged
99s         Normal    EnsuringLoadBalancer       service/router-default                 Ensuring load balancer
4m15s       Warning   SyncLoadBalancerFailed     service/router-default                 Error syncing load balancer: failed to ensure load balancer: error detaching AWS loadbalancer from subnets: "InvalidConfigurationRequest: Requested configuration change for LoadBalancer \"aee713a49f9a14013b79b3e8b3471710\" is invalid because you attempted to detach all the subnets for this LoadBalancer and a LoadBalancer cannot be attached to zero subnets in VPC.\n\tstatus code: 409, request id: 5d6dfba0-8f4c-43d1-b78b-9b53c8faaa61"
4m10s       Warning   SyncLoadBalancerFailed     service/router-default                 Error syncing load balancer: failed to ensure load balancer: error detaching AWS loadbalancer from subnets: "InvalidConfigurationRequest: Requested configuration change for LoadBalancer \"aee713a49f9a14013b79b3e8b3471710\" is invalid because you attempted to detach all the subnets for this LoadBalancer and a LoadBalancer cannot be attached to zero subnets in VPC.\n\tstatus code: 409, request id: 122d7ec7-44e3-4a35-ac77-b3b7db5cdb0f"

@vrutkovs thank you so much, that got me pointed in the right directly!! I didn't have my tagging set correctly on our VPC's subnets. Works now!
For anyone else out there who finds this, I needed to make sure my VPC's subnets had the following Tags:
On both public and private subnets:
"kubernetes.io/cluster/$CLUSTERNAME" = "owned"
On public subnets:
"kubernetes.io/role/elb = "1"
On private subnets:
"kubernetes.io/role/internal-elb" = "1"

@andfasano ,hello,I also encountered a similar problem, mine is bare-metal deploy ocp4.4, can you provide some ideas, thank you very much
[root@cloud-com-1 registry]# oc describe pod console-6b899d75d6-5k9qn -n openshift-console
Name:                 console-6b899d75d6-5k9qn
Namespace:            openshift-console
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 master1/<IP_ADDRESS>
Start Time:           Tue, 19 May 2020 12:02:09 +0000
Labels:               app=console
component=ui
pod-template-hash=6b899d75d6
Annotations:          console.openshift.io/console-config-version: 132198
console.openshift.io/default-ingress-cert-config-version: 131913
console.openshift.io/image:
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:52465443a0c0f8e1d9dd8f2e3c7ec0e5d32dc438f181adf467ab883a6b283c26
console.openshift.io/oauth-secret-version: 132207
console.openshift.io/proxy-config-version: 733
console.openshift.io/service-ca-config-version: 132714
console.openshift.io/trusted-ca-config-version: 132202
k8s.v1.cni.cncf.io/networks-status:
[{
"name": "openshift-sdn",
"interface": "eth0",
"ips": [
"<IP_ADDRESS>"
],
"dns": {},
"default-route": [
"<IP_ADDRESS>"
]
}]
openshift.io/scc: restricted
operator.openshift.io/pull-spec:
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:52465443a0c0f8e1d9dd8f2e3c7ec0e5d32dc438f181adf467ab883a6b283c26
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/console-6b899d75d6
Containers:
console:
Container ID:  cri-o://bf6538ff52cd90498263209a63663b13888679da6f34946a141d3a100a307f9e
Image:         quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:52465443a0c0f8e1d9dd8f2e3c7ec0e5d32dc438f181adf467ab883a6b283c26
Image ID:      quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:52465443a0c0f8e1d9dd8f2e3c7ec0e5d32dc438f181adf467ab883a6b283c26
Port:          443/TCP
Host Port:     0/TCP
Command:
/opt/bridge/bin/bridge
--public-dir=/opt/bridge/static
--config=/var/console-config/console-config.yaml
--service-ca-file=/var/service-ca/service-ca.crt
State:       Running
Started:   Tue, 19 May 2020 12:16:16 +0000
Last State:  Terminated
Reason:    Error
Message:   T12:14:48Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-05-19T12:15:07Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-05-19T12:15:22Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-05-19T12:15:37Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-05-19T12:15:52Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2020-05-19T12:16:07Z auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.okd4-cluster.okd4.com/oauth/token failed: Head https://oauth-openshift.apps.okd4-cluster.okd4.com: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
  Exit Code:    2
  Started:      Tue, 19 May 2020 12:12:56 +0000
  Finished:     Tue, 19 May 2020 12:16:15 +0000
Ready:          False
Restart Count:  4
Requests:
  cpu:        10m
  memory:     100Mi
Liveness:     http-get https://:8443/health delay=150s timeout=1s period=10s #success=1 #failure=3
Readiness:    http-get https://:8443/health delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:  <none>
Mounts:
  /etc/pki/ca-trust/extracted/pem from trusted-ca-bundle (ro)
  /var/console-config from console-config (ro)
  /var/default-ingress-cert from default-ingress-cert (ro)
  /var/oauth-config from console-oauth-config (ro)
  /var/run/secrets/kubernetes.io/serviceaccount from console-token-2dwlb (ro)
  /var/service-ca from service-ca (ro)
  /var/serving-cert from console-serving-cert (ro)

Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
console-serving-cert:
Type:        Secret (a volume populated by a Secret)
SecretName:  console-serving-cert
Optional:    false
console-oauth-config:
Type:        Secret (a volume populated by a Secret)
SecretName:  console-oauth-config
Optional:    false
console-config:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      console-config
Optional:  false
service-ca:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      service-ca
Optional:  false
default-ingress-cert:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      default-ingress-cert
Optional:  false
trusted-ca-bundle:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      trusted-ca-bundle
Optional:  false
console-token-2dwlb:
Type:        Secret (a volume populated by a Secret)
SecretName:  console-token-2dwlb
Optional:    false
QoS Class:       Burstable
Node-Selectors:  node-role.kubernetes.io/master=
Tolerations:     node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/memory-pressure:NoSchedule
node.kubernetes.io/not-reachable:NoExecute for 120s
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 120s
Events:
Type     Reason     Age                 From               Message

Normal   Scheduled             default-scheduler  Successfully assigned openshift-console/console-6b899d75d6-5k9qn to master1
Normal   Pulled     15m                 kubelet, master1   Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:52465443a0c0f8e1d9dd8f2e3c7ec0e5d32dc438f181adf467ab883a6b283c26" already present on machine
Normal   Created    15m                 kubelet, master1   Created container console
Normal   Started    15m                 kubelet, master1   Started container console
Warning  Unhealthy  12m (x3 over 13m)   kubelet, master1   Liveness probe failed: Get https://<IP_ADDRESS>:8443/health: dial tcp <IP_ADDRESS>:8443: connect: connection refused
Normal   Killing    12m                 kubelet, master1   Container console failed liveness probe, will be restarted
Warning  Unhealthy  47s (x89 over 15m)  kubelet, master1   Readiness probe failed: Get https://<IP_ADDRESS>:8443/health: dial tcp <IP_ADDRESS>:8443: connect: connection refused
[root@cloud-com-1 registry]#

@fenggolang
This issue has been closed for a while.  You should probably open a new issue.  You'll get more visibility.
I noticed that it looks like things are trying to connect to port 8443 instead of 6443 or 443.  Unless you explicitly changed the configuration, OKD 4.4 does not use port 8443 for any connections.  external API traffic is on 6443, machine-config uses 22623, and all other traffic is either HTTP or HTTPs on 80 and 443 respectively.

Nevermind, those are internal cluster connections.  Those pods may very well be using 8443 internally...


minor edit for next release:

https://github.com/fivetran/dbt_fivetran_log/blob/master/.DS_Store
.DS_Store file should be added to .gitignore

Addressed!


Remove campus routing

Updating this demo to v200 is not going to be straightforward, because Runtime is no longer compatible with the locator format in use and I don't have access to the source data.
Regardless, this should probably be removed because it duplicates functionality that is now available out of the box with ArcGIS Indoors. There is an existing geocode and route on mouse move that demonstrates the core concepts for working with locators, and the Toolkit components make working with floor-aware maps and search trivial.

it duplicates functionality that is now available out of the box with ArcGIS Indoors.

AFAIK that app isn't open source, and not an example of how to build an indoors application. The application also demonstrates a few other things, like partial resumable downloads from portal, and working with. I'd leave it as-is until we can get an updated version of the data.


AndroidThreeTen.init() Is it required to call in latest version 1.6.8

Are we need to call AndroidThreeTen.init() in latest version of library (1.6.8). Can you please provide change doc.

Seems like you want https://github.com/JakeWharton/ThreeTenABP. You'll find a change log there as well.

I have updated from 'com.jakewharton.threetenabp:threetenabp:1.2.4' to  'org.threeten:threetenbp:1.6.8'. So now are we need to initialise in Application onCrate.

@JakeWharton Can you please confirm - https://github.com/ThreeTen/threetenbp/issues/189#issuecomment-1944082837
Didn't found the change in any official document.

If you are migrating away from ThreeTenABP to ThreeTenBP then you do not need to do anything to initialize the timezone database. It will be read from the jar resources automatically.
I would also suggest profiling your startup after such a change. You should consider a custom timezone database loader that is perhaps lazy or eagerly done on a background thread during splash screen animation because there will likely be non-trivial impact.

Closing as discussion better suited to ThreeTenABP


nist.py regexp breaks in py27

Our CI server reports error nothing to repeat on line https://github.com/nltk/nltk/blob/develop/nltk/tokenize/nist.py#L110
@alvations: would you mind having a look at this please?

Hmmm... It's a little strange that the error doesn't happen locally:
>>> import re
>>> from nltk.corpus import perluniprops
>>> from six import text_type
>>> pup_symbol = text_type(''.join(set(perluniprops.chars('Symbol'))))
>>> symbol_regex = re.sub(r'[]^\\-]', r'\\\g<0>', pup_symbol)
>>> re.compile(u"({s})".format(s=symbol_regex))
<_sre.SRE_Pattern object at 0x35d9930>

Let me take a closer look.

Looks like there's a [] missing in the compiled regex but it still doesn't throw the error.
>>> sent = 'this is a foo' + pup_symbol[1] +'sentence.'
>>> patt =  re.compile(u"({s})".format(s=symbol_regex))
>>> patt.sub(' \\1 ', sent)
u'this is a foo\u2604sentence.'
>>> patt =  re.compile(u"([{s}])".format(s=symbol_regex))
>>> patt.sub(' \\1 ', sent)
u'this is a foo \u2604 sentence.'

Argh, github.com is doing strange thing with bad wifi... Reverting the latest https://github.com/nltk/nltk/commit/052cc88295d122834b7a21e1c73fdceb23130d8f and doing a fresh PR.


batch: Enable distributed tracing to trace local execution.

This issue consists of following issues:

Enable distributed tracing. In this branch https://github.com/risingwavelabs/risingwave/compare/main...renjie/batch_mini_trace I have enabled tracing, but distributed tracing and slow request filtering is missing.  You can see https://crates.io/crates/tracing-honeycomb for enabling distributed  tracing.
Implement trace statement:
https://docs.pingcap.com/tidb/stable/sql-statement-trace
You can refer to Subscriber api for reference.

cc @skyzh  @wangrunji0408   Any suggestions?

cc @BugenZhao

Cool.

I took a look at mini tracing, and it seems that it works well with our requirement, but it can't be used in rpc, right?

We'll need to implements things by ourselves if we want to carry tracing spans within RPCs.

Hmm, I think tracing has better support for this and I'm investigating it. Why we switch to minitrace? Just for performance?

https://docs.rs/tracing-jaeger/latest/tracing_jaeger/fn.current_dist_trace_ctx.html

Why we switch to minitrace? Just for performance?

Better API, better flexibility and allows us to read into spans. This is useful for filtering and tracing slow requests.

One concern with minitrace is the ecosystem. If we use minitrace, it would be difficult for use to inspect other libraries such tonic, object store api?

tonic doesn't use tracing spans for now.

tonic doesn't use tracing spans for now.

https://github.com/hyperium/tonic/blob/master/tonic/Cargo.toml
They are using tracing library.

They use it for logging, so it doesn't matter.

https://github.com/hyperium/h2/blob/e4cf88c1a19a7f7823dfaa9eb4c6a19a24f4ead8/src/server.rs

Tracing provides little control over spans. e.g., we cannot filter slow requests and only report slow requests to jaeger. It would be fine to have two tracing facilities in the codebase. RisingWave itself will use minitrace in release mode. If it is necessary to trace libraries like h2, then it would be good to enable it on demand.

During my debugging process I feel tracing api is friendly to use and setup, and it has native support distributed tracing. But we do need to investigate it's subscriber/filter api to filter slow requests.

Hi, what't the progress now?

I'll continue with this.

#10637


Component: Anchor Link functional specifications

User Story

As a [user role below]:
DDS developer

I need to:
have the Anchor Link functional specs

so that I can:
so that I can properly code the Anchor Link component that meets the Design functions and intent

Additional information

Overview and scope of the engineering work should be included in the linked epic (#5069 )
Design Issue #173
Development issue (#5072 )
Visual Designs & Functional Design Specs Box folder link(TBD)

Acceptance criteria

[ ] Documented Anchor Link functional specifications
[ ] Sent and/or presented the specs to Design and Engineering for their review and comments
[ ] Additional stories are created, if needed, for any work to be done in future sprints

Table of contents — horizontal
Functional specs
Prototype sticky example
Design specs


Added a Markdown file to document build.txt

hmm, do we not have enough on the documentation wiki? The problem with the markdown is that it's only really viewable in github, and few people use the repo

The idea is to move the documentation which is now only in the wiki next to the code it documents, then generate HTML documentation from that


Error while saving < filename > . Could not save Image.

Hi Khalim,
I am fairly new to GIMP. However I found your plugin very useful for the side project i am doing. I tried to use your plugin through gimp. I imported a PSD file and was trying to export the layers as png's. I am getting this error message

Basically for some reason the file is not getting saved. I have checked the permissions of the folders that does not seem to be a problem.
I am on GIMP version 2.8.10 and python 2.7.6.
Thanks,
Ravi

Hello Ravi,
first of all I apologize for the late reply, I was busy working on other projects (which took priority).
Have you tried exporting in a different file format?
Do you still get the error message when you export a layer or an image in PNG using the GIMP's export menu?

Closing this as no further information was provided to the original issue.


Out of date Atoms info for MD

Some keys self.dyn.atoms.info, such as "real_time" and "density", are not necessarily updated before Atoms objects are written out.
For example, these are set in get_stats, but not updated when writing out the trajectory, restart files, etc., meaning these values only change at the frequency the statistics are updated.
We could either remove these keys before writing out other files, or update them before writing.
For the latter, it would be relatively straightforward for "density", but possibly slightly more complicated for "real_time" due to the way we update it.
However, currently "real_time" isn't actually printed in the info due to its format, so we could leave that and only update "density". e.g. by updating _set_time_step

density is needed, especially for npt

Would you assume it's always in the info though, since it can always be calculated if needed?
(Just wondering, I'm perfectly happy for it to be fixed so it's still written, but up-to-date.)


Support toukoucity.to

[x] I've verified and I assure that I'm running youtube-dl 2017.02.07

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Site support request (request for adding support for a new site)

Support toukoucity.to
Support for http://toukoucity.to should be pretty easy, as the video is always called "video.mp4" in the page's source. Example below.
$ youtube-dl --version
2017.02.07
$ youtube-dl http://toukoucity.to/video/VpvpP3ghin/
[debug] System config: []
[debug] User config: [u'--no-overwrites', u'--continue', u'--verbose', u'-f', u'best']
[debug] Custom config: []
[debug] Command-line args: [u'http://toukoucity.to/video/VpvpP3ghin/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.02.07
[debug] Python version 2.7.9 - Linux-3.16.0-4-686-pae-i686-with-debian-8.7
[debug] exe versions: avconv 11.8-6, avprobe 11.8-6
[debug] Proxy map: {}
[generic] VpvpP3ghin: Requesting header
[redirect] Following redirect to http://toukoucity.to/
[generic] toukoucity: Requesting header
WARNING: Falling back on generic information extractor.
[generic] toukoucity: Downloading webpage
[generic] toukoucity: Extracting information
ERROR: Unsupported URL: http://toukoucity.to/
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 1741, in _real_extract
doc = compat_etree_fromstring(webpage.encode('utf-8'))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2526, in compat_etree_fromstring
doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2515, in _XML
parser.feed(text)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
ParseError: not well-formed (invalid token): line 4, column 451
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 696, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 369, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2589, in _real_extract
raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://toukoucity.to/

additional info:
Source of page and the video.mp4 link. Which is easy to download, but youtube-dl would make it even easier.
-From URL: "view-source:http://toukoucity.to/video/VpvpP3ghin/"
so.addVariable('file','http://<IP_ADDRESS>/p1/VpvpP3ghin/video.mp4');
So
wget http://<IP_ADDRESS>/p1/VpvpP3ghin/video.mp4 -O toukoucity-VpvpP3ghin.mp4
works now.
Note that the IP number and sub-dir "P1" are subject to change depending on the URL.
I don't think the site has alternative formats, so http://toukoucity.to/video/FFFFFFFFFF/ seems to be the only URL format.

https://github.com/rg3/youtube-dl/pull/3536/commits
This was done before but never integrated/pulled into the project (AFAIK) and therefore I assume this provider is not allowed?


Add query canceled exception

Added support to distinguish QueryCancel errors from Vertica:
https://my.vertica.com/docs/6.1.x/HTML/index.htm#22448.htm

Any feedback on this?

could you sign the electronic CLA? its a new requirement for all contributors.

Sure, all set.


Getting weird output

Hi,
I am not able to replicate the results correctly.
How do I get the final output?
For example,
I used the following code
python histoGAN.py --name Faces_histoGAN --generate True --target_his ./target_images/1.jpg --gpu 0
And got this output which seems to be noise

How can I use this to generate face samples as shown in the repo?
Thank you

It seems either you didn't download the pre-trained model or the path of the model is not correct. You should download the trained model and copy it in ./models/test_histoGAN/model_0.pt (it doesn't necessarily be 0, it can be any number. The code will take the highest number if more than one model exist).


Update bower error msg

Stating that the package couldn't be found on any bower error is confusing when things like version conflicts occur (This happens a lot with bower, especially when adding the ionic-platform-web-client).
Ideally, we should make bower a dependency of the cli, and not be installing via exec('some-command-here'), but this should at least provide a bit better info.

:+1: lgtm


input_field.py: IndexError: list index out of range

Let's use example from the README.md
import pytermgui as ptg

with ptg.WindowManager() as manager:
    demo = ptg.Window(
        ptg.Label("[210 bold]Hello world!"),
        ptg.Label(),
        ptg.InputField(prompt="Who are you?"),
        ptg.Label(),
        ptg.Button("Submit!")
    )

    manager.add(demo)
    manager.run()

After running this script with python 3.10.5 and pytermgui 6.4.0 I see this image:

which is far off

After seeing this image, one can write a lot of A into the input box.

Then clicking invisible [ Submit! ] button will trigger IndexError:
  File "/home/senyai/projects/pyminimg/cyclops_go.py", line 341, in <module>
    manager.run()
  File "/home/senyai/.local/lib/python3.10/site-packages/pytermgui/window_manager/manager.py", line 197, in run
    self._run_input_loop()
  File "/home/senyai/.local/lib/python3.10/site-packages/pytermgui/window_manager/manager.py", line 143, in _run_input_loop
    self.process_mouse(key)
  File "/home/senyai/.local/lib/python3.10/site-packages/pytermgui/window_manager/manager.py", line 515, in process_mouse
    window.handle_mouse(event)
  File "/home/senyai/.local/lib/python3.10/site-packages/pytermgui/widgets/containers.py", line 796, in handle_mouse
    handled = widget.handle_mouse(event)
  File "/home/senyai/.local/lib/python3.10/site-packages/pytermgui/widgets/input_field.py", line 317, in handle_mouse
    line = self._lines[y_offset]
IndexError: list index out of range

I tried gnome-terminal and alacritty which gave me same error and visuals. Hope it help.

Hey there! Sorry about the long delay, had some things life to handle and I got a bit wrapped up in the new TIM implementation.
The IndexError issue is something I've run into but I haven't isolated before this issue. It should be relatively easy to fix. The inaccuracy in the README stems from me forgetting to implement a prompt parameter into the new InputField, which once again will be fixed relatively soon.
This work is planned after the next release at the moment, but it might come before if things work out differently. The tim-v3 branch has gotten very large in terms of API changes and new functionality, so it makes things easier if I focus on that area for now.

Should be fixed now! Could you please confirm it works on the latest commit?
P.S. Thank you for the code example, it made debugging way easier!

Back from vacation. pytermgui is uninstallable (in fedora):
python -m pip install pytermgui -U
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: pytermgui in /home/senyai/.local/lib/python3.10/site-packages (6.4.0)
Collecting pytermgui
  Using cached PyTermGUI-7.1.0.tar.gz (18.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package pytermgui produced metadata for project name unknown. Fix your #egg=pytermgui fragments.
WARNING: Discarding https://files.pythonhosted.org/packages/97/45/53ea7da6c280c6555671c34dbf289c14444bf3741b5b3ee0a08ec546824e/PyTermGUI-7.1.0.tar.gz#sha256=1bd01209d5ed223748b704d5cddef404d10744125dbdfc63f06d17589d547ba6 (from https://pypi.org/simple/pytermgui/) (requires-python:>=3.8). Requested unknown from https://files.pythonhosted.org/packages/97/45/53ea7da6c280c6555671c34dbf289c14444bf3741b5b3ee0a08ec546824e/PyTermGUI-7.1.0.tar.gz#sha256=1bd01209d5ed223748b704d5cddef404d10744125dbdfc63f06d17589d547ba6 has inconsistent name: filename has 'pytermgui', but metadata has 'unknown'
  Using cached PyTermGUI-7.0.0.tar.gz (18.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package pytermgui produced metadata for project name unknown. Fix your #egg=pytermgui fragments.
WARNING: Discarding https://files.pythonhosted.org/packages/2e/22/0f3f99568aabec709154e7061111257e664bf4fcae49d32162c2d7bbf808/PyTermGUI-7.0.0.tar.gz#sha256=ef7fd086694cb108eb5bea5475d58a35bc9df22d0802c032d6b5d1fccc8febc8 (from https://pypi.org/simple/pytermgui/) (requires-python:>=3.8). Requested unknown from https://files.pythonhosted.org/packages/2e/22/0f3f99568aabec709154e7061111257e664bf4fcae49d32162c2d7bbf808/PyTermGUI-7.0.0.tar.gz#sha256=ef7fd086694cb108eb5bea5475d58a35bc9df22d0802c032d6b5d1fccc8febc8 has inconsistent name: filename has 'pytermgui', but metadata has 'unknown'

That's super odd. What version of pip are you using?

It's 21.3.1 in fedora. I tried pip 22.2 but nothing changed. I've never seen an error like this.

Have you tried running pip cache purge before installation? Maybe something got corrupted on the way.

No. Will try tomorrow.

Nope

I was able to install latest PyTermGUI on Ubuntu machine and there's no IndexError there. Let's leave Fix your #egg=pytermgui fragments till someone else encounters it, might be something Fedora specific.

I haven't seen it either, but it likely is something to do with the new build system. I have a change reversal (going from PyTermGUI -> pytermgui for the package [not module] name) that might target it, so if it's okay with you I might ping you here when that is released.
Thanks for (both) report(s)!

It worked!
python -m pip install PyTermGUI --user
Collecting PyTermGUI
  Downloading pytermgui-7.2.0-py3-none-any.whl (172 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 172.7/172.7 kB 2.6 MB/s eta 0:00:00
Requirement already satisfied: typing-extensions in /usr/lib/python3.10/site-packages (from PyTermGUI) (<IP_ADDRESS>)
Installing collected packages: PyTermGUI
Successfully installed PyTermGUI-7.2.0

[notice] A new release of pip available: 22.2 -> 22.2.2
[notice] To update, run: python -m pip install --upgrade pip

Nice! Something was wring with the setuptools way of building from pyproject.toml, but Hatch seems to have fixed that.


Update map-show-traffic.md

updated metadata

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

#sign-off

@jinzh-azureiot: I'm sorry - only the author of this article, @jinzh, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@jinzh-azureiot - a couple of notes about this PR:

the author metadata value is your github account. Can you update this PR so that the value is your github account name?
since you're a Microsoft employee in a content role, you should be using the private repos to make document edits and contributions.

Here's more information about number 2:
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.


storage driver sftp, Exception "This driver does not support retrieving URLs."

Version information

Laravel: v8.12.3
Voyager: v1.4
PHP: v7.4.3
Database: MySQL 5.7

Description
When i use sftp storage driver, and go to admin panel i get RuntimeException "This driver does not support retrieving URLs."
But went i test this code, all work fine and i not get Exception.
$exists = Storage::disk('sftp')->exists('users/default.png');
Code below, return Exception
$exists = Storage::disk('sftp')->url('users/default.png');
Steps To Reproduce
Steps to reproduce the behavior:

add to config "filesystems"
'sftp' => [
'driver' => 'sftp',
'host' => '<IP_ADDRESS>', // my sftp serverip
'username' => 'username',
'password' => 'password',
]
set in .env file FILESYSTEM_DRIVER=sftp
clear config cache
go to admin panel
get Exception

Screenshots

My question in laravel https://github.com/laravel/framework/issues/35159

Sadly I can only give you the same answer you recevied in Laravel/framework.
You need URLs to display images and other things you save in your storage and that driver does not support it.
Not a Voyager issue and nothing we can do our side.


Linear Conflict Violates Admissiblity

So heuristics violate admissibility if they are pessimistic. So say a puzzle requires 4 moves to get to the goal state but the heuristic says it requires 5.
Linear conflict applies when two tiles are positioned in their desired row or column but are reversed relative to their goal positions, meaning a given tile must move out of the row or column in order to let the other pass.
Say we are focusing on one row which has the configuration [ 3, 1, 2 ]
Let's assume [ 1, 2, 3 ] is the goal configuration.
The summed manhattan distance for the problem is: 4 (3 moves 2 times, 1 moves 1 time and 2 moves 1 time) The linear conflict for the row is: 4 ( 1 and 2 are both less than 3 so +2+2 )
Which results in an overall heuristic estimate of 8. [ 3, 1, 2 ] can be solved in 6 moves

You either use Manhattan distance or linear conflict as heuristic not the sum of both

Linear conflict is an extension to improve manhattan distance.
@Override
protected int calculate(State s) {

	int heuristic = super.calculate(s);

	heuristic += linearVerticalConflict(s);
	heuristic += linearHorizontalConflict(s);

	return heuristic;

}

your code follows this, it executes the manhattan distance of the state then adds the linearconflicts to it

Please take a look at the algorithm proposed here https://cse.sc.edu/~mgv/csce580sp15/gradPres/HanssonMayerYung1992.pdf
Linear conflict is more complex than just adding two each time

You either use Manhattan distance or linear conflict as heuristic not the sum of both

Your code seems to use the sum of both, which is fine if the linear conflict heuristic is correctly calculated. The article of Hansson et al. gives the following example: [5, 3, 4] (where goal is [3, 4, 5])

[...] the 5  tile is in conflict with the 3 and the 4. Clearly, either the 5  has to move out of the way (two  extra moves) and allow the others to pass to their goal positions, or the 3 and 4 have to  move and allow the 5  to pass (four extra moves).

In that case, the linear conflict heuristic should give 2 extra moves (the minimum of the 2 options). However, it looks like your code gives 4 for this particular case.


[bug] setIgnoreCursorEvents( ) not work

Describe the bug
I created a webview window with button click in main window, but can't do mouse click through the webview window with setIgnoreCursorEvents(true), even when the appwindow is also set.   I'm working on win10.
Reproduction
1, In main window, there is a button to open a webview window
2, set webviewwindow to ignore cursor event.
<template>

         <button @click="createChild"> Find Elements</button>

</template>

In page-a
<template>

       Hello, hello, hello, hello, hello
   </div
</template

Expected behavior
Is there workaround to click through the webviewwindow, and at the same time script in webview window can get position of mouse cursor ?
Full tauri info output
Can't click through the webview window

Stack trace
No response
Additional context
No response

please add the tauri info output


Question about data

I want to understand the data hosted in this repo.

Giessen_dataset folder has two files.

Is the cip_ctx_ctz_gen_pheno.csv file contain labels for resitance? 1=resistant and 0=susceptible?
Is the cip_ctx_ctz_gen_multi_data.csv file contain the transformed SNPs? A,C,G,T,N represented as 1,2,3,4,0?

Is there a way to reproduce the CGR representation? Or have I missed something?

Really appreciate your support on this.
Thanks
A

Could you also make a comment on INDELs, there is some processing in 01_SNPs_calling.sh but not sure from paper how they were handled.
Also how did you treat multi-allelic variants? I see you are using -m flag in bcftools.

我想了解此存储库中托管的数据。

Giessen_dataset文件夹有两个文件。

文件是否包含恢复标签？ 和？cip_ctx_ctz_gen_pheno.csv``1=resistant``0=susceptible
文件是否包含转换后的 SNP？ 表示为 ？cip_ctx_ctz_gen_multi_data.csv``A,C,G,T,N``1,2,3,4,0

有没有办法重现 CGR 表示？还是我错过了什么？

非常感谢您对此的支持。
谢谢 A
Hello, could you let me know if you've successfully replicated FCGR? If so, could you please guide me through it? Thank you very much.

我想了解此存储库中托管的数据。

Giessen_dataset文件夹有两个文件。

文件是否包含恢复标签？ 和？cip_ctx_ctz_gen_pheno.csv``1=resistant``0=susceptible
文件是否包含转换后的 SNP？ 表示为 ？cip_ctx_ctz_gen_multi_data.csv``A,C,G,T,N``1,2,3,4,0

有没有办法重现 CGR 表示？还是我错过了什么？

非常感谢您对此的支持。
谢谢 A

Hello, could you let me know if you've successfully replicated FCGR? If so, could you please guide me through it? Thank you very much.


Find out whether we can convert the 16 bit textures to 8 bit

This relates to the normals .exrs and mayyyybe the displacement map .pngs.
Convert them and then re-add them to Blender.

Related: https://github.com/bevyengine/bevy/issues/4532

Update: Photoshop can do this via Image -> Mode -> 8 Bits/Channel
Time to test whether this fixes the normals.

Update: normal maps work when using 32 bit instead of 16 bit precision!
Displacement maps should be able to be implemented via a vertex shader:  #171


fix(image-annotator-react): fix annootation selected style

:tada: This PR is included in version 1.3.0-alpha.4 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.3-alpha.4 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.20 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.16 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:


Playback doesn't work after update to Kodi 18.8

Playback doesn't work after system update including to Kodi 18.8.
Your Environment

Netflix add-on version: 1.6.1
Kodi: 18.8 (Build: 18.8.0)
Operating system version/name: Arch Linux
Device model:  Intel NUC

Used Operating system:

[ ] Android
[ ] iOS
[X] Linux
[ ] OSX
[ ] Raspberry-Pi
[ ] Windows

Describe the bug
Playback does not work anymore after system update including to Kodi 18.8(Build 18.8.0). Was working fine on Kodi 18.7.
020-08-17 09:45:49.922 T:140049880704768   ERROR: IAddonInstanceHandler::CreateInstance: inputstream.adaptive returned bad status "Permanent failure" during instance creation
2020-08-17 09:45:49.922 T:140049880704768   ERROR: CVideoPlayer::OpenInputStream - error opening [plugin://plugin.video.netflix/play/show/70283264/season/80066406/episode/80094486/?profile_guid=3BHDTBIKI5AOLCBYIA6TE7P3TM]
Expected behavior
Playback should start immediatly
Actual behavior
Nothing happens on selecting a movie/episode.  Error in the log
Steps to reproduce the behavior

Select any movie tv/show to play

Debug log
https://paste.kodi.tv/qesefuqohe.kodi

ERROR: IAddonInstanceHandler::CreateInstance: inputstream.adaptive returned bad status "Permanent failure" during instance creation
Your error comes from another component: inputstream.adaptive
not concern this add-on
this to me suggest two things:
that your device has badly updated Kodi components in Kodi upgrade
or you have tried rollback Kodi version or mixed versions which has broken the dependencies


python3Packages.google-cloud-texttospeech: 2.3.0 -> 2.4.0

Motivation for this change
Update to latest upstream release 2.4.0
Change log: https://github.com/googleapis/python-texttospeech/releases/tag/v2.4.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126000 at dee60871 run on x86_64-linux 1

1 package failed to build:

python39Packages.google-cloud-texttospeech

1 package built successfully:

python38Packages.google-cloud-texttospeech

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Superseded by #126015


PapiComponentError: Not supported by component for custom function

Hi! Cool package!
I wrote a custom function and was trying to estimate the number of flops during execution
from pypapi import papi_high
from pypapi import events as papi_events

papi_high.start_counters([papi_events.PAPI_FP_OPS])
foo
x1 = papi_high.stop_counters()
print(x1)

However, i encountered the following error:
Traceback (most recent call last):
  File "/mnt/c/Users/Pavan/Projects/PBM_Schemes/Python/2D/Case1/time.py", line 18, in <module>
    papi_high.start_counters([papi_events.PAPI_FP_OPS,])
  File "/home/pavan/miniconda3/envs/pyclaw/lib/python3.10/site-packages/pypapi/exceptions.py", line 170, in papi_error_wrapper
    raise object_()
pypapi.exceptions.PapiComponentError: Not supported by component. (PAPI_ECMP, PAPI_ESBSTR)

Would appreciate any help here! Thanks!

Hello,
You error comes from PAPI itself not from PyPAPI (this project is only a Python binding for the PAPI library). You may get some help from PAPI developers: https://icl.utk.edu/papi/custom/index.html?lid=50&slid=67
:)


Play / Pause Methods do not work

I've tried play and pause methods in my projects and it was not working... I thought I did something wrong, but in examples the car example is also not responding to any click events... Would be nice to have a fix for it :3
https://vue3-lottie.vercel.app/examples.html#play-on-hover

For your case would you mind sharing an example?
The reason the docs one doesn't work is a quirk of vitepress. Since I load the element after hydration it can sometimes bug out. If you look at the bottom of the page you should see all the elements.

Hi @schmeiger
There was indeed a bug introduced by a recent PR that only affected the pauseAnimation prop. It has been fixed in v2.2.3. Please give that a try :)

Oh that was fast :)
I will give it a go! And will report ;)

ok... I've updated to "vue3-lottie": "^2.2.3" ...  but sadly it didn't fix it... The strange thing is that autoplay: false as prop is also ignored...

I will take a second look at it tonight. Its 4am currently lol

@schmeiger I pushed a fix for the autoPlay prop. That should work as intended now. However, I think you might need to use a different method for the animation for your use case.
In this instance you should provide a ref to your lottie and run the methods manually. You can use v-show to hide the lottie above your heart button.
When the button is clicked you can show the element to reveal the animation. At the same time you can call the stop and then the play method. This should reset to the first frame and then play from there. To hide the animation after it is finished playing you can use the onLoopComplete event to hide the animation again.
Another alternative to the methods is to use the pauseAnimation prop to pause the animation onLoopComplete but you would have to time these correctly.
A third alternative is to use the goToAndPlay method and then hide the animation onLoopComplete.
Please let me know if this makes sense and if you need any more help. Thank you for using this library. Good luck :)

Cooooool! Autoplay did fix my
this.$refs.heartsLottie.play();
I guess, I was confused that, when it was on autoplay and the animation ran to the end, it doesn't replay automatically :)
Now I know, that I just have to reset the timeline! :)
Thank you so much! :)
And thank you for your work in general, I was after a proper Lottie player in Vue 3 for a long time... now I found it! 🥰👏

@schmeiger Not sure if this was the case in your instance but you have loop set to 1 in your example. That would be most likely the reason why the animation ends even with autoPlay enabled.

@schmeiger The loop prop if provided a number might not be working as you expected. I think for your use case you could try listening to onComplete instead? The lottie-web library I use internally might not be emitting the events for the first loop complete.
As for the loop prop itself, you can think of it as the number of repetitions instead:

true is to loop forever.
false is to not loop. (one plays once)
0 is to loop forever
1 is to loop once (this might not emit the onLoopComplete event)
x where x > 1 is the number of times the animation should play from the loading time.

Oh, cool! :) Now I got, why my :loop="0" was looping forever, I thought, something was broken... :)
That was basically my expectation -> if I set to autoPlay="true" and loop="0", the expected result -> it will play once and that's it, basically same as :loop=false :)
I think the info, that :loop=0 == loop forever, would be really useful in Docs :)
Thank you so much for your time! 🥰 My Fav/Hearts Button is very buuuuuuutiful now!!! :D


Error when using dispatchCloseEvent on component

When using livewire v3, if dispatchCloseEvent is true in the component, the following error occurs:
Only arrays and Traversables can be unpacked
This is because in modal.js, we have the following:
            if (this.getActiveComponentModalAttribute('dispatchCloseEvent') === true) {
                const componentName = this.$wire.get('components')[this.activeComponent].name;
                Livewire.dispatch('modalClosed', componentName);
            }

Note the old syntax of Livewire.dispatch.  It should, ideally be refactored to:
            if (this.getActiveComponentModalAttribute('dispatchCloseEvent') === true) {
                const componentName = this.$wire.get('components')[this.activeComponent].name;
                Livewire.dispatch('modalClosed', {component: componentName});
            }

Fixed in latest release


Paper Elements can't be natively imported

Hello! It's great to see that Polymer 3 with modules has been released! However, it looks like the migrated Polymer NPM elements (like paper-button) rely on "bare" module dependencies, which results in the following error when importing into the browser:
Failed to resolve module specifier<EMAIL_ADDRESS>Relative references must start with either "/", "./", or "../".
I understand the issues associated with relative path imports and that we can use "Rollup" or "Webpack" to build a project, but one thing I've always appreciated about Polymer is that you don't need a build process and, in my opinion, this requirement is a pretty big step back and makes migration for existing projects pretty difficult.
Is there any plan to allow these Polymer elements to work without a build process? I've seen the package name map proposal, but that seems like it will be a long way out and isn't even poly-fillable.
Would the Polymer team consider providing two versions of the migrated elements? paper-button.js and paper-button.relative.js, for example -- one with relative paths and one with bare modules? That way existing projects can choose to import the relative package modules for an easy upgrade.
Thanks!
Garrett

You may already be aware, but the Polymer CLI's built-in serve and build commands can perform only that transform (module specifiers to URL paths) on the fly, leaving everything else uncompiled native ES modules.
If you'd like to go one step further and not perform this transform on dependencies during dev time at all, we have an experimental script you can add as an npm postinstall step on your application which will do a one-time transform of module specifiers to paths in your npm dependencies.  This is experimental and we don't have any SLA around support, but feel free to try and see if it helps your workflow: https://github.com/PolymerLabs/empathy/tree/initial-implementation.
There has been discussion in the past with npm on whether an option to do this for front-end dependencies could be folded into a first-class feature of npm itself.  So depending on developer feedback and demand, and progress on package name maps and npm changes, that project could get more or less attention or go away altogether.
All that said, we don't have any plans to publish two entry points for components, so I'm going to go ahead and close this issue.

Hey @kevinpschaaf, thanks for the response! Empathy looks closer to what we're looking for, though it's a little heavy handed. I'll definitely look into it a bit more and give some feedback!

All that said, we don't have any plans to publish two entry points for components, so I'm going to go ahead and close this issue.

Can I ask what the expected path forward is for existing projects (or even new ones) looking to migrate to Polymer 3.0 and the new paper elements? In the prior versions it's been possible to just statically serve the files for development -- the upgrade guide doesn't cover this case.

the Polymer CLI's built-in serve and build commands can perform only that transform (module specifiers to URL paths) on the fly

I did see that, but is it expected that a project suddenly have to use this if they even import just one paper element? Or if the project already has a static-file serving solution?
I understand that the new import spec has left the js package world in a bit of a awkward spot. I'm sure there will be some kind of solution in the coming years to address this issue (either through tooling or new spec), but it would be nice to have some simple migration path forward in the interim.
I do feel obligated say that I really appreciate the work put into version 3 and the upgrade documentation. Aside from this hiccup, the upgrade and everything else has been really clean.
Thanks again for responding, I appreciate your time!

Yes, this was a very, very hard call for us to make, as we're as big of proponents of tool-free edit/refresh developing as they come.  We agonized over this decision in more meetings than I can count, frankly.
But on the whole, the barrier to entry of requiring flat installation of all dependencies required to use path-based module specifiers (when a large percentage of the OSS JS world does not currently and likely will never agree to that limitation) means a lot of developers were sidelined from stepping into the web components ecosystem altogether, and that just didn't feel like a tenable spot to continue to stay in.

Can I ask what the expected path forward is for existing projects (or even new ones) looking to migrate to Polymer 3.0 and the new paper elements? In the prior versions it's been possible to just statically serve the files for development -- the upgrade guide doesn't cover this case.

It's fair that the upgrade paths we mostly focused on were either a.) someone using the Polymer CLI for the dev/build workflow (which should hopefully be a seamless transition), or b.) someone happily using basically any other toolchain that can ingest code from npm (meaning they can already deal with module resolution), but not this third case which is "was using neither the Polymer tools nor need to work with other npm packages, and thus was happy with a purely static server."
So at least for the time being, I think the answer to your question is one of  1.) Polymer CLI, 2.) WebPack, Rollup, and friends, or 3.) empathy -- with a hopeful future of Package Name Maps, npm asset support, or both.

I understand -- it doesn't sound like it was an easy decision or an easy problem to solve. We'll probably look into empathy for the time being.
Thank you!

@kevinpschaaf

Yes, this was a very, very hard call for us to make, as we're as big of proponents of tool-free edit/refresh developing as they come. We agonized over this decision in more meetings than I can count, frankly.

That is really the best experiences indeed.

[...] but not this third case which is "was using neither the Polymer tools nor need to work with other npm packages, and thus was happy with a purely static server."

This case covers basically everyone using Firebase hosting a little heavily (to host a real world app with some functionalities).
That said, using empathy to sort of statically one time rewrite the imports seems like a viable options, if it works and is not something that will disappear.

@kevinpschaaf Is there a reason why there is no release of empathy till now? Are there any actual statements about "tool-less" development?

maybe also @TimvdLippe you can give an actual statement here. Or maybe someone can add a little bit of a description about only changeing "import paths" on polymer or lit-ement page?

I don't have any more information on empathy, sorry. You might be interested in this project: https://github.com/pikapkg/web


Bump deps, remove PR apks and fix wearos track

Background
Right now we can't upload wearos release to separate track
Changes

Use separate track for wearos
Remove pr apks workflow
Bump some deps

Test plan
CI passed

Lets try


Better error if publishing with a bid higher than balance

Right now it just says "content cannot be published at this time"

Took a look at this.
respective file is https://github.com/lbryio/lbry-react-native/blob/master/src/page/publish/view.js#L470 and it's a simple edit.
but for a more detailed response, respective file would be in  https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/publish/PublishFormFragment.java with a showError(getString(R.string.deposit_more_than_balance)); but requires more knowledge of code to go along with it of which I do not have.


Anaconda image has incompatible cryptography and openssl modules, breaking conda package manager

Hi,
Currently conda is broken in the latest image available (mcr.microsoft.com/devcontainers/anaconda:0-3).  This issue has been going on for a couple of months, but reporting it now that it's blocking installing new dependencies for a project.
If after creating a fresh container one attempts to install anything with conda, including just updating conda with 'conda update conda', the following error occurs: "AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'"
There is discussion of the issue here: https://github.com/pyca/cryptography/issues/7959  The root cause is due to incompatible versions of cryptography and openssl via pyopenssl coexisting at once in the same environment.
While one can work around the issue by upgrading pyopenssl using pip, this breaks the conda package manager's ability to successfully complete transactions going forward to upgrade or install new packages, transactions either taking very, very long to complete or failing to verify and ending without executing.
Would you please fix this incompatibility in the latest image and going forward so we can use conda to install packages?
A potential solution would be reving the version of anaconda being installed on the source image to one where this incompatibility isn't present from inception.  Thanks!

Also, I just tried creating a container using the dev image (mcr.microsoft.com/vscode/devcontainers/anaconda:dev-3) and the same issue outlined above is present.

I tried out the miniconda image this morning (mcr.microsoft.com/devcontainers/miniconda:0-3), and it does not have the same issue, and one is able to install new packages using conda.  However, you might find it interesting that if you try 'conda update conda' with the miniconda package, it does raise an error related to the cryptography package, although a different one than the Anaconda image:

@samruddhikhandale Thanks for taking a look at this.  I see you're working through developing your pull request, appreciate it.  I tried your latest solution for the Anaconda image, which is having pip install pyOpenssl.  That does indeed allow 'conda update conda' to succeed.  However, you should add another test to install a package after that, for example 'conda install -c conda-forge pylint'.  That is failing; I also tested with several other common packages on conda-forge.
I also tried your miniconda solution, also fails when you try the same conda-forge command mentioned above and several other common packages as well.

Hi, more info--I was able to get the miniconda image to a working state, built on top of your current fix in the pull request for that image, by resolving a permissions error I would get when installing or updating certain packages with conda by updating permissions for the python folders in /opt/conda with the following command: 'sudo chown -R vscode /opt/conda/lib/python3.10/site-packages/*'.  So potentially the Docker image build isn't getting everything sorted with permissions for the vscode user to operate on those directories?  Maybe some files created by 'RUN conda update -y cryptography' in the Dockerfile aren't getting the right permissions assigned?
I checked the smoke test logs, and they're the same error I was getting which was fixed by the above solution:'[Errno 13] Permission denied: '/opt/conda/lib/python3.10/site-packages/conda-23.1.0-py3.10.egg-info/PKG-INFO' -> '/opt/conda/lib/python3.10/site-packages/conda-23.1.0-py3.10.egg-info/PKG-INFO.c~''

Thanks for all the help, I appreciate that! my latest commit should fix the error for miniconda, (local tests passed 🎉 ). Let me know what you think.
https://github.com/devcontainers/images/pull/489

Just checked out the latest change--agree that makes sense.  I tried it out, it works.  If anyone wants to run any optional stuff after that command per the comments in the source code they'll need to switch the USER back to root so maybe noting something like that.  And this solution is quite hacky because if someone using this image downstream defines a different default username than vscode in their devcontainer.json, it'll almost surely be broken because they won't have permission to act on anything owned by vscode.  But hopefully this is all temporary and the upstream gets fixed so we don't have to patch it like this, I'm not sure what we do otherwise in the meantime.
Also, would be good to add another test for the Anaconda image, it's passing currently but I think it will fail (based on testing I did last night) if you add 'conda install -c conda-forge --yes tensorflow' as another test for that image.


Generator analog of pmrna

...to select the primary mRNA from a gene. Needs to consume and yield all entry types.

Implemented in feature/mrna branch. Still needed:

[ ] CLI
[ ] more concise imports (after refactor/import branch is merged)


NPM/Yarn examples: Use lock file usually

Why:

Highlighting to use package-lock.json / yarn.lock for installing usually
Replacing --frozen-lockfile with its successor

What's being changed:

Example using npm
Example using Yarn

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@SchulteMarkus Thanks so much for submitting a PR! I'll get this triaged for review :zap:

One of the Actions developers has taken a look at this and has approved the first part of the changes but said of the changes in the "Example using Yarn" section that the changes use Yarn 2 commands whereas, out of the box, GitHub hosted runners ships with Yarn 1.22.19 (https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md).
To avoid problems if people haven't modified this to upgrade the Yarn version on a runner, we need to be sure that the changes you are proposing will work using Yarn 1.22.19.
Could you check this and confirm here?

Ui, good that you asked!
I have added one more commit, so that the Yarn command is again Yarn 1.x compatible. I have updated the PR itself, too.
This PR changed a bit from it's indentation (not using yarn --frozen-lockfile any more) to now (using lock files as first examples). In my opinion, it's still an improvement.

Failure https://github.com/github/docs/actions/runs/5621341748/job/15231953003?pr=26699 seems to be GitHub infrastructure related. @hubwriter , can you execute the build again?


How to set Chunk Size default value in cmd ?

I am a rclone v1.35 new user with win7 64bit
I used rclone to upload to google drive with 1gbp but seems to fluctuate between 700KBPS - 2MBPS
So I try to change set  ''drive-chunk-size'' to 128M
And I used  CMD type  '' rclone --drive-chunk-size=131072k
but system show the maseage of
''Use ''rclone [command] --help'' for more information about a command
Command not found''
please teach me the correct way to set drive-chunk-size
or have anyway can change drive-chunk-size default value?
many thanks!!
![_2017_02_24_16_10_47_704](https://cloud.githubusercontent.com/assets/26002654/23300997/0c2707f6-fac3-11e6-80a5-e894923515f2.p

ng)

This is fine, but you need to pass it every time you use it.  rclone is complaining that you didn't give it a command.
So
rclone --drive-chunk-size=131072k copy xzy remote:subdir

will work
rclone --drive-chunk-size=128M copy xzy remote:subdir

will also work

thanks reply!!!
but I type ''rclone --drive-chunk-size=131072k copy xzy remote:subdir''
is show the maseage of
''Failed to create file system for "remote:subdir": didn't find section in config file''
is mean not work?

You need to create the remote first with rclone config

This was answered. Closing out.