'VAEEncode' has no attribute 'vae_encode_crop_pixels'

!!! Exception during processing !!!
Traceback (most recent call last):
File "H:\ComfyUI\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "H:\ComfyUI\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "H:\ComfyUI\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "H:\ComfyUI\ComfyUI\custom_nodes\ComfyUI-Advanced-ControlNet\adv_control\nodes_sparsectrl.py", line 157, in preprocess_images
image = VAEEncode.vae_encode_crop_pixels(image)
AttributeError: type object 'VAEEncode' has no attribute 'vae_encode_crop_pixels'

https://github.com/Kosinkadink/ComfyUI-AnimateDiff-Evolved/assets/35267721/b51b6e2c-3d89-4117-98fa-91533af5a362
here  is  the  workflow

Your Advanced-ControlNet is outdated relative to your ComfyUI version. Update your Advanced-ControlNet, and your problem will go away.


Possible To Use Existing Routes & Components?

Is there any way to configure the router so that if a route or component that has already been called is called again it re-uses the route/component rather than adding another to the stack?
Is there a way to search the stack to see if the same route is already in the stack and then return it to the top of the stack?
Is there a way to determine what the current route is so that it can be checked against the Action that is being called?

please check 'jump' type for newly released 2.0 version. It is actually the same as 'switch', but without inserting nested nav bar inside (which is useful for tab bars)


[Bug]: Code editor loses focus when ESC is pressed

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The JS code editor loses focus when ESC is pressed. This issue has been seen in Chrome/Firefox.
Cause - This behaviour stems from the fact that the "type / for commands" in editors found in the JS pane has to be closed when escape is pressed. Since no such menus show up on the editor for JS objects, the focus is lost without menu closing
Steps To Reproduce

Go to the JS Editor
Type something - make sure the autocomplete hinter is not showing
Press escape
Notice that the focus is lost and one needs to click on editor again to regain focus,

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
1.6.6

lgtm
cc: @rimildeyjsr


goog.fx.Dragger listens for touchmove instead of touchstart

This PR adresses issue #443 and makes goog.fx.Dragger listen to goog.events.EventType.TOUCHMOVE instead of goog.events.EventType.TOUCHSTART on the handle. This makes click listeners inside the handle element work on touch devices.

See https://github.com/google/closure-library/issues/443


Kernel error in spyder

Issue Report Checklist

[ yes] Searched the issues page for similar reports
[yes ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice

Problem Description
kernel doesn't start in Sypder,says traceback error
Paste Traceback/Error Below (if applicable)
An error ocurred while starting the kernel
Traceback (most recent call last):
File "D:\Anaconda\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "D:\Anaconda\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "D:\Anaconda\lib\site‑packages\spyder_kernels\console_main.py", line 11, in
start.main()
File "D:\Anaconda\lib\site‑packages\spyder_kernels\console\start.py", line 279, in main
import_spydercustomize()
File "D:\Anaconda\lib\site‑packages\spyder_kernels\console\start.py", line 39, in import_spydercustomize
import spydercustomize
File "D:\Anaconda\lib\site‑packages\spyder_kernels\customize\spydercustomize.py", line 27, in
from IPython.core.getipython import get_ipython
File "D:\Anaconda\lib\site‑packages\IPython_init.py", line 54, in
from .core.application import Application
File "D:\Anaconda\lib\site‑packages\IPython\core\application.py", line 16, in
from copy import deepcopy
File "D:\Anaconda\lib\copy.py", line 60, in
from org.python.core import PyStringMap
File "C:\Users\tjash\org.py", line 8, in
import pandas as pd
File "D:\Anaconda\lib\site‑packages\pandas_init_.py", line 42, in
from pandas.core.api import *
File "D:\Anaconda\lib\site‑packages\pandas\core\api.py", line 26, in
from pandas.core.groupby import Grouper
File "D:\Anaconda\lib\site‑packages\pandas\core\groupby_init_.py", line 1, in
from pandas.core.groupby.groupby import GroupBy # noqa: F401
File "D:\Anaconda\lib\site‑packages\pandas\core\groupby\groupby.py", line 37, in
from pandas.core.frame import DataFrame
File "D:\Anaconda\lib\site‑packages\pandas\core\frame.py", line 100, in
from pandas.core.series import Series
File "D:\Anaconda\lib\site‑packages\pandas\core\series.py", line 51, in
import pandas.plotting.core as gfx
File "D:\Anaconda\lib\site‑packages\pandas\plotting_init.py", line 11, in
from pandas.plotting._core import boxplot
File "D:\Anaconda\lib\site‑packages\pandas\plotting_core.py", line 36, in
from pandas.plotting import converter
File "D:\Anaconda\lib\site‑packages\pandas\plotting_converter.py", line 6, in
import matplotlib.dates as dates
File "D:\Anaconda\lib\site‑packages\matplotlib_init.py", line 141, in
from . import cbook, rcsetup
File "D:\Anaconda\lib\site‑packages\matplotlib\rcsetup.py", line 25, in
from matplotlib.fontconfig_pattern import parse_fontconfig_pattern
File "D:\Anaconda\lib\site‑packages\matplotlib\fontconfig_pattern.py", line 19, in
from pyparsing import (Literal, ZeroOrMore, Optional, Regex, StringEnd,
File "D:\Anaconda\lib\site‑packages\pyparsing.py", line 5235, in
_reBracketExpr = Literal("[") + Optional("^").setResultsName("negate") + Group( OneOrMore( _charRange | _singleChar ) ).setResultsName("body") + "]"
File "D:\Anaconda\lib\site‑packages\pyparsing.py", line 1365, in setResultsName
newself = self.copy()
File "D:\Anaconda\lib\site‑packages\pyparsing.py", line 1322, in copy
cpy = copy.copy( self )
AttributeError: module 'copy' has no attribute 'copy'
Versions

Spyder version: 3.3.6
Python version: 3.7
Qt version:
PyQt version:
Operating System name/version: windows 10

Dependencies

PASTE DEPENDENCIES HERE

Please search for a file called copy.py in your Users directory and remove it. That should solve your problem.

did resolve even after deletion

sorry did not resolve even after deletion


How to run Spark jobs that connect to Cassandra nodes on DCOS

@cornelf do you plan to do this? If so, can I ask you to create a new issue on Jira since we're migrating over?

Closing now. If you still plan to do it, please raise a new issue in Jira using the documentation component.


getting goreportcard up to 100%

This should cover all the cyclo checks and the misspell that cropped up.
Also adds gocyclo as part of the make lint check, which will make it a required check for circle. Now that we have everything at a cyclo score of 15 or under, let's keep it there :-)
Closes #815
Signed-off-by: David Lawrence<EMAIL_ADDRESS>(github: endophage)

@cyli @riyazdf @HuKeping ready for review!

Oh huh it doesn't undo the request changes - I guess "comment" doesn't reset state.  I guess I am requesting changes though...

Yay, this is such a great cleanup!  Thanks for doing this and adding the check!  LGTM!


ConnectionStrings support in CloudConfigurationManager

We are using CloudConfigurationManager in our webjobs to access the hosting sites app settings. Is there any reason why the connectionstrings settings is not exposed in CloudConfigurationManager?

This is outside the scope of cloud configuration manager.  Please see the azure websites documentation for information on hpw to access application settings.

I don't really agree on the answer. Connectionstrings and AppSettings are the same kind of configuration that you would expect to be accessible via the CloudConfigurationManager class. I know how to access them, but I would rather see the same approach for them.
Why are they outside the scope ?

@markcowl Any update on my last reply ?

@markcowl ?


Update geeksay.js

#5
please review and merge

I have 2 sayings please review and merge pr.

Invalid translations, please make sure to add more generalised translations.

@disha100 also don't create multiple PRs for just adding translations. I am closing you #397 PR as its spam. You can add translations in this PR.


DrySubmit create rule failure: sql: no rows in result set

Hi guys,
I'm new to PocketBase, and currently stuck on the API rules. I'm trying to only allow users to create a record if their id is the same as "creatorID", but I am getting "DrySubmit create rule failure: sql: no rows in result set"... let me just show you...
//API rules

//my code
import fs from "fs"; // Import filesystem module
import PocketBase from "pocketbase";

const pb = new PocketBase("<REDACTED>");

// Authenticate the user
await pb
  .collection("users")
  .authWithPassword("<REDACTED>", "12345678");

// Prepare form data
const formData = new FormData();
formData.append("creatorID", "dsa9myhib75uqnx");
formData.append("diena", "Vasario 22 d.");
formData.append("tipas", "ansablis");
// redacted

formData.append(
  "kurinys",
  new Blob([fs.readFileSync("./song.mp3")]),
  "song.mp3"
);

await pb.collection("anketos").create(formData);

(I've gotten the same error making an API create rule for users<EMAIL_ADDRESS>!= true", but gave up.)

hm.. using<EMAIL_ADDRESS>= @request.data.creatorID" worked, I don't see a difference between the two but I guess I'm just dumb...

Turns out because I'm dumb and used && instead of ||

I updated the field from a text one to a relation one. Now I'm experiencing the same thing, I've tried all of these:
@request.auth.id = creator.id

@request.auth.id = creator

@request.auth.id = @request.body.creator

@request.auth.id = @request.body.creator.id

@request.auth.id != "" && @request.body.creator = @request.auth.id

@request.auth.id != "" && @request.body.creator.id = @request.auth.id

@request.auth.id != "" && creator.id = @request.auth.id

@request.auth.id != "" && creator = @request.auth.id

@request.auth.id != "" && (
    // I am the original creator,
    @request.auth.id = creator.id
)

@request.auth.id != "" && (
    // I am the original creator,
    @request.auth.id<EMAIL_ADDRESS>)

Without any luck. Any advice?

@em-kaa It is not clear what is the issue, nor what you are trying to do because you are not providing the complete code sample to understand what is the body you are submitting (are you sure that the authenticated user id matches with the one you are submitting? what is the "redacted" data?).
If you are trying to ensure that the submitted relation field matches the authenticated user, then the rule:
@request.auth.id != "" &&
@request.auth.id = @request.data.yourRelField

I've just tested it locally on PocketBase v0.22.27 with the below minimal pb_public/index.html and it works correctly for me:
<!DOCTYPE html />
<html>
<head>
    <meta charset="utf-8" />
    <title>Test</title>
</head>
<body>
    <script type="module">
        import PocketBase from<EMAIL_ADDRESS>
        const pb = new PocketBase("http://<IP_ADDRESS>:8090");

        await<EMAIL_ADDRESS>"1234567890")

        await pb.collection("example").create({
            "yourRelField": pb.authStore.model?.id
        })
    </script>
</body>
</html>

In any case, the threaded format of the Q&A discussions is better suited for this type of posts.
If you are still not able to identify  the culprit:

elaborate more clearly what actually is the issue and what you are trying to do
export your collections configuration as json (Admin UI > Settings > Export collections)
provide more details how you are testing (what PocketBase version, what JS SDK version, where your code is running and how)
provide a more complete code sample and standalone code sample that can trigger the error

@ganigeorgiev Thanks for your quick reply! Unfortunately, your rule didn't work.
Here's a better explanation of what I'm trying to do,
Im trying to check, if the user creating the record linking themselves in the "creator" field, and not another user.
Here are my collections as json..
pb_schema (1).json
Im using PocketBase v0.23.0, SDK is v0.22.0, and I'm using React, but I don't my code is needed in this case, but here it is anyway.
import React, { useState } from "react";
import PocketBase from "pocketbase";
const pb = new PocketBase("");
const Anketa: React.FC = () => {
const [form, setForm] = useState({
creator: "53jbn4b61i592cr",
tipas: "ansamblis",
kolektyvo_pavadinimas: "",
sol_vardas: "",
sol_pavar: "",
sol_gimim: "",
ansa_dalyviu_skaicius: 0,
ansa_vaiku_amziaus_vidurkis: 0,
ansa_amziaus_kategorija: "",
solo_amziaus_kategorija: "",
ansa_aktyv_mic_skaicius: 0,
ansa_neaktyv_mic_skaicius: 0,
kurinio_pavadinimas_autoriai: "",
kurinio_trukme_min: 0,
kurinio_trukme_sek: 0,
kurinys: null as File | null,
vadv_vardas: "",
vadv_tel: "",
vadv_elpastas: "",
ar_reik_sask: true,
sask_rekv: "",
istaigos_pavadinimas: "",
kolektyvo_pavadinimas2: "",
vadovo_vardas_pavard: "",
choreografo_vardas_pavard: "",
akompaniatoriaus_vardas_pavard: "",
diena: "",
});
const handleFileUpload = (e: React.ChangeEvent) => {
const file = e.target.files?.[0] || null;
setForm({ ...form, kurinys: file });
};
const handleChange = (field: string, value: any) => {
setForm({ ...form, [field]: value });
};
const handleSubmit = (e: React.FormEvent) => {
e.preventDefault();
pb.collection("anketos").create(form);
};

@ganigeorgiev Thanks for your quick reply! Unfortunately, your rule didn't work.
Here's a better explanation of what I'm trying to do,
I'm trying to check if the user creating the record, links themselves in the "creator" field, and not another user.
Here are my collections as JSON.
pb_schema (1).json
I'm using PocketBase v0.23.0, SDK v0.22.0, and React. I don't think my code is needed in this case, but here it is anyway.
import React, { useState } from "react";
import PocketBase from "pocketbase";
const pb = new PocketBase("");
const Anketa: React.FC = () => {
const [form, setForm] = useState({
creator: "53jbn4b61i592cr",
tipas: "ansamblis",
kolektyvo_pavadinimas: "",
sol_vardas: "",
sol_pavar: "",
sol_gimim: "",
ansa_dalyviu_skaicius: 0,
ansa_vaiku_amziaus_vidurkis: 0,
ansa_amziaus_kategorija: "",
solo_amziaus_kategorija: "",
ansa_aktyv_mic_skaicius: 0,
ansa_neaktyv_mic_skaicius: 0,
kurinio_pavadinimas_autoriai: "",
kurinio_trukme_min: 0,
kurinio_trukme_sek: 0,
kurinys: null as File | null,
vadv_vardas: "",
vadv_tel: "",
vadv_elpastas: "",
ar_reik_sask: true,
sask_rekv: "",
istaigos_pavadinimas: "",
kolektyvo_pavadinimas2: "",
vadovo_vardas_pavard: "",
choreografo_vardas_pavard: "",
akompaniatoriaus_vardas_pavard: "",
diena: "",
});
const handleFileUpload = (e: React.ChangeEvent) => {
const file = e.target.files?.[0] || null;
setForm({ ...form, kurinys: file });
};
const handleChange = (field: string, value: any) => {
setForm({ ...form, [field]: value });
};
const handleSubmit = (e: React.FormEvent) => {
e.preventDefault();
pb.collection("anketos").create(form);
}

I'm not able to reproduce with your collection and PocketBase v0.23.0. Here is a minimal pb_public/index.html (I've only enabled password auth for the user collection for easier testing):
<!DOCTYPE html />
<html>
<head>
    <meta charset="utf-8" />
    <title>Test</title>
</head>
<body>
    <script type="module">
        import PocketBase from<EMAIL_ADDRESS>
        const pb = new PocketBase("http://<IP_ADDRESS>:8090");

        // note: enable password auth for your user collection for simplicity
        await<EMAIL_ADDRESS>"1234567890")

        await pb.collection("anketos").create({
            creator:                        pb.authStore.record?.id,
            tipas:                          "ansamblis",
            kolektyvo_pavadinimas:          "test",
            sol_vardas:                     "test",
            sol_pavar:                      "test",
            sol_gimim:                      "test",
            ansa_dalyviu_skaicius:          2,
            ansa_vaiku_amziaus_vidurkis:    1,
            ansa_amziaus_kategorija:        "Iki 8 m.",
            solo_amziaus_kategorija:        "4 - 7 m.",
            ansa_aktyv_mic_skaicius:        1,
            ansa_neaktyv_mic_skaicius:      1,
            kurinio_pavadinimas_autoriai:   "test",
            kurinio_trukme_min:             1,
            kurinio_trukme_sek:             1,
            kurinys:                        "",
            vadv_vardas:                    "test",
            vadv_tel:                       "test",
            vadv_elpastas:                  "test",
            ar_reik_sask:                   true,
            sask_rekv:                      "test",
            istaigos_pavadinimas:           "test",
            kolektyvo_pavadinimas2:         "test",
            vadovo_vardas_pavard:           "test",
            choreografo_vardas_pavard:      "test",
            akompaniatoriaus_vardas_pavard: "test",
            diena:                          "Vasario 22 d.",
        })
    </script>
</body>
</html>

Make sure that you are authenticated before submitting the response and that the submitted data are actually what you expect. More than I can't help further.

As a side-note, I also noticed that both collections have combined created, updated. Avoid using composite/combined indexes if you are not sure that your query will benefit from it because it could slow down your application (see https://github.com/pocketbase/pocketbase/discussions/3859#discussioncomment-7744045).

Also another unrelated side-note since I noticed that the users collection id is using a checksum from an older release candidate and not the one that comes with the stable v0.23.0 migration: as mentioned in the v0.23.0 changelog, if you had previously migrated to one of the release candidates before v0.23.0-rc14 and have a full collection snapshot migration generated, then you may have to regenerate it again to avoid conflicts when deploying on a new environment.

I'm not able to reproduce it with your collection and PocketBase v0.23.0. Here is a minimal pb_public/index.html (I've only enabled password auth for the user collection for easier testing):
<!DOCTYPE html />
<html>
<head>
    <meta charset="utf-8" />
    <title>Test</title>
</head>
<body>
    <script type="module">
        import PocketBase from<EMAIL_ADDRESS>
        const pb = new PocketBase("http://<IP_ADDRESS>:8090");

        // note: enable password auth for your user collection for simplicity
        await<EMAIL_ADDRESS>"1234567890")

        await pb.collection("anketos").create({
            creator:                        pb.authStore.record?.id,
            tipas:                          "ansamblis",
            kolektyvo_pavadinimas:          "test",
            sol_vardas:                     "test",
            sol_pavar:                      "test",
            sol_gimim:                      "test",
            ansa_dalyviu_skaicius:          2,
            ansa_vaiku_amziaus_vidurkis:    1,
            ansa_amziaus_kategorija:        "Iki 8 m.",
            solo_amziaus_kategorija:        "4 - 7 m.",
            ansa_aktyv_mic_skaicius:        1,
            ansa_neaktyv_mic_skaicius:      1,
            kurinio_pavadinimas_autoriai:   "test",
            kurinio_trukme_min:             1,
            kurinio_trukme_sek:             1,
            kurinys:                        "",
            vadv_vardas:                    "test",
            vadv_tel:                       "test",
            vadv_elpastas:                  "test",
            ar_reik_sask:                   true,
            sask_rekv:                      "test",
            istaigos_pavadinimas:           "test",
            kolektyvo_pavadinimas2:         "test",
            vadovo_vardas_pavard:           "test",
            choreografo_vardas_pavard:      "test",
            akompaniatoriaus_vardas_pavard: "test",
            diena:                          "Vasario 22 d.",
        })
    </script>
</body>
</html>

(Adjust the above user credentials, open the browser and navigate to http://<IP_ADDRESS> and check the console)
Make sure that you are authenticated before submitting the response and that the submitted data is actually what you expect. More than this I can't help further.

That worked. Thank you!


Update Docker instructions.

@juliaferraioli @kprobst
Closes https://github.com/GoogleCloudPlatform/kubernetes/issues/9460

Looking forward to. @brendandburns, Now the docker approach is a step-by-step appoach, do we need  shell scripts to automatically do the job and speed up the deployment?

@WIZARD-CXY we could turn it into a full-fledged provider in the shell scripts if we want to.  I kind of like keeping the steps so that people can see what is actually happening.

LGTM.


Adding apply styles from CartoCSS panel

When it is ready, it fixes https://github.com/CartoDB/cartodb/issues/7525.
cc @javisantana @nobuti

LGTM.

Frontend tests passing, merging ;)


Add subheadings to get started pages

Because we didn't add 'sections' to the Yaml, the page titles in the Get started section didn't have subheadings

You can preview this change here:
Built with commit 17ecb16f0dbc80854bc5778af6cce36ab6ea08d4
https://deploy-preview-401--govuk-design-system-preview.netlify.com


[BUG] CultureNotFoundException: Only the invariant culture is supported in globalization-invariant mode

Library name and version
Azure.Storage.Blobs 12.21.0
Describe the bug
Got an exception when trying to upload a content into a blob
InvalidOperationException: Failed to compare two elements in the array. TypeInitializationException: The type initializer for 'Azure.Storage.StorageSharedKeyPipelinePolicy' threw an exception. CultureNotFoundException: Only the invariant culture is supported in globalization-invariant mode. See https://aka.ms/GlobalizationInvariantMode for more information. (Parameter 'name')\nen-US is an invalid culture identifier.

I tried to resolve this problem by setting InvariantGlobalization to false in the project file, however, the AKS did not accept it.
Expected behavior
This error does not happen with Azure.Storage.Blobs version 12.20.0
Actual behavior
The service get an exception when uploading the content
Reproduction Steps
blob = new BlockBlobClient(connectionString, containerName, blobName);
NOTE:
relevant change is in sdk/storage/Azure.Storage.Common/src/Shared/StorageSharedKeyPipelinePolicy.cs in commit b99cccb
/sdk/storage/Azure.Storage.Common/src/Shared/StorageSharedKeyPipelinePolicy.cs
Environment
AKS Linux pod
dotNet6.0

Duplicate of https://github.com/Azure/azure-sdk-for-net/issues/45052


Correct menu position when menu is constrained

Fixes #142896
The original code below is to always place the selected item above(overlap) the popup button so that the selected item can always be visible: https://github.com/flutter/flutter/blob/f8a77225f360556322934a9a831ffc9c9f3125da/packages/flutter/lib/src/material/popup_menu.dart#L723-L732
But when menu height is constrained and the menu itself is super long, the selected item still assumes there is enough space to push up all the items whose index is smaller than the selected index. As a result, every time when the menu is open, the calculation provides a different result to be the offset for the selected index,  and then with a constrained height, the menu looks jumping all over the place based on the different selected index.
https://github.com/flutter/flutter/assets/36861262/ad761f95-0ff5-4311-a81d-dac56df879c5
Even though the original calculation is to make the selected item visible when open the menu, the menu doesn't auto scroll and only expands itself as much as possible to show the selected one. In this case, if the screen it too small to show the selected item, we still cannot see it. This can be fixed by using Scrollable.ensureVisible()(#143118).
So we remove the calculation in this PR and the menu will always show up based on the top left of the anchor(button).
https://github.com/flutter/flutter/assets/36861262/03272f26-9440-4ac4-a701-9a0b41776ff9
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

This changes the behavior of menus that don't need to scroll: before we tried to put the selected item over the menu button, now we always align the bottom of the menu with the bottom of the button. I think the original idea was that the button would look like it contained the selected item (when everything fit that is). I think this change is OK, although it may break some golden image tests.

Got it! Thanks a lot for the explanation! For next PR which implements the auto scroll, the scrolled item will always be scrolled to the top of the menu, and the top of the menu is aligned with the button. So probably it can feel similar to the original idea? But yes, this PR changes a lot of menu behaviors.
video demo
https://github.com/flutter/flutter/assets/36861262/0782ed76-0616-4892-925f-520073984e3a

I think the behavior shown in https://github.com/flutter/flutter/pull/143121#issuecomment-1933138597 is sufficiently close to the original (buggy) behavior and also to the original intended behavior. It looks like the customer tests are OK with it. It may trip up some internal tests; we'll have to see after you land it.


ENH: place tract_names instead of index id in output table

This patch provide possibility to add optional flags to tract_math.
Optional flags are always start with "--" and are considered as boolean
flags.
A newly added optional flag is "--useFileNamesAsIndex".
When this flag is used, the created output table uses tractography file
names instead of index IDs.
PS: I did not have access to push to BRAINSia/tract_querier; therefore, I created a new fork "aghayoor/tract_querier" and requested a pull request to BRAINSia/tract_querier.

@hjmjohnson : Please review this pull request.
This will make the pull request cleaner and easier to evaluate.
Then ensure that your patch is built upon the latest master branch.

@hjmjohnson:
My master branch is already rebased based on demianw/tract_querier master branch.
Actually BRAINSia/tract_querier master branch was way off from the main upstream and because of that, there are a lot of other commits in my pull request.


Client Pong timed out

Can't communiate with server, client pong timed out, the connection is disconnected too often

@rachelxj @jondubois  Can you give detail about how we can reproduce this.

Hi @lihan -
Just FYI - I'm experiencing the same thing with a very basic setup. I created a socketcluster app, fired it up with node server.js. I installed socketcluster-client-iOS via cocoapods and followed the instructions exactly.
Client side gets a lot of this:
WVJB RCVD: {"callbackId":"cb_6_1456874992151","handlerName":"onErrorHandler","data":{"data":"Server ping timed out"}}
WVJB RCVD: {"callbackId":"cb_9_1456875013152","handlerName":"onErrorHandler","data":{"data":"Client pong timed out"}}
Server side gets a lot of this:
[Warning] SocketProtocolError: Client pong timed out
And eventually this:
[Warning] SocketProtocolError: Socket hung up
It appears to be reconnecting after the time out - but then just times out again. That's why I'm seeing several of these.
Is this library actively developed and tested?

@elondon Yes this client out of date (that's what's causing the issue)... I asked @lihan if he can update it so stay tuned.

@lihan [Warning] SocketProtocolError: Socket hung up  is this issue fixed?

@lihan @elondon Please respond if this library is still getting supported by you.


check-cluster.rb don't work for password protected redis

Hi team,
After adding password to our redis instance, check-cluster.rb stopped working.
After a short look I've noticed that tiny_redis class don't have any option to provide the redis password.
The command used is
/etc/sensu/plugins/check-cluster.rb  --cluster-name prod --check check_backup
And the output:
CheckCluster CRITICAL: Redis error: NOAUTH Authentication required. (RuntimeError): ["/etc/sensu/plugins/tiny_redis.rb:91:in parse_response'", "/etc/sensu/plugins/tiny_redis.rb:84:in method_missing'", "/etc/sensu/plugins/tiny_redis.rb:27:in block in check_redis_connection'", "/etc/sensu/plugins/tiny_redis.rb:26:in upto'", "/etc/sensu/plugins/tiny_redis.rb:26:in check_redis_connection'", "/etc/sensu/plugins/tiny_redis.rb:17:in initialize'", "/etc/sensu/plugins/check-cluster.rb:101:in new'", "/etc/sensu/plugins/check-cluster.rb:101:in run'", "/opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/sensu-plugin-2.0.1/lib/sensu-plugin/cli.rb:58:in block in '"]`
Is there any way to provide the redis password to the current module?
Regards,
Adrian/

yeah, currently authenticating is not supported, but shouldn't be hard to add:
replacing https://github.com/Yelp/puppet-monitoring_check/blob/master/files/check-cluster.rb#L236 with something like:
TinyRedis::Client.
  new(redis_config[:host], redis_config[:port]).
  tap { |tr| tr.auth(redis_config[:password]) }

should do it.
PRs are welcome :)

@adriananeci hard to say without seeing the diff you're working with, but i would guess you're calling .tap on redis_config[:port] rather than an instance of TinyRedis::Client.
TinyRedis::Client should have no problem running the AUTH command because commands are dispatched via method_missing, which is ruby's way to say "if a method is not defined - run me instead". see line 15 in the gist you've linked.
here is the more imperative way to write the above change:
@redis = begin
  tr = TinyRedis::Client.new(redis_config[:host], redis_config[:port])
  tr.auth(redis_config[:password])
  tr # return actual client object from this block
end

Ah, yeah, sorry, my bad.
You were right, I've omitted a bracket :D
I can confirm that it's working now.
Thanks.


fix for #16

Since you said you could accept this that way, here is my last attempt ;)

O_o
Is this a joke?

partly a joke ;)


Feature Request: Graceful Handling of Duplicate Collections/Subcollections for Fireorm v >=0.18.0

Issue Description:
When upgrading Fireorm from version 0.16.0 to 0.18.0, encountering an error related to duplicate collections and subcollections poses a challenge. The current behavior throws an error if duplicates are detected, as evidenced by the code snippet below:
if (existing) {
  throw new Error(`Collection with name ${existing.name} has already been registered`);
}

A more favorable approach would be for Fireorm to gracefully skip duplicates instead of halting execution with an error. Consider the example below where the 'schools' collection is already registered:
@Collection('schools')
export class School {
  id: string;
  name: string;
}

@Collection('Drivers')
export class Driver {
  id: string;
  name: string

  @SubCollection(School, 'schools')
  schools?: School
}

This enhancement would streamline the upgrade process and improve the overall developer experience with Fireorm.

This issue has been resolved by this PR ✅


add cache key to /compressor url

is it possible to change compressor url to /compressor/some-cache-code/?
I ran into a difficulty busting the cache when compressor is enabled with a custom plugin.
Found a bug in a plugin affecting IE, now can't deploy the fix because of very sticky cache.
Thank you.

That's something we should work on. Do you want to tackle this?

I think the easy way to do it, is to take a hash of the content here: https://github.com/aljosa/django-tinymce/blob/master/tinymce/compressor.py#L138-L139
And add a ETag header with it.

It seems to be the case but we may add a test for it.


The image referenced in the documentation lacks required utils (lsblk)

When trying to deploy the operator using the prebuilt image referenced in the documentation (quay.io/mulbc/lvm-operator), everything seems to work fine until you create the LVMCluster resource. All pods are started, but when creating a pvc and a pod, nothing happens.
Looking at the pod logs, I found the following in the vg-manager pod:
{"level":"error","ts":1644504805.3839536,"logger":"controller.lvmvolumegroup","msg":"Reconciler error","reconciler group":"lvm.topolvm.io","reconciler kind":"LVMVolumeGroup","name":"vglvmoperator","namespace":"lvm-operator-system","error":"failed to list block devices: exec: "lsblk": executable file not found in $PATH","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:227"}
It looks like the image is based on Fedora 35, and lacks the util-linux package that provides lsblk.
I managed to build the images manually (replacing centos:8 with centos:stream8 in the Dockerfile definition), and then everything worked as expected.

Thanks for reporting this.The image has been updated and should work now.


Issue with the TF Connect App for multiple users

Farms are not showing up.

https://github.com/threefoldtech/threefold_connect/assets/152964575/3561a809-90d6-4c73-b138-5013c4ccf3c1

The issue is addressed and solved. Can you please try it?

Hello @AhmedHanafy725 , I checked the App and yes, the farms seem to be showing up, Thank you!


Should the strict-mode status of a file be dependent on its external module status

With #4811 merged we've decoupled ES6 module emit from the ES6 language level, allowing us to emit other module forms when targeting ES6. This brings up another interesting question - we parse all external modules in strict mode, ES6 or not, when this is only a requirement for ES6 modules. Should we fix this and make the parse dependent on the module selection? Or should we emit "use strict"; in non-ES6 forms so reality matches the parser? Even before #4811 we've actually had this wrong:
import * as foo from "./foo";

with (foo) {

}

We forbid the with as per strict mode, but we're emitting an amd module without a "use strict"; indicator. To be correct, when not targeting es6 modules, we should either disable strict mode when parsing or emit a "use strict";.

If in fact you are parsing all modules in strict mode, irrespective of the target, then it makes sense in my mind to emit the prolog in other module targets.  My comment in #3576 was of a worry that it might cause breakage or surprises, but since essentially if external modules have always been parsed in strict mode, if there is breakage, then it was in theory a bad emit and should break so it can be addressed.

+1 for emitting "use strict" when the code is parsed in strict mode.


Data Ingestion State

[x] Update config.YAML
[x] research or analysis
[x] Update the entity
[x] Update the configuration manager in src
[x] Update the components
[x] Update the pipeline

Dry run successful for stage 01


Make a calendar of community events and how SCR will participate in each

https://docs.google.com/document/d/1lqpj20wJhuGpM8RK-weJhUxQMQEoiJLMxdm0Yoy5fu4/edit?usp=sharing

@janawalke  can you move this file so that it's in the SCR folders (owned by Cori)? https://drive.google.com/drive/u/0/folders/1XabBitCoFgipcJD4DRPliYBkJSHtNaTu

Team review 7/18: Looks good other than moving file to shared folder.


Does mongo-express support mongo 3.x?

It has been working for me so far, no issues.

Yes! @catorda just submitted https://github.com/andzdroid/mongo-express/pull/148


The AspNetCoreCompat package needs to be updated

https://github.com/aspnet/Identity/tree/dev/src/Microsoft.AspNet.Identity.AspNetCoreCompat
The CreateSharedDataFormat method uses "Microsoft.AspNet.Authentication.Cookies.CookieAuthenticationMiddleware" which of course is the old name. Should check other parts of the source too and update the sample

@HaoK @Tratcher

Ah good catch, thanks!

9e0204279818869b43c7cb4695b726c2960be662


feat: add pydantic v2 compatibility

Pull Request

Description
Add pydantic v2 compatibility, original agent-protocol can only use in pydantic v1.
Detail see https://docs.pydantic.dev/2.0/migration/#continue-using-pydantic-v1-features
Checklist
Please review and check the following items to ensure your pull request can be processed smoothly:

[x] My code adheres to the project's coding standards and style guidelines.

[x] I have tested my changes thoroughly, including unit tests where applicable.

[ ] I have updated the documentation to reflect any changes made in this pull request.

[x] My branch is up-to-date with the latest changes from the main branch.

[x] I have received code review feedback and addressed any comments or concerns.

Additional Notes
This method is forked from langchain.
References, Fixes and Closes

Hi @merwanehamadi , could you please review this PR? I would greatly appreciate your feedback. Thank you.

What feature of v1 do we need that v2 doesn’t support?

I see the code. Current pydantic usage is compatible with both v1 and v2, it means this PR is unnecessary, but the problem is that poetry needs to be compatible with v2.
I create a new PR here #114


ForgePad

Ready to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!
What was your inspiration to make it?
from this guy called ScottpadV1's product, but without the spining input thing(i don't know how to make it) and more buttons(because i can lol)
Hardest challenges faced
don't know anything about it(case making, qmk, wiring, literaly everything)
Other fun facts to know
i spend 5 hours learning how to upload ai03's plate generator's product onto my top case in blender
Every hackpad submission's page will be published on the main hackpad website, so make sure to go submit!
I KNOW IT'S LATE BUT PLEASE ALLOW I'M BEGGING

Could you please put your PCB files for your PCB in a folder called "PCB"?

i also changed the cad to upper just in case, let me know if anything else is wrong


duration.toISOString() doing some floating point  arithmetic for milliseconds…

Description of the Issue and Steps to Reproduce:
It looks like duration.toISOString() is not handling milliseconds properly… You can reproduce this in the most recent version of Chrome in the console on momentjs.com
duration = moment.duration("1:00:1.1");
duration.toISOString(); // => "PT1H1.099999999999909S"

duration.milliseconds(); // => 100

It looks like any duration over 1 minute with milliseconds is experiencing the problem…
moment.duration("0:0:1.1").toISOString() // => "PT1.1S"
moment.duration("0:0:59.1").toISOString() // => "PT59.1S"
moment.duration("0:0:60.1").toISOString() // => "PT1M0.10000000000000142S"

Environment:
new Date().toString(): Fri Sep 15 2017 22:44:37 GMT-0700 (Pacific Daylight Time)
new Date().toLocaleString(): 9/15/2017, 10:44:37 PM
new Date()).getTimezoneOffset(): 420
navigator.userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3213.3 Safari/537.36
moment.version: 2.18.1

Thanks for the bug report.
This sounds like a duplicate of #4145.  The fix is ready and waiting to be merged in the next release (fix is in PR #4146)

Closing in favor of those.


Fix code scanning alert - Use of a broken or risky cryptographic algorithm

Tracking issue for:

[ ] https://github.com/smadi0x86/MalwareHolmes/security/code-scanning/1

This hashing is not for covering sensitive information or passwords, denied as a security risk.


Error: "Desired compensation matrix not found" - Source Localization with ref_meg=False

Hello
My issue is likely related to #5221.
I would like to perform analyses in the source space from a CTF dataset, however I am not able to create a forward solution for any of my subjects given the fact that during my pre processing steps, I chose not to include the reference channels. This has resulted in the error: "Desired compensation matrix not found" when running the make_forward_solution command with a transformation matrix that equals an identity matrix (i.e. =None), or in an error ponting out that there might be "1 MEG sensor inside the scalp surface" when using ='fsaverage' from your datasets. For the records, I don't have right now the MRI scans of my subjects, therefore I am solely relying on the head models 'fsaverage' and 'spm' that you guys provide.
Is there a way to work around this? For instance, calculating and adding such a compensation matrix to the epoch files before going to the source space? I would like to avoid, if possible re running from scratch the preprocessing.
Thanks in advance.
Rob

@RobertoFelipeSG what was the reason for dropping the ref_meg channels? how did you end up removing the compensation matrix? before trying to hack it back in let's see if it's easier to never have lost it.
my 2c

@agramfort Thanks for your willingness to help. I didn't include the ref_meg because our recordings include a 3rd level gradient compensation. I did not deliberately remove the compensation matrix. I don't really know if the matrix was dropped during any of my preprocessing steps following a standard pipeline. Would that have been possible through any of the MNE commands (e.g. Filtering, Finding events, Making a montage, Picks)?

I didn't include the ref_meg because our recordings include a 3rd level gradient compensation. I did not deliberately remove the compensation matrix.

When you pick channels without including the reference channels, their associated compensation matrices will be removed, too. If you want to use gradient-compensated data, in general you should keep the reference channels. Is it possible to change your pipeline to do this?

Dear @larsoner, thanks for the explanation. I re ran my preprocessing pipeline in one of my datasets including the ref_meg (i.e =True) channels, hoping that this would solve the issue later on during the source reconstruction. However, I always get the same error when creating the forward solution: "Found N sensors inside the scalp surface, perhaps coordinate frames and/or coregistration must be incorrect". I tried with the SPM and fsaverage datasets and the only difference is the number of channels N that are found outside the scalp surface when the error message pops up. Any ideas on how to make this work?
From one side, I would prefer not to re run all the preprocessing in all datasets for the sake of time. Nonetheless, if this would solve the issue, I am willing to start from scratch. From the other side, now I am doubting that the ref_meg channels are really the missing link that would permit me the creation of the forward solution. From a general perspective, what would be your advice to do source reconstruction on CTF data if I don't have access to the MRI of subejcts?

"Found N sensors inside the scalp surface, perhaps coordinate frames and/or coregistration must be incorrect".

This suggests that your CTF system is recording reference sensor positions that are inside the head. Can you check what plot_alignment looks like with these data with meg=('sensors', 'ref')?

@larsoner I am sorry for the delay in my response. To correctly perform the "plot_alignment", I had to deal with some visualization issues in the institutional server I use. In any case, here is the figure resulting from such an alignment. It indeed looks that my MEG recordings and the average MRI head are in two different planes of reference, even though I had included for this example the ref_meg = True in the picks function. What would you suggest to do in this case to align them? How could I possibly define a correct transformation matrix that permits me to perform a source reconstruction ?
Thanks in advance.

What would you suggest to do in this case to align them?

Either your MRI<->head transform is wrong, which you can fix using mne coreg. Or your head<->MEG transform is wrong, which indicates a problem with your recording.
This doesn't seem like an MNE-Python issue at this point, though, so let's continue the conversation over on https://mne.discourse.group/ since it's now about usage I think!


Add CJS distribution to allow both NextJS and Node usage

This package is esm-only at the time of writing. This is a good call and a growing trend.
However, NextJS does not currently fully support Node’s explicit file extension pattern for esm.
This means that it is impossible to:

Use this library with NextJS
AND write tests that use the library running in Node (such as E2E/Integration tests that require DB mutations).

Further, despite esm seen as the de-facto better future, its support is still limited, with many issues still to iron out.
A CJS distribution along an ESM one, would ensure that developers do not have to waste time on esm friction (I did, and it took 10 hours).
The diagram below depicts the issue.

We primarily use this driver in the Next.js app that serves https://app.planetscale.com. Can you provide more detail on what code isn't working?

We also use the driver so we can have edge API routes speaking to the DB as part of a NextJS app.
But production is only one side of the coin. There's also the development and testing side of things.
Example

Can you provide more detail on what code isn't working?

// app/pages/api/auth/login.js
import addUser from 'db/addUser';

// db/addUser
import { client } from './client';

// db/client
import { Client } from '@planetscale/database';

Now if we work it backwards:

@planetscale/database is esm only, so with Node you must configure the project package with "type": "module", or you'll get Error [ERR_REQUIRE_ESM]: Must use import to load ES Module.
But with "type": "module" the module specifier  in db/addUser needs to change to ./client.js, which NextJS can't handle.

Possible Workaround
To be fair, If instead of:
import { Client } from '@planetscale/database';

One writes:
const { Client } = await import('@planetscale/database');

Then it should (haven't tried) build alright both with NextJS and on Node CJS. But one will have to commit the whole import chain (from the API route) to dynamic imports. Not classy, but at least when used on edge functions (but not in Node-runtime API routes) the teardown is immediate so no real penalty in doing this (I believe).
But that's a workaround alright...
Testing
We want coverage for that part of the system - the scripts that mutate the DB. Sure, much of it can be done in E2E tests, but some scenarios are rare, and impractical to reproduce via the UI (or API) - you need a non-production environment with state control.
Related, during development we want to see exactly what the driver returns, and somehow be able to simulate errors for error handling.
Further, for integration tests, we also want to control the DB state - nuking all tables (which is not a public API) and installing fixtures. We can use a Node complaint library for that, like Prisma, but that's the RY in DRY.
There's also security tests like SQL injection - you REALLY want these going through the actual production code and not a look alike.
The takeaway is that you are likely to need Node to do some testing - no problem if you don't go through the same script as NextJS (because you can set it up to be purely ESM), but since NextJS does not support Node's ESM module specifiers (not without a really ugly hack), you can't go through the same scripts, which pretty much means you can test this part of the system.
Closing Thoughts
You can rightly argue that there's nothing wrong with this library - it works on Node, and it works on Edge Runtime.
But it locks Node usage to ESM, which doesn't marry with NextJS:

It will take NextJS some time to fully implement the fullySpecified config option (currently experimental).
It will take NextJS some time to take it out of experimental.
Even then using module specifiers throughout the app will probably be considered "adventurous".
It will take a few years (if at all, but I believe eventually it will happen), for the whole community to align around the ESM standard - specifically its requirement for valid URLs in the browser and explicit file extensions in Node.

Against all this stands adding CJS distribution to the library.

I've just tried the dynamic import option and it works alright (see code below).
I'm inclined to say that as I'm the only one who has experienced this issue, seems sensible to defer the addition of a CJS distribution for now - if others will have similar issues, we can reconsider.
I'm closing this issue and the linked PR. Owners are free to reopen at will.
export async function getExecute() {
  const { Client } = await import('@planetscale/database');

  const client = new Client({
    url: process.env['DATABASE_URL'],
  });

  const conn = client.connection();

  async function execute<T>(query: string, params?: object): Promise<T[]> {
    const result = await conn.execute(query, params);
    return result.rows as T[];
  }

  return execute;
}

Didn't work after all. Ended up using https://www.npmjs.com/package/fix-esm

Didn't work for me either, but fix-esm did


disable hostname lookup in ergo controller

What is it for, btw?

Cuts down on some spam in test output (https://github.com/ergochat/ergo/pull/1768), might speed things up on some systems (lookup of localhost should be near-instantaneous on most systems though).


Additional schema prefix not being used in cast_assoc

Environment

Elixir version (elixir -v): 1.8
Database and version PostgreSQL 9.6
Ecto version (mix deps): 3.3
Database adapter and version (mix deps): Ecto.Adapters.Postgres
Operating system: MacOs 10.14

Current behavior
I have run into an issue when using cast_assoc when the child association is a different schema prefix then the parent schema and I am receiving this error

defmodule ParentSchema do
  use Ecto.Schema
  import Ecto.Changeset

  @schema_prefix "parent"
  schema "table_1" do
    belongs_to(:child, ChildSchema)
  end

  def changeset(data, params) do
    data
    |> cast(params, __schema__(:fields))
    |> cast_assoc(:child)
  end
end

defmodule ChildSchema do
  use Ecto.Schema
  import Ecto.Changeset

  @schema_prefix "child"
  schema "table_2" do
    field(:text)
  end

  def changeset(data, params) do
    cast(data, params, __schema__(:fields))
  end
end

defmodule Test do
  def update do
    params = %{
      id: 1,
      child: %{
        id: 1,
        text: "Updated Text"
      }
    }

    ParentSchema
    |> MyRepo.get(1)
    |> My.Repo.preload([:child])
    |> ParentSchema.changeset(params)
    |> My.Repo.update()
  end
end

iex(28)> Test.update

** (Postgrex.Error) ERROR 42P01 (undefined_table) relation "parent.table_2" do
es not exist

    query: UPDATE "parent"."table_2" SET "text" = $1 WHERE "id" = $2

Expected behavior
In theory, this should be attempting to update "child.table_2" rather then "parent.table_2" based on the schema prefix provided
Based on @josevalim 's response to this stack overflow from May '19 it seems like it assumes all schemas are in the same prefix. - I was wondering if this was still the case, if it was something that would be fixable in the short term and what the reasoning behind this decision was.
Really appreciate all of your hard work and would be happy to dig into this if the change is reasonably scoped!

Thanks for the updates! Can you please do a quick sanity check? When you preload the child, which prefix is the query using? I assume it is the child right? Otherwise it would just fail.

I was hoping to get the generates sql query from the preload, but I don't actually know how to grab that since it executes in a separate query from the initial select...
Either way - it does seem to be using the correct schema prefix for the preload
iex(52)> ParentSchema |> preload([:child]) |> Repo.get(1) |> IO.inspect(structs: false)
%{
  __meta__: %{
    __struct__: Ecto.Schema.Metadata,
    context: nil,
    prefix: "parent",
    schema: ParentSchema,
    source: "table_1",
    state: :loaded
  },
  __struct__: ParentSchema,
  child: %{
    __meta__: %{
      __struct__: Ecto.Schema.Metadata,
      context: nil,
      prefix: "child",
      schema: ChildSchema,
      source: "table_2",
      state: :loaded
    },
    __struct__: ChildSchema,
    id: 1,
    text: "This is a test"
  },
  child_id: 1,
  id: 1
}
%ParentSchema{
  __meta__: #Ecto.Schema.Metadata<:loaded, "parent", "table_1">,
  child: %ChildSchema{
    __meta__: #Ecto.Schema.Metadata<:loaded, "child", "table_2">,
    id: 1,
    text: "This is a test"
  },
  child_id: 1,
  id: 1
}

Ok, that's good news! So the next step is to write a failing test for our suite, then I assume landing a fix is relatively straight-forward.  You can look at the places we call/test cast_assoc itself.

Will do! I appreciate the guidance!

It currently looks like there are some tests that are asserting that this behaviour is desirable - this is from the repo_test.exs document
  defmodule MySchemaWithAssoc do
    use Ecto.Schema

    schema "my_schema" do
      field :n, :integer
      belongs_to :parent, MyParent
    end
  end

  defmodule MyParent do
    use Ecto.Schema

    @schema_prefix "private"

    schema "my_parent" do
      field :n, :integer
    end

    def changeset(struct, params) do
      Ecto.Changeset.cast(struct, params, [:n])
    end
  end

    test "insert, update and insert_or_update parent schema_prefix overrides children schema_prefix" do
      assert {:ok, schema} = TestRepo.insert(%MyParent{id: 1})
      assert schema.__meta__.prefix == "private"

      valid =
        %MySchemaWithAssoc{id: 1}
        |> TestRepo.preload(:parent)
        |> Ecto.Changeset.cast(%{parent: %{id: 1}}, [])
        |> Ecto.Changeset.cast_assoc(:parent)

      assert {:ok, schema} = TestRepo.insert(valid)
      assert schema.parent.__meta__.prefix == nil

      assert {:ok, schema} = TestRepo.insert_or_update(valid)
      assert schema.parent.__meta__.prefix == nil

      assert {:ok, schema} = TestRepo.update(valid)
      assert schema.parent.__meta__.prefix == nil
    end

To me it seems like this is the opposite behaviour then what we would want, it seems like we would want the schema prefixes to be respected while casting the associations, what I would want to write as a failing test for this case would be to change the assertions on that test to respect the schema prefix provided

    test "insert, update and insert_or_update parent schema_prefix does not overrides children schema_prefix" do
      assert {:ok, schema} = TestRepo.insert(%MyParent{id: 1})
      assert schema.__meta__.prefix == "private"

      valid =
        %MySchemaWithAssoc{id: 1}
        |> TestRepo.preload(:parent)
        |> Ecto.Changeset.cast(%{parent: %{id: 1}}, [])
        |> Ecto.Changeset.cast_assoc(:parent)

      assert {:ok, schema} = TestRepo.insert(valid)
      assert schema.parent.__meta__.prefix == "private"

      assert {:ok, schema} = TestRepo.insert_or_update(valid)
      assert schema.parent.__meta__.prefix == "private"

      assert {:ok, schema} = TestRepo.update(valid)
      assert schema.parent.__meta__.prefix == "private"
    end

I agree. Especially because preload respects the child prefix so not respecting it on cast is weird.
So basically it should be this:

if child does not have a prefix, we use parent
if child has a prefix, we use it

That is the behaviour that I would expect to see

Can please send a PR? :)


change test blog in testing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
17 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-1.8%) to 57.632%

Files with Coverage Reduction
New Missed Lines
%

entry.go
2
78.57%

main.go
3
46.06%

broker.go
12
67.7%

Totals

Change from base Build<PHONE_NUMBER>:
-1.8%

Covered Lines:
555

Relevant Lines:
963

💛  - Coveralls


Revert "Load streamers in serial; handle rate limit"

Reverts whitep4nth3r/womenwhostream.tech#4
ISR requests time out after 10 seconds. As a result, ISR fails consistently in production when we are instructed to wait for 60 seconds to avoid limits.

What I'm going to try is writing a script that is fired by a GitHub action to populate a JSON file or something.


Recaptcha

Does this not have up to date software to bypass recaptcha or does that not work anymore. Becuase I thought bots don't work with recaptcha anymore because supreme blocked it. Thanks!

Anybody cop anything with this bot?


Add an alert for "event ended"

Upon starting the app it should check the date in the event file and the current date and if the event has passed show an alert to let the user know they are looking at an old content.
"The event happened from [begin date] to [end date]. You can still browse the session list and check the news feed." (refine text later)

When event has ended the label at the bottom says that: https://github.com/icanzilb/EventBlankApp/issues/39


Create ascii_letters.js

Python's ascii_letters

Cool, thanks!

@kvz can't pass all lint. Just because I can't configure all locally. But I'll try to do that :-)

@kvz I'll fix errors today. I just removed repository from my account and then forgot that I have open request. Anyway I'll fix all errors today!

@kvz I found that code didn't pass all checks and create new request to fix that https://github.com/kvz/locutus/pull/382 and sure with additional functions


[stable/Influxdb] make mounting of GSA key optional for backups to GCS

What this PR does / why we need it:
By making the mounting of a GSA key optional, it give the option of using workload identity to provide the backup with access to GCS. For more info on workload identity please see https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
Special notes for your reviewer:
@Aisuko I'm also hereby adding myself is a maintainer to this chart if you so do agree.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@naseemkullah Thanks for your PR. It's my pleasure that can get you here. Let's trying to merge the PR first

/ok-to-test


Is Syntastic supported in Neovim?

Before trying anything on a Neovim installation I wonder if syntastic would be supported on the vim fork Neovim. I'm placing a issue since I haven't found a proper channel to put my question.
Thanks in advance

Syntastic should work with Neovim, but it isn't "officially" supported.  Meaning, if you report a problem I'll try to address it only if I can reproduce it under plain Vim.  Also, syntastic might eventually support async checking (once Vim's API for job control gets stable), and when / if that happens the async functionality will use Vim's API rather than Neovim's.  However, neomake offers async checking today, and it (only) works with Neovim.

I thought i wasn't supported at all. I'll give a try to neomake (the name is not suggesting about the syntactic completion though). Thanks for your answer!


ROX-9958 : Create default policy to detect Spring4Shell CVEs (CVE-2022-22963 and CVE-2022-22965)

Description
Self Explanatory
Checklist

[x] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[x] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on stackrox/openshift-docs and merge into rhacs-docs)

Testing Performed
Checked to see if policy exists on Policy List page

Checked if CVE identifier in policy lists correct CVEs

LGTM but let's wait for if we want to push in 69.1 or 70.0


preview page is blank

Describe the bug
the preview page is blank with no show
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-ddxsc2?utm_campaign=stackblitz-on-page&utm_source=web-app&utm_medium=sidebar
Steps to reproduce
after chating to bolt and created a website , the preview page is blank with no show
Expected behavior
the preview page is blank with no show
Screen Recording / Screenshot
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Hi @oliviajiang1989,
Appreciate the feedback here. We are tracking this issue: #1791. You can follow there for updates. If you continue to have this problem, posting the requested details on that issue page would be helpful. Thanks!


Use a unified naming scheme for jobs

@jwendell to your comments: the idea was that all jobs are prefixed with the repository name so they're more easily searched in the prow UI. I'm not sure having names that are slightly different to the repositories is good, could be confusing


EF6 CodeFirst query return wrong values.

I created following CodeFirst Model.
public partial class ForumModel : DbContext
{
    public ForumModel()
        : base("name=ForumModel")
    {
    }

    public virtual DbSet<Subject> Subjects { get; set; }

    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
        // Create relationship
        modelBuilder.Entity<Subject>()
            .HasMany(e => e.Children)
            .WithRequired(e => e.Parent)
            .HasForeignKey(e => e.ParentId)
            .WillCascadeOnDelete(false);
    }
}

[Table("Subject")]
public partial class Subject
{
    public int Id { get; set; }

    public int? ParentId { get; set; }

    [Required]
    [StringLength(50)]
    public string Name { get; set; }

    public virtual ICollection<Subject> Children { get; set; }
    public virtual Subject Parent { get; set; }
}

Then i used a simple query like this
db.Subjects.Count(p => p.ParentId == null) // should be 2 but return 0

But if i remove the relationship, it return correct value.

@Knight1988 This GitHub tracker is for EF Core issues. EF6 issues should be filed at https://github.com/aspnet/EntityFramework6
That being said, it looks like the relationship is being defined as Required, meaning that the ParentId property is expected to be non-nullable, but your query is then expecting there to be nulls in the ParentId column.


ansible-later: 2.0.16 -> 2.0.19

Fix build for ansible-later and bump the version and dependecies:

python3Packages.nested-lookup: 0.2.23 -> unstable-2022-07-23
python3Packages.jsonschema: 4.9.1 -> 4.15.0
python3Packages.ansible-later: 2.0.16 -> 2.0.19

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Duplicate of https://github.com/NixOS/nixpkgs/pull/189477 but I would prefer this change.

Hmm, I didn't consider that this will trigger a lot of rebuilds because of jsonschema. Maybe it would be better to go with #189477 if it works with the current version.

Sounds reasonable

Closed in favor of #189477.


added packages page

Title and Issue number

Title :  added packages page
Issue No. : #71
Code Stack : html, css, bootstrap
Close #71

Video/Screenshots (mandatory)

https://github.com/apu52/Travel_Website/assets/110532770/c26a4be4-8b50-404a-afd0-c7419dff401c
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
created more packages in a new page
Are you contributing under any Open-source programme?

JWOC'24

@PranavBarthwal can you give a full view video from clicking on the view all button then deploy to the pricing page & coming back to the home page

https://github.com/apu52/Travel_Website/assets/110532770/f252f309-9c0e-4e7a-a8c5-46a351a6a271


Epic: storage consumption tracking

Motivation
Storage part of https://github.com/neondatabase/neon/blob/metering_rfc/docs/rfcs/021-metering.md (comments are also important).
DoD
Pageserver periodically sends it consumption events to the console. So far we've discussed the following metrics:

written size
real tenant size
s3 tenant size
number of s3 api calls
synthetic size

Each of that metrics should have prometheus endpoint as well
Implementation ideas
Seems that the proposed functionality could be implemented with two background workers (threads / actors / ...) per pageserver.
a) Consumption sender
Periodically (~1min) wakes up and walks over all active tenants to send consumption data to the console. Here it is important to avoid always sending info about all of the tenants. One way to do that is to send info about all tenants on the start, cache values, and then filter out unchanged ones. Other approaches are possible too. For each tenant consumption sender can just take values of corresponding prometheus metrics. All accumulated events about all the tenants can be sent using one query.
b) Synthetic size worker
Synthetic size [*] stands out a bit, as it is expensive to calculate. We can create another background thread which will walk around tenant one by one (potentially with some parallelism) and will update prometheus metric that can be used by the consumption sender. Would be good to skip tenants that did not receive any changes since the last calculation (e.g. if latest_lsn did not change).
[*] https://github.com/neondatabase/neon/pull/2884#discussion_r1029261929
Tasks

[x] Implement and deploy consumption sender for the existing metrics (written size, real tenant size, s3 tenant size) https://github.com/neondatabase/neon/pull/3187
[x] Implement synthetic size worker
https://github.com/neondatabase/neon/pull/3123
[ ] Add S3 api calls metric
[x] Write a page in /docs about it to standardize naming
[ ] https://github.com/neondatabase/neon/issues/2848

@hlinnaka @LizardWizzard @SomeoneToIgnore @koivunej does this plan with background workers sounds reasonable?

Apologies, somehow I have gotten a lot of notifications and am slow to go through them :)

with background workers

Note that with the tenant size there's already two limiting factors for parallelism and concurrency:

global setting for how many size calculations can the tenant size run at once: https://github.com/neondatabase/neon/blob/main/pageserver/src/config.rs#L143
per tenant lock: https://github.com/neondatabase/neon/blob/main/pageserver/src/tenant.rs#L140

We can create another background thread which will walk around tenant one by one (potentially with some parallelism) and will update prometheus metric that can be used by the consumption sender

The functionality is exposed in an async function, so adding a periodic background task would sound most applicable.

Can we please enable and rollout for both us-* regions same as we did for staging?

This Epic is finished. Consumption metrics are available on both staging and prod.
Documentation is in docs/consumption_metrics.md
Follow-ups will be done in separate issues.


Screen status sensor collect problematic status change patterns.

The screen status change should follow specific orders:

on to off (1 to 0)
off to on (0 to 1)
on to unlocked (1 to 3)
off to locked (0 to 2)
unlocked to off (3 to 0)
However, in some dataset, two adjacent rows have the same screen status, e.g., off to off.
In addition, two adjacent rows have problematic status change pattern. e.g., off to unlocked.

From our investigation, the 2 adjacent rows can be flipped order when the data is synced to remote db


Can anyone give in step by step tutorial for building Tesseract4.0

Hi to all experts. I am sorry i am a very novice person in the world of DotNet. I tried to understand in as how to build in the libtesseract 4.0 and all. But unfortunately i was not able to compile it 100%. Even if i was able to run through a build (as described), i failed in producing libtesseract
I always was able to generate Tesseract.dll - and the same was not sufficient for me to be able to load the same in my application.
Actually we are building in a Python based application and i was able to build and use the library sucessfully in Linux environment. The same was trying to achieve in Windows environment but still am a novice on the same. Please can anyone guide me as how once can build the same from scratch on windows using the source to generate (as we see in generated dll files in this repository).

Those instructions are found in the tesseract-ocr project page on GitHub.

I did follow the instructions...
Let me share you the steps i followed up:

Install CPPAN / Cmake
git clone https://github.com/tesseract-ocr/tesseract tesseract
mkdir Win64 && cd Win64
cppan ..
cmake .. -G "Visual Studio 15 2017 Win64" -DCPPAN_USE_CACHE=0 (this was useful step to actually allow the proper compilation for me.
Updated the CPPAN and uncommented on the generator string
cppan --generate .. - generated the solution files.
Opened up in Visual Studio - selected the release version
8.1 - Set the openmp feature (Disabled for myself)
Built the version.

I do get the EXE / DLL file - but what i got was tesseract dll (probably required for the main executable) but i was not able to build in libtesseract.dll
I was not able to able to genera the libtesseract.dll - the same that i see as output generated in this following GIT.
With this given lib file - i could also have loaded up in python and execute barebone stuff - not all - just barebone - but atleast it ran through. But with the ones built with the compilation from visual studio - i was not able to build things that i could load up in my python application.
It will be great if you guys can help me build up stuff - where i failed - what can i do to get it right.
Thanking you in advance.

When you say you can’t build libtesseract.dll, do you mean that you had compilation errors or do you mean that no dll was created by the name libtesseract.dll.
What were the errors?

There was no dll created by the name libtesseract.dll
There were warnings but no error.

Open …\Win64\tesseract.sln with Visual Studio.
Select Solution Explorer tab.
Right click libtesseract from the tree (the project) and choose Properties.
Under General | Target Name note the name of the dll that will be created and the Output Directory.  Look for the Target Name file in the Output Directory in your filesystem.


trying out build with newer travis system

not sure if this will work since I removed the rm rvm lines.
We'll see if the c language has rvm installed in it.

looks like this has already been fixed.
Great gem - thanks


fix:operationID is ResourceFuncName

fix:operationID is ResourceFuncName

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 1886

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
15 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.1%) to 66.521%

Files with Coverage Reduction
New Missed Lines
%

core/config/sd_config.go
2
0.0%

eventlistener/loadbalance_event_listener.go
2
66.67%

core/invoker.go
2
50.0%

core/config/config.go
9
69.23%

Totals

Change from base Build 1885:
0.1%

Covered Lines:
5774

Relevant Lines:
8680

💛  - Coveralls


Add support for default field value

https://github.com/tacowordpress/tacowordpress/commit/779d4bcedc2581b4517dca2e988b2b12427c2a88


[WIP] Initial SimpleSerialize (SSZ) spec

Initial specification outline for SSZ for #2.

Basic information about serializing types.
Basic information about deserializing types.
Checks to be performed for sanity.
Links to implementations.

TODO:

Ensure all implementations are listed.

There has been some discussion about ssz so if you notice any discrepancies would be great to have any input for changes :smile:.
Also, if I've forgotten an implementation feel free to update the implementation list. There are some eth2.0 implementations that do not use ssz at this point in time (that I could see), but if I couldn't see it please make sure to add them.
Any help is appreciated, especially in terms of readability and making it easier to understand. We appreciate your time!

I think we should also add the test format once it has been finalised.
Thoughts? :smile:

Thanks @hwwhww  :smile:

Thanks @mratsim for the excellent comments!
I'll provide the updates shortly! :smile:

I'm going to give it a look this morning and merge. Just need to make sure some sort of "work in progress" signal is at the top of the doc

Added Updates

Changed title to include explicit WIP status.
Updated Hash types to include hash96 and hash97 for BLS.

Note: It may be a point of discussion how this should be implemented. At this moment we went for simplicity and assumed it will be similar to the uint serialization technique.

Updated List to List/Vector and added @mratsim's suggestions.

There are currently 2 items that are to be discussed:
Container Serialization (@mratsim's comment):

Nice work!
One thing that is missing are "container types" serialization, for example ActiveState
# ActiveState
fields = {
    # Attestations that have not yet been processed
   'pending_attestations': [AttestationRecord],
    # Most recent 2 * CYCLE_LENGTH block hashes, older to newer
    'recent_block_hashes': ['hash32']
}

I feel like this should be an open discussion around the appropriate methods of serializing a container.  @AlexeyAkhunov may also have input.
List/Vector Serialization
@mratsim's comment:

The perf notes are to address the problem highlighted by @AlexeyAkhunov, if the container does keep > track of its length (for example LinkedLists) prefixing the length is inefficient.

You can refer to this post: #2 (comment)

On length prefix vs length suffix
ethereum/beacon_chain#94 and ethereum/eth2.0-pm#8

The argument for moving at the end is because otherwise you would have to iterate on the data structure once to get the length then once again to get feed the data. ==> All languages even Haskell have a vector implementation that tracks length so you wouldn't need the first iteration to get length.
Furthermore putting length at the end means you need specific token to indicate end of data like ‘\0’ in cstring. This is causing a lot of issue in C code also this prevents reading by chunk into a buffer, you would have to read token by token (or read by chunk and backtrack).

It might be appropriate like @hwwhww suggested to make this a separate discussion.
Thanks for all the input :smile:

Thanks @djrtwo! All applied :smile:. Thanks for the excellent comments!

@NatoliChris Let's add a "TODO section/note" in the document for "container types" to make it clear it's missing.
After that, I'll merge this

Done :smile:
Thanks again @djrtwo !

Excellent. Thanks!


feat(actix): basic implementation of actix

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Migrations
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description
Basic implementation of actix_web now health route can be hit and checked via localhost/health
Additional Changes

[x] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

How did you test it?
locally
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

I still see the unwanted lines in CI file


Add Type Support for Multibanco and Twint

Summary & motivation

Adds type support for Multibanco and TWINT, since both are now GA
Testing & documentation
Automated tests in tests/types/src/valid.ts.

r?


WIP: [nginx-ingress-controller] Add support for rate limiting in ingress rule locations

Mostly similar comments to those in the rewrite pr (https://github.com/kubernetes/contrib/pull/1079). I think we should err on the side of caution and leave as many explicit examples and send as many events as we can, when exposing site specific features through annotations, because it's so easy to get wrong. Both from a user perspective, and from a cross-platform perspective (i.e I look at how the nginx controller is handling redirects to make sure it's the same for other platforms)

LGTM but you have a merge conflict

done


feat: Build images prior to rollout in docker compose buildpack.

Currently rolling deployments for docker compose builds is not supported. The existing containers are stopped before new ones are built and deployed, which means there can be a lengthy downtime if the build time is significant.
The next best thing is the ensure the images are built and pushed to the dockerhost prior to restart to limit the downtime to near zero.

Thanks for the PR! It makes sense and great improvement!


Removing internal config and retry packages

Description
Removing internal config and retry packages that were moved to dapr/kit
Issue reference
Closes: #893
Checklist

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/cc @yaron2 @artursouza

lgtm


Inflation bonds - pricer

Inflation bonds: create pricer with at least the conventions for US (TIPS), France (OATi, OATie), and UK (Gilts)
Risk measures

present value
curve sensitivity (including inflation)
current cash
clean real price
dirty real price
accrued interest
duration
modified duration
convexity

France still to do

CapitalIndexedBond added


How to use libs such as ffmpeg, opencv etc

Hello !
I've started CEP development with your super cool generator (thanks so much for creating that).
I was wondering if using libs such as ffmpeg, youtube-dl, or opencv in Adobe CEP would be possible ?
For what I understand Adobe uses NW.js. I think I would have to make static builds of the binaries I want to use for Windows & Mac.
But then how would you create 2 builds of the Extension with the right binaries in it ? Is that even recommended ?
Thanks !

Hello! Sorry for the late reply, I've not needed to do this personally but I'm checking with a few people to get an answer for you. Thanks for using the library!

I'm currently using FFMPEG in a project. I've added the mac/win ffmpeg executables to the project that brings the ZXP file size to around 45mb. It's using exec to run ffmpeg in the command line.
`import util, { log } from 'util'
const exec = util.promisify(require('child_process').exec);
let ffmpeg = this.csInterface.getSystemPath(SystemPath.EXTENSION) + '/src/ffmpeg/ffmpeg'
let fileIn = renderData.layerName + '.' + renderData.ext
let fileOut = renderData.layerName + '.mp4'
async function ffmpegCompress() {
const { stdout, stderr } = await exec('"'+ ffmpeg +'" -y -i "'+ path + '/' + fileIn +'" -c:v libx264 -preset slow -crf 6 -vf yadif -strict -2 -pix_fmt yuv420p "'+ path + '/' + fileOut +'"');
console.error('stderr:', stderr);
return {
fileIn: path + '/' + fileIn,
path: path + '/' + fileOut,
layerName: renderData.layerName,
framelength: renderData.framelength,
}
}`

In addition to what Adam's said, I posted this to the Adobe Devs Slack and got an answer from @ericdrobinson:

@Tom Scharstein You can’t build static native stuff targeting the NW.js core in CEP. Adobe doesn’t give us enough to do so. However, that’s not what the user is doing: they’re simply including the static FFMPEG binary and executing it with exec. That is doable.

His real question is this:

But then how would you create 2 builds of the Extension with the right binaries in it ? Is that even recommended ?

You would still just make the one “build”. However, you would probably do this:

put the Windows static ffmpeg binary in bin\ffmpeg\win
put the macOS static ffmpeg binary in bin/ffmpeg/mac

Then you would make sure that the path you specify switches between the two based upon the executing environment.

Accessing the execution environment inside a .vue file can be done via process.platform or cep_node.process.platform if needed for certain binaries though Adam's also solved it above without doing so for ffmpeg

I have both of the mac and win versions sitting in src/ffmpeg and tested on mac and win with no trouble. It seems to auto target the correct version without needing to test for which version. I guess thats just a part of exec.

Thank you so much guys, that really helps !


Adding floorist plugin tests to pr_check.sh

RHINENG-12132

The changes here were implemented in https://github.com/RedHatInsights/policies-ui-backend/pull/693 . I am closing.


Batching

the codex part of https://github.com/Comcast/codex/issues/61

Codecov Report

Merging #73 into master will decrease coverage by 1.43%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##           master      #73      +/-   ##
==========================================
- Coverage   59.22%   57.78%   -1.44%
==========================================
  Files          17       19       +2
  Lines         949     1040      +91
==========================================
+ Hits          562      601      +39
- Misses        348      400      +52
  Partials       39       39

Impacted Files
Coverage Δ

db/batchInserter/batchInserter.go
0% <0%> (ø)

db/retry.go
97.29% <100%> (+8.83%)
:arrow_up:

db/batchInserter/metrics.go
71.42% <71.42%> (ø)

Continue to review full report at Codecov.

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


Auto-import without nested imports

I've been using Rust since before 1.0, and I still use the same style of imports as before nested imports were added in Rust 1.25. See the first example here:
https://doc.rust-lang.org/edition-guide/rust-2018/module-system/nested-imports-with-use.html
I prefer
use std::fs::File;
use std::io::Read;
use std::path::{Path, PathBuf};

instead of
use std::{fs::File, io::Read, path::{Path, PathBuf}};

I feel like it's not bad to prefer using that style since it's the only style Rust supported ~3 years. However, when you use auto-import, ra will merge the new import with an existing one that it chooses. I would really like to use auto-import, but I don't for this reason. Some projects support an older version of Rust than 1.25, like Serde supporting 1.13, so you also couldn't use auto-import when working on them.
I would like an option to have auto-import not use nested imports.

Yup, we definitely need to toggle for this.  But this is currently blocked on rewriting our import-insertion infra to work with syntax trees and not raw text: https://github.com/rust-analyzer/rust-analyzer/issues/3301#issuecomment-592931553

I'd also like this.
Supporting rationale: when nested imports are used you can end up with a HUGE amount of imports for the current crate and they seem to end up as one long line, which makes finding unused ones tricky.
I don't know if Rust-Analyzer has it yet, but it would be nice if when adding imports it kept the list 'nice':

Sorted by line
Sorted by name within the line
Long lines wrapped appropriately
Removed unused imports

Please this. A potential workaround would be to make merge_imports = false from rustfmt actually remove nesting (which I think it should do), but this is currently not the case.

This should already be possible with #5935, but I haven't tested it yet.

Yeah, I believe this is fixed now. The relevant config is "rust-analyzer.assist.importMergeBehaviour": "none",

It doesn’t seem to work on RA v0.8.0. I have set none and it still merges them.

Current behavior:

This works on master in VS Code. Could you try rebuildin rust-analyzer from source (or just waiting for a release later today)?
Alternatively, maaaybe coc-rust-analyzer needs to be upgraded to learn about the new config option (don't know how config is setup for it)?.

I’m rebuilding it right now and trying in coc-nvim. I’ll let you know when it’s cooked. Thanks for the fast replies.

(and yes I have updated the coc config)

Okay, it indeed works with the latest build; thanks!

Argh, sorry to bother again @matklad but I think I have found a weird… situation. So even though it now works, it also splits things like std::path::{Path, PathBuf} on two different lines, which I dislike. Any idea how to fix that?

Yeah but then it would put things like fs in std::{…}, and then when using something from fs only, it would do a use fs::…, which I really don’t like. I guess I’ll have to give up on what I want and switch to full and have them all nested and stop worrying about it… :(

@phaazon could you provide a minimal self-containd example for fs issue, with behavior you get with last, and behavior you want? This is a fresh feature, there may be bugs!

use std::fs::{self, File};

fn foo() {
    FileType
}

If you import FileType, you get:
use std::fs::{self, File};

use fs::FileType;

The empty line looks like a bug to me, but adding a new use seems both correct and undesirable.

So I guess the idea here is to not add new imports starting from paths already imported.

Yeah, I think we have a similar issue even with nested imports

This problem is the one thing that was missing from the PR in regards to inserting imports. Ideally the insert_use assists should go through the existing imports to check if the start of the path is imported somewhere already and merge that into that tree if it exists instead.

@Veykril filed https://github.com/rust-analyzer/rust-analyzer/issues/6071. I think the problem here is not that auto-import inserts fs::File in the wrong place, but that we tell it to insert fs::File (as opposed to std::fs::File).


No answers to questions

Within the data folder there are a number of pdfs but if i ask questions like the ones in the video they dont knwo the answer - how do i check this and how would i upload my own data for me to be able to ask it questions on say a pdf i uploaded myself?

In our experience, we've found that this model requires more prompting to decide to search the knowledge base. For example, with the sample data, I always say "Hello", and then once they respond, I ask "What is the whistleblower policy for Contoso Electronics?"
We need to experiment with more prompt engineering or perhaps few-shot examples to get it to more reliably search the knowledge base.
To upload your own data, assuming you used "azd up" for deploying from scratch:
add the files to the data/ folder, then rerun ./scripts/setup_intvect.ps1 or ./scripts/setup_invect.sh

I'm trying to find a better way to prompt an AI model to search the knowledge base more often or always. I've tried changing the tool_choice from "auto" to "required" and using {"type": "function", "function": {"name": "search"}}, but these either caused endless loops or didn't work at all. Do you have any insights or suggestions on how to handle this? I'd really appreciate your help!

@Piesson I haven't done much prompt engineering for this RAG app, but for others using function calling, I've found it helpful to provide few-shot examples. Here's an example of the format: https://github.com/Azure-Samples/rag-postgres-openai-python/blob/main/src/backend/fastapi_app/prompts/query_fewshots.json
It would need to match the format of the search tool used in this app.


Add support for DISQUE_SERVER

Allow Disque to pull config from environment variables to mirror functionality already present in Redis.pm

Thanks ! 👍
Looks good.


Return Range from rangeFromLineNumber

Fixes #83

I'm a bit surprised that ::serialize() returns an array and not the full object representation, but I guess that makes the spec diff small.
LGTM


Remove duplicate -Wall flag

The tasty-travis template got into a state where it had 2 -Wall flags for each executable (exec, benchmark, test suites).

Thanks!


ChannelWiseDivergence unused variable

In mmseg.distillation.losses.cwd.ChannelWiseDivergence the student softmax output is not used (also self.name):
softmax_pred_S = F.softmax(preds_S.view(-1,W*H)/self.tau, dim=1)
Intended or a bug?

Thanks for your attention !
The arg is deprecated.
If you want to distill model in OpenMMLab related repos, could join the wechat group in README.md


repeat configuration

Repeat configuration is a bit misleading.
Seems like 0 repetitions should not produce any confetti?
Did I miss something?
Expected Behaviour
code:
.confettiCannon(counter: $counter, repetitions: 3, repetitionInterval: 0.7)

produces 3 repeats
Actual Behaviour
code:
.confettiCannon(counter: $counter, repetitions: 3, repetitionInterval: 0.7)

produces 4 repeats
every time repeats count greater by '1' than expected
Steps to Reproduce the Issue
use any repetitions value in Repeat Configuration and compare with result.
even in README
.confettiCannon(counter: $counter, repetitions: 3, repetitionInterval: 0.7)

produces 4 repeats

PR is open.


smoke_catalina_hot_mode_dev_cycle__benchmark hotReloadMillisecondsToFrame & hotReloadMillisecondsToFrame above baseline

After the fix to https://github.com/flutter/flutter/issues/54368 in https://github.com/flutter/flutter/pull/54374, these benchmarks remain slightly above the baseline. Should we re-baseline them?

cc @jonahwilliams

I tried to rebaseline the benchmarks. I don't think there is an actual regression here, just a gradual increase

I think the website is still cached, I'll wait a bit to make sure these are still green.

All of the benchmarks have been re-baselined


Autoscaled nodes not joining cluster

Hello!
We are running Hetzner-k3s version 2.0.8 with the following worker pool config:
worker_node_pools:
- name: med-static
  instance_type: cpx31
  instance_count: 3
  location: hel1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 6

The nodes are created in Hetzner after autoscaling is initiated by stressing the cluster but they are not joining the cluster after that. We can ssh into the machines but they don't have for example ssh keys set or anything related to k3s installed. For static nodes the ssh keys are set correctly.
We think this has something to do with the previous cloud init wait problem in issue https://github.com/vitobotta/hetzner-k3s/issues/379
If we read the code correctly the cloud_init_wait.sh script is not called when creating a autoscaled node?
We are running a private network only cluster. Regarding to this PR https://github.com/vitobotta/hetzner-k3s/pull/458 our cloud init takes several minutes with both static and autoscaled nodes.

Hi, can you share your full config file (minus the token)?

Hi, this has been reported a couple of times before but I haven't had a chance to try and reproduce the problem yet. Can you share more details on how you have configured the network in Hetzner? The more details the better as they might help me understand where the problem might be.

Hi, I have the same problem. Is there any known config to work? my network config is same as static workers, but after autoscaling and waiting some minutes, I cannot ssh into the autoscaled worker and  it is not joining the cluster.
- name: medium-autoscaled
  instance_type: cpx31
  instance_count: 1
  location: hel1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 4
  image: debian-12
  additional_packages:
  - ifupdown
  post_create_commands:
  - ip route add default via <IP_ADDRESS>  # Adapt this to your gateway IP
  - echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf

Hi, I have the same problem. Is there any known config to work? my network config is same as static workers, but after autoscaling and waiting some minutes, I cannot ssh into the autoscaled worker and it is not joining the cluster.
- name: medium-autoscaled
  instance_type: cpx31
  instance_count: 1
  location: hel1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 4
  image: debian-12
  additional_packages:
  - ifupdown
  post_create_commands:
  - ip route add default via <IP_ADDRESS>  # Adapt this to your gateway IP
  - echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf

The problem is, the few reports I've come across about these issues all involve some custom commands to tweak the network settings, and that's something I haven't checked yet. So far, with the default network configuration, I haven't been able to recreate any of those problems.

so it might have to do with "private network only" setup? - because thats my only real difference - using a NAT routing VM for Internet access from inside the cluster.

Same here. Just trying the generic cluster_config.yaml and the following section:
...
worker_node_pools:
- name: small-static
  instance_type: cpx21
  instance_count: 2
  location: hel1
  # image: debian-11
  # labels:
  #   - key: purpose
  #     value: blah
  # taints:
  #   - key: something
  #     value: value1:NoSchedule
- name: medium-autoscaled
  instance_type: cpx31
  instance_count: 1
  location: fsn1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 2

"medium-autoscaled" doesn't get created.
Full config:
hetzner_token: <my token>
cluster_name: saashqcloud
kubeconfig_path: "./kubeconfig"
k3s_version: v1.30.3+k3s1

networking:
  ssh:
    port: 22
    use_agent: false # set to true if your key has a passphrase
    public_key_path: "~/.ssh/id_rsa.pub"
    private_key_path: "~/.ssh/id_rsa"
  allowed_networks:
    ssh:
      - <IP_ADDRESS>/0
    api: # this will firewall port 6443 on the nodes
      - <IP_ADDRESS>/0
  public_network:
    ipv4: true
    ipv6: true
  private_network:
    enabled: true
    subnet: <IP_ADDRESS>/16
    existing_network_name: ""
  cni:
    enabled: true
    encryption: false
    mode: flannel

  # cluster_cidr: <IP_ADDRESS>/16 # optional: a custom IPv4/IPv6 network CIDR to use for pod IPs
  # service_cidr: <IP_ADDRESS>/16 # optional: a custom IPv4/IPv6 network CIDR to use for service IPs. Warning, if you change this, you should also change cluster_dns!
  # cluster_dns: <IP_ADDRESS> # optional: IPv4 Cluster IP for coredns service. Needs to be an address from the service_cidr range

# manifests:
#   cloud_controller_manager_manifest_url: "https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.20.0/ccm-networks.yaml"
#   csi_driver_manifest_url: "https://raw.githubusercontent.com/hetznercloud/csi-driver/v2.9.0/deploy/kubernetes/hcloud-csi.yml"
#   system_upgrade_controller_deployment_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/system-upgrade-controller.yaml"
#   system_upgrade_controller_crd_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/crd.yaml"
#   cluster_autoscaler_manifest_url: "https://raw.githubusercontent.com/kubernetes/autoscaler/master/cluster-autoscaler/cloudprovider/hetzner/examples/cluster-autoscaler-run-on-master.yaml"

datastore:
  mode: etcd # etcd (default) or external
  external_datastore_endpoint: postgres://....

schedule_workloads_on_masters: false

# image: rocky-9 # optional: default is ubuntu-24.04
# autoscaling_image: 103908130 # optional, defaults to the `image` setting
# snapshot_os: microos # optional: specified the os type when using a custom snapshot

masters_pool:
  instance_type: cpx21
  instance_count: 3
  location: nbg1

worker_node_pools:
- name: small-static
  instance_type: cpx21
  instance_count: 2
  location: hel1
  # image: debian-11
  # labels:
  #   - key: purpose
  #     value: blah
  # taints:
  #   - key: something
  #     value: value1:NoSchedule
- name: medium-autoscaled
  instance_type: cpx31
  instance_count: 1
  location: fsn1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 2

embedded_registry_mirror:
  enabled: false # Check if your k3s version is compatible before enabling this option. You can find more information at https://docs.k3s.io/installation/registry-mirror

# additional_packages:
# - somepackage

# post_create_commands:
# - apt update
# - apt upgrade -y
# - apt autoremove -y

# kube_api_server_args:
# - arg1
# - ...
# kube_scheduler_args:
# - arg1
# - ...
# kube_controller_manager_args:
# - arg1
# - ...
# kube_cloud_controller_manager_args:
# - arg1
# - ...
# kubelet_args:
# - arg1
# - ...
# kube_proxy_args:
# - arg1
# - ...
# api_server_hostname: k8s.example.com # optional: DNS for the k8s API LoadBalancer. After the script has run, create a DNS record with the address of the API LoadBalancer.

Hey @saashqdev, do you have any pods that are waiting for resources that aren't currently available in the cluster? If not, the autoscaler won't do anything.

Ah, no I don't. I'll take it out then. Thanks

You can keep it, so it scales automatically only when actually needed :)

ok no problem. We still get the medium auto-scaled worker pools not showing tho

So, as I was saying, the autoscaler will only add new nodes when there are pods waiting to be deployed and the cluster doesn’t have enough resources to handle them. If the cluster already has enough resources or if you’re running workloads without specifying the needed CPU and memory, the autoscaler won’t take any action.

Since my last post to this issue,  I exactly followed Vito's Documentation with a new cluster project. Autoscaler works with no issue, as long as you DO NOT USE PRIVATE IP.
The root cause must be somewhere there, when you only have private IPs on your virtual metal and need NAT router to talk to Internet from the nodes.


localize/load integration docker images up-front

Currently docker images are loaded after data localization. Should be done up front in case of errors and to prevent potential wasted cost when egressing out large numbers of dataset inputs (e.g. time-series).

Implemented in https://github.com/hysds/hysds/commit/e61519d8373390698911f43aa4275487222d9dc4. Tested end-to-end using S1 QC ingest.