evecs.txt and projections.txt

Hi, I have a problem with the result. I have 1267 SNPs from 100 samples. The geno-file is:
1267 100
1111000010101...
0101000101001...
0100100010000...
......
After calculation, I found that the evecs.txt contains 1267 rows and the projections.txt contains 100 rows.
which file I should use for displaying the genetic structure of the 100 samples. I think I should use projections.txt, is that right?

Yes, you should be using 'projections.txt' as these are the sample genotypes projected onto the principal components (evecs.txt).

Yes, you should be using 'projections.txt' as these are the sample genotypes projected onto the principal components (evecs.txt).

Thanks for your help. I will use projections.txt. ProPCA is an excellent tool for big genotype matrix. Other tools, such as GCTA, generate principal components of sample genotypes into txt file with 'eigenvec' suffix. So, maybe there is a litter confusion when someone uses ProPCA instead of GCTA or plink. specifically when the ProPCA package storage principal components of sample genotypes in the example_evecs.txt in example-folder.


Publish a recent version to NPM

Quoting https://www.npmjs.com/package/multi-loader

version 0.1.0
last publish 4 years ago

Sad panda 🐼 😢  You removed the issue template, so we have to close your issue as invalid. Please don't ignore Issue or Pull Request templates.

It has begun. The machines have taken over...


Unknown command

What is the purpose of your issue?

[x] Bug
[ ] Feature Request
[ ] Question
[ ] Other

Description

Don't know if I'm just too dumb for this, or there is some problem.
I'm using Linux Mint 19.3 Tricia
My issue is I've installed PyPI with pip3 (python 3.6), installed spotdl, pip says it's installed.
Yet I try the commands and all I get is command unknown. While installing the spotdl it says
Failed building wheel for pathlib
Running setup.py clean for pathlib
Running setup.py bdist_wheel for unicode-slugify ... error
Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-rytw_b34/unicode-slugify/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/tmpvahpj4smpip-wheel- --python-tag cp36:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
This is happening to unicode-slugify, PyYAML and lyricwikia.
After these it shows the installed packages:
Successfully installed PyYAML-5.3 appdirs-1.4.3 beautifulsoup4-4.8.2 certifi-2019.11.28 chardet-3.0.4 idna-2.9 logzero-1.5.0 lyricwikia-0.1.11 mutagen-1.44.0 pafy-0.5.5 pathlib-1.0.1 requests-2.23.0 six-1.14.0 soupsieve-2.0 spotdl-1.2.6 spotipy-2.9.0 titlecase-0.12.0 unicode-slugify-0.1.3 unidecode-1.1.1 urllib3-1.25.8 youtube-dl-2020.3.8
I don't know much about pip or Python, and I'm quite new to Linux, I've switched from win a couple of months ago.
plz halp
cheers, David
Log

You need setuptools and wheel packages too.
$ pip3 install setuptools wheel -U

Should work then.
We should probably put these in our setup.py too.
On Sun, 15 Mar, 2020, 10:50 PM PersonalDavid<EMAIL_ADDRESS>wrote:

What is the purpose of your issue?

Bug
Feature Request
Question
Other

Description
Don't know if I'm just too dumb for this, or there is some problem.
I'm using Linux Mint 19.3 Tricia
My issue is I've installed PyPI with pip3 (python 3.6), installed spotdl,
pip says it's installed.
Yet I try the commands and all I get is command unknown. While installing
the spotdl it says
Failed building wheel for pathlib
Running setup.py clean for pathlib
Running setup.py bdist_wheel for unicode-slugify ... error
Complete output from command /usr/bin/python3 -u -c "import setuptools,
tokenize;file='/tmp/pip-build-rytw_b34/unicode-slugify/setup.py';f=getattr(tokenize,
'open', open)(file);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d
/tmp/tmpvahpj4smpip-wheel- --python-tag cp36:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
This is happening to unicode-slugify, PyYAML and lyricwikia.
After these it shows the installed packages:
Successfully installed PyYAML-5.3 appdirs-1.4.3 beautifulsoup4-4.8.2
certifi-2019.11.28 chardet-3.0.4 idna-2.9 logzero-1.5.0 lyricwikia-0.1.11
mutagen-1.44.0 pafy-0.5.5 pathlib-1.0.1 requests-2.23.0 six-1.14.0
soupsieve-2.0 spotdl-1.2.6 spotipy-2.9.0 titlecase-0.12.0
unicode-slugify-0.1.3 unidecode-1.1.1 urllib3-1.25.8 youtube-dl-2020.3.8
I don't know much about pip or Python, and I'm quite new to Linux, I've
switched from win a couple of months ago.
plz halp
cheers, David
Log
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ritiek/spotify-downloader/issues/686, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE27U5UYUPJFAOHEUFEXL23RHUE6BANCNFSM4LLGGMKQ
.

Thank you for the answer!
Now it's getting wheels during installation, but yet the same, when I run
$ pip3 list
it lists spotdl, and all the packages it needs to work:  beautifulsoup4 and etc.
Pip3 says there are no broken requirements, everything looks fine, but then I try to run
$ spotdl ...
spotdl: command not found

This might be related to #451. See if it helps.

It helped, thanks a lot dude! Sorry for my debility and thank you for this great tool!! :smile:


Path of Icon not work in windows 10, packed by asar

If asar is set to false , everything works fine, however, when asar is true
node-notifier can't resolve the path which contained asar file.
For example:
file:///path/to/example.asar/static/test.png --> should get test.png from example.asar
This is not work in Windows, Mac works fine.
https://github.com/electron/asar

Due to the nature of asar files, node-notifier cannot run under asar.
asar binaries cannot have executables within. See here for more information.

Why not use Electron's native notifications?

Because it only works in Windows 10, thanks for your reply.


invalid regular expression in safari

https://github.com/renanbastos93/image-to-base64/blob/be695c53d656529b59068d83878f184c14654c70/image-to-base64.js#L8
This line gives a problem in safari: invalid group specifier name.
apparently something to do with this:
https://stackoverflow.com/questions/51568821/works-in-chrome-but-breaks-in-safari-invalid-regular-expression-invalid-group

@jan-bogaerts
🤕 Oh nooo, Do you have an idea? Let's go to improve it together?

Hi Renan,
I tested the regular expression with this site https://regex101.com/ then I received an error.

If you escape delimiter should be work fine.
Cheers!!!

Hi Renan,
I tested the regular expression with this site https://regex101.com/ then I received an error.

If you escape delimiter should be work fine.
Cheers!!!

Hi @tomtapia ,
Well, what version are you using?

Hi Renan,
I tested the regular expression with this site https://regex101.com/ then I received an error.

If you escape delimiter should be work fine.
Cheers!!!

Hi @tomtapia ,
Well, what version are you using?

I'm using "image-to-base64": "^2.1.1" from NPM repository.

wow, thanks.

I tested using this regex on regex101 ant it was successful.

Yeah!!! You're right, it was my mistake. I'll keep trying to make this module work with my code.
Thanks a lot for your help. 👍


Publish S01E01

[x] (H) collect links
[x] (J) merge and trim audio files
[x] (J) add new podcast episode (use content for links etc from guests)

I figured we can also create a discussion thread for each new episode for discussions related to that particular one as the topics/issues will be closed when handled.
I made one for episode 0, the pilot here: https://github.com/fossified/podcast/discussions/17

Done


Fix workflow status when task is canceled

Fix Mistral workflow status when task is canceled. Currently, when a task is canceled, the workflow status is set to error. The workflow status should be set to canceled. Also, when a canceled action execution completes, the action execution will be updated from canceled to its new status. This should not be the case because the action execution has already been canceled. Before merging this patch, please ensure mistral fork is caught up with mistral upstream master. This requires another fix from mistral upstream.

Good catch - the st2 code change looks good to me :+1:

Just to confirm - this should fix intermediate examples.mistral-test-cancel Robot test failures we are seeing?
I assume it should, but I still see those tests intermediately failing on build server...


Firebase cloud messaging - all notifications at once

Hi ! I would need your help. I have an application mobile (android and iOS) with flutter and firebase cloud messaging.
My case: I receive 4 notifications on the device (as an example) and I want to read all of them when I click in the application’s icon. Currently I have to click each notification to read it and be able to create the widgets
How can I do it ?
For both Android and iOS ! Thanks !!!

Hi @sergitovar91
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you


clients/posts: add onboarding cards to admin-empty state on public page

Also removed the wrapping <Link /> from the AnimatedIconButton component, as it was causing hydration issues, as all usages already had a parent Link wrapping.


Fix apt unauthenticated packages error

During converge, apt failed to install nzbdrone with the following error:
STDERR: E: There were unauthenticated packages and -y was used without --allow-unauthenticated

Switching to sonarr's currently documented key ID fixed that problem.
Test kitchen converge also failed with 404s from apt when installing the dirmngr & apt-transport-https packages. Moving the apt_update resource earlier in the recipe ensures that apt's DB is up to date when installing them.
I confirmed that kitchen test now succeeds with these changes.

@aogail Thanks Ben! I've not actually been able to spend much time in chef-land these days. Do you have any interest in taking over this repo?

@jamesconant You're welcome :D And yes if you're looking for someone to take over I would be interested. The cookbook just worked for me for a while, so I think it would be a commitment level I can make.

@aogail Hi again Ben, apologies for the delay. Transferring over to you shortly!

@aogail I tried transferring, but it blocked me because it says you already have a sonarr-cookbook repo. Tried renaming as well. Maybe you have a fork that's blocking the transfer?

@jamesconant  Indeed, I still had my fork from this PR :) I've deleted it.


Fix application of maxed lists following page refresh

Issue

When there are too many resources to show in a list we enter max state
When in max'd state we force the user to select filters to restrict the number of results (changing filters results in new http requests with the filters)
We persist the state of the list to local storage. This includes filters but does not include the max flag
When the user re-visits the list after page refresh instead of fetching all resources we only fetch those applicable to the filter (which will be a small subset of all resources). As the max flag isn't persisted we assume we've fetched all resources. Any changes to the filter are then applied locally to the subset of resources... which may not contain any applicable to the new filter

Fix

Persist the list's max state such that when the list loads again all filter changes correctly result in http requests
This needed a fix in the way we watch the filters for changes (we block this watch until all filters report as ready)
Fix downside

Lists cannot ever leave the max state. All changes to filters will result in http requests. User would need to clear their local cache to reset the list (we have a button for this in the user's profile page)

Tested

Different types of org/space filter setups

orgs with no spaces
orgs with some spaces under maxed, some over

Different types of lists
Tested with UI_LIST_ALLOW_LOAD_MAXED true (allow user to overrule maxed state and fetch everything)

Codecov Report

Merging #559 (69f6a91) into master (b4438a9) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #559   +/-   ##
=======================================
  Coverage   28.65%   28.65%
=======================================
  Files          60       60
  Lines        5126     5126
=======================================
  Hits         1469     1469
  Misses       3470     3470
  Partials      187      187


💡html -> render

Describe a problem.

Describe the solution you'd like. Mockups are welcome.

Are there any alternatives?

https://github.com/codex-team/editor.js/issues/1515


Abort structure analysis on exceptions

Structure analysis shouldn't raise exceptions, but if it does, it shouldn't crash the program. Issues like https://github.com/jonpalmisc/ObjectiveNinja/issues/14 shouldn't cause crashes.

Depends on #15, as aborting with no information is not useful.


Just a little thing for UTC and time Zone Field

last working Home Assistant release (if known):
0.94.0b7
Operating environment (Hass.io/Docker/Windows/etc.):
raspberry pi 3 ->Hass.io
Component/platform:
Configuration
Description of problem:
We must delete everything in the field, to have the choice of time zones, it would be better to have the choice directly by clicking on the arrow.

Please use the issue template.

I did it, thanks for reopening

I think it's very understand what you mean here.
What do you mean by time zone field? Please try to explain in more detail and rephrase.

When i click on the arrow on the right of the field, I've got only "Europe/Paris", but if i delete all the characters in the field and click on the arrow i'v got all the choice of time zones.
I hope you understand now.


add tab completion support for gitbash

Currently tab completion does not work in gitbash, because windows does not use "/" as directory separator. The generated bash functions therefore do not have valid names. e.g.
complete -o filenames -F _C:\Users\user\AppData\Roaming\Python\Python310\Scripts\doit C:\Users\user\AppData\Roaming\Python\Python310\Scripts\doit

Codecov Report

Merging #433 (0259f39) into master (6e58b55) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #433   +/-   ##
=======================================
  Coverage   99.24%   99.24%
=======================================
  Files          60       60
  Lines        9134     9135    +1
=======================================
+ Hits         9065     9066    +1
  Misses         69       69

Impacted Files
Coverage Δ

doit/cmd_completion.py
98.37% <100.00%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

On my way.
-Tom
On Jul 31, 2022, 11:44 AM -0400, Codecov Comments Bot @.***>, wrote:

Codecov Report

Merging #433 (0259f39) into master (6e58b55) will increase coverage by 0.00%.
The diff coverage is 100.00%.
@@           Coverage Diff           @@

master     #433   +/-
=======================================
Coverage   99.24%   99.24%
=======================================
Files          60       60
Lines        9134     9135    +1
=======================================

Hits         9065     9066    +1

Misses         69       69
Impacted Files
Coverage Δ
doit/cmd_completion.py
98.37% <100.00%> (+0.01%)
⬆
Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute  (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e58b55...0259f39. Read the comment docs.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

merged. thanks.


Update gradle

Update Gradle
Some dependencies are running a higher gradle and soon can no longer be able to read by the current version of gradle

As per review, there's no need to update the gradle as long as dependencies are not yet fully deprecated.


StrongEmphSuperNode not properly parsed after special chars

There's a testcase here: https://github.com/martinklepsch/pegdown/commit/aa36ef5a779f093b02b8cd9e5cda93c770170782
Somehow parsing (**this** ... will not properly turn this into a StrongEmphSuperNode.

That is correct. Emphasis markers have to be preceded by a blank.

Interesting. I didn't know. How does one achieve something like (this is bold then? Apparently Github Flavoured Markdown supports it.

Yes, GFM has a lot of changes. Some good, some not so much. For example, I recently found out that you can indent nested lists with just one space for second level, and two spaces for the second.
It is changing an already loose spec for Markdown in areas where it isn't that critical.

Forgot to answer your question:
(test

See:
(test

As far as I can tell, CommonMark supports this: http://spec.commonmark.org/0.22/#example-355
It looks like the most complete markdown specification.


Fix critical-section impl so it disables all irqs.

It was disabling irqs only in ICER[0], but there's more at ICER[1]. Softdevice irqs are always in ICER[0], so ICER[1] doesn't need any masking, but we still need to disable and restore all.

As noted in the matrix channel, have been running with this patch on two of our lab units for 15h each, without further failures of our "SPI task stall" issue, when previously we couldn't run for more than somewhere between a few seconds and a few minutes, or about an hour at most.
We've also gone through a function by function analysis of the scenario that must have led to our stall issue, and confirmed that the issue we've been observing would definitely have been a possible outcome of the problem this patches, where the RTC1 timer interrupt was basically being interrupted in the middle of its critical section (which shouldn't be possible) by the SPIM2 interrupt (which wasn't properly disabled before this patch), resulting in a second critical section being entered as though it was a nested critical section in the first one, leading to the race condition which let the embassy task that was doing SPIM2 work end up with the RUN_QUEUED flag set despite not being actually in the run queue, at which point it was in the twilight zone and would never be polled again.
It appears a stress test case could be developed with just one task waking on an embassy Timer::after (maybe a few times a second) while a second task is doing rapid SPIM2 writes many times a second, and as long as their timing isn't synchronized then eventually (I'm guessing within a few minutes at most, for the right combination) the second task would get stalled.  If the second task updated a loop counter and the first task read it, it could report the failure as soon as it saw the counter stop incrementing.


Repository-related improvements

Description
Adding repository related improvements so make the project more professional and easier to manage/contribute to.
Tasks

[x] New labels
[x] Issue templates
[x] Pull request templates
[x] Code of Conduct
[x] Contributing guidelines
[x] CodeQL
[x] Labeler
[x] Discussions
[x] Sponsor Page
[x] Security Vulnerability Report
[x] Logger milestone
[x] Move documentation out of README.md and into docs/
[x] Improve README.md

[x] shield.io tags
[x] Contrib.rocks
[x] Link to docs/

[x] Add dev documentation to docs/

Let's do this 😎

DONE!


Force load history service

fix https://github.com/CodinGame/monaco-vscode-api/issues/529

@CGNonofr FYI can confirm that it works locally. PR in mlc comes soon...


Add to .forEach documentation how to deal with a iteration that you don't wanna write

This can happen when you delete with returnChanges = true and expect old_val to have the old data but if two processes are concurrently deleting, one can end with old_val = nil, so the user should know that in this case he needs to return an empty array from forEach.

The documentation for forEach could benefit from being more detailed. See https://github.com/rethinkdb/rethinkdb/issues/3798#issuecomment-75135022 and https://github.com/rethinkdb/rethinkdb/issues/3798#issuecomment-75139364

I see the comment from @atnn that forEach is "a map that combines the results by adding numbers and concatenating arrays," but is that an actual use case for this command that needs to be documented, or is it a kind of quirky byproduct? My impression was that it's really only designed for write queries.
r.table('users').forEach(function (doc) {
  return r.table('foreach').insert({posts: doc('posts')});
})

That appears to return just what you'd expect from inserting n documents.

I see it as a by-product, but it would be good to document the exact behavior of the forEach somewhere. There are a few corner cases where these details actually matter, like in @thelinuxlich 's use case.
I don't think we should add any non-write examples though.


feat(go/adbc/driver/flightsql): Improvements for flightSql error details

See https://github.com/apache/arrow-adbc/issues/2179

Closing as it seems to not improve anything.


运行 api server： python jina_server_demo.py报错   ModuleNotFoundError

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
(pytorch) E:\text2vec\examples>python jina_server_demo.py
DeprecationWarning: pkg_resources is deprecated as an API (raised from C:\Users\86187.conda\envs\pytorch\lib\site-packages\pkg_resources_init_.py:121)
DeprecationWarning: Deprecated call to pkg_resources.declare_namespace('google').
Implementing implicit namespace packages (as specified in PEP 420) is preferred to pkg_resources.declare_namespace. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages (raised from C:\Users\86187.conda\envs\pytorch\lib\site-packages\pkg_resources_init_.py:2870)
DeprecationWarning: Deprecated call to pkg_resources.declare_namespace('google').
Implementing implicit namespace packages (as specified in PEP 420) is preferred to pkg_resources.declare_namespace. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages (raised from C:\Users\86187.conda\envs\pytorch\lib\site-packages\pkg_resources_init_.py:2870)
DeprecationWarning: Deprecated call to pkg_resources.declare_namespace('google.logging').
Implementing implicit namespace packages (as specified in PEP 420) is preferred to pkg_resources.declare_namespace. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages (raised from C:\Users\86187.conda\envs\pytorch\lib\site-packages\pkg_resources_init_.py:2870)
DeprecationWarning: Deprecated call to pkg_resources.declare_namespace('google').
Implementing implicit namespace packages (as specified in PEP 420) is preferred to pkg_resources.declare_namespace. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages (raised from C:\Users\86187.conda\envs\pytorch\lib\site-packages\pkg_resources_init_.py:2349)
UserWarning: DistributionNotFound(Requirement.parse('pytest==6.2.4'), None) (raised from
C:\Users\86187.conda\envs\pytorch\lib\site-packages\hubble\executor\helper.py:698)
Traceback (most recent call last):
File "E:\text2vec\examples\jina_server_demo.py", line 15, in
with f:
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\orchestrator.py", line 14, in enter
return self.start()
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\flow\builder.py", line 33, in arg_wrapper
return func(self, *args, **kwargs)
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\flow\base.py", line 1830, in start
self.enter_context(deployment)
File "C:\Users\86187.conda\envs\pytorch\lib\contextlib.py", line 448, in enter_context
result = cm_type.enter(cm)
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\orchestrator.py", line 14, in enter
return self.start()
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\deployments_init.py", line 1008, in start
self.enter_context(self.shards[shard_id])
File "C:\Users\86187.conda\envs\pytorch\lib\contextlib.py", line 448, in enter_context
result = cm_type.enter(cm)
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\deployments_init.py", line 112, in enter
pod = PodFactory.build_pod(_args).start()
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\jina\orchestrate\pods\factory.py", line 39, in build_pod
cargs.uses = HubIO(_hub_args).pull()
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\hubble\executor\hubio.py", line 1323, in pull
install_package_dependencies(
File "C:\Users\86187.conda\envs\pytorch\lib\site-packages\hubble\executor\hubapi.py", line 109, in install_package_dependencies
raise ModuleNotFoundError(
ModuleNotFoundError: Dependencies listed in requirements.txt are not all installed locally, this Executor may not run as expect. To install dependencies, add --install-requirements or set install_requirements = True
Expected Behavior
No response
Steps To Reproduce
pip install jina已安装
Environment
- OS: windows
- Python:
- Transformers:
- PyTorch:
- CUDA Support (`python -c "import torch; print(torch.cuda.is_available())"`) :

Anything else?
No response

jina 我重新测试了一遍，是可以正确执行的。
pip install jina=3.17.0

python3.10 的环境。
先起jina_server, 再jina_client请求服务。
执行结果：


fix: use relative layout to stick FAB position to bottom of layout

This is the only solution I found online that actually works
Emulator screenshot

instead of this PR, here's what i think is the right way to do this:

add a constraint bottom2bottom in fragment_library/viewpager2 https://github.com/CMPUT301F20T21/Book_Friends/blob/5efececf44f11a64b614ee61dcddd14955c26f23/app/src/main/res/layout/fragment_library.xml#L20
remove the 48dp padding bottom in both constraint layouts (owned/borrowed) https://github.com/CMPUT301F20T21/Book_Friends/blob/5efececf44f11a64b614ee61dcddd14955c26f23/app/src/main/res/layout/owned_list_book.xml#L6


Request parameters with multiple values: CollectionFormat equivalent?

Is there an equivalent capability for @CollectionFormat(feign.CollectionFormat.CSV) from feign-core?
Objective: I have a request parameter dataset to which I pass a list of Strings.  Desired behavior is to get dataset=set1,set2,set3.  I currently obtain dataset=set1&dataset=set2&dataset=set3.
A lookthrough the source code and AllFeaturesFeign test case didn't turn up a means to accomplish.  Is this a supported use case / configuration for feign-reactive?

Seems we didn't implement support of @CollectionFormat.
Why don't you like this option dataset=set1&dataset=set2&dataset=set3 ?

Purely a matter of syntax, I'm sure.  Just seeking to send per a prescribed contract.  I recognize that the dataset=set1&dataset=set2&dataset=set3 should be accepted by the receiving party, though I don't yet have an endpoint to integrate with.  Was verifying whether I'd overlooked some alternative in the code base.

fixed in 3.1.5


Cannot read properties of undefined (reading 'searchInput')

TypeError: Cannot read properties of undefined (reading 'searchInput')
at Wc.saveState in src/vs/workbench/contrib/search/browser/searchView.ts:1919:25
at <anonymous> in src/vs/workbench/browser/parts/views/viewPaneContainer.ts:736:37
at Array.forEach (<anonymous>)
at O.saveState in src/vs/workbench/browser/parts/views/viewPaneContainer.ts:736:14
at <anonymous> in src/vs/workbench/common/component.ts:27:9
at g.invoke in src/vs/base/common/event.ts:701:17
at n.deliver in src/vs/base/common/event.ts:908:22
at a.fire in src/vs/base/common/event.ts:869:24
at T.flush in src/vs/platform/storage/common/storage.ts:507:25
at <anonymous> in src/vs/platform/storage/common/storage.ts:281:10

Go to Errors Site

/duplicate #171527


Block-type changes can affect adjacent sibling block

Repro:

Navigate to the Draft.js homepage
Add a few blocks of text
Triple-click a block of text

This will select the entire block

Change the block type to H1

Expected:

The block type for the selected line changes to a heading

Actual:

The block type for the selected line and the following line changes to a heading

As I typed this bug with Github Markdown editor, I noticed it also demonstrates this behavior (triple-clicking a line and applying bold will drop the trailing ** at the beginning of the next line). Maybe this is out of the hands of Draft. However, I do believe that fixing the issue would lead to more reasonable UX.

I should also add…
Killer work on this project, team. I have been exploring contentEditable-n-React solutions for a few weeks now. This project is a huge leap forward. Thanks for sharing it!

Thanks @gscottolson!
I think the problem here is that the SelectionState is wrapping into the next line, and probably looks something like:
SelectionState {
  anchorKey: 'a',
  anchorOffset: 0,
  focusKey: 'b',
  focusOffset: 0,
  ...
}

One option would be to change getDraftEditorSelectionWithNodes to be more aware of this possibility and normalize the DOM selection to a SelectionState that just includes block a. Another would be to make block-type and inline-style changes not apply to the second block, within modifier code.
I'm thinking the first option might be a little cleaner, though it means that there would be no state distinction between selecting an entire line of text and selection the text plus the newline. Given that we pretty much ignore the newline as content, though, that might be fine.
What do you think?

I think the first solution seems reasonable. Thanks for the quick reply.
FWIW, Facebook Notes does not exhibit this behavior. How is this selection case handled in that product?

Looks like Notes does have this problem. :)

Excellent. Thanks for the quick fix! :tophat:


[feat]: Update for Vite 4.x support

Clear and concise description of the problem
With Vite 4's released, it'd be great to update the peerDependencies to allow it to work with Vite 4.x (assuming no other changes are needed).
Suggested solution
PR to address the issue: https://github.com/antfu/vite-plugin-restart/pull/17
Update peerDependencies:
  "peerDependencies": {
    "vite": "^2.9.0 || ^3.0.0" || ^4.0.0"
  },

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

In my limited testing, I can confirm that just bumping the peerDependencies appears to work fine with Vite 4.x


renal interstitial pericyte - add textual definition and revise logical definition

Currently has very broad logical definition: pericyte and part_of some kidney.  Should have some restriction to kidney interstitium
Needs textual definition - potential references @emquardokus to add
Relationship to mesangial cells is confusing

Only some mesangial cells defined as pericytes in textual definitions.

For reference:
The renal interstitium is defined as the intertubular, extraglomerular, extravascular space of the kidney.  Its distribution varies within the kidney; it accounts for approximately 8% of the total parenchymal volume in the cortex and up to 40% in the inner medulla (6,7). The term “renal interstitium” is often inadequately used to refer to the peritubular interstitium (the space between tubules, glomeruli, and capillaries); the periarterial connective tissue and the extraglomerular mesangium are considered specialized interstitia (1). It is debated whether microvessels and capillaries, which are located within the peritubular space, are actually part of the renal interstitium or just run through it (1). Furthermore, lymphatics are considered interstitial constituents (1). The tubular interstitium in the cortex and medulla differ with regard to their cellular constituents, extracellular matrix composition, relative volume, and endocrine function, justifying the consideration of cortical and medullary interstitium as separate entities.
DOI: https://doi.org/10.2215/CJN.00640114

Proposed solution:
[ ] Change EA from:
'pericyte cell'
and ('part of' some kidney)
to
'pericyte cell'
and ('part of' some 'kidney interstitium')
Note that there seems to be debate whether this should invoke a 'part of' or 'located in' relationship as suggested in the reference above ("It is debated whether microvessels and capillaries ... are actually part of the renal interstitium or just run through it (1)")
[ ] Add textual definition:
A pericyte cell located in the kidney interstitium.
Since 'pericyte cell' and 'kidney intersitium' have text definitions in their respective terms, the above may be sufficient. @emquardokus, what do you think? Are there any defining features of this cell type you think we should add to the text definition?
[ ] Per https://en.wikipedia.org/wiki/Extraglomerular_mesangial_cell:
"Extraglomerular mesangial cells ... are light-staining pericytes in the kidney found outside the glomerulus..."
https://en.wikipedia.org/wiki/Intraglomerular_mesangial_cell#cite_note-2:
"Mesangial cells are macrophages[1] and resemble pericytes.[2]"
https://en.wikipedia.org/wiki/Glomerulus_(kidney)#Mesangium:
"Intraglomerular mesangial cells. They are not part of the filtration barrier but are specialized pericytes that participate in the regulation of the filtration rate by contracting or expanding..."
In CL, 'glomerular mesangial cell' has exact synonym 'intraglomerular mesangial cell'.
https://doi.org/10.1016/B978-0-12-815876-0.00015-2:
"Mesangial cells function as pericytes for the glomerular endothelium."
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4074211/:
"Mesangial cells are specialized pericyte/smooth muscle cells that surround and constrain the vascular network within the glomerulus of the kidney. They are derived from the stromal mesenchyme, a progenitor population distinct from nephron stem cells. Whether mesangial cells have a distinct origin from vascular smooth muscle cells (VSMCs) and the pathways that govern their specification are unknown."
Given the above, the current modelling may be justified, although the relationship between mesangial cells and pericytes does not seem absolute: ("is a" vs "resembles" vs "function as"). Perhaps we leave as-is for now.
@emquardokus, can you check with the kidney SME if the above seems like a reasonable solution?

Do this first & commit:

'pericyte cell'
and ('part of' some kidney)
to
'pericyte cell'
and ('part of' some 'kidney interstitium')

@bvarner-ebi  citation
STOCKAND, JAMES D., and STEVEN C. SANSOM. 1998. “Glomerular Mesangial Cells: Electrophysiology and Regulation of Contraction.” Physiological Reviews 78 (3): 723–44. https://doi.org/10.1152/physrev.19<IP_ADDRESS>3.


the question about Processing Paths.

Do you consider the situation when http Transfer-encoding is chunked?

I do not handle chunked at this time. This is primarily an extension on Traefik's original Rewrite Body with a few enhancements.


🐛 Bug Report: Unable to unregister a component

📜 Description
Hi, whenever I am trying to "unregister" a component, I get below error:
{
  "error": {
    "name": "error",
    "message": "select * from \"locations\" where \"id\" = $1 - invalid input syntax for type uuid: \"url:https://github.fkinternal.com/dheeraj-kabra/fcc-ansible/blob/backstage/ansible-component.yaml\"",
    "length": 229,
    "severity": "ERROR",
    "code": "22P02",
    "where": "unnamed portal parameter $1 = '...'",
    "file": "uuid.c",
    "line": "136",
    "routine": "string_to_uuid"
  },
  "request": {
    "method": "GET",
    "url": "/locations/url%3Ahttps%3A%2F%2Fgithub.fkinternal.com%2Fdheeraj-kabra%2Ffcc-ansible%2Fblob%2Fbackstage%2Fansible-component.yaml"
  },
  "response": {
    "statusCode": 500
  }
}

I go to 3 dots on right upper most corner for a given component, Click on "Unregister Entity" and I get this error.
I am on Backstage version  "version": "1.21.0"  and This is connected to the PostgrSQL running on Google cloud.
The Component is present in PostgrSQL:
fcc_backstage_catalog=> select * from locations where target = 'https://github.fkinternal.com/dheeraj-kabra/fcc-ansible/blob/backstage/ansible-component.yaml';
                  id                  | type |                                            target
--------------------------------------+------+-----------------------------------------------------------------------------------------------
 b7e483cd-c06d-42c8-a874-20d3e8d2fcd4 | url  | https://github.fkinternal.com/dheeraj-kabra/fcc-ansible/blob/backstage/ansible-component.yaml

However it seems from the UI, when I try to unregister, the value b7e483cd-c06d-42c8-a874-20d3e8d2fcd4 is not replacing the variable $1 and hence the Query is failing with error "select * from \"locations\" where \"id\" = $1 - invalid input syntax for type uuid:
👍 Expected behavior
The component should get unregistered from Backstage UI.
👎 Actual Behavior with Screenshots
As described in "Description"
👟 Reproduction steps
Deploy BAckstage 1.21.0 with PosstgreSQL DB
Register a component
Try to "unregister" given component.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
Backstage is running on K8S on Google GKE.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

I think that this has been fixed in later versions of Backstage. Looks like it was fixed in 1.22. https://github.com/backstage/backstage/issues/21962.
Going to close this issue as it's a duplicate :) But please upgrade and report back if there's anything awry!


Slightly confusing reports with SDC and multiecho

Version: 20.1.0
What I was doing:
I've rerun fMRIPrep 20.1.0 on my longitudinal sample with single echo task based fMRI and multi-echo resting state.
What I expected:
A single section of the report for each task based and resting state scan.
What actually happened:
In reviewing the reports, I was initially confused because there are two entries for each rest scan:

Reports for: session 04, task rest, run 1.
Reports for: session 04, task rest, run 1, echo 1.

It looks like the SDC report is getting split out and listed separately as echo 1, while the rest of the steps are shown under "Reports for: session 04, task rest, run 1." To make it more confusing, the steps under  "Reports for: session 04, task rest, run 1." list SDC:

Summary
Repetition time (TR): 2.5s
Phase-encoding (PE) direction: Anterior-Posterior
Slice timing correction: Applied
Susceptibility distortion correction: PEB/PEPOLAR (phase-encoding based / PE-POLARity)
Registration: FreeSurfer bbregister (boundary-based registration, BBR) - 6 dof
Non-steady-state volumes: 4 (Warning: 3 automatically detected)

I've checked four or five subject now and this has occurred for each of them, so I'm pretty sure this will replicate for any multi-echo scan with SDC, see https://openneuro.org/datasets/ds002156/versions/1.0.0 for one such example.

Thanks. This is likely to be a pretty simple fix, so we can target 20.1.x.

I've noticed this is indeed happening with our smoke test (ds210). Agree with @effigies this should be easy (just a dismiss_entities=("echo",) in the corresponding DerivativesDataSink).


Vim highlighting is not simple to install

Pathogen and Vundle etc expect the vim extensions to be at the root of the repository. I'd propose creating a docker/docker-vim-syntax repository or something for containing vim highlighting utilities.

How about creating a subtree split repo ?

I'm in favor of creating a new repo like docker/docker-vim because I don't want to clone the entire docker repository just to grab the plugin.
Keeping this repository on the main repository do not makes sense IMO because it would lead us to pull all unrelated changes from docker itself if we are just looking for updates on the plugin.
A 50/50 solution would be a subtree split repo like @greg0ire suggested.
That way everything would be kept at the main repository and for who want just to clone the plugin itself would be able using the second repository.
Although I see a dedicated repository a better choice since it would allow people related to vim to improve the plugin without all the noise that docker itself makes on the main repository like pull requests and issues.
Makes sense?


Testnet metrics/analytics

We need to instrument the testnet to measure/detect usage and deal with potential abuse

[ ] current block height/block explorer
[ ] web interface to view arbitrary dynamo mhashes
[ ] total # of indexed artefacts/entities
[x] alerts on S3 fill level, Dynamo throughput, machine health
what else?

We also need to think about code instrumentation to publish metrics we can track.

@vyzo reading through these, let's add a block height and an object count gauge

Ok, I will add a counter for canonical record writes and track the index of the returned entry with a gauge.

#172 adds the relevant metrics

Sweet. Gonna close this, the dynamo thing is optional


Problem with daughter volumes

Hello,
I am importing a CAD model of a shipping container and placing several objects inside of it. In order to track the pathlength through the various objects inside the container, I have implemented a stepping action class. However, it seems that the particles I am sending through the container volume can only see the container and none of the daughter objects inside of it (i.e. touchable->GetVolume()->GetCopyNo() always returns the copy number of the container).
Have you seen any issues like this before or do you know of a way to access the copy number of daughter volumes?
Thanks,
Joe

Hi Joe,
Is the mother volume (the shipping container) a shell? If so, the daughter volumes won't be logical daughters -they are inside the container, but not logically within it. Try and set the mother volume of the daughters to the same mother volume as the container.
Chris.

It seems like that was the problem. Everything works as long as they all have the same mother.
Thanks,
Joe


message view: Use inline date separators.

There may be a simpler way to check czo here, but the
main goal here is to just deploy-test the one-liner to
get some immediate user feedback.

Testing Plan:
GIFs or Screenshots:

OK, test-deploying now.

See https://chat.zulip.org/#narrow/stream/101-design/subject/date.20separators/near/661609.  I also found a weird bug where EDITED appeared somewhere totally weird:

So I think we have support for the concept but a handful of bugs reported by multiple people:

We should still be showing sender headers for messages on a new date.
The thing I posted above with EDITED positioning.
Floating recipient bar should update when you scroll past a date separator.

(Merged the second refactoring commit, now that I have a bit more time)

(See also https://github.com/zulip/zulip/issues/10839)

I rebased, but I haven't addressed any of the feedback yet.

The first three commits here are refactoring commits, and they all probably make sense regardless of how the experiment turns out.
I wasn't able to reproduce the EDITED things, but I think I may have fixed it as part of re-working my changes, plus there was some plausibly related recent activity on master that I picked up in rebases.  Tim, you should definitely test this out, since you reported the bug and may have some particular behavior that triggers it.
The last two commits change the actual UI here, and they can arguably be squashed together.  The first commit puts the date separators inside groups, not between them.  Then the second commit fixes the problem that @jackrzhang reported in #10839, and we now update the FRB as we scroll.
I made a couple decisions here that I think are pretty defensible, but we'll see if it elicits feedback:

I now always show dates in recipient bars.  I think this makes sense in general, but it particularly makes sense in a world where use the slimmer date separators within groups that span multiple days.
I don't put date separators between groups.  I think the recipient bars, with the dates, make them a bit redundant.  For the first group, you can visually scan up to either a date separator inside, or the date will show in the recipient bar (and if it's floating, it will be there, too).  And then for the second group, there will be a date in the recipient bar.

I merged the 3 prep commits and push back to this PR.

I now always show dates in recipient bars. I think this makes sense in general, but it particularly makes sense in a world where use the slimmer date separators within groups that span multiple days.

I think this decision we'll likely want to undo, in that we did the suppression of dates there when they are irrelevant as part of an effort to declutter the UI, and that change was popular at the time.
Changing this just requires bringing back the show_date value and setting it correctly, right?

@rishig can you play around with this and let me know if you can find any bugs and what you think about the UX?  It seems worth doing a round of that before test-deploying on chat.zulip.org.

cool!

I occasionally get browser errors of the form source_recip_bar is not defined while trying to navigate with up/down arrows over the recipient bars (couldn't figure out a repro, but has happened twice while testing).

Getting this when reaching top of narrow (pressing up arrow doesn't fix it, but reload does):

There are probably a number of styling changes we'll want to do, but I think the most noticable one is that the bar feels uncentered; i.e. too much bottom-margin relative to top-margin.
Only if it's not too hard, we could also do the following before testing on czo:

Have only 1 date (the new one)
Move it to the right side, in line with the other dates and timestamps
The date can be a bit bolder, and use sentence-case, similar to the date in the recipient bar

@rishig Thanks for testing this!  It's unfortunate that you were testing off a broken version.  I think some rebasing glitch or last-minute cosmetic cleanup introduced the "source_recip_bar" error, which not only caused actual errors but prevented the floating recipient bar code from working.  (It was basically source_recip_bar -> source_recipient_bar, and a spot was missed).
I re-pushed with a fix.
I agree on these changes:

Showing just the "forward" date seems fine to me (and right-aligning it, bolding it).
Fix the vertical centering.

I'm not really sure what you mean by "sentence casing" for the dates--don't we already do that?
Here's another screenshot:

(Just to be clear, I didn't try to address any of the styling concerns in the latest push--I just rebased and fixed the var-naming glitch I mentioned in the previous comment.)

The date dividers are mostly driven by this code in static/js/timerender.js:
137 // Given an XDate object 'time', return a DOM node that initially
138 // displays the human-formatted date, and is updated automatically as
139 // necessary (e.g. changing "Today" to "Yesterday" to "Jul 1").
140 // If two dates are given, it renders them as:
141 // --- ▲ Yesterday ▲ ------ ▼ Today ▼ ---
142
143 // (What's actually spliced into the message template is the contents
144 // of this DOM node as HTML, so effectively a copy of the node. That's
145 // okay since to update the time later we look up the node by its id.)
146 exports.render_date = function (time, time_above, today) {

And then styling is in static/styles/zulip.scss (although maybe should be moved, but doesn't have to happen as part of this effort):

2646 .date_row .date-line {
2647     display: inline-block;
2648     vertical-align: middle;
2649     width: 33%;
2650     border-top: 1px solid hsl(0, 0%, 88%);
2651     border-bottom: 1px solid hsl(0, 0%, 100%);
2652     margin: 0px 5px 0px 5px;
2653 }
2654
2655 .sub-unsub-message span,
2656 .date_row span {
2657     display: block;
2658     background: inherit;
2659     padding: 4px;
2660     overflow: hidden;
2661     text-transform: uppercase;
2662     font-size: 0.8em;
2663     opacity: 0.5;
2664 }

Played around with this; looks good to me! I think ready for pushing to master or czo, and then we can fix-forward on the styling.

OK, just test-deployed on chat.zulip.org.

Styling-wise, I think we want to remove the margin-bottom: 10px on .date-row on line 2637 of zulip.scss.

I squashed that change in, and added a fixes tag for #10171, and pushed back here.  Test-deploying to czo again.

I'm not really sure what you mean by "sentence casing" for the dates--don't we already do that?

I think this part is about the small caps case used in the date-line thingys.

After playing with this a bit, I like the overall experience, so we should definitely merge something in this direction.  I still really want https://github.com/zulip/zulip/pull/10820#issuecomment-451332564 to be changed back. Interleaved views like this (which is the only thing that decision affects) now have the date part look really spammy:

OK, I finished cleaning this up and merged it.  @showell FYI, I fixed a few things:

Left in place the between-recipient rows date dividers, since for the moment those are net helpful.
Fixed candidate_recipient_bars to handle there being non-recipient-row things between them.  This required debugging the annoying fact that .prev(selector) returns nothing if the selector doesn't apply (not the next child that matches!).
Adjusted the date row selection logic in first_visible to handle two tricky corner cases where we were either displaying no date at all in the floating recipient bar incorrectly or displaying a confusing date (when the floating recipient bar partially obscures a message feed recipient bar).

Huge thanks for building this @showell!  I think it makes zulip's UI look a lot cleaner.


DropDownButton is not customizable

Hello guys,
How can we actively customize the DropDownButton. You find you cant change color of the dropdown icon, or its padding. There is no direct way to adjust space within or out of the DropDownButton widget, the only thing you can change is the text style, which is okay for most use cases, but you find if you want a finer control on the widget you have to murk around within the flutter source code. I find it does not directly adhere to the flutter design of other widgets...
I am thinking we should be able to change icon type as well as space between the dropdown text and the icon relatively easily as it is with the rest of the widgets

PR is out for review #25198
Would you be able to review this, please?

To further add to this request, the Container that holds the DropDownItems list should be able to be customized as well. For instance when we customize the DropDownButton to have rounded corners, we would need the items List Container to have rounded corners as well in order to maintain the same look. So please whoever is elaborating, keep this in mind. To have different looks for DropDownButton in closed and opened states is a bad UI experience.

Why is this closed? It seems like there still is no way to customize the style of the expanded list, for example.

Sorry, the PR description in #29572 caused the issue to close despite only addressing part of the problem. I'll reopen this.

Bumping this - any update on custom padding/border/etc?

It would be great if we could also customize the orientation of the menu items so that we could consistently display the options above or below a DropDownButtonFormField

The enforced height of 48, is indeed very inconvenient.
But this is a common problem in material widgets in Flutter.
They prevent configuration to differ from the material design size constraints.
Its one thing to have certain defaults.
Its not ok to prevent full customisations, it only makes people to copy pasting entire widgets and do the needed changes :(

I've created a custom DropdownButton from current version of Flutter's DropdownButton and made it more customizable. It's easy, simple and you can have steady dropdown menu below the button "As long as it's possible" and many other features described with the package. Also added the same functionality to DropdownButtonFormField2 and added a feature of using the button as a popup menu button. I've tested it very well and it works like a charm!
You can use the package or use the source file on GitHub directly. Also, I've Added custom widget with the package you can customize default DropdownButton2 widget for your entire app and use it with few lines as shown in the examples.
Package: DropdownButton2
Repository (GitHub): DropdownButton2

_kMenuItemPadding in dropdown.dart is private, constant and has a value of EdgeInsets.symmetric(horizontal: 16.0). It should be customizable, i.e. we should be able to have menu items without any horizontal padding, or set our own padding.

To add to this, currently you can change the focusColor, but not the text colour of the focused menu item, so if the focusColor is of a different brightness than the default menu background colour, the text is not readable when focused.

In my use case, I want the space between value and trailer icon to be flexible.
For default, the dropdown button make that space according to the longest value in the list but I want it to be for selected value.
Any workaround this?

In most cases of all hardcoded widget limitations I end up making my own.
Either copy and change, or write something from scratch.
On Sun, 2 Oct 2022 at 18:16, Ahmad Khan @.***> wrote:

In my use case, I want the space between value and trailer icon to be
flexible.
For default, the dropdown button make that space according to the longest
value in the list but I want it to be for selected value.
Any workaround this?
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/25151#issuecomment-1264679466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABCY4JF5UW6IFBR4AMELKTWBGYNTANCNFSM4GJL2CYA
.
You are receiving this because you commented.Message ID:
@.***>

Yeah, I also ended up making custom widget

DropdownMenu is meant to replace DropdownButton, in the API docs there is a migration guide: https://api.flutter.dev/flutter/material/DropdownButton-class.html
If there are some properties that are not supported in the new widget, please file a new issue so we can take a look. Thank you!


Network Layer refactor

Refactor I/O part out of connection handle and simplify state machine logic.

Coverage decreased (-77.0%) to 0.0% when pulling 964b034083f26b7741809784156d1f9bfee1cea1 on tli2:tianyu-refactor into 91d9525ada479573a42feeb7ed3d633e54cc905a on cmu-db:master.

Will put in a new PR to fix Travis failure


Require at least py37

TL;DR
Require at least Python 3.7.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
The new API requires at least Python 3.7 to function.
Tracking Issue
NA
Follow-up issue
NA

@wild-endeavor What do you think?


ReadMe Fix

Your readme is missing one vital piece in the example for using the ytdl package, which is to tell the voiceConnection that you have begun speaking.
e := voiceConnection.Speaking(true)
if e != nil {
   // handle error
}

i guess that was kinda implied, since it's not showing connecting to voice either, but could add it

I suppose that's fair. I turned it all into something to this effect:
func ytPlay(v *discordgo.VoiceConnection, videoInfo *ytdl.VideoInfo) {
	defer v.Disconnect()
	defer v.Close()
	format := videoInfo.Formats.Extremes(ytdl.FormatAudioBitrateKey, true)[0]
	downloadURL, e := videoInfo.GetDownloadURL(format)
	if e != nil {
		rep(e)
		return
	}
	options := dca.StdEncodeOptions
	options.RawOutput = true
	options.Bitrate = 96
	options.Application = "lowdelay"
	encodingSession, e := dca.EncodeFile(downloadURL.String(), options)
	if e != nil {
		rep(e)
		return
	}
	defer encodingSession.Cleanup()
	e = v.Speaking(true)
	if e != nil {
		rep(e)
		return
	}
	d := make(chan error)
	s := dca.NewStream(encodingSession, v, d)
	t := time.NewTicker(time.Second)
	for _ = range t.C {
		e := <-d
		if e != nil && e != io.EOF {
			rep(e)
			break
		}
		f, e := s.Finished()
		if e != nil {
			rep(e)
			break
		}
		if e == io.EOF || f {
			break
		}
	}
}


wip: PhantomBounded

Codecov Report

Merging #193 (5b1b45e) into main (2b1dd81) will decrease coverage by 1.58%.
The diff coverage is 72.50%.

@@             Coverage Diff             @@
##              main     #193      +/-   ##
===========================================
- Coverage   100.00%   98.41%   -1.59%
===========================================
  Files           24       24
  Lines          787      820      +33
  Branches       162       98      -64
===========================================
+ Hits           787      807      +20
- Misses           0        9       +9
- Partials         0        4       +4

Impacted Files
Coverage Δ

src/phantom/sized.py
81.94% <72.50%> (-18.06%)
:arrow_down:

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


use shorter cache timeout

Summary of changes
Changes introduced in this pull request:

as @lemmih suggested, if the cache action doesn't complete within 2-3 minutes then it's most likely stalled and we would timeout anyway.
continue the job even if the cache failed for whatever reason. If it happens, we will just rebuild.

Reference issue to close (if applicable)

Closes
Other information and links

Hurrah for @LeshyBot!


Gh-2614: Enable alternative authentication to Accumulo using Kerberos

Related Issue

Resolve #2614

Codecov Report

Merging #2737 (8a5d372) into v2-alpha (8a43ebd) will decrease coverage by 0.04%.
The diff coverage is 86.45%.

@@              Coverage Diff               @@
##             v2-alpha    #2737      +/-   ##
==============================================
- Coverage       65.73%   65.69%   -0.05%
+ Complexity       2435     2276     -159
==============================================
  Files             862      614     -248
  Lines           27251    19281    -7970
  Branches         3126     2270     -856
==============================================
- Hits            17914    12667    -5247
+ Misses           7980     5555    -2425
+ Partials         1357     1059     -298

Impacted Files
Coverage Δ

...k/gov/gchq/gaffer/operation/impl/output/ToCsv.java
100.00% <ø> (ø)

.../gaffer/data/generator/OpenCypherCsvGenerator.java
73.17% <73.17%> (ø)

...eration/handler/output/ToOpenCypherCsvHandler.java
93.54% <93.54%> (ø)

...k/gov/gchq/gaffer/data/generator/CsvGenerator.java
16.09% <100.00%> (+16.09%)
:arrow_up:

.../gaffer/operation/impl/output/ToOpenCypherCsv.java
100.00% <100.00%> (ø)

...ov/gchq/gaffer/store/library/FileGraphLibrary.java
59.67% <100.00%> (+0.66%)
:arrow_up:

.../gchq/gaffer/accumulostore/AccumuloProperties.java

...k/gov/gchq/gaffer/accumulostore/AccumuloStore.java

...ov/gchq/gaffer/accumulostore/utils/TableUtils.java

...andler/javardd/ImportJavaRDDOfElementsHandler.java

... and 249 more

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


[DROOLS-7578] Evaluate Impact analysis for ansible integration rules

Quick prototype. Works for a basic example : ParserTest

Requires https://github.com/apache/incubator-kie-drools/pull/5594 to compile and run. drools and drools-ansible-rulebook-integration have different upstream repos ,so cross-repository build wouldn't work, hence this CI should fail until https://github.com/apache/incubator-kie-drools/pull/5594 is merged.

ParserTest generates a SVG file:

Run CI after the 8.45.0-SNAPSHOT update is deployed.

@mariofusco Please review, thanks!

Note that this visualization depends on https://github.com/apache/incubator-kie-drools/pull/5594 , so this doesn't run with drools 8.43.0.Final which drools-ansible-rulebook-integration 1.0.xbranch currently depends on.

This seems to be expected checkout.
2023-12-11T07:53:20.4391431Z ##[group]Checkout summary
2023-12-11T07:53:20.4392442Z [INFO] [apache/incubator-kie-drools]
2023-12-11T07:53:20.4393919Z [INFO]      Project taken from apache/incubator-kie-drools:main (Branch HEAD 0abd1fcbb2c126d4a6b5ad67764bce9c894c4b10)
2023-12-11T07:53:20.4395379Z [INFO] [kiegroup/drools-ansible-rulebook-integration]
2023-12-11T07:53:20.4397264Z [INFO]      Project taken from kiegroup/drools-ansible-rulebook-integration:main (Branch HEAD 5ceabec812f72d10368a2e669b0d608da9d52bf8)
2023-12-11T07:53:20.4399070Z [INFO]      Merged tkobayas/drools-ansible-rulebook-integration:DROOLS-7578-ansible-visualization into branch main
2023-12-11T07:53:20.4400088Z ##[endgroup]


RFC: internal middleware for "wrapping" workers

We're coming across multiple usecases where it's useful to "wrap" a worker with some functionality before running dev/publish.

--assets/config.assets uses a facade to add the boilerplate for serving static assets from kv
d1 uses a facade to inject D1 bindings that abstract over the underlying Durable Object (until the runtime native supports it, at which point we will remove the facade)
We can capture errors in dev to give a more user friendly experience for errors (tracking at https://github.com/cloudflare/wrangler2/issues/441)
We can use it to expose special routes that trigger scheduled workers
We could wrap a worker and inspect requests in dev to add live reload functionality (tracking in https://github.com/cloudflare/wrangler2/issues/1167)
We can use it in dev to inject bindings to override service bindings and implement zero config multiworker development (tracking https://github.com/cloudflare/wrangler2/issues/1182)
We use this in the wrangler@wasm builds to wrap .wasm files with a worker facade that makes it amendable to the Workers runtime
We could use it to detect missing favico responses in dev mode

There are probably a bunch more usecases, but this list should be sufficient to convince of it's usefulness.
The proposal here is to formalise this internally in the codebase so we can add/remove these facades/"middleware" based on conditions, so that we can add more than one for a worker if and when required.

One thing to keep in mind is this will (probably?) affect source maps.

Landed this in https://github.com/cloudflare/wrangler2/pull/1551, works well, sourcemaps included. Closing this.


feature: More Windows friendly instructions using cmd and powershell for those that cant use WSL

Feature Description
Most of the commands I've seen when trying to install Kube core or Kubeflex reflect more Mac-focused commands, so I find myself a lot of the time trying to translate so it works with Powershell. if we could add clearer installation instructions so that someone not experienced with Kube or Kubernetes can understand it better and follow the step-by-step in a way that makes more sense/easier to understand.
Proposed Solution
Adding sections that are more focused on Powershell/cmd instructions with sections like so
<Windows installation instructions with powershell/cmd>
installation etc...
Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

@rayoazul777 can you open a documentation PR to suggest how you would install KubeStellar on Windows using windows-native instructions?


Add DefaultShareLinkToExistingAcces advanced setting for sensitivity label

Docs Build status updates of commit 23a9880:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-Label.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-Label.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Homepage features section converted to liquid templates

Description
This PR fixes #1370
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

changes in Gemfile.lock aren't to be included in the commit @RavindraP04

Ok, I have remove that file from the commit

@RavindraP04
Let's discuss it on the websites call.
Please add this as an agenda item in the meeting minutes, if you would :)
https://docs.google.com/document/d/1XczAHXVe2FIWPqiF57ospJ43zw5cZQ7ui8mn39v5EvA/edit#heading=h.lohhtewfwima


Changes to constants

Not ready to be merget yet ... WIP

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 19.64%. Comparing base (c6db4f4) to head (edd44c9).
Report is 4 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   19.85%   19.64%   -0.22%
==========================================
  Files           7        7
  Lines        1264     1278      +14
==========================================
  Hits          251      251
- Misses       1013     1027      +14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


New operators

added push operator
added polymorphic reduce
added polymorphic filter
added polymorphic map
mapObject/filterObject/reduceObject now invoke callback with value, index (breaking change)

Coverage increased (+12.3%) to 86.179% when pulling 7d988e8cae57f1173eac2ad43fc76fd503413614 on new-operators into cfc0841c1417f406f41b349e76dcecf98d590bfe on master.


[stdlib] Various documentation fixes

This PR includes a variety of revisions to the standard library documentation:

Fix incorrect type in Float(_:String) examples
Expand discussions for ExpressibleBy____Literal protocols
Add notes about non-escaping unsafe pointers from closures
Add note about isEmpty to Collection.count discussions
Describe imported Bool types
Clean up some floating point discussions
Provide some additional operator documentation
Revise documentation for CVarArg functions
Fix incorrect Set method parameter descriptions
Clarify array bridging behavior
Add collection subscript complexity notes

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@airspeedswift OK to merge?

@swift-ci Please smoke test

LGTM with these changes.
@swift-ci please smoke test and merge

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

Thank you

@swift-ci Please smoke test and merge


Row._data as OrderedDict to allow element access by label

If headers are defined in a Dataset it would be helpful to allow element access within a row of the Dataset by column label in addition to index based access. Issue #22 suggested using namedtuples for this but --while acknowledging the general usefulness of such a feature-- was discarded because namedtuples would not support append, etc.
Implementing this via OrderedDicts should be possible though. It would require (it seems only in tablib/core.py on a first pass):

Row constructor to accept an additional headers argument
_set_headers to be augmented to update existing rows with new column labels
Changes to Row methods insert,  __getitem__, __setitem__, and updates/changes to a few other special methods in Dataset and Row

It would introduce some overhead but given that Tablib is aimed at use cases "below" the Pandas level that might be acceptable and should not break the API.
I'm happy to give this a shot but --given that it will require changes in quite a few places in core.py-- would appreciate some feedback if (a) people still think that this would indeed be useful and (b) anyone sees a reason why doing this as outlined above is not a good idea (or may not even work at all...).
Many thanks!

Actually, OrderedDict is probably overkill... can simply keep reference to the Dataset that created/owns Row instance in that instance to have access to headers from within the Row instance...


split header design

There's a common use case of wanting to use the pocketpy.h header as a header (without implementation) and also as a header (with implementation): basically to compile the  implementation part into a dynamic or static library and then use it with only the header part.
Currently the header is really just the implementation:
#ifndef POCKETPY_H
#define POCKETPY_H

// ... header + implementation

#endif // POCKETPY_H

whereas I suggest to change it to a classic split structure:
#ifndef POCKETPY_H
#define POCKETPY_H

// ... only header part

#endif // POCKETPY_H

#ifdef POCKETPY_IMPLEMENTATION

// ... only implementation part

#endif // POCKETPY_IMPLEMENTATION

In the latter case, I can use pocketpy.h in header-only mode as follows:
#include "pocketpy.h"

and as header + implementation mode as follows:
#include "pocketpy.h"
#define POCKETPY_IMPLEMENTATION

@blueloveTH
Ok fair enough. Thanks for your for explanation.


SyntaxError: Unexpected token: name (ChargingStationClient)

Hi,
I just built a project in order to reproduce this error.
Once unpacked, simply do:

npm install
grunt build:prod

Cheers,
Serge.

project_to_reproduce.zip

Hi again!. I will look into this.

This grunt task doesn't run JavaScript obfuscator.
It runs only uglification task.
grunt.registerTask("build:prod", ["clean", "uglify"]);

Thanks!
Then in other words, I have to open an issue to UglifyJS :-(

Even with creating an obfuscator task and replacing uglify I get the same error:
    obfuscator: {
        files: ["src/**/*.js"],
	    options: {
		    compact: true,
		    controlFlowFlattening: false,
		    controlFlowFlatteningThreshold: 0.75,
		    deadCodeInjection: false,
		    deadCodeInjectionThreshold: 0.4,
		    debugProtection: false,
		    debugProtectionInterval: false,
		    disableConsoleOutput: true,
		    mangle: false,
		    reservedNames: [],
		    rotateStringArray: true,
		    seed: 0,
		    selfDefending: false,
		    sourceMap: false,
		    sourceMapBaseUrl: '',
		    sourceMapFileName: '',
		    sourceMapMode: 'separate',
		    stringArray: true,
		    stringArrayEncoding: false,
		    stringArrayThreshold: 0.75,
		    unicodeEscapeSequence: false		    }
		},

I updated the grunt file and ran the obfuscator's task:
GruntFile.zip
It worked and produced an 'output.js' in the dist directory but when I want to start it with node it outputs the following error:
SyntaxError: Identifier 'ChargingStationClient' has already been declared
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:390:7)
    at startup (bootstrap_node.js:150:9)

What did I do wrong again :-( ?
Thanks in advance for your help!

Hi. Looks like problem in grunt-contrib-obfuscator. This plugin just obfuscate all files and then concatenate it into single file.
This is wrong behaviour, because it doesn't wrap modules in wrapper functions like Webpack, so after concatenation class and variable declaration with same name are conflicted because they in the same scope.
Please create this issue here:
https://github.com/javascript-obfuscator/grunt-contrib-obfuscator

Thanks for your support !
Do you know a grunt/gulp plugin that would do the trick with your javascript-obfuscator and encrypt my nodejs project correctly ?
I'm running out of patience :-(

You can use webpack (standalone or as gulp plugin) with https://github.com/javascript-obfuscator/webpack-obfuscator
webpack will bundle all your JS code into single file, and then webpack-obfuscator will properly obfuscate this bundle.

Ok, I'll try

The grunt-contrib-obfuscator mimics the behaviour of the grunt uglify task (i.e: receives a bunch of file names and outputs one file with the result). Maybe you can use a babel grunt plugin that will bundle the files into one and then use the obfuscator plugin on that file, but I don't recommend doing that. The best and modern way to do is to use webpack as @sanex3339 recommended.


RSA PSS signature generation with the option to specify the salt length (proposed solution for issue #3152)

Description
As discussed in issue #3152, the RSA PSS signature generation function does not allow to pass in the salt length. Some CAVP tests vector however require a salt length which is smaller or bigger than the hash length. This pull request introduces mbedtls_rsa_rsassa_pss_sign_ext() which like its _verify_ext() counterpart allows to provide the salt length as argument to the function.
Status

[x] add mbedtls_rsa_rsassa_pss_sign_ext()
[x] reuse mbedtls_rsa_rsassa_pss_sign_ext() in mbedtls_rsa_rsassa_pss_sign()
[x] compile without warnings (on Ubuntu 18.04)
[x] all existing test from the original test suite pass
[x] new _ext() function published and documented in rsa.h
[x] Builds cleanly on MSVC
[x] Fix CI failure - tests/scripts/all.sh test_check_params_functionality
[x] Rework the _ext() function to avoid duplicating some checks
[x] squash typo/whitespace commits
[x] add some invalid param test in test_suite_rsa
[x] add some backward compatibility test in test_suite_pkcs1_v21
[x] add new positive test vectors for cases where the salt length is specified explicitly
[x] add new negative test vectors.
[x] Changelog updated (add a file in ChangeLog.d)

Hi @meuter. This PR fails to build in VisualC:
47>C:\builds\ws\-3183-head-KSDOYLLV32MDDLSWRWSJG\worktrees\tmps_cgiqot\library\rsa.c(1931): error C2220: warning treated as error - no 'object' file generated [C:\builds\ws\-3183-head-KSDOYLLV32MDDLSWRWSJG\worktrees\tmps_cgiqot\cmake_solution\library\mbedcrypto.vcxproj]

47>C:\builds\ws\-3183-head-KSDOYLLV32MDDLSWRWSJG\worktrees\tmps_cgiqot\library\rsa.c(1931): warning C4267: 'function' : conversion from 'size_t' to 'unsigned int', possible loss of data [C:\builds\ws\-3183-head-KSDOYLLV32MDDLSWRWSJG\worktrees\tmps_cgiqot\cmake_solution\library\mbedcrypto.vcxproj]

Also, the last 2 commits should be squashed with the earlier ones.

The CI links are private, I'm afraid we can't make them public. Please ping someone from Arm to look them up. Currently:

tests/scripts/all.sh test_check_params_functionality is failing.
There's the failure with MSVC that Dan mentioned earlier.
Mbed OS testing is failing, but that's a preexisting issue and will not block PRs as long as we haven't resolved this preexisting issue.

Thanks for your review @gilles-peskine-arm. I'll integrate your feedback then move on to writing extra tests for the new function.

@gilles-peskine-arm I just finished adding the remaining tests as well as the missing entry in ChangeLog.d. As far as I can tell, this looks complete. Let me know what you think. Thanks!

Hi @meuter . It seems some of your added tests are not working. For example:
tests/scripts/depends-hashes.pl
...
******************************************
* Testing hash option: unset MBEDTLS_SHA512_C
******************************************
...
test_suite_pkcs1_v21 .............................................. FAIL
...
FAILED (86 suites, 8360 tests run)
Makefile:132: recipe for target 'check' failed
make[1]: *** [check] Error 1
Makefile:94: recipe for target 'check' failed
make: *** [check] Error 2
Failed test suite: unset MBEDTLS_SHA512_C

Also ChangeLog needs a trailing LF:
******************************************************************

* check_changelog: Check: changelog entries

* Tue Jun  9 03:41:29 UTC 2020

******************************************************************

Traceback (most recent call last):

  File "scripts/assemble_changelog.py", line 505, in <module>

    main()

  File "scripts/assemble_changelog.py", line 502, in main

    merge_entries(options)

  File "scripts/assemble_changelog.py", line 449, in merge_entries

    finish_output(changelog, options.output, options.input, files_to_merge)

  File "scripts/assemble_changelog.py", line 415, in finish_output

    check_output(output_temp, input_file, merged_files)

  File "scripts/assemble_changelog.py", line 399, in check_output

    raise LostContent(merged_file, line)

__main__.LostContent: Lost content from ChangeLog.d/mbedtls_rsa_rsassa_pss_sign_ext.txt: "b"     in the NIST's CAVP test suite (contributed by C\xc3\xa9dric Meuter).""

^^^^check_changelog: Check: changelog entries: scripts/assemble_changelog.py -o ChangeLog.new -> 1^^^^

Also  Windows cmaks build, cmake-clang-freebsd and gmake-clang-freebsd tests failing, e.g. for cmake-clang-freebsd:
 Start 63: pkcs1_v21-suite

63/85 Test #63: pkcs1_v21-suite ........................***Failed    6.59 sec
...
The following tests FAILED:

	 63 - pkcs1_v21-suite (Failed)

Errors while running CTest

*** Error code 8

@meuter As someone recently opened an issue with the same problem, I'm checking the status of this PR. It seems to me that the CI failures need to be addressed, then we can review again and check that all previous feedback has been addressed. Also, unfortunately in the meantime conflicts have appeared, so could you rebase your branch on recent development in order to resolve them?
For reference, here's the full list of failures in the CI (already mentioned by Dan, I'm just trying to add  more detail in case it helps):

tests/scripts/all.sh test_depends_hashes fails. Specifically, test_suite_pkcs1_v21 fails in a config with MBEDTLS_SHA512_C unset, so I assume some of the new test case are missing a depends_on:MBEDTLS_SHA512_C. You should be able to reproduce by building and running this test suite in a config without SHA-512, then fix by adding the missing dependency declaration to failing tests cases. Then you can run tests/scripts/all.sh test_depends_hashes to make sure there was no other similar issue.
tests/scripts/all.sh test_rsa_no_crt fails. Specifically, test_suite_pkcs1_v21 fails in a config with MBEDTLS_RSA_NO_CRT set - the only test case failure appears to be the last one:RSASSA-PSS Signature, RSA-1024, SHA-256, slen = (olen-hlen-2)-1 ... FAILED
hexcmp( output, result_hex_str->x, ctx.len, result_hex_str->len ) == 0

I'm not sure what's going on here, but this is something you should be able to reproduce locally.
test_suite_pkcs1_v21 appears to be failing in all of the 4 tests run by the CI on FreeBSD - all.sh component test_clang_opt,  test_default_out_of_box(doesn't tell which case(s) failed),test_cmake_out_of_source,  test_cmake_shared` (both failing the last case as in the point above). This might be harder to reproduce if it's platform-dependent, but with any luck all of them might turn out to be have the same root cause as the point above.
test_suite_pkcs1_v21 is also failing on Windows, and when details on each case are available, is turns out it's also the same case (slen = (olen-hlen-2)-1) failing, so the same comment as for FreeBSD applies.

I hope this is enough information to help you fix the failing test(s). Please let us know what you think.

@mpg Hi, first of all sorry for the lack of feedback on this one. I got sidetracked on another project. Anyhow, I just rebased my changes on top of the dev branch. I cherry picked the commits one by one making sure that the tests were passing at each commits. At the last commit, I did indeed find one test in test_suite_pkcs1_v21 that was failing. After a bit of debugging, I found out that in the last two tests in that suite (added in the last of my commits):
RSASSA-PSS Signature, RSA-1024, SHA-256, slen = olen-hlen-2 ....... PASS
RSASSA-PSS Signature, RSA-1024, SHA-256, slen = (olen-hlen-2)-1 ... PASS

the calls mbedtls_test_rnd_buffer_rand() (previously rnd_buffer_rand) was running out of hardcoded random data and falling back to the mbedtls_test_rnd_std_rand. My bad! So I simply added more random data in the test suite inputs. This should fix problems 2 and hopefully 3 and 4. For problem 1, I checked the depends_on declaration in the test suite inputs, and AFACT, everything look OK. We'll see the output of the CI, but I'm hoping that it's another symptom of the problem I just fixed.
Thanks again for the assist!

@meuter Thanks for resolving the conflict and fixing the problematic test!
The CI looks much happier now, we're nearly there, with only two failures:

tests/scripts/all.sh test_depends_hashes is still failing, but now it's when MBEDTLS_SHA512_NO_SHA384 is set (that is, SHA-512 is available, but SHA-384 is not). This time it might actually be a missing dependency declaration on !MBEDTLS_SHA512_NO_SHA384.
tests/scripts/all.sh test_depends_hashes_psa is failing in the same way, most probably for the same reason.

Hopefully this will be easy to reproduce locally and fix.

@mpg Just finished fixing the test suite data to avoid running the SHA384 tests when not appropriate. Hopefully this PR should be good to go now 🤞

Alright looking good! 😄
Let me know if you require other changes.
Oh, and Happy Holidays!

Great! I think the next steps are Gilles is going to re-review this when coming back in January, and a second team member needs to review as well - I'll do that next week.
Thanks and happy holidays to you too!

Hi @meuter. If your latest patches address the previous review's comments, you should remove the "needs: work" label and the "needs: review" one, so someone knows to look at this.

Hi @meuter. If your latest patches address the previous review's comments, you should remove the "needs: work" label and the "needs: review" one, so someone knows to look at this.

@danh-arm Only us with write permissions can manage labels.
@meuter Sorry for not replying sooner. I'm pretty busy with other things, and Manuel is currently on vacation, so it might take a while for us to re-review.

@danh-arm Only us with write permissions can manage labels.
@meuter Sorry for not replying sooner. I'm pretty busy with other things, and Manuel is currently on vacation, so it might take a while for us to re-review.

@gilles-peskine-arm no worries I understand ;-)

@gilles-peskine-arm no worries I understand ;-)


can't build project since 5pm EST

I'm getting the folllowing errors:
Error:(9) No resource identifier found for attribute 'panelHeight' in package 'com.sothree.slidinguppanel'
Error:(9) No resource identifier found for attribute 'initialState' in package 'com.sothree.slidinguppanel'
Error:(9) No resource identifier found for attribute 'paralaxOffset' in package 'com.sothree.slidinguppanel'
Error:(9) No resource identifier found for attribute 'shadowHeight' in package 'com.sothree.slidinguppanel'

Use the old version 2.0.4 in your gradle.build file or see the changelog and upgrade to v3.0.0

I upgraded to 3.0.0 and still couldn't compile... went back to 2.0.4 and the error was gone. So how do we use it in 3.0.0? what are those attributes changed to?

Please see the change log or the sample. An umano prefix has been added.

On your layout.xml files you must add the umano prefix to sothree attributes.
What before was:
<com.sothree.slidinguppanel.SlidingUpPanelLayout
    xmlns:sothree="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:gravity="bottom"
    sothree:panelHeight="68dp"
    sothree:shadowHeight="4dp">

from version 3.0 is
<com.sothree.slidinguppanel.SlidingUpPanelLayout
    xmlns:sothree="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:gravity="bottom"
    sothree:umanoPanelHeight="68dp"
    sothree:umanoShadowHeight="4dp">


Fix for #51 Wrong result of JsDiff.diffLines

Need to be checked as I don't know what is the expected behavior for TrimmedLineDiff.

Can you add a test case to cover this failure?

Done

Thanks!

Released in 1.3.1

Seems like there remains the bug when empty line after a change:
https://github.com/kpdecker/jsdiff/issues/235


[core] - Eagerly set canvas size on start

It appears that resize observer callback will do their first execution lazily - like in a microtask or on the next frame (did not have time to investigate). This PR takes care of a regression noticed in this discord thread by eagerly setting the store value before calling observe().

Ph, good catch! Immediate merge 👍


fix AMD/commonjs return object format incompability

Hello.
It's just standarize object that is returned from library, independently if AMD or CommonJS module load system is used. I using your library in my cycle-js driver (https://github.com/10clouds/cyclejs-cookie) and it need to work in harmony with any module loader.
http://ifandelse.com/its-not-hard-making-your-library-support-amd-and-commonjs/

Thanks!


415607E1 - Call of Duty 3

Marketplace

Tested on https://github.com/xenia-canary/xenia-canary/commit/293e9582ec35d30ef17a25f08858a82eed945f69
Issues:
Menu, intro etc. - great works. The game has problems with rendering textures(Corrupt Drawing)(Drawing ground, trees, etc.), namely "horizontal lines." The sound works well. The game itself can "freeze" anywhere in the 1-st mission(Help only restart emulator), sometimes happens error "Graphic device lost". 1-st mission playing until we are getting up at truck, then emulator "freezes" (Other missions works, but after few second emulator "freezes").
Log:
xenia.zip
Screenshot(s):

Labels:
state-gameplay, gpu-corrupt-drawing, gpu-missing-drawing, tech-middleware-demonware

Tested on https://github.com/xenia-canary/xenia-canary/commit/97fdf9c6dd9a6bad00182714b9205ef32e40d4f4/
Issues
As reported by FragsAreUs at xenia master game comaptibility, multiplayer maps now load, and light sources such as those on Fuel Plant are rendered through map geometry. Could not confirm crashing after 5-10 minutes.
Main menu music cuts itself short and loops back to the start
Log
Singleplayer Main Menu: xenia.zip
Multiplayer Main Menu: xenia.zip
Screenshots

Videos
https://user-images.githubusercontent.com/14031281/207445870-978b2dac-0e66-4161-a1a3-3f41b4247fac.mp4
https://user-images.githubusercontent.com/14031281/207445664-79738099-8a60-436f-a3f0-3692affb5943.mp4
Extended black video at the start while audio is playing is a lapse on the recording software's part

Patches: https://github.com/xenia-canary/game-patches/pull/329


Server Side Crash on Most Recent Update

Mod Loader
Forge 47.2.1
Mod version
Goety <IP_ADDRESS>
Issue description
Tried to update my modpack and worked fine on the client side, but when starting up on my server, was met with a crash.
Link or Post Log Files
https://mcpaste.io/7924dffef9e0e24b
Steps to reproduce

Launch Goety <IP_ADDRESS> for Forge 47.2.1 on a Dedicated Server
Check Logs ?

Additional information
No response

Will look into this!

Should be fixed as of Goety <IP_ADDRESS>


Revert #169 back but it should not really fix anything

seeing if tests would still consistently fail

as expected that was a red herring
current fails
FAILED test/test_install.py::test_install_miniconda_datalad - assert 1 == 0
FAILED test/test_install.py::test_install_venv_miniconda_datalad - assert 1 == 0
FAILED test/test_install.py::test_install_neurodebian_sudo_ok - subprocess.Ca...
FAILED test/test_install.py::test_install_git_annex_remote_rclone_latest_from_github_globally
======== 4 failed, 95 passed, 4 skipped, 1 xpassed in 519.83s (0:08:39) ========


Not sure if static builds are using static libs

We use a .props file in our vcpkg-enabled builds:
  <PropertyGroup>
	<WindowsTargetPlatformVersion>10.0.18362.0</WindowsTargetPlatformVersion>
	<PlatformToolset>v142</PlatformToolset>
    <VcpkgEnabled>true</VcpkgEnabled>
	<VcpkgUseStatic>true</VcpkgUseStatic>

We were building without VcpkgUseStatic but I added this and re-ran our build. I can see seemingly as many DLLs are being copied as previously in the AppLocalFromInstalled step in the msbuild logs. And I see this:

VcpkgTripletSelection:
Using triplet "x64-windows-vs2019" from "C:\vcpkg\scripts\buildsystems\msbuild......\installed\x64-windows-vs2019"

I am not sure if it should explicitly mention static building or not, I not it should append -static to the triplet name but not whether it should display this. The raw path above does not include the static suffix.
I am aware some ports only support dynamic linking but it seems like it's doing it for everything.
Is there some way to tell for certain if it is using the static version or not? Could I bodge something into one of the scripts maybe?

Afaik this only works if you not use a custom triplet name. If you use a custom triplet name you have to add -static yourself

Can anyone confirm @autoantwort is correct? I can't really see how vcpkg even knows it's a custom triplet and I figured it was a simple shortcut if(VcPckUseStatic)triplet = triplet+"-static" but it's an easy workaround. I could try building with my explicit static triplet by name tomorrow, but it takes a while to build :)

https://github.com/microsoft/vcpkg/blob/b7f99c3c4b32c0b31b73701e92bb42fbea0c83cb/scripts/buildsystems/msbuild/vcpkg.targets#L15-L16

https://github.com/microsoft/vcpkg/blob/b7f99c3c4b32c0b31b73701e92bb42fbea0c83cb/scripts/buildsystems/msbuild/vcpkg.targets#L15-L16

Oh, hang on my msbuild script is very minimal but is that saying in L16 to only use the result of L15 if the triplet is empty, e.g. default? I missed that!

is that saying in L16 to only use the result of L15 if the triplet is empty, e.g. default?

Yeah. So instead of doing <VcpkgUseStatic>true</VcpkgUseStatic> in your property sheet do <VcpkgTriplet>$(VcpkgPlatformTarget)-$(VcpkgOSTarget)-vs2019-static</VcpkgTriplet> or something like that.

Many thanks. Yeah we just need to explicitly set our triplet name.
I'll close as it seems to be pretty clear. I do wonder if this functionality is ideal (or if the documentation in VS could be improved). I quite like the idea of specifying triplet but still being able to toggle -static personally.


RealityKit: Model3D

Doc: https://developer.apple.com/documentation/RealityKit/Model3D

Blocked by Support visionOS/xrOS


Print TradingError with cause

With 2.0.5 we don't show the cause of an TradingError anymore.
An error on the coordinator side
ERROR coordinator::trade: Failed to execute trade. Error: Failed to open DLC channel: Could not propose DLC channel: Wallet error No bnb solution found after 0 rounds (max rounds is 100000).
will become only this on the app

will be received as this on the app
Failed to open DLC channel

which is a bit vague to classify errors.

I've labelled this as bug as it used to work.


stored procedure fails on long titles

Reported by atze on 19 Mar 2014 13:03 UTC
the procedure create_missing_encoding_tickets fails if there are tickets with too long titles.
proposed solutions:
a) replace lines 15 and 42 with:
CONCAT(substring(t1.title from 0 for 92),' (',ep.name,')') AS title,

b) change tbl_ticket.title to type text (removing length constraint)

Comment by atze on 19 Mar 2014 14:05 UTC
PS. in this file:
https://repository.fem.tu-ilmenau.de/trac/c3tt/browser/Application/Migrations/10_function_create_missing_encoding_tickets.sql

Modified by atze on 19 Mar 2014 14:06 UTC

Comment by texec on 12 Jul 2014 09:10 UTC
I think we should remove titles for child tickets altogether, in this case this would be obsolete.

Comment by atze on 20 Oct 2014 11:10 UTC
fixed in changeset:11b8b19

Comment by texec on 20 Oct 2014 13:28 UTC
Not what I hoped for, but [7443e611] should clean this up.


BUG: Catalog CreateBranch uses store.GetTag to verify branch exists

What happens if a tag and a branch have the same name?
I believe we do that do avoid inconsistent reference.

I see - so we might want to document it so there will be no future confusion

@itaiad200 why did we close it?


Disable parallel build on CI to avoid build failures

It seems CI builds irregularly fail due to parallel build. I've been re-running every failed CI tests whenever they failed. Not sure if this is related to #212.

Usually when this happens it is because an intermediate target is missing in a CMakeLists.txt somewhere.  Can you link some of the failing builds here so we can note what the specific errors were?

Here is an example case of the build failure.

bump :smile:

I can't seem to pull up the logfiles for this.. is it possible TravisCI garbage collected them? :sweat:

I can't seem to pull up the logfiles for this.. is it possible TravisCI garbage collected them?

I cannot pull up the log as well. I think is not available temporarily. This is an equivalent error from Azure Pipelines.

Noting this as possibly related from this log:
2020-04-04T16:23:02.1929291Z CMake Error at /usr/share/cmake-3.13/Modules/CTestTargets.cmake:28 (configure_file):
2020-04-04T16:23:02.1930280Z   configure_file Problem configuring file
2020-04-04T16:23:02.1930763Z Call Stack (most recent call first):
2020-04-04T16:23:02.1931525Z   /usr/share/cmake-3.13/Modules/CTest.cmake:264 (include)
2020-04-04T16:23:02.1932100Z   test/examples/CMakeLists.txt:1 (include)

I have to admit that I wasn't able to pinpoint what the root cause, but this resolves the build error.

Would it be possible to enable verbose flags and monitor for the output?  I think there might be a build error that is being logged but not printed in here.
I am also ok with just merging this if it unblocks other development.  I just don't know how to replicate locally to figure out the issue outside of the CI system.

I am also ok with just merging this if it unblocks other development. I just don't know how to replicate locally to figure out the issue outside of the CI system.

Yeah, I would like to just merge this and create an issue to track this instead. I think there are other issues to be resolved that might be higher priority.


Autogenerate a device template from a component raw data

I have tried to auto generate a device template from the raw data sent by device component. The following screen snippet shows  my test:

Note, that the feature is working well for raw data sent by default device component. Is this a limitation or a bug?
Thanks in advance.
Roman

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: df6faaa0-3f8f-0863-0d76-5dc5e4784b10
Version Independent ID: 46fae9f1-3c4d-8863-16eb-7f640d766836
Content: Define a new IoT device type in Azure IoT Central
Content Source: articles/iot-central/core/howto-set-up-template.md
Service: iot-central
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@romankiss Thanks for the feedback! We are currently investigating and will update you shortly.

@dominicbetts Could you please check this issue and provide your insights?

Hi @romankiss - it looks like IoT Central is only autogenerating from capabilities in the root component. Let me check with the product team to confirm if this is a bug. Thanks!

Hi @dominicbetts - thanks for your checking and I hope this is a bug. The autogenerating is a great feature and it should be worked for raw data sent by multi-components.
Thanks
Roman

Hi @romankiss - I've confirmed that this preview feature currently only works with root level capabilities. I'll update the docs to make this clear. The product team are aware of the ask for component support, but I don't have a timescale for this yet. The docs will be updated as soon as component support is available. Thanks for your interest!
#please-close

Hi @dominicbetts - thank you so much for your info.
Roman


Add DatabaseCleaner::strategy method

This PR adds a DatabaseCleaner::strategy getter method as discussed in issue #511.
Since there may be multiple connections, and different strategies for each connection, this getter method returns a hash of strategies.
The guard clause may be unnecessary, since the ::connections method already attempts to autodetect an ORM and populate the @connections array with it, but I figured better safe than sorry.

@rlue Things have finally improved here, with regards to the dependency issues you were having. If you try to implement this again on current master, you should have a much easier time.

Thanks guys! It's been a while since I've looked at this code; any thoughts on this proposal?

@rlue Hello! Thank you for taking the time to rebase this and add some tests!
My personal thoughts are that its a bit awkward for this one getter method to return so many different types of values, but I think that's a natural consequence of the configuration API itself being so awkward. So my first inclination is to merge it.
However, there's another consideration: once the dust settles on the v2.0 release, I'd like to pursue a new, non-awkward configuration API (more details in #546), and I imagine that this work might result in us wanting to make breaking changes to this new #strategy method, and we would not be able to without releasing v3.0.
So I'm a bit torn. @etagwerker do you have any thoughts?

@rlue okay, cool! I want to make improving the configuration API the next order of business after the v2.0 release is out the door, so if you're cool with postponing this API addition so that it can be a part of that endeavor, I think that could work out pretty well. Let's aim for v2.1!

@rlue Now that v2.0 is out, could you please look into this PR? I think it is a good idea but there are now some conflicts with the main branch.

Hi folks! Sorry for the delay; hope there is still interest in this PR!

My personal thoughts are that its a bit awkward for this one getter method to return so many different types of values, but I think that's a natural consequence of the configuration API itself being so awkward. So my first inclination is to merge it.

I have not had the chance to really reflect on this concern, but I think it's valid. If we want to follow the robustness principle (that is, to be strict about/consistent in the output that we provide), then rather than supplying potentially three different kinds of output (nil, symbol, or hash), we could always return a hash; i.e., simply
def strategy
  strategies = transform_values(&:strategy)
end

I chose the approach I did based on the assumption that this method would be used primarily for debugging, and thus valued eronomics over consistency. Happy to make amendments as you see fit.


Support parsing of Record expressions and patterns

Checklist:

[ ] Record patterns
[ ] Record expressions

[ ] New record
[ ] Record update

This is currently possible thanks to the tree-sitter-erlang grammar.

This is currently possible thanks to the tree-sitter-erlang grammar.