Add configurations for Llama 3.1 models(Llama-3.1-8B and Llama-3.1-70B)

Description
This PR introduces new configuration dictionaries for the Llama 3.1 models, specifically the 8B and 70B parameter versions.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] I have not rewritten tests relating to key interfaces which would affect backward compatibility

8b seems to be working perfectly!

My last commit should get the CI to pass. We need to add Instruct, but once that is done, we can close this out!


Guide text tweaks

There should be a way to bring back the guide text after it's been hidden, add a "Show guide" link under the Username/Login/Signup links. Change the color of the "Hide this guide" link to white so it stands out from the text. Change the text "Press Play to open the prompter..." to "Press Open to open the prompter..."

It still says "Press Play" in the guide, it should say "Press Open". Otherwise it's good.


Add option to keep individual stops instead of merging to nodes when importing a GTFS feed

When importing a GTFS feed, neighbouring stops are merged into nodes. This behavior limits the usefulness of the software because it makes it impossible to reliably compare a network before and after a redesign.
An option to keep the individual stops would enable planners to keep track of stop signs that need to be modified after a network redesign.
It would also enable the production of a turn/stop list (see issue 796).

Already implemented with the merge radius = 0? Re-open if you want something different.


Cleanups for VirtualFiles

Updated. I have manually verified with reversi that source maps work in fastOpt. I was unable to verify this in full opt since there is too much inlining.

Just to be sure: Did you see the last commit I added where I remove RelativeVirtualFile?

Updated.


matchAll Polyfill

We've been seeing some client side error logs re .matchAll() calls evaluating to undefined. After a bit of digging, we realized that all of those exceptions originate on older-ish browsers. Nonetheless, this is an issue for us (and I suspect others, too). Specifically, the issue stems from this line: https://github.com/dcastil/tailwind-merge/blob/a703309b6811b8b798b1a8cd2d1db3ac06811b36/src/lib/merge-classlist.ts#L83
I'm curious if you've given thought to adding a matchAll polyfill, or using a different approach to matching?

For a workaround, you could consider using the npm package string.prototype.matchall to polyfill.
It provides a shim, so at the start of your app, I think you could call const matchAll = require('string.prototype.matchall'); matchAll.shim(); to polyfill.
Which browser are you using?

Right -- I've impl'd that polyfill and it seems to work for us. But it took us an hour to realize this was the issue.
I'm able to reproduce this on Chrome 70.x on Mac. It's difficult to run multiple Chrome versions on the same machine, but you can download an old build of Chromium and easily run that side-by-side. Here's the version I'm using: version: 70.0.3538.124
Here's a sample stacktrace, although, the issue is rather straight forward:

Just checked on caniuse and matchAll is available for 93.59% of global users. I'd say for a library like tailwind-merge that probably isn't enough, especially since I think I should be able to replace it easily. I'll implement a fix for this.
@schonfeld out of curiosity, what browsers do you need to support? Do you have a defined policy for that?

Just checked on caniuse and matchAll is available for 93.59% of global users. I'd say for a library like tailwind-merge that probably isn't enough, especially since I think I should be able to replace the functionality easily. I'll implement a fix for this.
@schonfeld out of curiosity, what browsers do you need to support? Do you have a defined policy for that?

I don't really a policy, per se. We typically try to not be bothered by older/out-dated browsers, but this issue seemed to affect a non-negligible portion of our daily users, somewhere in the 200 uniques per day... It seems to affect mostly mobile browsers. I suspect because those are usually tied to OS updates, and some folks are unable to upgrade on older devices...

Okay, that makes sense. Thanks for the info!

@schonfeld you can now <my-favorite-package-manager> add tailwind-merge@dev where matchAll isn't used anymore, so you should be able to remove your matchAll polyfill as well. A v1.6.0 will come in the coming days.

Confirmed working on latest v1.6.0. Thanks so much, @dcastil !


Fix missing newlines in nginx template

This change is only cosmetic but makes the nginx configuration more readable.
Before:
     listen [::]:443 ssl http2;      server_name nc.example.org;

After:
     listen [::]:443 ssl http2;
     server_name nc.example.org;

Hi zorun, thanks for the merge request. I was about to abandon the master branch. I rewrote everything and started a nextcloud-reloaded branch. I'll transfer your improvements there.
Could do your next Mr against the new branch?
Thanks.


Add (boolean) featured to asset database and make it accessable via site-api

^

I am creating this on github because no one reads jira anymore
I don't want to break the database

Just realised it was implemented, but not documented, closing


Laravel 5.5 - Syntax error

Laravel Version: 5.5.32
PHP Version: 7.0
Database Driver & Version:

Description:
After running composer update command, following error occurred:
PHP Parse error:  syntax error, unexpected '?' in /home/apps/auditus/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php on line 233
Following the file and error line:
Helpers.php:
        if (is_string($arguments[0])) {
                return app('cache')->get($arguments[0], $arguments[1] ?? null);
        }

Steps To Reproduce:

I also have the same problem.
PHP 7.1.12
laravel 5.5.0

im getting same issue in web hosting

please help me

@BookNetwork Are you on PHP 7.0+?

im getting same issue in web hosting

I think that you should update your php version.

Even I am also. These issues in local system anyone could help me out


Expected context values

I'm seeing an issue where the assumption in the codebase isn't mapping to what I'm seeing when using the code inside Django. Specifically, the JSONWebTokenMiddleware makes the assumption that the provided info.context will always equal a Django-like HttpRequest object. In practice, I'm seeing two different behaviors:

info.context is a dictionary with a request key that is the request object
The request object is not always an HttpRequest-like object. I'm seeing starlette.requests.Request coming from Ariadne.

I've got a branch of code off of #1 that contains fixes to the tests to account for these differences, but I wanted to check with you before opening another PR (or merging in to #1). Am I seeing different behavior than what you see / expect when you're using this code?

Oh, the code is at in the branch fix/support-ariadne-requests if ya care to see. Here's the diff.

Hey @tswicegood, I haven't found any other request type. What type of server are you using?

@marco-btree I'm using the base ariadne.asgi.GraphQL (with the __call__ modification outlined in here: https://github.com/mirumee/ariadne/issues/210#issuecomment-508424149) and Django's runserver configured with an ASGI app. From my reading of the code, the handle_http method creates the request object using starlette.requests.Request here.
I've been using the code in that branch daily now this whole week with a configuration that looks like:
application = ProtocolTypeRouter(
    {
        "websocket": AuthMiddlewareStack(
            URLRouter(
                [
                    re_path(
                        r"graphql/?",
                        DjangoChannelsGraphQL(
                            schema, middleware=[JSONWebTokenMiddleware()], debug=True
                        ),
                    )
                ]
            )
        ),
        "http": AuthMiddlewareStack(
            URLRouter(
                [
                    path(
                        "graphql/",
                        DjangoChannelsGraphQL(
                            schema, middleware=[JSONWebTokenMiddleware()], debug=True
                        ),
                    ),
                    re_path(r"", AsgiHandler),
                ]
            )
        ),
    }
)

Without the changes in that diff (which have expanded since opening this ticket), I can't get this running in an ASGI server.

I run into the same issue with the Django v3.1.4 development server (python manage.py runserver).

I run into the same issue with the Django v3.1.4 development server (python manage.py runserver).


WIP: param support for v2

Check below docs for objective and design: oso_proxy_v2
Tasks:

[X] support type, space, w param
[X] tests for new param
[x] enhancement in cache behavior
[ ] optimize namespace_cache wrt in-memory usage

Fixes: https://openshift.io/openshiftio/openshift_io/plan/detail/444

[test]

@nurali-techie @alexeykazakov could we possibly include identity_id as a parameter for oso_proxy_v2? This would allow to have all the osio specific parameters to be passed in a centralized manner and avoid (mis)using query parameters / headers ?

@ibuziuk identity_id is application_level param (i.e. che).  the param which we are including in oso_proxy_v2 (i.e type, spaceid, w) are osio_level params which will be set by multiple service.  So identity_id is not right fit here.  Also, we are seriously looking forward to get rid of identity_id in oso_proxy code.

Also, we are seriously looking forward from che_team to remove identity_id from oso_proxy code

@nurali-techie what do you mean by that ? how oso_proxy would identify user in that case ?

identity_id is application_level param (i.e. che)

Sorry, I did not get the point. identity_id is not che specific parameter

@ibuziuk yup, identity_id is needed (or Impersonate-User) to identify user.  My bad.
I was referring to get rid of adhoc url format to support identity_id.
For now, I have added todo/task in this issue desc to check if identity_id param can be part of path_segment.  We will evaluate and update here.

@nurali-techie passing identity_id header seems to work just fine with the latest version of che, so there is no need to investigate possibility of passing identity_id via path_segment, since we would simply fall back on the initial approach with Impersonate-User header for passing the identity from che to oso-proxy. Also, please find a PR [1] for removing support of the query parameters on oso-proxy side.
[1] https://github.com/fabric8-services/fabric8-oso-proxy/pull/44

@ibuziuk thanks for the update, I have removed TODO item from desc for the same.

This PR is on Hold for now and will be resume when start integration between oso-proxy, tenant and env service for OSD stuff.

@alexeykazakov as we are no more working on OSIO on OSD these changes are not needed any more, closing this PR.


NIFI-13799 Improve Replicated Cluster Response Handling

Summary
NIFI-13799 Improves replicated HTTP response handling for requests to cluster nodes, avoiding potential heap exhaustion when downloading large FlowFiles.
Instead of buffering the entire response body, the updated approach buffers responses with known content length values that are less than 1 MB. For streamed responses with an unknown content length, or large responses, the replication client returns the HTTP response stream. The changes also include a close callback to ensure that the replicated response stream is closed.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for fixing that @exceptionfactory! Code changes look good, even a little bit of obvious cleanup that was necessary, likely that was missed during some old refactoring :) Was able to run some tests as well, and everything is checking out on my end. +1 will merge to main!


Is there anyway to make the redis commander readonly to redis db or setup a password to visit?

If I public the redis commander 8081 port to the public net, everyone can come and modify my db. Currently, I do not want to setup a password to my db because I have to do extra work on my API.
So, it there anyway to setup an account in redis commander? or simply disable writing permit in redis commander's configure?

It should support http auth
 --http-auth-username, --http-u  The http authorisation username.   [string]
 --http-auth-password, --http-p  The http authorisation password.   [string]

another issue with read-only mode request #341

Hi, i updated redis-commander to allow starting in read-only mode. It would be nice if someone could give it a try and check if its working as expected or if i missed something...
Currently only in git branch read-only-mode, no Docker images. Thought some more test might be good before merging...
Feedback welcome!

merged it into master, docker image with read-only support will show up soon...

Version with read-only mode release to npm too (0.6.3).
Now you can either add HTTP-Authentication and/or set Redis-Commander to read-only mode. If you find some problems with latest version, please create a new issue.
Thanks


Cannot install version 5.10.x anymore without explicitly forcing package manager to resolve @mui/system to version 5.10.x

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Steps:

Create a new project and explicitly install a 5.10.x version i.e. yarn add<EMAIL_ADDRESS>@emotion/react @emotion/styled
Add a <Button>Hi</Button> into the app
Try to start the app and enjoy the following:

✘ [ERROR] No matching export in<EMAIL_ADDRESS>for import "experimental_sx"

    node_modules/@mui/material/esm/styles/index.js:2:154:
      2 │ ...omposeColor, recomposeColor, getContrastRatio, getLuminance, emphasize, alpha, darken, lighten, css, keyframes, experimental_sx } from '@mui/system';
        ╵                                                                                ~~~~~~~~~~~~~~~

(node:31769) UnhandledPromiseRejectionWarning: Error: Build failed with 1 error:
node_modules/@mui/material/esm/styles/index.js:2:154: ERROR: No matching export in<EMAIL_ADDRESS>for import "experimental_sx"

Current behavior 😯
The MUI packages are deployed with dependencies of "@mui/system": "^5.10.10" which means that at the time the consumer installs the package, go and grab the latest version of @mui/system that starts with a major version of 5.
The issue here is that breaking changes were introduced in version 5.11.0, and now anyone trying to install an older version will get the above error.
Expected behavior 🤔
I would expect that a library should be able to be reliably installed at any version, at any point. This could be achieved in a couple of different ways.

don't use floating version numbers (i.e. remove all ^ out of your package.json so that 5.10.10 will always install @mui/system 5.10.10).
follow proper semantic versioning and do not introduce breaking changes on minor increments if you're intent on leaving floating version numbers on dependencies.

There is a workaround (at least for yarn users, not sure about other package managers) which is make use of the resolutions field in the package.json to force an explicit version of the package. However, this is obviously just a bandaid and not a root cause fix.
resolutions: {
  "@mui/system": "5.10.10"
}

Context 🔦
I manage a component library internally at my company which is built on top of @mui/material and have requirements of version locking for a whole slew of reasons. The 5.11.0 release has caused people installing the internal component library (which is locked on version 5.10.10) to observe the failure specified.
It appears that you are incrementing all of your versions on each release already, I would suggest you just remove the ^ from all of your listed dependencies moving forward so that any future release depends on the explicit version and only that version so that this type of thing cannot happen again in the future.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Linux 5.14 Ubuntu 20.04.5 LTS (Focal Fossa)
  Binaries:
    Node: 14.20.0 - /usr/bin/node
    Yarn: 1.22.15 - /usr/bin/yarn
    npm: 6.14.17 - /usr/bin/npm
  Browsers:
    Chrome: 104.0.5112.101
    Firefox: 107.0
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5
    @emotion/styled: ^11.10.5 => 11.10.5
    @mui/base:  5.0.0-alpha.102
    @mui/core-downloads-tracker:  5.11.0
    @mui/material: 5.10.10 => 5.10.10
    @mui/private-theming:  5.11.0
    @mui/styled-engine:  5.11.0
    @mui/system:  5.11.0
    @mui/types:  7.2.3
    @mui/utils:  5.11.0
    @types/react: ^18.0.26 => 18.0.26
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.9.3 => 4.9.4

I've been facing the same problem for a day, and with the following configuration (based on your suggestion) it was possible to deploy my app:
npmPackages:
  @emotion/react: 11.10.5
  @emotion/styled: 11.10.5
  @mui/icons-material: 5.10.9
  @mui/lab: 5.0.0-alpha.90
  @mui/material: 5.10.10
  @mui/styles: 5.10.10
  @mui/system: 5.10.10

Removing the possibility of having superior compatible versions is really necessary: ^version -> version
tnks @jereklas

Can you try the latest release 5.11.0?

Yes, installing 5.11.0 works fine, but that's not the point of the defect.  The defect is that 5.11.0 has broken all previous versions of 5 that someone might explicitly want to install, and there's a several reasons why someone might want or need to install a slightly older version of the library.

This PR fixes the breaking change, but doesn’t address the fact that keeping floating versions will potentially re-introduce a similar defect in the future. What steps are being taken to not allow this blatant failure to happen in the future?

What steps are being taken to not allow this blatant failure to happen in the future?

Any APIs that are planned to be removed will be done in the next major version only.


Where to find the folder to configure settings in mac (for pikabot)

https://github.com/PokemonGoF/PokemonGo-Bot-Desktop/issues/160#issuecomment-239537209


fix: dbt 1.5 compatibility

Fixing an error resulting from a change in the dbt api.
The following change resulted in the project path not passed properly to the get_nearest_project_dir() function in dbt-inbokes get_project_info().
change in dbt-core: https://github.com/dbt-labs/dbt-core/pull/6260/files#diff-ff72c0336d261308d5c769be4c470c64866a7ff8a860446e69650ad288259edaL143-R154
function affected in dbt-invoke: https://github.com/Dashlane/dbt-invoke/blob/main/dbt_invoke/internal/_utils.py#L109
Unpacking the project_dir variable before the function call should do the trick.

@ciklista thanks for the PR! (and sorry for the delay as I was away). Looks good!


Augur V2 fully local deployment

Hi, recently I would like to fully deploy Augur locally, including smart contracts (on geth private chain), augur-node and augur-ui, in order to inspect the source code. I noticed that there is a tutorial here about "running everything locally". However I tried that tutorial and found it is for Augur V1 instead of V2.
So my question is: how can I "run everything of Augur V2 locally"?
Thanks in advance.

There is a docker with the contracts deployed already. Pull down the augur mono repo < https://github.com/AugurProject/augur>
yarn
yarn build
To start docker yarn docker-all
Then you have a geth node with augur v2 contracts already deployed.

Thanks for response. Is there a way to deploy contracts by myself?

@bthaile Is Augur V2 still using augur-node as centralised database to store data? I didn't see it in the AugurProject/augur/packages


[RFC] New tokenizer code

Instead of searching through the input entirely character-wise in PHP userland, we could let strcspn() do the job. Runtimes of the testsuite greatly fail to reflect this, but this is great for longer, more complex input.

lgtm besides some style nitpicking

Just addressed the style issues in 0a52d00 and 87e2c8e


Eventually integrating openstreetmap-mapboxgl

I'd like to get your feedback on eventually integrating openstreetmap-mapboxgl into osm2vectortiles and maintaining it as a separate tile schema and style from the rest of osm2vectortiles? It doesn't even have to be part of official vector tiles you host, just have it part of master.
My branch of osm2vectortiles (openstreetmap-style) adds generate-tm2source and import-osm2pgsql as docker containers. import-osm2pgsql imports the PBF using osm2pgsql and gets the official shapefiles for lower zooms. It follows the switch2osm build path.
generate-tm2source gets a copy of https://github.com/stirringhalo/openstreetmap-carto-vector-tiles and generates the appropriate .yml with the database access settings, etc. The tile schema overall follows the openstreetmap-carto one very closely (with minor changes from https://github.com/geofabrik/openstreetmap-carto-vector-tiles which actually kicked this off). The only significant changes I am adding are a combined roads layer to ease later rendering. I am waiting on a few rendering/styling issues before it goes fully 100%.
Styling-wise, I am doing a simplified openstreetmap-carto with no pattern fills on polygons and missing some minor layers. My next major focus is proper road stacking, which is non-trivial (and in fact not even Mapbox itself gets 100% correct at times esp. on tunnels).
Thoughts?

My next major focus is proper road stacking, which is non-trivial (and in fact not even Mapbox itself gets 100% correct at times esp. on tunnels).

Abandon all hope before looking at the roads code ;) The roads MSS is about 40% of osm-carto, and a significant portion of the SQL. It tries to get everything right, more so than any other style out there. There are a grand total of approximately zero people who fully understand it.
I would add that I think the osm-carto queries are badly suited for server-side vector tile rendering and worse for client-side vector tile rendering, but if you can get it working well I applaud your work.

Abandon all hope before looking at the roads code ;) The roads MSS is about 40% of osm-carto, and a significant portion of the SQL. It tries to get everything right, more so than any other style out there. There are a grand total of approximately zero people who fully understand it.

Ha! I've been diving into how osm-carto interacts with the SQL selections. I think I get it, sorta...ish. :confused:
I have a plan for getting it to work, most of the hiccups are with Mapbox Style Spec. There's some new property functions that are in the works for lines. Just waiting for line-dasharray to be supported for property functions. The roads SQL will be majorly hacked up from the original, it's the only one that needs to be.

I would add that I think the osm-carto queries are badly suited for server-side vector tile rendering and worse for client-side vector tile rendering, but if you can get it working well I applaud your work.

They aren't actually half bad. Speeds for one worker are about 50-60 tiles per second for Switzerland. IIRC that's in the range of my planet builds using OSM2VectorTiles.

It tries to get everything right, more so than any other style out there

I politely disagree ;-)
There is at least one other style and renderer that gets about everything right, and that is the one I developed from the ground up for ArcGIS, and yes, there is a grand total of one person that understands it...
But there ends the joke, because I do share and understand your pain: it is hard!
For my ArcGIS renderer, I partly took the sting out of it, by making optimal use of ArcGIS's options like Symbol Level drawing to first stack the road types in a meaningful order, and then use the ability to re-order ArcGIS Table Of Contents thematic layers to fully automatically and dynamically stack them according to the OSM "layer" key.
This required some really hard thinking though, of what that program code should look like (which I developed in Python using ArcGIS's "arcpy" package), and a considerable amount of frustration to get it right and fix the bugs (and the logic). The final code stacks ArcGIS thematic layers, each representing a single OSM "layer" value, where each thematic layer defines all road types, and can even do this for multiple different thematic layers developed for different zoom levels (and even man_made=bridges).
The final ordering code that moves the thematic layers around in ArcGIS's TOC is quite elegant and not extremely long.
Below is a nice - but special case! - example. It is special, because the same code that drives the stacking and ordering for normal linear ways, has been used here to additionally stack OSM's area:highway=x features, which are Polygon representations of road surfaces. You can even see it correctly stacking normal "linear" roads, and two tram ways (the thin black lines running below the viaduct) in a mix of these feature types.
The corresponding carto rendering (only based on linear way objects) - also looking good and technically correct by the way! - can you view via this link:
https://www.openstreetmap.org/search?query=szczecin#map=17/53.42584/14.56509

@mboeringa
Wow, very nice looking. I agree 100% it's a pain in the ... . I actually just got it working properly with Mapbox GL JS and Openstreetmap tile schema.
Still lots of work to be done to make it zoom dependent widths and including railroads+paths (which at this point don't work the best with the approach I have) but stacking works 100%, even when it gets really hairy in the stacking!!
Keep an eye on http://<IP_ADDRESS>/ in the next day or two for the latest developments.

I would actually prefer to see it in a seperate repository inside OSM2VectorTiles instead of of two ways go generate vector tiles in the master branch.

Okie dokes!

I think it fits perfectly into the organization because it "turns OSM into vector tiles" but is a different approach (but one I really appreciate and am very happy to see realized!!).
I would like to keep it under the OSM2VectorTiles umbrella but as you wish. You can also take it to your own repo if you want.

I'm very happy to move it into the OSM2VectorTiles organization. I will do so once I have the road styling more complete. I have just figured out how to do proper road stacking, still need to figure out tracks but that should be mostly straight-forward!

We can even promote it on the website etc. since I like it but it kind of a different project we started here although using the same approach.
Whether we will prerender them and how to serve them will be a different topic :grin:
But perhaps we find someone to sponsor a rendering.

I can do the rendering :smile: I have a machine to do it on. I can upload a rendering, probably on a monthly interval.
At this stage I am using the line2 branch of mapbox-gl-js as I need the data property functions for lines so I can properly do roads.


changes time to 5 hours ahead

Hello and thank you for the awesome plugin. I was hoping you could help me with an issue I am having. The code adds 5 hours to the time before hitting the database. I am using a php restful api with MySql db. Is there a config setting to account for this and if so can you give me an example.
Again thank you so much...
God bless
jason

Please post a fiddle, plunker, or jsbin that demonstrates the problem

I don't know how to put this in a fiddle or plunkit. It is online, I can give you access to the system with instructions on how to repeat it

I think I figured out a solution. for whatever reason my system is adding 5 hours so I set the timezone in php to my timezone and it corrected the issue. My only concern is when I have a client using this system in a different time zone

Okay, it sounds like this directive is working correctly.


Fix #335: Shell unsigned pkt length bug

Describe the contribution
Fix #335
Really just avoids problems if users mistakenly define CFE_MISSION_ES_MAX_SHELL_PKT as an unsigned value (2000u, for example)
Testing performed
Steps taken to test the contribution:

CI

Suggest requester (@krmoore) confirm it works as requested
Expected behavior changes
None, except if someone defines this value as unsigned it won't break...
System(s) tested on

Hardware: AMD
OS: Ubuntu 18.04
Versions: bundle + this change

Additional context
None
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB 20200415 - APPROVED


_warn() is broken

Here's how it looks like if I call _warn() in the console (In my app it's called from somewhere inside neon animation). As you can see it's broken for some reason. How did THIS slip through the unit tests? :) I'm using<EMAIL_ADDRESS>

Hm, seems like they merged and released code that relies on code which is in Polymer master but not yet released to public.

Yah, that sounds right. I hope that this is fixed soon. I can't upgrade polymer in my app because of this :(

This has been fixed since and the elements have been updated to reflect this change.


Refactor github workflows

Purpose

$subject.

Codecov Report

Merging #23579 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #23579   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 c2c976f...0ef9e1b. Read the comment docs.


Some patches to edison-image.bb (nano editor etc. etc.)

Thanks, I'll have a look this weekend.

I applied these to master and warrior, thanks!


R3Name/SID can not be defined

Hi,
I could not find a way to define the  R3NAME/ SID / SYSID or whatever the correct name would be.
At least it's not in the stub so I dont know if this value could still be set?
Could you help me with this?
Thank you for the nice work!

The supported connection settings are linked from the documentation: Connecting to a SAP system


[Enhancement] Invert default value of xct:TouchEffect.ShouldMakeChildrenInputTransparent

Summary
Adding an xct:TouchEffect.NativeAnimation="True" in your visual hierarchy prevents touch events from working inside said element. This forces one to also always add an xct:TouchEffect.ShouldMakeChildrenInputTransparent="False" statement when a 'NativeAnimation' statement is added.
This is error prone, cumbersome, and may scare off new users as their app's logic will break without realising this has to be done.
API Changes
Change xct:TouchEffect.ShouldMakeChildrenInputTransparent's default value to "False" instead of "True".
Blocking child input is imho definitely a feature that should be opt in and not opt out.
Intended Use Case

Who Will Do The Work?

[ ] I am willing to take this on myself
[X] Just putting this out there for someone to pick up

That makes sense. @AndreiMisiukevich what do you think? Was this done with a certain reason behind it?
This is a breaking change though, so we should definitely target our vNext version.

That makes sense. @AndreiMisiukevich what do you think? Was this done with a certain reason behind it?
This is a breaking change though, so we should definitely target our vNext version.

I definitely did it for some reason :)
But I don't remember it LoL

Found it.
I did it because of the Android issue. (I will make a recording)

https://user-images.githubusercontent.com/10124814/107285408-668ebd00-6a5f-11eb-9da1-b6b18d6aa96d.mp4

@Tommigun1980 if you wish, I can add bool? DefaultShouldMakeChildrenInputTransparent property for setting this value only once.

Closing this issue because otherwise, unfortunately, it won't work fine on Android (at least on Android)

@AndreiMisiukevich Does this mean that Android isn’t compatible with the effect then?
I mean you have to set the flag to False in order not to break input, and you’re saying setting it to False doesn’t work on Android?
Shouldn’t this be fixed?
Thank you.

@Tommigun1980 I don't think that Android isn’t compatible with the effect.
This effect allows creating complex touchable layouts.
Of course, it would be great if we could fix it, but I am not sure that it's possible. (By default XF views on an android intercept gestures as you can see on the video).

Any reason the default can't be not to block child input if it works on
Android? I'm not sure I'm seeing the point.
The default to block input breaks most controls. If it can be turned off on
Android why not make it the default? If it can't be turned off on Android
it's going to be very hard to use, no?
All I want to use it for is to add a touch highlight on arbitrary controls.
Thank you again.
On Mon, Feb 15, 2021 at 4:38 AM Andrei<EMAIL_ADDRESS>wrote:

@Tommigun1980 https://github.com/Tommigun1980 I don't think that
Android isn’t compatible with the effect.
This effect allows creating complex touchable layouts.
Of course, it would be great if we could fix it, but I am not sure that
it's possible. (By default XF views on an android intercept gestures as you
can see on the video).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xamarin/XamarinCommunityToolkit/issues/852#issuecomment-778902261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOL6P6E23W7SLU5FXFG5MDDS7CCLZANCNFSM4XHAI2XA
.

@Tommigun1980 please check the video I attached above.
The problem is that it doesn't work on Android if we don't block children's input.
As you can see on the video, the control's state remains "pressed" even if touch is released in case the touch was started on some child inside the "touchable" view.

@AndreiMisiukevich seems there is some issue on IOS too.
As you said, on Android the view stays in the "pressed" state if you do a press and move the cursor out of that view.
But when testing on iOS I found the parent view is receiving the click even though ShouldMakeChildrenInputTransparent is set to false.
I have a Grid → Grid → Switch. The command is set on the first grid and when you click the Switch the Grid's command is executed.

@jpozo20 yeah. I don't know how to fix that to have it as "common" solution.

@AndreiMisiukevich I feel you, I was reading the code to understand how to replicate it and yeah it's a bit complicated.
I managed to do the ripple animation by creating an Effect and letting Android do the animation with a StateListDrawable. But seeing how much trial and error I had to do, I don't see it very feasible to modify the current code in the TouchEffect since it seems you're actively managing the animation of the drawable (maybe due to the available properties?).


demo_video.py error

Loading model from D:\PythonProjects\HybrIK\pretrained_w_cam_res50.pth...
Traceback (most recent call last):
File "D:\PythonProjects\HybrIK\scripts\demo_video.py", line 101, in
hybrik_model.load_state_dict(torch.load(CKPT, map_location='cpu'), strict=False)
File "C:\Users\hanzhao\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 1667, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for Simple3DPoseBaseSMPLCam:
size mismatch for init_cam: copying a param with shape torch.Size([3]) from checkpoint, the shape in current model is torch.Size([1]).
size mismatch for preact.layer1.0.conv1.weight: copying a param with shape torch.Size([64, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([64, 64, 1, 1]).
size mismatch for preact.layer1.1.conv1.weight: copying a param with shape torch.Size([64, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([64, 256, 1, 1]).
size mismatch for preact.layer1.2.conv1.weight: copying a param with shape torch.Size([64, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([64, 256, 1, 1]).
size mismatch for preact.layer2.0.conv1.weight: copying a param with shape torch.Size([128, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 256, 1, 1]).
size mismatch for preact.layer2.0.downsample.0.weight: copying a param with shape torch.Size([128, 64, 1, 1]) from checkpoint, the shape in current model is torch.Size([512, 256, 1, 1]).
size mismatch for preact.layer2.0.downsample.1.weight: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for preact.layer2.0.downsample.1.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for preact.layer2.0.downsample.1.running_mean: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for preact.layer2.0.downsample.1.running_var: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for preact.layer2.1.conv1.weight: copying a param with shape torch.Size([128, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 512, 1, 1]).
size mismatch for preact.layer2.2.conv1.weight: copying a param with shape torch.Size([128, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 512, 1, 1]).
size mismatch for preact.layer2.3.conv1.weight: copying a param with shape torch.Size([128, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 512, 1, 1]).
size mismatch for preact.layer3.0.conv1.weight: copying a param with shape torch.Size([256, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 512, 1, 1]).
size mismatch for preact.layer3.0.downsample.0.weight: copying a param with shape torch.Size([256, 128, 1, 1]) from checkpoint, the shape in current model is torch.Size([1024, 512, 1, 1]).
size mismatch for preact.layer3.0.downsample.1.weight: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for preact.layer3.0.downsample.1.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for preact.layer3.0.downsample.1.running_mean: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for preact.layer3.0.downsample.1.running_var: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for preact.layer3.1.conv1.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 1024, 1, 1]).
size mismatch for preact.layer3.2.conv1.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 1024, 1, 1]).
size mismatch for preact.layer3.3.conv1.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 1024, 1, 1]).
size mismatch for preact.layer3.4.conv1.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 1024, 1, 1]).
size mismatch for preact.layer3.5.conv1.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 1024, 1, 1]).
size mismatch for preact.layer4.0.conv1.weight: copying a param with shape torch.Size([512, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 1024, 1, 1]).
size mismatch for preact.layer4.0.downsample.0.weight: copying a param with shape torch.Size([512, 256, 1, 1]) from checkpoint, the shape in current model is torch.Size([2048, 1024, 1, 1]).
size mismatch for preact.layer4.0.downsample.1.weight: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for preact.layer4.0.downsample.1.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for preact.layer4.0.downsample.1.running_mean: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for preact.layer4.0.downsample.1.running_var: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([2048]).
size mismatch for preact.layer4.1.conv1.weight: copying a param with shape torch.Size([512, 512, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 2048, 1, 1]).
size mismatch for preact.layer4.2.conv1.weight: copying a param with shape torch.Size([512, 512, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 2048, 1, 1]).
size mismatch for deconv_layers.0.weight: copying a param with shape torch.Size([512, 256, 4, 4]) from checkpoint, the shape in current model is torch.Size([2048, 256, 4, 4]).
size mismatch for fc1.weight: copying a param with shape torch.Size([1024, 512]) from checkpoint, the shape in current model is torch.Size([1024, 2048]).
size mismatch for deccam.weight: copying a param with shape torch.Size([3, 1024]) from checkpoint, the shape in current model is torch.Size([1, 1024]).
size mismatch for deccam.bias: copying a param with shape torch.Size([3]) from checkpoint, the shape in current model is torch.Size([1]).
Process finished with exit code 1

Do you fixed it? I encountered the same issue

problem solved. use the last model in model zoo instead of others.

problem solved. use the last model in model zoo instead of others.

@Ajatar213455 can u explain more? thanks.

I encountered the same issue,Do you fixed it?

problem solved. use the last model in model zoo instead of others.问题解决了。使用模型动物园中的最后一个模型而不是其他模型。which model？


Update CORS configuration instructions

Issue #, if available:

Outdated instructions

Description of changes:

Because the AWS Console interface no longer allows users to input XML objects, I updated the instruction to include a JSON array.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can approve this pr :-)

Thanks for this @baoc75 !
This tutorial is still useful, it would be awesome if a maintainer would merge this!


Add a gitattributes file to specify auto CRLF

Since almost all files not on our gitignore are text files, it uses * text as a catch-all and specifies *.png as binary.

It would probably make WSL more foolproof to not use auto and just use unix file endings, idk, how would y'all feel about that?


[ENH] Adjust conf.py to target myst_parser, myst_nb?

Currently we have target_jupytext for enabling execution. This is an obscure reference as jupytext is probably not known users of the extension. An alternative would be to link directly to myst_parser and myst_nb as the config setting.
tomyst_parser = 'myst_parser'

for static builds of projects
tomyst_parser = 'myst_nb' (default)

to enable execution and build myst compatible with automatic jupytext conversions.

closed by PR #69


Fix "cannot range over" local lint errors

With the #122 local error on the make lint
appeared. This is not visible in the CI, however local go version and lint version are the same, so may be associated with other dependent libraries.
Still this is an issue when submitting a PR from the system where this linting error is visible.
For error message and insights:
https://github.com/migtools/oadp-non-admin/pull/122#issuecomment-2515304578
Why the changes were made

To fix local $ make lint errors introduced with #122
How to test the changes made

Ran the lint after change, no error appeared.

Was it even working? I don't think golang allows range over int.

I think we may have CI github action lint br8ken or some wired casting which github lint doesn't understand. Wired is that @mateusoliveira43 can not reproduce this error, where I can on a fresh clone without go deps pre-cached.

https://stackoverflow.com/a/21951131

That is the problem
I am using
$ ./bin/golangci-lint-v1.56.2 --version
golangci-lint has version v1.56.2 built with go1.22.6 from (unknown, mod sum: "h1:dgQzlWHgNbCqJjuxRJhFEnHDVrrjuTGQHJ3RIZMpp/o=") on (unknown)

https://github.com/golangci/golangci-lint/blob/794a340e63eb3c76cd904e590b5909c6c7e132d4/pkg/golinters/typecheck.go#L10

https://github.com/golangci/golangci-lint/issues/4459 says to use 1.56.0 built with go1.22

Can we fix linter instead of working around linter?

https://github.com/migtools/oadp-non-admin/blob/27679313ad6e7b4eaf53e59f3e0ae5a30947523a/go.mod#L86
is this being followed up later?

I favor #126 let's close this one.


Automated cherry pick of #1667: fix: task usercred should be utf8 charset

Cherry pick of #1667 on release/2.11.0.
#1667: fix: task usercred should be utf8 charset

/lgtm
/approve

Codecov Report

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

@@               Coverage Diff                @@
##             release/2.11.0   #1671   +/-   ##
================================================
  Coverage                  ?   7.65%
================================================
  Files                     ?     412
  Lines                     ?   63096
  Branches                  ?       0
================================================
  Hits                      ?    4832
  Misses                    ?   57855
  Partials                  ?     409

Flag
Coverage Δ

#aFlag
7.65% <ø> (?)

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 5e5dd79...314e6d8. Read the comment docs.


Not able to download 10.7 bootstrap installer

I’m trying to automate command central 10.7 setup.  I’m receiving below error. Can you help confirm if 10.7 bootstrap installer is available?
The

https://github.com/SoftwareAG/sagdevops-cc-server/tree/release/107oct2020

in the default.properties, I have to change installer.url from http to https. The issue is resolved.
installer.url=http://empowersdc.softwareag.com/ccinstallers

in the default.properties, I have to change installer.url from http to https. The issue is resolved.
installer.url=http://empowersdc.softwareag.com/ccinstallers

Thank you for pointing this out! The default value is now changed.


Release plan for 2018.4.0

Helpful links & info:

Milestone

Schedule
Monday, Apr 02

[x] Go through telemetry for GDPR
[x] Go through all merged pull requests and add the validate fix label as appropriate as well as checking for news entries

Planning

[x] Evaluate if TypeScript usage needs updating to sync with VS Code's usage
[x] Evaluate projects & meta issues
[x] Go through needs PR issues to see if there's anything we want to add to this milestone
[x] Finalize the initial set of issues for the milestone
[x] Make sure all issues for this milestone are assigned
[x] Close issues that have needed more info for over a month

Monday, Apr 09

[x] Go through telemetry for GDPR
[x] Check if there have been no performance regressions
[x] Go through all merged pull requests and add the validate fix label as appropriate as well as checking for news entries

Monday, Apr 16

[x] Go through telemetry for GDPR
[x] Go through all merged pull requests and add the validate fix label as appropriate as well as checking for news entries

Monday, Apr 23

[x] Go through telemetry for GDPR
[x] Go through all merged pull requests and add the validate fix label as appropriate as well as checking for news entries

Get legal details started

[x] Announce the lock-down of dependencies for this release
[x] Notify CELA of all changes to the repository and distribution dependencies

Release a beta version for testing

[x] Update the version to be a beta & update the changelog
[ ] Announce the beta development build (along with how to help validate fixes)
[x] Open appropriate documentation issues

Monday, Apr 30

[ ] Go through telemetry for GDPR
[ ] Go through all merged pull requests and add the validate fix label as appropriate as well as checking for news entries

Prep for the release candidate

[ ] Announce feature freeze
[ ] Make sure the repo and distribution TPNs have been updated appropriately
[ ] Ensure all new feature usages are tracked via telemetry
[ ] Make sure no extraneous files are being included in the .vsix file
[ ] Merge any last-minute pull requests

Test the release candidate code

[ ] Update the version to be an rc & update the changelog
[ ] Announce the release candidate development build
[ ] Open appropriate documentation issues
[ ] Begin drafting a blog post

Prep for releasing

[ ] Get team agreement that the code is ready to be released
[ ] Update the changelog (including the names of external contributors)
[ ] Update the version number to be final
[ ] Make sure CI is passing
[ ] Create the release- branch
[ ] Generate final .vsix file from the release- branch
[ ] Make sure the appropriate pull requests for the documentation -- including the WOW page -- are ready

Start preparing for the next release

[ ] Bump the version number to the next alpha
[ ] Make sure the next two milestones exist
[ ] Lift the feature freeze
[ ] Create a new release plan

Clean up after this release

[ ] Clean up any straggling fixed issues needing validation
[ ] Close the (now) old milestone
[ ] Delete the previous releases' branch

Wednesday, May 02 (hopefully 😉)

[ ] Upload the final .vsix file to the marketplace
[ ] Publish documentation changes
[ ] Publish the blog post
[ ] Create a release on GitHub (which creates an appropriate git tag)

I'm assuming we'd assign one section (e.g. Linting) to one person.

Test plan
Environment

OS: Windows 10
Python

Distribution: CPython
Version: 3.7.0b3

Tests
ALWAYS check the Output window under Python for logged errors!
Environment
Interpreters

[ ] Interpreter is shown in the status bar
[ ] An interpreter can be manually specified using the Select Interpreter command
[ ] Detected system-installed interpreters
[ ] Detected an Anaconda installation
[ ] (Linux/macOS) Detected all interpreters installed w/ pyenv detected
[ ] "python.pythonPath" triggers an update in the status bar
[ ] Run Python File in Terminal
[ ] Run Selection/Line in Python Terminal

Virtual environments
ALWAYS create environments with a space in their name.*

[ ] Detected a single virtual environment at the top-level of the workspace folder

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses --user
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] Detect multiple virtual environments in a directory specified by "python.venvPath"
[ ] Detected all conda environments created with an interpreter

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint installs into the conda environment
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS until -m is supported) Detected the virtual environment created by pipenv

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses pipenv install --dev
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS) Detected virtual environments created under {workspaceFolder}/.direnv/python-{python_version} for direnv and its layout python3 support

[ ] Appropriate suffix label specified in status bar
[ ] "python.terminal.activateEnvironments": false deactivates detection

Environment files
Sample files:
# example.py
import os
print('Hello,', os.environ.get('WHO'), '!')

# .env
WHO=world

[ ] Environment variables in a .env file are exposed when running under the debugger
[ ] "python.envFile" allows for specifying an environment file manually

Debugging

[ ] pythonPath setting in your launch.json overrides your python.pythonPath default setting

Linting
ALWAYS check under the Problems tab to see e.g. if a linter is raising errors!
Pylint/default linting
[Prompting to install Pylint is covered under Environments above]
For testing the disablement of the default linting rules for Pylint:
# pylintrc
[MESSAGES CONTROL]
enable=bad-names

# example.py
foo = 42  # Marked as a blacklisted name.

[ ] Installation via the prompt installs Pylint as appropriate
[ ] Pylint works
[ ] "python.linting.pylintUseMinimalCheckers": false turns off the default rules w/ no pylintrc file present
[ ] The existense of a pylintrc file turns off the default rules

Other linters

[ ] flake8 works
[ ] mypy works
[ ] pydocstyle works
[ ] pep8 works
[ ] prospector works
[ ] pylama works
[ ] 3 or more linters work simultaneously

[ ] Run Linting runs all linters
[ ] The Select Linter command lists all the above linters and prompts to install a linter when missing
[ ] "python.linting.enabled" disables all linters
[ ] The Enable Linting command changes "python.linting.enabled"
[ ] "python.linting.lintOnSave works

Editing
IntelliSense
Please also test for general accuracy on the most "interesting" code you can find.

[ ] "python.autoComplete.extraPaths" works
[ ] "python.autoComplete.preloadModules" works
[ ] "python.autocomplete.addBrackets": true causes auto-completion of functions to append ()

Formatting

[ ] autopep8 works
[ ] yapf works
[ ] "editor.formatOnType": true works and has expected results

Refactoring

[ ] Extract Variable works
[ ] Extract method works
[ ] Sort Imports works

Debugging
Test both old and new debugger (and notice if the new debugger seems at least as fast as the old debugger).

[ ] Configurations work

[ ] Current File
[ ] Module
[ ] Attach
[ ] Terminal (integrated)
[ ] Terminal (external)
[ ] Django
[ ] Flask
[ ] Pyramid
[ ] Watson
[ ] Scrapy
[ ] PySpark
[ ] All debug Options with appropriate values changed

[ ] Breakpoints

[ ] Set
[ ] Hit
[ ] Watch

[ ] Stepping

[ ] Over
[ ] Into
[ ] Out

[ ] Can inspect variables

[ ] Through hovering over variable in code
[ ] Variables section of debugger sidebar

[ ] Remote debugging works

[ ] ... over SSH

[ ] App Engine

Unit testing
unittest
import unittest

class PassingTests(unittest.TestCase):

    def test_passing(self):
        self.assertEqual(42, 42)

    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")

class FailingTests(unittest.TestCase):

    def test_failure(self):
        self.assertEqual(42, -13)

    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

[ ] Run All Unit Tests triggers the prompt to configure the test runner
[ ] Tests are discovered (as shown by code lenses on each test)

pytest
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Pytest gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

nose
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Nose gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

General

[ ] Code lenses appears

[ ] Run Test lens works (and status bar updates as appropriate)
[ ] Debug Test lens works
[ ] Appropriate ✔/❌ shown for each test

[ ] Status bar is functioning

[ ] Appropriate test results displayed
[ ] Run All Unit Tests works
[ ] Discover Unit Tests works (resets tests result display in status bar)
[ ] Run Unit Test Method ... works
[ ] View Unit Test Output works
[ ] After having at least one failure, Run Failed Tests works

Test plan
Environment

OS: Mac
Python

Distribution: CPython
Version: 3.6.5 (cpython)

Tests
ALWAYS check the Output window under Python for logged errors!
Environment
Interpreters

[ ] Interpreter is shown in the status bar
[ ] An interpreter can be manually specified using the Select Interpreter command
[ ] Detected system-installed interpreters
[ ] Detected an Anaconda installation
[ ] (Linux/macOS) Detected all interpreters installed w/ pyenv detected
[ ] "python.pythonPath" triggers an update in the status bar
[ ] Run Python File in Terminal
[ ] Run Selection/Line in Python Terminal

Virtual environments
ALWAYS create environments with a space in their name.*

[ ] Detected a single virtual environment at the top-level of the workspace folder

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses --user
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] Detect multiple virtual environments in a directory specified by "python.venvPath"
[ ] Detected all conda environments created with an interpreter

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint installs into the conda environment
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS until -m is supported) Detected the virtual environment created by pipenv

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses pipenv install --dev
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS) Detected virtual environments created under {workspaceFolder}/.direnv/python-{python_version} for direnv and its layout python3 support

[ ] Appropriate suffix label specified in status bar
[ ] "python.terminal.activateEnvironments": false deactivates detection

Environment files
Sample files:
# example.py
import os
print('Hello,', os.environ.get('WHO'), '!')

# .env
WHO=world

[ ] Environment variables in a .env file are exposed when running under the debugger
[ ] "python.envFile" allows for specifying an environment file manually

Debugging

[ ] pythonPath setting in your launch.json overrides your python.pythonPath default setting

Linting
ALWAYS check under the Problems tab to see e.g. if a linter is raising errors!
Pylint/default linting
[Prompting to install Pylint is covered under Environments above]
For testing the disablement of the default linting rules for Pylint:
# pylintrc
[MESSAGES CONTROL]
enable=bad-names

# example.py
foo = 42  # Marked as a blacklisted name.

[ ] Installation via the prompt installs Pylint as appropriate
[ ] Pylint works
[ ] "python.linting.pylintUseMinimalCheckers": false turns off the default rules w/ no pylintrc file present
[ ] The existense of a pylintrc file turns off the default rules

Other linters

[ ] flake8 works
[ ] mypy works
[ ] pydocstyle works
[ ] pep8 works
[ ] prospector works
[ ] pylama works
[ ] 3 or more linters work simultaneously

[ ] Run Linting runs all linters
[ ] The Select Linter command lists all the above linters and prompts to install a linter when missing
[ ] "python.linting.enabled" disables all linters
[ ] The Enable Linting command changes "python.linting.enabled"
[ ] "python.linting.lintOnSave works

Editing
IntelliSense
Please also test for general accuracy on the most "interesting" code you can find.

[ ] "python.autoComplete.extraPaths" works
[ ] "python.autoComplete.preloadModules" works
[ ] "python.autocomplete.addBrackets": true causes auto-completion of functions to append ()

Formatting

[ ] autopep8 works
[ ] yapf works
[ ] "editor.formatOnType": true works and has expected results

Refactoring

[ ] Extract Variable works
[ ] Extract method works
[ ] Sort Imports works

Debugging
Test both old and new debugger (and notice if the new debugger seems at least as fast as the old debugger).

[ ] Configurations work

[ ] Current File
[ ] Module
[ ] Attach
[ ] Terminal (integrated)
[ ] Terminal (external)
[ ] Django
[ ] Flask
[ ] Pyramid
[ ] Watson
[ ] Scrapy
[ ] PySpark
[ ] All debug Options with appropriate values changed

[ ] Breakpoints

[ ] Set
[ ] Hit
[ ] Watch

[ ] Stepping

[ ] Over
[ ] Into
[ ] Out

[ ] Can inspect variables

[ ] Through hovering over variable in code
[ ] Variables section of debugger sidebar

[ ] Remote debugging works

[ ] ... over SSH

[ ] App Engine

Unit testing
unittest
import unittest

class PassingTests(unittest.TestCase):

    def test_passing(self):
        self.assertEqual(42, 42)

    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")

class FailingTests(unittest.TestCase):

    def test_failure(self):
        self.assertEqual(42, -13)

    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

[ ] Run All Unit Tests triggers the prompt to configure the test runner
[ ] Tests are discovered (as shown by code lenses on each test)

pytest
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Pytest gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

nose
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Nose gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

General

[ ] Code lenses appears

[ ] Run Test lens works (and status bar updates as appropriate)
[ ] Debug Test lens works
[ ] Appropriate ✔/❌ shown for each test

[ ] Status bar is functioning

[ ] Appropriate test results displayed
[ ] Run All Unit Tests works
[ ] Discover Unit Tests works (resets tests result display in status bar)
[ ] Run Unit Test Method ... works
[ ] View Unit Test Output works
[ ] After having at least one failure, Run Failed Tests works

Test plan
Environment

OS: Linux (Ubuntu 16.04)
Python

Distribution: CPython
Version: 3.5

Tests
ALWAYS check the Output window under Python for logged errors!
Environment
Interpreters

[ ] Interpreter is shown in the status bar
[ ] An interpreter can be manually specified using the Select Interpreter command
[ ] Detected system-installed interpreters
[ ] Detected an Anaconda installation
[ ] (Linux/macOS) Detected all interpreters installed w/ pyenv detected
[ ] "python.pythonPath" triggers an update in the status bar
[ ] Run Python File in Terminal
[ ] Run Selection/Line in Python Terminal

[ ] Right-click
[ ] Command
[ ] Ctrl-Enter

Virtual environments
ALWAYS create environments with a space in their name.*

[ ] Detected a single virtual environment at the top-level of the workspace folder

[ ] Appropriate suffix label specified in status bar
[ ] Create Terminal works

[ ] Steals focus
[ ] "python.terminal.activateEnvironment": false turns off automatic activation of the environment

[ ] Detect multiple virtual environments in a directory specified by "python.venvPath"
[ ] Detected all conda environments created with an interpreter

[ ] Appropriate suffix label specified in status bar
[ ] Prompted to install Pylint

[ ] Asked whether to install using conda or pip
[ ] Installs into environment

[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS until -m is supported) Detected the virtual environment created by pipenv

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses pipenv install --dev
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS) Virtual environments created under {workspaceFolder}/.direnv/python-{python_version} are detected (for direnv and its layout python3 support)

[ ] Appropriate suffix label specified in status bar
[ ] "python.terminal.activateEnvironments": false deactivates detection

Environment files
Sample files:
# example.py
import os
print('Hello,', os.environ.get('WHO'), '!')

# .env
WHO=world
PYTHONPATH=some/path/somewhere

Make sure to use Reload Window between tests to reset your environment!

[ ] Environment variables in a .env file are exposed when running under the debugger
[ ] "python.envFile" allows for specifying an environment file manually (e.g. Jedi picks up PYTHONPATH changes)
[ ] envFile in a launch.json configuration works

Debugging

[ ] pythonPath setting in your launch.json overrides your python.pythonPath default setting

Linting
ALWAYS check under the Problems tab to see e.g. if a linter is raising errors!
Pylint/default linting
[Prompting to install Pylint is covered under Environments above]
For testing the disablement of the default linting rules for Pylint:
# pylintrc
[MESSAGES CONTROL]
enable=bad-names

# example.py
foo = 42  # Marked as a blacklisted name.

[ ] Installation via the prompt installs Pylint as appropriate

[ ] Uses --user for system-install of Python
[ ] Installs into a virtual environment environment directly

[ ] Pylint works
[ ] "python.linting.pylintUseMinimalCheckers": false turns off the default rules w/ no pylintrc file present
[ ] The existence of a pylintrc file turns off the default rules

Other linters
You can always use the Run Linting command to immediately trigger a newly installed linter.

[ ] flake8 works
[ ] mypy works
[ ] pep8 works
[ ] prospector works
[ ] pydocstyle works
[ ] pylama works
[ ] 3 or more linters work simultaneously

[ ] Run Linting runs all linters
[ ] The Select Linter command lists all the above linters and prompts to install a linter when missing
[ ] "python.linting.enabled": false disables all linters
[ ] The Enable Linting command changes "python.linting.enabled"
[ ] "python.linting.lintOnSave works

Editing
IntelliSense
Please also test for general accuracy on the most "interesting" code you can find.

[ ] "python.autoComplete.extraPaths" works
[ ] "python.autoComplete.preloadModules" works
[ ] "python.autocomplete.addBrackets": true causes auto-completion of functions to append ()

Formatting
Sample file:
# There should be _some_ change after running `Format Document`.
def foo():pass

[ ] Prompted to install a formatter if none installed and Format Document is run

[ ] Installing autopep8 works
[ ] Installing yapf works

[ ] autopep8 works
[ ] yapf works
[ ] "editor.formatOnType": true works and has expected results

Refactoring

[ ] Extract Variable works

[ ] You are prompted to install rope if it is not already available

[ ] Extract method works

[ ] You are prompted to install rope if it is not already available

[ ] Sort Imports works

Debugging
Test both old and new debugger (and notice if the new debugger seems at least as fast as the old debugger).

[ ] Configurations work

[ ] Current File
[ ] Module
[ ] Attach
[ ] Terminal (integrated)
[ ] Terminal (external)
[ ] Django
[ ] Flask
[ ] Pyramid
[ ] Watson
[ ] Scrapy
[ ] PySpark
[ ] All debug Options with appropriate values edited to make values valid

[ ] Breakpoints

[ ] Set
[ ] Hit
[ ] Conditional

[ ] Expression
[ ] Hit count

[ ] Log points (experimental debugger only)

[ ] Stepping

[ ] Over
[ ] Into
[ ] Out

[ ] Can inspect variables

[ ] Through hovering over variable in code
[ ] Variables section of debugger sidebar

[ ] Remote debugging works

[ ] ... over SSH

[ ] App Engine

Unit testing
unittest
import unittest

class PassingTests(unittest.TestCase):

    def test_passing(self):
        self.assertEqual(42, 42)

    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")

class FailingTests(unittest.TestCase):

    def test_failure(self):
        self.assertEqual(42, -13)

    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

[ ] Run All Unit Tests triggers the prompt to configure the test runner
[ ] Tests are discovered (as shown by code lenses on each test)

pytest
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] pytest gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

nose
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Nose gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

General

[ ] Code lenses appears

[ ] Run Test lens works (and status bar updates as appropriate)
[ ] Debug Test lens works
[ ] Appropriate ✔/❌ shown for each test

[ ] Status bar is functioning

[ ] Appropriate test results displayed
[ ] Run All Unit Tests works
[ ] Discover Unit Tests works (resets tests result display in status bar)
[ ] Run Unit Test Method ... works
[ ] View Unit Test Output works
[ ] After having at least one failure, Run Failed Tests works

Test plan
Environment

OS: Win10 16299
Python

Distribution: CPython
Version: 3.6-64

Tests
ALWAYS check the Output window under Python for logged errors!
Environment
Interpreters

[ ] Interpreter is shown in the status bar
[ ] An interpreter can be manually specified using the Select Interpreter command
[ ] Detected system-installed interpreters
[ ] Detected an Anaconda installation
[ ] (Linux/macOS) Detected all interpreters installed w/ pyenv detected
[ ] "python.pythonPath" triggers an update in the status bar
[ ] Run Python File in Terminal
[ ] Run Selection/Line in Python Terminal

[ ] Right-click
[ ] Command
[ ] Ctrl-Enter

Virtual environments
ALWAYS create environments with a space in their name.*

[ ] Detected a single virtual environment at the top-level of the workspace folder

[ ] Appropriate suffix label specified in status bar
[ ] Create Terminal works

[ ] Steals focus
[ ] "python.terminal.activateEnvironment": false turns off automatic activation of the environment

[ ] Detect multiple virtual environments in a directory specified by "python.venvPath"
[ ] Detected all conda environments created with an interpreter

[ ] Appropriate suffix label specified in status bar
[ ] Prompted to install Pylint

[ ] Asked whether to install using conda or pip
[ ] Installs into environment

[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS until -m is supported) Detected the virtual environment created by pipenv

[ ] Appropriate suffix label specified in status bar
[ ] Prompt to install Pylint uses pipenv install --dev
[ ] "python.terminal.activateEnvironments": false deactivates detection
[ ] Create Terminal works

[ ] (Linux/macOS) Virtual environments created under {workspaceFolder}/.direnv/python-{python_version} are detected (for direnv and its layout python3 support)

[ ] Appropriate suffix label specified in status bar
[ ] "python.terminal.activateEnvironments": false deactivates detection

Environment files
Sample files:
# example.py
import os
print('Hello,', os.environ.get('WHO'), '!')

# .env
WHO=world
PYTHONPATH=some/path/somewhere

Make sure to use Reload Window between tests to reset your environment!

[ ] Environment variables in a .env file are exposed when running under the debugger
[ ] "python.envFile" allows for specifying an environment file manually (e.g. Jedi picks up PYTHONPATH changes)
[ ] envFile in a launch.json configuration works

Debugging

[ ] pythonPath setting in your launch.json overrides your python.pythonPath default setting

Linting
ALWAYS check under the Problems tab to see e.g. if a linter is raising errors!
Pylint/default linting
[Prompting to install Pylint is covered under Environments above]
For testing the disablement of the default linting rules for Pylint:
# pylintrc
[MESSAGES CONTROL]
enable=bad-names

# example.py
foo = 42  # Marked as a blacklisted name.

[ ] Installation via the prompt installs Pylint as appropriate

[ ] Uses --user for system-install of Python
[ ] Installs into a virtual environment environment directly

[ ] Pylint works
[ ] "python.linting.pylintUseMinimalCheckers": false turns off the default rules w/ no pylintrc file present
[ ] The existence of a pylintrc file turns off the default rules

Other linters
You can always use the Run Linting command to immediately trigger a newly installed linter.

[ ] flake8 works
[ ] mypy works
[ ] pep8 works
[ ] prospector works
[ ] pydocstyle works
[ ] pylama works
[ ] 3 or more linters work simultaneously

[ ] Run Linting runs all linters
[ ] The Select Linter command lists all the above linters and prompts to install a linter when missing
[ ] "python.linting.enabled": false disables all linters
[ ] The Enable Linting command changes "python.linting.enabled"
[ ] "python.linting.lintOnSave works

Editing
IntelliSense
Please also test for general accuracy on the most "interesting" code you can find.

[ ] "python.autoComplete.extraPaths" works
[ ] "python.autoComplete.preloadModules" works
[ ] "python.autocomplete.addBrackets": true causes auto-completion of functions to append ()

Formatting
Sample file:
# There should be _some_ change after running `Format Document`.
def foo():pass

[ ] Prompted to install a formatter if none installed and Format Document is run

[ ] Installing autopep8 works
[ ] Installing yapf works

[ ] autopep8 works
[ ] yapf works
[ ] "editor.formatOnType": true works and has expected results

Refactoring

[ ] Extract Variable works

[ ] You are prompted to install rope if it is not already available

[ ] Extract method works

[ ] You are prompted to install rope if it is not already available

[ ] Sort Imports works

Debugging
Test both old and new debugger (and notice if the new debugger seems at least as fast as the old debugger).

[ ] Configurations work

[ ] Current File
[ ] Module
[ ] Attach
[ ] Terminal (integrated)
[ ] Terminal (external)
[ ] Django
[ ] Flask
[ ] Pyramid
[ ] Watson
[ ] Scrapy
[ ] PySpark
[ ] All debug Options with appropriate values edited to make values valid

[ ] Breakpoints

[ ] Set
[ ] Hit
[ ] Conditional

[ ] Expression
[ ] Hit count

[ ] Log points (experimental debugger only)

[ ] Stepping

[ ] Over
[ ] Into
[ ] Out

[ ] Can inspect variables

[ ] Through hovering over variable in code
[ ] Variables section of debugger sidebar

[ ] Remote debugging works

[ ] ... over SSH

[ ] App Engine

Unit testing
unittest
import unittest

class PassingTests(unittest.TestCase):

    def test_passing(self):
        self.assertEqual(42, 42)

    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")

class FailingTests(unittest.TestCase):

    def test_failure(self):
        self.assertEqual(42, -13)

    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

[ ] Run All Unit Tests triggers the prompt to configure the test runner
[ ] Tests are discovered (as shown by code lenses on each test)

pytest
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] pytest gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

nose
def test_passing():
    assert 42 == 42

def test_failure():
    assert 42 == -13

[ ] Run All Unit Tests triggers the prompt to configure the test runner

[ ] Nose gets installed

[ ] Tests are discovered (as shown by code lenses on each test)

General

[ ] Code lenses appears

[ ] Run Test lens works (and status bar updates as appropriate)
[ ] Debug Test lens works
[ ] Appropriate ✔/❌ shown for each test

[ ] Status bar is functioning

[ ] Appropriate test results displayed
[ ] Run All Unit Tests works
[ ] Discover Unit Tests works (resets tests result display in status bar)
[ ] Run Unit Test Method ... works
[ ] View Unit Test Output works
[ ] After having at least one failure, Run Failed Tests works


Enable console commands also on hostings where exec() not allowed

What steps will reproduce the problem?
Executing console commands (CLI) throws error on hostings with limited shell script support.
Typically some function like exec(), file_get_contents() etc. may be disabled by hosting administrators.
In such a case an error e.g. Error: exec() has been disabled for security reasons. pops up and command cannot be executed (e.g. migration).
What is the expected result?
Execute console command, e.g. migration.
What do you get instead?
Error e.g. Error: exec() has been disabled for security reasons. .
Additional info

Q
A

Yii version
2.0.45

PHP version
any

Operating system
linux, windows

Reason & solution
The reason of this message is exec() method in /helpers/BaseConsole::getScreenSize(). Using supress operator @ allows further code execution.

Replaced with #19471

Solved by #19471


Cannot use Vue with browserify (regression)

Vue.js version
2.0.6
Reproduction Link
https://github.com/ernestoalejo/vue-repro
(only 3 files, it's very simple)
Steps to reproduce

clone the repo
npm install
gulp

What is Expected?
To build the app correctly.
What is actually happening?
After the commit https://github.com/vuejs/vue/commit/a4fcdbe6731ca4a0ef6a3f94ef06d56cc92636f7 it requires the "he" package and it can't found it:
Error: Cannot find module 'he' from '/.../vue-repro/node_modules/vue/dist'
    at /.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:46:17
    at process (/.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:173:43)
    at ondir (/.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:188:17)
    at load (/.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
    at onex (/.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
    at /.../vue-repro/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
    at FSReqWrap.oncomplete (fs.js:82:15)

same issue with webpack-simple
Steps to reproduce
https://github.com/vuejs-templates/webpack-simple
$ npm install -g vue-cli
$ vue init webpack-simple my-project
$ cd my-project
$ npm install
$ npm run dev

following issue
ERROR in ./~/vue/dist/vue.js
Module not found: Error: Can't resolve 'he' in 'test\node_modules\vue\dist'
 @ ./~/vue/dist/vue.js 5762:11-24
 @ ./src/main.js
 @ multi main

It's somewhat difficult to workaround this bug because we cannot use an old version easily (npm resolves vueify>vue-template-compiler using ^2.0.0-alpha.8 and that's always<EMAIL_ADDRESS>even if we want to use a different version). We now need to add yarn or shrinkwrap to the project.

@ernestoalejo, it works well on my computer according to your steps, anything else missed ?

For now the workaround is do not parse vue/dist/vue.js for requires - browserify has the noparse flag and Webpack has the module.noParse option.
We will fix it in the next release.

same issue when using jspm with<EMAIL_ADDRESS>rolling back to<EMAIL_ADDRESS>solves it for now

Unrelated, but I tried with:
    var bundle = browserify({
      noParse: ['node_modules/vue/dist/vue.js'],
    });

and a quick console.log inside babel code here says the file is filtered correctly. It stills throws the error though, after all files pass the filter. Probably there is some other option I have not consider here.

The workaround for webpack is add he to externals

This has been reverted/fixed in 2.0.7.


fix: Terraform Helm error "invalid Yaml document separator: apiVersion: v1"

Apparently Terraform Helm doesn't like the notation used in the charts/redpanda/templates/service.internal.yaml (delimiter without condition).
Replicating the notation from charts/redpanda/templates/poddisruptionbudget.yaml fixed the issue.
Fixes the #1410

@maksym-iv if you could sign CLA and bump https://github.com/redpanda-data/helm-charts/blob/d2444af416d0e182f476bb231f90d7b2b7c636d7/charts/redpanda/Chart.yaml#L26

@maksym-iv if you could sign CLA and bump
https://github.com/redpanda-data/helm-charts/blob/d2444af416d0e182f476bb231f90d7b2b7c636d7/charts/redpanda/Chart.yaml#L26

Sure, done, lmk plz if any other change needed

@maksym-iv if you could sign CLA and bump
https://github.com/redpanda-data/helm-charts/blob/d2444af416d0e182f476bb231f90d7b2b7c636d7/charts/redpanda/Chart.yaml#L26

Sure, done, lmk plz if anything else needed

@maksym-iv if you could sign CLA and bump
https://github.com/redpanda-data/helm-charts/blob/d2444af416d0e182f476bb231f90d7b2b7c636d7/charts/redpanda/Chart.yaml#L26

My bad, I previously pushed with another email set in git config, force pushed with a proper one, CLA should be good now.

You can ignore the CI failure. That'll be fixed in https://github.com/redpanda-data/helm-charts/pull/1412
I think I had to do some cheating in one of our tests to filter out empty YAML blocks. Sounds like it would be good to remove that so we can catch this issue ourselves.

You can ignore the CI failure. That'll be fixed in #1412
I think I had to do some cheating in one of our tests to filter out empty YAML blocks. Sounds like it would be good to remove that so we can catch this issue ourselves.

Rebased from main, force pushed since #1412 seems to be merged

LGTM!

I believe I can't merge due to CI lint failure, if you have such permissions, may you merge plz?


Feature - "Visible Previews Per Second" Benchmark

This would require a certain world generated percentage before resetting, thus providing a more realistic benchmark as no one resets previews within 1 frame

Instead, a minimum percentage of rendered chunks could also be used.
This would probably be more accurate however it might have some inaccuracies with WorldPreview:
WorldPreview sends only sends chunks within Chunk Distance and within the view frustum, however additionally it also sends empty chunks for culled chunks that are neighbouring chunks that weren't culled for biome data and entities that are in those chunks but still visible because their render bounding box is outside the chunk bounding box.
These chunks shouldn't be build by Sodium, but it should be checked that they aren't and additionally I'm unsure off the top of my head if chunks that are outside Chunk Distance also send empty chunks.
Seems like an interesting issue for contributors who are interested in learning about WorldPreviews packet system and SeedQueues wall preview rendering!


fix: build one partition at a time to avoid OOM

we can build single HNSW graph in parallel, so don't need to build many partitions at a time.
this still slows the building progress cause the IO operations (reading the shuffled files) can't be done in advance

#2552 can solve this problem


Skip flaky test

I'm leaning against merging this PR, and just living with the Flaky test if we can't solve it.


Get started items keep coming back

I haven't seen this happen before so maybe a recent change affected this. I've hidden all of the walkthroughs and they flash back when I do a refresh and re-opening the welcome page makes them permanently show up.
https://user-images.githubusercontent.com/35271042/135511164-9b9dde6d-d4cb-4ddd-9340-282c4ae33130.mp4
Version: 1.61.0-insider (Universal)
Commit: 6fed60f8f4dd21fb16dcbe64a742296b339ff0ee
Date: 2021-09-30T05:17:41.877Z
Electron: 13.5.0
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.6.0

Hm I did make a small change here yesterday but I don't think it'd affect here... I'll look more into this.

It did indeed affect here. Good catch, thanks!

It did indeed affect here. Good catch, thanks!


What size VM does this need?

Hetzner-ocp4  is made for a bare metal server it creates VM's to run OpenShift. Using hetzner-ocp4 in a VM is not a good idea.


Add tag on the template to be able to reference a specific version.

Is your feature request related to a problem? Please describe.
In cookiecutter-home-assistant-custom-component I try to keep synchronized with the blueprint template. I plan to release once a month. It could be easier for users to know what version of the blueprint the cookiecutter will generate.
Describe the solution you'd like
The blueprint maintainers could add a tag or a release after major modifications.
Describe alternatives you've considered
open for other suggestions
Additional context
N/A

@oncleben31, as an option you can use my modification of this repository in which where are separate branch with blueprint which you can securely merge with you project at any time: https://github.com/Limych/ha-blueprint


Feat/editable participant

This PR enables users to edit participant name:

Add a new member participantPositions to Pariticipants class. participantPositions is a map where to keep track of participant names and their positions.

Record participant's position when traversing the parseTree.

Create a new component PariticipantLabel for editing label names and updating the participant instances in code

Disable edit in static render mode

https://github.com/mermaid-js/zenuml-core/assets/3481791/7e94e357-10fb-4f17-8915-ebc783fb9225

In the following case, the expected result should be
A as "A is a service 1"
A.method

https://github.com/mermaid-js/zenuml-core/assets/169417/a9461ce6-0c38-425f-bed2-6587c43d11b5

It seems that it does not handle participant alias correctly. The syntax is ParticipantA as ParticipantA_Alias.

Fixed

First part is on the main branch where new E works as expected. The second part is the PR branch participant is not displayed with new E.
https://github.com/mermaid-js/zenuml-core/assets/169417/969b8bda-7153-4591-9b90-783bb2f012dd

Address the issue of calling a method after creating a new instance and assigning to a new variable
https://github.com/mermaid-js/zenuml-core/assets/3481791/f59ee626-9063-4aa9-8744-ca21a3fc75d0


docs(sbb-dialog): fix links to other components

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

:exclamation: No coverage uploaded for pull request base (main@ddfd884). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2584   +/-   ##
=======================================
  Coverage        ?   93.18%
=======================================
  Files           ?      315
  Lines           ?    25381
  Branches        ?     2062
=======================================
  Hits            ?    23652
  Misses          ?     1696
  Partials        ?       33

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


Added projectId for a nursery transfer

#1789  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite


Error during build

Hi ,
I get this error when built in openstlinux, meta-flutter kirkstone branch
gn_fetcher_bbclass
0003:# SPDX-License-Identifier: MIT
0004:#
0005:
0006:python () {
*** 0007:    import gn
0008:    bb.fetch2.methods.append(gn.GN())
0009:}
0010:
0011:DEPENDS += "
Exception: ModuleNotFoundError: No module named 'gn'
Please help

Yes I could create the image i added the layer after that it fails
வெள்., 8 டிச., 2023, பிற்பகல் 9:56 அன்று, Joel Winarske <
@.***> எழுதியது:

@prakaashg https://github.com/prakaashg can you build an OS image
before adding the meta-flutter layer? Please confirm
—
Reply to this email directly, view it on GitHub
https://github.com/meta-flutter/meta-flutter/issues/368#issuecomment-1847479879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMIHICBN2PNTRFTVDD2F53YIM5TFAVCNFSM6AAAAABAMYTFNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGQ3TSOBXHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Have you reviewed the container runtime packages used in this CI job?
https://github.com/meta-flutter/meta-flutter/blob/kirkstone/.github/workflows/kirkstone-stm32mp15.yml
https://github.com/meta-flutter/docker-containers/blob/main/ubuntu-18-dev/Dockerfile

I copied from workflow yml now,  I get a different error this time,
tools/clang/lib/CodeGen/CMakeFiles/obj.clangCodeGen.dir/CGBuiltin.cpp.o -c /home/rsa-key-20231118/kirkstone/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/llvm-project-source-14.0.6-r0/git/clang/lib/CodeGen/CGBuiltin.cpp
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
Summary: 1 task failed:
virtual:native:/home/rsa-key-20231118/kirkstone/layers/layers/meta-clang/recipes-devtools/clang/clang_git.bb:do_compile
Summary: There was 1 ERROR message, returning a non-zero exit code.

What distro/version are you building with?

DISTRO=openstlinux-weston MACHINE=stm32mp1

Hi,
Looks the dart sdk build fails, it tries to download this commit (3470ab8451567dad237ddd54f992bfed066a2707) and it fails, Looks similar to this https://github.com/dart-lang/sdk/issues/54279 , Any idea please help
________ running 'git -c core.deltaBaseCacheLimit=2g fetch origin 3470ab8451567dad237ddd54f992bfed066a2707 --verbose --no-tags' in '/home/rsa-key-20231118/dl/gn/https__github.com_dart-lang_sdk.git/sdk/third_party/pkg/dart_style'
[0:02:41] POST git-upload-pack (1000 bytes)
[0:02:41] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
[0:02:41] fatal: the remote end hung up unexpectedly

Hi,
After changing the dart version the build succeeds, but running flutter auto results in segentation fault,
sr/share/flutter/gallery/3.13.9
[14:38:33.182080] [I] agl @ 3114782
[14:38:33.182512] [I] **********
[14:38:33.182544] [I] * Global *
[14:38:33.182568] [I] **********
[14:38:33.182632] [I] Application Id: .......... flutter-auto
[14:38:33.182670] [I] Disable Cursor: .......... false
[14:38:33.182700] [I] Debug Backend: ........... false
[14:38:33.182723] [I] ********
[14:38:33.182743] [I] * View *
[14:38:33.182762] [I] ********
[14:38:33.182785] [I] Bundle Path: .............. /usr/share/flutter/gallery/3.13.9
[14:38:33.182810] [I] Window Type: .............. NORMAL
[14:38:33.182867] [I] Output Index: ............. 0
[14:38:33.182898] [I] Size: ..................... 1920 x 720
[14:38:33.182926] [I] Fullscreen: ............... false
[14:38:33.182970] [I] Accessibility Features: ... 0
Segmentation fault (core dumped)
Any idea?

@prakaashg What hardware, and BSP?

The other thing is there are a number of patches for the AGL client Marius recently made.  If you're not using the AGL compositor please use ivi-homescreen (upstream to flutter auto).  I will be releasing a major point release ~first week of February

Hi ,
Board is STM32MP157c-Dk2, It was working fine with dunfell when we upgraded dart to 3.x and kirkstone I get this error.
When i enable weston logs we get this error
[1467645.098] wl_registry@10.global(17, "zwp_linux_explicit_synchronization_v1", 2)
[1467979.630]  -> wl_registry@10.bind(17, "zwp_linux_explicit_synchronization_v1", 1, new id [unknown]@13)
[1467979.781] wl_registry@10.global(18, "weston_content_protection", 1)
[1467979.874] wl_registry@10.global(19, "wl_output", 3)
[1467979.963] wl_registry@10.global(20, "zwp_input_panel_v1", 1)
[1467980.051] wl_registry@10.global(21, "zwp_input_method_v1", 1)
[1467980.141] wl_registry@10.global(22, "zwp_text_input_manager_v1", 1)
[1467980.230] wl_registry@10.global(23, "xdg_wm_base", 3)
[1467980.318] wl_registry@10.global(24, "wl_shell", 1)
[1467980.406] wl_registry@10.global(25, "weston_desktop_shell", 1)
[1467980.497] wl_registry@10.global(26, "weston_screenshooter", 1)
[1467980.587] wl_callback@11.done(75)
[1468014.600]  -> wl_compositor@3.create_surface(new id wl_surface@11)
[1468014.742]  -> wl_surface@11.frame(new id wl_callback@14)
Could this be related to https://github.com/meta-flutter/meta-flutter/issues/295 ?

I see.  It could, try applying the patch I have for NXP.  I will be updating the dunfell branch after I get back from CES, so expect some changes there

dunfell branch has been updated:
https://github.com/meta-flutter/meta-flutter/pull/386
This is the patch I was referring to.  It applies to both ivi-homescreen and flutter-auto (only different today is the executable name).
https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl-devel.git;a=blob;f=meta-agl-flutter/recipes-graphics/toyota/files/0001-Disable-on_frame_base_surface-wl_surface_commit.patch;h=a37233b50917f49ba561e6994c746d0a6373f4e5;hb=HEAD

closing since I have not gotten a response back.  Feel free to open a new issue, or re-open this issue as needed.


Integrate content into Eliademy when ready

Course is currently confidential but will be here: https://eliademy.com/app/a/courses/b55b4d7020

OK, this is basically ready to go, so gonna close now


Release and versioning

The current version schema is pretty confusing.
We have branch which follows Kubernetes release release-1.10, release-1.11 etc.
We also have a version v1.0.0-alpha.0, v1.0.0-beta.0 etc.
I think critest and crictl have different CRI version compatibility requirement:

critest is used to test all CRI features. A new field or slightly behavior change in CRI usually means a new corresponding CRI validation test, but doesn't necessarily mean a CRI version update, e.g. RunAsGroup. So I think critest version has to follow Kubernetes version.
crictl should be able to work with any CRI container runtime, as long as the CRI version matches. There might be field ignored or defaulted because of version skew, but things should not break. So I think crictl version can potentially follow CRI version in the future.

For now, given that CRI version schema is still not clear yet, let's graduate cri-tools to GA, and start following Kubernetes version for both critest and crictl.
@yujuhong @feiskyer @mrunalp @runcom @mikebrow

sounds good to me

:+1: Highly appreciated!

For now, given that CRI version schema is still not clear yet, let's graduate cri-tools to GA, and start following Kubernetes version for both critest and crictl.

what's process for graduation though? :thinking:

Cool! And I'd like to do some contribution in my spare time. 😆

+1

what's process for graduation though?

Cool!

Thanks! A lot of things need help. :)

@feiskyer Do you think for the coming version, should it be v1.11.0 or v1.0.0?

The version should match CRI version ideally, but CRI version schema is still not clear yet as you said. I also think it's better to follow kubernetes versions, e.g. v1.11.X for kubernetes v1.11.

+1 to follow kube major.minor

:+1:

@luxas Yep, the next release is GA and will be versioned as v1.11.0.

is there any possibility of getting the next version released ahead of Kubernetes 1.11?  This would really help with testing, etc.


Add CI badge

This adds the CI badge to the pages on crates.io, #323 adds it to the README. Sorry for the separate PRs, but I didn't feel like forking and cloning the repository down to my laptop and simply used the GitHub online editor instead :-)

Thanks!
bors r+


Reduce TPS to tagging actions in AmazonSQSIdleQueueDeletingClient

I am creating an instance of the AmazonSQSTemporaryQueuesClient across all hosts in a fleet and stickying a single temporary SQS queue per host, which should not be deleted as long as the host is active. In my use-case, I am explicitly making a create queue request to initialize the host queue after creating the client in order to reduce latency of sendMessage calls since the host queues are created lazily otherwise. As a result, I am hitting the 5 TPS AWS account limit for SQS tagging because multiple hosts across the fleet are concurrently calling AmazonSQSIdleQueueDeletingClient#createQueue, which in turn makes tagQueue calls. I've already increased the idleQueueSweepingPeriod to a large number on the order of days to reduce the listQueueTags call volume. I understand this 5TPS is a soft limit but I think there are a few minimal changes to the AmazonSQSIdleQueueDeletingClient that can be made to reduce the TPS:

Add IDLE_QUEUE_RETENTION_PERIOD_TAG tag to CreateQueueRequest in AmazonSQSIdleQueueDeletingClient (link), instead of explicitly calling tagQueue. I am not sure if adding a tag via CreateQueueRequest contributes to the 5TPS limit but at the very least it can save a tagQueue API call.
Set a random initial delay value to the scheduled heartbeating to add some jitter.
This is an alternative to #2 - remove scheduled heartbeating after creating a new queue (or provide the option to do so) and rely on other API operations like receiveMessage to heartbeat the host queue. I'm not quite sure what other implications this might have as I am not too familiar with the code base.

Thanks!

Hi concerning the changes you requested:

Adding the tag to CreateQueueRequest instead of explicitly calling tagQueue will still contribute to the 5TPS limit, it is still a good idea to have it in CreateQueueRequest since the tag will be set on create.
Will be adding a random initial delay to the scheduled heartbeating.

A good approach would be to also add a retry and backoff to handle the throttling.
Thanks for the request, will create a new release once the changes are merged.


Enable generic Grafana dashboards

Generic operator SDK dashboard
Generic go process dashboard

@amisstea although the guidelines are to create dashboards in team specific repos, but as you mentioned, this is a generic dashboard and not a team's dashboard, I believe it can be created the way it is (in infra-deployments).

/retest


Incorrect kata baku in dictionary

https://github.com/turfaa/IndonesianKataBakuChecker/blob/master/dict.txt#L392
"salah" is a correct and formal word. It's also an antonym of "benar".

It's pretty funny though

@adhikasp thanks! It's beacause I manually parse the dictionary :D

@adhikasp thanks! It's because I manually parse the dictionary :D

@adhikasp thanks! It's because I manually parse the dictionary :D