Sending to the REPL immediately after connection uses CL-USER package

99% of the time Vlime manages to autodetect the correct package for my Lisp buffers, but there's one case that trips it up.  If I start the Vlime server in another window (and quickload my project from there), then open (n)vim, connect with \cc and immediately try to send with \ss it will use the CL-USER package.  If I send again with \ss it works correctly, and if I open new buffers it also works.  It just seems to be that first time I try to send after connecting.

I failed to re-produce this problem in my environments. To make it clear, I did it like this:

Start a server using sbcl --load ~/quicklisp/setup.lisp --load vlime/lisp/start-vlime.lisp --eval (ql:quickload :clss);
vim <clss source dir>/selector.lisp;
\cc;
\ss on the first defun;
The compiler gave a warning on redefining CLSS:MAKE-SELECTOR, it means that defun was correctly evaluated in package clss.

Are these the same steps as how you produced this problem? If so, I may need more details. In particular:

What were you sending with \ss? I presume you sent the same expression twice?
In which file did you invoke \ss? It'll be nice if I can have a look at the content of that file.

Some implementation details: Vlime searches for an (in-package ...) form in the current buffer, and use that package if found. I'm suspecting the search failed to work with your file.

Oops, I just recalled that I have fixed a similar bug a while ago, when tangling with issue #6.
When the REPL buffer is not open, sending anything to the REPL would cause the cursor to jump to the REPL buffer first, and (incorrectly) make the following evaluation calls to use the package bound to the REPL buffer, which defaults to CL-USER.
This is fixed in the master branch. Would you please check the version you are using, and maybe update the code and then see if the problem still exists?

I'm closing this issue for now. If the problem ever rise again, please feel free to re-open this issue, or file another one.


Plugin does not immediately initialise in IE11/Firefox

You need to press return to initialise the plugin UI, in Chrome however the plugin initialises immediately after clicking into the medium editor enabled field.

Which version of Firefox are you using ?

Version is 37.0.1 (latest at time of writing)

Do you that problem on these pages too ?

http://orthes.github.io/medium-editor-insert-plugin/
http://daviferreira.github.io/medium-editor/

I've tested both on Firefox 37.0.1 and every thing goes well.

Yes, on your demo page.
If you clear all the text you have in the demo page. Then click away so that the placeholder is shown again. Click once and the plugin does not show the + at the side, click again or press return and it shows.

Thanks for steps to reproduce, it helps! I got the problem too on the demo page.
As a side note, I've integrated this plugin in our CMS and didn't get that problem.

No worries. Hope its not too much of a headache to fix at some point. Really nice tool you have here.


Digikey all blank

KiCost is a great tool!  But recently it's unable to retrieve parts from Digikey -- all parts come un "not found at digikey" but they're listed on Digikey's website.
On a related note: why scrape the website when Digikey offers a RESTful API for this purpose?

Digikey may have changed their web page format. It was working a few days ago. I'll have to look.
Reasons not to use the Digikey API: rate limiting, charges for some plans, only provides price for a given quantity (can't get all the price break info at once), complicates setup with a unique token for each user, etc. I'd rather just scrape the site. Like a pirate.

I just tested KiCost on Digi-Key. It's getting part information OK. Make sure you're using the latest version (kicost -v should print 0.1.35). If you are, then send me the XML that shows the problem.

Thank you for the prompt reply!!
I did some checking and discovered it works on Linux (Ubuntu 16.04 x64), but not on MacOSX (10.12.5, the latest).
Regards,
-david

On May 27, 2017, at 12:21 PM, xesscorp<EMAIL_ADDRESS>wrote:
I just tested KiCost on Digi-Key. It's getting part information OK. Make sure you're using the latest version (kicost -v should print 0.1.35). If you are, then send me the XML that shows the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/xesscorp/KiCost/issues/70#issuecomment-304471422, or mute the thread https://github.com/notifications/unsubscribe-auth/AbqSm5AC_Q8d7odOGEfrC6YClsNURbvPks5r-HfSgaJpZM4NobjZ.


fatal: no such branch: 'HEAD...' on empty repository

When I clone an empty repository pure throws me an error:
No such branch: 'HEAD...'

I'm trying to see if this is OS X specific.
I created an empty git repository locally (git init test) and didn't get any error on cd test/.
Does it happen to you when you do git init? or only specifically when you clone an empty repository?
Also, what's your git --version?

Apparently this occurs with bitbucket empty repo. (tested)
$ git version
git version 2.5.0

Here my screenshot:

Reproduced this on my machine (Fedora 23, 64-bit, git 2.5.0) as well.
I think I found a fix. Will submit a PR for review in a few moments.

:+1:


React in Vue - Vite.config.ts issue

@devilwjp, @zhangHongEn   I want to use React component in my project which built on Vue, Quasar and few typescript files (for interfaces, constants and config). I am trying to change the vite.config.ts. But I got the below error. Please help me to resolve the issue.
Code changes (vite.config.ts):

import { defineConfig } from "vite"
import { quasar, transformAssetUrls } from "@quasar/vite-plugin"
import veauryVitePlugins from "veaury/vite/index.js"

export default defineConfig({
plugins: [
veauryVitePlugins({
type: "vue",
vueOptions: { template: { transformAssetUrls } },
}),

quasar({
sassVariables: "src/quasar-variables.sass"
}),
]
})

Error Message:

i have the same problem :(

@hahatulk @laxmangaian
vite.config.js does not seem to configure the vite-tsconfig-paths plugin


[v*] Healthcheck goroutine leaks

Hi! This PR fixes goroutine leaks caused by healthcheck not using ctx properly.
I've managed to reproduce it via tests.

That looks interesting. Thanks for reporting/fixing it. BTW: Tests fail for Go 1.7 because http.Server in 1.7 doesn't have a Shutdown method.

Hmm. Stumbled upon something re: golang/go#20668.

@utrack That works as expected here: Context is canceled.

@olivere on Go 1.8 it works OK, but fails on 1.7.

@utrack Oh, I see.

I've also prepared v2 backport, should I open up another PR?

@olivere Fixed tests for all versions. It's not possible to monitor leaks directly on Go pre-1.8, so I'm using side effects to monitor stuck connections on pre-1.8.

@utrack Okay, thanks for figuring this out. Can you do three more things for me to merge this into v5:

As far as I can see it, you only have a test to check leaks for healthcheck. Can you also add a test for the sniffNode?
Can you please rename the test for healthcheck from TestRoutineLeaks to TestClientHealthcheckTimeout (or something more expressive). The test for the sniffer should be something like TestClientSnifferTimeout.
Can you move the tests to the end of the other TestClientHealthcheck... (and TestClientSniffer...) tests.

Then we can put together PRs for v2 and v3, or I'll do this in a batch.

Sure, done @olivere

Merged and will be published soon. Thanks again!

@utrack Do you mind to review #545 (and this commit). It's this PR backported into elastic.v3.
I will also backport to elastic.v2 later with #546, after merging #503 first.

Reviewed everything :) Looks good, thank you for the client!

@utrack Thanks.  I'm using elastic.v3... Upgrading Go to 1.8.3 resolved it...
 % wget https://storage.googleapis.com/golang/go1.8.3.linux-amd64.tar.gz
 % sudo tar -C /usr/local -xzf go1.8.3.linux-amd64.tar.gz
 % sudo mv /usr/bin/go /usr/bin/go1.6
 % sudo ln -s /usr/local/go/bin/go /usr/bin/go
 % go version
go version go1.8.3 linux/amd64
 % go build
 %

@wtfiwtz I see. However, 1.6 is no longer supported. I try to support the current and previous versions of Go (while Go itself even only supports the current version). From my experience, updating Go is nowhere as critical as in other environments.

Note that this bit me as well. I've updated to 1.8 and everything compiled.
Thanks,
-c


Mkdocs

Try to use mkdocs - material
Some issues, e.g. rendering math

And some helpful warnings of things to fix
$ mkdocs serve
➜  modelskill git:(mkdocs) ✗ mkdocs serve
INFO    -  Building documentation...
INFO    -  Cleaning site directory
WARNING -  Doc file 'getting-started.md' contains a relative link 'modelskill.model.PointModelResult', but the target is not found among documentation files.
INFO    -  Doc file 'getting-started.md' contains an unrecognized relative link 'PointObservation', it was left as is.
INFO    -  Doc file 'getting-started.md' contains an unrecognized relative link 'TrackObservation', it was left as is.
WARNING -  Doc file 'getting-started.md' contains a relative link 'modelskill.comparison.ComparerCollection', but the target is not found among documentation files.
WARNING -  Doc file 'getting-started.md' contains a relative link 'ComparerCollection.skill', but the target is not found among documentation files.
WARNING -  Doc file 'simple-compare.md' contains a relative link 'modelskill.connection.compare', but the target is not found among documentation files.
WARNING -  Doc file 'simple-compare.md' contains a relative link 'modelskill.comparison.Comparer', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison.ComparerCollection.skill', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.PointObservation', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.TrackObservation', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.model.PointModelResult', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.model.TrackModelResult', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.model.DfsuModelResult', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.model.GridModelResult', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.metrics', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison.ComparerCollection.score', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.from_matched', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.matching.compare', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison.Comparer', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison.Comparer', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.matching.compare', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison.ComparerCollection', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.matching.compare', but the target is not found among documentation files.
WARNING -  Doc file 'terminology.md' contains a relative link 'modelskill.comparison', but the target is not found among documentation files.
WARNING -  griffe: modelskill/plotting/_wind_rose.py:81: No types or annotations for parameters ['resize_calm']
WARNING -  griffe: modelskill/plotting/_wind_rose.py:81: Parameter 'resize_calm' does not appear in the function signature
WARNING -  griffe: modelskill/settings.py:436: Could not parse line '`obj` - the object to be checked'
WARNING -  griffe: modelskill/settings.py:436: Empty parameters section at line 2
WARNING -  griffe: modelskill/settings.py:399: Could not parse line '`_type` - the type to be checked against'
WARNING -  griffe: modelskill/settings.py:399: Empty parameters section at line 2
WARNING -  griffe: modelskill/settings.py:380: Could not parse line '`_type` - a type to be compared against (e.g. type(x) == `_type`)'
WARNING -  griffe: modelskill/settings.py:380: Empty parameters section at line 2
WARNING -  griffe: modelskill/settings.py:326: No types or annotations for parameters ['disabled']
WARNING -  griffe: modelskill/settings.py:326: Parameter 'disabled' does not appear in the function signature

Having examples in the docs are great. 🙂
Polars has nice user guide with input/output examples e.g. Polars
Combining DataFrames
This is achieved by executing a snippet of of python (and Rust) code and inserting the output to avoid errors from copy/pasting.

$ mkdocs build
INFO    -  Cleaning site directory
INFO    -  Building documentation to directory: /home/jan/src/modelskill/site
INFO    -  Documentation built in 1.44 seconds

-> No errors reported

How is it working out with the math?


Icons Added | #191

Hey, i finished adding the icons to the header. I have made sure that all four index, features, contact and team files have been changed successfully.
Issue number #191

Hope you like it 🙏
Please label me under gssoc and hacktober

Hey can you please remove the GSSOC'24 ext label and add gssoc-ext (all in small letters) label
i didn't receive any points for this contribution, so please do the changes as soon as possible. Thank You 🙏


OSError: Unable to open file (Unable to open file: name = '/home/user_li/linqin_tmp/sourcecode/rpiter/result/rpi1807/rpi1807-20-04-11-16-45-06/weights.hdf5', errno = 2, error message = 'no such file or directory', flags = 0, o_flags = 0)

@Pengeace
(base) user_li@WangLab:~/linqin_tmp/SourceCode/RPITER$ pip3 install -r requirements.txt
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: keras>=2.0.8 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 1)) (2.3.1)
Requirement already satisfied: numpy>=1.8.0 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 2)) (1.18.2)
Requirement already satisfied: tensorflow>=1.3.0 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 3)) (1.14.0)
Requirement already satisfied: matplotlib>=2.0.0 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 4)) (3.0.3)
Requirement already satisfied: scikit-learn>=0.18.1 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 5)) (0.22.2.post1)
Requirement already satisfied: h5py>=2.7.0 in /home/user_li/.local/lib/python3.5/site-packages (from -r requirements.txt (line 6)) (2.7.0)
Requirement already satisfied: keras-preprocessing>=1.0.5 in /home/user_li/.local/lib/python3.5/site-packages (from keras>=2.0.8->-r requirements.txt (line 1)) (1.1.0)
Requirement already satisfied: pyyaml in /home/user_li/.local/lib/python3.5/site-packages (from keras>=2.0.8->-r requirements.txt (line 1)) (5.3.1)
Requirement already satisfied: six>=1.9.0 in /home/user_li/.local/lib/python3.5/site-packages (from keras>=2.0.8->-r requirements.txt (line 1)) (1.14.0)
Requirement already satisfied: keras-applications>=1.0.6 in /home/user_li/.local/lib/python3.5/site-packages (from keras>=2.0.8->-r requirements.txt (line 1)) (1.0.8)
Requirement already satisfied: scipy>=0.14 in /home/user_li/.local/lib/python3.5/site-packages (from keras>=2.0.8->-r requirements.txt (line 1)) (1.4.1)
Requirement already satisfied: google-pasta>=0.1.6 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (0.2.0)
Requirement already satisfied: absl-py>=0.7.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (0.9.0)
Requirement already satisfied: tensorflow-estimator<1.15.0rc0,>=1.14.0rc0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.14.0)
Requirement already satisfied: grpcio>=1.8.6 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.27.2)
Requirement already satisfied: wheel>=0.26 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (0.34.2)
Requirement already satisfied: astor>=0.6.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (0.8.1)
Requirement already satisfied: tensorboard<1.15.0,>=1.14.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.14.0)
Requirement already satisfied: wrapt>=1.11.1 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.12.1)
Requirement already satisfied: termcolor>=1.1.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.1.0)
Requirement already satisfied: protobuf>=3.6.1 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (3.11.3)
Requirement already satisfied: gast>=0.2.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorflow>=1.3.0->-r requirements.txt (line 3)) (0.3.3)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /usr/lib/python3/dist-packages (from matplotlib>=2.0.0->-r requirements.txt (line 4)) (2.0.3)
Requirement already satisfied: cycler>=0.10 in /home/user_li/.local/lib/python3.5/site-packages (from matplotlib>=2.0.0->-r requirements.txt (line 4)) (0.10.0)
Requirement already satisfied: python-dateutil>=2.1 in /usr/local/lib/python3.5/dist-packages (from matplotlib>=2.0.0->-r requirements.txt (line 4)) (2.7.5)
Requirement already satisfied: kiwisolver>=1.0.1 in /home/user_li/.local/lib/python3.5/site-packages (from matplotlib>=2.0.0->-r requirements.txt (line 4)) (1.1.0)
Requirement already satisfied: joblib>=0.11 in /home/user_li/.local/lib/python3.5/site-packages (from scikit-learn>=0.18.1->-r requirements.txt (line 5)) (0.14.1)
Requirement already satisfied: markdown>=2.6.8 in /home/user_li/.local/lib/python3.5/site-packages (from tensorboard<1.15.0,>=1.14.0->tensorflow>=1.3.0->-r requirements.txt (line 3)) (3.2.1)
Requirement already satisfied: setuptools>=41.0.0 in /home/user_li/.local/lib/python3.5/site-packages (from tensorboard<1.15.0,>=1.14.0->tensorflow>=1.3.0->-r requirements.txt (line 3)) (46.1.1)
Requirement already satisfied: werkzeug>=0.11.15 in /home/user_li/.local/lib/python3.5/site-packages (from tensorboard<1.15.0,>=1.14.0->tensorflow>=1.3.0->-r requirements.txt (line 3)) (1.0.0)

cd sample
python3.5 rpiter.py -d RPI1807
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
/home/user_li/.local/lib/python3.5/site-packages/h5py/__init__.py:34: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/home/user_li/.local/lib/python3.5/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
Using TensorFlow backend.
WARNING:tensorflow:From rpiter.py:70: The name tf.ConfigProto is deprecated. Please use tf.compat.v1.ConfigProto instead.

WARNING:tensorflow:From rpiter.py:72: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.

2020-04-11 16:45:06.300261: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-04-11 16:45:06.306923: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-04-11 16:45:06.308236: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x6b14d10 executing computations on platform Host. Devices:
2020-04-11 16:45:06.308260: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): <undefined>, <undefined>
WARNING:tensorflow:From /home/user_li/.local/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py:4070: The name tf.nn.max_pool is deprecated. Please use tf.nn.max_pool2d instead.

2020-04-11 16:45:56.485911: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1412] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.
WARNING:tensorflow:From /home/user_li/.local/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py:422: The name tf.global_variables is deprecated. Please use tf.compat.v1.global_variables instead.

Dataset: RPI1807
Coding positive protein-rna pairs.

Coding negative protein-rna pairs.

Pos samples: 1801, Neg samples: 1436.

K-fold cross validation processes:

# ========== Fold 0 ==========

# Module Conjoint-CNN part #

Epoch 1/24
 - 4s - loss: 0.3599 - accuracy: 0.8478
Current loss: 0.5423307823546138, acc: 0.8919752836227417
Epoch 2/24
 - 1s - loss: 0.1532 - accuracy: 0.9467
Current loss: 0.5916879342661964, acc: 0.6033950448036194
Epoch 3/24
 - 1s - loss: 0.1048 - accuracy: 0.9614
Current loss: 0.6481671938557684, acc: 0.6018518805503845
Epoch 4/24
 - 1s - loss: 0.0829 - accuracy: 0.9676
Current loss: 0.5280121856449563, acc: 0.6496913433074951
Epoch 5/24
 - 1s - loss: 0.0853 - accuracy: 0.9668
Current loss: 0.7023663323050664, acc: 0.5879629850387573
Epoch 6/24
 - 1s - loss: 0.0676 - accuracy: 0.9776
Current loss: 0.9164928246151518, acc: 0.5694444179534912
Epoch 7/24
 - 2s - loss: 0.0580 - accuracy: 0.9803
Current loss: 0.6280492047008909, acc: 0.6188271641731262
Epoch 8/24
 - 1s - loss: 0.0640 - accuracy: 0.9799
Current loss: 0.8198991853306875, acc: 0.5972222089767456
Epoch 9/24
 - 1s - loss: 0.0553 - accuracy: 0.9811
Current loss: 0.7362000019645986, acc: 0.6342592835426331
Epoch 10/24
 - 1s - loss: 0.0533 - accuracy: 0.9799
Current loss: 0.4668149088313918, acc: 0.7453703880310059
Epoch 11/24
 - 1s - loss: 0.0487 - accuracy: 0.9826
Current loss: 0.35576998973610224, acc: 0.8626543283462524
Epoch 12/24
 - 1s - loss: 0.0443 - accuracy: 0.9834
Current loss: 0.26211990673600893, acc: 0.9320987462997437
Epoch 13/24
 - 1s - loss: 0.0469 - accuracy: 0.9830
Current loss: 0.2564059298163579, acc: 0.9135802388191223
Epoch 14/24
 - 1s - loss: 0.0505 - accuracy: 0.9795
Current loss: 0.17562148883294912, acc: 0.9537037014961243
Epoch 15/24
 - 1s - loss: 0.0463 - accuracy: 0.9815
Current loss: 0.16598785031632876, acc: 0.959876537322998
Epoch 16/24
 - 1s - loss: 0.0533 - accuracy: 0.9784
Current loss: 0.14235566735819535, acc: 0.9583333134651184
Epoch 17/24
 - 1s - loss: 0.0556 - accuracy: 0.9799
Current loss: 0.1377551966795215, acc: 0.9645061492919922
Epoch 18/24
 - 1s - loss: 0.0470 - accuracy: 0.9822
Current loss: 0.13861748516375635, acc: 0.9691358208656311
Epoch 19/24
 - 1s - loss: 0.0448 - accuracy: 0.9838
Current loss: 0.1311692446930173, acc: 0.970678985118866
Epoch 20/24
 - 1s - loss: 0.0457 - accuracy: 0.9838
Current loss: 0.12087944780050973, acc: 0.9722222089767456
Epoch 21/24
 - 1s - loss: 0.0400 - accuracy: 0.9849
Current loss: 0.12960734977214425, acc: 0.9691358208656311
Epoch 22/24
 - 1s - loss: 0.0442 - accuracy: 0.9815
Current loss: 0.11481868751623013, acc: 0.970678985118866
Epoch 23/24
 - 1s - loss: 0.0451 - accuracy: 0.9811
Current loss: 0.12951031823952994, acc: 0.9722222089767456
Epoch 24/24
 - 1s - loss: 0.0454 - accuracy: 0.9815
/home/user_li/.local/lib/python3.5/site-packages/keras/callbacks/callbacks.py:846: RuntimeWarning: Early stopping conditioned on metric `acc` which is not available. Available metrics are: loss,accuracy
  (self.monitor, ','.join(list(logs.keys()))), RuntimeWarning
/home/user_li/.local/lib/python3.5/site-packages/keras/callbacks/callbacks.py:707: RuntimeWarning: Can save best model only with acc available, skipping.
  'skipping.' % (self.monitor), RuntimeWarning)
Current loss: 0.12282926074148696, acc: 0.9722222089767456
Traceback (most recent call last):
  File "rpiter.py", line 421, in <module>
    model_conjoint_cnn.load_weights(model_weight_path)
  File "/home/user_li/.local/lib/python3.5/site-packages/keras/engine/saving.py", line 492, in load_wrapper
    return load_function(*args, **kwargs)
  File "/home/user_li/.local/lib/python3.5/site-packages/keras/engine/network.py", line 1221, in load_weights
    with h5py.File(filepath, mode='r') as f:
  File "/home/user_li/.local/lib/python3.5/site-packages/h5py/_hl/files.py", line 271, in __init__
    fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
  File "/home/user_li/.local/lib/python3.5/site-packages/h5py/_hl/files.py", line 101, in make_fid
    fid = h5f.open(name, flags, fapl=fapl)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2840)
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2798)
  File "h5py/h5f.pyx", line 78, in h5py.h5f.open (/tmp/pip-huypgcah-build/h5py/h5f.c:2117)
OSError: Unable to open file (Unable to open file: name = '/home/user_li/linqin_tmp/sourcecode/rpiter/result/rpi1807/rpi1807-20-04-11-16-45-06/weights.hdf5', errno = 2, error message = 'no such file or directory', flags = 0, o_flags = 0)

I also tried other datasets, but the errors were same.
what's the problem?
Best,
Ci

I'm very sorry for my late response.
The above problem is due to the package updates in Keras and tensorflow in these two years. In Keras callback function, the parameter name to get the train accuracy in each epoch has changed from "acc" to "accuracy". I have updated the codes to make the program compatible to this change. Please use the latest codes and the problem won't appear.
By the way, it should be pointed out that the underlying changes in DL packages could influence the program performance. Thus, please use the currently listed Python package versions in requirement.txt, which were tested on April 29, 2020. Anaconda is highly recommended to deploy the environment in your linux server.
If you still have any problems, don't hesitate to put them here.

@Pengeace
I sorry for replying so late for May Day holiday.  I tried new source code, and  results were mainly same with result of paper. But I found the folder name of NPInter dataset is wrong, maybe you need to corret it.
Thank you for your help this time.
Best,
Ci

Thank you for pointing out the file name error! It has been corrected.


Table on Meteor.user - search not working

Hi,
I have the following table:
if (!this.TabularTables) {
  this.TabularTables = {};
}

Meteor.isClient && Template.registerHelper("TabularTables", TabularTables);

TabularTables.Users = new Tabular.Table({
  name: "Users",
  collection: Meteor.users,
  columns: [
    {
      data: "createdAt",
      title: "CreatedAt"
    }, {
      data: "profile.firstName",
      title: "firstName"
    }, {
      data: "profile.lastName",
      title: "lastName"
    }
  ]
});

The table works awesomely fast, but as soon as I type something into the search field nothing is displayed any more.
Do you have any idea what the reason for this could be?
Cheers,
Gerwin

I'm experiencing the same issue on my site. If any columns have a property attached to the data object, then they are not searchable. For example:
{
id: '1q2w3e4r5t6y',
name: {
first: 'Jon',
last: 'Snow'
}
The id is searchable but the first and last names are not. I've tried commenting out some of cleanFieldName, which DID work - however the server keeps overwriting the file when I restart! :/

I'm trying to finish up a rewrite that will address this and all other outstanding issues.

@aldeed Looking forward to this feature working :smile: Let me know if you need help testing any code

1.0 is released and should fix this. Please see updated README for all features and options.

@aldeed woot! :metal:


fix ending QUICConnection with force: false

Description
While working on https://github.com/MatrixAI/Polykey/pull/609 I found the following problems.

When ending a connection with force: false any currently running streams will end with an error. The expected behaviour is that they finish gracefully.
If we end a connection with force: false we have no way to force the end after the fact. So if we wanted to gracefully end something at first but then need to force it to end afterwards, we have no way of doing this.

On top of fixes we need to expand the features of a connection slightly here.

Allow the ability to force close all streams at any time to allow skipping the graceful end of streams when ending the connection with force: false
when ending a connection with force: false we don't want any new connections to be started. Any new connections from either direction should be rejected.

Issues Fixed

No issues are directly fixed by this PR.
Related: https://github.com/MatrixAI/Polykey/pull/609

Tasks

[x] 1. When a connection is closed with force: false it should wait for all streams to gracefully end. Right now they throw an error.
[x] 2. When a connection is ending, forced or otherwise, all new streams should be rejected. when force: false we should allow all active streams to end gracefully but no new ones should be created from either direction.
[x] 3. When ending a connection with force: false we want the ability to force the end at any time. So we need a method of force closing all active streams at any time.

Final checklist

[x] Domain specific tests
[x] Full tests
[x] Updated inline-comment documentation
[x] Lint fixed
[ ] Squash and rebased
[ ] Sanity check the final build

Only task 1 needs to be addressed for https://github.com/MatrixAI/Polykey/pull/609. the rest are nice to have.

Only task 1 needs to be addressed for MatrixAI/Polykey#609. the rest are nice to have.

This PR is for all 3 tasks right?

Yes.

Ok, when a connection is stopping then any call to streamNew throws the ready error. This was already a thing. But now any new incoming stream is shut down with a code of 1.  this means that any remotely created stream will still be created, but any use of it will result in a error on that stream. There's no real way around this.
I don't like that it's a hard coded code of 1. Ideally the application can specify the code it wants for a rejected stream. Conversely, the code of 1 generally means generic or unknown error even on the application level. So it's kind of fine.
Thoughts?

It's fine to have a set of codes with some predetermined meaning.
We have transport codes and application codes.
Is this an application code? And then should the library default it? Should it be configurable? Make a judgement call here.

I've added a forceDestroyStreams method (name subject to change) to the QUICConnection, QUICClient and QUICServer. This allows you to cancel all active streams at any time. The main use for this is if we destroy any of these with force: false we can then later force it to finish destroying by destroying all the streams they're waiting for early.

I've added a forceDestroyStreams method (name subject to change) to the QUICConnection, QUICClient and QUICServer. This allows you to cancel all active streams at any time. The main use for this is if we destroy any of these with force: false we can then later force it to finish destroying by destroying all the streams they're waiting for early.

Why does each 3 need this method? Only QUICConnection needs to manage streams. And if it is not being called elsewhere, why factor it out of the relevant destroy or stop methods?

Do you want to squash some of the WIP commits?

I was going to squash this after any review changes were done.
Why does each 3 need this method? All 3 can be ended with force: false, in this case all 3 need a way to cancel all running streams if they want to upgrade from unforced end to a forced one.

Is there any way to centralise that logic to QUICConnection? I don't think it should be necessary to manage streams in the other ones?

The QUICConnection is the one cancelling the streams directly. The new methods in the server and client just call forceDestroyStreams for every connection it's managing. The methods could be called something else on the server and client.

This is just to destroy all streams while keeping the connection alive? No need to expose it. Why not keep it to the connection?

This is just to destroy all streams while keeping the connection alive? No need to expose it. Why not keep it to the connection?

It's mainly to allow you to force the server, client or connection to end now if it was waiting for streams to gracefully end during an unforced end. In reality it allows you to kill all active streams at any time.
It needs to be exposed on the client and server so we can force it to stop or destroy of we initially did an unforced stop or destroy.
Mainly needed by the server since you have direct access to the connection on the client but getting the connections on the server is a little more annoying.

After discussion.

forceDestroyStreams has been removed from the client and server.
forceDestroyStreams was renamed to destroyStreams.
It is only mean to be a debug method for the QUICConnection now. If you need to use it then you need to access the connection directly.
This is subject to further refactoring later.


Implement starkent_keccak

Refer utils.py in starknet_abi and add tests as well.

Pls assign

Hey @Rishikpulhani I ended up implementing it because I needed it for some other file. You can work on its tests in some other issue.

Ok sir


The major revision for v22.1 is the deprecation of ActionBarActivity.

my think use Taking its place will be AppCompatActivity.

Done!


Fix Alizer security vulnerabilities

Which area/kind this issue is related to?

/area alizer
Issue Description

When Alizer was migrated to Devfile (https://github.com/redhat-developer/alizer/issues/240), 3000+ vulnerabilities were fixed by updating all dependencies. The remaining alerts (https://github.com/devfile/alizer/security/code-scanning) need to fixed within the Alizer codebase.
Target date: July 11

PR opened and ready for review


Introduce authorizer & minor improvements

Changes

We introduce a new authorizer middleware that performs OAuth scope-based authorization.
We fix a problem where if a middleware throws an error, the validator middleware would obscure that and report it as an OAuth authentication problem.
We refactored a large part of the OAuth tests (boy scout rule).

Signed-off-by: Martin Aleksandrov<EMAIL_ADDRESS>

Coverage increased (+0.01%) to 90.905% when pulling 53044dc1e6ef5e46c736f25fbdbf3ac233645a8b on SAP:oauth_authorizer into 1f1dffd2ab3ff6e99147a111570cccfc2af41a85 on cloudfoundry-incubator:master.

Coverage increased (+0.01%) to 90.905% when pulling 53044dc1e6ef5e46c736f25fbdbf3ac233645a8b on SAP:oauth_authorizer into 1f1dffd2ab3ff6e99147a111570cccfc2af41a85 on cloudfoundry-incubator:master.


Fix a bug where last part of the key is discarded and replaced with default filename

Before 1.0.0, this line used to say
Some(name) if name.len() > 0 => {

With 1.0.0 it was changed to if name.is_empty() which caused the filename part of the path to be discarded instead of prepending it to PREFS_FILE_EXTENSION

I wasn't expecting any fails. Looks like something to do with app_dir. When test_save_load fails you can see it:
Err(Directory(Io(Error { repr: Os { code: 183, message: "Cannot create a file when that file already exists." } })))

Hahaaaa that is a terrible bug, whoops. Thanks for doing this.
As for the raciness, is there a way to make Cargo run tests in series rather than parallel? It would be nice not to glob all our tests together...

I realised it must be a race condition. I remove the second test in my fork and it got rid of the problem.
I don't think globing the test cases is a good idea either, it feels like just hiding the problem.
It might be possible to special case this using the error codes. It also feels quite std bug-worthy, "file already exists" doesn't feel like something DirBuilder should be returning.

There is a bug already opened for this https://github.com/rust-lang/rust/issues/33707.
I feel it's ok then to glob the test case for now and release a new version.
If that's ok with you I'll clean this up and make it use gen_sample_prefs again.

Sounds great, thank you! 😁
On Mon, Feb 6, 2017 at 6:45 PM Maciej Goszczycki<EMAIL_ADDRESS>wrote:

There is a bug already opened for this rust-lang/rust#33707
https://github.com/rust-lang/rust/issues/33707.
I feel it's ok then to glob the test case for now and release a new
version.
If that's ok with you I'll clean this up and make it use gen_sample_prefs
again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/AndyBarron/preferences-rs/pull/17#issuecomment-277884996,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADdko4PwpbdFeNfHkaX5y_Vv1WVxq1-Qks5rZ9rWgaJpZM4L42Hf
.

I think this looks fine

Wonderful, merging now. I'll publish 1.0.1 and yank 1.0.0 as soon as I get the chance.


[conflicts] Draft of the first tutorial

I have made a tutorial based on @Wikunia's post where he showcases this cool animation:

So I have made a step by step tutorial to make this animation. This is a draft of the tutorial, looking forward to your feedback. Thanks!

check #88 for the PR


Add row limit in Settings JSON

OS Info: Xubuntu 18.04

Hello!
First of all, I would like to say this is the best extension I've found so far for MySQL.
The only feature I miss is the same as the MySQL workbench, where you can limit the row count, not having to specify the LIMIT XX in every query.
Thank you :)

In fact, most clients will automatically add limit, but they hide it. In the next version, I will add an option to set the default limit size.

That would be perfect!
Thanks

2.3.7 has been add this feature.

Hey, Cweijan!
Not sure why, but it's not working here.
I've limited to 20 rows (screenshots below), and even though it's printing all 195 rows from the actor table (sakila).
Settings: http://i.imgur.com/6jUeU1M.png divided with results.
Settings.json also OK with ""vscode-mysql.defaultLimit": 20".
PS: all the other options work fine, like max table count.
Thank you for your quick response and for adding this amazing feature, btw :)

There is no limit to directly executing select, This needs improvement, please wait for the next version.

Version 2.3.12 has been auto add limit for select.

Thank you very much, @cweijan :+1: :100:


client character controller sticks to ground

only client character controller sticks to ground while it is moving and does not jump. server character controller is working.

works when stop input after jump


Viewport jump when clearing filter search

Description
Screen viewport bounces when user clears his filter search input
Impact
It's uncomfortable for user to interact with search field
Environment and steps to reproduce
Navigate to Search field when there are 10+ items on the list
Enter value
Clear the field
Expected behavior
Search field stays on the same place and nothing bounces

I guess this is different from https://github.com/kinvolk/headlamp/issues/593, but let's check out exactly what this means.


Add method to get open orders from 0x API

Related to #1663
In order to allow solvers to utilize 0x limit orders as liquidity our ZeroExApi needs to get extended.
Because the 0x endpoint to query those orders is paginated I added 2 functions. get_orders_with_pagination() retrieves a specific page of the results whereas get_orders() retrieves all orders (modulo some which don't pass a sanity check).
get_orders() uses get_orders_with_pagination() under the hood.
Test Plan
New (ignored) unit test which makes sure that deserializing the API responses works.

Codecov Report

Merging #1687 (f096d77) into main (7dd32c1) will decrease coverage by 0.18%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1687      +/-   ##
==========================================
- Coverage   65.74%   65.55%   -0.19%
==========================================
  Files         179      179
  Lines       35484    35583      +99
==========================================
  Hits        23328    23328
- Misses      12156    12255      +99

I used @vkgnosis idea for testing the pagination loop and used it as well to test retaining the valid orders.
This caused me to actually require 3 instances of #[derive(Derivative)] but I removed the other ones.


change the location of the .unittest-gtest subdirectory

Hello-
I notice that the .unittest-gtest subdirectory is opened in the source directory. I was wondering if it is possible to change this location and place it under the build location?
Thanks.

Hello-
I was wondering if you had a chance to think on this. Perhaps an option to pass in to provide a prefix to UNPACK_DIR?
Thanks,


Suggest improving the template for submitting issues

Electrifying project!
Improving the template for submitting issues can enhance the developer experience and improve community efficiency.

Thanks for your advice. We will update it.


"Create Notebook" button after /newNotebook does not work

Type: Bug
In Github Copilot Chat, ask @workspace /newNotebook predict iris species using online sklearn dataset and seaborn
The response is comming, but the Create Notebook button is not doing anyting
Extension version: 0.21.1
VS Code version: Code 1.94.1 (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
15.64GB (4.48GB free)

Process Argv
--remote=wsl+Debian --crash-reporter-id d48b4e35-b0e1-4008-8403-4807f860b107

Screen Reader
no

VM
40%

Item
Value

Remote
WSL: Debian

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
12th Gen Intel(R) Core(TM) i7-1255U (12 x 0)

Memory (System)
7.58GB (5.92GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
01bff139:31013167
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31150323
notype1:31151523
5fd0e150:31155592

It used to work in previous versions of VSCode, Chat and the Jupyter Notebook extension.

@markodraisma - Did you get any resolution for this?

@shubhnitb95 I have not yet received or found any resolution for this.

@markodraisma - Yeah, it's still not working, for me as well.

Hi, I can confirm this issue is still present in copilot-chat 0.21.2 and is reproducible across systems.
My system and extension information:

In the new 1.95 version of VS Code this issue seems to be resolved. I'm now able to use the /newNotebook command again.
@kbdharun @shubhnitb95 @mjbvz Is this true for you too? Than this issue can be closed.

In the new 1.95 version of VS Code this issue seems to be resolved. I'm now able to use the /newNotebook command again. @kbdharun @shubhnitb95 @mjbvz Is this true for you too? Than this issue can be closed.

Yep, can confirm the option works now after updating VSCode and the extension to the latest version.


Back to the original  position where I pressed the "ctrl+shift+left-click"

Hi,
I have a question,After I pressed "ctrl+shift+left-click"   to definition/declaration, How I original  position / line where I pressed the "ctrl+shift+left-click",
Thanks a lot

Use Sublime Text's shortcut ctrl+tab


Fix access to private static properties

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
n/a

Documentation
n/a

Why?
Using late static binding to access private static properties is wrong, as child classes are not allowed to access them. This would lead to a fatal error when using a child class.

Note that Scrutinizer knows about this kind of issues and reported it on your project already.

Thank you @stof.


Qrcode Version

Hi :-)
I'm very interested in your library. But for the same string, the QRcode generated by your library is in version 10 (= 57 columns/lines) although the old library I've been currently using (AwesomeQRCode) generates a version 7 (= 45 columns/lines).
I wonder why this difference ? is it a question of EC level used ?
If yes, would it be possible to make this level configurable in your library ?
Thank you for your answer

Hi,
Looking at your code, I think it would be very easy to add this function in QRCodeBuilder:
/** Error correction level used to generate QR code */
fun withErrorCorrectionLevel(level: ErrorCorrectionLevel): QRCodeBuilder {
errorCorrectionLevel = level
return this
}
And then use this errorCorrectionLevel new parameter in QrCode class instead of hard-coded ErrorCorrectionLevel.H :
/** The underlying [QRCodeProcessor] object that'll do all calculations */
val qrCodeProcessor: QRCodeProcessor =
QRCodeProcessor(data, errorCorrectionLevel, graphicsFactory = graphicsFactory)
/** Computed type number for the given [data] parameter */
val typeNum = QRCodeProcessor.typeForDataAndECL(data, **errorCorrectionLevel**).coerceAtLeast(6)

Unfortunately I can't build your project on my mac :-/ so if you mind adding this new errorCorrectionLevel customization it would be great.

Have a nice day


About the ALE settings

I have some questions in mind about the specific setup of the environment. I'm not sure did you check with the authors on these choice.

repeat_action_probability: The ALE Manual strongly suggests using the default 0.25. Is 0.0 a reasonable choice? Will 0.0 make it easier to learn?
treat_life_lost_as_terminal: This option would definitely make things much easier. Did the original paper use a similar setup?

Btw you're not using the frame_skip parameter anywhere but a magic number 4. You might want to fix that.
Great work!

I didn't check with the authors on my settings. I guess they used the same settings with their Nature paper of DQN, so I'm mimicking them. I agree that these settings make learning easier.

Thanks. So I just checked their alewrap and treat_life_lost_as_terminal seems like what they've always been using. Didn't find anything about the repeat_action_probability though.

repeat_action_probability is introduced recently (from ALE 0.5.0), after their DQN paper. So it should be turned off to reproduce their results. See the discussion below:
https://groups.google.com/forum/#!topic/deep-q-learning/p4FAIaabwlo

FYI, it is confirmed in two latest papers 1, 2 by @mgbellemare (author of ALE) that these two options have always been in easy-mode (as you did). He started to use hard-mode in these two papers.

Jumping in, in our latest paper [2 above] we found the life loss signal to be detrimental. The repeat action prob. affects the original DQN performance significantly, but more recent algorithms (such as Double DQN or our own) don't suffer so much from it.


Debug start/continue command leads to crash

Where can I find a log to send you?
Thanks.

Thank you, but could you elaborate? Does it happen every time? What OS are you using? You can also use lldb/gdb to generate a backtrace and paste it here.
Also, when it comes to lldb that juCi++ uses, try to reproduce the steps using lldb manually. On all occasions so far, the crash happens in lldb.

Start/continue without any options crashes.
gdb output for same scenario:
Starting program: /home/amit/seven-bridges-genomics/graph-alignment/build/debug/aligner
warning: the debug information found in "/lib64/ld-2.19.so" does not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
PARSE ERROR:
Required arguments missing: reference, fastq, output
Brief USAGE:
/home/amit/seven-bridges-genomics/graph-alignment/build/debug/aligner
[--genotype_tags] [-g <.7bg>] [-G
<.7bg>] -f <.fasta> [-v
<.vcf/.bcf/.vcf.gz>] -q <.fastq>
[-Q <.fastq>] -o <.bam> [-i] [-P
] [-I ] [-S ] [-E
] [-O ] [-x ] [-=
] [--thread_buffer_size ]
[-t ] [--debugging_tags]
[--no_local_aligner] [-M] [-l
] [-w ] [-m <{0-20}>]
[--hash_short_list ]
[--hash_table_size_log2 <{16-28}>]
[--hash_block_step <{1-14}>]
[--hash_block_size <{8-14}>] [-n
] [-N ] [--] [--version]
[-h]
For complete USAGE and HELP type:
/home/amit/seven-bridges-genomics/graph-alignment/build/debug/aligner --help
[Inferior 1 (process 5532) exited with code 01]

Try the same but with lldb instead of gdb please.

Removing any optimisation flags like -O3 when running debugging can also help work around lldb crashes. This is not a juCi++ issue however.

Closing this, but feel free to reopen if it's not an lldb issue.


Blacklisted links are saved

If a regular message arrived, it does not check for blacklist before it saves the link.

False alarm


sort

Can the latest log be topped?

@aicareles Not as of now. The new logs are always appended at the end of the list.

@aicareles Not as of now. The new logs are always appended at the end of the list.
If there are too many logs, it may not be easy to spot at the end of the list


gh-954 - renamed JsonUtil to JsonAssert

Created a JsonUtil class to compare json objects.
This is required for gh-954. The rest of the changes for gh-954 will come later.

Codecov Report

Merging #1023 into develop will decrease coverage by 0.31%.
The diff coverage is 40.74%.

@@              Coverage Diff              @@
##             develop    #1023      +/-   ##
=============================================
- Coverage      62.06%   61.75%   -0.32%
- Complexity      1103     1107       +4
=============================================
  Files            512      513       +1
  Lines          15315    15342      +27
  Branches        1744     1750       +6
=============================================
- Hits            9505     9474      -31
- Misses          5066     5116      +50
- Partials         744      752       +8

Impacted Files
Coverage Δ
Complexity Δ

...n/java/uk/gov/gchq/gaffer/commonutil/JsonUtil.java
40.74% <40.74%> (ø)
4 <4> (?)

...chq/gaffer/rest/mapper/GenericExceptionMapper.java
20% <0%> (-80%)
0% <0%> (ø)

...gov/gchq/gaffer/rest/service/OperationService.java
0% <0%> (-68.52%)
0% <0%> (ø)

...v/gchq/gaffer/rest/factory/UnknownUserFactory.java
66.66% <0%> (-33.34%)
0% <0%> (ø)

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 b0a3deb...e7196d3. Read the comment docs.

@m55624 thanks for adding the null test and fixing the bug. Looks good.


Added maximumBy and minimumBy

I recently needed the functionality of Data.List.maximumBy. I actually got away with using tuple's Ord instance instead. But, I think it would be nice to have maximumBy and minimumBy in here.

Yeah, this is a great contribution.  Thank you!

Do you have any other changes in mind or is it alright if I go ahead and upload this to Hackage?

No, currently I don't have anything else in mind. It would be great to have the new version Hackage, thanks!

Alright, this is up on Hackage as foldl-1.1.6

Great! Thanks for letting me know.


How to print different message to different file during simulation?

I have added the UART scala code from the sifive repo to the rocket-chip. In the code, there is a printf() to output the sending char during simulation:
printf("%c", io.in.bits)

At the same time, I hope that the rocket core will output execution logs to help me for debugging:
printf("C%d: %d [%d] pc=[%x] W[r%d=%x][%d] R[r%d=%x] R[r%d=%x] inst=[%x] DASM(%x)\n",
...

What troubles me is that these two printf() will output to screen at the same time during simulation. This makes messages sent by UART interrupted by a large number of logs. I hope the generated code can separate the output of these two printf(). For example, the execution logs will be printed to a file log.txt, while the UART char is still output to the screen. What should I do?
In fact, I opened an issue #428 for the same trouble last week, but it was misunderstood and closed, and I have not got the solution yet. I hope I have made this issue clear this time. Thanks!

FWIW, a non-solution is to just use a disciplined printf format for what you want to add.
All the rocket log printfs start with C so just inverting a match on that will dump everything else.
grep -v ^C rocket.log > uart.txt
grep    ^C rocket.log > rocket.txt

This can obviously get overloaded if you have other printfs that start with C, but as long as you're in control of the printfs (e.g., printf("[sashimi-yzh] ...", ...) you can use a unique printf that won't conflict with rocket.

@seldridge As discussed in issue #428, there does not exist a solution at this time. So thank you for the non-solution!

Ultimately, this is a request for a logging library that dumps prints in simulation.
Renamed issue.


Refactor JS for wayf

This PR is becoming way to big so finishing up here, will make separate PR's for all JS functionality that's still outstanding.  In this PR is the following:

Some refactoring here to make code more readable.  This is mainly getting rid of the className.replace(class, '') by using the classList.add/remove interface.  It's faster & more readable & less error-prone.
Some moving of initialization logic to the class it belongs to, mostly IdpPicker.
Utilize the initializePage function to render the JS logic for the WAYF
Duplicate all WAYF module files because the JS for skeune / material is too divergent.  Mainly because the material JS is very tightly coupled with the creation & structure of the html.  But also because there are no modals in skeune.
Add a hidden class to all sections but the "remaining IDP" section (aka the normal WAYF finder)
Ensure that the  "previous selection" list is shown if there is one.
Refactor the idp to contain the form & remove the link.  This is not yet complete, but until i start tackling the JS that belongs with it (which should be first thing tomorrow) i'm leaving it as is for now.  I also refactored the templates a bit to make it more readable / self-contained.
Add keyboard / mouse behaviour for the add account button.
Add keyboard / mouse behaviour for the disable / delete button.
Add keyboard / mouse behaviour for the "trashcan" button on an idp in the previous selection list.  It doesn't yet remove from the cookies because no cookie functionality is there yet (that's for after i add the idp selection functionality, first thing in the morning in it's own branch).

Good question.  I've not touched the integration tests for the moment, but all the skipped ones we should definitely fix.  I was planning on doing that afterwards, but probably better to add tests as we add features indeed.  I can update the test along with the next PR (selecting an idp) to avoid merge/rebase conflicts.

I've given this changeset a functional test spin. I noted that the WAYF is no longer functional.  No hard feelings there. But I assume successive PR's will take care of that.
Regarding test coverage. Feel free to add tests on your next PR(s). Or even at the end. My experience is that working in an 'agile' TDD manner works best for me. As this forces me to write my code in a test friendly manner.
Reviewing this PR was not difficult at all, thanks to your habit of putting together small coherent commits. Thanks again for that!


add support for authorizing subresources

Updates the APIRequestInfoResolver to handle subresources.
/cc @smarterclayton @erictune

Comments and TODOs added. I'll add the issue when it looks like this will get merged.

@smarterclayton as per our discussion, subresources on a namespace are now considered to be resources in their own right by authorizers.

LGTM

This is LGTM.  Any other comments from the other reviewers?


test: add orchestrator tests

Overview

Depends on https://github.com/celestiaorg/orchestrator-relayer/pull/133 and https://github.com/celestiaorg/orchestrator-relayer/pull/115
Closes https://github.com/celestiaorg/orchestrator-relayer/issues/51
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #134 (696b243) into main (74eb1d9) will increase coverage by 4.93%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
+ Coverage   43.27%   48.21%   +4.93%
==========================================
  Files          15       15
  Lines         952      952
==========================================
+ Hits          412      459      +47
+ Misses        491      438      -53
- Partials       49       55       +6

Impacted Files
Coverage Δ

orchestrator/orchestrator.go
15.76% <0.00%> (+15.76%)
:arrow_up:

orchestrator/retrier.go
22.22% <0.00%> (+22.22%)
:arrow_up:

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


ARTEMIS-457 upgrade JGroups

Some kind of memory problem on the Apache CI infrastructure prevented the PR build from running.


Feature: Add CIDR detection

Hi!
Currently DataSurgon can't handle CIDR-ranges:
Example:

<IP_ADDRESS>

<IP_ADDRESS>/10

<IP_ADDRESS>/30

<IP_ADDRESS>/16

<IP_ADDRESS>/4

2002::1234:abcd:ffff:c0a8:101

2002::1234:abcd:ffff:c0a8:101/64

2001:db8:3333:4444:5555:6666:7777:8888

2001:db8:3333:4444:5555:6666:7777:8888/64

Result
❯ ds -C -f test.txt
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888

(Also, by testing this I found a bug where it doesn't detect double colon in ipv6 urls) 😁
https://www.ibm.com/docs/en/i/7.5?topic=concepts-ipv6-address-formats

Hi,
Thanks! I will look into this....
Best,
Drew

Hi,
Is this the output you were looking for?
Contents of data.txt

<IP_ADDRESS>

<IP_ADDRESS>/10

<IP_ADDRESS>/30

<IP_ADDRESS>/16

<IP_ADDRESS>/4

2002::1234:abcd:ffff:c0a8:101

2002::1234:abcd:ffff:c0a8:101/64

2001:db8:3333:4444:5555:6666:7777:8888

2001:db8:3333:4444:5555:6666:7777:8888/64

2001:db8:3333:4444:5555:6666:7777::/64

Results
dalleman@drew-ubuntu:~/Projects/Software/DataSurgeon/target/release$ ./ds -Cf data.txt
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>/10
ip_address: <IP_ADDRESS>/30
ip_address: <IP_ADDRESS>/16
ip_address: <IP_ADDRESS>/4
ipv6_address: 2002::1234
ipv6_address: 2002::1234
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888/64
ipv6_address: 2001:db8:3333:4444:5555:6666:7777

Best,
Drew

Don't bother looking into it, your projects don't follow GitHub's Terms of Service and has been reported with the relevant information contained.

@Defirence I saw your now deleted comment. This project is not malicious and has various practical uses. Your Github ticket will be ignored.

Hi,
@borestad I think I got the Regex correct how does this look?
drew@ubuntu:~/Projects/Software/DataSurgeon$ ./target/release/ds -f target/release/data.txt -C
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>/10
ip_address: <IP_ADDRESS>/30
ip_address: <IP_ADDRESS>/16
ip_address: <IP_ADDRESS>/4
ipv6_address: 2002::1234:abcd:ffff:c0a8:101
ipv6_address: 2002::1234:abcd:ffff:c0a8:101/64
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777
Best,
Drew Alleman

Hi @Drew-Alleman !
Looks great. 👍
I wonder .... if one would like to split these into multiple groups later in another version?
like:
ip_address: <IP_ADDRESS>
ip_cidr: <IP_ADDRESS>/10
ip_cidr: <IP_ADDRESS>/30
ip_cidr: <IP_ADDRESS>/16
ip_cidr: <IP_ADDRESS>/4
ipv6_address: 2002::1234:abcd:ffff:c0a8:101
ipv6_cidr: 2002::1234:abcd:ffff:c0a8:101/64
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777

... but for now, this is excellent! I tried to write/improve the regexp myself yesterday evening, but was apparently to tired.
Great work! 😊

Hi,
Glad to hear it works for you. I am going to update the IPV4 and IPV6 regex for what I have now.
drew@ubuntu:~/Projects/Software/DataSurgeon$ ./target/release/ds -f target/release/data.txt -C
ip_address: <IP_ADDRESS>
ip_address: <IP_ADDRESS>/10
ip_address: <IP_ADDRESS>/30
ip_address: <IP_ADDRESS>/16
ip_address: <IP_ADDRESS>/4
ipv6_address: 2002::1234:abcd:ffff:c0a8:101
ipv6_address: 2002::1234:abcd:ffff:c0a8:101/64
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777:8888
ipv6_address: 2001:db8:3333:4444:5555:6666:7777

I might create a plugin for extracting CIDR information specifically.
Best,
Drew Alleman

This sounds great! :)

Hi,
I will try to get this rolled out this weekend.
Best,
Drew


On Alpine we must have a reasonable stack size

Threads created with default stack size are fine for glibc builds, but alpine creates a very small stack and so we are likely to overflow.  This makes it 8MB like what we set for our server threads, and is the same as the default on glibc.

Posterity note: implements a similar fix as #268. LGTM 👍


[Toast] Allow children in Viewport types for asChild composition

Fixes #1284

The same issue likely exists for NavigationMenu

The same issue likely exists for NavigationMenu

@andy-hook, feel free to raise a separate PR is so then 👍


Error while exporting .ply and .obj files.

Describe the bug
Error while exporting the .ply files for the individuals in the scene. Same error for the .obj files.
Steps to Reproduce
Exporting the helloworld scene to ply with command
What version of the code were you using?
Tell us the commit & commit hash from git log
What command did you run?
python -m infinigen.tools.export --input_folder infinigen/outputs/hello_world/fine --output_folder outputs/my_export -f ply -r 1024 --individual -v
What are your FULL output logs?
Read blend: "infinigen/outputs/hello_world/fine/scene.blend"
INFO:root:Exporting to directory export_folder=PosixPath('outputs/my_export/scene.blend')
INFO:root:---------------------------
INFO:root:atmosphere
INFO:root:Mesh hidden from render, skipping ...
INFO:root:---------------------------
INFO:root:atmosphere_fine
Traceback (most recent call last):
File "/home/lastbasket/miniconda3/envs/infinigen/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/lastbasket/miniconda3/envs/infinigen/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "infinigen/infinigen/tools/export.py", line 632, in
main(args)
File "infinigen/infinigen/tools/export.py", line 591, in main
folder = export_scene(
File "infinigen/infinigen/tools/export.py", line 472, in export_scene
result = export_curr_scene(folder, **kwargs)
File "infinigen/infinigen/tools/export.py", line 533, in export_curr_scene
bake_scene(
File "infinigen/infinigen/tools/export.py", line 424, in bake_scene
bakeVertexColors(obj)
File "infinigen/infinigen/tools/export.py", line 165, in bakeVertexColors
bpy.ops.object.bake(type='DIFFUSE', pass_filter={'COLOR'}, target ='VERTEX_COLORS')
File "/home/lastbasket/miniconda3/envs/infinigen/lib/python3.10/site-packages/bpy/3.6/scripts/modules/bpy/ops.py", line 113, in call
ret = _op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.bake.poll() failed, context is incorrect
If this is your first time running Infinigen, what are the full install logs?**
Run pip install -vv -e . > logs.txt 2>&1 and send logs.txt as an attachment.
Platform

OS & OS Version: Ubuntu 22.04
GPU (?) : 4090
GPU Driver Version (?) : CUDA 11.8
RAM (GB):

Additional context
Add any other context about the problem here.

It seems like the problem of https://github.com/princeton-vl/infinigen/blob/f98b9575c73c322f1cbcc2dd48d26bbe8d6239f6/infinigen/tools/export.py#L523

However, I cannot find the vertex color information in the exported .ply and .obj.

The bug is indeed caused by some of the objects being set to invisible in the blend file, which requires slightly different handling of visibility while baking. I have a patch that fixes this that will likely be out soon.


The disk space is enough, but I got "service not available now, maybe disk full" error after i run the program some times

BUG REPORT

I've installed the rocketmq in windows, follow the page https://www.jianshu.com/p/4a275e779afa, the nameserver, broke, and rocketmq console hava started rightly
I've run a simple producer-consumer example, follow the page https://blog.csdn.net/zhglance/article/details/54962870, I run the RocketMQConsumerTest firstly, and then I run the RocketMQProducerTest, I can get the right result.
I stop the RocketMQProducerTest and I start it again(the RocketMQConsumerTest is still running)  , I get the error as below:

org.apache.rocketmq.client.exception.MQClientException: Send [3] times, still failed, cost [402]ms, Topic: MQ-MSG-TOPICS-TEST, BrokersSent: [PC-20170208IHWA, PC-20170208IHWA, PC-20170208IHWA]
See http://rocketmq.apache.org/docs/faq/ for further details.
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendDefaultImpl(DefaultMQProducerImpl.java:544)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1069)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.send(DefaultMQProducerImpl.java:1023)
at org.apache.rocketmq.client.producer.DefaultMQProducer.send(DefaultMQProducer.java:214)
at testrocketmq.RocketMQProducer.send(RocketMQProducer.java:47)
at testrocketmq.RocketMQProducerTest.main(RocketMQProducerTest.java:22)
Caused by: org.apache.rocketmq.client.exception.MQBrokerException: CODE: 14  DESC: service not available now, maybe disk full, CL:  0.97 CQ:  0.97 INDEX:  0.97, maybe your broker machine memory too small.
For more information, please visit the url, http://rocketmq.apache.org/docs/faq/
at org.apache.rocketmq.client.impl.MQClientAPIImpl.processSendResponse(MQClientAPIImpl.java:551)
at org.apache.rocketmq.client.impl.MQClientAPIImpl.sendMessageSync(MQClientAPIImpl.java:353)
at org.apache.rocketmq.client.impl.MQClientAPIImpl.sendMessage(MQClientAPIImpl.java:335)
at org.apache.rocketmq.client.impl.MQClientAPIImpl.sendMessage(MQClientAPIImpl.java:298)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendKernelImpl(DefaultMQProducerImpl.java:696)
at org.apache.rocketmq.client.impl.producer.DefaultMQProducerImpl.sendDefaultImpl(DefaultMQProducerImpl.java:463)
... 5 more
I've installed the rocketmq in d disk, the total space is 61.7G, and the left space is 29.4G, I've checked the error in google, but all they say is that the space is not enough, I doubt about it as I've almost 50% space left, and if the space is not enough, why I can get the right result first time
And I have tried that, If I restart the broker, the program can run rightly again for about 5 or 6 times, and then the error happen again

free -g , memory check ?

free -g , memory check ?

I've pointed out that, I'm running in windows, not linux

May I ask if your problem has been solved? I have the same test problem as you

free -g , memory check ?

I've pointed out that, I'm running in windows, not linux

me too, i also install in win10, it also exist this problem ,  i want to handle this problem ,but  it isn't works . please  tell me how to resolve it ? thanks

i have the same problem too, run in win10, rocketmq version : 4.5.2

We will try to reproduce the above problem on Windows. Can you provide some server-side logs?

This question still alive and haven't been resolved yet.......

you just do that:

mqbroker.cmd -c  broker.conf ,  borker.conf in ROCKETMQ_HOME/conf
in broker.conf, you can set diskMaxUsedSpaceRatio = 99,  the default value is 75.

and i have a question, in  class MessageStoreConfig,  the property diskMaxUsedSpaceRatio is not decorated by @ImportantField.
what's means @ImportantField? i just find some code:
        if (onlyImportantField) {
                        Annotation annotation = field.getAnnotation(ImportantField.class);
                        if (null == annotation) {
                            continue;
                        }
                    }

                    if (logger != null) {
                        logger.info(name + "=" + value);
                    } else {
                    }
                }
            }

just for log? i dont' know.

Can you provide broker logs and broker config? And what version of RocketMQ do you use?
Maybe you set your store path to C:\ and C:\ is almost full.
The config diskMaxUsedSpaceRatio indicates RocketMQ's max disk usage roatio, which default is 75.
Check your store path config and if the store disk is almost full

you just do that:

mqbroker.cmd -c  broker.conf ,  borker.conf in ROCKETMQ_HOME/conf
in broker.conf, you can set diskMaxUsedSpaceRatio = 99,  the default value is 75.

and i have a question, in class MessageStoreConfig, the property diskMaxUsedSpaceRatio is not decorated by @ImportantField. what's means @ImportantField? i just find some code:
        if (onlyImportantField) {
                        Annotation annotation = field.getAnnotation(ImportantField.class);
                        if (null == annotation) {
                            continue;
                        }
                    }

                    if (logger != null) {
                        logger.info(name + "=" + value);
                    } else {
                    }
                }
            }

just for log? i dont' know.

I guess the @ImportantField is for logging important fields.
when calling MaxAll.printObjectProperties(final InternalLogger logger, final Object object, final boolean onlyImportantField), if you set onlyImportantField as true, it will only log the @ImportantField annotated fields of the object

meet the same problem in win 10

meet the same problem in centos. & 4.2.0 version


Details about the pooled embedding for SDXL

Hi, nice work!
I'm trying to reimplement ELLA on SDXL, and get confused about the pooled_prompt_embedding.
The original SDXL:
The output of SDXL text encoder comes from 2 CLIP text encoders and concatenated along the channel dimension, while the pooled_prompt_embedding only comes from the second one. The size of text embedding is 1772048 and the size of pooled_embedding is 1*1280.
It seems straightforward to build connectors that align with the size of text embedding. However, the pooled_prompt_embedding seems to be a special operator in SDXL structure. It would be very helpful if details about the pooled_prompt_embedding could be disclosed!

we use AttentionPool to convert 77x2048 tensor to 1x1280

Thanks. It helps!

Hi, It seems that PerceiverResampler is able to do that by providing num_latents=1.
Do you agree?
Additionally I guess that the pooling operation should have much less parameters since it's working on the output, i.e. the encoder_hidden_states which have gone a lot of processing.
Do you agree? :)

In my implementation, I pick the last latent's output as the pooled embedding, which is theoretically equal to AttentionPool, I guess.
And also I index the first 1280 channels out of the 2048 channels, to match the dimensions of SDXL. This line generate pooled embedding:
pooled_embedding = embedding[:, -1, :1280]
My model converges with this implementation. However, a quick train with the SAM1b data from PixArt doesn't yield good prompt following results. Perhaps a re-captioning is needed.

I pick the last latent's output as the pooled embedding,

Thanks for your explanation. So your pooled embedding directly comes from T5XL + AttentionPool?

@jmliu88 Did you have any luck with ELLA for SDXL?


C#: Make Grpc.Core nuget slimmer by moving mobile support to Grpc.Core.Xamarin package

Based on https://github.com/grpc/grpc/pull/24378.
Turns out most of the size of the Grpc.Core package are the prebuilt native libraries for mobile (android, ios, for ARM processors). At the same time, the iOS and Android support for Xamarin and Unity is still advertised as "experimental".
Unity doesn't use the nuget package at all (there is a separate zip file that is used for Unity), so there is not need to include the mobile libraries because of Unity.
For Xamarin, we can move the native libraries for mobile into a separate new package (Grpc.Core.Xamarin), where the size won't matter as much and including one more package in the projects seems easy enough for existing users of gRPC C# on Xamarin (we actually don't know how many there are).

adhoc package build: https://g3c.corp.google.com/results/invocations/5a8eb25b-7d9d-4703-86ba-e59594c27340/targets

adhoc packages:
https://storage.googleapis.com/grpc-testing-kokoro-prod/test_result_public/prod/grpc/core/master/windows/grpc_build_packages/14217/20201009-111715/github/grpc/artifacts/csharp_nugets_windows_dotnetcli.zip
Grpc.Core is now 36MB (before it was 203MB) and the new Grpc.Core.Xamarin is 137MB.
Distribtests are green: https://sponge.corp.google.com/target?id=a9a309a8-0561-45b5-ab85-d0d19763b7cd&target=grpc%2Fcore%2Fexperimental%2Fgrpc_distribtests_multiplatform&searchFor= (but Xamarin example needs to be tested manually).

CC @jskeet

I still need to test whether the new Grpc.Core.Xamarin package would work fine.

So far the Grpc.Core.Xamarin package doesn't seem to work with our example project - I'm still trying to find a way to fix it.
I also realized there's another problem - if the Grpc.Core.dll assembly and grpc_csharp_ext native library live in two different packages, it's difficult to make sure that the two packages will always be the same version - but if they are not, it can lead to Grpc.Core crashing etc (= very bad).

Another adhoc run: https://g3c.corp.google.com/results/invocations/febbc281-03c6-4b8b-977a-b88d795e2623/targets

Another adhoc run: https://g3c.corp.google.com/results/invocations/57819ff5-8f7b-4a07-bb0f-a1868262fb20/targets

After fixing the Grpc.Core.Xamarin.targets file name, Grpc.Core.Xamarin package is working well for me (I am able to run it with our example project).
The remaining part is to update the documentation and figure out how to ensure that the  Grpc.Core and Grpc.Core.Xamarin will always be at the same version (out of sync versions can and probably will lead to crash!).

Another adhoc distribtest: https://g3c.corp.google.com/results/invocations/7871e63d-bb9c-43bf-a8be-d3c059d94dab/targets

Based on my testing, the new Grpc.Core.Xamarin package now seems to work fine.
I solved the problem of ensuring Grpc.Core and Grpc.Core.Xamarin to be exactly the same version by mentioning that explicitly in the documentation (since our Xamarin support is marked as experimental, this is perhaps not too bad and I wasn't able to figure out anything better).
As pointed out above, the size reduction in Grpc.Core is very significant: Grpc.Core is now 36MB (before it was 203MB), so I think this PR is very much worth doing.

@apolcyn  this is now ready for review. Note that the first few commits are from https://github.com/grpc/grpc/pull/24378 (IMHO it make sense to also remove the x86 artifacts from Grpc.Core while we're at it).

@jskeet  do you have any opinion on the approach I took (especially the problem of enforcing that Grpc.Core and Grpc.Core.Xamarin are always at the same version).

CC @JamesNK  @JunTaoLuo  in case you have opinions.

@jskeet do you have any opinion on the approach I took (especially the problem of enforcing that Grpc.Core and Grpc.Core.Xamarin are always at the same version).

I haven't had a chance to review the details yet - I'll look tomorrow.

I've rebased this after merging https://github.com/grpc/grpc/pull/24378.
Another adhoc distribtest run, just to be sure:
https://g3c.corp.google.com/results/invocations/ecb54cfd-83b0-44db-8d27-246d885a4209

Bazel test failures are infrastructure failures - I'll investigate separately

@jskeet  do you think it's fine fine to merge as is or should I spend more time trying to figure out a way for stricter version enforcement?

Personally I'd be okay with it as-is, but hope to improve the strictness in a future release - and put that in the release notes.

I'll go ahead with this PR because it make Grpc.Core much more compact for most users and still provides a reasonably good experience for Xamarin users. I hope in the future I can improve on the version check (Grpc.Core version strictly equal to Grpc.Core.Xamarin) - or perhaps someone from community can help with that.

For Xamarin, we can move the native libraries for mobile into a separate new package (Grpc.Core.Xamarin), where the size won't matter as much and including one more package in the projects seems easy enough for existing users of gRPC C# on Xamarin (we actually don't know how many there are).

Just catching up on Nuget updates, and wanted to say that while our numbers may be small, there are some commercial apps using gRPC in Xamarin 😄


Intermediate format missing input layer making some layer types unusable as first layer

Currently the keras frontend is intentionally removing the input layer as it didn't provide any required attributes for the tested networks.

However, some layer types, e.g., AveragePooling2D, don't expose the batch_input_shape parameter leading to missing shape information of the expected input tensor (when using these types of layers as the first layer).
This could e.g. be resolved by incorporating the input layer into the intermediate format. This would probably require additional changes in the GCC backend.

Hi @TerrestrialEclipse,
thank you for contributing to the project and sorry for my delayed response. I agree with your idea of incorporating the input layer into the intermediate format. This should not be to hard since the intermediate format can contain any values as long as they follow the specified key structure.
This change would result in adjustments in the keras frontend as well as the gcc backend (and the utils class), I think.
I can look into that but due to other projects I'm working on I will have to delay this to the end of october, I think. Does this affect your fork and does this fit to your schedule? Let me know and we will figure things out!

Hi Philipp,
Thanks for your response. My fork would have to be slightly adapted. But that’s fine and fits well into my schedule; it is not criticial.
Best regards
Benjamin Hadwiger
Von: Philipp @.>
Gesendet: Montag, 4. Oktober 2021 21:19
An: pg020196/Neural-Network-Translator @.>
Cc: Benjamin Hadwiger @.>; Mention @.>
Betreff: Re: [pg020196/Neural-Network-Translator] Intermediate format missing input layer making some layer types unusable as first layer (#142)
Hi @TerrestrialEclipsehttps://github.com/TerrestrialEclipse,
thank you for contributing to the project and sorry for my delayed response. I agree with your idea of incorporating the input layer into the intermediate format. This should not be to hard since the intermediate format can contain any values as long as they follow the specified key structure.
This change would result in adjustments in the keras frontend as well as the gcc backend (and the utils class), I think.
I can look into that but due to other projects I'm working on I will have to delay this to the end of october, I think. Does this affect your fork and does this fit to your schedule? Let me know and we will figure things out!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pg020196/Neural-Network-Translator/issues/142#issuecomment-933780693, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUUXGXGESVFMR35ZPAGQS7TUFH4YNANCNFSM5EWD2KBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @pg020196
Thanks for your response. My fork would have to be slightly adapted. I will adapt the c_sharp backend once the intermediate format is adapted.


Fix simulcast for firefox

This is a patchset which at least improves using webrtc-rs on a SFU with simulcast and firefox as a client
I found that the simulcast example didn't work for Firefox. It might not really work now either, but this should be a step on the way.
Please let me know what you think :)

Ping @rainliu
Please leave some feedback on what you think about this. Thanks!


feat!: requests now try both DNS and IP, using whichever responds first

When running on non GCP environment, isAvailable() had two significant issues:

we were not properly catching timeout exceptions, causing exceptions to bubble all the way to the user.
a 3s timeout makes the cold-start time, even when an exception isn't bubbling, painful.

This PR addresses 1. by properly detecting timeout issues, and treating this the same as ENOENT or ENOTFOUND.
It addresses 2. by attempting both http://metadata.google.internal. and http://<IP_ADDRESS>, why?

when running in a non-GCP environment http://metadata.google.internal. fails fast.
when running in a GCP environment, there are some cases where http://<IP_ADDRESS> is significantly faster than DNS.

Do we allow writes to metadata? AFAICT we only seem to do GET requests, so parallel requests (and preexisting restries) should be safe, but worth double checking.

@ofrobots we only perform GET requests:
    const res = await fastFailMetadataRequest<T>({
      url: `${BASE_URL}/${type}${property}`,
      headers: Object.assign({}, HEADERS, options.headers),
      retryConfig: {noResponseRetries},
      params: options.params,
      responseType: 'text',
      timeout: 3000,
    });    const res = await fastFailMetadataRequest<T>({
      url: `${BASE_URL}/${type}${property}`,
      headers: Object.assign({}, HEADERS, options.headers),
      retryConfig: {noResponseRetries},
      params: options.params,
      responseType: 'text',
      timeout: 3000,
    });

:point_up: we don't allow method to be set in metadataAccessor, and all tests are indicative of the fact that we only support GETs.

fixes: https://github.com/googleapis/nodejs-logging-bunyan/issues/354, https://github.com/googleapis/gcp-metadata/issues/238


feat: add progress reporting to Sinkhorn

Hi,
Following https://github.com/ott-jax/ott/issues/210, here is a PoC for adding progress report to various solvers in OTT-jax. This PR focuses first on the Sinkhorn solver, but LRSinkhorn and others can follow if all goes fine.
How a user uses it
A user who wants to benefit from this feature simply needs to provide a callback function to the sinkhorn.Sinkhorn(progress_fn=myfunc). The callback func signature should be
def progress_fn(status: Tuple[jax.Array, Optional[jax.Array], Optional[jax.Array]], *args) -> None:

This callback function can do whatever side effects the user wants, such as printing or updating a tqdm progress bar.
How it works
The user provided function is provided to the Sinkhorn initializer and stored in the instance, and gets called on each Sinkhorn iteration via the dedicated jax host_callback mechanism (see here).
Examples
Here is a very basic example:
def progress_fn(status: Tuple[jax.Array, Optional[jax.Array], Optional[jax.Array]], *args) -> None:
    """
    Report progress.

    Args:
        status: tuple describing the current iteration number wrapped in a jax.Array,
            the optional total number of iterations wrapped in a jax.Array, and an array
            of errors.

    For iterative algorithms, the actual number of iterations needed to reach convergence
    is unknown beforehand. Depending on the use case, the value may be represented as None
    or have a default value.

    """
    iteration, total_iter, error = status
    iteration = np.array(iteration).sum()

    if error is not None:
        error = np.array(error).ravel()[-1]
        pbar.set_description_str(f"error: {error}")

    if total_iter is not None:
        total_iter = np.array(total_iter).sum()
        pbar.total = total_iter

    pbar.update()

    # alternatively:
    # print(f"Iteration {iteration} / {total_iter}")

and here is how it looks like at the call site:
from tqdm import tqdm
with tqdm() as pbar:
    out_sink = jax.jit(sinkhorn.Sinkhorn(progress_fn=progress_fn))(lin_p)

As @marcocuturi explained, instead of the default function being None, we could provide a default function that prints.

I can also update the callback for the Neural OT in #219 to be consistent with the final version of this sinkhorn progress report. It's currently:
https://github.com/ott-jax/ott/blob/0bf2467ce8cba7ea166c72699f14bfd725e277e1/src/ott/solvers/nn/neuraldual.py#L245

Thanks @bamos! I had missed this. Yes, it would be great to unify this kind of mechanics after we settle on some form we are happy with. Cheers

if there are prints, we only need to print when iteration % inner_iterations ==0.  Is there any way to print in-place?

Yes, I'd like that too. I gave it a quick look, and observed that Jax uses the string.Formatter. To my knowledge, printing in place requires the string to end with \r and also to use write instead of print. Hopefully this is possible with string.Formatter. I'll look into it.

if there are prints, we only need to print when iteration % inner_iterations ==0. Is there any way to print in-place?

Perhaps a jax.lax.cond conditioned on the modulo arithmetic?

Regarding printing only when iteration % inner_iterations == 0, as it reduces the frequency of prints, do you think it defeats a bit the purpose? I'm happy to try use a jax.lax.cond.

Honestly, I think everyone is going to have a different preference based on the size of their problem, compute, etc. I'm obviously not a maintainer of this repo, but here's my 2 cents:

Provide a sane default (I'd argue once per completed inner_iteration loop is reasonable but the argument could similarly be made for once per iteration)
Offer the ability to provide a custom callback for those who don't like the default

The latter introduces a bit more maintenance overhead, but in terms of LoC and impact elsewhere, it's (arguably) negligible and thus may be worth it.

Regarding printing only when iteration % inner_iterations == 0, as it reduces the frequency of prints, do you think it defeats a bit the purpose? I'm happy to try use a jax.lax.cond.

The error is only computed every inner_iterations. Hence the error does not move (as shown in your print) if printing every iteration. Of course, the user can set inner_iterations=1, but the reason why this is introduced is that computing the error has the same (roughly) complexity as 1/2  sinkhorn iteration. Hence computing the error every iteration multiply computational time by 1.5, so this is not reasonable (it's also related to checkpointing when running backprop, but that's a minor point).
On the other hand, a new user that does not know about this and uses the default of inner_iterations=10 will be certainly surprised to see that the error "stagnates" between iteration 1 and 9 they might draw wrong conclusions. Maybe a simple fix is to show the iteration when the error was last printed alongside the error, plus display current iteration.

Perhaps taking an (optional) dependency on something like tqdm and, via a callback, updating the progress bar every step and the error message every inner_iterations steps?

Hi, sorry for the long delay, I'm only part time on OTT.
Here is a short status:
@marcocuturi I 100% agree with both your points regarding printing frequency, thanks. Let's only print every inner_iterations.
Regarding the printing mechanism, after the discussion (thanks), I see 2 options:
1. My initial proposal
A user provides a callback function to the solver initializer. The callback can leverage tqdm if the user feels like so, but that dependency is on them. This allows printing and also write() with \r for updating the progress in-place (same line).
from tqdm import tqdm
with tqdm() as pbar:
    out_sink = jax.jit(sinkhorn.Sinkhorn(progress_fn=progress_fn))(lin_p)

where a print function using tqdm could be the one I gave in the initial message.
Advantages: flexible for the user
Drawbacks:

maybe the function signature does not adapt well to other solvers?
uses jax.experimental.host_callback which @ntenenz told us is about to be deprecated.

2. Leveraging jax.debug.print
As @ntenenz pointed out, Jax has a jax.debug.print function. A user passes a format string ("Hello {x}") along with the x argument. Internally this uses an instance of string.Formatter and is limited to printing.
I gave it a shot: this is the current state of this PR. Later today, I will decrease the printing freq down to iteration % inner_iterations == 0.
Advantages:

stable mechanism in Jax, at least not marked as experimental
simple for the user: just a bool argument to activate

Drawbacks: limited to printing one line per message is consumed: no write in place, no progress bar (with ETA). I'm thinking of opening an issue on Jax about writing in place.

I'll proceed with decreasing the printing frequency and open a discussion in the Jax repo.
If you're happy I can apply the same mechanism to other solvers, hopefully today too.

Hello @michalk8, I added a test providing a basic callback function to sinkhorn.Sinkhorn. This function simply traces what arguments it receives. At least, it shows the hooks works and passes correct arguments.
Regarding the docs, I went for something basic.

I just rebased on main. I believe I addressed all the comments. Thanks for the input and ping me back if I missed something or if you have additional comments.