Directories in bin/cache should have world read and executable bits set

Customer "amplify" reports trying to use a Flutter installation where it was installed as the root user, but they're running it as a non-root user.  When doing this, there are many problems caused by the fact that many directories in bin/cache are only readable or executable by the owning user.
e.g. they can't run the dart executable:
$ ll bin/cache/dart-sdk/
total 40
drwxr-xr-x  10 tvolkert  eng   320 Nov 11 22:42 .
drwxr-xr-x  16 tvolkert  eng   512 Nov 12 09:54 ..
-rw-r--r--   1 tvolkert  eng  2500 Nov  8 23:47 LICENSE
-rw-r--r--   1 tvolkert  eng   936 Nov  8 23:47 README
drwx------   8 tvolkert  eng   256 Nov  9 12:25 bin
-rw-r--r--   1 tvolkert  eng    47 Nov  8 23:47 dartdoc_options.yaml
drwxr-xr-x   5 tvolkert  eng   160 Nov  8 23:52 include
drwxr-xr-x  31 tvolkert  eng   992 Nov  8 23:52 lib
-rw-r--r--   1 tvolkert  eng    41 Nov  8 23:52 revision
-rw-r--r--   1 tvolkert  eng    14 Nov  8 23:52 version

We should consider making sure that all bin/cache directories are usable by all users (pending a more thorough analysis of any possible security issues there).
Moreover, however, bin/cache is populated on demand by the user running the flutter tool, so to facilitate this use case, users would need to make sure that they run flutter precache as the owning user to make the tool usable by other users.

There is some prior art in flutter_tools that shells out to chmod to set the execute bit. See: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/base/os.dart#L82. But it looks like among the bin/cache files, makeExecutable() is only called on flutter_tester: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/cache.dart#L560.

Yeah, I ran with that prior art in https://github.com/flutter/flutter/pull/24669

Using the latest dev channel package, flutter_macos_v1.1.0-dev, there are still some issues remaining with this.
The first problem is that the "bin/cache/" directory itself does not have world write permissions.
drwxr-xr-x@ 16 root  root   512 Dec 11 16:30 cache
Once that has world write permissions, the following issues arise, one at a time after resolving each individually:
FileSystemException: FileSystemException: Cannot open file, path = '/path_to_flutter/bin/cache/lockfile' (OS Error: Permission denied, errno = 13)
FileSystemException: FileSystemException: Cannot open file, path = '/path_to_flutter/version' (OS Error: Permission denied, errno = 13)
FileSystemException: FileSystemException: Cannot open file, path = '/path_to_flutter/bin/cache/flutter_version_check.stamp' (OS Error: Permission denied, errno = 13)
Once those are all resolved, I then get:
Creation of temporary directory failed, path = '/path_to_flutter/.pub-cache/_temp/dir' (OS Error: Permission denied, errno = 13)
pub get failed (66)
Once that one is resolved, I get:
Could not find a file named "pubspec.yaml" in "/path_to_flutter/.pub-cache/hosted/pub.dartlang.org/video_player-0.7.2".
pub get failed (66)
listing out that directory, it shows
985aeb8ceee6:wizard_module danny.valente$ sudo ls -la ~/Downloads/flutter_2/.pub-cache/hosted/pub.dartlang.org/
total 0
drwxr-xr-x@ 84 root  admin  2688 Dec 11 16:30 .
drwxr-xr-x@  3 root  admin    96 Dec 11 16:27 ..
drwx------@ 14 root  admin   448 Dec 11 16:27 analyzer-0.33.3
drwx------@ 13 root  admin   416 Dec 11 16:27 archive-2.0.4
drwx------@ 14 root  admin   448 Dec 11 16:27 args-1.5.1
drwx------@ 15 root  admin   480 Dec 11 16:27 async-2.0.8
drwx------@ 13 root  admin   416 Dec 11 16:27 boolean_selector-1.0.4
drwx------@ 14 root  admin   448 Dec 11 16:27 charcode-1.1.2
drwx------@ 16 root  admin   512 Dec 11 16:27 cli_util-0.1.3+2
drwx------@ 17 root  admin   544 Dec 11 16:27 collection-1.14.11
drwx------@ 13 root  admin   416 Dec 11 16:27 completion-0.2.1+1
drwx------@ 12 root  admin   384 Dec 11 16:30 connectivity-0.3.2
drwx------@ 14 root  admin   448 Dec 11 16:27 convert-2.0.2
drwx------@ 16 root  admin   512 Dec 11 16:27 coverage-0.12.3
drwx------@ 15 root  admin   480 Dec 11 16:27 crypto-2.0.6
drwx------@ 14 root  admin   448 Dec 11 16:27 csslib-0.14.6
drwx------@ 10 root  admin   320 Dec 11 16:30 cupertino_icons-0.1.2
drwx------@ 13 root  admin   416 Dec 11 16:27 dart2_constant-1.0.2+dart2
drwx------@ 19 root  admin   608 Dec 11 16:28 dart_style-1.2.0
drwx------@ 12 root  admin   384 Dec 11 16:30 device_info-0.2.1
drwx------@ 10 root  admin   320 Dec 11 16:27 file-5.0.6
drwx------@  7 root  admin   224 Dec 11 16:27 file_testing-2.0.3
drwx------@  6 root  admin   192 Dec 11 16:28 flutter_gallery_assets-0.1.6
drwx------@ 15 root  admin   480 Dec 11 16:27 front_end-0.1.6+3
drwx------@ 12 root  admin   384 Dec 11 16:27 glob-1.1.7
drwx------@ 12 root  admin   384 Dec 11 16:27 html-0.13.3+3
drwx------@ 11 root  admin   352 Dec 11 16:27 http-0.12.0
drwx------@ 13 root  admin   416 Dec 11 16:27 http_multi_server-2.0.5
drwx------@ 12 root  admin   384 Dec 11 16:27 http_parser-3.1.3
drwx------@ 14 root  admin   448 Dec 11 16:29 image-2.0.4
drwx------@ 15 root  admin   480 Dec 11 16:27 intl-0.15.7
drwx------@ 15 root  admin   480 Dec 11 16:28 intl_translation-0.17.2
drwx------@ 13 root  admin   416 Dec 11 16:27 io-0.3.3
drwx------@ 16 root  admin   512 Dec 11 16:28 isolate-2.0.2
drwx------@ 10 root  admin   320 Dec 11 16:27 js-0.6.1+1
drwx------@ 12 root  admin   384 Dec 11 16:27 json_rpc_2-2.0.9
drwx------@ 18 root  admin   576 Dec 11 16:27 json_schema-1.0.10
drwx------@ 16 root  admin   512 Dec 11 16:27 kernel-0.3.6+3
drwx------@ 19 root  admin   608 Dec 11 16:27 linter-0.1.72
drwx------@ 14 root  admin   448 Dec 11 16:27 logging-0.11.3+2
drwx------@ 13 root  admin   416 Dec 11 16:27 matcher-0.12.3+1
drwx------@  8 root  admin   256 Dec 11 16:27 meta-1.1.6
drwx------@ 15 root  admin   480 Dec 11 16:27 mime-0.9.6+2
drwx------@ 15 root  admin   480 Dec 11 16:27 mockito-4.0.0
drwx------@ 10 root  admin   320 Dec 11 16:27 multi_server_socket-1.0.2
drwx------@ 12 root  admin   384 Dec 11 16:27 mustache-1.0.2
drwx------@ 10 root  admin   320 Dec 11 16:27 node_preamble-1.4.4
drwx------@ 13 root  admin   416 Dec 11 16:27 package_config-1.0.5
drwx------@ 15 root  admin   480 Dec 11 16:27 package_resolver-1.0.6
drwx------@ 13 root  admin   416 Dec 11 16:27 path-1.6.2
drwx------@ 11 root  admin   352 Dec 11 16:29 path_provider-0.4.1
drwx------@ 10 root  admin   320 Dec 11 16:27 petitparser-2.0.2
drwx------@ 14 root  admin   448 Dec 11 16:27 platform-2.2.0
drwx------@ 11 root  admin   352 Dec 11 16:27 plugin-0.2.0+3
drwx------@ 12 root  admin   384 Dec 11 16:27 pool-1.3.6
drwx------@ 14 root  admin   448 Dec 11 16:27 process-3.0.9
drwx------@ 12 root  admin   384 Dec 11 16:27 pub_semver-1.4.2
drwx------@ 17 root  admin   544 Dec 11 16:27 quiver-2.0.1
drwx------@ 14 root  admin   448 Dec 11 16:27 shelf-0.7.3+3
drwx------@ 15 root  admin   480 Dec 11 16:27 shelf_packages_handler-1.0.4
drwx------@ 14 root  admin   448 Dec 11 16:27 shelf_static-0.2.8
drwx------@ 12 root  admin   384 Dec 11 16:27 shelf_web_socket-0.2.2+4
drwx------@ 14 root  admin   448 Dec 11 16:27 source_map_stack_trace-1.1.5
drwx------@ 13 root  admin   416 Dec 11 16:27 source_maps-0.10.8
drwx------@ 12 root  admin   384 Dec 11 16:27 source_span-1.4.1
drwx------@ 12 root  admin   384 Dec 11 16:27 stack_trace-1.9.3
drwx------@ 15 root  admin   480 Dec 11 16:27 stream_channel-1.6.8
drwx------@ 12 root  admin   384 Dec 11 16:27 string_scanner-1.0.4
drwx------@ 14 root  admin   448 Dec 11 16:27 term_glyph-1.0.1
drwx------@ 16 root  admin   512 Dec 11 16:27 test-1.5.1
drwx------@ 11 root  admin   352 Dec 11 16:27 test_api-0.2.1
drwx------@  8 root  admin   256 Dec 11 16:27 test_core-0.2.0
drwx------@ 14 root  admin   448 Dec 11 16:27 typed_data-1.1.6
drwx------@ 11 root  admin   352 Dec 11 16:30 url_launcher-4.0.1
drwx------@ 15 root  admin   480 Dec 11 16:27 usage-3.4.1
drwx------@ 14 root  admin   448 Dec 11 16:27 utf-0.9.0+5
drwx------@ 16 root  admin   512 Dec 11 16:28 vector_math-2.0.8
drwx------@ 14 root  admin   448 Dec 11 16:30 video_player-0.7.2
drwx------@ 15 root  admin   480 Dec 11 16:27 vm_service_client-0.2.6
drwx------@ 13 root  admin   416 Dec 11 16:27 vm_service_lib-0.3.10
drwx------@ 14 root  admin   448 Dec 11 16:27 watcher-0.9.7+10
drwx------@ 14 root  admin   448 Dec 11 16:27 web_socket_channel-1.0.9
drwx------@ 13 root  admin   416 Dec 11 16:27 xml-3.2.3
drwx------@ 14 root  admin   448 Dec 11 16:27 yaml-2.1.15
After fixing all those permissions, a flutter build succeeded, however I don't know if there might be even other issues with permissions.
Thanks

I saw that a fix was potentially merged into the master channel, so I just pulled that down to verify and I still see the same problems.
The issue is that the bin/cache directory doesn't have write permissions among other directories as well, which I listed in my comment above.
Thanks.

@dannyvalente #28090 isn't merged yet.

Ah, I didn't notice that @tvolkert . I saw that #26315 was merged, but I didn't realize there was another issue open too.
Thanks!

Re-application landed in https://github.com/flutter/flutter/pull/28090 - this should be fixed on master now.


added solution in cpp

Solution file  --> minimum-lines-to-represent-a -line-chart
Submission link -->  https://leetcode.com/submissions/detail/776258056/

There is a whitespace in the file name. Ok, I will fix it.👍🏻


make requestorID immutable

Add CEL validation rule to make NodeMaintenance RequestorID immutable.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 65.796%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
1008

Relevant Lines:
1532

💛  - Coveralls


Move @tanem/authors and @tanem/github-changelog-generator into this project

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f73128a). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #21   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      3
  Lines             ?     69
  Branches          ?     14
=======================================
  Hits              ?     69
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

src/index.ts
100% <100%> (ø)

src/authors.ts
100% <100%> (ø)

src/changelog.ts
100% <100%> (ø)

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 f73128a...6e8965d. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f73128a). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #21   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      3
  Lines             ?     69
  Branches          ?     14
=======================================
  Hits              ?     69
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

src/index.ts
100% <100%> (ø)

src/authors.ts
100% <100%> (ø)

src/changelog.ts
100% <100%> (ø)

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 f73128a...6e8965d. Read the comment docs.


"signups" update code can be deprecated

We've changed PgBouncer authentication method:
Signups update feature is no longer required.
We've already removed signups config key from app_config.yml, so it's safe to deprecate this feature from CartoDB code, that's the config involved:
signups:
  service:
    port: '9999'

cc @santisaez

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Update versions

Fixes #15
Fixes #16
Fixes #19
Related to #20
Update all the version in the project to the latest for all the dependencies except Kotlin test

Could someone from @47deg/team-celulares give an extra review here?


Deletion of existent place in the list as Admin

As an admin I want to delete existent place so that the list with places will not increase with unactual places.
Mockup:

Acceptance criteria:

"Delete" icon button is available on the "Places" tab near each row on the right side. It is shown as icon of recycle bin.

WHEN an admin see "Places" tab, THEN he can click on one of "Delete" icon button near each row.

WHEN an admin clicks "Delete" icon button THEN he/she see popup with the next information appears:
a. Text - "Are you sure you want to delete this item?"
b. "Cancel" button
c. "Delete" button

WHEN an admin clicks "Cancel" button THEN Admin see active row in the list with the same status as it was.

WHEN an admin clicks "Delete" button THEN status for mentioned row changes to "Deleted".

Not relevant.


Description of Assign Explicit OperationIds in readme is not complete

The readme file has to be edited in section Assign Explicit OperationIds.
I am using packages Swashbuckle.AspNetCore 4.0.1 and Swashbuckle.AspNetCore.Annotations 4.0.1. I could not get any any operation Id into the swagger initially with both ways to do it (Option 1 or Option 2). I inspected SwaggerUIOptions and I found there is the method DisplayOperationId(). After invoking in, I was able to see the operation Ids in the generated swagger.
My startup class looks like:
public class Startup
{
        //.... some other methods and properties
        public void Configure(IApplicationBuilder app, IHostingEnvironment env)
        {
            //.... some configuration on the IApplicationBuilder instance
            app.UseSwaggerUI(SetSwaggerUIOptions());
            //.... some configuration on the IApplicationBuilder instance
        }
        //.... some other methods and properties

        //.... some other methods and properties
        private Action<SwaggerUIOptions> SetSwaggerUIOptions()
        {
                var result = new Action<SwaggerUIOptions>(options =>
                {
                        options.SwaggerEndpoint($"/swagger/{ApiName}/swagger.json", $"{ApiTitle} {ApiVersion}");
                        options.DocumentTitle = $"{ApiTitle} {ApiVersion}";
                        options.DisplayRequestDuration();
                        options.DisplayOperationId();
                });
                return result;
        }
}

My controller looks like:
[Route("api/values")]
[Produces("application/json")]
[ApiController]
public class ValuesController : ControllerBase
{
        [HttpGet(Name = "get all values")]
        [ProducesResponseType(typeof(string[]), (int)HttpStatusCode.OK)]
        public IActionResult GetAll()
        {
                return Ok(new string[] { "value1", "value2" });
        }
}

The section you've referenced is referring specifically to the inclusion of operationId in the generated Swagger JSON, which I think it does reasonably well.
If I understand your comments correctly, you're wanting more details on the impact this field does or doesn't have on the swagger-ui - a completely separate component that's document elsewhere in the docs.
By design, the docs are broken down by component - i.e. there's a section related to the component that generates Swagger JSON, a section related to middleware that exposes that JSON, a section related to the swagger-ui etc. I'm not in a position to completely restructure the docs at this point and so I'm going to stick with this format for the moment.
With that said, there's a few situations where I do cross-reference between the SwaggerGen and SwaggerUI sections to add a little more color. See https://github.com/domaindrivendev/Swashbuckle.AspNetCore#add-security-definitions-and-requirements for an example. If you think something similar could work here, please put forwward a suggestion in the form of a PR.

@domaindrivendev, I would forward a PR with modification on the readme file :)

Added PR #967


Provide some way to annotate exports?

I'm trying to figure out what to do about https://github.com/evanw/esbuild/issues/668, which is an issue someone logged with esbuild because esbuild's export syntax doesn't exactly match the magic syntax forms used by this library.
I'm using a for-loop to generate export getters since it minifies better, but to work with this library I would presumably have to write out a long verbose list of Object.defineProperty() calls instead. This is undesirable both for minification reasons and because it would require me to support another code path, which is more overhead for me in terms of code complexity and would lead to a bigger test matrix.
Would you consider adding some way to annotate the exports that are available in a given file without having to rewrite the JavaScript in the file? A comment with something like //# cjsExports="someName","someOtherName",... would work, for example. I'm asking because this seems like the most straightforward solution. This library is trying to get a list of exports and instead of trying to magically infer the exports from the code, it could just read them out directly from a list.

We did discuss syntax approaches like this, but it seemed like in most cases the advisable approach was to use ESM wrappers or ESM modules directly for these executions since if Node.js supports this feature it would support ESM anyway.
We can make changes to this processing, but backporting is not necessarily a given at this point so changing things here would result in spotty support for 12 LTS, whereas right now there is comprehensive backwards compat on all Node.js modules semantics paths so it can be reliable.
//cc @geoffreybooth @mylesborins @bmeck @jkrems

We did discuss syntax approaches like this, but it seemed like in most cases the advisable approach was to use ESM wrappers or ESM modules directly for these executions since if Node.js supports this feature it would support ESM anyway.
We can make changes to this processing, but backporting is not necessarily a given at this point so changing things here would result in spotty support for 12 LTS, whereas right now there is comprehensive backwards compat on all Node.js modules semantics paths so it can be reliable.
//cc @geoffreybooth @mylesborins @bmeck @jkrems

Yeah, unfortunately Node.js v12 is now in maintenance so the bar to make changes is going to be pretty hard... especially ones that are not backwards compatible. Not impossible, but very very hard to do.

Yeah, unfortunately Node.js v12 is now in maintenance so the bar to make changes is going to be pretty hard... especially ones that are not backwards compatible. Not impossible, but very very hard to do.

Would you consider adding some way to annotate the exports that are available in a given file without having to rewrite the JavaScript in the file? A comment with something like //# cjsExports="someName","someOtherName",... would work

If esbuild could output such a comment, wouldn’t it also therefore be able to output a CommonJS module that cjs-module-lexer could successfully statically analyze? That seems like the most straightforward solution, as then nothing would need to change on Node’s side and it would work back to Node 12.

Would you consider adding some way to annotate the exports that are available in a given file without having to rewrite the JavaScript in the file? A comment with something like //# cjsExports="someName","someOtherName",... would work

If esbuild could output such a comment, wouldn’t it also therefore be able to output a CommonJS module that cjs-module-lexer could successfully statically analyze? That seems like the most straightforward solution, as then nothing would need to change on Node’s side and it would work back to Node 12.

If esbuild could output such a comment, wouldn’t it also therefore be able to output a CommonJS module that cjs-module-lexer could successfully statically analyze?

Yes it could. I addressed this in my original post:

This is undesirable both for minification reasons and because it would require me to support another code path, which is more overhead for me in terms of code complexity and would lead to a bigger test matrix.

It's fine if your answer is "no". The decision is up to you since it's your project. Just thought I'd ask first to see if there was a way to avoid the complexity of having to generate this magic syntax.

If esbuild could output such a comment, wouldn’t it also therefore be able to output a CommonJS module that cjs-module-lexer could successfully statically analyze?

Yes it could. I addressed this in my original post:

This is undesirable both for minification reasons and because it would require me to support another code path, which is more overhead for me in terms of code complexity and would lead to a bigger test matrix.

It's fine if your answer is "no". The decision is up to you since it's your project. Just thought I'd ask first to see if there was a way to avoid the complexity of having to generate this magic syntax.

@evanw it might be possible to write out an abbreviated form that basically fools the lexer, to avoid those calls being the full exact defineProperty statements. In a way this might effectively be like what you were asking about.
The lexer doesn't have any concept of execution flow at all, so a non-executed function that looks like it defines exports would be supported.
Here's one way of doing that:
// fake exports to inform lexer
(() => exports.a = exports.b = exports.c = void);

// actual exports definition function
defineExports(exports);

That is then something that is quite close to the syntax you are after that will work all the way back to Node.js 12 as well.
I'd still recommend simply outputting an analyzable form of exports definitions if you can and that would still be preferable. But if you can't then the above can be an option.

@evanw it might be possible to write out an abbreviated form that basically fools the lexer, to avoid those calls being the full exact defineProperty statements. In a way this might effectively be like what you were asking about.
The lexer doesn't have any concept of execution flow at all, so a non-executed function that looks like it defines exports would be supported.
Here's one way of doing that:
// fake exports to inform lexer
(() => exports.a = exports.b = exports.c = void);

// actual exports definition function
defineExports(exports);

That is then something that is quite close to the syntax you are after that will work all the way back to Node.js 12 as well.
I'd still recommend simply outputting an analyzable form of exports definitions if you can and that would still be preferable. But if you can't then the above can be an option.

I guess the remaining risk is minifiers removing these unused functions... perhaps there's a way to get around that as well?

I guess the remaining risk is minifiers removing these unused functions... perhaps there's a way to get around that as well?

It seems like https://github.com/guybedford/cjs-module-lexer/pull/46 or similar will be the approach for now.


ORES gives 500 Internal Server Error on revert score query for imported revisions

ORES chokes on this URL: http://ores.wmflabs.org/scores/enwiki/?revids=408030634&models=reverted and returns a 500 Internal Server Error.
My hypothesis is that this is because that very early revision was lost, and later restored from the nostalgia Wikipedia. ORES gives the same error when requesting the revert score of the other imported revision: http://ores.wmflabs.org/scores/enwiki/?revids=408030635&models=reverted
Instead of a server error, it should probably return the same kind of "nice" error as when a revision was deleted.
I discovered this while building archaeo. As part of the associated Wikimania talk, I'm fetching scores for all revisions of the Bee article on the English Wikipedia.
If it helps, Quarry 3990 provides the list of all revisions for "Bee". The imported revisions are chronologically the first ones (they have the earliest rev_timestamps) but they have very high rev_ids.

Note: I don't know if this happens for all imported revisions, but it does happen for imported revisions of other pages as well: ORES returns the same server error for this other imported revision.

Thanks for reporting this and going some digging @gpaumier.  It looks like this is the error that is being thrown.
RuntimeError('Failed to process <log((user.age + 1))>: math domain error',)
Traceback (most recent call last):
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/celery/app/trace.py", line 240, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/celery/app/trace.py", line 438, in __protected_call__
    return self.run(*args, **kwargs)
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/ores-0.2.0-py3.4.egg/ores/score_processors/celery.py", line 33, in _process
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/ores-0.2.0-py3.4.egg/ores/scoring_contexts/scoring_context.py", line 46, in score
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/revscoring-0.4.0-py3.4.egg/revscoring/dependencies/functions.py", line 240, in _solve_many
  File "/home/halfak/env/3.4/lib/python3.4/site-packages/revscoring-0.4.0-py3.4.egg/revscoring/dependencies/functions.py", line 231, in _solve
RuntimeError: Failed to process <log((user.age + 1))>: math domain error

It looks like the import results in a revision with a timestamp that is impossible given a user's registration date.  We'll want to bound user.age to zero to fix the issue.  So it looks like this is a 'revscoring' problem.

See https://github.com/wiki-ai/revscoring/issues/122 and https://github.com/wiki-ai/revscoring/pull/123

I've also confirmed that changes made in https://github.com/wiki-ai/ores/pull/57 will also solve the 500 Internal Server Error problem so that errors like this in the future will return a useful response.

Great! Thank you. I assumed that the issue was with revscoring, but I wasn't sure, so I reported it here. Thanks for fixing this so quickly!


rpy2 now requires manual installation of tzlocal

Coverage remained the same at 100.0% when pulling 7551db1c98f8203f48b93347152a71d0e8d386b5 on bugfix/R-tzlocal into f4997501f8b70a6f20161768c48ccee27589da9e on develop.


Implement vacuum index operation

Description
Implemented the VACUUM index statement in the plugin. The semantics slightly differ from what's defined in Flint Spark: similar to the current DROP index logic in the plugin, the vacuum operation can transition from REFRESHING, ACTIVE, or DELETED states directly, instead of only accepting DELETE.
Issues Resolved
https://github.com/opensearch-project/opensearch-spark/issues/104
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[x] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Will address conflicts once https://github.com/opensearch-project/sql/pull/2554 merged


Fix Normal Calculation+Mesh Welding and get rid of Tangent Calculation

https://github.com/buildaworldnet/IrrlichtBAW/blob/f90bea7cfe3ab54998a487f779d01619575412ac/source/Irrlicht/CMeshManipulator.h#L51
Tangent Calculation has to go, because we promote dervivative mapping with per-pixel fragment derivative tangent frames.
The legacy normal calculation algorithm is almost good, but it needs to be rid of the smooth parameter which shall always be true.
And this bad boy needs a rewrite
https://github.com/buildaworldnet/IrrlichtBAW/blob/f90bea7cfe3ab54998a487f779d01619575412ac/source/Irrlicht/CMeshManipulator.cpp#L33
Also an SSE implementation of core::plane3df would be nice.
Finally a non-angle weighted but a triangle surface area weighted version would be nice as well (or an extra parameter to choose between angle weighted and area weighted)
http://irrlicht.sourceforge.net/forum/viewtopic.php?f=4&t=52435&p=304544#p304544
Create welded mesh buffer routine probably needs to be inline and use a lambda function heuristic (default compare postion and angle between faces) as right now the heuristic is to only compare positions but obviously one needs to compare angles between faces as well.
Or maybe we should have one function for welding and one for smooth-group recalculation?
Or rename weld to smooth-group re-compute?

On second thought the weld function cannot perform the smooth group calc because of duplicate vertices due to extra vx attributes such as texture UVs.
So the flow should go something like this:

Calc smooth group + recalc normal
Weld (by comparing all attributes, just as we do now)

The hardest part is the smooth-group computation, which HAS TO BE ORDER INDEPENDENT W.R.T. INDEX AND VERTEX ORDER.

http://citeseerx.ist.psu.edu/viewdoc/summary?doi=<IP_ADDRESS>4.7649

http://www.beosil.com/download/CollisionDetectionHashing_VMV03.pdf
Code by Dale Weiler, but unsure what should the primes be with more attributes, and also how to handle different bit-widths of attributes.
    kbSize Hash( void ) const
    {
        static constexpr kbSize kPrime1 = 73856093;
        static constexpr kbSize kPrime2 = 19349663;
        static constexpr kbSize kPrime3 = 83492791;
        return ( m_nPosition   * kPrime1 ) ^
               ( m_nNormal     * kPrime2 ) ^
               ( m_nCoordinate * kPrime3 );
    }

What is essentially happening in mesh normal calculation is the following:

Smooth Group Determination
Normal calculation separately for each smooth-group
Welding (because some vertices might now be identical)

Now smooth group information could be provided by a loader or file format (OBJ) but we usually assume that meshes loaded by loaders should have been already properly smoothed.
So if we need to determine the smooth groups algorithmically we run into several problems:

Which edges are shared and which edges are split?
How to get deterministic results?
How to compute the vertex normal given the surroung polygon's from the same smooth group? (http://citeseerx.ist.psu.edu/viewdoc/summary?doi=<IP_ADDRESS>4.7649, or other methods?)

Furthermore the whole smooth group determination and normal calculation routine must be invariant under the following:

rotation
translation
mirroring
permuations of triangle orders in the index list

The term "smooth group" is a bit misleading as it implies that all triangles from the same smooth group around a vertex will contribute to its normal vector.
However one can think of a pathological case of a cylinder's apex, where its all one smooth group but not all adjacent triangles should contribute.

If one knows graph theory then we can think of the mesh as an implicit graph, the nodes are the mesh's vertices and edges between nodes are present only if we deem the two vertices' triangles to be "connected". Remember we can have multiple vertices at the same location and they will still be distinct.
Connection can be determined in two ways:

The vertex appears in the index list for two triangles
The  C++11 lambda function which tells us so, based on its inputs (2 vertex indices + 2 small index lists for triangle membership). Such a function is provided by the user and can compare angle between triangles is below a threshold, has the same material, etc.

A mesh vertex's normal is determined only via contributions of triangle normals of triangles which are deemed adjacent to the parent triangle of the vertex. It would be good to weigh the triangle contributions by the angle at the vertex within each triangle
http://www.bytehazard.com/articles/vertnorm.html (see the last part)

An idea for an adjacency structure:
struct VertexAdjacency
{
    struct MemberRecord
    {
        uint32_t selfAlias; // index of a vertex at the same position may be different from self
        uint32_t indexOffset; // offset into index buffer where the triangle is defined from 3 vertices}
        // indexOffset is always divisible by 3
    };
    MemberRecord adjTriangles[1]; // will always be a member of at least its own triangle
};

Then the entire vertex adjacency list can be packed into one array and allocated with our LinearAddressAllocator.
But obviously a cumulative-histogram/prefix-sum/skip-list is necessary
Member trinagle count for a vertex can be obtained from the cumulative-histrogram/prefix-sum/skip-list

Epic PR by @Przemog1 will take care of this


Add JSON support in query and response

Now you can pass JSON object to insert/update queries, and it will stringify it.
When you run "select", it will automatically parse it to JSON object (if it success)
	conn=mysql.createPool({
		host:'localhost',
		user:'root',
		password:''
	})

	conn.query('select ?',[{obj:true}],function(err,rows){
		console.log(rows)
	})

Console Result:
           [ { '{"obj":true}': { obj: true } } ]

As you can see. The JSON object converted to string.

Who see this commit, and want this merge (until it will accepted) you can manually install it using:
npm i @aminadav/node-mysql

Thank you for this PR! I added a few comments and also, we need you to add tests for all the new functionality and add documentation to the README for the functionality as well. Also, your changes case many of our tests to fail, so please look into the failures and get the existing tests to pass.

Do I need to change the version number in package.json?

I think reverting that autocommit will do a lot?

I have reverting it... didn't pushed it yet

Using Example:
Inserting:
      conn.query('insert into table ?',{a:{json_column:true }},function(){
    	} )

Quering:
    conn.query('select * from table',function(err,rows){
			console.log(rows	)
		} )

Result:
[ { json_column: { me: true } } ]

I seems the tests are failing because of linting issues
for easiness ;) :
/home/travis/build/felixge/node-mysql/lib/protocol/Parser.js
  301:11  error  Missing semicolon      semi
  304:29  error  Missing semicolon      semi
  305:43  error  Missing semicolon      semi
  307:15  error  Empty block statement  no-empty
/home/travis/build/felixge/node-mysql/lib/protocol/SqlString.js
  42:55  error  Missing semicolon  semi
  47:36  error  Missing semicolon  semi
/home/travis/build/felixge/node-mysql/index.js
   3:1  warning  Missing JSDoc parameter description for 'config'            valid-jsdoc
   3:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  15:1  warning  Missing JSDoc parameter description for 'config'            valid-jsdoc
  15:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  27:1  warning  Missing JSDoc parameter description for 'config'            valid-jsdoc
  27:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  38:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  38:1  warning  Missing JSDoc for parameter 'sql'                           valid-jsdoc
  38:1  warning  Missing JSDoc for parameter 'values'                        valid-jsdoc
  38:1  warning  Missing JSDoc for parameter 'callback'                      valid-jsdoc
  48:1  warning  Missing JSDoc parameter description for 'value'             valid-jsdoc
  48:1  warning  Missing JSDoc parameter description for 'stringifyObjects'  valid-jsdoc
  48:1  warning  Missing JSDoc parameter description for 'timeZone'          valid-jsdoc
  48:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  61:1  warning  Missing JSDoc parameter description for 'value'             valid-jsdoc
  61:1  warning  Missing JSDoc parameter description for 'forbidQualified'   valid-jsdoc
  61:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  73:1  warning  Missing JSDoc parameter description for 'sql'               valid-jsdoc
  73:1  warning  Missing JSDoc parameter description for 'values'            valid-jsdoc
  73:1  warning  Missing JSDoc parameter description for 'stringifyObjects'  valid-jsdoc
  73:1  warning  Missing JSDoc parameter description for 'timeZone'          valid-jsdoc
  73:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  95:1  warning  Missing JSDoc @returns for function                         valid-jsdoc
  95:1  warning  Missing JSDoc for parameter 'className'                     valid-jsdoc

Fixed

Hi @AminaG , unfortunately this PR is not backwards-compatible, so there is no timeline when we could ever incorporate the changes. The reason is that the changes here look at all columns and sniff their string contents to see if they look like they are a JSON object and parse it, which will break a lot of people.
This PR has the following two issues that need to be addressed:

People currently storing JSON objects in their existing string columns should not suddenly get back JSON objects. This will cause their code to break.
We do not want to introduce any new "maybe types" into this code. This introduces a maybe type, because the given column may be a string or an object, depending on what was in the column. This makes everyone's code very verbose, as they will have to always add guards everywhere.

Also, as far as I can tell, you only have tests for the escaping part; we need tests for the parsing part as well.h

What are you suggesting?
You right. if a end-user for example enter in text input field for his name {a:'1'} then it will be returned as object, but it should be string.

Seems this should be implemented in lib/protocol/packets/RowDataPacket.js:typeCast, the same way dates are.

I can take this over, let me know.


Functional test for customized XML marshal/unmarshal for user defined…

… aliases
Signed-off-by: Hao Yu<EMAIL_ADDRESS>
What this PR does / why we need it:
This PR adds function test to demonstrate and test the effect of the recently merged PR, #4927. The said PR fixed a VMI migration issue where some device aliases in the domain XML were not kept consistent during the migration.
Following a sound review suggestion, https://github.com/kubevirt/kubevirt/pull/4927#discussion_r573059909, we added a end-to-end migration test case with a tablet device in the migratable VMI. The newly added test will carry out a successfully migration with the fix defined in #4927 , but will fail the migration without the fix.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
The added function test directly follows the suggestion at https://github.com/kubevirt/kubevirt/pull/4927#discussion_r573059909, in PR #4927 .
Release note:

"NONE"

/assign @stu-gott @rmohr

/ok-to-test

/retest

/retest

/retest

/retest

/retest

/retest

/lgtm

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/approve

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest


Typing for Panic Lua classes (object.lua): class() and .extends()

The Playdate Lua SDK includes an object/class implementation which is called with the following syntax:
class("MySprite").extends("playdate.graphics.sprite")

Both these parts are required, the bulk of the class setup actually occurs in .extends and class("MySprite") alone does not create a usable class. In the example above there is an implicit creation of a MySprite in the _G table making it globally accessible -- this makes it difficult for lua-language-server to know where a MySprite object is declared.
Currently I am using the following workaround:
class("MySprite").extends("playdate.graphics.sprite")
---@class MySprite: _Sprite
MySprite = MySprite or {}

I have submitted an enhancement request at devforum.play.date for a trivial enhancement which have .extends() returning the class (it currently returns nil). This would allow the following syntax which feels relatively clear, if still technically redundant:
---@class MySprite: _Sprite
MySprite = class("MySprite").extends("playdate.graphics.sprite")

I think with this I would not define the return type of .extends() which would let the type-checker off the hook.

Also need to somehow inject .super as a field for new classes (empty or not).
Workaround:
---@field super any

@notpeter
---@class TextSprite: playdate.graphics.sprite
---@field text string
---@field font _Font
---@field alignment integer
---@overload fun(text: string): TextSprite
TextSprite = class("TextSprite").extends(playdate.graphics.sprite) or TextSprite -- no-op for LuaLS

---init
---@param text string
function TextSprite:init(text)
  self.text = text
end

-- t Will be recognized as TextSprite
local t = TextSprite("str")

Thanks for this @erasin.  I had tried to use ---@field __call but it didn't work.
I updated the readme to include this.
I wish there was a way to explicitly document the constructor with comments and just not the limited fun() function format. Perhaps via ---@meta if you included both the ---@class and an identically named function stub with LuaCATS comments. Dunno.


Dynamic variable scope is broken for +=

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
This code now only executes correctly when there's a breakpoint on it.
Expected behavior
function Test-Recursively {
    [CmdletBinding()]param($InputObject)
    if ($t -is [string] -and [string]::IsNullOrWhiteSpace($t)) {
        $t += "  "
    } else {
        $t = "  "
    }
    $result = "$t.`n"

    $null, $InputObject = $InputObject
    if ($InputObject) {
        $result += Test-Recursively $InputObject
    }
    $result
}

Test-Recursively 1,2,3

Should Output:
  .
    .
      .

Actual behavior
The if block doesn't work as expected:
Test-Recursively 1,2,3
  .
  .
  .

If I put the code in a file and set a breakpoint on line 4, it works again:
Set-PSBreakpoint Repro.ps1 4 -Action {}
Test-Recursively 1,2,3
  .
    .
      .

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.22622
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals

Note that if I change line 4 from:
        $t += "  "

To:
        $t = $t + "  "

This problem goes away.
It seems like this has been a bug for a long time, but I just don't understand the conditions that cause "+=" to just completely stop doing it's thing.

I think I have seen this before but it needs someone with better search skills than me - search doesn't like being asked for issues containing +=
$i = $i + 1
$i ++
$i += 1

Should be the same.
The first is $local:i = $whatever:i + 1
The last is  $local:i = $local:i + 1  and so fails
I would expect the middle one to work like the last but it works like the first.
Weirdly it is different if I run it in Windows Powershell normally, and powershell -version 2 -noprofile
PS>  $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.22000.832
...

PS>  function Test-Recursively {
>>     param($InputObject)
>>       Write-Verbose -Verbose "t was $t" ; $t += 1
>>      Write-Verbose -Verbose $t
>>      $null, $InputObject = $InputObject
>>      if ($InputObject) { Test-Recursively $InputObject}
>>      $t
>>  }

PS>  test-Recursively 1,2,3
VERBOSE: t was
VERBOSE: 1
VERBOSE: t was 1
VERBOSE: 1
VERBOSE: t was 1
VERBOSE: 1
1
1
1

PS>  powershell -version 2 -noprofile
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS> function Test-Recursively {
>>     param($InputObject)
>>       Write-Verbose -Verbose "t was $t" ; $t += 1
>>      Write-Verbose -Verbose $t
>>      $null, $InputObject = $InputObject
>>      if ($InputObject) { Test-Recursively $InputObject}
>>      $t
>>  }
>>

PS > test-Recursively 1,2,3
VERBOSE: t was
VERBOSE: 1
VERBOSE: t was 1
VERBOSE: 2
VERBOSE: t was 2
VERBOSE: 3
3
2
1

We talked this over a bit over discord and it seems like this is a bug that has existed for a long time, but in this case was masked by Pester code coverage adding breakpoints.
The bug being that the code gen for += statements assumes that the current value is also an optimized local.
So in the case of this scriptblock:
$n += 1

The optimized code gen will look like this:
locals.Item009 = Fake.Dynamic<Func<CallSite, object, object>>(PSVariableAssignmentBinder.Get())(
    Fake.Dynamic<Func<CallSite, object, int, object>>(
        PSBinaryOperationBinder.Get(ExpressionType.Add, ignoreCase: true, scalarCompare: false))(
            locals.Item009,
            1));

When it should look like this:
locals.Item009 = Fake.Dynamic<Func<CallSite, object, object>>(PSVariableAssignmentBinder.Get())(
    Fake.Dynamic<Func<CallSite, object, int, object>>(
        PSBinaryOperationBinder.Get(ExpressionType.Add, ignoreCase: true,scalarCompare: false))(
             VariableOps.GetVariableValue(Fake.Const<VariablePath>("n"), context, Fake.Const<VariableExpressionAst>("$n"),
             1));

The workaround is to use $n = $n + 1 or $n++ instead which should be equivalent, but is not in this case due to this bug.

Note that this bug also exists in 5.1 (and possibly earlier). Opening up to the Engine WG to discuss as it would be a breaking change.

I think the original issue is #11297 - backstory starts here.

WG-Engine discussed this and the related issue #11297 yesterday.
We agree that is is somewhat buggy and inconsistent behaviour that $a += $b does not behave the same as $a = $a + $b in some circumstances. However, given this was a change made in PowerShell v3 and has remained the same way in the years since, we do not think this level of a breaking change can be accepted.
Rather, we should look to update our documentation so that users are as aware as possible that this discrepancy exists and know the right ways to work around it when they need to do so.
@sdwheeler I am unsure which document this information should go into, but we need to capture and possibly expand on the notes linked in #11297 - https://github.com/nightroman/PowerShellTraps/tree/main/Basic/Compound-assignment-operators.
Currently it seems as though the only place this is documented is the WMF v3 release notes, so we need to call this out in (I guess?) our operator documentation. I believe this will affect all compound assignment operators (+=, *=, -=, and /=) as well.
However, for these issues specifically we determined that there is not going to be an opportunity to change the behaviour, and that doing so is extremely non-trivial due to the nature of how and why the change was introduced. As such, we will be closing these issues as Won't Fix.

This is documented in https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_assignment_operators
Please open a Docs issue and provide the information needed in the changes to docs.

@vexx32 Can we at least get a Set-StrictMode error "use $x = $x + 1 instead of $x += 1" $x is in outer scope? It should be relatively easy to implement in all op= operators.
Set-StrictMode is such an awesome tool for helping users not to fall into known pitfalls without introduction breaking changes, we should use it more.

Other folks would know better than I do on that, but I don't think there's a reliable way StrictMode could enforce that short of just preventing usage of += and other compound operators completely, without introducing the potential for excessive slowdowns on parsing/running most scripts.

I can look into it and try to create a PoC that could be measured. Just comparing the target variable scope to the current one sounds like it would work.

Actually, I did more testing and I think the proper resolution is to add new Set-StrictMode version to not allow compound assignment operate on non-existent variables. Since compound assignment have to retrieve the value anyway, it would see it does not exist and error out, without any performance impact. In the error, we could say that it does not use dynamic scope, so use long form instead if you want this behavior:
> function Test-Increment { $x++; $x }
> function Test-Assign { $x = $x + 1; $x }
> function Test-CompoundAssign { $x += 1; $x }
> Set-StrictMode -Version 3.0
> Test-Increment
InvalidOperation: The variable '$x' cannot be retrieved because it has not been set.
InvalidOperation: The variable '$x' cannot be retrieved because it has not been set.
> Test-Assign
InvalidOperation: The variable '$x' cannot be retrieved because it has not been set.
> Test-CompoundAssign
1

I can create a new issue with feature request for the Set-StrictMode -Version 4.0, and we can keep this one closed as won't fix to not introduce breaking behavior without opt-in.

@vexx32 Is the null-coalescing assignment operator ??= considered a compound operator? For example, does is support dynamic scoping?


rust assignments

rust assignments.

Hey Nathan,
I was wondering if it's possible for ai_reason to have multiple reasons for making a move, and if so how does it determine which reason takes precedence?

So, regarding the  Rust Tic Tac Toe game, the AI determines its moves based on evaluating the winning moves and threatening moves I believe ranker.rs. The moves are are prioritized  using find_best_move. priority Winning moves,  then threatening moves.
I think :)


Typo

Hi,
We have do a patch for correct typo s/Cancal/Cancel/
typo_cancal_cancel.patch.txt

Thank you very much for pointing out the typos. They have now been fixed.


Implement login with email link

Issue opened accidentally, I thought I was working on my own repository, apologies for any inconvenience.


Exiting the seat puts me in the void!

As the title says everytime i exit the seat i get thrown into the void! which is a pain in the butt because i play survival and lose everything.

Can you give me a step-bystep set of instructions on how to replicate this?  Is the seat on the rocket or being placed in the world?  Is there a particular block you are placing it on?

it is in a unbuilt rocket on top of a liquid fuel tank. lastest version of AR in 1.10.2 I place the seat then right click it. the rocket has not been built by the assembler yet. and then i push Lshift to dismount and i get thrown into the void!

I'm not able to replicate this.  My setup: http://imgur.com/KpSYXRV.png  Can you post a picture of the setup and a list of installed mods and forge version?

Zmaster copy this setup i just made is what i do every one of my rockets! im just installed the latest forge version which is 2111. and i have over 40 mods installed. so the list is pretty long.
Copy this setup throws me into the void everytime! http://imgur.com/a/LnQiz , http://imgur.com/MzLwv7A
The mods are:
Immersive Engineering
Mekanism
Ender IO
Ender Storage
Ender Core
Advanced Rocketry
AutoPickup
Extreme Reactors
Brandon's Core
Draconic Evolution
CodeChickenCore
Calculator
cxlibrary
Extra Utilities 2
More Furnaces
Advanced Generators
Pressure Pipes
Flux Networks
Quantum FLux
ShetiphianCore
TheOneProbe
JEI
The stuff extension
ZeroCore
Sonar Core
Prefab
Nether Metals
Multistorage
Iron chest
Multipage chest
Mekanism Generators
Mekanism Tools
Malisis Core
Malisis Doors
Libvulpes
Heaven and Hell
God's Weapons
Guide API
Floocraft
Bdlib

Alright, I can replicate with that setup.

Awesome

Also Zmaster i watch the videos on how to program a planet id chip and that didnt work because the planet analzer had a name change and now longer includes the planet selector can u explain to me how to program one?

So for some reason my email didn't make it to github, but anyway..
If you put a planet id chip into the rocket (before or after assembly, doesn't matter) then click the select destination/planet button, it'll open up a planet screen from which you can select the destination.

oh okay. and dont worry about it Zmaster! Github tweeted a couple days ago they were having problems with some stuff and idk if they still are but they might

If i find another issue ill report it here but if i have another question ill post it on curse.

So will the seat be fixed in the next release?

Yes, and the github tweet was due to a massive cyber attack that was resolved late friday if it's the same one i think you're referring to

maybe idk i dont pay much attention to what time the tweet was sent out!

You put it in the guidance computer of a constructed rocket and click
select planet/destination and that should bring up the same menu as the
planet selector


Implementation of punctual lights

Have you cross checked, if your solution also works, when the light is animated?
Actually, the same problem occurs with the camera.

@UX3D-nopper I added support for light animation (tested with light animation exported from blender, and imported back)
I checked for camera, but it seems to work (tested with camera animation exported from blender, and imported back)

@UX3D-schmithuesen If possible, I would like to manage myself PR merging / stuff regarding importer part of the addon

Okay, sure! So you just want some comments when you create a PR?


Packaging a multi-module project

Hi!
I have a multi module project here which I'm trying to publish as a spark package. It has 'core' and 'spark' modules, which would be bundled together in a jar and published.
The README doesn't seem to contain instructions for this -- what changes would be needed to package and publish a multi-module project?
Thanks!
Anurag

If spark depends on core, and core can be find on a repository (maven, bintray, github), you may simply use spark/spPublish in the sbt console. Please set all related keys (sparkVersion, sparkComponents, spDependencies, ...) under spark.
If you need more information on project scoping, please check out the sbt docs.


[FEATURE]: Add regex matching to spreadscalers

Description
This feature lets you deploy to a set of labels which match the RegEx rather than just being equal to a label. This could allow for the following:

may reduce the number of labels per-host
keep traffic within a single availability zone (for use with Nats Leaf Nodes)
should be backwards compatible (provided your label doesn't have , *, + etc...)

Example
Imagine a set of 5 nodes, each with the following zone labels:

us-east-1
us-east-2
us-west-1
us-west-2
eu-west-1

And the following spreadscaler config:
- type: spreadscaler
  properties:
    replicas: 100
    spread:
      - name: spread-a
        requirements:
          zone: ([a-z]{2})-west-1

Would result in deployment to:

us-west-1
eu-west-1

This prevents the need for separate labels for country, region and availability zone.

Ooh @jamesstocktonj1 this is a really cool feature idea! I don't think this would be all that difficult to implement in the spreadscalers + daemonscalers, and we might be able to just treat the whole thing as regex. We should publish recommendations here if there are issues with escaping + special characters in YAML strings.
Notably this would not allow for regex matching on the key of the label, which I think is okay. Happy to help point in the right direction to where this can be implemented

@brooksmtownsend Thanks for the feedback! I have used regex within yaml files before and they can just be wrapped in quote marks if/when escape characters become an issue. But I will be sure to check this out when testing.

This is a cool idea; I can imagine a lot of different ways this could be leveraged.


Feature Request: Add "nofollow" and "target" options to "add Link" form

Add an option to choose the target of the link and the ability to add (or not) "nofollow" rel. Something like that:

We released the Pagekit Beta today. I close this issue because the code base completely changed. Please open a new issue if it still exists.


Error installing version 0.4.11 on atom 1.5.3 and 1.9.8

Updating to<EMAIL_ADDRESS>failed.Hide output…

><EMAIL_ADDRESS>install /tmp/apm-install-dir-116718-32691-1wsho88/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas
> node-gyp rebuild

make: Wejście do katalogu `/tmp/apm-install-dir-116718-32691-1wsho88/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas/build'
  CXX(target) Release/obj.target/runas/src/main.o
make: Opuszczenie katalogu `/tmp/apm-install-dir-116718-32691-1wsho88/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas/build'

In file included from ../src/main.cc:1:0:
../../nan/nan.h:311:62: fatal error: nan_persistent_12_inl.h: Nie ma takiego pliku ani katalogu
 # include "nan_persistent_12_inl.h"  // NOLINT(build/include)
                                                              ^
compilation terminated.
The bug is not reproducible, so it is likely a hardware or OS problem.
make: *** [Release/obj.target/runas/src/main.o] Błąd 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 3.13.0-93-generic
gyp ERR! command "node" "/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/apm-install-dir-116718-32691-1wsho88/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas
gyp ERR! node -v v0.10.40
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
npm ERR! Linux 3.13.0-93-generic
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/me/.atom/.apm/.apmrc" "--userconfig" "/home/me/.atom/.apmrc" "install" "/tmp/d-116718-32691-pccgm7/package.tgz" "--target=0.34.5" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/apm-install-dir-116718-32691-1wsho88/npm-debug.log

hi @rubyconvict i've released v1.0.0 which changed many of the underlying dependencies in the package. can you upgrade and see if this is still an issue for you? If so please reopen.

Installing<EMAIL_ADDRESS>to /home/mkalita/.atom/packages ✗

><EMAIL_ADDRESS>install /tmp/apm-install-dir-117313-28197-12vhr34/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas
> node-gyp rebuild

make: Wejście do katalogu `/tmp/apm-install-dir-117313-28197-12vhr34/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas/build'
  CXX(target) Release/obj.target/runas/src/main.o
make: Opuszczenie katalogu `/tmp/apm-install-dir-117313-28197-12vhr34/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas/build'

npm WARN deprecated<EMAIL_ADDRESS>Switch to regular React - this project is no longer maintained
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>|| ^15.0.0 included from recompose will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
In file included from ../src/main.cc:1:0:
../../nan/nan.h:148:53: fatal error: nan_callbacks.h: Nie ma takiego pliku ani katalogu
 #include "nan_callbacks.h"  // NOLINT(build/include)
                                                     ^
compilation terminated.
make: *** [Release/obj.target/runas/src/main.o] Błąd 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 3.13.0-117-generic
gyp ERR! command "node" "/usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/apm-install-dir-117313-28197-12vhr34/node_modules/git-blame/node_modules/pathwatcher/node_modules/runas
gyp ERR! node -v v0.10.40
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
npm ERR! Linux 3.13.0-117-generic
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/home/mkalita/.atom/.apm/.apmrc" "--userconfig" "/home/mkalita/.atom/.apmrc" "install" "/tmp/d-117313-28197-s3aeqq/package.tgz" "--target=0.37.8" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/apm-install-dir-117313-28197-12vhr34/npm-debug.log

I had the same issue today, but the whole thing was probably my fault. I tried to install atom packages for the atom editor which was installed with a different version of node.


Document special test cases

All test cases should have written-out explanations which points to relevant specifications and how you can verify they are correct.
But especially so for something labeled "Special cases"!
@drinckes could you please help to add more documentation in the test case comments here? https://github.com/google/open-location-code/blame/master/test_data/decoding.csv#L19-L24

Those cases apparently were lost in translation when splitting the original test file for both decoding and encoding into separate test files for each. Previous test data can be found in this diff: https://github.com/google/open-location-code/commit/791c604da390a2a418e275fc0105e15864dedb28#diff-e7d87b738825c33824cf3fd32b7314161fc8c425129163ff5e7260fc7288da36

Special cases over 90 latitude and 180 longitude
CFX30000+,90,1,89,1,90,2
CFX30000+,92,1,89,1,90,2
62H20000+,1,180,1,-180,2,-179
62H30000+,1,181,1,-179,2,-178
CFX3X2X2+X2,90,1,89.9998750,1,90,1.0001250

The important part for these tests still lives in encoding.csv (https://github.com/google/open-location-code/blob/a323e80159d6d6170158cc22497250cb86bf3583/test_data/encoding.csv#L19-L28), where the existing comment seems to be enough documentation.
The decoding direction IMO contains no special case, meaning that the tests can probably just be removed from decoding.csv.


compose web: IllegalStateException: could not convert sym to ClassifierSymbol

Was reported in slack:
https://kotlinlang.slack.com/archives/C01F2HV7868/p1622556507126100
In my module serverApp, I can reproduce just with these dependencies added and no additional javascript code in the module (and no common dependencies).

val jsMain by getting {
    dependencies {
        implementation(libs.kotlinxCoroutines)
        implementation(compose.runtime)
        implementation(compose.web.core)
        implementation(compose.web.widgets)
    }
}
But in my module browserApp (which where the actual compose code lives), I’m not able to reproduce with a similar set of dependencies.

There was a similar stacktrace from the compiler caused by ktor and a coroutines version conflict, which was resolved with the ktor 1.6 release.  This could be a similar issue, although the error isn’t really helpful to isolate further.

This should reproduce the issue with ./gradlew assemble
project.zip

Compose (and androidx) still use Coroutines 1.4.3 under the hood, and the JS artifact is a compiled artifact, which is not binary compatible with 1.5.0

There is a new (not very official) release 0.0.0-web-dev-14.1 and it has coroutines version overridden. It's built from a "fix" branch, so people could start migrating to new APIs sooner rather than waiting for androidx getting the coroutines new version.
kotlinVersion=1.5.10
kotlinxCoroutinesVersion=1.5.0
composeWebVersion=0.0.0-web-dev-14.1

having these versions, ./gradlew assemble was successful.
I'm not closing the issue for now. Please let me know how dev-14.1 works for you. Thanks :)

0.0.0-web-dev-14.1 fixed the issue for me.

It works for me too. But I don't like the current dependency behavior with the compiled IR klib artifacts at all. This prevents you changing one dependency, you can't simple override one usage.
Eg I have a bootstrap compose wrapper library, and to use 14.1, I have to update compose not only in the consumer project, but in the library as well. This is not a problem with owned libraries, but it is one with third party libraries.

@hfhbd I see your point.  The thing is that sometimes such things can't be avoided unfortunately.
We hope/expect it won't happen often though, especially when we get to some mature state of compose-web.
Thanks for your feedback!

https://android-review.googlesource.com/c/platform/frameworks/support/+/1717755 - is not merged at the moment.
So I guess we'll need to make a special build  from a "fix" branch for the next release as well.
Closing this for now.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


fix dependency mapping of dompurify in utilities package

Detailed description

Describe in detail the issue you're having.

The NextJS staging environment did not build properly as dompurity, which is an import for the markdownToHTML utility, was identified as a devDependency so it isn't getting picked up on the application side. A fix has already been pushed directly to the release branch, but this is an issue to track this fix in case other adopters pick up this issue in v1.8.0-rc.0.

Is this a feature request (new component, new icon), a bug, or a general
issue?

bug

Is this issue related to a specific component?

markdownTo

What did you expect to happen? What happened instead? What would you like to
see changed?

Need to move dompurity into dependencies in the utilities package

What version of the IBM.com Library are you using?

v1.8.0-rc.0
Additional information

ibmdotcom-nextjs-staging will be failing until we get this fix in rc.1.

FYI; Seems that we need to do similar for marked, too: https://github.com/carbon-design-system/ibm-dotcom-library/blob/7fea9b2/packages/utilities/package.json#L70 https://github.com/carbon-design-system/ibm-dotcom-library/blob/41ebf6f/packages/utilities/src/utilities/markdownToHtml/markdownToHtml.js#L9


Enforce writing JSON files using UTF8 No BOM encoding

Fixes microsoft/coe-starter-kit#3717. This PR is to run integration tests on your PR https://github.com/microsoft/coe-alm-accelerator-templates/pull/212 from @fredrikhr

This PR was created to incorporate the updates from https://github.com/microsoft/coe-alm-accelerator-templates/pull/212 per our guidelines on reviewing external contributor PRs https://github.com/microsoft/coe-starter-kit/wiki/External-Contribution-Review-(Fork-PRs).
I've also merged the latest from main and resolved the merge conflicts in this PR and incorporated non-ASCII characters in our export json payload in the integration test to cover the specific issue going forward.
Once this PR is merged we can close https://github.com/microsoft/coe-alm-accelerator-templates/pull/212
@RajeevPentyala @fredrikhr


Components storybook

This demonstrates that component hot reloading works without additional configuration in storybook as long as we import the components from the src/ directory. Lerna does the right thing and links these files as expected. Looking at the dependency from the docs package to the vue-components package this is fine, because the src/ files are part of the package contents.
It does come with a risk of creating a disconnect between the standard usage of components and how we use storybook to develop them, think import { Component } from '@wmde/wikit-vue-components'; vs import Component from '@wmde/wikit-vue-components/src/components/Component';. I think that this is probably fine for now and we can revisit this if it becomes a problem.
Bug: https://phabricator.wikimedia.org/T257825

@wiese thanks for spotting that.
I now turned it around to not use a src file, but directly use the commonjs build instead. You can start storybook and run docker-compose run --rm node lerna run dev in a separate terminal. Uploaded for early feedback, but I want to ponder this a bit more and add some docs.

You can start storybook and run docker-compose run --rm node lerna run dev in a separate terminal.

FWIW workflow-wise this sounds very intuitive to me.
On the other hand (this is a mere hunch), things like vue-docgen-loader0 - on behalf of addon-docs (to show the slots, properties) - may need access to the very source. Fingers crossed.

@wiese Yes, it seems that the addon-docs "prop tables" indeed can't be generated from a component at run time. I checked that this works out of the box with 3a97630 but no longer works with the latest state. What do we do?

With #105 and friends merged, I think this can be closed! :tada:


Ciao-cli: create a new cluster

Allow the user to create a new k8s cluster via the ciao-cli interface.

Depends on #709

add bat tests to test this feature end to end.

we changed our k8s strategy, so this is no longer relevant.


Image does not fit 8 GB flash drive

Most Clevers are shipped with 8 GB flash drive.

This problem solved in https://github.com/CopterExpress/clever/commit/a91f9e5a6b460027ca4ca250bdbebca4d7bf687c.
And image available in https://github.com/CopterExpress/clever/releases/tag/v0.6


docs: add Column example with width

Changes proposed in this PR:

Add column example.

[x] I have followed (at least) the PR section of the contributing guide.
@90milesbridge/tigger

Pull Request Test Coverage Report for Build 2783

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.455%

Totals

Change from base Build 2753:
0.0%

Covered Lines:
2580

Relevant Lines:
3097

💛  - Coveralls


Increase the importance of avatars, show them wherever possible

This needs some specifictation to know when this is fulfilled so it can be closed

What is the specification? Could you give an example?

What does "wherever possible" mean in practice? Where do you want to see it?

It is examples.
What is the point of avatars if they are displayed only in chat channels? There are players who do not communicate in chats.


Remove go get <binary> instances

Go getting bninaries has been deprecated in go1.17 and not supported
in go1.18.
Signed-off-by: Andrea Panattoni<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
12 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.2%) to 15.585%

Files with Coverage Reduction
New Missed Lines
%

controllers/sriovibnetwork_controller.go
2
65.35%

controllers/sriovnetwork_controller.go
4
67.0%

api/v1/helper.go
6
34.2%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1145

Relevant Lines:
7347

💛  - Coveralls

LGTM


do stats at parse: new pairsamtools

tested commit, that moves statistics gathering to parsing step of the pipeline. This way we are getting stats virtually for free (performance degradation is minor - unnoticeable in a cluster environment anyways). Before stats were gathered at the merge_chunks_in_runs step by decompressing large pairsam file and parsing it one more time - it has proven to be a major slow down, taking almost as much time as the merging itself.
Commit has been tested using test data and big data (1 lane of sequencing data).
We created one more process and an output folder, but we might consider some simplifications afterwards - let's just do single step at a time to avoid braking the whole thing completely.

will upload new docker and test


Functions tab is missing in the Cloud

Is this thing intended to happen cuz I can't find another way to check functions logs, thanks

It's under Logs, using the filter.

Well then this not good. It used to have separate tab and see all the functions with there url. Please is possible we get the old functions tab

I'm just another user by I'm sure it was important to NHost to remove duplicate functionality in the dashboard and free up resources for critical development tasks elsewhere.
If you prefer the previous version you can add suggestions or comments to this issue where I also expressed a fondness for the earlier split: https://github.com/nhost/nhost/issues/1581 but I recognize the limited time available to do all the things NHost wants to.
In the mean time you could try some of the workarounds I mention there:

focus on just Functions from the drop down, narrow your date/time filters.
search the page by the path to your function: you'll note that the wrapper around each log message has your function's path in it

Duplicate of https://github.com/nhost/nhost/issues/1581


setup-user: Accept an existing /boot mount

For RHCOS, dracut mounts /boot in the FIPS case, and things
blow up if we try to mount it twice.
Also bigger picture at this point we have a crap ton of services
all trying to mount /boot; we might as well just add a boot.mount
unit to our initramfs.

For my understanding.. If both ignition-setup-user.service and rhcos-fips.service have  MountFlags=slave how are we hitting this problem?

Because it's actually dracut that mounts /boot and it does so globally.

https://github.com/dracutdevs/dracut/blob/05b75703b0e378f0dac2db89dd5a4ad88ed9e529/modules.d/01fips/fips.sh#L3

(And yeah this should go to master too in theory, but it's not urgent and we should do a bigger rework there around having a single boot.mount or so)

having a single boot.mount

agree

Strictly speaking, I think just (re-)backporting e96e7fc would fix this. But this works too.

Ahh.  OK...hmm, yes, probably worth backporting that too.

Oh I see, I did it implicitly.


Getting error: If you wish to make changes to it, then you will have to pass the --allow-live flag

I'm getting the following error when deploying the theme to shoplift store:
If you wish to make changes to it, then you will have to pass the --allow-live flag

We're using themekit for some of the behind the scenes connections with Shopify. By default, you cannot use themekit's watch or deploy commands on the live theme. This is to prevent people from messing up the live theme and to encourage the use of development themes.
The error messages is a little misleading since we're not using the themekit CLI, we're using the integrated node package. So passing --allow-live doesn't actually have any impact.
I'll look further into this when I get a chance.

Have any workaround this?

Yes this is fixed in this commit https://github.com/WorkshopCLI/workshop-advanced-gulp/commit/b7c8eeb1d699dd4fc22bbe9653e7b6b7860aef9c


Abbreviated commands /l /reg do not work

I made 3 servers using waterfall, configured everything, but to log in, for example, you need to enter the full command /login, not /l

Hi, @Ciferblood!
You need to allow these commands before logging into nLogin BungeeCord configuration.


Arc3D bad calculations

    //Get the points in the unit circle (circle with a radius of 1f).
    var centerAsVc2 = new Vector2(center.x, center.z);
    var startUnitCircle = (new Vector2(start.x, start.z) - centerAsVc2) / radius;
    var endUnitCircle = (new Vector2(end.x, end.z) - centerAsVc2) / radius;

    //Get the equivalent degree on the unit circle.
    var startDegree = startUnitCircle.x.ArcCos().ToDegreeFromRadian();
    var endDegree = endUnitCircle.x.ArcCos().ToDegreeFromRadian();`

    In this case the Z (Y) value isnt taken into account, this should be fixed by simply using the Vector2.normalized, instead of all this
    nonsense.
    Then get the angles the same way from there.

Not needed.


Set long_description_content_type

By clarifying that it's markdown, the description should render better on PyPI.

Awesome, Thanks


Bug: (dnd5e 3x) Vehicle Sheet - Description tab issues

When there is a description entered into the description tab, the next time the vehicle is opened, this error occurs:
logging.ts:37 tidy5e-sheet | Failed to render svelte tab TypeError: Cannot read properties of null (reading 'addEventListener')
    at Tidy5eVehicleSheet.activateListeners (vehicle-sheet.mjs:270:1)
    at Object.activateFoundryJQueryListeners (Tidy5eKgarVehicleSheet.ts:135:15)
    at activateProseMirrorListeners (VehicleDescriptionTab.svelte:12:14)
    at Object.mount [as m] (VehicleDescriptionTab.svelte:26:15)
    at Object.mount [as m] (RerenderAfterFormSubmission.svelte:2:30)
    at Object.mount [as m] (RerenderAfterFormSubmission.svelte:12:25)
    at mount (RerenderAfterFormSubmission.svelte:11:32)
    at targetCmp.$$.fragment.m (svelte-hooks.js?v=4c851f67:291:24)
    at mount_component (chunk-J2VQCU4O.js?v=4c851f67:2134:24)
    at Object.mount [as m] (VehicleDescriptionTab.svelte:28:7)

When saving changes to the description tab, this error occurs:
VehicleDescriptionTab.svelte:24 Uncaught (in promise) TypeError: dispose is not a function
    at Object.destroy [as d] (VehicleDescriptionTab.svelte:24:36)
    at Object.destroy [as d] (RerenderAfterFormSubmission.svelte:2:30)
    at Object.destroy [as d] (RerenderAfterFormSubmission.svelte:12:25)
    at chunk-J2VQCU4O.js?v=4c851f67:1408:17
    at run (chunk-J2VQCU4O.js?v=4c851f67:30:10)
    at Array.forEach (<anonymous>)
    at run_all (chunk-J2VQCU4O.js?v=4c851f67:36:7)
    at check_outros (chunk-J2VQCU4O.js?v=4c851f67:1389:5)
    at Object.update [as p] (RerenderAfterFormSubmission.svelte:11:32)
    at update (chunk-J2VQCU4O.js?v=4c851f67:1351:32)

Fixed.


Revert "Defer last option breaking (#1114)"

This reverts commit b458397a37084b20792bc0c24ddb95c0d397550a.
Reintroduced last that returns Option

Pull Request Test Coverage Report for Build 3628
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 82.766%

Totals

Change from base Build 3626:
0.08%

Covered Lines:
4255

Relevant Lines:
5141

💛  - Coveralls


Optimising the look of the command outputs

Adding New Look and Feel of the CLI of the command execution
The new output will now look like :

Tests are also passing:

@yorinasub17 Please review these changes :+1:


error during rendering

Hello, my English is not very good, but I would like to ask you to help me look at this problem, how can I solve it? I'm using vuesion for the first time. I'm looking forward to your answer. Thank you first.
error: error during rendering: /foo; error: {"stack":"Error: Error: Request failed with status code 404\n    at Store.eval (webpack-internal:///./src/app/foo/actions.ts:61:31)\n    at step (webpack-internal:///./src/app/foo/actions.ts:34:23)\n    at Object.eval [as throw] (webpack-internal:///./src/app/foo/actions.ts:15:53)\n    at rejected (webpack-internal:///./src/app/foo/actions.ts:7:65)\n    at process._tickCallback (internal/process/next_tick.js:68:7)","message":"Error: Request failed with status code 404"}

Hello @zhanghanbing1998,
Can you tell me the steps on how to reproduce this error?
basically, it says that the URL you try to request from the prefetch function of your component doesn't exist. That means you have to either remove this request or make sure that the endpoint is available.

I'm sorry to reply to you now. I created the foo module based on the document. I used the npm run generate script and made an error when accessing http://localhost:3000/foo.

@zhanghanbing1998 just to understand it correctly. You followed the guide in the documentation and this step: https://vuesion.github.io/docs/en/guide/cli.html#what-is-a-module did not work for you. Is that correct?

I found the reason, because this problem arose after deleting unnecessary code and files according to the document.https://vuesion.github.io/docs/en/guide/clean-up.html，after I clone the project again and try again, this problem does not arise. Finally, I want to ask you whether the redundant code deleted in the document is the dependency of creating the module.https://vuesion.github.io/docs/en/guide/cli.html

@zhanghanbing1998 Ok, I understand it now.
The blueprints for the module and connected components are based on the counter module and as you deleted the counter route on the server side the newly generated module is not able to reach the API.
I might change the order of the guide to do the cleanup step after the module creation to avoid this confusion in the future. Do you think this would be enough?

Thank you. That's good. Thank you very much for answering my question. vuesion is very good. I spent a lot of time to solve SSR before. vuesion solved my problem better. Thank you for developing it. Finally, I wish you a good job!

Thank you very much for your support @zhanghanbing1998 😊
I'll let you know as soon as I made the changes to the docs.

hello,Johannes Werner,I have another question to ask you. I use the "vue-awesome-swiper" as a carousel plug-in, but this component relies on windows objects and document objects. However, when doing SSR, node does not have these objects, such as: window, document, how to solve this problem?

Hey, you can use this trick: https://vuesion.github.io/docs/en/tutorials/third-party.html scroll to the bottom

Thank you. It's very useful.


Duplicate "magic" BINs

My recollection was that nycdoitt:bin was kept around because it was a unique identifier that would make it easier in the future to integrate updates from NYC. I admit that I can't find this in the import documentation, but it might of been in a google+ meeting.
Ways 247624968 and 247624969 have duplicate magic values of nycdoitt:bin=3000000. These magic values should be documented on the import's page on the wiki, and we should consider if these special values should be kept.

just wow


extended docs to show conditional shortcut execution

I had other extensions using the same shortcut I wanted to use for duplication, so I had to find out how to make it conditional so that it would only run, when I focus the file in the explorer.
Thought this might be helpful information for other users as well.
What is the purpose of this pull request?
Improve readme.
What changes did you make? (Give an overview)
Added some json to readme.

*bump

Here's mine.
    {
        "key": "ctrl+d",
        "command": "duplicate.execute",
        "when": "explorerViewletVisible && filesExplorerFocus && !explorerResourceIsRoot && !inputFocus"
    },


raftstorev2: add basic layout

What is changed and how it works?
Issue Number: Ref #12842
What's Changed:
This is an attempt to reimplement raftstore using the new assumptions
that peer's range can be overlapped.

Currently, compatability is not considered, though we may think about
how to migrate from old version by the end of this year.

No concrete implementations is added yet, we may choose reuse
implementation from v1 or implementing new logic base on actual
requirement. The principle is
1. do not introduce history debt while reusing code as much as possible.
2. do not change the current implementations.

Check List
Tests

Unit test
Integration test

Release note
None

Also regarding the assumptions:

peer's range can be overlapped: do you mean the actual tablet's data range or the region's range.
"Currently, compatability is not considered, though we may think about
how to migrate from old version by the end of this year",  does it mean the TiKV won't work for both version until this end of the year? (Or do you mean we will essentially two version of tikv?)

1. peer's range can be overlapped: do you mean the actual tablet's data range or the region's range.

Both can be overlapped.

does it mean the TiKV won't work for both version until this end of the year? (Or do you mean we will essentially two version of tikv?)

Yes, it will work with either one but not both at the same time. There will be only one version TiKV while can start with different version of raftstore.

/LGTM

/merge


remove year, date_recorded, date_released

All readable and settable fields are also removable, except for these three fields. Is there a particular reason for this? If not I'll make a PR to add a .remove_*() method for these three fields.

The named functions are fairly incomplete and written based on how common these fields are, I think. After inheriting this codebase, this was not a concern of mine.
Feel free to submit a PR :)

I agree that exact dates are not common but IMO 'year' is a quite essential attribute (probably because I'm coming from an academic background and all bibliography entries must have a year).


fix discovery start-up deployment issue #816

Closing this one as all the bug fixes will go in master.

@barnstee, I thought you want this in 2.7.199 as well.

No.


Change encoding to UTF-8 in xmlrpc_decode.

Fix XML-RPC UTF-8 issue.

Please accept this pull request


Changed the gradle script.

This pull request fixes #1

This pull request was for demo purposes only.

This pull request was for demo purposes only.


Unrecognised configuration name: plugins

Dear developers,
I installed you plugin using pip3 as suggested. While serving mkdocs I am getting the following:
WARNING -  Config value: 'plugins'. Warning: Unrecognised configuration name: plugins
Could you guide me to make your plugin work?
Thanks,
Martin

Please attach / post your full mkdocs.yml file.

Here is my mkdocs.yml
site_name: title
extra_javascript:
- https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0/MathJax.js?config=TeX-AMS-MML_HTMLorMML
markdown_extensions:
- mdx_math
plugins:
- search
- pdf-export

Sorry for the delayed response. What version of mkdocs are you using? We are using the standard mkdocs plugin infrastructure, so this should actually work just out of the box. You might get better responses from the mkdocs support channels though.

Closing, seems to be an issue with mkdocs rather than this plugin.


Process creation bug

When creating a process sometimes extra process is left over after rename

This may only be happening with duplicate currently

Duplicated in this issue
https://github.com/louisVottero/vtool/issues/325


Enable middleware by default

Cut's down on the number of steps required to install the plugin as this should remove the need to have the user add in the setting to ./config/middleware.js

Thanks ! It's an hidden feature than I don't know ^^


[Feature request] Support loading pbf file from local assets

I imagine a lot of people might want to distribute the vector maps with the app or allow users to download the maps file for usage without the internet connection. Is this something that might be on the roadmap?

I opened a similar issue couple of weeks ago, see this reply in how to implement it: https://github.com/greensopinion/flutter-vector-map-tiles/issues/80#issuecomment-1201519776
Now rethinking it, the implementation will be quite different depending on the use case. It will hard to have a general solution for that I guess.

Thanks @FaFre you're right, by implementing VectorTileProvider you can plug in any kind of map tile source that you want - e.g. over the filesystem, from app assets, from a database, whatever.


Crypt2.munki.recipe is potentially an invalid file

When testing 2.8.1 with @nmcspadden rewrite I get this error:
WARNING: /Users/jonasb/Library/AutoPkg/RecipeRepos/com.github.autopkg.grahamgilbert-recipes/Crypt2/Crypt2.munki.recipe is potentially an invalid file, not adding it to the recipe map! Please file a GitHub Issue for this repo.
More info here: https://macadmins.slack.com/archives/C056155B4/p1691608955567799

I'd take a PR to delete them pretty happily.


Runtime error (mac)

when I run "runbot_mac.command" i get this
  File "/Users/student/Desktop/MusicBot/musicbot/opus_loader.py", line 17, in load_opus_lib

    raise RuntimeError('Could not load an opus lib. Tried %s' % (', '.join(opus_libs)))

 RuntimeError: Could not load an opus lib. Tried libopus-0.x86.dll, libopus-0.x64.dll, libopus-0.dll, libopus.so.0, libopus.0.dylib
logout

running Sierra 10.12.1

I had this same issue but I just figured it out. Did you install Homebrew first?

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Run this in terminal. I started over all the way from the beginning and now my bot is up and running!

I installed it and it doesn't seem to have fixed anything.
Do you need to run anything else after? I'm still getting the same error message.

Looks like you're missing opus which should be installed using brew install opus.

http://macappstore.org/opus/ this is what i did and it worked


Move Login Modal styles to separate component

This separates the login modal styles from the generic modal.

Reviewer: @pierlo-upitup

I see this

@pierlo-upitup Should have documented this. You'll see that until the FormModal changes get merged in #214.

i still see pierlo's problem and #214 is merged. i also rebased this with master locally

@kennyt My bad, this PR also needs to merge: https://github.com/mesosphere/dcos-ui-plugins-private/pull/137/files cc @pierlo-upitup

Nice, that PR is merged and the issue is fixed, but this is what it looks like:

@kennyt Good catch! I will adjust the styles to handle wrapping text.

@kennyt It's fixed now in the plugin's styles, here: https://github.com/mesosphere/dcos-ui-plugins-private/pull/208

@jfurrow is it also possible to set the title of it too so we can hover to read fully?

@kennyt Good point, done! https://github.com/mesosphere/dcos-ui-plugins-private/pull/209


Add table of contents to README (closes #103)

(closes #103)

This is waiting on #104

Merging headed into V2, can review there later.


Windows Binary doesn't work

Application closes before giving any information. It seems to be an issue with MoviePy (library used to convert MP4s to MP3s), as Python is able to download the MP4 with no issues.

?


Inline base read and write methods

Motivation
The basic methods, read_char and write_char are repeatedly executed from the other methods. Looking at the assembly, we can see that generated assembly for methods themselves are so tiny, that the cost of invoking them is more than the cost of actually running the methods themselves. Unfortunately since the methods are inside a namespace they are not automatically inlined as would happen if they were inside a struct/class, so we have to manually inline them.
Comparison
Without inlining: https://godbolt.org/z/5rW4rPeT3
With inlining: https://godbolt.org/z/o5nrhYGdh
Benchmark
On SPOJ INOUTTEST, this results in a ~30% speedup
Without inlining: https://vjudge.net/solution/31119043
With inlining: https://vjudge.net/solution/31119051

FAQ
1. Why not inline the other methods?
Most of the other methods are quite complex, meaning that inlining them does not actually yield much of a benefit since,
A) they are not called as much as read_char and write_char,
B) the cost of invoking them is small compared to what actually goes on inside them.
In some rare cases (e.g. for the vector case) the performance of the inlined version could actually be worse.

Motivation
The basic methods, read_char and write_char are repeatedly executed from the other methods. Looking at the assembly, we can see that generated assembly for methods themselves are so tiny, that the cost of invoking them is more than the cost of actually running the methods themselves. Unfortunately since the methods are inside a namespace they are not automatically inlined as would happen if they were inside a struct/class, so we have to manually inline them.
Comparison
Without inlining: https://godbolt.org/z/5rW4rPeT3
With inlining: https://godbolt.org/z/o5nrhYGdh
Benchmark
On SPOJ INOUTTEST, this results in a ~30% speedup
Without inlining: https://vjudge.net/solution/31119043
With inlining: https://vjudge.net/solution/31119051
FAQ
1. Why not inline the other methods?
Most of the other methods are quite complex, meaning that inlining them does not actually yield much of a benefit since,
A) they are not called as much as read_char and write_char,
B) the cost of invoking them is small compared to what actually goes on inside them.
In some rare cases (e.g. for the vector case) the performance of the inlined version could actually be worse.

Thanks for this, I assumed without much thinking and benchmarking the compiler would be able to optimize this. Looks like it's not the case.


Build script for slides

The build script is fragile because it is easy to make conflicts with a single line of include directories.
Now it is ugly because there are no spaces allowed between those directories so trying to split this across multiple lines is also fragile.
Suggest we consolidate everything under one directory that can be included. Recursive includes is done automatically so it means the script will not need to be changed.

Some courses have latex Beamer slides and these could easily be built to be included as a pdf slideshow. This can be added to the build script quite easily


Vue SFC template cannot display obj which has ref

Version
2.7.2
Reproduction link
codesandbox.io
Steps to reproduce
use obj which has ref variable in template mustache cannot render.
TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Watcher'

    |     property 'vm' -> object with constructor 'VueComponent'

    |     property '_scope' -> object with constructor 'EffectScope'

    |     property 'effects' -> object with constructor 'Array'

    --- index 0 closes the circle

    at JSON.stringify (<anonymous>)

What is expected?
render correctly like vue3
What is actually happening?
error

please upgrade to 2.7.3 , I see your code, why do you put setup on top of script tag, maybe you can remove setup from script;

why do you put setup on top of script tag

🤣 I didn't notice that, it fork from others,  hhhh
it works fine on 2.7.3, thank you! @Teaghy