Wall Light positions getting garbled using EXPORT NMS

I honestly don't know if this is an issue with the mod or simply a native wall light limitation a/o the sheer number of objects intersecting in such close proximity, but all seems fine in blender until I export the objects--then the positions get garbled.
Before Export (36 parts total)

After Export

I first noticed it when I made a typeface composed of wall lights and added a pangram specimen to a series of walls erected at an existing base in the game. When the result looked like gibberish, I went back to Blender to see if I could remedy the problem there.
Character set + pangram == 630 parts

Specimen test BEFORE EXPORT

Specimen test AFTER EXPORT

I tried making the specimen a preset to see if that made nay difference (it didn't).
Preset test BEFORE EXPORT

Preset test AFTER EXPORT

Can I see what the transformation data looks like on a wall light? I imagine the text generation tool is introducing some scaling/sheering which I'm not really accounting for in the NMS tool.
If you go to the blender item properties and look for the location, rotation, scale values and pose a screenshot.
Or you can just attach the blender file and I can look inside :)

Bender specimen file attached.
volfont-ltd-specimen.zip

I did change the origin on the first set of lights that were duplicated and then used everywhere else.

This is your problem :)
Changing the origin basically gives you a misrepresentation of where the object actually is. NMS is only concerned with the origin/transform data to position it's objects. As you've moved the origin to the edge, the objects are going to shift the other way when they are re-imported. The origin information you've changed isn't being tracked by the tool.

I'm a complete Blender newb, but as soon as I posted that I thought maybe that might be the problem.
Thanks for confirming.
Back to the drawing board.

No worries, let me know how it goes! :)

Thanks again for the prompt response.
As it happens, most of the problem was solved by having the culprit revisit the scene of the crime: Set Origin > Origin to Center of Volume (Mass). I applied that, en masse, which placed the origin for each selected light pretty close to where it is natively. I used EXPORT NMS, then turned right around and imported it all back into Blender. That did the trick. I made a few adjustments, then composed some hasty specimens:

It has warts, but I'm still finessing. I fully intend on contributing some presets once I have something ready.

Very nice! :)

I would like to become a contributor to No Man's Sky Base Builder Presets
(but could not find another way to message you through GitHub, other than
this).
My github: https://github.com/davebastian
Thanks. That is all.
On Thu, Oct 22, 2020 at 2:22 PM Charlie Banks<EMAIL_ADDRESS>wrote:

Very nice! :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/charliebanks/nms-base-builder/issues/55#issuecomment-714739211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE372IBOGNNWVYFVCRW4IL3SMCH7JANCNFSM4SXQRKBQ
.

Done :)


re-link from beta1 to stable documentation of kubelet-config.v1

The introductory paragraph of the english documentation for "Configuring a cgroup driver" discusses differences between kubelet's systemd and cgroupfs driver usage in the context of kubeadm. Here is an outdated reference to an older beta version of the "Kubelet Configuration" documentation (kubelet-config.v1beta1). Shouldn't we point to the current documentation for the stable v1 release (kubelet-config.v1)? This PR fixes #41587

just tested the newly generated link on netlify's PR deployment: cgroupfs driver documentations link on "Configuring a cgroup driver" now points as expected to current stable v1 version of "Kubelet Configuration" documentation.

No. The KubeletConfiguration struct is defined in kubelet.config.k8s.io/v1beta1.
Currently, there is only one struct graduated into kubelet.config.k8s.io/v1, which is CredentialProviderConfig.
/close

@tengqm
ok, i see in kubelet.config.k8s.io/v1 are many structs missing e.g. KubeletConfiguration which exists in kubelet.config.k8s.io/v1beta1 and is also referenced by other documentation pages.
I don't want to prolong this unnecessarily so i have to apologize in advance for my further question.
I don't quite understand the current situation: kubelet is in stable release, but the documentation for it is in beta? Then what's the sense of kubelet.config.k8s.io/v1 page in the documentation?

@tengqm ok, i see in kubelet.config.k8s.io/v1 are many structs missing e.g. KubeletConfiguration which exists in kubelet.config.k8s.io/v1beta1 and is also referenced by other documentation pages.
I don't want to prolong this unnecessarily so i have to apologize in advance for my further question. I don't quite understand the current situation: kubelet is in stable release, but the documentation for it is in beta? Then what's the sense of kubelet.config.k8s.io/v1 page in the documentation?

Kubernetes components used to use command line flags for customization and then people introduced configuration files for the same purpose. The reason is for easier maintenance of the configurations (as a structured YAML). There was a hope that these configurations for kubelet can be centralized at the API server, but that effort wasn't successful. With that said, the configuration struct is still not mature, no matter how the component itself is mature. The same goes with the configuration for kube-scheduler or kube-controller-manager.
We leave the sig-node team to decide whether the KubeletConfiguration is stable. AFAICT, some of the configurations can be migrated into a shared library. Changes like this are not uncommon in the community. v1beta1 is a good version for this struct, IMHO.


Issue of code generation when using type field reservation word field

If the field in the input schema is a reserved word, the Pair value of the fields method of the generated code is missing a backup (`) resulting in a compilation error.
Is there any way to solve the above issue?
used codegen version: 6.0.3
Example Type
type SampleType {
  return: String!
}

Generated Class
@JsonTypeInfo(use = JsonTypeInfo.Id.NONE)
@JsonDeserialize(builder = SampleType.Builder::class)
public class SampleType(
  `return`: () -> String = returnDefault,
) {
  private val _return: () -> String = return // error

  @get:JvmName("getReturn")
  public val `return`: String
    get() = _return.invoke()

  public companion object {
    private val returnDefault: () -> String =
        { throw IllegalStateException("Field `return` was not requested") }

  }

  @JsonPOJOBuilder
  @JsonIgnoreProperties("__typename")
  public class Builder {
    private var `return`: () -> String = returnDefault

    @JsonProperty("return")
    public fun withReturn(`return`: String): Builder = this.apply {
      this.return = { return } // error
    }

    public fun build() = SampleType(
      return = return, // error
    )
  }
}

gradle
tasks.withType<com.netflix.graphql.dgs.codegen.gradle.GenerateJavaTask> {
    generateClient = true
    generateDataTypes = true
    snakeCaseConstantNames = true
    generateKotlinClosureProjections = true
    generateKotlinNullableClasses = true
    language = "kotlin"
}

Parameters are created with backup, but assignments are not made with backup

Fixed here (pending build/merge/release): https://github.com/Netflix/dgs-codegen/pull/623
I'm still unsure how these reserved word issues regressed, but now we have tests to lock in the behavior


Add label option to Marker

Fix #69

Hello @tonydspaniard
Can you take a look at this?
It's a very simple PR but the lack of this label is preventing me from using the extension.
Thanks!


[MM-15407] Fix fastlane for PR build

Summary
Fix Fastlane for PR build.  This fixes issue where PR builds are not correctly upload into its correct path and not sending success message to Mattermost webhook.
Follow up PR to https://github.com/mattermost/mattermost-mobile/pull/2796
Community server report (EN) - https://community.mattermost.com/core/pl/s86imt8i37gxtbi7amxcxcczkr
Ticket Link
Jira ticket: MM-15407

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.plist

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.plist

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2804/PR-2804.plist

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.


Readme update

I had a lot of trouble understanding why my app would not load. It turns out that the answer was at the bottom of the README. I've the moved required configuration up to the installation section and made some minor edits. This should help some other users.

Wow! I cannot stress how important that readme update is. It should be even made more prominent that the deviceready event may never fire, if the plugin is included in a cordova app but never configured.
We spent one (!) week trying to out find out why the app would randomly not start.
This should be merged as soon as possible and the plugin should behave with that config by default, meaning nobody should need to set those preferences in the first place.

@pke, are these config.xml updates resolving the https://issues.apache.org/jira/browse/CB-11089?

@daserge it's possible. There are a number of other reasons that the deviceReady event does not fire, this is one of them.

@daserge no, they do not solve this problem. I have not set splashscreen delay to 0, fade to 0 and the darn screen is still NOT hiding when hide() is called. How can such a simple operation be so broken?

@laidig the deviceready event does fire, the app starts fine and is running behind the splashscreen all along.

If deviceready fires, then wkwebview loaded, so this would not be the
problem.
dumb question: have you added and removed the plugin?
On Wed, Jun 15, 2016 at 11:01 AM, Philipp Kursawe<EMAIL_ADDRESS>wrote:

@laidig https://github.com/laidig the deviceready event does fire, the
app starts fine and is running behind the splashscreen all along.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/cordova-plugin-wkwebview-engine/pull/9#issuecomment-226215016,
or mute the thread
https://github.com/notifications/unsubscribe/AAwdPaofVNMJKgo9zixyBb5ZNr9_q0w_ks5qMBOtgaJpZM4IXew7
.

Those settings are set by the CLI from the plugin.xml. They are explicitly put in the README to show what permissions are needed by the plugin.
It might be a splashscreen bug.

In my case the problem was that the wkwebview does not work well with async loaded script files.
I had
<script src="cordova.js" async/>
<script src="bundle.js" async/>

As soon as I removed the async attribute (after one week of trying other things) everything worked, including the splashscreen. I think the splashscreen uses the message queue (event loop) to postpone some of its actions (when fading out) and this collides with the async attribute and creates a race-condition. It seems like a bug in wkwebview to not handle async script loading properly.

@shazron any testing that I could help with?

@laidig it is not set in your root config.xml, but the platform's config.xml (under platforms/ios/projectname/config.xml) since the settings are only for the ios platform.
thanks @pke for that information. do you mind adding a bug for it, so I can tag it as a known issue?

@shazron sure: https://issues.apache.org/jira/browse/CB-11469
I guess its historical reasons why issues are not tracked directly here in GH?

@pke thanks! Historical, and permissions granularity issues. Apache is working on it so we can use GH issues, but that's still a ways off (in testing phase).


Can an Apfloat number be rationalized?

There is a constructor for double:
  Aprational(double value)

is  it also possible to have a constructor (or valueOf method) which converts an approximate number Apfloat to a "nearby" rational  Aprational?
  Aprational(Apfloat value)

Somebody once suggested this (by email)
Basically, the algorithm is to calculate the continued fraction for the given Apfloat and then take the n:th convergent to get a rational approximation of the floating-point number (the bigger the n, the better the approximation)
The corresponding function in Mathematica is Convergents
It currently isn't implemented in the apfloat library but I suppose it shouldn't be that hard to implement


Error

An error occured while trying to parse the .env file. ENOENT: no such file or directory, open '/c:/xampp/htdocs/portal1/.env'

Windows seems to be adding an extra "/" to the path. I'm looking into it.

facing the same issue

Same issue as well.

same issue as well

same issue

An error occured while trying to parse the .env file. ENOENT: no such file or directory, open '/c:/xampp/htdocs/portal1/.env'

I have fixed this issue in windows, and I have shared a pull request or you guyz can download vsix file from here https://github.com/wahhabc23/laravel-eloquent-model-attributes

An error occured while trying to parse the .env file. ENOENT: no such file or directory, open '/c:/xampp/htdocs/portal1/.env'

I have fixed this issue in windows, and I have shared a pull request or you guyz can download vsix file from here https://github.com/wahhabc23/laravel-eloquent-model-attributes

Thanks for that but since this plugin hasn't been maintained for sometime now I think someone should take over and maintain or add new features to it as well, it has potential

An error occured while trying to parse the .env file. ENOENT: no such file or directory, open '/c:/xampp/htdocs/portal1/.env'

I have fixed this issue in windows, and I have shared a pull request or you guyz can download vsix file from here https://github.com/wahhabc23/laravel-eloquent-model-attributes

Thanks. I published the new extension and added you as a contributors to the README.


The 'Showing Time Elapsed/Remaining' example from README doesn't look like in README

Instead it looks like this:

Do you see this issue if you lower the bar width? This typically happens because the progress bar total width (prefix text + bar + postfix elapsed/remaining text) is larger than the width of the terminal

Do you see this issue if you lower the bar width? This typically happens because the progress bar total width (prefix text + bar + postfix elapsed/remaining text) is larger than the width of the terminal

Hello, can you check if this still happens after this commit https://github.com/p-ranav/indicators/commit/4790bfddcad6ff3bd814584083e7490c096a3a2b?

This is still happening with 4790bfd
Lowering bar width to 10 doesn't help.
xfce4 terminal (xfce4-terminal-<IP_ADDRESS>)

I have the same problem

I have met the same problem, and I find that the reason lies in the symbol "👀". Actually, if "👀" is used in the PrefixText, other progress bars will also have this problem mentioned by Yurivict.


Update atleast 5 landmarks for every city present in cities.json

There should be atleast 5 landmarks for a specified city.

Hi @thenishantsapkota
Do you mean, as a part of the PR we must ensure that the json object at https://github.com/Know-Nepal/borderlines/blob/main/data/borderlines.json contains at least 5 landmarks for each of the already added cities?

Yes that's exactly my intention, atleast there must be 5 landmarks per city @dyaramatreya

Assigned it to you @dyaramatreya!

@thenishantsapkota Linked the PR #17 . Please review and approve the PR. Thanks


Config maxUnackMessagesPerConsumer and maxUnackMessagesPerSubscription on a namespace

For now, we can config maxUnackMessagesPerConsumer and maxUnackMessagesPerSubscription in broker.conf.
It's useful to support config it on namespace level to overwrite global broker config.

The issue has been fixed in #5936


Feature/combined updates

Description

Add MSSQL active directory auth per https://www.terraform.io/docs/providers/aws/r/db_instance.html#domain
Bump pre-commit versions and run pre-commit to generate documentation changes
Mark database password output as sensitive to avoid exposing in stdout output
Correct usage of name and name_prefix on option group, subnet group, and parameter group. Previously all defaulted to use a prefix but there are now 3 scenarios supported (as was the original intent I believe). a user can provide a name to an existing group to use (create flag = false), a user can provide a name to create a new group (create flag = true), a user can provide a name prefix to create a new group (create flag = true && use prefix = true).
Add support for certificate authority setting and its associated output
Add delete timeout configuration for option group, currently set to resource default
Subnet group, option group, and parameter group names and the database instance identifier have been made lowercase as this is either required and/or when created manual they will be converted to lowercase (tested through console)
The use of name, name prefix, and identifier have been updated to be consistent. when a group name is not provided, the db instance identifier will be used, and likewise for name prefix. the Name tag was updated to be consistent with what is selected from the above coalesce results to be consistent

This PR is rather quite large but that is because it culminates a lot of changes that have been building up in open PRs that have either gone stale, did not function as intended, etc. I have tested and validated these changes and they appear to be working as intended - currently this setup is used in production on a MSSQL instance without issue as  well. Hopefully we can get this resolved quickly, let me know if I can be of any help!
Note - at minimum this supersedes and closes the following PRs if merged: #177, #98, #121, #115, #175, #145 - there may be more but that can be determined after resolution

@antonbabenko let me know if there is anything I can do to help speed up the review process and get to a resolution, thank you!


Add support for fragment only pipelines

What we need:

an empty vao
a vertex stage with the glsl main(){}
a geometry shader which emits a fullscreen quad
call (gl:draw-arrays :points 0 1) to draw

This is allowed in GL Core for all versions we need

Done


Add helpers header for working with CPython in C++ tests

Followup to comment on https://github.com/skupperproject/skupper-router/pull/524

Codecov Report

Merging #526 (c3a9786) into main (6aaadd5) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #526      +/-   ##
==========================================
- Coverage   25.17%   25.17%   -0.01%
==========================================
  Files         115      115
  Lines       28771    28771
  Branches     4669     4669
==========================================
- Hits         7243     7242       -1
  Misses      20561    20561
- Partials      967      968       +1

Flag
Coverage Δ

unittests
25.17% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/router_core/address_watch.c
78.48% <0.00%> (-1.27%)
:arrow_down:

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 6aaadd5...c3a9786. Read the comment docs.


add naming decision tree

www? use first match
else use second match

not necessary at this point imo


Recurring expenses creation and edit screen for non registered organizations

[x] Remove tax treatment field from creation and edit screen

issue fixed


Support info for the  element

Note that this is not the same as the "Video Tracks" support already in caniuse. This is a request for information about support for text tracks via the  element, as described here:
http://www.html5rocks.com/en/tutorials/track/basics/

Available via MDN now: https://caniuse.com/?search=track+element

https://caniuse.com/mdn-html_elements_track


We have methods for WaitForPipeLine And WaitForStateFulSetReady ,Need a method to for Pods to Be Ready

Reference -
https://github.com/numaproj-contrib/numaflow-utils-go/commit/8701b0864a0210759bad9210bbc00c64e780a0f0

fixed in - https://github.com/numaproj-contrib/numaflow-utils-go/releases/tag/v0.0.7


Animated Login Form

Hi, This is to add login form

I will make many pull requests after this one so please still online


Error deploying Flux on AKS via Terraform provider: Certificate verification failure

Describe the bug
I'm encountering a certificate verification error when attempting to deploy Flux on AKS using the Terraform provider.
Steps to reproduce

    flux = {
      source  = "fluxcd/flux"
      version = "1.2.3"
    }

provider "flux" {
  kubernetes = {
    host                   = module.aks.host
    client_certificate     = base64decode(module.aks.admin_client_certificate)
    client_key             = base64decode(module.aks.admin_client_key)
    cluster_ca_certificate = base64decode(module.aks.admin_cluster_ca_certificate)
  }
  git = {
    url =<EMAIL_ADDRESS>    ssh = {
      username    = "git"
      private_key = var.ssh_private_key
    }
  }
}

resource "flux_bootstrap_git" "this" {
  path    = var.target_path
  version = "v2.2.3"
  components_extra = [
    "image-reflector-controller",
    "image-automation-controller"
  ]
}

Expected behavior
Terraform terminated without error
Screenshots and recordings
 Error: Bootstrap run error
│
│   with flux_bootstrap_git.this,
│   on flux.tf line 17, in resource "flux_bootstrap_git" "this":
│   17: resource "flux_bootstrap_git" "this" {
│
│ CustomResourceDefinition/alerts.notification.toolkit.fluxcd.io dry-run failed: Get "https://aks-0qp2b7k1.hcp.westeurope.azmk8s.io:443/api?timeout=32s": tls: failed to verify certificate: x509: “apiserver” certificate is not
│ trusted

OS / Distro
Azure AKS v1.28.3
Flux version
v2.0.0 and v2.1.3
Flux check
► checking prerequisites
✔ Kubernetes 1.28.3 >=1.26.0-0
► checking version in cluster
✗ checking failed: customresourcedefinitions.apiextensions.k8s.io "gitrepositories.source.toolkit.fluxcd.io" not found
► checking controllers
✗ no controllers found in the 'flux-system' namespace with the label selector 'app.kubernetes.io/part-of=flux'
► checking crds
✗ no crds found with the label selector 'app.kubernetes.io/part-of=flux'
✗ check failed
Git provider
Github
Container Registry provider
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

More
If I execute bootstrap from my local terminal, it installs Flux without any warnings or issues.

@swade1987 I was using
module "aks" {
  source                            = "Azure/aks/azurerm"
  version                           = "8.0.0"

After retrieving information by leveraging as follows:
data "azurerm_kubernetes_cluster" "this" {
  name                = module.aks.aks_name
  resource_group_name = azurerm_resource_group.this.name
}

provider "flux" {
  kubernetes = {
    host                   = module.aks.host
    client_certificate     = base64decode(data.azurerm_kubernetes_cluster.this.kube_config[0].client_certificate)
    client_key             = base64decode(data.azurerm_kubernetes_cluster.this.kube_config[0].client_key)
    cluster_ca_certificate = base64decode(data.azurerm_kubernetes_cluster.this.kube_config[0].cluster_ca_certificate)
  }
}

@mbaykara just to close the loop on this ... did you close the issue as it's now been resolved by moving to the correct module reference?

Yeah, that's true.


Question about prediction accuracy improvement

A very good tool!
I have used this tool to test and use an application scenario.
The scenario is as follows:
Chinese document for environmental penalties, 26 labels indicating the type of problem existing in the enterprise, and labeling each document with 1-5 labels. The length of the document is 5000 in the range of 0-49 bytes, 3300 in 50-100 bytes, 1100 in 100-149 bytes, and 500 in 150-700 bytes. The problem with tags is that there are 3-4 tags that are relatively large, up to 80% cumulative, and these tags often appear alone or in combination, the degree of association is complex, and the text describing the tags is similar.
The situation is this: I use 10,000 pieces of data for training, 8000 for training, 2000 for testing, cnn, word vector 128, batch-size64, epochs=10. The trained model is used directly to predict the 10,000 trained data.
The result is this: I set the filter with a confidence greater than 0.2 as the result, and the top 5 for more than 5 tags. About 5,000 are completely correct, accounting for about 66%, and 90% of them are single-label, but only about 5% is completely wrong. A complete error means that a correct label is not predicted. 15% are labels with multiple predictions, but there are also labels that hit the correct ones, and 5% are labels with less predictions, meaning that some of the labels are not correctly predicted, but there are also hits with the correct labels. I am very satisfied with the results of the single label. However, the problems in multi-labels are also very prominent. Multi-prediction is a very headache, and most of the multi-predictions and low-predictions are the 3-4 labels that I have mentioned, which are more difficult to distinguish.
So now you feel how I can improve the accuracy to what I want: 95% full pair of single tags, reducing the number of multi-predicted tags, so that the overall correct number of tags reaches 80-90%, may be difficult?
And there are some additional questions:
1,I try to add stop words that I think can be removed when the word segmentation, and some common words are mandatory as a dictionary. Does this help the result? The result I get is the ability to identify the difference between the parts of the label, but it also reduces the confidence of some labels that were previously highly trusted.
2, the training of the word vector, I use 10000 pieces of data for word vector training, will it be impossible to correctly establish the appropriate distance space for each word vector? If I use other people's 120G Chinese corpus to train good word vectors to use, is it better? Do you need to worry about the different dictionaries? (I used a custom dictionary extra)
3,Regarding the attention mechanism, is this mechanism applicable to my scenario, increasing the model's attention to some specific words in the text, and how to apply it to magpie?
4, Other methods that you feel are likely to increase the accuracy of prediction with greater precision. Thank you very much, I hope to get your help.

hey @dyf180615 , good questions!  The model is designed to use them, so in principle should give better results without filtering.
10000 documents for training word2vec embedding should be enough, but perhaps you could get better results by pretraining the embeddings on a different corpus. The only way to know is to check, but I wouldn't bet my money on it. I also wouldn't worry about the dictionary differences unless you expected the corpora to have vastly different vocabularies e.g. training on legal documents and predicting on physics papers.
What is probably happening is that your model is very eager to predict the most popular labels and very reluctant to predict the rare ones. That usually falsely increases your accuracy, but makes the model slightly biased. You might want to explore training and testing on a more balanced dataset where the label occurrences are more or less equal (the same amounts of documents with label 1 as with label 2 etc.)
Picking the threshold 0.2 as the cutoff also might favour the most popular labels. You might want to pick a different threshold for each label, to capture that. In the ideal scenario the thresholds should also be trained and fitted based on the data (but this is hard).
Try decreasing the Word2Vec vector size from 128 to 60-70. I would expect the accuracy to be the same and the training much faster.
I only used Magpie on European languages, so if your dataset is in Chinese, them some of those rules might not hold :)

Hope that helps a bit!

@jstypka thanks so much for your tips ,i saw your reply bofore i slept yesterday,i even dream about some tips similar to yours but i forget everything after waking up in th morning :)
First of all, thank you very much for your suggestions. I will do the tests one by one, and follow-up feedback. Here are some of my confusion:

I think that there is a big difference between Chinese and European languages. European language words are separated by spaces, and the word segmentation is clear. However, Chinese needs to segment words for specific application scenarios. The combination of words into words is too complicated, and the unrelated interference is more complicated. Much, I think maybe the design of the stop word will make the content of the document more focused. Maybe the design of the model mechanism can capture this kind of interference. I don't quite understand whether the model is based on word distribution or semantic recognition. I even I want to streamline a document by adding a dictionary to a few keywords that can be artificially judged! A sentence or a paragraph becomes a few words that determine the results of different labels! But maybe you are right, but how can the model recognize the focus of a paragraph on some of the words? Through the analysis of the test, there are quite a few strange predictions. The sentence is very simple and the keywords are very With clear documentation, the model will not be able to correctly predict the labels that I thought would be easily predicted. So I am also wondering if it would be better not to remove the stop words, I will test it.
2.The corpus is Baidu Encyclopedia's entry 20G and a large number of novels 90G and Sohu News 12G. I think this can cover almost all vocabulary in a unified vector space, because my data set has a distinctive feature that the description is more solid. In theory, it should be easier to be classified, but because the accuracy requirements are higher, it is probably like the model can distinguish the difference between basketball and football, but it is not necessarily able to distinguish the difference between left-back, center-back and right-back in football. Basically, there are many parts of the label (3-4 are more important and less discriminative). When manually sub-labeling, you need to use the human brain to understand the semantics to be able to give labels, instead of seeing a certain keyword. In this case, can I expect the model to give reasonable and accurate predictions?
3.How should I prepare the data set to balance the number of tags? Considering that the combination of labels is more than the number of labels alone, I think it would be easy to reduce the number of labels, but I am worried that the effect will decrease, because the model requires more data as possible! This is called dimensionality sampling? If you add each type of label or a combination of labels, what is the appropriate amount for each of the total number of 10,000? For example, A, B, C labels, A accounted for a large proportion, how can I increase the label of B, C, BC? Considering that I have a total of 26 labels, I really feel that my head is big. I am curious that the labels in your scene should be much more than ours. I am curious about how you train your models, or based on a fairly large collection of data, and how a model can be fed back based on predicted results. Model so that he can improve his abilities under the wrong experience?
4.I really want to set different thresholds for each tag. Even the uniform tags on different orders should have different thresholds. Obviously, the confidence gap between the first tag and the fifth tag is very different. Big. Is the threshold trained and fitted to the values? How to do it! Provide some specific ideas?
Sorry to write such a long paragraph, it may be my lack of ability to express = =. I hope to keep in touch with you in this field. It is some exchange of ideas and tech. I am very interested in the field of neural networks. I call it the realm of God. The above is some of my views, I look forward to your views :)

@jstypka
After a while, there has been new progress in the last project, as follows：
1.Cancel the filter stoppage, obviously improve the effect, good idea!
2.The training of word vectors has been improved from 10,000 to 170,000 texts of the same type, and the result has increased by 2%. In the case of higher accuracy, I think it may be a good upgrade.
3.There is a problem in the test. For example, the A tag is a tag with a high proportion. The word with A1 or A2 will cause the prediction to be A tag, B be the tag with low proportion, B1 be the prone word of B tag, and the text will exist. If there is A1+B1 word distribution, A+B label is predicted, and the confidence is very good, but if A2+B1, A label will appear, the confidence is very high, B label will give very low confidence, even Being ignored, this is the place that puzzles me. Even A1>>>A, B1>>>B, C1>>>C, but A1+B1+C1>>>A, high confidence, B, C are ignored
4.Can you give me some advice on how to add attention-model to magpie? I think it can better identify the key to some extent....
Looking forward to your reply，thanks


feat(POB): In-Protocol Top of Block Auctions (V1)

Overview
This PR integrates Skip's POB V1 into Juno. We are still pending a few changes from the audit so I will make sure to update the release in this PR once it is cut and remove some of the genesis code that is currently required to start up. In terms of testing, there is a script that will be merged into POB soon that will allow the team to verify transactions are executing successfully at the top of block (and are rejected when they should be).

@davidterpay Do you think you could get this bumped to v1.0.1 & passing CI in the next day or 2? I would like to get v16 up on Uni Thurs/Friday this week.
If now we can bump it back to v17 which is much smaller & will be out in August.

Hi @Reecepbcups!
@davidterpay is on vacation this week, so I'll be taking over this work. Apologies for not seeing your comment on this PR sooner. I'll try to get this done by EOD today, California time.
LMK if you need it more urgently than that.

@keefertaylor This works for me (EOD today or by tomorrow afternoon)!
Thank you very much 🙏🏻

@Reecepbcups Sorry for the delay. I did some work today, but it's a bit more than I realized.  We'll get this over to you tomorrow.

@keefertaylor All good. Make sure to pull in main if you have not already, all CI confirms passing there + is linted :)

Completed in https://github.com/CosmosContracts/juno/pull/750


Colab button missing from tutorials on GitHub

Describe the issue
With PR https://github.com/deepset-ai/haystack-tutorials/pull/40 the Colab button is no more visible when looking at the tutorial files on GitHub. In my opinion, we should add them again.
Here is the old view with the button:
https://github.com/deepset-ai/haystack-tutorials/blob/1b592d5791e711489a6d25a4ff8f0a7160b174d1/tutorials/01_Basic_QA_Pipeline.ipynb
And the new one without the button:
https://github.com/deepset-ai/haystack-tutorials/blob/main/tutorials/01_Basic_QA_Pipeline.ipynb
@TuanaCelik if we don't add the button linking to colab I'd assume that fewer users will try running the code.
As an alternative to adding the button, maybe we could at least add a link?

Hey @julian-risch  - This was taken out because we auto-generate a button on the website: https://haystack-home.vercel.app/tutorials/01_basic_qa_pipeline
So if we have it back in (without some preprocessing in markdown generation) it would show up twice.
If you think it's important to have the button for the people who will run the tutorials via accessing them on GitHub we can make this a feature issue and do some edits to the generate_mardowns.py script to skip the button cell.

I think it would be nice to have the button also here on GitHub, yes. Otherwise, if somebody links to the tutorial on GitHub (https://github.com/deepset-ai/haystack-tutorials/blob/main/tutorials/01_Basic_QA_Pipeline.ipynb) there is no button at all and no link in that file to colab.

@julian-risch - I've closed that PR as it won't be the way we go :)
But I'll think about how we can do this alongside a download button. @bilgeyucel I might as for your help coming up with something nice that works for everyone here. Let's take this offline and I'll update the issue when we have some suggestions.

Hey @julian-risch I'm doing a clean up of the issues on haystack-tutorials. If it's ok I will close this one as we already made some changes based off of this conversation:

easier spottable colab button on websits
Download option
Colab buttons for each tutorial on the readme here

And looking at any tutorial being run on Colab, things have started to look up in the past few weeks:


data model: bind connections to document objects

Currently it is possible to create a document, do an operation within one connection and another operation within another connection. The object's values then quickly become meaningless. I think it would be better if we can find a way to more tightly tie a connection to an object. An additional benefit would be that it then doesn't need to be wired through explicitly anymore, which is a very error prone process.

isn't that the repository / dao pattern used in lsm?


Taxonomy Class Trips Fatal Error

This is because the $name param is set to protected when it must be public. It should probably be removed from this class in general since this class extends Feature_Extension and inherits this variable anyway.

Resolved in #11


REBASE: feat/common/loading-indicator improves TypeScript support and fixes inferred type error

BREAKING CHANGES

The useDependencyTimeout now returns true if all dependencies are defined and false if not all dependencies are defined yet. Before the return value was inverted. (9ca4b6a)
The loading indicator gives the children function the current dependencies which are always defined. (e482423)

Features

The loading indicator now supports variadic tuples for the dependency list via generics and gives the children function the current dependencies which are always defined. (e482423)
Now the LoadingIndicator is simpler to use, for example:const [position, setPosition] = useState<Position>();
return (
  <LoadingIndicator dependencies={[position]}>
    // "currentPos" is "position" from above but always defined
    {([currentPos]) => (

{currentPos}

    )}
  </LoadingIndicator>
);

Make useDependencyTimeout generic and usable as type guard for the dependency list. (9ca4b6a)
It makes the hook useful as a condition in if-statements, for example:const [position, setPosition] = useState<Position>();

// throws if no position received after 5 seconds
if (useDependencyTimeout(5000, [position])) {
  // type guarded - "position" is always defined
  return
Latest position: {position}
;
}

return
Waiting for incoming data
;

Add utility type to make all elements in a tuple undefinable. (419970f)
Add utility function to check if a value is defined. (51a64d3)

Fixes

It fixes a type error where TypeScript wrongly infers the return type of the loading indicator component. (e482423)

To me, passing the dependencies as direct parameters instead of the array makes more sense:
const [position, setPosition] = useState<Position>();
return (
  <LoadingIndicator dependencies={[position]}>
    // "currentPos" is "position" from above but always defined
    {(currentPos) => (

{currentPos}

    )}
  </LoadingIndicator>
);

I.e., instead of passing dependencies to the CB function, we'd pass ...dependencies. What do you think?

To me, passing the dependencies as direct parameters instead of the array makes more sense:
const [position, setPosition] = useState<Position>();
return (
  <LoadingIndicator dependencies={[position]}>
    // "currentPos" is "position" from above but always defined
-    {([currentPos]) => (
+    {(currentPos) => (

{currentPos}

    )}
  </LoadingIndicator>
);

I.e., instead of passing dependencies to the CB function, we'd pass ...dependencies. What do you think?

Sounds good to me. :+1:


Backups on Rancher/Convoy/GlusterFS

I just wrote a blog post about this issue:
https://microblog.pierre-o.fr/2016/backups-on-rancherconvoyglusterfs
I'd love to have your feedback!

The relevant passage is:

And actually, convoy-glusterFS doesn't even implement backups nor snapshot option. So we are really out of luck here.

And the question: Is supporting backups and/or snapshots on the roadmap for convoy-glusterfs?

Sorry we're no longer support glusterfs in convoy, put this as low priority...


Yatin: Watch<EMAIL_ADDRESS>

Yatin requests the watch of the watch_keyword kenmaxxy(?:@protonmail\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

<EMAIL_ADDRESS>has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by cigien in Charcoal HQ. Reason: 'typo'


Ticker remaining() error.

At least in version 4.2.0.
For MILLIS initiaslisation there is an error within the function remaining().
ticker_midnight=new Ticker(__midnight, mid_start * 1000L, 1, MILLIS);

The function remaining() is a substraction of the initialised value timer and
the result fo function elapsed().
The value timer has ofcourse already the value in MILLIS (as initialised)
and also the function elapsed() is in the right value by function millis().
uint32_t Ticker::elapsed() {
if (resolution == MILLIS) return millis() - lastTime;
else return micros() - lastTime;
}
So the divide by 1000 in function remaining() is not needed and gives now
wrong values when used as it is now:
return timer / 1000 - elapsed();
Please adapt considder to adapt the function remaining() to:
uint32_t Ticker::remaining() {
return timer - elapsed();
}
Test example:
#include <Ticker.h>
Ticker *ticker_minute;
void __minute(void)
{
Serial.println("__minute(): The end.");
}
void setup() {
// put your setup code here, to run once:
Serial.begin(115200);
while (!Serial);
ticker_minute=new Ticker(__minute, 60 * 1000L, 1, MILLIS);
}
void loop() {
// put your main code here, to run repeatedly:
ticker_minute-> update();
Serial.print("remaining: ");
Serial.println(ticker_minute->remaining());
Serial.print("elapsed: ");
Serial.println(ticker_minute->elapsed());
}
givves as output:
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97382
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97385
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97389
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97392
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97395
13:25:53.924 -> remaining:<PHONE_NUMBER>At least in version 4.2.0.
For MILLIS initiaslisation there is an error within the function remaining().
ticker_midnight=new Ticker(__midnight, mid_start * 1000L, 1, MILLIS);

The function remaining() is a substraction of the initialised value timer and
the result fo function elapsed().
The value timer has ofcourse already the value in MILLIS (as initialised)
and also the function elapsed() is in the right value by function millis().
uint32_t Ticker::elapsed() {
if (resolution == MILLIS) return millis() - lastTime;
else return micros() - lastTime;
}
So the divide by 1000 in function remaining() is not needed and gives now
wrong values when used as it is now:
return timer / 1000 - elapsed();
Please adapt considder to adapt the function remaining() to:
uint32_t Ticker::remaining() {
return timer - elapsed();
}
Test example:
#include <Ticker.h>
Ticker *ticker_minute;
void __minute(void)
{
Serial.println("__minute(): The end.");
}
void setup() {
// put your setup code here, to run once:
Serial.begin(115200);
while (!Serial);
ticker_minute=new Ticker(__minute, 60 * 1000L, 1, MILLIS);
ticker_minute->start();
}
void loop() {
// put your main code here, to run repeatedly:
static int e=0, el;
el=ticker_minute->elapsed();
if(e!=el/1000)
{
e=el/1000;
ticker_minute-> update();
Serial.print("remaining: ");
Serial.println(ticker_minute->remaining());
Serial.print("elapsed: ");
Serial.println(el);
}

}
gives as output:
15:48:49.419 -> elapsed: 55000
15:48:50.444 -> remaining:<PHONE_NUMBER>
15:48:50.444 -> elapsed: 56000
15:48:51.436 -> remaining:<PHONE_NUMBER>
15:48:51.436 -> elapsed: 57000
15:48:52.428 -> remaining:<PHONE_NUMBER>
15:48:52.428 -> elapsed: 58000
15:48:53.420 -> remaining:<PHONE_NUMBER>
15:48:53.420 -> elapsed: 59000
15:48:54.445 -> __minute(): The end.
expected output:
15:38:29.168 -> remaining: 3000
15:38:29.168 -> elapsed: 57000
15:38:30.160 -> remaining: 2000
15:38:30.160 -> elapsed: 58000
15:38:31.153 -> remaining: 1000
15:38:31.153 -> elapsed: 59000
15:38:32.178 -> __minute(): The end.
Thanks
Ed Faber
Netherlands.
13:25:53.924 -> elapsed: 97399
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97402
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97405
13:25:53.924 -> remaining:<PHONE_NUMBER>
13:25:53.924 -> elapsed: 97409
Thanks
Ed Faber
Netherlands.

Solved with 4.3.0


Allow threads to skip context switching

Add an option to invoke HPX threads directly on the worker thread stack instead of switching to a new stack. This would be a useful option for tasks that don't do much, e.g. the tasks in simple data-parallel for loops. This may lead to nice performance improvements in our thread scheduling.
A simple proof-of-concept is probably a good first step to see if we actually gain anything by this.

@msimberg FWIW, at some point we did have an implementation of this in HPX (see https://github.com/STEllAR-GROUP/hpx/commit/2217e2792b7170ae08b93218165d68a202edf0a4#diff-11f383c8f29752a630098984712b40bb). AFAIR, it didn't give us a big benefit, but things might have changed based on the massive scheduler improvements we have implemented over the last month.

Thanks for the link! Even if it doesn't give us a big benefit that would be valuable information. It would tell us that there's significantly more slack in the queues and schedulers than we (at least I) thought.


Added a Medium article for February - Authorization — New Buzzword in Access Control

Authorization — New Buzzword in Access Control
by Chathura Gunasekara
Contribute to Identity Beyond Borders

We strongly recommend adding the blog to Identity Beyond Borders
publication maintained by WSO2 Identity Server team. Follow the guide to add yourself as a writer.

Let's add the name to https://github.com/wso2/iam-blogs/blob/main/README.md


Improve serialization speed

For longer ontologies, it takes too long to process. We need to improve this.

I've noticed there is a significant slowdown corresponding with the length of rdf:Lists.  Is code handling sorting rdf:Lists in this code base, or in an imported library?

Addendum: I observe this most often with Turtle serialization.

@ajnelson-nist did you try the latest build:  ?
I am asking because the speed should be improved by https://github.com/edmcouncil/rdf-toolkit/pull/35.
If it is still bad in your opinion, could you send us a file to test together with some estimate of time needed for its serialisation?

Hi @mereolog ,
Apologies for the delayed reply.
The file with which I've seen a rdf:List-based slowdown most frequently is this one:
https://github.com/ucoProject/UCO/blob/master/ontology/uco/vocabulary/vocabulary.ttl
Sorting that should take under 1 second.  However, because of something involving how rdf-toolkit sorts rdf:List members, the runtime is superlinear w.r.t. length of at least the longest rdf:List.
For example, after observing the runtime of that file as-is, try removing any hunk of the list involved with vocabulary:ObservableObjectRelationshipVocab.  You should see the time decrease dramatically.
I think the issue is rdf-toolkit is not treating a rdf:List as an item that only needs its head sorted with wherever the head is referenced.  There should be no decision process involved with any member of the list after the first rdf:next, once the rdf:List is constructed.  For example, a file with two 100-member rdf:Lists defined, and nothing else, should only sort 2 nodes, not 200.
FWIW, I did see a speedup from the build posted soon after #35 was merged.  However, the fundamental issue still remains.

Hi @mereolog ,
Apologies for the delayed reply.
The file with which I've seen a rdf:List-based slowdown most frequently is this one:
https://github.com/ucoProject/UCO/blob/master/ontology/uco/vocabulary/vocabulary.ttl
Sorting that should take under 1 second. However, because of something involving how rdf-toolkit sorts rdf:List members, the runtime is superlinear w.r.t. length of at least the longest rdf:List.
For example, after observing the runtime of that file as-is, try removing any hunk of the list involved with vocabulary:ObservableObjectRelationshipVocab. You should see the time decrease dramatically.
I think the issue is rdf-toolkit is not treating a rdf:List as an item that only needs its head sorted with wherever the head is referenced. There should be no decision process involved with any member of the list after the first rdf:next, once the rdf:List is constructed. For example, a file with two 100-member rdf:Lists defined, and nothing else, should only sort 2 nodes, not 200.
FWIW, I did see a speedup from the build posted soon after #35 was merged. However, the fundamental issue still remains.

Suppose there are two lists:

[A, B, C]
[A, D, E]
When serialising a graph with these two lists, the serialiser may need to sort the lists themselves, i.e., it needs to establish which list is put first in the sorted file. The current solution is that the serialiser walks both lists and compare its elements as long as it finds different elements. Then it finds which of the different elements is to be sorted first and this element decides which list is sorted first.
In the example below list 1 is sorted before 2 because its second element is sorted before the second element of list 2 - I assume a simple lexicographic sorting for elements.

The time needed for this operation should be linear wrt length of the list being sorted.


is_standard_normal test is flaky

Relax confidence level? Or could seed it.
Weirdly only seems flaky on Python 3.8.

Argh, still flaky. Clearly this test is not as robust as I hoped, maybe need to use something other than (or in addition to?) K-S.

Temporarily fixed this byusing default_rng with a seed -- but would rather have a test that a decent sample passes on.

Much better now but failed again on 3.9 here https://github.com/scienxlab/redflag/actions/runs/6385283773


[2918] Increase valid age range possibilities

Context
An option for age ranges on the frontend did not pass validation
Changes proposed in this pull request
Increase the validation range to support the option the user can select
Guidance to review

Create a secondary course on course creation flow
Select "14 to 19"
Press continue

Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

Rebasing and merging


Adds Concurrent Reconciles.

Adds options for concurrent reconciles.  Also fixes some linting errors.

/lgtm
Those "fmt.Sprintf(ALREADY A STRING)" lint errors are insidious!  They creep in everywhere.

/hold

I'd like to put this PR on hold, we actually don't this requirement currently.
I would consider this kind of change if the outcome of the load tests was indicating we have a bottle-neck on the account claiming process. So far the results from our load tests with 500 regular clusters are not indicating any of that.
On top of that, IMO we have some prep work to do in order to start parallel processing with the operator.

@rogbas Ahh, okay, I just saw this in the TODO for this sprint and knew I had the prior knowledge of how "simple" this would be, so I figured I'd just knock this out.
@2uasimojo I'd like to discuss with you sometime offline your thoughts on why this wouldn't work, as my preliminary tests during the spike had shown that this would work, and that it was this simple (albeit this was before InitRegions went async).  But then again, I could easily be missing something.
With all of that said, though, I've also pulled out the linting error fixes into #481 in order to not block those.

Unless I missed something major, I'm almost certain it's not this simple.

My strong reaction was because (at least) the account controller is not idempotent. If we can prove that we never enter the Reconcile twice for the same CR in parallel (other than during async region init) then I'd be much less concerned.
However, we should consider @rogbas's question: Do we have evidence that we need to do this in the first place?

I agree with the "Let's see if we need this".
As of this moment, this should be the required work to add this.  I removed and force-pushed the linting commit and moved that out (did I say that already? I'm not scrolling back up).
Worst case scenario, we close this as of right now, but we have the diff to show what needs to be done (not that it's really a lot, anyway...)

Still working on this.  Should be able to finish first thing next week after my Primary shift is over.

This builds off of #470 so to view only the changes related to this PR use this link: https://github.com/openshift/aws-account-operator/pull/480/files/b2cbc44ec50860a629e618c38e9c704d034b39d5..a3ce3632242f9fa97de5b904d04baa1e98662cec

@iamkirkbater Could you please rebase and squash?

@rogbas @fahlmant @clcollins @drewandersonnz @drpaneas I would like to hear your thoughts on the above question from @2uasimojo :

This actually looks like it'll fail if the CM doesn't have an entry for a given controller. Is that what we want?

Related code: https://github.com/openshift/aws-account-operator/pull/480/files#diff-435eecb1d2af40ee96747f88ab71eb2758da989c92f76dcb1f714fc1b300c633R116-R123

@iamkirkbater I think we should default to 1 if there's no specific config in the CM

Trivial rebase and squash since previous
/lgtm

/hold

@iamkirkbater can you please check the failing prow/coverage test and remove hold?

/retest
Looks like it's that bug that Eric fixed with the coverage job failing due to the missing file.

@rogbas - PR has been rebased and is ready for final review.

@rogbas update respective Jira card and close PR


Corrupted Save - A History of Violence Background Quest

Following up on my last thread:
https://github.com/SolastaMods/SolastaUnfinishedBusiness/issues/4628
The data for the save is now corrupted, and the Solasta forums have been taken down as Tactical Adventures is working on their next project.
Save attached. Please do not be dismissive and actually explain what I should do if it's something on my end. I've already tried Googling and those solutions didn't work.
Movie.zip

Most likely related with entries in combat log related to lucky feat. You will need an older save, preferably after a long rest where these entries in combat log aren’t there.
Don’t open a 3rd ticket. I cannot babysitter every single player out there. This is a hobby.


pip requirements not installing properl

The pip requirements for invenio are included in a file, but the task is not being executed properly - the file requirements.txt is not found.

Turns out this was a problem with matplotlib installation. The freetype packages were not installed
freetype: no  [The C/C++ header for freetype2 (ft2build.h)

                        could not be found.  You may need to install the

                        development package.]

For some reason, this doesn't get reported on Travis, but on the container locally it does.


Update to PG10 package name/path for Docker image

Depends on https://github.com/ManageIQ/manageiq-pods/pull/326 to be merged and new backend/frontend images to be built.

Ivanchuk backport details:
$ git log -1
commit 8a52cca727e467fb70b6233100ba6adbd61ec9e8
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Fri Aug 2 16:21:45 2019 -0400

    Merge pull request #19096 from simaishi/docker_update

    Update to PG10 package name/path for Docker image

    (cherry picked from commit 9068f8c50268761040a44e0b8e8d89a3f4f58d47)


Bug: Fixup stuck in Applying state

When doing an edit fixup, the fixup is stuck in the applying state after applying the edits. "Cannot define property error is also shown along with it".
See this for the exact behaviour:
https://github.com/sourcegraph/cody/assets/44617923/648930cc-f505-464e-903e-63f18e3ada5d
CC: @umpox @abeatrix

I tried to reproduce in the dev mode too, same issue. Looking over the fix of this.

@deepak2431 thanks for letting us know! @umpox has a wip that might have fixed it, can you give his branch a try and let us know if that helps? https://github.com/sourcegraph/cody/pull/1411

@abeatrix Thanks for letting me know about that. Let me give that branch a try.

@abeatrix It's the Same issue with that branch, too. This applies to the inline-chat edit too.
https://github.com/sourcegraph/cody/assets/44617923/36da9437-8d0d-4e07-8074-f8b5ca33ad4f
The auto-apply edits look good, but it is missing a case as when there's any error in the output, it just replaces the whole code with the error in the editor.
https://github.com/sourcegraph/cody/assets/44617923/26e7b926-14e7-4837-9b15-2505f35ea1d7

Thanks @deepak2431, I'll investigate fixing this in the mentioned PR

@deepak2431 This should be fixed on the latest main now. Please take a look if you have chance!
The error was due to an incorrect assumption about a VS Code command (we get undefined instead of an empty array)
The second error looks unusual as it seems Cody is providing that as a valid response. I have added a PR to fix some cases where it'll catch an invalid response: https://github.com/sourcegraph/cody/pull/1561. I'll look further - may need to look at tweaking the prompt, I haven't been able to replicate this yet

@umpox Great!  Got it. I will test it again and let you know.
I think the second error is when Cody responds, but it's something not code but like "I do not have enough context about the code" or a similar message.  So, we don't flag this as an error for now, and this is not a CORRECT response either. So, we need to find a way to flag this response in case of a fixup. LMK, What do you think?
I looked at your PR #1561, and that would display any error in case of an invalid response. I think so.

@umpox I tested it again on the latest same; the issue is still there for me. Can you please check it again once on your side?

Thanks @deepak2431
I think there is a possibility that this is dependant on the formatter on your machine, it could be timing out or taking a while. This is tricky for us to handle as we can't really control much here.
We can do better at showing this though, I've added a PR to show the formatting state and also add an option to skip:
https://github.com/sourcegraph/cody/pull/1561
I'd be curious to see if you now get stuck on "Formatting" which might help us narrow it down a bit (I still can't replicate this on main 🤔). We can look at adding the option to disable the formatting feature too

@umpox You are right. This was happening for me due to the formatter issue. I spent some time debugging it at the root level, so it's the Python Black Formatter that I am using that was causing this.
Also, after your recent change in the main, it shows stuck at Formatting instead of Applying. So, I'm not sure if this happens with all of the formatter, but yeah, I found the issue with the Python formatter, but with the TS formatter, it was not.

@deepak2431 Thanks you for following up! It looks like some formatters expect us to pass certain options. This will be fixed in this PR: https://github.com/sourcegraph/cody/pull/1620


404 at deletion of an existing attachment when using wrong rev

Description
https://github.com/apache/couchdb/pull/3673 created a bug. When we try to DELETE an existing attachment with an invalid rev we get a 404 instead 409.
Steps to Reproduce

Create a document with an attachment
Try to DELETE it with an invalid rev like 4-somegarbage

Expected Behaviour
The response code should be 409, not 404 similarly to PUT.
Your Environment

CouchDB version used: 3.x, after the f31e92 commit
Browser name and version: cURL
Operating system and version: MacOS Big Sur 11.3.1 (20E241)

Additional Context

Thanks for the bug report @mojito317

These PRs should fix it https://github.com/apache/couchdb/pull/3687 https://github.com/apache/couchdb/pull/3686


Invalid argument on Meteor 2.5-beta

I'm getting the following error on Galaxy when running on Meteor 2.5 beta, which crashes the container:
t3y2m
2021-10-07 08:05:25+02:00TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received function onStreamEnd
t3y2m
2021-10-07 08:05:25+02:00 at Function.from (buffer.js:330:9)
t3y2m
2021-10-07 08:05:25+02:00 at toBuffer (/app/bundle/programs/server/npm/node_modules/meteor/webapp/node_modules/compression/index.js:286:14)
t3y2m
2021-10-07 08:05:25+02:00 at ServerResponse.end (/app/bundle/programs/server/npm/node_modules/meteor/webapp/node_modules/compression/index.js:115:22)
t3y2m
2021-10-07 08:05:25+02:00 at Curl.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/request-libcurl/index.js:222:24)
t3y2m
2021-10-07 08:05:25+02:00 at Curl.emit (events.js:400:28)
t3y2m
2021-10-07 08:05:25+02:00 at Curl.emit (domain.js:470:12)
t3y2m
2021-10-07 08:05:25+02:00 at /app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:198:22
t3y2m
2021-10-07 08:05:25+02:00 at wrapper (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:188:23)
t3y2m
2021-10-07 08:05:25+02:00 at Curl.onEnd (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:189:9)
t3y2m
2021-10-07 08:05:25+02:00 at Easy.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:47:22)

After removing the package things go back to normal.

Hello @StorytellerCZ ,
Pardon me for the silence. So far we haven't faced such issue on our end. Hopefully latest v1.6.4 solve all compatibility issues.
Feel free to close it in case if the issue is solved on your end.
If issue persists on your end, please share more details on your setup and connected website

I'll give it a try.

I think it is working now. Closing!

Never mind, just got the error again and it crashed my app. Though this time it was after hours of running:
pkssb
2022-05-09 15:27:23+02:00TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received function onStreamEndpkssb
2022-05-09 15:27:23+02:00 at new NodeError (internal/errors.js:322:7)pkssb
2022-05-09 15:27:23+02:00 at Function.from (buffer.js:334:9)pkssb
2022-05-09 15:27:23+02:00 at toBuffer (/app/bundle/programs/server/npm/node_modules/meteor/webapp/node_modules/compression/index.js:286:14)pkssb
2022-05-09 15:27:23+02:00 at ServerResponse.end (/app/bundle/programs/server/npm/node_modules/meteor/webapp/node_modules/compression/index.js:115:22)pkssb
2022-05-09 15:27:23+02:00 at Curl.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/request-libcurl/index.js:222:24)pkssb
2022-05-09 15:27:23+02:00 at Curl.emit (events.js:400:28)pkssb
2022-05-09 15:27:23+02:00 at Curl.emit (domain.js:475:12)pkssb
2022-05-09 15:27:23+02:00 at /app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:206:22pkssb
2022-05-09 15:27:23+02:00 at wrapper (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:196:23)pkssb
2022-05-09 15:27:23+02:00 at Curl.onEnd (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:197:9)pkssb
2022-05-09 15:27:23+02:00 at Easy.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/ostrio_spiderable-middleware/node_modules/node-libcurl/dist/Curl.js:47:22)

My settings are:
import { WebApp } from 'meteor/webapp'
import Spiderable from 'meteor/ostrio:spiderable-middleware'

WebApp.connectHandlers.use(
  new Spiderable({
    rootURL: 'https://www.literaryuniverse.com',
    serviceURL: 'https://render.ostr.io',
    auth: 'myauthkey',
    ignore: ['/user/', '/workshop/', '/library/', '/pm/']
  })
)

@StorytellerCZ figured it out. Pushed fixes in 1.6.5. I hope it will get solved now.
Feel free to reopen it in case if the issue is still persists on your end.


private vs public FQDN and connecting to a cluster

If I've configured an AKS cluster using private link and it also created the public FQDN, how do I tell my client to connect to the cluster using one or the other DNS names?  For example I might be trying to connect via a VPN client that can't properly resolve the private record but can resolve the public one.

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

ID: 0b68f2c4-bb6c-11a2-6c61-8af4057a2438
Version Independent ID: e3498bed-1447-6841-8353-9f1b5d3dc8df
Content: Create a private Azure Kubernetes Service cluster - Azure Kubernetes Service
Content Source: articles/aks/private-clusters.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

If you are creating a private cluster, there should not be public access to the cluster. If your VPN connections cannot resolve the private IP, you can connect via the IP. If you need to resolve SSL with a FQDN or DNS name, you can add the cert & dns record in the hosts.txt file, or use a VNET level custom DNS solution.
If you want to have the public record present, you can have the VPN connections use the public FQDN if they cannot resolve the private DNS name. It should both point to the same IP Address.

My VPN client works to attach to the private network but DNS resolution doesn't always work to resolve private DNS zones.  According to the documentation page, "When you provision a private AKS cluster, AKS by default creates an additional public FQDN and corresponding A record in Azure public DNS. "  How do I find the public name of the cluster?
So I should be able to use the public FQDN, if I knew it, and successfully use the cluster.

I see in the portal two addresses, one inthe "essentials" part and another under Properties-->Networking.  In the screen shot attached, the two addresses do not match, the upper one is the private link address, the lower one is the public FQDN.  But the lower one sometimes matches the upper one.  The lower ones seems to vary every time we refresh the window, sometimes showing the private link address, sometimes the FQDN.
How do we reliably pull the QDN so we can use that?

@ToddBowman , we have not heard from you in some time. If you need further help on this please feel free to comment on this thread and we shall proceed from there.
#please-close


Automated cherry pick of #4368: fix: alter user email charset to utf8

Cherry pick of #4368 on release/2.11.
#4368: fix: alter user email charset to utf8

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.11   #4371   +/-   ##
==============================================
  Coverage                ?   7.11%
==============================================
  Files                   ?     480
  Lines                   ?   78080
  Branches                ?       0
==============================================
  Hits                    ?    5554
  Misses                  ?   72060
  Partials                ?     466

Flag
Coverage Δ

#aFlag
7.11% <ø> (?)

Impacted Files
Coverage Δ

pkg/keystone/models/users.go
1.93% <ø> (ø)

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 c8c9e1a...79074e4. Read the comment docs.


CI: Use 2.6.3

This PR updates the CI matrix.

Sorry but I missed this one and updated it in master already.


Kernel Memory on kubernetes

Context / Scenario
Hello, good morning/afternoon/evening and Happy Monday!
Initially, I must say that I am very impressed with this solution and keen to implement it as an internal service to our k8s clusters.
Question
To my question: I went through all the documentation available. As of now, is it possible to deploy it to kubernetes?
Thanks!

hi @rmelilloii great to hear the solution could help!
KM should totally work fine in Kubernetes. I would try first with the docker image mentioned in the main README. Configuration can be provided via a file or env vars, let me know if you encounter any problem.
Aside for the basic docker image, there are also optimizations, for example it's possible to turn on/off various aspects of KM, for example you could run ingestion workers on 10 VMs while running the web service only on 2-3 nodes, if that's something that could interest.

Hello @dluc good morning and happy Tuesday!
Thanks for your message. I will then read the "service/Service/appsettings.json" to figure out which variables I can inform on my
yaml.
My initial stateful deployment should be something like:

Document Storage: local disk
Memory Storage: ElasticSearch
Data ingestion orchestration: RabbitMQ
LLM: OpenAI (latest GPT)

I am indeed interested in the different workloads for better resource utilisation. To avoid too much noise here I will do tests and post back with results/doubts to help similar needs, maybe adding working examples to the repo.
Thanks!

Hello again o/
@dluc , sorry to bother.
Deploy goes green (pod running) but it is on a crash loop. The pod log is not enough to help with a cause. Any suggestion?
It complains about: "DataIngestion.EmbeddingGeneratorTypes", which has no value on the documentation.
Elasticsearch and RabbiMQ endpoints are up and accepting connections (Auth validated).
Any help is very appreciated.
Thanks!
Log:
******
Data ingestion embedding generation (DataIngestion.EmbeddingGeneratorTypes) is not configured.
Please configure the service and retry.

How to configure the service:

1. Set the ASPNETCORE_ENVIRONMENT env var to "Development" or "Production".

   Current value: Development

Documentation:

manifest:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: msft-km
  labels:
    service: msft-km
spec:
  replicas: 1
  selector:
    matchLabels:
      service: msft-km
  template:
    metadata:
      labels:
        service: msft-km
    spec:
      containers:
      - name: msft-km
        image: kernelmemory/service:latest
        imagePullPolicy: IfNotPresent
        ports:
        - name: http
          containerPort: 9001
          protocol: TCP
        - name: https
          containerPort: 9002
          protocol: TCP
        env:
        - name: ASPNETCORE_ENVIRONMENT
          value: "Development"
        # Whether to run the web service that allows to upload files and search memory
        # Use these booleans to deploy the web service and the handlers on same/different VMs
        - name: KernelMemory__Service__RunWebService
          value: "true"

        # Whether to run the asynchronous pipeline handlers
        # Use these booleans to deploy the web service and the handlers on same/different VMs
        - name: KernelMemory__Service__RunHandlers
          value: "true"

        # Whether to expose OpenAPI swagger UI at http://<IP_ADDRESS>:9001/swagger/index.html
        - name: KernelMemory__Service__OpenApiEnabled
          value: "false"

        # Whether clients must provide some credentials to interact with the HTTP API
        - name: KernelMemory__ServiceAuthorization__Enabled
          value: "false"

        # Currently "APIKey" is the only type supported
        - name: KernelMemory__ServiceAuthorization__AuthenticationType
          value: "APIKey"

        # HTTP header name to check
        - name: KernelMemory__ServiceAuthorization__HttpHeaderName
          value: "Authorization"

        # Define two separate API Keys, to allow key rotation. Both are active.
        # Keys must be different and case-sensitive, and at least 32 chars long.
        # Contain only alphanumeric chars and allowed symbols.
        # Symbols allowed: . _ - (dot, underscore, minus).
        - name: KernelMemory__ServiceAuthorization__AccessKey1
          value: "***"
        - name: KernelMemory__ServiceAuthorization__AccessKey2
          value: "***"

        # "AzureBlobs" or "SimpleFileStorage"
        - name: KernelMemory__ContentStorageType
          value: "SimpleFileStorage"

        # "AzureOpenAIText", "OpenAI" or "LlamaSharp"
        - name: KernelMemory__TextGeneratorType
          value: "OpenAI"

        # "AzureOpenAIText", "OpenAI" or "LlamaSharp"
        - name: KernelMemory__DefaultIndexName
          value: "noName"

        # - InProcess: in process .NET orchestrator, synchronous/no queues
        # - Distributed: asynchronous queue based orchestrator
        - name: KernelMemory__DataIngestion__OrchestrationType
          value: "Distributed"

        # "AzureQueue", "RabbitMQ", "SimpleQueues"
        - name: KernelMemory__DataIngestion__DistributedOrchestration__QueueType
          value: "RabbitMQ"

        # Whether the pipeline generates and saves the vectors/embeddings in the memory DBs.
        # When using a memory DB that automatically generates embeddings internally,
        # or performs semantic search internally anyway, this should be False,
        # and avoid generating embeddings that are not used.
        # Examples:
        # * you are using Azure AI Search "semantic search" without "vector search": in this
        #   case you don't need embeddings because Azure AI Search uses a more advanced approach
        #   internally.
        # * you are using a custom Memory DB connector that generates embeddings on the fly
        #   when writing records and when searching: in this case you don't need the pipeline
        #   to calculate embeddings, because your connector does all the work.
        # * you are using a basic "text search" and a DB without "vector search": in this case
        #   embeddings would be unused, so it's better to disable them to save cost and latency.
        - name: KernelMemory__DataIngestion__EmbeddingGenerationEnabled
          value: "true"

        # Vectors can be written to multiple storages, e.g. for data migration, A/B testing, etc.
        # "AzureAISearch", "Qdrant", "SimpleVectorDb"
        - name: KernelMemory__DataIngestion__MemoryDbTypes__0
          value: "Elasticsearch"

        # "None" or "AzureAIDocIntel"
        - name: KernelMemory__DataIngestion__ImageOcrType
          value: "None"

        # "AzureOpenAIEmbedding" or "OpenAI"
        # This is the generator registered for `ITextEmbeddingGeneration` dependency injection.
        - name: KernelMemory__Retrieval__EmbeddingGeneratorType
          value: "OpenAI"

        # "AzureAISearch", "Qdrant", "SimpleVectorDb"
        - name: KernelMemory__Retrieval__MemoryDbType
          value: "Elasticsearch"

        # Maximum number of tokens accepted by the LLM used to generate answers.
        # The number includes the tokens used for the answer, e.g. when using
        # GPT4-32k, set this number to 32768.
        # If the value is not set or less than one, SearchClient will use the
        # max amount of tokens supported by the model in use.
        - name: KernelMemory__Retrieval__SearchClient__MaxAskPromptSize
          value: "-1"

        # Maximum number of relevant sources to consider when generating an answer.
        # The value is also used as the max number of results returned by SearchAsync
        # when passing a limit less or equal to zero.
        - name: KernelMemory__Retrieval__SearchClient__MaxMatchesCount
          value: "100"

        # How many tokens to reserve for the answer generated by the LLM.
        # E.g. if the LLM supports max 4000 tokens, and AnswerTokens is 300, then
        # the prompt sent to LLM will contain max 3700 tokens, composed by
        # prompt + question + grounding information retrieved from memory.
        - name: KernelMemory__Retrieval__SearchClient__AnswerTokens
          value: "300"

        # Text to return when the LLM cannot produce an answer.
        - name: KernelMemory__Retrieval__SearchClient__EmptyAnswer
          value: "INFO NOT FOUND"

        # Options: "Disk" or "Volatile". Volatile data is lost after each execution.
        - name: KernelMemory__Services__SimpleFileStorage__StorageType
          value: "Volatile"

        # Directory where files are stored.
        - name: KernelMemory__Services__SimpleFileStorage__Directory
          value: "_files"

        # Options: "Disk" or "Volatile". Volatile data is lost after each execution.
        - name: KernelMemory__Services__SimpleQueues__StorageType
          value: "Volatile"

        # Directory where files are stored.
        - name: KernelMemory__Services__SimpleQueues__Directory
          value: "_queues"

        # Options: "Disk" or "Volatile". Volatile data is lost after each execution.
        - name: KernelMemory__Services__SimpleVectorDb__StorageType
          value: "Volatile"

        # Directory where files are stored.
        - name: KernelMemory__Services__SimpleVectorDb__Directory
          value: "_vectors"

        # RabbitMQ

        - name: KernelMemory__Services__RabbitMq__Host
          value: "<IP_ADDRESS>"
        - name: KernelMemory__Services__RabbitMq__Port
          value: "5672"
        - name: KernelMemory__Services__RabbitMq__Username
          value: "***"
        - name: KernelMemory__Services__RabbitMq__Password
          value: "***"

        # Elasticsearch

        - name: KernelMemory__Services__Elasticsearch__CertificateFingerPrint
          value: ""
        - name: KernelMemory__Services__Elasticsearch__Endpoint
          value: "http://<IP_ADDRESS>:9200"
        - name: KernelMemory__Services__Elasticsearch__UserName
          value: "***"
        - name: KernelMemory__Services__Elasticsearch__Password
          value: "***"
        - name: KernelMemory__Services__Elasticsearch__IndexPrefix
          value: "km-"
        - name: KernelMemory__Services__Elasticsearch__ShardCount
          value: "1"
        - name: KernelMemory__Services__Elasticsearch__Replicas
          value: "0"

        # OpenAI

        # Name of the model used to generate text (text completion or chat completion)
        - name: KernelMemory__Services__OpenAI__TextModel
          value: "gpt-3.5-turbo-16k"
        # The max number of tokens supported by the text model.
        - name: KernelMemory__Services__OpenAI__TextModelMaxTokenTotal
          value: "16384"
        # Name of the model used to generate text embeddings
        - name: KernelMemory__Services__OpenAI__EmbeddingModel
          value: "text-embedding-ada-002"
        # The max number of tokens supported by the embedding model
        # See https://platform.openai.com/docs/guides/embeddings/what-are-embeddings
        - name: KernelMemory__Services__OpenAI__EmbeddingModelMaxTokenTotal
          value: "8191"

        # OpenAI TextGenerationType
        - name: KernelMemory__Services__OpenAI__TextGenerationType
          value: "Auto"

        # OpenAI API Key
        - name: KernelMemory__Services__OpenAI__APIKey
          value: "***"

        # OpenAI Organization ID (usually empty, unless you have multiple accounts on different orgs)
        - name: KernelMemory__Services__OpenAI__OrgId
          value: ""

        # How many times to retry in case of throttling
        - name: KernelMemory__Services__OpenAI__MaxRetries
          value: "10"

        # Logging

        - name: Logging__LogLevel__Default
          value: "Trace"
        - name: Logging__LogLevel__Microsoft_KernelMemory_Pipeline_Queue_DevTools_SimpleQueue
          value: "Information"
        - name: Logging__LogLevel__Microsoft_AspNetCore
          value: "Trace"

        # Allowed hosts

        - name: AllowedHosts
          value: "*"

        # Urls for Kestrel server endpoints
        - name: Kestrel__Endpoints__Http__Url
          value: "http://*:9001"
        - name: Kestrel__Endpoints__Https__Url
          value: "https://*:9002"

Some of the env vars can be seen also here https://github.com/microsoft/kernel-memory/blob/main/infra/modules/container-app.bicep
For EmbeddingGeneratorTypes, since it's an array, the env var name is KernelMemory__DataIngestion__EmbeddingGeneratorTypes__0 for the first element, KernelMemory__DataIngestion__EmbeddingGeneratorTypes__1 for the second, and so on
- name: KernelMemory__DataIngestion__EmbeddingGeneratorTypes__0
  value: "Elasticsearch"

Thanks, I really appreciate it. I had the impression that the variable was superseded as it didn't inform any possible value on the "comments", only a reference to a related env.
It is up now, play time! :)
Do you have any documentation regarding:

there are also optimizations, for example it's possible to turn on/off various aspects of KM, for example you could run ingestion workers on 10 VMs while running the web service only on 2-3 nodes, if that's something that could interest.

Thanks a lot!

There are two main config settings:

KernelMemory.Service.RunWebService: with this you can turn on/off the web service. For example you might have a set of workers dedicated processing jobs in the queues, and here you can turn the web service off.
KernelMemory.Service.RunHandlers: with this you can turn on/off the threads polling queues for ingestion jobs.

Handlers share state via files which can be stored on disk/azure blobs/mongodb. When using disk, it's harder to share state across VMs, unless you mount the same across.
Assuming state is shared with a central storage like blobs or DB or mounted disk, then the service can work across multiple VMs, splitting workload. For instance, this could be one setup to scale the web service separately from the async ingestion workload:

3 nodes with RunWebService=true, RunHandlers=false
N autoscale nodes, with RunWebService=false, RunHandlers=true

In the async ingestion pipelines, each task is managed by a dedicated handler. Handlers provide another way to load balance across mutliple nodes. E.g. it's possible to control which handlers to execute, using the config setting array KernelMemory.Service.Handlers


ref: log files are suffix for easier viewing

ref: log files are suffix for easier viewing

please rebase to the latest master commit.

please rebase to the latest master commit.

have been merged


Implement ValidateUnsigned as SignedExtension

A follow up on #5003
Related: #3419
Closes: #4419
This PR removes a special role ValidateUnsigned has in executive. Instead we have a ValidateUnsigned extension defined in frame_system, which dispatches the calls instead.
This is not properly tested yet, and possibly not something we want to include for 2.0, but still wanted to make the PR visible.
Let me know what you think, CC @bkchr @jimmychu0807

I def. like the idea better as now we don't have two thing flying around doing the same thing: ValidateUnsigned and SignedExtension. But I think in the very long term, we want only the latter. Even with this PR, it is a bit confusing: You as a runtime dev have two options:

implement ValidateUnsigned and system will do the rest of the magic for you (if I have understood your code correctly -- had to read it really fast)
Implement your own SignedExtension.

If we can find a nice way to be able to have the nice features of ValidateUnsigned into SignedExtension, then I think that is much better. Based on the issue discussions the main problem with SignedExtension seem to be the glowing list of Extra.

Based on the issue discussions the main problem with SignedExtension seem to be the glowing list of Extra.

Exactly this, so it's definitely possible for every pallet to expose it's own SignedExtension, but it seems like an overkill and it adds a lot of boilerplate - i.e. you need to change your UncheckedExtrinsic::Extra implementation every time you add a new module that has unsigned transactions which seems insane.
I think that ValidateUnsigned implementation for a pallet should be the way to go in the future. It's simple and does the job really well. We already aggregate all ValidateUnsigned impls from modules and implement ValidateUnsigned for the entire Runtime, and it's makes it definitely less effort.
If ever anyone needs the additional info passed to SignedExtensions they can definitely implement one for their module. Also we can revisit the set of methods of SignedExtensions as suggested in #3419

@tomusdrw is this a draft or ready for review?

To be frank, I'm not actively working on this. I was hoping that we will merge that after 2.0 is released, as I didn't put a lot of work into testing it's correctness (and was quite surprised that none of our tests broke :)).
That said, we can review that and let @gnunicorn decide if we want to include in 2.0 or rather put on hold. IMHO this makes the Applyable API way cleaner which might help with #5130 as well.

Tests added, should be ready to re-review.

If we really want to combine ValidateUnsigned and SignedExtension, then I think a better direction would be first to consider the possibility of introducing some way to allow a pallet to state that a SignedExtension were mandatory for the runtime and have it auto-included without the need to collated SignedExtensions manually as is the case now. We might then revisit this PR in so much as to add the API that would allow SignedExtensions to be used for the various ValidateUnsigned use-cases that we have. We could then move the ValidateUnsigned usages over and retire the API.

I see almost no improvement in the API; the only advatage here that I can see is that we get to lose one generic param in Executive (which could perhaps be lost in a better way by combining with AllModules) and one generic param elsewhere in validate/apply.

The main improvement imho is unified validation pipeline for signed and unsigned transactions, and decoulping unsigned transactions from Executive (the generic parameter you've mentioned).

we have an additional param going into validate

I see that more as an improvement actually - having TransactionSource in SignedExtension is basically a missing part in my previous PR - I think it should simply be there for consistency.

we have an additional datapath out of SignedExtension::pre_dispatch with the (rather opaque concept of) IsFullyValidated.

Only added to address Basti's critique about unsigned transactions being valid by default, removed in new approach. However I think this is a moot point anyway, since even though validate is going to return Ok
the ValidTransaction has no provides tags which would cause the pool to reject it anyway.

We also have an additional item in SignedExtra that must be there or random other stuff in a runtime will break.

I agree this is suboptimal, I want to get rid of all () in SignedExtra by introducing a single SignedExtension that is able to group a tuple of SignedExtension<AdditionalData=()>. So that all
adding/removing no-argument validator-like extensions would not alter SignedExtra type. But
that's rather a separate PR.

It is highly questionable whether ValidateUnsigned should be subjugated to SignedExtension and whether the latter should see its API bloated in that cause.

The point is that currently SignedExtensions make an impression of being able to handle unsgined transactions
while in reality it's not possible at all. You can't create a SignedExtension and whitelist a call
there, because UnsignedValidator takes precedence anyway. SignedExtension can only be used to further restrict unsigned transactions (or augment the ValidTransaction result). I think having two mechanisms that seem to address the same problem is confusing and that's why I believe this unification makes sense.

(Sorry for a wall of text above, tl;dr is below)
@gavofyork I've made another attempt to reduce the surface of API changes:

The InvalidTransaction::NoUnsignedValidator is special cases for *_unsigned pipeline so that it doesn't short-circuit, but rather all SignedExtensions are allowed to whitelist a transaction. This changes the semantics only for unsigned transactions (whitelist).
Same behavior for signed transactions is now reverted, so as previously they are valid by default (yet they will be rejected by the transaction pool anyway).

If that approach is going to be rejected as well I will split the PR into smaller improvements/fixes that don't change the semantics, namely:

Extra tests and docs
Passing TransactionSource to SignedExtension
Returning InvalidTransaction instead of UnknownTransaction in case of unsigned validation failure.

Happy for the incremental improvements. Also happy to continue with the approach to try to merge the APIs, but like I say in my previous comment, I think that the primary aspect of the approach must be to allow a pallet to state that a SignedExtension be mandatory for a runtime that includes the pallet since the API is entirely independent of the pallet APIs, and to handle it appropriately in any edge-cases (e.g. with instanceable pallets).

Closing. Will split into smaller PRs.


Board datetime picker as classic widget

The BoardDatetimePickerBuilder is hard to be integrated into an existing page, it needs to be wrapped around the entire page, furthermore if i have many datepickers it's not that immediate to use as i need to map which picker was selected and then get the value and assign to that selected picker.
Wouldn't a classic widget be easier to use? For example a button that when pressed opens a modal bottom sheet with the calendar/pickers and a callback function that returns the value selected as other packages do, that can be found on pub.dev

Thank you very much.
You are right, it would be useful to have a use like a modal bottom sheet.
I will consider implementing it.

@matteoberla
I have added the ability to display the picker in bottom_moda_sheet in version 1.2.0.
Best regards.

Thank you very much, I’ll test it on Monday.
Il giorno sab 28 ott 2023 alle 08:33 mytooyo @.***> ha
scritto:

@matteoberla https://github.com/matteoberla
I have added the ability to display the picker in bottom_moda_sheet in
version 1.2.0.
Best regards.
—
Reply to this email directly, view it on GitHub
https://github.com/mytooyo/board_datetime_picker/issues/4#issuecomment-1783721933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQP6TTUDWNHEIQT5FMXZQGTYBSRNLAVCNFSM6AAAAAA6S37SCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTG4ZDCOJTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


chore: Upgrade Storybook to v7.0.26

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[x] 📦 Chore (Release)
[ ] ⏩ Revert

Description
Upgrade Storybook to v7.0.26
Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@foxyblocks we can land this if you are good on the changes

This was failing on CI for mysterious reasons so I went ahead and ran the upgrade script again. This bumped the version to storybook v7.2 to account for the latest releases


We're attempting to run pact_mock_server_cli from pre- and post-action scripts in an Xcode scheme.
There seems to be no way to stop the master server and all its sub-servers (for our post-action script.) Are we missing something?

You can shut it down by killing the process, but I'll add a shutdown master command.

I've added a shutdown-master which will force the server process to terminate.

This is done now.


IA-2423 Get one Org Unit Change Request

Get one Org Unit Change Request.
Related JIRA tickets:

IA-2423
IA-2229 (Epic)

Self proofreading checklist

[x] Did I use eslint and black formatters
[x] Is my code clear enough and well documented
[x] New translations have been added or updated if new strings have been introduced in the frontend
[x] My migrations file are included
[x] Are there enough tests
[x] Documentation has been included (for new feature)

Changes
Implement GET /api/orgunits/changes/{change_id}/:

new API endoint /api/mobile/orgunits/changes/id
new ThreeDimPointField serializer field

Important notice
Unfortunately, accuracy is not included as originally planned.
Note that it was inconsistent between models.
I used a custom DRF ThreeDimPointField to group attributes of a GeoDjango PointField used with dim=3:

it makes it easier to manipulate a PointField in a DRF serializer in both read and write mode
reusability and validation are built in
it will benefit the rest of the project

How to test

Create OrgUnitChangeRequest objects in admin:

http://localhost:8081/admin/iaso/orgunitchangerequest/
Follow requirements of OrgUnitQuerySet.filter_for_user_and_app_id for ACL compliance

Test API with DRF UI:

Get:

http://localhost:8081/api/orgunits/changes/id

Screenshot

Please add the id to the groups too. Don't use just the names.

Done in #883.


Workspace Settings

💡 Describe the solution you'd like
A clear and concise description of what you want to happen.
A feature that let you decide to sync user settings, workspace settings, or both to a gist
💡 Additional context
As of now I have workspaces for multiple projects that use different settings as well as extensions and it would be helpful if I was able to sync the settings to different gists.

Settings Sync wont sync your all projects workspaces.
but you can manually add this feature using Custom Sync Feature.
Read Wiki here:
https://github.com/shanalikhan/code-settings-sync/wiki/Custom-Sync

Duplicate of #258