工作流报错

Occurrence environment

[X] Workflow
[ ] GUI
[ ] Docker
[ ] Command line

Bug description
你好，昨天同步了最新代码，工作流报错
Error log
2024-12-10T22:35:38.0254888Z Sorting: 100%|██████████| 789/789 [09:30<00:00,  1.36it/s]Traceback (most recent call last):
2024-12-10T22:35:38.0273105Z   File "/home/runner/work/iptv-api/iptv-api/main.py", line 214, in <module>
2024-12-10T22:35:38.0273939Z     loop.run_until_complete(update_source.start())
2024-12-10T22:35:38.0274487Z     ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
2024-12-10T22:35:38.0275542Z   File "/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/asyncio/base_events.py", line 720, in run_until_complete
2024-12-10T22:35:38.0276556Z     return future.result()
2024-12-10T22:35:38.0276941Z            ~~~~~~~~~~~~~^^
2024-12-10T22:35:38.0277567Z   File "/home/runner/work/iptv-api/iptv-api/main.py", line 200, in start
2024-12-10T22:35:38.0278224Z     await self.main()
2024-12-10T22:35:38.0278810Z   File "/home/runner/work/iptv-api/iptv-api/main.py", line 142, in main
2024-12-10T22:35:38.0279554Z     self.channel_data = await process_sort_channel_list(
2024-12-10T22:35:38.0280119Z                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-12-10T22:35:38.0280538Z     ...<3 lines>...
2024-12-10T22:35:38.0280822Z     )
2024-12-10T22:35:38.0281076Z     ^
2024-12-10T22:35:38.0281748Z   File "/home/runner/work/iptv-api/iptv-api/utils/channel.py", line 580, in process_sort_channel_list
2024-12-10T22:35:38.0282657Z     info_list = sort_urls_by_speed_and_resolution(name, info_list, logger)
2024-12-10T22:35:38.0283648Z   File "/home/runner/work/iptv-api/iptv-api/utils/speed.py", line 292, in sort_urls_by_speed_and_resolution
2024-12-10T22:35:38.0284802Z     filter_data.sort(key=combined_key, reverse=True)
2024-12-10T22:35:38.0285284Z     ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-12-10T22:35:38.0285995Z   File "/home/runner/work/iptv-api/iptv-api/utils/speed.py", line 282, in combined_key
2024-12-10T22:35:38.0286949Z     speed, delay, resolution, origin = item["speed"], item["delay"], item["resolution"], item["origin"]
2024-12-10T22:35:38.0287874Z                                        ~~~~^^^^^^^^^
2024-12-10T22:35:38.0288411Z TypeError: tuple indices must be integers or slices, not str
2024-12-10T22:35:41.1325472Z /home/runner/work/_temp/7db0fbc4-d834-4a74-8419-e0a30a09f9fe.sh: line 1:  1896 Segmentation fault      (core dumped) pipenv run dev
2024-12-10T22:35:41.1337289Z ##[error]Process completed with exit code 139.
2024-12-10T22:35:41.1420144Z Post job cleanup.

更新代码，再试试

更新代码，再试试

已无问题，谢谢作者辛勤付出


event.offsetY is reporting unexpected values

Hi,
I am listening for events in an 140x140 layer, but the event param inside the listener handler reports an offsetY property that simply resets after pixel 79 (i.e.: 1, 2, 3 ... 78, 79, 0, 1, 2 ... etc).
I'm really puzzled with this and already checked everywhere in the code to see if something could be impacting this property, but I'm pretty much sure that there's nothing at all. Scope is correct, and even the event.offsetX is working as expected (from 0 to 140).
I'm posting just for the chance that there's anything yet to be reviewed on this.
Thanks!

This has probably recently been fixed by the new point conversion API, so I'm closing this. Please feel free to open a new issue or comment here if you want to follow up on this.


Request: Allow comment-description suffix to csharpier-ignore comments

I would like to be able to specify a "WHY" comment after I add //csharpier-ignore
Example (which is not possible today)
// csharpier-ignore-start -- Keep Matrix formatting
float m11 = m.M11, m12 = m.M12, m13 = m.M13;
float m21 = m.M21, m22 = m.M22, m23 = m.M23;
float m31 = m.M31, m32 = m.M32, m33 = m.M33;
// csharpier-ignore-end

or
// csharpier-ignore -- Class copied as-is from other project, want to keep formatting
internal class Euler {

CSharpier v0.21 does not find comments which start with // csharpier-ignore but have a different ending.
This is a suggestion seen in eslint, and I find it useful to keep the "why-comment" inline.
Example from eslint docs on this feature: https://eslint.org/docs/latest/use/configure/rules#configuration-comment-descriptions
/* eslint eqeqeq: "off", curly: "error" -- Here's a description about why this configuration is necessary. */
Suggested allowed (regexish) format (tests):
\/\/ csharpier-ignore($| --)
This is NOT supported by prettier though, so feel free to close this if you feel it is out of scope.

I'm not sure why prettier doesn't support this, it seems like a good idea to me. If someone was using // csharpier-ignore at work I'd like to understand why they were and this is cleaner than adding another comment above or below it.


Add ol.renderer.dom.VectorLayer#clearFrame

Fixes #4907

Thanks for any review

Looks great, please merge.

Oh wait, I think it is not allowed to set the with and height of a canvas to 0.

Please disregard my previous comment. Everything looks fine. I just tried
canvas.width = 0;
canvas.height = 0;
var context = canvas.getContext('2d');

All without error. So I think this is good to merge.

Thanks for the review

From the spec:

The canvas element has two attributes to control the size of the element's bitmap: width and height. These attributes, when specified, must have values that are valid non-negative integers.


add v:lua support to directly interface with lua global vars from vimscript

This is an inspiration from https://github.com/neovim/neovim/pull/11338 but different implementation and unfortunatly not 100% compatible. It will be good to hear @bfredl thoughts on the neovim implementation and this one.
Here is the list of differences with neovim.

Neovim only seems to support function call while this PR supports all types that can be converted.
Neovim seems to detect v:lua in parser while this PR uses it as a readonly dict with a flag to mark it as a v:lua.
In neovim echo v:lua.vim.fn.has('timer') works but echo v:lua['vim'].fn.has('timer')  doesn't work. In this PR it won't work at all since we can never translate lua tables to vim type as it is required to use vim.dict() or vim.list({}).
Neovim only supports functions so :echo v:lua._VERSION will not work. In this PR you can do :echo v:lua['_VERSION'].
In vim :echo v:lua.print('hello') doesn't work at all and requires explicit brackets use i.e. echo v:lua['print']('hello'). This to me seems like a vim parser bug.

[x] implement v:lua
[ ] add tests
[ ] update docs

lua <<EOF
function hello()
    return 'hello'
end

function world()
    return 'world'
end
EOF

echom v:lua['hello']() . v:lua['world']()

I can only comment based on our intended usages, but:

does it work with function options like set omnifunc=v:lua.myomnifunc ?
can you access nested fields like v:lua.mymod.myfunc(args) without converting other fields of mymod (which could result in errors in case those are not convertible)

For some reason, v:lua behaves differently from a hand-crafted dictionary of functions.  I think maybe <lambda># vs function(<lambda>#) hints at the reason function call syntax doesn't work correctly.  Since this is the usage "in the wild" I think it should be the first supported.
let g:Print = {x->luaeval('print(_A)', x)}
let g:lua = #{print: g:Print}
call g:lua.print('asd')    " works
" asd

echo g:lua
" {'print': function('<lambda>46')}

echo v:lua
" {nothing, probably fine.. but better if it listed the globals}

echo g:lua.print
" function('<lambda>46')

echo v:lua.print
" <lambda>49

This seems to have stalled and there are some conflicts now (and there are still open items, not yet taken care of). So let me close it.


Parse integers directly instead of casting doubles

When parsing numeric values as doubles, its possible for users to
specify values that cannot be converted to integers, such as Inf, NaN,
and extremes such as 1e100.  If this value is received, and then cast to
an int, it is undefined behavior, which trips ubsan when running
tinygltf under a fuzzer.
Instead of parsing integral values as doubles, use nlohmann/json's
built-in support to parse integer and unsigned values directly, with
.is_number_integer() and .is_number_unsigned().
Add ParseIntegerProperty, ParseUnsignedProperty, and
ParseIntegerArrayProperty helpers that allow parsing directly to
int/uint values and update code to use them when appropriate.

Super awesome! This makes tinygltf parser more robust. Thanks!


avoid creating GLOBAL variable and exposing it, created/exported twig.templates namespace

see #92

I've managed to find free time to finish this PR.
@hnrysmth please take a look


Improve a11n

I implemented some WCAG's rules to improve the overall interface accessibility.

Good to go! :+1:


[BUG] Inaccurate CloudFront Requests Metrics

Is there an existing issue for this?

[X] I have searched the existing issues

YACE version
0.61.2
Config file
apiVersion: v1alpha1
discovery:
  jobs:
    - type: AWS/CloudFront
      regions:
        - us-east-1
      roles:
        - roleArn: xxx
      searchTags:
        - key: Project
          value: cdn
      dimensionNameRequirements:
        - DistributionId
        - Region
      period: 60
      length: 60
      metrics:
        - name: Requests
          statistics: [Sum]

Current Behavior
There is an inconsistency between the data seen in YACE logs and the CloudFront console for the same point in time.
At 2024-10-27 12:24:00 UTC, YACE shows 11

while CloudFront console shows 16.

Expected Behavior
The data for both is consistent.
Steps To Reproduce
No response
Anything else?
No response

similar to the #1548

To find the root cause of the problem, I adjusted the period and length parameters, and noticed that the requests metric data settled down after two minutes.
logs with period: 60, length: 180

In the CloudFront requests metrics, the latest pushed data is unstable and takes some time to stabilize, which can also be observed in the console.

after a while.

Referr to the explanation #865, I add the parameter delay: 120, and obtained the stable data.


ui-select dropdown searchbox appears temporarily during the page load

It is hard to get the screenshot. During the page load or reload the drop-down with the search box appears for a fraction of second and disappears like a flash. Any reasons for that? Is it any existing issue?

Is it because of the flicker effect during page load(showing unfinished angular code?

Probably a usage issue, causing by slow connection/loading.

@user378230 I tried using ng-cloak but it is not working in IE and firefox coincidentally works in chrome. May be something wrong in the way using ui-select?

The flicker effect was caused due to the transparency of the dropdown. I've used opacity as 0 in the respective css class and it disappeared. Closing the issue.


Walkthrough setup

Walkthroughs are here and boy are they... ... well they aren't the most attractive thing but they have :sparkles: potential :sparkles:
This PR includes the following:

A new fancy footer and modal!  You can probably close PR #339 if you merge this in.
A walkthrough menu for selecting walkthroughs
some redux reducers for storing the walkthrough state
a new hints box that needs some css love but hey, it's ok for now
the ugliest error messaging you've ever seen
a lot of Bill Murray.  There are 2 example walkthroughs, that exist in /walkthrough/files.   Am I in love with this folder structure? nope.
I am not loading the walkthrough json through "thunks", I am just loading them through require since they exist inside the app. I thought about this and I don't see any reason you might host them outside of the app.

This PR includes:

[x] Tests
[x] functional comments
[x] high level description of any new components

Steps to functionally test this:

click on the WALKTHROUGHS link in the footer
select a walkthrough
follow the prompted steps, or don't follow them and get errors.

The validator is very forgiving. It's only going to check that the things you asked for in the walkthrough spec exist, but if you do extra fancy things like change colors, or fonts or add 17 line marks, it's not going to yell at you as long as you meet the requirement of the prompts. That's by design.

I think this needs some css love and a good functional walkthrough with feedback, but just in case you're feeling merge-happy, please wait until I do some css cleanup and squash these commits.  :)

ok I cleaned up the css and squashed this so it's good to review/merge if it looks ok & travis doesn't die again (I could have sworn we already had lodash in package.js)

Functional +1. This is fantastic. Some minor comments throughout the code.

Removed all the lodash! :O  Made all the updates


Registration Agency: NE-DGI

Hi Aidstream,
Please can the Registration Agency NE-DGI be added to Aidstream?
This is for the Tax Directorate (Niger) - https://github.com/org-id/register/pull/291
Thank you,
Jahnvi

Hi Jahnvidave,
The Registration Agency NE-DGI has been added to Aidstream.
Thank you


Document a working example of concurrent workloads

Some users have asked for a simple example for how to run different workloads against a target system concurrently.
This needs to be a top level example in the docs.

@jshook - Any updates on this specifically for Cassandra?


Upgrade to Calico 2.6.0

What this PR does / why we need it:
Updates calico from  v2.4 Kubernetes Datastore hosted installation to the v2.6.0 Kubernetes Datastore hosted installation, supporting 1.7+ K8s clusters.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
fixes #1417, fixes #1197, fixes #897
Updates calico from  v2.4 Kubernetes Datastore hosted installation to the v2.6.0 Kubernetes Datastore hosted installation, supporting 1.7+ K8s clusters.

The 1.6 failure is expected since calico 2.6 is designed to only work with K8s 1.7 or later.

I found a bug with calico 2.6.0 running on 1.8 ACS engine from Lachie's branch and they fixed it in 2.6.1
https://github.com/projectcalico/calico/issues/1131#issuecomment-333281999

@dtzar The best way to manage calico going forward given that different versions of calico work better on different versions of Kubernetes is to dynamically assign the image variable string depending on the version of Kubernetes.
The implementation is clunky, but a representative example is the dashboard image. To get started, look at the Kubernetes version-specific constants defined in pkg/acsengine/const.go, e.g.:
https://github.com/Azure/acs-engine/blob/master/pkg/acsengine/const.go#L95
The "dashboard" key for each version is consumed thusly in pkg/acsengine/engine.go:
https://github.com/Azure/acs-engine/blob/master/pkg/acsengine/engine.go#L541
Continuing this example, search for all instances of kubernetesDashboardSpec in the codebase and you will be able to follow how the assignments are dispatched along the pasta sauce. Let me know if you have any more questions!

cc @ozdanborne

There are significant changes in 2.6.x which only work with 1.7+ which means that we really need an entirely separate YAML file for the addons.  This is why I made this change.
It would be great to know the long-term plan from @ozdanborne on which versions of calico node/cni they plan to keep compatible with what version(s) of K8s.  In looking through the release notes, it seemed like there weren't any significant changes from 2.4.1 --> 2.5.1 so I left the version of calico at 2.4.1 for K8s 1.5 and 1.6.  Please let me know if you believe it should be otherwise.  Once we know the plan/strategy here, then this will help inform the need for when we may (or may not) need to implement the similar strategy to what is done with the dashboard spec as @jackfrancis has mentioned above.

@jchauncey Is there a problem with at least the k8s-1.7-release-e2e test itself?  I did a local acs-engine build and deployed a calico and a non calico 1.7 K8s cluster successfully.

Yeah I am working on a fix for those tests right now.

I think we can get this in without worrying that https://github.com/Azure/acs-engine/blob/master/parts/kubernetesmasteraddons-calico-daemonset1.5.yaml is still at Calico v2.4, especially since Calico v2.5 was mainly KDD updates for compatibility with k8s-v1.7.

/lgtm

{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorRelease": "1.8",
      "kubernetesConfig": {
        "clusterSubnet": "<IP_ADDRESS>/23",
        "networkPolicy": "calico",
        "enableRbac": true
      }
    },
    "masterProfile": {
      "count": 3,
      "dnsPrefix": "dev-eu2-m",
      "vmSize": "Standard_D2_v2",
      "vnetSubnetId": "/subscriptions/REDACTED/resourceGroups/dev-eu2/providers/Microsoft.Network/virtualNetworks/dev-eu2-vnet/subnets/dev-eu2-k8s-subnet",
      "firstConsecutiveStaticIP": "<IP_ADDRESS>",
      "vnetCidr": "<IP_ADDRESS>/19"
    },
    "agentPoolProfiles": [
      {
        "name": "agent",
        "count": 3,
        "vmSize": "Standard_D3_v2",
        "vnetSubnetId": "/subscriptions/REDACTED/resourceGroups/dev-eu2/providers/Microsoft.Network/virtualNetworks/dev-eu2-vnet/subnets/dev-eu2-k8s-subnet",
        "availabilityProfile": "AvailabilitySet"
      }
    ],
    "linuxProfile": {
      "adminUsername": "user",
      "ssh": {
        "publicKeys": [
          {
            "keyData": "REDACTED"
          }
        ]
      }
    },
    "servicePrincipalProfile": {
      "clientId": "REDACTED",
      "secret": "REDACTED"
    }
  }
}

@zimmertr The newest calico release 2.6.2 has NO changes relevant for Kubernetes, per the release notes.  It is likely some other commit which touched etcd (like PR 1564) caused problems.  Please file a new issue.

@dtzar thank you for your feedback. I've made a new issue which can be found here: https://github.com/Azure/acs-engine/issues/1621

@dtzar thank you for your feedback. I've made a new issue which can be found here: #1621
Can you elaborate on which software you intend for me to revert back to 0.8.0? etcd?

Build or download/use the acs-engine binary from this commit/release https://github.com/Azure/acs-engine/releases/tag/v0.8.0


fix: same manifest folder rules shouldn't be declared multi times

warn users with a warning, raise exception when user passed --check-manifest-rules flag

Hello, I have tested the solution, and it LGTM.
Maybe we can add sorting for paths in the 'from_files' method (def from_files(cls, paths: t.List[str])) to make the result independent of the '--manifest-file' input?

Hello, I have tested the solution, and it LGTM. Maybe we can add sorting for paths in the def from_files(cls, paths: t.List[str]) to make the result independent of the '--manifest-file' input order?

Hi @horw, the sort will happen on Manifest.__init__


Question: Why Moondream?

The README says use Moondream for local Ollama use?  "Install moondream if you want to use the incognito mode"
Moondream is a very small 1.6B parameter LLM that is oriented around vision tasks which, according to its Web site, has limitations.
See here:
https://medium.com/@scholarly360/moondream2-tiny-visual-language-model-for-document-understanding-df75ab1e0a02
Moondream2: Tiny Visual Language Model For Document Understanding
Why on earth would this model be recommended over using one of the more common 7B or higher models such as Qwen2 or Llama3? Or for that matter, the Microsoft Phi models, the smallest of which was used to create Moondream? I've run Phi Mini and Phi Medium on my machine easily.
If you're going to enable running entirely locally using Ollama, might as well let it use any of the main LLMs Ollama supports.

Totally agree, good point, I am having trouble to use my local Ollama in this too, Ollama runs well in flowise now...any help?

Totally agree, good point, I am having trouble to use my local Ollama in this too, Ollama runs well in flowise now...any help?

We might swap it out for Gemini but that wouldn’t be offline ;)
Would having a toggle for more powerful, online models be of interest?


When I pass the parameter by put method, I got nothing.

I use restful api, and pass the parameters by postman with put method.
But I can not get any paramters.
What steps will reproduce the problem?
$request = Yii::$app->request;
if ($request->isPut) {
      var_dump($request->bodyParams);
      var_dump($request->getBodyParam('title'));
     exit;
}

What is the expected result?
the passed value of title, such as title = "test".
What do you get instead?
Additional info

Q
A

Yii version
Yii 2.0.18 dev.

PHP version
php 7.2

Operating system
Windows 7

How do you pass parameters?


XmlRpcClient not found

Hi dude.
After adding the dependency to pom file and installing, it only downloads xmlrpc-common, but it does not install XmlRpcClient.
Any idea why?

Hi @fdbatista ,
You can add xmlrpc-client dependency in pom.xml, as shown below :
<dependency>
    <groupId>org.apache.xmlrpc</groupId>
    <artifactId>xmlrpc-client</artifactId>
    <version>3.1.3-2</version>
</dependency>

When you run mvn compile, you can check the console log, something like:
Downloading from fillzero-maven-repo: https://raw.githubusercontent.com/fillzero/apache-xmlrpc/master/maven-repo/repository/org/apache/xmlrpc/xmlrpc-client/3.1.3-2/xmlrpc-client-3.1.3-2.pom

Downloading from fillzero-maven-repo: https://raw.githubusercontent.com/fillzero/apache-xmlrpc/master/maven-repo/repository/org/apache/xmlrpc/xmlrpc-client/3.1.3-2/xmlrpc-client-3.1.3-2.jar

Yes, I really don't know what happened. Dependencies were being downloaded, but the packages were not available.
I just closed/reopen the application in Intellij and suddenly it started to work.
Thanks!


TokenDumper exists with "Failed to create CoreCLR, HRESULT: 0x80004005"

Could not find a repository for the Token-Dumper, so reporting it here.
Nothing more than this message:
$ ./SteamTokenDumper
Failed to create CoreCLR, HRESULT: 0x80004005

$ uname -r
Linux HOSTNAME 5.3.0-7625-generic #27~1576774560~19.10~f432cd8-Ubuntu SMP Thu Dec 19 20:35:37 UTC  x86_64 x86_64 x86_64 GNU/Linux

I'm not sure if this might help, but i ran strace. Here's the log:
log_SteamTokenDumper.txt

This appears to be some kind of generic .NET Core issue, can't really help with that.

Okay, will use the Windows version as soon as I'm on a Windows PC.
Keep up the good work, really cool Idea :+1:

This appears to have been caused by publishing incorrectly. I uploaded a new build which should work.


KAFKA-14495: assert the cache size for each operation

Improve the test verification to make sure the cache size is expected before and after each call.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@satishd , call for review. Thanks.


fix: ui bugs

ui -> 300.1

:tada: This PR is included in version 0.279.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Breaking change - Searching for NormUniqueId now requires {}

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
not applicable
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[X] other (enter in the "Additional environment details" area below)

Additional environment details
Microsoft Search
Describe the bug / error
MS Search 'NormUniqueId' managed property value syntax has changed from 'GUID' to '{GUID}'.
All the queries that used old syntax stopped working.
We had been using NormUniqueId in this way due to the suggestion made  on this issue:
https://github.com/SharePoint/sp-dev-docs/issues/7160
Steps to reproduce
Execute query to obtain result for an item. Observe the NormUniqueId property.
Expected behavior
Support old syntax of the 'NormUniqueId' Managed Property in the search results.
Example using rest API:
This does not return a result:
/_api/search/query?querytext=%27NormUniqueId:55555555-5555-5555-5555-555555555555%27&selectproperties=%27NormUniqueId%27&clienttype=%27ContentSearchRegular%27
This does:
/_api/search/query?querytext=%27NormUniqueId:{55555555-5555-5555-5555-555555555555}%27&selectproperties=%27NormUniqueId%27&clienttype=%27ContentSearchRegular%27
Twitter discussion: https://twitter.com/vesajuvonen/status/1519303753521938433

In addition, it seems like uniqueID in some tenants have brackets {} and some of them don't have.
Search Query Results from different tenants:

@cawillwe can you retry, and ensure you use the schema casing of NormUniqueID on your query, as casing on properties can have an impact on how it works. I blogged briefly about casing at https://www.techmikael.com/2019/02/eh-ok-beware-of-casing-when-using.html, and seems to apply to more properties

This has been fixed.


Fix various nullability problems in OpenXmlCompositeElement and OpenXmlElement

The MaybeNull attribute is redundant in these cases - the nullability is well covered by the NotNullIfNotNull attribute solely.

Happy to explore different ways of annotating this stuff, but we can't introduce breaking changes.

/azp run


[Draft] Training and Certification doc updates

Purpose of this pull request
This pull request updates Training and Certification doc
Select the type of change

[x] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-310

@kimsauce, will this PR be ready to review soon? It would be nice to get this published before we update the training information for an upcoming rebrand (DOCS-452).

Closing this out in favor of rebrand


Azure File storage support for Remote content library and package source

Is Azure File storage supported hosting the Remote content library and package source?

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

ID: 0a6a4e18-8d5c-dc3b-f189-cfeacd9f7b68
Version Independent ID: 64456d54-bf60-ea66-4037-6995409375cb
Content: High availability - Configuration Manager
Content Source: sccm/core/servers/deploy/configure/high-availability-options.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @santoshseth for the feedback. It's a duplicate of #1285, here's my response:
We've not tested this configuration, so not sure if it will work, thus not supported. If Azure is sharing the content as any Windows file share, then it might just work. But again, not something we've tested. If you want the product to consider support for this scenario, please file product feedback.
I'm closing this issue as there's nothing actionable for docs at this time; we don't generally document what we don't support.


Adding Manacker algorithm

Hello. I would add Manacker algorithm for searching all palindromes in the sequence in O(N).

Hello, is it completed? Are you going to continue it?


[Update Request]: Dell Command | Update

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
Dell.CommandUpdate
Package Version
4.9.0
Please describe the changes you would like to see
There is a new release (4.9.0) available.
Download Page Url: https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=30f6m

There's yet another update to this package; it has version 5.0.0 now.

See https://github.com/microsoft/winget-pkgs/pull/122364 and https://github.com/microsoft/winget-pkgs/pull/122363
Unfortunatly we cannot update it until this has been implemented in winget: https://github.com/microsoft/winget-cli/issues/1417

How did the packages make it in to begin with if the validation process fails due to non-Dell hardware? The packages should be dropped until they can be updated as older DCU versions are known to be vulnerable.

The reason is simple: In earlier versions dell did not check if the manufacturer is Dell and the application installed fine.
The package should not be dropped therefore.

I really disagree to be honest... There's present vulnerabilities in versions prior to 4.9.0 that make it dangerous to use in production systems. https://www.dell.com/support/kbdoc/en-au/000213546/dsa-2023-170-dell-command-update
Someone needs to accept the PR for the new versions despite the validation error due to incompatible hardware, or drop the package. It's not acceptable that Microsoft's repository ships insecure and outdated versions that have been patched upstream.

Does command update not have a built in self-updater? I was sure it did.
Getting a version installed and then running dcu-cli.exe /applyUpdates via whatever remote administrative tool is being employed should automatically handle it.

I'm sorry man, but I see that as akin to installing Windows 11 21H2 and letting Windows Update get it up to 23H2. As with my last comment, 4.6.0 has known vulnerabilities and is not something I want on my systems for even a second.
I've seen packages that fail to build in the PR CI/CD pipeline get manually pushed, I don't know what the problem is for doing the same with these now-vulnerable Dell packages also.

@stephengillie Just bringing your attention to this one and looking for your input.
TL:DR;
Current versions available via winget didn't need Dell hardware to pass check, newer versions require hardware check, current versions are vulnerability ridden.
New versions (5.2.0) opened here #138818 and here #138817 are up to date, but won't pass validation due to hardware req on the validation worker (see: #1417).
Any chance these two PRs can get a pass so that users can upgrade to a safe version, or should best practice be to remove current manifests from winget due to their security issues? Or additional option/route (maybe get manifest tested/verified by contributors with appropriate hardware/spec)?

Hi @BiosPlus,
The difficulty is that if we can't install these packages correctly, then we can't scan them correctly. Since the developer has added this requirement that effectively blocks our VMs from installing their product, we aren't able to validate new versions, and the best course of action is to remove their older software from the repo as well.

Hi @stephengillie,
so what would be the process to unlist a package, as we can't maintain this any longer?

7 PRs will need to be opened, to remove the old manifest files - one PR per set of (usually 3) manifest files. Versions: 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.1, 4.1.0, 2.4.0

Super curious how this finally got updated after months of issues, but thanks to everyone involved!

@mjr4077au these flags would be why.
InstallerSwitches:
  Silent: /passthrough /S /V/quiet /V/norestart
  SilentWithProgress: /passthrough /V/passive /V/norestart
  Interactive: /passthrough
  InstallLocation: /VDELL_COMMAND_UPDATE="<INSTALLPATH>"
  Log: /V"/log ""<LOGPATH>"""
  Custom: /VREMOVE="CLI" /VADDDEFAULT="ALL"

I can't see them documented anywhere, so I'm not above still giving the one finger salute to dell on this one.

@mjr4077au these flags would be why.
InstallerSwitches:
  Silent: /passthrough /S /V/quiet /V/norestart
  SilentWithProgress: /passthrough /V/passive /V/norestart
  Interactive: /passthrough
  InstallLocation: /VDELL_COMMAND_UPDATE="<INSTALLPATH>"
  Log: /V"/log ""<LOGPATH>"""
  Custom: /VREMOVE="CLI" /VADDDEFAULT="ALL"

I can't see them documented anywhere, so I'm not above still giving the one finger salute to dell on this one.

They can never be documented. It is kinda installer switches tricks.


Unexpected end of input with comments

I just ran into this with comments and was wondering if it was expected behavior.
[1] pry(main)> src = "; this is a comment"
=> "; this is a comment"
[2] pry(main)> SXP::Reader::Scheme.read(src)
SXP::Reader::EOF: unexpected end of input
from /Users/amedeiros/.rvm/gems/jruby-<IP_ADDRESS>@scheme/gems/sxp-1.0.0/lib/sxp/reader.rb:155:in `read'

Awesome thank you!


Can't run NaverLogin.login

Hi @dooboolab ,
When i run my app, in onNaverLogin function:
If i use name: kConsumerKey, kConsumerSecret, kServiceAppName, kServiceAppUrlScheme
const initials = {
      kConsumerKey: 'VN6WKGFQ3pJ0xBXRtlN9',
      kConsumerSecret: 'AHBgzH9ZkM',
      kServiceAppName: 'dooboolab',
      kServiceAppUrlScheme: 'dooboolaburlscheme', // only for iOS
};

then app crash: Unfortunately, app has stopped
If i use name: key, secret, name, urlScheme
const initials = {
	key: 'VN6WKGFQ3pJ0xBXRtlN9',
	secret: 'AHBgzH9ZkM',
	name: 'dooboolab',
	urlScheme: 'dooboolaburlscheme', // only for iOS
};

then run to "console.log(props);" then stop:
const naverLogin = (props) => {
  return new Promise(function (resolve, reject) {
      console.log(props);
      NaverLogin.login(props, (err, token) => {
        console.log(`\n\n  Token is fetched  :: ${token} \n\n`);
        ...
      });
  });
};

This is my config:
"dependencies": {
    "apsl-react-native-button": "^3.1.0",
    "react": "16.0.0-beta.5",
    "react-native": "0.49.3",
    "react-native-extended-stylesheet": "^0.7.0",
    "react-native-naver-login": "^1.0.6",
    "react-navigation": "^1.0.0-beta.13"
  }

Can you help me? Thanks

@teemobk
Can you tell me which OS did you face error?

There was a bug in iOS bridge methods. Sorry for that.
The constants example of Readme file was wrong.  kConsumerKey ...  are right.
Please refer to the newest Readme. Sorry for that too.
Please upgrade to newest version.

Thanks @dooboolab and @JJMoon ,
I run on Android. About error: Unfortunately, app has stopped, i add to /android/app/src/main/AndroidManifest.xml:
<activity
        android:name="com.nhn.android.naverlogin.ui.OAuthLoginActivity"
        android:screenOrientation="portrait"
        android:theme="@android:style/Theme.Translucent.NoTitleBar" />
<activity
        android:name="com.nhn.android.naverlogin.ui.OAuthLoginInAppBrowserActivity"
        android:label="OAuth2.0 In-app"
        android:screenOrientation="portrait" />

Fixed!
Great, Thank you very much^^

@teemobk
OMG.. Sorry man.

Your error looks like the error in the package name because I have set the default pacakage name.
I will update this library to npm 1.0.8 fixing the problem.

Then you will have to define applicationId in app/build.gradle file.

Thank you very much!^^


Dawnsilver is currently not bypassing Devil's Physical resistance.

The description for Dawnsilver in GM Core page 253 states: Dawnsilver is renowned for its lightness, durability, and effectiveness against a range of creatures including devils and werecreatures. It has the same sheen as silver but a slightly lighter hue. Dawnsilver weapons and armor are treated as if they were silver for the purpose of damaging creatures with weakness to silver.
While this doesn't specify it also works as silver to bypass Physical resistance, the fact it's mentioning devils in the description, and that no devils have weakness to Silver, I believe it is RAI that Dawnsilver should bypass this resistance just as silver does.
Thank you.

Gonna have to write a letter to Dr. Paizo, sorry.


add double free version of tcache poisoning

and a new version of tcache poisoning.
BTW, can we use something like setvbuf so that we don't have to use fprintf(stderr, ...) ?
It is quite awkward to do that.

tested on ubuntu 18.04

and a new version of tcache poisoning.
BTW, can we use something like setvbuf so that we don't have to use fprintf(stderr, ...) ?
It is quite awkward to do that.

Is setvbuf a heap safe function?
By the looks of this implementation, it isn't

why does "heap safe" matter?  It uses heap but it does not do anything to our heap layout. They are just buffers of stdout, stdin object.
And by the way, it can be "heap safe".
Here is the poc:
#include <stdio.h>
#include <stdlib.h>

int main()
{
    setbuf(stdout, NULL);
    setbuf(stdin, NULL);

    malloc(0x10);
    printf("test");
    getchar();
}

gef➤  x/100gx 0x0000555555756000
0x555555756000:	0x0000000000000000	0x0000000000000251
0x555555756010:	0x0000000000000000	0x0000000000000000
0x555555756020:	0x0000000000000000	0x0000000000000000
0x555555756030:	0x0000000000000000	0x0000000000000000
0x555555756040:	0x0000000000000000	0x0000000000000000
0x555555756050:	0x0000000000000000	0x0000000000000000
0x555555756060:	0x0000000000000000	0x0000000000000000
0x555555756070:	0x0000000000000000	0x0000000000000000
0x555555756080:	0x0000000000000000	0x0000000000000000
0x555555756090:	0x0000000000000000	0x0000000000000000
0x5555557560a0:	0x0000000000000000	0x0000000000000000
0x5555557560b0:	0x0000000000000000	0x0000000000000000
0x5555557560c0:	0x0000000000000000	0x0000000000000000
0x5555557560d0:	0x0000000000000000	0x0000000000000000
0x5555557560e0:	0x0000000000000000	0x0000000000000000
0x5555557560f0:	0x0000000000000000	0x0000000000000000
0x555555756100:	0x0000000000000000	0x0000000000000000
0x555555756110:	0x0000000000000000	0x0000000000000000
0x555555756120:	0x0000000000000000	0x0000000000000000
0x555555756130:	0x0000000000000000	0x0000000000000000
0x555555756140:	0x0000000000000000	0x0000000000000000
0x555555756150:	0x0000000000000000	0x0000000000000000
0x555555756160:	0x0000000000000000	0x0000000000000000
0x555555756170:	0x0000000000000000	0x0000000000000000
0x555555756180:	0x0000000000000000	0x0000000000000000
0x555555756190:	0x0000000000000000	0x0000000000000000
0x5555557561a0:	0x0000000000000000	0x0000000000000000
0x5555557561b0:	0x0000000000000000	0x0000000000000000
0x5555557561c0:	0x0000000000000000	0x0000000000000000
0x5555557561d0:	0x0000000000000000	0x0000000000000000
0x5555557561e0:	0x0000000000000000	0x0000000000000000
0x5555557561f0:	0x0000000000000000	0x0000000000000000
0x555555756200:	0x0000000000000000	0x0000000000000000
0x555555756210:	0x0000000000000000	0x0000000000000000
0x555555756220:	0x0000000000000000	0x0000000000000000
0x555555756230:	0x0000000000000000	0x0000000000000000
0x555555756240:	0x0000000000000000	0x0000000000000000
0x555555756250:	0x0000000000000000	0x0000000000000021
0x555555756260:	0x0000000000000000	0x0000000000000000
0x555555756270:	0x0000000000000000	0x0000000000020d91
0x555555756280:	0x0000000000000000	0x0000000000000000
0x555555756290:	0x0000000000000000	0x0000000000000000
0x5555557562a0:	0x0000000000000000	0x0000000000000000
0x5555557562b0:	0x0000000000000000	0x0000000000000000
0x5555557562c0:	0x0000000000000000	0x0000000000000000
0x5555557562d0:	0x0000000000000000	0x0000000000000000
0x5555557562e0:	0x0000000000000000	0x0000000000000000
0x5555557562f0:	0x0000000000000000	0x0000000000000000
0x555555756300:	0x0000000000000000	0x0000000000000000
0x555555756310:	0x0000000000000000	0x0000000000000000

The first chunk is tcache list object, it is inevitable. If you are on ubuntu 16.04, you should not see that chunk.

and as far as I know, printf uses alloc to allocate memory during formatting, and zero them out after execution most of the time. There is one exception, if you do something very large, it uses malloc.

@Kyle-Kyle thanks for creating this example.
It is fairly similar to the tcache_poisoning, just makes the mechanism that gives you the ability to modify the forward pointer of a freed tcache chunk more explicit.
Considering, there is a check merged already preventing this "straightforward" way of exploiting a double free, I would prefer modifying this example, so it bypasses the check, which is pretty "straightforward" as well and gives a good example on how to do slightly more complicated tcache exploits.

@m1ghtym0 I take the tweet back. The security check is not that stupid, at least I can't do the same thing to smallbin without libc leak.

Oh yes we can. But that will be another technique. And even more complicated. Let me leave it to others. XD.

BTW, I just checked it on latest libc. I does not work. But if I tweak it a liiiiiitle bit. It works.
I will upload the working poc after iCTF.

It's a neat way of playing with tcache, let's add it:-)


allow using different challenge per domain

Hi,
I would like to create a certificate for the domains *.example.org, example.com and example.net.
As *.example.org is a wildcard domain, it needs to be verified with the dns challenge.
However, I would like to verify example.com and example.net with the http challenge.
Unfortunately, this is not possible with dehydrated at the moment.
Therefore I'd like to make a feature request to implement this :-)

Have you set HOOK_CHAIN=no in your config? The default behavior (outlined at https://github.com/dehydrated-io/dehydrated/blob/master/docs/hook_chain.md) is to deploy, verify, and clean on challenge, then deploy, verify, and clean the next challenge in sequence, and so on.

this is possible already you can do per cert settings see https://github.com/dehydrated-io/dehydrated/blob/master/docs/per-certificate-config.md

this is possible already you can do per cert settings see https://github.com/dehydrated-io/dehydrated/blob/master/docs/per-certificate-config.md

That does not cover the example given by @Yannik, where there is only ONE cert created with different challenge types per SAN.


AttributeError: type object 'Executer' has no attribute 'setup'

Just a bug report. I'm trying to use the new @Device.setup decorator (I am on v0.14.1), but I get the following error:
from belay import Device
import time

class PicoW(Device):
    @Device.setup
    def setup():
        led = Pin('LED', Pin.OUT)

    @Device.task
    def led_toggle():
        led.toggle()

if __name__ == "__main__":
    picoW = PicoW('/dev/cu.usbmodem14240')
    picoW.setup()
    picoW.led_toggle()
    time.sleep(2)
    picoW.led_toggle()
    picoW.close()

# Traceback (most recent call last):
#   File "/Users/roaldarbol/MEGA/Documents/sussex/research/experiments/experiments/PicoW.py", line 14, in <module>
#     picoW = PicoW('/dev/cu.usbmodem14240')
#   File "/usr/local/lib/python3.10/site-packages/belay/device.py", line 251, in __init__
#     executer = getattr(Executer, metadata.executer.__registry__.name)
# AttributeError: type object 'Executer' has no attribute 'setup'

Fixed in #59 and v0.14.2. Don't know how that slipped through, sorry about that!

Haha, no apologies needed! I’ll check later🤘🏼


AZ-418: Add per peer buffering

I applied changes suggested off-github, to reduce number of created NotificationSenders


ISSUE: ValueError: unconverted data remains: ,

Describe the bug
I'm able to authenticate to outlook. However no sensors updating due to this.
I do have to use an App Password, and i have 2FA (but the app password should i believe nullify the need for 2FA)
Environment (please complete the following information):

OS: Unraid
Type of device: PC
Home Assistant version: 2021.3.4
Hassio/Docker/Core?  Docker core
Component version: 0.3.1

Logs
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 151, in async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 139, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/mail_and_packages/__init__.py", line 78, in async_update_data
    return await hass.async_add_executor_job(process_emails, hass, config)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/mail_and_packages/helpers.py", line 128, in process_emails
    fetch(hass, config, account, data, sensor)
  File "/config/custom_components/mail_and_packages/helpers.py", line 229, in fetch
    count[sensor] = get_items(account, const.ATTR_COUNT, amazon_fwds)
  File "/config/custom_components/mail_and_packages/helpers.py", line 971, in get_items
    dateobj = datetime.datetime.strptime(
  File "/usr/local/lib/python3.8/_strptime.py", line 568, in _strptime_datetime
    tt, fraction, gmtoff_fraction = _strptime(data_string, format)
  File "/usr/local/lib/python3.8/_strptime.py", line 352, in _strptime
    raise ValueError("unconverted data remains: %s" %
ValueError: unconverted data remains: ,

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Please add emails in plain/text format if possible and applicable.

Please try the beta 0.3.2-b8 and see if that resolves your issue.


Add Component Management page

Description
Add Component Management page
Add Component Management API (Pkgpanda Swagger UI)
Urgency

[ ] Blocker
[ ] High
[X] Medium

Pkgpanda and AdminRouter are two different components. I'm working on another approach for documenting AdminRouter, which can't really use Swagger.

@emanic: Can you add tags to it upstream? I don't want to have this doc be different than the upstream doc. https://github.com/dcos/dcos/blob/master/pkgpanda/docs/http-swagger.yaml

I rewrote the text to make a few distinctions more obvious:

api vs impl component
package managere vs package builder
routes vs resources

I added tags to the yaml and made a PR for upstreaming them: https://github.com/dcos/dcos/pull/1362

Tags have been approved int he upstream PR.

Commits squashed.


IPFS Weekly #11

Here’s the crosspost of the weekly #11 for the blog.

This already went through a review in the newsletter repo, do we need any other review before we get it merged?


Using a denon 4310 only the first command works.

It looks like the default for the telnet client library is to use input/output record separators of irs=\r and ors=\r\n (or maybe the other way around, sorry, doing this by memory), however, my receiver does not use \n at all, it strictly wants a \r only as separator.  This is an easy fix by changing connectionparams to include ors and irs set to '\r', however I don't have a more modern AVR to test this with... but I guess you do?
I would imagine someone thought that limiting it to \r as a delimiter was dumb and updated the software at some point. If it turns out that \r only works on newer AVRs, perhaps it would help someone else out there?
Thanks for creating this library, I am using it for a roon extension to control my AVR's volume (there is one that already exists, but it doesn't work for my AVR, I guess it is too old).

Yes, they are picky about separators. I'm going to test \r this evening.

I have no doubt you were able to make the change... but now I'm in front of my computer, I can post a diff:
@@ -28,11 +28,13 @@ var MarantzDenonTelnet = function(ip) {
     this.connectionparams = {
         host: ip,
         port: 23,
         timeout: 1000, //  The RESPONSE should be sent within 200ms of receiving the request COMMAND. (plus network delay)
         sendTimeout: 1200,
-        negotiationMandatory: false
+        negotiationMandatory: false,
+        ors: '\r', // Set outbound record separator
+        irs: '\r'
     };
     this.cmdCue = [];
     this.connection = null;
 };

Finally came around to test this on my receivers and it runs without hiccups. Txs!


[Feature Request]: add configuration to allow the override of the current allure report html file

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
configuration to allow the override of the current allure report html file

Dear @themosaeed , kindly explain more what you mean by override current html , do you mean keep history and each time html report contains current and past run ?

@zanoon2020  right now the behavior is that with each run a new HTML report is generated and added to the folder alongside the old one. What we need is the option to do this or delete the old one and keep only the most recent report.

Dear @themosaeed if you are using custome property file try the below property and feedback :
cleanAllureResultsDirectoryBeforeExecution=true
But take into consideration that will wipe the allure history and just keep the last run.

@zanoon2020  this clears the allure-results folder but doesn't delete the old HTML report generated in allure-report folder. still adds new one and keeps the old HTML file

Thanks @themosaeed for feedback ,
We will discuss it and get back to you

@zanoon2020 what I understand is that we need to modify the behavior of "cleanAllureResultsDirectoryBeforeExecution" to clean both the allure results and allure reports directories.
which makes sense...
shall I leave that to you? I remember you wanted to pickup a small task to warm up.

@MohabMohie i think the question is , we want to clean allure results directory and leave allure report history. And in this situation allure report folder will have it's own flag. Do you agree on this

related to #1566
I will restructure the current allure properties and move them to a dedicated "Allure" properties object for better management. this will be a breaking change but will allow the user more customization.


Migrate to mongodb

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 36 (80.56%)  changed or added relevant lines in 11 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.04%) to 90.653%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/events/events.service.ts
6
8
75.0%

src/transactions/transactions.service.ts
4
9
44.44%

Totals

Change from base Build<PHONE_NUMBER>:
-1.04%

Covered Lines:
519

Relevant Lines:
547

💛  - Coveralls


[Migration] chart: timescaledb-single. Migrating secrets as per v0.10.0 upgrade guide fails:  templates/secret-certificate.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 2: did not find expected node content

Have a look at Troubleshooting or some Common Issues

Describe the bug
Empty secret templates such as service-patroni.yaml prevent helm from successfully completing the templates rendering when following k8s secrets migration from v0.10.0 upgrade guide.
Changes:

Deleted: Secrets provided via Kustomize.
Added: secrets.credentialsSecretName: "foobar-credentials" (+ 2 credentials params)

To Reproduce
Both commands fail with the same error (the 1st command being the most important as it prevents proper chart deployment: we do helm template ... and then kubectl apply ...)
Note: foobar-timescaledb-timescaledb-single-original is simply the original chart folder name being renamed by a script on my end.
Command 1:
helm template foobar-timescaledb-timescaledb-single-original --values foobar-timescaledb-timescaledb-single-custom/values.yaml --name-template foobar --output-dir foobar-timescaledb-timescaledb-single-final/

Command 2:
helm lint foobar-timescaledb-timescaledb-single-original --values foobar-timescaledb-timescaledb-single-custom/values.yaml

Expected behavior
Template rendering to not fail for this configuration.
Deployment

Chart: timescaledb-single
values.yaml: See bug description section.
Chart: 0.10.0
k8s: 1.20.x

Deployment
None, the template rendering fails on a local machine, without ever needing to talk to the k8s cluster.
Logs
+ helm lint foobar-timescaledb-timescaledb-single-original --values foobar-timescaledb-timescaledb-single-custom/values.yaml
==> Linting foobar-timescaledb-timescaledb-single-original
[INFO] Chart.yaml: icon is recommended
[ERROR] templates/secret-certificate.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 2: did not find expected node content
[ERROR] templates/secret-patroni.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 2: did not find expected node content
[ERROR] templates/secret-pgbackrest.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 2: did not find expected node content

Error: 1 chart(s) linted, 1 chart(s) failed

Additional context
Deleting those files allows the command to successfully complete: secret-certificate.yaml, secret-patron.yaml, secret-pgbackrest.yaml

@feikesteenbergen @thedodd Pinging you guys :-)

This should've been fixed in latest helm chart release after https://github.com/timescale/helm-charts/pull/327 was merged. If you find that the problem is still happening in your environment, please reopen this ticket.


why there is logits_per_image.t() in contrastive loss?

Hello, there!
In the https://github.com/adymaharana/VLCStoryGan/blob/74112404689e8144c2ed2d375e1e5a1cde09debb/vlcgan/miscc/utils.py#L163, there is two kinds of loss values (loss_i and loss_t) in line 184 and 185.
And the function calculate the average of them.
https://github.com/adymaharana/VLCStoryGan/blob/74112404689e8144c2ed2d375e1e5a1cde09debb/vlcgan/miscc/utils.py#L186
Why to calculate like this? I didn't figure out the meaning of this. And what is the difference with the loss below?
loss = loss_fct(logits_per_image, labels)

one is for image, and the other is for text.
the reference is the figure 3 in the paper 'Learning Transferable Visual Models From Natural Language Supervision'.


[consoleApp] [Manage] Secondary userstore added via console manage cannot be deleted from the management console

Describe the issue:
Secondary userstore added via console cannot be deleted from the management console
How to reproduce:
1.Access https://localhost:9443/console
2.Login as super admin
3.Navigate to Manage > Userstores > New Userstore > JDBC
4. Add a maria db Userstore as a secondary userstore by giving the necessary details
4.Save
5. Go to added userstore edit view > Enable Userstore
6. Update
7. Login to managementconsole
8. Try to delete the added userstore from management console
Observation
Cannot delete the userstore from the management console
Environment information
Mssql 2019
uniqueid jdbc primary US
IS 5.11.0 beta3
ubuntu 16.04
Chrome Version 85.0.4183.121

Couldn't reproduce this issue with 5.11.0-beta4. Hence closing this issue.


REST update device not working?

I send a post request to update this device:
2016-12-21 17:43:32,227:IH:INFO: request:post: http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 17:43:32,228:IH:INFO: request:post: body={'name': u'Family Room Floor Lamp', 'dimUrl': 'http://.../${intensity.byte}', 'mapId': u'isy:2E 59 94 1', 'deviceType': 'custom', 'onUrl': 'http://.../DON', 'offUrl': 'http://.../DOF', 'httpVerb': 'GET'}
2016-12-21 17:43:32,246:IH:INFO: request:connect:success: url=http://<IP_ADDRESS>:8090/api/devices/23

Is this what is expected to be returned?
2016-12-21 17:43:32,248:IH:DEBUG: request:connect:success: text=[{"success":{"username":"912e5d00ba644e7ca94a51508fe8c9bf"}}]

And to see if it actually changed the "name", I grab it to see:
2016-12-21 17:43:32,249:IH:INFO: request:get: http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 17:43:32,265:IH:INFO: request:connect:success: url=http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 17:43:32,266:IH:DEBUG: request:connect:success: text={"id":"23","uniqueid":"00:17:88:5E:D3:17-17","name":"Floor Lamp","mapId":"isy:2E 59 94 1","deviceType":"custom","offUrl":"http://.../DOF","dimUrl":"http://.../DON/${intensity.byte}","onUrl":"http://.../DON","httpVerb":"GET","deviceState":{"on":false,"bri":0,"hue":0,"sat":0,"effect":"none","ct":0,"alert":"none","reachable":true}}

But the name is still "Floor Lamp".  Am I doint this wrong?

Also, just to make sure, I forced the unicode strings into straight strings, still the same result:
2016-12-21 18:08:24,895:IH:INFO: request:post: http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 18:08:24,896:IH:INFO: request:post: body={'name': 'Family Room Floor Lamp', 'dimUrl': 'http://.../DON/${intensity.byte}', 'mapId': 'isy:2E 59 94 1', 'deviceType': 'custom', 'onUrl': 'http://.../DON', 'offUrl': 'http://.../DOF', 'httpVerb': 'GET'}
2016-12-21 18:08:24,920:IH:INFO: request:connect:success: url=http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 18:08:24,922:IH:DEBUG: request:connect:success: text=[{"success":{"username":"ed6936c22a7b42a5929431c958766197"}}]
2016-12-21 18:08:24,923:IH:INFO: ihab:bridge: st=True
2016-12-21 18:08:24,924:IH:INFO: request:get: http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 18:08:24,943:IH:INFO: request:connect:success: url=http://<IP_ADDRESS>:8090/api/devices/23
2016-12-21 18:08:24,944:IH:DEBUG: request:connect:success: text={"id":"23","uniqueid":"00:17:88:5E:D3:17-17","name":"Floor Lamp","mapId":"isy:2E 59 94 1","deviceType":"custom","offUrl":"http://.../DOF","dimUrl":"http://.../DON/${intensity.byte}","onUrl":"http://.../DON","httpVerb":"GET","deviceState":{"on":false,"bri":0,"hue":0,"sat":0,"effect":"none","ct":0,"alert":"none","reachable":true}}

Sorry, I meant to include the ha-bridge log.  This looks like the section of the log:
12-21-2016 18:29:08.682	DEBUG	httpMethod:post, uri: /api/devices/32	spark.webserver.MatcherFilter
12-21-2016 18:29:08.683	DEBUG	get params	spark.Request
12-21-2016 18:29:08.689	DEBUG	get splat	spark.Request
12-21-2016 18:29:08.693	DEBUG	HH trace: hue api user create requested for device type: <not given> and username: db708b16a528418b966030d9e56203a7	com.bwssystems.HABridge.hue.HueMulator
12-21-2016 18:29:08.728	DEBUG	httpMethod:get, uri: /api/devices/32	spark.webserver.MatcherFilter
12-21-2016 18:29:08.730	DEBUG	get params	spark.Request
12-21-2016 18:29:08.730	DEBUG	matchedPart: :id = 32

and I have tried getting, and then passing the username, but no difference:
12-21-2016 18:41:05.540	DEBUG	Get a device	com.bwssystems.HABridge.devicemanagmeent.DeviceResource
12-21-2016 18:41:05.805	DEBUG	httpMethod:post, uri: /api/9bc4e32d2d3b470a90ed85a43ad15eee/devices/23	spark.webserver.MatcherFilter
12-21-2016 18:41:05.806	DEBUG	get params	spark.Request
12-21-2016 18:41:05.806	DEBUG	get splat	spark.Request
12-21-2016 18:41:05.808	DEBUG	HH trace: hue api user create requested for device type: <not given> and username: b8c31b52eede46d9a4ff60f2b6d81b2c	com.bwssystems.HABridge.hue.HueMulator
12-21-2016 18:41:05.827	DEBUG	httpMethod:get, uri: /api/devices/23	spark.webserver.MatcherFilter
12-21-2016 18:41:05.827	DEBUG	get params	spark.Request
12-21-2016 18:41:05.828	DEBUG	matchedPart: :id = 23

I wasn't passing usernames because it didn't seem to use it anyway?

Looks like we are hitting an issue with the spark rest server url matching algorithm. And I think I know what it is.

sounds great, thanks

Ok, did some testing. It works great! You will need to change your device update to a PUT instead of POST as the documentation is incorrect. Sorry about that. Post is only used for adding an array of new devices.

But ,there is a bug that it creates a new device instead of updating it properly.

Well, scratch that...no bug.... works as designed....
To update a device you will need to send the complete device description back to the ha-bridge including the id field.

awesome, so the id has to be in the URL and the data as well?

That is correct!

Also, the update is a replace of the complete device definition, not a field by field update.

OK, thanks. I will try that tonight. As long as the id stays the same so I can rename without having to reprogram my Harmony Elite buttons I'll be very happy.

That would be correct. Just make sure you get the definition and then change the field and you will be all set.

makes sense, I'll do that

Works perfectly, thank you for debugging!
Probably should leave this open until the documentation is updated?

Updated in 4.0.0


Implement checkpoint command

This enables the checkpoint command. Right now it can be used like this:
  # crictl checkpoint --export=/tmp/cp.tar CTR-ID

See #662

Hi! please submit PRs that update CRI API  under the  main repo

Does anyone have any ideas why critest containerd / main / ubuntu-18.04 / io.containerd.runc.v1 / runc (pull_request) might have failed. Does not look related to this PR:
 Summarizing 2 Failures:
[FAIL][k8s.io] Streaming runtime should support streaming interfaces [It] runtime should support portforward in host network
github.com/kubernetes-sigs/cri-tools/pkg/validate/networking.go:253
[FAIL][k8s.io] Streaming runtime should support streaming interfaces [It] runtime should support portforward [Conformance]
github.com/kubernetes-sigs/cri-tools/pkg/validate/networking.go:253

@adrianreber this seems to be a flake, let me re-kick the CI

@adrianreber this seems to be a flake, let me re-kick the CI

Now it passed. Thanks!

@saschagrunert Changed as suggested. Can you approve the CI run again? Thanks.

Oh, the containerd build seems to be broken we now require golang 1.18 for it.

That seems to be only part of CI which still was using golang 1.17. I updated this 1.18. Let's see if CI likes it better.
@saschagrunert please approve the CI run once more.

Hmm, seems like cri-tools uses a containerd version from 1.5.x branch. I updated the Github Actions yaml files to point to release 1.6.6, but not sure if this breaks more than it fixes. Let's see.

CI is happy now.

This enables the checkpoint command. Right now it can be used like this:
  # crictl checkpoint --export=/tmp/cp.tar CTR-ID

See #662

# crictl restore

When will it be implemented and integrated?

This enables the checkpoint command. Right now it can be used like this:
  # crictl checkpoint --export=/tmp/cp.tar CTR-ID

See #662

# crictl restore

When will it be implemented and integrated?

There is no plan to have a separate restore command. You can use create and start to restore a container. See the test script in CRI-O for an example (https://github.com/cri-o/cri-o/blob/main/test/checkpoint.bats) or https://kubernetes.io/blog/2022/12/05/forensic-container-checkpointing-alpha/#restore-checkpointed-container-standalone

This enables the checkpoint command. Right now it can be used like this:
  # crictl checkpoint --export=/tmp/cp.tar CTR-ID

See #662

# crictl restore

When will it be implemented and integrated?

There is no plan to have a separate restore command. You can use create and start to restore a container. See the test script in CRI-O for an example (https://github.com/cri-o/cri-o/blob/main/test/checkpoint.bats) or https://kubernetes.io/blog/2022/12/05/forensic-container-checkpointing-alpha/#restore-checkpointed-container-standalone

Is the effect of create and start exactly the same as that of restore? Ensure that the task can be restored to the status at the checkpoint

Is the effect of create and start exactly the same as that of restore?

In CRI-O I would say yes. The create code detects if it is a checkpoint image and then tries to prepare everything so that during start the actual restore is done. The restore command I used to have was using exactly the same code as going through create and start.

Ensure that the task can be restored to the status at the checkpoint

I don't understand this part of the question. But if a checkpoint image is detected only the restore code path is being used.

Is the effect of create and start exactly the same as that of restore?

In CRI-O I would say yes. The create code detects if it is a checkpoint image and then tries to prepare everything so that during start the actual restore is done. The restore command I used to have was using exactly the same code as going through create and start.

Ensure that the task can be restored to the status at the checkpoint

I don't understand this part of the question. But if a checkpoint image is detected only the restore code path is being used.

Has it been tested based on containerd? I'm using containerd, not cri-o. I want to perform c/r based on containerd. If I use create and start to perform restore, is it OK?

@Carol-code2222 CRI-O and containerd currently use different interfaces and checkpoint image format. For example, you can create a checkpoint with containerd and restore it as follows:
ctr image pull docker.io/library/redis:alpine
ctr run -d docker.io/library/redis:alpine redis

ctr c checkpoint --rw --task redis checkpoint/redis:1
ctr c restore --rw --live redis-debug checkpoint/redis:1

AFAIK the containerd checkpoint/restore functionality is not currently supported via the Kubernetes API. However, there is an open pull request to enable this functionality: https://github.com/containerd/containerd/pull/6965

What @rst0git said. containerd does not support checkpoint restore via CRI. If you want to use it via CRI (crictl or kubernetes) you can only use CRI-O.

Kubernetes API

The c/r function of containerd cannot be performed through the Kubernetes API, which sounds bad news for me！！！

Kubernetes API

The c/r function of containerd cannot be performed through the Kubernetes API, which sounds bad news for me！！！

The PR exists and someone needs to review and merge it. You are welcome to work on this. It works in CRI-O, so you can easily test it. It is still marked as an alpha feature in Kubernetes, so if not all CRI implementations support it there is still time to work on it.

@Carol-code2222 CRI-O and containerd currently use different interfaces and checkpoint image format. For example, you can create a checkpoint with containerd and restore it as follows:
ctr image pull docker.io/library/redis:alpine
ctr run -d docker.io/library/redis:alpine redis

ctr c checkpoint --rw --task redis checkpoint/redis:1
ctr c restore --rw --live redis-debug checkpoint/redis:1

AFAIK the containerd checkpoint/restore functionality is not currently supported via the Kubernetes API. However, there is an open pull request to enable this functionality: containerd/containerd#6965

I run the following ctr containers command to try to perform the checkout/restore for the K8S container, but no result is generated and no error is reported.
ctr -n k8s.io c checkpoint --rw --task 5e7a6e7bc98a77f87f741a7fa34721ed6887825a9cb70c18e5e5516732a456d7 my-nginx

At the same time, I tried the following ctr tasks command to dump the container process, which was successful, but I don't know how to restore the container process.
ctr -n k8s.io tasks checkpoint --exit --image-path=/root/criu-img  --work-path=/root/criu-work  9b90293d96ae0e6aa7435e2732887b2ea4ec9fe615fc999a89b4696a1e14f63a

You should ask your questions at containerd and not here. Not sure we can help You here. This PR was about crictl.

You should ask your questions at containerd and not here. Not sure we can help You here. This PR was about crictl.

I'm sorry, I didn't notice, I just followed the last @rst0git reply and left a message,


Remove defaultDataProjection as a format option

Formats should have a default data projection, but this does not need to be exposed as an option while reading and writing.  For example, GeoJSON and KML will have a default data projection of Geographic/WGS-84 set.  If a user wants to override this when reading or writing, they use the dataProjection option.  Having defaultDataProjection as an option only adds confusion.

The option can be useful, for example when configuring a vector source.
But the name is confusing and unconsistent with the name used for the projection of the features.
What about simply renaming the defaultDataProjection option passed to formats like GeoJSON to dataProjection? Then it would be consistent with the featureProjection that these formats accept.
Reading the src/ol/format/GeoJSON.js code I see:
  this.defaultDataProjection = getProjection(
    options.defaultDataProjection ?
      options.defaultDataProjection : 'EPSG:4326');

  if (options.featureProjection) {
    this.defaultFeatureProjection = getProjection(options.featureProjection);
  }

Which would become:
  this.defaultDataProjection = getProjection(options.dataProjection ? options.dataProjection : 'EPSG:4326');

  if (options.featureProjection) {
    this.defaultFeatureProjection = getProjection(options.featureProjection);
  }

I agree with @gberaudo here. Renaming the option to dataProjection sounds reasonable.
It's much more convenient API-wise to configure a source with a url and a format than with a custom loader where readFeatures(data, {dataProjection: myProj}) would be called, if someone has to deal e.g. with a GeoJSON data set that has a non-standard projection.


Request::respond returns a IoResult

For the moment the respond function ignored errors.
This PR moves this responsibility to the user.
If the user wants to make sure that the response has been sent, it's now possible.
In any real-life scenario, you will probably just write let _ = request.respond(..);
This is not a breaking change, but it adds an unused result warning to the users' code.

Good idea!


Modifications / Enhancements

If someone wants to modify the cost analysis is there any documentation on how to do it?  Is it a simple fork in Github, or are there embedded links as part of the install process?

HI SCBob,
Currently the repo is not open for external contributions. That is currently under evaluation and will be posted in the repo notifications. What contributions are you considering? Also, I see a couple of other emails from you in the queue. Let me review and respond.
Just wanted to acknowledge your emails and will follow up.
Best,
jpm
From: SCBob @.>
Date: Thursday, September 7, 2023 at 6:01 AM
To: oracle-samples/adbs-tools @.>
Cc: Subscribed @.***>
Subject: [External] : [oracle-samples/adbs-tools] Modifications / Enhancements (Issue #60)
If someone wants to modify the cost analysis is there any documentation on how to do it? Is it a simple fork in Github, or are there embedded links as part of the install process?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/oracle-samples/adbs-tools/issues/60__;!!ACWV5N9M2RV99hQ!MFst5vO30A0LePut1GMPKGwDliK_ju_Wy4U-YYDJb4vBsFe3FUomUXDLSb-y_KqxUAmpeiLYqz1aAIqosmI8uigyBjw$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ACBYKNKZUYB63ZOHXOCES63XZHARVANCNFSM6AAAAAA4O3YO7M__;!!ACWV5N9M2RV99hQ!MFst5vO30A0LePut1GMPKGwDliK_ju_Wy4U-YYDJb4vBsFe3FUomUXDLSb-y_KqxUAmpeiLYqz1aAIqosmI8uiEbU-0$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

@SCBob Closing this issue, but please follow up as necessary. Thx


Solve Candles Counting problem

please add the Hackerrank url of problem

Thanks, as I asked earlier, can you add your name along with country/language in README.md and commit again? It is not compulsory, let me know if you have any problem

Thanks!


Cherry-pick: fix metrics for establish connection

What problem does this PR solve?
Issue Number: close #6656 #6212
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge

/run-all-tests

/run-all-tests

/merge

/run-all-tests

/merge


x86_64 iOS simulators do not work with Xcode 14.3

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Download Xcode 14.3
Pick an iOS simulator with x86_64 architecture (you can do xcrun xcdevice list to find which have the arch)
Open the x86_64 iOS simulator
Do flutter run -d device-id-xxx with any flutter app

Actual results
Results in this error:
Error waiting for a debug connection: The log reader failed unexpectedly
Error launching application on iPhone SE (2nd generation).

Expected: no error
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output
[!] Flutter (Channel master, 3.10.0-15.0.pre.31, on macOS 13.3.1 22E261 darwin-arm64, locale en)
    • Flutter version 3.10.0-15.0.pre.31 on channel master at xxx
    • Framework revision ea179fe033 (61 minutes ago), 2023-04-27 13:32:25 -0400
    • Engine revision 3d6d915cb7
    • Dart version 3.1.0 (build 3.1.0-49.0.dev)
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at xxx
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = xxx
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (5 available)
    xxx

[✓] Network resources
    • All expected network resources are available.

It's erroring here because deviceUri is null.
https://github.com/flutter/flutter/blob/4ff505c86108415da79008241b5125d5aafde4b2/packages/flutter_tools/lib/src/ios/simulators.dart#L493-L499
When it launches here
https://github.com/flutter/flutter/blob/4ff505c86108415da79008241b5125d5aafde4b2/packages/flutter_tools/lib/src/ios/simulators.dart#L477
the onDone gets triggered here
https://github.com/flutter/flutter/blob/4ff505c86108415da79008241b5125d5aafde4b2/packages/flutter_tools/lib/src/protocol_discovery.dart#L29
which causes the stream to close, which leads me to believe there's something wrong happening in the _IOSSimulatorLogReader class.

I was able to get the following error message by adding a breakpoint here and looking at the line value.
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=9):
Process spawn via launchd failed.
Bad file descriptor
Underlying error (domain=NSMachErrorDomain, code=9):
The operation couldn’t be completed. (Mach error 9 - (os/kern) memory failure)

Found this related issue: https://github.com/flutter/flutter/issues/116248
They were able to do a workaround by using flutter attach. I have the suspicion that it's because it's using mDNS with the attach command. Perhaps we need to update the simulator startApp code to look up with mDNS too

Perhaps we need to update the simulator startApp code to look up with mDNS too

It used to do that before https://github.com/flutter/flutter/pull/66399.
Note if you re-implement that you're going to hit https://github.com/flutter/flutter/issues/44717, https://github.com/flutter/flutter/issues/44718, https://github.com/flutter/flutter/issues/54781, https://github.com/flutter/flutter/issues/58078

@vashworth which simulators are still x86_64?  If I recall it was just old devices, one option would be to stop supporting them as run targets on arm machines.

@jmagman Seems to me to be any device with iOS 13.7


Popup not closing when hosted on heroku

The popup window does not close, and the redirect-to page reloads inside the popup window itself. This only happens when the app is deployed on heroku. In localhost the popup window closes as it should. Am testing with Google and Facebook login, and the same issue happens for both.
Tried the fixes suggest in #915 but they dont work.
Any ideas?

I figured out what was wrong.
For some reason my deployed app was loading on a https URL, not just a normal http. When I load it on http the popup closes fine.


Current Day displayed

#Current Day
User Story
AS AN employee with a busy schedule
I WANT to add important events to a daily planner
SO THAT I can manage my time effectively
Acceptance Criteria
GIVEN I am using a daily planner to create a schedule
WHEN I open the planner
THEN the current day is displayed at the top of the calendar

Current date displayed


[Bug] Cannot set persistent volume claim storage size for FE

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
24.1.0
What's Wrong?
Currently cannot set the persistent volume claim storage size for FE as any value configured other than 100Gi get's set to 100Gi.
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.

apiVersion: disaggregated.cluster.doris.com/v1
kind: DorisDisaggregatedCluster
metadata:
  name: test-disaggregated-cluster
spec:
  metaService:
    image: selectdb/doris.ms-ubuntu:3.0.2
    configMaps:
      - name: ms-configmap
    fdb:
      # address: ${fdb_endpoint}
      configMapNamespaceName:
        name: ${fdb-configmap}
        namespace: ${fdb-namespace}
  feSpec:
    replicas: 2
    image: selectdb/doris.fe-ubuntu:3.0.2
    persistentVolume:
      # logNotStore: true
      persistentVolumeClaimSpec:
      # storageClassName: ${storageclass_name}
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 10Gi
  computeGroups:
    - uniqueId: cg1
      replicas: 3
      image: selectdb/doris.be-ubuntu:3.0.2
      persistentVolume:
        # logNotStore: true
        persistentVolumeClaimSpec:
          # storageClassName: ${storageclass_name}
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 100Gi
    - uniqueId: cg2
      replicas: 3
      image: selectdb/doris.be-ubuntu:3.0.2
      persistentVolume:
        # logNotStore: true
        persistentVolumeClaimSpec:
          # storageClassName: ${storageclass_name}
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 100Gi

10Gi gets interpreted as 100Gi.
  feSpec:
    replicas: 2
    image: selectdb/doris.fe-ubuntu:3.0.2
    persistentVolume:
      # logNotStore: true
      persistentVolumeClaimSpec:
      # storageClassName: ${storageclass_name}
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 100Gi

What You Expected?
Expect storage size to match configured value of persistent volume claim template.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

This appears to be due to the following lines that require the PVC to be 100Gi or greater. Suggest allowing smaller volume sizes for smaller/test deployments.
https://github.com/apache/doris-operator/blame/e45a51aad7e9d413a318cfb7b3708537bd62e51b/pkg/controller/sub_controller/disaggregated_cluster/disaggregated_fe/statefulset.go#L182-L184

yes, you are right. thanks for your suggestion. The log pvc will not allowed less than 100Gi. The operator restricts the size and will issue an event on DorisDisaggregatedCluster resource. this is because the log will use the maximum storage space is 100Gi. Less than 100Gi may be not a good choice for use.  test deployments used 100Gi , I think will not cost so much.


FreeBSD tesseract installation - missing configs dir

Hi,
when installing tesseract on FreeBSD, the configs dir, which should be in "/usr/local/share/tessdata/" is not created.
It was necessary for me, to download the complete package from here, extract the configs folder and place it on my server.
After that, tesseract was working fine.
Please fix that!

Which version of Tesseract did you try to install?
How did you build / install Tesseract?
Additional information is needed to understand, reproduce and finally fix the issue.

HI,
i installed the folllowing:
pkg install tesseract-5.0.0 tesseract-data-4.1.0
After that, i ran the following command:
ocrmypdf -v --redo-ocr 2020_11_30_Kellerdecke_neu.pdf Keller_neu.pdf
This told me, that tesseract was not able to open "params_file" txt and pdf. So, ocrmypdf didnt create such a file.
I downloaded the package from here, extracted the configs dir and placed it into the tessdata folder.
After that, it was working.

Did you report the problem to the maintainer of the FreeBSD package?
I am afraid here is the wrong place for your report.

Cc'ing @pkubaj.

Where is that package located?

It looks like FreeBSD uses the cmake build. Debian bases distributions use the autotools build (which I normally use, too).

Where is that package located?

https://www.freebsd.org/cgi/ports.cgi?query=tesseract-5.0.0
https://cgit.freebsd.org/ports/tree/graphics/tesseract

Ok.
And who is maintaining this package? Because i installed it via pkg.

@egorpugin, I just tried make install with a cmake build. It did not install /usr/local/share/tessdata. Is that a regression compared to 4.1.3?

Does it work on 4.1.3?

https://github.com/marketplace/actions/freebsd-vm
Maybe someone here wants to use this and write an action to test Tesseract on FreeBSD.

I did not implement our cmake install.
Probably it was contributed via PRs, so not every expected functionality might present.

Maybe that is also not necessary. @pkubaj, could FreeBSD use autotools like the other distributions?

I switched back to autotools, please test.

You should clearly state that cmake support is incomplete to avoid such issues.

Do you have a suggestion where and how we should state that?

For example, here https://tesseract-ocr.github.io/tessdoc/Compiling.html.

Yes, cmake build was never complete.
I uploaded initial bits long time ago.
There were no install() and some important things. Some of these were contributed in PRs, but people ususally tune cmake build for themselves rather than doing really general support.

After this commit https://github.com/tesseract-ocr/tesseract/issues/2551 there is no need to install configs... ;-) Everything can be replaced by tesseract option -c or with SetVariable.
Installing configs via autotools is IMO relict from tesseract version 3 (autotools installed also langdatas and config files have to be at the same location aslangdatas ). At that time it made sense.
This was changed with tesseract 4: there are 3 sets of language data files and we stop installing langdatas with autotools. At the moment configs are still part of langdatas structure and therefore they should be part of the installation process of langdatas - not the library. Actually, you can run OCR with tesseract without configs, but you can not run it without langdata and nobody complains that make install is broken...
There was some discussion in past/attempt  to improve this situation, but AFAIR no progress was done.
Personally, I like the idea to store my preferred settings in text file, but I think we should get rid of old logic (why configs and tessconfigs subdirectories? Why use the same directory for configs and lang data, when I need 3 or more directories for langdata???)  enhance searching for user location (~/.config/tessdata ?)
And yes - as (nowadays) windows user I am happy user of tesseract cmake installation process already for several years - without any major problem (usually any new feature is implemented in the same time to autotools and cmake), as langdatas I need to install/update by a separate process...


HDDS-2660. Create insight point for datanode container protocol

What changes were proposed in this pull request?
The goal of this task is to create a new insight point for the datanode container protocol (HddsDispatcher) to be able to debug client<->datanode communication.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2660
How was this patch tested?
Manually. See the video:
https://www.youtube.com/watch?v=msQgfF95ivc&list=PLCaV-jpCBO8UK5Ged2A_iv3eHuozzMsYv&index=7&t=0s
;-)

Closing this pr temporary. This is on my list but today, it's pending.
I will improve the insight first to support multiple nodes, or making the datanode insight is to be a one-node insight point...

Both of the open questions are answered with an improvement: instead of using pipeline as a filter I started to use datanode (host or ip) as a filter. With this approach we can check the metrics and it's more obvious what is printed out.

@adoroszlai
I think the new approach addressed all the earlier problems. Can we merge it now?

Thanks @elek for updating the patch.  Interestingly log -v stopped working, even if I execute log first (as mentioned previously).

Thanks @elek for updating the patch. Interestingly log -v stopped working, even if I execute log first (as mentioned previously).

I double-checked and it worked for me. When you use leader, the messages are displayed immediately, when you use follower, the messages will be appeared only after the commit...

Thanks @elek for updating the patch. Interestingly log -v stopped working, even if I execute log first (as mentioned previously).

I double-checked and it worked for me. When you use leader, the messages are displayed immediately, when you use follower, the messages will be appeared only after the commit...

It seems to depend on the content.  Plain text files work fine, but it stops working on the first binary, eg. ozone freon ockg -n1 -t1.  I guess it's caused by control chars in the random data.
I think we should avoid logging chunk content.  ContainerCommandRequestMessage implements related logic to clear data.

I think we should avoid logging chunk content. ContainerCommandRequestMessage implements related logic to clear data.

I checked but it's not something which can be added easily. The OzoneProtocolMessageDispatcher is very generic. To support this one, it should be modified to accept a very specific function as an argument which transforms the original message just for the tracing.
And would also introduce significant overhead in case of tracing is turned on.
I am not sure if it's worth it, but I can add it if you think so.

I think we should avoid logging chunk content. ContainerCommandRequestMessage implements related logic to clear data.

I checked but it's not something which can be added easily.

Thanks for checking.  I'm fine with doing it as a follow-up.

I checked but it's not something which can be added easily.

Thanks for checking. I'm fine with doing it as a follow-up (created HDDS-4271).

You were right, you did it easily ;-)


java.sql.BatchUpdateException: Error writing request body to server

Describe the bug
We're using the com.clickhouse.jdbc.ClickHouseDriver with Spark Structured Streaming to write micro-batches to Clickhouse and it works really well. However, intermittently, we get this error. It eventually gets retried by Spark and the batch goes through. I'm just trying to understand what is the underlying cause of this error. More specifically, whether it's a network issue or not.
We run Spark on AWS EMR and Clickhouse on a fleet of EC2 instances. We have a Load Balancer sitting between Spark (the Clickhouse-driver) and Clickhouse nodes. I have tried increasing the timeout but to no avail.
Code example
     df.coalesce(numCoalescePartitions)
              .write
              .mode(SaveMode.Append)
              .option("driver", "com.clickhouse.jdbc.ClickHouseDriver")
              .option("batchsize", batchSize)
              .jdbc(jdbcProps.uri, table = tableName, jdbcProps.properties)

Error log
java.sql.BatchUpdateException: Error writing request body to server, server ClickHouseNode [uri=http://master-clickhouse-lb.internal:8123/events, options={connect_timeout=15000,send_timeout=1500000,receive_timeout=1500000,socket_timeout=1500000,sslmode=NONE,jdbcCompliance=false,nullAsDefault=1}]@74960053
	at com.clickhouse.jdbc.SqlExceptionUtils.batchUpdateError(SqlExceptionUtils.java:107)
	at com.clickhouse.jdbc.internal.InputBasedPreparedStatement.executeAny(InputBasedPreparedStatement.java:154)
	at com.clickhouse.jdbc.internal.AbstractPreparedStatement.executeLargeBatch(AbstractPreparedStatement.java:85)
	at com.clickhouse.jdbc.internal.ClickHouseStatementImpl.executeBatch(ClickHouseStatementImpl.java:754)
	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.savePartition(JdbcUtils.scala:713)
	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.$anonfun$saveTable$1(JdbcUtils.scala:868)
	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.$anonfun$saveTable$1$adapted(JdbcUtils.scala:867)
	at org.apache.spark.rdd.RDD.$anonfun$foreachPartition$2(RDD.scala:1011)
	at org.apache.spark.rdd.RDD.$anonfun$foreachPartition$2$adapted(RDD.scala:1011)
	at org.apache.spark.SparkContext.$anonfun$runJob$5(SparkContext.scala:2269)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
	at org.apache.spark.scheduler.Task.run(Task.scala:138)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:548)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1516)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:551)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)

Configuration
Driver config:

connect_timeout=15000
send_timeout=1500000
receive_timeout=1500000
socket_timeout=1500000 (not sure whether this is used or send/received timeout or both)
sslmode=NONE
jdbcCompliance=false
nullAsDefault=1

Environment

Client version: 0.4.6
OS: Amazon Linux 2

ClickHouse server

ClickHouse Server version: <IP_ADDRESS>

Hi @jalili, it seems like there is an exception originating from HttpURLConnection, which is utilized for posting queries to ClickHouse.
Since we have limited information on the client side, could you please check the system.query_log table or the error log in ClickHouse? Additionally, if there is a high volume of requests being sent to the load balancer for insertion, you may consider increasing the request_chunk_size option (which defaults to 4096) to minimize network calls.

Since we have limited information on the client side, could you please check the system.query_log table or the error log in ClickHouse? Additionally, if there is a high volume of requests being sent to the load balancer for insertion, you may consider increasing the request_chunk_size option (which defaults to 4096) to minimize network calls.

Thank you for getting back to me. I have scoured Clickhouse server logs but couldn't find anything. I've also looked into the query log. I see the successful INSERTs but nothing with exceptions. Since we go through the load balancer, it's hard to narrow the exception down to a specific node so I checked them all. That's what initially lead me to think it may be a network issue between EMR/LB.
Your suggestion about request_chunk_size makes a lot of sense. I'll start digging to load balancer logs/metrics to get a better understanding of the frequency of requests. I'll update the ticket with my findings.

It might be worth considering checking the keep_alive_timeout setting in the server configuration as well, although I cannot guarantee that it will directly resolve the issue.

We switched from using the network load balancer to using Clickhouse nodes directly and the issue has disappeared. I will update the ticket when I figure out what the root-cause was. Closed the ticket.

I have the same problem as you. Have you found the answer? thanks


Override fts5?

When I was loading this extension, the fts5 function was missing.
Used sqlite3_auto_extension in rusqlite
Dependencies
anyhow = "^1.0"
rusqlite = { version = "~0.31", features = ["bundled"] }
sqlite-regex = "0.2.4-alpha.1"

Code
use std::ffi::{c_char, c_int};

use anyhow::Result;
use rusqlite::Connection;
use rusqlite::ffi::{sqlite3, sqlite3_api_routines, sqlite3_auto_extension, SQLITE_OK};

fn main() -> Result<()> {
    unsafe extern "C" fn regex(db: *mut sqlite3, pz_err_msg: *mut *const c_char, p_api: *const sqlite3_api_routines) -> c_int {
        sqlite_regex::sqlite3_regex_init(db as _, pz_err_msg as _, p_api as _) as _
    }
    unsafe {
        assert_eq!(sqlite3_auto_extension(Some(regex)), SQLITE_OK);
    };
    let connection = Connection::open_in_memory()?;
    connection.prepare("SELECT fts5(?1)")?;
    Ok(())
}

But when I comment out these lines:
    unsafe {
        assert_eq!(sqlite3_auto_extension(Some(regex)), SQLITE_OK);
    };

it works.
Is there any error in my code? I'm curious why, these should be two unrelated extensions.

Output
Error: no such function: fts5 in SELECT fts5(?1) at offset 7

Caused by:
    Error code 1: SQL error or missing database

I also tested sqlite-regex = "0.2.3", but the same error.

Oooh that's not good. I think this has to do with a bug from a previous version of sqlite-regex, where it would accidentally link it's own version of sqlite3 instead of what rusqlite created. I thought it was fixed in 0.2.4-alpha.1.
I'm having trouble reproducing - I ran what you have but it seemed to work fine. A few questions:

Did you cargo clean before running that code-snippet? Hoping it's not some lingering build artifacts in target/ that's causing the issue
Can you print out the result of sqlite_version() In your code-snippet, before calling fts5()? The latest published version that rusqlite has should be 3.45.1, but for some reason locally I'm getting 3.45.0

Thanks for reporting!

I just run cargo clean, but unfortunately it output the same error.
The sqlite_version() is 3.39.4. I searched the source codes, it's in sqlite3ext-sys.
I cloned your two repositories, it works. and the sqlite_version() is 3.45.0

Ok cool, thanks for the info! So it does appear to be the issue I alluded to earlier - the 3.39.4 version definitely comes from sqlite3ext-sys, which should not be linked to in this case. That linked sqlite3 version also probably doesn't compile in the fts5 extension, which is causing the original error you reported here.
The sqlite-loadable crate is what depends on sqlite3ext-sys. However, when the static feature is enabled, it instead links to libsqlite3-sys. So the goal should be to enable the static feature on sqlite-loadable, which avoids sqlite3ext-sys and won't overwrite the sqlite3 linking.
Could you try something like this in your Cargo.toml?
sqlite-loadable = { version = "0.0.6-alpha.6", features=["static"]}

I tried this locally but ran into some version conflicts. Might need to push a new update to sqlite-regex for a proper fix

I encountered the same version conflicts.
error: failed to select a version for `libsqlite3-sys`.
    ... required by package `sqlite-loadable v0.0.6-alpha.6`
    ... which satisfies dependency `sqlite-loadable = "^0.0.6-alpha.6"` (locked to 0.0.6-alpha.6) of package `tester v0.1.0 (D:\Projects\tester)`
versions that meet the requirements `^0.26.0` are: 0.26.0

the package `libsqlite3-sys` links to the native library `sqlite3`, but it conflicts with a previous package which links to `sqlite3` as well:
package `libsqlite3-sys v0.28.0`
    ... which satisfies dependency `libsqlite3-sys = "^0.28.0"` (locked to 0.28.0) of package `rusqlite v0.31.0`
    ... which satisfies dependency `rusqlite = "~0.31"` (locked to 0.31.0) of package `tester v0.1.0 (D:\Projects\tester)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "sqlite3"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `libsqlite3-sys` which could resolve this conflict

Downgrade rusqlite to ~0.29 and it works

Hi, I created a PR that may fix the conflicts. I hope you can merge it.


webkitgtk: 2.40.2 → 2.40.3

https://webkitgtk.org/2023/06/28/webkitgtk2.40.3-released.html
https://webkitgtk.org/security/WSA-2023-0005.html
https://github.com/WebKit/WebKit/compare/webkitgtk-2.40.2...webkitgtk-2.40.3
CVE-2023-32439
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build gnome.epiphany

@bobby285271 @jtojnar Just letting you know since I'm not sure if there are any implications on the broader user base. Feel free to ignore this if I'm too dramatic.
I'm currently trying to update my system and this new version of webkitgtk is eating up all of my 16 gigs of RAM and then floods my swap completely which effectively crashes my pc.
It's probably an upstream issue with the new version of the package since a few days ago everything built fine.
To be more precise it begins to fill the RAM in the cmake build step [2016/6819] when it starts to build JavaScriptCore related things.

I have the impression that building this always uses lots of RAM :joy: I personally suggest following a proper channel like nixos-unstable so the cache is guaranteed to be available on cache.nixos.org, or try limiting --cores if you have to build yourself.