进行MFA音素对齐时出错

系统：wsl2-ubuntu20.4
python版本：3.8.13
之前用库里的pinyin.dict和pinyin_eng.dict进行MFA音素对齐时提示字典错误，去MFA官网下了Mandarin (China) MFA dictionary v2.0.0后不报字典错误了，但是运行一段时间以后报了以下错误，文件夹里也没有生成TextGrid文件
错误：
INFO - Accumulating statistics...
100%|████████████████████████████████████████████████████████████▉| 841/842 [00:22<00:00, 37.72it/s]
INFO - Training complete!
INFO - Compiling training graphs...
100%|███████████████████████████████████████████████████████████▉| 841/842 [00:02<00:00, 337.80it/s]
INFO - Generating alignments...
100%|████████████████████████████████████████████████████████████▉| 841/842 [00:29<00:00, 28.54it/s]
INFO - Initializing training for lda...
100%|███████████████████████████████████████████████████████████▉| 841/842 [00:01<00:00, 707.74it/s]
ERROR - There was an error in the run, please see the log.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/home/ms903/anaconda3/envs/py38/bin/mfa", line 11, in
sys.exit(main())
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/command_line/mfa.py", line 1071, in main
run_train_acoustic_model(args, unknown)
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/command_line/train_acoustic_model.py", line 112, in run_train_acoustic_model
train_acoustic_model(args, unknown_args)
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/command_line/train_acoustic_model.py", line 36, in train_acoustic_model
trainer.train()
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/acoustic_modeling/trainer.py", line 394, in train
trainer.train()
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/acoustic_modeling/base.py", line 533, in train
self.initialize_training()
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/acoustic_modeling/base.py", line 266, in initialize_training
self._trainer_initialization()
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/acoustic_modeling/lda.py", line 453, in _trainer_initialization
self.lda_acc_stats()
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/site-packages/montreal_forced_aligner/acoustic_modeling/lda.py", line 442, in lda_acc_stats
shutil.copyfile(
File "/home/ms903/anaconda3/envs/py38/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ms903/Documents/MFA/split_train_acoustic_model/lda/lda.mat'

用不同的字典可能在后面会有问题，用pinyin.dict和pinyin_eng.dict会报什么错？最近没时间搞这个了，之前没固定版本，可能MFA更新了？如果用之前的MFA2最开始的几个版本试试呢？

用不同开始的字典可能会在后面出现问题，用pinyin.dict和pinyin_eng.dict会报什么？最近没时间搞这个了，在没有固定版本之前，可能MFA更新了？用之前的MFA2最差的几句一个版本呢？

用pinyin.dict和pinyin_eng.dict 的错误是：
OMP: Info #276: omp_set_nested routine deprecated, please use omp_set_max_active_levels instead.
ERROR - There was an error in the run, please see the log.
DictionaryError:
Error parsing line 0 of MFA/pinyin.dict: Did not find any tabs, please ensure that your dictionary has tabs between
words and their pronunciations.
OMP: Info #276: omp_set_nested routine deprecated, please use omp_set_max_active_levels instead.
ArgumentError:
Could not find the corpus directory /home/ms903/data/wav/speaker_name.
OMP: Info #276: omp_set_nested routine deprecated, please use omp_set_max_active_levels instead.
ERROR - There was an error in the run, please see the log.
DictionaryError:
Error parsing line 0 of /home/ms903/Downloads/VTuberTalk/MFA/pinyin.dict: Did not find any tabs, please ensure that
your dictionary has tabs between words and their pronunciations.
后面还跟着一长串重复的错误代码。

我用MFA官网的模型加字典成功生成了TextGrid，进行训练的时候爆显存了，调什么参数能避免爆显存？
报错：
Exception in main training loop: (Fatal) Operator transpose2 raises an paddle::memory::allocation::BadAlloc exception.
The exception content is
:ResourceExhaustedError:
Out of memory error on GPU 0. Cannot allocate 145.312500MB memory on GPU 0, 7.999878GB memory has been allocated and available memory is only 0.000000B.
Please check whether there is any other process using GPU 0.

If yes, please stop them, or start PaddlePaddle on another GPU.
If no, please decrease the batch size of your model.
If the above ways do not solve the out of memory problem, you can try to use CUDA managed memory. The command is export FLAGS_use_cuda_managed_memory=false.
(at /paddle/paddle/fluid/memory/allocation/cuda_allocator.cc:87)
. (at /paddle/paddle/fluid/imperative/tracer.cc:307)

Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/training/trainer.py", line 149, in run
update()
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/training/updaters/standard_updater.py", line 109, in update
self.update_core(batch)
File "train/models/fastspeech2/fastspeech2_updater.py", line 77, in update_core
spk_emb=spk_emb)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "train/models/fastspeech2/fastspeech2.py", line 557, in forward
tone_id=tone_id)
File "train/models/fastspeech2/fastspeech2.py", line 718, in _forward
zs, _ = self.decoder(hs, h_masks)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/encoder.py", line 361, in forward
xs, masks = self.encoders(xs, masks)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/repeat.py", line 25, in forward
args = m(*args)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/encoder_layer.py", line 95, in forward
x = residual + self.dropout(self.feed_forward(x))
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/multi_layer_conv.py", line 67, in forward
return self.w_2(self.dropout(x).transpose([0, 2, 1])).transpose(
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/layers/nn.py", line 5692, in transpose
out, _ = _C_ops.transpose2(x, 'axis', perm)
Trainer extensions will try to handle the extension. Then all extensions will finalize.Traceback (most recent call last):
File "train/exps/fastspeech2/train.py", line 233, in
main()
File "train/exps/fastspeech2/train.py", line 229, in main
train_sp(args, config)
File "train/exps/fastspeech2/train.py", line 170, in train_sp
trainer.run()
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/training/trainer.py", line 198, in run
six.reraise(*exc_info)
File "/usr/local/lib/python3.7/dist-packages/six.py", line 719, in reraise
raise value
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/training/trainer.py", line 149, in run
update()
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/training/updaters/standard_updater.py", line 109, in update
self.update_core(batch)
File "train/models/fastspeech2/fastspeech2_updater.py", line 77, in update_core
spk_emb=spk_emb)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "train/models/fastspeech2/fastspeech2.py", line 557, in forward
tone_id=tone_id)
File "train/models/fastspeech2/fastspeech2.py", line 718, in _forward
zs, _ = self.decoder(hs, h_masks)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/encoder.py", line 361, in forward
xs, masks = self.encoders(xs, masks)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/repeat.py", line 25, in forward
args = m(*args)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/encoder_layer.py", line 95, in forward
x = residual + self.dropout(self.feed_forward(x))
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 930, in call
return self._dygraph_call_func(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/dygraph/layers.py", line 915, in _dygraph_call_func
outputs = self.forward(*inputs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/paddlespeech/t2s/modules/transformer/multi_layer_conv.py", line 67, in forward
return self.w_2(self.dropout(x).transpose([0, 2, 1])).transpose(
File "/usr/local/lib/python3.7/dist-packages/paddle/fluid/layers/nn.py", line 5692, in transpose
out, _ = _C_ops.transpose2(x, 'axis', perm)
SystemError: (Fatal) Operator transpose2 raises an paddle::memory::allocation::BadAlloc exception.
The exception content is
:ResourceExhaustedError:
Out of memory error on GPU 0. Cannot allocate 145.312500MB memory on GPU 0, 7.999878GB memory has been allocated and available memory is only 0.000000B.
Please check whether there is any other process using GPU 0.

If yes, please stop them, or start PaddlePaddle on another GPU.
If no, please decrease the batch size of your model.
If the above ways do not solve the out of memory problem, you can try to use CUDA managed memory. The command is export FLAGS_use_cuda_managed_memory=false.
(at /paddle/paddle/fluid/memory/allocation/cuda_allocator.cc:87)
. (at /paddle/paddle/fluid/imperative/tracer.cc:307)

我用MFA官网的模型加字典成功生成了TextGrid，进行训练的时候爆显存了，调什么参数能避免爆显存？ 我的显卡是1070

train/conf里调整batch size


Bug - Next/prev arrows should be enabled when there are two or more slides

I would like to report a bug in "slide.ts". The next and previous arrows should be shown if there are two or more slides. Instead, arrows are only shown if there are three or more slides due to the following line in "slide.ts".
isNextArrowDisabled() {
return this.isLastSlide(this.counter) ||
(!this.visibleCellsOverflowContainer && this.cellLength <= this.numberOfVisibleCells) ||
(this.visibleCellsOverflowContainer && this.cellLength < this.numberOfVisibleCells)
}
isNextArrowDisabled() {
return this.isLastSlide(this.counter) ||
(!this.visibleCellsOverflowContainer && this.cellLength < this.numberOfVisibleCells) ||
(this.visibleCellsOverflowContainer && this.cellLength < this.numberOfVisibleCells)
}
It's an easy fix, but I thought that others may run into this issue as well. My settings are cellWidth='100%', [lightDOM]='true' and [overflowCellsLimit]='1' for showing one slide at a time with one slide being lazy loaded in the background. Hope this helps. Thank you.

This issue is also stopping the autoplay from executing.

I'm also with this problem.


Adding 3 features that can convert Decimal to Binary| Binary to Decim…

…al | tan
![Uploading feature 3.jpg…

]()

Adding 3 features that can convert Decimal to Binary| Binary to Decimal and also tan


WHEN prompted for the length of the password

THEN I choose a length of at least 8 characters and no more

closed


Updating pypuppetdb dependency to 1.2.0

Updating version of pypuppetdb to avoid missing requirements-test.txt issue present in versions 1.0.0 and 1.1.0.
This change is required to fix deployment issues with the current puppet-puppetboard module. It's a precursor a new release of the puppetboard module.

Coverage remained the same at 81.635% when pulling 05ef6baf27c7ed64fdd5bd2169543fc55c006700 on pjonesIDBS:master into 309875570e6854bf87cfc0231882841f8b6e122e on voxpupuli:master.


Add device lookup by IMEI and devEUI.

A lot of files go touched because I ran generate with the correct gql version.

I normally do that in a separate commit and push to main.

I didn't update the gql version just the last person didn't run generate

What happens is I update go.mod and don't regenerate like a rat.


Add discovery support

This is needed for Blazor to be able to login.
https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig

Basic support added in this commit: https://github.com/Etimo/etimo-id/commit/3a990f0421682eead6177f2e51e1cefb473555cf

Basic support added in this commit: https://github.com/Etimo/etimo-id/commit/3a990f0421682eead6177f2e51e1cefb473555cf


Blobstore walkthrough

These commits will use Blobstore to allow users to add picture to their comments.
Note: Sorry that some commits seem repeated. Internet was really bad today and it said they hadn't been pushed yet.

Oops! I copy/pasted that function from somewhere and forgot to check for indentation. Fixed it


Vulnerability roundup 100: openssl-1.1.1j: 2 advisories [9.8]

search, files

[ ] CVE-2018-16395 CVSSv3=9.8 (nixos-20.09, nixos-unstable)
[ ] CVE-2016-7798 CVSSv3=7.5 (nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.09: 12d9950bf47; nixos-unstable: 1f77a4c8c74.
Cc @peti

another one: https://mta.openssl.org/pipermail/openssl-announce/2021-March/000196.html

The first one seems to be a false positive.it's about Ruby; not openssl https://nvd.nist.gov/vuln/detail/CVE-2018-16395

As far as I can see the openssl ruby gem is not shipped in nixpkgs. I think we can close this issue as a false positive @ckauhaus

Yes - and sorry for the late reply. Had really busy days.


Failed to run e2e ossf-tests/scorecard-action

Repo: https://github.com/ossf-tests/scorecard-action/tree/main \n Run: https://github.com/ossf-tests/scorecard-action/actions/runs/2445383490 \n Workflow name: Scorecards-with-default-GH-Token-golang-staging \n Workflow file: https://github.com/ossf-tests/scorecard-action/tree/main/.github/workflows/Scorecards-with-default-GH-Token-golang-staging.yml \n Trigger: schedule \n Branch: main \n Date: Mon Jun  6 03:22:38 UTC 2022

Happening due to recent updates to Scorecard API.


Document dependency on InfluxDB 1.x

Describe the bug
While InfluxDB 2.x is a mighty fine database, it is not entirely backwards compatible with v1.x (which Butler still uses).
Document this dependency and stress the need to use for example InfluxDB 1.8.4 (which is latest as of this writing).

Done and deployed to https://butler.ptarmiganlabs.com/docs/getting-started/install/


nodejs 20 upgrade

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature
Due to "Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Expected Behavior
New version to use.
Use Case
Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Alternatives Considered
Explain what alternative solutions or features you've considered.
Additional Context
Add any other context or screenshots about the feature request here.

sorry i saw, that the newest version has it. thx


need an egeria version that bundles plexus-archiver jar with version > 3.0.1

egeria 1.0 bundles plexus-archiver-3.0.1.jar and this particular jar file has been flagged for security vulnerability. Please provide an egeria version that uses upgraded plexus libraries. Thanks.

The plexus security vulnerability is the following one: https://nvd.nist.gov/vuln/detail/CVE-2018-1002200
@mandy-chessell or anybody else, can you confirm if egeria is actually exposed or not and if it is, how (to see if our own usage of egeria is making us exposed or not?
Thanks.

I can confirm that 3.0.1 is used throughout (mvn dependency:tree), and is pulled in by components such as commons-collections.
I will aim to create a pr to aim to upgrade plexus-archiver using dependencymanagement. If required will check through dependencies.

I've submitted a pr with a fix for this
We're probably not particularly exposed since the plugin should just be used as part of the build.
I've not looked at other dependencies for now (outside plexus).

Thanks @planetf1. If only used as part of the build, would be nice/good if it is not listed and/or packaged as a runtime dependency.

Agreed. I think we do have some overall improvements we can make in dependency management, including better scoping of the dependencies (and ensuring maven build plugins are only declared as such - not as dependencies too).
I'll change the plexus archiver issue here -- in fact the dependency came in through the maven download plugin, which is certainly build time only. It was expressed as both a dependency and plugin, but only the former is needed in this case.
I've updated the PR with this additional change (not yet merged).
plexus-archiver no longer appears in the output of mvn dependency:tree

Perfect. Thanks @planetf1 .
Any ideas as when an updated version of egeria that we can consume for production will be available with these changes?

Hi,
I'm not aware that a date has been decided for the next release yet.
We can push the code to master easily/quickly, and they can be picked up via the odp.org nexus repository (or you can build yourself). We don't yet have snapshots going to maven central (but this is work in progress), but that of course won't meet your requirements for production I presume.
The current release is 1.0
Are there other fixes & enhancements you would be dependent on?
I would recommend contacting @mandy-chessell and/or joining one of our regular calls to discuss your needs for a release.
Thanks for the issue/feedback :-)


Control event propagation and default action. Implements #5545

This PR is the runtime part of #5545, which is hopefully the vast majority of it. The remaining tooling work is to add directive attributes for @oneventname:stopPropagation and @oneventname:preventDefault.
Design notes
This closely follows the plan described here.
The first major decision point here was to make this entirely a feature of .Web/.Web.JS and not part of .Components core at all. I think that's the right thing to do, because the vast majority of the implementation is in .Web.JS and there's no reason to say that some other non-web UI platform would have any meaning for "prevent default", and another platform need not necessarily have a concept of event bubbling/propagation. The semantics of both are extremely closely tied to DOM semantics. As such, the rendertree APIs for attaching this information are given as extension methods that live in .Web, so the compiler is only going to be able to use them if you're referencing .Web.
The second major decision point was how to represent these flags in the rendertree. Note that these flags behave like attributes:

You can have multiple of them on an element (e.g., for different events)
They are independent of other attributes (e.g., you can stop "click" propagation on some element without necessarily also having a "click" handler on that same element)
They can be added and removed dynamically

I think eventually we will want to introduce a concept of "attribute type". Today there are several types of attributes (regular string/bool attributes, event handler attributes, component parameters, and now stopPropagation/preventDefault ones), but we don't explicitly declare their types anywhere, and instead handle things based on conventions around where they are used and what their value types are.  There is a slot in RenderTreeFrame where we could put an AttributeType enum value and hence be more explicit about all this. At that point, it would make sense for a "stop propagation" attribute to have AttributeType.StopPropagation and name=nameOfTheEvent. Given the attribute type discriminator, we could overload the memory slots with the "attribute" frame type to have different meanings for different types, letting us scale this whole system up further without consuming more memory.
However, I don't think attribute types are useful for this purpose until we also solve "allow multiple same-named attributes" (#14365). So in the short term, my plan is:

Keep the internal representation of stopPropagation/preventDefault information as a private implementation detail. The APIs you (or the compiler) call are builder.AddEventPreventDefaultAttribute and builder.AddEventStopBubblingAttribute, but you don't get to know what they are doing to set that information. How they represent themselves in the tree can change in the future non-breakingly, as long as the APIs and their resulting behavior remains unchanged.
The actual thing they do today is the simplest thing: they just set magic-named attributes. Again, it's an internal implementation detail.

If/when we later do #14365, we could change the internal behavior of AddEventPreventDefaultAttribute and AddEventStopBubblingAttribute to make use of it.
Review notes
Most of the complicated-looking noise in EventDelegator.ts is just refactoring. Previously it used a very loosely-typed scheme for tracking event data, with lots of duplicated checks like Object.hasOwnProperty('something'). Now it's more explicitly typed. I did this just because I'm storing more information here now, and didn't like to expand the ad-hoc loose-typeness.
I'm not trying to override or change DOM semantics for event propagation and its interaction with navigation. So,

events affect each other, e.g., if you preventDefault on a checkbox click that will prevent the subsequent 'change'
you can only preventDefault on an element (or one of its ancestors) that actually listens for that event
you can only receive onfocus events on elements that have a tabindex attribute, and it doesn't bubble anyway
preventDefault does nothing on onfocus

These are all browser behaviors and not controlled by Blazor.
Similarly, stopPropagation does not block navigation. You might think that stopping a "click" from propagating up to an <a href...> would mean the browser doesn't navigate. But you'd be wrong: the native behavior is that it navigates anyway. So I've reproduced the same with Blazor's synthetic event bubbling mechanism and its link click interception. There are E2E tests for this.

Also, the E2E tests hard-code the magic-named attributes. This can be replaced with @oneventname:stopPropagation and @oneventname:preventDefault once they are implemented.

Ping to reviewers @rynowak @pranavkm.
Even though the tooling side won't be in preview 2, it would be valuable to have the runtime part in, so that (1) it doesn't get out of sync and need more work later and (2) for extra verification that my refactoring hasn't broken anybody. There's no drawback to shipping the runtime part that I'm aware of.


Import Option

HI
There must be option to import tasks from the excel sheet, and there must be option to bind fields while importing like the project name, task name, assignee, column, coulur, due date etc

True story and makes life easier to use an API when creating the Webhooks I think?

Any importfeature available yet?

@ashbike made this a while ago -
https://github.com/ashbike/csv2kanboard>

Does https://github.com/ashbike/csv2kanboard still function - it hasn't been updated for some months and I have to admit - I haven't been able to get it to import. It would be great to have this as native functionality.

It does. You see an error while importing?

No error - I'm probably using it wrong. I downloaded an existing install to my laptop and ran the command in terminal as I don't have ssh access to the server at the moment - the script did output 'Finished' to the terminal though.

There is now a basic CSV import for tasks in the development version.
More complex solution (Excel import or automated import etc..) have to be done with plugins or with an external script.

Hi @fguillot , any news about this important feature? +1 on this.


mitmdump hangs when execute "mitmdump -S  temp"

Steps to reproduce the problem:

Type command "mitmdump -w temp" in console and then visit a HTTP website.
Close capture.
Execute "mitmdump -S temp" to replay.

What is the expected behavior?
Server-side replay should be performed.
What went wrong?
mitmdump hangs, no anything print out and also no crash.
Any other comments? What have you tried so far?
mitmdump have an alert like below, but I think it is not related to server side replay.
I searched this issue but nothing found, seems no one report this issue before. I appreciate if you can give me any advice.
lester@ubuntu:mitm$ mitmdump -S ./temp
ALPN support missing (OpenSSL 1.0.2+ required)!
HTTP/2 is disabled. Use --no-http2 to silence this warning.

Mitmproxy Version: mitmdump 0.17
Operating System: ubuntu 14.04 LTS 64-bit

The warning about missing ALPN support is ok. It simply means you cannot use HTTP/2 in your mitmdump session. If you are not using HTTP/2, you can ignore this.
As for the hanging - hard to tell. Maybe you could provide us a capture file where we can see this problem?

Thanks Kriechi. The capture file attached, It quite simple, just captured the traffic when opening www.google.com
temp.zip

@Kriechi

Thanks for the report! We need to take a look at this once #1265 is in. :smiley:

This doesn't hang for me, but it looks like we are exiting prematurely.

mitmdump -S temp exits prematurely for me, but mitmproxy -S temp works just fine. Weird.


Broken Greek letters completion for julia language server

Description
Completion for Greek letters for julia notebook currently cannot work:

If lsp is not loaded, completions from kernel works well, sorry but I cannot capture a gif for it.
Expected behavior
Gives a unicode letter as in repl or vscode's jupyter extension:

Reproduce
Type \alpha , press <Tab>, press <Enter>
Context

Operating System and version: Archlinux
Browser and version: Microsoft Edge Beta
JupyterLab version: 3.2.1

Required: installed server extensions

Config dir: /home/wuli/.jupyter
    jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 1.5.0 OK
    jupyter_server_mathjax enabled
    - Validating jupyter_server_mathjax...
      jupyter_server_mathjax  OK
    jupyterlab enabled
    - Validating jupyterlab...
      jupyterlab 3.2.1 OK
    jupyterlab_code_formatter enabled
    - Validating jupyterlab_code_formatter...
      jupyterlab_code_formatter 1.4.10 OK
    jupyterlab_git enabled
    - Validating jupyterlab_git...
      jupyterlab_git 0.33.0 OK
    nbclassic enabled
    - Validating nbclassic...
      nbclassic  OK
    nbdime enabled
    - Validating nbdime...
      nbdime 3.1.0 OK

Required: installed lab extensions

JupyterLab v3.2.1
/home/wuli/.local/share/jupyter/labextensions
        nbdime-jupyterlab v2.1.0 enabled OK
        @telamonian/theme-darcula v3.1.1 enabled OK (python, theme-darcula)
        @jupyterlab/git v0.33.0 enabled OK (python, jupyterlab-git)
        @jupyterlab/mathjax3-extension v4.2.2 enabled OK (python, jupyterlab-mathjax3)
        @ryantam626/jupyterlab_code_formatter v1.4.10 enabled OK (python, jupyterlab-code-formatter)
        @krassowski/jupyterlab-lsp v3.9.1 enabled OK (python, jupyterlab-lsp)
Other labextensions (built into JupyterLab)
app dir: /usr/share/jupyter/lab
jupyterlab-ihaskell v0.0.14 enabled OK
Disabled extensions:
@jupyterlab/mathjax2-extension:plugin

Now....I don't know why, the whole julia language server is not working.
Giving me error like this:
[I 2021-11-05 16:10:20.403 ServerApp] Adapting from protocol version 5.0 (kernel d189d8e5-3278-43b5-8d94-722d2b1c2943) to 5.3 (client).
[W 2021-11-05 16:10:20.410 ServerApp] Got events for closed stream None
[ Info: Received new data from Julia Symbol Server.
┌ Error: get_hover failed to convert Expr
│   exception =
│    TypeError: in Expr, expected Symbol, got a value of type CSTParser.EXPR
│    Stacktrace:
│      [1] Expr
│        @ ./boot.jl:253 [inlined]
│      [2] get_hover(b::StaticLint.Binding, documentation::String, server::LanguageServerInstance)
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:58
│      [3] get_hover(x::CSTParser.EXPR, documentation::String, server::LanguageServerInstance)
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:20
│      [4] textDocument_hover_request(params::LanguageServer.TextDocumentPositionParams, server::LanguageServerInstance, conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint})
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:6
│      [5] (::LanguageServer.var"#96#97"{typeof(LanguageServer.textDocument_hover_request), LanguageServerInstance})(conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, params::LanguageServer.TextDocumentPositionParams)
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:252
│      [6] dispatch_msg(x::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, dispatcher::JSONRPC.MsgDispatcher, msg::Dict{String, Any})
│        @ JSONRPC ~/.julia/packages/JSONRPC/yu0G3/src/typed.jl:67
│      [7] run(server::LanguageServerInstance)
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:361
│      [8] runserver(pipe_in::Base.PipeEndpoint, pipe_out::Base.PipeEndpoint, env_path::String, depot_path::String, err_handler::Nothing, symserver_store_path::Nothing)
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:46
│      [9] runserver()
│        @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:44
│     [10] top-level scope
│        @ none:1
└ @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:60
ERROR: get_hover failed to convert Expr
Stacktrace:
 [1] get_hover(b::StaticLint.Binding, documentation::String, server::LanguageServerInstance)
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:61
 [2] get_hover(x::CSTParser.EXPR, documentation::String, server::LanguageServerInstance)
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:20
 [3] textDocument_hover_request(params::LanguageServer.TextDocumentPositionParams, server::LanguageServerInstance, conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint})
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:6
 [4] (::LanguageServer.var"#96#97"{typeof(LanguageServer.textDocument_hover_request), LanguageServerInstance})(conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, params::LanguageServer.TextDocumentPositionParams)
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:252
 [5] dispatch_msg(x::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, dispatcher::JSONRPC.MsgDispatcher, msg::Dict{String, Any})
   @ JSONRPC ~/.julia/packages/JSONRPC/yu0G3/src/typed.jl:67
 [6] run(server::LanguageServerInstance)
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:361
 [7] runserver(pipe_in::Base.PipeEndpoint, pipe_out::Base.PipeEndpoint, env_path::String, depot_path::String, err_handler::Nothing, symserver_store_path::Nothing)
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:46
 [8] runserver()
   @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:44
 [9] top-level scope
   @ none:1

caused by: TypeError: in Expr, expected Symbol, got a value of type CSTParser.EXPR
Stacktrace:
  [1] Expr
    @ ./boot.jl:253 [inlined]
  [2] get_hover(b::StaticLint.Binding, documentation::String, server::LanguageServerInstance)
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:58
  [3] get_hover(x::CSTParser.EXPR, documentation::String, server::LanguageServerInstance)
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:20
  [4] textDocument_hover_request(params::LanguageServer.TextDocumentPositionParams, server::LanguageServerInstance, conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint})
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/requests/hover.jl:6
  [5] (::LanguageServer.var"#96#97"{typeof(LanguageServer.textDocument_hover_request), LanguageServerInstance})(conn::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, params::LanguageServer.TextDocumentPositionParams)
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:252
  [6] dispatch_msg(x::JSONRPC.JSONRPCEndpoint{Base.PipeEndpoint, Base.PipeEndpoint}, dispatcher::JSONRPC.MsgDispatcher, msg::Dict{String, Any})
    @ JSONRPC ~/.julia/packages/JSONRPC/yu0G3/src/typed.jl:67
  [7] run(server::LanguageServerInstance)
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/languageserverinstance.jl:361
  [8] runserver(pipe_in::Base.PipeEndpoint, pipe_out::Base.PipeEndpoint, env_path::String, depot_path::String, err_handler::Nothing, symserver_store_path::Nothing)
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:46
  [9] runserver()
    @ LanguageServer ~/.julia/packages/LanguageServer/JrIEf/src/runserver.jl:44
 [10] top-level scope
    @ none:1
[E 2021-11-05 16:11:04.542 ServerApp] <LspStdIoWriter(parent=<LanguageServerSession(language_server=julia-language-server, argv=['/usr/sbin/julia', '--project=.', '-e', 'using LanguageServer, LanguageServer.SymbolServer; runserver()', '.'])>)> couldn't write message: Content-Length: 208

    {"jsonrpc":"2.0","id":4,"method":"textDocument/documentHighlight","params":{"textDocument":{"uri":"file:///home/wuli/.virtual_documents/CodesWSL/Jupyter/JuliaTest.ipynb"},"position":{"line":5,"character":0}}}
    Traceback (most recent call last):
      File "/home/wuli/.local/lib/python3.9/site-packages/jupyter_lsp/stdio.py", line 193, in write
        await convert_yielded(self._write_one(response.encode("utf-8")))
      File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
        result = self.fn(*self.args, **self.kwargs)
      File "/home/wuli/.local/lib/python3.9/site-packages/jupyter_lsp/stdio.py", line 201, in _write_one
        self.stream.write(message)
    BrokenPipeError: [Errno 32] 断开的管道
[E 2021-11-05 16:11:06.461 ServerApp] <LspStdIoWriter(parent=<LanguageServerSession(language_server=julia-language-server, argv=['/usr/sbin/julia', '--project=.', '-e', 'using LanguageServer, LanguageServer.SymbolServer; runserver()', '.'])>)> couldn't write message: Content-Length: 208

    {"jsonrpc":"2.0","id":5,"method":"textDocument/documentHighlight","params":{"textDocument":{"uri":"file:///home/wuli/.virtual_documents/CodesWSL/Jupyter/JuliaTest.ipynb"},"position":{"line":5,"character":0}}}
    Traceback (most recent call last):
      File "/home/wuli/.local/lib/python3.9/site-packages/jupyter_lsp/stdio.py", line 193, in write
        await convert_yielded(self._write_one(response.encode("utf-8")))
      File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
        result = self.fn(*self.args, **self.kwargs)
      File "/home/wuli/.local/lib/python3.9/site-packages/jupyter_lsp/stdio.py", line 201, in _write_one
        self.stream.write(message)
    BrokenPipeError: [Errno 32] 断开的管道
^C[I 2021-11-05 16:11:20.313 ServerApp] interrupted

Please provide a minimal reproducible example in a separate issue; ERROR: get_hover failed to convert Expr suggests that this is an error in the Julia language server, not in jupyterlab-lsp extension. It is likely a very specific code fragment that triggers it.

Please provide a minimal reproducible example in a separate issue; ERROR: get_hover failed to convert Expr suggests that this is an error in the Julia language server, not in jupyterlab-lsp extension. It is likely a very specific code fragment that triggers it.

OK, I'll try. But what I concern is BrokenPipeError in later of the log, which seems to occur every time I try to do code completion.

No, I was wrong, seems I run into some random error, after restart jupyterlab, the errors are gone. But still cannot correctly
completion. Thanks for reply!

BrokenPipeError only tells us that the LSP server had an internal error; the traceback tells us what this error is and it definitely is on the Julia language server side.

Thank you for bringing the issue of Greek letters up. I found the cause: both kernel and LSP server return Greek letter suggestions leading to a clash; because we do not handle textEdits yet, the label is inserted (again) instead of the Greek letter.
To fix that we will need to implement handling of textEdit property from completion response. This in turn will require refactoring completer API in JupyterLab core to allow multiple start/end points.
I investigated potential workarounds but none can be reliably applied without improving the completer API internals. I hope I can get the necessary changes in between JupyterLab 4.0 release (by the end of the year) so that it can work in the next version.

I have this issue too.
Has it been fixed?

FWIW, This also seems to be broken in Python for me. My versions:
ipython                   8.7.0
jupyter-lsp               1.5.1
jupyterlab                3.5.2
python-lsp-server         1.7.0

Disabling completion in the advanced settings editor and reloading lab seems to restore greek letter completion.


Fixing a typo in the Readme

Describe the change
What does this Pull Request do?
Why are we doing this?
Any related context as to why is this is a desirable change.
Benefits
How will the library improve?
Drawbacks
Possible drawbacks applying this change.
Requirements
Put an X between brackets on each line if you have done the item:
[] Tests written & passing locally?
[] Code style checked?
[] Rebased with master branch?
[] Documentaion updated?

Pull Request Test Coverage Report for Build 88

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

Totals

Change from base Build 87:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Thanks ❤


explore Tableau Cloud as a possible software checkout target

https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_users_and_groups.htm

Decided not to do this


Google Sites Placeholder

There are placeholders to missing Wiki pages:
<a href="https://sites.google.com/post.do?id=204539" rel="nofollow">
  Grid Control (11)
</a>

The discovered files are:

docs/home/10g-ocm/10g-services/grid-control/grid-control-14.html
docs/home/10g-ocm/10g-services/grid-control/grid-control-12.html

Manually fixed docs/home/10g-ocm/10g-services/grid-control/grid-control-14.html

Manually fixed docs/home/10g-ocm/10g-services/grid-control/grid-control-12.html

No occurrences of Google Sites placeholders remain in the unconverted web pages:
find_unconverted_web_pages.sh | \
    xargs grep -il post.do | \
    wc -l

The result is:
0


Temp fix for issue #13

Now we only need to call the propagate function with rejoined true and some msg xD Fast and dirty fix :D

Please see here for the new way over figuring out if an object exists or not

Okay great, let me know if you need anything else


haproxy/http-edge: Add option to pass host as a regular expression https://github.com/sbitio/puppet-ducktape/issues/56

Superseded by https://github.com/sbitio/puppet-ducktape/pull/58


removed aling-items from service bottom to make sure all service items stay of same height

when service items have different length of content, one with bigger content is higher and symmetry of service items is gone.  removing align-items: center from service bottom aligns all height to biggest content box ( I just commented it out for now). Alternatively, we can do align-items: stretch on .service-bottom  OR  align-self: stretch on .service-item . Feel free to test these and implement change you like.

I commented out instead of deleting. First time contributing to GitHub project. Learned to practice and start writing basic site using your tutorial and thanks for that. I have been making bilingual react sites now using inspiration on a few section from your tutorial and had noticed the service item issue earlier with simple non-react version of this site a few months ago and it notices again with my  react version recently, to fix I had to do some debugging and I uses stretch to solve this nd thought it will be good to contribute (though just one line of CSS) to project that I had learned a lot from (specifically on header effects etc). Feel free to accept, reject or suggest something else.


Xpand.Utils en Xpand.Xpo as NuGet package targeting .NET 4.5.2 and .NET Standard 2.0

As we also have non-XAF applications that use XPO we like to add only Xpand.Xpo and Xpand.Utils to our projects. Currently, the Xpand.Xpo and Xpand.Utils projects are added in the eXpandLib package which contains XAF packages.
Since the current XAF projects target .NET Framework and not .NET Standard like DevExpress.Xpo is, we can't use the Xpand.Xpo and the Xpand.Utils in non-XAF applications such as (ASP).NET Core projects.
We would like a solution where the Xpand.Xpo and the Xpand.Utils project (Xpand.Xpo references Xpand.Utils) are targeted at .NET Standard 2.0 and .NET 4.5.2 like DevExpress.Xpo and are available as a NuGet package. This way the projects are more future-proof and can these projects can still be referenced to current projects using those Xpand projects.
The problem that might be there when targeting .NET Standard 2.0 is the .NET Framework specific code such as System.Management, but we can work around and discuss about solutions for this.
What do you think about this?

yes I agree its time to start releasing portable packages however I rather focus on doing it as part of the DevExpress.XAF.
There are already plans to release the https://github.com/eXpandFramework/DevExpress.XAF/tree/lab/src/Extensions as source only packages e.g https://nikcodes.com/2013/10/23/packaging-source-code-with-nuget/ where each package will contain only one feature like this https://github.com/eXpandFramework/DevExpress.XAF/blob/lab/src/Extensions/Extensions/XAF/Object/GetTypeInfo.cs. If the feature has dependencies that are not portable then the package cannot be published as a .NET standard lib.
In time Xpo and utils will be puzzled from those Nuget source only packages.
So perhaps is better to hear what features of xpo and utils you find useful, so to prioritize works and thoughts

Since the current XAF projects target .NET Framework and not .NET Standard like DevExpress.Xpo is, we can't use the Xpand.Xpo and the Xpand.Utils in non-XAF applications such as (ASP).NET Core projects.

note that this is planned to changed soon, spa is an asp.net core isn't?

Tolis,
I understand that you only want to continue with the DevExpress.XAF project, a progressive move.
I will look in our codebase which Xpand code we currently are using. It might take some time, because we are currently rewriting our code. Former coworkers copied the Xpand code and started to change Xpand into our company name and start editing the code, which made it a horrible mess to maintain and to read. We currently are seperating the Xpand and our code and will be able to see the differences. Then I am able to tell which functions we are currently using in our projects and might add functionalities from our code later on.
We don't use SPA yet, because it is very unstable and hasn't all the features yet. SPA is based on .NET Framework but references the ASP.NET Core libraries.

I understand that you only want to continue with the DevExpress.XAF project, a progressive move.

actually I plan to use them both, but the standalone packages will be documented and tested.

We don't use SPA yet, because it is very unstable and hasn't all the features yet. SPA is based on .NET Framework but references the ASP.NET Core libraries.

true but I did soon didn't I? DX is working hard on that already

actually I plan to use them both, but the standalone packages will be documented and tested.

reasoning for this is, the main project will clearlt demonstrate how to create puzzles from the standlone for newcomers and for those that are lazy to create one from themselves.

I got the answer now and I will look forward to test the source only packages and see how it will do in production. I will close the issue now.

just for reference the source only packages althought not published are already used from the standalone packages as linked files

now I remember why I fail migrating fasterflect the first time.
https://github.com/HelloKitty/fasterflect/issues/5

I have noticed that and thought to create an issue on that repo, but I don't have to since you did.

if they reject we can always publish our own signed version

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


Release process: can't create tag

I'm not sure why I can't create tags. It seems it's calling gpg for some reason and I don't have it set it up.
$ git tag -s 2.1.0rc2
error: gpg failed to sign the data:
gpg: skipped "Manuel Kaufmann<EMAIL_ADDRESS>No secret key
[GNUPG:] INV_SGNR 9 Manuel Kaufmann<EMAIL_ADDRESS>[GNUPG:] FAILURE sign 17
gpg: signing failed: No secret key

error: unable to sign the tag
The tag message has been left in .git/TAG_EDITMSG

We need to create 2.1.0rc1 and 2.1.0rc2.

I'd check your local configuration as this should not be configuration at the repo level.
In the past, we did sign packages with GPG. Since PyPI dropped this support, we stopped this though. The key used would have been the<EMAIL_ADDRESS>GPG key, not your private key. I'm guessing your Git configuration is old and still referencing tag/commit signing.

Specifically, do you have this in your local .git/config?
[commit]
    gpgsign = true

In the past, we did sign packages with GPG. Since PyPI dropped this support, we stopped this though

I understand this is not related with PyPI, but with Git itself since we are passing -s to sign the tag creation.

The key used would have been the<EMAIL_ADDRESS>GPG key, not your private key

I was able to perform the PyPI signing without issues.
I opened https://github.com/readthedocs/sphinx_rtd_theme/pull/1596 to remove the -s which is what's causing the issue.

I was able to perform the PyPI signing without issues.

@humitos I don't think so. It stopped accepting PGP signature uploads a while ago: https://discuss.python.org/t/gpg-signature-support-removed-from-pypi/27014 / https://blog.pypi.org/posts/2023-05-23-removing-pgp/.
Though, there's a new PEP 740 digital attestations feature upcoming that you can enable already and wait until the related bits and pieces start showing up on PyPI: https://github.com/marketplace/actions/pypi-publish#generating-and-uploading-attestations.


Nested Queries in 3.8.22 not working

I did a clean npm install in our project, and some tests that were previously working are now broke. I don't know what previous version I was on, but my best guess would be 3.8.21 or earlier.
Previously, I could build a query with the following syntax:
MyModel.find({
  some_param: 'param',
  some_obj: {
    param_a: 'a',
    param_b: 'b'
  }
}, callback);

That no longer works in 3.8.22. However, the following syntax does work:
MyModel.find({
  some_param: 'param',
  'some_ob.param_a': 'a',
  'some_obj.param_b': 'b'
}, callback);

While it still works, it's a big inconvenience when you've got nested objects. When I have a chance, I will try to create a bare-bones repro.

Hmm I don't think this is the exact cause. In MongoDB,
MyModel.find({
  some_param: 'param',
  some_obj: {
    param_a: 'a',
    param_b: 'b'
  }
}, callback);

Is only supposed to match documents where some_obj is exactly equal to { param_a: 'a', param_b: 'b' }, with no other properties. For instance, the following standalone script fails on mongoose 3.6.17, 3.8.1, 3.8.22, 4.0.0-rc1, etc:
var mongoose = require('mongoose');
var assert = require('assert');
var Schema = mongoose.Schema;

mongoose.connect('mongodb://localhost:27017/gh-2648');

var schema = Schema({ food: { eggs: Number, bacon: Number } });
var Breakfast = mongoose.model('gh-2648', schema, 'gh-2648');

Breakfast.create({ food: { eggs: 4, bacon: 2 } }, function(error) {
  assert.ifError(error);
  var query = { food: { eggs: 4 } };
  Breakfast.findOne(query, function(error, doc) {
    assert.ifError(error);
    assert.ok(doc);
    assert.equal(4, doc.food.eggs);
    assert.equal(2, doc.food.bacon);
    process.exit(0);
  });
});

However, once you make the doc an exact match, like below:
var mongoose = require('mongoose');
var assert = require('assert');
var Schema = mongoose.Schema;

mongoose.connect('mongodb://localhost:27017/gh-2648');

var schema = Schema({ food: { eggs: Number, bacon: Number } });
var Breakfast = mongoose.model('gh-2648', schema, 'gh-2648');

Breakfast.create({ food: { eggs: 4, bacon: 2 } }, function(error) {
  assert.ifError(error);
  var query = { food: { eggs: 4, bacon: 2 } };
  Breakfast.findOne(query, function(error, doc) {
    assert.ifError(error);
    assert.ok(doc);
    assert.equal(4, doc.food.eggs);
    assert.equal(2, doc.food.bacon);
    process.exit(0);
  });
});

You get the correct behavior on 3.6.x, 3.8.x, and 4.x. So I suspect the reason why your tests are failing is something different. Can you tell me how you're creating the objects that you're querying, and what they look like in the db?

@vkarpov15 I appreciate pointing out that sub-documents must match exactly, which I didn't realize before. It will assuredly help me figure out future bugs.
 As I played around with it more, my issue may be related to having nested refs that were not getting cast to ObjectIds when getting passed a string. My recollection is that I tried passing in strings and strings cast to ObjectIds, which neither worked, though I can't guarantee that I did everything correctly.
Since I can't repro, I'll close the issue. Thanks for your help. If I can repro my issue in the future, I'll come back.

Thanks. Good luck, let me know if you ever find why this is failing. 3.8.22 should in theory be a seamless transition from 3.8.0 or 3.8.21, but that isn't always the case unfortunately.


[FEATURE] Add search Functionality to Frontend

⭐ Suggestion
We added search endpoint to the rest API
curl -X 'GET' \
  'https://api.bhagavadgita.io/v2/search?query=Karma' \
  -H 'accept: application/json' \
  -H 'X-API-KEY: <API-KEY>'

would be good to add search to frontend
Current Implementation

Required:

Also, before creating pull Request, check the functionality working across all the headers.
💻 Use Cases
No response
❌ Related Problems
No response

Hi @Gupta-Anubhav12, any idea if we already have figma designs for "Search Result" component? Thanks

Hii for sure

Hi @Gupta-Anubhav12, @ankitach23, do you mind if I take this one and start working right away? Feel free to assign this to me if that's fine otherwise I am happy with another ticket if that's more prior to this, thanks.

Hi @redraushan, Let me know if you are still available to take this issue, Happy to assign it to you. :)

Hey Search thing was already done
so closing this


Problem：GetElfSymbolOffset Failed with GetElfSymbolOffset: symtab not found

When I executed this command, I got the following error. Has anyone encountered a similar problem?
\Test.exe pseamldr.so.consts pseamldr.so libtdx.so
error：
[+] Creating the Cornelius VM
[+] Executing PSEAMLDR.INSTALL on VCPU0
[!] GetElfSymbolOffset Failed with GetElfSymbolOffset: symtab not found

You must pass DO_NOT_STRIP=1 to the make command lines when you build the TDX firmware. I've added it to the README: #11. Closing as fixed, thanks

When compiling the P-SEAMLDR and TDX module, I added DO_NOT_STRIP=1 to the make command line, but the same issue still occurred.


Adding "placeholderTextColor" and "keyboardType" props

Added "placeholderTextColor" and "keyboardType" props in the search field.

Thank you faslash for your contribution


[CognitiveServices] remove ci_enabled=false from qnamaker for release

ci_enabled=false should not be set in pyproject.toml in order to release. Fixing here and will add back in after package is released.

/check-enforcer override


[Sema] Revert enabling require-explicit-availability for public modules by default

This is a partial revert of #61105. Passing the flag -require-explicit-availability=ignore to the stdlib broke the bot building the stdlib with the last toolchain. We should wait until the flag is available in a toolchain on swift.org before we adopt it in the stdlib. Until we can use the flag, to avoid misleading warnings in the stdlib I'm also reverting the automatic enabling of require-explicit-availability for public modules.
rdar://99993044

@swift-ci Please smoke test

The macOS failure is unrelated:lldb-api :: lang/swift/unknown_reference/TestSwiftUnknownReference.py tracked by rdar://100034078


New package: MayOptimize v0.2.0

Registering package: MayOptimize
Repository: https://github.com/emmt/MayOptimize.jl
Created by: @emmt
Version: v0.2.0
Commit: 685d08905fe1e566158e466801f9364ca61a7fe7
Git reference: master
Release notes:

First official release of MayOptimize.

TagBot tag

Nothing happens, let us retry ;-)
TagBot tag


[#427] Added PyPi check and refactored

If the host parameter is not pypi or readthedocs this function should error out Wednesday, 21 October 2020, 09:42AM +02:00 from Farwent<EMAIL_ADDRESS>:

@Imipenem commented on this pull request.
In  cookietemple/create/template_creator.py :
"""

   log.debug(f'Look up {project_name} at readthedocs.io .')

   print(f'[bold blue]Looking up {project_name} at readthedocs.io!')

   print(f'[bold blue]Looking up {project_name} at {host}!')

   url = 'https://' + (f'pypi.org/project/{project_name.replace(" ", "")}' if host == "PyPi" else f'{project_name.replace(" ", "")}.readthedocs.io')

-> if it s no pypi or readthedocs you should catch that earlier and inform the user```
You mean in terms of scalability? Because this function is only called with either PyPi or readthedocs
—
You are receiving this because your review was requested.
Reply to this email directly,  view it on GitHub , or  unsubscribe .


optimizations in eredis_parser

Cache binary pattern in eredis_parser
Use the process dict as a cache to store the compiled binary pattern.
This makes binary:match/2 significantly faster for small binaries
where size is <10000.
optimize first clause of eredis_parser:split_by_newlines
For erlperf, see https://github.com/max-au/erlperf
precompiled/cached pattern vs. non-compiled
BIN="<<\"$(echo -n "b"; head -c 99 /dev/urandom | base32 -w 0 ; echo -n '\r\n'; head -c 19 /dev/urandom | base32 -w 0)\">>"
./erlperf \
    'runner({Bin, UncompiledPattern}) -> binary:match(Bin, UncompiledPattern).' \
    --init_runner "{${BIN}"',<<"\r\n">>}.' \
    'runner(Bin) -> binary:match(Bin, get(newline_pattern)).' \
    --init_runner 'put(newline_pattern, binary:compile_pattern(<<"\r\n">>)), '"${BIN} ."

results in
Code                                                                              ||        QPS       Time     Rel
runner(Bin) -> binary:match(Bin, get(newline_pattern)).                            1   17316 Ki      57 ns    100%
runner({Bin, UncompiledPattern}) -> binary:match(Bin, UncompiledPattern).          1    3519 Ki     284 ns     20%

binary:split vs. binary:match
Also use binary:split instead of binary:match. The former seems to be faster by a significant margin:
BIN="<<\"$(echo -n "b"; head -c 99 /dev/urandom | base32 -w 0 |head -c 99 ; echo -n '\r\n')\">>"
./erlperf \
'runner(Bin) -> case binary:match(Bin,get(bin)) of {P, L} -> <<A:P/binary, _B:L/binary, C/binary>> = Bin, {A, C} end.' \
    --init_runner 'put(bin,binary:compile_pattern(<<"\r\n">>)), '"${BIN} ." \
'runner(Bin) -> case binary:split(Bin,get(bin)) of [A, C] -> {A, C} end.' \
    --init_runner 'put(bin,binary:compile_pattern(<<"\r\n">>)), '"${BIN} ."

results in
Code                                                                                ||        QPS       Time     Rel
runner(Bin) -> case binary:split(Bin,get(bin)) of [A, C] -> {A, C} end.                                               1   13240 Ki      75 ns    100%
runner(Bin) -> case binary:match(Bin,get(bin)) of {P, L} -> <<A:P/binary, _B:L/binary, C/binary>> = Bin, {A, C} end.  1    9253 Ki     108 ns     69%

Optimize first clause of eredis_parser:split_by_newlines
Optimize the first clause for the most common case - when Acc is empty.
This happens a lot with small DB commands which do not produce much
output at all (which is most DB commands in almost every use case).
The new clause slightly duplicates the 3rd clause,
but avoids building a new binary from the empty Acc.
Use guard size() == 0 as it is the faster than matching on <<>>:
Benchmarks:
BIN="<<\"$(echo -n "b"; head -c 99 /dev/urandom | base32 -w 0 ; echo -n '\r\n'; head -c 19 /dev/urandom | base32 -w 0)\">>"
./erlperf \
    'runner({A, B}) -> <<A/binary, B/binary>>.' \
        --init_runner "{<<>>, ${BIN}}." \
    'runner({A, B}) -> if A =:= <<>> -> B; true -> <<A/binary, B/binary>> end.' \
        --init_runner "{<<>>, ${BIN}}." \
    'runner({A, B}) -> case A of <<>> -> B; _ -> <<A/binary, B/binary>> end.' \
        --init_runner "{<<>>, ${BIN}}." \
    'runner({A, B}) -> case byte_size(A) of 0 -> B; _ -> <<A/binary, B/binary>> end.' \
        --init_runner "{<<>>, ${BIN}}." \
    'runner({A, B}) -> case size(A) of 0 -> B; _ -> <<A/binary, B/binary>> end.' \
        --init_runner "{<<>>, ${BIN}}."

results in
Code                                                                                ||        QPS       Time     Rel
runner({A, B}) -> case size(A) of 0 -> B; _ -> <<A/binary, B/binary>> end.               1   51284 Ki      19 ns    100%
runner({A, B}) -> case byte_size(A) of 0 -> B; _ -> <<A/binary, B/binary>> end.          1   51170 Ki      19 ns     99%
runner({A, B}) -> if A =:= <<>> -> B; true -> <<A/binary, B/binary>> end.                1   43204 Ki      23 ns     84%
runner({A, B}) -> case A of <<>> -> B; _ -> <<A/binary, B/binary>> end.                  1   42995 Ki      23 ns     83%
runner({A, B}) -> <<A/binary, B/binary>>.                                                1    7061 Ki     141 ns     13%

By the way, process dictionary is faster than persistent_term:
BIN="<<\"$(echo -n "b"; head -c 99 /dev/urandom | base32 -w 0 |head -c 99 ; echo -n '\r\n')\">>"
./erlperf \
'runner({Bin,GetProcDict}) -> case binary:split(Bin,GetProcDict()) of [A, C] -> {A, C} end.' \
    --init_runner 'put(bin,binary:compile_pattern(<<"\r\n">>)),'"{${BIN} , fun() -> get(bin) end}." \
'runner({Bin,GetPersTerm}) -> case binary:split(Bin,GetPersTerm()) of [A, C] -> {A, C} end.' \
    --init_runner 'persistent_term:put(my_bin,binary:compile_pattern(<<"\r\n">>)),'"{${BIN} , fun() -> persistent_term:get(my_bin) end}." \
-l 100M

Code                                                                                ||        QPS       Time     Rel
runner({Bin,GetProcDict}) -> case binary:split(Bin,GetProcDict()) of [A, C] -> {A, C} end.          1   11321 Ki      88 ns    100%
runner({Bin,GetPersTerm}) -> case binary:split(Bin,GetPersTerm()) of [A, C] -> {A, C} end.          1   10180 Ki      98 ns     89%

of course with the caveats being

for each eredis_client process the cached compiled pattern is duplicated -> more memory use (but this object seems small, probably few dozen bytes)
each eredis client process calls binary:compile_pattern/1 once when they parse their first query response -> slightly longer latency on very first command (latency of a compile_pattern seems to be ~100ns on my machine for \r\n as a pattern)

Perhaps we shuold include code comments ore a separate markdown file in the repo, describing the erlperf menchmarks you've done here. It's important background and useful for future optimization attempts.

CI: Elvis complains about code style:
# src/eredis_parser.erl [FAIL]
  - operator_spaces
    - Missing space right "," on line 27
make: *** [Makefile:78: elvis] Error 1


add ukrainian and more russian

@kissarat Great, this is awesome.
Could you please update the README, available languages section ?

@kissarat If you don't have any further changes, let me know so I can merge.


how to change currency

how to change currency in this code

@rambhai99
application/config/config.php
There is a line:
/*
|--------------------------------------------------------------------------

Default Language

This determines which set of language files should be used. Make sure

there is an available translation if you intend to use something other

than english.

Must set currencyKey: BGN, USD or other.. Look in currency

hepler for help.. :)

*/

$config['language'] = 'english';

$config['language_abbr'] = 'en';

$config['currency'] = '€';

$config['currencyKey'] = 'EUR';


A new flower out there

Greetings
I made a widget for kivy and I would appreciate an expert's opinion.
It might be of interest to you.
https://github.com/unjuan/Rotabox
Thanks in advance
unjuan

dude/dudete this is awesome!!!
On Sat, Mar 26, 2016 at 1:40 AM, ænas<EMAIL_ADDRESS>wrote:

Greetings
I made a widget for kivy and I would appreciate an expert's opinion.
It might be of interest to you.
https://github.com/unjuan/Rotabox
Thanks in advance
unjuan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/kivy-garden/kivy-garden.github.io/issues/116

@unjuan, would you like to transfer the repo to kivy-garden and become a member?

@akshayaurora, thanks man (excuse the delay - I somehow missed your message)
@dessant, yes, of course. What do I need to do?

Transfer it to me, at the bottom of repo settings, then i'll pass it on to kivy-garden.

@unjuan, once the invitation is accepted, you will become a kivy-garden member and have write access to https://github.com/kivy-garden/garden.rotabox.
Welcome and thank you for your neat work. :tropical_drink:


Can't get NodeGroup to update

Problem or feature description
I'm struggling with getting a NodeGroup to properly update even though the data array changes and the component is re-rendered. I must have gotten something small really wrong but I can't for the life of me figure it out.
Steps to reproduce (only needed for problems)
I've made a sample where I've reproduced the issue: https://codesandbox.io/s/z2102pqmn4
Versions (only needed for problems)
See versions in above sample
UPDATED: I didn't realize that codesandbox, unlike jsfiddle etc, doesn't save automatically so I had to redo the whole thing. Anyway - it's there now :)

Closing after getting help from @tannerlinsley : https://codesandbox.io/s/0xw5vvmlyv


No channel and post id in context from post_menu entry

I'm trying to create an app with a post menu.
I use the following in bindings:
  {
    "location": "/post_menu",
    "bindings": [
      {
        "app_id": "hello-world",
        "location": "create-from-post",
        "icon": "icon.png",
        "label": "Create from post",
        "hint": " -- TODO --",
        "description": "Use this post to create an entry.",
        "submit": {
          "path": "/create-from-post",
          "expand": {
            "acting_user": "all",
            "acting_user_access_token": "all",
            "channel": "all",
            "post": "all",
            "root_post": "all",
            "user": "all",
            "oauth2_user": "all"
          },
          "state": "post-menu"
        }
      }
    ]
  }

This is working pretty well, I have an icon in post app-menu that I can click and this fires a call to the /create-from-post endpoint of my app.
However, the incoming call's context doesn't have any information about the channel and post despite the doc says it should include channel and post information for /post_menu bindings.
Here is a sample of payload received from mattermost to the /create-from-post endpoint:
{
  "path": "/create-from-post",
  "expand": {
    "acting_user": "all",
    "acting_user_access_token": "all",
    "channel": "all",
    "post": "all",
    "root_post": "all",
    "user": "all",
    "oauth2_user": "all"
  },
  "state": "post-menu",
  "context": {
    "app_id": "",
    "mattermost_site_url": "http://mattermost:8065",
    "developer_mode": true,
    "app_path": "/plugins/com.mattermost.apps/apps/myapp",
    "bot_user_id": "8sfyfREDACTED4fiih",
    "bot_access_token": "oboREDACTED7ixw",
    "acting_user": {
      "id": "5fy1REDACTED8e4y",
      "create_at":<PHONE_NUMBER>478,
      "update_at":<PHONE_NUMBER>713,
      "delete_at": 0,
      "username": "myusername",
      "auth_service": "",
      "email"<EMAIL_ADDRESS>      "nickname": "",
      "first_name": "",
      "last_name": "",
      "position": "",
      "roles": "system_admin system_user",
      "locale": "en",
      "timezone": {
        "automaticTimezone": "Europe/Paris",
        "manualTimezone": "",
        "useAutomaticTimezone": "true"
      },
      "disable_welcome_email": false
    },
    "oauth2": {}
  }
}

Did I miss something ?
Note: I'm using mattermost in docker container from image mattermost/mattermost-enterprise-edition:7.5.0 as shipped within mattermost-app-example's docker-compose.yml

Hi @sblaisot, thanks for creating this issue. Are you able to gather any server logs that may be showing some errors for this request?

You can search for com.mattermost.apps in the logs to find messages specific to the Apps framework

here are the logs cot com.mattermost.app when clicking on the app icon in the app post menu :
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.664 Z","level":"debug","msg":"CSRF Check failed for request - Please migrate your plugin to either send a CSRF Header or Form Field, XMLHttpRequest is deprecated","caller":"app/plugin_requests.go:200","path":"/plugins/com.mattermost.apps/api/v1/call","ip":"<IP_ADDRESS>:40270","session_id":"d1g35gir9tna5b56ga1sxwigbr","user_id":"a3q8phu5e3d47pjyr4jzpnzkry"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.674 Z","level":"debug","msg":"failed to expand field acting_user_access_token","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","path":"/api/v1/call","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w","error":"hello-world does not have permission to use Mattermost REST API as connected users: forbidden","plugin_caller":"server/proxy/expand.go:197","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.681 Z","level":"debug","msg":"failed to expand field channel","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","request_id":"njrs53fnj38w8e51ieepgjje9w","error":"id: s1ho64834if9dq74jr1434piya: : You do not have the appropriate permissions., userId=1srjdsk73ff7idrqdpcc1itpph, permission=read_public_channel,","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call","destination":"hello-world","plugin_caller":"server/proxy/expand.go:197"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.681 Z","level":"debug","msg":"failed to expand field oauth2_user","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","plugin_caller":"server/proxy/expand.go:197","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call","error":"hello-world does not have permission to use a remote (3rd party) OAuth2 and store secrets: forbidden"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.685 Z","level":"debug","msg":"failed to expand field post","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call","error":"failed to get post qybro84ciiy5uepqxiiwukirma: : You do not have the appropriate permissions., userId=1srjdsk73ff7idrqdpcc1itpph, permission=read_public_channel,","plugin_caller":"server/proxy/expand.go:197","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.685 Z","level":"debug","msg":"failed to expand field root_post","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w","error":"no post ID to expand","plugin_caller":"server/proxy/expand.go:197","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.689 Z","level":"debug","msg":"failed to expand field team","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w","error":"failed to get team pwipob453trw7bu8o9sgfh39fw: : You do not have the appropriate permissions., userId=1srjdsk73ff7idrqdpcc1itpph, permission=view_team,","plugin_caller":"server/proxy/expand.go:197","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.690 Z","level":"debug","msg":"failed to expand field user","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","destination":"hello-world","request_id":"njrs53fnj38w8e51ieepgjje9w","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call","error":"no user ID to expand","plugin_caller":"server/proxy/expand.go:197"}
mattermost_1  | {"timestamp":"2023-03-20 16:42:33.697 Z","level":"debug","msg":"Handled HTTP request","caller":"app/plugin_api.go:970","plugin_id":"com.mattermost.apps","request_id":"njrs53fnj38w8e51ieepgjje9w","from_user_id":"a3q8phu5e3d47pjyr4jzpnzkry","path":"/api/v1/call","plugin_caller":"server/httpin/service.go:166"}

Oh, it seems I was missing act_as_user permission in my manifest.
after adding it, I now have all team, channel and post infos.
This can be closed (but should probably be documented in https://developers.mattermost.com/integrate/apps/structure/bindings/#call-context-data

@sblaisot That seems odd that this permission is required for this. Maybe the bot isn't a member of that specific channel?

For the post_menu use case, it seems act_as_user is appropriate. Maybe the framework should not allow for binding locations like post_menu

I don't think this is about the location. The expand fails if PermissionActAsUser is not granted and the bot doesn't have permission to read what ever should be expanded. IMO the code works as intended and the log messages make it clear what is going wrong.

@hanzei there is a similar problem with /command binding. Even if bot has act_as_bot & act_as_user permissions and is a member of the channel there is still no channel_id in the context.

@akuzia Do you see an related log messages in the server logs?

@hanzei cannot find anything useful in grepd by com.mattermost.apps logs. Only messages are:
debug [2023-03-23 10:53:54.112 +03:00] Handled HTTP request                          caller="app/plugin_api.go:970" plugin_id=com.mattermost.apps from_user_id=eoxm6g17gprnjmiyyt1pc4tfje path=/api/v1/call request_id=pyuts38eptg1pcriyxdsccmh4o plugin_caller="server/httpin/service.go:166"
debug [2023-03-23 10:53:54.373 +03:00] Handled HTTP request                          caller="app/plugin_api.go:970" plugin_id=com.mattermost.apps request_id=94k7msfcs3fojfunod1t3jjuac from_user_id=eoxm6g17gprnjmiyyt1pc4tfje path=/api/v1/bindings plugin_caller="server/httpin/service.go:166"
debug [2023-03-23 10:53:57.748 +03:00] Handled HTTP request                          caller="app/plugin_api.go:970" plugin_id=com.mattermost.apps request_id=j7ico5jripf5jphqm33ncqeiyo from_user_id=eoxm6g17gprnjmiyyt1pc4tfje path=/api/v1/bindings plugin_caller="server/httpin/service.go:166"
debug [2023-03-23 10:54:00.941 +03:00] Handled HTTP request                          caller="app/plugin_api.go:970" plugin_id=com.mattermost.apps plugin_caller="server/httpin/service.go:166" request_id=8pwwdwiczfy5dxcm4ufc3bjada from_user_id=eoxm6g17gprnjmiyyt1pc4tfje path=/api/v1/bindings


Catch and log Error on deployment.stop()

Otherwise ClassNotFound and Linker errors prevent the server from
removing a deployment.

Windows Build 2462 outcome was UNKNOWN using a merge of d208282ae112cb921fb4e0fc1434f865bdc3052e
Summary: Canceled (Error while applying patch; cannot find commit 63f9010c002e9cb84fcf3b4d8f66a27ccd264678 in the git://github.com/undertow-io/undertow.git repository, possible reason: refs/pull/649/merge branch was updated and the commit selected for the bui... Build time: 00:00:17

I have merged the commits and commited them under https://issues.jboss.org/browse/UNDERTOW-1363

Wonderful, thank you!


Make timer stop if all questions are answered before it runs out

added "or" operator with questions.length condition on line 60 and "timerEl.innerHTML = 00" on line 62 to reset timer


Don't delete Line Feeds in Column mode deletes.

dontDelLF.txt
dontDelLF.txt
Issue Type: Feature Request
It's probably too late, but I request a change to Column Mode editing (Shift, Alt, Click, Drag).  When a Line Feed is in a column selected, it should not be deleted on Delete.  This removes empty lines that editors will most-often want to remain.  This is also more like notepad++ column mode editing which I think got it right.
VS Code version: Code - Insiders 1.53.0-insider (861a88ebadb4335df92251faf6420b598440e082, 2021-01-29T21:49:22.151Z)
OS version: Windows_NT x64 10.0.19042

It's actually Click, Shift-Alt-Click, Drag.

Just to note if we are tracking here in #115559, adding a single space before the linefeed on the second and fourth lines of dontDelLF.txt shows a different behavior for the same column mode delete - all lines retained.

I couldn't repeat. Insanely difficult to make this maneuver. Once you have T, A, I highlighted how do you get the highlight to go away? More dragging? Backspace?  I can't get the 5 lines to stay without deleting (or backspacing) T, A, I.  If it takes "Virtual Space" to do this cleanly, it would still be nice to have.  I can understand it might be more than just slipping something in to a complex model.

To Henning:
Thanks.  I can’t get the workaround to work for me, but I appreciate your efforts.
I still fire up notepad++ occasionally, but when I saw it doing some unprompted ‘ghost writing’ I went to 99.9% VS Code editing.
VS Code really does have MANY nice features. Thanks all.
From: Henning Dieterichs @.***
Sent: Friday, October 15, 2021 2:47 AM
To: microsoft/vscode
Cc: mrmsbarnes; Author
Subject: Re: [microsoft/vscode] Don't delete Line Feeds in Column mode deletes. (#115559)
Workaround:
https://user-images.githubusercontent.com/2931520/137468086-d09c9466-7a94-444a-ae77-f9b66da96c32.gif recording
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/115559#issuecomment-944155737 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AB7C7JB5UBG37IQCJYNXSITUG72A3ANCNFSM4W5IWOSQ .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .   https://github.com/notifications/beacon/AB7C7JFSB32277X5PTDVB3TUG72A3A5CNFSM4W5IWOS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHBDKYWI.gif

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

I can only agree with @mrmsbarnes : VSCode does have a lot of nice and cool feature, but this one is almost a show stopper for me.
I have to use column mode editing a lot, and deleting LineFeed in column mode is really annoying... It would be nice if this change could be implemented!
Thanks!


Users cannot access Chant-Create page for Source with ID 637892

We recently were forwarded an email by Debra:

My name is [name]. I am currently part of a project working with [name] and [name] to index the Dominican exemplar (British Library Add. Ms 23935) in Cantus.
I've been able to access the database fine since it came back online last week, but today and yesterday have continued to run into an error message every time I try to log in and click "Add new chant" to 23935. It reads:
502 Bad Gateway
etc....

For reference, this is the source: https://cantusdatabase.org/source/637892
@dchiller and I spent some time looking into this, and we're stumped. Adding chants to other sources works just fine. Adding chants to this source on staging and locally works fine - it's only broken on production.
We tried restarting the docker containers on Production, and that didn't fix it.
Looking at the nginx logs, this is the error message that is being logged for this request:
2023/08/01 19:51:47 [error] 21#21: *717092 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: , request: "GET /chant-create/637892 HTTP/2.0", upstream: "http://<IP_ADDRESS>:8000/chant-create/637892", host: "cantusdatabase.org", referrer: "https://cantusdatabase.org/source/637892"

Set your settings.py to DEBUG=True on production and restart the service. Trigger the problem, get the traceback, and then set it back.

If the user's initials are P.H. this is the same problem I mentioned in #905 (he later reported things were working, and I think has since added some chants.) And I have been corresponding with another person working on this manuscript who didn't report anything. But I got an error just now too (on production but not staging) so...?
It may or may not be relevant that this source is being actively worked on by several people at once, which I don't think is the case for any other sources at the moment.

@annamorphism: no, the person's initials are K.K. Do you know which source was causing the issues for #905? Might be helpful.

Ok. In that case it is all the same source, but three different users have now reported difficulties with it (in addition to you and me.) Could it have to do with multiple people accessing this source at the same time (some sort of race condition?)? It would explain why it doesn't seem to happen on staging/locally.

Update: this is fixed on Production currently! The last chant added in the source was "Gloria patri" (cantus id = 909000), and we have a ton of gloria patris in the database. So it was taking way too long to go through all these chants to create a list of suggestions for adding subsequent chants.
The current fix running now on production is to simply bail out early and not provide suggestions if Gloria patri is the most recently added chant. We have a handful of ideas how to improve the performance of the suggestion feature, which we can try implementing over the next few days/weeks.

Interesting! "Gloria Patri" does indeed lead to 502s on staging but not on production as of now. Wild!
I don't think there are too many other chants that will have the same order of magnitude of results, but there could be a few other slightly problematic ones lurking.

Hi Anna,
To your last point, we checked this out as well. It turns out that none of the other chants have the same order of magnitude as "Gloria Patri". Here are the cantus id's with the highest counts:
[{'cantus_id': '909000', 'cantus_id_count': 9709}, {'cantus_id': '008097', 'cantus_id_count': 931}, {'cantus_id': '008081', 'cantus_id_count': 886}, {'cantus_id': '001328', 'cantus_id_count': 861}, {'cantus_id': '909030', 'cantus_id_count': 792} .......

From: Anna @.>
Sent: Wednesday, August 2, 2023 11:24 AM
To: DDMAL/CantusDB @.>
Cc: Lucas March @.>; Mention @.>
Subject: Re: [DDMAL/CantusDB] Users cannot access Chant-Create page for Source with ID 637892 (Issue #912)
Interesting! "Gloria Patri" does indeed lead to 502s on staging but not on production as of now. Wild!
I don't think there are too many other chants that will have the same order of magnitude of results, but there could be a few other slightly problematic ones lurking.
—
Reply to this email directly, view it on GitHubhttps://github.com/DDMAL/CantusDB/issues/912#issuecomment-1662412890, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ55ULXN5YWJZJ24SWT4Y6LXTJWKBANCNFSM6AAAAAA3AI25SU.
You are receiving this because you were mentioned.Message ID: @.***>

very cool, @lucasmarchd01 ! Now I'm all set for CantusTriviaNight: "what is the SECOND most common chant in the Cantus Database?"


DEFAULT_MODEL not working when using Azure Models

Hey,
I love this UI, but I have one problem. I want the default model to be GPT-3.5 every time the user want to start a conversation - no matter which model they used for their previous conversation (e.g., GPT-4). Right now, the default in the drop down bar when starting a new conversation is whatever model you picked from your old conversation.
I tried to play around with DEFAULT_MODEL but somehow does not seem to work for Azure OpenAI model??
I also tried playing around with this code - https://github.com/mckaywrigley/chatbot-ui/blob/main/components/Chat/ModelSelect.tsx - for a long time. I have not found a solution.
Anyone who has found a solution on this? Or an easy fix to ensure default model is the GPT-3.5 from azure, and GPT-4 only is selected if the user actively decide to choose it from the dropdown box (no matter if the users previous conversation was with GPT-4 or nor)

open utils/server/index.ts
replace line 35 :
url = ${OPENAI_API_HOST}/openai/deployments/${AZURE_DEPLOYMENT_ID}/chat/completions?api-version=${OPENAI_API_VERSION};
with
url = ${OPENAI_API_HOST}/openai/deployments/${model.id}/chat/completions?api-version=${OPENAI_API_VERSION};
enjoy


Losing combo and node color after activate-relations

When activate-relations is enabled by combo/node click the color of all combos and nodes is set to white until activate relations is disabled with a click on the canvas.
Link to example code: https://codesandbox.io/s/ecstatic-ganguly-mhhc0?file=/index.js
How to reproduce:

The combos have different colors
Click on any node to activate relations
You will see that all the combos/nodes background color is changed to white

Expected behavior:
•	Combos and nodes to retain their colors regardless of activate relations enabled or disabled.

The default  'active' and 'inactive' styles are taking effect when you are using active-relations with default configurations. You could assign different activeState and 'inactiveState' for active-relations behavior and design your own state styles in comboStateStyles, nodeStateStyles, and edgeStateStyles:


ColorPicker's size theme constants don't have effect

Godot version:
3.2
Issue description:
So there's stuff like h_width, sv_width and sv_height in ColorPicker, but changing them does nothing.
Steps to reproduce:

Add a ColorPicker
Set sv_width to some insane value like 100000
Run the game
The ColorPicker still has default size

Should these constants also be renamed? I have no idea what they do without looking at the class reference :slightly_smiling_face:

In https://github.com/godotengine/godot/blob/master/scene/gui/color_picker.cpp, it looks like those constants are set once at creation and then not used again. I tried throwing a call in one of the update functions to set the uv size using sv_width and sv_height and the ColorPicker changed. It might take a little work to make sure the overall ColorPicker is formatted correctly with each change.


Make sure publish() endpoint will return a valid PublishResponse

This PR adds the missing MessageId in publish() response.
It's required by some other languages AWS SDK (JavaScript is so forgiving), hence I guess this is might be a good addition.
(I also made sure the type definition will also return a PublishResponse as defined in the AWS SDK)

Very nice work!


Securing the URL Endpoint

Is there a way to secure this function with an access key and refresh key? Or some mechanism so that if this is deployed that the URL is just open to the world for anyone to shorten URLs.

I must have seen an earlier version with multiple endpoints. When I found this project, I was looking for a shortener api that I could call to create short links without a management frontend. Your FE was super nice though for displaying and checking on links.  I guess in V3 its only a redirect api with the CloudFlare rules for re-writes.
I still love the project and enjoyed working through all of this with your help of course.  If you would like I can open an issue/feature request for a more complete API but I am not sure if that is in your roadmap.
Again thank you
-Fatpacket

That make sense the previous version was doing that. The current is much simpler.
The more complete API would be in the TinyBlazorAdmin project under the /api folder.
I would like to extract the azFunction but only if I can keep it as budget friendly and simple to deploy.  Those are prime requirement for this project.
I will close this issue for now. Keep watching TinyBlazorAdmin as I might move out the API (I'm interested at making a CLI so I would need that)
Thank you for your help validating the documentation.

@all-contributors add @fatpacket for doc


Polymer 3.0 support

Hello,
Is there an estimated time when we could expect a new version of polymerfire which will be built according to the new Polymer 3.0 standard and stored in NPM?

I would like to try creating a PR over the week and see if it is going to be merged.

Oh wait... it uses some sort of builder. I think the Polymer team has that builder that auto-updates it to Polymer 3.0 standards...

This element will be auto-upgraded once the modulizer is more robust.

I took a look at this trying to modify and ran into issues.  The modulizer didn't transform the hybrid polymer elements so the code would need to be updated to the  class syntax for modulizer. However after conversion I had an issue importing the firebase code. It's using a global variable (firebase)  which works fine for HTML imports but with modules that value wasn't being pulled in with imports. The firebase code isn't exporting anything for ES2015 modules to use.  Without a build tool I wasn't sure how to proceed from there especially in regards to using only specific components.

Although I would love to just use the modulizer. I have to review the whole code (and might do a re-write of some parts). Given that the modulizer is still in its alpha-stage, and have some problems... I don't have a better idea on what's the best alternative.
I also want to think if it is possible to rewrite the behaviors to mixins and add a Firestore behavior for backwards compat.

Any update on this folks? Not long until the end of Q1 (aka 3.0 launch).
Does the current build work in a 3.0 project?

We should probably just make a PR. I made a WIP PR (#344) against firestore branch since it is the most important part for me.
Can we split the work somehow?

@zevdg I just tried running the modulizer on the project and it produced the same thing (as far as I can tell) as what @Mash19 reported. It converts the imports, but not the Polymer(); call.

Modulizer won't do everything for us. It just requires some manual work to make it Polymer 3 - compatible.

Hi
I'm new to polymer, and planning to use in a new project and that will use firebase too, on reasearch I found this issue, any thing to worry? or its ok to use Firebase Javascript SDK until you got back polymerfire working? or for now better use version 2.0 then migrate to 3.0 when all things are solved for last version?

@cwichoski If you start a new project with polymer 3, it's probably simpler to use the normale firebase SDK instead of polymerfire. Since the developer experience of Polymer 3 (with LitElement) and React are now practically identical, I would have a look at React + Firebase.

@Mash19 @merlinnot have you guys had any luck with this?

That's the current status: @intcreator https://github.com/firebase/polymerfire/issues/353

I started playing around with PWA Starter Kit (https://polymer.github.io/pwa-starter-kit/) and then found this tutorial Simple ToDo application using React Redux and Firebase (https://github.com/codewithbernard/react-redux-firebase), and it connects to Firebase... So far, I was able to reproduce the connection to Firebase in the PWA Starter Kit, yet could not import the Firebase modules using the ECMAScript 6 syntax...  The imports worked for firebase-app and firebase-database, not for firebase-database - so, I imported all three using script tags of the main file.

@Anid4u2c this isn't really the right repo/issue for that specific problem.  https://github.com/firebase/firebase-js-sdk/issues/100 is the issue to track.

@zedvg ...okay, will move it.

Try https://github.com/iceflow19/polymerfire
works for me, including geofire

https://www.npmjs.com/package/polymerfire3
Hope it helps you :)


latedef: false doesn't work in a particular case

The following code reports that 'y' is not defined, even if latedef is set to false:
(function(){
    var x = function(){
        y();
    };

    var y = function(){
        x();
    };
})();

This one works correclty, though:
    var x = function(){
        y();
    };

    var y = function(){
        x();
    };

i don't have the numbers off the top of my head but this is a duplicate and it has been resolved recently

This was fixed in GH-133. We will put the updated version on the website soon.

I tested this against the "master" version. Are you sure it's fixed?

I'll check again tonight.

I'm having the same issue on node-jshint v0.5.6, but it is strange that it doesn't happen always..
latedef:false doesn't work properly on this module but it does work properly on other modules like array/unique so I'm not sure what is causing the problem.
my settings:
/*jshint eqnull:true, noempty:true, undef:true, latedef:false, boss:true */
/*global define*/

this example is interesting:
/*jshint undef:true, latedef:false */
(function(){
    bar();
    function foo(){
        ipsum();
    }
    function bar(){
        foo();
    }
    function ipsum(){
        return true;
    }
}());

based on it the problem is probably on the way jshint checks what is available on the current scope (since bar() isn't considered an error and ipsum() is)...


Allow for multiple possible aliases for test data files

To ensure that tests are understood in a business context it is necessary to have descriptive names for the test data .json files. For example, the following scenario -
Given I have created 'an entity record with a particular field value'

This provides needed context to the scenario, but it demands a test data file named an entity record with a particular field value.json This results in a lot of data files being created with only minor differences.
It would be better if we could refer to the same test data object graph by many aliases.

I believe the best way to approach this is to retain the current 1-to-1 with the step and the data file name but to instead implement something similar to the tsconfig.json extends property to encourage reuse of test data files. Possibly using folder structure to help with organisation.


fix: update README for beta tag

This PR fixes the beta tag to the README's section about v10. I used a fix type commit to make sure it gets updated on npm.

Apparently prettier wanted to do some edits to other parts of the readme...

@iiroj not sure about the fix though. What's the purpose of publishing a new version? I assume the documentation is read online anyways.

@okonet if a new version doesn’t get published, the readme at npmjs.com website won’t get updated. That’s read from the package.

@iiroj I think that's fine with me. I personally never read readme on npmjs.org so I think we won't miss too many people. I'll squash as docs if you're okay with that. Just don't won't getting a new version released without an actual change to the lib.

@okone, sure, but with doc the change won't be propagated to npmjs. I don't mind, but that's what I always use. There's also the command npm view lint-staged readme which shows it from the dist.

:tada: This PR is included in version 10.0.0-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Change exceptions to extend Error.

This changes exception classes generated for --target thrift-server so that they extend ErrorThriftLike instead of ThriftLike. There's a corresponding thrift-server change to add the ErrorThriftLike class.
As mentioned in the GitHub issue, this is useful because it causes Thrift exceptions to have stack traces and because some frameworks expect exceptions to derive from Error. The GitHub issue mentions graphql-js. Jest's toThrow() function would also benefit from this. Here's an example:
await expect(thriftClient.someFunction()).rejects.toThrow()

toThrow doesn't identify Thrift exceptions as exceptions because they don't derive from Error and so it will return false in such cases. Part of the blame could fall on Jest, because perhaps toThrow should return true for any rejected promise regardless of the type of object being throw, but I think some of the blame still falls on Thrift.
A downside of extending Error is that there's a naming collision when developers define fields named name, message, stack, etc in their Thrift exceptions (because these are defined by the super class). I think this is an acceptable tradeoff. FYI tsc complains if someone defines a field that differs from the super class. For example, if someone has a Thrift exception with 1: required i32 message (because message must be a string) or 1: optional string message (because message is required).
I tried to avoid the naming collisions by manually adding Error to the exception class's prototype chain. It might avoid the tsc compile errors when there's a naming collision but it doesn't really eliminate the problem of same-named fields being used for two different things. And so I think manually changing the prototype chain is a bad solution.
Remaining work:

Fix tests.
Update README.md to mention that end-users need to require the new version of thrift-server which includes ErrorThriftLike.
Update README.me to mention the naming collision limitation.
tsc complains for naming collisions, and that's fine. Maybe the Thrift compiler should check for and report on collisions? Would probably be a friendly user experience. One challenge is different JS implementations define different properties on their Error class.
I didn't change the code generated for --target apache. It looks like those classes also don't derive from Error. They probably should.

I can clean this up a little (fix tests, update documentation as needed, etc), but wanted to get feedback from Credit Karma folks to make sure I'm heading in the right direction before spending more time on it.