feat: added lifecycle color-coded text

Description
This PR adds a component named LifeCycle which provides color-coded text to Lifecycle terms. It takes 3 keywords and outputs the text in a specific color, according to the keyword added. Till now, 3 keywords have been added. They are: Deprecated, Required and Optional.
Related issue(s)
Resolves #592

@iambp WIll you please go through the preview link and check whether it is placed at the right positions?

@akshatnema the background colors are still not visible

@imabp Now, the background colors are visible. There is a slight change in the color. Hope it doesn't matter to you. Please review it.

My recommendation is that you split it into 3 components: Deprecated, Required, and Optional

@fmvilas Yepp, I have changed it to this implementation now, since it makes it much more flexible to add the relevant component with required formatting anywhere in the file.

BTW, you forgot to remove the changes you did in the specification documents. Please, revert them.

Hmm, I did it before because I thought it is part of my job. But no problems :v:, I have reverted them. If you want to do it from your side or using spec generation scripts, it will be great.
The rest of the changes required have been completely removed from the PR. So, they are no longer needed to be corrected :smile:. Thanks for your review and feedback. If certain more changes are to be implemented, feel free to tell me. I'm there to go with them.

🤔 You split the component in 3 but I don't see you using it anywhere. Why are you creating them then?

@fmvilas That's what I had done before and you asked me to revert the changes in specification files, so I reverted them. If you think I need to add it again, I will do it again. It's better if you can guide me where it is needed.

I think we're not understanding each other. See my comment above: https://github.com/asyncapi/website/pull/597#discussion_r809400240. You can't use MDX because spec files are copied automatically from spec repo. This file can't have MDX syntax because it's used in other places where MDX is not supported + it's a normative document.
I thought you wanted to use these components in other places but if it's not the case I don't think this PR is needed then.

@fmvilas I understand that we can't use MDX directly in specification files as they are generated from scripts. But if certain special encoded text is needed to show lifecycle terms in specification files, what can be another approach/implementation to do this?
If this is not needed, we can surely close this PR and issue #592 to avoid confusion for other contributors and community members.

No Problem at all. We know that it is a good change but the only thing is that the implementation requires a lot of effort (which is not worth it, comparing the change we are producing). I will request @fmvilas to close that issue as well if you think it can't be implemented or it is not required.
Meanwhile, anyone who wishes to provide some closing notes to this PR, feel free to do that as I am getting an option of Close with comment :smile:.

No comments from my side. I think it's clear in the discussions above :) Sorry, @akshatnema! And thanks a lot for pushing it 🙏


Just curious...

Just kind of curious why you created this.  Are these some additional API's you wish stdlib had?

nah mostly just a spot for little utilities like the semaphore, finally tired of having hundreds of repos haha

ahhh I see, cool thx :-)


mac os build err

dyld: Symbol not found: _fdopendir$INODE64
Referenced from: /usr/local/go/bin/go
Expected in: flat namespace
Trace/BPT trap: 5

I tested, golang 1.9 is ok, but golang 1.10,1.11,1.12,1.13 show this error

Are you still experiencing this issue?

Closing this issue but feel free to open another if you're still having problems.


Problem with hard-coded shebang in generator.sh

I propose to change from hard-coded to dynamic shebang in the generator.sh script. This is the same that is used in setup.sh of getting-started, which is useful for portability (nixos here).

Sure, would be a good idea to use the same conventions as in other parts of the project!


feat(sumologicextension): use different key for encryption and filename

What is difference between key and passphrase in hashing functions?

Nothing 😅 I was also hesitant on the naming. I can make them both keys if you feel that would be better

I would make it consistent :)
key is fine

I would make it consistent :) key is fine

done


OpenSSL 1.1.1h

I am not sure why we can't use that latest GCC version. It seems rust uses the old march=armv7-a instead of march=armv7-a+fp to compile. I don't know what is the root cause.
New GCC for version forces you to specify +fp for floating point. If rust calls with the wrong parameter, it fails.
But I still don't understand why because the C code is supposed to be compiled already when the openssl-sys compiles.


feat: shuttle init --from

Description of change

Closes #867 (part 2), Follow-up on #888
Allows you to init by cloning any repo with

cargo shuttle init --from https://github.com/abc/123 --subfolder path/to/template
cargo shuttle init --from gh:abc/123 --subfolder path/to/template # gh:, gl:, bb:
cargo shuttle init --from abc/123 --subfolder path/to/template
cargo shuttle init --from ../some/local/repo --subfolder path/to/template

User is prompted if they want to use a different example template than hello-world: (also added link to examples repo; the README there should change to suggest using the above commands)

Improved post-init:
You can `cd` to the directory, then:
Run `cargo shuttle run` to run the app locally.
Run `cargo shuttle project start` to create a project environment on Shuttle.

Also bumped Cargo.lock
How has this been tested? (if applicable)

Testing locally for various combinations of flags and expanded test cases to cover everything new

@jonaro00 is this the most user intuitive approach? How will the user know which git urls they should be using?
Would expanding the list of templates from
Shuttle works with a range of web frameworks. Which one do you want to use?
›
❯ actix-web
  axum
  rocket
  tide
  tower
  poem
  salvo
  serenity
  poise
  warp
  thruster
  none

to something like
  actix-web
  actix-web/postgres
  actix-web/websocket-actorless
  axum
  axum/static-files
  axum/static-next-server
  axum/websocket
  axum/with-state
  ...

be more intuitive?
I suppose you could do both...

I like the idea, but there are some things to consider.

Most people that run init in interactive mode probably want to start from a hello world template(?)
Having all templates is more complex, more information overload, harder to see variety in what is available (but fuzzy find helps).
Would the list of examples be hardcoded or dynamically fetched?

I think there can definitely be more hints for how to use the git option, in examples repo and in docs.

Sounds good. First you choose framework and then between hello-world (default) and other templates (if those exist).

@jonaro00 I agree with @joshua-mo-143
And I also think this is a great idea.
Btw. from your last message; there should be a step asking for whether the users wants to pick a template (y/N) rather than prompt them with the list of templates and have them choose 'No' there.
This is running on the assumption that the majority will be satisfied with the hello world one to start building on top of it.

Caveat: the now forced git init will init a git repo even when already inside one.

Hmmm.
What if we check the folder to see if there's a .git subfolder? It shouldn't be too difficult.

It would need to be a recursive check, but a git lib can probably to this with one line.

Regarding all the sleeps and extra steps in tests:
I think the fails stem from that our tests and cargo-generate create a lot of tempdirs in a short amount of time. Not sure though.
One time got an error where the canonicalize failed for the init path (default) argument.
That was ultra rare compared to the more common error: an unwrap somewhere in cargo-generate due to "no such file or dir". Again, probably the tempdirs failing for some reason.
I find the "same random dir name" scenario too unlikely for it to fail so often, but a sequential approach could be taken. Still, this might just randomly fail aswell.
What I can say is that CI holds a bit better due to the changes, and now I'm too afraid to remove any of them 😅.
(If the sleeps are a concern due to CI time, then you are looking at the wrong kinds of tests.)

Oops, forgot to post this:
The flow now looks like this. I opted to put the examples hint after choosing template because the amount of text combined with the choice filled many lines and pushed text off-screen.
Is the "See the docs or help page." too unclear? (should there also be a link~?)


[release-2.5] Added sonar project properties file to repo

Signed-off-by: dislbenn<EMAIL_ADDRESS>

/approve
/lgtm


Integrating Razorpay in a React Django(Django Rest Framework) Application

Proposed article introduction
Razorpay is an Indian Payment Processing Platform that allows businesses to accept, process, and disburse payments with its product suite. In this article, we will take a look at how we can integrate Razorpay in a React Django Application to enable a business to send and receive payments.
Key takeaways

Working with payment applications.
Integrating Razorpay in a React Django application.
React best practices.

Article quality
Articles published on the web covering this topic only tackle the article from one side, either React only or Django only. This is good but not ideal for a beginner who might have an application that works with both React and Django. Implementing it might be difficult for them. In this article, we will do things differently by creating a REST API using Django Rest Framework and consuming the API routes with React. The payment process will be triggered by the user from the React frontend and the Django Rest Framework will interact with the Razorpay API to process the payment.
Other articles also cover this topic using Django templates but in this article, we will create a REST API with Django Rest Framework.

This article by @zolomohan discusses how to implement razorpay in React. How is this topic different from it?

Hi @WanjaMIKE. My article covers Razorpay integration with React Native. React and React Native have different Razorpay SDKs.
Also the backend that I used is Node.js but this article aims to cover Django.
I believe there's no overlap here with my article.

Hello @WanjaMIKE, as zolomohan has explained, my approach is totally different. There's no overlap.

@WanjaMIKE :eyes:

@WanjaMIKE, it has been way too long now and Zolomohan already cleared on the overlapping issue.
cc @ahmadmardeni1

@hectorkambow, can you please reopen this? The article is now ready.


Switch to openmmtools NCMC integrator

We should switch our NCMC alchemical integrators with calls to NonequilibriumLangevinIntegrator and use g-BAOAB-based splittings (e.g. V R O H O R V).
Note that V R O H O R V requires 2 x (1/2) force evaluations and two energy evaluations per timestep, all at different configurations. I'm not sure if NonequilibriumLangevinIntegrator supports more than one H perturbation per timestep, but if so, H V R O R V H` may be superior since it moves the energy evaluations to occur at the same positions as the force evaluations and allows them to be reused at the boundaries between timesteps.

Complete


commit-template.txt is mentioned in CONTRIBUTING.md but does not seem to exist

See: https://github.com/nmstate/nmstate/blob/base/CONTRIBUTING.md#L46

I will move this to https://github.com/nmstate/nmstate/issues/1296


updated v1 CRDs to 1.9.1 from community

changed v1 CRD labels to retain the version info
changed v1 CRD variables to be embedded with YAML files because using raw string literals with backticks caused issues since there are backticks in the descriptions of the CRDs
updated gitignore to include cache folder since that gets generated by bundle-run command
Signed-off-by: Henry Li<EMAIL_ADDRESS>

/cherry-pick release-ltsr

Steps to test:

Check if you already have cert-manager CRDs on the cluster. It's fine if you do not.
$ oc get crds | grep cert-manager
certificaterequests.cert-manager.io                               2022-09-01T15:57:37Z
certificates.cert-manager.io                                      2022-09-01T15:57:37Z
challenges.acme.cert-manager.io                                   2022-09-01T15:57:37Z
clusterissuers.cert-manager.io                                    2022-09-01T15:57:37Z
issuers.cert-manager.io                                           2022-09-01T15:57:37Z
orders.acme.cert-manager.io                                       2022-09-01T15:57:37Z

Most likely these CRDs are older than 1.9.1, so check the labels for one of them, which should look like:
labels:
    app.kubernetes.io/instance: ibm-cert-manager-operator
    app.kubernetes.io/managed-by: ibm-cert-manager-operator
    app.kubernetes.io/name: cert-manager

Follow testing steps in doc.

After operator is running, check the cert-manager CRDs again, the labels should look like
labels:
    app.kubernetes.io/instance: ibm-cert-manager-operator
    app.kubernetes.io/managed-by: ibm-cert-manager-operator
    app.kubernetes.io/name: cert-manager
    app.kubernetes.io/version: v1.9.1

Verify you can create cert-manager operands

Verify you can create basic self-signed Issuer and Certificate chain

/lgtm


Tableau Login failing with 401001: Signin Error; Error signing in to Tableau Server

Hi All,
First, let me state that my company has SSO enabled for our Tableau Server, and I'm thinking this might be a server-side issue rather than a code issue.
My code is taken from the most basic login provided on the Get Started Page, with two lines added
import tableauserverclient as TSC
import requests

tableau_auth =<EMAIL_ADDRESS>'MyPassword', 'MyCompany/datasources')
server = TSC.Server('https://us-west-2b.online.tableau.com/')

# I added the following two lines of code as I was getting an error[...] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1056)')))'
# These two lines at least got me around the error being printed to my screen, but I'm not sure if that fixed the underlying issue
server.add_http_options({'verify': False})
requests.packages.urllib3.disable_warnings()

with server.auth.sign_in(tableau_auth):
    all_datasources, pagination_item = server.datasources.get()
    print("\nThere are {} datasources on site: ".format(pagination_item.total_available))
    print([datasource.name for datasource in all_datasources])

This code results in an error:
_Traceback (most recent call last):
File "C:\Users\gdeemer\Documents\Projects\TableauAPI\Sing_on_v01.py", line 16, in
with server.auth.sign_in(tableau_auth):
File "C:\Users\gdeemer\AppData\Local\Continuum\anaconda3\lib\site-packages\tableauserverclient\server\endpoint\endpoint.py", line 127, in wrapper
return func(self, *args, **kwargs)
File "C:\Users\gdeemer\AppData\Local\Continuum\anaconda3\lib\site-packages\tableauserverclient\server\endpoint\auth_endpoint.py", line 32, in sign_in
self._check_status(server_response)
File "C:\Users\gdeemer\AppData\Local\Continuum\anaconda3\lib\site-packages\tableauserverclient\server\endpoint\endpoint.py", line 70, in _check_status
raise ServerResponseError.from_response(server_response.content, self.parent_srv.namespace)
ServerResponseError:
401001: Signin Error
	Error signing in to Tableau Server_

Is this something that I can I fix on my end, or do I need to raise a question to our admins so that the API is accessible?

I think what you'll need to do here is alter your 3rd parameter to TableauAuth to be just your "site name", for example:
tableau_auth =<EMAIL_ADDRESS>'MyPassword', 'MyCompany')

Regarding your company using SSO here, if the above doesn't work you could try personal access tokens instead. The usage with TSC library is a bit different which you can see here: https://tableau.github.io/server-client-python/docs/sign-in-out
Finally, regarding needing to set server.add_http_options({'verify': False}) to get rid of the SSL certificate error, that should be fine. I'm not sure whether requests.packages.urllib3.disable_warnings() is also needed; usually just the http_options call is enough.

@EisMann88 I'll go ahead and closed this one as solved, but please reopen with an update if needed.

I know this is closed, and I'm just trying a quick POC on the side, but I get the same error. Tried both with user login and PAT (I'm a Server Admin on the Tableau Server). We use SAML SSO.
Using sample code, plus turned off check for SSL cert error:
import tableauserverclient as TSC

#site is blank, as connecting to main (and only) site on Tableau Server
tableau_auth = TSC.TableauAuth('<token_name>', '<token>', site_id='')
server = TSC.Server('https://SERVER_URL')

server.add_http_options({'verify': False})
server.auth.sign_in(tableau_auth)

Then I the same error as @EisMann88 .
401001: Signin Error
		Error signing in to Tableau Server

I am also getting same error when trying to login to server

Do this for PATs:
    tableau_auth = TSC.PersonalAccessTokenAuth('token_name', 'mytoken', site_id='helloworld')
    server = TSC.Server('https://whatever', use_server_version=True)
    server.auth.sign_in(tableau_auth)

@bcantoni  Can you please suggest here, what should be the right way to resolve the issue?


Bug: Level format FirstCharacter is not working

Bug
NLog version:  4.4.5  (File Version: 4.4.4755.0)
Platform: .Net Framework 4.5
Hi!
I've found that format "FirstCharacter" is not working. The whole word "Trace" or "Info" is printed instead expected just one letter "T" or "I" as it is described in documentation.
XML configuration - NLog config:

The result in log file is:
2017-04-05  09:47:17.1851 | Trace | Collection elements contained in the custom section collection:
2017-04-05  09:47:17.2319 | Trace | TurnOnAfterStart = False
2017-04-05  09:47:17.2319 | Info | EuromapMachine 0:   Name=S12, SessionPath=c:\Euromap\Euromap\Plant\S12\Exchange, HistoryPath=c:\EuromapHistory\S12, ParametersConfig=S12.Parameters.config, RefreshRate=10000
2017-04-05  09:47:17.2319 | Info | EuromapMachine 1:   Name=S13, SessionPath=c:\Euromap\Euromap\Plant\S13\Exchange, HistoryPath=c:\EuromapHistory\S13, ParametersConfig=S13.Parameters.config, RefreshRate=10000
Best Regards
JBrzo

Think you will have better luck with NLog 4.4.6 BETA where the new change is actually included.

Yes this hasn't released yet ;)

Is there a documentation issue?

NLog 4.4.6 is live - so this works now!
https://www.nuget.org/packages/NLog/4.4.6


Add series_column_types

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (868efd9) 100.00% compared to head (b10f818) 100.00%.

:exclamation: Current head b10f818 differs from pull request most recent head 90745ee. Consider uploading reports for the commit 90745ee to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #155   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           62        62
  Lines         1433      1435    +2
  Branches       139       139
=========================================
+ Hits          1433      1435    +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


JS and PHP API keys are different

When I set up bugsnag, it requested I set up 2 x projects, one for php and one for js. And the API keys are different for both but with this component, can only set up 1 api key (so I can't use both at the same time).

We piped both JS and PHP using the same API keys.  I saw no issue using the same one.  I think the only thing it might affect is syntax highlighting, but I don't even think that was an issue.


License: change to LGPLv3 as the rest of the project

Plotjuggler is LGPLv3 and the package.xml state this is LGPLv3 so I think that the MIT license was a mistake as it should be LGPLv3 too

No, it is not a mistake

So if I make a new pluggin based on the sample pluggin, how do I handle the License ? Ideally, I would like it LGPLv3

This is interesting and need to be discussed in the readme.
To build a plugin you need:

Qt, that is  LGPL
Header files of PlotJuggler, that are also LGPL.

On the other hand, for the former, I will probably adopt the same license used by QWT:
https://qwt.sourceforge.io/qwtlicense.html
That is LGPL with some exceptions:
Then, the code in THIS particular repository is MIT, because you can basically do whatever you want with it.
You can use MIT code in GPL/LGPL one, but not the opposite. Therefore, this should not affect you

Ok ! Then shouldn't we fix the package.xml that state that this ros package build is lgpl when it is MIT ?


Grunt test tasks fails in

Running grunt does the build. But grunt test fails at the intern:functional task. It seems that it fails when opening the tunnel to SauceLabs due to missing credentials.
The grunt test output is:
Running "intern:functional" (intern) task
Verifying property intern.functional exists in config...OK
File: [no files]
Options: runType="runner", config="tests/intern.js", functionalSuites=["tests/functional/detectors.js","tests/functional/helpers.js"]
Listening on <IP_ADDRESS>:9000
Error: Tunnel failed to start: Exit code: 1
  at handleChildExit  <node_modules/digdug/Tunnel.js:336:16>
  at Socket.<anonymous>  <node_modules/digdug/Tunnel.js:379:6>
  at emitOne  <events.js:101:20>
  at Socket.emit  <events.js:191:7>
  at Pipe._handle.close [as _onclose]  <net.js:511:12>
Warning: Test failure; check output above for details. Use --force to continue.

and in the generated ./SauceLabsTunnel.log the last few entries are:
20170823 123219.209 [22439] ***********************************************************
20170823 123219.209 [22439] A newer version of Sauce Connect (build 3688) is available!
20170823 123219.209 [22439] Download it here:
20170823 123219.209 [22439] https://saucelabs.com/downloads/sc-4.4.9-linux.tar.gz
20170823 123219.209 [22439] ***********************************************************
20170823 123219.209 [22439] PROXY *** scproxy started ***
20170823 123219.210 [22439] PROXY found DNS server <IP_ADDRESS>
20170823 123219.259 [22439] Started scproxy on port 40559.
20170823 123219.259 [22439] Please wait for 'you may start your tests' to start your tests.
20170823 123219.259 [22439] Starting secure remote tunnel VM...
20170823 123220.359 [22439] GET https://saucelabs.com/rest/v1/undefined/tunnels?full=1: HTTP response code indicated failure.
20170823 123220.359 [22439] Response: {"message": "Not authorized"}.
20170823 123220.359 [22439] Error checking overlapping tunnels.
20170823 123220.359 [22439] Cleaning up.
20170823 123220.360 [22439] Sauce Connect could not establish a connection.
20170823 123220.360 [22439] Please check your firewall and proxy settings.
20170823 123220.360 [22439] You can also use sc --doctor to launch Sauce Connect in diagnostic mode.
20170823 123220.360 [22439] Goodbye.

Tried this both locally and on travis-ci.org, thinking that perhaps the .travis.yml env section would help:
env:
  global:
  # SAUCE_USERNAME
  - secure: S/6Ild1n9SmW8xYqarjkigDqmyFgWS4Hi0M07e/ryPeS1MNQdiS5+WuSmlSTevM/wU/oSCvzXnKhO9W/1tvz4qj/BMQYxYWFjwWAXJrkjJPvWoa5ogYkR3ETSYrqdhkT+8LVof8iLPlpHjS1y2fozyJbYf1YNSkcVCLxMdIwnk0=
...

but got same output on both.
I'm doing this with latest version 2.8.2.
How do I get the functional tests on SauceLab to run?

When opening a PR, the tests should run with the correct credentials, unless I'm mistaken?

Hey @tkalfigo @BenFradet only PRs from within Snowplow get access to those credentials.  Otherwise you could have someone open a PR with malicious changes to dump those credentials to plain text.
For more information: https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml
I believe this issue can be closed?

Agree, closing

How do you expect contributors test their implementation before sending a pull request? Could you provide i wiki document, how to setup a saucelabs account and how to configure all moving parts? We do not feel confident sending  a PR withouth prior successfully running the test suite. @alexanderdean, what do you think?

Good idea, re-opened and renamed ticket.

Some initial documentation is already on wiki: https://github.com/snowplow/snowplow/wiki/4-For-developers#54-tests, though requiring step-by-step guide and some rewording.

@chuwy I don't see how that wiki page helps devs who want to run the tests on a fork of the project as @christoph-buente requested. Also it seems outdated or inaccurate. I don't see a file tests/integration/request_recorder.js mentioned therein. And of course doesn't explain what would need to be adopted to run the tests, locally or through travis (e.g. AWS and NPM deployment among others I see in travis.yml).


Add text-size-adjust?

Need to review if this is suitable to go in.

Done in "Version 3" updates (see the v3 branch).


Rule to enforce a copyright at the beginning of a file

Reference: https://palantir.github.io/tslint/rules/file-header/
Useful for teams that enforce a Copyright MyCompany. All rights reserved. comment at the beginning of files.

Closing out my old issues for repos I no longer have context on. If anybody has a need for what this issue was asking about, I'd encourage them/you to file a new issue. Cheers!


AIOBoto3ServiceResource needs to inherit from contextlib.AbstractAsyncContextManager

Describe your idea
AIOBoto3ServiceResource needs to inherit from the standard library's contextlib.AbstractAsyncContextManager such that it can be used with the standard library facilities for async context managers, such as contextlib.AsyncExitStack, and still type check correctly.
AsyncExitManager is useful when you can't scope resource acquisition and release with a with statement, such as when you want to set up client connections at import time, which is what you need to do if you want to benefit from AWS Lambda provisioned concurrency.
Code sample
Currently type checking works for
async with session.resource('dynamodb') as dynamo_resource:
    ...

but the following fails
exit_stack = contextlib.AsyncExitStack()
dynamodb = await exit_stack.enter_async_context(session.resource('dynamodb'))

with the following type error:
Argument 1 to "enter_async_context" of "AsyncExitStack" has incompatible type "DynamoDBServiceResource"; expected "AbstractAsyncContextManager[<nothing>]"  [arg-type]mypy(error)

I believe this is due to AIOBoto3ServiceResource and thus by extension DynamoDBServiceResource not implementing AbstractAsyncContextManager, despite actually having the right __aenter__ and __aexit__ methods.
The type of enter_async_context is
def enter_async_context(cm: AbstractAsyncContextManager[_T@enter_async_context]) -> Coroutine[Any, Any, _T@enter_async_context]

Additional context
Versions:
boto3 = "1.24.59"
botocore = "1.27.59"
boto3-stubs = {version = "1.24.59", extras = ["apigatewaymanagementapi", "cloudsearch", "cloudsearchdomain", "cognito-idp", "dynamodb", "s3", "secretsmanager", "ses", "sns", "sqs", "transcribe", "translate"]}
aioboto3 = "^10.4.0"
types-aioboto3 = {version = "10.4.0", extras = ["dynamodb"]}
types-aiobotocore = "2.4.2"

AIOBoto3ServiceResource itself does not inherit contextlib.AbstractAsyncContextManager. So looks like it could potentially lead to incorrect type annotations. Could you please check if aioboto3 code works as expected with AsyncExitStack?
exit_stack = contextlib.AsyncExitStack()
dynamodb = await exit_stack.enter_async_context(session.resource('dynamodb'))

The code example you gave is the one I tested (see my initial comment). It runs OK but doesn't type check. AIOBoto3ServiceResource needs to inherit from contextlib.AbstractAsyncContextManager

I found the issue. Typing was incompatible with AbstractAsyncContextManager, but an inheritance from it is not required. Fixed ServiceResource, dynamodb.Table and dynamodb.Query classes. I will prepare a new release by tomorrow.

@tibbe Fixed in types-aioboto3 11.0.1.post1. Please test the new release and let me know if it works as expected.

Thanks!
Looking into it now. A first nit is that I think the traceback type should be Optional[TracebackType] rather than Any. Validating the rest now.

Seems to still not work (unless I'm holding it wrong):
async def test() -> None:
    exit_stack = contextlib.AsyncExitStack()
    session = aioboto3.Session()
    dynamodb: DynamoDBServiceResource = await exit_stack.enter_async_context(
        session.resource('dynamodb'))

note: Following member(s) of "DynamoDBServiceResource" have conflicts:
note:     Expected:
note:         def __aexit__(self, Optional[Type[BaseException]], Optional[BaseException], Optional[TracebackType], /) -> Coroutine[Any, Any, Optional[bool]]
note:     Got:
note:         def __aexit__(self, exc_type: Type[BaseException], exc_value: BaseException, exc_tb: Any) -> Coroutine[Any, Any, None]

There's a difference in the traceback type and the return type (None vs Optional[Bool]).

Thank you for testing. I do not use TracebackType because stubs had to be compatible with py36. Py36 is no longer supported, so I can actually use this type. Closing the issue.


dropbox-node: permission problem

i'm new dropbox developer, i'm try to run examples/db-browser/app.js but get some error:
This is dropbox i show:
{ consumer_key: 'c3i9jy0hnxlxm4t',
consumer_secret: 'cxmupkxtmh0ga1b',
access_token: undefined,
access_token_secret: undefined,
oauth:
{ _isEcho: false,
_requestUrl: 'https://api.dropbox.com/1/oauth/request_token',
_accessUrl: 'https://api.dropbox.com/1/oauth/access_token',
_consumerKey: 'c3i9jy0hnxlxm4t',
_consumerSecret: 'cxmupkxtmh0ga1b',
_version: '1.0',
_authorize_callback: null,
_signatureMethod: 'HMAC-SHA1',
_nonceSize: 32,
_headers:
{ Accept: '/',
Connection: 'close',
'User-Agent': 'Node authentication' },
_defaultClientOptions:
{ requestTokenHttpMethod: 'POST',
accessTokenHttpMethod: 'POST' },
_clientOptions:
{ requestTokenHttpMethod: 'POST',
accessTokenHttpMethod: 'POST' } } }
And this is error i have:
{ statusCode: 400,
data: '{"error": "This app does not have permission for this operation."}' }
{ lastAccess:<PHONE_NUMBER>932,
cookie:
{ path: '/',
httpOnly: true,
_expires: Mon, 13 Feb 2012 18:43:19 GMT,
originalMaxAge: 14400000 }
How to fixed problem, please help me
i already get newest dropbox-node

Is it possible that you're using an old consumer key pair? According to [this|http://forums.dropbox.com/topic.php?id=47214] this error can occur if your key predates the era of Dropbox's OAuth-only API.

Thanks alot for your help,  i've just created my app, so app key is new.
but i'm worry about: i use account login dropbox (mail/pass) to connect, it's right?
I can't add users (five user) to test
The program show: Test your app with up to five users	No users accessing this app
This is one of my development apps where I haven't enabled extra users yet: http://dl.dropbox.com/u/340607/enable_extra_users.png
This is one of my development apps where I have enabled extra users: http://dl.dropbox.com/u/340607/extra_users_enabled.png
How is what you're seeing different?

The db-browser example app accepts a consumer key/secret pair via the command line and then the web page prompts you for your Dropbox login credentials. The additional users feature shouldn't matter for the db-browser example app, as you can simply connect to your own Dropbox as the app's sole user.


[Question] Is harvester effected by log4j security vulnerability?

Is log4j security issue with harvester? If it is, then is there any fix?

No. Log4j is not used by Harvester or any of the components that Harvester depended on.


Add make verify target for running static analysis checks

Closes #31

@jmhbnz do we want to update the static-analysis pipeline to use make verify?
Also, would we want to include the fmt part for house-keeping, too?

@jmhbnz do we want to update the static-analysis pipeline to use make verify?
Also, would we want to include the fmt part for house-keeping, too? :)

I think yes for both :)
Thanks!

@jmhbnz do we want to update the static-analysis pipeline to use make verify?
Also, would we want to include the fmt part for house-keeping, too? :)

I think yes for both :)

Agreed - Thanks @henrybear327
Note: Please ensure your commit is signed so the developer certificate of origin check passes.

@jmhbnz do we want to update the static-analysis pipeline to use make verify?
Also, would we want to include the fmt part for house-keeping, too? :)

I think yes for both :)
Thanks!

Thanks for the feedback! :)
I have updated the linter target and added fmt!
For the linter, I took the linter config file from etcd project, as I am trying to keep the consistency across projects :)

Don't forget to signoff every commit :)

One nit comment. Otherwise LGTM.


Move logging before importing TF

The logging level has to be set before importing tensorflow for it to take effect. But, because it was set after import, there was no impact and TF was throwing warning after each epoch which is very distracting. This PR moves the logging to the right place.

LGTM!


Change input argument to optionals in AR

Either for ar_params: None or iterable, not [None], and let's use arrays instead of lists to make stuff faster internally.

Using an numpy array as input will now raise errors due to usage of list methods


typo in string namespace for capitalize function

Prerequisites

[x] I have read the Contributing guidelines
[x] I have read the Code of conduct and I agree with it

Description
There is a typo in index.js file in string namespace. There is a z instead of a t in method name.
import { capizalize } from './capizalize'
import { replace } from './replace'
import { toLower } from './toLower'
import { toUpper } from './toUpper'

/**
 * String functions.
 * @namespace string
 * @since 0.3.0
 */
export {
  capizalize,
  replace,
  toLower,
  toUpper,
}

Only for bugs :bug:
Version : 3.0.0

closed by #92


Feature: Templated Page Creation In Dashboard

Problem
Vapid's data model is restrictive for users that need the ability to create new standalone pages for their site. From the dashboard, users should be able to:

Create new pages using page templates
Create new collections of content to display on a page.

Proposed Solution
With a few small changes to the internal data model, we can enable these two features while maintaining full backward compatibility with current site structures.
Additionally – if we choose to go this syntax route – we can set up the framework for a breaking change down the line that will reduce the template syntax surface area, simplifying the developer experience even further. These new syntax features can be added now, and deprecation warnings can be added to the current compiler to help encourage migration. Because Vapid is statically analyzable, code mods for migration assistance are also possible.
In order to talk about these changes, we need to talk about it in the context of Vapid's current data model and templates constructs, and then map them to a model that will work in a multi-page world.
Current State of the World
Vapid data model actually already has a somewhat implicit understanding of pages, but it is not surfaced in the dashboard and there is no way for users to create new ones.
This is because with Vapid's current "everything is a {{section}}" data model, most projects end up with sections serving split concerns: some sections are more like site-wide settings, while others only appear in a single html file and operate as page content. We can codify this split responsibility of sections into the data model and template syntax.
For clarity in this proposal, I will be using some new language to better describe both the current framework behavior and the new proposed behavior to enable more granular user editing:

Page: A single rendered page on the site. These are currently non-partial .html files in the site root, have no dedicated instance data, are not exposed in the dashboard, and are currently singletons. Often pages will have one or more dedicated sections that serve as their page content.
Collection: A collection of Records. These are currently designated by the multi-section {{#section <name> multiple=true}} handlebar tag.
Record: An individual item in a Collection. Records may have an optional standalone template to render a single record at a permalinked URL, currently represented by a magically named partial in the site root.
Setting: Any handlebar tag – in the general scope or a specific {{section}} – that is shared between more than one Page and/or Record template.

Vapid's current behavior can be described as followed:

Vapid Page Sections

Each non-partial .html file is a Page.
Users to not have the ability to make additional pages. By default, a single page instance is created per non-partial .html file.
Pages have autogenerated metadata fields for _permalink (currently the file name), _created_at and _updated_at (file timestamp info) but they are not exposed to the template system, not configurable in the dashboard, and not actually stored in the database.
Pages may choose to display multiple Collection Records using the multi-section syntax (see below).
The default generatePage singleton will automatically use the default generate Collection singleton (see below).

Vapid Collection Sections and Records

By default, a single Collection instance is created for every multi-section type discovered in the site's Page templates, or by the presence of a standalone Record template.
A developer may define a Record template to render a single Record from the Collection – currently, this is a specially named partial in the root of the site www directory (see #66 for additional thoughts).
Each multi-section can be considered a named Collection of designated sub-page Records.
Users may not create additional Collection instances (Ex: I want a second blog collection that uses the same Record templates and overall data model, but is an entirely separate list of posts).
By default, zero Record instances are created for each generated Collection.
A Record has autogenerated metadata fields _permalink, _created_at and _updated_at that are exposed to the templating system but are not configurable in the dashboard.
Users may create additional Records in any Collection. By default, there are zero sub-pages present in a newly created Collection.

Vapid Setting Sections

Settings are shared configuration values that are meant to span more than one Page or Record. Non-multiple sections that appear in more than one Page or Collection item template are considered a shared site Setting.

Required Data Updates
To meet the stated needs of this issue, the following data changes are required:

Create a new pages sqlite table. Structure should be

CREATE TABLE pages (
  id int,
  created_at date,
  updated_at date,
  name varchar(255),
  content json
);

Move all multiple=true sections from sections to a new table called collections The multiple column may be dropped from the new collections table. The sortable and multiple columns may be dropped from the old sections table
Rename the sections table to settings
Rename the records.section_id column to records.collection_id
Add pages.template and collections.template columns. Fill them in with the same value that is in pages.name and collections.name. These will let Vapid know what template file to use. The name column will determine the page slug and dashboard .

Required Dashboard Updates
To meet the stated needs of this issue, the following dashboard changes are required:

Display Pages in the admin dashboard. By default, there is a single page created per template, as is currently done.
Allow users to create new Pages, selecting from the project Page templates as data structure options.
Allow users to delete Pages, including the default created ones. (this in part addresses #8. The ability to edit metadata for each Page or Record will finish it off.)
Allow users to create new Collection instances, selecting from the available templates. By default one Collection will be created for each unique multi-section discovered in the templates, as is the current behavior.
Allow users to delete Collection instances – including the default Collection created.
Because there may be multiple of any given Collection, Page dashboard pages must allow users to select the Collection they want to render on the page. Effectively, this means that {{#section collectionName multiple=true}} becomes a kind of directive, where users can select the Collection instance they want to render on the given page. This should be presented in the dashboard as a dropdown of all the Collection instances in the project that match that Collection type (eg: I have two pages on my site for my pets, one for dogs, and one for cats. I can code a single pets.html page, create two instances of it – one called Dogs and one called Cats – and two Collections – one called Dogs and one called Cats – and choose to render the correct collection on each given page.)
Consider all values in the general or a named {{#section}} to be a Setting and render it in the dashboard appropriately.

Required Syntax Updates
I have one major outstanding question for this feature is: How do we differentiate between the general scope, and a Page's specific content? Currently, the general scope is – by convention – un-prefixed in vapid templates. This poses a problem, since we need a way for developers to specify certain fields as Page content to be edited in the dashboard under appropreate page side menu item. Do do this, we need a way to differentiate between general site Settings, and Page specific content.
I see three options here:

Choose a reserved word prefix for Page content.
Glimmer has chosen to prefix all component specific data values with this. We can use this syntax to differentiate Page specific content in the template by prefixing it with this. So:
{{title}} {{!-- The general site title Setting --}}
{{this.title}} {{!-- The Page specific title --}}
{{#section social}}
  {{facebook}} {{!-- The social section facebook Setting --}}
  {{this.facebook}} {{!-- A Page specific facebook value --}}
{{/section

Require all general references to be prefixed with general.
#155 introduces the ability to reference the general scope from any context with {{general.value}}. We could add this as a hard and fast rule and mandate that all general refernces either be prefixed, or wrapped with {{#section general}} (presumably with the ability to reference any other Setting through dot syntax as well, ex: {{social.facebook}})
Because the concept of Page specific values is new to this change, we can easily apply a code mod on upgrade to prefix all general values with general. to maintain backward compatibility.

Attempt to infer what is general and what is a Page value.
Presumably, Page values will be unique to their .html file. This means that if the same {{value}} appears across two different .html files (either in a Page or a Record template) we can assume it is a shared setting and belongs in general. This approach has several downsides though:

It's ✨magic ✨and relatively opaque – there are no syntax hints as to what context a value will be injected in to.
Accidental name conflicts in large projects are totally possible and can cause accidental breakage as you edit .html templates in far-flung sections of the site.

Personal Syntax Recommendation
If I had my 'druthers, I'd pick both solutions 1 and 2. This would mean that:

all Settings values must be referenced by {{dot.syntax}}, and

all Page values must be referenced via {{this.value}}.

Bare values (ex: {{sectionValue}}) would still reference the general scope but log a deprecation warning and support for bare values would be removed at a later date.

Most contentiously –  the {{#section}} block would log a deprecation warning and instead encourage users to reference settings values via {{dot.syntax}}.
Many modern templating languages (including the next evolution of Handlebars, Glimmer) have moved away from context unwrapping constructs because it becomes very hard to manage inherited scope – both for the compiler and the developer. With the ability to reference Setting scopes via dot syntax, the {{#section}} block becomes vestigial. (Related, see my comments in #66 about scope management in templates).

The above four syntax updates would clear up the un-prefixed namespace for use by template helpers that – although not currently used – may be a valuable syntax to reserve for the future.
Optional Changes
These are things that are not entirely necessicary to deliver the features, but are nice to haves since we'd be touching bit swaths of project structure anyway 🙂

Deprecate {{#section name multiple=true}} in favor of a {{#collection name}} directive, which would be functionally equivalent bot more descriptive. The compiler will log deprecation warnings until we're ready to remove {{#section}} entirely, and we can provide an optional code mod to ease migration. This change would not effect the current Collection list rendering for Record templates in the proposal as drafted.
As mentioned in #66, we can move our magic Record template partials to a new /www/collections directory, remove the _ prefix, and not require a {{#section}} wrapper. This will reduce the (granted, already minimal) framework boilerplate, and align naming conventions if we go with the new {{#collection name}}block mentioned above. We can maintain backward compatibility by falling back to the old magic_partial.html` templates and logging a deprecation.
Because {{#section collectionName multiple=true}} is interpreted as a directive type in Page dashboards, it opens up the option to override the order, limit and query settings for any given page. This may be a very handy feature.
The ability to select multiple collections of the same type to render on the page. Eg: I want to create a blog page that shows both cats and dogs collections.

Describe alternatives you've considered
None... this was the one data model that could maintain backward compatibility with old sites, while still introducing the ability for ad-hoc user page creation in the site. Open to alternatives!
Additional context
This change would open up the dashboard to a number of new features that have been kicking around for a while:

Fully featured, Page and Record metadata panels to provide custom page slugs, social media metadata, page draft/publishing settings, authorship accreditation, code injection, etc
Dashboard hosted nav bar management for a user-configured site navbar.

Wrote a novel 😅 Didn't know how else to present the idea though! Let me know any thoughts – I think this could be a powerful addition to the platform.

Simple dashboard side menu concept that could accommodate this change. Would obvs need to mock out a Page and Collection creation flow / settings menu so users can set the page name and select the associated template.

@srobbin, began playing with this over in https://github.com/amiller-gh/vapid/pull/1 🙂 It feels really good... and is fully backward compatible!  The biggest reason is that right now there's a clear separation of concerns: site structure is controlled by those who have access to the templates, and the dashboard is for editing pre-determined content. Giving dashboard users the ability to add pages blurs that line.
I agree that the current model of creating permalinked record pages isn't great, though. Let me think on this one, and I'll reply again shortly.

I think there's a lot of good in that experimental PR even if we don't allow the ability to create multiple pages beyond the default created ones – the ability to reason about page-scoped values is a mental model that I think will resonate with clients more. Ex: You're not editing the "Company Description" section that may or may not be used elsewhere on the site, your editing the "About Us" page. If something is a "Setting" you know it's pretty darn likely to be used elsewhere.
The internal mental model for multiple instances of a page is like a special case of collections (aka multiple=true sections). Allowing users to create multiple standalone pages should be no more complicated rendering standalone pages for collections.
Specific use case example: A user needs to make special one-off donation pages for events with special copy and a dedicated URL for each page. This could be done with a {{collection}}, but if a site needs to have a global setting for multiple donation levels (ex: $1 Supporter, $30 Sponsor, $100 Co-Host) then this page needs a nested collection associated with it. From a user's perspective, grouping these all into "Sections" will not be as manageable since there is no communicated relationship between the "Donation Page" collection and the "Supporter Levels" collection. With the page abstraction this relationship becomes more clear in the UI and in the internal data model.
Beyond the page data model changes I think the most important change in there is swapping out the goatee renderer with Handlebars propper. By leaning on it for AST generation and rendering ( with the appropriate server-side runtime helpers for page creation) we get all of the nice features that come with handlebars templates without the parser maintenance :)
Nifty side effect of the new parser: Partials have full support now, including passing scope, rendering block contexts (layout partials work now!!) and we don't have to maintain any parsing code for hash values and content excaping. By working directly with the AST we can transform templates as they go through the parser (ex: I enforce Vapid's distinction between un-prefixed paths and this. paths, when the default hbs renderer looks both up in the same local scope) and log deprecation warnings (ex: log _ pseudo-private paths as deprecated in favor of the language-native @ prefixed data paths). Restrictive language features in Vapid can be implemented in our AST crawler by throwing custom errors instead of doing it at parse time and assuming a huge maintenance burden.

(Also, PR is very experimental still – section sorting / limit directives aren't implemented, tests won't pass, the @data page meta aren't implemented, and there are likely a slew of other bugs – but its a good conversation starter! 😄)


Using custom .env path only works from workspace root

(moved from https://github.com/NiklasPor/nx-remotecache-azure/issues/22)
Hello,
I don't know if I mis understood something, but I'm having troubles to configure the custom cache (using azure in my case).
When I run pnpm nx run "@myorg/myproject:build" --verbose from the root of the workspace, I can see cache populated.
But if I run cd packages/myproject then pnpm nx build --verbose, the cache does not works.
I get this error:
Warning: Failed to store cache to Azure Blob Storage
File:<PHONE_NUMBER>3156603647.tar.gz
Error: Did not pass valid container. Supply the container either via env or nx.json.

To setup the cache, I configured my root nx.json file like this:
{
	"tasksRunnerOptions": {
		"default": {
			"runner": "nx-remotecache-azure",
			"options": {
				"maxParallel": 4,
				"dotenvPath": ".env.secrets",
				"cacheableOperations": ["build", "test", "lint", "e2e", "release"]
			}
		}
	},
     ....
}

And I created a file .env.secrets sibling to the nx.json file which contains:
# Chaine de connexion du blob storage stockant le cache de Nx
NXCACHE_AZURE_SAS_URL=https://mystorageaccount.blob.core.windows.net/nx-cache?sp=racwdli&st=2024-03-26T07:59:15Z&se=2028-03-26T14:59:15Z&spr=https&sv=2022-11-02&sr=c&sig=abcabcabcabcabc%3D

The full error is:
------------------------------------------------------------------------------
Warning: Failed to store cache to Azure Blob Storage
File:<PHONE_NUMBER>3156603647.tar.gz
Error: Did not pass valid container. Supply the container either via env or nx.json.
------------------------------------------------------------------------------
Error: Did not pass valid container. Supply the container either via env or nx.json.
    at getBlockBlobClient (C:\path\to\node_modules\.pnpm\nx-remotecache-azure@18.0.0_nx@18.0.8\node_modules\nx-remotecache-azure\index.js:26:15)
    at blob (C:\path\to\node_modules\.pnpm\nx-remotecache-azure@18.0.0_nx@18.0.8\node_modules\nx-remotecache-azure\index.js:49:32)
    at storeFile (C:\path\to\node_modules\.pnpm\nx-remotecache-azure@18.0.0_nx@18.0.8\node_modules\nx-remotecache-azure\index.js:54:42)
    at C:\path\to\node_modules\.pnpm\nx-remotecache-custom@18.0.0_nx@18.0.8\node_modules\nx-remotecache-custom\get-safe-remote-cache-implementation.js:30:30
    at Object.store (C:\path\to\node_modules\.pnpm\nx-remotecache-custom@18.0.0_nx@18.0.8\node_modules\nx-remotecache-custom\create-remote-cache-store.js:17:11)
    at async C:\path\to\node_modules\.pnpm\nx@18.0.8\node_modules\nx\src\tasks-runner\cache.js:99:17
    at async _try (C:\path\to\node_modules\.pnpm\nx@18.0.8\node_modules\nx\src\tasks-runner\cache.js:222:24)
    at async Promise.all (index 0)
    at async TaskOrchestrator.postRunSteps (C:\path\to\node_modules\.pnpm\nx@18.0.8\node_modules\nx\src\tasks-runner\task-orchestrator.js:261:13)
    at async TaskOrchestrator.applyFromCacheOrRunTask (C:\path\to\node_modules\.pnpm\nx@18.0.8\node_modules\nx\src\tasks-runner\task-orchestrator.js:216:9)

When running from the workspace root, I get, in the output
Stored output to remote cache: Azure Blob Storage
File:<PHONE_NUMBER>3458654225.tar.gz

If I set up manually the env variable using
$env:NXCACHE_AZURE_SAS_URL="https://mystorageaccount.blob.core.windows.net/nx-cache?sp=racwdli&st=2024-03-26T07:59:15Z&se=2028-03-26T14:59:15Z&spr=https&sv=2022-11-02&sr=c&sig=abcabcabcabcabc%3D"

The cache always works, so I guess there's something wrong with the way the local .env.secrets file is read.
I tried to explicitely targets the env file at workspace root using "dotenvPath": "{workspaceroot}/.env.secrets", but there's no more success.
If it matters, pnpm why nx* give:
devDependencies:
nx 18.0.8
└─┬ @nrwl/tao 18.0.8
  └── nx 18.0.8
nx-remotecache-azure 18.0.0
├─┬ nx 18.0.8 peer
│ └─┬ @nrwl/tao 18.0.8
│   └── nx 18.0.8
└─┬ nx-remotecache-custom 18.0.0
  └─┬ nx 18.0.8 peer
    └─┬ @nrwl/tao 18.0.8
      └── nx 18.0.8

And my node version is 16.20.2
Thanks

I think the issue come from there:
https://github.com/NiklasPor/nx-remotecache-custom/blob/fb48a25285fee19589f4ddd9b2a7f235bc2dd40b/lib/init-env.ts#L7C1-L10C4
I believe the dotenv path provided is relative the current location where the nx command is ran.
I quickly prototyped a workaround:
import dotenv from "dotenv";
import { workspaceRoot } from "nx/src/utils/workspace-root";
import { CustomRunnerOptions } from "./types/custom-runner-options";
/**
 * Initializes the environment variables.
 */
export const initEnv = (options: CustomRunnerOptions) => {
  if (options.dotenv !== false) {
    const dotenvConfig = {
      path: options.dotenvPath?.replace("{workspaceRoot}", workspaceRoot),
    };
    console.log("🍕 dotenvConfig", dotenvConfig);
    dotenv.config(dotenvConfig);
  }
};

This way, the token {workspaceRoot} is properly resolved if present.
I can submit a PR with it if you think this is the solution, but I'm note sure if it's the proper way to handle it, and there's other token to take into account.

Seems to be fixed in the latest version. Not sure if it was a nx or this lib issue actually.

Nevermind. The issue is still present (had the env files loaded elsewhere). sorry


Prometheus rule created but not loaded on prometheus operator

Hello,
I am not sure if this is a bug or I am missing something in setup process.
I am trying to setup sloth on my cluster based on this approach https://github.com/slok/sloth#kubernetes-controller-prometheus-operator.
I successfully set up the sloth controller which runs without any errors.
I added a sample slo for a service running. The respective prometheus rule created successfully. But the rule doesn't get attached to prometheus operator. Should I do it manually? If yes why not to follow the cli approach instead?
Thanks in advance for any answer.

Hi @stafot
Once the Prometheus operator Rules CRs are created, Sloth's job finishes, and you shouldn't need to do anything manually either.
Are you already loading automatically any other rules (apart from the Sloth ones) with the Prometheus operator?
Normally when you create a Prometheus instance with the Prom-operator, you will tell what is the label selector this Prometheus needs to match to discover the rules it should own (and load), if you don't have this configured correctly it will not discover the created rules. For example:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
  namespace: monitoring
  labels:
    prometheus: prometheus
spec:
# ...
  ruleSelector:
    matchLabels:
      prometheus: prometheus
      role: alert-rules
# ...

Now my PrometheusRules CRs at least should have prometheus: prometheus and role: alert-rules labels so this prom can load them automatically. Sloth will set the same labels the Sloth CRs has to the PrometheusRule CR, so, for example:
---
apiVersion: sloth.slok.dev/v1
kind: PrometheusServiceLevel
metadata:
  name: some-slo
  namespace: monitoring
  labels:
    prometheus: prometheus
    role: alert-rules
    app: sloth
    something: something
spec:
# ...

Let me know if this solves the problem.

Thanks for your quick answer. I will review my setup based on your instructions and I will come back to you! Appreciated.

@slok Thank you very much, your suggestion did the trick.

Awesome!


Solved the problem in linux based system. I've edited jar.

    Solved the problem in linux based system. I've edited jar.

ignore unnecessary line as its added by to to view commands of processbuilder.

Originally posted by @nikzdevz in https://github.com/iBotPeaches/Apktool/issues/1969#issuecomment-1200244673
Please tell me how you edited your jar file

I don't see a problem or solution.

I want to know how to solve the problem for building using apktool it
results in an error even after considering the answers posted it still
doesn't work
On Tue, Nov 22, 2022, 2:01 PM Connor Tumbleson @.***>
wrote:

Closed #2949 https://github.com/iBotPeaches/Apktool/issues/2949 as not
planned.
—
Reply to this email directly, view it on GitHub
https://github.com/iBotPeaches/Apktool/issues/2949#event-7866671249, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3CI65MQZY4BVQFYUN5QWK3WJSR2NANCNFSM6AAAAAASHVF56M
.
You are receiving this because you authored the thread.Message ID:
@.***>

Where is the solution?

I: Building resources...
W: aapt: brut.common.BrutException: brut.common.BrutException: Could not extract resource: /prebuilt/linux/aapt_64 (defaulting to $PATH binary)
W: /home/blackhat/Vaim-RamSom/vaimpier/res/values/strings.xml:5: error: Apostrophe not preceded by \ (in You're being hacked!)
W:
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [aapt, p, --min-sdk-version, 8, --target-sdk-version, 21, --version-code, 1, --version-name, 1.0, --no-version-vectors, -F, /tmp/APKTOOL3649120788464392945.tmp, -0, png, -0, arsc, -I, /root/.local/share/apktool/framework/1.apk, -S, /home/blackhat/Vaim-RamSom/vaimpier/res, -M, /home/blackhat/Vaim-RamSom/vaimpier/AndroidManifest.xml]
[!] Failed to signed APK's
Got this error

@Rawanrao29 - This issue looks unrelated. As the error suggests I would fix the apostrophe


column head individual search not working (also on version django>2 and mysql_5.7

Hi, the column head individual search is not working and also not working on the django>2 and mysql_5.7 version (I made some edits to that with column search).
Any ideas? Thank you,
您好，我发现这个版本以及django>2 and mysql_5.7版本(加上列搜索功能后)的列单独搜索都不能使用。

@chainwang31 Do you mean the search function? I just tested it, it is normal, can you explain it clearly?

Hi @chainwang31
Do you mean the search function? I just tested it, it is normal, can you explain it clearly?

Hi @chainwang31
I am not very familiar with the part of JavaScript (I am more focused on the back end), may have to trouble you to study on your own.


build: add BOM files to dist packages

Description

Add SBOM files to release packages and Docker images.
Resolved or fixed issue: #2028
Affirmation

[x] My code follows the CONTRIBUTING.md guidelines

Is it common practice to also bundle SBOMs into Docker images and Vagrant boxes? We try to avoid any unnecessary steps in the Docker build process particularly, to keep the image as small as possible.

re https://github.com/juice-shop/juice-shop/pull/2031#issuecomment-1595641098
do you see an alternative?
I mean, it is the BOM of the application that was custom-built for(/in) the docker env; it is not the bom of the whole docker image.

That's not really an option as we don't build package ZIPs unless it's a release. Docker images are built from two branches constantly. Ok, then, I'll have to take a look at the impact, which hopefully isn't huge, and then see what else you added. I'll be pretty much unavailable the entire next week, so please expect some delay in the review.

thank you for merging. :rocket:
Please let me know if this change causes unexpected trouble during the next release.


710 reductive pruning

Description
Replaced the reductive reducer with new reductivePruner. Before, the tree was not being reduced correctly with multiple fields. Now, it is being pruned and the state of the reduction is held as the pruning progresses.
Changes

Created ReductiveTreePruner to prune the tree for contradictions with the current fixed field
Removed ReductiveDecisionTreeReducer
Created ConstraintNodeBuilder to assist in testing

Additional notes
There is still a known issue with the reductive walker, where it does not correctly reduce the final fixed field. This issue is out of the scope for this PR.
Issue
Resolves #710

Codecov Report

Merging #750 into master will decrease coverage by 0.13%.
The diff coverage is 91.46%.

@@             Coverage Diff              @@
##             master     #750      +/-   ##
============================================
- Coverage     65.75%   65.61%   -0.14%
+ Complexity     1757     1733      -24
============================================
  Files           278      277       -1
  Lines          6205     6113      -92
  Branches        727      715      -12
============================================
- Hits           4080     4011      -69
+ Misses         1855     1836      -19
+ Partials        270      266       -4

Impacted Files
Coverage Δ
Complexity Δ

.../generator/walker/reductive/FixedFieldBuilder.java
81.48% <ø> (ø)
9 <0> (ø)
:arrow_down:

...electionstrategy/ProfileBasedFixFieldStrategy.java
90% <ø> (ø)
5 <0> (ø)
:arrow_down:

...r/walker/reductive/FieldSpecExtractionVisitor.java
100% <100%> (+13.33%)
4 <3> (+1)
:arrow_up:

...deg/generator/decisiontree/TreeConstraintNode.java
69.41% <100%> (ø)
26 <1> (+1)
:arrow_up:

...c/deg/generator/decisiontree/TreeDecisionNode.java
72.41% <100%> (ø)
10 <1> (ø)
:arrow_down:

...or/constraints/atomic/AtomicConstraintsHelper.java
75% <75%> (ø)
2 <2> (?)

.../generator/walker/ReductiveDecisionTreeWalker.java
78.94% <83.33%> (+5.13%)
9 <2> (ø)
:arrow_down:

...logic/deg/generator/walker/reductive/Combined.java
88.23% <88.23%> (ø)
10 <10> (?)

...ogic/deg/generator/fieldspecs/FieldSpecMerger.java
68.96% <90.9%> (+11.07%)
13 <7> (+8)
:arrow_up:

...enerator/walker/reductive/ReductiveTreePruner.java
95% <95%> (ø)
15 <15> (?)

... and 16 more

Continue to review full report at Codecov.

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


Incorrect Link

Step 2. at https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#option-1-uninstall-the-classic-teams-client-and-install-the-new-one links to "Hardware and software requirements for SharePoint Server 2016" instead of the MSIX for the new version of Teams.

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

ID: db74252a-f531-8fcf-4da0-5e439cfdfd8d
Version Independent ID: db74252a-f531-8fcf-4da0-5e439cfdfd8d
Content: New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams
Content Source: Teams/new-teams-vdi-requirements-deploy.md
Service: msteams
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

Duplicate of https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/10530

Fixed in https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/commit/5e1aff2bd9bb8f4227b20c1f4dfb2ba6034823b9


spring-cloud-starter-config causes config bean validation to fail

Spring boot 1.5.2 fails to start because of bean validation errors caused by spring-cloud-config-starter:Camden.SR5.
We have a couple of @ConfigurationProperties in our project - some of properties to be set are coming from a defaults.properties in the classpath and others are overwritten by a config provided by a config server. Since we upgraded to boot:1.5.2 and spring-cloud:Camden.SR5 our app does not start properly anymore because of a bean validation error like the following:
Binding to target com.example.config.MiscConfigInfo@6f6962ba failed:

    Property: misc.kmsToWarning
    Value: null
    Reason: may not be empty

    Property: misc.listener
    Value: null
    Reason: may not be null

Action:

Update your application's configuration

So far so good, the description seems very clear, but it actually is wrong - the configuration is all fine and it works as soon as we remove spring-cloud-config-starter from the classpath.
Here is a very small project demonstrating the issue: https://github.com/imod/spring-config-validation-issue
For now, there only seems one workaround: we have to disable the field validation (remove the annotations on the properties).

It's fixed in snapshots (Camden and Dalston). New releases are coming shortly.

@dsyer yep, i just tested and Camden:SNAPSHOT works - thanks!

@dsyer but I have an question: is it normal/expected that the config beans are instantiated twice? at least afterPropertiesSet() is called twice on the config object (MiscConfigInfo) in this example project.

Might be a bug. But can you open a new issue please if you think it is?

done: #663


Update LICENSE.txt

Hi @hariyerra, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Hi, could you tell me the purpose of this pull request?

Closing this PR because it is not clearly addressing a problem and there has been no activity.


chore: add 1.0.7 docs

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: website/versioned_docs/version-1.0.7/Deploy Models/Overview.md
66
94
65
44

:white_check_mark: website/versioned_docs/version-1.0.7/Deploy Models/Quickstart - Deploying a Classifier.md
68
50
100
40

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Advanced Usage - Async, Batching, and Multi-Key.md
79
100
44
54

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Geospatial Services.md
69
57
67
50

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Multivariate Anomaly Detection.md
88
100
100
66

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Overview.md
85
100
96
73

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Analyze Celebrity Quotes.md
91
100
100
55

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Analyze Text.md
68
70
100
49

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Create Audiobooks.md
100
100
100
100

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Create a Visual Search Engine.md
87
100
100
68

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Document Question and Answering with PDFs.md
73
100
87
35

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Flooding Risk.md
75
74
100
31

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/AI Services/Quickstart - Predictive Maintenance.md
71
68
87
41

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Anomaly Detection/Quickstart - Isolation Forests.md
70
100
73
33

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Causal Inference/Overview.md
86
100
100
71

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Causal Inference/Quickstart - Measure Causal Effects.md
83
100
59
74

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Causal Inference/Quickstart - Measure Heterogeneous Effects.md
84
100
60
75

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Causal Inference/Quickstart - Synthetic difference in differences.md
66
100
66
56

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Classification/Quickstart - SparkML vs SynapseML.md
86
100
69
82

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Classification/Quickstart - Train Classifier.md
84
100
100
61

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Classification/Quickstart - Vowpal Wabbit on Tabular Data.md
83
100
100
49

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Classification/Quickstart - Vowpal Wabbit on Text Data.md
74
71
100
56

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Distributed Training.md
91
100
100
72

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Getting Started.md
94
100
100
100

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/ONNX.md
87
100
89
46

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Quickstart - Fine-tune a Text Classifier.md
100
100
100
100

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Quickstart - Fine-tune a Vision Classifier.md
100
100
100
100

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Quickstart - ONNX Model Inference.md
98
100
100
92

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Deep Learning/Quickstart - Transfer Learn for Image Classification.md
100
100
100
100

:white_check_mark: website/versioned_docs/version-1.0.7/Explore Algorithms/Hyperparameter Tuning/HyperOpt.md
70
100
60
66

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx


git lfs track "/somedir/*" error

I think a slash at the beginning of a pattern is valid and indicates the root of the repository. This is explicitly stated in .gitignore but seems to work in the same way for .gitattributes.
git-lfs 1.1.0 returns " is outside repository" in that case.

This was put in to prevent people from referencing absolute paths outside of the repository. You can update .gitattributes and add whatever you want though. Is there some reason you can't use just "somedir/*"?

Yes, I edited .gitattributes manually. I think the difference is:
"somedir/*" will match:
somedir/*
foo/bar/somedir/*
...

whereas "/somedir/*" will match only:
somedir/*

no?

Ok, seems legit :+1:

thanks :-) ... I am a bit busy right now but maybe I can provide a patch next week or so...

Cool. I added it to the v1.2 checklist. Though being a bug, it could technically go towards v1.1.1 if we need it.


Next Word Prediction

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Next Word Prediction
:red_circle: Aim : To predict the next word according to the data present and collected in our database.
:red_circle: Dataset : https://drive.google.com/file/d/1GeUzNVqiixXHnTl8oNiQ2W3CynX_lsu2/view
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.
A Demo Project has been created to guide you about the whole structure of presenting the Project in this repository. Here's the link of the Demo Project - https://github.com/abhisheks008/ML-Crate/tree/main/Project-Demo-Folder

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
Are you a participant of SWOC 2.0?

[ ] YES
[ ]  No

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

I have registered for JGEC Winter of code, can I work on this?

Yes @PurnaChandraMansingh you can, wait for the coding period to start from Feb 1.

Ok, Thank you

Full name : Kartik Chauhan
GitHub Profile Link : https://github.com/skartikc
Participant ID : N/A
Approach for this Project :
Preprocess the given dataset - clean, generate tokens, stem, lemmatize each word and apply different approaches for vectorization - GloVe, TF-IDF, etc. Generate a vocabulary to predict the work from and use, compare different algorithms for next word prediction with visualizations.
Are you a participant of SWOC 2.0? - NO

Are you contributing here for any open source program? @skartikc

i am not currently a part of any open source program, but i want to contribute, how should i proceed?

Okay first of all thanks for approaching this project repo.
Follow the guidelines written in the issue itself and comment out here accordingly with your credentials and approach for solving this project. If that feels appealing to me, I'll assign this to you. After that you can start working on it.
Sorry for the late reply @skartikc

Full name : Kartik Chauhan
GitHub Profile Link : https://github.com/skartikc
Participant ID : N/A
Approach for this Project :
Preprocess the given dataset - clean, generate tokens, stem, lemmatize each word and apply different approaches for vectorization - GloVe, TF-IDF, etc. Generate a vocabulary to predict the work from and use, compare different algorithms for next word prediction with visualizations.
Are you a participant of SWOC 2.0? - NO

Sounds good to me. Issue assigned to you @skartikc.
Best wishes!

@skartikc updates regarding this issue.

I have been working on this issue for the past week, learned a lot of text vectorizing techniques and exploring various combination of those with different models (RNN, LSTM). I have forked the repo and committing changes daily to it, my next step will be the final 2 model training.

Sounds great. Keep learning and make sure you complete the project as early as possible.
@skartikc


Paths get parsed wrong

Hi,
I'm on Windows 10 and I'm getting the following error:
$ yarn steps
yarn run v1.22.4
$ yarn cucumber-generator --template cucumber -f features --relativePathToFeatures ./ --output file
$ C:\Development\testing\cucumber_datalab\node_modules\.bin\cucumber-generator --template cucumber -f features --relativePathToFeatures ./ --output file

Found files:
:/Development/testing/cucumber_datalab/features/login.feature
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open 'C:\Development\testing\cucumber_datalab\features\:\Development\testing\cucumber_datalab\features\login.feature'
Emitted 'error' event on ReadStream instance at:
    at internal/fs/streams.js:162:14
    at FSReqCallback.oncomplete (fs.js:163:23) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\Development\\testing\\cucumber_datalab\\features\\:\\Development\\testing\\cucumber_datalab\\features\\login.feature'
}

It looks like the paths are joined incorrect.

Try to explicitly define --outputDirectory [directory] (eg. --outputDirectory steps).

Still the same error

Okay, it is functional on MacOS and I will check it on Windows this weekend.

Okay sorry for the delay, it should be fixed in #33. Please try if the fix works.


Option to display date difference on clocks (ie, one day ahead/behind)

What?
Date difference displays whether the local date of a clock's region is a day ahead or a day behind of the date at the user's location. A "+1" is displayed if the local date is a day ahead and a "-1" is displayed if the local date is a day behind. The user can toggle this option in the Options pane for each clock they add.
Fixes bluecaret#240 from the original repo
Why?
This is a requested enhancement and a currently open issue: bluecaret#240
Although the issue requested an option to display the date in clocks 2-5, adding multiple dates could result in a confusing user interface because the date and the time are separate features so the date doesn't have to be located right next to the time. If there are multiple dates floating around separate from their respective times, a user would not know what was the actual date.
How?

Whether or not the date difference is enabled, the font size of the date difference, and the offset amount of the date difference are saved as part of the clock configuration under TimeSettings and can be referred to as clock.dateDiff.enabled, clock.dateDiff.scaling, and clock.dateDiff.offset for a Clock clock.
These new fields have also been added to the Clock class in models/clock.ts
If the dateDifference is on, the date difference will be calculated and displayed after the meridian.

Testing?

Successful local dev build
Manual testing through clicking and refreshing

Screenshots

Anything Else?

Translation is needed for the "Date difference" blurb as well as the blurbs of the size and offset options in the "Time" panel,

I think this pr deletes the entire package-lock.json file; is there any way you could add it back in?

nice catch! package-lock.json should be restored to the version in master now.


How to use the standalone executables for Windows

Hi, can you give me an example of how to run the standalone executables of CAPA for Windows?
On opening any malware sample with it, the output screen does not hold, it opens and closes by itself. and not able to open using cmd also.
please help.

capa-v1.0.0-win.exe <sample>

We should update our documentation to highlight that capa is "a command line tool that should be run from the terminal".

'capa-v1.0.0-win.exe' is not recognized as an internal or external command,
operable program or batch file.

You should add the location of your capa file path to windows environment variables.

what are the file types currently supported by CAPA?
will it work for doc, pdf  file?

And FYI, CAPA is built only to work with PE & shellcode, not gonna work with non-PE i.e. .doc etc.

I already told you and you should check the https://github.com/fireeye/capa/blob/master/README.md carefully before asking and also check here for CAPA's limitations.

sorry i missed the previous edited section in your comment. thank u

a command line tool that should be run from the terminal

added in https://github.com/fireeye/capa/commit/9b873aeba75945464769f3c01a5c7168605aee04


add support for datagrams

pretty well copy pasta'd from github.com/adriancable/webtransport-go, adds support for datagrams
depends on https://github.com/quic-go/quic-go/pull/4112
resolves https://github.com/quic-go/webtransport-go/issues/8

Thanks for the PR, but this is the wrong layer to implement datagrams.

Oh interesting! This is based on how https://github.com/adriancable/webtransport-go/blob/main/webtransport.go works (mostly copy pasta'd 😅) for which send / receive message are called on the quic connection (and use the quic-go datagram queue)... I'm super new to these protocols so can definitely appreciate that I might be misunderstanding how it's supposed to work but this does work with WebTransport (tested with firefox) - The datagram queue in this lib is attached to the quic connection so are you saying that queue in quic-go should not be used but rather it should be built into http3 and exposed another way?


WIP: Fixes #787 not to restore output view when without serialized view

In this PR, I'm trying to address the problem proposed in #787.
What's wrong
So far, I confirmed that when there is a previously serialized view, deserializedOutputView works fine and restores the view into the location where it located.
But even when the view had been destroyed, activate function still creates a new OutputViewContainer object anyway, and the pane is even toggled because it's defined in the constructor, which makes this problem.
Workaround
I deleted the line in activate function and the annoying restoring seems disappeared 👇
Why WIP ? (Remaining work)
The remaining problem now is that when we don't have a restored output view and then call git-plus:run, we have to manually create the view by invoking git-plus:toggle-output-view in order to see the result, since there is no view yet.
I think it's better to create (and toggle) the view when we first call git-plus:run by checking if there is an already existing view.
But I'm not sure git-plus:run is the only user command which uses OutputViewComponent, thus I leave this PR WIP.
So, could you tell me all the cases when we use OutputViewComponent ??
Or does this workaround seem inappropriate this time ?

Thanks for getting started on this. I ended up making the changes myself and implementing a ViewController that can create the view only when it's requested. Feel free to take a look at the commit to see how it was working before.

Thanks for your work ! Looking forward to nxt release〜


Added github action yml

Added github action php.yml

Coverage remained the same at 100.0% when pulling 4685d37edac330ee30ade867978a8a132a2f9c08 on ceyeong:github-actions into 43603654ddb33fd6ad70cfcccbe9420fc7aa5ff9 on slimphp:4.x.

We're currently using Travis for this. Maybe in the future we can move to github actions.


KeyVault: Wrap/Encrypt/Sign

Item out of date, closing as there are no plans in the future for this


Cannot use BOOST_HANA_CONSTANT_ASSERT at class scope. (0.6.0)

Hey, I found a little bug. Clang (3.7.0) fails with error
main.cpp:5:5: error: 'auto' not allowed in non-static class member
    BOOST_HANA_CONSTANT_ASSERT(boost::hana::bool_c<true>, "ERROR");

when using BOOST_HANA_CONSTANT_ASSERT at class scope.
Steps to reproduce:
compile this file:
// main.cpp
#include <boost/hana.hpp>

class a
{
    BOOST_HANA_CONSTANT_ASSERT(boost::hana::bool_c<true>, "ERROR");
};

int main(){}

with this command:
clang++ -std=c++14 -stdlib=libc++ main.cpp -I"<path to boost hana 0.6.0>" -omain

Full compile log is attached.
log.txt

BOOST_HANA_CONSTANT_ASSERT & friends do not allow for an additional error message. I guess this should probably be supported.

@GuapoTaco I'm going to add _MSG versions of the assert macros that allow for a custom failure message. However, BOOST_HANA_CONSTANT_ASSERT may not be used at class scope, because of the way it is implemented. Well in theory you could use it at class scope, but it would add a member to your class, which you definitely don't want. It turns out that it's incredibly hard to come up with a general purpose macro that will work in all cases. It's fairly easy if you don't allow arbitrary variables to be used inside the conditional expression (e.g. BOOST_MPL_ASSERT), but it's much harder for us because the macro should work with local variables and stuff like that.

Basically, for class scope, I would say use static_assert(decltype(condition)::value, ""); if the condition is a Constant.


Fix chevron wrapping on small screens

On the secondary button on cookies banner the chevron will wrap on to the next line on small screens. Solution is to make the secondary button go onto the next line instead and make both buttons span the width of the screen.
This PR also fixes an issue where text on secondary  buttons wasn't centred.

 Issue #655: Cookie settings button wraps chevron to new line on small screens.


Fixed navbar overflow

PR Fixes:

Category navbar overflow

Changed the "All"  button border to be the same as the other categories

Resolves #566
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I assure there is no similar/duplicate pull request regarding same issue

already done in https://github.com/code100x/daily-code/pull/565


Application-specific types are back

New stuff:

Minor refactoring of unstable data types in uavcan.time to facilitate their reuse in future application-specific namespaces. No semantic changes.
Added new SI types for force, torque, and frequency. Torque and frequency are used in the new namespace, force is added for completeness.
Added an application-specific namespace robotics (read below) intended for software-defined vehicular systems at large. The new namespace contains data types for the following applications so far:

ESC, primarily intended for multirotors and other types of electric aircraft.
Smart battery (BMS).

Updated the documentation in the README.

This pull request should resolve the recurring argument about the removal of application-specific data types from the standard set in UAVCAN v1. A few months ago, it prompted Scott to write a FAQ entry specifically about standard data types; also, our presentation at the PX4 dev summit addressed the problem with the help of the following infographic:

Originally, the intent was to arrange regulated application-specific data types (such as BMS messages) in several categories, named profiles, and dedicate a separate namespace to each profile:

Upon a closer assessment, I concluded that a strict separation may be undesirable because the protocol encourages similar approaches to common problems that may be encountered in different application domains. If the original plan was followed, it would likely lead to a noticeable overlap between the functionalities offered by different profiles.
In this PR, I am proposing a modified approach that is closer to the model of a generic robotics framework, where all profile-agnostic functionality is extracted into a generic namespace under a sufficiently generic name. I found robotics to suit the purpose, but new suggestions are welcome. This change does not preclude the addition of profile namespaces later, shall the need arise.
You will notice that the definitions lack fixed port-identifiers. This is by design: excessive reliance on those was one of the major problems in v0. The related issues are briefly explained in the recap of the Stockholm Summit. For the few (very few) types where a fixed port-ID will be found to be desirable one can always be added later, since it does not affect backward compatibility.
Right now, the main objective is to establish the general architecture. Once it is accepted, I am planning to extend the namespace with new commonly needed types such as GNSS positioning messages and related generic geometric types.
I invite the following people to look at the definitions and the namespace design to ensure their adequacy:

Approach and architecture: @thirtytwobits @kjetilkjeka @antoinealb @eshamaev
ESC group messages: @dimracer
BMS messages: @dimracer @AlexKlimaj @igalloway
FYI: @mrpollo

I think we can discuss a generic application profile but I don't think this should be included in the standard. For example, if a system integrator defines their own actuator messages the inclusion of a generic actuator in the set of regulated types will cause confusion. I would rather we move your proposed robotics namespace to a repo which manages public, regulated, but generic types (public_regulated_generic_data_types perhaps?).

I would rather we move your proposed robotics namespace to a repo which manages public, regulated, but generic types (public_regulated_generic_data_types perhaps?).

Indeed, I am aware of the risk of confusion. Here, I attempted to eliminate it by explicitly differentiating between the standard namespace (uavcan) and everything else, as you can see in the diffs for README.md. I am inclined to avoid splitting our definitions across multiple sources (I might have been infected by your monorepo ideas) because the increase in the costs of maintenance is noticeable, whereas the only meaningful difference perceptible to the user is the change of the name from public_regulated_data_types to public_regulated_generic_data_types. Maybe we could save ourselves the effort and take a shortcut by avoiding the split and substitute that with better docs explaining what it is we are really offering here?
Or the namespace could be renamed into something that is less generic-looking than robotics?
We could also make it purely vendor-specific by renaming it into zubax but I am not sure yet about the public-relations and other non-technical implications of this change.

We just had a brief call with @thirtytwobits about this, and we concluded that currently, we are unlikely to be able to define a sufficiently generic and application-agnostic data type library because the UAVCAN development team does not have the required expertise. The updated plan is to move the proposed generic definitions to a new namespace zubax and use it as a stabilization playground. In the future, we may revisit the idea of an application-agnostic profile if there is sufficient interest and the adopters are willing to supply the necessary expertise.

For the battery message. I think the only thing I would add to what you've got is the time remaining message that is in the mavlink smart battery status message.

For the battery message. I think the only thing I would add to what you've got is the time remaining message that is in the mavlink smart battery status message.

@AlexKlimaj Are you saying that a BMS may be able to calculate a substantially better estimate than a subscriber to battery status messages? The proposed interface is built around an estimate of the amount of energy that can be reclaimed from the battery; knowing the available energy and the current power consumption, the time-to-empty can be obtained by a trivial division of one to another.

The change from robotics to zubax is currently staged in a separate branch; will merge it here soon.

Please review.

Okay. I will postpone merging this until we have discussed the regulated namespace management policy with @thirtytwobits and @LorenzMeier.


[mdbook] Disable the Search Index

This PR prevents mdbook from generating searchindex.js and related files. This means that searching the content at http://rust-lang.github.io/rfcs/ will no longer work.
searchindex.js currently contains 38MB(!!) of JavaScript. Even when compressed, that's still around 6MB. Aside from being unreasonably large, this also causes Mobile Safari to crash the tab.
Search functionality is still available on the GitHub repo, so I suggest disabling the search index until its size can somehow be reduced.

r? @rust-lang/docs

Hm, I'm not sure how I feel about this. Disabling it for everyone because of one platform is not ideal.

While I originally noticed this due to the crashing in iOS, I believe that 38MB is unreasonably large for any browser / device. For example, on Desktop Chrome, it takes about ~2 seconds before scrolling works after the initial content is displayed. Also, from Chrome's Performance audit, it spent ~2s to parse and compile the script plus an additional 6.5s(!!) to execute it.

Yeah I mean, I certainly don’t think that it’s a great state of affairs. I wonder why it’s so much larger than say, the book, when I feel like it has significantly less content.

On Jun 11, 2018, at 7:20 AM, Tim Neumann<EMAIL_ADDRESS>wrote:
While I originally noticed this due to the crashing in iOS, I believe that 38MB is unreasonably large for any browser / device. For example, on Desktop Chrome, it takes about ~2 seconds before scrolling works after the initial content is displayed. Also, from Chrome's Performance audit, it spent ~2s to parse and compile the script plus an additional 6.5s(!!) to execute it.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

A first searchindex.js size reduction PR got merged: https://github.com/rust-lang/rust/pull/56709
A few others will follow. :)

@GuillaumeGomez: I don't think https://rust-lang.github.io/rfcs uses rustdoc to render itself, but rather mdbook (which I don't think was affected by your changes).
However there was https://github.com/rust-lang-nursery/mdBook/pull/707, which should have reduced the size of the search index at least somewhat.


ARROW-5860: [Java][Vector] Fix decimal utils to handle negative values.

Padvalue was defaulted to zero
This incorrectly writes negative numbers to buffers.

thanks @praveenbingo


Use partially applied syntax extensively

This is just a show-case of the feature. It's not like I want to merge this -- this is for review & reference only.

Rebased on master


When using http_proxy, can upload an empty action.

This results in errors similar to:
ERROR: $WORKSPACE/$PACKAGE/BUILD:1:1: output '$PACKAGE/lib$TARGET-class.jar' was not created
ERROR: $WORKSPACE/$PACKAGE/BUILD:1:1: output '$PACKAGE/lib$TARGET.jar_manifest_proto' was not created
ERROR: $WORKSPACE/$PACKAGE/BUILD:1:1: output '$PACKAGE/lib$TARGET.jdeps' was not created
ERROR: $WORKSPACE/$PACKAGE/BUILD:1:1: output '$PACKAGE/lib$TARGET-native-header.jar' was not created
ERROR: $WORKSPACE/$PACKAGE/BUILD:1:1: not all outputs were created or valid

when using java rules for example.

I added that check because I kept seeing errors in cached builds, and traced it down to bazel uploading empty files. For example, I was seeing linker crashes as the .o files were (unexpectedly) empty. This was with bazel 0.54, so maybe it can safely be removed now.

I think empty artifacts are ok, especially if they're 0 byte files as opposed to no files at all. They are a valid output after all. Empty actions seem to be the invalid case.

I agree in principle that empty outputs should be ok. However, over tens of thousands of builds with 0.5.4, I've seen bazel mistakenly upload empty files. These errors would show up as linker errors (if the truncated file was an object file), or even compiler errors (if it was a generated header). Any builds that touched the truncated file would fail until the cache was wiped.
Many things have changed in bazel since then, so the bug might very well have gone away.

I added some ActionResult validation a while back which might help catch corrupt action cache files, if they are corrupted by bazel-remote itself. On upload we now make sure that the worker is set in execution_metadata, which makes the serialized data non-empty. Then we check that ActionCache items aren't empty before returning them to the client.
However technically speaking a zero-length ActionResult proto is valid, so we can't reject a zero-sized ActionResult if that's what the client or REAPI worker uploads.

I think we've done all we can here, closing.


Example is missing from the latest.

hash: c97437ea6e371c5e413adc558c5a013dc3d5898d

The vsgimgui example can now  be found in vsgExamples repo /Desktop/vsgimgui

The vsgimgui example can now  be found in vsgExamples repo /Desktop/vsgimgui