compilation fails for caffe opencl branch in CPU_ONLY mode

Compilation fails for caffe opencl branch in CPU_ONLY mode with error:
/home/daniil/CK-TOOLS/lib-caffe-bvlc-opencl-clblast-trunk-android-ndk-4.9.x-android21-arm-v7a-32/src/src/caffe/layers/softmax_layer.cpp:21:3: error: 'use_slm_' was not declared in this scope
   use_slm_ = (bottom[0]->shape(softmax_axis_) * inner_num_
   ^
make[2]: *** [src/caffe/CMakeFiles/caffe.dir/layers/softmax_layer.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/daniil/CK-TOOLS/lib-caffe-bvlc-opencl-clblast-trunk-android-ndk-4.9.x-android21-arm-v7a-32/obj'
make[1]: *** [src/caffe/CMakeFiles/caffe.dir/all] Error 2
make[1]: Leaving directory `/home/daniil/CK-TOOLS/lib-caffe-bvlc-opencl-clblast-trunk-android-ndk-4.9.x-android21-arm-v7a-32/obj'
make: *** [all] Error 2

I've fixed error  and keep same code for CPU_ONLY mode as for BVLC/caffe  master branch

Compilation works fine now but I've got problem at runtime:
      I0201 12:05:26.929121  6517 caffe.cpp:426] Performing Backward
      I0201 12:05:26.929172  6517 caffe.cpp:434] *** Benchmark begins ***
      I0201 12:05:26.929227  6517 caffe.cpp:435] Testing for 1 iterations.
      F0201 12:05:26.929330  6517 common.cpp:213] Cannot use GPU in CPU-only Caffe: check mode.
      *** Check failure stack trace: ***
      Aborted

also
/data/local/tmp/tmp/libOpenCL.so still required at runtime for CPU mode
I've tried to create two ck packages with reduced dependencies and turned off flags like GREEN_TEE
and can't see libOpenCL.so at compiled caffelib.so or caffe binaries:
daniil@daniil:~/CK-TOOLS/lib-caffe-bvlc-master-cpu-trunk-android-ndk-4.9.x-android21-arm-v7a-32/install/lib$ readelf -a libcaffe.so | grep NEED
  [ 7] .gnu.version_r    VERNEED         001ddd60 1ddd60 000040 00   A  3   2  4
 0x00000001 (NEEDED)                     Shared library: [libdl.so]
 0x00000001 (NEEDED)                     Shared library: [liblog.so]
 0x00000001 (NEEDED)                     Shared library: [libstdc++.so]
 0x00000001 (NEEDED)                     Shared library: [libm.so]
 0x00000001 (NEEDED)                     Shared library: [libc.so]
 0x6ffffffe (VERNEED)                    0x1ddd60
 0x6fffffff (VERNEEDNUM)                 2
daniil@daniil:~/CK-TOOLS/lib-caffe-bvlc-master-cpu-trunk-android-ndk-4.9.x-android21-arm-v7a-32/install/lib$ ls -l
total 19216
-rw-r--r-- 1 daniil daniil    75324 Feb  1 12:01 libcaffe_jni.so
-rw-r--r-- 1 daniil daniil 18494736 Feb  1 12:00 libcaffe.so
-rw-r--r-- 1 daniil daniil  1098310 Feb  1 11:59 libproto.a
daniil@daniil:~/CK-TOOLS/lib-caffe-bvlc-master-cpu-trunk-android-ndk-4.9.x-android21-arm-v7a-32/install/lib$
daniil@daniil:~/CK-TOOLS/lib-caffe-bvlc-master-cpu-trunk-android-ndk-4.9.x-android21-arm-v7a-32/install/bin$ readelf -a caffe | grep NEED
  [ 6] .gnu.version_r    VERNEED         00004a3c 004a3c 000020 00   A  3   1  4
 0x00000001 (NEEDED)                     Shared library: [libcaffe.so]
 0x00000001 (NEEDED)                     Shared library: [libdl.so]
 0x00000001 (NEEDED)                     Shared library: [liblog.so]
 0x00000001 (NEEDED)                     Shared library: [libstdc++.so]
 0x00000001 (NEEDED)                     Shared library: [libm.so]
 0x00000001 (NEEDED)                     Shared library: [libc.so]
 0x6ffffffe (VERNEED)                    0x4a3c
 0x6fffffff (VERNEEDNUM)

Steps to reproduce at branch issue-48

Compile new program

ck compile program:caffe-time-opencl-cpu --target_os=android21-arm-v7a --env.DISABLE_DEVICE_HOST_UNIFIED_MEMORY=ON --env.CPU_ONLY=ON

select new package

run new program

not it works without libOpenCL.so:
shell@trelte:/data/local/tmp/tmp $ ls -l *.so
-rw-rw-rw- shell    shell    18494736 2017-02-01 12:46 libcaffe.so

but still got error at run time:
      I0201 12:57:45.596982 13358 caffe.cpp:435] Testing for 1 iterations.
      F0201 12:57:45.597076 13358 common.cpp:213] Cannot use GPU in CPU-only Caffe: check mode.
      *** Check failure stack trace: ***

looks like one more hardcoded case at opencl original branch mode works only in gpu mode

Looks like it because of stub:
/caffe/include/caffe/util/device_alternate.hpp
used in CPU mode and fails for all *_gpu methods:
#define NO_GPU LOG(FATAL) << "Cannot use GPU in CPU-only Caffe: check mode."
...
void classname<Dtype>::Forward_gpu(const vector<Blob<Dtype>*>& bottom, \
    const vector<Blob<Dtype>*>& top) { NO_GPU; } \

@daniil: it's not a bug, it's a feature! :) You can't use any GPU run commands when you compile for the CPU only!

works fine now closing


ASTR i18n Notification Thread

This thread will push changes of astr-i18n project. Discussion or feedback should be continue in astr-i18n repo rather than this thread.
If you wanna contribute to the i18n project, please read the Code of Conduct.
If you wanna receive update notification on i18n project, please click the subscribe button in the right panel.
Thank you for your contribution!
Translator who contributed to the ASTR before:

zh_CN: @30000lightyears
en_US: @jaywyeee
ja_JP: @c-stella @momizi06
ko_KR: @178619

v1.9.2 Updates

Adding i18n keys for homepage.

v1.10 Updates

Adding i18n key for export warning. Key: eventpage.export.warning


classes aos-animate not being applied (NextJs)

I'm working with NextJs and the aos-init classes on my elements are applied and only the elements in view on load are properly animated. The rest of my elements do not get the aos-animate class applied on scroll. There seems to be some kind of interference with the scroll listeners. Help!
This is:

Bug

Specifications

AOS version:
OS: MacOS
Browser: Chrome

Expected Behavior
aos-animate class being applied on scroll
Actual Behavior
aos-animate class not being applied on scroll. Only on load on elements in the viewport.
Steps to Reproduce the Problem
N/A
Detailed Description

aos-init classes are being applied
aos-animate classes are only being applied on load to the elements in the viewport
aos-animate classes are not being applied on scroll

One solution I've tried so far is manually adding an event listener and triggering AOS.refresh() but the animation isn't smooth and does not work as well as how it should behave (also a very sketchy patch)
  useEffect(() => {
    AOS.init({
      duration: 700,
      delay: 50,
      once: true,
    })
    window.addEventListener('touchmove', () => {
      AOS.refresh()
    }, false)
  })

Thanks!

Did you solve your issue ? Could you help me set up AOS in next.js ?

Same issue

Same issue

Check my repo "Aos-implementation", check how I configured _app.js and how I am using aos in the sectionOne.js for example (In the component folder) for example. Working out of the box on Safari, Chrome, Firefox, DuckDuckGo.

Same issue

Check my repo "Aos-implementation", check how I configured _app.js and how I am using aos in the sectionOne.js for example (In the component folder) for example. Working out of the box on Safari, Chrome, Firefox, DuckDuckGo.
Here you can have a quick look to see that it's working, and animation gets reset every time you scroll back up :
aos-implementation-git-main.egamopi.vercel.app

Thanks @EgamoPi , It's Work successfully 🔥

Do we have any fix for this issue? anyone's reply will be helpful. Thank you!

  useEffect(() => {
		AOS.init({
			delay: 400,
			duration: 800,
		});
	});

Can anyone help me with this? I'm using NEXT js + AOS, facing the same issue. But animations are working on the latest browsers of Chrome, Firefox, and Safari. But for some old versions of the browser, elements in view on load are properly animated, the rest of my elements do not get the AOS animations and they get disappear. Only the elements which have no AOS animations are visible on the scroll

Hello @NitinHirve
Please make sure to set data-aos-duration and data-aos-delay attributes for every component.
Or you can just do this globally in _app.js file as I mentioned in my previous response above.

Hi @zeghmouri
I tried the below code in _app.js but still facing the same issue
 useEffect(() => {     Aos.init({delay:400 ,duration: 1300});   })

I have tried to apply it inside the nested component, which is not working :
the main class is not being added "aos-animate".

|---
            |-----
                        |----- when this comment everything is fine
                        |-----  (add here ) it's not working until I comment on the above component
               any reply and solution would be very grateful :
               PS: I am using react-router dom v-6 .


Replacing remaining strings by localization variables for localization

@jdpigeon do you think you could try building the app with these changes?

@jdpigeon I'll update the localization spreadsheet when I have a little time, so please don't merge yet!

Thanks!


Problem with IO::Socket::SSL

I had problem with SSL when i used SQLi Vulnerability Scanner ( both Common and Advanced)
I use Cmder on Windows 10
Can you help me ?
Thanks

Hi LuongPhuHoa!,
Sorry, i'm being inactive for months in GitHub. Can you provide some details of what Perl are you using and the version. Also, have you tried it again to see if the problem appear again ? I've tested that and no problem occured in my PC. This error may occurs in Windows OS because of the OS, not the code or the module. Thank you!

Hello
I'm using Active Perl 5.28.1.I have tried for many times but I still got that error.

Hmm, does the error disturb your scanning process ? Like the error stop the program from scanning the url (like onlyscan 5 from 10 urls because of the error force stop it), or it just show up and doesn't disturb the program ? If yes it doesn't disturb the program, just ignore it (it is known bug for threading system on some Windows OS). If no the error disturb the program, send the Results_Dork_q.txt file that you used on the screenshot above and the once more.

It disturbed my scanning process. It forced the program to stop
Results_Dork_q.txt
Here is the result file
I will try to use it on Strawberry Perl

Alright, the error stopped the scanning process. I got the point. I'll try to find a way to fix this. Report if you have tried it using Strawberry Perl.


Add ForestAdmin dashboard

Current version: https://app.forestadmin.com/JabRefOnline/Development/Operations/data/_prisma_migrations/index
Motivation: we need a simple admin interface to e.g. check what data is currently present in the database. At the moment, this is especially helpful to check our azure setup.
Docs: https://docs.forestadmin.com/beta-developer-guide-agents-v2/
Admin: https://app.forestadmin.com/JabRefOnline
Alternative considered: https://adminjs.co/, but this brings in all the react dependencies

Currently blocked by https://github.com/ForestAdmin/agent-nodejs/issues/398 and by https://github.com/ForestAdmin/agent-nodejs/issues/608.

Next step: fix https://github.com/tobiasdiez/nuxt-forestadmin/issues

Closing this for now, keeping track at https://github.com/JabRef/JabRefOnline/issues/1831


instead of calling out to touch, use Lwt_unix.openfile...

now, command (calling Sys.command) is only used for recursive remove

also see discussion https://github.com/mirage/mirage-fs-unix/pull/6#discussion_r18967824

:+1:


Ignore .DS_Store files in the bundle

What kind of change does this PR introduce? (check at least one)

[X] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[X] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[X] Yes
[ ] No

The PR fulfills these requirements:

[X] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[X] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

Other information:
Bundle includes .DS_Store files<EMAIL_ADDRESS>These files are macOS artifacts and clearly not intended to be included in the release modules.
The problem stems from how npm handles bare directories.  The files entry in package.json merely says "src".  The npm client includes all files in the src directory, including those in .gitignore.  The proposed fix tells NPM not to include .DS_Store files.
Fixes #10112

See https://github.com/vuejs/vue/issues/10112#issuecomment-511787278

With all due respect, your comment was from July 2019.  More than a year later, the most recent publish 2.6.12 still has the issue<EMAIL_ADDRESS>.  There's a nice dropdown on the unpkg page so you can look at older releases.  Every single 2.6.x publish is affected by the same issue.
The process you proposed is a manual step that hasn't been followed.  The fix is to tell NPM not to include those files.

I tried your fix locally and it doesn't remove the .DS_Store.

Start from scratch:
$ npm --version
6.14.8
$ node --version
v12.19.0
$ git clone https://github.com/vuejs/vue
...
$ cd vue

Now let's make the .DS_Store files that are on the publisher's computer:
$ touch src/.DS_Store src/platforms/.DS_Store

Normal run includes them in the bundle:
$ npm pack
$ tar -tzf vue-2.6.12.tgz | grep DS
package/src/.DS_Store
package/src/platforms/.DS_Store

Now let's apply my patch:
$ echo ".npmignore" >> src/.npmignore
$ echo ".DS_Store" >> src/.npmignore

Now let's try the bundle again:
$ npm pack
$ tar -tzf vue-2.6.12.tgz | grep DS | wc -l
       0

yes this PR work https://docs.npmjs.com/files/package.json#files


How to assign hive kerberos parameters in recipe-hive.yml

Describe the bug
Now hive-server provided kerberos mode to access,  there have 2 files such as krb5.conf and xxxxx.keytab，the Datahub-CLI version is v0.8.45,  recipe-hive.yml is like this:
source:
type: "hive"
config:
host_port: "localhost:10000"
options:
connect_args:
auth: KERBEROS
kerberos_service_name: hive
sink:
type: "datahub-rest"
config:
server: "http://localhost:8080"
when execute datahub --debug ingest -c recipe-hive.yml command, many errors occured on datahub-cli console like this:
TTransportException: Could not start SASL: b'Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server<EMAIL_ADDRESS>not found in Kerberos database)'
[2022-11-17 13:37:45,649] DEBUG    {datahub.entrypoints:198} - DataHub CLI version: 0.8.45 at /usr/local/lib/python3.8/site-packages/datahub/init.py
[2022-11-17 13:37:45,650] DEBUG    {datahub.entrypoints:201} - Python version: 3.8.15 (default, Nov 14 2022, 18:32:39)
My question is how to configure the krb5.conf and xxxxx.keytab manually for hive kerberos mode in recipe-hive.yml? thanks!

this issue is fixed by add machine to hdfs cluster

this issue is fixed by add machine to hdfs cluster

想具体问您一下 如果datahub在其他机器部署，要访问配置了kerberos的hive的数据，具体应该怎么做？
虽然看到文档写如下配置就可以：
options:
#  connect_args:
#    auth: KERBEROS
#    kerberos_service_name: hive
但是我配置了依然报错，如果不按照您说的把datahub的服务器添加到集群，那我应该怎么做？ 谢谢你


Support absolute path for DeviceVerificationUrl configuration

This is a suggestion related to the device flow.
I think it would be useful to be able to configure an absolute path for DeviceVerificationUrl in the UserInteractionOptions class.
The reason is that the value of the "verification_uri" property returned from the /connect/deviceauthorization endpoint, will in some cases not be a link the user can click or copy, but manually read from a monitor and written in a browser. This can be a bit tedious for the user, so it would be nice to be able to configure this to something a bit shorter and less cryptic than the Identity Server base URL and instead redirect to the Identity Server from that URL.
The current model for UserInteractionOptions seems to suggest that this should be possible based on this comment:
/// <summary>
/// Gets or sets the device verification URL.  If a local URL, the value must start with a leading slash.
/// </summary>slash.

With the current implementation of DeviceAuthorizationResponseGenerator, the DeviceVerificationUrl value is appended to the end of the Identity Server base URL regardless of whether it's a local or absolute path.
Do you have any thoughts on this?

The only advice I can find in the current version of the spec is:

The URI should be short and easy to remember as end users
will be asked to manually type it into their user-agent.

I remember there being a mention that the URL should also be trusted and recognised by the user, e.g. a domain the user recognises as owned by the IdP.
How were you thinking of shortening the URL? Would the user still be able to judge that it is legitimate?

Good question.
The idea was to shorten the URL to the minimum version that will still be recognized by the user.
In my case the Identity Server is hosted on sts..com, where .com is a website the user has already visited when registering the user.
The value of "verification_uri" will in this case be "https://sts.<domain>.com/device", where the final /device part is something I can configure.
Since the user might not know what https or sts is, it would be nice to be able to change this to just <domain>.com/device and redirect from there to the Identity Server instead, to make login as easy as possible.

Would you also use the same shortened domain for verification_uri_complete? Currently the IdentityServer base url and the registered device flow path are driving both values.
I think not displaying the URI scheme should be something handled by the client app, rather than in the protocol messages.

I think it makes sense to shorten the verification_uri_complete the same way. I can't think of a good use case where you would want to shorten the  verification_uri and display the verification_uri_complete with a different URL.
I agree that hiding the URI scheme should probably be handled by the client.

What's the status of this issue? @scottbrady91?

It's fixed by PR #3201

merged, thanks


vue create [project] fails with v3.0.0-beta.6 on linux (Ubuntu)

Version
3.0.0-beta.6
Reproduction link
https://github.com/vuejs/vue-cli/releases/tag/v3.0.0-beta.6
Steps to reproduce

npm install -g @vue/cli
vue create vue-test-cli3
Select default preset

After the line "Invoking generators..." I get the specified error.
What is expected?
Expected cli to create project
What is actually happening?
Receiving the error:
ERROR  Error: Cannot find module '@vue/cli-service/generator' from '/home/jim/dev/vue-test-cli3'
Error: Cannot find module '@vue/cli-service/generator' from '/home/jim/dev/vue-test-cli3'
at Function.module.exports [as sync] (/home/jim/.nvm/versions/node/v8.9.4/lib/node_modules/@vue/cli/node_modules/resolve/lib/sync.js:42:15)
at Object.keys.map.id (/home/jim/.nvm/versions/node/v8.9.4/lib/node_modules/@vue/cli/lib/Creator.js:265:30)
at Array.map ()
at Creator.resolvePlugins (/home/jim/.nvm/versions/node/v8.9.4/lib/node_modules/@vue/cli/lib/Creator.js:264:36)
at Creator.create (/home/jim/.nvm/versions/node/v8.9.4/lib/node_modules/@vue/cli/lib/Creator.js:137:26)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

Running Ubuntu 16.04, node 8.9.4, and npm v5.6.0.

FYI, I tried this on beta.5 and beta.1 and got the same results.

After rebooting my system this issue disappeared. Must have been an environment issue.  FYI, I use nvm to install node.


lua_equal expected in luv_check_handle

lua_equal expected here in luv_check_handle?

Could you explain what you mean.  I don't understand.

I think the question is asking why the handle's metatable is being indexed rather than checked for equality REGISTRY["uv_handle"][getmetatable(handle)] == true rather than getmetatable(handle) == REGISTRY["uv_handle"] The answer to this interpretation of the question is that there is more than one type of uv_handle. A bunch of different types with different methods and different metatables are all handles. To tag something as a handle, the metatable initialization code here stores every handle metatable as a key in REGISTRY["uv_handle"] with a value of true. Therefore, presumably every metatable for a type of uv_handle is a key in REGISTRY["uv_handle"] set to true but no other metatable is unless someone goes out of their way to break it, which would require either using the C API or the debug library.

It’s been inactive for too long, so it’s closed.


Fuzzy search.

I would add fuzzy search to Boost.Algorithm. First part is adding different cofficients(they are useful for developers).
Second part, that will be added later, will contain approximate search algorithms.

Current status - we have some implementations. But unfortunately now we are much slower than agrep


Proper handling of invalid traceparent header

Codecov Report

Merging #216 into master will increase coverage by 0.29%.
The diff coverage is 92.68%.

@@             Coverage Diff              @@
##             master     #216      +/-   ##
============================================
+ Coverage     73.19%   73.49%   +0.29%
- Complexity     1088     1098      +10
============================================
  Files           117      117
  Lines          4145     4165      +20
  Branches        403      409       +6
============================================
+ Hits           3034     3061      +27
+ Misses          915      907       -8
- Partials        196      197       +1

Impacted Files
Coverage Δ
Complexity Δ

.../co/elastic/apm/impl/transaction/TraceContext.java
92.3% <100%> (+5.35%)
30 <5> (+2)
:arrow_up:

...n/java/co/elastic/apm/impl/transaction/SpanId.java
87.5% <100%> (+0.83%)
13 <0> (ø)
:arrow_down:

...a/co/elastic/apm/impl/transaction/Transaction.java
79.48% <100%> (ø)
24 <0> (ø)
:arrow_down:

.../java/co/elastic/apm/impl/transaction/TraceId.java
77.77% <100%> (+1.3%)
14 <0> (ø)
:arrow_down:

...re/src/main/java/co/elastic/apm/util/HexUtils.java
91.17% <81.25%> (+13.39%)
18 <11> (+8)
:arrow_up:

...stic/apm/report/IntakeV1ReportingEventHandler.java
75.55% <0%> (+2.22%)
12% <0%> (ø)
:arrow_down:

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 9af11ba...f5c22ac. Read the comment docs.


how to get the vehicle to derive collision information

Dear Professor, during the training in intersection env, how to get the vehicle to derive collision information? Thanks!

Hi, (I am no professor,)
You can check whether the controlled vehicle has collided by checking:
env.vehicle.crashed


add intermediate states when install/update a helm chart

What would you like to be added:
example:
add a install-pending state after trigger a helm install
add a upgrade-pending state after trigger a helm upgrade
Why is this needed:

@DanielXLee  please  also include helm rollback

@huxiaoliang The current design don's support rollback like helm CLI rollback. We can use helm upgrade to rollback to an older version


[Feature] Enable NumberField to handle int Values

Describe the solution you'd like
The NumberField should be able to not only take double Values as Parameter, but also int Values. It should then also display them in an  int format and not as a double.
This enables Developers to also directly pass int Values withouth casting from String/int to double and enables them to easily display int Values and ensure safety without providing an extra Validation to check if the Value contains String elements.

After testing, this has been implemented as planned. The component should only work with doubles. The following #835 improves the component’s logic to detect when a number can be displayed as an integer and display it correctly.
NumberField numberField = new NumberField("Enter a number");
numberField.setValue(100.0);


watchEffect within a Setup Store is stopped unexpectedly

Reproduction
https://stackblitz.com/edit/github-u4jlt8
Steps to reproduce the bug

Click "Negate store.flag" buttonn any times you like. You will see how store.flag negates, ang how its computed store.negated stays reactive.
Uncheck "Show StoreUser" input. The component will be unmounted.
Check it again, to mount the component back.
Click "Negate" button again - store.negated is not reactive anymore.

https://user-images.githubusercontent.com/43530070/206888917-94ba28ba-6507-4bfd-a034-1d9e744de4fc.mov
Expected behavior
I expected the watchEffect(), called within a Setup Store, to be active as long as the store's scope is active. It makes possible for utilities like computedEager() just work in setup stores.
Actual behavior
The watch effect seems to bind not to the store's setup scope, but to the component where the initial useStore invocation happened. Thus, when the component is unmounted, the watch effect is cleared and stopped, leaving the store in a broken and hard-to-debug state.
Additional information
No response

Created https://github.com/vuejs/core/issues/7319 to track it


How to Send push notification To Topics ?

Please can you give an exemple how to send a push notification To Topics ?

You can use tag property

Hi @twsjozef did that solve your issue?

Hi @chrisbjr  , Realy i didint try it , i changed it with a simple curl request

@twsjozef show me the curl request, I'm sure you can convert that into a notification

Hi @twsjozef will close this now.


adding guide for function parameters (both declaring and calling)

Thanks for cleaning this up. Looks good to me.


accountInfo.result might be null

18:35:46.546 [default] [pool-2-thread-1] TRACE si.mazi.rescu.HttpTemplate - Http call returned 200; response body:
{"frozen_btc_display":"0.0000","total":"0.00","loan_ltc_display":"0.0000","net_asset":"0.00","loan_cny_display":"0.00","available_ltc_display":"0.0000","loan_btc_display":"0.0000","frozen_ltc_display":"0.0000","available_cny_display":"0.00","frozen_cny_display":"0.00","available_btc_display":"0.0000"}
18:35:46.582 [default] [pool-2-thread-1] ERROR DETAIL_APPENDER - 查询账户信息异常: java.lang.NullPointerException: null
at com.xeiam.xchange.huobi.service.polling.HuobiAccountServiceRaw.getHuobiAccountInfo(HuobiAccountServiceRaw.java:24) ~[xchange-bitvc-3.0.0-SNAPSHOT.jar:na]
at com.xeiam.xchange.huobi.service.polling.HuobiAccountService.getAccountInfo(HuobiAccountService.java:26) ~[xchange-bitvc-3.0.0-SNAPSHOT.jar:na]
as above ,accountInfo.getResult() might be null.

Someone really needs to put some effort into completing the BitVC/Huobi implementation. There are no unit tests or example classes. Whoever made it, just slapped something quickly together. That's helpful, but to make it really robust, someone needs to add samples json responses, unit tests, and example classes.
See: https://github.com/timmolter/XChange/wiki/New-Implementation-Best-Practices

@timmolter I am the guilty :) I am using the implementation heavily and it works very well though, including borrowing, switching between Huobi providers etc. I will look into adding unit tests / json responses.
@DISSIDIA-986 @timmolter this should have been fixed with https://github.com/timmolter/XChange/pull/822 which I can't see represented in 3.0.0 for some reason?

@jheusser 3.0.0 has that patched code in issue #822. The problem reported above is that there is no result json field, hence the result field in HuobiAccountInfo is null, leading to if (accountInfo.getResult()... throwing a NPE. It's weird though that in his posted JSON, everything is 0 (zero). So there might be a different problem there.
Would you be willing to push some redacted json as a basis for unit tests? If you do that, I can make the unit tests.

@timmolter  @jheusser  The account is new created,so everything is 0.

@timmolter yes I will provide that, hopefully this weekend. I plan on improving the implementation anyway and include all of Huobi's exchanges (BitYes has the same API as well).

@jheusser Awesome. What's the deal with Huobi and BitVC? It looks like they are both crammed into the bitvc module? The only thing they share are the DTOs and the adapter class, right? Perhaps we should create two modules and have the bitvc one depend on the huobi one? What do you think?

@timmolter BitVc and Huobi are the same company. BitVc is basically the margin trading side of Huobi, you can execute trades on BitVc on Huobis market data. So it really is a combination of the two sites, the market data you get from Huobi, and trading / account information comes from BitVc.
As their the APIs are 95% identical (everything except some account info fields) it makes no sense to copy&paste the entire code base twice (or actually three times now with BitYes, which is the same except for USD), and fix bugs / changes and keep the two repos in sync.
Perhaps it would make more sense if everything went under the name "Huobi" (just like the company) and you select which implementation you want to use through an exchange specific parameter, either Huobi (market data and trading), BitVc (huobi market data and bitvc trading)?

Yeah, kinda like the Use_Intl flag in OKCoin (IIRC). Putting it all under Huobi like you suggested meks a lot of sense.

Lots of changes since then, closing this for now.


Persist AuthData to resubmit after "pending" response

See https://github.com/stellar/stellar-protocol/pull/124

@bartekn In this case, if transaction is sent again, is there any changes to the 'nonce' field?

@bartekn In this case, if transaction is sent again, is there any changes to the 'nonce' field?

No, when sending the request again (for pending responses) it should send exactly the same auth data, including nonce.

@bartekn What is RequestID here? Is this the unique payment ID passed by the user?

Exactly, it's id parameter from request to the Bridge server.


Avro 1.9.0-SNAPSHOT, with jsr310 enabled

JSR310 is enabled in this initial commit. TODO add configuration to
default to the Avro default, but allow enabling JSR310 or JODA
explicitly.
Fixes #69

Thank you for bringing this to my attention, and the pull request.  This is good work in the the right direction.  I've left some initial comments, and will do a more detailed pass to review the failing tests in the next few days.

Thanks for your review. I'll take a look early this week.

Great work.  If avro-1.9.0 were released, I'd merge this to master now.  As it is, we can either leave it as-is, or merge to an avro-1.9 branch of the commercehub-oss repo; whichever you'd prefer.

Great work. If avro-1.9.0 were released, I'd merge this to master now. As it is, we can either leave it as-is, or merge to an avro-1.9 branch of the commercehub-oss repo; whichever you'd prefer.

Leaving it as-is is fine for me, but if you want to "publicize" the changes by bringing them into your repo, that works for me too.

Let's leave it as-is for now.  If you notice that 1.9.0 is released before I do, please ping me.

I added a fixup commit for some docs -- I'll rebase once you've reviewed that.
I'll hold off on the removal of setValidateDefaults until we have some more info from upstream.

I added a fixup commit for some docs -- I'll rebase once you've reviewed that.

Docs changes look good.

Docs changes rebased. Removal of validateDefaults option also added as a new commit, in the assumption we'll hear what we expect to hear from upstream. If not, we can just remove that commit.

@davidmc24 Avro has issued a 1.9 release candidate. I added a couple of commits -- the first fixes some code style violations, and the second runs the code against the RC.

@rocketraman Thanks for the update. Changes look good.  It's exciting that 1.9 is getting closer to release.

@rocketraman or @davidmc24.
Thanks for this hard work, any chance to have this merge and publish ?
Starting a new project with avro and I really want to use jsr310 instead of Joda.
Or is there any way to use it before the release ?

@tchiotludo Building a local version of this plugin and using it is not difficult. However if you can wait a week or so I suspect avro 1.9 will be released officially and then this branch can be merged.

I've try but I'm stuck with this exception :
Caused by: java.lang.ClassNotFoundException: org.apache.avro.compiler.specific.SpecificCompiler$DateTimeLogicalTypeImplementation
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	... 182 more

Seems that gradle can't load the avro 1.9.0 but I've check and seems to be the good one in my dependencies :
buildscript {
    ext {
        avroVersion = "1.9.0"
    }
}
    repositories {
        // ...
        // @TODO: temporary for avro 1.9
        maven { url "https://repository.apache.org/content/groups/staging/" }
    }

dependencies {
    compile group: "org.apache.avro", name: "avro", version: avroVersion
}

Avro 1.9 has been released. I'll make the final updates to this pull request over the next few days!

@rocketraman Awesome.  Ping me when you're ready for a final review, and we'll get this merged and released.

Ready to go!

Looks great, merging!


Telepath - give form widget adapters a mechanism for obtaining bound widgets for existing form elements

Part of the "Auto-save support refactorings with Telepath" roadmap item for Wagtail 6.0.
Wagtail uses the Telepath library to provide client-side counterparts for Django form widget objects, with an API as documented at https://docs.wagtail.org/en/stable/reference/streamfield/widget_api.html. Currently, this allows for creating new instances of a widget, and retaining a 'bound widget' handle for reading and writing the widget's state. This works well within StreamField, where all widgets are constructed in JS on page load. However, there is no mechanism for obtaining a bound widget object for a widget that is already part of the page. This would allow the same kind of client-side access to form widgets that are a direct part of a Django form and are thus rendered in the document HTML up-front.
I propose that the API for form widget Telepath adapters is extended to include a getById(id) method, that takes an HTML ID and returns the bound widget for the form field with that ID. Repeated calls on the same ID should return the same object.
The ChooserFactory base class in src/components/ChooserWidget/index.js already implements a superset of the widget API including this method - since choosers always set up a JS object for the widget's own functionality, and this JS object complies with our form widget API, we can just stash a reference to that JS object on the HTML element. For other form widgets that aren't inherently JS-powered, we can do the same thing but 'lazily' - creating the bound widget object on the first call to getById, and stashing it on the HTML element for future accesses.

Just adding some thoughts here, we will need to consider the implications for non-core Wagtail widgets that are instantiated by other means.
I also think that over-reliance on form elements having an id will add a bit more complexity to HTML generated throughout the forms system.
Why not rely on the https://developer.mozilla.org/en-US/docs/Web/API/FormData serialisation mechanism more? This provides a browser built in way to manage (even binary) data as it changes through an entire form object.
We could even leverage the built in browser validation system to maybe help manage things like timed updates to the forms & rethink a bit about how we are enabling custom error messages. https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/reportValidity  & https://developer.mozilla.org/en-US/docs/Web/HTML/Constraint_validation - this provides a mechanism to manage advanced validation in JS/DOM.
The nice thing about leaning in on Browser APIs is that we have to think less about management of custom code and we are working with objects that are essentially the same that get sent to the server on POST.
I may not have all the context though I just know that having to map things to ids causes a lot of wrangling in our current code.


Regenerate when config has been changed

When the rsspls configuration file is changed, the feed is not always regenerated. For the rss to be regenerated, the website needs to have changed. Or you can delete the site's cache file. When I started using rsspls I struggled a bit with this.
While developing a feed config, it would be nice when the config changes, the feed is also regenerated. A simple strategy to do this is just to look at the last changed date of the config file. The problem with this is all sites would be regenerated, even when config and content of the site didn't change.
A beter approach would be to calculate a checksum of the feed-config (or better: only the selectors), and save the config-checksum to the feed's cache file. And when the checksum has changed between fetches, force fetch the sites HTML.
After developmen t, when the sites config are stable, this functionality wouldn't be used, but calculating a checksum, comparing and storing it wouldn't be very expensive operations.
Anyways, love to hear what you think, and if this is a good idea.

Yes I've run into this too, definitely needs addressing. Adding a checksum of the config into the cache seems like a reasonable approach.


Add metrics for bull

Add metrics
Update moleculer to 0.13.12
Fix code by eslint

Pull Request Test Coverage Report for Build 341

17 of 45 (37.78%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-9.8%) to 86.866%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/moleculer-bull/src/index.js
17
45
37.78%

Totals

Change from base Build 340:
-9.8%

Covered Lines:
221

Relevant Lines:
249

💛  - Coveralls


Failed to open TCP connection on 9090 port with motor-admin-rails gem

Hi @nickjj !
Thanks for all your work! I already use your repository for some of my personal projects. Recently, I wanted to create a project to use the motor-admin-rails gem.
I followed their doc and yours to install the gem:

add to Gemfile
./run rails g motor:install
./run rails db:setup

On startup I get this log from the web service which confirms the installation of the gem:
web-1 | ⚡ Motor::Admin is starting under /motor_admin (the gem has been installed)

But when I want to access the page linked to the gem, I get this error:
web-1 | I, [2024-05-29T15:56:05.269178 #15] INFO -- : Started GET “/motor_admin/assets/main-3b866105d1b5846018e0.css” for <IP_ADDRESS> at 2024-05-29 15:56:05 +0000
web-1 | E, [2024-05-29T15:56:05.285530 #15] ERROR -- :
web-1 | Errno::EADDRNOTAVAIL (Failed to open TCP connection to localhost:9090 (Cannot assign requested address - connect(2) for “localhost” port 9090)):

I've already tested these modifications but nothing changes:
Dockerfile:78 EXPOSE 9090
docker-compose.yml:89 - "9090:9090"
Do you know how to allow a connection to port 9090 (for the motor-admin-rails gem) while keeping the connection to port 8000 for the standard rails application?

Hi,
I haven't used that gem but their docs mention you can add mount Motor::Admin => '/admin' to your routes. This project does something similar with Sidekiq in the sense I'm guessing you'd be able to access http://localhost:8000/admin then.
I looked at motor admin's README and there's no reference to 9090 anywhere. Is it expected that you run a dedicated process? If so then you can make a separate Docker Compose service for that using the same Docker image as Puma and Sidekiq.

docker-compose.yml:89 - "9090:9090"

That would make it available but only if there's a running a process using port 9090 in the container. That wouldn't be the case here since this project runs Puma on port 8000 by default unless you changed the Dockerfile to use a process manager and are running both Puma plus whatever motor's process is.

Thank you for your fast response!
I hadn't modified the basic Dockerfile...
In the end, the solution proposed by motor-admin doesn't really fit my needs.
All the best and thanks again for your work!

Both 😅
I had the error by mounting and trying to access the route. I gave up on the gem.


HTTPS/SSL fix

Well it seems that soundcloud has switched their api stream to https, which broke the http download thread. So I switched the HTTP stuff to HTTPS.

Looks good to me, but I wonder how others are able to use it these days then? @petems

Both seem to work, I've tried using this PR cherry-picked and the HTTPS stream works also, seems like a good PR to merge! 👍


Update README.md

Credits weren't up to date
"Installation" paragraph because it may not be as obvious to everyone as it is to us who are used to schematics

Fixme: We should have that upaste link not be external to the github but I don't know how to do that without creating a new file.
I think there's a way to add blobs ?

And while you're at it, you should also update the repository description to match the README, e.g. "Schematic files for modded Minecraft that can be used with Schemetica and WorldEdit."

We can add a link to a gist for the config? Or do it on a wiki?
I'll update the Description. Thanks for the help ^_^

I have added the cfg file as "additonal file" in release section, that could work?
https://github.com/eddoww/modded-schematics/releases/download/v1.2/schematica.cfg


Test when to make parent paths when writing files

Alaska Airlines Pull Request
Before Submitting this pull request:

Link all tickets in this repository related to this PR in the Development section
note: all pull requests require at least one linked ticket
If this PR is Ready For Review, all ticket's linked under Development must have their status changed to Ready For Review as well
Closes #92

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I have performed a self-review of my own update.
Summary by Sourcery
Ensure directories are created recursively when writing files and add a test to verify this behavior.
Bug Fixes:

Ensure directories are created recursively when writing files to prevent errors if the parent directory does not exist.

Tests:

Add a test to verify that directories are created if they do not exist when writing a file.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ensure stop & restart timeouts apply to Excon timeout

Previously if a very long timeout was specified for a container, the HTTP request would likely time out before Docker responded. This ensures that the Docker timeout is hit before the HTTP request timeout configured in Excon

Note I have also cherry-picked a7129c5 from a previous fork which allows custom options to be passed in attached.  I don't see any downside to this option being included, but happy to omit that commit as it certainly is not entirely related to this PR

PS. I see the test are failing.  I ran the related tests locally and they all passed so I believe the failures are unrelated to this PR.

can you rebase to get a green build ?

/fyi @tlunter

Rebased, ok?

BTW. The failure in CI seems to be unrelated, not failures in the CI suite, see https://travis-ci.org/swipely/docker-api/jobs/161045152


Scroll every page

I can`t scroll every page of pdf view. Scroll happens directly and it sounds bad...

Can you please post a code snippet so we can try to see what's going wrong?

@CrisBarreiro Older versions of this lib it was possible scroll pages one per time, now page scroll is continuous. Did you understand? I would like to scroll page per page, but I can't

There is no such possibility in version 2.x, you can use 1.x

It would be really nice to swipe to the next page instead of going through multiple pages with one swipe

can you make a method to make the new version implement one page scroll per swipe?

Can you at least give us an hint on how to do it ?


docs(gpio-example): restrict the architectures on which this example runs

Description

This fixes the nightly CI builds.
Issues/PRs references

Open Questions

Change checklist

[x] I have cleaned up my commit history and squashed fixup commits.
[x] I have followed the Coding Conventions.
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.

Lgtm!


Python: do not add user site directory to PYTHONPATH

Issue description
By default Python adds the user site-directory to PYTHONPATH. We should prevent it from doing this in our applications to prevent (bugs due to) impurities.

https://docs.python.org/3.6/library/site.html
https://www.python.org/dev/peps/pep-0370/

-s     : don't add user site directory to sys.path; also PYTHONNOUSERSITE

I didn't find this bug because I looked in the wrong place, so I went and created https://github.com/NixOS/nix/issues/1497, which I've now closed. I'm pasting the text from that issue here because it fleshes out this issue somewhat.
Setup
I'm using nix as a package manager on top of Ubuntu. This problem may also exist on NixOS, I don't know. To trigger the bug we need a system python install with pip and the same python version in nix. I'll use 3.5 in this example, so make sure Python 3.5 is installed with whatever package manager the OS uses, for example:
sudo apt-get install python3.5

We also need to make sure that the directory containing user-installed packages exist. I'm using lxml to illustrate a particular problem with this bug, but any package can be used. I'm also using python3.5 -m pip to make certain I'm using the right pip.
 python3.5 -m pip install --user --upgrade lxml

It may be possible to use a nix-shell with pip to achieve the same effect, but I haven't tested this.
Reproduce bug
Again, any python package may be used, but I'm using BeautifulSoup4 as an example. It's important that the python version matches the one used in the setup.
nix-shell --pure -p pkgs.python35Packages.beautifulsoup4 --run \
"python -c 'import sys; print(*sys.path, sep=\"\\n\")'" | grep ".local"

Expected behaviour
No output.
Observed behaviour
Output like this:
/home/username/.local/lib/python3.5/site-packages

Consequences
All the packages the user has ever installed with pip install --user (and their dependencies) are importable in the pure nix environment, which is not expected behavior.
Fortunately, the nix-provided python packages override the user-installed packages, so the explicit dependencies of any nix package always have the correct versions.
Unfortunately, there are several packages whose behaviour depends on what packages are available for import. For example, BeautifulSoup has a prioritized list of html parsers and uses the best of those that are importable. So the expected behaviour -- that a script will run the same way no matter the environment if run in a pure nix shell -- is wrong. Instead, the script runs differently depending on what modules the user has installed using pip install --user.
This is not a special case. A quick search through the installed python modules on my PC show that import statements inside try clauses are very common in python code, so the real-life effect of having lots of unexpected packages available for import is almost certainly considerable.
Temporary workaround
A workaround until this is fixed is to use the -s switch to python:
$ nix-shell --pure -p pkgs.python35Packages.beautifulsoup4 --run \
> "python -s -c 'import sys; print(*sys.path, sep=\"\\n\")'" | grep ".local"
$

Mitigation
PEP 370 describes the mechanism used to insert the path to the user-installed packages into sys.path, so a solution would involve one of the options presented in that document, for example setting ENABLE_USER_SITE to False in site.py, or setting the PYTHONNOUSERSITE environment variable.

@stxlvt yes, we need to update our wrappers and python.buildEnv to set PYTHONNOUSERSITE. This will have to go in before 17.09.


Module version mismatch: Expected 44, got 43.

I need help in running the demo
I followed the instructions on https://github.com/jaruba/node-vlcPlayer-demo

git clone https://github.com/jaruba/node-vlcPlayer-demo.git
cd node-vlcPlayer-demo
npm install
installed electron via "npm install electron-prebuilt --save-dev" . My electron version inside node_modules is "v0.29.2"
took the vlc lib zip created by RSATom from https://github.com/jaruba/node-vlcPlayer-demo/issues/1#issuecomment-113905284 and placed it next to WebChimera.js.node

I get the following error
/Users/***/code/node-vlcPlayer-demo/node_modules/wcjs-player/node_modules…s-renderer/node_modules/webchimera.js/node_modules/bindings/bindings.js:83 Uncaught Error: Module version mismatch. Expected 44, got 43.
What step should i check?

use this https://github.com/RSATom/WebChimera.js/blob/master/build_electron.sh to build

Building with the build_electron.sh throws the following
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
LIBVLC_LIBRARY
linked by target "libvlc_wrapper" in directory /Users/**/code/node-vlcPlayer-demo/node_modules/wcjs-player/node_modules/wcjs-renderer/node_modules/webchimera.js/deps/libvlc_wrapper
-- Configuring incomplete, errors occurred!
See also "/Users//code/node-vlcPlayer-demo/node_modules/wcjs-player/node_modules/wcjs-renderer/node_modules/webchimera.js/build/CMakeFiles/CMakeOutput.log".
ERR! OMG Process terminated: 1
Unhandled rejection Error: Process terminated: 1
at ChildProcess. (/Users//code/node-vlcPlayer-demo/node_modules/wcjs-player/node_modules/wcjs-renderer/node_modules/webchimera.js/node_modules/cmake-js/lib/cMake.js:366:28)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
Should i point LIBVLC_LIBRARY to the unzipped libvlc that i downloaded from issue#1

You should install VLC.app before build to /Applications

Works. I removed vlc.app while debugging. Hoping to narrow down the issue. Adding VLC 2.2.1 into applications solved the issue.
Thanks RSATom

I'm glad to hear you got it working.

Hi guy:
I have some problems on the platform of win32 .
The code project  is  in my mac . I  pack a electron.exe ,  then run it on windows .
export WCJS_RUNTIME="electron"
export WCJS_RUNTIME_VERSION="v1.4.13"
export WCJS_VERSION="v0.2.7"
export WCJS_ARCH="x64"     //  ia32 is not work, will have a error "!% is not a valid Win32 application"
export WCJS_PLATFORM="win"

electron : v1.4.13
platform : win32   (console.log(process.platform))

A week ago , I have the same problem on the platform of macOS  , but I solved according to your answer  .
export npm_config_wcjs_runtime="electron"
export npm_config_wcjs_runtime_version="1.4.13"
npm install

I also try this methods , but not work .
Can you help me ?  thank you.   @RSATom

Are you sure use Electron v1.4.13?

Yes 。
npm uninstall electron
npm install electron v1.4.13

check it with electron --version

oh , sorry , it show v1.6.2
but I install v1.4.13 ,it is why ?

Don't know. I've forced binaries rebuild for latest electron version. It will be available soon.

ok, I will try again .

error
I set up a new project  on platform OSX,  use command
export WCJS_RUNTIME="electron"
export WCJS_RUNTIME_VERSION="v1.4.13"
export WCJS_VERSION="v0.2.7"
export WCJS_ARCH="x64"

It will download  WebChimera.js_v0.2.7_electron_v1.4.13_VLC_v2.2.4_x64_osx.tar.gz ,  and the electron version is v1.4.13
It's show error Node.js version 50 and 53 are against .
correct
After many attempts ， I found the  difference between two project . use commond
export WCJS_RUNTIME="electron"
export WCJS_RUNTIME_VERSION="latest"   ## changed
export WCJS_VERSION="latest"           ## changed
export WCJS_ARCH="x64"

It will download  WebChimera.js_v0.2.7_electron_v1.4.3_VLC_v2.2.4_x64_osx.tar.gz ,  and the electron version is v1.4.13  .
It's work !
question
But only work on platform OSX .
The same commond , just change WCJS-PLATFORM="win", can't work on windows .

wcjs-prebuilt is not mine project, and I don't know internals. It's possible some bug there. Don't know.


Thumbnail missing in android notification

🐛 Bug Report
Great work!

Expected behavior
In android, the thumbnail (icon or album art) of the audio file played is not shown in the notification.

Reproduction steps
Sorry, I don't have the time to write a full demo project for this bug. I am providing the snippet below I am using. The API I am using is here.
var mediaItems = (await nextTracks
                    .Select(x => new FileInfo(this.cacheService.GetCacheFilePath(x.Url)))
                    .CreateMediaItems())
                    .ToList();

await this.mediaManager.Play(mediaItems);

Looking into this repository, I see that the parsing for the thumbnail is not correct. In this line below each provider is parsed and then overwritten. So whichever is the last successful provider will be the metadata used. The sample audio file to test this behavior is here.
https://github.com/martijn00/XamarinMediaManager/blob/7ec7d505d3950c8cbabc60e7431b3e67a6943420/MediaManager/Media/MediaExtractorBase.cs#L152-L161
Also on another note, an optional feature to dismiss the notification and audio playback with a swipe or at least a stop button for dismissal would be nice to have with the default behavior.
Configuration
Version: 0.8.8
Platform:

[ ] :iphone: iOS
[X] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[ ] :tv: tvOS
[ ] :monkey: Xamarin.Forms

Can you test 0.8.9? There are several fixes around this.
The feature to dismiss the notification and audio playback with a swipe or at least a stop button: this already exists. If it doesn't show you might have disabled it in the Notification manager, or your device software doesn't support it.

Thanks! It is fixed in the latest version.
The swipe feature works for other apps like outlook, so the device does support it. I couldn't find any specific setting that would prevent swipe to dismiss. I have a Galaxy S7 installed with Android 8.0 API 26.
I am closing this since the issue is resolved.

I see that we are setting PlayerNotificationManager.SetOngoing(true) in MediaBrowserService. My understanding is that SetOnGoing(true) will disable swipe to dismiss as answered in SO here.
https://github.com/martijn00/XamarinMediaManager/blob/develop/MediaManager/Platforms/Android/MediaSession/MediaBrowserService.cs#L135

If you pause it is set to false: https://github.com/martijn00/XamarinMediaManager/blob/develop/MediaManager/Platforms/Android/MediaSession/MediaBrowserService.cs#L81
You have access to change it too: https://github.com/martijn00/XamarinMediaManager/blob/develop/MediaManager/Platforms/Android/Notifications/NotificationManager.cs#L16

Thanks! The second link is what I needed.


Updated header in app.py

Changed the layout of the header so it's more responsive across multiple screen sizes.  Also added a bootstrap logo for branding sake :D

Hi @Spyhuntr
Thanks for the pull request - your changes are a huge improvement to the app design.  And it looks so much better on a smaller screen!
A couple minor comments:

Let's use a Plotly logo rather than Bootstrap, since this project uses components from other libraries as well.
Looks like there's room to put "Example Index" in the nav bar in the small screens rather than DEI

I'm looking forward to seeing your ideas on how to jazz up the "Welcome to the Dash Example Index" box too, if you are up for more design contributions.

Made the changes from the comments.

Thanks the the contribution  :woman_dancing:


add "Compile a C library while setting custom defines" example

Use cc crate to compile a C library from a build.rs file while setting custom defines/CFLAGS.
Please note that it will be important to mention that this is a build time crate.
Most likely we will dedicate a separate (last) chapter like "build_time.md"
cc https://github.com/rust-lang-nursery/rust-cookbook/issues/236

I can take a look at this one


[BUG] Array field create table and insert issue

Mage version
0.9.68
Describe the bug
Issue 1
Insert statement in iceberg connector does not work with array field while @wangxiaoyou1993  already fixed delta lake connector. So we need to replicate the same changes for iceberg too.
Issue 2
While the array field works because of fix done by @wangxiaoyou1993 now but create table statement with both delta lake and iceberg connectors does not still work for array field when value is null. I caught this issue during temp table creation. I think we should still cast null as array(null) too.
To reproduce

Create delta lake or iceberg connector in trini
Create an array field in a table in source Postgres
Ensure array field is null
Run data integration pipeline

Expected behavior
It should create the table and insert data
Screenshots
No response
Operating system
No response
Additional context
No response

Issue fixed


Display tags (params, returns...) along with method documentation

[x] All compiled assets are included

I tried something to solve #1262
Also renamed some 'class' tags to 'className' as recommended by React
Also, this is my first contribution. Feel free to amend & comment.
Preview:

Hi. Thanks for creating the pull request! I have a few suggestions, which I will outline shortly as diff comments, but a couple I do have to note here.
Atom-TypeScript can work without atom-ide-ui also, in which case it needs to use builtin tooltips. The code for those is in lib/main/atom/tooltips/tooltipView.tsx, particularly in the tooltipContents method. Do you suppose you could do pretty much the same there? Yes, I know, a bit of code duplication is happening here. If you'd like to avoid that, feel free to re-use TSDatatipProvider, or factor out the common code.
The reason for using class is in part historical, but the crux of the matter is: we're not actually using React, and in etch class and className are in fact synonyms. So for the sake of consistency, I would request you to use class actually. It's probably a reasonable idea to switch to className at some point, but we should do that on the whole code base at once, and that probably should be a separate PR.

Hi ! Thank you for your comments. Be sure I'll add commits to my PR accordingly as soon as I can (probably early next week).
About moving class into className tags, I totally understand the benefits of a dedicated PR. I'll revert these modifications. It's just that an error popped in the console everytime I tested the tooltips, so I thought that it'd be a good idea to fix it while I was at it.

an error popped in the console everytime I tested the tooltips

Unless you're using some React-specific plugins, it really shouldn't have... I mean, etch doesn't complain about class at all. So I'm not entirely sure what you're referring to.

Okay I pushed some more commits, and now the two tooltips are displaying correctly.

I only managed to factor out the code for the two tooltip renderers by passing the etch instance to the builder method. I assume that's because the one in TSDatatipProvider is kinda mocked or overriden ?  Let me know if I did, haha.
Concerning the error I mentioned the other day, here it is. It pops everytime I make a tooltip appear (even if I checkout to master).

I just realized that I made a little regression on the first tooltip (I made the signature method disappear). I'll fix that along with the modifications you may suggest, hence the WIP status on the PR.
Cheers !

I only managed to factor out the code for the two tooltip renderers by passing the etch instance to the builder method

Yeah, I kinda forgot about this quirk. So here's the thing: we use etch, and atom-ide uses React. Atom-ide accepts either markdown, which doesn't work for us, or React components. But we don't really want to depend on React directly (it's big and heavy), and we still want to use etch. Hence, a minimal React JSX constructor is mocked in lines 7-26 of datatipProvider.tsx. That is also why you're seeing the error thing -- sorry I didn't realize this sooner.

Concerning the error I mentioned the other day

Yeah... It only pops up in Atom's dev-mode, which I rarely use, so it went unnoticed for a while. Honestly, not a huge deal, React complains, but works fine. Anyway, I've pushed a commit to master that changes class to className project-wise. I took the liberty of rebasing this PR on current master. Please remember to fetch & rebase your local changes before trying to push.

Okay, I understand better what's going on under the hood. Let me know if you want me to change anything, otherwise I'll let you merge this.
Cheers !

One thing I have to note is that I would probably go one step further with renderTooltip and let it render the code, too -- just pass it the code rendering function as well.

Agreed, and this was my first thought too. The problem is that one tooltip is renderered fully synchronously, and the other, because of the highlightCode part, is asynchronous. I suppose that it's because of all of the atom calls ? I just couldn't figure how to bypass this problem. Any idea welcome !
Anyway, I fixed pretty much all the suggestions you had earlier.

I added one more commit. I now make renderTooltip render the code part too, and just don't use the result in the datatipProvider, because of the asynchronous calls we have to await for to highlight code.

This feels somewhat redundant... Why not make renderTooltip async and move its invocation to update method in TooltipView? You'll need to save its result though, but it's nothing a private class property can't handle. Does that make sense?

This feels somewhat redundant... Why not make renderTooltip async and move its invocation to update method in TooltipView? You'll need to save its result though, but it's nothing a private class property can't handle. Does that make sense?

Yep, absolutely. I didn't know a lot about the JSX.ElementClass lifecycle. Thanks for the suggestion. I just commited the suggested changes.

Thanks for your work! Merging.

Thanks for your work! Merging.

Hey, no problem ! Thank you for your time & help on this cool projet. I'll try to take an issue from time to time.
Bye !


Update superfluid.yaml

Update the Superfluid project data entry with additional contract addresses on the Optimism and Base networks.

/validate 8f76b58e94f8ddaa94dd39c92e32a8fd5e2f2d71

@mdalie Thank you for this!!
We are currently in the process of refactoring this directory to strongly bias towards just entering your deployer address, which we should be able to auto-detect your contracts deployed (either directly or indirectly via a factory).
Would you mind updating this by:

Checking if your deployer address sufficiently covers all relevant contracts in our contracts_v1 API?
https://cloud.hasura.io/public/graphiql?endpoint=https://opensource-observer.hasura.app/v1/graphql
Then updating this file to only include deployer addresses?

Awesome, thanks! I just want to make sure factory contracts are tracked correctly as most of Superfluid's activity is routed via contracts deployed by the listed factories (like SuperTokens, for example).

/validate 8f76b58e94f8ddaa94dd39c92e32a8fd5e2f2d71

Validations passed 🎉
We have a little bug in our validator that is attributing addresses that aren't in your project file to you, but I've manually reviewed and this is good to go!
Best of luck in RF4!


Tool has exit code == 0 when invalid cli arguments are given

It should be a non-zero exit code

Sorry, I just forgot an assert


New request for native WSS support

I've followed the information provided in I believe #37, to bury the ws server inside of a https server with certificates. This works for me but only under one condition. I have to access the server directly at https://IP:9999 to get the certificates in the browser. Then I can use my actual website to open up that wss:// connection. The server doesn't just listen for and accept an attempt to open a wss:// connection at the node-rtsp stream without me doing that. I can't seem to get around it.
VideoStream.prototype.pipeStreamToSocketServer = function() {
  const server = https.createServer({
    cert: fs.readFileSync('./cert/cert.pem'),
    key: fs.readFileSync('./cert/key.pem'),
  }).listen(9999, '<IP_ADDRESS>');
  this.wsServer = new ws.Server({
    server
  })
  this.wsServer.on("connection", (socket, request) => {
    return this.onSocketConnect(socket, request)
  })
  this.wsServer.broadcast = function(data, opts) {
    var results
    results = []
    for (let client of this.clients) {
      if (client.readyState === 1) {
        results.push(client.send(data, opts))
      } else {
        results.push(console.log("Error: Client from remoteAddress " + client.remoteAddress + " not connected."))
      }
    }
    return results
  }
  return this.on('camdata', (data) => {
    return this.wsServer.broadcast(data)
  })
}

This piece of code works perfectly only if the browser is already certified. To do that I have to manually visit the IP the server is running on over https://IP:9999, accept the warnings, then leave. Now my hosted website over https:// can connect to that wss:// socket no problem and play video, but first having to certify with an https: visit is a major problem

This has been identified and solved. The issue is a bit tricky. Depending on where you're hosting the server, you will need to configure DNS so that you can register a REAL SSL/TSL certificate. You'll see in my example the cert.pem and key.pem are just some quick generated self signed certificates. I changed the way my server is hosted (gave it a domain) and generated a real key and cert with the domain name and it works.
Secure browsers like firefox will silently reject wss:// connection attempts in the background so it looks like it's just failing. In my case I had to visit my server directly at https::9999 to accept the warnings which would certify the browser. From there it would work.
That process is completely bypassed if your certificates are legitimate and not self signed. Now my jsmpeg player access wss://mydomain.app:9999 and it starts without question.
The information in #37 is accurate so thank you to everyone in there, this just fills in the blanks it leaves behind. I'll leave the issue open just because native WSS support would be nice, but it's not like the author can generate certs for you.


Support external diff algorithms in internal diff editor

Reopening closed feature request #30694
Openness, extensibility and customisability are the features that keep me coming back to VSCode. Being built upon an OSS core (Electron) was strong evidence of a change of culture at Microsoft.
In that spirit, would you please reconsider the original request from @myfairsyer. Different diffing algorithms produce significantly different results and are suited to different purposes. There is no one-size-fits-all solution.
Paraphrasing @myfairsyer, please consider abstracting the diff functionality to allow different hunk-list providers. Respecting the algorithm set in Git configuration would be an ideal baseline.
As another example, BeyondCompare allows significant customisation, including 2 of the 4 algorithms offered by Git.

Yep, I agree that VS code should support external diff tools with their known algorithms.

I'm missing Git's "patience" algo.
In my opinion there's a place for API and extensibility here. We could have various diff algorithms available as extensions, in addition to a good set provided right inside VS Code.

Any update here?
Internal diff algorithm sometimes gives poorly visual results.
So I wish I could use patience diff algorithm in vscode diff editor.

Yeah, this is ridiculous; notepad++ compare on the left, vscode compare on the right.

I would like to reference feature request #145068 here (disclaimer: it is taking votes, and I am the author) which may or may not make sense considering when defining an interface for alternative diff algorithms or diff extensions (in which case it might also be implemented independent of the diff algorithm as some kind of post-processing.)
In essence, I propose another change category (in addition to the current ones, which are green = line added and red = line removed). This new category (let's call it gray) shall represent lines which have no other change but being commented out or in (using language-specific grammar rules) with respect to the reference lines, allowing to overscroll them more easily because color and font style encode the only change (enabling/disabling the line).

this is ridiculous; notepad++ compare on the left, vscode compare on the right.

Highlighting inside a line is an Ediff feature. Diff just looks for changed lines, no matter what the algorithm is. The difference between the diff algorithms (the original diff, myers, minimal, patience, histogram) is how the lines between two files are ligned up. So it seems Ediff is being used on the left by notepad++ and not on the right. In Emacs for example you can activate Ediff for displaying a diff / diff3 output (and this is independent from the diff algorithm).

Do you have any updates on that? Do you have any plans on adding support for external diff tools? 🤔 . I'm thinking more about using difftasctic as a diff tool for vs code.
I'm not the only one here :
https://news.ycombinator.com/item?id=30841244.
https://stackoverflow.com/questions/73671245/how-to-change-the-diff-tool-used-by-vscode-for-git
Also, if anyone knows if it's possible right now, how can we achieve that?


Allow setting of DDL_LOCK_TIMEOUT for Oracle databases (DAT-7649)

Environment
Liquibase Version:
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
Liquibase Extension(s) & Version:
Database Vendor & Version:
Operating System Type & Version:
Pull Request Type

[ ] Bug fix (non-breaking change which fixes an issue.)
[x] Enhancement/New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
A clear and concise description of the issue being addressed.  Additional guidance here.

Describe the actual problematic behavior.
Ensure private information is redacted.

Steps To Reproduce
List the steps to reproduce the behavior.

Please be precise and ensure private information is redacted
Include things like

Files used - sql scripts, changelog file(s), property file(s), config files, POM Files
Exact commands used - CLI, maven, gradle, spring boot, servlet, etc.

Actual Behavior
A clear and concise description of what happens in the software before this pull request.

Include console output if relevant
Include log files if available.

Expected/Desired Behavior
A clear and concise description of what happens in the software after this pull request.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Fast Track PR Acceptance Checklist:

[ ] Build is successful and all new and existing tests pass
[ ] Added Unit Test(s)
[ ] Added Integration Test(s)
[ ] Added Test Harness Test(s)
[ ] Documentation Updated

Need Help?
Come chat with us on our discord channel

Because we used this PR for early testing of the github actions shift, I had to cherry pick these changes into master rather than merge this PR.


Argo CLI support for custom request headers

Summary
Add support for setting custom HTTP headers to argo CLI, similar to argocd -H, --header.
Use Cases
When Argo Workflows is configured behind IAP proxy like Cloudflare Access, we need to set a custom header with key cf-access-token and the actual token as a value.
Otherwise, when we execute argo list, we face the following error:
FATA[2022-02-23T22:38:56.530Z] invalid character '<' looking for beginning of value

This is already implemented in argocd CLI.
As an example, you can see issue #7036.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

I'm assuming you're using ARGO_HTTP1=true.
We would need to pass the header here:
https://github.com/argoproj/argo-workflows/blob/6076524cd51484b5f1efb3b6ff96cebdd020eba2/pkg/apiclient/http1/facade.go#L60
It would get the header values from here:
https://github.com/argoproj/argo-workflows/blob/6076524cd51484b5f1efb3b6ff96cebdd020eba2/pkg/apiclient/argo-server-opts.go#L7
Which would be set here:
https://github.com/argoproj/argo-workflows/blob/6076524cd51484b5f1efb3b6ff96cebdd020eba2/cmd/argo/commands/client/conn.go#L48
Would you like to submit a PR?

Would you like to submit a PR?

Yes, I will be working on a PR.


log proposerAddress when invalid state machine block

Description
Closes https://github.com/celestiaorg/celestia-core/issues/810

thinking about this more, we should probably keep this logic in the app.

For my education, is the motivation behind this to minimize the diff between celestia-core and tendermint?

...so we should be able to add the proposer to that log message

Will do in all Error logs for rejected blocks in https://github.com/celestiaorg/celestia-app/blob/main/app/process_proposal.go

as a side note, all of the logs there take up so many lines of code that is makes the function difficult to read. If we get a tad creative, we should be to refactor all of those lines into much few lines, while also including the proposer in the error message.

Created https://github.com/celestiaorg/celestia-app/issues/610

For my education, is the motivation behind this to minimize the diff between celestia-core and tendermint?

that certainly a part of it, also just being able to see all of our changes in one place. We might not need this in the future after ABCI++ is more widely used and this issue is common place.


Not working properly on 21:9 monitor

As you can see below the dashboard dont work really well in a 21:9 monitor
http://imgur.com/gallery/no3t9ib

that is the only image that can describe my reaction.. fuck.. that was some serious old classic right there. good old times friend... good old times.

Really good times! Hope you are doing well and "Fica frio ai"! Hugs :p


Fix description for configureOnOpen

Change the description to match new behaviour
from https://github.com/mesonbuild/vscode-meson/pull/106

cc: @xclaesse

LGTM, but I don't have push permission. @dcbaker


Enable Server Side Apply for Client Patch Calls

Description
What problem are you trying to solve?
Karpenter currently doesn't use Server Side Apply when making patch calls to the apiserver. This doesn't cause a ton of issues today since there aren't a ton of writers to the objects that we own (although the Node is a bit of an exception to this rule)
We should use Server Side Apply since then we can declare a set of managed fields that we own and ensure that only these fields are updated when we make a Patch call to the apiserver and no other updates are made to the object.
Server Side Apply Docs: https://kubernetes.io/docs/reference/using-api/server-side-apply/
How important is this feature to you?
It will prevent us from fighting and overwriting with other controllers that may also be trying to write different fields to the same object.
Related Issues
https://github.com/aws/karpenter-core/issues/660

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

/assign

Hi @jonathan-innis ,Tried looking at it I guess it considers our crd's as unstructured object . so we would have to make some more changes such as converting the crd resources into unstructured and also pulling dynamicclient and then applying them

I'd consider looking deeper into how controller-runtime directly handles this as well as look into how CAPI (Cluster API) does SSA. I believe they should have paths forward to enable us to do the same in Karpenter.

/reopen

/triage accepted
/remove-lifecycle stale

/remove-lifecycle rotten


Action hits deprecation warnings

Running the basic config specified on the Action page results in:
Run<EMAIL_ADDRESS>Run python -m pip install --upgrade pip -q

Requirements file requirements.txt not found
Run pip install behave -q

  DEPRECATION: parse is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Behave artifact full path = tests/results.txt
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Thanks for the issue report, Mike.
v0.4.0 is updated to use actions/upload-artifact@v4 and actions/setup-python@v5
Note: v0.3.0 will be deprecated November 30, 2024 with actions/upload-artifact@v3
The deprecation warning for v0.3.0 is also on the github action marketplace page
Additionally, there is a bug fix so the artifact name will actually match the test-output-name input


Maintenance: Update Rollbar Ruby gem and tighten configuration

More explicitly describe some privacy-related configuration.  Make sure default Rails person tracking is disabled.  Within Rollbar, only store anonymized identifiers and partially anonymized IP addresses, for the purpose of investigating issues.  Retention policy there is 30 days.

selfie


Passing data into a renderer function isn't passed into the component

var frag = stache("<data-from-scope {foo}='bar'/>")({
  bar: "bar"
});

There's a breaking test that is being skipped currently.

To visualize the difference between can-component and can-custom-elements this is pseudo-code for how can-view-target works:
var el = document.createElement("some-component");
new SomeComponent(el, { scope: scope });

Whereas custom elements the constructor and document.createElement are the same thing. So we have to get the scope in the constructor some how.

We could setup a tag using callbacks.tag so that we get the scope and set it on the element.


Updates capability statements for R4

R4 seems to be missing vread.

Some of the definitions doesn't look right:
                        {
                            "name": "identifier",
                            "definition": "http://hl7.org/fhir/SearchParameter/Account-identifier",
                            "type": "date",
                            "documentation": "Account number"
                        },

Identifier should not be type of date.

@brandonpollett @jackliums anything else seem out of place on this one?

I did a quick scan of the file and they all seemed to be fine now.


Scripttag job is not dispatching

Expected Behavior
Scripttag api and webhooks are not executing.
Current Behavior
I think scripttags and webhook script is not executing even after I did the correct configuration in config/shopify-app.php.
Is there any other steps involved.

Please fill out the issue template.

Are you using a tunnellike ngrok? There are lots of issues around using tunnels when trying to fire webhooks and tags. They can sometimes work and sometimes not.
We also need more information to be able to give you any more assistance.

Closing for lack of info and no template.

Closing for lack of info and no template.


remove default user and password

The user can be created in the image-builder repos or with cloud-init at first boot.

LGTM


Help with actuators

Hi,
I'm an engineer and I'm trying to use MuJoCo for visualizing and manipulating a Universal Robot UR3e robot.
I'm looking for some help with actuators - specifically, examples I have looked at and loaded work perfectly, with each joint controllable. I have tried building my own XML using the official files from Universal Robot's website (https://www.universal-robots.com/download/mechanical-e-series/ur3e/robot-ur3e-jt-file-e-series/) which I converted to STLs, also attached. I noticed that to get any movement, I need to set kp to obscenely high values, and the resulting motion oscillates.
Here is a model which explains my question - I included only ground and base to make things easier:

minimal XML
<mujoco model="ur3e">
    <compiler inertiafromgeom="auto" angle="degree" meshdir="./mesh/ur3e/collision/" texturedir="./mesh/ur3e/visual/" />
    <option gravity="0 0 -9.81" collision="predefined" />
    <asset>
        <mesh name="ground"     file="GroundModel.stl" />
        <mesh name="base"       file="BaseOffModel.stl" />
    </asset>
    <default>
        <default class="ur3e_actuator">
            <position ctrllimited="true" kp="1000000" ></position >
        </default>
    </default>
    <worldbody>
    <body name="ground" pos="0 0 0">
        <geom type="mesh" contype="0" conaffinity="0" group="1" rgba="0.7 0.7 0.7 1" mesh="ground" />
        <geom type="mesh" rgba="0.7 0.7 0.7 1" mesh="ground" />
        <body name="base_link" pos="0 0 151.85">
            <joint name="base_joint" pos="0 0 0" axis="0 0 1" limited="true" range="-360 360" />
            <geom type="mesh" contype="0" conaffinity="0" group="1" rgba="0.7 0.7 0.7 1" mesh="base" />
            <geom type="mesh" rgba="0.7 0.7 0.7 1" mesh="base" />
        </body>
    </body>
    </worldbody>
    <actuator>
        <position class="ur3e_actuator" name="base_pos" joint="base_joint" ctrlrange="-360 360" gear="1000" ></position >
    </actuator>
</mujoco>

Here is a screenshot where I set the actuator to 360 degrees but resulting rotation is a fraction of that, as well as the two relevant STL models:

collision.zip
Thank you very much.

Hi @dreamxjei, the masses are absurdly high in your model (you can check by inspecting body_subtreemass in the file generated by PRINT MODEL. You should specify them using proper inertial tags, see the official URDF files for those.
FYI, the MuJoCo team recently released a UR5e MJCF in MuJoCo Menagerie. The README in there details the steps that were taken to convert the URDF file to a working XML one. Should be almost identical if you want to create an XML for the UR3.


Deploy Link error

I have switched on my hotspot but it's not working what should I do plssss help


Flutter beta 1.22.0-12.1.pre - compile error

/C:/Programs/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-3.14.0-alpha.3/lib/src/form_builder_custom_field.dart:96:40: Error: The getter 'autovalidate' isn't defined for the class 'FormField<T>'.
 - 'FormField' is from 'package:flutter/src/widgets/form.dart' ('/C:/Programs/flutter/packages/flutter/lib/src/widgets/form.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'autovalidate'.
        autovalidate: widget.formField.autovalidate,
                                       ^^^^^^^^^^^^

For 3.13.5 it is even worse:
/c:/Programs/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-3.13.5/lib/src/fields/form_builder_range_slider.dart:21:9: Error: Type 'RangeSemanticFormatterCallback' not found.
  final RangeSemanticFormatterCallback semanticFormatterCallback;
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/c:/Programs/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-3.13.5/lib/src/fields/form_builder_range_slider.dart:21:9: Error: 'RangeSemanticFormatterCallback' isn't a type.
  final RangeSemanticFormatterCallback semanticFormatterCallback;
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/c:/Programs/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-3.13.5/lib/src/form_builder_custom_field.dart:96:40: Error: The getter 'autovalidate' isn't defined for the class 'FormField<T>'.
 - 'FormField' is from 'package:flutter/src/widgets/form.dart' ('/c:/Programs/flutter/packages/flutter/lib/src/widgets/form.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'autovalidate'.
        autovalidate: widget.formField.autovalidate,
                                       ^^^^^^^^^^^^

I fixed in it my fork, you can use it via
flutter_form_builder:
git:
url: https://github.com/knaeckeKami/flutter_form_builder.git
ref: v3.14.0-alpha.2-fix
I would open a PR, but I'm not sure against which branch I should open it, and the alpha.3 version seems to not be tagged, so I used the alpha.2 tag. I'm happy to follow up with a PR.

This is a breaking change, I don't think there is a backwards compatible way to handle this. Maybe with an extension on FormField?

It looks like they are adding back in at least a (deprecated) getter so it'll compile. However, I'm not sure how quickly it'll go through the various Flutter versions.
So it looks like autovalidateMode was added (in 1.21.x) present before autovalidate was removed (in 1.22.x). We could just fully switch that line to using:
 autovalidateMode: widget.formField.autovalidateMode,

All state is already stored by the underlying FormField
As of 1.21.x, the only guaranteed state in FormField is from autovalidateMode

If autovalidate is used in creating the FormField, autovalidateMode is also set
If autovalidateMode is used in creating the FormField, autovalidate is left to its default value (false)
Ref: FormField constructor code in 1.21-candidate.10

There'd be no way to utilize AutovalidateMode.onUserInteraction, since that's new middle-ground state

It looks like they are adding back in at least a (deprecated) getter so it'll compile. However, I'm not sure how quickly it'll go through the various Flutter versions.
Do you have an issue number for this?

No issue, but (draft) PR is https://github.com/flutter/flutter/pull/66267

https://github.com/flutter/flutter/issues/66940 is now marked for cherry pick into Flutter 1.22 and should solve this.

@kuhnroyal
While the property is being added back in to not break things, it's still being deprecated.
  @Deprecated(
    'Use autoValidateMode parameter which provides more specific '
    'behavior related to auto validation. '
    'This feature was deprecated after v1.19.0.'
  )
  final bool autovalidate;

So should probably still go ahead with the fix suggested above and switch to autovalidateMode

@skyeskie That is correct, but for now I am looking just for a library version that compiles with 1.22.0

v3.14.0 compiles with Flutter 1.22.*

Proposed fix:
autovalidate: widget.formField.autovalidateMode == AutovalidateMode.always,

this is the correct answer


Fix stream writer flushing to be thread safe.

Overview
This change fixes the raft streams so that Flush() is not called asynchronously while the snapshot is being written. Previously the logWriter would call Flush() while the snapshot was being written. Now it will not call flush until the snapshot is complete.

:shipit: on green

+1, the write will now only take place is snapshotting is not.


Tailwind scaffold template is out of sync with rails/rails ERB scaffold template

https://github.com/rails/tailwindcss-rails/blob/main/lib/generators/tailwindcss/scaffold/templates/index.html.erb.tt is out of sync with https://github.com/rails/rails/blob/main/railties/lib/rails/generators/erb/scaffold/templates/index.html.erb.tt, namely it's missing the <% content_for :title, "New event" %>
Should template files be kept in sync (except the tailwind classes)?

@yshmarov Thanks for spotting that! If you have the time to submit a PR I would be happy to merge it. If not, please let me know and I can fix it later this week.

Looking at the changes to rails templates since 2021, there are a few changes that should probably be carried over to this gem. I'm not going to do this work, but would welcome anyone from the community who would like to submit a PR.
I think the set of changes that should be looked at is limited to:

rails/rails#43611 (rails/rails@6cd75a42)
rails/rails#43846 (rails/rails@1c390905)
rails/rails#43880 (rails/rails@ea15f8e6)
rails/rails#49702 (rails/rails@42ca4de4)


loop_type support

Support Loop_type opcode.
Allows sample looping to be:
• forward
• backward
• alternate
https://sfzformat.com/opcodes/loop_type.html

This is supported in DropZone, Dimension and Rapture.
Sforzando parsed this silently and just set it to forward only.


Swift branch multi-language not work

We're looking into it right now. We believe it has to do with the access to the bundle in the module. The previous access procedures no longer work.

@graysonwebster
I tried to solve, but did not succeed
https://github.com/zhangao0086/DKImagePickerController
Multilanguage of this library is also by bundle

DateToolsSwift is now the preferred cocoapod and Swift 3 compatible version (as per documentation). Localizations have been confirmed to work as of version 2.0.2. Thanks for using DateTools!


Late Move Reductions

LMR 😃
Hope you don't mind the ping, thank you @cosmobobak again. For lending me help and code 🚀❤

Score of svart-dev vs svart-master: 89 - 25 - 58  [0.686] 172
...      svart-dev playing White: 42 - 17 - 27  [0.645] 86
...      svart-dev playing Black: 47 - 8 - 31  [0.727] 86
...      White vs Black: 50 - 64 - 58  [0.459] 172
Elo difference: 135.8 +/- 43.9, LOS: 100.0 %, DrawRatio: 33.7 %
SPRT: llr 2.96 (100.7%), lbound -2.94, ubound 2.94 - H1 was accepted

don't worry! it's always a pleasure to know that I'm contributing to good engine development :)


Upgrade "connect" to a modern version (or look into koa/express)

The packager is using an old version of connect which has some vulnerabilities (in practice probably not an issue but would be good to fix) and the API has changed a bunch. Most small Node servers are using koa or express now so it could be good to upgrade to one of those.
This work should be fairly accessible to potential contributors who have JS experience and are looking for a challenging but accessible task if someone wants to work on a PR.

cc @amasad - this work should be mostly contained to the packager frontend but tell me if it'd be stepping on toes

I think we should be good. We have a few more middlewares internally that needs to be tested by they seem fairly straightforward.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/upgrade-connect-to-a-modern-version-or-look-into-koaexpress
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix. We rely on the community to provide
bugfixes as the core team is heavily focused working on performance.


Implement cancel commands

Implement these messages:

OrderCancelRequest (35=F)
OrderMassCancelRequest (35=q)

This change is

Could you fixup the whole branch ?


All Workspace Enabled

Notion card
Summary

Preview

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactor (non-breaking and retains same functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

Closing this PR as bug on staging and production got resolved due to user roles missing


Special case Elasticsearch 7.8+ Composable index templates

Feature:
If we prefer composable templates or otherwise prioritize our index templates, we can avoid support problems like https://github.com/openzipkin/zipkin-support/issues/23 where the template doesn't kick in due to something else matching on '*'
Rational
Composeable templates are both introduced and preferred in ES 7.8+, which refers to _template as legacy ones.
This would introduce an issue of composeable template priority, either it would have to determine automatically what value should be set or be parameterizable through env variable.
Example Scenario
Test would have a pre-existing composable template and ours still applies
Thanks @benqs for the hint. cc @openzipkin/elasticsearch

BTW this is part of a bigger change around time-based indices that will lead to data streams; though that is still work in progress. So I would wait a little longer here and see if that might make sense for Zipkin as well.


升级后关于透明度的动画失效了

3.1.2版本里，addAnimate opacity从0到1的动效到新版本里都直接不展示了

Change the opacity property to alpha

Change the opacity property to alpha

可不可以提供，这次change，总共涉及到哪些地方，需要怎么修改？

FFCreator upgrades almost do not need to modify the api, this part is because of the modification of the rendering kernel.
https://github.com/tnfe/FFCreator/blob/master/CHANGELOG.md

FFCreator upgrades almost do not need to modify the api, this part is because of the modification of the rendering kernel.
https://github.com/tnfe/FFCreator/blob/master/CHANGELOG.md

刚才发现旋转角度也变成弧度

Are you interested in this project https://github.com/tnfe/FFCreator/issues/99? Maybe you can try.

Oh, maybe you can use lowcode and ffcreator to create a visual creation video site.


Make the HttpEnumRollupIntegrationTest less fragile

What:
Make the HttpEnumRollupIntegrationTest less fragile
How:
Sometimes the points rolled up do not exactly correspond to the points expected (because 1500 points roll up to 288 or 289 depending on when the timestamp falls) and the test fails. We want the test to be less fragile and a number in the ballpark of +-5 is ok with us. So I took the difference between the expected and the given, and check to see if the absolute value of the difference is less than 5.

:+1:  lgtm, thanks for fixing @tilogaat


Incorrect indent warning

Describe the bug
I am using the formatter and code style check. Here is my config.
nvim_lsp.sumneko_lua.setup {
  cmd = { "lua-language-server", "--preview" },
  settings = {
    Lua = {
      runtime = {
        -- Tell the language server which version of Lua you're using (most likely LuaJIT in the case of Neovim)
        version = 'LuaJIT',
        -- Setup your lua path
        path = runtime_path,
      },

      diagnostics = {

        neededFileStatus = {
          ["codestyle-check"] = "Any",
        },

      },

      format = {
        enable = true,
        defaultConfig = {
          indent_style = 'space',
          indent_size = 2,
        },
      },

      workspace = {
        -- Make the server aware of Neovim runtime files
        library = vim.api.nvim_get_runtime_file("", true),
      },
      -- Do not send telemetry data containing a randomized but unique identifier
      telemetry = {
        enable = false,
      },
    },
  },
}

As the config above, my indentation size is 2 spaces. However, it gives me wrong warnings for the indentations in functions.

It seems that the setting of indent_size has no effects. I tried to change it like indent_size = 8, however, nothing happened after I executed vim.lsp.buf.formatting().
Environment (please complete the following information):

OS: macOS (the latest version)
Client: neovim

I posted this issue at EmmyLuaCodeStyle repo as well.
Thank you so much.

Wow, I figured it out. From this line in the source code config.lua, the value in defaultConfig table should be string, not integer. So to make it work, we should use indent_size = "2" instead of indent_size = 2.
I think this should be mentioned somewhere. I will add it in the "Code Formatter" section in Wiki.


Fix bug with transpose and pad

Looks like with this fix and the fix for eliminate_concat, the following models that have different results on CPU and GPU can have same results now:
opset7,8,9,10,11:
tf_inception_v1
tf_inception_v2
tf_mobilenet_v1_1.0_224
tf_mobilenet_v2_1.0_224
tf_mobilenet_v2_1.4_224
opset9/LSTM_Sequence_unpack
There are still 4 fp16 models that are incorrect
I will test this branch in onnxruntime, and let you guys know the output.


Template override via Bundle

You mention overriding the layout and manage Twig file in your readme, but I think this can easily be done by using Symfony's default Bundle inheritance.
Copying layout.html.twig to app/Resources/DmishhSettingsBundle/views will allow users to override it without having to define it in the config. :+1:

What if you want to use your existing layout without copying it to the app/Resources/DmishhSettingsBundle/views folder?

Let /app/Resources/DmishhSettingsBundle/views/layout.html.twig extend your existing layout, and put the {% block settings_form %}{% endblock %} in your default block. Maybe the block can be renamed to content to make the block's name more consistent with other bundles.

@rvanlaak @Nyholm hi guys. I really don't have time to support this bundle, but I don't want to just bury it. I would like to transfer the bundle to one of you, since you've been the most active contributors. Of course if you want to.

Lets both do it. I've been reading all issues and PRs for a year now.
@rvanlaak Do you want to join forces and make sure 2.0 is released?

Ok, I'll give you guys push access.

Done @Nyholm @rvanlaak

Would be great! :rocket: How is sf3.0 compatibility? Otherwise I'll focus on that.

@rvanlaak: Will you send a PR?

Do you want me to get rid of the settings_manager.layout parameter? It is solely used by the SettingController:108. Think we should always advocate for the bundle inheritance.

Yeah. Lets follow the Symfony best practices. Only inheritance will be fine.