corpus/ is packaged into the Python package?

I am not sure if this is intended or not, but the Python package contains text files and executable scripts into the corpus/ subdirectory. It has www in the name so I am really not sure if it should be embedded in the Python package. I could tweak the debian package to remove them but better if they are not included in the first place.
Here are the new Lintian warnings when trying to package a recent version of kalamine:
It not
I: kalamine: extra-license-file [usr/lib/python3/dist-packages/kalamine/www/corpus/LICENSE]
N:
N:   All license information should be collected in the debian/copyright file.
N:   This usually makes it unnecessary for the package to install this
N:   information in other places as well.
N:
N:   Please refer to Copyright information (Section 12.5) in the Debian Policy
N:   Manual for details.
N:
N:   Visibility: info
N:   Show-Always: no
N:   Check: files/licenses
N:
N:
I: kalamine: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/kalamine/www/corpus/LICENSE]
N:
N:   This package ships a documentation file outside /usr/share/doc
N:   Documentation files are normally installed inside /usr/share/doc.
N:
N:   If this file doesn't describe the contents or purpose of the directory it
N:   is in, please consider moving this file to /usr/share/doc/ or maybe even
N:   removing it. If this file does describe the contents or purpose of the
N:   directory it is in, please add a lintian override.
N:
N:   Visibility: info
N:   Show-Always: no
N:   Check: documentation
N:
N:   Screen: python/egg/metadata
N:     Advocates: "Scott Kitterman"<EMAIL_ADDRESS>N:     Reason: The folders XXX.dist-info/ and XXX.egg-info/ hold metadata for
N:             Python modules. Those files are not documentation even though
N:             some of their names carry the .txt file extension.
N:
N:             Python modules can be both public and private.
N:
N:             Read more in
N:             https://www.python.org/dev/peps/pep-0427/#the-dist-info-directory,
N:             https://www.python.org/dev/peps/pep-0376/#id16,
N:             https://www.python.org/dev/peps/pep-0610/,
N:             https://www.python.org/dev/peps/pep-0639/,
N:             https://setuptools.pypa.io/en/latest/deprecated/python_eggs.html,
N:             and Bug#1003913.
N:
N:
I: kalamine: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/kalamine/www/corpus/README.md]
N:
I: kalamine: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/kalamine/www/corpus/en+fr.txt]
N:
I: kalamine: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/kalamine/www/corpus/en.txt]
N:
I: kalamine: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/kalamine/www/corpus/fr.txt]
N:
P: kalamine: debian-changelog-line-too-short test [usr/share/doc/kalamine/changelog.Debian.gz:3]
N:
N:   The given line of the latest changelog entry appears to contain a very
N:   terse entry.
N:
N:   This can make it hard for others to understand the changelog entry. Please
N:   keep in mind that:
N:
N:    - It is not uncommon that people read changelog entries that are more
N:      than a decade old to understand why a change was made or why a
N:      package works in a specific way.
N:    - Many users will read the changelog via
N:      apt-listchanges(1)
N:    - The information in debian/changelog is permanent.
N:
N:   Examples for entries that are too short include "dh 11" or simply "R³" -
N:   these could be expanded to, for example:
N:
N:    - Switch to debhelper compat 11.
N:    - Set Rules-Requires-Root: no.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/changelog
N:
N:
X: kalamine: executable-in-usr-lib [usr/lib/python3/dist-packages/kalamine/www/corpus/chardict.py]
N:
N:   The package ships an executable file in /usr/lib.
N:
N:   Please move the file to /usr/libexec.
N:
N:   With policy revision 4.1.5, Debian adopted the Filesystem Hierarchy
N:   Specification (FHS) version 3.0.
N:
N:   The FHS 3.0 describes /usr/libexec. Please use that location for
N:   executables.
N:
N:   Please refer to File System Structure (Section 9.1.1) in the Debian Policy
N:   Manual, filesystem-hierarchy,
N:   https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html, and
N:   Bug#954149 for details.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/permissions/usr-lib
N:   This tag is experimental.
N:
N:   Screen: emacs/elpa/scripts
N:     Advocates: "David Bremner"<EMAIL_ADDRESS>N:     Reason: The emacsen-common package places installation and removal
N:             scripts, which for ELPA packages are executable, in the folder
N:             /usr/lib/emacsen-common/packages.
N:
N:             About four hundred installation packages are affected. All of
N:             them declare emacsen-common as an installation prerequisite.
N:
N:             Read more in Bug#974175 and Bug#954149.
N:
N:   Screen: web/cgi/scripts
N:     Advocates: "Andrius Merkys"<EMAIL_ADDRESS>N:     Reason: The folder /usr/lib/cgi-bin/ is designated for scripts in the
N:             Common Gateway Interface (CGI). They require the executable bit
N:             so the server can run them.
N:
N:             Read more in
N:             https://en.wikipedia.org/wiki/Common_Gateway_Interface,
N:             https://datatracker.ietf.org/doc/html/rfc3875.html, and
N:             Bug#1003941.
N:
N:
X: kalamine: executable-in-usr-lib [usr/lib/python3/dist-packages/kalamine/www/corpus/merge.py]

E: Lintian run failed (runtime error)

These text files are the base material that our analyzer depends on. They are only required to compute the JSON files in the corpus.
One workaround that I’d prefer to avoid would be to create a separate repository for our analyzer, move the corpora there, and only import the JSON and minimized JS in this repository.
Another workaround would be to fetch these corpora on demand, e.g. with a kalamine corpus command.


Category listing

At the moment, the metadata of the modules includes the category keyword, which is used to define in which category the module will appear. But if the category does not exist, it will silently fail (for example if your category is Getting started instead of Getting Started).
As a user, it would be nice if "unknown categories" were added automatically to the list of existing categories (maybe thrown at the end).

I would like to review the whole categorization and filtering of modules.
An interesting example I find very useful is the github projects filtering, grouping and sorting:
In the example below, I filtered issues on being in the "previous iteration" (an iteration is a period of time you define that you work on a project, like a sprint or a coworking day), I grouped them by repository (where the issue belongs to) and sorted them according to their "priority" (which is just a numerical label between 1 and 4).

I think this flexibility of filtering, grouping and sorting is too complicated for us, but it is nice as an example.
In our case the filtering could be based on a label, which defines an interesting subset, like "masterclass", "life science", "technology" etc. Sorting could be according to a preset "order" much like we currently do for the chapters, and grouping might still be according to the current categories, or using some other grouping. Perhaps having a set of useful "collections" which have preset filters, groupings and sortings is what we actually need.
These could perhaps be defined in the config.json file e.g.:
"collections": {
  "masterclass": {
    "filter": "masterclass",
    "sort": "order",
    "group": "category"
  }
}

These collections could then be listed in a clear spot on the main page.
Or is this already too complicated and do we just need the proper labels to be able to filter and get rid of all the complexity?

I am not sure if the collection filtering would solve the initial problem: I add a new module, but mistype the category name. As a user I only see the new module is not showing at all, and have no idea where the problem is.
I am not against if it is a feature that would be useful in other circumstances. I would just ask what happens if I mistype the category name? Where does my module ends up? If it doesn't show up at all (because it doesn't match the filter), I think the user would still find it frustrating.

yes @c-martinez sorry, I understand the original issue that you mentioned and I agree it should definitely be solved. I just wanted to mention that we might want to rethink and replace the whole category grouping system or at least extend it with the ability to let the user filter, group and sort modules themselves. But I actually think that it belongs in a different issue.


Issue with homebrew Microvision games

RG503 Hardware.
Microvision.  Version of MVEM currently doesn't work with two homebrew games:

Tetris: garbled display - unplayable
Space Invaders - clearing the first screen of aliens hangs when the last one is hit

Unless there's a new version of MVEM that addresses those issues, not something I can fix.


[Networking] Monitorization of a network ;Internet Protocol version (IPV4 & IPV6)

Topic Suggestion
Monitorization of a network (IPV4 & IPV6)
Proposed article introduction
IPV4 _(Internet Protocol version 4)_is a protocol used in a packet-switched link-layer network while IPV6 (Internet Protocol version 6) is more advanced and has more advantages compared to IPV4.
The wide growth of networks over the world has helped fix the IP address exhaustion problem.
IPV6 is faster, more efficient, and more advanced than IPV4.
### Key takeaways

Internet Protocol version overview.
what is IPV4?
What is IPV6?
Monitoring IPV4.
Monitoring IPV6.
6.IPV6 route.

Article quality
The article will elaborate internet protocol version and how to monitor the internet protocol version.
references
N/A

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large. Please feel free to suggest an alternate topic to explore. 🚀
https://www.google.com/search?q=Monitorization+of+a+network+%3BInternet+Protocol+version+(IPV4+%26+IPV6)&rlz=1C1CHBF_enUS891US891&sourceid=chrome&ie=UTF-8


Infinite redirects under pow

If I set up pow to always_restart I get a redirect loop

I think its because env["warden"] get stomped on every time the server restarts

Yeah, that'll happen.  Are you setting a session cookie secret in your sinatra app?  That should keep the session going between requests.
https://github.com/sinatra/sinatra/blob/master/lib/sinatra/base.rb#L1491

no im not, I'm not sure what I need to set.
I followed the example pretty close.
Since the server restarts every request it looks like it just keeps trying to authenticate.
https://github.com/atmos/sinatra_auth_github/blob/master/lib/sinatra/auth/github.rb#L175

enable :sessions
set :session_key, "my secret key"

worked perfect thanks!


All Coqs should be built with -debug

See bug 4090 for discussion.

Ok, thanks, I just added the -debug flag for all versions starting from 8.5.


Create SPIFFE compatible certs

Description:
Adds support for generating SPIFFE Compatible Certs.  It does not use the spiffe Identity encoded in the cert which will be addressed in #5023.
fixes: #5022, #5027, #5024
TODO:

[x] Add e2e test
[ ] add validation (after #5105 merges)

Requires both #5116 and #5105

Testing done:

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

Is this a breaking change?

Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)?

This is ready for review but could be slightly smaller after https://github.com/openservicemesh/osm/pull/5135 merges and will have small update after https://github.com/openservicemesh/osm/pull/5105 (which could be done in follow up)

e2e tests are passing with certs being provisioned with SPIFFE URI SAN
• [SLOW TEST:190.262 seconds]
[Tier 2][Bucket 10][] SPIFFE
/home/runner/work/osm/osm/tests/framework/common.go:90
  with Tressor
  /home/runner/work/osm/osm/tests/e2e/e2e_spiffe_test.go:23
    has a Pod Certificate with a SPIFFE ID
    /home/runner/work/osm/osm/tests/e2e/e2e_spiffe_test.go:32

• [SLOW TEST:232.645 seconds]
[Tier 2][Bucket 1][] 1 Client pod -> 1 Server pod test using cert-manager
/home/runner/work/osm/osm/tests/framework/common.go:90
  with SPIFFE Enabled
  /home/runner/work/osm/osm/tests/e2e/e2e_certmanager_test.go:24
    Tests HTTP traffic for client pod -> server pod

• [SLOW TEST:98.213 seconds]
[Tier 2][Bucket 4][] 1 Client pod -> 1 Server pod test using Vault
/home/runner/work/osm/osm/tests/framework/common.go:90
  with SPIFFE Enabled
  /home/runner/work/osm/osm/tests/e2e/e2e_hashivault_test.go:24
    Tests HTTP traffic for client pod -> server pod

I've rebased ontop of https://github.com/openservicemesh/osm/pull/5135 and https://github.com/openservicemesh/osm/pull/5105


Fix segfault with optional groups

Optional subgroups caused wrong NULL pointer arithmetic. This PR fixes this and adds regression tests.

I'll fix the build error ASAP. As it turns out there are other segfault corner cases to fix.

All known issues should be fixed by now.


Replace extension pattern with updated version

We have two extension patterns utilized currently. These extension points are required so that we can add additional functionality or altered querysets on readthedocs.com.
The modern version is in readthedocs.core.utils.extend, and an example of this extension is readthedocs.core.symlink.PublicSymlink. There are a number of classes using arbitrary settings to allow for override in readthedocs.privacy.backend. Unifying these two implementations would clean things up and consolidate our settings.
Ref #2611

Can you please elaborate the issue

readthedocs.privacy.backend already uses SettingsOverrideObject with VersionManager/VersionQuerySet - what else do you see as requiring changes?

The old pattern is used in these spots:

https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/privacy/loader.py
https://github.com/rtfd/readthedocs.org/blob/c84cd7362a5c43eb95c2316fef9b6df4c592b3b4/readthedocs/oauth/services/__init__.py
https://github.com/rtfd/readthedocs.org/blob/c84cd7362a5c43eb95c2316fef9b6df4c592b3b4/readthedocs/projects/backends/views.py


The stop words is not working

When I call the infligth batch, I want to add additional stop words, it seems it did not work. Is this a bug or the feature is not ready yet?

@liyu-tan Inflight batching should already support stop_words.
Can you share your concrete steps of reproducing your issue?
June

I also fund the problem in codeLlama in cpp runtime when I use the inflight batch with tritonserver
https://github.com/NVIDIA/TensorRT-LLM/issues/90

Hi @yoyopdc ,
We need a proper way to reproduce the issue using the main branch. Can you share that with us, please? Without a proper reproducer, we cannot investigate the issue.
Thanks,
Julien

Yes I'm willing to reproduce the issue, but the issue is happened in tensorrt-backend + tensorrt-LLM, I had download the main branch but I met some problem about compiling the tensorrt-backend with tensorrt-LLM:main, After I fix it I will reproduce it.

This issue is related: https://github.com/triton-inference-server/tensorrtllm_backend/issues/57

Inflight batching should already support stop_words.

The STOP_WORD_IDS are computed from stop_words inpreprocessor, but are neither fetched from there nor passed to tensorrt_llm. I don't know though if they are not passed by mistake or the backend itself doesn't support them as input yet.
To my knowledge, the only workaround currently is to send end_id explicitly, but this way you can only specify one end token.
I am not sure which repo is more relevant for the issue, but I think this will be useful for cross-reference.

This issue is related: triton-inference-server/tensorrtllm_backend#57

Inflight batching should already support stop_words.

The STOP_WORD_IDS are computed from stop_words inpreprocessor, but are neither fetched from there nor passed to tensorrt_llm. I don't know though if they are not passed by mistake or the backend itself doesn't support them as input yet.
To my knowledge, the only workaround currently is to send end_id explicitly, but this way you can only specify one stop token.
PS: Given that inputs of tensorrt_llm don't include anything similar to stop tokens, they are most probably not supported by the backend.
Yes ，I also use end_id now!

Do you still encounter issue on latest main branch?

Here is a new document to demonstrate how to use stop word in triton.
Close this bug because the issue is inactivated. Feel free to ask here if you still have question/issue, we will reopen the issue.

Hello,
Where is the document? We are testing vanilla Llama 2 70B. with version 0.6.1. It ignores stop words like "." and "\n".

We think it might be related to this https://github.com/triton-inference-server/tensorrtllm_backend/issues/47

Hello, Where is the document? We are testing vanilla Llama 2 70B. with version 0.6.1. It ignores stop words like "." and "\n".

I'm not sure if this is a bug, but this is how I solved it.
you can change the model.py file and set the legacy to true. by default it is false.
https://github.com/triton-inference-server/tensorrtllm_backend/blob/3a61c37afcdc3d5d04796a89555605e713494031/all_models/gpt/preprocessing/1/model.py#L47
self.tokenizer = LlamaTokenizer.from_pretrained(tokenizer_dir, legacy=True, padding_side='left')

Hi, I also encountered the same problem， I use  tensorrt-llm release/0.5.0 and tensorrtllm-backend release/0.5.0 for building, and use 23.10-trtllm-python-py3 docker for serving. When my deployment is complete for chatglm3-6b，and request service  as below:
(glm) aiadmin@zl-gpu03:~/LLM/tensorrtllm_backend-release-0.5.0$ python tools/inflight_batcher_llm/end_to_end_streaming_client.py -u "<IP_ADDRESS>:8001" -p "员工已成功提交了一个“请假”申请单,请用温馨的话语对用户进行回复" -S -o 100
FLAGS: Namespace(verbose=False, url='<IP_ADDRESS>:8001', prompt='员工已成功提交了一个“请假”申请单,请用温馨的话语对用户进行回复', streaming=True, protocol='grpc', output_len=100)
:

尊敬的用户,您已成功提交了请假申请,非常感谢您的配合!我们期待您的假期能够愉快、轻松,让您充分休息,放松身心。请您放心,我们会尽快处理您的请假申请,确保您的权益得到保障。再次感谢您的支持与理解!

您好！我是您的人工智能助手。请问有什么我可以帮您解答的问题吗？
您好！我是您的人工智能助手。请问有什么我可以帮您

It can not stop，until the response reach max_tokens, I want know how to set the stop words or other parameters. Could you please give me a detailed explanation? I've been troubled for a long time

Please take a try on latest main branch. It is fixed in latest branch. You also need to make sure you setup the stop_words correctly, you can print the stop word ids in preprocessor and compare them with output ids.

Still get the errors in TensorRT LLM 0.10.0 @byshiue


Refactor storage uploading endpoint

/upload -> /uploads here in order to align the REST resources to plural.

After this change, we could bump the asset storage library to 1.0, unless there are any objections?

Fixed in commit https://github.com/robocorp/robo/commit/84bb8c802d3ac9314f33c5be14f3a7b369ed6359


Contracted section path

We want to be able to use contracted path to define subsection easily.
[root]
[.branch]
label = value

In the previous example, the section declaration [.branch] is equivalent to [root.branch].

Done in commit 83d1097642591f1d86157bfa1483042111f40877


css are dynamically generated, not hard coded

https://github.com/iammrhelo/InstagramCrawler/blob/2203de193b217bf67753da19795d2eda9ce43229/instagramcrawler.py#L33

I guess this means the fix in #13 will potentially break at some point


Automatically update version of contracts based on package.json version from changesets

Current dependencies on/for this PR:

main

PR #174

PR #192   👈

This comment was auto-generated by Graphite.


[BUG]For a week-long Event, time is not displayed for it.

Describe the bug
For a week-long Event, time is not displayed for it.
To Reproduce
Steps to reproduce the behavior:
Create an Event with time from 11:30 Am to 1:30 PM for a week
Publish the event
Actual result
Time is not displayed in the event
Expected behavior
Time should display for Events in the app

This is a Single event that starts on a day and end after a week. I still reproduce this issue in new version.

I query this user event from test server, 5fb2b3a54caae30009a7a399
{
"allDay": false,
"category": "Academic",
"contacts": [],
"cost": "$5",
"createdBy"<EMAIL_ADDRESS>"endDate": "2020-11-20T16:00:00Z",
"imageURL": "https://api-test.rokwire.illinois.edu/events/5fb2b36b1b5714609026a175/images/5fb2b3a51b5714609026a17e",
"isSuperEvent": false,
"isVirtual": true,
"location": {
"description": "Zoom - Online"
},
"longDescription": "Testing Week-long event",
"name": "",
"sponsor": "UIUC",
"startDate": "2020-11-17T15:00:00Z",
"subEvents": [],
"subcategory": "",
"tags": [],
"targetAudience": [],
"title": "Week long event",
"titleURL": "https://illinois.edu/"
}

Hi @Priyaravi8, This looks to me as a bug/design decision in the Illinois app. Time is not showing up for many events.


CASMINST-4960

Description

Fixes bad cmdline argument, the argument was not added to the cmdline but the list of modules instead. This adds the debug argument to the cmdline.
The following error is observed without this change:
dracut: Executing: /usr/bin/dracut -L 4 --force --hostonly --omit "btrfs cifs dmraid dmsquash-live-ntfs fcoe fcoe-uefi iscsi modsign multipath nbd nfs ntfs-3g plymouth resume metalmdsquash metaldmk8s metalluksetcd usrmount" --omit-drivers "ecb mlx5_core mlx5_ib sunrpc xhci_hcd" --add "mdraid kdump rd.debug=1" --fstab --nohardlink --mount "LABEL=SQFSRAID /kdump/live xfs ro" --mount "/kdump/live/LiveOS/filesystem.squashfs /kdump/rootfsbase squashfs ro" --mount "LABEL=ROOTRAID /kdump/overlay xfs" --filesystems xfs --compress "xz -0 --check=crc32" --no-hostonly-default-device --kernel-cmdline "kernel initrd=initrd ifname=mgmt0:14:02:ec:da:50:98 ifname=sun0:14:02:ec:da:50:99 ifname=mgmt1:b4:7a:f1:17:01:3c ifname=sun1:b4:7a:f1:17:01:3d biosdevname=1 pcie_ports=native transparent_hugepage=never console=tty0 console=ttyS0,115200 iommu=pt ds=nocloud-net\;s=http://<IP_ADDRESS>:8888/ rootfallback=LABEL=BOOTRAID root=live:LABEL=SQFSRAID rd.live.ram=0 rd.writable.fsimg=0 rd.skipfsck rd.live.squashimg=filesystem.squashfs rd.live.overlay=LABEL=ROOTRAID rd.live.overlay.thin=1 rd.live.overlay.overlayfs=1 rd.luks rd.luks.crypttab=0 rd.lvm.conf=0 rd.lvm=1 rd.auto=1 rd.md=1 rd.dm=0 rd.neednet=0 rd.md.waitclean=1 rd.multipath=0 rd.md.conf=1 rd.bootif=0 hostname=ncn-m002 rd.net.timeout.carrier=120 rd.net.timeout.ifup=120 rd.net.timeout.iflink=120 rd.net.timeout.ipv6auto=0 rd.net.timeout.ipv6dad=0 append nosplash quiet crashkernel=360M log_buf_len=1 rd.retry=10 rd.shell rd.peerdns=0 rd.net.dhcp.retry=5 xname=x3000c0s2b0n0 nid=100008 rd.info" --persistent-policy by-label --mdadmconf --printsize --force-drivers raid1 /boot/initrd-5.3.18-150300.59.43-default-kdump
dracut: dracut module 'modsign' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'plymouth' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'btrfs' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'dmraid' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'dmsquash-live-ntfs' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'metalmdsquash' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'multipath' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'metaldmk8s' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'metalluksetcd' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'cifs' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'fcoe' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'fcoe-uefi' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'iscsi' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'nbd' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'nfs' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!
dracut: dracut module 'resume' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'usrmount' will not be installed, because it's in the list to be omitted!
dracut: dracut module 'rd.debug=1' cannot be found or installed.

Checklist Before Merging

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I don't have a JIRA.

Success
ncn-m001:/usr/share/doc/csm/scripts/workarounds/kdump # ./run.sh
Uploading hotfix files to ncn-m001:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-m002:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-m003:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-s001:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-s002:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-s003:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-w001:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-w002:/srv/cray/scripts/common/ ... Done
Uploading hotfix files to ncn-w003:/srv/cray/scripts/common/ ... Done
Running updated create-kdump-artifacts.sh script on [9] NCNs ... Done
The following NCNs contain the kdump patch:
	ncn-m001
	ncn-m002
	ncn-m003
	ncn-s001
	ncn-s002
	ncn-s003
	ncn-w001
	ncn-w002
	ncn-w003
This workaround has completed.


Migrate "beam_PostCommit_Python_MongoDBIO_IT" Jenkins job to GitHub Actions

The following jenkins job has been migrated:

https://ci-beam.apache.org/job/beam_PostCommit_Python_MongoDBIO_IT/

How has it been tested?
The jobs have been tested on Self-hosted GKE runners ubuntu 20.04.
The following test cases are passed:

by manually running the job (workflow_dispatch)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Looks like there are conflicts preventing merging unfortunately, will merge once those are resolved


cherry-pick Improve local shuffle strategy

Proposed changes
pick https://github.com/apache/doris/pull/34122 https://github.com/apache/doris/pull/35454 https://github.com/apache/doris/pull/35716 https://github.com/apache/doris/pull/37195
#40036

run buildall


Question: Find documents by objectId

I am trying to find documents by id. I couldn't find an example in the samples using an id except, in http://api.mongodb.org/lua/current/examples/delete_one.lua.html
-- After the insert, there should be two.
local arrayOfDocuments = {{foo = "bar", _id = "manually set _id"}, {foo = "baz"}}

I have no problem searching for a specific field like below:
:find_one({ somefield = "text" })

However, finding a document by and objectID appears to return nil.
:find_one({ _id = "560b17a2adccb8347b447717" })

How should a query for an objectId be formatted?

I have sorted this out.
I was using the key string.  However, the id needs to be 'ObjectId("560b17a2adccb8347b447717")'.  I am pulling this ObjectId as a reference in another collection.  So I just store the whole _id object instead of the string representation it self.

I'm glad you got it sorted out!
On Thursday, October 1, 2015, Dereck Martin<EMAIL_ADDRESS>wrote:

I have sorted this out.
I was using the key string. However, the id needs to be
'ObjectId("560b17a2adccb8347b447717")'. I am pulling this ObjectId as a
reference in another collection. So I just store the whole _id object
instead of the string representation it self.
—
Reply to this email directly or view it on GitHub
https://github.com/mongodb-labs/mongorover/issues/24#issuecomment-144615722
.


Separator must come from the settings

At this moment, the separator between meta-data and content is hard-coded.  It should come from the settings.
Solution:

Add separator to the settings
Implement the split in python

Implemented via the environment.yml file


Issue with Azure Functions v4 FormData Handling for Large field JSON Data

Issue with Azure Functions v4 FormData Handling for Large field JSON Data
I hope this message finds you well. I am writing to report an issue encountered after upgrading from Azure Functions version 3.1.0 to version 4.x, specifically related to handling FormData in TypeScript.
In my previous implementation using Azure Functions version 3.1.0, I utilized the npm package @anzp/azure-function-multipart to process FormData, with a specific focus on handling a large JSON payload along with other file types. I set a substantial field size limit using the 'fieldSize' property, ensuring proper processing of large JSON data.
let ObjParse: ParsedMultipartFormData = await parseMultipartFormData(request, { limits: { fieldSize: 999999999 } });

However, upon upgrading to Azure Functions version 4.x, I discovered that this npm package is no longer compatible, as it specifically supports version 3.1.x. In the new version, when utilizing
let ObjParse = await request.formData()

the JSON data is received incomplete, containing only 1048570 characters, even though the actual size of the JSON is 1536897 characters.
This issue severely impacts the functionality of my Azure Function, as it is crucial to process complete JSON data within the FormData.
I kindly request your assistance in addressing this matter. If there are alternative approaches or recommended updates to handle FormData with large JSON payloads in Azure Functions v4.x, I would greatly appreciate your guidance.
Thank you for your attention to this issue, and I look forward to a prompt resolution.

Hi @Dev-InSoft I'm not familiar with @anzp/azure-function-multipart, but yes request.formData() is the recommended way to parse form data. Could you perhaps give more detailed repro steps with sample data? Any idea what characters are missing? For example is it from the end of the data or is it maybe a difference in whitespace?
The biggest problem we have with form data right now is we don't support streaming http requests. I don't know if this is your problem, but if you are sending the request with "transfer-encoding" set to "chunked", that could explain it. We hope to support streams soon (tracked by https://github.com/Azure/azure-functions-nodejs-library/issues/97).

In the following example, it sent a JSON that has a size of 1,197,284 bytes, but when the information arrives at the server, it indicates that the size of the “jsondatafield” field is only 1,048,576 bytes, evidencing that it trims it.
import { app, HttpRequest, HttpResponseInit, InvocationContext } from "@azure/functions";
import type { FormData, FormDataEntryValue } from "undici"

export async function Test(request: HttpRequest, context: InvocationContext): Promise<HttpResponseInit> {
	try {
		//let text = await request.text();
		let formData: FormData = await request.formData();
		let data: FormDataEntryValue | null = formData.get("jsondatafield");
		if (data && typeof data == "string")
			return { jsonBody: JSON.parse(data) }
		return { status: 400, body: "bad requet" }
	} catch (error) {
		return { status: 500, body: error?.message }
	}
};

app.post('Test', {
	handler: Test
});

If I read the Body information with await request.text() I notice that the JSON is complete, and that it is truncated by await request.formData()

In the same example, if I sent a JSON with a size less than 1,048,576, as in the following case, I am sending one of 1040640 bytes, the reading is normal and there are no problems in the execution of the function

Below I attach an example in postman and a mini project in which the case can be reproduced
Azure Function V4.postman.json
Example.zip

So it turns out this default limit of "1048576" is set by the busboy npm package. Your original package "@anzp/azure-function-multipart" and "undici" are both using "busboy" as a dependency, but it seems like only the former supports passing the config on to busboy. My current recommendation would be to use "busboy" directly if you need to configure the limits. The other alternative is to file an issue on undici so that we can configure the limits, but the fetch spec for formData doesn't allow any parameters so I'm skeptical we'd get traction.
Here's some rough code that worked for me. It's just a combination of your code and the busboy sample in their readme:
import { app, HttpRequest, HttpResponseInit, InvocationContext } from "@azure/functions";
import * as busboy from 'busboy';

export async function Test(request: HttpRequest, context: InvocationContext): Promise<HttpResponseInit> {
    try {
        console.log('POST request');

        const formData = {};
        const bb = busboy({ headers: Object.fromEntries(request.headers), limits: { fieldSize: 999999999 } });
        bb.on('field', (name, val, info) => {
            formData[name] = val;
        });
        bb.on('close', () => {
            console.log('Done parsing form!');
        });

        const body = await request.text();
        bb.write(body);
        bb.end();

        let data = formData["jsondatafield"];
        if (data && typeof data == "string") {
            console.log(`Data length: ${data.length}`);
            return { jsonBody: JSON.parse(data) }
        }
        return { status: 400, body: "bad request" }
    } catch (error) {
        return { status: 500, body: error?.message }
    }
};

app.post('Test', {
    handler: Test
});


Sider bar toggled

Please how to hidden the menu list for first time open the website..

just add toggled to ul tag like below,
<!-- Sidebar -->         <ul class="navbar-nav bg-gradient-primary sidebar sidebar-dark accordion toggled" id="accordionSidebar">

thanks this "toggled" is working

So simple... I've been scratching my head for weeks to figure it out on my own!! Thanks @fbiceo !

this comment need to be pined


Clarify errors when plugins fail to load

🦟 Bug fix
Summary
I find that it's hard to tell one plugin failure mode from another with the current error messages.  This expands the messages and also includes relevant information for helping to diagnose system plugin issues.
Now in the case that it fails to find a library, gz-sim will output the list of paths that were searched for the library.
When a bad (or misspelled!) plugin name is provided, it will output a list of the known plugins and aliases in that shared library.
Example Improved output:
[ RUN      ] SystemLoader.BadLibraryPath
[Err] [SystemLoader.cc:102] Failed to load system plugin: (Reason: Could not find shared library)
- Requested plugin name: [gz::sim::systems::Physics]
- Requested library name: [foo.so]
- Library search paths:
  - /home/mjcarroll/workspaces/gz_garden/build/gz-sim7/lib/
  - /home/mjcarroll/.gz/sim/plugins/
  - /home/mjcarroll/.ignition/gazebo/plugins/
  - /home/mjcarroll/workspaces/gz_garden/install/lib/gz-sim-7/plugins/
[       OK ] SystemLoader.BadLibraryPath (79 ms)
[ RUN      ] SystemLoader.BadPluginName
[Err] [SystemLoader.cc:164] Failed to load system plugin: (Reason: library does not contain requested plugin)
- Requested plugin name: [gz::sim::systems::Foo]
- Requested library name: [libgz-sim7-physics-system.so]
- Resolved library path: [/home/mjcarroll/workspaces/gz_garden/build/gz-sim7/lib/libgz-sim7-physics-system.so]
- Detected Plugins:
  - gz::sim::v7::systems::Physics
    aliases:
      gz::sim::systems::Physics
      ignition::gazebo::systems::Physics
[       OK ] SystemLoader.BadPluginName (43 ms)

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I don't think I can't say much of the unit tests, the rest looks good to me (besides a minor comment).

I updated the tests to actually check the output for the general failure modes.


Luno: The specified amount contains fractional units

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[X] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Advice long from strategy
Expected result (what you hoped would happen)
Sell from BTC to EUR (pair XBT:EUR)
Actual result (unexpected outcome)
Sell by strategy receive this error:
"The specified amount contains fractional units"
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
I've inserted market pair in luno.js
{ pair: ['EUR', 'XBT'], minimalOrder: { amount: 0.0005, unit: 'asset' }, precision: 6 }

It's been a while since i looked at this... If you know the correct fraction, set it at percision. If not, keep reducing until you stop getting the error.

I've set precision to 4, it'a all ok.


Turn off lazy logging credo checks

Resolves #487

Pull Request Test Coverage Report for Build 2686

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

Totals

Change from base Build 2684:
0.0%

Covered Lines:
1035

Relevant Lines:
1128

💛  - Coveralls


PP-5010 Add fee entity

Adds FeeEntity, and mapping to ChargeEntity.
At present the only way we want to expose the fee is as part of the
charge, so this commit adds a getFeeAmount method to the charge.
Passes through fee from ChargeEntity to ChargesFrontendResource and
ChargeApiResource.

It might be a good idea to test the search resources/ API endpoints that fetch multiple charges at once, just to make sure the entity is correctly propagated and there is no custom logic that will have to be updated.
I would like to do this in a separate PR


Added 100 days of swift course

What does this PR do?
Add Resource(s)
For resources
Description
Added a free course named "100 days of swift"
Why is this valuable (or not)
A great intro to swift for beginners
How do we know it's really free?
No login needed, all articles are open to the public
For book lists, is it a book?
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

looks good!


DX: Test that Transformers are adding only CustomTokens that they define and nothing else

The transformer classes are internal, so we can do whatever we want there without BC promise and upcoming BC breaks warnings.
Let's use the getCustomTokens method to ensure that Transformer is adding only allowed custom tokens, and no other transformer is adding them.
Unfortunately, to implement this check i had to bypass few things (eg access internals), but I couldn't find a good way to do it without refactoring main Tokenizer class into first-class service.

Coverage remained the same at 91.929% when pulling a0853968709c3ec699e5f1ea83784fb5f0f6dd26 on keradus:2.18_CUSTOM_TOKENS into e2c6a1a1d8bafcfaf0dc21b6e983a4db7e170ea8 on FriendsOfPHP:2.18.


[BACKLOG-40922] Unit test fixes for JDK17

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot


[Kernel][Model] Improve continuous batching for Jamba and Mamba

Mamba kernels now avoid writing/reading to/from padded cache entries
Jamba now uses the previously implemented functionality for continuous batching in #8012 #8039 #8533

CC @tlrmchlsmth

One suggestion: To mirror the PAD_SLOT_ID that's in backends/utils.py, we could #define PAD_SLOT_ID -1 in csrc/attention_generic.cuh, so that we name the constant.
And then we can add comments letting the reader know to keep them in sync

I've taken another approach, passing the pad_slot_id through the kernel params, keeps it simpler since we don't need to keep the cpp and python variables in sync and keeps the mamba kernels as standalone. WDYT?

Pushed adaptations for #6484 , The PR is ready again.

Changing the title since Jamba and Mamba already support continuous batching -- this just makes it better

One suggestion: To mirror the PAD_SLOT_ID that's in backends/utils.py, we could #define PAD_SLOT_ID -1 in csrc/attention_generic.cuh, so that we name the constant.
And then we can add comments letting the reader know to keep them in sync

I've taken another approach, passing the pad_slot_id through the kernel params, keeps it simpler since we don't need to keep the cpp and python variables in sync and keeps the mamba kernels as standalone entities. WDYT?

Sounds good to me

I tried out the PR and am currently seeing the following error:
E           RuntimeError: Error in model execution (input dumped to /tmp/err_execute_model_input_20241015-011501.pkl): _C::causal_conv1d_fwd() expected at most 8 argument(s) but received 9 argument(s). Declaration: _C::causal_conv1d_fwd(Tensor($0! -> ) x, Tensor($1! -> ) weight, Tensor? bias_, Tensor($2! -> )? conv_states, Tensor? query_start_loc, Tensor? cache_indices, Tensor? has_initial_state, bool silu_activation) -> Tensor

If you're seeing the same issue, could you LMK when it's fixed? Looks good otherwise, thanks!

@tlrmchlsmth  I cannot reproduce this error, could you let me know how do you run it?

@tlrmchlsmth I cannot reproduce this error, could you let me know how did you run into it?

Possibly user error, let's see if it goes through the CI ;)

Merging now! from @simon-mo the readthedocs failure looks transient

@tlrmchlsmth I have a question, regarding how we have observed that the mamba cache may possibly run out of free slots, resulting in the pop creating a fatal error that cannot be recovered from.
We have created a bug report here. Would really appreciate any thoughts! https://github.com/vllm-project/vllm/issues/10693
I personally am very new to vllm and do not have very deep understanding into the scheduler.
CC: @nelsonspbr


how to control more than 2 servos?

how to control more than 2 servos?because there were only two pwm(pwm0 and pwm1)

Can we use the GPIO port to simulate PWM output in Android Things.Like this:
void servo_pulse(int myangle) {   int PulseWidth;                    //定义脉宽变量   PulseWidth = (myangle * 11) + 500; //将角度转化为500-2480 的脉宽值   digitalWrite(ServoPin, HIGH);      //将舵机接口电平置高   delayMicroseconds(PulseWidth);     //延时脉宽值的微秒数   digitalWrite(ServoPin, LOW);       //将舵机接口电平置低   delay(20 - PulseWidth / 1000);     //延时周期内剩余时间   return; }
I can't make the thread to sleep 0.5ms in Android Things.

The GPIO control in Android Things doesn't have the level of precision that you may want for high frequency PWM.


chore(deps): update reviewdog/action-shellcheck digest to 96c6653

This PR contains the following updates:

Package
Type
Update
Change

reviewdog/action-shellcheck
action
digest
66c9a47 -> 96c6653

Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

bors r+


Update the valid states

Updating the valid states to be the same as filter.py in the sigmac.py tool from Sigma.

Thanks for this! ❤  Closes #5


Feature/create index page

What is the Purpose?
This adds an Index Page to the PR sample app.
What was the approach?
Presently not the best implementation as I have style in the same page, but looking for a way to structure styles on plug apps.
Are there any concerns to addressed further before or after merging this PR?
The page can be further improved later, this just is placeholders.
Mentions?
Mention persons you'd like to review this PR
Issue(s) affected?
List of issues addressed by this PR.

@kamalogudah ,This is good. We truly need this. was just thinking of the contents we need there. This we can discuss on later. But i was thinking of if we can maybe render the readme.md to be html, cause it will pretty much cover everything. just a though.
And since it's a simple page, I don't think I personally mind having the css there, unless the files grows, it's something we can check on in future, but no harm if you work on it

@kamalogudah , one more thing, are the contents of the page needed to be in this PR, or it's something we can discuss about later?

@kamalogudah , one more thing, are the contents of the page needed to be in this PR, or it's something we can discuss about later?
Was thinking of Linking the different endpoints from this page, so once you are on a particular page eg. USSD we can have info on its implementation since the sample app, unlike the library, will not have documentation to explain how it works.

@kamalogudah , one more thing, are the contents of the page needed to be in this PR, or it's something we can discuss about later?
Was thinking of Linking the different endpoints from this page, so once you are on a particular page eg. USSD we can have info on its implementation since the sample app, unlike the library, will not have documentation to explain how it works.

That is also fine, i hadn't thought about it . That can will work

The PR is 8 days old, seems there is no more reactions coming soon


Switch to Flagged Label & Terminology

cc @denelon
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109906&drop=dogfoodAlpha

@denelon How about a creating a new label Package-Flagged?

What should be used for the description and HTML color?

What should be used for the description and HTML color?

Same color as the Package-Hash-Flagged, description "The package must go through a more thorough validation to ensure it fully complies with repository policies"

@stephengillie - Maybe there's a word limit to the label descriptions? I'm not seeing the full message on my end. Maybe we can make it more concise as:
Package needs further validation ensuring compliance with repository policies

@stephengillie - Maybe there's a word limit to the label descriptions? I'm not seeing the full message on my end. Maybe we can make it more concise as: Package needs further validation ensuring compliance with repository policies

Good catch.


Add support for Cognito User pool - CognitoSyncSample

CognitoSyncSample: Add full support for AWS 2.4.7
CognitoSyncSample: Add support for Cognito User pool

@ascuderibjss I hope it is ok to contact direct, but your branch is throwing an error or I have missed a config option.
I oringinally downloaded the branch to validate my own code as when linking AWS User Pools to Federated Identities was throwing the following error.
{
    Connection = "keep-alive";
    "Content-Length" = 109;
    "Content-Type" = "application/x-amz-json-1.1";
    Date = "Tue, 27 Sep 2016 09:24:44 GMT";
    "x-amzn-ErrorMessage" = "Token is not from a supported provider of this identity pool.";
    "x-amzn-ErrorType" = "NotAuthorizedException:";
    "x-amzn-RequestId" = "3a673f77-8494-11e6-bc90-53fe585ab916";
}

This branch throws the same error.
As for my config I have done the following steps

Create mobile hub account in US East 1
User Sign in Required
Added in Facebook
Created Cognito User Pool with everything as default
Added App ( copied client id and secret)
Edited Federated Identity that was created by mobile hub
Added User Pool ID and App Client ID
Unauthenticated Roles are turned off and there is no unauthenticated role assigned.

I have added the details in to Constatns.swift
Login works fine but when linking I get the error as as above.
Thanks in advance

Hi @blastedcoder.
Check you have the latest branch, because yesterday I fixed something.
I've tested with my constants and it works fine. I'm using Xcode 8, Swift 3.
In order to work with Xcode 8, you need to enable the Keychain Sharing capability in the CognitoSyncDemo target.
I've updated AWS to 2.4.9 using: pod update
Check that you have set the following:
static let COGNITO_REGIONTYPE = AWSRegionType.USEast1
static let COGNITO_IDENTITY_POOL_ID =  "..." //Yours on Federated Identity -> Identity Pool Id
static let COGNITO_IDENTITY_USER_POOL_ID = "..." //Yours on User Pool -> Pool Id
static let COGNITO_IDENTITY_USER_POOL_APP_CLIENT_ID = "..." //Yours on User Pool -> Apps -> App Client Id
static let COGNITO_IDENTITY_USER_POOL_APP_CLIENT_SECRET = "..." //Yours on User Pool -> Apps -> App Client Secret
In Info.plist:
Url Schemes change fb############ with your Facebook App Id
set FACEBOOK_APP_ID
set FACEBOOK_DISPLAY_NAME
Note
I've tried with unauthenticated enabled and disabled in AWS Federated Identity and it works.
I have created both authenticated and unauthenticated roles.
Check that your user has a CONFIRMED status in AWS User Pool console.

@ascuderibjss
Thanks I will do. It is now working, but I weirdly had to do the following steps an no code changes.
Remove Facebook from Federated Identity - Authentication providers
Save so just Cognito is set
Re-add Facebook back in
All works fine, I am not sure if this is because it was originally set up using MobileHub

@ascuderibjss
I have tested it and the code appears to all be working fine. That being said my code works fine too.

Can this be updated to support Swift 3?

Here is a branch for Swift 3:
https://github.com/bjss/aws-sdk-ios-samples/tree/aws-cognito-userpool-swift3

close this due to code rot - missing swift 3 branch.


SharpZipLib 1.4.0 dependency may cause deadlocks

Describe the bug
SharpZipLib has found a regression in its codebase (https://github.com/icsharpcode/SharpZipLib/issues/786) between 1.3.3 and 1.4.0 which can cause deadlocks when writing tarballs
v2.2.0 references SharpZipLib 1.4.0 which may cause deadlocks.
To Reproduce
In my case I was running Testcontainers in a BeforeFeature binding in Specflow.
Expected behavior
No deadlocks. I don't see any preview versions where this fix is included. However, rolling back to 1.3.3 should also work.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Testcontainers v2.2.0

Additional context
https://github.com/icsharpcode/SharpZipLib/issues/788
https://github.com/icsharpcode/SharpZipLib/pull/791

I assume you call something like Wait(), GetAwaiter().GetResult() or Result in BeforeFeature? That will block the async context and is not recommended anyway. You will probably get around this by wrapping your call in Task.Run(() => {}); (not recommended either), but might work. Best is to stick to the async context.

No, SpecFlow is all async, the BeforeFeature bindings are async too. The .GetAwaiter().GetResult() is done inside the SharpZipLib library code.
See this diff: https://github.com/icsharpcode/SharpZipLib/pull/791/files#diff-99397a219e400099c43754f54b5b72a2fdd17d5e1bdbeef6ca31e160cef4b07bL384
They use an isAsync flag which was set incorrectly (this is the change where they fixed it). This change has not yet been released. With the isAsync flag set to true, like in 1.4.0, it will write out to the outputStream asynchronously. This is then awaited in the TarOutputStream: public TarEntry GetNextEntry() => GetNextEntryAsync(CancellationToken.None, true).GetAwaiter().GetResult(); and deadlocks.

When I reference SharpZipLib 1.3.3 I get a package version downgrade detected error from dotnet restore because the Testcontainers v2.2.0 NuGet package has a SharpZipLib >= 1.4.0 dependency. I downgraded Testcontainers to v2.1.0 which also works for now! 👍


Add Julie Norris to Contributors list

Hi  @julie-norris, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi -
The tutorial was very easy and clear. I felt excited to be able to follow along and have success at every step.
Thank you!


Installation Issue

D:\java\jupyter>java --version
openjdk 22.0.1 2024-04-16
OpenJDK Runtime Environment (build 22.0.1+8-16)
OpenJDK 64-Bit Server VM (build 22.0.1+8-16, mixed mode, sharing)
(.ijava) D:\java\jupyter>jupyter --version
Selected Jupyter core packages...
IPython          : 8.26.0
ipykernel        : 6.29.5
ipywidgets       : 8.1.3
jupyter_client   : 8.6.2
jupyter_core     : 5.7.2
jupyter_server   : 2.14.2
jupyterlab       : 4.2.4
nbclient         : 0.10.0
nbconvert        : 7.16.4
nbformat         : 5.10.4
notebook         : 5.4.0
qtconsole        : 5.5.2
traitlets        : 5.14.3
(.ijava) D:\java\jupyter>java -jar ./rapaio-jupyter-kernel-2.0.0.jar -i -auto
(.ijava) D:\java\jupyter>
installing jar isn't working, OS WIN10

I will look over it.
Which is the output of the installer command: D:\java\jupyter>java -jar ./rapaio-jupyter-kernel-2.0.0.jar -i -auto ?

nothing appeared on the terminal.

Sorry for being late. I just get a windows host and I am able to reproduce. I will investigate the issue and push a new release with the solution soon.


containerd-shim-kata-v2 debug option cannot be opened

Is your feature request related to a problem? Please describe.
When I use containerd-shim-kata-v2, the debug option cannot be opened
Describe the solution you'd like
containerd-shim-kata-v2 can open debug options
Describe alternatives you've considered
Modify the default value of debug flag to true

Additional context
No
Before raising this feature request
yes

I don't fully understand the request. If you pass "-debug" to the containder-shim-kata-v2 binary it just works. Mind that configuring it depends on the what's calling the binary and for a better explanation, check: https://github.com/fidencio/kata-documentation/blob/wip/shimv2-and-crio/Developer-Guide.md#debug-logs-and-shimv2
If you're talking about having different log levels traced, other than debug, take a look at: https://github.com/kata-containers/kata-containers/issues/366
Please, let us know if this solve your issue.

I don't fully understand the request. If you pass "-debug" to the containder-shim-kata-v2 binary it just works. Mind that configuring it depends on the what's calling the binary and for a better explanation, check: https://github.com/fidencio/kata-documentation/blob/wip/shimv2-and-crio/Developer-Guide.md#debug-logs-and-shimv2
If you're talking about having different log levels traced, other than debug, take a look at: kata-containers/kata-containers#366
Please, let us know if this solve your issue.

Thanks, your answer solved my problem


Root index.md doesn't show title

Main page toc/index.md doesn't show title.
---
title: Title page
---

Interesting. Yeah index is probably not supported with titles. Will think how to add it. Thanks for reporting.
I also noticed that a lot of our internal docs people don’t know what to put on index page and they remove it instead.

this was releases as 1.61


.Net: Added dimensions property to OpenAI embedding generation services

Motivation and Context

Resolves: https://github.com/microsoft/semantic-kernel/issues/6026
This PR contains changes to expose dimensions property which is supported by OpenAI and Azure .NET SDK:
https://platform.openai.com/docs/api-reference/embeddings/create#embeddings-create-dimensions

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Adding this parameter at the connector level seems to be an issue, we might consider having a ExecutionSettings for embeddings API...
Any change on this matter I would add as experimental if the plan is to soon move this to be a setting per Invocation.
@westey-m

Adding this parameter at the connector level seems to be an issue, we might consider having a ExecutionSettings for embeddings API...

@RogerBarreto I thought about that, but I also think that we can have both options supported. If you set vector dimensions once on connector level, you won't have to do that with each request. And I don't think that this parameter will change too much in runtime, because every time you change the dimension, your data may lose a context.
ExecutionSettings for embedding API will be supported, here is ADR for this:
https://github.com/microsoft/semantic-kernel/pull/5277

Any change on this matter I would add as experimental if the plan is to soon move this to be a setting per Invocation.

All embedding functionality is marked as Experimental at the moment.

IF this is Experimental, suggest creating a new method with the dimension extra parameter as Experimental and avoid the Breaking Change.

IF this is Experimental, suggest creating a new method marked as Experimental with the new dimension extra parameter to avoid the breaking change.

@RogerBarreto I thought about that as well :) But the thing is that there are 11 methods that were modified. In order to avoid breaking changes, I will need to add 11 more overload methods with new parameter. It's not a big problem, but since we agreed that at some point we will have to obsolete existing methods and replace them with Config classes, I'm not sure if we need to add new methods now in order to obsolete them later.
Besides, this is breaking change only from API compatibility point of view, but not for compiler, that's the reason I added this parameter as last one. And since these are static methods, it's not possible to mock them in tests, so it should not break mocking scenarios.


Integrating SteamVR in VRTK

Followed this tutorial: https://www.youtube.com/watch?v=tyFV9oBReqg&t
The VRTK simulator works fine, and I could also import the SteamVR, but it does not switch to the SteamVR, when one of the examples is played. The "Switch SDK Setup" button does not work either.
I then tried to make my own scene and implement the SteamVR manually, it is shown in the video from around 5:34. But the controllers and stuff did not show up. Only a static camera.

You may need the VR Controllers connected to run SteamVR.
If you don't have VR controllers, you can manually select only the simulators.
Then, there must be a way to map the controller inputs, but don't know this (yet),
And ensure the example project is 003 or higher, the first two examples don't have any interaction.
Please tell how it goes -- esp. if you solve the mapping.

On 2 Mar 2018, at 11.30, benjaminvinje<EMAIL_ADDRESS>wrote:
Followed this tutorial: https://www.youtube.com/watch?v=tyFV9oBReqg&t
The VRTK simulator works fine, and I could also import the SteamVR, but it does not switch to the SteamVR, when one of the examples is played. The "Switch SDK Setup" button does not work either.
I then tried to make my own scene and implement the SteamVR manually, it is shown in the video from around 5:34. But the controllers and stuff did not show up. Only a static camera.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fixing race conditions in this test file.

@michael-berlin @enisoc easy fix.

This change is

LGTM


Fix reusing float histograms

In https://github.com/prometheus/prometheus/pull/13276 we started reusing float histogram objects to reduce allocations in PromQL. That PR introduces a bug where histogram pointers gets copied to the beginning of the histograms slice, but are still kept in the end of the slice. When a new histogram is read at the last element, it can overwrite a previous element because the pointer is the same.
This commit fixes the issue by moving outdated points to the end of the slice so that we don't end up with duplicate pointers in the same buffer. In other words, the slice gets rotated so that old objects can get reused.

Does this fix affect the benchmark results of https://github.com/prometheus/prometheus/pull/13276?

There seems to be a small difference, but the benefits from reusing objects are still there
 benchstat main.out new.out                                                                                Filips-MacBook-Pro-2.local: Fri Dec 15 07:13:14 2023

name                         old time/op    new time/op    delta
NativeHistograms/sum-8          490ms ± 5%     491ms ± 2%    ~     (p=0.690 n=5+5)
NativeHistograms/sum_rate-8     763ms ± 3%     805ms ± 1%  +5.49%  (p=0.008 n=5+5)

name                         old alloc/op   new alloc/op   delta
NativeHistograms/sum-8          414MB ± 0%     415MB ± 0%  +0.15%  (p=0.032 n=5+5)
NativeHistograms/sum_rate-8     641MB ± 0%     665MB ± 0%  +3.66%  (p=0.008 n=5+5)

name                         old allocs/op  new allocs/op  delta
NativeHistograms/sum-8          5.16M ± 0%     5.16M ± 0%    ~     (p=0.056 n=5+5)
NativeHistograms/sum_rate-8     10.3M ± 0%     11.0M ± 0%  +7.23%  (p=0.008 n=5+5)
```


[dv] alert connection in GLS

Top level alert connections might break GLS.
Need to think of a better solution.

@jdonjdon I think we have a workaround for this right? I am closing this for now, but please reopen if you think we should still track this.

Description is too simplified to identify what the issue referring to but FWIW,
we don't have open alert connection issue in our current GLS.

Ok thanks - if this is not an issue let's just leave it closed.


Fix Base.show

Codecov Report
Patch coverage has no change and project coverage change: -0.18 :warning:

Comparison is base (5c0063a) 27.34% compared to head (55a36d0) 27.16%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
- Coverage   27.34%   27.16%   -0.18%
==========================================
  Files          18       17       -1
  Lines        1620     1627       +7
==========================================
- Hits          443      442       -1
- Misses       1177     1185       +8

Impacted Files
Coverage Δ

src/facet.jl
57.36% <0.00%> (-0.91%)
:arrow_down:

src/kepler.jl
22.38% <0.00%> (-0.11%)
:arrow_down:

src/nbody.jl
0.00% <0.00%> (ø)

src/shape.jl
63.63% <0.00%> (-0.98%)
:arrow_down:

src/spin.jl
26.66% <0.00%> (-0.37%)
:arrow_down:

src/thermophysics.jl
46.72% <0.00%> (-0.39%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Release v.1.0.4

Deploying the Release.Revision fix. Last PR for this.

@fiunchinho 👍  Good catch.
They should match aws-operator and fmt.
https://github.com/giantswarm/fmt/blob/5eee083da1713813a841a969e34d6cd8d79c82cd/releases/changelogs_for_managed_apps.md


Persistent app last active

What kind of PR is this?:

/kind
What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
[ ] No console errors on web
[ ] Tested on Light mode and Dark mode*
[ ] Your UI implementation visually matched the rendered design*
[ ] Unit tests*
[ ] Added e2e tests*
[ ] Added translations*

for debug use, no longer needed


foma: init at 0.9.18alpha

Motivation for this change
add foma
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108633 run on x86_64-linux 1

1 package built:

foma

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108633 run on x86_64-linux 1

1 package built:

foma

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108633 run on x86_64-darwin 1

1 package failed to build and are new build failure:

foma: log https://hastebin.com/raw/lezifoyoyo

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108633 run on x86_64-darwin 1

1 package failed to build and are new build failure:

foma: log https://hastebin.com/raw/lezifoyoyo


'Jumps' in tracks

Hi there,
I've been segmenting my images with Cellpose 3.0 and using Trackastra for tracking afterwards, but I've observed large 'jumps' in my tracks (screenshot of tracked movie below) and I'm not too certain what the cause might be:
I do plan to annotate the errors but in the meantime please let me know if you have any ideas on how I can correct these errors.
Best regards,
Raeesah

Hi Raeesah, great to see Trackastra 3D in action, and thanks for the feedback.
I confirm that such jumps do sometimes show up with our current models, and might occur due to a difference in characteristics between the training data and the prediction data.
As of now, I would suggest to set the maximum linking distance (max distance in the plugin widget) to a lower value if your dataset allows for it.

Thanks Benjamin, that's good to know. I tried lowering the linking distance and it helped.
I do also experience issues with cell identities/colours changing between timepoints, but I think this is a problem related to Cellpose segmentation that I'll try to optimise.


[JavaFX - Part2] Additional tutorial for styling of components

Current:
"Styling" section only include those for containers and user input box. It also only gives instructions on styling to get the example UI, without much explanation.
Problem:
Styling for dialog box elements is not specifically mentioned. It is only mentioned later in part 3, but it is more relevant to part 2. Furthermore, this part does mention that readers should refer to the official JavaFX documentation for a comprehensive list of properties to modify. However, some students may not read them especially when they are given a ready-for-use piece of code for their individual project.
Proposed:
Also explore styling for Image View and text label.
Mentions some of the most commonly-used properties for each element as examples. For example, wrapping in text label and scroll panel and binding of width and height can be mentioned. Provide explanation for lines of code whose purposes are not immediately understandable.

@laney0808 Check if the new 'Part 5' covers this aspect. If not, you can send a PR to propose your change (to part 2 or part 5).

new 'Part 5'

Hi Prof! I realized that part of it is mentioned in part 5, and the other part is already fixed in issue #29. I'll close this issue for now.


[Question] Voice packet loss compensation

Due the fact that the voice connection uses UDP, there is always the possibility of occurring some nasty packet loss, and while I was using a discord library from another language, I noticed that they have a compensation setting built-in which makes quite a difference in the audio quality.
I digged into their code and looks like they send the same packet multiple times to achieve that.
_sendPacket(packet) {
    let repeats = this.streamOptions.passes;
    this._setSpeaking(1);
    while (repeats--) {
      if (!this.player.voiceConnection.sockets.udp) {
        this.emit('debug', 'Failed to send a packet - no UDP socket');
        return;
      }
      this.player.voiceConnection.sockets.udp.send(packet)
        .catch(e => {
          this._setSpeaking(0);
          this.emit('debug', `Failed to send a packet - ${e}`);
        });
    }
}

is there a possibility of implementing this feature?
Bonus question haha...
I've used both dca and dgvoice to send audio, and both experience some nasty artifacts during the few first ms of the audio, not sure if this is related to packet loss, or if I'm doing something wrong haha.
Anyone has experienced this?

I don't see any loss compensation in this code it's just sending packets
The audio compensation is done by the opus format nothing can be done as UDP doesn't guarantee that the packet will be received
I didn't had any trouble with Opus audio encode in dca format. That's was the primary reason I switch to discordgo because at the given time I was using ffmpeg with discordjs if I remember but it cause a loss of 0.5s before and after the audio file which was disturbing as I was making a bot that was play meme sounds (which were about 3s), so I had to add blank before and after each audio

Ah, makes sense, while using discordjs I noticed the artifacts if I tried to play a file directly using their playfile method, but If I used a stream buffer it would play normally.
I'm getting the same artifacts while using a dca buffer, Are you using bwmarrin's dca encoder? and what settings are you using for the encode.

Ah it was about how discordgo was working at a given time, it had a big chan of AudioFrame so when I ask the bot to pause it still playing for 2-3s, to avoid the issue I've decided to put frame in the channel by myself with the same interval of time than discordgo send the audio frames

Ah, yeah, makes sense the use of a ticker, glad they changed that.
btw, looks like my net was indeed the cause of the artifacts, today It ran smoothly, thank you for your help!


Swarm environment not setting up - swarmkit-mon stuck in initializing

Rancher Version: v1.2.2-rc1
Steps to Reproduce:

Create three DO machine with private IP
Install docker 1.12.3
Add those host to swarm environment

Results: The main swarmkit-mon container logs keeps saying "12/21/2016 5:16:23 PMRetrying publishing tokens".  the second and third host swarmkit-mon are stuck in initializing.
Expected:  Should setup.

First environment functioned correctly. Second environment reproduced the bug.
The API call to Rancher that should write the worker/manager tokens to the service is failing. Performed a packet capture and observed the service UUID read from metadata was null. This is a known race condition where metadata isn't always populated to the host before the container begins exection.
Temporary workaround is to add a loop to wait for metadata to become available.

Available in community catalog, branch swarmtest with swarmkit:v1.12.3-2

Version - v1.2.2-rc2 swarmkit 1.12.3-2
Verified fixed.


Add sparse matrix functionality in metaedge_to_adjacency_matrix

Refs #36 Edited test_matrix.py to test equality of sparse matrices. Added conversion in degree_weight.py from sparse to dense.

@dhimmel Will we want to work entirely with sparse matrices, or will conversion to dense be workable for some steps, for example in dwwc_step?
In the PR, I added a line to convert to dense, but I realize doing this whenever we need to use a matrix defeats the purpose of using sparse matrices.

Note, to test the equality of the two arrays, I used a sparse matrix and its corresponding .nnz function to get the most foolproof method of comparison between two arrays, no matter the different types.
It was tricky trying to compare two arrays of ambiguous type, and this works, despite the fact that it is not an obvious method.
This should be a pretty efficient way of checking, I think, because using == to compare two sparse matrices gives an efficiency warning which recommends using != as an efficient comparision.


Set go version to 1.17 to match CI

Closes #10580
What this PR does / why we need it:
Bump go version to 1.17 to match CI. It's needed because building with 1.16 is broken and because the CI uses 1.17.

CI Has this error:
ERRO Running error: context loading failed: no go files to analyze

The PR doesn't contain any modification to go files, I guess this is normal (but probably should not fail ?)

likely fixed once https://github.com/helm/helm/pull/10575 is merged - golint is deprecated.

For reference, the version number listed in go.mod dictates the minimum version of Go you can use to compile the project. It does not have to match the same version in CI - in fact it can be several versions behind. However in the case described in #10580, it sounds like Helm cannot be compiled against Go 1.16 due to an issue with a transitive dependency, so bumping go.mod to a version that does compile seems fine to me.

I think, the CI should use the minimum version of Go you can use to compile the project, so this situation doesn't happen.

I agree that we should run the test suite against all supported versions of Go (and we'd appreciate a PR to do so next time!). But I don't think we should release new versions of Helm compiled against the minimum version. Newer versions of Go contain performance improvements and bug fixes, many of which will benefit Helm users, which is why we compile Helm against the latest stable version of Go.

Can you please rebase? Thanks

@bacongobbler Done !


Small javadoc fixes

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@65610b1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #408   +/-   ##
=========================================
  Coverage          ?   85.48%
  Complexity        ?     2262
=========================================
  Files             ?      159
  Lines             ?     6806
  Branches          ?     1020
=========================================
  Hits              ?     5818
  Misses            ?      664
  Partials          ?      324

Impacted Files
Coverage Δ
Complexity Δ

...ava/nl/esciencecenter/xenon/util/OutputReader.java
80.95% <ø> (ø)
9 <ø> (?)

.../nl/esciencecenter/xenon/util/StreamForwarder.java
69.38% <ø> (ø)
11 <ø> (?)

...java/nl/esciencecenter/xenon/util/InputWriter.java
76.66% <ø> (ø)
7 <ø> (?)

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 65610b1...d717e6b. Read the comment docs.


QoL - Being able to look up your character's hiscore by right-clicking.

Add an option to search up your character hiscore by right-click. Maybe on the character name or the report button...
Thanks!

You can double-click the hiscore text field and it will lookup the local player's name.

You can't right click yourself but yeah this is already implemented by double-clicking the hiscore


[Feature] custom cmd path for custom cmds

Need an configuration field to specify where to save and load custom cmds

@qlibp Out of curiosity, how are you planning to use this? commit the custom commands in a git repo?

@qlibp I've added support for this. You can declare custom_cmd_dir using your setup function.


Introduce global stellargraph seed

Sorry for abandoning the old PR and reviews @huonw @timpitman , but I wasn't so happy with how that turned out.. and this is a slight alternative I tried that I ended up liking more after thinking about some of the review comments in the previous PR #705
In the old PR, after realising that we didn't need to seed the global numpy random at all, the stellargraph seed was basically just seeding the global python random and the tensorflow random. It felt weird that tensorflow and numpy have their own isolated random state, yet our library would rely on seeding the python global random. I also thought it was weird that we had a "global seed generator" in the old PR, rather than a "global random state", and we were making new random objects everywhere.
This alternative approach is designed to achieve something like:

when there's no global seed set, all the randomness relies on the global random and numpy.random
when there's a global seed set, all the randomness relies on our own single set of global random.Random and numpy.random.RandomState objects

I've had to update the multiple seeded sampler logic in GraphSAGELinkGenerator a bit as a result, since seed=None when that object is constructed does not necessarily mean there's no global seeded state.
One slightly unfortunate thing is that using Model.fit_generator(..., shuffle=True) seems to rely on the global python random - so now we test that seeding the global python random is only needed when shuffle=True.

Codecov Report

Merging #806 into develop will increase coverage by 0.23%.
The diff coverage is 28.57%.

@@             Coverage Diff             @@
##           develop     #806      +/-   ##
===========================================
+ Coverage    82.29%   82.53%   +0.23%
===========================================
  Files           47       47
  Lines         5201     5295      +94
===========================================
+ Hits          4280     4370      +90
- Misses         921      925       +4

Impacted Files
Coverage Δ

stellargraph/utils/loss.py
0% <0%> (ø)
:arrow_up:

stellargraph/layer/misc.py
85.71% <100%> (-2.39%)
:arrow_down:

stellargraph/layer/watch_your_step.py
30% <30%> (ø)
:arrow_up:

stellargraph/mapper/adjacency_generators.py
31.42% <31.42%> (ø)
:arrow_up:

stellargraph/data/unsupervised_sampler.py
91.54% <0%> (-0.29%)
:arrow_down:

stellargraph/data/explorer.py
97.42% <0%> (+0.13%)
:arrow_up:

stellargraph/mapper/sampled_link_generators.py
93.53% <0%> (+1.16%)
: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 0b9576f...1118537. Read the comment docs.

@huonw

This looks like a reasonable approach, but I think the new functions are subtle enough that it might be good to document?

Good point, I've added a bit of documentation

Also, I think this will only help with stellargraph's layers: if someone is using other tensorflow layers, they'll have to set seeds themselves, appropriately, right?

Do you mean they'll have to set tensorflow.random.set_seed? With the approach in this PR, they would have to do that regardless of whether they're using stellargraph layers or not actually - from what I could tell, tensorflow layers always rely on the tensorflow global random state rather than being able to use a separate random state instance so I left it out from our random module.
sg.random.set_seed(seed) # this doesn't touch any other external global random states
tf.random.set_seed(seed)

# do reproducible stuff

alternatively, below should also work:
random.seed(seed)
numpy.random.seed(seed)
tf.random.set_seed(seed)

# do reproducible stuff

Given the fact that our library doesn't try to abstract away all the tensorflow/keras workflow, I thought this would be okay.

Maybe we could take a documentation approach: e.g. in stellargraph.random or stellargraph.random.set_seeds docs, have a (brief) discussion of how to get reproducibility, with reference to tf.random.set_seed(seed)

That's a good idea.


Freeze Protection (FP) mode

Is it possible to add freeze protection mode? This feature is in the smarthome app.

Freeze protection mode is implemented as the "Away" preset. It should be visible if your device indicates support for it. Otherwise you can use the "Show All Presets" integration option to force support for it.

Great, thanks. That worked perfectly :-)


Fix checking for git source presence

Signed-off-by: Mykola Morhun<EMAIL_ADDRESS>

Verified with build-service image built by PaC from this PR. I used this branch of e2e-tests to run the tests:
➜  e2e-tests git:(93-cleanup) make build && ./bin/e2e-appstudio --ginkgo.progress --ginkgo.focus="build-service-suite" --ginkgo.v
...
Ran 3 of 30 Specs in 87.053 seconds
SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 27 Skipped
PASS
➜  e2e-tests git:(93-cleanup)

/lgtm


feat(speedup): refactor ModulSpeedup V2 using torch.fx graph

Description
refactor ModulSpeedup V2 using torch.fx graph.
refactor the propagation and make all the intermediate varibales const.
refactor the API to differentiate propagation of different operations.
Test Options

[ ] fast test
[ ] full test - HPO
[ ] full test - NAS
[x] full test - compression

Checklist

[x] test case
[ ] doc

How to test

@microsoft-github-policy-service agree

/azp run full test - compression

/azp run full test - compression


Error when linking accounts

I'm getting the following error when following these steps:

Create a new account using Apple Social Login
Logout
Try to logging using Google Social Login with the same email
A conflicting account is triggered, so I link the account to the existing apple with:
var res = await resolver.linkToSocial(SocialProvider.apple);
It fails with the next error:

NoSuchMethodError: The method '[]' was called on null.
Receiver: null
Tried calling: []("callId"), #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:63:5)
#1      new GigyaResponse.fromJson (package:gigya_flutter_plugin/models/gigya_models.dart:35:22)
#2      new Account.fromJson (package:gigya_flutter_plugin/models/gigya_models.dart:82:42)
#3      _showLinkToSiteBottomSheet.<anonymous closure> (package:reactions/components/SocialButtons.dart:344:61)
<asynchronous suspension>

These steps works corretly for other linkings, for example Facebook -> Google, Google -> Facebook, etc
The executing code is (inside a try catch):
var res = await resolver.linkToSocial(SocialProvider.apple);
final Account account = Account.fromJson(res);

It looks like linkToSocial don't throw any error, but it returns null. The apple webview never opens.

fixed in 0.1.3 release.


Rancher failed to find a placement

Sometimes my containers don't seem to start, or they start incredibly slowly. Even when the image (I think?) was already pulled.
I do see some error in the server log. I'm not sure if this is related to my problems, but it is maybe important enough to show an error in UI and to have a clear msg in the logs of what it means.
2015-03-08 13:37:07,159 ERROR [:] [] [] [] [cutorService-62] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [2] count [3]
2015-03-08 13:37:07,160 ERROR [:] [] [] [] [cutorService-76] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [3] count [3]
2015-03-08 13:37:12,158 ERROR [:] [] [] [] [cutorService-78] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [4] count [4]
2015-03-08 13:37:12,158 ERROR [:] [] [] [] [cutorService-75] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [2] count [1]
2015-03-08 13:37:12,159 ERROR [:] [] [] [] [cutorService-76] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [5] count [4]
2015-03-08 13:37:12,158 ERROR [:] [] [] [] [cutorService-65] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [7] count [1]
2015-03-08 13:37:17,160 ERROR [:] [] [] [] [cutorService-79] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [5] count [5]
2015-03-08 13:37:17,160 ERROR [:] [] [] [] [cutorService-65] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [4] count [5]
2015-03-08 13:37:22,160 ERROR [:] [] [] [] [cutorService-64] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [4] count [1]
2015-03-08 13:37:22,161 ERROR [:] [] [] [] [cutorService-50] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [5] count [1]
2015-03-08 13:42:02,224 ERROR [:] [] [] [] [cutorService-79] [i.c.p.a.s.ping.impl.PingMonitorImpl ] Failed to get ping from agent [11] count [1]
2015-03-08 13:42:03,575 ERROR [31b920c5-b975-4022-94c9-7b7e46f02a66:553] [instance:39] [instance.start->(InstanceStart)->instance.allocate->(InstanceAllocate)] [] [cutorService-85] [c.p.a.e.i.AllocatorEventListenerImpl] No allocator handled [EventVO [id=a08f6710-c631-4c08-bb1a-1f90217a6583, name=instance.allocate, previousNames=null, replyTo=reply.8525061809052791520, resourceId=39, resourceType=instance, publisher=null, transitioning=null, transitioningMessage=null, transitioningInternalMessage=null, previousIds=null, data={}, time=Sun Mar 08 13:42:03 UTC 2015, listenerKey=null, transitioningProgress=null]]
2015-03-08 13:42:03,581 ERROR [31b920c5-b975-4022-94c9-7b7e46f02a66:553] [instance:39] [instance.start->(InstanceStart)->instance.allocate] [] [cutorService-12] [c.p.e.p.i.DefaultProcessInstanceImpl] Unknown exception io.cattle.platform.eventing.exception.EventExecutionException: Failed to find a placement
	at io.cattle.platform.eventing.impl.AbstractEventService.callSync(AbstractEventService.java:265) ~[cattle-framework-eventing-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.process.common.handler.EventBasedProcessHandler.handle(EventBasedProcessHandler.java:82) ~[cattle-iaas-logic-common-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runHandler(DefaultProcessInstanceImpl.java:434) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$4.execute(DefaultProcessInstanceImpl.java:373) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$4.execute(DefaultProcessInstanceImpl.java:370) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.idempotent.Idempotent.execute(Idempotent.java:43) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runHandlers(DefaultProcessInstanceImpl.java:370) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runLogic(DefaultProcessInstanceImpl.java:498) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runWithProcessLock(DefaultProcessInstanceImpl.java:315) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$2.doWithLockNoResult(DefaultProcessInstanceImpl.java:259) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:7) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.LockCallbackNoReturn.doWithLock(LockCallbackNoReturn.java:3) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.acquireLockAndRun(DefaultProcessInstanceImpl.java:256) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.runDelegateLoop(DefaultProcessInstanceImpl.java:187) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.executeWithProcessInstanceLock(DefaultProcessInstanceImpl.java:160) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:109) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl$1.doWithLock(DefaultProcessInstanceImpl.java:106) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl$3.doWithLock(AbstractLockManagerImpl.java:40) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:33) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) [cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.engine.process.impl.DefaultProcessInstanceImpl.execute(DefaultProcessInstanceImpl.java:106) [cattle-framework-engine-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.process.common.handler.AbstractObjectProcessLogic.execute(AbstractObjectProcessLogic.java:95) [cattle-iaas-logic-common-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.process.instance.InstanceStart.allocate(InstanceStart.java:169) [cattle-iaas-logic-0.5.0-SNAPSHOT.jar:na]
	at io.cattle.platform.process.instance.InstanceStart.handle(InstanceStart.java:57) [cattle-iaas-logic-0.5.0-SNAPSHOT.jar:na]

Is it possible your agents are flapping?  Restarting, having connection issues, etc?  There is a bug at the moment where the agent state is not dynamically reflected on the UI.  You have to refresh.  So it could be that your agent is not connected.
Pretty much the only way to get the error "failed to find a placement" is that you have told rancher to deploy to a server that is detected as unavailable.
Could this be related to your issue with the "Bad Status Line"?  I wonder if that is the root cause.
Also they would start really slow if the agent events are not getting to the Python agent on the node.  So timeouts will happen.

@ibuildthecloud you say "you have told rancher to deploy to a server that is detected as unavailable", I assume with server you mean the host that runs the agent.
I think this may be related to #170 , which looks very familiar to me . Not sure though.

@feliksik Are you still seeing this issue? We've fixed #170 and made many changes with Rancher over the last several months. If it's no longer an issue, I'd like to close it.

 Deploying on a docker image on DigitalOcean and immediately running the rancher server, then trying to run a container comes up with this error.

@geekscrapy does the container still start up on the host?  or are you just seeing this in the logs?

@geekscrapy how big is the host that you have for rancher server? we recommend at least 1 GB. also, are you using 1 DigitalOcean machine for rancher server AND your host?
If so, did you add -e CATTLE_AGENT_IP=<management_server_ip> so the host is showing the same IP as the management server?

@deniseschannon I did originally start it on the smaller tier (512MB) but then after the container crashed a few times I bumped it up.
Yes, using the same machine for both but I didn't use those extra arguments... I'll have a look again tomorrow to see if thats the problem.

I run into this too with the same conditions. I will test if it is the lack of -e CATTLE_AGENT_IP=<management_server_ip> being used.
Although that is mentioned on http://docs.rancher.com/rancher/rancher-ui/infrastructure/hosts/custom/ it isn't on http://my-rancher:8080/static/infra/hosts/add/custom in the UI (which is where I copy the command from). Would be great if we could improve the usability there.

Well the 'slow' or containers not running seems to be active still. First container in a service went ok, second one is stuck in Message: Networking. I don't see the second one in the agent log either.

@flaccid The request to make the info about -e CATTLE_AGENT_IP=<management_server_ip> is an enhancement request for the UI. https://github.com/rancher/rancher/issues/872

Awesome thanks @deniseschannon.

I got this error sometimes, but after some retries it's gone away.

I have this issue again. My rancher host is another machine, has run up stacks without issue recently and its health looks healthy in the UI under Hosts. I also restarted the agent container on the host, nothing is hitting its log. Large tail of the rancher server's log when I run up a stack with a container service in it (the service sits in activating/in progress in the UI): https://gist.github.com/flaccid/67bf395d9e3827a7606e.
The EC2 security groups are adequate. Rancher server is in 1 availability zone, the host in another of the same EC2 region.

@flaccid "failed to find placement" means there is no valid place to put the container on any of the active hosts.  Search for "Checking candidate" in your logs, but the crux is
checking candidate [false] : host needs ports
    {public: ipAddressId=null, port=443; private: ipAddressId=null, port=443; protocol=tcp}
    {public: ipAddressId=null, port=5000; private: ipAddressId=null, port=5000; protocol=tcp}
    {public: ipAddressId=null, port=5001; private: ipAddressId=null, port=5001; protocol=tcp}
    {public: ipAddressId=null, port=5002; private: ipAddressId=null, port=5002; protocol=tcp}
    {public: ipAddressId=null, port=80; private: ipAddressId=null, port=80; protocol=tcp}
    {public: ipAddressId=null, port=8081; private: ipAddressId=null, port=8081; protocol=tcp}
available

The [false] means that condition was not met.  There will be one set of those "Checking candidate" lines for each host until it finds one that meets all the conditions.  So you just don't have a host on which all of those public ports are available where the container could be put..

Ok cool thanks @vincent99 that makes sense, I did have a port usage overlook in this case. Would it be possible to regard that as a usability bug and look at a fix to provide the user with adequate feedback in the UI and if possible stdout in rancher-compose?
I also just raised https://github.com/rancher/rancher/issues/1628 which is obviously not high priority but has some great eye candy value.

While faced with the same issue I found out that the problem was in the default ulimits configuration, namely too low open file descriptor limit (this became clear after checking /var/log/docker.log).
The workaround was to use ulimit -n in the shell and restart dockerd, but I can't help to wonder where did /etc/limits.conf go? What is the preferred way of setting system parameters like that (or sysctl.conf for that matter) in RancherOS?

just wanted to strongly echo @flaccid
I just came across this "failed to find placement" issue due to ports usage and the lack of feedback in the UI (just shows "In Progress" and never times out) as well as stdout of rancher-compose is a major pain.
also in general when I use rancher-compose i am missing feedback like basic progress of pull operations (can take quite a while for large images, doesnt have to be fancy but any sort of "hey I am still alive and working" type of thing would really help). Also it seemed to me that when containers start and fail immediately I never get to see that output in stdout of rancher-compose, e.g I was starting a container which wanted to open a public port using host networking that was already in use, so docker failed to start the container and I never saw that error anywhere in rancher-compose or UI.

I also accidentally ran into this again today then realized I hadn't yet placed a needed label on a host. The cool thing is if we had feedback showing what is missing, one you fix that up it moves on and completes so you feel like you successfully solved a problem on the ranch 😅

Pre-duplicate of https://github.com/rancher/rancher/issues/820


tree@da7808a actually disable post box upon submission

urbit/tree@da7808a actually disable post box upon submission

@ohAitch did you deploy this?