Dart Migration: NoSuchMethodError: The getter 'isDynamic' was called on null.

When running dart migration on dart 2.12.2 the following exception was thrown.
Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:
https://github.com/dart-lang/sdk/issues/new
Please include the SDK version (2.12.2) in your bug report.
To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.
Exception details:
NoSuchMethodError: The getter 'isDynamic' was called on null.
Receiver: null
Tried calling: isDynamic at offset 4909 in /home/bsutton/git/conduit/conduit/conduit/lib/src/http/managed_object_controller.dart (Operation.get)
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:54:5)
#1      EdgeBuilder._makeEdgeOrigin (package:nnbd_migration/src/edge_builder.dart:3141:25)
#2      EdgeBuilder._checkExpressionNotNull (package:nnbd_migration/src/edge_builder.dart:1985:18)
#3      EdgeBuilder._handleTarget (package:nnbd_migration/src/edge_builder.dart:3056:14)
#4      EdgeBuilder._handlePropertyAccess (package:nnbd_migration/src/edge_builder.dart:2980:20)
#5      EdgeBuilder.visitPrefixedIdentifier (package:nnbd_migration/src/edge_builder.dart:1405:14)
#6      PrefixedIdentifierImpl.accept (package:analyzer/src/dart/ast/ast.dart:8257:49)
#7      EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#8      EdgeBuilder.visitAnnotation (package:nnbd_migration/src/edge_builder.dart:325:7)
#9      AnnotationImpl.accept (package:analyzer/src/dart/ast/ast.dart:280:49)
#10     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#11     EdgeBuilder._dispatchList (package:nnbd_migration/src/edge_builder.dart:2229:7)
#12     EdgeBuilder._handleExecutableDeclaration (package:nnbd_migration/src/edge_builder.dart:2470:5)
#13     EdgeBuilder.visitMethodDeclaration (package:nnbd_migration/src/edge_builder.dart:1243:5)
#14     MethodDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7033:49)
#15     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#16     EdgeBuilder._dispatchList (package:nnbd_migration/src/edge_builder.dart:2229:7)
#17     EdgeBuilder.visitClassOrMixinOrExtensionDeclaration (package:nnbd_migration/src/edge_builder.dart:607:7)
#18     EdgeBuilder.visitClassDeclaration (package:nnbd_migration/src/edge_builder.dart:574:5)
#19     ClassDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:1536:49)
#20     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#21     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#22     GeneralizingAstVisitor.visitCompilationUnit (package:analyzer/dart/ast/visitor.dart:202:51)
#23     CompletenessTracker.visitCompilationUnit. (package:nnbd_migration/src/utilities/completeness_tracker.dart:52:24)
#24     PermissiveModeVisitor.reportExceptionsIfPermissive (package:nnbd_migration/src/utilities/permissive_mode.dart:26:24)
#25     CompletenessTracker.visitCompilationUnit (package:nnbd_migration/src/utilities/completeness_tracker.dart:43:5)
#26     CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2134:49)
#27     NullabilityMigrationImpl.processInput (package:nnbd_migration/src/nullability_migration_impl.dart:244:12)
#28     NonNullableFix.processUnit (package:nnbd_migration/src/front_end/non_nullable_fix.dart:164:15)
#29     _FixCodeProcessor.runLaterPhases. (package:nnbd_migration/migration_cli.dart:1154:19)
#30     _FixCodeProcessor.runLaterPhases. (package:nnbd_migration/migration_cli.dart:1152:28)
#31     _FixCodeProcessor.processResources (package:nnbd_migration/migration_cli.dart:1081:30)

#32     _FixCodeProcessor.runLaterPhases (package:nnbd_migration/migration_cli.dart:1152:5)

#33     MigrationCliRunner.run (package:nnbd_migration/migration_cli.dart:749:24)

#34     MigrateCommand.run (package:nnbd_migration/migration_cli.dart:185:7)

#35     CommandRunner.runCommand (package:args/command_runner.dart:196:13)

#36     DartdevRunner.runCommand (package:dartdev/dartdev.dart:199:18)

#37     runDartdev (package:dartdev/dartdev.dart:53:16)

#38     main (file:///b/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)

Hi @bsutton, thanks for the bug report!  Were you able to make progress by re-running dart migrate with the --ignore-exceptions option?

yes, I stepped around the issue by using the --ignore-exceptions option.
On Wed, 7 Apr 2021 at 09:36, Paul Berry @.***> wrote:

Hi @bsutton https://github.com/bsutton, thanks for the bug report! Were
you able to make progress by re-running dart migrate with the
--ignore-exceptions option?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/45600#issuecomment-814500130,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OECYZJDVTYQ7YNY5STTHOLJBANCNFSM42OTQN6Q
.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


map enhancements

Following enhancemantes would be great

[x] change marker circles to 0.5 or 0.66 of current size
[x] marker and polygons should get solid boarder lines in gray (#808080)
[ ] show coordinates of object together with name when hovering
[x] show coordinates in the popup
[x] when creating a new marker show box to enter coordinates so that marker moves to new location - like in google maps

show coordinates of object together with name when hovering

I don't think we need this. It's sufficient to look up coordinates within the popup.


some treesitter errors, directly after installation

Describe the bug

Directly after I've copied the init.lua into my .config/init.lua, my treesitter commented while compilation, that he can't find several files.
To Reproduce

...
open nvim

nvim-treesitter[lua]: Error during compilation
/usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/cc1: error while loading shared libraries: libisl.so.23: cannot open shared object file: No such file or directory /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/cc1: error while loading shared libraries: libisl.so.23: cannot open shared object file: No such file or directory
Desktop

OS: Steam OS
Terminal: kde terminal

Neovim Version

`NVIM v0.8.0
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/share/nvim"
Run :checkhealth for more info    `

What happens when you run :checkhealth ?

Also, I have no sense of SteamOS, are you sure you installed the package that provides libisl.so to your system?
Either way, this isn't a problem with kickstart.nvim so I'm closing this for now.


Change ndimage.imread to imageio.imread.

Scipy will not support imread from 1.0.0 as its document says:
https://docs.scipy.org/doc/scipy-1.0.0/reference/generated/scipy.misc.imread.html
Change to imageio.imread and add its correspond exception.

Can one of the admins verify this patch?

Thanks @zxcqwe4906!


Apache licence text is incomplete

The current Apache licence text included is incomplete.  The text of section 6 is truncated, and sections 7 through 9 are missing.
The licence text should be synced with the official copy here: http://www.apache.org/licenses/LICENSE-2.0.txt

great catch. goodness. Would you mind putting together a PR that replaces it?

See https://github.com/brianfrankcooper/YCSB/pull/969


Redo pinned columns in assay tables

Assay tables currently pin the source column of their respective study. This does not add much information in multiplexed experiments, where one source material is split into multiple samples via different treatments etc. Here the sample name would be a better pin, but maybe it's worth making this a customisable setting of the table?

Pinning the sample name would also basically require us to omit the preceeding study columns from the assay tables. So far I've gotten positive feedback on the fact that one can make those columns visible in the assay table if needed.
Still, this could be something to consider. Another thing where we should collect feedback from multiple "power users" familiar with the sheets and make a decision.
If the pinning itself is an issue, adding an option to disable it would be trivial.

The issue basically is: In the example above, source material was treated with different conditions to create samples. Pinning the Source column sort of hides this fact when viewing the assay table and scrolling to the right.


feat: tagRelease.sh bump versions in 1.2.x for 1.2 release

Signed-off-by: RHDH Build (rhdh-bot<EMAIL_ADDRESS>

Missed a step in https://issues.redhat.com/browse/RHIDP-1311, fixing that now.


Joining a choir destroys the "leader" status

IF I am a "leader" of a choir (e.g. I have a "choirmember" object with memberType = leader) and I click on a link to join that choir, the front end says"

"You are now a member of the choir"!

which is great, but I am now only a "member" of the choir - I've lost my "leader" status.
Now there is no leader of the choir so I can't get it back!
(This may turn out to be a bug in the API, but putting here to track it)

The API respects the memberType passed in, so the front end presumably says "hey, make this guy a member" and the back end goes "ok. This guy is already a leader, so let's downgrade him".
https://github.com/Choirless/choirlessapi/blob/master/postChoirJoin.js#L38-L47

I thought I'd patched this already. Will look into it again.


[iOS] MoltenVK shader compilation errors

Godot version:

master branch
OS/device including version:

Vulkan backend on iPad and iPhone6
Issue description:

On launching any Godot's project on iOS devices using old (?) GPUs, some shaders do not compile on iOS.
In case of iPad (with A9X GPU) shaders failing to compile are the ones used in rasterizer_effects_rd.
Some of them fail to compile giving XPC_ERROR_CONNECTION_INTERRUPTED and Total number of indirect argument buffer resources exceeded for textures (33/31). errors, but project still launches (at least in 2D).
In case of iPhone6 (A8 GPU) seems like all shaders fail to compile either giving black screen or freezing application and give VK_ERROR_FEATURE_NOT_PRESENT: Device Apple A8 GPU does not support arrays of textures. error.
iPhone XS and 8 compile shaders without a problem, but give some warnings.
iOS Simulator fails with [mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: Device Apple iOS simulator GPU does not support arrays of samplers. and [mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: Device Apple iOS simulator GPU does not support arrays of textures.
Logs
Steps to reproduce:
Export Godot project with Vulkan support to iOS and run it.

Removing shaders usage from rasterizer_effects_rd allowed Godot project to run on iPhone 6 without getting stuck on shader compilation. Seems like some shader is too complex for iPhone 6 to process. As the result app was displaying a default color only.

Rendered scene

Commenting arrays and their usage from .glsl allowed Godot to render the scene. At first glance scene is rendered the same way as it is on any other new device without this changes.

Rendered scene

Adding a workaround for arrays to canvas.glsl has broken rendering to some extent, but project was still running. Changing the code that used arrays like material_samplers[0] to material_samplers_0 didn't change result rendering.

Arrays workaround in `rasterizer_canvas_rd.cpp`

        global_defines += "\n#define SAMPLER_ARRAY_FOR_SHADER \\\n";

        for (int i = 0; i < 12; i++) {
            Dictionary values;
            values["index"] = i;

            global_defines += String("layout(set = 1, binding = $index) uniform sampler material_samplers_$index;\\\n").format(values, "$_");
        }

        global_defines += "\n#define LIGHT_ARRAY_FOR_SHADER \\\n";

        for (int i = 0; i < state.max_lights_per_item; i++) {
            int light_index = 5 + i;
            int shadow_index = 6 + state.max_lights_per_item + i;

            Dictionary values;
            values["index"] = i;
            values["light_index"] = light_index;
            values["shadow_index"] = shadow_index;

            global_defines += String("layout(set = 2, binding = $light_index) uniform texture2D light_textures_$index;\\\n"
                                     "layout(set = 2, binding = $shadow_index) uniform texture2D shadow_textures_$index;\\\n").format(values, "$_");
        }

Rendered scene

Adding a workaround for arrays to canvas.glsl has broken rendering to some extent, but project was still running. Changing the code that used arrays like material_samplers[0] to material_samplers_0 didn't change result rendering.

This changes also completely breaks rendering for iPhoneXS build

I'm going to close this as the Vulkan renderers have changed dramatically in the last two years and many users are using Godot on iOS devices. If you are still experiencing issues with this device, please open an updated issue.


Remove unused chinesecities dependency

❯ np patch
 ✔ Prerequisite check
 ✔ Git
 ✔ Cleanup
 ✔ Installing dependencies using npm
 ✔ Running tests
 ✔ Bumping version
 ✔ Publishing package
 ✔ Pushing tags

 provinces 1.9.1 published 🎉

Thanks!


Memory Writes are performed in third stage

@carol045 Please test this branch with coremark and berkeley COE before we approve.


added a warning about the size of the profile picture to be uploaded

Description
added a detailed warning to allow users to check the size of the images they are uploading before uploading.
Fixes #130
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] this was tested by uploading different sized images both graeter and lesser than 101kb

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

@Tushar19varshney please review

@ivantha @Tushar19varshney please review

Please rebase this

Duplicate of #331


Generate RPM for deployment

Instrumentation requests that this library be installable via yum rpm.

Wouldn't pip or poetry install it in a more Pythonic way? If we create the .rpm, are we going to have to include stuff to make it recognized by the local Python installation?

It appears we can simply build for the rpm target. Since it uses the same process we do for building the tarball, I assume it will unpack in the same way. Maybe that's a bad assumption?
https://docs.python.org/3/distutils/builtdist.html#creating-rpm-packages

The acsys tarball contains things like an acsys.egg-info subdirectory. I don't know if pip has a registry or if it simply scans the directory in PYTHONPATH to see what's installed.
Would rpm users know where to unpack the tarball? Would they be able to rpm-install any dependencies?

I misunderstood this request. It has to do with acnetd and the ACSys-Erlang environment.


Prevent callback from being called more than once in LimitDialer

The callback in LimitDialer gets called more than once in certain circumstances which breaks some async artifacts such as waterfall or parallel. I have currently patched this in https://github.com/libp2p/js-libp2p-swarm/pull/224/files#diff-0e91f710aa050de15c82e5d320bb289cR41 by using once, however as @dignifiedquire pointed out, we need something smarter that cancels pending requests and does the proper clean up. This issue is here to keep track of that change.
Also, the reason not to have this as part of https://github.com/libp2p/js-libp2p-swarm/pull/224, is to keep it from holding that PR, tho we probably want this fixed before shipping it.

@dryajov is this still an issue?

yes, this is still an issue.


Fix dialyzer errors and add dialyzer to build

These changes fix a few dialyzer errors in the project and also run dialyzer during the Travis CI build. I made a couple notable changes below
I removed the typespec from the assert_has and refute_has macros, because dialyzer was raising a warning on them. I checked in the Elixir, Ecto, Plug and Phoenix libraries and couldn't find a single example of where someone documented macros using a typespec.
I also changed the call to Port.open/2 so it passes a charlist as the second element in the {:spawn_executable, _} tuple. This call passed directly to the open_port/2 erlang function and expects an erlang string.
Please let me know what you think and if there's any changes you'd like me to make.

It looks like travis timed out for the elixir 1.3.2 build and I don't have permissions to retry the build.

:heart: to have dialyzer in the build! Thank you very much! :)
Too bad about the macros... there ought to be a way but that's rather something to take up with the elixir forum together with the appropriate error message :)


chore(travis): release on node 10 success

Releasing on node 12 success won't work until we move to node 12

:white_check_mark: Build karma 2496 completed (commit https://github.com/karma-runner/karma/commit/23bab7a5cf by @johnjbarton)


Module fails when real distribution name is used

This module is useless unless the function is deployed in the same serverless.yml that contains the distribution resource. Can't even put the distribution Id in the distribution field!

@cyberfox1 I'm not sure what the point of your opening this issue is. It seems more like an attack on people who are providing free and useful software instead of a valid issue.
If you have a valid issue that you'd like to report or a feature enhancement to suggest, feel free to open an issue using words that are courteous and respectful.


Generate more pleasant colors for the built in "java" mod

Generate more pleasant colors for the built in "java" mod

Will merge in #529


Allow local interface name to be specified

Maybe I missed something, but it doesn't look as though the current schema for local interface name generation is chosen for any specific reason. This option allows the local interface name to be set to something meaningful (for instance the name of the container to which the interface belongs).
I haven't built in any error checking (i.e. checking if the interface to be specified already exists), this could be done in a further step if this change is seen as useful.

Sure, this could be useful! Would you like to rebase this? (Sorry, I reformatted the whole file, thus breaking every pending PR...)

I've rebased it against the current version and ran shellcheck on it - all good!

I've rebased again against the latest changes, this is ready to merge.

I'm very very sorry, but there were (more) breaking PRs merged... Do you think you could rebase one more time? If you do it, feel free to drop me an email directly so I can merge it right away... Sorry and thanks again for your time!

@jpetazzo I've rebased again - this is ready to merge.

Thanks a lot, I merged this! Do you think you could also add a little paragraph to the README? Pretty pretty please :x


[Feature] dbt should know about joins

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
When deriving core dim/fact models it's often the case that multiple intermediate tables are created to derive specific feature columns of the final table. For example, stg_users may have int_user_feature_1 and int_user_feature_2 which join together with stg_user to produce dim_user.
It is very tempting to define a unifying model like dim_user earlier in the DAG, ie as int_user, so that further feature work can benefit from a one-stop-shop of columns instead of having to bring them in "a la carte". Accessory unifying models are a bad practice, however because they create a bottleneck in the DAG, which slows run time, increases the risk of cyclical references by creating many unnecessary dependencies. and ultimately cannot add to itself which all lead to future un-unifying efforts down the line.
The best practice is for a dbt developer working on int_user_feature_3 - which references features 1, and 2 - to copy-paste the joins contained in dim_user rather than referencing it, in order to keep the DAG nice and orderly.
It would be convenient if dbt could be told of the joins in dim_user, and compile them as needed to serve references earlier in the DAG without creating an actual node. I'll call this abstraction abs_user. Looker users will note that this is how Looker Explores work. A predefined pattern of joins presents a set of selectable things to a user, and SQL is compiled based on what they select to produce the minimum query required for the output. In this case I'm thinking smaller than a Looker explore which can have weird granularity interactions, and just thinking about a table like dim_user with multiple sources of additional columns at the same granularity.
This solves the two problems of real unifying model node in the DAG. First, abs_user would not be a bottleneck because it's not a thing that has to itself be run before its dependencies. It would actually automate the known best practices for referencing pre-defined features and maximizing parallelization. And second, abs_user could build on itself; it could both be referenced in int_user_feature_3 and know that it's possible to join int_user_feature_3 to stg_user. If you tried to do such a self-reference, the compiled model code would contain a self reference (or detectable cycle) and fail.
Further Thoughts
It would likely be that dim_user is the DAG node produced by SELECT * FROM {{ ref('abs_user').
Someone at dbt knows much more than me about the challenge of parsing SQL queries to recognize the source join of selected columns. It sounds like this is one of the benefits of Malloy which is said to "Produce rich metadata [including] the originating column...". While it would be cool if the whole 'macro' was written in SQL and dbt parsed it, I could see a YAML based version more like LookML for Explores being great too.
The task of deifning minimum ingredient CTEs for a new model is nicely captured by dbt's "import" style to refs. However that style just tells developers where to write the code rather than doing it for them, and the task is generally very well defined.
If I knew more about other web development I could probably name an example of something that imports only the parts of a library actually used by a file.
Describe alternatives you've considered
A macro could be written today that takes a list of columns and, through basic hardcoded branching logic, determines a minimal subquery to access those columns.
dbt's "import" approach to refs defines a clear space in the file for developers to do this task, but it doesn't help them do it. The suggested feature could be used inline, and generate a subquery, or it could be used within a "import" CTE to produce more readable compiled code.
Who will this benefit?
Analytics Engineers
If joins can be considered business logic, then this feature would DRY up considerable business logic in the repo. It would also make doing right by the DAG and writing convenient SQL the same thing, which is rare!
Analysts Doing Analytics Engineering Work
The DAG can be an unintuitive concern for analysts used to writing analytical SQL. This feature lets them write SQL like they would with dim/fact models without concerning themselves with an underlying lineage and future cycle risks.
Refactor-ers
Refactoring a dbt repo with poorly structured references can be a lot of work.  Wokring through 10 models using dim_user and trying to peel back which columns they actually need, and whether they create cycles, could be very challenging. This feature would allow the step to be carried out once in a central non-model, and distributed as a reference.
Are you interested in contributing this feature?
No
Anything else?
stg/int/dim/fact
https://discourse.getdbt.com/t/how-we-structure-our-dbt-projects/355
"Imports" Style
https://discourse.getdbt.com/t/why-the-fishtown-sql-style-guide-uses-so-many-ctes/1091

note for consideration wrt implementation:
in a world with column-level dependency tracking, this might become moot - if FK relationships are established early in a project, and column parsing is available, lattices among downstream objects can be derived. So if that is an "intended" future feature, it probably would be good to think of implementations that would not conflict too hard with that. My feeling is that PK/FK relationships could therefore form the backbone of any implementation.
Bonus points: defining actual key constraints (and enforcing them automatically post-build) provides strong hints to the optimizer about how much memory will be required to execute a join and can thus enhance performance, so i think leaning into that is a good idea.

Hi All,
From my opinion, If you look at it from the fact/dim star schema perspective, why not defining your PK/FK where you need it? So in the end of your pipeline? I think that is an easier start, than requiring inheritance.
Most of the int_ (intermediate) models are staging or intermediate models, that are just for realizing the required transformations.
These PK/FK relationships would be useful in  your end user facing layers such as

your core dwh

For your core dwh is to make sure your data integrity is fine, you can already use tests to make sure all referential integrity is fine. And of course, if you could define PK/FK here, it would help reduce the manual tests you need to write.

your end-user facing marts
End user facing marts, with PK/FK, would also benefit from data integrity, but especially the new Metrics feature will benefit. If you have worked with Fact/Dim, you know that Metrics are calculated over Fact measures and Dimensions are in related tables. If you would want to utilize this Metrics feature well and use it possibly with downstream tools/frameworks such as Cube JS, defining dimensions that are not in the current model is required.

To be a bit more concrete, I think this Relationships would live in the .yml file that is in the folder of each layer. Take again the

core_dwh
—- core_dwh.yml
data_marts
—- data_marts.yml

In each of these YML files you would describe the relationships, that would have the following functions:

referential integrity
when you want to enforce referential integrity, you can add a boolean, to make dbt enforce referential integrity, so creating tests that make sure your references make sense
feed the Metrics feature
when you are defining metrics on top of a model such as fact_sales, you should be able to use dimension fields from dim_customer by putting in:

`
dimensions:
- model: ref(“dim_customers”)
- columns:
plan
country
`

I'm way overdue for responding to this issue. Thanks for opening, and for the great comments!
There are a lot of really neat ideas in here, and I don't have too much to add myself. I'd just add that these two things feel quite different:

Joins within transformation DAG: In a world where dbt can read and understand SQL, it could understand which columns are being used to join tables together—and whether those same joins are being repeated over and over again. It's sort of possible to do this today, with model-level lineage, as a measure of "DAG modularity." The use case here is really around
Joins within the "semantic layer": As dbt evolves into providing a real semantic layer, in the form of metrics, it does feel important that it gains an intrinsic understanding of how "final" models join together. This has overlap with other thinking about exposures (#3533), ERDs (https://github.com/dbt-labs/dbt-docs/issues/84), and of course the future of metrics, which don't support joins today.

We're not in a place where we'll be ready to write code for any of this very soon. I think this will be living rent-stabilized in my mind for the next year+. For now, I'm going to convert this to a real discussion, and invite more folks to join in :)


fix(ingress-host-match-tls): repair policy and add tests

Related Issue(s)

fixes https://github.com/kyverno/policies/issues/360
Description

Repair validation of the policy for multiple hosts.
Add more tests.

Checklist

[x] I have read the policy contribution guidelines.
[x] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.

DCO sign-off is required.


Define a Simple Data Model and OData Service with CDS

Tutorial URL: https://developers.sap.com/tutorials/odata-05-data-model-service.html
Please specify the step you are referring to: 3
Half of step 3 can be omitted as the builder isn't needed anymore

Fixed, thanks. https://github.com/SAPDocuments/Tutorials/commit/f289ecd8f43a259d079aabb8bf55263ed75deb98


Simplify CI and extend to Node.js 15.x

 AssertionError [ERR_ASSERTION]: INIT_CWD is not defined.

Seeing it locally as well (hence why I raised the PR). Will look into it.

Okay, I'm using PWD as a workaround, and it's working. And here I thought using Node.JS would be less buggy.


[Geolocation] Add permissionTypeIOS option

This adds backgroundMode to the geolocation options. When options.backgroundMode === true for both gelocation.getCurrentPosition and gelocation.watchPosition:

Enforce NSLocationAlwaysUsageDescription is set in Info.plist
Requests requestAlwaysAuthorization as opposed to requestWhenInUseAuthorization

This should probably be an enum instead of a boolean or at least renamed to be clearer.

@ide something like permissionType: ENUM('IN_USE', 'ALWAYS') ?
Does using ios'y terms make sense or are we trying to keep things platform agnostic?

Android's permissioning is pretty different (coarse vs. fine updates rather than background vs. foreground) so I think we should optimize for iOS in this commit and clearly name the property something like permissionTypeIOS.
cc @frantic are you the right person to take a look at geolocation diffs (saw you were active on a few others)?

IIRC @sahrens built the original implementation. Re: this PR, I think we
should be explicit about the platform, especially when Android has a
different model
On Wed, Jun 3, 2015 at 5:19 PM James Ide<EMAIL_ADDRESS>wrote:

Android's permissioning is pretty different (coarse vs. fine updates
rather than background vs. foreground) so I think we should optimize for
iOS in this commit and clearly name the property something like
permissionTypeIOS.
cc @frantic https://github.com/frantic are you the right person to take
a look at geolocation diffs (saw you were active on a few others)?
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/1506#issuecomment-108655302
.

Ok, replaced backgroundMode with permissionTypeIOS which (if defined) must be one of ['ALWAYS', 'IN_USE']
I am not sure about the code style here, e.g. is it appropriate to use indexOf in an invariant argument as a surrogate for enum. Should we enum the permissionTypeIOS option again in objC land? Following react style is less obvious when working outside of components :(
Would it make sense to expose an explicity requestPermission method even though that does not conform for w3 geolocation spec?

This seems ok to - @nicklockwood, you re-wrote this recently, any qualms?

Ah, thanks @sahrens
I changed the constants to be in line with react-native conventions, now: RCTPermissionTypeAlways, RCTPermissionTypeInUse, RCTPermissionKey. I also changed the permission type strings from all caps to camel case as that seems to be the convention, now: "always", "inUse"

This is working great in the background. The only time it stops running is when the display is off. If I press the home button, it starts running again (even while locked) but as soon as the display goes black again, it stops running.
My code is the same as the React Native - Geolocation Example (with the added permissionTypeIOS: 'always').
Any ideas why this is happening? I will provide more details if needed.
Thanks! Love this!

@timdoes it may be an issue with your app setup. For example make sure the location background mode is enabled: https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/plist/info/UIBackgroundModes
This diff only changes the permission type requested, the mechanism for retrieving the location is still the standard startUpdatingLocation method https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocationManager_Class/index.html#//apple_ref/occ/instm/CLLocationManager/startUpdatingLocation

My background mode declaration:
<key>UIBackgroundModes</key>
<array>
	<string>fetch</string>
	<string>location</string>
	<string>remote-notification</string>
</array>

Does this need to be used with a custom library class and bridged to React Native?
Sorry if this is a rookie question. Just thought this would add full background capabilities by just declaring the background mode and using the https://facebook.github.io/react-native/docs/geolocation.html example.

@timdoes just tested this out, and I see the same behaivor (no updates with display off). I do not have a definitive answer for you, apple does not make debugging this types of situations easy. You may consider playing around with allowDeferredLocationUpdatesUntilTraveled:timeout or signifigant location changes api or geofencing (none of which are currently supported by react-native gelocation)

Actually going to pass this one to nick to finish review and import.

any news on what's causing the events not to fire when screen is locked ?
I see the same behavior with https://github.com/machard/react-native-location.
It must be in the way the bridge eventDispatcher works because didUpdateLocations is called.

@nicklockwood @rt2zz Any updates on this?

@satya164 not sure about the status, but fwiw I just rebased against master, so if you want to take this patch for a test drive feel free.

@rt2zz Everyone is on holiday. This PR might have to wait till next year :D

ping @nicklockwood :)

I'm not wholly happy with the implementation, but in the interests of moving forward, I'll accept this and then make some tweaks in a follow-up diff.

@facebook-github-bot shipit

Thanks @nicklockwood - let me know if there is anything needed from me to follow up / tweak.

I'm closing this in favour of https://github.com/facebook/react-native/pull/5093, which solves the problem without exposing any proprietary props in Geolocation.js


renderer: dont fork the process when there is server redirect

Fixes #3471
Otherwise url_request associated with the process will be destroyed.

:+1:


Add a "Getting started" page

I suggest adding a new top-level page titled "Getting started". Its purpose would be to provide a quick and safe answer to the many budding Rust game developers who are wondering "where should I start?"
@kvark already made one such write-up:
https://gist.github.com/kvark/840c8cadf755b0d822b331222b0c3095
I would prefer something a tad more fleshed out, but the essence of it is spot-on. It's also encouraging to see that a year later it is still good advice, which speaks to the growing stability of the ecosystem.
How to write the article as democratically as possible is of course an issue. A more elaborate process could be considered for the future, but for now I would suggest the following:

Start a new issue: "RFC: Getting started 09-2018", provide a skeleton similar to kvark's and solicit feedback from the Rust community. Invite engine creators and game developers to make their case.
Once the discussion has gone on for two weeks or so (which might not be much discussion at all at this early stage) the AWGY team makes an executive decision and publishes the final draft to the website.
The "Getting started" page will link back to the draft discussion for transparency.

@erlend-sh  Agreed on adding a Getting Started article.
Though isn't that whole procedure a tad overcomplicated for one simple article?
I'd rather just draft one, and then people can send pull requests to tweak it, or entirely change it or whatever.

Yeah I agree, I was getting a bit ahead of myself. Best to just start it off as a living document like you're suggesting.


fix: State trait does not require &mut self

This change is

Codecov Report
Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (d6dd88b) 70.88% compared to head (014b4a8) 70.95%.

Files
Patch %
Lines

crates/blockifier/src/state/cached_state.rs
85.71%
10 Missing and 1 partial :warning:

...ve_blockifier/src/state_readers/py_state_reader.rs
0.00%
5 Missing :warning:

...tive_blockifier/src/state_readers/papyrus_state.rs
60.00%
2 Missing :warning:

...tes/blockifier/src/test_utils/dict_state_reader.rs
80.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1325      +/-   ##
==========================================
+ Coverage   70.88%   70.95%   +0.07%
==========================================
  Files          59       59
  Lines        7350     7362      +12
  Branches     7350     7362      +12
==========================================
+ Hits         5210     5224      +14
+ Misses       1726     1724       -2
  Partials      414      414

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

@giladchase can you review this one? And re-run the codecov CI that seems to fail in a way unrelated to my code?

@giladchase could you review this one?


Ebooks with the format 'ebook-epub-open' and 'ebook-pdf-open' are tre…

…ated as no-drm works
Description
The fulfill endpoint will not proxy download the files anymore, but will ask the clients to redirect to the files
For this a special property FulfillmentInfo.content_link_redirect has been introduced to allow
any API integration class to direct the flow of the fulfillment downstream

Motivation and Context
Overdrive open content package items were unable to be displayed by the frontend clients due to
a problem with proxying chunked downloads.
The better approach is to move the burden of download to the client itself.
Notion

How Has This Been Tested?
Unit tests were written to mock out the entire flow as described in the ticket, since production keys were not available for testing

Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

This is in pretty good shape, just a few minor suggestions for naming, comment context, and where to put expected response values.

Thanks for the review. Updated


Duplicate declaration of plugin maven-dependency-plugin in dspace/modules/server/pom.xml

Describe the bug
I noticed this warning from maven while building current main (9.0-SNAPSHOT):
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.dspace.modules:server:war:9.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-dependency-plugin @ line 71, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]

There are indeed two declarations of the maven-dependency-plugin plugin in dspace/modules/server/pom.xml.
To Reproduce
Steps to reproduce the behavior:

Run mvn package and see the warning from Maven immediately.

I can claim this while I'm doing other dependency cleanup on main (using dependabot).  Thanks for the ticket, @alanorth !  I hadn't noticed this warning yet.


New version: Pylogmon.pot version 2.7.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Sorry, I don't know what's wrong. I've checked and I don't see anything wrong.

Automatic Validation ended with:

2023-11-16 16:25:49.956 [FAIL] Installer failed security check. Url: https://github.com/pot-app/pot-desktop/releases/download/2.7.0/pot_2.7.0_x86-setup.exe Result: 0x80004005

Hi @Pylogmon,
Please virus scan your systems. This might be a false positive, and we can rescan Monday.


To call the tests on PR from lf-edge/eden

For the purpose of running the eden tests, this PR will call the lf-edge/eden process and pass the eve build tag.
Note:- TIDY version of https://github.com/lf-edge/eve/pull/3370

@uncleDecart thanks, commits are squashed

@yash-zededa Would it be possible to shorten this:
Test from lf-edge/eden / call_test_wf_from_eden / Smoke tests (zfs, true)

to just:
Eden / Smoke tests (zfs, true)

I see this in the list of checks for example in this PR: https://github.com/lf-edge/eve/pull/3375

@milan-zededa Yes, it is possible and I will shorten the name of the workflow with the future PR's. This one is merged. Just to let you know we would first test the workflow from eve to eden and if everything is working as expected will switch to this workflow for all the PR's.


Correcting typos throughout project

Summary
Typos corrected across source files in project.
Details and comments
I encountered a few typos in the sources and decided it may be beneficial to correct these as automagically as possible. All source files in the project were passed to scspell (https://github.com/myint/scspell) and the resulting valid typos were corrected across all files. Most changes were in comments/documentation, but some classes and variables were also corrected.

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

@mlxd thank you for this! We can merge after the minor style issue is fixed.

Glad to help out.
I just accepted that change using the online GUI, but I think I may have added an additional line by doing this. I'll fix when back at my laptop and then resubmit.


Navbar components

added responsive bootstrap navbar with routing to pages

Your editor somehow removes the newline at the end of the files. Please fix that. We do want a newline at the end of each file :)

I think it's because of Windows. How can I fix that?


Rancher server URL is not accessible on an upgrade from 2.4.5

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Deploy a cluster in rancher:v2.4.5 - 3 nodes all roles cluster.
Upgrade rancher to master-head - commit id: ec1ea7a99
Unable to access rancher server through the URL.
Rancher logs show:

2020/07/06 23:31:47 [INFO] Stopping cluster agent for c-4r5cn
2020/07/06 23:31:47 [ERROR] failed to start cluster controllers c-4r5cn: context canceled
E0706 23:32:16.628890      23 watcher.go:214] watch chan error: etcdserver: mvcc: required revision has been compacted
E0706 23:32:18.118783       6 reflector.go:178] github.com/rancher/lasso/pkg/cache/cache.go:112: Failed to list *v3.GlobalDNSProvider: no kind "GlobalDnsProviderList" is registered for version "management.cattle.io/v3" in scheme "github.com/rancher/types/config/context.go:68"
2020-07-06 23:32:27.472718 I | mvcc: store.index: compact 8050
2020-07-06 23:32:27.500413 I | mvcc: finished scheduled compaction at 8050 (took 26.560044ms)
E0706 23:33:07.361234       6 reflector.go:178] github.com/rancher/lasso/pkg/cache/cache.go:112: Failed to list *v3.GlobalDNSProvider: no kind "GlobalDnsProviderList" is registered for version "management.cattle.io/v3" in scheme "github.com/rancher/types/config/context.go:68"
E0706 23:33:43.526520       6 reflector.go:178] github.com/rancher/lasso/pkg/cache/cache.go:112: Failed to list *v3.GlobalDNSProvider: no kind "GlobalDnsProviderList" is registered for version "management.cattle.io/v3" in scheme "github.com/rancher/types/config/context.go:68"
2020/07/06 23:33:51 [INFO] Stopping cluster agent for c-4r5cn
2020/07/06 23:33:51 [ERROR] failed to start cluster controllers c-4r5cn: context canceled

Expected Result:
Upgrade of rancher server should work and Rancher should be accessible
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.5 to master-head - commit id: ec1ea7a99
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): DO
Kubernetes version (use kubectl version):

1.18

With later master-head version, this issue is not seen. (master-head from 07/22/2020)


fails Test reverse on arm64

Running on the alternative CPU arm64, Test reverse in test_actors.py fails:
Processing test_actors.py script..
---------------------------------
vtkVersion 7.1.1
---------------------------------
getArrayNames: {'PointData': ['parr', 'Normals'], 'CellData': ['carr', 'Normals']}
Test getPointArray
Test __add__
Test points
Test faces (2112, 3)
Test texture
Test deletePoints
Test reverse
Traceback (most recent call last):
  File "test_actors.py", line 159, in <module>
    assert sr.N() == 576
AssertionError

see https://ci.debian.net/data/autopkgtest/testing/arm64/v/vedo/6399125/log.gz
The test passes on amd64.

Oh! :-(
that's particularly weird because reverse() doesn't even touch the mesh vertices.. just flipping face orientations.
How may i test what's happening with the arm64 system?
Though I very much suspect this is a vtk issue not a vedo one, as reverse is just a thin wrapper of vtkReverseSense.
(btw, vtk7.1.1 seems quite old already.. is there a specific reason for not having the more modern 8.1.2 in debian?)

In regards to the version of vtk in Debian, kitware have made their software extremely difficult to package.  Difficult in the sense that they embed 3rd-party libraries inside their builds rather than using the versions installed on the system (paraview contains it's own copy of vtk, for instance), which makes it nearly impossible to maintain the packages with normal quality control.  Several attempts have been made to package vtk-8, and stalled because of these problems.  We've asked kitware to straighten out their builds, but they haven't replied.
  The information needed is summarised at https://dsa.debian.org/doc/guest-account/ (non-DMs section).  I can sponsor you, the main thing the application needs is your PGP key fingerprint for authentication.  My email is<EMAIL_ADDRESS>

Thanks Drew for the detailed explanation. Before trying to get a guest account I would love to see if anything else fails in the latest release: so I temporarily commented out the reverse() test and added more printout to have more info of what could have gone wrong, although I doubt that it could be something fixable in vedo... i think it must be a problem of the upstream vtk.
Besides, I moved all the data files to vedo.embl.es/examples/data, they are downloaded and cached on the fly when needed. This simplifies the licence file which changed accordingly (I also replaced all non-free textures with CC0-licensed ones). Fonts licensed under OFL needed a name change - as explained here at sec.5.2 - because i created a polygonized version of them.
Let me please know if you think it's ok or if I missed anything! Thanks again for your support, M.

Hi Marco, nice to see the CC0 images in 2020.4.0
I'd still count vedo/fonts/Inversionz.ttf as DFSG-non-free since it's commercial donationware (free only for personal use), so not public-domain.  The other fonts look good (name-change is fine, the original name and author is still acknowledged).
I've got a build problem with vedo/examples, presumeably related to swapping the symlink around.
The Debian build (pybuild, invoking python3 setup.py build) reports
   dh_auto_build -O--buildsystem=pybuild
   I: pybuild base:217: /usr/bin/python3 setup.py build
   running build
   running build_py
   package init file 'vedo/examples/__init__.py' not found (or not a regular file)
   running egg_info
   creating vedo.egg-info
   writing vedo.egg-info/PKG-INFO
   writing dependency_links to vedo.egg-info/dependency_links.txt
   writing requirements to vedo.egg-info/requires.txt
   writing top-level names to vedo.egg-info/top_level.txt
   writing manifest file 'vedo.egg-info/SOURCES.txt'
   reading manifest template 'MANIFEST.in'
   writing manifest file 'vedo.egg-info/SOURCES.txt'
   error: can't copy 'vedo/examples': doesn't exist or not a regular file
   E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build

Can you reproduce that problem?  I'm not sure if the vedo/examples/__init__.py' warning is responsible or if it can be ignored.

I'd still count vedo/fonts/Inversionz.ttf as DFSG-non-free since it's commercial donationware (free only for personal use), so not public-domain.

oh, you're right... i overlooked that, thanks for spotting it. I'll simply remove it.

Can you reproduce that problem? I'm not sure if the vedo/examples/init.py' warning is responsible or if it can be ignored.

I guess it's because examples is not a separate package, and it has no __init__.py, so it can be ignored. If you remember some time ago I merged examples back into the main module, as it's simpler to maintain and it gives the possibility to run them directly from command line e.g.:
vedo -r some_example_script
and
vedo --list
I liked to have the directory examples at the top (along with setup.py) in the git repo, so I added the symlink vedo/examples which points to it so that it gets detected and installed by pip.
I'm not sure what is the best practice to achieve this.

It makes sense for the examples to stand separate. In fact dh_installexamples installs them into the debian doc dir, and I have to make a symlink in the python install dir just as you've done.  The question is simply what needs to be done with the config files so that the install error doesn't happen. I don't understand the error well enough to be certain what needs to be done (I tried hacking MANIFEST.in but that didn't seem to help)
One option is to keep the examples out of the python module altogether. For instance place them in /usr/share/vedo/examples with that path known to the python code.

what happens if you add and empty file examples/__init__.py ?

have them installed in /usr/share/vedo/examples with that path known to the python module code.

that makes a lot of sense! ..but I'm not sure how to do it.. I guess one needs to add something in the setup.py (?), analogous to the line:
    scripts=["bin/vedo", "bin/vedo-convert"],

That sounds right.  If it's packages=["vedo", "vedo.examples"] causing the complaint, then that explains why editing MANIFEST.in does not fix it.

I added an empty __init__.py, but the build error still occurs.
Probably the problem is the packages=["vedo", "vedo.examples"] entry, but the behaviour suggests adding __init__.py alone is not enough to avoid the error.

But removing the "vedo.examples" entry doesn't help either.  In fact, removing all references to examples from setup.py and MANIFEST.in does not fix it.  The error message remains, error: can't copy 'vedo/examples': doesn't exist or not a regular file.
The only action I've found so far that allows a successful build is to delete the symlink in the vedo dir itself.  Then the build proceeds (but with vedo/examples not installed).

Indeed it looks like it doesn't like the symlink as you say, what if you had some patch script which removes the link and moves examples to vedo/examples?
The error is pretty weird though - why don't i get it in my ubuntu ...

I needed two parts to the patch

remove "vedo.examples" from the packages entry in setup.py
delete the vedo/examples symlink

Both of these steps are needed, but I don't need to add an __init__.py
Strange you're not seeing the same problem on Ubuntu.  Usually Ubuntu tracks Debian closely on these kind of problems.  Maybe the problem comes from some update in python 3.8 or setuptools which hasn't got to your Ubuntu version yet.
I've now uploaded 2020.4.0+dfsg2-1 to debian unstable.

I see.. it's strange that it doesn't like vedo.examples I think that's quite standard practice to organize code into subfolders. No big deal though.. thanks for taking care of this!
M.

There are some reports of setuptools getting finicky over folders vs files (and certainly the symlink is "not a regular file"),
e.g. using the package_data field in https://stackoverflow.com/questions/3712033/python-distutils-error-directory-doesnt-exist-or-not-a-regular-file
The underlying problem might remain a mystery!


Update Go and modules

Issue: open-cluster-management/backlog#15473
Signed-off-by: Jakob Gray<EMAIL_ADDRESS>

/test test-unit

/test test-unit

/retest


alternative for db-generated user ID

For a REST endpoint like that /api/users/{user_id}, I currently use the user id generated by the database. That is fine but is a not very descriptive integer. The email would not be a good replacement as it not nicely integrates in a URL.
This is why it might be nicer if we would have a user alias that uniquely identifies a user in the database. This alias or username has to be set by the user upon registration.
Again, It is not absolutely necessary as db user IDs technically work fine. However, if we would want such a user alias, we should think of it now to avoid to much rewriting.
@lkuchenb, @GoliathMarks, @MoritzHahn1337

It would be advantageous for users because they are much more likely to remember their user id than some random number, particularly if that number is multiple digits. Additionally, it's unwise to reveal anything about the inner workings of the database, even something as seemingly innocuous as the number of a particular user. I think we should generated a unique id on the back end, but we should only have that ID used behind the scenes, and we can allow anything displayed to the user to happen via their chosen username.

Yes, I fully agree, however, currently we only have email (which is not a good idea to embed in a  URL) and full name (which is not necessarily unique). So @lkuchenb should we think of implementing a unique username that a user has to choose upon registration?

Fixed in #102


Can you please add a function?

Hello.
Can you add a visibility check for chams? this game is way too easy if you always have 100% information. Just a visual indicator when you actually see the enemy on the scree would be enough.

I am currently HWID banned so I don't really have an interest in persisting with the cheat. That being said in nearly all games visibility is extremely difficult to measure externally. Rather you can implement a FOV circle for ESP so it will only render people within that circle or add binds or a minimum distance check.


[hyperbeam] Could not detect remote address

$ cat '/home/manu/Videos/Screencasts/Screencast from 06-06-2022 05:05:32 PM.webm' | pv | hyperbeam
[hyperbeam] Run hyperbeam hqjtwkgv2wqeqbdzqpwgpywsobunkmjqazkwni7aw23zoxozgkpa to connect
[hyperbeam] To restart this side of the pipe with the same key add -r to the above
[hyperbeam] Could not detect remote address

Is your network blocking all udp traffic?

Fair enough, that might well be the case.
Thanks :)


[diem-vm] Adjust the internal api for diem-vm

Motivation
Adjust the internal api for DiemVM to allow for a more generic transaction scheduler. The main change is to replace StateViewCache with a trait so that it could be replaced with some other data structure in the future.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cargo test

Just renamed in a new commit!

Might be best to hold off on this for a bit to allow https://github.com/diem/diem/pull/8287 to go in and be more easily cherry-picked

LGTM except that I still think it's possible to convert all dyn Traits to impl Traits.
Hmm... could also rename the parameter name R to something like S (Storage) for even T? It used to be the R in "RemoteCache" but that name is no more.

Renamed R to S. For impl Trait, I think we need to change the caller side of VMExecutor as well. Tho this is totally doable, I would prefer talk to the executor&mempool folks before making the change in this PR.

/land


daemon-status: added global status endpoint to known daemon status

Fixes: https://github.com/cilium/cilium/issues/93
Signed-off-by: André Martins<EMAIL_ADDRESS>

Very clean code overall, see one comment inline. Otherwise this looks very good.

Looks great now!


[UI] Setup Routes

[ ] Install react router dom
[ ] Setup route for / , /flag?mode=edit, /flag?mode=create

Kindly sign me up for further contributions

New requirements:
1.Add left nav #48
2. These would be in the left nav: users, segments, settings, env switching between test and prod
3. Other links on whole project: Create flag, edit, delete, login, logout


can you share ISAID pretrained models

I would like to test your approach for new classes, the models for ISAID don't seem to be available, can you share those? Also, share instruction on a quick evaluation if I had just a handful of samples of the class?
thanks for sharing.

Hi, unfortunately, I have no more access to the pretrained models on ISAID.


one windows only

Hi! I wan't to make it one window only, how can i do that??

Style > menu style

i mean to make the source code

dumbass

Hi! I wan't to make it one window only, how can i do that??

Config.h
int menuStyle{ 1 };


Legacy corteza server add beta column modification

Unfortunately when doing some cleanup the PR's I created were deleted (probably because I deleted my fork and created a new one).
As I left it standing I needed to clean up some tests that were failing. I'll get working on that now.

Hey @darh ,
I'm ready for a final review when you guys have the time. I also caught a small bug and fixed it ( see 561a7761a9deed5f018facb679b7195428292442 ) so that a test would not fail.
Some tests do fail, but these were failiing when I started working on this:
TestApigwRouteUpdate
TestAuthExternalSAMLSuccess
Test0001_basics_detect_datarace_issues

Reviewing this now. It will not go to 2022.9.3 (this week) because I want it to live in a version branch for a couple of days.

What is a version branch? 2022.9.3 is not a version branch?

version branch would be 2022.9.x
More info: https://docs.cortezaproject.org/corteza-docs/2022.9/developer-guide/release-cycle/index.html

👍 I'll squash and merge in the next couple of days.


Replace emptyArray with []

Redux of #49269, but with tests passing.

@typescript-bot perf test this

@typescript-bot perf test this and i'm sorry I broke your previous run

Hm, checking is faster, but binding is slower? Or it's noise?


rtc: bump ffi to v0.10.2

@theomonnom can you re-check? want to make sure i did this impl correctly


Not able to open downloaded file in Android

Not able to open the downloaded file in Android. In iOS it works perfectly fine.
Path for Android local file:
/storage/emulated/0/download/test.pdf
For download file I am using RNFetchBlob.fetch(....)
Thanks in Advance.

Have you finished this problem ? @sharadkatre19

@sharadkatre19 try to add
<root-path name="root" path="." />
in filepath.xml, it work for me :)

@sharadkatre19 try to add
<root-path name="root" path="." />
in filepath.xml, it work for me :)

It works ! Wow big thanks

hi, I don't have this file.... "filepath.xml" can someone tell me where should it be and how it should look like?...

guys, this is how filepath.xml should look like?

"

"

hi, I don't have this file.... "filepath.xml" can someone tell me where should it be and how it should look like?...

I added it to res/xml/file_viewer_provider_paths.xml. Still doesn't work for me

@sharadkatre19 try to add
<root-path name="root" path="." />
in filepath.xml, it work for me :)

@rizki-fr can you tell us where this file is situated exactly? I'm kind of stuck in this issue and if it works your way it'll be great to have this fixed.

@sharadkatre19 try to add
<root-path name="root" path="." />
in filepath.xml, it work for me :)

where is the location of this file?

adding these code will fix the issue for me
https://github.com/vinzscam/react-native-file-viewer/issues/94#issuecomment-767743365

@sharadkatre19 try to add
<root-path name="root" path="." />
in filepath.xml, it work for me :)

It works ! Wow big thanks

Mind sharing the filepath.xml path?


requests-cache==0.9.0 too spammy again

The problem
"WARNING: Invalid JSON body" printed during application run.

WARNING: Invalid JSON body:
Traceback (most recent call last):
  File "/Users/glen/.cache/direnv/PlexTraktSync/python-3.10.1/lib/python3.10/site-packages/requests_cache/cache_keys.py", line
165, in normalize_json_body
    body = json.loads(decode(original_body))
  File<EMAIL_ADDRESS>line
346, in loads
    return _default_decoder.decode(s)
  File<EMAIL_ADDRESS>line
337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File<EMAIL_ADDRESS>line
355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
WARNING: Invalid JSON body:
Traceback (most recent call last):
  File "/Users/glen/.cache/direnv/PlexTraktSync/python-3.10.1/lib/python3.10/site-packages/requests_cache/cache_keys.py", line
165, in normalize_json_body
    body = json.loads(decode(original_body))
  File<EMAIL_ADDRESS>line
346, in loads
    return _default_decoder.decode(s)
  File<EMAIL_ADDRESS>line
337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File<EMAIL_ADDRESS>line
355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Expected behavior
If the data in cache is not decode-able, be silent about it. not application fault. the logging should be level=debug.
Workarounds
Downgrade to 0.8.x
Environment

requests-cache version: [e.g. 0.9.0]
Python version: [e.g. 3.10]
Platform: [e.g. macOS/brew]

Getting those warnings with empty cache as well.

Good call. I bumped that back down to debug level.

Can you add some unit tests, this is not the first time the messages are overly verbose :)

Would it possible to add request method, URL and headers to this trace.
my debug log is filled with these, but not sure what is the request and the response. as I understand the response content type and body doesn't match, so it needs to be reported to who serves the api responses

Seems the code here is trying to encode+decode request body, not response?


Legacy of Kain: Soul Reaver was delisted

LoK:Soul Reaver was delisted from pretty much everywhere quite a while ago.

It looks like they're possibly reserving the Steam page for the upcoming remasters. I made a pull request regarding  this.

I merged Settyness’ pull request. Thanks for your help!


Request: non hard-coded name consts

Hi!
First, many things for making your work open!
In PINDiskCache.m, this is a kind request to make the values for PINDiskCachePrefix and PINDiskCacheSharedName changeable at build time (i.e. not hard-coded into the repository!).
Suggestions that would all work:

check a if a macro is defined and use that instead if defined
add a NSString param to initWithName:rootPath that is used instead of PINDiskCachePrefix if non-nil
put a macro in PINCache.h that is used as a name base (and is skipped if is already defined)

Thanks!!
Drew

Hey Drew, we're open to pull requests, sounds like you already know how you might implement it!


Table Items not persisted across server starts

Actual Behaviour
Configuration in serverless.yml.
  dynamodb:
    start:
      port: 8089
      migrate: true
      inMemory: false
    stages:
      - ${self:provider.stage}

After closing and starting up again serverless offline the database is restarted and all data is lost. As if it was using inMemory. But inMemory is set to false.
It seems that the tables are created after every sls offline start.
This also happens with sls dynamodb start.
Expected Behaviour
sls offline start does not create tables if they already exist.
Steps to reproduce it

Start offline server
Insert items into DynamoDB
Close server
Start offline server
Scan table -> Table is empty

LogCat for the issue
None
Screenshots of the issue
None
Would you like to work on the issue?
I would love to, but it seems that there is something I am doing wrong. It doesn't seem a bug in the library.

I'm trying to do the same thing using Docker in order to provide persistent data but this plugin is actually cannot create tables. There's a problem about migrating tables i guess. But you have to use Docker in order to provide persistent data. Check my issue: https://github.com/99xt/serverless-dynamodb-local/issues/254

Yes, it seems to be a related issue.

@Imuntaner Did you ever figure this out? I'm running into the same issue.

We are using AWS docker image directly. Not this plugin anymore.


feat: add extra fields like category(loggerName), application name and instanceId

add support to use index name pattern $indexPrefix-yyyymmdd

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Dose this client has an API to write 'description' filed ?

I  tried to write some description information about an image, but I  did't find the command .
Dose this client has an API to write 'description' filed ?

This field was probably introduced in new Harbor API, be appreciated if you can pull request to fix it.


Update the Mixed Reality Visual Studio docs for HoloLens 2

Docs Build status updates of commit 93b7011:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/holograms-101.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-210.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-211.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-212.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-220.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-240.md
:warning:Warning
View
Details

mixed-reality-docs/images/arm64setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deploywithdebugging.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/x86setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/using-visual-studio.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-101.md

Line 120: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-210.md

Line 156: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-211.md

Line 97: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-212.md

Line 107: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-220.md

Line 109: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-240.md

Line 107: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 62cc590:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/holograms-101.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-212.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-210.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-220.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-240.md
:warning:Warning
View
Details

mixed-reality-docs/holograms-211.md
:warning:Warning
View
Details

mixed-reality-docs/images/arm64setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deploywithdebugging.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/x86setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/using-visual-studio.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-101.md

Line 120: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-212.md

Line 107: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-210.md

Line 156: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-220.md

Line 109: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-240.md

Line 107: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

mixed-reality-docs/holograms-211.md

Line 97: [Warning] Cannot find bookmark '#pairing-your-device---hololens-1st-gen' in 'mixed-reality-docs/using-visual-studio.md'

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ea8224e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/holograms-101.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-210.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-211.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-212.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-220.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-240.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/arm64setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/buildsettingsusbdeploy_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deployemulator2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/deploywithdebugging.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/remotemachinesetting_arm64.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/x86setting.png
:white_check_mark:Succeeded
View

mixed-reality-docs/using-visual-studio.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@grbury - Your turn to review

This is a good update, and my additional PR should finish it up.


bbox loss is 0.0000 from first step

Hi I am trying to train a cascade with hrnet as backbone (cascade_mask_rcnn_hrnetv2p_w32_20e). When I train this config on COCO dataset it aligns very well with the public log.
However, when I try on my own dataset, the bbox loss is 0.00000 at first step as below.
2020-08-19 04:43:02,754 - mmdet - INFO - Start running, host: yinhan@thinkmate, work_dir: /home/yinhan/mmdetection/work_dirs/cascade_mask_rcnn_hrnetv2p_w32_20e
2020-08-19 04:43:02,754 - mmdet - INFO - workflow: [('train', 1)], max: 50 epochs
/home/yinhan/miniconda3/envs/cv/lib/python3.8/site-packages/torch/nn/functional.py:2970: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
warnings.warn("Default upsampling behavior when mode={} is changed "
/home/yinhan/miniconda3/envs/cv/lib/python3.8/site-packages/torch/nn/functional.py:2970: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
warnings.warn("Default upsampling behavior when mode={} is changed "
2020-08-19 04:43:43,174 - mmdet - INFO - Epoch [1][50/70130]	lr: 4.784e-04, eta: 32 days, 18:12:04, time: 0.807, data_time: 0.244, memory: 5687, loss_rpn_cls: 0.2385, loss_rpn_bbox: 0.0000, s0.loss_cls: 0.6128, s0.acc: 94.9863, s0.loss_bbox: 0.0000, s1.loss_cls: 0.4171, s1.acc: 91.7490, s1.loss_bbox: 0.0000, s2.loss_cls: 0.2471, s2.acc: 90.0566, s2.loss_bbox: 0.0000, loss: 1.5156
2020-08-19 04:44:11,353 - mmdet - INFO - Epoch [1][100/70130]	lr: 5.584e-04, eta: 27 days, 19:32:35, time: 0.564, data_time: 0.003, memory: 5687, loss_rpn_cls: 0.0000, loss_rpn_bbox: 0.0000, s0.loss_cls: 0.0000, s0.acc: 100.0000, s0.loss_bbox: 0.0000, s1.loss_cls: 0.0000, s1.acc: 100.0000, s1.loss_bbox: 0.0000, s2.loss_cls: 0.0000, s2.acc: 100.0000, s2.loss_bbox: 0.0000, loss: 0.0000
I am trying to detect table, so I only have 1 class object, it is not surprising the cls loss dropped to 0 shortly.
My dataset looks like this
{'segmentation': [[85.0, 396.0, 85.0, 495.0, 510.0, 495.0, 510.0, 396.0]],
'area': 42075.0,
'image_id': 1,
'category_id': 1,
'id': 1,
'iscrowd': 0,
'bbox': [85.0, 396.0, 425.0, 99.0]}
The only thing I have changed for this config is data path. I am really new here. Any help is appreciated!
Thanks so much!

I forgot to reset the classes for dataset.
My bad

I forgot to reset the classes for dataset.
My bad

我忘了重置数据集的类。
我的错

I met the same question when I was using detectors_casecade
can you tell me the detail how you solve the problem?


[SPARK-40352][SQL] Add function aliases: len, datepart, dateadd, date_diff and curdate

What changes were proposed in this pull request?
In the PR, I propose new functions as aliases for the existing functions:

len() for length(). It exists in Snowflake, Oracle.
curdate() for current_date(). It exists in MySQL, DB2.
date_diff() for datediff(). It exists in BigQuery, Dremio.
dateadd() for date_add(). It exists in MS SQL Server, Snowflake.
datepart() for date_part(). It exists in MS SQL Server.

Why are the changes needed?
To make the migration from other systems to Spark SQL easier. That should improve user experience w/ Spark SQL.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the related test suites:
$ build/sbt "sql/testOnly *ExpressionsSchemaSuite"
$ build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z extract.sql"
$ build/sbt "test:testOnly *.DateFunctionsSuite"
$ build/sbt "test:testOnly *.StringFunctionsSuite"

Merging to master. Thank you, @cloud-fan for review.


Implement pageview counter

[x] Tests pass
[x] Appropriate changes to documentation are included in the PR

TODO

[] Page level KV settings
[] pv_counter store in localStorage
[] modify & add how to use pv_counter in GAM in makrdown


Failed to open key error: undefined, even when running as Administrator

This code throws an error:
const registry = require('windows-registry');
const windef = registry.windef;

const key = new registry.Key(windef.HKEY.HKEY_LOCAL_MACHINE, 'SOFTWARE\\SomeVendor\\SomeApp\\Settings');

Failed to open key error: undefined

This happens even when running in an Administrator command prompt.  What could the issue be?

Brad would be interested in hearing if you found a solution.  I followed a rabbit hole of downgrading node to v8 in an attempt to find a version that played nice with node-ffi and ref.  Since I only need a small registry change, will probably develop an EXE to bundle in my electron windows install.

@tahoemate Yeah, I ended up switching to this package:  https://github.com/ironSource/node-regedit  It's not as efficient, but works well enough.
Unfortunately, it seems that windows-registry-node has been abandoned.  It hasn't had meaningful commits in years.

@bradisbell @tahoemate  i just used this lib recently, here is my working script, hope this help
    const key = new Key(windef.HKEY.HKEY_LOCAL_MACHINE, '', windef.KEY_ACCESS.KEY_READ);
    const key2 = key.openSubKey(`SOFTWARE\\SomeVendor\\SomeApp\\Settings`, windef.KEY_ACCESS.KEY_READ);
    const value = key2.getValue(`SOMENAME`);
    key2.close();
    key.close();
    console.log(`value=${value }`);


CPA package

Has (a few) tests, but no CI, which is also one of our requirements.

Probably want this one https://github.com/theislab/cpa

agree doesn't match all checklist, would close for now.

closing, missing tests

no CI?


Add Generate Token and Valid Token functionality for JWT Authentication

As part of this user-story, We must enhance the security by generating the JWT Access tokens which would be used while logging.

Generate Token and Valid Token functionality has been added which would be required for JWT Authentication


Cross-platform replacement for SoundPlayer for playing audio across devices/paltforms

Cannot play sound files as part of .net core console apps in windows and running on windows IoT Core on Raspberry Pi due to lack of audio support. Third party libraries don't offer any simple solution for playing wav or mp3 streams like the .NET Framework SoundPlayer does.

Issue moved to dotnet/corefx #32413 via ZenHub


Don't export system related symbols like strlcat

I'm on a system where strlcat is not defined.  netcdf then builds with strlcat and exports the symbol.  Then a user creates a binary that links against another library that also doesn't see strlcat and also exports strlcat.  The linker is then sad.  Neither package should be exporting strlcat.  I'm hacking around in my system by renaming strlcat to nc_strlcat.
Environment Information
netcdf 4.6.1 point release

Feel free to skip this if the issue is related to documentation, a feature request, or general discussion.

What platform are you using? (please provide specific distribution/version in summary)

[x ] Linux = Custom

32 and/or 64 bit?

[x ] 64-bit

What build system are you using?

[x] bazel

Can you provide a sample netCDF file or C code to recreate the issue?

[x] No

Steps to reproduce the behavior
Link against something like unix file or https://virustotal.github.io/yara/

Good point. We can fix for netcdf-c by using a name such as "nc_strlcat" and
a macro #define strlcat nc_strlcat

I believe this has been fixed and this issue can be closed.

Can you link to the commit where it was fixed?

No! ;-) But I seem to recall that Dennis fixed all these at one point. Can you look in the current main branch and see?

I was just looking at this. The change I made was to try and replace
use of strncpy with strlcat.
The code for  the last resort strlcat is in netcdf-c/libdispatch/dstrings.c
So we could rename it to, say, nc_strlcat, and then modify the strlcat
related ifdefs in include/ncconfigure.h.
But is this problem restricted to strlcat? are there other functions in dstrings.c
that need similar treatment.


ng build  changes output of another project in the workspace

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
No
Description
When building a project in a workspace, the build output of other project are changed during build. Have a look at the reproduction below. After you followed the steps, inside the dist folder, you can see that my-lib is not built for production anymore, even though I previously built the library for production. It seems that the command ng build my-application --prod changes the output of my-lib. If I build my-application, the output of my-lib should not be changed in my opinion.
This is annoying, because what I need to do to prevent errors in the build pipeline, is to

build the library for production
build the application for production
build the library for production

The third step should not be necessary.
🔬 Minimal Reproduction
Create a workspace with a library and an application
ng new my-workspace --create-application=false
cd my-workspace
ng generate library my-lib
ng generate application my-application

Now build the library and the application with production configuration:
ng build my-lib --prod
# my-lib is now built for production
ng build my-application --prod
# my-lib is not anymore built for production

🔥 Exception or Error
Below is the output in the console. As you can see, one step of the application build is Compiling my-lib : es2015 as esm2015
> ng build my-lib --prod && ng build my-application --prod

Building Angular Package

------------------------------------------------------------------------------
Building entry point 'my-lib'
------------------------------------------------------------------------------
Compiling TypeScript sources through ngc
Bundling to FESM2015
Bundling to FESM5
Bundling to UMD
Minifying UMD bundle
Writing package metadata
Built my-lib

------------------------------------------------------------------------------
Built Angular Package
 - from: C:\Projects\example-library-workspace\projects\my-lib
 - to:   C:\Projects\example-library-workspace\dist\my-lib
------------------------------------------------------------------------------
Compiling my-lib : es2015 as esm2015
Generating ES5 bundles for differential loading...
ES5 bundle generation complete.

chunk {0} runtime-es2015.1eba213af0b233498d9d.js (runtime) 1.45 kB [entry] [rendered]
chunk {0} runtime-es5.1eba213af0b233498d9d.js (runtime) 1.45 kB [entry] [rendered]
chunk {2} polyfills-es2015.4265614f51b38bdc5abc.js (polyfills) 36.1 kB [initial] [rendered]
chunk {3} polyfills-es5.d7f438905a78995e41d5.js (polyfills-es5) 129 kB [initial] [rendered]
chunk {1} main-es2015.a8830bb6116aeecf10ff.js (main) 137 kB [initial] [rendered]
chunk {1} main-es5.a8830bb6116aeecf10ff.js (main) 160 kB [initial] [rendered]
chunk {4} styles.3ff695c00d717f2d2a11.css (styles) 0 bytes [initial] [rendered]
Date: 2020-05-13T14:18:05.269Z - Hash: b6f9baef21f8ce0ea869 - Time: 93640ms

🌍 Your Environment
     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 9.1.5
Node: 12.16.3
OS: win32 x64

Angular: 9.1.6
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.901.5
@angular-devkit/build-angular      0.901.5
@angular-devkit/build-ng-packagr   0.901.5
@angular-devkit/build-optimizer    0.901.5
@angular-devkit/build-webpack      0.901.5
@angular-devkit/core               9.1.5
@angular-devkit/schematics         9.1.5
@angular/cli                       9.1.5
@ngtools/webpack                   9.1.5
@schematics/angular                9.1.5
@schematics/update                 0.901.5
ng-packagr                         9.1.3
rxjs                               6.5.5
typescript                         3.8.3
webpack                            4.42.0

Hi @json-derulo,
This happens because when building a library in prod mode, the library is build using the old rendering engine VE. When this is consumed in an application, it needs to be transformed and compiled to be Ivy compatible, which is done by NGCC. NGCC, will write the transformed code in the library folder.
What I suspect is that you don't need to run the --prod flag for the library build. --prod flag is intended to be used only when you want to publish your library to NPM repository. If you are consuming the library solely in your Angular workspace, you don't need to build using --prod.
In case you do want to public your library to npm, there are a couple of thing you can do. See here: https://github.com/angular/angular/issues/36119#issuecomment-600511071 for more information.


Error when testing on the Cityscapes dataset

I tried to test my trained model on the Cityscapes dataset via following command:

python experiments/deeplab/deeplab_test.py --cfg experiments/deeplab/cfgs/deeplab_resnet_v1_101_cityscapes_segmentation_dcn.yaml

However, it gave me this error:

Traceback (most recent call last):
File "experiments/deeplab/deeplab_test.py", line 20, in
test.main()
File "experiments/deeplab/../../deeplab/test.py", line 99, in main
test_deeplab()
File "experiments/deeplab/../../deeplab/test.py", line 95, in test_deeplab
pred_eval(predictor, test_data, imdb, vis=args.vis, ignore_cache=args.ignore_cache, logger=logger)
File "experiments/deeplab/../../deeplab/core/tester.py", line 102, in pred_eval
evaluation_results = imdb.evaluate_segmentations(all_segmentation_result)
File "experiments/deeplab/../../deeplab/../lib/dataset/cityscape.py", line 182, in evaluate_segmentations
info = self._py_evaluate_segmentation()
File "experiments/deeplab/../../deeplab/../lib/dataset/cityscape.py", line 241, in _py_evaluate_segmentation
seg_pred = np.array(Image.open(res_save_path)).astype('float32')
File "/home/haowang/software/miniconda2/lib/python2.7/site-packages/PIL/Image.py", line 2410, in open
fp = builtins.open(filename, "rb")
IOError: [Errno 2] No such file or directory: './output/cityscape/deeplab_resnet_v1_101_cityscapes_segmentation_dcn/leftImg8bit_val/results/frankfurt/frankfurt_000001_059642.png'

I guess there is a bug in ./lib/dataset/cityscape.py, line 179, where

if not pred_segmentations:
self.write_segmentation_result(pred_segmentations)

should be

if pred_segmentations:
self.write_segmentation_result(pred_segmentations)

Yes. That's a bug. The code should be:
if not (pred_segmentations is None):
   self.write_segmentation_result(pred_segmentations)

Thanks a lot:)


Query SELECT with IN operator not working

Hi, I have a question, I can't remember if this query is working before or not, but the same query works fine if I tried to run it in phpmyadmin.
SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN (?)

and I added parameter 1,2,3 to replace ? (question mark in the query) so it becomes:
SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN (1,2,3)

This query works fine in phpmyadmin, can return exactly data with id 1, 2, and 3, but when I run it using npm mysql, it doesn't work as expected, in some cases it returns empty row, and in another cases, only return data with the first id of the sequence (1).
Does anybody gone through the same issue?
I'll appreciate any help.

I just found the answer, after trying to debug the compiled query, I found that the result has quotes on input (I guess because of PDO). So it becomes like this:
SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN ('1,2,3')

instead of
SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN (1,2,3)

as an alternative, I didn't use param, directly use variable on the query (not sure if this is a good approach, but at least it works for now):
connection.query(`SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN (${id})`, callback)

Yea, in order to get SELECT a.*, b.status FROM tableA a LEFT JOIN tableB b ON a.id=b.id WHERE a.id IN (?) to expand as you expect, you need to provide an actual array of the numbers to this module (as in [1,2,3]. The output you are getting would be produced when you're instead providing a single string of '1,2,3' to this module.
The rules for how values are expanded into ? are defined here: https://github.com/mysqljs/mysql#escaping-query-values


Add Portfolio Optimizer application

Looks good!

Not really tbh, needs a lot of cleanup but wanted to meet the deadline. Which I hear is Friday now?

You can see the built version on the dev site: https://pyviz-dev.github.io/examples/portfolio_optimizer/portfolio.html

@philippjfr , shouldn't this project include the original notebook that has all the human-readable discussion, and move the current .ipynb's file into a .py file that solely implements the dashboard version?  The project would then show the full dashboard when it's visited, but can then have a link to the standalone dashboard version.

The project would then show the full dashboard when it's visited, but can then have a link to the standalone dashboard version.

Presumably you mean"The project would then show the notebook when it's visited"...?
The original notebook is quite different from the dashboard, which is why I didn't do this originally.

Right, I meant show the notebook, not the dashboard, when first visited.  Even if it's sparse, it at least has some verbiage directed at humans.  If you'd rather put such info into the current .ipynb file, be my guest, but I think there needs to be something readable...