Django 1.11.6 migrate error

Hi,
I must upgrade my django version from 1.9.13 to 1.11.6 for support reasons.
I'm testing with a virtualenv.
I use django==1.11.6, xadmin==0.6.1.
When I run python manage.py migrate command, I've the following error :
from django.forms.widgets import RadioFieldRenderer, RadioChoiceInput ImportError: cannot import name RadioFieldRenderer
I saw the #387 issue but i didn't understand the issue.
Please help me with the correct code.
Thanks.

Use the latest version of xadmin.

Download of last version fixed the error message.
Thanks.


module documentation

Urgent need in project documentation as in "big" python projects

https://github.com/Multi-Agent-io/robonomics-interface/commit/acdc8c46e8f2ca1463b6f0b5bdd1b91d27dce2d2


TimeoutError: waiting for selector #passwd failed: timeout 30000ms exceeded

I'm wondering if anyone has successfully authenticated recently.  Mine's been broken for weeks, and it appears others have also posted issues, though I didn't see any responses or fixes on others' issues, and other issues have been closed.   I'm really just wondering if I need to attempt to troubleshoot/fix, or if it's just known to be broken at this point.
xfinity    | 2022-07-13 10:23:55 [verbose] : Fetching Data
xfinity    | 2022-07-13 10:23:55 [debug] : Loading (https://customer.xfinity.com)
xfinity    | 2022-07-13 10:23:55 [info] : Connected to MQTT
xfinity    | 2022-07-13 10:23:57 [debug] : Login redirects: 3
xfinity    | 2022-07-13 10:23:57 [debug] : Logging in
xfinity    | 2022-07-13 10:24:00 [debug] : Page Title: Sign in to Xfinity
xfinity    | 2022-07-13 10:24:00 [debug] : Loading Usage https://customer.xfinity.com/apis/csp/account/me/services/internet/usage?filter=internet
xfinity    | 2022-07-13 10:24:01 [debug] : Not logged in
xfinity    | 2022-07-13 10:24:01 [debug] : Loading (https://customer.xfinity.com)
xfinity    | 2022-07-13 10:24:03 [debug] : Login redirects: 3
xfinity    | 2022-07-13 10:24:03 [debug] : Logging in
xfinity    | 2022-07-13 10:24:35 [error] : TimeoutError: waiting for selector #passwd failed: timeout 30000ms exceeded. Next update at 11:23:55 AM

You might need to change your frequency to >60 mins. I'm getting the same timeout error sometimes but there's also cases where it will update. see my logs below
2022-07-02 14:53:41 [error] : Error: net::ERR_NAME_NOT_RESOLVED at https://customer.xfinity.com. Next update at 10:53:21 PM, 2022-07-02 22:53:56 [error] : TimeoutError: waiting for selector #passwdfailed: timeout 30000ms exceeded. Next update at 6:53:21 AM, 2022-07-03 06:53:33 [info] : Usage updated: 24 GB. Next update at 2:53:21 PM, 2022-07-03 14:53:33 [info] : Usage updated: 26 GB. Next update at 10:53:21 PM, 2022-07-03 22:53:56 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 6:53:21 AM, 2022-07-04 06:53:34 [info] : Usage updated: 31 GB. Next update at 2:53:21 PM, 2022-07-04 14:53:33 [info] : Usage updated: 32 GB. Next update at 10:53:21 PM, 2022-07-04 22:53:34 [info] : Usage updated: 34 GB. Next update at 6:53:21 AM, 2022-07-05 06:53:41 [info] : Usage updated: 36 GB. Next update at 2:53:21 PM, 2022-07-05 14:53:33 [info] : Usage updated: 39 GB. Next update at 10:53:21 PM, 2022-07-05 22:53:35 [info] : Usage updated: 60 GB. Next update at 6:53:21 AM, 2022-07-06 06:53:34 [info] : Usage updated: 63 GB. Next update at 2:53:21 PM, 2022-07-06 14:53:58 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 10:53:21 PM, 2022-07-06 22:53:33 [info] : Usage updated: 115 GB. Next update at 6:53:21 AM, 2022-07-07 06:53:38 [info] : Usage updated: 118 GB. Next update at 2:53:21 PM, 2022-07-07 14:53:57 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 10:53:21 PM, 2022-07-07 22:53:34 [info] : Usage updated: 124 GB. Next update at 6:53:21 AM, 2022-07-08 06:53:34 [info] : Usage updated: 127 GB. Next update at 2:53:21 PM, 2022-07-08 14:53:57 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 10:53:21 PM, 2022-07-08 22:53:58 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 6:53:21 AM, 2022-07-09 06:53:57 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 2:53:22 PM, 2022-07-09 14:53:57 [error] : TimeoutError: waiting for selector#passwdfailed: timeout 30000ms exceeded. Next update at 10:53:22 PM, 2022-07-09 22:53:38 [info] : Usage updated: 169 GB. Next update at 6:53:22 AM, 2022-07-10 06:53:34 [info] : Usage updated: 173 GB. Next update at 2:53:22 PM, 2022-07-10 14:53:35 [info] : Usage updated: 200 GB. Next update at 10:53:22 PM, 2022-07-10 22:53:35 [info] : Usage updated: 224 GB. Next update at 6:53:22 AM, 2022-07-11 06:53:43 [info] : Usage updated: 228 GB. Next update at 2:53:22 PM, 2022-07-11 14:53:34 [info] : Usage updated: 259 GB. Next update at 10:53:22 PM, 2022-07-11 22:53:34 [info] : Usage updated: 282 GB. Next update at 6:53:22 AM, 2022-07-12 06:53:44 [error] : Error: Unable to login. Next update at 2:53:22 PM, 2022-07-12 14:53:34 [info] : Usage updated: 303 GB. Next update at 10:53:22 PM, 2022-07-12 22:53:34 [info] : Usage updated: 348 GB. Next update at 6:53:22 AM, 2022-07-13 06:53:57 [error] : TimeoutError: waiting for selector#passwd failed: timeout 30000ms exceeded. Next update at 2:53:22 PM

I have my update set to 20 mins and it has been working fine. Yes, there are some TimeoutErrors here and there but it succeeds most of the time.

Thanks for the feedback.  Glad to know it's still working for others.  I set this up on both Docker and Kubernetes, and haven't had either of them work since July 3.  I'll try running this from a different IP just to see if it changes anything.

I've started trying to test more in my Docker instance.  I had an old pwsuffix and cookies.json that I've cleared and hardcoded in with the new pass.  I also added a pageTimeout of 60 to the config.yml since I thought maybe it was a timeout issue, but it doesn't seem to respect that interval, and always reports that it times out after 30 seconds.
I'm intermittently seeing a different issue now, which is a crash on the security check, which is maybe now my main issue:
xfinity    | 2022-07-14 10:23:36 [debug] : Login redirects: 3
xfinity    | 2022-07-14 10:23:36 [debug] : Logging in
xfinity    | 2022-07-14 10:23:41 [debug] : Page Title: Security Check
xfinity    | 2022-07-14 10:23:41 [info] : Clicking "Ask me later" for security check
xfinity    | /home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:217
xfinity    |             this._callbacks.set(id, { resolve, reject, error: new Error(), method });
xfinity    |                                                               ^
xfinity    |
xfinity    | Error: Protocol error (Runtime.callFunctionOn): Target closed.
xfinity    |     at /home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:217:63
xfinity    |     at new Promise ()
xfinity    |     at CDPSession.send (/home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:216:16)
xfinity    |     at ExecutionContext._evaluateInternal (/home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:204:50)
xfinity    |     at ExecutionContext.evaluateHandle (/home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:155:21)
xfinity    |     at WaitTask.rerun (/home/node/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/DOMWorld.js:536:37)
xfinity    |     at processTicksAndRejections (node:internal/process/task_queues:96:5)

Yeah, logging in and manually dealing with those pages was required. It looks like the container can't handle an updated 2FA prompt page.
My steps were to login, add 2FA, and then immediately remove 2FA (there's not actually an "Ask me later" on that screen, which is maybe what changed, and the container code can't handle the new page that's forcing 2FA).
After adding and removing 2FA, I relaunched the container and got the timeout waiting for passwd.  I instantly killed and recreated the container, and it successfully went through...
Whew...


Feature request:  Open last rib file button

Mainly for debugging.

So then we would need to save a copy of the previous rib right?
On Tue, Dec 22, 2015 at 12:58 PM, bsavery<EMAIL_ADDRESS>wrote:

Mainly for debugging.
—
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/162.

No I mean a button that just "opens the last rib we created".  Could save just the filename of the last rib, or figure out what the rib file name is on the fly, open it in a text editor.

Ok, That make more sense.
On Tue, Dec 22, 2015 at 1:11 PM, bsavery<EMAIL_ADDRESS>wrote:

No I mean a button that just "opens the last rib we created". Could save
just the filename of the last rib, or figure out what the rib file name is
on the fly, open it in a text editor.
—
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/162#issuecomment-166693418
.

Button made. You can also use your favorite text editor if you want.

Hooray!
On Tuesday, December 22, 2015, MWY3510<EMAIL_ADDRESS>wrote:

Button made. You can also use your favorite text editor if you want.
—
Reply to this email directly or view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/162#issuecomment-166792343
.

--
<EMAIL_ADDRESS>508-274-8700


[Suggestion] Add the clear output logs when uploading a file to blob container/file share

OS: All
Build Version: 20200903.17
Repro Steps:

Upload a file to one blob container and one file share.
Check the output logs.

Actual:
The output logs are unclear.
Upload to file share:

Upload to blob container:

Suggestion:
Add the clear output logs, such as uploading to blob container/file share "xxx/xxx" from... and Successfully uploaded "xxx/xxx".

We removed the success log message

Verified on the latest build 20201025.1.
The output logs only have "uploading..." when uploading a file to blob container/file share. Sometimes the following occurs: the output logs already show "100%", but there is an uploading notification at the same time-> Not sure whether the upload is complete or not.

So, it would be better add a success log message/notification after uploading a file.


Need documentation for "Uploading Files"

We need documentation in README.md for how a user can upload files to Dropchop (drag-drop & upload button).

@mapsam, you added this functionality, care to add a quick bit of writeup?

Yup, I can do this. Can you give an example of the perspective you'd like this written from? How technical should it be?

I was thinking pretty non-technical. Basically, something like "you can drag and drop files or use the icon to select files to upload. Here are the supported file types: ...  Note that no data will actually be put online when uploading files".

Closed via #244 and #243


Two factor authentication ignores devise registration edit and update

If the two-factor authentication is turned on, the user can still navigate to the edit registration path and update the information.

Thanks for your report, could you please provide some example?

Example:
If the devise model is "user", once logged in you are presented with the two-factor authentication wall to enter the code. From here you can navigate to "users/edit" and since this is a devise controller the gem skips code validation.
Once in the edit view you can edit the user information without being authorized with the code.
Ps. Great gem!

@mesbahmilad This can be solved by overriding the Devise RegistrationsController in your app (or any other controller where you want to enforce 2FA), and adding a before_action, such as:
before_action :confirm_two_factor_authenticated, except: [:new, :create, :cancel]

def confirm_two_factor_authenticated
  return if is_fully_authenticated?

  flash[:error] = t('devise.errors.messages.user_not_authenticated')
  redirect_to user_two_factor_authentication_url
end

This is a pretty huge security flaw. You can sign in without 2FA, go to the edit page and disable 2FA from there. I'd recommend adding a note in the README at least.

This note should definitely be added to the readme, as a post-setup installation note. Can the gem be secured internally, though?

I made a PR, here:
https://github.com/Houdini/two_factor_authentication/pull/160
I'm not sure why it failed travis-CI, I only updated the readme...


Not possible to modify vertical dimension of equation with resizebox package

Description
So, I am trying to write some long equations, but I want them to be on one line. So I resorted to the resizebox package, normally one can specify the width and height of the said equation. In my case I had no problem with the width, but the height seems to be unmodifiable. The following example consists of 5 equations, some are longer than others. I want them to be all with the same height so I modified each one differently (especially the middle 3). But their height seems to be linked to the width as if I have specified the height to be {i} which adjusts it automatically.
Any idea what the reason can be?
Thanks a bunch for the quality work you do here btw.
Minimal Working Example

\documentclass{kaobook}
\usepackage[english]{babel}
\usepackage{blindtext}
\usepackage{kaobiblio}
\usepackage{kaotheorems}
\usepackage{kaorefs}
\usepackage{amsmath}
\usepackage[makeroom]{cancel}
\begin{document}

\title{Bug Report}
\author{Author}
\date{\today}

\frontmatter
\maketitle
\mainmatter
\setchapterstyle{kao}

\chapter{First Chapter}

\begin{align*}
\ddot{\theta} & = -\frac{mgl\sin\theta + ml\cos\theta\frac{\left(I+ml^2\right)\left(u - b\dot x\right) + ml\sin\theta\left[\left(I+ml^2\right)\dot\theta^2 + mlg\cos\theta\right]}{\left(I+ml^2\right)\left(M+m\right) - m^2l^2\cos^2 \!\theta}}{I+ml^2}\\
&= \frac{ml\cos\theta\frac{\left(I+ml^2\right)\left(u - b\dot x\right) + ml\sin\theta\left[\left(I+ml^2\right)\dot\theta^2 + mlg\cos\theta\right]}{m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)} - mgl\sin\theta}{I+ml^2}\\
&= \resizebox{\linewidth}{1.3\height}{$\frac{ml\cos\theta}{I+ml^2}\cdot\frac{\left(I+ml^2\right)\left(u - b\dot x\right) + ml\sin\theta\left[\left(I+ml^2\right)\dot\theta^2 + mlg\cos\theta\right]}{m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)} - \frac{mgl\sin\theta}{I+ml^2}$}\\
&= \resizebox{\linewidth}{1.7\height}{$\frac{ml\cos\theta}{I+ml^2}\cdot\frac{\left(I+ml^2\right)\left(u - b\dot x\right) + ml\sin\theta\left[\left(I+ml^2\right)\dot\theta^2 + mlg\cos\theta\right] + \left[\left(I+ml^2\right)\left(M+m\right) -m^2l^2\cos^2 \!\theta\right]mgl\sin\theta}{m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)}$}\\
&= \resizebox{\linewidth}{2\height}{$\frac{ml\cos\theta\left(I+ml^2\right)\left(u - b\dot x\right) + m^2l^2\cos\theta\sin\theta\left(I+ml^2\right)\dot\theta^2 + \cancel{m^3l^3g\cos^2 \! \theta\sin\theta} + \left(I+ml^2\right)\left(M+m\right)mgl\sin\theta -\cancel{m^3l^3\cos^2 \!\theta\sin\theta}}{\left(I+ml^2\right)\left[m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)\right]}$}\\
&= \frac{ml\cos\theta\left(u - b\dot x\right) + m^2l^2\dot\theta^2\cos\theta\sin\theta + \left(M+m\right)mgl\sin\theta}{m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)}\\
&= \frac{ml\left[\cos\theta\left(u - b\dot x\right) + ml\dot\theta^2\cos\theta\sin\theta + \left(M+m\right)g\sin\theta\right]}{m^2l^2\cos^2 \!\theta - \left(I+ml^2\right)\left(M+m\right)}\\
\end{align*}

\end{document}

Expected behavior:
Change in the height of each equation based on the coefficient with which the height is affected
Actual behavior:
Height is adjusted automatically, it is the same behavior as if the height argument is given as {i}.
Additional Information

Thanks. Does this happen also with the srcbook class, or just with kao?


PP-6353: Log payment transition to hosted graphite

We want to be able to detect anomalous drops in successful live authorisations.
It is envisaged that we can do this by noticing trends in authorisation errors
and successes. However it is currently hard to see this in the way we send data
to hosted graphite (HG). For example, currently we have to drill into
aggregates.production.connector.gateway-operations.worldpay.live.gatewa-account-id
(which is fine) then into authorise/authorise3ds,
without-billing-address/with-billing-address which makes it difficult to
graph the data we want. This PR sends the states a payment goes into which will
help us graph the trends more easily. This is similar to what we send to splunk.

What feedback do you need?
If manual testing is needed, give suggested testing steps.

Code review checklist
Logging

[ ] only emit log lines at ERROR level which require immediate attention from a support engineer. These will trigger a zendesk alert.

Documentation

[ ] Updated README.md for any of the following ?

Introduced any new environment variables / removed existing environment variable
Added new API / updated existing API definition

For reference

👍


chore(deps): update renovate/renovate docker tag to v35.58.0

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
35.48.2 -> 35.58.0

Release Notes

renovatebot/renovate
v35.58.0
Compare Source
Features

managers/asdf: Add poetry support in asdf manager (#21765) (454f259)

v35.57.4
Compare Source
Build System

deps: update dependency commander to v10.0.1 (#21743) (c2e7388)

v35.57.3
Compare Source
Bug Fixes

versioning/composer: compatible composer numeric soft (#21744) (ad0a2e1)

Code Refactoring

workers: Extract lookup stats helper (#21762) (888cbda)

v35.57.2
Compare Source
Bug Fixes

datasource/docker: omit empty service search key from auth url (#21755) (75ac52b)
manager/gradle: Filter false positives out of extracted deps (#21753) (6bd1277)
platform/azure: improve getPolicyConfigurations latency via mergePolicyGuid filter (#21723) (8d8c3d1)

v35.57.1
Compare Source
Bug Fixes

onboarding): Revert "feat(onboarding: use cache to check if repo is onboarded" (#21731) (b27ec63)

Miscellaneous Chores

deps: update github/codeql-action action to v2.3.0 (#21735) (4caa2bf)

v35.57.0
Compare Source
Features

implement bazel-module VersioningApi (#21606) (be08f1b)

Bug Fixes

fs: permit square brackets [] in file paths (#21625) (b853af2)

Miscellaneous Chores

update eslint config to allow direct reference of static class functions (#21632) (d6b5679)

v35.56.1
Compare Source
Bug Fixes

ansible-galaxy: handle git source (#21640) (bf0e39d)

Documentation

config options: rewrite forkProcessing (#21621) (6990f7f)

v35.56.0
Compare Source
Features

presets: deprecate npm-based presets (#21654) (6341703)

Miscellaneous Chores

deps: update dependency @types/lodash to v4.14.193 (#21641) (7de094a)
deps: update dependency @types/lodash to v4.14.194 (#21651) (f465f6f)

Build System

deps: update dependency @renovatebot/ruby-semver to v2.1.11 (#21650) (a94c0dc)

Code Refactoring

schema: Enhanced "loose" collections (#21541) (3fbdcdc)

v35.55.2
Compare Source
Bug Fixes

manager/git-submodule: use appropriate hostType for auth (#17400) (455de72)

Build System

deps: update opentelemetry-js monorepo (#21636) (205e227)

Miscellaneous Chores

deps: update codecov/codecov-action action to v3.1.3 (#21635) (7b3e01f)

v35.55.1
Compare Source
Bug Fixes

platform/github: Fix branch recreation for existing branches (#21629) (1adc077)

Continuous Integration

npm publish requires write permissions for id-token (#21612) (f61d49f)

Miscellaneous Chores

deps: update dependency @types/shelljs to v0.8.12 (#21613) (ac2dea0)

Documentation

remove outdated node/git minimum versions (62d051f)
self-hosted configuration: globalExtends can't be private (#21597) (c5ac66c)

Code Refactoring

date: Use Jest fake timers (#21631) (58fe0bd)

Tests

remove useless jest fake timer reset (#21633) (8e8e8a7)

v35.54.0
Compare Source
Features

presets: add vitest to jsUnitTest (#20389) (1637d13)

v35.53.1
Compare Source
Bug Fixes

sanitize special characters in URLs (#21575) (18d0fbc)

Code Refactoring

git: Rename fetchCommit to fetchBranch (#21581) (66d1ae9)

Documentation

constraints should work for all managers (#21593) (ecf7f40)
convert caution admonition to warning (#21600) (14dbd5e)
drop link to maven-cmp repository (#21601) (bd2dba0)
fix typo in regex versioning (#21579) (3d19f0a)

v35.53.0
Compare Source
Features

config: rename azureAutoApprove to autoApprove (#21576) (bce88c8)
manager/cargo: support private registry index env var (#20379) (2a72f85)

Documentation

fix broken relative link (#21572) (ce96324)

Miscellaneous Chores

managers/sbt: remove unused types (#21570) (7d6438b)

Code Refactoring

vulnerabilities: return interface for Vulnerabilities (#21310) (75a1ab0)

v35.52.0
Compare Source
Features

manager/gomod: add goGetDirs option (#20156) (91812d0)
support depth URL argument in Terragrunt modules (#21494) (288ad1f)

Build System

deps: update dependency semver to v7.5.0 (#21565) (e5fd6ce)

Documentation

contributing: update bug/feature request rules (#21551) (b00acdd)

v35.51.0
Compare Source
Features

versioning/regex: add revision as fifth capture group (#21555) (4fa199e)

v35.50.2
Compare Source
Miscellaneous Chores

deps: pin dependencies (#21557) (4487951)
deps: update devcontainers/ci action to v0.3.1900000329 (#21563) (a6a50b6)

Build System

deps: update dependency semver to v7.4.0 (#21564) (60ac8c7)

v35.50.1
Compare Source
Build System

deps: update aws-sdk-js-v3 monorepo (#21549) (07930b1)

Documentation

explain how to use presets (#21534) (e8c5fa6)

Miscellaneous Chores

devcontainer: Fixed errors and added CI workflow (#21515) (93e8bda)
devcontainer: unpin docker image (#21553) (2ac8f1b)

v35.50.0
Compare Source
Features

schema: Better utility for JSON parsing (#21536) (e9adc3d)

v35.49.0
Compare Source
Features

disable setting COMPOSER_AUTH for gitlab (#20634) (62b57aa)

Documentation

update references to renovate/renovate to v35.48.2 (#21542) (69740ba)

Miscellaneous Chores

deps: lock file maintenance (#21543) (e362474)
deps: lock file maintenance (#21544) (7a2376b)
deps: lock file maintenance (#21545) (2125ba2)
deps: lock file maintenance (#21546) (0ca8d8a)
deps: lock file maintenance (#21547) (5b4f7e9)

Code Refactoring

gradle/manager: introduce method to resolve variables (#21531) (94b42c5)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.4.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Initial graph visualization

Description
Created initial graph visualization using React sigma JS library and mock API. Added generate button. Since CORS is not yet supported, generate button will be enabled even if the upload is failed.
Related Backlog Item
Issue: #56

Context
We need to implement the graph visualization along with the generate button.

Checklist:

[x] I have documented my changes
[x] I have tested the changes and they work as expected
[x] I have assigned this PR to someone
[ ] I have run make format to format my code

Additional references

@Sandeep-kumar-Ramesh should i merge it or do you want to do it?


Tab completion type inference does not account for generic method invocation with explicit type parameters

Steps to reproduce
TabExpansion2 -inputScript ($s = '[array]::Empty[int]().') -cursorColumn $s.Length |
    % CompletionMatches |
    select -f 5

Expected behavior
CompletionText ListItemText   ResultType ToolTip
-------------- ------------   ---------- -------
Count          Count            Property int Count { get; }
IsFixedSize    IsFixedSize      Property bool IsFixedSize { get; }
IsReadOnly     IsReadOnly       Property bool IsReadOnly { get; }
IsSynchronized IsSynchronized   Property bool IsSynchronized { get; }
Length         Length           Property int Length { get; }

Actual behavior
No results

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.3.0-preview.2
PSEdition                      Core
GitCommitId                    7.3.0-preview.2
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

/cc @MartinGC94 if you have an interest.

I'm working on this now, I've gotten it to work with the example in the OP but I'm having some trouble getting it to work with this example:
[System.Collections.Generic.List[int]]$list = @( 1, 2, 3, 4, 5 )
$result = [System.Linq.Enumerable]::Select[int, float](
    $list,
    [Func[int, float]]{
        param($item)
        [math]::Pow($item, 3)
    }
)
$result.<Tab>

The type inference sees it as an:
System.Collections.Generic.IEnumerable`1[[System.Single, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]

while the actual type after running it is:
System.Linq.Enumerable+SelectListIterator`2[[System.Int32, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Single, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]

I've just updated the method here: https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/parser/TypeInferenceVisitor.cs#L1702 to also have a parameter for the generic type arguments and then I simply run this: var returnType = methodInfo.MakeGenericMethod(genericTypes).ReturnType; to get the return type.
What am I missing here?

Type inference is seeing the static type definition -- see https://docs.microsoft.com/en-us/dotnet/api/system.linq.enumerable.select?view=net-6.0
It's declared as the IEnumerable type. The runtime (concrete) type that you see after actually running it is just some probably internally-visible-only type that implements that IEnumerable interface. Probably not quite as important as it might change between .NET versions anyway, and it's not likely that folks will be expecting to see any methods specifically from that type. Even in C# you only deal with it as the IEnumerable, the underlying types tend to be a bit opaque.

Yeah unfortunately that seems like just another bug. Ideally it'd give you members for float but this also returns very little:
([System.Collections.Generic.IEnumerable[float]]$null).<tab>

So your change works! And there's more work to be done separately 😁

Yeah I suspect there's something to be added there for checking the element type of the IEnumerable and giving those members back.

If I had to guess, I'd say we're probably looking for IEnumerable<> in interfaces of the inferred type, but not checking if the inferred type itself is IEnumerable<>.


Communication: Allow author of the message to remove link preview

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[ ] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[ ] I chose a title conforming to the naming conventions for pull requests.

Server

[ ] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[ ] I followed the coding and design guidelines.
[ ] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[ ] I documented the Java code using JavaDoc style.

Client

[ ] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[ ] I followed the coding and design guidelines.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[ ] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

In #6616
Description

Steps for Testing

Prerequisites:

1 Instructor
2 Students
1 Programming Exercise with Complaints enabled

Log in to Artemis
Navigate to Course Administration
...

Exam Mode Testing

Prerequisites:

1 Instructor
2 Students
1 Exam with a Programming Exercise

Log in to Artemis
Participate in the exam as a student
Make sure that the UI of the programming exercise in the exam mode stays unchanged. You can use the exam mode documentation as reference.
...

Review Progress

Performance Review

[ ] I confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Codecov Report

Merging #6760 (4891a94) into feature/link-preview (8f851c1) will increase coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@                   Coverage Diff                   @@
##             feature/link-preview    #6760   +/-   ##
=======================================================
  Coverage                   84.94%   84.94%
- Complexity                  14018    14019    +1
=======================================================
  Files                        1164     1164
  Lines                       45197    45197
  Branches                     4660     4660
=======================================================
+ Hits                        38391    38392    +1
  Misses                       4275     4275
+ Partials                     2531     2530    -1

see 1 file with indirect coverage changes

Flag
Coverage Δ

server
84.94% <ø> (+<0.01%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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

But since regular users are unlikely to add a backslash before a link, I approve.

Thanks for noticing this. I would merge this PR first, then edge cases could be addressed in separate PR.

In the communication tab, the button is only partially visible.

Hi, thanks for noting this i clearly missed this 👍 . I managed to fix this by tweaking the css, can you test again and see how it looks now?


Renaming file rewrite PDF doc

When I use method save() or output() and download the PDF document, content is overdrawed.
If I do not rename file when saving PDF the file's content it's fine.
I have an example:
doc.setFontSize(8); doc.text("El presente certificado queda INVALIDADO en caso de efectuar Reparaciones, Ajustes o Reemplazo de partes. \n En tal caso, el instrumento deberá ser recalibrado previo al uso.",105,5, {align:"center"}); doc.save("certificate.pdf");
Then I want to rename file when saving but I have this problem.

That's a really odd behavior. Which browser are you using?

I'm using Chrome

Cannot reproduce. Please provide a jsFiddle or similar and the exact steps to reproduce this issue. I'm pretty sure this is not an issue in jsPDF.

Of course, here is my example. Sometimes rewrites making bold text.
https://jsfiddle.net/opftk6g3/2/

The issue is not the renaming of the PDF but the fact that you press the "Generate PDF" button twice. In your code you use the same jsPDF instance for each button press, each time appending the same line of text to the document. The text is not bold but just rendered twice. To fix this, just create a new jsPDF document for each button press.

Thanks! It works now. My mistake!


Unbreakable Potion Charms are unobtainable?

It is written clearly in the Chronicle of Shadows that unbreakable charms can be obtained with fusion crafting in the enchantment table, but there are no resources online or in the book as to how to receive the enchantment. Still, experimenting with shelf combinations make getting infusion on hellshelves and seashelves easy enough, but I have yet to be able to figure out how to receive infusion on a potion charm.
Is this a bug? Are unbreakable charms purposefully disabled, and the book needs an update? Or am I simply not doing it right?
I have an enchantment table with maxed-out eterna, quanta, rectification and arcana, and still infusion only pops up for shelves, and not potion charms.

In our modpack, REI does not show recipes for infusion. For the hellshelf for example, REI only shows tabs for the item's tag and the block drop--no enchantment table recipe. Is this a bug?

That's strange, I'm in a test world right now and the infusion recipes are displaying correctly.

This is what the item's recipes look like from my end.
Also, here is a setup I have for the enchanting table, and still no infusion. (50E, 5Q, 91.5A)


feat: add web search

Description
Search web for information.
When agent ask a question, google search can provide a list of urls which relative with the question, then using requests to get
each url and extract text. Split the text to small chunks and feed to chatgpt to get answer.
Notice: these functions require google api key you can find here https://developers.google.com/custom-search/v1/overview,
and search engine id you can find here https://cse.google.com/cse/all.
Motivation and Context
Why is this change required? What problem does it solve?
Give the agent ability to search internet.

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

The functionality is overall good. But there exists a vital problem that this should not be a version that can be publically merged because you use your own Google Key in the example... (you definitely do not hope all the public users use your api key, do you?) A good idea to make these be input via environment variables, but I think you definitely should talk with team members such as Guohao @lightaime first to have our team's API key beforehand and embed it into the Github workflow as secret variables just as the OpenAI key. (I guess these depend on whether our team approves to support this and buy a Google API key).
And I guess you need to get a new key now because even the commits here are publically available, which can be potentially abused by others.

The functionality is overall good. But there exists a vital problem that this should not be a version that can be publically merged because you use your own Google Key in the example... (you definitely do not hope all the public users use your api key, do you?) A good idea to make these be input via environment variables, but I think you definitely should talk with team members such as Guohao @lightaime first to have our team's API key beforehand and embed it into the Github workflow as secret variables just as the OpenAI key. (I guess these depend on whether our team approves to support this and buy a Google API key). And I guess you need to get a new key now because even the commits here are publically available, which can be potentially abused by others.

Thank you for your concern, but don't worry, this google api key is free, and only 100 times search every day.

Do you mind my directly modifying the code and submitting commits in this branch for collaboration? @zhiyu-01

Ok, i also think it need to be improved.

In my test, the texts extract from website sometimes may have a huge amount, 10k+ or even more. I have set a limit length 3000 to cut texts, if that's still smaller than your thought, we can change it.  And we can't guarantee the first website will give us enough information, so i think we do need an angent to decide  whether to continue search or not. @HalberdOfPineapple

Looks good now. Please share the code coverage report. See this page on how to generate it: https://github.com/camel-ai/camel/blob/master/CONTRIBUTING.md#coverage-

Is this OK?

Looks good now. Please share the code coverage report. See this page on how to generate it: https://github.com/camel-ai/camel/blob/master/CONTRIBUTING.md#coverage-

 Is this OK?

Good that the test are covered. But what about your new code? :)
camel/functions/web_search.py

@Obs01ete  What about this?

@Obs01ete What about this?

Your file is called camel/functions/web_search.py, I do not see it. Please attache a zip with the coverage report.

@Obs01ete What about this?

Your file is called camel/functions/web_search.py, I do not see it. Please attache a zip with the coverage report.

htmlcov.zip
Sorry, I am trying to get familiar with this.

@Obs01ete What about this?

Your file is called camel/functions/web_search.py, I do not see it. Please attache a zip with the coverage report.

htmlcov.zip Sorry, I am trying to get familiar with this.

Seems that you forgot to pip install -e . after adding files. Also see the coverage is basically zero. Your functions are not called for whatever reason.

@Obs01ete Check this, it looks better.

@Obs01ete Check this, it looks better.

Indeed better. But why not 100%? Pls attach the zip.

@Obs01ete Check this, it looks better.

Indeed better. But why not 100%? Pls attach the zip.

htmlcov.zip
It might be my open ai key expired.

@Obs01ete Check this, it looks better.

Indeed better. But why not 100%? Pls attach the zip.

htmlcov.zip It might be my open ai key expired.

Please analyze the coverage for camel\functions\web_search.py. Why a good half of a function is not called? Exited with exception.

@lightaime We need people responsible for their code to check the coverage and find out why each part of the code is not executed.

htmlcov.zip
log.txt
@Obs01ete

Okay. This is finally acceptable. Notice that you had a critical bug in your code but were oblivious about it without checking code coverage.
@lightaime this is a good case study.
Also in terms of communication please add short text explanation of what you did other in messages on in commit messages.

@HalberdOfPineapple Hi, I need you to approve the changes.

@Obs01ete Check this, it looks better.

Indeed better. But why not 100%? Pls attach the zip.

htmlcov.zip It might be my open ai key expired.

Please analyze the coverage for camel\functions\web_search.py. Why a good half of a function is not called? Exited with exception.

@lightaime We need people responsible for their code to check the coverage and find out why each part of the code is not executed.

We should add test coverage into workflow.

Sorry for my previous absence as I was busy with my personal stuffs (e.g. dealing with living stuffs when entering the new university)
The code now looks generally good but my concern is whether it really works. I have just pulled the new code and tested locally. Something weired happend when I ran examples/role_playing_with_function_call.py such that the two agents do not work correctly. Both of them were stuck in complaining as Ais they could not provide instructions and no progress could be made.
But this may not be completedly caused by your code and I suspect this is also related to any internal change in GPT-4 or OpenAI backends because when I removed the newly implemented functions from the search function list (only search_wiki was kept), the two agents could call correct functions and get the correct result but their collaboration seemed not normal. The user agent kept saying as an AI it could not provide instructions.
I have not dived into why this happened (I will do a little later) but I hope you could try running examples with your newly implemented functions and see what actually happened. If the code does works in your side, please kindly share any related screenshot to help us check the actual effect :)

@HalberdOfPineapple Congratulations on your new home.

I have modified this code which worked well in the past, but after the modify, the role_playing_with_function can work correctly.
Here is the output:
output.txt
I print the update_messages, and got this.

I runned an example ai_society\role_playing.py, it also print 'assistant' using the modified code.

but the original code will output just 'user', and work correctly.

We have two agent, one assistant, one user, it should specifies the role name when update messages, which we didn't
do that, and it still worked untill today. Should we open an issue to report this?
@lightaime

I have  reverted the task back, and reduced the nmber of results the search_google returned to 5. I quite like this function, I want to keep it.
@HalberdOfPineapple

@zhiyu-01 Well I don't mean search_google is not good, but it is more like an intermediate step of the method search_google_and_summarize. Even if you changed the number of available options to 5, the output of search_google is still quite long for each search while the essential "viewable" range for summarization shrinks.
What I mean is to only keep search_google_and_summarize in the availble list but remove search_google, in this way the output will not be too long and you can still have many available search results to be considered by the model for summarization.

@zhiyu-01 Well I don't mean search_google is not good, but it is more like an intermediate step of the method search_google_and_summarize. Even if you changed the number of available options to 5, the output of search_google is still quite long for each search while the essential "viewable" range for summarization shrinks. What I mean is to only keep search_google_and_summarize in the availble list but remove search_google, in this way the output will not be too long and you can still have many available search results to be considered by the model for summarization.

Alright, I have removed it, this shouldn't be a big problem.

I have runned a test for the sequence of roles, and fund more strange codes in role_playing.py:

An assistant messasge have given to user, and a user message to assistant, I don't know why this worked in the past, but I fund it in the intermediate output:

After the modify, I have runned several example files, they all worked correctly, but it may need more tests.
@Obs01ete

This pr has been reverted, and I opened an issue #298, you can see more detail in it.
@Obs01ete

I have changed the role at backend to match the message, this function is works well now.
@Obs01ete

@zhiyu-01 thank you for following the instructions! Please remind, did you send code coverage report for this PR? If not, please check CONTRIBUTING.md and attached zipped HTML folder.

htmlcov.zip
@Obs01ete Here is the coverage.

@lightaime I have some misunderstand about how camel works, thanks for @HalberdOfPineapple , I have understanded now. Sorry for the bother.

@HalberdOfPineapple Hi, you need to submmit an approve review, so I can merge this pr.

@zhiyu-01 Well after @Obs01ete or @lightaime approve this change you would be able to merge it. The write access is not controlled by me. And we are still discussing the implementation of web search.

@HalberdOfPineapple @lightaime approve pls


Markdown Text CSS style override my userstyle.css

This theme's CSS style overrides userstyle.css here:

Is it a intented feature or bug?

@ylc395 There are styles injected in the markdown editor also, so that might be the case. However, you can probably make the userstyle take precedence by increasing the specificity of your CSS selector.


[Question]: Inconsistent AI Response Lengths between Ragflow and Direct ollama Interactions

Describe your problem
Hello Ragflow team,
I am encountering an issue where the AI responses I receive when using ollama through Ragflow are significantly shorter and less detailed compared to when I interact directly with ollama.
Could you please help understand why there is such a discrepancy and how it might be resolved?

I'm encountering the same issue. Docker dev installed yesterday.  I increased output tokens to 2048 but that doesn't make any difference.
Tried with several ollama models (llama3, mistral-openorca, llama3-chatqa) with same truncated results.
Furthermore and related to this, RAGflow says that the Knowledge Base does not provide information, but it identifies the correct file and even the correct section as source for the response.

If it refers to correct chunks (you can test it in retrieval test) but the answer is still about nothing, it's probably caused by the LLM since its capability shortage to under stand the relevance between question and chunks.

Describe your problem
Hello Ragflow team,
I am encountering an issue where the AI responses I receive when using ollama through Ragflow are significantly shorter and less detailed compared to when I interact directly with ollama.
Could you please help understand why there is such a discrepancy and how it might be resolved?

What about disable max token toggle in dialog setting?

I disabled the "max token toggle" as mentioned and it worked. Thanks!

max token toggle

the images can't see now, where I can set the 'max token toggle'?

Describe your problem
Hello Ragflow team,
I am encountering an issue where the AI responses I receive when using ollama through Ragflow are significantly shorter and less detailed compared to when I interact directly with ollama.
Could you please help understand why there is such a discrepancy and how it might be resolved?

btw, did you running ollama in Macosx ?

max token toggle

the images can't see now, where I can set the 'max token toggle'?

Chat properties -> model settings -> toggle switch at bottom:

got it, thank u.

max token toggle

the images can't see now, where I can set the 'max token toggle'?

Chat properties -> model settings -> toggle switch at bottom:

does work！！

Yes, "Chat properties -> model settings -> toggle switch at bottom" helps! Thanks!


Pushing updated XLIFF translation files not working

When I update a pulled (via tx pull -l de,fr,es) XLIFF translation file locally and then push back the file via tx push -t, the translated strings do not appear in Transifex' editor and remain listed as "untranslated"

Never mind. My mistake – it is actually working!


Use validation_data properly

Hello all,
I'm experimenting with the Graph model and I think I'm not using the validation_data parameter properly.
This is the structure of my model where I'm trying to fit a time series using lags:
f_length = [2,3,4,5]
convs = []
model = Graph()
model.add_input(name='endog', input_shape=(len_ts_y,1))
for i in f_length:
    model.add_node(Convolution1D(nb_filter=nb_filter/2,
                                filter_length=i,
                                border_mode="full",
                                activation="relu",
                                subsample_length=1,
                                W_regularizer=l1(0.0001)
                                ),
                                name='conv_'+str(i), input='endog')
    model.add_node(MaxPooling1D(pool_length=pool_length),
               name="Max_pool"+str(i), input='conv_'+str(i))

for i in f_length:
    model.add_node(Convolution1D(nb_filter=nb_filter/2,
                                filter_length=i,
                                border_mode="full",
                                activation="relu",
                                subsample_length=1,
                                W_regularizer=l1(0.0001)
                                ),
                                name='conv_2'+str(i), input="Max_pool"+str(i))

    model.add_node(Flatten(), name="flat_"+str(i), input='conv_2'+str(i))
    convs.append("flat_"+str(i))

model.add_node(Dense(32, activation="sigmoid"), name="Dense_rec2", inputs=convs)
model.add_node(Dense(32, activation="sigmoid"), name="Dense_rec3", input='Dense_rec2')
model.add_node(Dense(1, activation="softplus"), name='last_dense', input='Dense_rec3')
model.add_output(name='output', input='last_dense')
model.compile(optimizer='adam', loss={'output':'mse'})

The shape of my data is:
endog_train.shape, y_train.shape
((182725, 60), (182725, 120))

And I tried with both validation_split and validation_data.
model.fit({'endog': endog_train[:-10000,:,None], 'output': y_train[:-10000,-1]},
          # validation_split=0.3,
          validation_data={'endog':endog_train[-10000:,:,None], 'output': y_train[-10000:,-1]},
          batch_size=batch_size,
          nb_epoch=nb_epoch+4)

When the model is evaluated on the test set I get this error:
Train on 172725 samples, validate on 10000 samples
Epoch 1/8
172544/172725 [============================>.] - ETA: 0s - loss: 0.0155
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-50-c0aba739c291> in <module>()
      3           validation_data={'endog':endog_train[-10000:,:,None], 'output': y_train[-10000:,-1]},
      4           batch_size=batch_size,
----> 5           nb_epoch=nb_epoch+4)

/media/thomas/data/libraries/keras/keras/models.pyc in fit(self, data, batch_size, nb_epoch, verbose, callbacks, validation_split, validation_data, shuffle, class_weight, sample_weight)
    680                             verbose=verbose, callbacks=callbacks,
    681                             val_f=val_f, val_ins=val_ins,
--> 682                             shuffle=shuffle, metrics=metrics)
    683         return history
    684

/media/thomas/data/libraries/keras/keras/models.pyc in _fit(self, f, ins, out_labels, batch_size, nb_epoch, verbose, callbacks, val_f, val_ins, shuffle, metrics)
    226                     if do_validation:
    227                         # replace with self._evaluate
--> 228                         val_outs = self._test_loop(val_f, val_ins, batch_size=batch_size, verbose=0)
    229                         if type(val_outs) != list:
    230                             val_outs = [val_outs]

/media/thomas/data/libraries/keras/keras/models.pyc in _test_loop(self, f, ins, batch_size, verbose)
    280         for batch_index, (batch_start, batch_end) in enumerate(batches):
    281             batch_ids = index_array[batch_start:batch_end]
--> 282             ins_batch = slice_X(ins, batch_ids)
    283
    284             batch_outs = f(*ins_batch)

/media/thomas/data/libraries/keras/keras/models.pyc in slice_X(X, start, stop)
     56             if hasattr(start, 'shape'):
     57                 start = start.tolist()
---> 58             return [x[start] for x in X]
     59         else:
     60             return [x[start:stop] for x in X]

IndexError: index 1 is out of bounds for axis 1 with size 1

Everything is working fine if I use validation_split.
Am I doing something wrong?
Thank you!

Is your version of Keras up-to-date with the repo?

Yes (commit 653ee91d35a215e231c4d1b0042983d9e3addcf0), to be sure I just pulled and ran the whole snippet in a new process and I still have the error.
Also, I'm not sure if it's right for the fit method of the graph model documentation:
-validation_data: tuple (X, y) to be used as held-out validation data. Will override validation_split.
Thank you!

Your usage of the API is correct. It might be a bug, but I cannot repro. Try using the same data as the training data for validation, to check that the problem is not with the data.

I just retried and it still have the issue with the same training and testing data.
I also used simulated data and I stil have the same problem:
from sklearn.feature_extraction.image import extract_patches_2d

sample = 100000
Fs = 8000
f = 5
x_bug = np.arange(sample)

y_test = np.sin(2 * np.pi * f * x_bug / Fs)
y_test = y_test+np.random.normal(0, 0.2, sample)

data_patched_2 = extract_patches_2d(y_test[:,None], (len_ts_x,1))
y_train = data_patched_2[:,:,-1]
endog_train = data_patched_2[:,-len_ts_y-1:-1,-1]

@fchollet and @tboquet  I had the same problem and i "solved" by using a custom callback but it is possibly a bug i did't dig into it

Likely to be a bug. Can you post a full code snippet (including fake data) for reproduction? I'll look into it.

Sure :
from sklearn.feature_extraction.image import extract_patches_2d
import theano
import keras

import numpy as np
np.random.seed(1337)

from keras.models import Graph
from keras.layers.core import Dense

len_ts_x = 120
len_ts_y = 60
sample = 100000
Fs = 8000
f = 5
x_bug = np.arange(sample)

y_test = np.sin(2 * np.pi * f * x_bug / Fs)
y_test = y_test+np.random.normal(0, 0.2, sample)

data_patched_2 = extract_patches_2d(y_test[:,None], (len_ts_x,1))
y_train = data_patched_2[:,:,-1]
endog_train = data_patched_2[:,-len_ts_y-1:-1,-1]

f_length = [2,3,4,5]
convs = []

model = Graph()
model.add_input(name='endog', input_shape=(len_ts_y,))
model.add_node(Dense(30, activation="tanh"), name='dense', input='endog')
model.add_node(Dense(1, activation="linear"), name='last_dense', input='dense')
model.add_output(name='output', input='last_dense')

model.compile(optimizer='adam', loss={'output':'mse'})

model.fit({'endog': endog_train[:-10000,:], 'output': y_train[:-10000,-1]},
          validation_data={'endog':endog_train[-10000:,:], 'output': y_train[-10000:,-1]},
          batch_size=128,
          nb_epoch=4)

Thank you!

Fixed. I could have sworn we fixed that bug months ago...


amazon linux 2023

adds dockerfiles for Amazon Linux 2023

Duplicates https://github.com/apple/swift-docker/pull/367?

that PR does not build the toolchain for Amazon Linux 2023, it just installs an Amazon Linux 2022 toolchain in an Amazon Linux 2023 image.

@etcwilde, now that you got AL2023 into the CI, any plans to distribute toolchains like this?


BUG: Releases in non-default namespaces not always visible

I noticed that some but not all pods from releases installed in a namespace other than "default" do not show up in Capacitor.
It turns out that if a release is installed a non-default namespace Capacitor would incorrectly detect the corresponding artifacts as belonging to the "default" namespace unless the chart templates explicitly set the "metadata.namespace" attribtue even though that is not required.
Installing the "podinfo" chart in a non-default namespace is a good way to reproduce this.

I was able to reproduce this issue. Seems like the Helm client sets the namespace to the namespace that is set in kubecontext. This has tricked me many times before, not sure why it works like that.
But, your code, your repro case everything was amazing. Thank you so much for taking the time.
Merging.


Remove TODO that is already TODONE

https://github.com/google/elemental2/commit/a89a855e1a8470cd5076646a2bba3dc7bd4f0649


zathura - epub plugin doesn't seem to be loaded/handling epub files

Describe the bug
The zathura package definition, per my understanding, shows that epub-supporting plugins are installed by default.
I am trying to load and display/read epub files since it's my main document format, but zathura only loads (and fails) them as PDFs.
Steps To Reproduce
Steps to reproduce the behavior:

install zathura from nixos 22.11 package index
run zathura ./file.epub

Expected behavior
zathura opens the document without complaining and works out of the box.
Screenshots
zathura Dans\ La\ Peau\ D\'Un\ Chien\ -\ Alexandra\ Horowitz.epub
error: cannot recognize version marker
warning: trying to repair broken xref
warning: repairing PDF document
warning: name is too long
warning: ... repeated 6 times...
error: invalid key in dict
warning: name is too long
warning: ... repeated 4 times...
error: invalid key in dict
warning: name is too long
warning: ... repeated 5 times...
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
warning: name is too long
warning: ... repeated 2 times...
error: invalid key in dict
warning: name is too long
error: invalid key in dict
warning: name is too long
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
error: invalid key in dict
warning: name is too long
error: invalid key in dict
warning: name is too long
error: no objects found
error: could not open document

Additional context
I installed zathura using home-manager, with home-manager configured to inherit the nixos configuraiton.nix nixpkgs block.
Notify maintainers
cc @grwlf @globin  @TethysSvensson
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 5.15.85, NixOS, 22.11 (Raccoon), 22.11.1137.dac57a4eccf`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"home-manager-22.11.tar.gz, nixos-22.11, nixos-unstable"`
 - channels(nyx): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

The zathura I get with nix run github:nixos/nixpkgs/nixos-22.11#zathura seems to open epub files file.
This is very much a guess, but can you try adding this to your configuration.nix?
  environment.systemPackages = [ pkgs.shared-mime-info ];
  environment.pathsToLink = [
    "/share/mime"
  ];

If the issue is zathura's filetype detection, this might fix it.

I forgot to retry the issue before trying this fix, but since I didn't do anything new with my laptop after this bug report, and since trying this change makes zathura behave as expected with epub files, I'll consider it fixed.
Thanks a lot!


Add Dive into Ansible Extension

Please add it under Infrastructure category.
https://github.com/spurin/diveintoansible-extension

Thanks!  See the following pull requests:
https://github.com/collabnix/docker-community-extensions/pull/2
https://github.com/collabnix/docker-community-extensions/pull/3


Request: Support Cisco Meeting Management (CMM)

Hi,
I would like to suggest supporting Cisco's CMM as a syslog source. The system supports UDP/TCP/TLS.
This is the management system for one of the more prevalent video conferencing solutions (CMS).
I don't have a syslog example available yet.

There are two types of CMM syslogs: Audit and System logs. Each can be configured to different destinations and ports.
Here are examples of audit logs:
<134>Feb 20 18:52:05 mycmmserver 2022-02-20  18:52:05,141 - local:myuser/HTTP/IPv3:<IP_ADDRESS>:tcp:50000 - Logged in

<134>Feb 20 18:52:22 mycmmserver 2022-02-20  18:52:22,150 - local:myuser/HTTP/IPv3:<IP_ADDRESS>:tcp:50010 - Applied configuration modifications:#012    Configuration path ["time", "ntp_servers", 1] unset

<134>Feb 20 18:52:22 mycmmserver 2022-02-20  18:52:22,250 - local:myuser/HTTP/IPv3:<IP_ADDRESS>:tcp:50010 - Update configuration successful

Here are examples of system logs:
<11>Feb 20 18:54:00 mycmmserver cmm-web_smart_agent_1[273]:  INFO 2022-02-20T18:53:05.123456Z SUCCESS | initializing smart agent v1.2.5 | sapy.manage:19

<14>Feb 20 18:54:08 mycmmserver cmm-web_proxy_1[273]:  Web is available - starting

<11>Feb 20 18:54:16 mycmmserver cmm-web_events_monitor_1[273]:  2022-02-20 18:54:16,460 - INFO - 154:123456789012345 - /home/unprivuser/cmm/cmm_meetings/management/commands/run_events_handler.py:38 - Handler for mycmsserver01 (2) started

<11>Feb 20 18:54:16 mycmmserver cmm-web_events_monitor_1[273]:  2022-02-20 18:54:16,600 - INFO - 155:123456789012345 - /home/unprivuser/cmm/cmm_meetings/consumers.py:523 - Websocket for server mycmsserver02 (3) opened

<11>Feb 20 18:54:16 mycmmserver cmm-web_events_monitor_1[273]:  2022-02-20 18:54:16,630 - INFO - 154:123456789012345 - /home/unprivuser/cmm/cmm_meetings/consumers.py:523 - Websocket for server mycmsserver01 (2) opened

looks good will get this on the queue

I suggest cisco:cmm:system and cisco:cmm:audit for the source types I suspect we can make both a soup parser so no need to manage ports

:tada: This issue has been resolved in version 2.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


export types?

Hi, I was wondering if you could export types from this library? I definitely appreciate the types that come out-of-the-box, but for the use case of wrapping additional business logic around these hooks, importable react-native-navigation-hooks types would make my life easier. Thank you!

Sure! I'll include this in the next release
Thank you for the feedback!


Cargo feature migrations

Extend Cargo to allow some limited forms of migrations of feature sets to be expressed.
This will allow new features to be added that make existing functionality optional without causing needless breakage.
Rendered

I have a different suggestion:

Allow defining a feature that is always on, even when used with default-features = false. Admittedly, this makes default-features = false a bit weird, but I think default-features is problematic anyway and it can be obsoleted and ignored. Hence the second point:

Add syntax to explicitly exclude feature from defaults, e.g. features = ["ignore:foo"] or features = ["~foo"] or no-default-features = ["foo"]. This is distinct from disabling features which can't be done in Cargo. It's simply an equivalent of removing a named feature from this dep's default features.

This solves the problem with default-features = false removing future features users haven't heard of.
If a dep has [features] default = ["foo"], then user can disable it with no-default-features = ["foo"], and when dep changes to [features] default = ["foo", "bar"], then no-default-features = ["foo"] still does what it did previously. New users can change it to no-default-features = ["foo", "bar"] to explicitly say what they don't want.

@kornelski I have tried to address the opt-out approach, and why I considered but rejected it, in the alternative section. I also agree default-features = false bad and proposed (optionally) deprecating it.

I don't see default-features = false being deprecated, especially given the fact that there are a fair number of crates using features in a non-additive way in the first place, and a subset of them specifying one of the mutually exclusive features as a default feature.

I've gotten into a habit of checking, and disabling all default features in my libraries. As the RFC says:

The key thing aspect about features to realize is that the ultimate reason they are used is not to control a crate's interface (exports), but its dependencies (imports).

I don't want to be on the hook for unknowingly enabling some feature and therefore a dependency that some binary down the line could avoid.
What this RFC proposes would effectively force downstream libraries to be maintained and updated every time a crate it depends on adds a feature.
I do want to also nit here that I've seen a fair share of crates attempting to vary their API using features. A most prominent example that comes to mind is a choice of the TLS implementation used by default (which tends to leak into the public API with e.g. hyper).

I do think @kornelski's proposed direction is better than the proposal in this RFC. IMO the proposed RFC adds a lot of complexity. Responding to the alternatives section from the RFC:

First of all, this complicates the "additive" features mental model. We've worked very hard to teach people how features are additive: it should always be safe to add more features. We can't give that up across-the-board without destroying feature resolution, so it's important that "without necessarily features x or y" doesn't mean the crate will for sure not get x or y, but just that they are not requesting them. I worry this will be very subtle and hard to teach.

That's not a change from the status quo. Obviously this part is a trade-off, but renegotiating the idea of additivity seems pretty fundamental and likely out of scope for whatever is used to solve the present use case.

Second of all, there is an especially unintuitive case of the former where a non-opted-out default feature depends on an opted-out feature. Consider this example:
Consumer depends on "default features without foo".
bar is another default
bar depends on foo.
In this case, the not-mentioned feature still drags in the opted-out feature. This might happen because the user simply forgot to include both features. It might also happen because the problematic bar -> foo dependency only exists in a newer version, and not the one the user was using when they wrote the dependency spec. Finally, it might be that that bar itself, and thus necessarily also the bar -> foo dependency, is newer than the dependency spec. In any case, the result is that all build plans using a problematic version of the package have the explicitly opted-out feature foo, which is liable to confuse the user even more.

This works as designed. If after an update there are new dependencies. This is also not much different from today: if I disable the default features from my dependency but re-enable foo, that might pull in bar in the new release.

One might think there is a fix making the out-out a hard rejection, so such that no plan is allowed to have those features. But that creates other problems, namely that those same sneaky new deps would rule out all plans causing solving to fail. Moreover, this sort of "negative reasoning" undermines the entire "additive" comparability story Cargo features are supposed to have. This will make the overall Cargo solving brittle, and also make it impossible to express the situation where one is in fact, agnostic to whether some unneeded feature is enabled for some other consumer's sake.1

I do think a solution to this problem that might improve related issues is to have some configuration for forcibly opting out of features at the binary level rather than the library level, provided a way to configure this at the workspace level is included as well (for scalability).

Finally, and is a matter of taste, I find writing down features that I don't need poor UX. We say "pay for what you use" in Rust, but writing down features that we, by definition, don't care about means cluttering our minds and Cargo.tomls. I would only want to propose negative reasoning as an absolute last resort.

On the other hand, today we have to exhaustively write down features that are enabled by default if we want to disable only one of the features that are enabled by default, which is also cluttering our minds and Cargo.tomls. IMO it clutters my mind more because I now will have to keep track over time if I haven't missed features which ought to be enabled by default but which I by accident disabled because I wanted to disable some other things.

1: N.B. I do think is useful to be able assert some features aren't enabled. but I that such "global reasoning" should just be allowed in the workspace root, and not dependency crates, for sake of modularity / compositionality.

Hi, I have literally zero experience in this area, but I did have an idea I wanted to explore as I was following along reading these threads. If this doesn't contribute to the discussion or completely misses the mark, please feel free to mark off topic. I don't want to disrupt the thread. I had to lookup the cargo book to even know what the current syntax for features was. :)
Idea
Have default features become versioned by a simple incrementing number, and have downstream opt out of defaults using that version number. Any time a new feature is added that gates pre-existing functionality, the defaults version number would increment (like a semver bump). The "negative" feature would be marked to indicate that it is such, along with the version where it was introduced. Purely additive features would be added to the existing default features sets without a version bump.
With this information, pre-existing functionality can be put behind a feature gate and then enabled by default, without breaking pre-existing crates that had opted out of default features. In this case, the pre-existing crate will get the new negative feature that is on by default without explicitly requesting it, thus preserving backwards compatibility. Any new additive features that are enabled by default would not be picked up by a pre-existing crate that had opted out of defaults.
This works by having downstream crates that opted out of default features still implicitly enable negative features from a higher versioned defaults set. So opting out of default features at "v0" will still bring in any later negative features that were added at "v1", "v2", etc.
This doesn't enable anything fancy or try to improve default features generally, it's just doing the bare minimum needed for negative features like this to be added backwards compatibly. "Negative" feature is a bit of a misnomer too because they still behave like normal additive features, but I wasn't sure what to call them. They're just features that would be breaking changes to introduce.
Purely mock-up not-actually-valid syntax
Default features versioned sets:

default = ["ico", "webp"]
default_1 = ["ico", "webp", "negative_feature1"]
default_1 = ["ico", "webp", "negative_feature1", "additive_feature2"]
default_2 = ["ico", "webp", "negative_feature1", "additive_feature2", "negative_feature3"]

Opting out of default features:

default-features = false
default-features-1 = false
default-features-2 = false

Identifying features as gating pre-existing functionality:

[features]
negative_feature1 = []
negative_feature1_negative_default_at = 1
additive_feature2 = []
negative_feature3 = []
negative_feature3_negative_default_at = 2

Scenario 1: An upstream crate wants to gate pre-existing functionality behind a new feature flag: "negative_feature1". We're on status quo Rust upstream and downstream, so we'll call our defaults version 0.

Upstream: Bump the defaults version to 1 by creating a new "default_1" set with the new feature enabled. Mark the feature as being a negative feature introduced at version 1 with a "negative_feature1_negative_default_at = 1" entry.

Downstream, normal defaults: There's been no opt out of default features, so just use the latest default set: "default_1".

Downstream, opted-out defaults: Because downstream has "default-features = false" it will only get the features it requested. But in addition it will now also get any negative features from future versions, in this case "negative_feature1" from "default_1". The downstream crate may in fact not need this feature, but including the feature ensures backwards compatibility is preserved. The new feature can then be explicitly opted out of, if desired.

Downstream, opted-out defaults and wants to opt out of new feature: If downstream doesn't actually require the pre-existing functionality that is being gated, it can now upgrade to disable the new feature. Change "default-features = false" to "default-features-1 = false" and now "negative_feature1" will no longer be implicitly enabled as it is no longer from a higher version. This is an optional step that only needs to be done if downstream wants to take advantage of a new "slimming down" capability that didn't exist before.

Scenario 2: An upstream crate wants to gate new functionality behind a new feature flag that's enabled by default.
In this scenario nothing about the status quo changes. Add the new feature to the existing default features sets without bumping the version number. Any downstream crates that didn't opt out of defaults will pick it up, and any downstream crates that did opt out of defaults won't pick it up. Because it's a purely additive feature, downstream won't break if it doesn't pick it up.

@nagisa

I don't see default-features = false being deprecated...

That's fine, it's a purely optional step.

I've gotten into a habit of checking, and disabling all default features in my libraries.

Woo! I like to hear that :).

I do want to also nit here that I've seen a fair share of crates attempting to vary their API using features. A most prominent example that comes to mind is a choice of the TLS implementation used by default (which tends to leak into the public API with e.g. hyper).

I will revise the motivation a bit. The latter bits were focusing more on that second case of why to use features, and not trying to make blanket statements about how they are used in all cases.
In this specific one,

I don't want to be on the hook for unknowingly enabling some feature and therefore a dependency that some binary down the line could avoid.
What this RFC proposes would effectively force downstream libraries to be maintained and updated every time a crate it depends on adds a feature.

I don't understand this? This is definitely not my intent. Perhaps i have made some mistake.

Can we get a rigorous definition of "base version of the dependency spec"? What does that mean for all of the semver operators X leading zeros X prerelease versions?

Does it matter how the migrations from old versions change over time? E.g. how the migrations from 1.1 -> 1.2 -> 1.3 might not match the migrations from 1.1 -> 1.3 directly?

As the person that understands Cargos dependency resolver the best, I am not shore. And this needs to be thought about very carefully. The fact that different versions can have different requirements is what makes Dependency resolution NP-Complete. This may make the problem O( numbers of packages considered ) harder to solve and explain, or it may be a surface level problem that has no theoretical impact. I will think about it.

Public and private dependencies

are all challenging problems that are amendable to this sort of analysis. ... that there is some sort of holistic approach for both deciding on a fundamental level what we want from Cargo

The problem with "Public and private dependencies" is not the thery. It is fairly clear what we want it to mean. It is implementation that is the problem. In a SAT/SMT reduction of Dependency resolution it adds O( (numbers of packages considered) ^ 2) terms to the problem. More importantly in the Resolver as implemented it takes common use cases from sub second time to multiple hours time. There are a lot of changes to the Resolver that we can not stabilize because of limitations to performance or error messages even though we have a clear understanding of exactly what behavior we want and why.

@Eh2406

Can we get a rigorous definition of "base version of the dependency spec"? What does that mean for all of the semver operators X leading zeros X prerelease versions?

Good question! I do not know all the myriad types of version specifiers off hand. If you don't mind, I rather punt on these details until we've established whether we want to do anything like this at all. There is always an escape hatch of the user specifying a base version explicitly if it would be ambiguous (e.g. if there isn't a unique lowest pre-release version matched by the spec). Is that OK with you?

As the person that understands Cargos dependency resolver the best, I am not sure...I will think about it.

Thanks! I am very curious about this.

Good question! I do not know all the myriad types of version specifiers off hand.

The new Semver 1.0 crate makes this much easier to deal with! Here is the list of ops. Thanks to everything being pub in the new versions of Semver, we can make a fn base_version(req: &VersionReq) -> Version anyware we want. I think all the details will need to be documented at some point. But you are right, we can punt for now.

Does it matter how the migrations from old versions change over time? E.g. how the migrations from 1.1 -> 1.2 -> 1.3 might not match the migrations from 1.1 -> 1.3 directly? (Note that multi-step migrations might be possible if Cargo combines depenency specs to avoid duplicate crates / public dep violations mid-solving.) The "path dependency" of migrating different ways could make for unexpected behavior as the solver tries different versions.

Having taken a walk, I now think it is a surface level problem that has no theoretical impact. The thing I remembered is that we already need to do computation to figure out what the set of features from the Dependency object mean when looking at a particular package version (here), now the code needs to figure out what the features mean for this package version in light of the "base version".

Prior art

Do other package managers have a system like this? How do they deal with the stability hazards of moving code to opt in flags?

While we haven't written up and RFC yet, there are some of us interested in @kornelski idea.  For now, it is being discussed in https://github.com/rust-lang/cargo/issues/3126.

. If you don't mind, I rather punt on these details until we've established whether we want to do anything like this at all

For me, the RFC's ambiguity around versions vs version requirements and how "base versions" work makes it hard for me to give a clear answer.  My gut says that this RFC is a bad idea from my vague understanding of this RFC but I can't fully articulate the thought and make sure I'm responding to your idea instead of some other idea I created when trying to read this.
In case this can short-circuit some discussion, I'll share my thoughts based on my interpretation of the RFC:  I feel like this RFC is trying to make decisions of what is happening based on the user's version requirement based on rules in the package in the lockfile.
The most immediate concern I would have is that modifying a version requirement to a compatible version would be a breaking change because you are now missing the migrated features.  If we had cargo upgrade merged, then the RFC could say "apply the migration directly to the Cargo.toml on upgrade" but I don't think we should say "you have to use cargo upgrade to avoid breaking changes between compatible versions".  That leaves out hand edits, editor integration, Dependabot, etc.

@epage that's a fair point. Tightening bounds would have new unanticipated effects.

I'm going to close this as I have a new simpler idea I like better as a first step.

https://github.com/rust-lang/rfcs/pull/3347 Here's a new attempt on this problem


Add support for multi2vec-cohere

Closes https://github.com/weaviate/weaviate-python-client/issues/1383

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

Project coverage is 93.95%. Comparing base (2378385) to head (76cd752).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1390      +/-   ##
==========================================
- Coverage   93.97%   93.95%   -0.03%
==========================================
  Files         221      221
  Lines       21283    21300      +17
==========================================
+ Hits        20001    20012      +11
- Misses       1282     1288       +6

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

was validated by @databyjp  :)


fixed issue where gaze provider gets forcibly reset on profile modification

Overview
The way we were reinitializing profiles called into a systems Disable() function, causing side effects. In particular, for the gaze provider, it would aggressively remove and repopulate the gaze provider.
This PR changes that.
Changes

Fixes: #10485

/azp run


Persisting high-dimensional vectors in QdrantLocal

We have problems with persisting of high-dimensional vectors in QdrantLocal
If we try to save vectors with dimensionality >= 433, it fails (see traceback in the bottom)
We also don't properly close db in LocalCollection
I read some sources about dbm or shelve (shelve is a layer on top of dbm which provides interface to store values in any format) and there were written, that these modules work with fairly small values.
dbm docs (look for Warning in the bottom of the page)
shelve docs
blog (some guy also encountered NegativeSize exception)
Code snippet to reproduce:
import random
import numpy as np
import qdrant_client
import qdrant_client.http.models as rest

default_collection_name = "example"
qdrant_args = {"path": "qdrant"}

def ingest_data(vector_size=433):  # vector_size < 433: works, vector_size >= 433: crashes
    lines = [x for x in range(10)]
    embeddings = np.random.randn(len(lines), vector_size).tolist()
    client = qdrant_client.QdrantClient(**qdrant_args)
    client.recreate_collection(default_collection_name, vectors_config=rest.VectorParams(
                size=vector_size,
                distance=rest.Distance.COSINE,
            ),)
    client.upsert(
        collection_name=default_collection_name,
        points=rest.Batch.construct(
            ids=[random.randint(0, 100) for _ in range(len(lines))],
            vectors=embeddings,
        )
    )

if __name__ == '__main__':
    ingest_data()
    ingest_data()  # Crashes here. Here we have the second instance

Traceback
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/Users/qdrant/qdrant-local-issue/raw.py", line 29, in <module>
    ingest_data()
  File "/Users/qdrant/qdrant-local-issue/raw.py", line 13, in ingest_data
    client = qdrant_client.QdrantClient(**qdrant_args)
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/qdrant_client.py", line 80, in __init__
    self._client = QdrantLocal(location=path)
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/local/qdrant_local.py", line 39, in __init__
    self._load()
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/local/qdrant_local.py", line 55, in _load
    self.collections[collection_name] = LocalCollection(config, collection_path)
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/local/local_collection.py", line 48, in __init__
    self.load()
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/local/local_collection.py", line 53, in load
    for idx, point in enumerate(self.storage.load()):
  File "/Users/qdrant/qdrant-local-issue/venv/lib/python3.8/site-packages/qdrant_client/local/persistence.py", line 52, in load
    for key in self.storage.keys():

Thanks for opening this issue with a more narrow example on how to reproduce


Please cut a coq-8.15 branch

For now, commit 75127a67 seems to work (it's the parent of https://github.com/MetaCoq/metacoq/pull/621).

cc @aa755

Hi. I cloned the repo and switched to the coq-8.15 branch but it doesn't compile. It finishes the attempt at compilation with
make[1]: Entering directory '/home/user/code/coq/metacoq/pcuic'
make[1]: *** No rule to make target 'metacoq-config', needed by '_CoqProject'.  Stop.
make[1]: Leaving directory '/home/user/code/coq/metacoq/pcuic'
make: *** [Makefile:58: pcuic] Error 2

@rhz you were missing a ./configure.sh local


On click on chatcard in conversation, popup with options:

Create option for attachments sent to a chat

Probably important too: what happens the second time? Same action? Same dialog? Open in quatum -> same file is opened?


chrome crashes  when cesiumContainer width and height is 100% and the chrome's scroll bar is display

i use cesiumContainer with  width and height for 100% as container for Cesium,when the real width or height out of the screen width or height and the chorme's scroll bar displayed,the chrome is  crashed.

sorry,maybe is my pc os problem,i change orther pc to test and it is work fine

Thanks for confirming @skylning . If you're able to recreate this in an example you can share, feel free to open an issue for it. If you're unsure you can always ask on the Cesium forum (https://groups.google.com/forum/#!forum/cesium-dev).


CORE-8691: Delay Closing SandboxGroupContext

Do not automatically close sandboxes when evicted from the cache if
there are still references in use. Ported from commit 4316838 1.

I've been running the smokeTest locally against the combined worker (both with the default cache size and hard-coding it to 1 so entries are continuously evicted)  without issues so far.

Need to come up with something different, this approach won't work without causing memory leaks.


Added names for the apps from the letter "e"

Added names to 19 casks
Changed license for 8 casks
Added appcast's sha256 for 2 casks

@phinze Ahah, you made my day with these pics :laughing: Thanks :blush:


Possible to use macro_rules to expand methods prior to #[Object] attribute macro?

For my root-level query, I have a lot of repeated methods to expose various objects in my database externally. I use a macro_rules implementation named ent_query_fns to generate three async functions for each of the names I provide. Unfortunately, the attribute macro takes precedence over the macro_rules functions expanding, so none of the macro-generated methods get fed into your #[Object] attribute macro.
Is there any way to leverage macros to add functions to the async graphql object prior to the attribute macro being processed? Or is there another way to mark a struct as a graphql object where I could use macro_rules inside an impl first?

In this case, you can only let macro_rules generate the entire Object, not a part of the resolver.
Based on my experience, mixing procedural macros and macro_rules in Rust will encounter a lot of strange things, hope it helps you. 😁

I tried moving nathe object generation inside the macro thinking the same
thing, but no success :'(
Guess I'll just have to do it manually instead.
On Sun, Mar 28, 2021, 7:36 PM Sunli @.***> wrote:

In this case, you can only let macro_rules generate the entire Object,
not a part of the resolver.
Based on my experience, mixing procedural macros and macro_rules in Rust
will encounter a lot of strange things, hope it helps you. 😁
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/async-graphql/async-graphql/issues/454#issuecomment-808992611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS55CVCUXEI6Z5SK3HUVSTTF7DQFANCNFSM4Z5FSOVQ
.

I tried moving nathe object generation inside the macro thinking the same thing, but no success :'( Guess I'll just have to do it manually instead.
…
On Sun, Mar 28, 2021, 7:36 PM Sunli @.***> wrote: In this case, you can only let macro_rules generate the entire Object, not a part of the resolver. Based on my experience, mixing procedural macros and macro_rules in Rust will encounter a lot of strange things, hope it helps you. 😁 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#454 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAS55CVCUXEI6Z5SK3HUVSTTF7DQFANCNFSM4Z5FSOVQ .

I used macro_rules to implement a lot of code in the past, but I encountered some weird problems when including procedural macros, and eventually I had to implement them manually. 😂

Okay, closing out since this is more challenge with Rust than any specific library. :)


[FLINK-32407][table] Notify catalog modification listener for table ddl in CatalogManager

What is the purpose of the change
This PR aims to create event for table ddl and notify catalog modification listener in CatalogManager
Brief change log

Create event for table and temporal table
Notify listener in CatalogManager

Verifying this change
This change added tests and can be verified as follows:

Added CatalogManagerTest to validate listener for table/view ddl

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no) no
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no) no
The serializers: (yes / no / don't know) no
The runtime per-record code paths (performance sensitive): (yes / no / don't know) no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) no
The S3 file system connector: (yes / no / don't know) no

Documentation

Does this pull request introduce a new feature? (yes / no) no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi @PatrickRen @leonardBang Please help to review this PR when you're free, thanks

The CI failed because of a known issue FLINK-32632. All table test cases passed so I'll give a green light


Improve stacktrace for failed dependency loading

Originally posed by @OliverJAsh in https://github.com/systemjs/systemjs/issues/512:
This is what the errors looks like when a dependency fails to load:
Potentially unhandled rejection [3] Internal Server Error: <dependency>
	Error loading <dependency> from <requester>
	Error loading <dependency> (WARNING: non-Error used)

Sometimes dependency is a nested dependency of a dependency of requester, e.g. requester -> foo -> bar -> dependency. Is it possible to show the immediate requester (bar)?

Looking at an issue in systemjs/builder, I found that the right way to address that would be here. I think load objects would need to be extended to include their (first?) immediate requester, and their un-normalized requested name (i.e. "requested as") in order to report these errors usefully.
I've started (i.e. 15 minutes to fork, clone, write a failing test) work on a PR for this.

I think this can be done via some reflective lookups in the error handler itself to run a dependency trace just for the error message.

Thanks @nyarly for your work on this.

Released in 0.17.4.


The ASF Jenkins build hangs exhausting resources

Please check all your Jenkins CI builds because the one [1] hangs or is doing something 3 days.
It is not clear what it does because the logs [2] are so huge (96GB) that Jenkins does not want to show the tail.
[1]: https://builds.apache.org/job/Royale Pipeline/
[2]: https://builds.apache.org/job/Royale Pipeline/job/feature%252Fvivid-ui-set/2/console

Last build seemed to pass after removing the -X option.  Not sure if it was really that or not.  But there was a ton of output about downloading the huge Adobe AIR SDK so maybe having all of that extra debug output really did overwhelm resources.


chore: update config cache paths

Which problem is this PR solving?

Remove http2 path and add ioredis and resources package.

Codecov Report

Merging #826 into master will decrease coverage by 1.57%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #826      +/-   ##
==========================================
- Coverage   94.14%   92.56%   -1.58%
==========================================
  Files         248      228      -20
  Lines       10711     9998     -713
  Branches     1030      986      -44
==========================================
- Hits        10084     9255     -829
- Misses        627      743     +116

Impacted Files
Coverage Δ

...s/opentelemetry-core/test/context/B3Format.test.ts
50% <0%> (-50%)
:arrow_down:

packages/opentelemetry-core/test/utils/url.test.ts
50% <0%> (-50%)
:arrow_down:

...pentelemetry-core/test/internal/validators.test.ts
50% <0%> (-50%)
:arrow_down:

...elemetry-core/test/trace/spancontext-utils.test.ts
55.55% <0%> (-44.45%)
:arrow_down:

...lemetry-core/test/trace/ProbabilitySampler.test.ts
56.52% <0%> (-43.48%)
:arrow_down:

...s/opentelemetry-core/test/trace/tracestate.test.ts
65.06% <0%> (-34.94%)
:arrow_down:

...ntelemetry-core/test/trace/NoRecordingSpan.test.ts
71.42% <0%> (-28.58%)
:arrow_down:

...ackages/opentelemetry-core/src/platform/node/id.ts
71.42% <0%> (-28.58%)
:arrow_down:

...entelemetry-core/test/common/ConsoleLogger.test.ts
77.01% <0%> (-22.99%)
:arrow_down:

...ckages/opentelemetry-core/test/platform/id.test.ts
77.77% <0%> (-22.23%)
:arrow_down:

... and 57 more


Use Vagrant plugins

Hey,
This PR enables the project to make use of some Vagrant plugins that make things abit smoother to setup.

Vagrant Cachier - Caches downloaded packages. Speeds up re-provisioning and saves bandwidth.
Vagrant Hostsupdater - Automatically updates hosts file on vagrant up and vagrant destroy. Removes manual step to be taken by user.
Vagrant Librarian Puppet - Installs required puppet modules upon provisioning and automatically resolves module dependencies. Removes the need for submodules.

+1 - maintainers?

Actually @mike182uk does the Puppet 3 syntax (hasn't yet been updated to 4) lead to any breakage?

@cwonrails No breakages, everything works as it did before :smiley:

I keep trying to use our vagrant setup instead of having everything directly on my mac, and often seem to hit issues (yes, that's pretty vague). It already has quite a few setup steps, is installing plugins really better?
I ask this genuinely - does it give a better experience of vagrant or does it make it even harder to use?

@ErisDS Just responded in Slack. I recommend creating a new branch dedicated to a 4.0 and merging @mike182uk's PRs into that branch, which will hopefully encourage more collaborators going forward.
@mike182uk Thanks again for your work here!

ok cool, no worries.
To answer the question, I would say it makes the experience better. For one, there is no need to manually edit / update your hosts file (as this is handled by vagrant-hostsupdater). vagrant-librarian-puppet is better for managing puppet dependencies than just plain old git submodules, which is probably not going to have a massive effect on the end user. vagrant-cachier is a good general purpose plugin to have and will save bandwidth on multiple provisions. It will also benefit any other VM's the user has. My change only adds 1 new step, and removes another, so there is still the same amount of steps.

I completely agree. Can a maintainer please merge this PR? It's been a long time and it works. cc @ErisDS

Hi @mike182uk, @cwonrails, thanks for all your work here.
Big :+1: from me for getting rid of git submodules and using puppet modules instead.
Going forward I'll try to keep a closer eye on this repository and help to make the experience for using and contributing better :-).


Bots decrease over time

After starting my bots, they increase like normal, then when they stop increasing, they begin to slowly decrease. I could have 100 and then end with 20-30, and help or ideas to stop this decrease in bot numbers?

socks proxys?
socks proxys never last long really. try http ones they are better.

How do i use/get HTTP proxies? I have tried them before using #HTTP in the proxy.txt, but i always get errors and they never work, any ideas?

because you don't have a reconnect script bots .

@alezboyy  And how are we supposed to get that script?
@Rassyp Use good premium socks5 proxies.I had the same problem. A guy recommended me to use this site -  http://proxybag.blogspot.com/  .
My opinion about this site? - The proxies in this site are more working ones.
Hope that helps you.

@nfsboy101 I use proxies from that site, they are just as bad as you other free ones

@Rassyp Sorry to hear that. Try http://bulksocks5.blogspot.in/

Http no better in my opinion they still disconnect with bad packet errors over time.