[Bug]: Update depedencies for llama-index-embeddings-azure-openai

Bug Description
llama-index-embeddings-azure-openai is not compatible with the latest llama-index release.
Version
0.11
Steps to Reproduce
pip install -U llama-index-embeddings-azure-openai
Relevant Logs/Tracbacks
Using cached llama_index_core-0.10.68.post1-py3-none-any.whl (1.6 MB)
Using cached llama_index_embeddings_openai-0.1.11-py3-none-any.whl (6.3 kB)
Using cached llama_index_llms_azure_openai-0.1.10-py3-none-any.whl (5.1 kB)
Using cached llama_index_llms_openai-0.1.31-py3-none-any.whl (12 kB)
Installing collected packages: llama-index-core, llama-index-llms-openai, llama-index-embeddings-openai, llama-index-llms-azure-openai
  Attempting uninstall: llama-index-core
    Found existing installation: llama-index-core 0.11.0.post1
    Uninstalling llama-index-core-0.11.0.post1:
      Successfully uninstalled llama-index-core-0.11.0.post1
  Attempting uninstall: llama-index-llms-openai
    Found existing installation: llama-index-llms-openai 0.2.0
    Uninstalling llama-index-llms-openai-0.2.0:
      Successfully uninstalled llama-index-llms-openai-0.2.0
  Attempting uninstall: llama-index-embeddings-openai
    Found existing installation: llama-index-embeddings-openai 0.2.1
    Uninstalling llama-index-embeddings-openai-0.2.1:
      Successfully uninstalled llama-index-embeddings-openai-0.2.1
  Attempting uninstall: llama-index-llms-azure-openai
    Found existing installation: llama-index-llms-azure-openai 0.2.0
    Uninstalling llama-index-llms-azure-openai-0.2.0:
      Successfully uninstalled llama-index-llms-azure-openai-0.2.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
llama-index 0.11.0 requires llama-index-core==0.11.0.post1, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index 0.11.0 requires llama-index-embeddings-openai<0.3.0,>=0.2.0, but you have llama-index-embeddings-openai 0.1.11 which is incompatible.
llama-index 0.11.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-agent-openai 0.3.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-agent-openai 0.3.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-cli 0.3.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-cli 0.3.0 requires llama-index-embeddings-openai<0.3.0,>=0.2.0, but you have llama-index-embeddings-openai 0.1.11 which is incompatible.
llama-index-cli 0.3.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-embeddings-bedrock 0.3.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-embeddings-huggingface 0.3.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-indices-managed-llama-cloud 0.3.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-llms-anthropic 0.2.1 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-llms-bedrock 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-llms-bedrock-converse 0.2.1 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-multi-modal-llms-openai 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-multi-modal-llms-openai 0.2.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-program-openai 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-program-openai 0.2.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-question-gen-openai 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-question-gen-openai 0.2.0 requires llama-index-llms-openai<0.3.0,>=0.2.0, but you have llama-index-llms-openai 0.1.31 which is incompatible.
llama-index-readers-file 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-readers-llama-parse 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.
llama-index-utils-workflow 0.2.0 requires llama-index-core<0.12.0,>=0.11.0, but you have llama-index-core 0.10.68.post1 which is incompatible.

Works fine here
https://colab.research.google.com/drive/1hjTTewxyleTzO96_CGllux3hahci6Qyt?usp=sharing

Hmm but if you read my tracebacks - upgrading this package downgraded all my previous package upgrades including the core which caused an error.

Super sus, because the deps here make sense?
https://github.com/run-llama/llama_index/blob/78f9a1130d58ced123e267891fc8c6590fb088b4/llama-index-integrations/embeddings/llama-index-embeddings-azure-openai/pyproject.toml#L32
A handy command here is maybe
pip list --outdated | grep llama-index | cut -f 1 -d " " | xargs pip install -U

It also installed the proper versions im colab 🤔

And it's only for this library. All the other libraries upgraded fine. really strange.

@tituslhy maybe try a fresh venv? I can't seem to replicate this behaviour
pipdeptree also outputs the correct version info
(venv) (base) loganmarkewich@Logans-MBP test_install % pipdeptree -p llama-index-embeddings-azure-openai | grep llama-index
llama-index-embeddings-azure-openai==0.2.0
├── llama-index-core [required: >=0.11.0,<0.12.0, installed: 0.11.0.post1]
├── llama-index-embeddings-openai [required: >=0.2.0,<0.3.0, installed: 0.2.1]
│   ├── llama-index-core [required: >=0.11.0,<0.12.0, installed: 0.11.0.post1]
└── llama-index-llms-azure-openai [required: >=0.2.0,<0.3.0, installed: 0.2.0]
    ├── llama-index-core [required: >=0.11.0,<0.12.0, installed: 0.11.0.post1]
    └── llama-index-llms-openai [required: >=0.2.0,<0.3.0, installed: 0.2.0]
        ├── llama-index-core [required: >=0.11.0,<0.12.0, installed: 0.11.0.post1]

Just for sanity sake, going to republish azure embeddings (and fixing a small bug in openai embeddings) here:
https://github.com/run-llama/llama_index/pull/15576

Sorry I'm still having the same issue with a fresh conda environment and I think I know why. llama-index-embeddings-azure-openai only supports up to python 3.11. I'm using python 3.12 so it always downgrades to the most compatible version with python 3.12 and that's llama-index-embeddings-azure-openai v0.1.11 which uses llama-index-core 0.10 versions.
Is it possible for llama-index-embeddings-azure-openai to support up to python 3.12?

@tituslhy just did that today actually


my1266897@

[Enter feedback here]

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

ID: 47010f4d-7d5e-c26d-4b9f-066d510c5f35
Version Independent ID: 4a50a101-0899-69f9-0177-6bbeeed27948
Content: Manage Azure portal settings and preferences - Azure portal
Content Source: articles/azure-portal/set-preferences.md
Service: azure-portal
GitHub Login: @JnHs
Microsoft Alias: jenhayes

@Masonta1976
Thanks for your feedback! We will investigate and update as appropriate.
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

@Masonta1976
We are going to close this thread   but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Requesting a copy button on codeblocks

Thanks for a nice theme!

@mitanshu7 You can and should give it a try. It should be rather straightforward. Feel free to ask for help ;)


Rendering objects as semi-transparent.

It is possible to render objects as semi-transparent so that the interior remains visible? Or another alternative could be wireframing objects. I can see the different material classes in geometry.py such as MeshPhongMaterial and MeshToonMaterial but these shaders make the surface opaque. Maybe a surface texture is the way to do this? But I'm unsure how to proceed.

Hi @danieljfarrell,
I'm also interested in such a feature. As far as I can see, meshcat-python doesn't provide such an API. However, Three.js supports transparent objects, so it can be added quite easily. This
patch adds a transparency and opacity field to the MeshMaterial object for configuring these properties.
So the following code
import meshcat

visualizer = meshcat.visualizer.Visualizer()
sphere = meshcat.geometry.Sphere(1.0)
material = meshcat.geometry.MeshLambertMaterial()
material.transparency = True
material.opacity = 0.5
visualizer["sphere"].set_object(sphere, material)

renders a transparent sphere:

@rdeits Do you confirm this isn't currently possible with meshcat? If so, I can make a PR with this patch.

Would be really interested in knowing how you solved this problem. Would you upload your fork to GitHub?

@danieljfarrell Sure! There isn't anything more than what was in the patch, it's just a few lines of code to have meshcat communicate an extra attribute to Three.js
FYI, I found the information about transparency in Three.js in the doc: https://threejs.org/docs/#api/en/materials/Material.opacity
I just created a PR for this issue.

Oh sorry! Missed the link to the patch in the original comment.

Ok, this should now be available in meshcat v0.0.15. You should be able to pip install --upgrade meshcat to get the newest version. Thank you @matthieuvigne for the PR!


Fixed issue preventing submission when environments is empty

Currently when configuring the Advanced tab, if environments is left empty, the form submission is broken. This fixes the issue by checking for null values

Currently when configuring the Advanced tab, if environments is left empty, the form submission is broken. This fixes the issue by checking for null values

Hi,
Currently when configuring the properties tab we have a similar error when submitting any value, the form breaks.
Will it have the same origin or is it another problem?


Add icon when file has not been saved

This displays a circle icon when the file is not saved, making it easier to know what needs to be saved and what doesn't that you have open.

Similar to vscode, if you hover over the tab the dot-icon is replaced with the close-icon.
Note that this does not add any alert when closing a file that has not been saved, which is a feature that should also be added.

Thank you so much for your PR. Looks good to me.


Wrong error message when device is offline

Before creating a new issue, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.

Which UI component?
Authenticator
Gradle script dependencies
// Put output below this line
authenticatorVersion = "1.1.0"

Environment information
# Put output below this line
Gradle 8.6

Please include any relevant guides or documentation you're referencing
No response
Describe the bug
The Authenticator is showing wrong error message's when e.g. device is offline and user tries to Sign-in. In can see that there is a valid text ("Please check your connectivity") defined for these cases but it just isn't used. It seems that AuthenticatorViewModel is mapping UnknownHostException -cause to the this error message but for some reason the mapping code doesn't work and ambigious "Sorry, something went wrong" -message is shown to the user. With AndroidLoggingPlugin enabled I can see the following lines in Logcat:
Auth State Change: Configured(authNState=SigningIn(signInState=SigningInWithSRP(srpSignInState=Error(exception=aws.smithy.kotlin.runtime.http.HttpException: java.net.UnknownHostException: Unable to resolve host "cognito-idp.eu-central-1.amazonaws.com": No address associated with hostname))), authZState=SigningIn(id=)) Auth State Change: Configured(authNState=SignedOut(signedOutData=SignedOutData(lastKnownUsername=null, hostedUIErrorData=null, globalSignOutErrorData=null, revokeTokenErrorData=null)), authZState=Configured(id=))
Reproduction steps (if applicable)
No response
Code Snippet
// Put your code below this line.

Log output
// Put your logs below this line
Auth State Change: Configured(authNState=SigningIn(signInState=SigningInWithSRP(srpSignInState=Error(exception=aws.smithy.kotlin.runtime.http.HttpException: java.net.UnknownHostException: Unable to resolve host "cognito-idp.eu-central-1.amazonaws.com": No address associated with hostname))), authZState=SigningIn(id=))
Auth State Change: Configured(authNState=SignedOut(signedOutData=SignedOutData(lastKnownUsername=null, hostedUIErrorData=null, globalSignOutErrorData=null, revokeTokenErrorData=null)), authZState=Configured(id=))

amplifyconfiguration.json
No response
Additional information and screenshots
No response

Looks like Authenticator is looking for a direct cause of UnknownHostException, but there's an extra layer of HttpException wrapping the UnknownHostException. Authenticator should search through the causes instead of only looking one level deep.

This has been resolved in Authenticator 1.2.1


Support for omitting prefix in @Flatten

Sometimes it could be necessary to flatten a structure without prefixing the field names.

Do not merge this yet, we miss some tests!

Do not spend a lot of time reviewing this, I think we'll re-open it on top of #39 once.

Closing in favor of #40.


Deploy on Heroku

Hi,
I'm trying to deploy pymushra on Heroku but no web process running.
I using Python App and "-e git+https://github.com/nils-werner/pymushra.git#egg=pymushra" in requirements file.
Webmushra was cloned in heroku github but i cant run web with command pymushra server.
Can you help me fixing my problem ?
Many thanks!

I have no experience with Heroku, and without an error message or anything I am not sure I can be of much help.


fix comment, and fix a few bugs which allow us to run loadTransientDB…

…Views script as standalone operation

rebased and merged


Created a pre-commit hook to avoid duplicate links

Fixes Issue
Closes #408
Changes proposed
A pre-commit hook is created using husky
Screenshots

Note to reviewers

@Isha988 your vercel deployment is getting failed bcz of the following issues

@Isha988 your vercel deployment is getting failed bcz of the following issues

@rupali-codes resolved👍

Looks pretty good to me ! 👍 (just asking how the error will be shown to the user who is trying to add duplicate link directly via github)

@ujjawaltyagii Please look at the screenshot in PR description .

Hey, @rupali-codes  and @ujjawaltyagii  any updates on this?

@rupali-codes could you have a look at this PR 👀

@ujjawaltyagii

This script is only looking for those staged files which are having JSON extension, and are present in a subfolder inside the database folder.

Yes, the script treats url as case-sensitive.

It is not checking for duplicates across all files. What exactly it does is,  extract the URLs from a selected staged file and check for duplicates within those URLs if any duplicates are present it prints them, and then moves to another file and so on


awesome font pdf icon does not work in markdown

Hello,
Firstly I wanted to say this is an awesome template for creating academic websites.
I am unable to make the awesome font pdf icon to render in markdown files. More specifically, I am trying to add awesome font icons to cv.md however either the icon does not properly or at all. I have to say that some icons are rendering but not the awesome font pdf icon which I wanted. Is it an issue specific to markdown files ? Should I try using .html files instead ?
I have tried using both <i class="fa fa-file-pdf-o" aria-hidden="true"> and <i class="fal fa-file-pdf"></i> but neither worked. I tried the markdown awesome font icon and it worked. I checked in the codebase that the source code base already contains the fa-solid files (pdf icons are part of the solid class).
Can someone help or have any suggestions ?

Might be related to #413


feat(pkg): Install / Template Charts without downloading to filesystem

fixes https://github.com/helm/helm/issues/7545

This will allow users to use the charts without them being downloaded to the HELM_REPOSITORY_CACHE by setting ChartPathOptions.UseInMemoryCache to true.

https://github.com/helm/helm/pull/7758 provides --use-inmemory-cache which can be used like helm install chart stable/schart --use-inmemory-cache

cc @sbose78 @mattfarina

Thank you!
Could you add a test for a helm install or a helm template flow?

Thanks @waveywaves for taking a stab at this.  I'm having trouble understanding what the PR does however.
From what I understood of #7545, the ask is that when helm install (called by API) downloads a chart, it not write it to disk.  The modifications of this PR are within the main package which I don't believe gets called when a program uses the helm API.
Similarly, since the changes are under cmd/helm, I believe they get triggered when helm is run from the command-line.  In that case however, each command is independent, so running a helm repo add is a different call than helm install, so anything stored in memory will not be persisted between calls.
Finally, the new InMemoryCache has repos added to it and removed from it, but the cache is never read.  Is there something missing?
This is not my area of expertise, so forgive me if I completely missed something.

@marckhouzam Thank you for reviewing this. And as you said, I have only taken an initial "stab" at this hahaha. I was having trouble understanding where exactly the cache would lie. In this case considering that we are dealing with "helm repository cache" the first thing that came to my mind was to enable caching mechanism there. Based on your comment

Similarly, since the changes are under cmd/helm, I believe they get triggered when helm is run from the command-line. In that case however, each command is independent, so running a helm repo add is a different call than helm install, so anything stored in memory will not be persisted between calls.

I was confused about this as well. It makes more sense now. I will update the PR based on this and the comment below, just need to evaluate some bits.

Finally, the new InMemoryCache has repos added to it and removed from it, but the cache is never read. Is there something missing?

@marckhouzam I have updated the PR. Now we are able to install charts without saving them to cache. Can you PTAL
cc @sbose78

@waveywaves can you take a look at the CI failure? seems related to your change:
Downloading testdata/testcharts/empty to InMemoryCache--- FAIL: TestInstall (0.04s)
    --- FAIL: TestInstall/install_with_--use-inmemory-cache (0.00s)
        helm_test.go:86: expected error, got 'repo testdata not found'
        helm_test.go:89: does not match golden file testdata/output/cached-chart.txt

            WANT:
            'NAME: cached
            LAST DEPLOYED: Fri Sep  2 22:04:05 1977
            NAMESPACE: default
            STATUS: deployed
            REVISION: 1
            TEST SUITE: None
            '

            GOT:
            'Error: repo testdata not found
            '

@akashshinde  could you please review this?

@jdolitsky I have added the required output needed in repo testdata, can you help me out in figuring what I might be doing wrong here ?

@jdolitsky Can you PTAL ?

Thanks for the rework @waveywaves!
Based on the recommendation at https://github.com/helm/helm/issues/7545#issuecomment-589706721 could you limit this PR to the necessary changes to the API (pkg/) and avoid changes to the command-line (cmd/)?
This will help ensure the original request is fulfilled and avoids adding new flags until we get a little more experience with this feature.

To simplify testing, how about separating the changes of pkg/ into one PR (this one) and have a second PR using the first one, where you'd include the cmd/ changes?  That way we could easily see how the pkg/ changes are meant to be used, but we wouldn't have to include the cli changes right away.

Thanks @waveywaves for splitting the PR, it makes the review easier.  The code looks quite good!
I've finished the review but before I post comments, let's discuss two points:

the true request from  #7545 is not necessarily for an in-memory cache (although that is what the title says) but, based on https://github.com/helm/helm/issues/7545#issuecomment-587270220, to not leave modifications to the file system after installing the chart.  Therefore, a possible solution is to still create the necessary files, but to cleanup after ourselves; this is not as elegant as the memory cache, but may allow you to implement the provenance check more easily.  I actually like the in-memory cache better, but I feel the provenance check must be implemented and may be causing too much code duplication.  I'll let you think about it and make a recommendation.

In this comment https://github.com/helm/helm/issues/7545#issuecomment-589706721 @mattfarina  suggested making the cache 'pluggable', which means it could be an in-memory cache, or some other caching technique (he mentions object-storage) that could be selected by the user (assuming we implement it eventually).  I don't think you need to implement the whole pluggable solution, but we do need to keep the API generic so that the full pluggable solution could still be possible.  So, at a minimum, we should avoid any new API that specifically refers to 'in-memory', but use more generic terms.

@marckhouzam I have updated the PR with Provenance Verification done without having to download the chart.
Regarding the naming convention for this solution, considering that "in-memory" can cause some issues, can you suggest some other names ?

Thanks for the update! The provenance was important.
As for the naming convention, I'm having trouble coming up with something future proof.  We are introducing a new API but I'm not clear enough on what this cache could evolve into to define the API well.
Maybe @mattfarina can explain a little more what he has imagine as a "pluggable cache"?

@waveywaves Please check the breaking change here - https://github.com/helm/helm/pull/7601/files#diff-4140e2fe89434d8f5a9133898128bcefR233 for the Verify method name change. It's an exported method. We can't have breaking changes in the API, also mentioned here. I get it that a new method has been added - I would recommend giving a good name to that (if you think the existing name is good, cool 👍 ) but we can't change the name for the existing method till we go to v4

@karuppiah7890 I am slowly getting the hand of what is backward compatibility in help. Thanks for checking it out. I will update the PR with the exiting name. That seems alright.
Thanks for checking this out :D

Thanks for the update @waveywaves.  We're getting closer 😄
I've put new comments after reviewing the latest version.

Also, the proposed datastructure grows indefinitely over time - not important for CLI invocations, but very important for someone implementing long-lived service on top of Helm.

Good point!  We should probably use a  Least Recently Used (LRU) cache.

@marckhouzam @pedjak Do check it out. setting HELM_REPOSITORY_CACHE to "off" yeilds the desired result. And the cache has been updated to a LRU Cache.


add attribute time to DTO

verified on android
(cherry-picked at https://github.com/Stimim/background_locator/commit/b1e83ac78c3a1ffb68a54f1e79ca7546e4edda99 )


[feature] Error message for non-wasm32-unknown-unknown compatible crates

Currently if a crate is not wasm32-unknown-unknown compatible, strange errors can be seen (See this issue on Tauri).
Would it be possible to check if a crate or any of its dependencies are not compatible with the wasm32-unknown-unknown target and return an error message indicating as such?

Hm, I am wondering how we could actually detect this. You can just compile any crate to any target, unless it then fails due to some build errors.


fix: KeyError if _granian logger is missing in user logging configuration

Minimal example:
from granian import Granian

Granian(target="", log_dictconfig={"loggers": {}}).serve()

@monosans thank you for your contribution! ❤


[BUG] eth_getBalance(["0x","latest"]): -32602: Invalid length.

Sample code:
import {bonds, formatBlockNumber, formatBalance} from 'oo7-parity';

import React from 'react';

import {Rspan} from 'oo7-react';

export class Screenshot05 extends BaseScene {
	render() {
		return (
			<div>
				Current block author's balance is:
				<Rspan style={{
					fontWeight: 'bold'
				}}>
					{bonds
						.balance(bonds.head.author)
						.map(formatBalance)}
				</Rspan>
			</div>
		);
	}
}

Screenshot:

I also have the same problem.

@gavofyork
After your last update in package.json, it works well.

Confirm fixed


[WIP] Release notes v1.2 alpha.20171211

For https://github.com/cockroachdb/cockroach/issues/20457.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/52bcc5d08578f38dcb4a11d55e968ab1bcd734c0/

Need some help from the following devs. I assume most of these don't require a note, but please check your name off after either adding a comment with release notes or confirming that none are needed:

[ ] @benesch
[ ] @tschottdorf
[ ] @nvanbenschoten
[ ] @knz
[ ] @justinj
[ ] @m-schneider
[ ] @mberhault
[ ] @a-robinson
[ ] @lego
[ ] @spencerkimball
[ ] @RaduBerinde
[ ] @jordanlewis

* | |   commit ff49a9d83d20e201f3546bef70ced64a74b2a714
|\ \ \  Merge: d0472f0d2 749885cc7
| | | | Author: Nikhil Benesch<EMAIL_ADDRESS>| | | | Date:   Wed Dec 6 11:18:51 2017 -0500
| | | |
| | | |     Merge pull request #20429 from benesch/ui-cache
| | | |
| | | |     ui: allow browsers to cache assets
| | | |
| * | | commit 749885cc76435b6de737909515bfdb67876ed8a8
| | | | Author: Nikhil Benesch<EMAIL_ADDRESS>| | | | Date:   Sun Dec 3 12:40:01 2017 -0500
| | | |
| | | |     ui: allow browsers to cache assets
| | | |
| | | |     Include the the UI asset files' mtimes in bindata.go so that Go's HTTP
| | | |     server can properly compute a Last-Modified header.  Is is merged in `draft` status.
| | | |
| | | |       This RFC proposes a mechanism for subscribing to changes to a set of key ranges
| | | |       starting at an initial timestamp.
| | | |
| | | |       It is for use by Cockroach-internal higher-level systems such as distributed
| | | |       SQL, change data capture, or a Kafka producer endpoint. A "sister RFC" detailing
| | | |       these higher-level systems is in #17535.  The actual lease request previously inherited the
| | | | | | | |     context of the originating request.  Each goroutine then takes out a
| | | | | | | |     handle on the lease request which allows it to unregister from the
| | | | | | | |     request on its own context cancellations.       We would ignore all but the first
| | | | | | |     intent for a transaction being pushed.    We do this by removing the associated methods and type and instead
| | | | | | |     exporting the `Add` method to be used directly.    This makes the structure slightly less efficient
| | | | | | |     because it will result in locking at a finer-granularity.         In the latter,
| | |       everything is allowed -- the server is fully functional. In the former, the
| | |       server is either waiting for an Init command or busy bringing its moving parts
| | |       into motion: only a select subset of "safe" grpc endpoints are available
| | |       (gossip, init, ping) and connections opened against the Postgres listener are
| | |       eagerly closed (a TODO in the code hints at a straightforward UX improvement
| | |       here).
| | |
| | |       Fortified the init server to prevent overlapping init requests, and made its
| | |       resilient to double-initialization (which in turn simplified the listener
| | |       handling).  Also the
| | | |     file/lineno location as prefix of the message is desired in this case.
| | | |
| | | |     To respond to this common case, this patch introduces the variant
| | | |     `SHOW COMPACT [KV] TRACE` which only renders the age, message, tag and
| | | |     operation columns.  Also, the extraction was performed using the SQL
| | |       function `regexp_replace`, causing some RE lookup overhead.
| | |
| | |       This patch fixes the issues by extracing the filename/lineno in a
| | |       separate column.  This adds new columns `tag` and `loc` in
| | |       `crdb_internal.session_trace`.  The extraction is done in Go, with a
| | |       well-identified, pre-compiled RE.
| | |
| | |       It also exposes the `loc` column in the output of SHOW TRACE.  The
| | |       `context` column is renamed to `tag`, since this name more closely
| | |       mirrors the terminology used in the source code, and users looking at
| | |       the output of SHOW TRACE will usually also look at the source code
| | |       too.
| | |
* |   commit 4ebabadc7db413cc3164cc878f8efc0414b0e3ff
|\ \  Merge: 4c0c5997e 60fe5ad05
| | | Author: marc<EMAIL_ADDRESS>| | | Date:   Mon Nov 27 15:00:44 2017 -0500
| | |
| | |     Merge pull request #20255 from mberhault/marc/fix_dump
| | |
| | |     cli: dump: fix infinite loop in when resolving dependencies.
| | |
| * | commit 60fe5ad05b86e09be403ebd2dbe8087c134556fa
| | | Author: marc<EMAIL_ADDRESS>| | | Date:   Fri Nov 24 16:03:05 2017 -0500
| | |
| | |     cli: dump: fix infinite loop in when resolving dependencies.
| | |
| | |     While this will avoid the loop and keep dependency order, there may
| | |     still be problems with dependency cycles.
| | |
| | |     This came up in #20254 when encountering a foreign key referring to the
| | |     same table.
| | |
| | |     Before the fix, the test fails with:
| | |     ```
| | |     runtime: goroutine stack exceeds<PHONE_NUMBER>-byte limit
| | |     fatal error: stack overflow
| | |     ```
| | |

Just one from me:
cli: dump: fix crash on dependency cycles [#20255]
All others are cleanups/refactors/work for future features.

Nothing from me (checked my box).

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4b36d581834c7b84e89495d38db10154a5ef69eb/

Sorry, @jseldess! Hopefully this'll get easier now that there's a lint warning in place to help us remember to include these.
The additional only release note that may be needed from my commits is:
(General Change) Alpha and beta releases are now published as Docker images under the name cockroachdb/cockroach-unstable  #20331

(Performance improvement) replace interval tree structure in CommandQueue with arena-backed concurrent skiplist. Reduces global locking and GC pressure, improving average and tail latencies.
(Bug fix) prevent context cancellation during lease acquisition from leaking to coalesced requests.

@nvanbenschoten Did you mean s/CommandQueue/TimestampCache/g?

... wow yeah, but one can dream!

None required for any of my commits.

Release note (sql): the SHOW [KV] TRACE statement now properly extracts file/line number information when analyzing traces produced in debug mode. A new SHOW COMPACT [KV] TRACE statement is also provided to provide a more compact view on the same data. #20093
Release note (sql): some queries using IS NOT NULL conditions are now better optimized. #20436

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9a68a4e1a024eda6a546682bc1802475a4dcccc1/

Release note (sql change): Views now support LIMIT and ORDER BY (#20246).
Release note (admin ui change): The Admin UI now sets the Last-Modified header when serving assets to permit browser caching.  AS ...`](../v1.2/create-table-as.html) is now [`SELECT`](../v1.2/select.html), like in PostgreSQL. [#20268](https://github.com/cockroachdb/cockroach/pull/20268)
- OIDs can now be compared with inequality operators. [#20367](https://github.com/cockroachdb/cockroach/pull/20367)
- The [`CANCEL JOB`](../v1.2/cancel-job.html) statement now supports cancelling [`IMPORT`](../v1.2/import.html) jobs. [#20343](https://github.com/cockroachdb/cockroach/pull/20343)

s/cancelling/canceling

releases/v1.2-alpha.20171211.md, line 64 at r2 (raw file):

- Added missing Distributed SQL flows to the exported `sql.distsql.flows.active` and `sql.distsql.flows.total` metrics and the "Active Flows for Distributed SQL Queries" admin UI graph. [#20503](https://github.com/cockroachdb/cockroach/pull/20503)
- Fixed an issue with stale buffer data when using the binary format for [`ARRAY`](../v1.2/array.html) values. [#20461](https://github.com/cockroachdb/cockroach/pull/20461)
- The [`cockroach sql`](../v1.2/use-the-built-in-sql-client.html) shell now better reports the number of rows inserted by a [`CREATE TABLE ... AS ...`](../v1.2/create-table-as.html) statement. Note,  however, that the result are still formatted incorrectly if the `CREATE TABLE ... AS ...` statement create zero rows in the new table. [#20268](https://github.com/cockroachdb/cockroach/pull/20268)

s/create/creates/

releases/v1.2-alpha.20171211.md, line 78 at r2 (raw file):

- Improved p99 latencies for garbage collection of previous versions of a key, when there are many versions. [#20373](https://github.com/cockroachdb/cockroach/pull/20373)
- Smoothed out disk usage under very write heavy workloads by syncing to disk more frequently. [#20352](https://github.com/cockroachdb/cockroach/pull/20352)
- Improved garbage collection of very large [transactions](../v1.2/transactions.html) and large volumes of abandoned writes (intents). [#20396](https://github.com/cockroachdb/cockroach/pull/20396)

s/writes (intents)/write intents/
or...something like that "writes intents" is odd.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4898cc6178f500060e49107e4ca5bf7465ced7ed/


[folly] build failure

Operating system
Fedora Linux 38 (Container Image)
Compiler
gcc (GCC) 13.1.1 20230511 (Red Hat 13.1.1-2)
Steps to reproduce the behavior
./vcpkg install folly

Failure logs
root@NixOS-RoT ~/vcpkg (master) [1]# ./vcpkg install folly
Computing installation plan...
The following packages will be built and installed:
    folly[core,zlib]:x64-linux -> 2<IP_ADDRESS>#6
Detecting compiler hash for triplet x64-linux...
Restored 0 package(s) from /root/.cache/vcpkg/archives in 6.92 us. Use --debug to see more details.
Installing 1/1 folly:x64-linux...
Building folly[core,zlib]:x64-linux...
-- Using cached facebook-folly-d8ed9cd2869c74b00fa6f1a7603301183f5c2249.tar.gz.
-- Cleaning sources at /root/vcpkg/buildtrees/folly/src/183f5c2249-df85b9f5e8.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /root/vcpkg/downloads/facebook-folly-d8ed9cd2869c74b00fa6f1a7603301183f5c2249.tar.gz
-- Applying patch reorder-glog-gflags.patch
-- Applying patch disable-non-underscore-posix-names.patch
-- Applying patch boost-1.70.patch
-- Applying patch fix-windows-minmax.patch
-- Applying patch fix-deps.patch
-- Using source at /root/vcpkg/buildtrees/folly/src/183f5c2249-df85b9f5e8.clean
-- Configuring x64-linux
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: /usr/bin/cmake --build . --config Debug --target install -- -v -j7
    Working Directory: /root/vcpkg/buildtrees/folly/x64-linux-dbg
    See logs for more information:
      /root/vcpkg/buildtrees/folly/install-x64-linux-dbg-out.log

Call Stack (most recent call first):
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/folly/portfile.cmake:69 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

error: building folly:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+folly
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?title=[folly]+Build+error&body=Copy+issue+body+from+%2Froot%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

Additional context
install-x64-linux-dbg-out.log

I just met the same build error issue, but my vcpkg is up to date (version 2023-08-09). The log is shown in the following:
Package: folly[core,zlib]:x64-linux -> 2<IP_ADDRESS>
Host Environment

Host: x64-linux
Compiler: GNU 11.4.0
vcpkg-tool version: 2023-08-09-9990a4c9026811a312cb2af78bf77f3d9d288416
vcpkg-scripts version: c95000e1b 2023-08-18 (32 hours ago)

To Reproduce
vcpkg install folly
Failure logs
-- Using cached facebook-folly-v2<IP_ADDRESS>.tar.gz.
-- Cleaning sources at /home/suyupilemao/vcpkg/buildtrees/folly/src/<IP_ADDRESS>-e0c29fc583.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/suyupilemao/vcpkg/downloads/facebook-folly-v2<IP_ADDRESS>.tar.gz
-- Applying patch reorder-glog-gflags.patch
-- Applying patch disable-non-underscore-posix-names.patch
-- Applying patch boost-1.70.patch
-- Applying patch fix-windows-minmax.patch
-- Applying patch fix-deps.patch
-- Applying patch openssl.patch
-- Using source at /home/suyupilemao/vcpkg/buildtrees/folly/src/<IP_ADDRESS>-e0c29fc583.clean
-- Configuring x64-linux
-- Building x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: /home/suyupilemao/vcpkg/downloads/tools/cmake-3.27.1-linux/cmake-3.27.1-linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j17
    Working Directory: /home/suyupilemao/vcpkg/buildtrees/folly/x64-linux-dbg
    See logs for more information:
      /home/suyupilemao/vcpkg/buildtrees/folly/install-x64-linux-dbg-out.log

Call Stack (most recent call first):
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/folly/portfile.cmake:70 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)


Single sign out support

Is it possible to configure Flask-CAS to support single logout?

That's more of a CAS issue than a Flask-CAS issue.  The default /logout path goes to the CAS logout, but it's wise to destroy the app session.
Single Sign Out is a general issue due to cross-domain browser cookie restrictions (for good reason!).  As a client side middleware, Flask-CAS is probably already doing all it can here.

Well - my problem is that Flask-CAS sends as 'service' parameter http://some-url/login. So if I configure my CAS Server for single sign out it tries to logout the user with the same url (POST request to http://some-url/login) which doesn't work. So one possibility would be to handle that request in login and redirect to logout. I was just asking if something like that might have been already implemented and just needs to be configured.

In case anyone is having the same issue, here's how I solved it:
from xmltodict import parse

@csrf.exempt
@app.route('/login/', methods=['POST'])
def cas_logout():
    if request.form.get('logoutRequest'):
        logout_request = parse(request.form['logoutRequest'])
        ticket = logout_request.get('samlp:LogoutRequest', {}).get('samlp:SessionIndex')
        # get corresponding session and invalidate it
        if ticket:
            sess = r.get(ticket)
            if sess:
                r.delete(sess)
                r.delete(ticket)
                return 'OK'
    return 'Bad Request', 400

my application can not single sign out, how to configure flask client or cas-server


Spring-cloud-stream and spring-cloud-config messing up multiple binder config

issue
I found an issue when using spring-cloud-stream and spring-cloud-config using multiple binders.
Starting the demo app without config-service everything works perfect. All bindings are directed to their dedicated connection.
Activating the config-service results in false connections. All bindings are directed to the default connection. Erroneous exchanges/queues are created.
how to reproduce
I made a demo app to show it.
https://github.com/HaVonTe1/spring-cloud-stream-multiplebinder-config-issue-
In there is a demoservice with simple config in application.yml:
spring:
  rabbitmq:
    host: localhost
    virtual-host: /defaultVH
    username: defaultUser
    password: defaultPassword
  cloud:
    stream:
      bindings:
        sampleQueueA:
          binder: rabbit-A
          contentType: application/x-java-object
          group: groupA
          destination: sampleQueueA
        sampleQueueB:
          binder: rabbit-B
          contentType: application/x-java-object
          group: groupB
          destination: sampleQueueB
      binders:
        rabbit-A:
          defaultCandidate: false
          inheritEnvironment: false
          type: rabbit
          environment:
            spring:
              rabbitmq:
                host: localhost
                virtualHost: /vhA
                username: userA
                password: paswdA
                port: 5672
                connection-timeout: 10000
        rabbit-B:
          defaultCandidate: false
          inheritEnvironment: false
          type: rabbit
          environment:
            spring:
              rabbitmq:
                host: localhost
                virtualHost: /vhB
                username: userB
                password: paswdB
                port: 5672
                connection-timeout: 10000

There is also a bootstrap.yml for using the config-service:
spring:
  main:
    banner-mode: "off"
  application:
    name: demo-service
  cloud:
    config:
      enabled: true #change this to use config-service
      retry:
        maxAttempts: 3
      discovery:
        enabled: false
      fail-fast: true

When setting spring.cloud.config.enabled=false the rabbit connections are just fine:
image_rabbit_good
But with spring.cloud.config.enabled=true the connections are messed up.
image_rabbit_bad
I made 100% sure the config-service is delivering the exact same properties like the application.yml of the demoservice includes.
expected behaviour
Regardless of using the config-service. The connections should be the same.

@HaVonTe1 Didn't you raise the same issue in spring-cloud-config the other day? I thought I saw something similar.

Yes I did. I dont know if this is a config-service or cloud-stream issue. The config guys didnt comment on this so I thought of giving it a try here also.

Thanks, I'll give it a look and reach out to the config team as well.

@HaVonTe1 I've pinged the 'config' guys, possibly some extra config being pulled up as part of the switch to s-c-config. They are looking at it. Will let you know.
Thank you for being patient

The problem with your configuration is that it defines spring.rabbitmq.* in the config server, and these properties always take precedence over the ones provided by the binder in Spring Cloud Stream. The problem essentially stems from the way Spring Cloud Stream creates the binder's ApplicationContext. You can probably work around it by making config server properties lower priority (http://cloud.spring.io/spring-cloud-static/Dalston.SR4/single/spring-cloud.html#overriding-bootstrap-properties).

The definition of spring.rabbitmq.* is necessary for Actuator. Without this config, the "/health" check will use default credentials (guest/guest@/) in RabbitHealthIndicator.
Disabling this indicator is not an option. We must make sure Rabbit is up and running.

and these properties always take precedence over the ones provided by the binder in Spring Cloud Stream.

I dont think this is correct.
This would not explain why everything is fine when the config-service is switched off.

You can probably work around it by making config server properties lower priority

Do you mean adding the binding configs in bootstrap.yml and telling the demoservice to ignore the properties from config-service?
Well this would mean to disable the config-service at all. Right? Why use it at all in further??

I dont think this is correct.

It is. When the config server is switched off that property source is not used, so it can't get in the way.

Well this would mean to disable the config-service at all.

That's not what I suggested. Did you read the documentation in that link?

Ok. It is hard to understand why some properties are only used when they are serverd by the config-service. Please forgive me my confusion.
I read the docs in the link but what I understood was:

set spring.cloud.config.overrideSystemProperties=false
use SystemProperties/Environment Vars to set up the bindings

Is this correct? Or can you provide an example?

Per the user guide I would say that you need to set spring.cloud.config.allowOverride=true (in the remote properties) and either spring.cloud.config.overrideSystemProperties=false or spring.cloud.config.overrideNone=true. You don't need to set any system properties (that's kind of the point of what the Stream binder is doing).

I am sorry, but it didnt work.
I made a branch in my demo project on github to test your suggestions.
https://github.com/HaVonTe1/spring-cloud-stream-multiplebinder-config-issue-/tree/issue/1124
Please have a look at it and tell me if I made something wrong.

Based on your hints about the role of the spring.rabbitmq.* properties I found a solution/workaround.
See https://github.com/HaVonTe1/spring-cloud-stream-multiplebinder-config-issue-/tree/workaround
I still think this is a serious issue and needs resolving but the workaround helps me to go further withour getting rid of cloud-config.
Thanks a lot.
I lay it up to you to close this issue or not.

I sent a PR to your sample repo (https://github.com/HaVonTe1/spring-cloud-stream-multiplebinder-config-issue-/pull/1). You need to put the override settings in the remote properties as well.

@dsyer I merged the PR and tested it.
It worked like a charm.
I still would like to classify  this as some kind of workaround. Because the config file deliverd from cloud-config differs from the one that would be used without cloud-config. But I guess this is more than acceptable.
I realy want to thank you for your help.

I still would like to classify this as some kind of workaround.

That's why I said "You can probably work around it by making config server properties lower priority".

@HaVonTe1 is it ok to resolve this issue or there are still some outstanding questions you have?

By creating the  new issue (1136) I am fine. This can be closed.

#1136 is nothing to do with this is it? This issue is still open as far as I know.

Oh Ok. Sry. I got confused.

@HaVonTe1  Is this still an issue?

I think that this issue is related/same as https://github.com/spring-cloud/spring-cloud-stream/issues/1273 which have been addressed now. Please feel free to reopen it if you believe it is still an issue

: Can you please help me with, why it is not creating the Virtualhosts in respective users.

Attempting to connect to: [localhost:5672]
2019-02-22 16:25:10.151  WARN 47440 --- [ <IP_ADDRESS>:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Socket closed)
2019-02-22 16:25:10.155  WARN 47440 --- [:0:0:0:0:1:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Socket closed)
2019-02-22 16:25:10.336  INFO 47440 --- [eueA.groupA-253] o.s.a.r.l.SimpleMessageListenerContainer : Restarting Consumer@34d19ae6: tags=[[]], channel=null, acknowledgeMode=AUTO local queue size=0
I ran the same program for me its not creating the any Virtual-Hosts


Test failure with latest nestedtext

With the latest nestedtext release, there seems to be a test failure.
============================= test session starts ==============================
platform linux -- Python 3.10.9, pytest-7.2.0, pluggy-1.0.0
rootdir: /build/parametrize_from_file-0.17.0, configfile: pyproject.toml
collected 300 items

parametrize_from_file/__init__.py .....                                  [  1%]
tests/test_namespace.py ................................................ [ 17%]
........................................................................ [ 41%]
................................                                         [ 52%]
tests/test_parameters.py ..........................F.................... [ 68%]
.....................................                                    [ 80%]
tests/test_schema.py ................................................... [ 97%]
........                                                                 [100%]

=================================== FAILURES ===================================
___________ test_load_suite_params_err[load-err.nt-files5-messages5] ___________

loader = <function load at 0x7ffff66c49d0>, path = 'err.nt'
files = {'err.nt': 'a ='}
messages = ['failed to load parametrization file', 'attempted to load file with: nestedtext.load\\(\\)']
tmp_path = PosixPath('/build/pytest-of-nixbld/pytest-0/test_load_suite_params_err_loa2')

    @pytest.mark.parametrize(
            'loader, path, files, messages', [(
                lambda p: None,
                'does-not-exist.json',
                {},
                [
                    "can't find parametrization file",
                    "does-not-exist.json",
                ],
            ), (
                # Check examples of real files that the built-in loaders will fail
                # to parse, to make sure that the error messages are still good.
                pffp.get_loaders()['.json'],
                'err.json',
                {'err.json': '{"a":'},
                [
                    "failed to load parametrization file",
                    r"attempted to load file with: json.load\(\)",
                    "Expecting value",
                ],
            ), (
                pffp.get_loaders()['.yml'],
                'err.yml',
                {'err.yml': ':'},
                [
                    "failed to load parametrization file",
                    r"attempted to load file with: yaml.safe_load\(\)",
                    "expected <block end>, but found ':'",
                ],
            ), (
                pffp.get_loaders()['.yaml'],
                'err.yaml',
                {'err.yaml': ':'},
                [
                    "failed to load parametrization file",
                    r"attempted to load file with: yaml.safe_load\(\)",
                    "expected <block end>, but found ':'",
                ],
            ), (
                pffp.get_loaders()['.toml'],
                'err.toml',
                {'err.toml': 'a ='},
                [
                    "failed to load parametrization file",
                    r"attempted to load file with: toml.decoder.load\(\)",
                    "Empty value is invalid",
                ],
            ), (
                pffp.get_loaders()['.nt'],
                'err.nt',
                {'err.nt': 'a ='},
                [
                    "failed to load parametrization file",
                    r"attempted to load file with: nestedtext.load\(\)",
                ],
            ), (
                # Any braces in error messages must not be evaluated by tidyexc.
                value_error_with_braces,
                'braces.xyz',
                {'braces.xyz': ''},
                [
                    "failed to load parametrization file",
                    "attempted to load file with: .*value_error_with_braces",
                    r"\{hello world\}",
                ],
            ),
        ]
    )
    def test_load_suite_params_err(loader, path, files, messages, tmp_path):
        for p, contents in files.items():
            (tmp_path / p).write_text(contents)

        with pytest.raises(pff.ConfigError) as err:
            pffp._load_and_cache_suite_params(loader, tmp_path / path)

        for msg in messages:
>           assert err.match(msg)
E           AssertionError: Regex pattern did not match.
E            Regex: 'attempted to load file with: nestedtext.load\\(\\)'
E            Input: 'failed to load parametrization file\n• attempted to load file with: nestedtext.nestedtext.load()\n✖ /build/pytest-of-nixbld/pytest-0/test_load_suite_params_err_loa2/err.nt, 1: unrecognized line.\n'

tests/test_parameters.py:269: AssertionError
=========================== short test summary info ============================

I'm not familiar with the code base of parametrize_from_file thus all help would be appreciated. Thanks.

Sorry for the slow reply; for some reason I didn't notice this issue when you originally posted it.  This test failure is just due to a change in the way a certain error message is worded, so it's not something that will adversely affect users.  It was fixed by 1fb2b7b, but I haven't made a new release with that commit yet since there haven't been any user-facing changes since then.  If this is causing problems for you, though, let me know and I can make a new release.

I'm closing this issue now that I've finally made a new release.  Let me know if you are still having problems.


cross-platform: DateTime Implementation

Implements DateTime support Cross-Platform
Redesigns DaylightHelper and Date utilities
Replaces #915

            && preciseTime >= dLastTime)              // the time computed via perf counter is running backwards

Should you add an assert here that the time is always going forward?

Refers to: lib/Runtime/Base/HiResTimer.cpp:82 in d4b6df9. [](commit_id = d4b6df9211d96423e2d47acefe8f50a419af8fa0, deletion_comment = False)

PR is updated and re-based to latest

This requires benchmark runs (Octane\SS\Kraken\Jetstream)


x/mobile: iOS Simulator crash when running under Rosetta

When running an iOS app on Simulator under Rosetta (sometimes necessary when certain libraries do not support arm64 simulator), importing an xcframework built with gomobile makes the app freeze on boot, makes it crash when trying to stop it from XCode, and leaves the Simulator in a broken state.
This happend with a library we are working on, then I reproduced it with a minimal gomobile library test project ( https://github.com/arantes555/gomobile_test ).
When building this project with gomobile bind -target=ios -prefix=GomobileTest -v -o=./GomobileTest.xcframework ./mobile_sdk, then importing the resulting .xcframework in a freshly created template iOS app (both swift and objc), the app works correctly on Intel mac, works correctly on M1 mac using arm64 Simulator, but crashes on M1 mac using rosetta Simulator. Here is a repo with an iOS app which reproduces the issue : https://github.com/arantes555/gomobile_ios_crash_repro_app
When running on rosetta, the app freezes on start, and does not do anything. Then, when trying to use the Stop button from XCode, I get the following error in the XCode console:
assertion failed [gTaskSuspended]: cannot resume thread when task not suspended (DebugServer.cpp:230 thread_resume) Message from debugger: failed to send the k packet

Also, I get a crash report window with an error stack including these lines:
Coalition: com.apple.CoreSimulator.SimDevice.8813C46E-A23C-47F2-A621-0510CA85B316 [72815]
Responsible Process: SimulatorTrampoline [68471]

The full error report is in this file : simulator crash.txt
Lastly, after this, the simulator is left in a weird state where it does not respond to the XCode commands, and when closing it I get the error contained in this file : simulator-crash-2.txt
I am aware this is probably a bug in Rosetta itself, and I also reported it to Apple, but maybe the Go community can fix it on our side.

cc @golang/ios

After some investigation, it seems this also happens on a CGo library built for iOS.

As you mentioned, the assertion failure looks like a bug in Rosetta. Thank you for reporting to Apple.
For a workaround, you may try setting the environment variable GODEUBG=asyncpreemptoff=1 and don't send signals to you program. In the past Rosetta is known to have a number of bugs related to signal handling (which are fixed, but new bug could appear).

Hello @cherrymui . Thanks for your answer. Looks like setting the env var at runtime works ! Thank you very much ! Looks like there may be a few bugs related to signal handling left in Rosetta ... Is this something that could be solved on Go's side, or only on Apple's side? Just in case, here is my precise setup:

Macbook Air M1
macOS Ventura 13.2.1
XCode 14.3.1
Simulator 14.3.1 (994) SImulatorKit 629 CoreSimulator 885.2
I don't think there is a way to check a version for the rosetta runtime itself?

If there's anything else I can do to help diagnose this?
BTW, I didn't send any signal manually, except starting / stopping the app through XCode.

Setting the environment variable is probably the best workaround. I don't think we're going to disable signals by default on the Go side for this bug. As signals can arrive at any point, it doesn't seem easy to have a more limited workaround. Given the assertion text

assertion failed [gTaskSuspended]: cannot resume thread when task not suspended (DebugServer.cpp:230 thread_resume) Message from debugger: failed to send the k packet

It looks like the Rosetta runtime is probably in some inconsistent state, perhaps due to a race condition.
Are you running under some debugger? (LLDB? Within Xcode?) Maybe that adds another layer of complexity. If so maybe you could try not running under debugger?
I think Apple usually fixes bug like this in a reasonable amount of time, so I hope it will get fixed soon. If you could write a C producer (perhaps sending a bunch of signals to itself or to another thread in the same process), that may speed up Apple's fix. Thanks.

To reproduce the bug, I simply:

Create fresh ios app from XCode
Force it to run under rosetta (Product -> Destination -> Destination Architectures -> Show both, then selecting a "(Rosetta)" destination
importing any xcframework built from gomobile
using the "play" button in xcode to start the app.

I am not doing anything special to attach a debugger, not sure if XCode attaches a debugger by default.
I am sorry but I definitely don't have the knowledge to write a C repro case for this.
The env var workaround works for me for the moment. I guess the ball is in Apple's court.
Feel free to close the issue if you believe there is nothing more to do on Go's side. Or leave it open if you prefer until I update you about Apple's answer to my report.
Thanks again for your help!

Hello @arantes555, I hope this message finds you well. I've been experiencing the same freezing issue that you've described in this thread. Despite trying several solutions (based on the env var workaround), including adding an environment variable through Xcode scheme (the screenshot) and the gomobile bind command (GODEBUG=asyncpreemptoff=1 gomobile bind...), I've not had any success when running under Rosetta simulators. If it's not too much trouble, could you please explain your approach in details to help me resolve this issue? Your insights would be greatly appreciated, many thanks.

This thread saved my day!!! For those also suffering from this issue, here's how to set up the workaround in your Xcode


Split and cached model

(cached model)

Adds a CachedEoS, that can perform caching.
ideally, all caching operations should be done in this type instead of each model. a basic TP interpolation scheme is implemented for sat_pure.
(split model)
SingleParam, PairParam, AssocParam, GroupParam and SiteParam are "splittable", that is, split_model(param) will return a vector of params for each component. for that, SiteParam and GroupParam have now some parameters that were present before in the eos struct.
GroupParam has a constructor that skips the csv, that constructor is only used if no csv to parse are passed.
model.allcomponentnflattenedgroups -> model.groups.n_flattenedgroups
model.allcomponentnsites -> model.sites.n_sites
model.allgroupsnsites -> model.sites.n_sites (same)
SiteParam now has a printing method. with that, all ClapeyronParams now have pretty printing
new models:
joback model is up, (a_ideal is missing)
improvement in models:
GERG2008 now uses the same printing structure that the rest of EoS uses
SAFTgammaMie is around 2x faster, by sacrificing some pretty functions and using some static arrays)

Codecov Report

Merging #33 (227ee9b) into master (c2b281d) will decrease coverage by 3.61%.
The diff coverage is 24.20%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
- Coverage   52.72%   49.10%   -3.62%
==========================================
  Files          57       60       +3
  Lines        4537     4916     +379
==========================================
+ Hits         2392     2414      +22
- Misses       2145     2502     +357

Impacted Files
Coverage Δ

src/Clapeyron.jl
100.00% <ø> (ø)

src/methods/initial_guess.jl
25.00% <0.00%> (-0.51%)
:arrow_down:

src/models/eos/SAFT/LJSAFT/LJSAFT.jl
0.00% <0.00%> (ø)

src/models/eos/cached/CachedEoS.jl
0.00% <0.00%> (ø)

...odels/eos/cached/sat_pure_aprox/TPInterpolation.jl
0.00% <0.00%> (ø)

src/models/eos/ideal/JobackIdeal.jl
0.00% <0.00%> (ø)

src/utils/visualisation.jl
0.00% <0.00%> (ø)

src/methods/methods.jl
13.33% <7.14%> (-86.67%)
:arrow_down:

src/utils/ClapeyronParam.jl
19.02% <19.09%> (-2.33%)
:arrow_down:

src/utils/macros.jl
41.26% <44.44%> (-14.00%)
:arrow_down:

... and 18 more

Continue to review full report at Codecov.

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


Should use java.lang.Math.addExact() for runtime int add operation

Description:
$subject.
Currently its a LADD instruction and doesn't handle byte overflow.

Assign to @Nadeeshan96

int i =<PHONE_NUMBER>854775807;
i = i + 1;

Above should overflow and crate a runtime error, we can use java.lang.Math.addExact() to achieve this


Try to get rid of data$column notation

https://github.com/jhudsl/intro_to_R_class/issues/53

Think we did this


Change ga_add_string to ga_copy_string in MMBackend.m

Patch 8.2.4040 missed this change in MMBackend.m, creating an issue that crashes MacVim when multiple files are dropped into MacVim window.

ref #1227

Thank you, but I think better to remove vim_free(escapedFname) rather than changing to ga_copy_string().
(to be accurate, need check the result of ga_add_string() and do vim_free() if failed)

Thank you, but I think better to remove vim_free(escapedFname) rather than changing to ga_copy_string(). (to be accurate, need check the result of ga_add_string() and do vim_free() if failed)

Thanks. I'm not the expert on MacVim development; this patch merely helped me to resolve this issue locally. If there is a better solution, feel free to ignore mine.😀

fixed #1227

I just merged it. Thank you 👍


Fix references to master branch as main

Noticed this when working on previous PR

lgtm - could we backport?

Yes will do


Create Spectra-Jool-shine-on-Laythe

Add-on for Spectra

MISTAKE IN NAME; change to: Spectra-JoolShineOnLaythe


(GH-36) Installation Scripts use WScript Note

Closes #36

:+1:

@ferventcoder updated with suggested changes.

Requires rebase.

@ferventcoder rebased.


Trailing slash and route parameters

I was reading the cookbook
https://www.slimframework.com/docs/v4/cookbook/route-patterns.html
The first thing I noticed is that the TrailingSlash middleware would need to call the redirect method as well like so
$app->add((new TrailingSlash(true))->redirect($responseFactory));
Otherwise I find the behavior a bit inconsistent when adding a trailing slash
$app->get('/hello/{name}/') => works well
$app->get('/hello/{name}') => doesn't work because it doesn't have the trailing slash
it would be great that defined routes worked in both cases regardless of the ending slash that may change due to a middleware that is added or not.

Unfortunately we don’t control the route pattern matching. FastRoute provides that functionality which is a dependency of Slim.
The middleware is specifically designed to remove the trailing slash from the URI and needs to be place on the outermost layer of the middleware stack so when routing is performed the route can be matched without the slash.
As for redirection, you can implement your own middleware to do that if you care to.


Pagination and Total Answer Count Loading Issue on Question Details Page

Describe the bug
There is a pagination issue on the answer list within the question details page. The total count of answers and the pagination list fail to load correctly. The pagination is constantly set to 1, and the total count of answers matches the number on a single page. This bug occurs across all devices and operating systems, and is independent of the browser and its version.
To Reproduce
Steps to reproduce the behavior:

Go to the question details page.
Observe the answer list section.
Notice that the pagination is always set to 1, regardless of the number of answers.
Observe that the total count of answers is equal to the number of answers on one page, indicating a failure in loading the correct total.

Expected behavior
The expected behavior is that the answer list should correctly load with appropriate pagination. The total count of answers should reflect the actual number of answers available, and pagination should adjust accordingly, allowing users to navigate through multiple pages if necessary.
Screenshots
Not applicable.
Platform (please complete the following information):

Device: All (e.g. Desktop, Mobile)
OS: All (e.g. macOS, Windows, iOS, Android)
Browser: All (e.g. Chrome, Safari, Firefox)
Version: All_versions

Working on fix this bug...

First of all, thanks for your contribution！
Answers are not paged because current technology would cause performance degradation if the url of an answer was accessed directly, so given that there aren't many answers yet, there is no paging.
eg: When you visit this answer link: https://meta.answer.dev/questions/D13i/E14i；We need to display the answer with id=E14i. If the answer is not on the current page,performance will be affected! Therefore, paging has not been used here.

I understand what you mean, thank you for the explanation.
In the situation you described, there indeed exists such an issue, and perhaps we can improve it in this way:

if the Q&A in the link exists on the first page of the answer list, then we can simply scroll to the corresponding position;
if the answer is not on the first page, then we can add a 'Related Answer' section at the front of the answer list to directly load and display this answer, avoiding the need to handle subsequent pagination issues;
whether to name this section 'Related Answer' can be further considered.

In our use of 'answer', the number of user answers has already exceeded 20, so directly removing the pagination feature would cause users to be unable to view more answers.

We will consider the solution you mentioned, and more discussion is needed on exactly how to solve the problem.


Playground download: Make sure that the canvas area occupies 100% of the surface.

See https://forum.babylonjs.com/t/html-page-demo-is-broken/39280/4

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13701/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13701/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13701/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13701/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13701/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13701/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13701/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13701/merge#BCU1XR#0


Flaky tests HealthcareAsyncCancellation

See https://dev.azure.com/azure-sdk/internal/_build/results?buildId=610284&view=logs&j=196c4937-6990-58b5-7d18-234ac2f0888b&t=cc1c87ab-eca8-5343-1fbb-f79703f5f67f
Azure.RequestFailedException : Failed to cancel job with job id e994c142-cea6-4ecc-9750-723bae5af7ff as its already completed.

Another instance: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=611550&view=results


Use cluster management commands have some errors

i run some cluster management command such as "cluster delsots" on the 3 masters 3 slaves cluster, it need a  node_id args, but it will raise a TypeError.
this is my cluster env:

<IP_ADDRESS>:7000> CLUSTER nodes

09a04bb91ffa311e1cdd5b778883a60c46313304 <IP_ADDRESS>:7004 slave 5790b6ee3317d7a006b336d350d2b7d1135ec91a 0<PHONE_NUMBER>108 5 connected
7397529702f726de196fe8325a805a5efebb6a50 <IP_ADDRESS>:7000 myself,master - 0 0 1 connected 0-3999 4002-4999 5002-5460
5790b6ee3317d7a006b336d350d2b7d1135ec91a <IP_ADDRESS>:7001 master - 0<PHONE_NUMBER>106 2 connected 5461-10922
fd6d59e7d658363fa304910112515c08f818cb54 <IP_ADDRESS>:7005 slave e81ade1d0deadaa30e679fb9122bfebe9e88b928 0<PHONE_NUMBER>108 6 connected
fd72ca4e22bb2e6f704d6a82eb874e5a75c19003 <IP_ADDRESS>:7003 slave<PHONE_NUMBER>f726de196fe8325a805a5efebb6a50 0<PHONE_NUMBER>607 4 connected
e81ade1d0deadaa30e679fb9122bfebe9e88b928 <IP_ADDRESS>:7002 master - 0<PHONE_NUMBER>609 3 connected 10923-16383

the next is my test code:
from rediscluster import StrictRedisCluster

startup_nodes = [{"host": "<IP_ADDRESS>", "port": "7002"}]

rc = StrictRedisCluster(startup_nodes=startup_nodes, decode_responses=True)

rc.set("foo", "bar")

print(rc.get("foo"))
nodes = rc.cluster_nodes()
for node in nodes:
    print node['port']
    if node['port'] == 7000:
        print node['id']
        id = node['id']
        rc.cluster_delslots(id, 3009, 3011)

and this is the excute result:
root@ubunu-test:~/work/test/python# python basic.py
bar
7005
7001
7002
7004
7003
7000
7397529702f726de196fe8325a805a5efebb6a50
Traceback (most recent call last):
  File "basic.py", line 18, in <module>
    rc.cluster_delslots(id, 3009, 3011)
  File "/usr/local/lib/python2.7/dist-packages/rediscluster/client.py", line 391, in cluster_delslots
    return self.execute_command('CLUSTER DELSLOTS', *slots, node_id=node_id)
  File "/usr/local/lib/python2.7/dist-packages/rediscluster/utils.py", line 93, in inner
    return func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/rediscluster/client.py", line 309, in execute_command
    return self.parse_response(r, command, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/redis/response_callbacks", line 579, in parse_response
    return self.response_callbacks[command_name](response, **options)
TypeError: bool_ok() got an unexpected keyword argument 'node_id'

it seems this command will call the response_callbacks function bool_ok to check the response, and it will pass args "node_id = ....", this args is not used for this command, and the bool_ok is also can not handle it, what this is used? it seems most cluster management commands have this problem. and another problem is the return reslut of the cluster nodes command, it sometimes can not return less than 6 nodes info. i think the result is not correct.
nodes = rc.cluster_nodes()
for node in nodes:
    print node['port']

@ywllx One of the problems was fixed in this commit 97e3f66e376eb2d98edd1a97223e248f26fea526 where i fixed the bool_ok problem. It should fix the other cluster methods that have the same problem with bool_ok error.
I will take another pass on all the CLUSTER ... commands again to see if more are generally broken or not.

@ywllx About the delslot commands. I was thinking about changing it to be abit more magic where you do not need to specify the slot_id for the node that has the slot, but you just specify the slot and the method looks up the node_id by looping over CLUSTER NODES and get the id by itself.

@ywllx I rebuilt the cluster_delslots command in this commit c9648106880c32a511a51c670a00fd3dc6466495
If you find any other bugs with cluster commands, please open a new issue.


Invalid input exception in NODE_MERGE_TEMPLATE of neo4j_csv_publisher

While creating users using User model class, I received the following error for one of the users in our org.
ERROR - Failed to execute Cypher query
 Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/databuilder/publisher/neo4j_csv_publisher.py", line 449, in _execute_statement
    tx.commit()
  File "/usr/local/lib/python3.7/site-packages/neo4j/__init__.py", line 792, in commit
    self.close()
  File "/usr/local/lib/python3.7/site-packages/neo4j/__init__.py", line 815, in close
    self.sync()
  File "/usr/local/lib/python3.7/site-packages/neo4j/__init__.py", line 780, in sync
    self.session.sync()
  File "/usr/local/lib/python3.7/site-packages/neo4j/__init__.py", line 531, in sync
    detail_count, _ = self._connection.sync()
  File "/usr/local/lib/python3.7/site-packages/neobolt/direct.py", line 527, in sync
    detail_delta, summary_delta = self.fetch()
  File "/usr/local/lib/python3.7/site-packages/neobolt/direct.py", line 419, in fetch
    return self._fetch()
  File "/usr/local/lib/python3.7/site-packages/neobolt/direct.py", line 461, in _fetch
    response.on_failure(summary_metadata or {})
  File "/usr/local/lib/python3.7/site-packages/neobolt/direct.py", line 755, in on_failure
    raise CypherError.hydrate(**metadata)
neobolt.exceptions.CypherSyntaxError: Invalid input 'i': expected 't/T' (line 1, column 36 (offset: 35))
"MERGE (node:User {key: 'some.d'name@org.com'})"

In neo4j_csv_publisher.py, we have defined node merge template as
NODE_MERGE_TEMPLATE = Template("""MERGE (node:$LABEL {key: '${KEY}'})
ON CREATE SET ${create_prop_body}
${update_statement}""")

Current Behavior
Due to ' in the email id of the user and use of ' for encoding in NODE_MERGE_TEMPLATE, I am getting invalid input exception
Your Environment

AmunsenDataBuilder version used: 2.6.5
Data warehouse stores: neo4j
Deployment (k8s or native): ECS

Root cause: https://github.com/amundsen-io/amundsen/issues/513
I think here, escaping KEY would suffice -- can you try escaping it on input as a work-around?

@dorianj I can escape it in my input but will it be escaped during auth_user call?


Bump teamviewer version to 14

Motivation for this change
Upgrade teamviewer from version 13 to version 14
Fixes https://github.com/NixOS/nixpkgs/issues/51059
NOTE: TeamViewer segfaults with newer Qt.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Not needed as https://github.com/NixOS/nixpkgs/pull/54259 does it


Fix/issue 376

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

/area event-generator-chart

What this PR does / why we need it:
Fixes pod-template value name for podPriorityClassName
Which issue(s) this PR fixes:

Fixes #376
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] CHANGELOG.md updated

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

64dd477 fix: falco helm chart priorityClassName on pod template
9a5a247 fix: falco helm chart priorityClassName on pod template

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: enmuro
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval by writing /assign @leogr in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @enmuro! It looks like this is your first PR to falcosecurity/charts 🎉

Hi @enmuro, thanks for the PR! Could you please add the DCO? You can find more information here

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

64dd477 fix: falco helm chart priorityClassName on pod template
9a5a247 fix: falco helm chart priorityClassName on pod template
d6cc96f Merge branch 'fix/issue-376' of https://github.com/enmuro/falco-charts into fix/issue-376

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@enmuro: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi, I've added DCO. sorry I'm new to PRs

Hi @enmuro, as @poiana suggested you need rebase and squash/drop some commits. Instruction can be found here.
An easier way could be to close this PR and open a new one from a new branch with you original commit containing the DCO.
Let me know if you need help!

I will create a new one, thank you


HBASE-28612 fix replication quota leak when peer changes

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 18s
master passed

+1 :green_heart:
compile
0m 54s
master passed

+1 :green_heart:
shadedjars
5m 49s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 27s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s
the patch passed

+1 :green_heart:
compile
0m 54s
the patch passed

+1 :green_heart:
javac
0m 54s
the patch passed

+1 :green_heart:
shadedjars
5m 45s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

_ Other Tests _

-1 :x:
unit
12m 29s
hbase-server in the patch failed.

35m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5930/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5930

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5bbae93c5d43 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / d85574aa1f

Default Java
Eclipse Adoptium-17.0.10+7

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5930/1/artifact/yetus-jdk17-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5930/1/testReport/

Max. process+thread count
1838 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5930/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 48s
Docker mode activated.


RSDK-8553-RSDK-8552: create python module template

Jira ticket
This ticket is the start of writing the module templates, with the first being in the Python SDK. Later, this will move on to another repo. A lot of work still has to be done, but those are out of scope for this work.
The cookiecutter tool and package is being used to create a Python module after prompting a user to give necessary information.
An example run is given in the README.md. The README.md is a work in progress, and is specific to how it's being done now. It will change significantly as more work is done on this epic, but it is a start.
(For reviewers: To see a preview of the README, go to the Files changed tab, scroll to the README, click the menu button on the top right, and click View file.)

Closing this PR since we moved this functionality to the RDK


openbmctool:  env python3

Request to change the openbmctool.py shebang line from
#!/usr/bin/python3
to
#!/usr/bin/env python3
Some systems may not have python3 at /usr/bin but have it in $PATH.

@thalerj


sudo docker-compose up failed on local development.

Hello, I was trying Mail For Good on my local development but I receive the following error.
Is there anything I can do to fix it?
Thank you!
arkloves-MacBook-Pro% sudo docker-compose up
Password: ********
mailforgood_redis_1 is up-to-date
mailforgood_postgres_1 is up-to-date
Starting mailforgood_app_1 ... done
Attaching to mailforgood_redis_1, mailforgood_postgres_1, mailforgood_app_1
postgres_1  | The files belonging to this database system will be owned by user "postgres".
postgres_1  | This user must also own the server process.
postgres_1  |
postgres_1  | The database cluster will be initialized with locale "en_US.utf8".
postgres_1  | The default database encoding has accordingly been set to "UTF8".
postgres_1  | The default text search configuration will be set to "english".
postgres_1  |
postgres_1  | Data page checksums are disabled.
postgres_1  |
postgres_1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres_1  | creating subdirectories ... ok
redis_1     | 1:C 14 Mar 02:02:10.660 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
postgres_1  | selecting default max_connections ... 100
redis_1     | 1:C 14 Mar 02:02:10.667 # Redis version=4.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
postgres_1  | selecting default shared_buffers ... 128MB
redis_1     | 1:C 14 Mar 02:02:10.667 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
postgres_1  | selecting dynamic shared memory implementation ... posix
redis_1     | 1:M 14 Mar 02:02:10.671 * Running mode=standalone, port=6379.
postgres_1  | creating configuration files ... ok
redis_1     | 1:M 14 Mar 02:02:10.671 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
postgres_1  | running bootstrap script ... ok
redis_1     | 1:M 14 Mar 02:02:10.671 # Server initialized
postgres_1  | performing post-bootstrap initialization ... ok
redis_1     | 1:M 14 Mar 02:02:10.674 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
postgres_1  | syncing data to disk ... ok
redis_1     | 1:M 14 Mar 02:02:10.674 * Ready to accept connections
postgres_1  |
postgres_1  | WARNING: enabling "trust" authentication for local connections
postgres_1  | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1  | --auth-local and --auth-host, the next time you run initdb.
postgres_1  |
postgres_1  | Success. You can now start the database server using:
postgres_1  |
postgres_1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1  |
postgres_1  | ****************************************************
postgres_1  | WARNING: No password has been set for the database.
postgres_1  |          This will allow anyone with access to the
postgres_1  |          Postgres port to access your database. In
postgres_1  |          Docker's default configuration, this is
postgres_1  |          effectively any other container on the same
postgres_1  |          system.
postgres_1  |
postgres_1  |          Use "-e POSTGRES_PASSWORD=password" to set
postgres_1  |          it in "docker run".
postgres_1  | ****************************************************
postgres_1  | waiting for server to start....LOG:  could not bind IPv6 socket: Cannot assign requested address
postgres_1  | HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
postgres_1  | LOG:  database system was shut down at 2018-03-14 02:02:15 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started
postgres_1  |  done
postgres_1  | server started
postgres_1  | ALTER ROLE
postgres_1  |
postgres_1  |
postgres_1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1  |
postgres_1  | LOG:  received fast shutdown request
postgres_1  | LOG:  aborting any active transactions
postgres_1  | LOG:  autovacuum launcher shutting down
postgres_1  | LOG:  shutting down
postgres_1  | waiting for server to shut down....LOG:  database system is shut down
postgres_1  |  done
postgres_1  | server stopped
postgres_1  |
postgres_1  | PostgreSQL init process complete; ready for start up.
postgres_1  |
postgres_1  | LOG:  database system was shut down at 2018-03-14 02:02:17 UTC
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started
app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start /usr/src/app
app_1       | > NODE_ENV=production npm-run-all --parallel start:*
app_1       |
app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~prestart:main<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~start:main<EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start:main /usr/src/app
app_1       | > node server/index.js
app_1       |
app_1       | npm info lifecycle nonprofit-email-service@1.0.0~prestart:consumer<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~start:consumer<EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start:consumer /usr/src/app
app_1       | > node server/feedback-consumer/consumer.js
app_1       |
app_1       | /usr/src/app/server/models/setting.js:7
app_1       |   throw new Error('AWS encryption password was empty. Set a password by providing the ENCRYPTION_PASSWORD environment variable in .env');
app_1       |   ^
app_1       |
app_1       | Error: AWS encryption password was empty. Set a password by providing the ENCRYPTION_PASSWORD environment variable in .env
app_1       |     at Object.<anonymous> (/usr/src/app/server/models/setting.js:7:9)
app_1       |     at Module._compile (module.js:569:30)
app_1       |     at Object.Module._extensions..js (module.js:580:10)
app_1       |     at Module.load (module.js:503:32)
app_1       |     at tryModuleLoad (module.js:466:12)
app_1       |     at Function.Module._load (module.js:458:3)
app_1       |     at Module.require (module.js:513:17)
app_1       |     at require (internal/module.js:11:18)
app_1       |     at Sequelize.import (/usr/src/app/node_modules/sequelize/lib/sequelize.js:686:61)
app_1       |     at /usr/src/app/server/models/index.js:23:36
app_1       |     at Array.forEach (native)
app_1       |     at Object.<anonymous> (/usr/src/app/server/models/index.js:22:4)
app_1       |     at Module._compile (module.js:569:30)
app_1       |     at Object.Module._extensions..js (module.js:580:10)
app_1       |     at Module.load (module.js:503:32)
app_1       |     at tryModuleLoad (module.js:466:12)
app_1       | npm info lifecycle nonprofit-email-service@1.0.0~start:main: Failed to exec start:main script
app_1       | npm ERR! code ELIFECYCLE
app_1       | npm ERR! errno 1
app_1       | npm ERR<EMAIL_ADDRESS>start:main: `node server/index.js`
app_1       | npm ERR! Exit status 1
app_1       | npm ERR!
app_1       | npm ERR! Failed at the<EMAIL_ADDRESS>start:main script.
app_1       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
app_1       |
app_1       | npm ERR! A complete log of this run can be found in:
app_1       | npm ERR!     /root/.npm/_logs/2018-03-14T02_11_09_715Z-debug.log
app_1       | npm info lifecycle nonprofit-email-service@1.0.0~poststart:consumer<EMAIL_ADDRESS>app_1       | npm info ok
app_1       | ERROR: "start:main" exited with 1.
app_1       | npm info lifecycle<EMAIL_ADDRESS>Failed to exec start script
app_1       | npm ERR! code ELIFECYCLE
app_1       | npm ERR! errno 1
app_1       | npm ERR<EMAIL_ADDRESS>start: `NODE_ENV=production npm-run-all --parallel start:*`
app_1       | npm ERR! Exit status 1
app_1       | npm ERR!
app_1       | npm ERR! Failed at the<EMAIL_ADDRESS>start script.
app_1       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
app_1       |
app_1       | npm ERR! A complete log of this run can be found in:
app_1       | npm ERR!     /root/.npm/_logs/2018-03-14T02_11_09_776Z-debug.log
mailforgood_app_1 exited with code 1

Hey @darkrubyist - please set a password in your .env file, as in https://github.com/freeCodeCamp/mail-for-good/blob/master/.env.example

Thank you very much for your help.
Now seems that Docker is composing and the server is starting, but when I visit the http://localhost:8080, there is no server running:
Here are my logs. Thank you very much again!

arkloves-MacBook-Pro% sudo docker-compose up
Starting mailforgood_redis_1 ...
Starting mailforgood_redis_1 ... done
Starting mailforgood_app_1 ... done
Attaching to mailforgood_postgres_1, mailforgood_redis_1, mailforgood_app_1
postgres_1  | LOG:  database system was shut down at 2018-03-16 11:54:51 UTC
redis_1     | 1:C 16 Mar 11:57:15.989 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
redis_1     | 1:C 16 Mar 11:57:15.989 # Redis version=4.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1     | 1:C 16 Mar 11:57:15.990 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1     | 1:M 16 Mar 11:57:15.991 * Running mode=standalone, port=6379.
postgres_1  | LOG:  database system is ready to accept connections
postgres_1  | LOG:  autovacuum launcher started
redis_1     | 1:M 16 Mar 11:57:15.992 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1     | 1:M 16 Mar 11:57:15.992 # Server initialized
redis_1     | 1:M 16 Mar 11:57:15.994 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1     | 1:M 16 Mar 11:57:15.994 * DB loaded from disk: 0.000 seconds
redis_1     | 1:M 16 Mar 11:57:15.995 * Ready to accept connections
app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start /usr/src/app
app_1       | > NODE_ENV=production npm-run-all --parallel start:*
app_1       |
app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info it worked if it ends with ok
app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info using<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~prestart:main<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~start:main<EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start:main /usr/src/app
app_1       | > node server/index.js
app_1       |
app_1       | npm info lifecycle nonprofit-email-service@1.0.0~prestart:consumer<EMAIL_ADDRESS>app_1       | npm info lifecycle nonprofit-email-service@1.0.0~start:consumer<EMAIL_ADDRESS>app_1       |
app_1       | ><EMAIL_ADDRESS>start:consumer /usr/src/app
app_1       | > node server/feedback-consumer/consumer.js
app_1       |
app_1       | Feedback consumer started: watching for feedback messages (bounces, complaints, etc) from SQS
app_1       | (node:53) DeprecationWarning: Using the automatically created return value from client.query as an event emitter is deprecated and will be removed in<EMAIL_ADDRESS>Please see the upgrade guide at https://node-postgres.com/guides/upgrading
app_1       | Clickthrough tracking: Make sure that geoip data has been downloaded:
app_1       |    $ cd node_modules/geoip-lite
app_1       |    $ npm run-script updatedb
app_1       |
app_1       |   ############################
app_1       |   #   Mail 4 Good started    #
app_1       |   ############################
app_1       |   # Port: 8080
app_1       |   ############################
app_1       |
app_1       | (node:47) DeprecationWarning: Using the automatically created return value from client.query as an event emitter is deprecated and will be removed in<EMAIL_ADDRESS>Please see the upgrade guide at https://node-postgres.com/guides/upgrading

I figure out why it was not working. http://localhost:8080 didn't work but http://localhost did. Thanks for help @AndrewGHC

@darkrubyist Glad you got it working, thanks.