VS 2017 Preview 3 does not load blazor template projects

Updated to VS 2017 15.7.0 Preview 3 and Blazor projects had errors loading. I assume I need to wait for a new update to the language extension VSIX? I think the road map said should be this week for next Blazor preview release?

I updated too but:
No errors loading existing 0.1 project.
No errors creating a new Blazor project
No errors creating a new Blazor + Server project.
What kind of errors do you have?

See the attached ActivityLog.Setup.xml. I think this was recorded on the first opening of a Blazor solution after the update to Preview 3 of VS 2017. However, since then I have closed VS 2017 and restarted the VM and now the projects open just fine.
ActivityLog.Setup.zip
This activity log seems to contain many warnings and errors related to registry collisions..
Let me know if I can provide anything else.

Here also no problems with 15.7.0 Preview 3 and Blazor.
Initial Install was made using 15.7.0 Preview 2.

Ok going to close for now. Seems like maybe an isolated issue to my installation...

@chassq I also have no problem with preview 3.
Please let us know if you find out anything!


Database soft limits

We have recently optimised our hard limits, see #7932.
One optimisation which is missing are the soft limits. A soft limit is a limit which is defined within the application as validation condition - client and server side.
See original issue and discussion https://github.com/TryGhost/Ghost/issues/4134.
e.g. it was suggested to increase the post title validation from 150 to 255.
We have to go over all soft limits and decide on a reasonable limit.

Assigned to 1.0.0 Beta Ready. The plan here is to get an overview of which soft limits we would like to define. And then implement them before launching 1.0.

We would like to change the following database soft limits (== input validation).

increase post title to 255 (current is 150)
increase meta title to 300 (current is 150)
increase meta description to 500 (current is 200)

I will move this issue into the 1.0 Launch milestone.

This was not added on the server side. We should figure out first how complex it is to add the soft limits on the server side now. e.g. other external clients might not have the same soft limits we have added on the Ghost admin (Desktop client, mobile apps).

We had a call today, @AileenCGN will post the result from it tomorrow morning.

In the call yesterday, @kirrg001 and I came to following conclusion:
We have two options:

We run over every db and check if entries exceed the - planned to set - soft limits and do something with is (e. g. cut them off manually)
We set the soft limits anyway, but with common sense. Means, we will try to decrease the soft limits for as little fields as possible to minimize any negative effects for the users 1.

We decided to go with option 2, because there only very few fields that are affected, and the chances, that someone would have an entry in the db, which exceeds these soft limits, are pretty low, especially for LTS imports, some limits were lower and Ghost only worked with Ghost Admin client.
Soft limits for server side
These are the affected db tables and fields, where we're going to set a soft limit, using the isLength() method from validator.js (this is done already for post.custom_excerpt. See here):

posts:

title: 255 chars (current hard limit: 2,000 chars)
meta_title: 300 chars (current hard limit: 2,000 chars)
meta_description: 500 chars (current hard limit: 2,000 chars)

users:

bio: 200 chars (current hard limit: 65,535 chars)
location: 150 chars (current hard limit: 65,535 chars)
meta_description: 500 chars (current hard limit: 2,000 chars) -> special case, as it's not currently used in our client
meta_title: 300 chars (current hard limit: 2,000 chars) -> special case, as it's not currently used in our client

tags:

description: 500 chars (current hard limit: 65,535 chars)
meta_title: 300 chars (current hard limit: 2,000 chars)
meta_description: 500 chars (current hard limit: 2,000 chars)

It's going to be more tricky to set a soft limit for the value field in the settings table for a specific key, so we will have to do it manually (see additional tasks):
- title: 150 chars
- description: 200 chars
Add/Adjust soft limits on client side

soft limits we're going to increase on the client side (reason: increasing on the client side rather than setting a soft limit on the server side, so we have less fields that could possible have a negative impact for the user):

tags.name: 191 chars
users.name: 191 chars
users.slug: 191 chars

soft limits missing on client side (see additional tasks):
- posts.slug: 191 chars

tags.slug: 191 chars
users.email: 191 chars
subscribers.name: 191 chars
subscribers.email: 191 chars

Additional tasks

[ ] 1. Verify if db inputs, that exceed the hard limit get cut of by the db. If they get cut off, we will add validations for every input field, which then validates for the same max length as the set hard limit.
[ ] 2. Find a way to validate settings (blog title and description)
[ ] 3. Check, if we can customize the default validator.js error message
[ ] 4. Add missing soft limits in admin client

1 I tested the following scenario with users.name:

Deactivate all client side validations, so it's possible to reach the db hard limits.
Enter a user name, that is 191 characters long and save.
Set soft limit in schema.js for user name to 150 chars.
See, that everything still loads fine, only when changes to the name are made, the saving fails because of the new validation rule.

@kirrg001 Can you please let me know, if I got everything right? If not, just change it in my comment

I tested with MySQL and sqlite, if values get cut of by the db if they exceed the hard limit and the result is that they don't. This means, there's no need to use set soft limits for the remaining db fields.

@kirrg001 I also stumbled over another problem:
The generateSlug method in our model layer here doesn't have a validation. In our case, for posts.title, users.name and tags.name it is then possible to generate a slug, which is longer then the allowed 191 characters, because the allowed title or name can either have the same length or (in the case of posts.title) be even longer.
I suggest, that we cut the rendered slug to a maximum of 191 chars, so we never return a slug that would fail the validation and therefore prevent the saving process.

Check, if we can customize the default validator.js error message

This is actually a message, we produce here.
Is it necessary to change the message, @kirrg001?

chances, that someone would have an entry in the db, which exceeds these soft limits, are pretty low, especially for LTS imports, some limits were lower...

To extend that a bit. If you did an import without having the server-side soft limit validator in place for e.g. the meta fields, you might already hit the client validation as soon as you start editing an affected post.

...and Ghost only worked with Ghost Admin client.

It's always possible to use the Ghost API directly without any client, but we should not care about this case too much. Only common external clients are important e.g. the native android Ghost app.

I tested with MySQL and sqlite, if values get cut of by the db if they exceed the hard limit and the result is that they don't. This means, there's no need to use set soft limits for the remaining db fields.

Yeah we have a maxlength validator for the hard limits for each field which has a maxlength, see.

Is it necessary to change the message, @kirrg001? And if so, what is your suggestion?

I think it's necessary, but this is how the soft limit validation message looks like: Validation (isLength) failed for slug. It does not sound very user friendly. Furthermore, because we would like to go with option 1, we should care about showing an affected user a very clean error message. We could use the a similar description like we use for the hard limits, see.

The generateSlug method in our model layer here doesn't have a validation... I suggest, that we cut the rendered slug to a maximum of 191 chars, so we never return a slug that would fail the validation and therefore prevent the saving process. I added this to the task-list in my comment above.

If a generated slug is too long, it would hit the hard limit validation by default. But e.g. a post title can be up to 255 characters, whereas the post slug can be up to 191 only, this is definitely an additional task, because this is out of the control of the user - you won't be able to create a post.

If you are doing an LTS migration to 1.x and some of your fields hit a server-side soft limit, should we auto-fix or let the user fix it manually?

If you are doing an LTS migration to 1.x and some of your fields hit a server-side soft limit, should we auto-fix or let the user fix it manually?

This is a very good point. I am not sure, which way to go here. If we auto-fix those cases, the user loses data. But it's also very unlikely (IMO) that those limits are hit, but it's still possible. On the other hand, if we don't auto-fix them, the migration would fail and the user has to find the affected part and fix it himself. 🤔

I think it's necessary, but this is how the soft limit validation message looks like: Validation (isLength) failed for slug. It does not sound very user friendly.

Can certainly optimize the error message to make it more user friendly.

Furthermore, because we would like to go with option 1, we should care about showing an affected user a very clean error message.

So, we go for option 1 now?

Can certainly optimize the error message to make it more user friendly.

👍

So, we go for option 1 now?

Will confirm this approach with @ErisDS - we have a call in an hour anyway. As well as the import auto-fix concern. Will come back here soon.

Option 1 confirmed.
Could you please add a sub task to notify @cobbspur of this change?

Option 1 confirmed

@kirrg001 I updated the bis comment above reflecting those changes and add a subtask for @cobbspur to run queries and do the cut offs of exceeded soft limits.

NAME: ValidationError
MESSAGE: Value in [posts.meta_description] exceeds maximum length of 500 characters.

level:normal

posts.meta_description
ValidationError: Value in [posts.meta_description] exceeds maximum length of 500 characters.

@cobbspur This is an example error message, that Ghost will return.

If https://github.com/TryGhost/Ghost/pull/9251 gets merged as is, we won't need to add the two last missing client side validations for posts.slug and users.slug, as it won't be possible to enter or save a slug which is longer than 191 characters.
The generated slug will always be max 185 chars plus possible counter, and updating a slug goes through the same bit of logic, where we first cut the slug and then check for duplicates.


Jackson-core version conflict

Hi,
I am using dropwizard for developing my application. When I included docusign as a dependency I got version conflict of library jackson core. I am using jackson - core 2.6.3 but it look likes docusign is using 2.4.2.
This is the error  i am getting
Exception in thread "main" java.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonParser.isExpectedStartObjectToken()Z
at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:207)
at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:69)
at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:15)
at com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:3708)
at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2113)
at io.dropwizard.configuration.ConfigurationFactory.build(ConfigurationFactory.java:87)
at io.dropwizard.cli.ConfiguredCommand.parseConfiguration(ConfiguredCommand.java:115)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:64)
at io.dropwizard.cli.Cli.run(Cli.java:70)
at io.dropwizard.Application.run(Application.java:80)

Ifyou don't mind, please share your pom.xml, so we can help telling Maven what packages to pickup.

I am attaching my pom.xml as txt file. Unfortunately or fortunately, our project has all the dependencies this java client needs. So, we excluded all dependencies and the code compiled. But we are getting runtime errors for methods not found.
There were issues with jersey dependency also. Dropwizard framework uses different artifact for jersey, glassfish dependency but you are using sun jersey dependency.
Any help is appreciated.
pom.txt
Thanks,
Sandeep

I have the same hell problem with dropwizard. We use org.glassfhish.jersey. Seems like you version of jersey (com.sun.jesey) is too old and it's in conflict with all jersey version with are'n so ancient.

Guys are you here? Are you going to fix somewhow your useless api?!

@sandeepmandii, @lyapharov please try with the latest release of the client aka 2.0.1 and let me know your feedback.
Thanks!

By the way, here are the dependency versions for this new client:
1.19.1
2.7.0

Please share updates, otherwise the ticket will be closed within 3 days

Hi, I had a similar issue, adding the following dependencies fixed my issue:
    <dependency>
        <groupId>javax.ws.rs</groupId>
        <artifactId>javax.ws.rs-api</artifactId>
        <version>2.0</version>
    </dependency>
    <dependency>
        <groupId>org.glassfish.jersey.core</groupId>
        <artifactId>jersey-common</artifactId>
        <version>2.23.1</version>
    </dependency>

@mmallis87 Do you really think i will wait for 2 months for your updates? But i would like to say - i've never worked with api worse than yours. You shouldn't write programs

@PainHex Can you try with the newest version (2.0.2) that I just released. If the problem still persist I will dig into it.

Hi, I'm still running into the issue that I need to explicitly include these two dependencies. Perhaps its something wrong with my setup rather than your project?

Seeing the same issue as PainHex. Both dependencies he mentioned have to be included. I am using a new version of Jackson. v2.8.1 so I am also excluding jackson dependencies from your depenencies.
From my pom.xml
<dependency>
            <groupId>com.docusign</groupId>
            <artifactId>docusign-esign-java</artifactId>
            <version>${docusign.version}</version>

            <exclusions>
                <exclusion>
                    <groupId>com.fasterxml.jackson.core</groupId>
                    <artifactId>jackson-core</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.fasterxml.jackson.core</groupId>
                    <artifactId>jackson-databind</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.fasterxml.jackson.jaxrs</groupId>
                    <artifactId>jackson-jaxrs-json-provider</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.fasterxml.jackson.core</groupId>
                    <artifactId>jackson-annotations</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.fasterxml.jackson.datatype</groupId>
                    <artifactId>jackson-datatype-joda</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

Hi, I am using dropwizard version 0.9.3 and docusign version 2.0.2; I already added the dependencies suggested by PainHex, however I got a new exception while trying to create the ApiClient:
java.lang.NoClassDefFoundError: com/sun/jersey/api/client/config/ClientConfig
It looks like the same conflict with the jersey version with com.sun.* packages; any idea to fix this one?
Thanks in advance

Running into the same problem here once I exclude the jersey libraries in the Docusign dependency to get things to compile:
java.lang.ClassNotFoundException: com.sun.jersey.multipart.BodyPart
We could write something that would manually create an HttpClient and perform the REST call on our own, but that gets a bit messy. It would be nice to be able to use the Java API.

Has anyone ever found an elegant solution for this one? Having same problem with 2.1.0 version.

I had the following exception and here's my solution.
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jersey.core.header.MediaTypes
There are two implementation of javax.ws.rs.ext.RuntimeDelegate (JAX-RS)

javax:javaee-api
javax.ws.rs:jsr311-api

If your project contains dependency javaee-api it will use by default this implementation org.glassfish.jersey.internal.RuntimeDelegateImpl so you can add this dependency org.glassfish.jersey.core:jersey-common to project. If your project contains dependency jsr311-api it will use by default this implementation com.sun.ws.rs.ext.RuntimeDelegateImpl so you can add this dependency com.sun.jersey:jersey-client to project.
Doesn't matter which one you use in project either javaee-api or jsr311-api, you can set up which implementation to use. For this you should create file javax.ws.rs.ext.RuntimeDelegate in META-INF\services\ and file should contains full name of class (with package), for example com.sun.ws.rs.ext.RuntimeDelegateImpl.
I hope it will help.

We're now using Jackson 2.9.8.
For Jersey, we have an open ticket to upgrade to the current v2 version.
Ticket DCM-2850

Updating Jersey is now internal ticket DCM-3324

We now have a beta version with Jersey 2 support! See version 3.7.0-Beta.
Please try it out and open a new issue if you spot any problems.


RFC - revamp server-side property substituion pattern

This isn't quite complete, but is a possible model for us to consider
to revamp the way server side substitution works.

Here's a quick example showing this one...
version: "3.0"
services:
  lb:
    image: busybox
    command: sleep $$TIME
    environment:
      - TIME=1h
    deploy:
      replicas: ${LB_SCALE:-1}
  webapp:
    image: busybox
    command: sleep 1h
    deploy:
      replicas: ${WEB_SCALE}
  db:
    image: busybox
    command: sleep 1h

% DOCKER_HOST=tcp://localhost:8080 WEB_SCALE=1 ./build/docker stack deploy -c ./dh_tests/docker-compose.yaml t1

% DOCKER_HOST=tcp://localhost:8080 WEB_SCALE=1 ./build/docker stack inspect t1

[
    {
        "Index": 1,
        "spec": {
            "Name": "t1",
            "Labels": null,
            "templates": [
                "version: \"3.0\"\nservices:\n  lb:\n    image: busybox\n    command: sleep $$TIME\n    environment:\n      - TIME=1h\n    deploy:\n      replicas: ${LB_SCALE:-1}\n  webapp:\n    image: busybox\n    command: sleep 1h\n    deploy:\n      replicas: ${WEB_SCALE}\n  db:\n    image: busybox\n    command: sleep 1h\n"
            ],
            "services": {
                "db": {
                    "build": {},
                    "command": [
                        "sleep",
                        "1h"
                    ],
                    "credential_spec": {},
                    "deploy": {
                        "resources": {},
                        "placement": {}
                    },
                    "image": "busybox"
                },
                "lb": {
                    "build": {},
                    "command": [
                        "sleep",
                        "$TIME"
                    ],
                    "credential_spec": {},
                    "deploy": {
                        "replicas": 1,
                        "resources": {},
                        "placement": {}
                    },
                    "environment": {
                        "TIME": "1h"
                    },
                    "image": "busybox"
                },
                "webapp": {
                    "build": {},
                    "command": [
                        "sleep",
                        "1h"
                    ],
                    "credential_spec": {},
                    "deploy": {
                        "replicas": 1,
                        "resources": {},
                        "placement": {}
                    },
                    "image": "busybox"
                }
            },
            "property_values": [
                "LB_SCALE=1",
                "WEB_SCALE=1"
            ]
        },
        "stack_resources": {},
        "orchestrator": "swarm",
        "stack_status": {
            "message": "",
            "phase": "",
            "overall_health": "",
            "services_status": null,
            "last_updated": ""
        },
        "ID": "1"
    }
]


Model 705 - VRef and VRefAuto scale factor

Currently VRef and VRefAuto do not use the voltage scale factor (V_SF). Should they?

I believe they should.

I believe they should.


Wildcard for subscribing to all events

Wildcard subscriptions to a topic prefix, like account.* work fine, but how can I subscribe to all events? I tried hub.Susbcribe(1, "*"), but apparently that doesn't work.

Hi!
Sorry for the delay.
The * is an alias for only one word, I need to add the support for an alias to one or more words (#).
For now, you need to add *, *.*, *.*.*, and so on...


Added Profile Manager (e.g. Groups Distribution Lists) API specifications

See documentation https://developers.symphony.com/restapi/v20.13/reference#groups-distribution-lists

20.13 backport will follow too


Unable to filter test by name (-t, --run_test) if template type contains multiple parameters

Hello,
I'm used to using the -t option to separate a failing test during TDD and to inspect the cause be using printf() debugging. Usually, I just copy the test name just from the error message. So, if I have an error message like this:
error: in "filter_me<test_parameters<100, 100>>": check sizeof( int ) == sizeof( Param ) has failed [4 != 1]

I'm used to filter the test with: -t "filter_me<test_parameters<100, 100>>". That works fine as long as there is no comma in the test name, as above.
Following example:
#define BOOST_TEST_MODULE "reproducer"
#include <boost/test/included/unit_test.hpp>

#include <tuple>

template < int, int >
struct test_parameters {};

using test_cases = std::tuple<
    test_parameters< 100, 100 >
>;

BOOST_AUTO_TEST_CASE_TEMPLATE( filter_me, Param, test_cases )
{
    BOOST_CHECK_EQUAL( sizeof( int ), sizeof( Param ) );
}

Will generate the error message above and will not allow you to filter the test by the name printed. However, the test can be filter with a wildcard behind the first comma: -t "filter_me<test_parameters<100,*".
I would expect that I can use the reported name of a failing test to filter for exactly that failing test.
Edit: Observed in Boost 1.68 with Apple LLVM version 10.0.0

Thanks for the report. Right now, two possible solutions that come to my mind:

Either replace every symbols (<, >, ,...) etc by _
Or properly handle the name of the test test_parameters< 100, 100 > in the filtering

As a user, I find test_parameters< 100, 100 > nicer, but it also gives the sense that the framework is able to parse the syntax properly (means that if I have test_parameters<100,100.      > it should also work).
Since 1. is much easier than 2. and 2. can also be misleading, and also considering the fact that we already do that for user provided names, I'll go for 1.
What do you think?

Hi, I would just expect the framework to take the exact same name, that it prints. My expectation would be, that when the framework says test "filter_me<test_parameters<100, 100>>" discovered a bug, that I can execute exactly that test by exactly that name ("filter_me<test_parameters<100, 100>>").

We both agree to qualify the current behaviour that you described as buggy, and that was not my question.
Thanks for the report, I'll go for 1.

Hi,
sorry for not understanding your question! :-) I'm ok with the names of the symbols as they are now, but I would be ok if they would change.
Thank you for looking into this!

I implemented a fix on the branch topic/GH-223-cannot-filter-template-test-cases. Would it be possible for you to try?

Works like a charm. Thank you very much!

Thanks for the quick feedback! (I'll close the issue when this gets merged to master)


Font paths lacking asset hash production environment (nginx+unicorn)

Set-up: unicorn and nginx (serving assets) in production environment.
font-awesome-rails generated paths for fonts hadn't the hash in the asset path. I was able to get it working using the CSS fix proposed here.
Maybe you should fix the CSS of the gem by using the asset-url helper too.

Are you sure you're precompiling your assets correctly? It sounds like you might not be precompiling the assets in production mode. What version of Rails? Are you using a separate asset server? Are you using another asset gem that also includes Font Awesome and is breaking the path of the assets here? Did you follow the debugging steps in the contribution guidelines before submitting this issue?

Maybe you should fix the CSS of the gem by using the asset-url helper too.

Uh, it already does, and it actually does one better by using the more accurate font_path helper.
https://github.com/bokmann/font-awesome-rails/blob/master/app/assets/stylesheets/font-awesome.css.erb#L15

Sure I was precompiling my assets correctly. I use capistrano recipes to do that and only by overriding that piece of CSS it worked, the app now is generating links with the hash included. The expected behavior of this gem is to generate the links with or without that hash?
I was using Rails 4.1, serving my assets from an nginx instance in the same machine as I'm running unicorn, no other asset gem, no cache involved (using the 'Disable cache' of Chrome developer tools)...

Yes, the expected behavior of this gem is that it generates links in the
CSS with the signature hash, cache-busting suffix. I personally use it on a
half a dozen projects ranging from Rails 3.2 to Rails 4.2, and the assets
are generated as expected and the CSS font paths are as expected.
It sounds like you might have another gem or CSS that was also trying to
reference font awesome that overrode the CSS from font-awesome-rails, but
until you following our suggestions/steps in our contribution/debugging
guidelines, I can't offer much help.

Experiencing the same issue, with  *= require font-awesome in my application.css, config.assets.digest = true in my environment, and font-awesome-rails-<IP_ADDRESS> & rails-4.2.0 I get font paths generated that lack the digest part of their url. They're compiled into public/assets just fine, but the css paths are just /assets/fontawesome-webfont.woff?v=4.3.0. All my other assets using path helpers are processed correctly.

@zrisher. I'm going to tell you the exact same thing that I told @douglascamata. If you don't follow the debugging steps in our contribution guidelines, I can't provide much help.
Afterall, before submitting an issue, GitHub warns you to read the Contribution Guidelines before opening the issue.
Some quick examples of what might be wrong.

There might be other gems or project assets that reference broken Font Awesome assets (this is why the guidelines ask you to provide a bundle list).
There might be files in your public/assets directory of your repository that are overriding things.
Assets precompilation might be triggered incorrectly (i.e. Just because you claim to rely on capistrano doesn't necessarily guarantee anything).
Is config.assets.digest = true in your development.rb and production.rb??

Here is what this gem generates with a proper assets precompilation on Rails 4.2 (this was taken from one of my live projects). Again, we're already using the font_path Rails helper to generate this CSS.
/*!
 *  Font Awesome 4.3.0 by @davegandy - http://fontawesome.io - @fontawesome
 *  License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License)
 */
/* FONT PATH
 * -------------------------- */
@font-face {
  font-family: 'FontAwesome';
  src: url("/assets/fontawesome-webfont-245085072b75421dcf3905ea1d3eeeec.eot?v=4.3.0");
  src: url("/assets/fontawesome-webfont-245085072b75421dcf3905ea1d3eeeec.eot?#iefix&v=4.3.0") format("embedded-opentype"), url("/assets/fontawesome-webfont-011b450c29c698726739dec9c520eccd.woff2?v=4.3.0") format("woff2"), url("/assets/fontawesome-webfont-d91398710edfa0f4a3b8e3a33a313757.woff?v=4.3.0") format("woff"), url("/assets/fontawesome-webfont-2751d584a0c31f9b2a2f6c6d25b03b82.ttf?v=4.3.0") format("truetype"), url("/assets/fontawesome-webfont-c93bed61f9efdb1750df2c4e53d536cb.svg?v=4.3.0#fontawesomeregular") format("svg");
  font-weight: normal;
  font-style: normal;
}

Furthermore, if you're using the proper defaults for Rails 4.2, the signature hash suffixes should even show up in development mode, not just when you precompile to production.
Can someone point me to a CSS file in the wild that claims to use font-awesome-rails in production, but the font assets urls are missing the signature hash suffix?

If I change *= require font-awesome to * require font-awesome in application.css the 404s go away, so it's not this.
I start with a blank public/assets before compiling, and it does compile with digests just fine. They're simply not referenced with digest strings in the css.
I'm testing by manually compiling the assets.
Yes, config.assets.digest = true is set to true in my compliation environment.

I do feel like I covered all that in my initial post. Regardless... this is now working. I have no idea what's different. After going through and trying to debug it by putting some putss in the gem's .css.erb, it's just working. Exact same git commit for my repo, no changes there, no changes in font-awesome-rails.... I don't understand. There might be a Heisenbug lurking around.
Anyway, thanks for the awesome gem, sorry to take your time.

Regardless... this is now working.

That's great.

I have no idea what's different.

@zrisher It sounds like a caching issue.  If you're using Sass, this could be related to not clearing your tmp/cache directory. It could also be related to not touching your application.css file before a server restart.

I do feel like I covered all that in my initial post.

But yet the rest of our debugging steps continue to go ignored. The caching gotchas above are covered there:
https://github.com/bokmann/font-awesome-rails/blob/master/CONTRIBUTING.md#found-an-issue

There might be a Heisenbug lurking around.

Unlikely. It really just boils down to fully understanding how the (complicated) asset pipeline works along with potential caching gotchas.  Assets can get cached in a lot of different places. Belts and suspenders are required when debugging issues like this. It sucks, but it's a reality.

Getting the same issue with puma right now.


Analyzes changes in unsafe code in dependency update review

Changes made:
Update review returns number of files changed that contains unsafe code [with their details] and the list of files potentially containing changes in unsafe code
Improvement TODOs
As we use geiger crate to get unsafe count for a file, when an unsafe line gets modified but before and after counter for the overall file remains same, we have no way to verify if an unsafe line got touched or not and for now return that it requires manual review. We eventually would have to implement our own rust file walker to verify such changes.

I have some concerns below about the module boundary for unsafety

Yeah it sort of seems like gieger may not be the right tool for determining this

\help

/help

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/canary

:sunny: Canary successful

I already merged a PR opened after this which resulted in some conflict in the Cargo.toml. GitHub took me to a conflict resolution tab where I resolved and committed which resulted in this change. Should I rebase locally and re-push?

Yes, you need to rebase this PR. Merging from main into PR branches should never be done.

/land


pointpillar deployment by ros

What is the feature?
Excuse, how can I deploy the trained model such as pointpillar on the car for real-time 3D target detection by ros.
Any other context?
No response

You can Use MMDeploy


Feature issue23 pulse

Coverage increased (+6.8%) to 92.355% when pulling 91719cb5e7a61d15a19f121147487b0bd40b62a9 on feature-issue23-pulse into 9dc3a696d6bf4fd7e304be836f895fa0c0f0b02e on development.


Correction for raw affiliation Department of Movement Science, Human Movement Biomechanics Research Group, KU Leuven, Leuven, Belgium; Movement - Interactions - Performance (MIP, UR 4334), Nantes Université, Nantes, France

Correction needed for raw affiliation Department of Movement Science, Human Movement Biomechanics Research Group, KU Leuven, Leuven, Belgium; Movement - Interactions - Performance (MIP, UR 4334), Nantes Université, Nantes, France
raw_affiliation_name: Department of Movement Science, Human Movement Biomechanics Research Group, KU Leuven, Leuven, Belgium; Movement - Interactions - Performance (MIP, UR 4334), Nantes Université, Nantes, France
new_rors: 03gnr7b55;05f950310;04q2ax456
previous_rors: 03gnr7b55;05f950310
works_examples: W4390007300
contact: b73e3ce0a4ed6d5af622a7088dd7d447:08c50b800fe21e82bd8e71e3e1797c @ univ-nantes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Should module.g.cpp import ?

I’m using cppwinrt.exe v1.0.171122.1.
I get some compiler errors in the generated file module.g.cpp like this:
module.g.cpp(10): error C2039: 'atomic': is not a member of 'std'

It seems like module.g.cpp should be importing <atomic> but it’s not.
Is this a known issue in that version of cppwinrt.exe or am I doing something wrong?
Adam Comella
Microsoft Corp.

This has been fixed. Please try a newer version of C++/WinRT.

@kennykerr Thanks for the quick response!
Is there an easier way to obtain the latest version of cppwinrt.exe than installing a preview version of Windows and installing the preview Windows SDK? This process is a bit painful given that I'm using and targeting an older version of Windows 10.
Adam Comella
Microsoft Corp.

Yes, you can email the internal C++/WinRT discussion alias and we'll point you to the internal build share.


Unable to Marshal Sequence of SequenceOF

Hi,
I have this go struct:
type RegistrationInfo struct {
      User string
     Addrs []string
     SecretKey []byte
     ControllerName string
}

That is marshalled into the following ASN struct:
   RegistrationInfo ::= SEQUENCE {
      user        User,
      addrs      Addrs,
      secretkey SecretKey,
          controllername ControllerName}

   User ::= UTF8String
   Addrs ::= SEQUENCE SIZE (1..MAX) OF UTF8String
   SecretKey ::= SEQUENCE SIZE (1..MAX) OF BITSTRING
   ControllerName ::= UTF8String

I would like to reproduce the same using pyasn1:
I tried the following:
   class RegistrationString(univ.Sequence):
       componentType = namedtype.NamedTypes(
           namedtype.NamedType('User', univ.BitString()),
           namedtype.NamedType('Addrs', univ.SequenceOf(univ.BitString())),
           namedtype.NamedType('SecretKey', univ.SequenceOf(univ.BitString())),
           namedtype.NamedType('ControllerName', univ.BitString()),
       )

But I get the following error:
   pyasn1.error.PyAsn1Error: NamedTypes can cast only scalar values

Could you please help me with that?
I am missing something for sure.
Thank you.

Sorry for delay!
@idahogray might be right - you've missed the SequenceOf component definition:
class RegistrationString(univ.Sequence):
       componentType = namedtype.NamedTypes(
           namedtype.NamedType('User', univ.BitString()),
           namedtype.NamedType('Addrs', univ.SequenceOf(componentType=univ.BitString())),
           namedtype.NamedType('SecretKey', univ.SequenceOf(componentType=univ.BitString())),
           namedtype.NamedType('ControllerName', univ.BitString()),
       )


Programming exercises: Warnings in the assessment editor trigger flickering

Describe the bug
If there are warnings in the assessment editor from static code analyses (e.g. Checkstyle), you get some kind of flickering. It occurs when you move your mouse of the code lines, and you hit some lines with warnings.
One possible solution could be to make the column weight enough to contain both icons, if there are warnings in at least one line, independent of the actual line of the mouse course.
To Reproduce

Create a programming exercise with static code analysis (e.g. Java Maven Project)
Make a submission for this exercise with changes that add warning (e.g. Rename the constants in the Client.java see Screenshots)
Set the Due Date of the exercise to now and add a manual assessment
Open your submission in the assessment editor
Went through the code with your mouse courser

Expected behavior
There are no visual distractions when going through the code with the mouse courser.
Screenshots

Gif convertation had added some color bugs, so here also the video file: https://github.com/ls1intum/Artemis/assets/73783062/63fe0676-5d80-4184-8b29-0f1c79d540f9
Which version of Artemis are you seeing the problem on?
7.1.2
What browsers are you seeing the problem on?
Firefox
Additional context
No response
Relevant log output
No response

This was the workaround we implemented to prevent the button being hidden under the build annotations. We might be able to move the button to the right of the line numbers.
I quickly typed something up in the Monaco Editor playground: example - move your mouse around in the preview editor
Would you prefer it if this was what it looked like?

Yes, that approach seems suitable for me if nobody misses the arrows to collapse code blocks like methods.
When changing already something here, a more discreet icon would be nice e.g., a lighter color. If you read the code with your mouse cursor as a pointer, you can be easily got distracted from the moving icon on the left.


Weird problem that I can't nail down in terms of script formatting

We're using the go-templates prettier setup and it work 99% of the time, but every once in a while it will convert.
      <script type="text/javascript">
        {{ $data.script | safeJS }}
      </script>

to
      <script type="text/javascript">
        {
           {
              $data.script | safeJS;
           }
        }
      </script>

At seemingly random times. Something is triggering it to do the wrong thing but only very few occasions.
Not sure what to attribute it to.

Hmm I can't replicate that one. This code example stays just the same:
<script type="text/javascript">
  {{ $data.script | safeJS }}
</script>

Could you provide a larger example where the formatting fails?

Yea I can't either by choice. It happens all of a sudden when I run prettier from the command line or suddenly within visual studio code. We can just ignore it for now. It's some kind of edge case I think. It crept up on me several times but would not be visible on demand.

Hey @richtera , I'll close this one for now. If you happen to encounter it again, please open another issue!
Greetings
Niklas

Yes that one is good


IOS crashing when opening the app during first attempt

What happened?
Running detox test on the iOS simulator(iPhone 14 Pro 16.4 and 17.1) crashes the app always in the first run.
During the retry 2nd attempt, it hangs a bit before starting the app and the test but it works without crashing as we can see in the Detox logs.
I tried downgrading the iOS to 16.4 to check if there was something with the OS version but remained the same.
What was the expected behaviour?
App running when using the test suite without crashing at the first attempt.
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.13.5
React Native version: 0.70.13
Has Fabric (React Native's new rendering system) enabled: no
Node version: 20.9.0
Device model: iPhone 14 Pro
iOS version: 16.4 and 17.1
macOS version: Sonoma 14.0 (Apple M1 Pro)
Xcode version: 15.0.1
Test-runner (select one): jest
Detox logs
Detox logs
paste logs here!

Device logs
No response
More data, please!
No response

Closing this, I'm moving away from Detox, many problems to solve, advice to people looking at issues, move to Maestro.


Better parsing of BMP files - now works with BMPs from Aseprite

Improve thumbnail generation
We parse the header of the BMP to determine where the image data starts; this allows supporting a wider range of BMP files
Also added a .bat to allow drag & dropping a bmp to generate a thumbnail

oh sorry I missed this one! merging


Bazel

Add a bazel build

Per discussion on Slack, we won't switch to Bazel at this time but it is a very useful experiment that demonstrates that Rust projects can be integrated into larger Bazel ones, leaving room for open source or VMware RabbitMQ to adopt Rust where it makes sense (for example, using Rustler but not limited to it).


Nesting Code-block Admonitions - Custom Callouts troubles...

Hi there 😊 !
I was again trying to nest 2 admonitions/custom callouts  but I'm having some troubles with that 😊 ...
The admonitions I created through the plugin and used for my tests here are both supposed to display no type and not title (which works perfectly with the native Obsidian Callout syntax when I'm not trying to nest them in a note 🙌 )
Here are the things I tried on Mac + Obsidian v0.14.2 + Admonition 8.2.3 (No Community theme)
1. Nested Code-Block Admonitions
🟠  It seems to fail in LP : The closing ````` of the 1st level code block admonition seems to be ignored when rendered in LP.
I've tested this with the code block example from the README and my admonitions/custom callouts created through the plugin with the same result 😊
`````ad-note
title: Nested Admonitions
collapse: open

Hello!

````ad-note
title: This admonition is nested.
This is a nested admonition!

```ad-warning
title: This admonition is closed.
collapse: close
```
````

This is in the original admonition.
`````

Which looks like this in LP 🟠

And like this in Reading 🟢

And for the Admonitions I created through the plugin
(The setting No Admonition Title by Default is toggled ON for both ad-nav & ad-ephemeris)
````ad-nav
Something...

And another Admonition...
```ad-ephemeris
Something else
```
Back to the 1st level admonition ...
````

It gives me this in LP 🟠

And this in Reading 🟢

Note
I'm a big fan of the new native Obsidian callouts syntax and I don't wish to use code-block admonitions 😊.
Since the now gone MS Docs syntax was introduced in the plugin, I never used any other available syntax 😊, so I'm all for creating custom callouts through the plugin and using them with the native Obsidian callouts syntax.
I ran the tests with the code blocks Admonitions to see if what I wanted to do was somehow feasible or not...
And the result I'm looking for here using my custom callouts with the native Obsidian callouts syntax in LP is indeed the one I get in Reading with the nested code block admonitions 😇
2. Nested Admonitions using the native Obsidian Callouts syntax
> [!nav]
> Something
>
> And another "Custom Callout"
> > [!ephemeris]
> > Something else...
>
> Back to the 1st level admonition ...

It definitively works in LP  and Reading with the exception that, for some reasons, the toggled ON setting No Admonition Title by Default seems to be ignored for the nested Admonition/custom callout (> > [!ephemeris]) but it works for the 1st level  Admonition/custom callout  (> [!nav]) without any problem ...
(The setting is also taken in to account when those 2 custom callouts (using the native Obsidian callouts syntax) are not nested and placed in my notes one after the other)

After all this...
As I'm trying to get this result 👇 (Reading + code block admonition)

... but with the native Obsidian callouts syntax ... I guess my question is :
Would there be any way to force the No Admonition Title by Default for the nested custom callouts to be taken into account by Obsidian ?
Couldn't this setting be added to the Admonition CSS snippet so it potentially override the Obsidian callout CSS ? 😇
(same goes for the drop-shadow 😇 ... which seems to work in block code admonition but not with Obsidian callouts syntax, as mentioned in #222 )
I have no idea how to do that 😅 ... hence why I'm here 😊...
Once again, I'm sorry for the length 😇 ... But I thank you very much in advance for any help 😁 !

Can you make multiple issues for the different problems?

Sure 😊 !
but what do you mean ?
One issue for the nested code block problem, one for the nested custom callouts and one for the drop-shadows ?

One issue for the nested code block problem, one for the nested custom callouts and one for the drop-shadows

This one, but the drop shadow issue already exists, no need to make another one 😃

Ok 😁 ! I'm on it 😁 !


Animated textures

1.13 breaks the way certain animated textures work. this program did not fix the animated textures in the pack that i was updating. now im not sure what the changes that were made to animated textures are but the texture went from being a shine moving across the ore to this:

Please provide a resource pack download so I can check it out.

The pack is chalu's 1.11 ocd pack. I personally removed the map icons when
1.12 hit because it was the only thing that broke.
https://www.youtube.com/redirect?event=video_description&q=http%3A%2F%2Fwww.mediafire.com%2Ffile%2F0n8mwfcnuue1u38%2FOCD_Pack_1.11.zip&redir_token=Ehy9FUljt0iu5B8q-9mnotVC9eV8MTUzMjE5NjA1N0AxNTMyMTA5NjU3&v=z051rPOkweI
On Fri, Jul 20, 2018, 1:53 PM Plancke<EMAIL_ADDRESS>wrote:

Please provide a resource pack download so I can check it out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HypixelDev/ResourcePackConverter/issues/2#issuecomment-406678267,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXWYdgoSTFDrNZpHAsyukzTcRo08S8O9ks5uIhkGgaJpZM4VYpCP
.

Fixed with latest release 1.0.1

Also just pushed a fix that will convert map icons to 1.13

thank you for fixing this so quickly i really appreciate this.


Problem Highlighting with Extra Params not displaying terms correctly

Hi, I am using the library to apply Highlighting to a search, but the presentation is being done by breaking the term into several.
I have:
var queryOptions = new QueryOptions();
queryOptions.ExtraParams = GetExtraParams();
queryOptions.Highlight = GetHighlight(highlightFields);
return queryOptions;

private static Dictionary<string, string> GetExtraParams()
        {
            return new Dictionary<string, string>
            {
                {"mm", "100"},
                {"hl.mergeContiguous", "true"},
                {"hl.bs.type", "SENTENCE"}
            };
        }

private static HighlightingParameters GetHighlight(IList<string> highlightFields)
        {
            var highlight = new HighlightingParameters();
            if (highlightFields.Any())
            {
                highlight.Fields = highlightFields.Distinct().ToArray();
                highlight.Snippets = 10;
                highlight.BeforeTerm = "";
                highlight.AfterTerm = "";
                highlight.Fragsize = 50000;
                highlight.UsePhraseHighlighter = true;
                highlight.MergeContiguous = true;
            }

            return highlight;
        }

With the following search term with quotes: "House of cards"
I have the following return:
House of cards
Congressman Francis Underwood and his wife, Claire, do everything they
can to achieve their goals, no matter what.
A political world filled with greed, corruption and lust in the capital Washington.

Wish that instead of:  House of cards
Be that: House of cards
Can someone help me? Thanks.

I think I know what is happening. Please go to Solr and use the Analysis and you will see the problem. Basically I think "of" is being removed because it is a stop word. Can you check and confirm?

Hi, the problem is exactly a stop word. I resolved creating a new parse words when the term with it is between quotes. Thanks!


installing: create shell script to pull helm charts and install into k8s

Need a shell script that can pull the helm charts from the poly repos and then perform a helm upgrade to k8s.  We should be able to run this curl -sSL https://ortelius.io/install | sh  where install is the full shell script.

Looks like we need to host our charts from our hugo server for https://ortelius.io or GitHub Pages.  See https://helm.sh/docs/topics/chart_repository/

@benhpoh

Hello. Please add me.

Ashish already has experience in solving this issue, so I will work with Ashish on this issue.

Hey @sbtaylor15 @sachajw
There is a GitHub action 'helm-chart-releaser' for this in place already. The point that we discussed about how we are going collect different helm charts to work together and collect them as a single artifact, the functionality for that is already there.
This action will combine these charts and create a zip artifact updating the gh-pages branch->index.yml file of the ortelius repo. Infact, it will also host our repo as a helm chart repo. So, we do not even need to create a separate helm chart repo. I verified that the Github Pages is already hosted for ortelius repo and that is our helm repo.
Now, the work related to this ticket. We only need shell script which can supply the environment variables and then deploy it as helm install.
This took a while to understand this. Didn't know that a lot of the surrounding work is already implemented, which has reduced the size of this ticket to a minimum. I will be working on the actual part now i.e. the script for this.
P.S: This is the first time I have seen Github Action working. That loose coupling of the helm repo with the code base is awesome. My TRYST with Open Source.

Excellent @AshishKmrSingh and thank you very much!

completed


RESTORE on a table complains about another index being open

Hello Crate team,
When I do (on Crate 0.54.5):
RESTORE SNAPSHOT snapshots.snapshot_prod_2016_03_01 TABLE events_2015_10 WITH (wait_for_completion=true);

I get:
SQLActionException[[snapshots:snapshot_prod_2016_03_01] cannot restore index [events_2015_07] because it's open]

The snapshot contains all the tables.
Any idea?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31527759-restore-on-a-table-complains-about-another-index-being-open?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github).

hi @benjaminrigaud, are you doing anything else with crate while executing the restore query?

There may be some queries running on other indices.
The strange part is events_2015_07 preventing a restore on events_2015_10.

ok. thanks we'll look at it.

Can you provide the CREATE REPOSITORY and CREATE SNAPSHOTS commands that you used to create the repo and snapshot?

Sure.
CREATE REPOSITORY snapshots TYPE S3 WITH (bucket='....', region='eu-central-1', base_path='snapshots', access_key='...', secret_key='...');
CREATE SNAPSHOT snapshots.snapshot_prod...
Do you have any partitioned tables in your cluster or within the snapshot?

No.

Since you've written in slack that you'll do some additional tests I'll wait here for the results.
If you can come up with steps to reproduce this it would be great.
Unfortunately there is also almost no logging in the restore code which would provide any insight. But I could provide a custom built with more logging included if that would be an option for you

It would be an option :) As soon as I can reproduce this: I don't have incoming RESTORE to do on the production cluster. I'll have to setup a test cluster.

I just reproduced this on my (single-node) system.
CREATE REPOSITORY crate_snapshots TYPE fs WITH (location='/crate_snapshots', compress=true);
CREATE SNAPSHOT crate_snapshots.snapshot1 ALL WITH (wait_for_completion=true, ignore_unavailable=true);
Which created the following snapshot:

repository: crate_snapshots
name: snapshot1
STATE: SUCCESS
concrete_indices[".partitioned.events.044j4c1h6oo36chk",".partitioned.events.044j4c1h6oo36chi","tweets",".partitioned.events.044j4c1h6oo36chj"]

After dropping the tweets table and then attempting to restore, I get the error.
RESTORE SNAPSHOT crate_snapshots.snapshot1 TABLE tweets WITH (wait_for_completion=true)

SQLActionException[[crate_snapshots:snapshot1] cannot restore index [.partitioned.events.044j4c1h6oo36chk] because it's open]

After dropping the .partitioned.events.044j4c1h6oo36chk partition from my events table, I attempted the tweets restore again using the same RESTORE SNAPSHOT script. The dropped partition in my events table was restored instead of the tweets table like I requested.
Here's the schema for my events table:
CREATE TABLE IF NOT EXISTS "doc"."events" (
   "id" LONG,
   "reseller_id" INTEGER,
   "day" STRING,
   "value" FLOAT,
   PRIMARY KEY ("id", "reseller_id", "day")
)
CLUSTERED BY ("reseller_id") INTO 500 SHARDS PARTITIONED BY ("day")
WITH (number_of_replicas = '0-all', column_policy = 'strict');

thanks @tellezb for the clarification. we'll investigate what is happening here under the hood.

@tellezb @benjaminrigaud
We've found the bug and fixed it at our current master as well as at the 0.54 release branch.
It will be released with the next 0.54 hotfix release.


Price checking

It would be very helpful if you show how to do price checking from database!
Thanks,

Thanks for the suggestion! I could definitely add some price lookup sections using websites like http://csgo.steamlytics.xyz/ – is that about what you're looking for?

Steamlytics SDKs

PHP (official)
Javascript (unofficial)

Steamlytics APIs

Steam API for inventory and currencies.
CS:GO API for items, prices, and pricelist.

Yep, adding that is one of the best ideas, so that you don't really have to make many calculations on what the prices are and so on.. :)

CSGOFAST API
BitSkins API

get_all_item_prices

Csgobackpack API
OPSkins API v2

SDK - Node.js (official)

This can also be used to get price info directly from steam without any restrictions :
http://steamcommunity.com/market/priceoverview/?appid=730&market_hash_name={market_hash_name}
Result for M4A1-S | Decimator (Field-Tested) would be :
{"success":true,"lowest_price":"$5.44","volume":"468","median_price":"$5.54"}

Price checking will definitely be included in the new guide. See #100.


No Data Collected

HI Team,
We are using Pinpoint 1.6.2 and instrumented Java application.
We are not to be see data on the console
This is new setup and let us know if we need to enable anything at the collector.

Pinpoint version:1.6.2
OS, WAS, affected library, etc:
Additional details (e.g. how your collector/web is set up):

Additional Info

But getting these data only

Hi All,
Please help us at the earliest as why we any transactions are not captured as shown in above screenshot

Can you please share an checklist at agent/collector end that will help to narrowdown the issue.
like Ports/Properties

you hbase and pinpoint-web pinpoint-collector just one server?
if dosen't please check zookeer address info configure with pinpoint-collector.properties，pinpoint-web.properties。

Yes in one server.
In properties, it is pointing to localhost

1：please check pinpoint web console ，you can select application?
2：If you can select application, and home page center show server icon？

yes its shows application name but able to capture BT

1：Do you have observable pinpoint-collector pinpoint-web  error log？
2：pinpoint-agent with pinpoint.config set profiler.sampling.rate=1 you can try

1 both the logs are not generated ,
2 This setting we have configured and restart the application  instance  getting same status .

@GyaneshRahatekar
What kind of application/WAS is CISCO_CVP?

Its a Tomcat ( JAVA )
OS WINDOWS

CVP15_CALL_Server-pinpoint.log

Sometimes pinpoint can not auto-detect applicationType.
I recommend you to try fixing your service type TOMCAT
# pinpoint.config
profiler.applicationservertype=TOMCAT

Hello, I'm a new and I have the same problem, which tab do you mean please ? I'm not collect on inspector too. Thank's for you reply !

@Xylus Thank's a lot, the problem was that we had to wait :)

May be the UDP port of your collector was blocked by firewall, please check the log of agent.


DDS Cubemap Support (GPUOpen CMP #69)

Hi,
I was wondering if cubemap compression will be added in a future release.
Right now I am using CMFTStudio for generating irradiance maps and related maps which output either RGBA16 or RGBA32 dds cubemaps and was trying to compress them to BC6H but it always fails, so I am assuming there is no cubemap support in the current state.
Is this planned or should I contribute to it myself? Which I am willing to do since I think is something very useful that is missing from this really amazing tool.
Cheers

@NPCompress
@AlvaroBarua
The cube map structure formats are in place (MIPS.cpp MipSet structure m_nDepth settings under TextureType TT_CubeMap and TT_VolumeTexture) but the code is not fully implemented. It is highly encouraged that users contribute to this tool. Our KTX plugin also has a partial implementation.
BC6H and related codecs do not take advantage of these settings.
Please contribute so that all can benefit.


Add a condition to set xliffPath value

The current default value doesn't proper on xliff 2.0 usage case.
I've added a condition to make valid when the xliff version is not 2.0. It not, It shows a warning message when it tries to load the file. it may confuse people who are not familiar with loctool.

Please update the minor version number to 2.8.2 and add a release note

Please update the minor version number to 2.8.2 and add a release note

The version is already updated to 2.8.2 and I've updated a release note. Thank you.


Build micro:bit project with autoreset

We need to ensure we can build the micro:bit project with autoreset enabled by default.

Not yet finished: https://github.com/microbit-foundation/DAPLink/wiki/Building-micro:bit-interface-image-to-update-bootloader

Process creates a hex file, but haven't been able to test it on a micro:bit as I don't have any with soldered programmer cables for the KL26Z.

Waiting for micro:bit jig.

Jig has arrived, so I can erase the KL and test the built image.

Will need to check if the micro:bit DAPLink bootloader is protected from being updated via DAPLink interface image.

Image created via https://github.com/microbit-foundation/DAPLink/wiki/Building-full-micro:bit-images tested and autoresets.
details.txt file also shows the same configuration, and the same DAPLink interface + bootloader image fails to update the DAPLink bootloader, so it looks like it's pretty much the same.
@jaustin was there any other behaviour I needed to check?

We still need to:

[ ] Check if the URLs are the same
[ ] If needed create a new URL to be able to log micro:bit ID and DAPLink firmware version
[ ] Ensure the internal nRF51 unique ID is not used in the URL (this should be already the case)
[ ] If new URL is created, submit patch upstream
[ ] Produce the same build with WebUSB firmware

nRF51 unique ID is not included:
Unique ID:  9900 0000 36424e45004c30150000004f00000000 97969901
Board ID: 0x9900
Reserved - was version number: 0x0000
Host ID (KL26 unique ID 3 4-Byte words): 0x36424e45_004c3015_0000004f_00000000
HIC ID: 0x97969901


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_fddf0233-bea9-4ef3-bb78-13e382aeeab4/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_fddf0233-bea9-4ef3-bb78-13e382aeeab4.git

Docs Build status updates of commit 12f438c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


getting error in RUNETagGenerator

The RUNETag  builds fine but when I build RUNETagGenerator I get the following error. Now I have this libRUNETag.a in the build of RUNETag. Is it the same? and how can I use it in the generator?
[ 90%] Building CXX object CMakeFiles/RUNETagGenerator.dir/RUNETagGenerator_automoc.cpp.o
make[2]: *** No rule to make target '../../dist/lib/libRUNETag.a', needed by 'RUNETagGenerator'.  Stop.
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/RUNETagGenerator.dir/all' failed
make[1]: *** [CMakeFiles/RUNETagGenerator.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

I was able to avoid the above issue by making changes in the CMakeLists of RUNETagGenerator and changing /../dist/lib/libRUNTEtag.a to /../RUNETag/build/libRUNTEtag.a which was the address for the required file.
Although everything builds fine (with a few warnings) and  the RUNETagGenerator executable now opens up, however, it is unresponsive and no tags show up although UI buttons and dialogue boxes are responsive.
~/RUNEtag/RUNETagGenerator/build$ make
Scanning dependencies of target RUNETagGenerator_automoc
[  9%] Automatic moc for target RUNETagGenerator
AUTOGEN: warning: /home/civit/RUNEtag/RUNETagGenerator/MarkPointSet.cpp: file is empty

Generating moc_runetaggenerator.cpp
[  9%] Built target RUNETagGenerator_automoc
[ 18%] Generating qrc_runetaggenerator.cpp
RCC: Warning: No resources in '/home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.qrc'.
[ 27%] Generating ui_runetaggenerator.h
Scanning dependencies of target RUNETagGenerator
[ 36%] Building CXX object CMakeFiles/RUNETagGenerator.dir/main.cpp.o
[ 45%] Building CXX object CMakeFiles/RUNETagGenerator.dir/MarkPoint.cpp.o
[ 54%] Building CXX object CMakeFiles/RUNETagGenerator.dir/MarkPointSet.cpp.o
[ 63%] Building CXX object CMakeFiles/RUNETagGenerator.dir/runetaggenerator.cpp.o
/home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.cpp:22:0: warning: "M_PI" redefined
 #define M_PI 3.141592
 ^
In file included from /usr/include/c++/5/cmath:44:0,
                 from /usr/include/c++/5/complex:44,
                 from /home/civit/RUNEtag/RUNETagGenerator/MarkPointSet.h:6,
                 from /home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.h:6,
                 from /home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.cpp:1:
/usr/include/math.h:418:0: note: this is the location of the previous definition
 # define M_PI  3.14159265358979323846 /* pi */
 ^
[ 72%] Building CXX object CMakeFiles/RUNETagGenerator.dir/TagCode.cpp.o
[ 81%] Building CXX object CMakeFiles/RUNETagGenerator.dir/qrc_runetaggenerator.cpp.o
[ 90%] Building CXX object CMakeFiles/RUNETagGenerator.dir/RUNETagGenerator_automoc.cpp.o
[100%] Linking CXX executable RUNETagGenerator
[100%] Built target RUNETagGenerator

I was able to avoid the above issue by making changes in the CMakeLists of RUNETagGenerator and changing /../dist/lib/libRUNTEtag.a to /../RUNETag/build/libRUNTEtag.a which was the address for the required file.
Although everything builds fine (with a few warnings) and  the RUNETagGenerator executable now opens up, however, it is unresponsive and no tags show up although UI buttons and dialogue boxes are responsive.
~/RUNEtag/RUNETagGenerator/build$ make
Scanning dependencies of target RUNETagGenerator_automoc
[  9%] Automatic moc for target RUNETagGenerator
AUTOGEN: warning: /home/civit/RUNEtag/RUNETagGenerator/MarkPointSet.cpp: file is empty

Generating moc_runetaggenerator.cpp
[  9%] Built target RUNETagGenerator_automoc
[ 18%] Generating qrc_runetaggenerator.cpp
RCC: Warning: No resources in '/home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.qrc'.
[ 27%] Generating ui_runetaggenerator.h
Scanning dependencies of target RUNETagGenerator
[ 36%] Building CXX object CMakeFiles/RUNETagGenerator.dir/main.cpp.o
[ 45%] Building CXX object CMakeFiles/RUNETagGenerator.dir/MarkPoint.cpp.o
[ 54%] Building CXX object CMakeFiles/RUNETagGenerator.dir/MarkPointSet.cpp.o
[ 63%] Building CXX object CMakeFiles/RUNETagGenerator.dir/runetaggenerator.cpp.o
/home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.cpp:22:0: warning: "M_PI" redefined
 #define M_PI 3.141592
 ^
In file included from /usr/include/c++/5/cmath:44:0,
                 from /usr/include/c++/5/complex:44,
                 from /home/civit/RUNEtag/RUNETagGenerator/MarkPointSet.h:6,
                 from /home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.h:6,
                 from /home/civit/RUNEtag/RUNETagGenerator/runetaggenerator.cpp:1:
/usr/include/math.h:418:0: note: this is the location of the previous definition
 # define M_PI  3.14159265358979323846 /* pi */
 ^
[ 72%] Building CXX object CMakeFiles/RUNETagGenerator.dir/TagCode.cpp.o
[ 81%] Building CXX object CMakeFiles/RUNETagGenerator.dir/qrc_runetaggenerator.cpp.o
[ 90%] Building CXX object CMakeFiles/RUNETagGenerator.dir/RUNETagGenerator_automoc.cpp.o
[100%] Linking CXX executable RUNETagGenerator
[100%] Built target RUNETagGenerator

I have the same problem as you, can you solve it now?


F-Droid inclusion

Hi,
Since this app is MIT licensed, are you considering the fact to add it to F-Droid? There is a strong community behind.
You can find some documentation here.
Otherwise, if you don't want to work on the inclusion of this app by yourself, would it be ok for you if someone else do it for you?

Hi there, thanks for the suggestion. I already considered that and read the faq. I've read that the build server takes up 150gb of storage and only runs on Linux. I just need to free some storage and install a VM or is there an easier way using windows?

Firstly you have to add fastlane/metadata to your project. You can take a look Vibe for example.
After that you have to create Merge Request to F-Droid Data. It will be com.blazecode.tsviewer.yml file with instructions. You can take a look me.lucky.vibe.yml for example. Because TS is closed source, you have to add
AntiFeatures:
  - NonFreeNet

to your file I suppose.

Thanks! I added some of the files, I just need to verify my GitLab account.

It took a while, but here it is:
https://f-droid.org/en/packages/com.blazecode.tsviewer/


Add SMNCopyNumberCaller to raredisease

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/raredisease branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR> -stub).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

With the newest minimal test data set, SMNcaller successfully completes, but with a trio of cases, it generates 3 output files, instead of one concatenated file. This is because of the way we currently input the data.

To do list:
[ ] Change input to take multiple bam files at once.
[ ] Successfully complete online tests (needs chr5,6 to complete).
[ ] generate the stubs for the stub tests to complete.


DIP3 compatibility code

This PR is extracted from #2083. It adds compatibility code to CMasternode and CMosternodeMan so that all code using these classes switch to deterministic mode when spork15 is activated.
I omitted the MN rewards/payments related changes for now and will put these into their own PR as they contain the most critical code.

FYI, I'm aware that the many if(spork15Active) blocks that I introduces are very bad quote quality and style. I however chose to go this way so that the changes outside CMasternode and CMasternodeMan are as non-intrusive as possible. After 12.4 has been rolled out and the BIP9 and spork15 deployment logic is activated, I will cleanup all the code. Cleanup means, that most of the legacy code will actually vanish and most places would directly use CDeterministicMNManager instead of going through the old CMasternodeMan code.

Pushed review fixes


ESP32-S3-DEVKITC-1 PSRAM REBOOT PROBLEM (IDFGH-10073)

i m using esp32-s3-devkitc-1 with idf 4.4 but when psram enabled always reboot .
what should I do?

Hi @cyberumut Could you provide the full console log?


CosmosDB, accessing Document client in v4 function.

I am using Azure Function v4 with the isolated process.  Some of the documentation refers to the CosmosDB attribute.  I now use either the CosmosDBInput and CosmosDBOutput attributes where required, however, when trying to use the DocumentClient or CosmosClient to be able to search for multiple documents, there appears to be no example of how to achieve this.

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

ID: fa5bcb79-2af8-3b0e-c78c-0c89a2535e15
Version Independent ID: 31b87687-7841-f46f-8c97-38898e7b97db
Content: Azure Cosmos DB bindings for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@AndyWDev
Thanks for your feedback! We will investigate and update as appropriate.


Add color to notify-send

Hi! I wrote this out of necessity, I need my notify-send messages to show up with a background-color depending on whether any tests failed.
I also refactored a little bit.
I didn't add the same for terminal-notifier, but it should be easy to do so.

I'm good with the addition of color, but not sure how I feel about a blanket refactoring without any real reason.

Sorry, my reasoning is:
There's no need for any of those to be macros, so make them regular functions
A default should be provided in case neither of notify-send or terminal-notifier is available
A multimethod seems to fit the bill nicely, allowing easy extension to other notification tools

In any case please submit the refactor in a separate PR than the one to add
color and we'll discuss it there (you might already be winning me over :))
On Mon, Jul 20, 2015, 2:33 PM Blake Miller<EMAIL_ADDRESS>wrote:

Sorry, my reasoning is:
There's no need for any of those to be macros, so make them regular
functions
A default should be provided in case neither of notify-send or
terminal-notifier is available
A multimethod seems to fit the bill nicely, allowing easy extension to
other notification tools
—
Reply to this email directly or view it on GitHub
https://github.com/glittershark/midje-notifier/pull/2#issuecomment-122980121
.


Add deployment cleanup to minikube quickstart

Since many users of minikube documentation are novices to Kubernetes, it would be a positive developer experience enhancement to explicitly show deleting the deployment creating in the Quickstart documentation's terminal session.
This way the novice user isn't left with a loose deployment in their cluster until they've learned about the concept of a deployment and how to manage them.
Fixes #6188

This change is

/lgtm


fix: account deletion QA comments

This PR resolves the following:

Keyboard issue inside the account deletion process
Success message after deleting user account
Logging out after deleting account

cc @brainbicycle

PR Checklist

[x] I tested my changes on iOS / Android.
[x] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

#nochangelog
Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

I will merge this and create new betas

thanks 🙏


Init DD Priorities

In the moment the priority by channel is initialized with the default priority 100. This should changed to the priority which is initialized with the constructor.

Done with v1.1


Fix plus signs in URL paths.

When building a URL, store the rawPath. When dealing with pathParts, you
will deal with decoded values, but toString() and getRawPath() deal with
encoded strings.

This did not pass internal testing.


refactor: Adjustments to Stores & Agents

Ongoing discussion: https://talk.fission.codes/t/rs-ucan-1-0-api-notes/5347/5

Made delegation::Store::get return Option
Make delegation::Store::get return Arcs
Make delegation::Store::insert take &self instead of &mut self
Similar changes for invocation::Store

Make delegation::Store::get return Arcs

I missed a step on this
    fn get(
        &self,
        cid: Cid,
    ) -> Result<Option<Arc<Invocation<T, DID, V, C>>>, Self::InvocationStoreError>;

Invocations are immutable. Why do they need to be Arced?

Also while we're talking about it: there's two approaches to the type signature. The nested version is what I have here...
// Current
get(/* ... */) -> Result<Option<Invocation<T, DID, V, C>>, Self::InvocationStoreError>;

...where Self::InvocationStoreError is user-defined, so that Option separates out that there was no database error, but there's more unwrapping to do (ok -> some -> value). The other can also use nesting on the Err branch:
struct StoreErr<T> {
  NotFound(Cid),
  DbErr(T)
}

get(/* ... */) -> Result<Invocation<T, DID, V, C>>>, StoreErr<Self::InvocationStoreError>>;

This cleans up the type a bit by putting anything not on the happy path over in the Err, but not having that Option is perhaps less idiomatic — thoughts?

Invocations are immutable — won't that make them threadsafe?

Maybe to expose my mental model:
The Invocation is owned by the Store. This may be a database or an in-memory store. We can make as many clones of the Invocation as we want, because they never change. In my mind, the thing passed back from the store is either owned by the store. My understanding of the borrow system is that you can have [practically] infinite immutable refs.
I'm almost certainly missing a part of the picture, so mostly using this as a learning opportunity :)

Invocations are immutable — won't that make them threadsafe? Why do they need to be Arced?

Requiring to return a &Invocation instead of an Invocation or Arc<Invocation> will make some implementations of invocation stores impossible - e.g. implementations backed by a database or by the file system.
The reason is that the reference means you're passing out a 'borrowed' invocation. But where are you borrowing it from? In the case of MemoryStore, you're borrowing it from the &self parameter, and self will "take care of" the Invocation's lifetime - it stores it itself, and takes care of when it needs to be freed.
But if you want to implement get via reading the filesystem, parsing an invocation, passing it out, and immediately forgetting about this - this won't be possible in rust, because at the end of get, that parsed invocation will be freed, and you can't pass out the reference after the invocation has been freed.
With both Rc<Invocation> and Arc<Invocation>, the invocation is still immutable. I think of [A]Rc<T> as &T, but instead of figuring out when T needs to be dropped at compile time, it's figured out at runtime via reference counting.
Someone that has a reference to an Arc<Invocation> can't change other Arc<Invocation> instances. Or - another way of saying that is "Arc<T> doesn't provide interior mutability". Which is confusing since it appears in the Arc<Mutex and Arc<RwLock pattern a bunch, but it's the Mutex and RwLock that provide the interior mutability in those cases.

This cleans up the type a bit by putting anything not on the happy path over in the Err, but not having that Option is perhaps less idiomatic — thoughts?

I think the Option< version is totally fine.
The BlockStore trait at the moment returns an error on not found. It's been awkward in places where you expect the block to be missing sometimes, but a lot cleaner in many other places, where you expect every block to be resolvable.
So it kind of depends on that ratio? How often would you expect the caller to be "fine" with get not resolving?
Also - the associated type for errors is nice, but I want to point out that for simplicity, it's fine making it a concrete ucan::Error type (or perhaps a ucan::invocation::store::Error type, where one case is simply CustomError(Box<dyn StdError>) (or something along those lines, I forgot the exact incantation. Although I'm less sure of that last point.

So where will it live?

Ah, right, this is the bit that I keep missing. I keep thinking of it as almost like an actor where there's some long-lived location representing "the database" that can hold various bits of memory, but that's not necessarily the case — I mean, you could build this, but that's way more work than an Arc<T>. Cool; thanks for explaining!


skin mesh obj has render artifects on mobile

all good without artifects :  editor , mobile simulator
but on real device, skin mesh will produce black dots around the silhouette of the skin.
the apk was built using unity2018

this scene was done with standard unity depth+motion vector pass and all using standard shader, i hav tested on Redmi 9A, Honor 8X, all producing artifects
can you hint me on what might have caused this to happen on real device?
cheers

my bad, man, this issue was due to that i did not explicitly specify point filter mode for all the velocity tiles RTs from my side. the original implementation in this repo has no such issue when built to device, sorry about the fuzz. closing down this issue now la. cheers


Cloudflare icon do not appear

Cloudflare icon only exists on figma

Are there specific file extensions you are wanting support with Cloudflare?


array_pad on list+explode

This fixes some edge-cases that we encountered during unit-tests, where the response might not carry a body for example.
Context
What has been done

How to test

Todo

[ ]
[ ]

Notes

This is missing a unit test and those items from the PR template.

Yupp. I’ve done this from the Github editor.
This might have caused it.

On 9. Feb 2018, at 16:12, James Hall<EMAIL_ADDRESS>wrote:
@MrRio commented on this pull request.
In src/VCR/Util/HttpUtil.php https://github.com/php-vcr/php-vcr/pull/242#discussion_r167252848:

@@ -66,8 +66,8 @@ public static function parseStatus($status)
public static function parseResponse($response)
{
$response = str_replace("HTTP/1.1 100 Continue\r\n\r\n", '', $response);

   list($rawHeader, $rawBody) = explode("\r\n\r\n", $response, 2);

list($rawHeader, $rawBody) = array_pad(explode("\r\n\r\n", $response, 2), 2, '');

Accidental indentation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/php-vcr/php-vcr/pull/242#pullrequestreview-95450441, or mute the thread https://github.com/notifications/unsubscribe-auth/AB13cNuELhJGvSqCpJqdpEIapYWu7KWtks5tTGBFgaJpZM4R_-jD.


mis-spelled extraIncludes should throw a warning

I just typo'd extraIncludes to extraincludes.
This confused me a lot, until I realised I'd missed the capital 'I'. (My 'i's aren't good enough?)
For other errors in my module.json I get errors, like if I'm missing a license.
Could we have a warning for this, too please?

This is a little tricky, because we want to maximise compatibility: this means that old versions of yotta should probably ignore module.json properties introduced in new versions, and we can't simply add a warning that "extraIncludes" is missing, because it's use is regarded as bad practise, not to be encouraged ;)
Possibly things are stable enough now that warning about unrecognised properties isn't a problem though?

In this case, I think I'm looking for a warning not that extraIncludes is
missing, but that we have a field we are ignoring...
Perhaps coupling this with some knowledge of the expected yt version
would help, right?
If I have something made for yt x.y and it doesn't include a field that x.y
required, then we warn/error?
On 5 February 2016 at 04:10, James Crosby<EMAIL_ADDRESS>wrote:

This is a little tricky, because we want to maximise compatibility: this
means that old versions of yotta should probably ignore module.json
properties introduced in new versions, and we can't simply add a warning
that "extraIncludes" is missing, because it's use is regarded as bad
practise, not to be encouraged ;)
Possibly things are stable enough now that warning about unrecognised
properties isn't a problem though?
—
Reply to this email directly or view it on GitHub
https://github.com/ARMmbed/yotta/issues/697#issuecomment-180282975.

:thumbsup: having a minimum required yotta version in module files is definitely a good idea.
Also warning about unknown properties is something we should do: this would be a simple change to the schema, but if we want to have them as a separate level of warning/error than other schema errors, then we'll need to do it differently.

I guess one counter to this is that in the npm land you can have a lot of extra config in the package.json which isn't necessarily for npm. For example, we have eslintConfig as a property rather than an extra eslintrc file. Do you want to force a separate configuration file for that rather than collecting all config in one place for a given module?
Regardless, required version of Yotta seems helpful as you mutate it.

The minimum yotta version can now be specified (#703 / #706) :)
Having other tools store config at the root of module.json seems a bit risky: a good reason to do it might be to experiment with extra tools which provide functionality that might become core to yotta in the future (possibly this is why it it's allowed in npm, I don't know), but otherwise it seems like it's like to cause confusion.

I think npm just isn't very fussy about what you put in there, I don't think there's a plan to merge any of the things sharing package.json into the core of npm because the community takes more responsibility for writing the modules using that configuration. Using the same eslint example the guys at npm would have to pick one of X linters as the packaged one which I don't think they'd be keen to do as it'd harm the community around the other ones.
And thanks for the heads up on the minimum version, did not see that!


Changelog notes missing for SQS packages

Currently your changelog notes have the most recent mention of SQS package updates for the <IP_ADDRESS> version, As of this writing, the current version is <IP_ADDRESS>, and we'd like to see what changed between <IP_ADDRESS> and current. We are using AWSSDK.SQS from nuget. Any info would be helpful.

The point releases were done because there was a new version of AWSSDK.Core that we wanted everybody to pick up. In order to do that we needed to bump the AWSSDK.SQS version and all of the other NuGet packages with the dependencies update.
You can see that in the changelog when there is a core update it will say "All services packages updated to require new Core". If we listed every package when we do that the change log would be huge.

closing due to inactivity.


Turn by object

Now if the camera is tied to an object, it will look straight all the time, and to rotate it, you need to use manual_control, which is quite difficult since you need to take into account the speed of the object. For example, in a racing game, the car is standing still and when turning left or right, if you send a manual_control message, the camera will turn while only the wheels will turn, and not the car itself.

Added the follot_object_rotations property in 1.5.0.