Configuring issues with tag 2.1.0

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian 9
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no
TensorFlow installed from (source or binary): source
TensorFlow version: 2.1.0rc1 (and rc0)
Python version: 3.6.8
Installed using virtualenv? pip? conda?: virtualenv
Bazel version (if compiling from source): bazelisk
GCC/Compiler version (if compiling from source): 6.3.0
CUDA/cuDNN version: 10.1 and 7.6.5
GPU model and memory: 2x NVidia Titan XP 11GB

Configuring from both tags (rc0 and rc1) picks the wrong bazel (0.26 instead of 1.1.0) due to misconfigured .bazelversion, which should be cherry-picked from a later commit to make it work. I don't see the reason for this to be necessary and not having a buildable tag. The commit a5f9bcd64453ff3d1f64cb4da4786db3d2da7f82 should be the one but, while I understand this making rc0 not work, I don't understand rc1 also not working since it's a later tag.

Configuring out of source, i.e. with a tree made to be able to call ../configure (hybrid out-of-source) or ../tensorflow/configure (full out-of-source) results in /usr/local/bin/python3.6: can't open file 'third_party/gpus/find_cuda_config.py': [Errno 2] No such file or directory, likely due to 'third_party/gpus/find_cuda_config.py' being an absoulte path instead of a relative one.

Ok
On Wed, Dec 18, 2019, 08:24 aPonza<EMAIL_ADDRESS>wrote:

Please make sure that this is a build/installation issue. As per our
GitHub Policy
https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md, we only
address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian 9
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on mobile device: no
TensorFlow installed from (source or binary): source
TensorFlow version: 2.1.0rc1 (and rc0)
Python version: 3.6.8
Installed using virtualenv? pip? conda?: virtualenv
Bazel version (if compiling from source): bazelisk
GCC/Compiler version (if compiling from source): 6.3.0
CUDA/cuDNN version: 10.1 and 7.6.5
GPU model and memory: 2x NVidia Titan XP 11GB

Configuring from both tags (rc0 and rc1) picks the wrong bazel (0.26
instead of 1.1.0) due to misconfigured .bazelversion, which should be
cherry-picked from a later commit to make it work. I don't see the reason
for this to be necessary and not having a buildable tag. The commit is
a5f9bcd
https://github.com/tensorflow/tensorflow/commit/a5f9bcd64453ff3d1f64cb4da4786db3d2da7f82
should be the one but, while I understand this making rc0 not work, I don't
understand rc1 also not working since it's a later tag.
2.
Configuring out of source, i.e. with a tree made to be able to call
../configure (hybrid out-of-source) or ../tensorflow/configure (full
out-of-source) results in /usr/local/bin/python3.6: can't open file
'third_party/gpus/find_cuda_config.py': [Errno 2] No such file or directory,
likely due to 'third_party/gpus/find_cuda_config.py' being an absoulte path
instead of a relative one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/35228?email_source=notifications&email_token=AOBPXOQMRDENFD6MAQMTG4TQZIXA3A5CNFSM4J4LV4UKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBLJPYA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOBPXOVOMPLOQEUSNC7LRXLQZIXA3ANCNFSM4J4LV4UA
.

@mihaimaruseac: the .bazelversion in the r2.1 branch does not match the allowed range in configure.py (range is 0.27-0.29, `.bazelversion is 0.26)

I'll make a cherry-pick

Actually, there is #35470 already for this.

I still don't see the reason to not have a buildable tag. Regardless, that would fix point 1. What about the second? Could that be a valid way to fix the issue or am I the only one having it?

r2.1 branch was cut before changes were made to support bazel 1.1.0. Thus, tags on this branch should be buildable with Bazel from 0.27 to 0.29. It is lucky if it also builds with 1.1.0.
Regarding second point, I don't think you're supposed to run configure out of tree. I don't know of any other open source project which allows you to ${path_to}/configure from outside the tree

tags on this branch should be buildable with Bazel from 0.27 to 0.29 isn't true though, due to said bazelversion being incorrectly set to 0.26. The point of my last comment was to point out my desire to have r2.1 build out of the box after dependencies are satisfied (i.e. include the commit from 5 days ago which you linked in the final r2.1 tag), I suppose that's the reason it's still a release candidate.
Now that you say it, I can only think of CMake Open Source projects which allow it, but it is a "best practice" so to speak, as far as I know. Many projects not only allow it but enforce it as well (e.g. OpenCV, ROS, ...), but still mostly CMake ones. Actually google tells me Qt allows it, but I see your point, and that is a very old link.

#35470 has been merged


Update RemoteConfig workflow.

RemoteConfig quickstart is updated and objc quickstart is removed.

quickstart framework/quickstart tests are done in 6c14b01.


fixes for pinned ceres formula

What changed

class name has to reference pinned version
unreference bottles (they 404)
CXSparse (see below)
remove a temporary patch that now fails

CXSparse

the cxsparse library causes a cmake error in this build
I removed it with -DCXSPARSE=OFF in the cmake invocation
ceres supports multiple sparse solvers and it seems like suite-sparse is the most powerful. per this line, I'm guessing they're interchangeable, but not totally sure
if our downstream dependencies fail with messages related to CXSparse, this is the reason

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.m1loaner seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Chainlink OCR aggregators as reporters 🚀

since this is going live in a few hours, time to merge the PR?


Fix extra nesting level

Fixes https://github.com/zalando/api-first-hand/issues/79

@slavaschmidt, could you please tag/release it? Is it a long procedure?

will release 0.2.2. tomorrow, ok?

@slavaschmidt, sure, thanks!


Configure cuebot logs to write WARN and ERROR messages to stdout

This change allows for the cuebot logs to be visible from docker logs, full logs are still written to logs/spcue.log.

Oh also - you'll probably want to update https://github.com/imageworks/OpenCue/wiki/Deploying-Cuebot with any new expected log output.

Good call. I'll also update the troubleshooting doc to mention that errors are visible in the docker logs but also explain that the full logs are available by looking at the logs/spcue.log file.


👷 Divide Dart packages tests by platforms

Helps to determine exceptions occurrences during Dart tests.
New Pull Request Checklist

[x] I have read the Documentation
[x] I have searched for a similar pull request in the project and found none
[x] I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
[ ] I have added the required tests to prove the fix/feature I'm adding
[ ] I have updated the documentation (if necessary)
[x] I have run the tests without failures
[ ] I have updated the CHANGELOG.md in the corresponding package

When separating scripts into a standalone script file, I have no idea why tests will fail. https://github.com/cfug/dio/commit/808ea913d9789fa425caadab6eee837a623ff857


riak_kv_pipe_get's failover has trouble with fast-input+slow-output rates

A problem was uncovered with riak_kv_pipe_get's failover strategy.
Description
When the KV vnode that the pipe worker talks to returns an error, "not
found" for example, the worker attempts to have another worker for
this fitting try on a different vnode by returning the
forward_preflist result.  The last worker in the fallback list is
then supposed to forward the error to the next phase if it also fails.
This strategy does not work when the kvget workers are unable to keep
up with the rate of incoming inputs.  The forward_preflist strategy
has to use a non-blocking enqueue to prevent workers in a fitting from
mutually blocking on one another.  If the workers' queues are already
full of other inputs, forwarding retry inputs to them will never
succeed.  When forwarding retry inputs fails, the worker does not get
a chance to send the error to the next phase; Pipe's internal code
sends an error trace message and drops the input instead.
This bug manifests itself as MapReduce queries failing with a
timeout-like error before their configured timeout, since both the
HTTP and PB mapreduce endpoints treat error trace messages as reasons
to terminate the query.  The issue was raised on the mailing list:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2012-February/007590.html
Possible fixes
One quick and incomplete fix may be to simply set the q_limit much
higher on the riak_kv_pipe_get fittings in the riak_kv_mrc_pipe
module.  This would raise the level/rate of inputs necessary to
trigger the bug.  Raising the following riak_kv_mrc_map fitting's
q_limit may help as well.
One long-term fix is likely to change riak_kv_pipe_get such that it
does not use the forward_preflist return value.  Either it will need
to talk directly to the fallback KV vnodes without forwarding the
input, or it will need to be able to call
riak_pipe_vnode_worker:recurse_input/5 directly (which will also
require passing the used-preflist to the worker) to be able to handle
with full-queue errors.
Another long-term fix might be to alter the behavior of
forward_preflist such that instead of producing a trace error, it
forwards some standard message to the downstream fitting.
Reproduction
Below is a basic method for reproducing the problem.  The method is to
follow a riak_kv_pipe_get fitting with a fitting that takes forever
to process its first input.  This in turn causes the
riak_kv_pipe_get fitting's queues to back up.  The nval, q_limit
and chashfun parameters have been tuned to provide a minimal case.
The sleeps are not needed, but they make the trace easier to read.
Each call to riak_pipe:queue_work/3 is preceeded by a description of
how the worker (W), input queue (Q), and blocking queue (B) look
after each input settles in its final position.
KVGet = #fitting_spec{name = kvget,
                      module = riak_kv_pipe_get,
                      chashfun = chash:key_of(now()),
                      nval = 2,
                      q_limit = 1},
SlowMap = #fitting_spec{name = slowmap,
                        module = riak_pipe_w_xform,
                        chashfun = chash:key_of(now()),
                        arg = fun(I,P,F) ->
                                 receive never -> ok end
                              end,
                        q_limit = 1},
{ok, Pipe} = riak_pipe:exec([KVGet, SlowMap],
                            [{log, sink}, {trace, all}]),

%% 1: makes it all the way to the slowmap worker
%% K1: W=idle, Q=[], B=[]
%% K2: W=idle, Q=[], B=[]
%% M1: W={notfound,1}, Q=[], B=[]
riak_pipe:queue_work(Pipe, {<<"notthere">>, <<"1">>}, noblock),
timer:sleep(1000),

%% 2: makes it into the slowmap worker's queue
%% K1: W=idle, Q=[], B=[]
%% K2: W=idle, Q=[], B=[]
%% M1: W={notfound,1}, Q=[{notfound,2}], B=[]
riak_pipe:queue_work(Pipe, {<<"notthere">>, <<"2">>}, noblock),
timer:sleep(1000),

%% 3: makes it to the fallback kvget worker,
%%    blocking that worker on the slowmap worker's queue
%% K1: W=idle, Q=[], B=[]
%% K2: W={notthere 3}, Q=[], B=[]
%% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notthere 3}]
riak_pipe:queue_work(Pipe, {<<"notthere">>, <<"3">>}, noblock),
timer:sleep(1000),

%% 4: makes it to the fallback worker's queue
%% K1: W=idle, Q=[], B=[]
%% K2: W={notthere 3}, Q=[{notthere, 4}], B=[]
%% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
riak_pipe:queue_work(Pipe, {<<"notthere">>, <<"4">>}, noblock),
timer:sleep(1000),

%% 5: fails because preflist forwarding would block on the
%%    fallback worker's queue
%% K1: W={notthere 5}, Q=[], B=[]
%% K2: W={notthere 3}, Q=[{notthere, 4}], B=[]
%% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
riak_pipe:queue_work(Pipe, {<<"notthere">>, <<"5">>}, noblock),
timer:sleep(1000),

{timeout, [], Trace} = riak_pipe:collect_results(Pipe),
rp(Trace).

Below is the value captured in the Trace variable, with additional
comments about what is happening at each step.
%% K1: W=idle, Q=[], B=[]
%% K2: W=idle, Q=[], B=[]
%% M1: W=idle, Q=[], B=[]

[{slowmap,{trace,all,{fitting,init_started}}},
 {slowmap,{trace,all,{fitting,init_finished}}},
 {kvget,{trace,all,{fitting,init_started}}},
 {kvget,{trace,all,{fitting,init_finished}}},

 %% 1: send first input to primary kvget vnode
 %% K1: W=idle, Q=[{notthere,1}], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W=idle, Q=[], B=[]
 {kvget,
     {trace,all,
         {fitting,
             {get_details,#Ref<<IP_ADDRESS>313>,
<PHONE_NUMBER>247607560106752257205091097473808596992,
                 <11776.302.0>}}}},
 {kvget,
     {trace,all,
         {vnode,
             {start,1438665674247607560106752257205091097473808596992}}}},
 {kvget,
     {trace,all,
         {vnode,
             {queued,1438665674247607560106752257205091097473808596992,
                 {<<"notthere">>,<<"1">>}}}}},
 %% 1: primary kvget worker processes first input
 %% K1: W={notthere,1}, Q=[], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W=idle, Q=[], B=[]
 {kvget,
     {trace,all,
         {vnode,
             {dequeue,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}},
 %% 1: primary kvget worker forwards first input to fallback vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[{notthere,1}], B=[]
 %% M1: W=idle, Q=[], B=[]
 {kvget,
     {trace,all,
         {fitting,{get_details,#Ref<<IP_ADDRESS>313>,0,<0.282.0>}}}},
 {kvget,{trace,all,{vnode,{start,0}}}},
 {kvget,
     {trace,all,{vnode,{queued,0,{<<"notthere">>,<<"1">>}}}}},
 %% 1: fallback kvget vnode processes first input
 %% K1: W=idle, Q=[], B=[]
 %% K2: W={notthere,1}, Q=[], B=[]
 %% M1: W=idle, Q=[], B=[]
 {kvget,{trace,all,{vnode,{dequeue,0}}}},
 {kvget,
     {trace,all,
         {vnode,
             {waiting,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}},
 %% 1: fallback kvget worker sends notfound output to slowmap vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W=idle, Q=[{notfound,1}], B=[]
 {slowmap,
     {trace,all,
         {fitting,
             {get_details,#Ref<<IP_ADDRESS>313>,
<PHONE_NUMBER>65679310520246963290989976735222595584,
                 <11775.290.0>}}}},
 {slowmap,
     {trace,all,
         {vnode,
             {start,593735040165679310520246963290989976735222595584}}}},
 {slowmap,
     {trace,all,
         {vnode,
             {queued,593735040165679310520246963290989976735222595584,
                 {{error,notfound},{<<"notthere">>,<<"1">>},undefined}}}}},
 {kvget,{trace,all,{vnode,{waiting,0}}}},
 %% 1: slowmap vnode picks up first input
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[], B=[]
 {slowmap,
     {trace,all,
         {vnode,
             {dequeue,
<PHONE_NUMBER>65679310520246963290989976735222595584}}}},
 %% 2: send second input to primary kvget vnode
 %% K1: W=idle, Q=[{notthere,2}], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[], B=[]
 {kvget,
     {trace,all,
         {vnode,
             {queued,1438665674247607560106752257205091097473808596992,
                 {<<"notthere">>,<<"2">>}}}}},
 %% 2: primary kvget worker forwards second input to fallback vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[{notthere,2}], B=[]
 %% M1: W={notfound,1}, Q=[], B=[]
 {kvget,
     {trace,all,{vnode,{queued,0,{<<"notthere">>,<<"2">>}}}}},
 {kvget,
     {trace,all,
         {vnode,
             {waiting,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}},
 %% 2: fallback worker sends notfound output to slowmap vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[]
 {slowmap,
     {trace,all,
         {vnode,
             {queued,593735040165679310520246963290989976735222595584,
                 {{error,notfound},{<<"notthere">>,<<"2">>},undefined}}}}},
 {kvget,{trace,all,{vnode,{waiting,0}}}},
 %% 3: send third input to primary kvget vnode
 %% K1: W=idle, Q=[{notthere 3}], B=[]
 %% K2: W=idle, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[]
 {kvget,
     {trace,all,
         {vnode,
             {queued,1438665674247607560106752257205091097473808596992,
                 {<<"notthere">>,<<"3">>}}}}},
 %% 3: primary kvget worker forwards third input to fallback vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W=idle, Q=[{notthere 3}], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[]
 {kvget,
     {trace,all,{vnode,{queued,0,{<<"notthere">>,<<"3">>}}}}},
 {kvget,
     {trace,all,
         {vnode,
             {waiting,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}},
 %% 3: falback worker blocks on sending third notfound to slowmap vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W={notthere 3}, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notthere 3}]
 {slowmap,
     {trace,all,
         {vnode,
             {queue_full,
<PHONE_NUMBER>65679310520246963290989976735222595584,
                 {{error,notfound},{<<"notthere">>,<<"3">>},undefined}}}}},
 %% 4: send fourth input to primary kvget vnode
 %% K1: W=idle, Q=[{notthere, 4}], B=[]
 %% K2: W={notthere 3}, Q=[], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
 {kvget,
     {trace,all,
         {vnode,
             {queued,1438665674247607560106752257205091097473808596992,
                 {<<"notthere">>,<<"4">>}}}}},
 %% 4: primary kvget worker forwards forth input to fallback vnode
 %% K1: W=idle, Q=[], B=[]
 %% K2: W={notthere 3}, Q=[{notthere, 4}], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
 {kvget,
     {trace,all,{vnode,{queued,0,{<<"notthere">>,<<"4">>}}}}},
 {kvget,
     {trace,all,
         {vnode,
             {waiting,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}},
 %% 5: send fifth input to primary kvget vnode
 %% K1: W=idle, Q=[{notthere 5}], B=[]
 %% K2: W={notthere 3}, Q=[{notthere, 4}], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
 {kvget,
     {trace,all,
         {vnode,
             {queued,1438665674247607560106752257205091097473808596992,
                 {<<"notthere">>,<<"5">>}}}}},
 %% 5: primary kvget worker fails to forward input to fallback
 %%    because fallback's queue is full
 %% K1: W={notthere 5}, Q=[], B=[]
 %% K2: W={notthere 3}, Q=[{notthere, 4}], B=[]
 %% M1: W={notfound,1}, Q=[{notfound,2}], B=[{notfound, 3}]
 {kvget,
     {trace,all,
         {error,
             [{module,riak_kv_pipe_get},
              {partition,
<PHONE_NUMBER>247607560106752257205091097473808596992},
              {details,
                  [{fitting,
                       #fitting{
                           pid = <0.1434.0>,ref = #Ref<<IP_ADDRESS>313>,
                           chashfun =
                               <<249,252,247,9,220,75,44,145,58,167,246,118,61,
                                 183,57,33,176,79,180,32>>,
                           nval = 2}},
                   {name,kvget},
                   {module,riak_kv_pipe_get},
                   {arg,undefined},
                   {output,
                       #fitting{
                           pid = <0.1433.0>,ref = #Ref<<IP_ADDRESS>313>,
                           chashfun =
                               <<102,4,176,137,137,246,153,214,136,172,94,97,
                                 152,118,215,52,233,8,52,4>>,
                           nval = 1}},
                   {options,
                       [{sink,
                            #fitting{
                                pid = <0.1223.0>,ref = #Ref<<IP_ADDRESS>313>,
                                chashfun = sink,nval = undefined}},
                        {log,sink},
                        {trace,all}]},
                   {q_limit,1}]},
              {type,forward_preflist},
              {error,[timeout]},
              {input,{<<"notthere">>,<<"5">>}},
              {modstate,
                  {state,1438665674247607560106752257205091097473808596992,
                      #fitting_details{
                          fitting =
                              #fitting{
                                  pid = <0.1434.0>,ref = #Ref<<IP_ADDRESS>313>,
                                  chashfun =
                                      <<249,252,247,9,220,75,44,145,58,167,246,
                                        118,61,183,57,33,176,79,180,32>>,
                                  nval = 2},
                          name = kvget,module = riak_kv_pipe_get,
                          arg = undefined,
                          output =
                              #fitting{
                                  pid = <0.1433.0>,ref = #Ref<<IP_ADDRESS>313>,
                                  chashfun =
                                      <<102,4,176,137,137,246,153,214,136,172,
                                        94,97,152,118,215,52,233,8,52,4>>,
                                  nval = 1},
                          options =
                              [{sink,
                                   #fitting{
                                       pid = <0.1223.0>,
                                       ref = #Ref<<IP_ADDRESS>313>,
                                       chashfun = sink,nval = undefined}},
                               {log,sink},
                               {trace,all}],
                          q_limit = 1}}},
              {stack,[]}]}}},
 {kvget,
     {trace,all,
         {vnode,
             {waiting,
<PHONE_NUMBER>247607560106752257205091097473808596992}}}}]

Thanks for looking into this!


Deluge

Hi there,
I as just wondering if we could add Deluge Support to this script?

Dupe of #58


Update PPP for Chung Loong

This is an ongoing PR. Hence, it is not advisable to merge for now.
Resolves #262

Codecov Report

Merging #263 (580057c) into master (3a566a5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #263   +/-   ##
=========================================
  Coverage     66.05%   66.05%
  Complexity      603      603
=========================================
  Files           101      101
  Lines          2083     2083
  Branches        239      239
=========================================
  Hits           1376     1376
  Misses          656      656
  Partials         51       51

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Channel Registration new password

Bot Info

App ID: 7307467b-55b4-4fec-bd3e-69f9e834dfc1
SDK Platform: .NET
SDK Version: <IP_ADDRESS>
Active Channels: none-webchat
Deployment Environment: ngrok, Azuree App Service

Issue Description
Cannot create new password here;
https://apps.dev.microsoft.com/?referrer=https%3A%2F%2Fportal.azure.com%2F#/application/7307467b-55b4-4fec-bd3e-69f9e834dfc1
Code Example
Reproduction Steps
goto;
https://apps.dev.microsoft.com/?referrer=https%3A%2F%2Fportal.azure.com%2F#/application/7307467b-55b4-4fec-bd3e-69f9e834dfc1
in application secrets -> create new password
Expected Behavior
new password to be created
Actual Results
GraphExcepion thrown

This is not a temporary problem, experiencing since two days.

I have same promble

This is a known problem. We are currently working on a fix. I will keep you updated here.
Regards,
Francisco

Thanks!

I have the same issue since yesterdar

I have the same issue since yesterday

When this gonna be fixed, several days with the same issue.

Somebody knows any time estimate when this will be solved? Thanks in advance

Closing the issue assuming it as resolved. Please reopen a new issue if it still persists.


Monitor panel glitch bug

Hi, I installed last version, and have glitch monitor bug.
I have 3 monitors and on one of them panel get glitching/ when im click on it, glitch happened on second monitor
how to fix that?
Im trying to explain it on video:
https://user-images.githubusercontent.com/103393069/208851099-49f92fef-ba31-4d8d-9c7f-2106044bc1c9.mp4
Latest version: [<IP_ADDRESS>]
Windows 10

I'm having same issue, whenever the taskbar update it flickers on all the monitors, sometimes when I'm gaming that flick lowers my fps


Fix a possible crash when importing an OGG file with zero-length packets

Fixes #87076.
Supersedes #87233.
A zero-length memcpy into a null pointer itself does not fail but apparently causes an optimizing gcc (production build) to generate incorrect code further down the line because it then assumes the pointer to be non-null and skips any conditionals referencing that pointer.
~Keeping this as a draft until someone with a gcc build pipeline can verify this fix.~
Edit: Might also fix #84712 since that's the file I used to track down the crash. Not sure about those non-monotonous timestamps reported by ffmpeg, but that file imports and plays fine for me in the Godot 4.3 dev 1 release build if I just skip processing the zero-length packet in the debugger.
Edit 2: Thank you @RichTeaMan for building this with gcc and verifying that it fixes the crash. As for the numerous errors and warnings, I've now changed the importer to completely strip zero-length packets and pages that contain no packets from the OggPacketSequence. This makes it conform better to the assumptions that AudioStreamPlaybackOggVorbis makes (such as "after I successfully move to the next packet, I have new data that I can decode"). With this change in place, I don't get any more warnings or errors when importing and playing the OST.ogg file from #84712.

Cherry-picked for 4.2.2.

Cherry-picked for 4.1.4.


BKSF-Mapper

Migrated from Enterprise Github.
Creator: @mrossinek

What is the expected behavior?
Implement and test the BravyiKitaevSuperFastMapper.
This issue breaks-out of #18 and can be used to assign and discuss BKSF-related topics.

[x] Implementation
[ ] Unittest
[ ] Documentation

I would like to point out the proposed re-design of the mappers in terms of "label-translators" as explained here: https://github.com/Qiskit/qiskit-nature/issues/18#issuecomment-773494151
I am not sure that it is worth opening another issue to propose a refactoring of the mappers but this will likely be the necessary implementation approach for the BKSF mapper. When this issue gets tackled we can potentially re-design the existing mappers accordingly.
The benefit of such an implementation would include:

a clearer and more maintainable implementation (i.e. no "odd" pauli_table object)
an implementation which is inspired closely by the actual mathematical definitions of the mappings
a more abstract implementation allowing greater flexibility for future development of other mappings

I favor retaining a class that stores the fermionic Hamiltonian as 2-d and 4-d arrays, as in aqua's FermionicOperator. And furthermore that this class be exposed in the API.

This is essentially how the operators are produced by the electronic-structure software. Going through a string representation, although it offers some advantages, is more complicated.
Because it's more complicated, it is susceptible to bugs and performance issues. For example, currently the performance of FermionicOp prohibits mapping Hamiltonians that can easily be done using the simpler format. This can be performance can be fixed. But, the representation of Fermionic operators has been in flux and may continue to change in the future.
The direct representation serves as a control for the correctness of the derived one. This is important because the software is still in a developmental/experimental stage.

Disadvantage

A FermionicOperator-like class, if exposed, increases the API and maintenance burden.

I do see where you're coming from with this. However, I also see some disadvantages with this approach.
For one, your suggestion inherently limits us to one- and two-body terms whereas the current implementation can easily be generalized to n-body terms (especially with #220 well underway). Although (right now) none of our classical drivers supports n-body terms, this should not be limitation which we restrict ourselves too.
If, however, BKSF by its nature does not support n-body terms anyways, then this is a different discussion all together. Previously,  a suggestion was brought up to provide to_matrix() conversion methods on the SecondQOps (#129). I am not sure what the status of that discussion is (@pbark @LaurinFischer @ikkoham), but would that resolve some of the issues you are facing? Or do you explicitly need to retain the information whether you were dealing with 1- or 2-body terms?
In terms of performance: I agree, that things are not ideal right now. And a more general framework is usually less performant than  a "restricted" one. But I also believe that we can still improve the performance significantly (see also #234).
And a final note on inter-operability: It may be true, that this is currently not straight forward, but I don't think it is impossible to do. And since this is not an essential part of the general workflow, this does not necessarily need to be the most performant code either. So a simple set of conversion methods should be sufficient.

I think I wasn't clear enough. I'm not proposing getting rid of the string-based representation in favor of the tensor-based. I was thinking of retaining both. And don't use the latter in cases where it doesn't apply, i.e. more than one- and two-body terms.

I have no doubt the performance can be improved. The point is that it had degraded and has to be fixed. And there will likely be further bugs or performance issues in the future. They can be fixed, too. Hopefully, they don't make it through to a release, but maybe they will.  The tensor-based representation is simpler and more widely understood.

I'm not 100% convinced that it should be retained, or in what way it should be retained. I'm mainly concerned about throwing away simple, working, relatively performant, structures and routines in favor of something that is more complicated and under development.

This is related to what John is saying about integrals as input for an operator. Some people have integrals from elsewhere and had been creating the FermionicOperator in the past and are now lost. They don't start from driver. I fielded another such question today. An operator such as John describes might be helpful for those that prefer to experiment more and are coming at the code from different angles. Of course another way, and its what I refer people too, would be to simply expose the integrals builder function that builds out the FermionicOp from one and two body ints.  While its there in the code it does not come out in the published API ref, not do we have it in any init file where we might want to expose it etc. I know this is not exactly related to BKSF but figured I'd mention since this alterate operator construction was being discussed here anyway - more though in view of BKSF of course.

I also thought of having something like the old FermionicOperator just as a way to organize and expose an API for building FermionicOp. I agree with @woodsp-ibm that this could be really useful.

With #220 merged, you can use the ElectronicEnergy to build an FermionicOp from integrals like so:
property = ElectronicEnergy(ElectronicBasis.MO, {
    1: OneBodyIntegrals(ElectronicBasis.MO, (qmol.mo_onee_ints, qmol.mo_onee_ints_b),
    2: TwoBodyIntegrals(ElectronicBasis.MO, (qmol.mo_eri_ints, qmol.mo_eri_ints_ba, qmol.mo_eri_ints_bb, None),
})

fermionic_op: List[FermionicOp] = property.second_q_ops()  # length == 1

The syntax may improve slightly during the work on #243 but the overall benefit of this approach is its generality because we are able to easily extend this approach to include n-body integrals in the future.

Closed by #232


Accessing SSL with REST Client

I am trying to test SSL REST webservices in our test env and getting. I did load keystroe .jks cert in REST Client. The same cert seems working fine in soapUI. Any help would be greatly appreciated.
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:533)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:401)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:178)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.wiztools.restclient.HTTPClientRequestExecuter.execute(HTTPClientRequestExecuter.java:387)
at org.wiztools.restclient.ui.RESTViewImpl$2.run(RESTViewImpl.java:322)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
at sun.security.validator.Validator.validate(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
... 18 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source)
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
at java.security.cert.CertPathBuilder.build(Unknown Source)
... 24 more

Same as #48 ... is it possible for you to verify the commit I had done for #48? I can rollout a build if someone confirms that it works as expected.

This should hopefully fix it.


form_upload.html  upload more file well Display is not normal

Display is not normal

This is  because of the declaration of inline style 'height'. Fix is on PR https://github.com/puikinsh/gentelella/pull/109

谢谢


Fix some overflows and windows warnings

When I looked at a few of the warnings that the MSVC compiler generates, I realized that many of them point to potential overflows with 64bit indices, so I will use this PR to collect fixes for these issues.

Yes, this needs a lot more work, I only picked a few low-hanging fruits


flutter_locker: generateDebugProto - Windows support not enabled

Hi,
Seems this library is not supported on Windows.
I continuosly see this error when trying to build my app on a windows machine.
Can someone please check.
Thanks
Manmeet Chadha
Logs.txt

I have the same problem

Sorry, we don't have much control of it, because issue comes from protobuf library that we use. Our goal now is to completely replace protobuf, but for that you'll have to wait (hopefully a week or two). I'll keep you updated.

Hi Josip... Just wanted to check if you had any update on the issue.

Hi Josip... any update on this issue?

@Shradha1824 we're testing the new version, so expect it during the next week.
If you want to try it before that you can do it with:
  flutter_locker:
    git:
      url: https://github.com/infinum/flutter-plugins-locker.git
      ref: 60e72b911f2b40bd081386965b8a7c5db203ef76

We have a breaking change: Every parameter in save and retrieve method is now named.
FlutterLocker.retrieve(RetrieveSecretRequest(
      key: 'key',
      androidPrompt: AndroidPrompt(
        title: 'title',
        cancelLabel: 'cancel',
        descriptionLabel: 'description',
      ),
      iOsPrompt: IOsPrompt(touchIdText: 'text),

Hey @ManmeetChadha9. We are now in final stages of testing the lib. Release will probably be early next week 🙂

Hey @lukaknezic , any luck with the release ?

@ManmeetChadha9 Just published new version with the fix: 2.1.0
It has braking change, because of pigeon all parameters in models are now named parameters instead of unnamed ones

@lukaknezic Looks like flutter_locker 2.1.0 requires Flutter 3. Maybe new version should've been 3.0.0?

@tudor07 Yeah you are right, will push a quickfix. For now you can use:
  flutter_locker:
    git:
      url: https://github.com/infinum/flutter-plugins-locker.git
      ref: b12db5d9d6ccc9d52c40d049fc76486a2b4c33f1

@tudor07 Quickfix is available: 2.1.0+1


Would it be possible to display pos_hint ?

Would it be possible to display the pos_hint?
For example, when you create a button and move it around on the screen/grid
Update the right-hand menu to output :
pos_hint: {"top": 0.8 + 0.12, "right":  1 }
I think this would make, this app next level useful.

Thanks for the input. You can now add a property like widget.pos or widget.pos_hint to the properties window just by adding it to the settings.json file. For instance to display the pos property of a widget add:
                {
                    "name": "pos",
                    "init": "TextInput()",
                    "save": false
                }

The save option has been added to allow a property to be displayed but not exported if set to false. Just have to make sure the settings.json has the correct syntax when modified.

Incredible! I think should be added by default to all widgets


ArgumentError when making reservation

Originally created by Tom Smyth at 2016-07-25 13:25, migrated from redmine-#4829

Status changed from New to Closed

By Tom Smyth at 2016-07-25 17:25


Mutually Exclusive wiki entry

Right now the Mutually Exclusive wiki page is blank.
This is what I propose as the first version. This is based on the existing section in the readme.io site and based on my conversation with @danthorpe.
Mutually Exclusive
A condition can assert whether its operation should be evaluated with mutual exclusion of other operations. This can be very handy for stopping operations from executing at the same time.
For example, if our application presents a modal alert, by executing this in the context of an operation with a mutually exclusive condition, we will prevent any other modal alert from being presented. Given the nature of event based applications this would otherwise be quite tricky. With Operations this can be done like this:
let alert = AlertOperation(presentAlertFrom: viewController)
alert.title = NSLocalizedString("Hello World", comment: "Hello World")
queue.addOperation(alert)

AlertOperation adds a mutually exclusive condition to itself during its initializer.
If your operation runs in isolation, it might be more beneficial to add it to its own queue which has a maxConcurrentOperationCount set to 1. If your operation runs  as a part of a group of operations (using either GroupOperation or simply queuing up multiple operations at the same time), then using mutual exclusion makes more sense.

Note: mutual exclusion does not stop subsequent operations from running.

Implementation
To add mutual exclusion to your own operation you’ll need to create an enum which will be used to define the mutual exclusion. Name it based on the type of operation you’ll be performing.
public enum CoreDataWork { }

Then in your operation, add a condition for mutual exclusion:
self.addCondition(MutuallyExclusive<CoreDataWork>)

If you are going to use this mutual exclusion in multiple operations it might be useful to create a typealias for this mutual exclusion:
public typealias CoreDataExclusive = MutuallyExclusive<CoreDataWork>

Then you can add it to your operation with:
self.addCondition(CoreDataExclusive())

Warning
You can cause a deadlock in your program if you add the same exclusion on a group operation and one of it's children.

Done - https://github.com/danthorpe/Operations/wiki/Mutual-Exclusion
Thanks @ryanjm!


Implement leaveChat method

Implements methods for leaving a chat.
Telegraph::chat($telegraphChat)->leaveChat();

$chat->leave();

This was not as straightforward as my last PR. Let me know if anything is in the wrong place, and I'll push a fix for you 👍
Closes #192

thanks!


Variable data attribute not accessible through Model.getVars()

In #268 the .data attribute was added to the Variable class, but this attribute is not accessible via Model.getVars(). See the following MWE:
from pyscipopt import Model, SCIP_RESULT

m = Model()

var1 = m.addVar(vtype = 'C', obj = 2, name='foo')
var1.data = 'foobar'

print(var1.data) # works just fine

print("----")

for var in m.getVars():
    print(var.name)
    print(var.data) # returns "None"

actual output:
foobar
----
foo
None

expected output:
foobar
----
foo
foobar

Note that similar issues might exist for the other classes adapted in #268

yes, the problem here is that every time you get a variable from SCIP, PySCIPOpt creates a new Variable object. Some time ago we discussed how to keep a single variable object but we didn't decide on anything. I guess now is the time for talking again about this.
Since variables have vardata (internally in SCIP) I guess one solution would be to store the python Variable in the vardata.
However, the other objects do not have a data, so then one would need to remember them on the python side.
I guess a more homogeneous solution would be to store a mapping between the SCIP data and the python data. @mattmilten any thoughts?

I am definitely in favor of storing a mapping in Python. This could lead to a more expensive lookup whenever you want to get the data, though.
Another solution is to store the variables (including their data) inside the model data:
m.data = vars

Then, when you want to retrieve them you don't need to call getVars() but simply access them in m.data.

the problem with storing it in m.data is what happens when you read a problem from a file. There was an issue about this, but can't find it anymore

I just tested reading in a model and storing something in a variable and then storing all variables in the model data. All works fine.

If it is stored in m.data one would have to take care to manually delete the info in m.data once a variable object is destructed , but that shouldn't be a problem

Well, if you store the variables in m.data they will not be destroyed, because there is always a reference left.

yes, the problem here is that every time you get a variable from SCIP, PySCIPOpt creates a new Variable object. Some time ago we discussed how to keep a single variable object but we didn't decide on anything. I guess now is the time for talking again about this.

I belive the same thing happens when I try to store an attribute in a Node (e.g. node.data and then try to access it via
node = model.getCurrentNode()
print(node.data)

?
A new Node object is created and thus I lose access to the attributes?

Yes, unfortunately this is currently the case. I understand that with Nodes my work around from above does not make much sense either. We need to make these objects persistent.

Would using a constraint handler as outlined in the SCIP FAQ work for now in PySCIPOpt or are there any further pitfalls?

that should work. I translated the coloring example of SCIP to pyscipopt some time ago. You can have a look in the branch use-probdata-to-store-model the file tests/test_coloring.py. However, do not expect it to work with the current pyscipopt.

I don't know what you are trying to implement. In general a constraint handler should work because the entire constraint handler is stored within SCIP itself using the constraint handler data. This should be the case for all the plugins. I suppose we really need to implement this functionality also for the simpler objects, like Node or Variable.


[WIP] Add support for counters

PROVISIONAL: Add support for the new RLMInteger and RLMNullableInteger types, which act as normal integers and contain API methods that allow them to take advantage of additional Realm functionality.
The basic functionality is working and there are a few tests.
To do (add items as necessary)

[ ] Review the API proposed in this PR
[ ] Should the new types inherit from NSNumber?
[ ] Compatibility with KVO
[ ] Compatibility with notifications
[ ] Compatibility with migrations
[ ] Compatibility with queries
[ ] Compatibility with initializing an object using a value
[ ] Swift support
[ ] Figure out how this works with the dynamic API
[ ] Fix everything marked in the code with a TODO flag

Bugs:

[ ]  Need to figure out what to do about object store-level schemas, which have no knowledge about the difference between counters and normal nullable/non-nullable integers. Right now we set the property on the schema as a nullable int, but it's being read back out as a non-nullable int, causing a test to fail (and other problems).

Retest this please

I don't expect the tests to pass yet, there are some outstanding issues.

Sorry for the disruption @austinzheng. This PR just happened to be the first one I found during my tests earlier today.

No worries @emanuelez, I just didn't want you to be misled because of all the failures :).

I'm still working on this, but since the remaining work is mostly more tests and the Swift API, I've added some reviewers.

The current failures are primarily due to a pair of tests failing:
CompactionTests.testReturnNoCompactOnLaunch
CompactionTests.testSuccessfulCompactOnLaunch

Those tests are way too strict. I'll take care of relaxing their constraints in a PR shortly.

I feel like the correct thing to do is to rewrite this PR to use RLMProxyBase (or whatever it's called) as the base for RLMInteger, and get rid of the two different types (nullable and non-nullable).

I don't think we have any spare bandwidth, but whenever we do this is probably ready for a first pass.

Not an employee anymore, but would love to get this in...eventually. If there are plans to review and merge this in the future, I'm happy to keep it up-to-date and on latest master (cc @bdash).


Reloading JEI causes a CMod crash

As you can see in this log after running /ct jeiReload I get a few tooltip errors that do not show up when the game is initially started and then a CMod crash which freezes my game. This might be due to the fact that I am using HEI rather than JEI and I have not had time to do much testing regarding that or maybe its just the large number of recipes in my pack. Here are the relevant mod versions I was using:
CT: 1.12.2-<IP_ADDRESS>7
ZenUtils: 1.16.3
ZRR: 1.1.5
HEI: 1.12.2-4.25.1

Here if the full log if you need it and here is my jei/jei.cfg file. My scripts are also here if you need them

I wonder why the server was stopped. Anyway, try v1.2.0, which adds progress bar while reloading JEI to avoid window freeze.

I tried v1.2.0 and it showed the bar and things seemed to load correctly, but once the bar was done and it seemed to finish reloading I got the same freeze/crash

:concerned: Can you post the new log?

Here is the log. The current issue might not be what I thought it was but the freeze/crash does still happen

zenrecipereload-1.2.1.zip
Try this?

That seems to give me this mixin crash

Oh, I typed wrong reference map name. missing ing
zenrecipereloading-1.2.1.zip

I can confirm that I was able to startup and run /ct jeiReload without my game crashing for the first time. Even the tooltip errors are gone now too.


Investigate Jenkins Pipeline and Shared Library Testing

Hi!
I just wanted to give you a heads-up that we plan to run a quick PoC to see how we could possibly test an ODS component's Jenkins pipeline and a shared library's code. Here are some resources we plan to have a closer look at:

https://github.com/homeaway/jenkins-spock
https://dev.to/kuperadrian/how-to-setup-a-unit-testable-jenkins-shared-pipeline-library-2e62

Resource 1) is capable of testing both pipelines and shared libraries by mimicking a Jenkins execution environment and makes use of the Spock testing framework. If you haven't had any touch-points with Spock yet, please have a look here:

http://spockframework.org
https://www.blazemeter.com/blog/spock-vs-junit-which-one-should-you-choose/

I'll post the results of the PoC soon. Cheers!

Should we also create an issue in shared library project?

IMHO don't think so. This is foremost at a PoC level to show off feasibility and value.

Jenkinsfile runner might also be an option:
https://github.com/jenkinsci/jenkinsfile-runner


Add weak platform independent PRNG to test framework.

Implement the GNU C library's random(3) pseudorandom number generator.
The algorithm is described: https://www.mscs.dal.ca/~selinger/random/
The rationale is to make the tests repeatable across differing platforms with
different underlying implementations of the random(3) library call.
More specifically: when executing tests with random ordering.

[ ] documentation is added or updated
[x] tests are added or updated

I would think the LGPL copyright is a problem.
Why not just do an RC4 stream cipher?

I would think the LGPL copyright is a problem.

Not if @paulidale has created code from scratch following a description.

Test test_ec failure isn't relevant here, is it?

I can confirm that the code was produced by me from the algorithm description alone.  I did not look at the GNU C library sources and I did not consult the code at the bottom of the page I linked to (nor any other code).
I did confirm that the output matches GNU's C library.  Surprisingly, it did the first time the code compiled.
I can't imagine why the EC test would fail.  Nothing, apart from the testutil driver, uses rand(3) or random(3).

I've seen other reports that EC is a bit off, so I will count that as irrelevant here, unless someone else is better informed.

Merged to master and 1.1.1.
Thanks all.


Made some changes in the readme file

some read me changes

The test case has not passed for get route /ice-flakes please solve it

The test case has not passed for get route /ice-flakes please solve it


Hotfixes

A quick fix to the NSF badges, installation instruction, and the format of reference entries

Nice LGTM!


Cuda error: no kernel image is available for execution on the device

📚 Installation

Version 1.3 no longer supporting Tesla K40m？ K40m has a compute capability of 3.5, which I believe we have dropped support of (https://developer.nvidia.com/cuda-gpus#compute). PyG needs pytorch 1.4 version. DOWNGRADED pytorch 1.2 version will be OK

You can use older versions of the extensions, e.g.:

torch-scatter==1.4.0
torch-sparse==0.4.3
torch-cluster==1.4.5
They should work fine for GPUs with older compute capabilities.

like this？
 pip install torch-scatter==1.4.0+${CUDA}
@rusty1s source build for PyTorch 1.4 may be one of the solutions，and Reminding GPU capabilities in install documentation should be better.
Thanks!


Error on Xcode 12.5.1

ERROR
Failed to build module 'PayUCheckoutProKit' from its module interface; the compiler that produced it, 'Apple Swift version 5.2.4 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1<IP_ADDRESS>)'
Description
I've used all solution provided by you guys in closed issues and tried stack overflow solutions to but my issue is didn't resolved. I think your pod is not supporting latest

PayUIndia-AssetLibrary (2.3.0)
PayUIndia-CheckoutPro (2.3.0):

PayUIndia-AssetLibrary (~> 2.2)
PayUIndia-CheckoutProBase (~> 2.3)
PayUIndia-Custom-Browser (~> 6.0)
PayUIndia-PG-SDK (~> 6.1)
PayUIndia-UPICore (~> 4.0)

PayUIndia-CheckoutProBase (2.5.0):

PayUIndia-PayUParams (~> 2.0)

PayUIndia-Custom-Browser (6.1.1)
PayUIndia-Logger (2.0.1)
PayUIndia-Networking (2.0.1):

PayUIndia-Logger (= 2.0.1)

PayUIndia-NetworkReachability (1.0.1)
PayUIndia-PayUParams (2.0.1)
PayUIndia-PG-SDK (6.2.2):

PayUIndia-NetworkReachability (~> 1.0)
PayUIndia-PayUParams (~> 2.0)

PayUIndia-UPICore (4.1.0):

PayUIndia-Networking (~> 2.0)
Socket.IO-Client-Swift (= 15.1.0)

PayUmoney_CoreSDK (4.2):

PayUIndia-Custom-Browser (~> 6.0)

PayUmoney_PnP (2.5.3):

PayUmoney_CoreSDK

@RajvinderPayU Please help me asap 😊

Hi @Akshay-bcat : Please refer the below link for this problem:
https://payumobile.gitbook.io/sdk-integration/ios-faqs#compile-time-error-while-compiling-payu-frameworks-like-below

@umangarya336 I did all those setting but still my issue is not solved


Project Name
Pixie
Project Website
px.dev
Contact Details 1
aimichelle
Contact Details 2
zasgar
Links to communication channels
CNCF Slack (#pixie)
Reason for governance review request
Application for moving levels from Sandbox to Incubation
Are there any sub-projects, plugins, and related?
N/A
Governance model
Our new governance model consists of a governing board of 2 maintainers, 2 end users, and 2 community users. End users represent people who actively use Pixie. The community users are active members of the Pixie community, but do not have maintainer responsibilities.
The goal of the governing board is to make decisions of the high level vision and direction of the project. For example, many users request to run Pixie in non-K8s environments, whereas Pixie's focus has always been on K8s.
Other governance duties, such as making decisions on architecture/design or pull requests falls to the maintainers of the project.
Governance documents
Project purpose: https://github.com/pixie-io/pixie/blob/main/README.md
Maintainers: https://github.com/pixie-io/pixie/blob/main/MAINTAINERS
Decision making process/maintainer process: https://github.com/pixie-io/pixie/blob/main/GOVERNANCE.md
Code of Conduct: https://github.com/pixie-io/pixie/blob/main/CODE_OF_CONDUCT.md
Contributing Guide: https://github.com/pixie-io/pixie/blob/main/CONTRIBUTING.md
Security: https://github.com/pixie-io/pixie/blob/main/SECURITY.md
Governance Execution Examples
We have just recently changed to this new governance model, so do not yet have examples.
Governance Evolution
We originally open sourced Pixie under the BDFL model: https://github.com/pixie-io/pixie/blob/490e08266649267fd8ff34e27192e0da7e6f55c6/GOVERNANCE.md
However, we would like to move away from the BDFL model now that we have matured. We would like to maintain the governance board, as we believe it is easier to make high-level decisions across a small group of people from different backgrounds.
Any specific aspects of your governance structure are you seeking feedback on?
No response
Do you have any concerns or specific areas where you feel your governance could be improved?
No response
Additional notes and resources
No response

Hi!  I'll be reviewing this, but I will not be able to start until early June.  If this review becomes the one thing holding up Incubation, please alert the TAG.

@jberkus when this is up for review a couple of considerations:

the governance was recently updated to move from BDFL model to a dual governance model
the new governance outlines two leadership groups, board and maintainers but does not articulate how these two groups work together or provide representation/feedback to one another

This review has been completed.
I hope that our assessment will help Pixie make continuous improvements on the project.  Thanks for your patience, everyone.


Divide model into Model, ModelAPI, Trainer

Description
Currently the models are called directly from the training method.
Thus model & library specific codes are having dense union to the common code.
I want to call model using common method.
Goal
Model & library specific codes not implemented out of src/model.
Create two models implementing Model, Trainer, ModelAPI.
Can change model from config (without modifying the code!)
Impact
Be able to handle different models using same method.
Reduce risks of changing improper codes.
Reference
Use architecture from TIS Kubo.
TIS_Kubo_2016
TIS_Kubo_2018
Additional
Each models contain Model, Trainer, ModelAPI.
Class Model implements the model & library specific codes.
To train: Trainer.train() calls Model.train()
To predict: ModelAPI.predict() calls Model.predict()
Tasks

[ ] Create AbstractClass of ModelAPI, Trainer
[ ] Implement lightgbm into Model, ModelAPI, Trainer
[ ] Implement NN into Model, ModelAPI, Trainer
[ ] Choose model from config file

This issue was solved in #16.
close #6


Migration and txid fixup

Creates migration framework with first migration that fixes txn.txid (in the background, while server is available for other queries) takes about 10 minutes to fixup mainnet.
#127

I think a migration is specific to it's database engine. If we're adjusting the schema of how something is stored, that could be different from database to database. There winds up being a lot of complexity in the Postgres layer and I really don't know what it will look like when we support a second database. So, I'll leave factoring out common things until we really know what they are?

I think a migration is specific to it's database engine. If we're adjusting the schema of how something is stored, that could be different from database to database. There winds up being a lot of complexity in the Postgres layer and I really don't know what it will look like when we support a second database. So, I'll leave factoring out common things until we really know what they are?

I generally agree with everything you mentioned. And no need to refactor at the moment, mainly thinking out loud.
What got me thinking about it here, is that the bug came from outside the DB engine. So all engines would have been effected. No need to solve it now, but I think that this is an example of a common thing that is needed.


Unable to successfully get Grafana Plugin working

Hi,
I am trying to get the plugin up and running as part of a POC for my company as we would like to bring this into our space however I am getting the below error:
Module not found: Error: Can't resolve '@k-phoen/backstage-plugin-grafana' in '/home/qsmidt/backstage-1/packages/app/src/components/catalog'
I have tried running the install command : cd packages/app && yarn add @k-phoen/backstage-plugin-grafana with the following output:
`cd packages/app && yarn add @k-phoen/backstage-plugin-grafana
yarn add v1.22.19
warning package.json: "dependencies" has dependency "react" with range "^17.0.2" that collides with a dependency in "devDependencies" of the same name with version "^16.14.0"
warning package.json: "dependencies" has dependency "react-dom" with range "^17.0.2" that collides with a dependency in "devDependencies" of the same name with version "^15.0.0"
[1/4] Resolving packages...
[2/4] Fetching packages...
warning Pattern ["app@link:packages/app"] is trying to unpack in the same destination "/home/qsmidt/.cache/yarn/v6/npm-app-0.0.0/node_modules/app" as pattern ["app<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping.
[3/4] Linking dependencies...
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0 || ^18.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @internal/plugin-data-file-plugin ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^16.0.0 || ^17.0.0 ".
warning "workspace-aggregator-3ef177af-8e4e-41aa-80f4-2278598a37ac > @backstage/cli ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^16.0.0 || ^17.0.0 ".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "@k-phoen/backstage-plugin-grafana ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
warning Error running install script for optional dependency: "/home/qsmidt/backstage-1/node_modules/cpu-features: Command failed.
Exit code: 1
Command: node buildcheck.js > buildcheck.gypi && node-gyp rebuild
Arguments:
Directory: /home/qsmidt/backstage-1/node_modules/cpu-features
Output:
/home/qsmidt/backstage-1/node_modules/buildcheck/lib/index.js:115
throw new Error('Unable to detect compiler type');
^
Error: Unable to detect compiler type
at BuildEnvironment.getKind (/home/qsmidt/backstage-1/node_modules/buildcheck/lib/index.js:115:9)
at BuildEnvironment.tryCompile (/home/qsmidt/backstage-1/node_modules/buildcheck/lib/index.js:537:15)
at BuildEnvironment.checkHeader (/home/qsmidt/backstage-1/node_modules/buildcheck/lib/index.js:423:25)
at Object. (/home/qsmidt/backstage-1/node_modules/cpu-features/buildcheck.js:16:4)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47"
info This module is OPTIONAL, you can safely ignore this error
success Saved 1 new dependency.
info Direct dependencies
info All dependencies
└─<EMAIL_ADDRESS>Done in 12.53s.`
Any info to get me going in the right direction would be greatly appreciated.

@qsmidt As per above logs it seems Grafana Plugin is installed.
Can you cross check it in package.json file located in packages\app folder
You can search for
    "@k-phoen/backstage-plugin-grafana": "<version-number>", in your case version number will be 0.1.12
If it is there than you are good and can follow rest of the document to add Grafana alerts and dashboard to your Backstage instance.

I tried setting up the plugin on a fresh Backstage instance (newly generated using npx @backstage/create-app) and didn't have any issue.
Is there any chance anyone having troubles can publish a minimalist Backstage app that doesn't work as it should?

Closing this since it's an old issue


zilencer: Migrate to @typed_endpoint.

migrated views:

zilencer.views.register_remote_server
zilencer.views.register_remote_push_device
zilencer.views.unregister_remote_push_device
zilencer.views.unregister_all_remote_push_devices
zilencer.views.remote_server_notify_push

to make sure the previous checks for remote_server_notify_push matches to old one, The RemoteServerNotificationPayload is defined.

Fixes:

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@PIG208 FYI in case you have ideas for some of the pydantic questions.

Changes:

removed AfterValidation for string pattern checking, thanks (Zixuan Li) for suggestion.
removed the min/max length passing to validate length for zulip_org_id, zulip_org_key, and new_org_key.
added test case to validate fixed-length check
updated typed_endpoint validation error template

Should @has_typed_endpoint wrapper for parameterized views should be removed, reference

Posted a handful of comments, otherwise lgtm.

addressed:

https://github.com/zulip/zulip/pull/29428#discussion_r1540001967

Should these be marked as the UUID types (https://docs.pydantic.dev/2.0/usage/types/uuids/)?

reason being that in the request and response, the UUID's will be represented as a string, validating it with UUId will raise Pydantic is_instance_of error.

I think https://github.com/zulip/zulip/pull/29428#discussion_r1569474892 might be worth a follow-up conversation you start in #backend; the current work isn't a regression at all, but I'm not sure I understand why it wouldn't be good to turn a string into a UUID object at our API boundary.
Anyway, merged after tweaking https://github.com/zulip/zulip/pull/29428#discussion_r1569479469, since that and the other proposed follow-ups are not necessary for this to be a useful productive checkpoint.


Something went wrong parsing the json output of reanalyze: 'SyntaxError: Unexpected token W in JSON at position 4'

Similar to #537
Parsing JSON from reanalyze failed. The raw, invalid JSON can be reproduced by following the instructions below. Please run that command and report the issue + failing JSON on the extension bug tracker: https://github.com/rescript-lang/rescript-vscode/issues
> To reproduce, run "/root/.vscode-server/extensions/chenglou92.rescript-vscode-1.7.6/server/analysis_binaries/linux/rescript-editor-analysis.exe reanalyze -json" in directory: "/root/project/src/Components/folder_1/folder_2"

I ran the above command and here's my output:
root@46a74b7bf5b6:~/project# cd /root/project/src/Components/folder_1/folder_2
root@46a74b7bf5b6:~/project/src/Components/folder_1/folder_2# /root/.vscode-server/extensions/chenglou92.rescript-vscode-1.7.6/server/analysis_binaries/linux/rescript-editor-analysis.exe reanalyze -json

[  Warning: can't find source dirs: /root/project/lib/bs/.sourcedirs.json
  Types for cross-references will not be found by genType.

]
root@46a74b7bf5b6:~/project/src/Components/folder_1/folder_2#

Seems like the JSON generated is invalid?

cc @cristianoc (the reporting mechanism actually works 😄 🎉 )

cc @cristianoc (the reporting mechanism actually works 😄 🎉 )

Indeed! Much faster to fix.

@Ashesh3 as a side done would you check why .sourcedirs.json was not found? Did the project fail to compile? This file should be generated by the compiler.

@Ashesh3 as a side note would you check why .sourcedirs.json was not found? Did the project fail to compile? This file should be generated by the compiler.

Yep, the build was never run before. Fixed now.


Spring version upgrade broke FeignClient loadbalancing

Describe the bug
Hello,
I recently upgraded a project from Spring Boot version 2.6.8 -> 3.1.3 and Spring Cloud version 2021.0.0 -> 2022.0.3
We had been utilizing the Spring Cloud Loadbalancer to provide custom loadbalancing logic to our feign clients with the following configuration (based on code found here https://www.tutorialspoint.com/spring_cloud/spring_cloud_load_balancer.htm).
@LoadBalancerClient(name = "my-service", configuration = CustomConfiguration.class)
@FeignClient(name = "my-service")
public interface MyServiceClient
{
   ...
}

After completing the version upgrade, it appears the default Round-Robin load balancing is always used as opposed to the CustomConfiguration.class.
I have been unable to find anything in the release notes for either OpenFeign or Cloud Loadbalancer to indicate a breaking change, so I was hoping for some insight here.
Thank you!

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


whenever i am trying to run the cmd "npm run build" it just shows error,and says npm is not able to find this file in the file directory

If you want to make your own version of the library you need to fork @coreui/coreui-react and work on your Github repo. (npm files doesn't contain build files on purpose)


Fix some issues in MPP framework and add client invalidate-all policy for internal RPC

Description

Fix the issue that cli will be blocked when the getState() is successful but getBatchResult() is failed.
Add a new invalidateAll() policy to resolve the issue that all cached client are invalid when target Node restarts. (added by Jackie Tien)

Coverage decreased (-0.004%) to 51.866% when pulling 99a273fe5dfab80c2d1ab65bb74d40ffb423d1ce on xingtanzjr/0511_test into 7a14619f9ad95561f2189edb64b1e6ee368273e3 on master.


Do we support hotwords in sherpa_ncnn?

Do we support hotwords in sherpa_ncnn?

Yes, please see

#257
#260
#285

I see. Do we need to change the decoding method to modified_beam_search like you did in sherpa onnx?

Yes. sherpa-onnx and sherpa-ncnn share the same doc for hotwords.

I see. Thank you for your patience.


Edit to do is not working properly

When we click on edit there is no option to save and it is returning to original list state.

willing to work on  this, kindly assign.

someone else has covered it.

yup


Release notes for MTV 2.6.3

MTV 2.6.3
Resolves https://issues.redhat.com/browse/MTV-1142 by creating release notes for MTV 2.6.3.
Previews:

https://file.emea.redhat.com/rhoch/263_rn/html-single/#new-features-and-enhancements-26_release-notes [First 4 items in New features]
https://file.emea.redhat.com/rhoch/263_rn/html-single/#resolved-issues-26_release-notes [First 6 items in Resolved issues]

@ahadas Please review this PR.

@ahadas I made the changes you suggested, with a few minor tweaks. Please review the PR again.

@bkhizgiy Please review this PR.

@ahadas @yaacov I made the changes you suggested. Please review the PR again.


Feat/multi site implementation

Description
This PR implemented on the feature of multisite for the Retail React App (Pwa). The starting point will be set inside pwa-kit-config.json file.
Context
According to 1 pager, we'd like to provide options 1a, and 2 for multisite feature
There are two options developers can choose to set up their multisite.

Option 1a: When a developer is standing up a multi-site project, they can configure a single codebase running on a single MRT environment/domain to work with multiple sites configured in Commerce Cloud business manager.
For example:

pwa-kit.mobifystorefront.com/us → RefArch site
pwa-kit.mobifystorefront.com/global → RefArchGlobal site

Option 2: When a developer is standing up a multi-site project, they can configure a single codebase running on multiple MRT environments/domains to work with multiple sites configured in Commerce Cloud business manager
For example:

us.pwa-kit.mobifystorefront.com → RefArch site
intl.pwa-kit.mobifystorefront.com → RefArchGlobal site
How does it look like in the code
In the PWA, we have a config file pwa-kit-config.json file that allows developers to set up their multisite configuration. The site configuration is a list of site objects. Each site object will require siteId and l10n, and siteAlias for option 1a, and hostname for option 2. The algorithm to look for site will look like this:

There is a util function that will look for the site based on the url. From the url, it should be able to pick out either a siteAlias or siteId from the url. If alias is found, it will use that value to look for site info, if not, the siteId will be used next. If none is found, it will return undefined
If no site info is found from previous way, another function will use the hostname to determine the site info
If none is found, use the default value declared in the pwa-kit-config.json
If none can be found, throw an error

Assumptions
Some assumptions for the algorithm to work:

Site Alias and site Id have to be unique for each site configuration

A few examples of site configuration:

Single site, single locale

{
    "app": {
        "defaultSiteId": "RefArchGlobal",
        "url": {
            "locale": "none",
            "site": "none"
        },
        "sites": [
            {
                "id": "RefArchGlobal",
                "l10n": {
                    "supportedCurrencies": ["GBP"],
                    "defaultCurrency": "GBP",
                    "supportedLocales": [
                        {
                            "id": "en-GB",
                            "preferredCurrency": "GBP"
                        }
                    ],
                    "defaultLocale": "en-GB"
                }
            }
        ]
    }
}

Option 1A: Multi-site, multi-locale that shows locale and site alias in the url as path or query_param. This will be deployed to one single MRT

{
    "app": {
        "defaultSiteId": "RefArchGlobal",
        "url": {
            "locale": "path|query_param",
            "site": "path|query_param"
        },
        "sites": [
            {
                "id": "RefArch",
                "alias": "us",
                "l10n": {
                    "supportedCurrencies": ["USD"],
                    "defaultCurrency": "USD",
                    "supportedLocales": [
                        {
                            "id": "en-US",
                            "preferredCurrency": "USD"
                        },
                        {
                            "id": "en-CA",
                            "preferredCurrency": "USD"
                        }
                    ],
                    "defaultLocale": "en-US"
                }
            },
            {
                "id": "RefArchGlobal",
                "alias": "global",
                "l10n": {
                    "supportedCurrencies": ["GBP", "EUR", "CNY", "JPY"],
                    "defaultCurrency": "GBP",
                    "supportedLocales": [
                        {
                            "id": "en-GB",
                            "preferredCurrency": "GBP"
                        },
                        {
                            "id": "fr-FR",
                            "preferredCurrency": "EUR"
                        },
                        {
                            "id": "it-IT",
                            "preferredCurrency": "EUR"
                        },
                        {
                            "id": "zh-CN",
                            "preferredCurrency": "CNY"
                        },
                        {
                            "id": "ja-JP",
                            "preferredCurrency": "JPY"
                        }
                    ],
                    "defaultLocale": "en-GB"
                }
            }
        ]
    }
}

Option 2:  Multi-site, multi-locale that does not want to display site info on the url.

{
    "app": {
        "defaultSiteId": "RefArchGlobal",
        "url": {
            "locale": "path",
            "site": "none"
        },
        "sites": [
            {
                "id": "RefArch",
                "hostname": ["us.domain.com"],
                "l10n": {
                    "supportedCurrencies": ["USD"],
                    "defaultCurrency": "USD",
                    "supportedLocales": [
                        {
                            "id": "en-US",
                            "preferredCurrency": "USD"
                        },
                        {
                            "id": "en-CA",
                            "preferredCurrency": "USD"
                        }
                    ],
                    "defaultLocale": "en-US"
                }
            },
            {
                "id": "RefArchGlobal",
                "hostname": ["global.domain.com"],
                "l10n": {
                    "supportedCurrencies": ["GBP", "EUR", "CNY", "JPY"],
                    "defaultCurrency": "GBP",
                    "supportedLocales": [
                        {
                            "id": "en-GB",
                            "preferredCurrency": "GBP"
                        },
                        {
                            "id": "fr-FR",
                            "preferredCurrency": "EUR"
                        },
                        {
                            "id": "it-IT",
                            "preferredCurrency": "EUR"
                        },
                        {
                            "id": "zh-CN",
                            "preferredCurrency": "CNY"
                        },
                        {
                            "id": "ja-JP",
                            "preferredCurrency": "JPY"
                        }
                    ],
                    "defaultLocale": "en-GB"
                }
            }
        ]
    }
}

3PP Approval

Currently in manual legal review here

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

a few util functions are added to determine the siteId based on the configuration (e.g based on hostname or site alias)
Move the l10n config from package.json into pwa-kit-config.json
Change the logic to dynamically load l10n config when the user switches site because each site will have a different config for their l10n. For example: RefArchGlobal has en-GB, it-IT, fr-FR while RefArch has en-US and en-CA.

How to Test-Drive This PR

Option 1a: Demo site: https://scaffold-pwa-test-env-2.mobify-storefront.com/ or at your local dev localhost:3000

When you first land on the site, the default site should be RefArchGlobal, when you navigate the site, the url should have global in the url.
On the home page, you should see a button that allows you to switch to another site (RefArch)
.
Click on it should navigate you to RefArch site, and when you navigate through the site, you should see us as part of the urls

Option 2: A bundle for two different domains are deployed to two MRT targets

RefArchGlobal: https://scaffold-pwa-multi-site-1.mobify-storefront.com/
RefArch: https://scaffold-pwa-multisite-2.mobify-storefront.com/

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@rsexton404 Multi-site PR for docs.

We probably need to document the new config structure, how about adding it to the README just like the URL customization feature?

Hi everybody, some question. In next time we start a project with a customer. Is a planned roadmap for this future und some sample. If i have one site My-Site with multiple locales but every country has his own domain, can i configure it like this then?
{     "app": {         "defaultSiteId": "My-Site",         "url": {             "locale": "path",             "site": "none"         },         "sites": [             {                 "id": "My-Site",                 "hostname": ["my-site.de"],                 "l10n": {                     "supportedCurrencies": ["EUR"],                     "defaultCurrency": "EUR",                     "supportedLocales": [                         {                             "id": "de-DE",                             "preferredCurrency": "EUR"                         },                         {                             "id": "en-DE",                             "preferredCurrency": "EUR"                         }                     ],                     "defaultLocale": "de-DE"                 }             },             {                 "id": "My-Site",                 "hostname": ["my-site.at"],                 "l10n": {                     "supportedCurrencies": ["EUR"],                     "defaultCurrency": "EUR",                     "supportedLocales": [                         {                             "id": "de-AT",                             "preferredCurrency": "EUR"                         },                         {                             "id": "en-AT",                             "preferredCurrency": "EUR"                         }                     ],                     "defaultLocale": "de-AT"                 }             }         ]     } }

Hi everybody, some question. In next time we start a project with a customer. Is a planned roadmap for this feature and some sample: If i have one site My-Site with multiple locales but every country has his own domain, can i configure it like this then?

Hi @nx-renezwinge, thank you for taking a look at the PR, please be aware that we are working on an alternative approach for config that allows you to override your URL config from the top level. You can see it here.
Regarding your question, hostnames or domain (in a new PR) is an array where you can specify a list of domains that share a same site. In your example, you only need to declare one site where hostnames looks like this  "hostname": ["my-site.de", "my-site.it"]. We also apply this same logic to the new PR.

I am closing out this PR because the alternative approach #318 is a better solution


Duplicate removal should use the globally configured temporary directory

It looks like it writes inside on the work directory instead for temporary files.

Luca -- thanks for the report. Which command line is running (from log/bcbio-nextgen-commands.log) when you're seeing temporary files in the work directory? There are a few different methods to de-duplicate depending on the input files and on a quick read of the code they appear to use the temporary directory. If I could focus on the place you're seeing issues happy to try and debug further. Thanks much.

I've found another occurrence of this during sv calling, when split and discordant reads are handled. Example command (notice that all temporary dirs are in /storage/rozo, while my path is configured elsewhere for temporary directories):
/storage/rozo/bcbio/anaconda/bin/samtools sort -n -@ 7 -m 682M -O sam -T /storage/rozo/projects/OV-223/ov223-final/work/tx/tmpJwI0MO/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-namesort /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup.bam | /storage/rozo/bcbio/anaconda/bin/samblaster --addMateTags -M --splitterFile >(/storage/rozo/bcbio/anaconda/bin/samtools sort -@ 7 -m 682M -T /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmp1iw6xJ/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-dedup-sorttmp-spl -o /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmps56WvI/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-sr.bam /dev/stdin) --discordantFile >(/storage/rozo/bcbio/anaconda/bin/samtools sort -@ 7 -m 682M -T /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmp1iw6xJ/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-dedup-sorttmp-disc -o /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmplrnQEc/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-disc.bam /dev/stdin) | /storage/rozo/bcbio/anaconda/bin/samtools view -b -S -u - | /storage/rozo/bcbio/anaconda/bin/sambamba sort  -t 7 -m 682M --tmpdir /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmp1iw6xJ/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-dedup-sorttmp-full -o /storage/rozo/projects/OV-223/ov223-final/work/bamclean/LC0044_R-OV-MNOD/tx/tmp1iw6xJ/LC0044-R-OV-MN-ready-reorder-fixrgs-gatkfilter-dedup-dedup.bam /dev/stdin

Luca;
Sorry about the issues. I can't replicate this with our test cases -- they appear to do the right thing with respect to the temporary directory. Could you provide more detail about your input YAML and how you define the temporary directories? Perhaps this is some sort of issue wtih the specification we can resolve. Thanks much.

Does tmp need to be defined inside the resources section in the bcbio_system.yaml file?

Luca -- that's exactly right:
http://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html#temporary-directory

Well, as embarrassing as it may seem, my indentation was off and the tmp field was on the wrong level. Adjusted and now works. Thanks and sorry for the noise!


feat(services): add SqliteConfig

Part of #3240

Hi, please ensure you use the same email (or at least linked to your GitHub account) when submitting patches. This helps us verify they're from you and avoid potential licensing issues.
The ASF mandates that all contributions meet the requirements.

Hi, https://github.com/apache/incubator-opendal/pull/3497/commits/48e6a99b00fe3e5f2bc103fc5ac8bf746ffc38f3 still has the same problem:
Is<EMAIL_ADDRESS>a valid email? Can you connect this mail with your github account?

Hi, 48e6a99 still has the same problem:
Is<EMAIL_ADDRESS>a valid email? Can you connect this mail with your github account?

Just a moment, please. Let me check

The pgsql part has been finished in #3495.

The pgsql part has been finished in #3495.

Yep, this is the another issue. This PR seems contain changes from others, maybe we need to Update branch.

Hi, 48e6a99 still has the same problem:
Is<EMAIL_ADDRESS>a valid email? Can you connect this mail with your github account?

I modified it


Oidc fails with 'Not a valid authorization code' error

When we try to access OIDC identity server, without providing any tenant we want to use (such as using it as a single tenant),
Helidon chooses default tenant configuration. This tenant has name @default. This name is now propagated as the tenant to be used. It is part of the redirection URI we receive back from the OIDC identity server (in my case KeyCloak when tested)
In TenantAuthenticationHandler#297 is the following code:
String redirectUri =
        encode(redirectUri(providerRequest.env()) + "?" + oidcConfig.tenantParamName() + "=" + tenantId);

This redirectUri is encoded to be part of the query params for OIDC identity server during initial request, but it its tenant name stops being encoded when sent back to the client. That means, there is suddenly  @default as a query parameter even though it should be encoded.
This can be fixed by the following line:
String redirectUri =
        encode(redirectUri(providerRequest.env()) + "?" + encode(oidcConfig.tenantParamName()) + "=" + encode(tenantId));

Fixed


open cert.pem: no such file or directory

When I try and run habitus (Linux build, ubuntu machine) I get the following error:
> habitus -f habitus.yaml --host tcp://docker:2345
2016/05/07 14:46:20 ▶ Using 'habitus.yaml' as build file
2016/05/07 14:46:20 ▶ open cert.pem: no such file or directory

My Docker doesn't require TLS to connect to. It looks like builder.go (https://github.com/cloud66/habitus/blob/f133be298d74c444bb260684e7b4f6989f4fdb18/build/builder.go#L59-L63) assumes it does.

@BenHall the latest in dev branch has a switch to turn TLS off now. Will merge into master for the next release.

this error is due using the new 'native' Docker mac support which is not using TLS.

How do you specify the use-tls flag? I'm using the 0.3 build but it doesn't seem to accept it

Non-TLS connection is supported on versions 0.4.5 and above.

I have to put this for it to work: ./habitus --use-tls=false


[hotfix][flink-java] Refactor DataSetUtils apply java 8 features

What is the purpose of the change
This PR contains just little refactoring.
Refactor DataSetUtils to get rid of redundant code, also apply some java 8 features, lambda functions in particular to substitute anonymous classes and shorten the code and make it more readable...
Brief change log

DataSetUtils: get rid of redundant code, like throw Exception in anonymous classes...
DataSetUtils: apply some java 8 features to shorten the code and make it more readable.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Closing this PR because the DataSet API is deprecated, making such changes (as well-intentioned as they might be) not worthwhile for us to review.


Duplicate keys detected: '0'. This may cause an update error

That is my component, it render well, but sometimes doesn't load, and I get these errors repeatly:

What must be done to fix that.

This has to do with the data you're providing. You do have duplicate keys in your data or it doesn't work with datatable in some way. Please send a console.log of columns and data in order to help you any further.

These are the two props

@marteoma data must be an array of objects, not an object itself.

Sorry, but that's not the mistake, I was passing an array, just forgot to use it this time.

@MicroDroid I am having the same error for the following columns and data

@MicroDroid please check my repo: https://github.com/ermand/vue-materialize-datatable-testing
Thanks in advance :)

Thanks a lot for creating the repository, I will check it out as soon as
possible and get back to you
On Mon, Nov 26, 2018, 17:36 Ermand Durro<EMAIL_ADDRESS>wrote:

@MicroDroid https://github.com/MicroDroid please check my repo:
https://github.com/ermand/vue-materialize-datatable-testing
Thanks in advance :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicroDroid/vue-materialize-datatable/issues/35#issuecomment-441682299,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIINf_Q3U-pg7r4tyYLsbI47wi1uvpsJks5uzAqOgaJpZM4WmVsK
.

Is this going to be merged?


Parse into JSON.

Hey,
I'm not familiar at all with Python and their structure. So this might be more a Python related question than a Carball related question. Hard to tell:
My goal is to parse a replay into a JSON that includes the analysis etc...
Currently I'm able to load the replay perfectly and let it parse it. Now I want to write that data to a .json file. Looked things up and found the json.dumps but it's providing me the following error:
TypeError: Object of type 'Game' is not JSON serializable
I pretty much understand the error but not sure how I would go about on parsing that into JSON.
Any help or clue towards the correct answer is very welcome.
Kind regards,
Pollie

We use the protocol buffers format detailed here to store our stats: https://developers.google.com/protocol-buffers/
The advantage is that our formats are backward compatible and somewhat self-documenting (https://github.com/SaltieRL/carball/tree/master/api). However the thing doesn't support jsonifying using the standard library json and has its own functions to do such things.
Use something like with py open(os.path.join('output.pts'), 'wb') as fo:     analysis.write_proto_out_to_file(fo)
(as written in our readme haha) to convert it to a format that can be read by the protobuf library in any of their supported languages, or call json = MessageToJson(analysis.protobuf_game) and write that out if you want it in (human-readable) json.
https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.json_format-module

Hey,
I saw the first part but was confused by what it returned.
Thank you very much for the link, that was exactly what I was looking for and it's working wonderfully.
Thank you for this and the previous answer on the other issue!


Truncate chromosome name when displaying in Analyze Variants view

New chromosome names are longer, but can be truncated for analyze view. Something like:
truncated_c_name = c_name
if len(truncated_c_name) > 15:
    truncated_c_name = truncated_c_name[:15] + '...'

Fixed in 22116600ad2fabfe68bfc3b29f7674e0d9f44c73. Thanks Brian.