[Fix] Clean TVM when no extra_operator is given

Description
Fix Makefile.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@yzhliu

Thanks @sxjscience

@sxjscience @yzhliu Is the cmake configuration output intended when calling make clean?
(mxnet) [lvtao@Mlt2-clx101 mxnet-official]$ make clean
Makefile:227: "USE_LAPACK disabled because libraries were not found"
Makefile:355: WARNING: Significant performance increases can be achieved by installing and enabling gperftools or jemalloc development packages
rm -f -r R-package/src/image_recordio.h R-package/NAMESPACE R-package/man R-package/R/mxnet_generated.R \
        R-package/inst R-package/src/*.o R-package/src/*.so mxnet_*.tar.gz
rm -f -r 3rdparty/mkldnn/build
rm -rf python/mxnet/*/*.so python/mxnet/*/*.cpp
rm -f build/tests/cpp/mxnet_unit_tests  build/tests/cpp/engine/engine_shutdown_test.o  build/tests/cpp/engine/threaded_engine_test.o  build/tests/cpp/engine/thread_local_test.o  build/tests/cpp/kvstore/gpu_topology_test.o  build/tests/cpp/misc/base.o  build/tests/cpp/misc/libinfo_test.o  build/tests/cpp/operator/activation_perf.o  build/tests/cpp/operator/coreop_perf.o  build/tests/cpp/operator/dropout_perf.o  build/tests/cpp/operator/fully_conn_perf.o  build/tests/cpp/operator/krprod_test.o  build/tests/cpp/operator/runner/core_op_runner_test.o  build/tests/cpp/operator/slice_channel_perf.o  build/tests/cpp/operator/tune/operator_tune_test.o  build/tests/cpp/operator/batchnorm_test.o  build/tests/cpp/operator/mkldnn_operator_test.o  build/tests/cpp/operator/mkldnn_test.o  build/tests/cpp/storage/storage_test.o  build/tests/cpp/test_main.o
rm -f -r build lib bin *~ */*~ */*/*~ */*/*/*~
(cd scala-package && mvn clean) || true
/bin/sh: mvn: command not found
cd /home/lvtao/Workspace/mxnet-official/3rdparty/dmlc-core; make clean; cd -
make[1]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/dmlc-core'
rm -f line_split.o indexed_recordio_split.o recordio_split.o input_split_base.o io.o filesys.o local_filesys.o data.o recordio.o config.o  libdmlc.a test/filesys_test test/dataiter_test test/iostream_test test/recordio_test test/split_read_test test/stream_read_test test/split_test test/libsvm_parser_test test/libfm_parser_test test/split_repeat_read_test test/strtonum_test test/logging_test test/parameter_test test/registry_test test/csv_parser_test test/unittest/dmlc_unittest test/unittest/unittest_inputsplit.o test/unittest/unittest_env.o test/unittest/unittest_main.o test/unittest/unittest_json.o test/unittest/unittest_array_view.o test/unittest/unittest_optional.o test/unittest/unittest_parser.o test/unittest/unittest_any.o test/unittest/unittest_lockfree.o test/unittest/unittest_param.o test/unittest/unittest_threaditer_exc_handling.o test/unittest/unittest_thread_group.o test/unittest/unittest_serializer.o test/unittest/unittest_threaditer.o test/unittest/unittest_tempdir.o test/unittest/unittest_logging.o test/unittest/unittest_config.o *~ src/*~ src/*/*~ include/dmlc/*~ test/*~
make[1]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/dmlc-core'
/home/lvtao/Workspace/mxnet-official
cd /home/lvtao/Workspace/mxnet-official/3rdparty/ps-lite; make clean; cd -
make[1]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/ps-lite'
rm -rf build  tests/test_connection  tests/test_simple_app  tests/test_kv_app_multi_workers  tests/test_kv_app_benchmark  tests/test_kv_app tests/*.d
find src -name "*.pb.[ch]*" -delete
make[1]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/ps-lite'
/home/lvtao/Workspace/mxnet-official
cd /home/lvtao/Workspace/mxnet-official/3rdparty/tvm/nnvm; make clean; cd -
make[1]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/nnvm'
rm -f -rf build lib bin *~ */*~ */*/*~ */*/*/*~ */*.o */*/*.o */*/*/*.o cli_test
make[1]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/nnvm'
/home/lvtao/Workspace/mxnet-official
cd /home/lvtao/Workspace/mxnet-official/3rdparty/tvm; make clean; cd -
make[1]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm'
-- The C compiler identification is GNU 7.3.1
-- The CXX compiler identification is GNU 7.3.1
-- Check for working C compiler: /opt/rh/devtoolset-7/root/usr/bin/cc
-- Check for working C compiler: /opt/rh/devtoolset-7/root/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /opt/rh/devtoolset-7/root/usr/bin/c++
-- Check for working CXX compiler: /opt/rh/devtoolset-7/root/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build with RPC support...
-- Build with Graph runtime support...
-- Build VTA runtime with target: sim
-- Build with contrib.hybriddump
-- Performing Test SUPPORT_CXX11
-- Performing Test SUPPORT_CXX11 - Success
-- Build with c++11
-- Build with thread support...
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build
make[2]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[3]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Entering directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[4]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[3]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[2]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm/build'
make[1]: Leaving directory '/home/lvtao/Workspace/mxnet-official/3rdparty/tvm'
/home/lvtao/Workspace/mxnet-official
cd /home/lvtao/Workspace/mxnet-official/amalgamation; make clean; cd -
make[1]: Entering directory '/home/lvtao/Workspace/mxnet-official/amalgamation'
rm -f *.d *.o *.so *.a *.js *.js.mem mxnet_predict-all.cc nnvm.cc
make[1]: Leaving directory '/home/lvtao/Workspace/mxnet-official/amalgamation'
/home/lvtao/Workspace/mxnet-official


no linux arm64 python bindings in pip

Hey! Could you please explain why python bindings build for linux/arm64 is disabled?
https://github.com/datafuselabs/bendsql/blob/3ba9d1fe50e55c86182e5bc565036195c89cc512/.github/workflows/bindings.python.yml#L57

It depends on ring which could not build on the default manylinux_2_17 with maturin.


Flutter web: Connectycube : P2P :Not disposing camera of User 2 on video call end when User 1 ends the call

We are using the below code as given in in the same P2P calling project
_callClient!.onSessionClosed = (callSession) {
if (_currentCall != null &&
_currentCall!.sessionId == callSession.sessionId) {
_currentCall = null;
CallKitManager.instance.processCallFinished(callSession.sessionId);
}
};
This code is correctly invoked at User 2's end when User 1 ends the call.  The call ends as expected for both users and the page transitions as expected. But the light next to camera remains on  and the browser tab indicates that the camera is still on.
This issue is happening on both chrome and edge browsers and is reproducing with P2P calling sample project hosted at https://github.com/ConnectyCube/connectycube-flutter-samples.git

could you please fill in all required fields on the creation issue step? What OS do you use for building the app? Do you use the latest version of our SDK and the sample? Please provide steps on how can we reproduce it on our side.

@paddymahadeva please try the new version (2.5.3), there we did some improvements for local media stream initialization and disposal of.
we will update our samples later for applying these fixes

Hey @TatankaConCube  thanks for your response, we are upgrading to 2.5.3 and will report back by next 2 days.
The build is made from windows OS and deployed to firebase
The connectycube versions we are on
connectycube_flutter_call_kit: ^2.2.4
connectycube_sdk: ^2.5.0
BTW, We are building for the web. This issue is faced on web browsers, specifically edge & Chrome.  It works fine on Firefox and Safari.

The issue still persists in edge after upgrade. We found the below exception there when we ended the call
0  Uncaught MissingPluginException(No implementation found for method reportCallEnded on channel connectycube_flutter_call_kit.methodChannel)
at Object.v (https://carefirst360-demo.web.app/main.dart.js:4770:3)
at https://carefirst360-demo.web.app/main.dart.js:141521:15
at bIs.a (https://carefirst360-demo.web.app/main.dart.js:6045:62)
at bIs.$2 (https://carefirst360-demo.web.app/main.dart.js:64769:14)
at bGQ.$1 (https://carefirst360-demo.web.app/main.dart.js:64763:21)
at bBB.b5f (https://carefirst360-demo.web.app/main.dart.js:65768:34)
at bBB.X6 (https://carefirst360-demo.web.app/main.dart.js:65770:21)
at biS.$0 (https://carefirst360-demo.web.app/main.dart.js:65150:11)
at Object.K0 (https://carefirst360-demo.web.app/main.dart.js:6170:40)
at aN.ww (https://carefirst360-demo.web.app/main.dart.js:65083:3)
v @ main.dart.js:4770
Could this be the reason?

The issue still persists in edge after upgrade. We found the below exception there when we ended the call
0 Uncaught MissingPluginException(No implementation found for method reportCallEnded on channel connectycube_flutter_call_kit.methodChannel)
at Object.v ()
Could this be the reason?

@paddymahadeva could you please try our test branch improvements_for_p2p where we reworked the UI and simplified the local stream initialization and disposing of. And please use the latest version of our SDK (2.5.5 at this moment).

Could this be the reason

no, it shouldn't, it is just the side effect of not supporting the Web platform by the  connectycube_flutter_call_kit plugin

@paddymahadeva had you a chance to check it? the issue is that the issue doesn't reproduce on our side

Hi @TatankaConCube not yet. We have not tried with test branch. Will report back in the coming week. For us the issue is reproducing with the P2P example project also.


[BUG] /personal-data - Text between options in the checkbox group is inconsistent.

Describe the bug
The text between the options in the checkbox group at the bottom of the /personal-data page is inconsistent.
Currently:

The wording for the notification and email checkbox is worded as a question, and in second-person. "Would you like us to send you notifications and emails?" The other two options in the group are written in first-person and as a statement. "I am okay with letting Reach4Help use my profile pic" and "I understand and acknowledge the Terms & Conditions."
(This option would also benefit from specifying that Reach4Help will send the notifications and emails. The word "us" could imply that the user is also agreeing to receiving emails and notifications from affiliates.)

The first option in the group does not have punctuation, whereas the other two do.

Suggested fixes:

Reword the notification and email text to: "I would like Reach4Help to send me notifications and emails"
Add a period.

https://reach4help-staging-web-client.firebaseapp.com/personal-data
To Reproduce
Steps to reproduce the behavior:

Navigate to the /personal-data page.
Scroll below the forms.
Notice the lack of punctuation in the first option.
Notice the difference in wording for the the second option.

Expected behavior
Information and options should be presented in a clear, specific and consistent manner, especially on pages asking the user for personal information, and permission to send emails.
Screenshots

Desktop:
Windows 10 - Chrome - Incognito

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Fixed and deployed to https://app.reach4help.org/


fix: allow empty non-required fields to save

Issue #, if available:
Description of changes:
If a non-required field is empty, DataStore.save would fail because we would try to save "" for AWSEmail, etc.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #861 (d7ac13a) into main (2e8504d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #861   +/-   ##
=======================================
  Coverage   92.80%   92.81%
=======================================
  Files         115      115
  Lines        4798     4800    +2
  Branches     1371     1371
=======================================
+ Hits         4453     4455    +2
  Misses        326      326
  Partials       19       19

Impacted Files
Coverage Δ

.../codegen-ui-react/lib/amplify-ui-renderers/form.ts
94.64% <100.00%> (+0.09%)
:arrow_up:

...-react/lib/forms/form-renderer-helper/cta-props.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Query nova client for allowed flavors based on config

Set min RAM and vcpu for flavor
tests

Looks good to me, subject to test suite


Logo proposal

Greetings, @prcutler
I am a designer in development and an open source enthusiast who would love to contribute to your project by designing a logo for it. I found your project exploring GitHub and found it interesting. About the process, we would be working together to create the logo that fits best with your project. The process is, of course, totally free and you can quit whenever you want. In case you agree, it would be useful if you had any ideas (shapes, colours, etc) to have something to start with.
Best regards!

Hi Michael!
Thanks for reaching out!  Yes, I'd definitely be interested in a logo for NFLPool.  I am not very good at design or user experience, be warned.  :)
You can see NFLPool in production at https://nflpool.xyz - I'd love to replace the "NFLPool" text in the upper left hand corner with a logo.  Something that probably has a transparent image that would work well under the black title bar.  (I can make the bar bigger to allow a logo, too)
As far as ideas - maybe something that uses an American football?  Probably don't want anything related to the NFL's shield logo (I'm already afraid that someday I'll have to change the name of the app and remove "NFL" as it's their copyrighted trademark).  I'm open to ideas, I'm terrible at brainstorming this kind of stuff and would be happy to continue the conversation with any ideas you have.
Thanks again and look forward to hearing from you!

Hello, I'm so sorry for disappearing I was finishing a semester. I want to resume the work as soon as possible just passing by to ask if you are still interested.

No problem!  Absolutely still interested.  I almost pinged you yesterday, glad to know your'e still interested in helping out.  Thanks!

Hi Michael,
Thanks so for much for working on this!
One question - what would it look like it if you took the water effect away and just used the font?  I ask because while the app is "NFLPool" it's more of a betting pool than water related and I don't want to cause confusion for new players.   What are your thoughts?
Thanks again - I really appreciate you taking time to work on this.
Paul

Hello, here you have some sketches, I want to hear your opinion about them.

Hi,
Sorry for the delay getting back to you, been busy over the holidays.
Thanks for doing these!  I like the third one down the most, but it's pretty close.  I also like #2.
Paul

Merry Christmas hahaha. I can use the coins like Os on #3. Apart from that, what would you like me to add/modify?

Actually, I like the coins not being the O's.  I can't think of anything else to modify, looks good to me.

Great! do you want me to upload the files through a pull request? I will add the svg and pdf version for you to have full control of your logo.


[PDI-15737] File encoding setting for INI files in Property Step are ignored

[PDI-15737] File encoding setting for INI files in Property Step are ignored
fix and test

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/test-src/org/pentaho/di/trans/steps/propertyinput/PropertyInputMetaTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change:  + 7.14%
Complexity Change:  + 7.69%

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -.39%:small_red_triangle_down:
Complexity Change: -.51%:small_red_triangle_down:
Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Instruction Change: -.19%:small_red_triangle_down:
Line Change: -.27%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.08%:small_red_triangle_down:
Complexity Change: -2.11%:small_red_triangle_down:
Instruction Change: -.14%:small_red_triangle_down:
Line Change: -.37%:small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%

org.pentaho.di.trans.steps.propertyinput.PropertyInput

Branch Change:  + 3.57%
Complexity Change:  + 2.46%
Instruction Change:  + 5.34%
Line Change:  + 6.49%
Method Change:  + 11.11%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change:  + .53%

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change:  + .18%


Unable to install DraStic from Play Store

Trying to install DraStic Nintendo DS emulator purchased from the Play Store and after downloading it gives error "Can't install DraStic DS Emulator. Try again..."

You may need to do a factory reset.
Just do a factory reset by holding power button, go to restart, then go to recovery.
From recovery menu, choose the factory reset option. Use the volume keys to navigate the menu, and the power button to confirm selection.


fix two phase topn opt support topn-project-filter-scan

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

since defer materialized for topn not support projection yet, close this PR


Obsolete GO:1902699 pentose catabolic process to acetate & some siblings

Similar to https://github.com/geneontology/go-ontology/issues/24353
These terms were created to capture data from a bioengineered Clostridia bacteria and there is no evidence that these are physiologically relevant.
There are no annotations, no mappings, these terms are not present in any subsets.

[x] GO:1902699 pentose catabolic process to acetate
[x]  GO:1902700 pentose catabolic process to butan-1-ol
[x] GO:1902698 pentose catabolic process to butyrate
[x]  GO:0044576 pentose catabolic process to ethanol
[ ]  GO:1902701 pentose catabolic process to propan-2-ol

Thanks, Pascale

Also obsolete regulation terms
GO:1900509 regulation of pentose catabolic process to ethanol
GO:1900511 positive regulation of pentose catabolic process to ethanol
GO:1900510 negative regulation of pentose catabolic process to ethanol


Cleanup type expansion in crochet_infer

[x] merge key_of.rs into expand_type.rs
[ ] simplify expansion of mapped types
[ ] update value AST to support numeric keys in object literals

Codecov Report

Merging #371 (cbe67be) into main (7b3023b) will decrease coverage by 0.20%.
The diff coverage is 81.98%.

@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
- Coverage   88.98%   88.78%   -0.21%
==========================================
  Files          42       41       -1
  Lines        6155     6186      +31
==========================================
+ Hits         5477     5492      +15
- Misses        678      694      +16

Impacted Files
Coverage Δ

crates/crochet_infer/src/lib.rs
97.51% <ø> (ø)

crates/crochet_ast/src/types/obj.rs
53.84% <75.00%> (+2.41%)
:arrow_up:

crates/crochet_codegen/src/d_ts.rs
76.15% <75.00%> (-0.11%)
:arrow_down:

crates/crochet_infer/src/expand_type.rs
75.88% <79.68%> (+1.78%)
:arrow_up:

crates/crochet_infer/src/util.rs
87.93% <80.00%> (-0.19%)
:arrow_down:

crates/crochet_dts/src/parse_dts.rs
88.55% <100.00%> (-0.08%)
:arrow_down:

crates/crochet_infer/src/infer.rs
95.08% <100.00%> (ø)

crates/crochet_infer/src/infer_expr.rs
95.09% <100.00%> (ø)

crates/crochet_infer/src/infer_pattern.rs
91.08% <100.00%> (ø)

crates/crochet_infer/src/infer_type_ann.rs
82.91% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Angular "ng serve" is not answering on http://localhost:4200 from Java

This is referenced there: https://github.com/angular/angular-cli/issues/2375
For some obscure reason, the workaround is to replace ng serve by ng serve --host <IP_ADDRESS> to make it work.
To reproduce, start ng serve then try this script with jbang:
///usr/bin/env jbang "$0" "$@" ; exit $?

import static java.lang.System.*;
import java.io.*;
import java.net.*;

public class MyTest {

    public static void main(String... args) {
         try {
            URL url = new URL("http://localhost:4200");
            HttpURLConnection connection = (HttpURLConnection) url.openConnection();
            connection.setRequestMethod("GET");
            connection.setConnectTimeout(2000);
            connection.setReadTimeout(2000);
            connection.connect();
            int code = connection.getResponseCode();
            System.out.println(code);

        } catch (ConnectException | SocketTimeoutException e) {
            e.printStackTrace();
        } catch (IOException e) {
            throw new RuntimeException("Error while checking if package manager dev server is up", e);
        }
    }
}

I just found the same problem using plain webpack on the patternfly react seed: https://github.com/patternfly/patternfly-react-seed.git
The same fix works: <IP_ADDRESS> as HOST.

Right :)


weird error stack trace and error printing

Let say I throw an error in render() of React component, the console output is ok. But if i try console.log(this.a.b.c.d.e.f) instead, the console error message is sent by redux-saga to point out that the error is caused by the last saga even if that saga is well tested, and the stack trace is helpless as it just show the location of the log() utils func in redux-sage source code but not the wrong console.log(this.a.b.c.d.e.f)

what version are you using? the v0.10.0 has some improvements on error reporting
https://cloud.githubusercontent.com/assets/5453835/14753131/30f3dd10-08cb-11e6-869e-6519cd463ff7.png
As for getting the exact location of the error (i.e. console.log) this is not possible to inside a library and requires external tooling like a babel plugin

I am using v0.10.0 and noted the improvement of error printing whick helps a lot to trace exceptions in sagas.
The problem I meet is that my code work like below
class Chart extends Component{
  componentDidMount(){this.doSomething()}
  doSomething(){
   let a = undefined.getFullyear()
  }
  render(){...}
}

But I get a error report like this

Then I change the code like this
class Chart extends Component{
  componentDidMount(){
  let a = undefined.getFullyear()
 }
 render(){...}
}

This time I get rignt error report

I want to know how is this wired problem caused?

clicking on the arrow of the first trace will give you the raw JS trace

sorry for my bad screenshot, the trace of the first one will help nothing

I reproduce the bug in the jsfiddle by changing https://github.com/yelouafi/redux-saga/blob/master/examples/shopping-cart/src/components/Product.js to be
import React, { Component, PropTypes } from 'react'

export default class Product extends Component {
  componentDidMount(){
    this.doSomething()
  }
  doSomething(){
    let a = undefined.getFullyear()
  }
  render() {
    const { price, quantity, title, action } = this.props
    return (
      <div>
        {title} - ${price} {quantity ? `x ${quantity}` : null}
        {' '}
        {action}
      </div>
    )
  }
}

Product.propTypes = {
  price: PropTypes.number,
  quantity: PropTypes.number,
  title: PropTypes.string,
  action: React.PropTypes.node
}

you can find the console output similar to the the attached above.

From the trace it appears the error is raised in the open saga; while it's trying to execute some Effect. Can't really see the link with React component, unless you're trying to render from within the Saga.

Ah didn't say your last message; I'll check

In the fiddle, the error is thrown while the Saga is executing a put Effect. Seems the dispatching causing react-redux's Connect React to re-render the React Component. the Error is thrown from the Saga (because it was thrown in the same stack frame of yield put), However Can't understand why all React specific calls where removed from the stack trace

That sounds like to have something to do with the length limit of stack trace, but when I change the location of the wrong line a little, as I mention above,  this bug is gone. And one more thingis that, aftet hot replacement by webpack ,the bug will also gone.

I think I've been experiencing this issue recently.  I've been digging into it a bit and I haven't quite figured it out but thought I'd pass along some info.
It seems like there are two issues that may or may not be related.  First is the fact that redux-saga is seemingly throwing errors initially thrown by React components.  @yelouafi, like you said, I traced this to a put effect updating my state, which caused react-redux to render components that had errors.  However, one strange thing I noticed was that the behavior seems to change when using promises.  Here's a fiddle to demonstrate:
https://jsfiddle.net/npbee/d5dt0fmw/4/
If you comment out the promise call at line 35, the error is thrown by React and not redux-saga.
The second issue I think is what this issue was originally about.  When redux-saga does throw, the full stack traces aren't there.  The best I could do was trace it back to this line:
https://github.com/yelouafi/redux-saga/blob/master/src/internal/proc.js#L237
if(result instanceof Error)
    result.sagaStack = `at ${name} \n ${result.sagaStack || result.message}`

It seems like it's just building up a new stack from the message of the given error and throwing away any stack trace info that may already be there.
Let me know if any other info would be helpful!

@npbee your second point is what I've debugged today, too. I think the problem is that result.stack (where the precious stack is) is not passed into successive log call.
https://github.com/yelouafi/redux-saga/blob/master/src/internal/proc.js#L243
if(result instanceof Error) {
    result.sagaStack = `at ${name} \n ${result.sagaStack || result.message}`
}
if(!task.cont) {
    log('error', `uncaught`, result.sagaStack || result.message)
}

I think the issue comes from the log('error', ...) call. In the browser the call translates to console.error which prints the error stack at the moment of the console.error call rather than the stack at the moment the error happened.
In redux-saga there is a different between the 2 moments: When an error happens the middleware bubbles the error up the call/fork chain so it can be caught by parent sagas. The propagation stops at the top level parent (root saga or a spawned saga) and at this moment the error is printed on the console.

I see, that's right!
I've tried to replace result.message in previous code with result.stack and got:

which is fine for me. Is that a good fix for this?

which is fine for me. Is that a good fix for this?

I think so

In the fiddle, the error is thrown while the Saga is executing a put Effect. Seems the dispatching is causing react-redux's Connect to re-render the React Component. the Error is thrown from the Saga (because it was thrown in the same stack frame of yield put)

Like mentioned on #250, i'm also trying to send all uncaught exceptions to a monitoring system. The problem is when it happens on the same frame as a put effect. It would simply be logged by redux-saga and not reach the window.onerror handler.
@yelouafi, is there an option to disable this behavior and rethrow the exception? Does it makes sense?

@yarcub
If what you need is crash reporting, you can attach an error handler to the root saga
sagaMiddleware.run(rootSaga).catch(...)

@yelouafi, is that the correct API?
sagaMiddleware.run(...).catch is not a function

@yarcub should be
sagaMiddleware.run(...).done.catch(...)

b/c run returns a Task object not a promise


Specify raw ISO format explicitely to avoid QEMU warning

Warning occurs in QEMU 2.3.0. It looks like this:
WARNING: Image format was not specified for 'build/os-x86_64.iso' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.

So QEMU does not allow writing to block 0 if we auto detect the image type. It seems like QEMU uses block 0 to perform the autodetection, so writing some random bytes to it could cause an accidental image type change on the next start. See the QEMU changelog for (a bit) more information.
We can fix this by specifying the format explicitely through format=raw. Thus the autodetection is disabled and block 0 is writable again. It eliminates the warning, too.

[ ] cherry-pick to all tags


Enable DISPLAY_NAME in sasjs service response

We need a consistent display name in the service response - currently it differs between SAS9 and VIYA.

actually - for SAS 9 - %mf_getuser() DOES return the display name.
For Viya, the display name is not available as a macro variable, and should be collected from the NAME attribute of the following endpoint, eg:
https://sas.analytium.co.uk/identities/users/@currentUser


Migrate away from https://helm.min.io/

The E2E tests rely on MINIO for a reliable standalone API that can simulate S3 buckets.
The current https://helm.min.io/ (github repository) is deprecated and no longer supported.
The new repository is https://charts.min.io/ (github repository).
An initial migration attempt led to timeouts on E2E tests due to the new images being way larger than the current images. However, it would be nice to move away from the old and unsupported version.

Discovered during the process of supporting arm64 e2e tests (https://github.com/fluxcd/source-controller/pull/523).

Hello @pjbgf, this issue seems to have been left out. Is a fix still needed? If so I'd be happy to work on it
Will the Helm version and tag need to change too? Currently, the Minio Helm version is at 4.0.1
https://github.com/pjbgf/source-controller/blob/f6029ab0f6085b41348e14be75e9b7378741c99f/hack/ci/e2e.sh#L9

Yes, we still need to work on it - thank you for volunteering.

Will the Helm version and tag need to change too?

The goal is to move away from the unsupported version. It would be great to go for that latest version. :+1:


Frontend Functionality - User

Take the user logged-in user and do the following on these sites:
header.html

Display the user name
Enable the user to logout with the logout button

profile.html

Display the user name
Display the statistics of the user

matchresult.html

Display and set the user as a default value for the first player of the first team

To logout just use a hyper link to /logout and for the username you can use ${#authentication.getName()} but you need to check if ${#authentication} is null before calling .getName() on it. You can also use ${#authentication.getName()} to get the default value for Team 1 Player 1. No null check needed there because only logged in users can visit that page.


Updates spring cloud build/commons to 3.1.0

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[X] Enhancement
[ ] Refactoring

:scroll: Description

Updates to spring cloud 2021.0.0 and boot 2.6.x
:bulb: Motivation and Context

:green_heart: How did you test it?
Ran a full build
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[x] All tests passing
[ ] No breaking changes

:crystal_ball: Next steps

Would need a new 2.4.x branch

Thanks @spencergibb. We will release 2.4 with this change in upcoming days.

Thank you @maciejwalkowiak :+1:

@maciejwalkowiak is there an ETA for a 2.4 release? Would it be possible to release a milestone or release candidate now?

@sfussenegger it will happen most likely over the weekend or beginning of next week - we are having team meeting today in the afternoon to discuss it.


docs: Add Monitor resolution impacts into the guide

I've been using Aerospace for the last couple months, while it worked great in office, it didn't at home where I have 2 different monitors with different screen resolutions.
As a result I've been having performance impacts, where it took long for my windows to switch between workspaces.
After stalking the the issues tab I noticed #333 and in that conversation #149  and wished this was somewhere included into the guide/docs, either as a warning or in the comparison.

Initially it seemed to work fine with Displays have separate Spaces' disabled, but now I'm again hitting delays when pressing keyboard shortcuts and Aerospace hanging, (loading when hovering over the menubar) to then all of a sudden catch up to switch between all spaces.
Pr can be ignored for now, will create a defect with example, later today when I reproduce it again.


How to pass FORM.cs data from Master Dialog to Details Memory Grid editor

hello everyone!
I want to pass the detaillist field from form.cs  to editor.ts
so I can push data in that detaillist from editor.ts
any suggestion would be appreciated
Thanks

There are several issues regarding this, just do a search first please....

Thanks, @brunobola
I already search for several issues regarding this but I end up by getting only fields
I want to access my whole DetailList data on the dialog.ts

Modify your ListHandler, to return the data, then see my post on the post button for the code, this is done in the grid ts and displays the data in the dalog ts, the data comes from the form which is mapped to the repository


Configure latest pebble in spring using xml configuration

Hello!
As the subject says :-)
How can I set up latest pebble in spring using xml configuration?

Please see this: https://github.com/mbosecke/pebble-spring3/issues/7
It may be time to update the docs with the snippet :)

Thanks.
I've now open sourced the documentation, pull requests are welcome: https://github.com/PebbleTemplates/pebble-docs


Upload YouTube Videos Automatically

This PR includes a new feature that enables an import of all the youtube videos of a specific user to the Streams DB.
*Note - the user model should be updated to include a new field for youtube_profile_link
How it works -

A YouTube user was created specifically to use the youtube_api_key safely
Google API was installed - (pipfile & pipefile.lock)
Title and description fields were added to Streams model - (migration - 0002)
The function - (view.py) -

Receives a youtube_profile_link from the User model
Extracts the user's playlist
Extracts title, description, link and publish date for each video in the playlist
Returns the extracted data into Streams DB

new PR was added instead


Mirrored content formatting enhancement

Would be great to reduce the focus of the meta-data and provide more focus to the mirrored content.
Taking https://github.com/gberche-orange/pivotal-tracker-mirror/issues/178 as an example, this would translate into:
When a user is authenticated to a sample app via an external IdP, and they try to authenticate to another sample app, they get a sad cloud if the second sample app does not have the IdP enabled for the second sample app.

Steps to reproduce:
1. Push the auth code sample app and select an external IdP
1. Push the implicit sample app and do not select an external IdP
1. Log into the auth code sample app via the external IdP
1. Click the log in link for the implicit sample app. (See the screenshot for error)

Expected result:
1. The user should be redirected to the UAA login page to enter creds in UAA.

---

Mirrors: [story 117497613](https://www.pivotaltracker.com/story/show/117497613) submitted on Apr 13, 2016
- Labels:
- Requester: Kevin Huang
- Estimate: 0.0

while it is currently:
- **Link**: https://www.pivotaltracker.com/story/show/117497613
- **Labels**:
- **Requester**: Kevin Huang
- **Estimate**: 0.0

When a user is authenticated to a sample app via an external IdP, and they try to authenticate to another sample app, they get a sad cloud if the second sample app does not have the IdP enabled for the second sample app.

Steps to reproduce:
1. Push the auth code sample app and select an external IdP
1. Push the implicit sample app and do not select an external IdP
1. Log into the auth code sample app via the external IdP
1. Click the log in link for the implicit sample app. (See the screenshot for error)

Expected result:
1. The user should be redirected to the UAA login page to enter creds in UAA.

Stories with empty descriptions would not display null as in https://github.com/gberche-orange/pivotal-tracker-mirror/issues/231#issue-167689093
Similarly for comments such as https://github.com/gberche-orange/pivotal-tracker-mirror/issues/178#issuecomment-235334252 this would result in
Madhura Bhave [commented](https://www.pivotaltracker.com/n/projects/997278/stories/119548885/comments/133997707) on May 13, 2016, 9.23pm :

@stummidi pausing this story because we cannot guarantee that the email entered on the first page will only map to one username because emails are not unique.

One alternative is to show the username and password fields one the internal IDP has been "discovered" based on email entered on the first page.

<!--
Comment Id: 134010181
-->

while it is currently (note the comment URL typo):
- **Link**: https://www.pivotaltracker.com/n/projects/997278/stories/119548885/comments134010181
- **User**: Madhura Bhave

@stummidi pausing this story because we cannot guarantee that the email entered on the first page will only map to one username because emails are not unique.

One alternative is to show the username and password fields one the internal IDP has been "discovered" based on email entered on the first page.

Comment Id: 134010181

@ArthurHlt in https://github.com/cf-trackermirror-bot/buildpacks-tracker-mirror/issues/36#issuecomment-239445010 the comment URL typo is still there: it links to https://www.pivotaltracker.com/n/projects/1042066/stories/120715555/comments135644775 instead of https://www.pivotaltracker.com/n/projects/1042066/stories/120715555/comments/135644775

Fixed typo in 6e63f405c1d336774de0948a971c1235d530dda2

Note comment url fix into https://github.com/ArthurHlt/pivotaltracker-java-client/commit/9be49dd2475a9febe9af3247d7510edd019553ca

Mention corrected here: https://github.com/orange-cloudfoundry/pivotaltrackermirror/issues/10
Null description corrected on commit: bce8131


support for pytrees in projection_halfspace and projection_hyperplane

re-implemented projection_halfspace and projection_hyperplane so they work with pytrees
added tests to reflect support
also added a test for projection_box,

Thanks for the suggestions and comments @mblondel  ! I've incorporated them all (except the further fix for box projections). Shall I squash the commits into one?

Yes please :)
Le mer. 29 sept. 2021 à 17:50, Robert M. Gower @.***> a
écrit :

Thanks for the suggestions and comments @mblondel
https://github.com/mblondel ! I've incorporated them all (except the
further fix for box projections). Shall I squash the commits into one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/jaxopt/pull/47#issuecomment-930304697, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZB2XDYZFPONGYG73256TUEMYTTANCNFSM5E6HBEYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Ok, I think I managed to squash the commits (excluding a merge commit that came for free)

Did you force push? There are currently 8 commits.

nope, I hadn't forced the push. Now it's right (I hope)


[KED-786] Fix zoom offset

Description
Previously, when nav sidebar was open, zooming the chart would kind of skew the viewport to the left. This change fixes this, and also helpfully removes an extra animation element, so performance will hopefully be improved, if anything.
Development notes
I've also improved React ref usage on the Flowchart component:

Improve naming (remove underscores etc, as these are not a widely-recognised naming pattern).
Use React.createRef instead of callback refs.

QA notes
Check zoom when nav is both open and closed. Check different screen sizes, and hover on tooltips.
Checklist

[x] Read the contributing guidelines
[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[x] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[x] Added tests to cover my changes
[x] Assigned myself to the PR
[x] Added Type label to the PR

Legal notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Have you explored other ways to get the nav offset width? Could the current implementation (below) become brittle over time if we were to change the side bar width in the design (have to change in multiple places)
getNavOffset(width) {
    const navWidth = width > 480 ? 300 : 0; // could these numbers be in some shared config?
    return this.props.visibleNav ? navWidth : 0;
  }

Have you explored other ways to get the nav offset width? Could the current implementation (below) become brittle over time if we were to change the side bar width in the design (have to change in multiple places)

Yeah it's not ideal, but it's using both JS variables and Sass variables:
$nav-width: 300px;
$breakpoint-small: 480px;

Without an easy way to share variables between Sass and JS (and I think it'd be overkill to implement a complicated tooling solution for this use-cas), I'm inclined to leave as is. But perhaps it could be documented better?

@richardwestenra ok cool let's go with the documentation, maybe there's a good way of doing this - will investigate


xActiveDirectory: Removing SupportsShouldProcess

Pull Request (PR) description

Changes to xADObjectPermissionEntry

Remove remnants of the SupportsShouldProcess (issue #329).

Changes to xADRecycleBin

Removed SupportsShouldProcess from the resource since DSC does not
support that interactive function (issue #328).

Changes to xADOrganizationalUnit

The unit tests are using the stub classes so the tests can be run locally.

This Pull Request (PR) fixes the following issues
Fixes #329
Fixes #328
Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in resource directory README.md.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #441 into dev will decrease coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            dev   #441   +/-   ##
===================================
- Coverage    96%    96%   -1%
===================================
  Files        20     20
  Lines      2705   2704    -1
  Branches     10     10
===================================
- Hits       2608   2607    -1
  Misses       87     87
  Partials     10     10


Host frontend assets on GitHub Pages.

This patch introduces a build pipeline that hosts frontend assets on GitHub Pages.
In order to do that, I've done these:

Changed Parcel build URL so that it points to relative URL, instead of root URL. (Important if we don't have a custom domain)

we may use vaxx.tw custom domain and move API to api.vaxx.tw for the next step, but that requires further migration, so let's run it on g0v.tw/vaccinate first.

Added CORS rules to backend.

Currently allowing ANY origin * to access GET, HEAD and OPTIONS.

What I didn't change by intention:

Backend server still responds to GET / => index.html. Keeping this for now so that we can do iterative migration.

To @kevinjcliao :
It seems that gh-pages branch already exists. If you merge this branch, all files in that branch will be replaced by Parcel build. If there is any file that is being accessed somewhere else, please let me know, I'll come up with a solution.
Closes #67

Thank you for your hard work on this!

@kevinjcliao Likewise! Please let me know if you need help on the api.vaxx.tw thing I mentioned in the description.


fix macro style

修改宏的代码风格为驼峰格式

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

PR to v1.2.0


fix: could not pass dart analyze

Description
With Flame v1.6.0 add method of the Component class has a return type of FutureOr<void>. Since the Behaviour class extends from Flame's Component class and overrides its add method, it needed to be updated.

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[x] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Can you also update the version constraint in the pubspec.yaml for the Flame dependency? We should bump this to 1.6.0 to allow for this change!


Validation always return true

I Have this  model
  public class BaseData
  {
    [Required]

    [MinLength(10)]

    public string ActionSource { get; set; }

    }

and this is my code
        Json.Schema.JsonSchema schema = new JsonSchemaBuilder().FromType<BaseData>().Build();

        ValidationOptions options = new ValidationOptions();

        options.OutputFormat = OutputFormat.Basic;

        var validate = schema.Validate(JsonDocument.Parse(bodyString).RootElement, options);

the problem is validate.isvalid always returns true when ActionSource  in json or not

Note:
when build the schema manually everything work without any issues
            Json.Schema.JsonSchema schema1 = new JsonSchemaBuilder().Properties(                (                    "ActionSource", new JsonSchemaBuilder()                        .Type(SchemaValueType.String)                        .MinLength(10)                )            )            .Required("ActionSource");

Please serialize the resulting schema and print it for me.

Can You Please Tell me how can i serialize it ?
I mean all object or only specific object  inside it ?

Just with the serializer.  Schemas are already serializable.
var json = JsonSerializer.Serialize(schema);

Then print json.

i found where is the problem,
i'm using [required] attribute of dotnet DataAnootations not Json.Schema.generation
I'm sorry for that
can i ask you a question before close the issue ?
in json i want to write "actionSource"  (small letter) not "Actionsource" (capital letter) without impact the required validation attribute, how can i do it ?

That's not currently supported, but I can add support for the JsonPropertyName attribute to do this.

Thanks @gregsdennis

@bahaasamoudi I was wrong.  Looks like I do support the JsonPropertyName attribute already. See https://github.com/gregsdennis/json-everything/blob/master/JsonSchema.Generation.Tests/SchemaGenerationTests.cs#L152

Thanks @gregsdennis  it's work,
i have a question, when i have DateTime property and pass it in postman like  {"eventTime": "2021-05-19T12:41:32-05:00"}
the validation message is "Value is string but should be object"
how can i solve this problem ?
this is my class
 public class BaseData     {         [Required]             [JsonPropertyName("eventTime")]         public DateTime EventTime { get; set; } }

What does the schema look like?

"{\"type\":\"object\",\"properties\":{\"eventTime\":{\"type\":\"object\",\"properties\":{}}},\"required\":[\"eventTime\"]}"

Looks like the system doesn't know what to do with DateTime.  You'll need to provide a generator for it.

Please open a new issue for this. The system should handle that, but it seems I don't have a test for it, so it's not being checked.


[Known Issue] Processing NaN May Result Undefined Behavior & Crash

We are not planing to fix this issue. You may need to delete the app and restart over.

maybe fixed fd16398


Empty articles global feed update

Newsbeuter version (copy from newsbeuter -v):
newsbeuter 2.9 - http://www.newsbeuter.org/
Copyright (C) 2006-2010 Andreas Krennmair
newsbeuter is free software and licensed under the MIT/X Consortium License.
Type `newsbeuter -vv' for more information.
System: Linux 3.16.0-4-amd64 (x86_64)
Compiler: g++ 6.2.1 20161215
ncurses: ncurses 6.0.20161126 (compiled with 6.0)
libcurl: libcurl/7.52.1 GnuTLS/3.5.8 zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3 (compiled
with 7.51.0)
SQLite: 3.16.2 (compiled with 3.15.2)
libxml2: compiled with 2.9.4
Steps to reproduce the issue:

Add feeds to the urls file
Open newsbeuter (with the option to update feeds at start or after hitting R)
Open a feed and article while newbeuter updates the feeds
Wait for newsbeuter to finish updating the feeds

Other info you think is relevant:
When newsbeuter finishes updating the feeds, the open article is turned "blank", with (what seems to be) garbage from memory.
If I hit q to close the article, it goes back to the article list for that feed, as it should, and the article is still marked as new.
I'm using the version from the testing branch of Debian (Stretch).
While updating:

After updating:

While updating:

After updating:

EDIT: TL;DR: A bug, but not a big scary one, more like a ladybug.

This is a duplicate of #223, so I'm going to close it. Thanks for a nice report though.

@Minoru Ah I searched for different keywords, that's why I couldn't find it. Sorry for the trouble!


set error to true when payload instanceof Error

Should set error to true when payloadCreator return error

@xiaohanzhang Thanks for the contribution!

can you write some tests around this?
can you describe some specific use cases (when I have an error, I usually pass the error to the action creator directly)?

#43 is related.
@xiaohanzhang can you describe the use case?
@timche if the use case makes sense, I don't see a problem with merging this, as it seems to have been asked for and supported before.

@yangmillstheory Thanks for great work and quick reply, I added a test for it
use case:
const fooAction = createAction('FOO', (...args) => {
  return isValid(args) ? {foo: 'bar'} : new Error('arguments is not valid');
});

I feel it will make more sense to put arguments validator inside actions, otherwise we need check it in every components.
With current implementation, I need create another wrapper for real action:
const fooActionWrapper = (...args) => {
  return isValid(args) ? fooAction(...args) : fooAction(new Error());
}

Thanks @xiaohanzhang. I think we should merge (pending @timche's feedback), but I would like to understand this a bit deeper, beyond avoiding writing wrappers.
Can you give a couple of examples of an actual flow in your application where this comes in useful? What kind of validation are you doing in your payload creators?

We have some rest api action,  I want add more client-side validation before it send to server.
It been used by many components and projects. So I hope can put the validator inside action.

@timche please let us know if there are any blockers.

Hi, this new change doesn't seem to affect payloadCreator that returns a Promise, there's no error field in the dispatched action. I'm using redux-promise as well.
export const myAction = createAction('ACTION_TYPE', () => myAsyncFunc());
myAsyncFunc does some network requests and returns a Promise that can resolve into an Error. Can you suggest a way to make it work?

@holybom I usually just throw an error inside myAsyncFunc, redux-promise will catch that error:
https://github.com/acdlite/redux-promise/blob/master/src/index.js#L19


fix(cli): argo cron list and get to show schedules without timezone

Motivation
Currently argo cron list and argo cron get are showing the schedules with timezone, when available. This PR removes it as it doesn't bring any value because it can be seen in the timezone field.
Modifications
The schedule string can now be requested with and without the timezone.
With timezone, it is used for the annotation last-used-schedule, so changing the timezone while keeping the schedule will be seen as a new schedule.
Without timezone, it is used in argo cron CLI.
Also update every instance of schedule to be schedules as suggested by @agilgur5 https://github.com/argoproj/argo-workflows/pull/12616#discussion_r1501850996

Verification
Current:
argo cron list

argo cron get

With this PR changes:
argo cron list

argo cron get

The CronWorkflow label last-used-schedule still uses the schedule with timezone

whille implementing this, I also found that schedule was still marked as required in the open api spec/json schema/CRD spec so I removed it. Do you think it should have a dedicated PR or is it ok to have it here? @agilgur5

Is the CLI fix only relevant to 3.6? Or does it also impact 3.5/3.4?
If these are all just follow-up fixes to the multiple schedules PR, we can leave it all as one I suppose -- just would rename the PR.
If the CLI fix is relevant to 3.5/3.4, then I think we should split the rest out, so that it can be backported

Is the CLI fix only relevant to 3.6? Or does it also impact 3.5/3.4?
If these are all just follow-up fixes to the multiple schedules PR, we can leave it all as one I suppose -- just would rename the PR.
If the CLI fix is relevant to 3.5/3.4, then I think we should split the rest out, so that it can be backported

this only applies to 3.6 as it was introduced in #12616

I know schedules was, but I wasn't sure if this TZ duplication happened in earlier versions with single schedule as well

I know schedules was, but I wasn't sure if this TZ duplication happened in earlier versions with single schedule as well

the timezone in argo cron lilst and argo cron get was also introduced in that PR

Ok gotcha, wanted to make sure since I hadn't reviewed that whole PR. Then let's just fix-up the title and description to include all follow-ups as one
Also btw, no need to quote reply if you're replying to the whole thing in order. Quoting is useful for replying to parts at a time or out of order comments. In this case they read fluidly down and so quoting actually reads duplicatively

@eduardodbr, any chance that you'd have a chance to fix/update this so it can go into 3.6?
We're currently missing the documentation on multiple schedules, which is in this PR.

Hi @Joibel will try to finish this ASAP, sorry for the delay

Looks like there's some test failures in CI


fixed addition code

Failing test:
======================================================================
ERROR: Tests contig generation on samples with preexisting alignment
Traceback (most recent call last):
File "/Users/gleb/Dropbox/Backup/Projects/churchlab/millstone/genome_designer/../genome_designer/main/tests/test_genome_finish.py", line 162, in test_generate_contigs_with_existing_alignment
perform_variant_calling=False, alignment_options={})
ValueError: too many values to unpack
-------------------- >> begin captured stdout << ---------------------
/Users/gleb/Dropbox/Backup/Projects/churchlab/millstone/genome_designer/conf/../temp_test_data/projects/4761c527/alignment_groups/abe98e6e/sample_alignments/87eeee95/bwa_align.error
START VARIANT CALLING PIPELINE
CHECK SAMPLES
START PIPELINE COMPLETION
--------------------- >> end captured stdout << ----------------------

Ran 2 tests in 26.289s
FAILED (errors=1)
Destroying test database for alias 'default'...
(venv)gleb@glebs-mbp.private.wireless.med.harvard.edu:~/Dropbox/Backup/Projects/churchlab/millstone/genome_designer$ ./scripts/run_unit_tests.sh main/tests/test_genome_finish.py

Yeah just need to catch an extra return value from call to run_pipeline() at offending line above.


Update test-summary/action to v2.1

Updated test-summary/action to version 2.1 so that the node.js 12 error message disappears.
closes #7

I updated the README consequently #11


next-use-posthog throws error when trying to build after upgrading posthog-js to 1.16.0

After upgrading toposthog-js to 1.16.0, next-use-posthog started throwing the error bellow and fails to build, thus deploying on Vercel.
Argument of type 'typeof import("/node_modules/next-use-posthog/node_modules/posthog-js/dist/module").default' is not assignable to parameter of type 'typeof import("/node_modules/posthog-js/dist/module").default'.
  Property 'group' is missing in type 'typeof import("/node_modules/next-use-posthog/node_modules/posthog-js/dist/module").default' but required in type 'typeof import("/node_modules/posthog-js/dist/module").default'.

 opt_out_capturing_by_default: true,
 loaded: (client) => {
       analytics.init(client)
                            ^
       askUserConsent()
     },
   })

Adding any like so analytics.init(client as any) fixes the issue and it builds. Could this be because next-use-posthog needs to upgrade posthog to latest version?.

You can now use the version 1.16.0 which comes with<EMAIL_ADDRESS>👍

You can now use the version 1.16.0 which comes with<EMAIL_ADDRESS>👍

I'm not sure what you mean. Does it means that I don't need next-use-posthog anymore? Does posthog-js has this hook?

Indeed, it does solve the problem. So does it means also that I don't need to install posthog-js since it's already included in next-use-posthog?
Thank you

That's correct @alveshelio :)


nixos/borgbackup: add an option to ignore warnings

borgbackup exit code 1 means warning, not error. For example if a file is modified during backup, borg create exits with code 1. It may be desirable to count that as success.
See also https://github.com/NixOS/nixpkgs/pull/201969 which does the same but by patching source code instead.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I think it might be easier to configure SuccessExitStatus= for the systemd service instead.

I think it might be easier to configure SuccessExitStatus= for the systemd service instead.

that would only work if the service consisted only of one borg invocation. With set -e, if borg create returns a warning and we exit, borg prune/compact are not run.


How to get  onloadStart  callback

How to get  onloadStart  callback
onLoadStart: (controller, url)  {
},

It has been resolved and modified as follows
Future handleMethod(MethodCall call) async {
// final arguments = call.arguments as String?;
print(
  'method1:${call.method} InlineWebviewMacOsController arguments:${call.arguments}',
);


Buttons are positioned incorrectly

using v2.3.3
   const dom = $(".medium-editor-element");
    let medium = new MediumEditor(dom);
    medium.setContent("hello world");

    $(dom).mediumInsert({
      editor: medium
    });

container (Bootstrap) was setting container to position relative

This is not a bug, it's a feature. There were always problems with positioning + button under an image and since + button is connected to the image, I moved it to the right bottom corner.


Implement stddev_samp and stddev_pop ppl stats function

Description
Implement stddev_samp and stddev_pop ppl stats function
Issues Resolved
https://github.com/opensearch-project/opensearch-spark/issues/483
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

hi
plz also run sbt scalafmtAll  for solving the failed CI / build

hi
plz also run sbt scalafmtAll  for solving the failed CI / build


SPARK-22531 Migrated IDF from MLLib to ML and removed use of MLLib ve…

…ctors in ML IDF
What changes were proposed in this pull request?
Migrated IDF functionality from MLLib to ML to avoid converting vectors from ML vectors to MLLib vectors and back.
How was this patch tested?
Changed tests to adapt to ML Vectors instead of old IDF MLLib model.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This issue was resolved in https://github.com/apache/spark/pull/24963, in which a batch of algs were modified.
So this pr & ticket can be closed?


build: fix branch to branches use release branch for version bump

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Extract last command typed in the session

I would like to have an option in the terminal.
With this option I can extract the last (success) commands typed in the terminal.

Are you hoping for something like command history? PowerShell supports command history by default.

Yes.
But made it general.
Can extract command history for a Linux distro (WSL), cmd, poweshell, azure cli.
Enviado desde Correohttps://go.microsoft.com/fwlink/?LinkId=550986 para Windows 10
De: Dustin L<EMAIL_ADDRESS>Enviado: jueves, 8 de octubre de 2020 05:25 p. m.
Para<EMAIL_ADDRESS>CC: Roberto<EMAIL_ADDRESS><EMAIL_ADDRESS>Asunto: Re: [microsoft/terminal] Extract last command typed in the session (#7867)
Are you hoping for something like command history? PowerShell supports command history by default.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/7867#issuecomment-705855220, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEFQUHUQJ6IVFPWK5II5NVLSJY35BANCNFSM4SJKTIYQ.

All of those products, except for CMD, can do this already. Terminal does not need to do any work here :smile:


Add global option for istio support

This adds a global option for istio.
If it is under istio environment by the global option, then new channels will be added by WLST when creating the domain.
Now this change applies to domain on pv only. If this solution is approved, then it will be applied to domian in image in the next step.

General questions:

Where is the detailed description of this change's intent?  (Can you update the description with JIRAs & wiki links?)
At one point I recall someone suggested using config overrides to add the ISTIO channels.  This change has the customer 'manually' adding them in the original configuration instead.   Why?

I've created a new branch from latest develop, merged the changes from this PR, resolved some conflicts, and then changed the top-level domain resource element to be "istio" instead of just a top-level boolean.  That PR is here: https://github.com/oracle/weblogic-kubernetes-operator/pull/1143.  Let's take the concerns here over to that PR.

I've merge the proposed configuration change from the istio-enablement branch to here and also merged latest develop.


Stancli user api

proposal for new programmatic interface to core Stan algorithms
link to rendered proposal:  https://github.com/stan-dev/design-docs/blob/stancli-user-api/designs/0034-stancli-api.md

This is very exciting!
A few general thoughts, right off the bat:

I tend to find it much easier to read/type command line arguments that --look-like-this (so called kebab-case) rather than --ones_with_underscores. In stanc3 we have deprecated any command line arguments with _ in favor of versions with - as the separator.
I understand the desire to avoid deeply nested and order-dependent argument parsing. I also think it is useful if we have exactly 1 level of nesting, e.g. the executable has subcommands (not prefixed with --) for very different purposes, similiar to tools like apt, git, etc. I think one level makes --help pages clearer and is useful for communicating what the different options are, rather than having a --help which lists both settings for HMC treedepth and how to get compiled model information (assuming something like ./mymodel info would be included).
"hmc", "optimize", "laplace", "variational", "eval-log-prob" seems like it is a mix of the names CmdStan currently has and of the specific algorithm names - is there a reason to not go full in and rename optimize as lbfgs and variational as advi?

And a couple questions:

Does cli11 support something like "take this JSON file and treat it as my config"? Especially for complicated configs it would be super useful. This is certainly optional though
Do you imagine this executable will be built in the same was as cmdstan executables (e.g. with make), or is that UI also getting another look?

I would like to see what the doc would look like for the command-line interface.
Question 1:  Is there going to be an executable compiled from a model?
Question 2:  Are there going to be subcommands corresponding to the operation?
Question 3: How are arguments specified?
I assume the answer to Q1 is yes, to Q2 is yes with one level of nesting, and that Q3 is up for grabs.  I can imagine that Q1 is no and you build a higher-level driver that also compiles the model.
Then a spec should look something like this standard command-line doc.  As an example, here's the head of the doc for git resulting from man git in the terminal.

       See gittutorial(7) to get started, then see giteveryday(7) for a useful minimum set of commands.
       The Git User’s Manual[1] has a more in-depth introduction.

       After you mastered the basic concepts, you can come back to this page to learn what commands Git
       offers. You can learn more about individual Git commands with "git help command". gitcli(7) manual
       page gives you an overview of the command-line command syntax.

       A formatted and hyperlinked copy of the latest Git documentation can be viewed at
       https://git.github.io/htmldocs/git.html or https://git-scm.com/docs.

OPTIONS
       -v, --version
           Prints the Git suite version that the git program came from.

           This option is internally converted to git version ... and accepts the same options as the
           git-version(1) command. If --help is also given, it takes precedence over --version.

       -h, --help
           Prints the synopsis and a list of the most commonly used commands. If the option --all or -a
           is given then all available commands are printed. If a Git command is named this option will
           bring up the manual page for that command.

           Other options are available to control how the manual page is displayed. See git-help(1) for
           more information, because git --help ... is converted internally into git help ....

So for us, that'd be something like the following, where nuts_diag_adapt picks out what is now specified with method = sample, algorithm = hmc, metric = diag_e, algorithm engine = nuts, and adapt engaged = true.
<model.exe> nuts_diag_adapt --step_init <real+> --metric_init <file> --max_depth <nat> --warmup_iter <nat> --sampling_iter <nat> --save_warmup <bool> --thin <nat> --adapt_gamma <real+> --adapt_delta <prob> --adapt_kappa <real+> --adapt_init_buffer <nat> --adapt_termn_buffer <nat> --adapt_window <nat> --sample_file = <file> --adapt_file = <file>

And of course, we need the ranges (nat is for "natural", which is 0, 1, ...) and default values in the longer doc.  And of course, I'm just guessing on things like sample file and adaptation file.  You may also need a specification for output in ASCII, JSON, or binary format.

command line arguments that --look-like-this (so called kebab-case)

I also prefer kebab case.  The only issue is that the corresponding Python variable, look_like_this, has to be in so-called bruschetta case.

cf https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
"Option names are typically one to three words long, with hyphens to separate words."


not validating the queue

when added producer configuration and trying to publish message from the ui it isn't validating the queue please help me to understand a way in validating the queue

I'm sorry but I am not sure what you mean by validating the queue - do you mean that you would like springwolf to validate the existence of a queue?

so can you clarify what should we give in the channel("<<here?>>") i'm giving queue name to which publisher is publishing
in that place if in case we don't have queue name can we take it with binding ?

I'm still nut sure I understand your question. I will close this for now.


Migrate to rofi with customization

Wofi is not enough for me, need to migrate to basic rofi with customization.
Needs:

running menu;
calculator;
power menu.

Configured.


Migration changes

Relative chages for migration.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage remained the same at 58.596%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/nexus/nexus.py
2
73.93%

pynxtools/dataconverter/readers/ellips/reader.py
5
87.59%

pynxtools/dataconverter/readers/ellips/mock.py
11
85.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4843

Relevant Lines:
8265

💛  - Coveralls


Vendor in case functions

Fixes

Fixes #2464 by @obulat
Description

Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@obulat CI is passing on the PR and the changes look good too, why is this a draft?

This looks fine, but should we also vendor the tests associated with these utilities to ensure functionality?

👍  I added the tests.