add aurora workload for third party capital using news-site-next as a basis

This pr adds a new variations of the news-site-next to the apps folder.
This version is using third-party-capital to showcase an example of each available wrapper.
Local testing:
make a copy of the env.example and rename to .env. update api key for google maps

breaking pr into two parts... closing this one


Plugin system

This issue is an umbrella issue for Erlang Performance Lab UI plugin system.
We're working on plugin system which will provide other developers easy way for creating new functionality for Erlang Performance Lab.
Our key part are epl-scripts. This is Node dependency providing dev, build and test functionality for every plugin. It's preconfigured blackbox with all required parts for new EPL plugin development. Because by default epl-scripts are preconfigured we support almost none additional configuration. But there comes eject functionality. You can eject your project which move all epl-scripts config and scripts into your project. This allow you to tweak configs and/or add custom functionality which we don't support. This is one way path. You cannot revert ejection.
Another part are epl-components. This dependency will provide styled component for building new EPL views as well as some helper functions for socket connection, Footer and Menu API, etc.
Both epl-scripts and epl-components will be published to npm.
erlangpl-ui will require some refactoring to allow plugins loading in both development mode as well as production mode. In later phase we're thinking about loading additional plugins at runtime, but this may change in the future.
epl-scripts

[ ] Add Elm support https://github.com/erlanglab/epl-scripts/issues/2
[ ] Make eject work https://github.com/erlanglab/epl-scripts/issues/3

epl-components
erlangpl-ui

Can you please explain eject functionality? I'm not sure I get it 😦

This is concept borrowed from create-react-app. This will remove one dependency (epl-scripts) and move al configs/scripts from this into your project so you can tweak them and adjust as you want.

erlangpl-ui stared as create-react-app project and right now, we're ejected which gives us full control over configuration so we support Elm for example.

Thanks, now I understand :)  Sounds good 👍

I'm going to merge experimental plugin system as fast as possible because we want to merge erlangpl-ui into erlangpl repo. This issue will be updated to contain all things for complete plugins system for both UI and Erlang part.


Can't run at all, asking for help

Comments below were machine-translated
@appleyuchi commented on Wed Apr 08 2020
Python code cannot run:
(Python2.7) appleyuchi @ ubuntu19: bing search API usage $ python test.py
File "test.py", line 10
client = WebSearchClient(endpoint="YOUR_ENDPOINT",CognitiveServicesCredentials(subscription_key))
SyntaxError: non-keyword arg after keyword arg

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 73a384e5-1447-14f0-e55d-37d7c4c6ea1f
Version Independent ID: 2fe02dc2-b1db-14c1-543f-add375503d40
Content: 快速入门：使用必应 Web 搜索客户端库 - Azure Cognitive Services
Content Source: articles/cognitive-services/Bing-Web-Search/quickstarts/client-libraries.md
Service: cognitive-services
Sub-service: bing-web-search
GitHub Login: @aahill
Microsoft Alias: aahi

@srvbpigh commented on Wed Apr 08 2020
Hello, @appleyuchi
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

@CeciAc
Thanks for the feedback! We are currently investigating and will update you shortly.

@CeciAc Hi Cecilia, customer need to replace "YOUR_ENDPOINT" with their actual endpoint url from portal then it should be fine.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Upgrades to Springboot 2.1 and Zipkin Layout Factory v0.0.3

travis is angry https://travis-ci.org/openzipkin/zipkin/builds/449208466?utm_source=github_status&utm_medium=notification

Removed CharacterEncodingFilter as it is no longer required since Springboot doesn't enforce the response encoding
Removed WebMvcConfigurerAdapter as it is deprecated and we can WebMvcConfigurer interface to add the resource handlers

lemme know if you think this is ready to go

I suppose we could merge, but we wouldn't be able to release with this as currently logging is broken. As mentioned in chat, we think this is the same issue as https://github.com/spring-projects/spring-boot/issues/15074.

I would suggest against merge as skippable master is important. there might
be change here that works also with boot v2. we can pull that out and merge.

Oh I see. Thanks for the clarification, I agree then.. Click merge!


Added support for assigner to be a group, when requesting approvals f…

Added support for assigner to be a group, when requesting approvals for a group.

When I ran against a real approval I got this.
WARNING: VS4029130: Invalid parameter combination specified. IncludeMyGroupApprovals parameter is supported only with
parameters (releaseIdsFilter, assignedToFilter and statusFilter = Pending).  Make sure that you either specify
includeMyGroupApprovals as false or specify it along with all the three mentioned parameters.

The includeMyGroupApprovals is now only used when asignedToFilter is filled in.
Added an unit test for that.

:)
On Mar 15, 2018 19:23, Donovan Brown<EMAIL_ADDRESS>wrote:
Merged #38https://github.com/DarqueWarrior/vsteam/pull/38.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DarqueWarrior/vsteam/pull/38#event-1523992300, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZU6gj0Ag389PE-N13AHnLWvy-zQAWJeks5terGSgaJpZM4R2Xw1.


Fix copying report

There is a weird format like /reports/new.1017786038 when I start writing a new report from a previous one. This PR replaces it with /reports/new?id=1017786038.

[x] Replaced /reports/new.XXXXX with /reports/new?id=XXXXX
[x] Copied practices from a previous report
[x] Fixed N+1 problem in categories of report
[x] Show a category name with a practice title

Before

After

@rono23 You are exactly right. Thank you!


Support for setting activeSystemsMisc

Is your feature request related to a problem? Please describe.
We currently support setting these active systems:

--activeSystemsDeploy
--activeSystemsPromote
--activeSystemsRemove
--activeSystemsTask

But we are missing --activeSystemsMisc.
Describe the solution you'd like
I'd like --activeSystemsMisc support added.
Describe alternatives you've considered
The only way to set this at the moment is via manual graphql mutation.
Additional context
n/a

PR #166 added support for activeSystemsMisc but promote still needs to be fixed in Lagoon itself.

Closing this as all the supported flags are in the CLI now, the remaining issues in Lagoon need some attention though (https://github.com/amazeeio/lagoon/issues/2321)


Oracle wallet authentication

Please see the following commit:
https://github.com/msobczak/soci/commit/a3b061af6954d0d9048b34c9c939222bc8e3baca
This improvement adds optional wallet-based authentication for Oracle, which is related to different methods of user authentication that are available there. The modification in code is rather cosmetic.
Let me know if you have any feedback on this before I can introduce this modification in the main repository.

Looks good to me.

:+1:

Committed in:
https://github.com/SOCI/soci/commit/cae51eec9c7fdb28bd2afc261a1f45c73b880e04


C++ unittest cases

I can see python and distributed test cases in the tests/ folder.
I wanted to know whether creating C++ unittests is something that you guys would like in the repo ?
I think it would be useful, to have both C++ and python tests as the C++ tests can test the internal working better rather than just the things exposed by the c_api.
It would be nice to have (wishlist? with the call-for-contributors label?) and would be something I would be interested in contributing.

I am all for it if you are interested in contributing

If you both have a look at my pull request: https://github.com/dmlc/xgboost/pull/1710
You will see I have added basic c++ unit test functionality.  Unfortunately, the test had to be embedded inside the xgboost dll as most required tests within c++ wouldn't be possible as the required data is likely unavailable via the external interface. See my comments under that pull request you will see my thoughts and reasons.

We could adopt gtest, as in other dmlc frameworks. e.g. https://github.com/dmlc/nnvm/tree/master/tests/cpp

I agree with the gtest approach.
In fact I have this Work In Progress commit which I guess would be a good first step to it https://github.com/AbdealiJK/xgboost/commit/6bdaefa1a21fb5e417a8d0d48e60ac01f99d8ded

I didn't even realise this was possible!  If I could use this for my validation code, this would be far superior :+1:


Feature fix rust version

Hi, thanks for the contribution.
there seems to be conflicts, and the PR mixes the fix for rust 1.80 with support for third-party blocks.
could you split the PR in two? this would also avoid having a merge commit in the pr itself, i think.


Error getting an access token

Great tutorial!
I am trying to implement apple sign in for an app (currently in testflight), which also has a web login component which I am trying to get working.
The apple sign in OAuth flow seems to go OK, but the response I get back from the auth / token is a:
stdClass Object
(
[error] => invalid_client
)
https://imgur.com/a/R19oRks
I believe my $client id, $client_secret and $redirect_uri are all correct, as this will cause errors earlier in the Auth flow if they are not set correctly.
Is there anything I might be missing? my php demo can be found at: https://thesnowylist.com.au/appleSignIn.php
Thanks again for a well made tutorial.

This likely means your client secret is wrong, as the token request is the first time it's used. That's the hardest part of the setup since it requires setting a bunch of properties and making the JWT. Double check that you've got the team ID and client ID and key ID all set properly.

Thanks for the reply!
I've double checked my team ID, service identifier (aka "client ID" for web apple sign in) and key ID
I've been using a pure PHP solution to generate the JWT, as I don't have ruby installed on my shared hosting. I'm familiar with creating JWTs for signing push notifications - the structure of that JWT is almost identical to the JWT that is required for apple sign in, the only difference being 3 extra required fields in $claims for apple sign in. I'm using the following code to generate the JWT using my key:

<?php
$keyfile = '/home/thesn142/keys/AuthKey_B4GQ6S6M2V.p8';
$keyid = 'B4GQ6S6M2V';
$teamid = 'T6NP2A4T7T';
$client_id = 'au.com.thesnowylist-web'; //service identifier

$key = openssl_pkey_get_private('file://'.$keyfile);

$header = ['alg'=>'ES256','kid'=>$keyid];
$claims = ['iss'=>$teamid,'iat'=>time(), 'exp' => (time() + (86400*14)), 'aud' => 'https://appleid.apple.com', 'sub' => $client_id];
$header_encoded = rtrim(strtr(base64_encode(json_encode($header)), '+/', '-_'), '=');
$claims_encoded = rtrim(strtr(base64_encode(json_encode($claims)), '+/', '-_'), '=');
$signature = '';
openssl_sign($header_encoded . '.' . $claims_encoded, $signature, $key, 'sha256');
$jwt = $header_encoded . '.' . $claims_encoded . '.' . base64_encode($signature);

$file = '/home/thesn142/public_html/appleSignIn.jwt';
file_put_contents($file, $jwt)

?>

I know you use ruby to create and sign your JWT, but there would be any chance to see if my php version works for you?

I do have a PHP example in the repo, but it uses a JWT library instead of doing it manually.
Looking at your code, it looks like you're using base64_encode for the signature instead of base64-url-encoding it. I'd pull out your rtrim(strtr(base64_encode(json_encode($header)), '+/', '-_'), '=') code into a function and call it base64_urlencode so that you can use it for all three parts.

I will have a look your PHP example... I've updated my code but no success, still invalid_client...:
$keyfile = '/home/thesn142/keys/AuthKey_B4GQ6S6M2V.p8';
$keyid = 'B4GQ6S6M2V';
$teamid = 'T6NP2A4T7T';
$client_id = 'au.com.thesnowylist-web';

$key = openssl_pkey_get_private('file://'.$keyfile);

$header = ['alg'=>'ES256','kid'=>$keyid];
$claims = ['iss'=>$teamid,'iat'=>time(), 'exp' => (time() + (86400*14)), 'aud' => 'https://appleid.apple.com', 'sub' => $client_id];
// $header_encoded = rtrim(strtr(base64_encode(json_encode($header)), '+/', '-_'), '=');
// $claims_encoded = rtrim(strtr(base64_encode(json_encode($claims)), '+/', '-_'), '=');

$header_encoded = base64url_encode(json_encode($header));
$claims_encoded = base64url_encode(json_encode($claims));
$signature = '';
openssl_sign($header_encoded . '.' . $claims_encoded, $signature, $key, 'sha256');
$jwt = $header_encoded . '.' . $claims_encoded . '.' . base64url_encode($signature);

$file = '/home/thesn142/public_html/appleSignIn.jwt';
file_put_contents($file, $jwt);

function base64url_encode($data) {
  return rtrim(strtr(base64_encode($data), '+/', '-_'), '=');
}

The next things to try would be to see if the PHP code in this repo works for you, and also to try running the Ruby version on a different computer (MacOS has Ruby built in so that should work) and try using the generated client secret hardcoded into your actual app. If neither of those work, then that points to a problem elsewhere, such as using the wrong value for the client_id or some other configuration error in the Apple developer portal.

Well, the PHP library and ruby scripts work, the issue was with my client_secret - but I'm sure that's no suprise! It's strange that my basic method of signing works for APNs, but not for Apple Sign In.
Thanks for your help mate, very much appreciated!

No problem! tbh it doesn't surprise me too much, since I'm pretty sure Sign in with Apple is made by a completely different team from the APNS team, and Sign in with Apple seems to have deviated from the OAuth and OIDC standards in ways that make very little sense. Best of luck!

@primeviltom  Can you share some details about what was wrong with your client_secret? I'm currently having the same issue. Already tried the Ruby and PHP scripts from this repo and triple-checked all the parameters with Apple Developer portal.


Performance improvements to security checks when group policies are in effect for ExecutionPolicy

Fixes #2578
When group policies are in effect for execution policy, a check is made to determine if the current process has been launched by gpscript.exe, and in that case, ignore the execution policy.
This is expensive to determine, is done over and over again, and has resulted in very long load times for scripts and modules.
One of the things that is checked (in an expensive way) is the parent id of the current process. That never changes, and is now cached.
The other change is to check once if we are launched by gpscript.exe or not and save that value.
This results in speedups in the order of a magnitude for module loads.

Hi @powercode, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@powercode - it looks like these changes cause the test failures.
@LeeHolmes - can you review these changes?

It is my bad. Fixing now.

Fixing

Pushed new version with
private static int GetParentProcessIdCandidate
instead of
internal static int GetParentProcessId

@powercode Can you please rebase this PR to the latest from master and push an update? It looks like it is ready to merge and just needs final code review sign off.
@LeeHolmes - Please take another look at this PR and provide feedback as appropriate.
@PaulHigin - I am adding you as Lee's backup if he is too busy or if you are curious

@PaulHigin We now have an implementation of GetParentPid available. Using it instead, and inlining the caching as suggested.


Please support release Spark 3.0

It was released yesterday, can you please update
https://spark.apache.org/docs/latest/
I'm happy to create my own base image if this can already be supported

Will create a new release based on Spark 3.0 soon. Stay tuned. Thanks.

I have just built and pushed the following images:
gcr.io/spark-operator/spark:v3.0.0
gcr.io/spark-operator/spark-py:v3.0.0
gcr.io/spark-operator/spark-operator:v1beta2-1.1.2-3.0.0

Thanks @liyinan926, will there be any changes to the API?

@itamar-otonomo There won't be major or backward incompatible changes to the API. There's a couple of new options in Spark 3.0.0 missing in the API. I created https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/954 to add them.

We have pretty much added support for most new options in Spark 3.0.0 that are relevant in the context of the operator. We just added support for a limited form of dynamic allocation without an external shuffle service in #976. Closing this and will prepare a new release for 3.0 soon.

Can you create or point to some docs on the dynamic allocation?


Configuration improvements

When using OCIS, there are two improvements we have identified:

We would like to configure OCIS will plain simple configuration files apart from environment variables
OCIS redefines Reva configuration parameters, making it difficult to understand the connection between OCIS config and Reva config (in practical terms means having to look at the code to see how a OCIS config maps to a Reva config), cannot we just use the same ?

We would like to configure OCIS will plain simple configuration files apart from environment variables

Each service will pick up default configs from predefined locations (see https://github.com/owncloud/ocis/blob/8fa89f50676d065fc469ccb780037135a29639f4/proxy/pkg/command/root.go#L83-L85)

OCIS redefines Reva configuration parameters, making it difficult to understand the connection between OCIS config and Reva config (in practical terms means having to look at the code to see how a OCIS config maps to a Reva config), cannot we just use the same?

Agree. Would like not to repeat variables there. Needs some concept. Closing and opening a follow up on the second point.

We would like to configure OCIS will plain simple configuration files apart from environment variables

Each service will pick up default configs from predefined locations (see https://github.com/owncloud/ocis/blob/8fa89f50676d065fc469ccb780037135a29639f4/proxy/pkg/command/root.go#L83-L85)

OCIS redefines Reva configuration parameters, making it difficult to understand the connection between OCIS config and Reva config (in practical terms means having to look at the code to see how a OCIS config maps to a Reva config), cannot we just use the same?

Agree. Would like not to repeat variables there. Needs some concept. Closing and opening a follow up on the second point.


Not authorized by proxy

I keep getting the following when running mvn clean package.
I have tried specifying proxies for http, https, socks but all in vain using -D command line parameters. Anyone else getting this?
Could not resolve dependencies for project com.uber.uReplicator:uReplicator-Controller:jar:1.0.3-SNAPSHOT: Failed to collect dependencies at org.restlet.jse:org.restlet:jar:2.2.1: Failed to read artifact descriptor for org.restlet.jse:org.restlet:jar:2.2.1: Could not transfer artifact org.restlet.jse:org.restlet:pom:2.2.1 from/to maven-restlet (http://maven.restlet.org): Not authorized by proxy , ReasonPhrase:Proxy Authentication Required. -> [Help 1]

@msiddiqi  Have you solved this issue? I never experienced this before. Maybe check your setting.xml (https://stackoverflow.com/questions/5151345/maven-error-authorization-failed-not-authorized-by-proxy)


feat: add repo files edit views

Added file content viewer components.
Implemented a Git commit dialog with a form.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


lineage from union statement not parsed

Hi maintainers, First of all, thanks for this awesome contribution to the community.
I'm trying to extract the column lineage from a union query, for example:
CREATE OR REPLACE TABLE `project.dataset.table` AS (
    SELECT
        *,
        MIN(title) OVER (
            PARTITION BY title
            ORDER BY title
            ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
        ) AS min_title
    FROM (
        SELECT
            title, comment
        FROM
            `bigquery-public-data.samples.wikipedia` UNION ALL
        SELECT
            corpus, word
        FROM
            `bigquery-public-data.samples.shakespeare`
    )
)

The extracted lineage looks like this:
project.dataset.table.title
                <- $union_all.title
project.dataset.table.comment
                <- $union_all.comment
project.dataset.table.min_title
                <- $union_all.title

But I'll expect:
project.dataset.table.title
                <- bigquery-public-datasamples.wikipedia.title
                <- bigquery-public-datasamples.shakespeare.corpus
project.dataset.table.comment
                <- bigquery-public-datasamples.wikipedia.comment
                <- bigquery-public-datasamples.shakespeare.word
project.dataset.table.min_title
                <- bigquery-public-datasamples.wikipedia.title
                <- bigquery-public-datasamples.shakespeare.corpus

Can you kindly point me to the required changes or help to support this case?
Also what are the limitations of the current extractors, are there unsupported scenarios?

Thank you for reporting this and apologies for the late reply!
We recently released version 0.4.1 of the ZetaSQL Toolkit, which expands the column-level lineage support with a few new features. That includes properly mapping columns for set operations (i.e. UNIONs, INTERSECTs, etc). I tested the query you shared explicitly and it works as expected.
Regarding your question, the current version of column-level lineage extraction should have all bases covered. It supports joins, subqueries, WITH clauses, set operations, STRUCT columns and operations, etc. The only major features that are explicitly not supported at the moment are the PIVOT and UNPIVOT operators.
However, we are yet to do more thorough testing to verify edge cases work as intended. I hope to do that in the near future. In the meantime, feel free to open an issue for any case you find not working as expected!


[RFC] Improved CHANGELOG workflow

Some of the arguments are taken from keepachangelog.com. This is generally a good resource for changelog practices.
Add changelog updates in place with PR
I propose to add new changelog entries directly with the pull request that introduces them to a Unreleased section at the top of CHANGELOG.md (see keepachangelog.com#effort)
The current practice of updating the changelog only when there is a new release is error-prone. If it is directly included, everyone reviewing the PR can directly review the changelog message and make suggestions for improvements. If it's done later, it is more likely that important aspects might be lost. Or entire entries are missed out and require someone else to double check everything (see #4854).
Approving core members can decide if a PR demands an entry in the changelog and if so, check whether it is included and properly implemented.
This way it is easy to preview what (breaking) changes an upcoming release will bring.
I don't see any benefit for updating the changelog in bulk at release, but I'd like to be entertained.
Restrict types of changes
Changelog entries should be restricted to the following set of types:

Added for new features.
Changed for changes in existing functionality.
Deprecated for soon-to-be removed features.
Removed for now removed features.
Fixed for any bug fixes.
Security in case of vulnerabilities.

The changelog currently fits mostly, but there are some few entries that don't adhere to this (like More iconv fixes for FreeBSD in 0.19.4).

I think that if we included every pr as a line in the changelog it'd be unwieldy. Doing the changelog as one operation at the end makes it much much easier to collect similar changes and comment on general efforts inside the stdlib. Viewing a change log as a linear description of simple changes is actually incorrect: that function is already performed by the git commit log. Change logs should be readable and fairly concise and be grouped by function whereas the commit log should be chronological and verbose.

I'm not suggesting every PR should have a changelog entry, just that noteworthy changes are immediately added to the changelog. This could also be for example an addition to an existing entry. This procedure certainly won't prevent rewriting the changelog on release (or somewhere before) if it seems fit. But you don't have to start from scratch looking through all merges since the last release making the release process much easier. This way it's much less likely to mess something up or miss a change entirely.
And imho it makes sense for a changelog to include all changes included in the current code version, not only those that are already released.

Its fairly easy to find all the applicable PRs when writing the change log since we add all PRs to the "next" release. If we're going to to rewrite the change log anyway then why bother adding the extra burden to pr authors to add a line to the change log.

Sure, we can dig for information in commits, but a commit history can be hard to search, with noteworthy features hidden in noise, especially in such a large project. Regularly updating the changelog with noteworthy changes, especially for new features, deprecations, breaking changes and long awaited fixes, is really nicer. No need to dig for information: just look at the changelog!
Pushing the burden to the developer may be leveraged a bit, since maintainers can usually edit a pull request, thus edit the changelog before merge, squash or rebase.
Bonus: if the changelog is directly updated from a pull request, it's commit history will link directly to the curated list of commits and pull requests that affected it. Sweet.

I agree with @ysbaddaden here, having up to date changelog, containing list of note-worthy changes is a welcomed thing to have in every project.
Another thing to note IMO is that changelog-worthy changes might come directly from commits, not from PRs alone, so we're back to digging through history, again.

Sure, we can dig for information in commits, but a commit history can be hard to search, with noteworthy features hidden in noise, especially in such a large project.

This is exactly my point. By encouraging people to make changes to the change log at or around the same time they make their commit messages, the change log will naturally end up being a close reflection of the commit log. And a commit log, which is ungrouped and uncurated is a very bad change log.

Another thing to note IMO is that changelog-worthy changes might come directly from commits, not from PRs alone.

Nobody can commit to master without making a PR any more so this isn't a problem.

The times I prepared the Changelog it took me maybe 15~30 minutes to traverse the commit history, pick the interesting stuff and put it in a text file. I think it's simpler that way. It also means when someone sends a PR they don't have to worry about the Changelog.

We tried having changelog entries added by its PR for quite a while at diaspora. We actually got rid of it since it caused merge conflicts for almost all open PRs after any is merged.
Also I think it's wrong to put the burden of deciding whether something needs a changelog entry on the contributer, it's the maintainers job.
One trick is to amend the changelog entry into the commit as you merge. But that requires doing it locally everytime (even if it's very easy with github/hub) and actually in a rebase based merge strategy also won't show the PR as merged on Github.

@jhass great to hear about some hands-on experience! I didn't figure it would have such an impact on the merge workflow.
While I still think it would be logical to follow the proposed procedure, I guess it makes no sense to hold this up and discuss semantic pros and cons when there is no easily accessible technical solution anyway.
But maybe there are other ideas to improve some of the mentioned issues in a different way?

a section of Unreleased changes allows to see what (breaking) changes are to be expected in the upcoming release. This would be beneficial for library developers to release a working version of their library when a new Crystal version is release without having to regularly build a custom crystal version from master (this would probably not be as important when we have nightly builds).
Note-worthy changes might be missed (like it was the case with 0.23.0 release). Currently, there are quite a few recently merged PRs which are not in the Next milestone. This tends to be forgotten.
Changelog entries are written by the maintainer that publishes the release and who might not be familiar with the implications of each PR that might have been discussed weeks (or months) ago. People who are involved in a PR would have to manually look through the changelog (after the release!) to spot possible mistakes or add missing information.
At the very least, the code at each release should include the current changelog (it was missing from 0.23.1)

Maybe it would be possible to update the changelog in an Unreleased section between releases (for example biweekly). Perhaps ping the included PRs to invite subscibers to double check. I know this adds some additional work and it's probably faster to do everything in one pece when there is a release. But this wouldn't need to be done by a core member.

I think is good to have a changelog branch to allow contributions to the changelog before releasing. It can be rebased onto master (or even receive merge from it) to signal up to which point was already revised.
That way is a process that can happen en a "weekly" basis and changes can be done incrementally.
I personally done that to keep track of where things were left.
Before releasing the changes can be squashed / grabbed and put in to master in to a single commit and the whole history of the changelog entry can be discarded (and reincarnate).
Another alternative is to flag issues / pr as "changelog:add", etc. and use that for the changelog but is more limited and solves only one part of the problem.

By the way, a lot of troubles with CHANGELOG merging can be solved by commiting this file:
echo CHANGELOG.md merge=union > .gitattributes
git add .gitattributes

The changelog process has somewhat evolved and seems to work. This can be closed.


Skip tests for specific context if precondition functions failed

Hi,
Is there any way to not execute tests in context if functions "once", "before" has failed for some reason?

I can add a configuration flag to enable that I believe.
Let me rephrase so that I make sure I understand what you want.
If at any point during running tests for a context, if the once or before functions fails, skip all remaining tests for that context.
Sound right?

Yes, that's exactly what we need. This will reduce failure investigation time, since in most cases test failures are caused by incomplete execution of "before" and "once".
"Configuration flag" sounds great. Please let me know when to expect this feature. Thanks in advance!

Looking at the code a failure in once should already fail the rest of the Suite.  I will test that this works.
There is also a configuration flag called failFast which if you set it it to true it will stop running tests after any test fails (including the before).  It will stop running all tests though, and not just tests for a specific context.
In its current state, the runner is a total mess and I need to refactor it.  I will take the time to do that today hopefully and get your feature in too.  It may take longer than I want and spill over a few days though.

You can download this now!
https://www.nuget.org/packages/canopy/0.9.46
Set this configuration to true
skipRemainingTestsInContextOnFailure <- true
Then any failure in once or before will skip the rest of the tests for that context.

Im trying to add this feature to my tests, if the test fails in once block skip the rest of the tests,  I am having a hard time changing the value of skipRemainingTestsInContextOnFailure  to true. Pls let me know if any changes are needed to the following code.
let all _ =
context "Executing Tests"

once (fun _ ->
start firefox
url "application.com"
let currentTitle = title()

if (currentTitle <> expectedTitle) then

// added failwith and tried
skipRemainingTestsInContextOnFailure <- true
//tried the full name canopy.configuration.skipRemainingTestsInContextOnFailure <- true
)
LoginTests()
ShoppingTest()

Its not compiling or its not working?
If its not working it must be because your currentTitle does equal your expected title.

It is compiling. No , current title is google and expected is my application. I put a breakpoint at let currentTitle = title () and navigate to google.com
When the condition is true , it is stepping into line number 184 in runner.fs

Ok I think I understand.
This flag is just a configuration setting, so if a test fails, it will skip any remaining tests in the current context.
You need to set it to true, then if a test fails it will work.
If there is a failure in the once code it will fail the suite also, you can see that here:
https://github.com/lefthandedgoat/canopy/blob/master/src/canopy/runner.fs#L205-L208
If you want your test to fail because in the once, your title is wrong, don't use an if statement, use an assertion like:
currentTitle === expectedTitle

ok will try that.

Got the exception "equality check failed" and stepped into and executed line no .111 in runner.fs and the following lines were not executed
reporter.testStart test.Id
fail ex test suite true <| safelyGetUrl()
reporter.testEnd test.Id
my code is
let all _ =
context "Executing Tests"
once (fun _ ->
start firefox
url "application.com"
let currentTitle = title()
currentTitle === expectedTitle

Its generally best to not run your tests in Visual Studio because the debugger will attach to any exceptions it thinks are un-handeled.
Try running the exe from console and it should work.

Okay, i will wait till I find a broken environment and test it.
Thank you .

My test environment was down today , Jenkins job will execute exe , and it didnt work still , all the tests i have were executed and reported failure.

I need to see your full test to help.

Pls let me know if I can reach you out via email.

lefthandedgoat gmail
On Tue, Aug 9, 2016 at 3:37 PM, danuma<EMAIL_ADDRESS>wrote:

Pls let me know if I can reach you out via email.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lefthandedgoat/canopy/issues/242#issuecomment-238683075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsQ6WQRY1zi4_LlsACU6c0e3sxdeYooks5qeOT5gaJpZM4HtrJp
.


Compress for multi http services

Hi, how to enable compress to multi-http-services sample?

Right now there is no built in middleware for compression with xitca-http so the only way is to write a similar one to what xitca-web offers https://github.com/HFQR/xitca-web/blob/main/web/src/middleware/compress.rs
In a code snippet form it can be like this:
*. http/1 service from the example:
fn_service(handler_h1)
    .enclosed_fn(compress) // add compression middleware here
    .enclosed(HttpServiceBuilder::h1())
    .enclosed(SocketConfig::new())
    .enclosed(Logger::default()),

*. sample middleware implementation:

use http_encoding::{encoder, Coder, ContentEncoding};
use futures_core::stream::Stream;

async fn compress<S, Ext>(service: &S, req: Request<Ext>) -> Result<Response<Coder<ResponseBody>>, S::Error>
where
    S: xitca_service::Service<Request<Ext>, Response = Response<ResponseBody>>
{
    // copy paste from xitca_web
    let mut encoding = ContentEncoding::from_headers(req.headers());
    let res = service.call(req).await?;

    match res.body().size_hint() {
        (low, Some(up)) if low == up && low < 64 => encoding = ContentEncoding::NoOp,
        (usize::MAX, Some(0)) => encoding = ContentEncoding::NoOp,
        _ => {}
    }

    Ok(encoder(res, encoding))
}


WIP. Update for Xcode 8 beta 6.

https://github.com/apple/swift-evolution/blob/b56c722ef4bc8ca8899606be06fb20936d6732e8/proposals/0025-scoped-access-level.md
https://github.com/apple/swift-evolution/blob/2989538daa1640cfa6a56f80b5c7599967af0905/proposals/0116-id-as-any.md
https://github.com/apple/swift-evolution/blob/a018af5890133f234a31c4568d43a52508d3f71c/proposals/0111-remove-arg-label-type-significance.md

There are still errors:
realm-cocoa/RealmSwift/LinkingObjects.swift:388:1: error: type 'LinkingObjects<T>' does not conform to protocol 'RealmCollection'
extension LinkingObjects : RealmCollection {
^
realm-cocoa/RealmSwift/RealmCollectionType.swift:360:10: note: protocol requires function 'addNotificationBlock(block:)' with type '((RealmCollectionChange<LinkingObjects<T>>) -> Void) -> NotificationToken'; do you want to add a stub?
    func addNotificationBlock(block: (RealmCollectionChange<Self>) -> Void) -> NotificationToken
         ^
realm-cocoa/RealmSwift/LinkingObjects.swift:381:17: note: candidate has non-matching type '<T> (block: ((RealmCollectionChange<LinkingObjects<T>>) -> Void)) -> NotificationToken' (aka '<τ_0_0> (block: (RealmCollectionChange<LinkingObjects<τ_0_0>>) -> ()) -> RLMNotificationToken')
    public func addNotificationBlock(block: ((RealmCollectionChange<LinkingObjects>) -> Void)) -> NotificationToken {
                ^
realm-cocoa/RealmSwift/RealmCollectionType.swift:363:10: note: protocol requires function '_addNotificationBlock(block:)' with type '((RealmCollectionChange<AnyRealmCollection<T>>) -> Void) -> NotificationToken'; do you want to add a stub?
    func _addNotificationBlock(block: (RealmCollectionChange<AnyRealmCollection<Element>>) -> Void) -> NotificationToken
         ^
realm-cocoa/RealmSwift/LinkingObjects.swift:416:17: note: candidate has non-matching type '<T> (block: (RealmCollectionChange<AnyRealmCollection<T>>) -> Void) -> NotificationToken' (aka '<τ_0_0> (block: (RealmCollectionChange<AnyRealmCollection<τ_0_0>>) -> ()) -> RLMNotificationToken')
    public func _addNotificationBlock(block: @escaping (RealmCollectionChange<AnyRealmCollection<T>>) -> Void) ->

I have no idea to solve it because it seems to be already conformed.

Thanks for the PR, @uny! We'll need you to accept our Contributor License Agreement before we can merge your contributions.
Cheers,
The robots and humans at Realm

Thanks for your contribution @uny! We've actually already started working on migrating to the newest Swift beta (https://github.com/realm/realm-cocoa/pull/3965), but I appreciate your help. :)

Thank you.


[feature] Build slsa-github-generator binaries from release tag

Update the release.yml workflow to use the previously released verison of slsa-github-generator so that released binaries are built with an actual release at a tag.
This will make it easier to verify our binaries with slsa-verifier v2.2.0+ and require less special cases for our binaries.

Currently slsa-verifier 2.2.0 will fail to verify older binaries
$ ./slsa-verifier-linux-amd64 verify-artifact --source-tag v1.5.0 --source-uri github.com/slsa-framework/slsa-github-generator --provenance-path slsa-builder-go-linux-amd64.intoto.jsonl slsa-builder-go-linux-amd64
Verified signature against tlog entry index 14306963 at URL: https://rekor.sigstore.dev/api/v1/log/entries/24296fb24b8ad77ab55bcc8d58cb6f92f82a9c7993bb4922f0999f885af8e9e3bbf5356b88349538
Verifying artifact slsa-builder-go-linux-amd64: FAILED: invalid ref: refs/heads/main: not of the form 'refs/tags/name'

FAILED: SLSA verification failed: invalid ref: refs/heads/main: not of the form 'refs/tags/name'

Given that we already update release.yml to reference the workflows by tag I wonder why the builder.id (job_workflow_ref) is at ref/heads/main rather than ref/tags/v1.5.0 in the provenance.
$ jq -r '.payload | @base64d' < slsa-builder-go-linux-amd64.intoto.jsonl  | jq '.predicate.builder.id'
"https://github.com/slsa-framework/slsa-github-generator/.github/workflows/builder_go_slsa3.yml@refs/heads/main"

It seems to be ok for the v1.6.0-rc.0 release. Did we not update the builder tags until after v1.5.0 was released? Or did we just mess up the past releases somehow.
$ jq -r '.payload | @base64d' < slsa-builder-go-linux-amd64.intoto.jsonl.1 | jq '.predicate.builder.id'
<EMAIL_ADDRESS>

It seems like we updated the RELEASE instructions to catch this in https://github.com/slsa-framework/slsa-github-generator/commit/139e60c6d4f4d00329d5d44c26e0ec534e3a1a1a#diff-2b1b69303b927a484e02c7fad9fc87d0d3ff0dc22ae1da0ecd0dc935d922a23cR375 which was after v1.5.0.
So this should be fixed in the next release. Will close after we can test that slsa-verifier v2.2.0 can verify binaries for the v1.6.0 release without SLSA_VERIFIER_TESTING being set.


Creating an app with:  npm create ionic-svelte-app@latest no longer includes any pwa code?  The src/lib folder is now empty when creating a new project.

Creating an app with:  npm create ionic-svelte-app@latest no longer includes any pwa code?  The src/lib folder is now empty when creating a new project.
The lib folders were removed by this commit on Feb 15:
https://github.com/Tommertom/svelte-ionic-app/commit/4e6e7fe24edaba793a3a493de94cf5896b93ff82

Hi
Yes I did not feel that should be part of what the package should distribute also because the vite pwa api can change. Next the vite pwa docs have better documented info on service workers and so on.
Happy to hear other thoughts...

You mean like adding a link in the closing comments?
Link to Vite PWA? https://github.com/vite-pwa/sveltekit

Yeah, I'd copy over the steps needed to set up the PWA and include it in your readme, and provide a link as well. :)

Feel like doing a PR on the README?

I created a branch and tried to push it, but I don't have access:
ERROR: Permission to Tommertom/svelte-ionic-app.git denied to burggraf.

You need to fork it and then create a change and then do a PR

Added a mention in the install script - add the end of it

Ok, I'm now revising this and when I create a new app with npm create ionic-svelte-app@latest and try to follow the instructions at https://github.com/vite-pwa/sveltekit, I'm lost.  I've spent several hours on this and just can't get it to work.  In your older build here, the default setup automatically set up a pwa with automatic app updating, and it was great.  How can we get back to that awesome setup?
Does anyone have some working pwa code using the latest SveltKit setup here (preferably that allows apps to work offline and auto-updates like the app used to)?

I tried to build and deploy the demo app in the source tree here, and it installs a service worker, but it doesn't work offline (and I'm not sure if it auto-updates either.)

I was able to get things working by studying this project:
https://github.com/vite-pwa/sveltekit/tree/main/examples/sveltekit-ts


feat: Update Tags CRUD API

SUMMARY

Updated API to allow users to create a Tag w/ description. Also user's can bulk tag resources from the new CRUD modal in the Tags ListView page.
Note: I did fix the onHide functionality that's not show in the video when the user completes
https://github.com/apache/superset/assets/27827808/c4face31-57f3-44e3-9a4e-3ad7cedf5e7d
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

So I've been looking for this "New Tag" button for a while now, but it doesn't seem to exist in the apache/superset:3.0.0 docker image.
Next to this, even though this PR was merged into master on August 25, it doesn't seem to exist in the source code of the upcoming 3.0.1rc1 release candidate either.
How can I go about enabling this?

Hi @jordibeen, you can test out the feature by turning on the TAGGING_SYSTEM feature flag in your config. It's still in a development/testing stage, so you may find it a little buggy until it's ready for GA, which will likely be around the 3.1 release.

Yes, the issue I mentioned above is with the TAGGING_SYSTEM feature flag already enabled.
Enabling this does give us the option to create and apply tags on a Chart (by editing the Chart Properties), but it doesn't add the "New Tag" button on the Tag ListView page.
We're looking for some kind of "Tag management" like in the video above, but our [superset-domain]/superset/tags page doesn't have all the functionalities that the video in this PR shows, such as the "New Tag" button in the top right. (We're on 3.0.0)
Even though this PR was merged into master on August 25, it doesn't seem to exist in the source code of the upcoming 3.0.1rc1 release candidate.
I guess my question is: which Superset version will contain this great new Tag ListView page?


fix using lines

@HumJ0218 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@HumJ0218 Thank you for signing the Contributor License Agreement!


Ergo: Replacement

Discussion 🗣
Currently all logic within a Accord Project (Cicero) template is executed as Ergo.
Given the niche nature of this language and the difficulty in finding OCaml/Coq Developers, there may be some benefit in allowing other languages (e.g. NodeJS, C#, Python, Rust, etc.) being used as target languages instead of or in addition to Ergo.
Context
Ergo is a domain specific language developed specifically for the Accord Project.  Ergo was developed using OCaml, Coq and Cert by @jeromesimeon.
Detailed Description
Although there are many design advantages in having a custom language dedicated to the Accord Project, the maintenance, support and ongoing development of the Ergo language is dependent on niche skills which are not readily available at scale within the developer community.
This restricts who can maintain and/or contribute to the Ergo codebase and slows the ongoing development of this language.
In addition, Ergo has a custom syntax that, although similar to other languages, is distinct and requires some effort for template authors to learn.  This introduces a barrier to entry for template authors wanting to create AP templates but are unfamiliar with the Ergo syntax.
The current Ergo implementation is incomplete and requires additional language constructs to be added in order for it to be fully useable by template authors.
However... there are some downsides to introducing generic target languages.
Due to their very nature, general purpose languages may provide too much flexibility w.r.t. language features which could produce undesirable effects during execution of template logic.
For example, Ergo is a functional language where every expression evaluates, and the code is restricted to executing only within the AP template.  General purposes languages can, potentially, execute or invoke executions beyond the template boundaries, if allowed to do so. Other general purpose languages (e.g. NodeJS) may pull in external libraries that could contain vulnerabilities.
In addition, some AP template functionality (e.g. Parse) is tightly coupled to Ergo/OCaml/Coq and would not be easily replicated using a general purpose language.
Ergo touches many different areas of the AP code base.  Therefore, replacing Ergo or allowing other languages to be targeted alongside Ergo is a non-trivial process which could require many person months of effort.
In summary....
We have the following options:

Keep Ergo - find additional contributors / maintainers who can step up ongoing support and maintenance of Ergo.
Replace Ergo - introduce support for other target languages and treat Ergo as legacy code.
Keep Ergo & target other languages - find additional contributors / maintainers who can keep Ergo alive and introduce support for other target languages.
Some other option* - whatever that may be.

TSC Notes:

Further development on Ergo is not expected
Alternative proposals to be sought through the TSC
@dselman to give an overview of existing Ergo integration points.

If I'm not late to the discussion: I want to access to this system with Python so option 3. If it has design advantages there is no point in discarding the whole language.

I would like to add that being able to compile to a memory-safe language/runtime can be a strong value proposition. Looking forward into the future (years, decades), we may find that applications and stacks vulnerable to things like buffer overflows are deprioritized by either legislation or industry best practice.

TSC Minutes
Ergo has been removed from Cicero ("template-archive" repo). Some small house-keeping to do.
Need documentation and exemplars for BYO runtime. @martinhalford prototyping with Rust.
Need to update documentation and marketing website. @martinhalford to lead.
Ergo repo archived.

TSC Minutes
Priority is to update public docs and the marketing website to reflect reality.
@dselman is willing to match investment from others, but needs to be driven by someone with demand for capabilities.


When using the nitro preset as 'node', the example in the documentation does not execute correctly.

Environment
Nuxt project info:

------------------------------
- Operating System: Linux
- Node Version:     v16.17.0
- Nuxt Version:     3.8.1
- CLI Version:      3.9.1
- Nitro Version:    2.7.2
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, nitro
- Runtime Modules:  -
- Build Modules:    -
------------------------------

Reproduction

Configuring nuxt.config

export default defineNuxtConfig({
  nitro: { preset: 'node' }
})

Creating an index.mjs server

import { createServer } from 'node:http'
import { handler } from './.output/server/index.mjs'

const server = createServer(handler)
server.listen(3000)

Compiling and starting the server

yarn build && node index.mjs

Reproduction Here
Describe the bug
Expected Result:
The server should start normally and execute the Vue program in the client side without issues.

Actual Result:
The server starts up correctly, but the Vue program in the client side fails to execute.

Additional context
Nuxt and Nitro are fantastic, and I really appreciate this community and the team's effort. However, I expected that following the Nuxt and Nitro documentation for setup would result in a successful execution. I would appreciate some assistance in troubleshooting this issue. Thank you.
https://nitro.unjs.io/deploy/runtimes/node#handler-advanced
Logs
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/index.ae8c31f5.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/entry.97d8de00.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-404.4a434e74.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/error-500.4b457395.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"
[Vue Router warn]: No match found for location with path "/_nuxt/vue.f36acd1f.5681e6db.js"

node-server is probably what you want.
node is, to quote from the docs:

... a more low-level preset that directly exports a function with (req, res) => {} signature usable for middleware and custom servers.

@danielroe thanks, enable serveStatic is suitcase for me. Maybe this related options should be notice on doc.


[AMBARI-23504] Pre-Upgrade Configuration Check for Kafka should only apply to HDP 2.6.5-> HDP 2.6.x (Not HDF) (dgrinenko)

What changes were proposed in this pull request?
Making pre-upgrade check to be fully optional and run as it supposed by instruction from upgrade packs
How was this patch tested?
live cluster

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1699/
Test FAILed.
Test FAILured.


unit_vector doesn't work as a parameter

The parser allows unit_vector to be a type, but we can't compile the generated C++ code.
We need to add tests for this.

Just need to add one test with unit_vector as a parameter in a non-syntax only test.

Actually, it "works" in 2.9.0 but makes a vector that is too short
library(rstan)
mc <- '
parameters { unit_vector[3] u;}
model {}
generated quantities { print("length of u = ", rows(u)); }
'
stan(model_code = mc,  chains = 1)

...
length of u = 2

Chain 1, Iteration: 2000 / 2000 [100%]  (Sampling)length of u = 2
#
#  Elapsed Time: 0.047789 seconds (Warm-up)
#                0.036342 seconds (Sampling)
#                0.084131 seconds (Total)
#
Inference for Stan model: unit_vector.
1 chains, each with iter=2000; warmup=1000; thin=1;
post-warmup draws per chain=1000, total post-warmup draws=1000.

      mean se_mean   sd  2.5%   25%   50%   75% 97.5% n_eff Rhat
u[1]  0.01    0.03 0.73 -1.00 -0.70  0.01  0.76  1.00   758    1
u[2]  0.02    0.03 0.69 -0.99 -0.65  0.02  0.71  1.00   722    1
u[3]  0.00    0.00 0.00  0.00  0.00  0.00  0.00  0.00  1000  NaN
lp__ -1.01    0.05 0.94 -3.30 -1.41 -0.77 -0.32 -0.02   339    1

Interestingly, the output is of length 3 (although the third value is a constant) but internally it thinks u is of length 2.


NVIDIA make generate_engines Error Code 4: Internal Error Network has dynamic or shape inputs

Run generate_engines
cmd  make generate_engines RUN_ARGS="--benchmarks=bert --scenarios=offline" will lead to the error Error Code 4: Internal Error (Network has dynamic or shape inputs, but no optimization profile has been defined.)

The detailed error is as follows:
(mlperf) user@mlperf-inference-user-x86_64:/work$ make generate_engines RUN_ARGS="--benchmarks=bert --scenarios=offline"
[2023-07-12 18:56:08,807 main.py:231 INFO] Detected system ID: KnownSystem.H100_PCIe_80GB_Custom
[2023-07-12 18:56:11,032 generate_engines.py:172 INFO] Building engines for bert benchmark in Offline scenario...
[2023-07-12 18:56:11,057 bert_var_seqlen.py:67 INFO] Using workspace size: 0
[07/12/2023-18:56:11] [TRT] [I] [MemUsageChange] Init CUDA: CPU +2, GPU +0, now: CPU 38, GPU 928 (MiB)
[07/12/2023-18:56:16] [TRT] [I] [MemUsageChange] Init builder kernel library: CPU +2981, GPU +750, now: CPU 3096, GPU 1680 (MiB)
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
[07/12/2023-18:56:18] [TRT] [I] Using default for use_int8_scale_max: true
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
...
[07/12/2023-18:56:18] [TRT] [W] Tensor DataType is determined at build time for tensors not marked as input or output.
[2023-07-12 18:56:18,733 bert_var_seqlen.py:215 INFO] Building ./build/engines/H100_PCIe_80GB_Custom/bert/Offline/bert-Offline-gpu-_S_384_B_0_P_0_vs.custom_k_99_MaxP.plan
[07/12/2023-18:56:18] [TRT] [E] 4: [network.cpp::validate::3036] Error Code 4: Internal Error (Network has dynamic or shape inputs, but no optimization profile has been defined.)
Process Process-1:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/work/code/actionhandler/base.py", line 189, in subprocess_target
    return self.action_handler.handle()
  File "/work/code/actionhandler/generate_engines.py", line 175, in handle
    total_engine_build_time += self.build_engine(job)
  File "/work/code/actionhandler/generate_engines.py", line 166, in build_engine
    builder.build_engines()
  File "/work/code/bert/tensorrt/bert_var_seqlen.py", line 231, in build_engines
    assert engine is not None, "Engine Build Failed!"
AssertionError: Engine Build Failed!

The system device id info is as follows:
I have already set the system id as H100_PCIe_80GB_Custom

(mlperf) user@mlperf-inference-user-x86_64:/work$  python3 -m scripts.custom_systems.add_custom_system
This script creates a custom system definition within the MLPerf Inference codebase that matches the
hardware specifications of the system that it is run on. The script then does the following:

    - Backs up NVIDIA's workload configuration files
    - Creates new workload configuration files (configs/<Benchmark name>/<Scenario>/__init__.py) with dummy values
        - The user should fill out these dummy values with the correct values

============= DETECTED SYSTEM ==============

SystemConfiguration:
    System ID (Optional Alias): H100_PCIe_80GB_Custom
    CPUConfiguration:
        2x CPU (CPUArchitecture.x86_64): Intel(R) Xeon(R) Platinum 8480+
            56 Cores, 2 Threads/Core
    MemoryConfiguration: 528.08 GB (Matching Tolerance: 0.05)
    AcceleratorConfiguration:
        2x GPU (0x233110DE): NVIDIA H100 PCIe
            AcceleratorType: Discrete
            SM Compute Capability: 90
            Memory Capacity: 79.65 GiB
            Max Power Limit: 310.0 W
    NUMA Config String: &

Thanks for any hint of this issue.

Here, "B0" means batch size used is 0 which is invalid.
We are supporting nvidia implementation inside CM and have currently tested on L4, T4, A100 and RTX 4090. We'll be very happy to assist you if you can test it on H100. Here, are the instructions: https://github.com/mlcommons/ck/blob/master/docs/mlperf/inference/bert/README_nvidia.md and public discord channel for any queries.


No loader on chat room

Description
Initially the chat room appears as a blank page. I want to add a loader to it until it fetches data.
Steps to reproduce
Go to community chat
It will appear blank until the data id fetched.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

right, you can work on this! :)

Btw about that older loader issue, I think we can add a shimmer effect for the loading posts, how'd that be??

Yes I think they are fantastic. Can I create a issue for it?

Yes I think they are fantastic. Can I create a issue for it?

I think there's already an issue for loader, maybe you can edit it to include this. If we work on this, we wont need those issue

Yes there is issue for loader but I think that is for the common loader and shimmer effect would be specific to post


Installation instructions missing

Its too difficult to get up and running. Perhaps installation instructions or an automated script

Update Passwords on private repo with the 2 instabug passwords.


bug: Tattoo not workin' properly

Change this active thingy when its related section comes at least 25 - 40%.
Current behaviour: it changes even when its related section is not in the view.
Tattooing not correct :\

Fixed :D


⚠ Bofrost.be has degraded performance

In 57a971a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1112 ms

Resolved: Bofrost.be performance has improved in 3668a6a after 10 minutes.


quote value in rabbitmq trigger example

The current documentation suggests that the value field in the rabbitmq trigger is an integer, which can lead to confusion.

@PaulFarver thanks! could you please update the other versions of this doc as well? (in content/docs/*)

@zroubalik thanks for the quick reply. I've updated the 2.3 version as well. :)


Bug: Unexpected  MissingQueryParamRejection(QueueUrl) in SQS SendMessage when using a context path

When setting node-address.context-path to a non-empty value, calls to SqsClient.sendMessage stop working.
Issue disappears if  node-address.context-path = ""
Calls to SqsClient.getQueueUrl still work, so I think the issue is in the way QueueDirectives.scala#L46 is parsing the request.
Info from some debug logging:
Starting ElasticMQ server on http://localhost:34998/context
Slf4jLogger started
Started SQS rest server, bind address <IP_ADDRESS>:34998, visible server address http://localhost:34998/context
Started statistics rest server, bind address <IP_ADDRESS>:34999
Creating queue QueueData(test-queue-1,MillisVisibilityTimeout(30000),PT0S,PT0S,2021-12-08T13:03:10.252Z,2021-12-08T13:03:10.252Z,None,false,false,None,None,Map())
Dec 08, 2021 1:03:12 PM TestClientClass getQueueUrlFromSqs
DEBUG: GetQueueUrlRequest(QueueName=test-queue-1)
Dec 08, 2021 1:03:13 PM TestClientClass getQueueUrlFromSqs
DEBUG: GetQueueUrlResponse(QueueUrl=http://localhost:34998/context/000000000000/test-queue-1)
Dec 08, 2021 1:03:13 PM TestClientClass addMessage
DEBUG: SendMessageRequest(QueueUrl=http://localhost:34998/context/000000000000/test-queue-1, MessageBody=This is the message)
Dec 08, 2021 1:03:13 PM TestClientClass addMessage
DEBUG: software.amazon.awssdk.services.sqs.model.SqsException: Invalid request: MissingQueryParamRejection(QueueName), MissingQueryParamRejection(QueueUrl); see the SQS docs. (Service: Sqs, Status Code: 400, Request ID: 00000000-0000-0000-0000-000000000000, Extended Request ID: null)

Issue occurred using on:

Java AdoptOpenJDK 1.8.0_292 Hotspot
Maven 3.6.3
org.elasticmq > elasticmq-server_2.13 > version 1.3.3

Much appreciated @micossow! 😄

you are welcome, it's fixed in v1.3.6 :)


chore(deps): update xunit to v3

This change is part of the following stack:

#61 ◀

Change managed by git-spice.


Fs Resource Create and Edge Expansion

This task is meant to satisfy the Fs construct's expansion.
To do so we will:

Add Create Methods for Each Resource necessary

[x] S3Bucket

Add Configure Method For Each Resource Necessary

[x] S3Bucket

Add the expand method for an fs construct and our internal resource construct
My initial thought is that this will connect an edge from the method to their corresponding lambda
Add EdgeKB data

[ ] LambdaFunction -> S3Bucket
[ ] IamPolicy -> S3Bucket

DoD:

All Methods above are written and have unit tests
ts-cloudfs (or any cloudfs) sample app is able to pass tests ts-cloudfs

Similarly, removing the S3BucketPolicy — we need that for static files (#607), but not for FS


Update docfx.json

@Taojunshen can you provide any background or details here on why you're proposing this change?
Our plan is to move all content here to our new https://github.com/MicrosoftDocs/CommunityToolkit repo, is this to align to the ms-technology tag used there?


Update screeenshots

Hello,
Please update the screenshots to reflect the latest version of the portal, it took me some time to find the settings for the portal in the section "Disable access to the public endpoint".
Thank you for your great documentation, it has helped so me many times!
Regards
Åke S.

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

ID: 87a52dac-048f-2a4d-b857-cb91b9534cf5
Version Independent ID: a1e64a4a-dcfb-eac3-4851-366dd8893428
Content: Configuring Azure Files network endpoints
Content Source: articles/storage/files/storage-files-networking-endpoints.md
Service: storage
Sub-service: files
GitHub Login: @roygara
Microsoft Alias: rogarana

@AkeSamuelson Thanks for the question! We are investigating and will update you shortly.

@AkeSamuelson Thanks for the question! We are investigating and will update you shortly.

@AkeSamuelson  Firstly, apologies for the delay in responding here! Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@AkeSamuelson  Firstly, apologies for the delay in responding here! Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Hello @AkeSamuelson , thanks for bringing this to our attention, we appreciate it! I've gone ahead and updated the screenshots for the storage account networking. Those updates should be live sometime tomorrow.
I'll go ahead and close this out, accordingly.
Again, thanks for pointing this out, and helping us improve our documentation. :)
#please-close

Hello @AkeSamuelson , thanks for bringing this to our attention, we appreciate it! I've gone ahead and updated the screenshots for the storage account networking. Those updates should be live sometime tomorrow.
I'll go ahead and close this out, accordingly.
Again, thanks for pointing this out, and helping us improve our documentation. :)
#please-close


WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.

In the process of starting the service for the first time, this kind of error is reported.
What should I do?
The following is the full text of the whole error message.
PS D:\KKK_usual tools\ChatFiles-main> docker compose up
[+] Running 2/0

Container chatfiles     Created                                                                                0.0s
Container chatfiles-ui  Created                                                                                0.0s
Attaching to chatfiles, chatfiles-ui
chatfiles     | None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
chatfiles-ui  |
chatfiles-ui  | ><EMAIL_ADDRESS>start
chatfiles-ui  | > next start
chatfiles-ui  |
chatfiles-ui  | ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
chatfiles     | WARNING:llama_index.llm_predictor.base:Unknown max input size for gpt-3.5-turbo, using defaults.
chatfiles     |  * Serving Flask app 'server'
chatfiles     |  * Debug mode: off
chatfiles     | INFO:werkzeug:WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
chatfiles     |  * Running on all addresses (<IP_ADDRESS>)
chatfiles     |  * Running on http://<IP_ADDRESS>:5000
chatfiles     |  * Running on http://<IP_ADDRESS>:5000
chatfiles     | INFO:werkzeug:Press CTRL+C to quit

It is a warning, not an error, you can ignore it.


ML 1.5 : Probability Distributions (Gaussian, Standard, Poisson) (V)

Description 📜
Fixes #609

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Machine Learning

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@abhisheks008 @Isha307

Merged @parvatijay2901


Fix demo build status badge in README

I'm not sure these changes are correct, but as-is the two AppVeyor 'build status' badges in the README are pointing to the same (AppVeyor) project. Based on the markup in the README file itself, I'm guessing one of the badges was meant to reference the build status of the demo project.
But, even with these changes, there's no visual distinction between the two build status badges. If you have an idea how that should be affected, I'll take a stab at it.

Good catch @kenny-evitt and thank you for stepping in :)
Check this out https://www.appveyor.com/blog/2014/11/26/customizing-text-of-build-status-badges/
We could call one "master" and the other "demo"

@kblok Thanks for the project!
I added the custom text to the badges just now.

Your welcome @kenny-evitt! Thank you for jumping in!

@kblok Need anything else for this before merging?


⚠ Secret Website 3 has degraded performance

In 8d3800b, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 19848 ms

Resolved: Secret Website 3 performance has improved in 7e944b9.


How to configure intellisense in VS Code (and exclude the default js definitions?)

I have duktape embedded into my application, and all works nicely.
I wish to be able to point users at a pre-configured VS Code workspace folder, which will include intellisense set up for the duktape defined globals, and my own defined application bindings.
Through a bit of trial and error, and lots of googling, I've got a typings folder in my workspace root, containing the .d.ts file from https://github.com/kimushu/duktape-types/blob/master/index.d.ts and my own application.d.ts definition file.
This appears to work as far as I can tell (I get Intellisense autocomplete for Duktape globals) but I also get all of the node.js globals pulled in by default too - this wouldn't be a huge problem other than there are name collisions between node's module names and the modules I define within my own application (and node's ones seem to win out over my own)
So does anyone know how to tell VS code "only use these specific files for intellisense lookup"?

@benjymous I don't have an answer, unfortunately, but a related question: would it make sense to have a Wiki page on configuring Visual Studio? If so, what issues should it cover besides autocomplete? I ask because VS Code questions have come up a number of times, so maybe it would be useful to document.

@svaarala Just for the record in case you weren't aware, Visual Studio and VS Code are very different - VS is a huge IDE and is Windows-only while the latter is a cross-platform pluggable Electron-based text editor (albeit probably powerful enough to be an IDE).

@fatcerberus Oops, I'm aware of that, meant Visual Studio Code above.
I'll add at least a placeholder: https://github.com/svaarala/duktape-wiki/pull/201, as VS Code autocompletion has been asked several times.

Okay, just making sure you knew :)

@svaarala absolutely - I'd be happy to document where I've got to so far!


Adds support for Gitter.IM

Create our own channel in Gitter.IM

Done!
We are now in: https://gitter.im/mono/HapSharp


Issue Calculating "doji" without enough candles.

Issue
Versions:
Python: 3.9.10
pandas_ta: 0.3.14b0 (git install)
TA-Lib: 0.4.24
ta-lib-config:
Error Message
2022-02-17 14:12:31,968 | ERROR | base_events:asyncio:default_exception_handler:1738  | Exception in callback TaskWrapper.on_task_done(<Task finishe...bute 'name'")>)
handle: <Handle TaskWrapper.on_task_done(<Task finishe...bute 'name'")>)>
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/libraries/cm_utils/cm_utils/utils/async_utils.py", line 27, in on_task_done
    fut.result()
  File "/libraries/cm_brokers/cm_brokers/backtester/source.py", line 200, in _stream_ticker
    await callback(tick)
  File "/app/service.py", line 104, in process_ticker_updates
    await self.create_indicators(ticker_update.id)
  File "/app/service.py", line 128, in create_indicators
    self.markets[market].candles.ta.cdl_pattern(name=["dojistar", "doji"], append=True)
  File "/usr/local/lib/python3.9/site-packages/pandas_ta/core.py", line 874, in cdl_pattern
    result = cdl_pattern(open_=open_, high=high, low=low, close=close, name=name, offset=offset, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pandas_ta/candles/cdl_pattern.py", line 57, in cdl_pattern
    result[pattern_result.name] = pattern_result
AttributeError: 'NoneType' object has no attribute 'name'

Describe the bug
When attempting to calculate the "Doji" indicator i get that error message. This does NOT happen when calling "dojistar" it appears to be an issue when calling the following:
# Patterns that implemented in pandas-ta
    pta_patterns = {
        "doji": cdl_doji, "inside": cdl_inside,
    }

I get the same error when calling strategy.all, however not tracked that down any further then this, or confirmed same issue, however very likely. I am building up the dataseries as i get live data, and therefore my series starts with 1 candle row as I add more, however each time i add a row i re-calculate the indicators.
Tracked down
So i wanted to avoid creating an error as the issue, so after I stepped through my code during the doji creation at:
57: result[pattern_result.name] = pattern_result

I found that the candles/cdl_doji.py will return None if the length is considered to short less than (10) as each value (open,high..) is passed to verify_series which will overwrite each one with None if less then the length.
if open_ is None or high is None or low is None or close is None:
        return

This in turn makes pattern_result a None value and of course None has no attributes.
To Reproduce
import pandas_ta as ta
import pandas as pd

dict_data = {
    "open": {
        pd.Timestamp("2021-11-03 14:00:00", freq="10S"): 15982.7,
        pd.Timestamp("2021-11-03 14:00:10", freq="10S"): 15984.2,
        pd.Timestamp("2021-11-03 14:00:20", freq="10S"): 15984.0,
    },
    "high": {
        pd.Timestamp("2021-11-03 14:00:00", freq="10S"): 15986.4,
        pd.Timestamp("2021-11-03 14:00:10", freq="10S"): 15986.0,
        pd.Timestamp("2021-11-03 14:00:20", freq="10S"): 15985.5,
    },
    "low": {
        pd.Timestamp("2021-11-03 14:00:00", freq="10S"): 15982.2,
        pd.Timestamp("2021-11-03 14:00:10", freq="10S"): 15982.1,
        pd.Timestamp("2021-11-03 14:00:20", freq="10S"): 15977.2,
    },
    "close": {
        pd.Timestamp("2021-11-03 14:00:00", freq="10S"): 15984.5,
        pd.Timestamp("2021-11-03 14:00:10", freq="10S"): 15983.2,
        pd.Timestamp("2021-11-03 14:00:20", freq="10S"): 15977.2,
    },
    "volume": {
        pd.Timestamp("2021-11-03 14:00:00", freq="10S"): 323,
        pd.Timestamp("2021-11-03 14:00:10", freq="10S"): 210,
        pd.Timestamp("2021-11-03 14:00:20", freq="10S"): 433,
    },
}

new = {
    "open": {
        pd.Timestamp("2021-11-03 14:00:30", freq="10S"): 15966.1,
    },
    "high": {
        pd.Timestamp("2021-11-03 14:00:30", freq="10S"): 15967.5,
    },
    "low": {
        pd.Timestamp("2021-11-03 14:00:30", freq="10S"): 15966.1,
    },
    "close": {
        pd.Timestamp("2021-11-03 14:00:30", freq="10S"): 15966.5,
    },
    "volume": {
        pd.Timestamp("2021-11-03 14:00:30", freq="10S"): 29,
    },
}

def candle_compress_dataframe(data: pd.DataFrame, frame: str = "10S"):
    """
    Frame is timeframe, Hours(H), Minutes(T), Seconds(S):
    E.G 1T = 1 min | 10S = 10 seconds
    """
    ohlc_dict = {
        "open": "first",
        "high": "max",
        "low": "min",
        "close": "last",
        "volume": "sum",
    }

    for col in data.columns:
        if col not in ohlc_dict.keys():
            ohlc_dict[col] = "last"

    data = data.resample(frame, closed="left", label="left").apply(ohlc_dict)
    return data

df = pd.DataFrame.from_dict(dict_data)

df = pd.concat([df, pd.DataFrame.from_dict(new)], sort=False)
df = candle_compress_dataframe(df)
df.ta.cdl_pattern(name=["dojistar", "doji"], append=True)

print(df)

Expected behavior
Doji indicator is added as 0
Additional context
I spent a good day googling and debug this unsure the issue, could find no references to this error. I ended up stepping through to find the cause. So glad i did.

Thanks for the reply! This makes sense, I get the change not wanting to create invalid data if length is too low.
Im not suggesting removing the length check.
    if open_ is None or high is None or low is None or close is None:
        return

However if the  function cdl_doji called at pta_patterns[n] (in below snippet) can return None, then the function cdl_pattern shouldn't attempt to access an attribute it, which causes the exception.
if n in pta_patterns:
            pattern_result = pta_patterns[n](
                open_, high, low, close, offset=offset, scalar=scalar, **kwargs
            )
            result[pattern_result.name] = pattern_result

A possible solution to stopping people running into this exception without causing indicators is to simply check the return type prior to attempting to access the attribute:
if n in pta_patterns:
            pattern_result = pta_patterns[n](
                open_, high, low, close, offset=offset, scalar=scalar, **kwargs
            )
            if not isinstance(pattern_result,Series):
                continue
            result[pattern_result.name] = pattern_result

Thanks for replying so quick!

Hello @MerlinR,
Some updates to development branch this past month should handle and DataFrame size of at least 1 row now.
$ pip install -U git+https://github.com/twopirllc/pandas-ta.git@development

If you could give it a test and let me know what you think, that would be great!
Thanks,
KJ

Hey @twopirllc
Appoligies for LONG delay, can confirm this appears to be resolved.
Thanks for the hard work!


[Java] FlightSQL Java JDBC Driver JAR includes unshaded SLF4J 1.x class files

Describe the bug, including details regarding any error messages, version, and platform.
Arrow 11.0.0, creating a Gradle/Clojure deps.edn project (but assume same's true for other dependency managers) with both org.apache.arrow:flight-sql:11.0.0 and org.slf4j:slf4j-api:2.0.6 dependencies, I get the follow warnings:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

This is an SLF4J 1.x error (2.x uses service locators instead) which implies the class files in the FSQL JAR are taking preference over the 2.x ones - removing the FSQL dependency removes this warning. (I have logback 1.4.5 which correctly hooks into 2.x when 2.x is available). This prevents me from using SLF4J 2.x if the FSQL JAR happens to be higher in my classpath. I can obviously try to ensure that my version of SLF4J takes preference, but these things are notoriously fickle.
Related: https://github.com/apache/arrow/issues/22498. Not suggesting Arrow abstracts over it, but if the classes can't be renamed like the others, maybe we could include it as a standard dependency that can then be overridden, rather than shipping class files in the JAR?
(I may be missing something obvious, please do tell me to go look on StackOverflow if so :slightly_smiling_face:)
Component(s)
Java

I'd also be fine with FSQL bumping to 2.x, but I suspect others might not be :smile:

CC @lwhite1, @davisusanibar maybe we can shade after all? I think we don't want the driver JAR's logging interfering with an application's logging (but, we still do want to have it configurable, somehow)

The only workaround for me is manually removing package org.slf4j from jar. Any other ideas?

@davisusanibar @vibhatha

I will take a look @lidavidm


Setup does not install shared object

Running the installation routine on Linux does install all python files from top level but not the embedded folder structure libs/linux/*.so
So the library is finally not present and module fails to load the same.
Same can be observed in microservice-base with MicroserviceManagerGUI files. Also there all embedded file structures are not correctly copied

Hi @milanac030988 ,
please look into this for 0.13.0
Thank you,
Thomas

Ready, but not yet integrated in 0.13.0

Hi @milanac030988 ,
what is the status of this issue?
Thank you,
Thomas

Hello @test-fullautomation ,
Fixed by https://github.com/test-fullautomation/python-microservice-cleware-switch/pull/19
Thanks,
Cuong


level-name matching default

The default for level-name matching is wild-cards, but the dropdown incorrectly states that the default is to do no generic matching

Fixed by commit 15dc73f397414582c6e5c01ab9c7122ad0a8113a
This is a UI issue and cannot be assessed with automated testing.


ls-qpack-rs" requires a specific environment. When I try to use your project and build it with the MSVC compiler, I encounter an error: "error: failed to run custom build command for ls-qpack-sys v0.1.1 (https://github.com/BiagioFesta/ls-qpack-rs#866e740f)

Can you please attach the entire error log?

Checking libc v0.2.144
Compiling bindgen v0.59.2
Compiling ls-qpack-sys v0.1.1 (https://github.com/BiagioFesta/ls-qpack-rs#866e740f)
error: failed to run custom build command for ls-qpack-sys v0.1.1 (https://github.com/BiagioFesta/ls-qpack-rs#866e740f)
error: failed to run custom build command for ls-qpack-sys v0.1.1 (https://github.com/BiagioFesta/ls-qpack-rs#866e740f)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully: E:\untitled1\target\debug\build\ls-qpack-sys-ced565158fd145b6\build-script-build (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn't find any valid shared libraries matching: ['clang.dll', 'libclang.dll'], set the LIBCLANG_PATH environment variable to a path where one of these files can be found (invalid: [])"', D:\Rust-1.69\registry\src\mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd\bindgen-0.59.2\src/lib.rs:2144:31
stack backtrace:
0: std::panicking::begin_panic_handler
at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library\std\src\panicking.rs:579
1: core::panicking::panic_fmt
at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library\core\src\panicking.rs:64
2: core::result::unwrap_failed
at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library\core\src\result.rs:1750
3: core::result::Result<T,E>::expect
4: core::ops::function::FnOnce::call_once
5: lazy_static::lazy::Lazy::get::{{closure}}
6: std::sync::once::Once::call_once::{{closure}}
7: std::sys_common::once::queue::Once::call
at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library\std\src\sys_common\once\queue.rs:183
8: std::sync::once::Once::call_once
9: <bindgen::ensure_libclang_is_loaded::LIBCLANG as core::ops::deref::Deref>::deref
10: <bindgen::BindgenOptions as core::default::Default>::default
11: <bindgen::BindgenOptions as core::default::Default>::default
12: bindgen::Builder::generate
13: std::io::IoSlice::advance_slices
14: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.

The relevant part is here:
 thread 'main' panicked at 'Unable to find libclang: "couldn't find any valid shared libraries matching: ['clang.dll', 'libclang.dll'],

It seems that libclang is not installed in the system where you are building the library.
libclang is provided by the LLVM project.
Try to install LLVM on Windows and try again.

There are several ways to install LLVM on Windows.
For some versions, the LLVM Github repository already provides installer for windows, for instance the version 9.0.0:
https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1 (LLVM-9.0.1-win64.exe).
Of course if you are able to install a newer version is even better.

error: failed to run custom build command for ls-qpack-sys v0.1.1
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully: C:\Users\redoriental\Downloads\test2\target\debug\build\ls-qpack-sys-ac765e8bd384709e\build-script-build (exit code: 101)
--- stdout
CMAKE_TOOLCHAIN_FILE_x86_64-pc-windows-msvc = None
CMAKE_TOOLCHAIN_FILE_x86_64_pc_windows_msvc = None
HOST_CMAKE_TOOLCHAIN_FILE = None
CMAKE_TOOLCHAIN_FILE = None
CMAKE_GENERATOR_x86_64-pc-windows-msvc = None
CMAKE_GENERATOR_x86_64_pc_windows_msvc = None
HOST_CMAKE_GENERATOR = None
CMAKE_GENERATOR = None
CMAKE_PREFIX_PATH_x86_64-pc-windows-msvc = None
CMAKE_PREFIX_PATH_x86_64_pc_windows_msvc = None
HOST_CMAKE_PREFIX_PATH = None
CMAKE_PREFIX_PATH = None
CMAKE_x86_64-pc-windows-msvc = None
CMAKE_x86_64_pc_windows_msvc = None
HOST_CMAKE = None
CMAKE = None
running: "cmake" "D:\Rust-1.69\registry\src\mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd\ls-qpack-sys-0.1.1\deps/ls-qpack" "-G" "Visual Studio 17 2022" "-Thost=x64" "-Ax64" "-DLSQPACK_BIN=OFF" "-DCMAKE_INSTALL_PREFIX=C:\Users\redoriental\Downloads\test2\target\debug\build\ls-qpack-sys-ce5b6b6e2b0feb19\out" "-DCMAKE_C_FLAGS= -nologo -MD -Brepro" "-DCMAKE_C_FLAGS_DEBUG= -nologo -MD -Brepro" "-DCMAKE_CXX_FLAGS= -nologo -MD -Brepro" "-DCMAKE_CXX_FLAGS_DEBUG= -nologo -MD -Brepro" "-DCMAKE_ASM_FLAGS= -nologo -MD -Brepro" "-DCMAKE_ASM_FLAGS_DEBUG= -nologo -MD -Brepro" "-DCMAKE_BUILD_TYPE=Debug"
-- Compiler flags:  -nologo -MD -Brepro
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/build
running: "cmake" "--build" "." "--target" "install" "--config" "Debug" "--parallel" "8"
MSBuild version 17.3.1+2badb37d1 for .NET Framework
ls-qpack.vcxproj -> C:\Users\redoriental\Downloads\test2\target\debug\build\ls-qpack-sys-ce5b6b6e2b0feb19\out\build\Debug\ls-qpack.lib
-- Install configuration: "Debug"
-- Up-to-date: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/lib/ls-qpack.lib
-- Up-to-date: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/include/lsqpack.h
-- Up-to-date: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/include/lsxpack_header.h
-- Up-to-date: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/include/sys
-- Up-to-date: C:/Users/redoriental/Downloads/test2/target/debug/build/ls-qpack-sys-ce5b6b6e2b0feb19/out/include/sys/queue.h
cargo:root=C:\Users\redoriental\Downloads\test2\target\debug\build\ls-qpack-sys-ce5b6b6e2b0feb19\out
cargo:rustc-link-search=native=C:\Users\redoriental\Downloads\test2\target\debug\build\ls-qpack-sys-ce5b6b6e2b0feb19\out\lib
cargo:rustc-link-lib=static=ls-qpack
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: LexError { span: Span }', D:\Rust-1.69\registry\src\mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd\bindgen-0.59.2\src\codegen\mod.rs:3640:22
stack backtrace:
0: std::panicking::begin_panic_handler
at /rustc/398fa2187c88de46c13c142f600064483a563c86/library\std\src\panicking.rs:593
1: core::panicking::panic_fmt
at /rustc/398fa2187c88de46c13c142f600064483a563c86/library\core\src\panicking.rs:67
2: core::result::unwrap_failed
at /rustc/398fa2187c88de46c13c142f600064483a563c86/library\core\src\result.rs:1651
3: core::result::Result<T,E>::unwrap
4: <bindgen::ir::ty::Type as bindgen::codegen::TryToRustTy>::try_to_rust_ty
5: <bindgen::ir::item::Item as bindgen::codegen::TryToRustTy>::try_to_rust_ty
6: ::try_to_rust_ty
7: <bindgen::ir::ty::Type as bindgen::codegen::TryToRustTy>::try_to_rust_ty
8: <bindgen::ir::item::Item as bindgen::codegen::TryToRustTy>::try_to_rust_ty
9: ::try_to_rust_ty
10: ::to_rust_ty_or_opaque
11: <bindgen::ir::comp::FieldData as bindgen::codegen::FieldCodegen>::codegen
12: <bindgen::ir::comp::Field as bindgen::codegen::FieldCodegen>::codegen
13: <bindgen::ir::comp::CompInfo as bindgen::codegen::CodeGenerator>::codegen
14: <bindgen::ir::ty::Type as bindgen::codegen::CodeGenerator>::codegen
15: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
16: <bindgen::ir::module::Module as bindgen::codegen::CodeGenerator>::codegen::{{closure}}
17: <bindgen::ir::module::Module as bindgen::codegen::CodeGenerator>::codegen
18: <bindgen::ir::item::Item as bindgen::codegen::CodeGenerator>::codegen
19: bindgen::codegen::codegen::{{closure}}
20: bindgen::ir::context::BindgenContext::gen
21: bindgen::codegen::codegen
22: <bindgen::BindgenOptions as core::default::Default>::default
23: bindgen::Builder::generate
24: std::io::IoSlice::advance_slices
25: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
I never thought I would get stuck on installing dependencies.

If I can't use ls-qpack, I won't be able to use your wtransport. I want to know what other dependencies I need to install in order to successfully build ls-qpack. My Rust compiler is capable of compiling the quiche library.

Your wtransport project is excellent, and I don't want to miss the opportunity to use it.

TypeKind::Enum(..) => {
let path = item.namespace_aware_canonical_path(ctx);
let path = proc_macro2::TokenStream::from_str(&path.join("::"))
.unwrap(); //error
Ok(quote!(#path))
}

I understand.
Unfortunately, the error you are facing is not totally clear at the moment. It seems it comes from a dependency of this project, that is, bindgen.
This crate (i.e., ls-qpack-rs) depends on its C-version and bindgen is the rust way to generate C-FFI.
Unfortunately it is harder to deal with dependencies in Windows I guess. However, I built this crate in Windows without any problem by just ensuring to had installed:

Windows C compiler and runtimes (Windows Visual Studio)
Rust windows toolchain (via rustup)
LLVM (I've tested LLVM 9.0.1)
CMake

And that is.
Can you please try to provide to me versions of such tools so I can try to reproduce and better understad why it is not building on your environment?

From the linked issue it seems it was indeed and env issue. I am going to close this


Enable GitHub Discussions for this repo

https://github.com/features/discussions
https://docs.github.com/en/discussions/quickstart
https://resources.github.com/devops/process/planning/discussions/
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository

Okay, discussions are now enabled.


Selectively running stacks in debug mode

Would it be possible to selectively run specific starts in debug mode using 'sst start'? Allowing this would be useful for those apps that have a lot of stacks. You might want to look at a specific stack for debugging and not have all the noise of other lambda's logging to the console.

This became a blocker for us as well, so we implemented a tiny solution where you configure each lambda to be enabled or disabled for live lambda via an uncommitted local config file. We called it .lambda-config.local.yml and then when defining the sst.Function we call a helper utility to check what's in the config file: enableLiveDev: isLambdaLiveDevEnabled(id) by passing it the ID of the construct.
This had the following benefits for us:

When debugging integration tests we could only see the logs of the thing we're looking at rather than all our event handler picking up other events in the system.
sst deploy became much quicker after a start.

The selectively starting stacks is also a good idea, but it depends how people have their stacks structured.
The config file looks like this:
defaults:
  liveDev: false
lambdas:
  GraphqlApi:
    liveDev: true
  EventHandler:
    liveDev: false

And the code behind isLambdaLiveDevEnabled is:
import fs from 'fs';
import yaml from 'js-yaml';
import { z } from 'zod';

/**
 * Determines based on a local config file of: .local-lambda-config.yml if the lambda should be live
 * or not.
 * SST by default guarantees that deployed functions are never live (i.e. pnpm run deploy)
 */
export function isLambdaLiveDevEnabled(functionName: string): boolean {
  const lambdaConfig = loadLambdaConfig(functionName);
  return lambdaConfig.liveDev;
}

const FILE_NAME = '.lambda-config.local.yml';
const CONFIG_FILE_LOCATION_RELATIVE_TO_ROOT = `./${FILE_NAME}`;
let lambdaConfigFileCache: LambdaConfigFile | null = null;

const LambdaConfig = z.object({
  liveDev: z.boolean().optional().default(true),
});

export type LambdaConfig = z.infer<typeof LambdaConfig>;

const LambdaConfigFile = z.object({
  defaults: LambdaConfig,
  lambdas: z.record(z.union([LambdaConfig, z.undefined()])).optional(),
});

type LambdaConfigFile = z.infer<typeof LambdaConfigFile>;

export function loadLambdaConfig(functionName: string): LambdaConfig {
  if (lambdaConfigFileCache === null) {
    lambdaConfigFileCache = parseConfigFile();
  }
  const config = lambdaConfigFileCache.lambdas
    ? lambdaConfigFileCache.lambdas[functionName]
    : lambdaConfigFileCache.defaults;
  return config !== undefined ? config : lambdaConfigFileCache.defaults;
}

const defaultIfFileMissing: LambdaConfigFile = {
  defaults: {
    // By default sst enables live dev
    liveDev: true,
  },
};

function parseConfigFile(): LambdaConfigFile {
  if (!fs.existsSync(CONFIG_FILE_LOCATION_RELATIVE_TO_ROOT)) {
    console.log(
      `${FILE_NAME} doesn't exist, using defaults: ${JSON.stringify(defaultIfFileMissing)}`
    );
    return defaultIfFileMissing;
  }
  const yamlFile = yaml.load(fs.readFileSync(CONFIG_FILE_LOCATION_RELATIVE_TO_ROOT).toString());
  const lambdaConfigFileResult = LambdaConfigFile.safeParse(yamlFile);
  if (!lambdaConfigFileResult.success) {
    throw new Error(
      `Failed to parse config file ${FILE_NAME}: ${JSON.stringify(
        lambdaConfigFileResult.error,
        null,
        2
      )}`
    );
  }
  return lambdaConfigFileResult.data;
}

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble